Skip to main content

qToggleServer integration with Zigbee2MQTT

Project description


About

This is an add-on for qToggleServer.

It provides a peripheral driver that exposes ports for Zigbee devices controlled by Zigbee2MQTT.

Install

If you run qToggleOS, you'll need Zigbee support.

Install using pip:

pip install qtoggleserver-zigbee2mqtt

Peripheral Driver & Parameters

driver: qtoggleserver.zigbee2mqtt.Zigbee2MQTTClient

mqtt_server

  • type: string
  • default: required
  • example: "test.mosquitto.org"

mqtt_port

  • type: integer
  • default: 1883

mqtt_username

  • type: string
  • default: null

mqtt_password

  • type: string
  • default: null

mqtt_client_id

  • type: string
  • default: qtoggleserver

mqtt_reconnect_interval

Represents the interval, in seconds, between two (re)connection attempts to the MQTT server.

  • type: integer
  • default: 5

mqtt_base_topic

  • type: string
  • default: "zigbee2mqtt"

mqtt_logging

Indicates whether the logs generated by the MQTT client will be added to the qToggleServer or not.

  • type: boolean
  • default: false

bridge_prefix

Sets an optional prefix for bridge-specific ports (such as permit_join). This is useful when multiple Zigbee2MQTT bridges are used, to avoid name clashes.

  • type: string
  • default: ""

bridge_logging

Indicates whether the logs generated by the Zigbee2MQTT bridge will be added to the qToggleServer or not.

  • type: boolean
  • default: false

bridge_request_timeout

Indicates the timeout, in seconds, when waiting for a response (via MQTT) when sending a request (via MQTT) to the bridge.

  • type: integer
  • default: 10

permit_join_timeout

Indicates the timeout, in seconds, to permit new Zigbee devices to join, once enabled.

  • type: integer
  • default: 240

device_config

Allows specifying static configuration for particular Zigbee devices. Each entry in the dictionary is the (friendly) name of a device associated to a configuration dictionary or a wildcard pattern that friendly names of devices must match. See Device Configuration for details on the available configuration options.

  • type: dictionary
  • default: {}

Device Configuration

The following configuration options are available for a device:

get_state_property

Some Zigbee devices won't allow obtaining the current state by doing a get {"state": ""}. Instead, they need one of the specific properties to be requested, such as get {"temperature": ""}. This option allows setting the name of this property. If set to null, disables querying for state. See zigbee2mqtt/FRIENDLY_NAME/get for details.

  • type: string
  • default: "state"

force_port_properties

By default, exposed capabilities with category set to config or diagnostic, along with exposed options, will be treated as attributes of the corresponding qToggle control port. This option allows specifying a list of property names that will be associated to dedicated qToggle ports, regardless of their category (see zigbee2mqtt exposes for details). Capability (property) names are dot separated when they are part of a composite type (e.g. color.hue). Wildcards are also supported (e.g. color.* will match all the properties inside the color composite type).

  • type: [string]
  • default: []

force_attribute_properties

By default, exposed capabilities with no category set will be treated as standalone qToggle ports. This option allows specifying a list of property names that will become attributes of the corresponding control port, regardless of their category (see zigbee2mqtt exposes for details). Capability (property) names are dot separated when they are part of a composite type (e.g. color.hue). Wildcards are also supported (e.g. color.* will match all the properties inside the color composite type).

  • type: [string]
  • default: []

rename_properties

Allows renaming the property names of exposed capabilities, regardless of whether they become standalone qToggle ports or attributes of the corresponding control port. Each entry in the dictionary is a regex pattern that is matched against the full dot-separated property path (e.g. color.hue), associated to a replacement string. The first matching pattern wins. Group references (e.g. \1) are supported in the replacement string.

  • type: {string: string}
  • default: {}

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

qtoggleserver_zigbee2mqtt-1.10.3.tar.gz (18.7 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

qtoggleserver_zigbee2mqtt-1.10.3-py3-none-any.whl (18.4 kB view details)

Uploaded Python 3

File details

Details for the file qtoggleserver_zigbee2mqtt-1.10.3.tar.gz.

File metadata

File hashes

Hashes for qtoggleserver_zigbee2mqtt-1.10.3.tar.gz
Algorithm Hash digest
SHA256 f1860703c7cb62b0eff09a0164c8e0e4a8161b3f185e5f7ef4a6e400300cbcb2
MD5 66e0f164b677fd98bed6acaaca4c9b9e
BLAKE2b-256 0dcdeb3ed09e02044ece031dd31a5145d24ffaf9aa91da0940469ab0f3d86680

See more details on using hashes here.

File details

Details for the file qtoggleserver_zigbee2mqtt-1.10.3-py3-none-any.whl.

File metadata

File hashes

Hashes for qtoggleserver_zigbee2mqtt-1.10.3-py3-none-any.whl
Algorithm Hash digest
SHA256 90a8508ef552d54eee4425b1e70561058d657e8493eed773cc051b307aca9400
MD5 82f2e7e1f6edf5d502e2e5183eef44b5
BLAKE2b-256 c2f7314d8a3e5d33381426ea0150a9a90edfe697c157c67b1e9fe5aac6ecb49f

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page