John Doeandnurikk
d064a73131
* Update ci * Use package-lock * Use package-lock.json * Use cache for ci * Enable node18 windows * Revert "Enable node18 windows" This reverts commit e427551acdd64c3a256b48a5b8e86b3c4c986405. * Remove redundant cache * Don't do shrinkwrap * Remove shrinkwrap * Remove redundant step * Cache node-gyp * Debug * Add key * Update ci.yml * Add cache detection * Fix * Add deps * Fix2 * Update caches * Fix ci * Update patsh * Update paths * Update paths * Fix max cache path * Change cache key * Remove spaces * Split caches * Fix linux cache * Fix linux cache * Merge caches * Ignore errs * Find only dirs * Run find after ci * Fix mac cache * Fix caches * Remove env run Co-authored-by: nurikk <ainur@yojee.com>
Zigbee2MQTT 🌉 🐝
Allows you to use your Zigbee devices without the vendor's 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 and 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. Zigbee2MQTT provides a web-based interface that allows monitoring and configuration.
Developing
Zigbee2MQTT uses TypeScript (partially for now). Therefore after making changes to files in the lib/ directory you need to recompile Zigbee2MQTT. This can be done by executing npm run build. For faster development instead of running npm run build you can run npm run build-watch in another terminal session, this will recompile as you change files.
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) easily, 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.