Hassio-zigbee2mqtt: Cannot enable option adapter: deconz

Created on 10 May 2020  路  5Comments  路  Source: danielwelch/hassio-zigbee2mqtt

Currently, it is not possible to add the entry

adapter: deconz

in the configuration file in order to enable raspbee/conbee support for z2m on hassio. Adding the entry simply has no effect, and it also doesn't appear in the configuration file

Most helpful comment

Just ran into this as well. Definitely need this fix, stability fixes just got merged into the latest zigbee-herdsman and Z2M release which should make this ready for primetime, see discussion here.

In the meantime I've found a workaround. If you use the SSH & Web Terminal add-on you can do the following:

  1. Add e2fsprogs-extra to the list of packages in the config of the SSH add-on. This is so it it makes chattr available for use within the add-on
  2. SSH in and do the following:

    • cd share/zigbee2mqtt

    • edit configuration.yaml and add "adapter":"deconz" under serial in the JSON and save

    • chattr +i configuration.yaml

This will make the configuration file immutable so that the add-on cannot re-write it and remove the adapter option. Then it will use the option and you'll get conbee support:

zigbee2mqtt:info  2020-06-10 13:31:19: Starting zigbee2mqtt version 1.14.0 (commit #unknown)
zigbee2mqtt:info  2020-06-10 13:31:19: Starting zigbee-herdsman...
CREATED DECONZ ADAPTER
zigbee2mqtt:info  2020-06-10 13:31:20: zigbee-herdsman started
zigbee2mqtt:info  2020-06-10 13:31:20: Coordinator firmware version: '{"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}'

NOTE once you do this you literally will not be able to edit the configuration via the UI in the supervisor panel. The only way to edit this file will be to go back to ssh and do chattr -i configuration.yaml to make it mutable again. Just something to be aware of.

All 5 comments

same here

Would be great to get this fixed. Currently no way to test the new Zigbee herdsman support of the Conbee with hassio that I have found.

Just ran into this as well. Definitely need this fix, stability fixes just got merged into the latest zigbee-herdsman and Z2M release which should make this ready for primetime, see discussion here.

In the meantime I've found a workaround. If you use the SSH & Web Terminal add-on you can do the following:

  1. Add e2fsprogs-extra to the list of packages in the config of the SSH add-on. This is so it it makes chattr available for use within the add-on
  2. SSH in and do the following:

    • cd share/zigbee2mqtt

    • edit configuration.yaml and add "adapter":"deconz" under serial in the JSON and save

    • chattr +i configuration.yaml

This will make the configuration file immutable so that the add-on cannot re-write it and remove the adapter option. Then it will use the option and you'll get conbee support:

zigbee2mqtt:info  2020-06-10 13:31:19: Starting zigbee2mqtt version 1.14.0 (commit #unknown)
zigbee2mqtt:info  2020-06-10 13:31:19: Starting zigbee-herdsman...
CREATED DECONZ ADAPTER
zigbee2mqtt:info  2020-06-10 13:31:20: zigbee-herdsman started
zigbee2mqtt:info  2020-06-10 13:31:20: Coordinator firmware version: '{"type":"ConBee2","meta":{"transportrev":0,"product":0,"majorrel":38,"minorrel":74,"maintrel":0,"revision":"0x264a0700"}}'

NOTE once you do this you literally will not be able to edit the configuration via the UI in the supervisor panel. The only way to edit this file will be to go back to ssh and do chattr -i configuration.yaml to make it mutable again. Just something to be aware of.

  1. Add e2fsprogs-extra to the list of packages in the config of the SSH add-on. This is so it it makes chattr available for use within the add-on

@mdegat01 This may appear stupid, but I'm unable to build the SSH addon locally so I'm not able to add e2fsprogs-extra to requirements.txt

Would you be able to point me in the right direction? Without the immutable config file, the addon rewrite the file everytime it's restarted :(

Thanks a lot for that workaround!

OK, I was able to install it in the running container but didn't have the right to set the immutable flag.
I had to install it in the main docker container of Home Assistant and was able to set the flag.

Sorry for that!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

talondnb picture talondnb  路  10Comments

aaamoeder picture aaamoeder  路  3Comments

backcountrymountains picture backcountrymountains  路  6Comments

highground88 picture highground88  路  7Comments

eric-zimmer picture eric-zimmer  路  6Comments