- Notifications
You must be signed in to change notification settings - Fork663
Official Zigbee2MQTT Home Assistant add-on
License
zigbee2mqtt/hassio-zigbee2mqtt
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
Caution
If you're using a Raspberry Pi, ensure you have at least a Raspberry Pi 4, as running it on a Raspberry Pi 3 may cause instability due to its limited resources.
- If you don't have an MQTT broker yet; in Home Assistant go toSettings → Add-ons → Add-on store and install theMosquitto broker add-on, then start it.
- Go back to theAdd-on store, click⋮ → Repositories, fill in
https://github.com/zigbee2mqtt/hassio-zigbee2mqttand clickAdd → Close or click theAdd repository button below, clickAdd → Close (You might need to enter theinternal IP address of your Home Assistant instance first). - The repository includes two add-ons:
- Zigbee2MQTT is the stable release that tracks the released versions of Zigbee2MQTT. (recommended for most users)
- Zigbee2MQTT Edge tracks the
devbranch of Zigbee2MQTT such that you can install the edge version if there are features or fixes in the Zigbee2MQTT dev branch that are not yet released.
- Click on the add-on and pressInstall and wait till the add-on is installed.
- Start the add-on by going toInfo and clickStart
- Wait a few seconds and pressOPEN WEB UI, you will now see the onboarding page. More information about the onboarding can be foundhere.
- Fill in the desired settings, for most setups changing the following is enough:
- Select your adapter underFound Devices, this will configure theCoordinator/Adapter Port/Path andCoordinator/Adapter Type/Stack/Driver.
- Fill in theClosests WiFi Channel to select the most optimal Zigbee channel.
- PressSubmit, Zigbee2MQTT will now start, wait a few seconds and refresh the page. You should now see the Zigbee2MQTT frontend.
- If it shows
502: Bad Gatewaywait a bit more and refresh the page. - If this takes too long (e.g. 2 minutes +) check theLog tab to see what went wrong.
- In case the add-on fails to start with the following error:
USB adapter discovery error (No valid USB adapter found). Specify valid 'adapter' and 'port' in your configuration., we need to fill in theserialsection. Format can be foundhere, but skip the initialserial:indent. e.g.:If you don't know the port and you have just one USB device connected to your machine tryadapter:zstackport:/dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0018ED3DDF-if00
/dev/ttyACM0or/dev/ttyUSB0or/dev/ttyAMA0. Else use theHome Assistant CLI and executeha hardware infoto find out.
- If it shows
For more information seethe documentation.
- Ensure that both environments are running the same version
- Ensure you canSSH to your Home Assistant OS (NOT to the SSH Add-on)
- Backup your standalone environment
datafolder (possibly leaving out thelogs/folder) - Start the Zigbee2MQTT HA add-on with a non-existing
ttydevice, to create thedatafolder - Restore your
datafolder contents into/mnt/data/supervisor/homeassistant/zigbee2mqtt, e.g. viascp -O -P 22222 -i PATHTOUSEDSSHKEY ./data/* root@hass:/mnt/data/supervisor/homeassistant/zigbee2mqtt/ - Configure your serial port and MQTT settings using the HA add-on configuration UI
- Edit the
/usr/share/hassio/homeassistant/zigbee2mqtt/configuration.yamlfile:- Ensure that the serial port section matches the one configured with the UI
- Remove any irrelevant sections from the config (e.g.
mqtt(if not needed),advanced/log_syslog,frontend)
- Start the add-on
The format is based onKeep a Changelog.
All notable changes to this project will be documented in theCHANGELOG.md file.
Version for releases is based onZigbee2MQTT format:X.Y.Z.
Any changes on the add-on that do not require a new version of Zigbee2MQTT will use the format:X.Y.Z-A whereX.Y.Z is fixed on the Zigbee2MQTT release version andA is related to the add-on.
Edge version will not maintain a CHANGELOG and doesn't have a version.
If you find any issues with the add-on, please check theissue tracker for similar issues before creating one. If your issue is regarding specific devices or, more generally, an issue that arises after Zigbee2MQTT has successfully started, it should likely be reported in theZigbee2MQTT issue tracker.
Feel free to create a PR for fixes and enhancements.
If you're submitting a PR and wish to test it locally:
- Gain root access to your Home Assistant installation
- In the Add-on Settings, Ensure "Watchdog" is turned off so the container isn't automatically restarted when it's stopped via the CLI
- Enter the
zigbee2mqttcontainer interactively.
docker exec -it $(docker ps | grep zigbee2mqtt | cut -d" " -f 1) /bin/sh- Edit the file you'd like to test & save.
vi node_modules/zigbee-herdsman-converters/converters/toZigbee.js- Back on the Home Assistant installation, restart the
zigbee2mqttcontainer
docker restart $(docker ps | grep zigbee2mqtt | cut -d" " -f 1)- Refresh the web UI and perform your testing.
About
Official Zigbee2MQTT Home Assistant add-on
Topics
Resources
License
Contributing
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Packages0
Uh oh!
There was an error while loading.Please reload this page.

