Hey guys, I observed some super strange behaviour when it comes to my Zigbee network which I cant explain to myself at all.
Using HA as VM on proxmox, I throughput some no-name zigbee cc2531 dongle (via device ID) to HM using the ZHA integration.
The Zigbee network works perfectly fine till I try to pair my Sonoff TRVZB radiator valves. It starts configuring and then the zigbee network fails. After restarting the dongle wont detected in ha nor proxmox. After restarting the whole proxmox node and swaping the dongle into another usb everything is up and running as before. Sadly the Sonoff TRVZB did not paired and will just shown as unavailable device in ha.
Debuging log contains 4600 lines of what so ever. Any ideas whats the connection between paring the new device within ha and disconnecting the dongle from the entire proxmox note? Hance any idea how to get around without migrating my whole network to zgibee2mqtt without knowing if this brings any change?
Changing to Zigbee2MQTT didnt solved the problem but I found out that the issue in Z2MQTT ont only occures when paring the Sonoff TRVZB but also for all other devices. In Z2MQTT this issue has been observed quite often due to missing compatibility and wrong firmware (see here CC2531 USB device disconnects when permit join enabled - General support - Zigbee2mqtt.
I will were able to get my valves in by rebooting the node after connecting every valve. I will observe if this only occurs when paring. If not I might just exchange the dongle with the Home Assitant Skyconnect.
Keep you posted here.
As mentioned changing to a more powerfull sonoff dongle-p with cc2652p chipset solved the issue on my side perfectly well after the cc2531 stick quited its job completly. If yours is not detected at all anymore might thinging about upgrading and reconfiguring the network or re-flashing the dongle might help.