- Git clone this project into your apps folder
- Remove the
imagekey fromzigbee2mqtt-edge/config.jsonto enable local builds. - Add back
"image": "zigbee2mqtt/zigbee2mqtt-edge-{arch}"tozigbee2mqtt-edge/config.jsonafter you're done.
- Change the version number in
zigbee2mqtt/config.json:"version": "$NEW_VERSION" - Update
zigbee2mqtt/CHANGELOG.md - Commit the changes to
masterbranch - Wait till ci finishes
- Publish a new "Release". Very important you specify Target: master. Example
Tag version: v1.25.2-1 @ Target: master
Release title: v1.25.2-1
When you want to check the impact of developing work, e.g. adjusting devices in zigbee-herdsman-converters, you need access to the app container in Home Assistant. Here's how:
🚨 Following these directions will make your Home Assistant system more prone to misconfiguration (by yourself) to the extent of rendering it completely useless, so only touch what you're confident to and "know what you do".
- install the Portainer app from the App store
- Make sure to disable its
Protection mode:
- Start Portainer and
Open Web UI - in the left menu,
- head to
Settings> section Hidden Containers and removeio.hass.type:addon - go to
Containers,addon_[…]_zigbee2mqtt,Console,Connect
- head to
- ℹ️ the location of zigbee-herdsman-converters for example is
/app/node_modules/zigbee-herdsman-converters - make your adjustments by copying or
vi'ing - Still in portainer, go back to the app's container and
Restart
- Install and setup
Advanced SSH & Web Terminalwith disabled safe mode - run
docker psand see which container name is the zigbee2mqtt one. (eg.addon_45df7312_zigbee2mqtt) - build your whole application with
npm run build - upload the resulting build to your HA instance (eg. vscode server via drag n drop)
- execute
docker cp(eg.docker cp <the location of your build>/. <container_name>:/app/node_modules/zigbee-herdsman-converters) - execute
docker restart <container name>
After work is done, don't forget to clean up and reintroduce the safety measures:
- re-add the filter
io.hass.type:addonfor Hidden Containers - re-activate the "Protection mode" of the Portainer