deCONZ: add-on halted once started

My deCONZ add-on running for a long time with a ConBee II stick recently stopped working.

  • Raspberry Pi 4
  • HA Core 2024.2.5
  • Supervisor 2024.02.1
  • Operating System 12.0
  • Frontend 20240207.1
  • deCONZ 6.23.0

The add-on is configured with the correct device id. No network ports were changed.

The only change I have applied to my instance before was the addition of HA cloud remote access including the use of a custom domain. The remote access was working fine until there was some HA restart. On HA startup, the add-on ran into an infinite loop because of the enabled watch dog. In the end my whole HA instance crashed and became locally inaccessible as well.

Now I have managed to revive my instance again with the exception of the deCONZ add-on. Its logs always look like this (this is the full log - I tried it with both ConBee II and III sticks):

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/firmware.sh
[08:36:33] INFO:
cont-init: info: /etc/cont-init.d/firmware.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
cont-init: info: running /etc/cont-init.d/novnc.sh
cont-init: info: /etc/cont-init.d/novnc.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun deconz (no readiness 
notification)
services-up: info: copying legacy longrun nginx (no readiness 
notification)
services-up: info: copying legacy longrun otau-deconz (no readiness 
notification)
services-up: info: copying legacy longrun otau-ikea (no readiness 
notification)
services-up: info: copying legacy longrun otau-ledvance (no readiness 
notification)
services-up: info: copying legacy longrun websockify (no readiness 
notification)
[08:36:34] INFO: Websockify waiting for VNC to start
[08:36:34] INFO: Running the deCONZ OTA updater...
[08:36:34] INFO: Running the OSRAM LEdvance OTA updater...
s6-rc: info: service legacy-services successfully started
[08:36:34] INFO: Running the IKEA OTA updater...
[08:36:35] INFO: Starting VNC server (local/yes)...
[07:36:36] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[07:36:36] INFO: Service restart after closing
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

I am also unable to discover the gateway via Phoscon App. In the integrations section of the UI, the deCONZ integration also reports that it is unable to initialise. It seems that it has someting to do with the start of the VNC server as the add-on halts right afterwards. Maybe there is some connection to the remote access topic.

How can I solve this? I highly appreciate any suggestions! :pray:

I have somehow managed to solve this on my own. Not really sure what exactly did the trick. Somewhere in the forum I found the suggestion to run the command

ha supervisor repair

in the console. In addition, I followed @zbeez 's perfectly elaborated walkthrough here:

After that, everything seems to be working again. :sweat_smile: I would really love to know what hammered my setup before but I guess this will remain a mystery.

1 Like