After updating my Raspberry Pi to the Bullseye version, I encountered an unexpected problem: my deCONZ installation kept losing the connection to the ConBee II stick. Both piVCCU and deCONZ run on the Raspberry Pi to enable control and automation of my smart devices. But after the update, a conflict between the two services caused me problems.
The problem: conflict between deCONZ and CuX-Daemon
After several tests, it turned out that the error was caused by the CuX-Daemon add-on. As soon as I stopped CuX-Daemon, deCONZ worked without interruption and maintained a stable connection to the ConBee II stick. However, when I started CuX-Daemon again, deCONZ lost the connection to the stick again. A look at the status of the add-on provided information: CuX-Daemon established a connection to the ConBee II stick itself, which apparently interfered with deCONZ and led to the connection being lost.
Solution: Specific setting for CuX-Daemon
To permanently solve the problem, I had to make a specific setting in the CuX-Daemon. By configuring the parameter TTYPARAM=1-1.4, the add-on could be instructed to only establish a connection to a specific device. With this adjustment, CuX-Daemon now communicates exclusively via the device I specified, so that deCONZ continues to have unrestricted access to the ConBee II Stick. Since then, the interaction between deCONZ and CuX-Daemon has worked smoothly.
Summary and recommendation
If you are also faced with connection problems between deCONZ and the ConBee II Stick after an update to Bullseye and are using the CuX-Daemon add-on, the setting TTYPARAM=1-1.4 can be an effective solution. With this small adjustment, I was able to restore the stability of my configuration and continue to operate my smart home without any problems.
In the Smart Home category you will find other interesting articles on the topic of Smart Home.