- Git clone this project into your add-ons folder
- Remove the
image
key fromnbogojevic/zigbee2mqtt-edge/config.json
to enable local builds. - Add back
"image": "zigbee2mqtt/zigbee2mqtt-edge-{arch}"
tozigbee2mqtt-edge/config.json
after you're done.
- Change the version number in
zigbee2mqtt/config.json
:"version": "$NEW_VERSION"
- Update
zigbee2mqtt/CHANGELOG.md
- Commit the changes to
master
branch - 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 add-on 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 addon from the Add-on 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 add-on's container and
Restart
After work is done, don't forget to clean up and reintroduce the safety measures:
- re-add the filter
io.hass.type
:addon
for Hidden Containers - re-activate the "Protection mode" of the Portainer