All updates are performed with “apt-get” using Raspbian packages:
pi@raspberry4:~ $ cat /etc/apt/sources.list.d/deconz.list
deb http://phoscon.de/apt/deconz buster-beta main
I do have some older backups, but are you sure that these would help? All components are still there, they’re just greyed out (in Phoscon) and communication doesn’t seem to work. Please note that I’m running in headless mode with “-platform minimal”.
Yes, I’m quite sure. There’s some related good news: I’ve discovered that re-pairing each of my Zigbee devices one by one brings them successfully back into the network under their original names and settings,
What can cause this type of failure (different devices needing a re-pair all at once) and how can it be prevented in the future?
It’s quite unlikely that all the different devices would leave the network at the same time for reasons unrelated deCONZ, isn’t it? What deCONZ problem could cause this behaviour?
What “sensor” and “router” do you refer to? The only sensor is the default “Tageslichtsensor/Phoscon/Virtueller Sensor”.
It s for that I m asking. Xiaomi/aqara sensors can left if they are without parent too much long time, but if you have only router, it s another problem.