9dd9f33b4a
* OTA privacy enhancement Adds the option to disallow device-initiated OTA update checks. Currently these OTA update checks can be quite frequent, and essentially mean the device is indirectly able to ping a cloud server. In the EU it's wise to handle an IP address as personal information, and therefore it might be wise to not enable OTA checking by default. Ideally a user would agree to a privacy policy that clarifies things a bit first. * Added default settings for OTA update management * Set update interval in minutes * OTA update settings * Adds both settings for OTA updates control * Update settings.schema.json * Update settings.js * Update otaUpdate.js * Update otaUpdate.test.js * Update bridge.test.js Co-authored-by: Koen Kanters <koenkanters94@gmail.com> |
||
|---|---|---|
| .github | ||
| data | ||
| docker | ||
| images | ||
| lib | ||
| scripts | ||
| test | ||
| .dockerignore | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitignore | ||
| .npmignore | ||
| .npmrc | ||
| cli.js | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| index.js | ||
| LICENSE | ||
| npm-shrinkwrap.json | ||
| package.json | ||
| README.md | ||
| update.sh | ||
Zigbee2MQTT 🌉 🐝
Allows you to use your Zigbee devices without the vendors bridge or gateway.
It bridges events and allows you to control your Zigbee devices via MQTT. In this way you can integrate your Zigbee devices with whatever smart home infrastructure you are using.
Getting started
The documentation provides you all the information needed to get up and running! Make sure you don't skip sections if this is your first visit, as there might be important details in there for you.
If you aren't familiar with Zigbee terminology make sure you read this to help you out.
Integrations
Zigbee2MQTT integrates well with (almost) every home automation solution because it uses MQTT. However the following integrations are worth mentioning:
Home Assistant
- Home Assistant: Using the official addon
- Generic install or Hassbian: Using instructions here
Domoticz
- Integration implemented in domoticz-zigbee2mqtt-plugin
Architecture
Internal Architecture
Zigbee2MQTT is made up of three modules, each developed in its own Github project. Starting from the hardware (adapter) and moving up; zigbee-herdsman connects to your Zigbee adapter an makes an API available to the higher levels of the stack. For e.g. Texas Instruments hardware, zigbee-herdsman uses the TI zStack monitoring and test API to communicate with the adapter. Zigbee-herdsman handles the core Zigbee communication. The module zigbee-herdsman-converters handles the mapping from individual device models to the Zigbee clusters they support. Zigbee clusters are the layers of the Zigbee protocol on top of the base protocol that define things like how lights, sensors and switches talk to each other over the Zigbee network. Finally, the Zigbee2MQTT module drives zigbee-herdsman and maps the zigbee messages to MQTT messages. Zigbee2MQTT also keeps track of the state of the system. It uses a database.db file to store this state; a text file with a JSON database of connected devices and their capabilities.
Supported devices
See Supported devices to check whether your device is supported. There is quite an extensive list, including devices from vendors like Xiaomi, Ikea, Philips, OSRAM and more.
If it's not listed in Supported devices, support can be added (fairly) easy, see How to support new devices.
Support & help
If you need assistance you can check opened issues. Feel free to help with Pull Requests when you were able to fix things or add new devices or just share the love on social media.