DeCONZ constantly crashing / restarting

Configuration
, , ,
1

Hi all, suddenly I could not control my lights any more usin Home Assistant. After some debugging I realized it’s because the DeCONZ add-on keeps restarting (see logs below). I did not change a thing before (maybe something auto-updated, I don’t know …), yet actively I did not.

I already tried:

  • turning it off and on again …
  • re-installing it
  • completely uninstalling, then installing it
  • ha supervisor repair in the shell (from here - seems to be the same problem, yet the solution doesn’t help …)

… and nothing helped. I was hoping for some more pointers, because I lost basically every zigbee device in my apartment.

Remarks:

  • HASS is running on Proxmox
  • I’m using ConBee (II, I think)
    • yes, it is connected to HASS, and detected / available :slight_smile:

My current configuration:

# settings -> about
Core              2024.11.3
Supervisor        2024.11.4
Operating System  13.2
Frontend          20241106.2

The deCONZ logs:

[22:10:22] 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
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
[23:10:28] INFO: Path              | Serial      | Type
------------------+-------------+---------------
/dev/ttyACM0      | DE2436215   | ConBee_II
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-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)
[23:10:29] INFO: Websockify waiting for VNC to start
[23:10:29] INFO: Running the IKEA OTA updater...
[23:10:29] INFO: Running the OSRAM LEdvance OTA updater...
s6-rc: info: service legacy-services successfully started
[23:10:29] INFO: Starting VNC server (local/yes)...
[23:10:29] INFO: Starting websockify...
WebSocket server settings:
  - Listen on 127.0.0.1:5901
  - Web server. Web root: /usr/share/novnc
  - No SSL/TLS support (no cert file)
  - proxying from 127.0.0.1:5901 to 127.0.0.1:5900
[22:10:31] WARNING: Halt add-on
s6-rc: info: service legacy-services: stopping
[22:10:31] INFO: Service restart after closing

In exit
Closing socket listening at 127.0.0.1:5901
s6-rc: info: service legacy-services successfully stopped

... and repeat
2

I don’t use DeCONZ, so unfortunately, I can’t help you with that. However, I will let you know that I used to use it but have since switched to the Zigbee2MQTT add-on instead and haven’t had any problems since. In my opinion, it works much better.

3

I’ll take whatever works :slight_smile: . How would I do this change? Do you have a tutorial link, maybe?

4

There are three integrations you can use to control Zigbee devices. Ranked from worst to best, they are: DeCONZ, ZHA (Zigbee Home Automation), and Zigbee2MQTT.

Below is a link to a tutorial that explains how to install Zigbee2MQTT with a Conbee II. I’m using the same controller and I don’t have any issues. However, I recommend performing a full system backup just in case. That way, if something does go wrong or you decide you don’t like the new integration, you can easily restore your system to its previous state.

Tutorial - CLICK HERE
Video for above tutorial - CLICK HERE

5

yes, out of frustration i simply re-installed the full home assistant VM – luckily there was not too much going on in there.

and – what can I say – the home assistant zigbee integration … simply recognized my devices. and works. like magic. :smiley:

if zigbee2mqtt has more advantages (and i some more time later) i am tempted to try that one. thanks a lot for your hints!

1 Like