In order to sometimes get a view of the mesh, I’m stopping deconz headles and starting the gui instead.
After switching back to headless some switches (aqara smart switches) disconnect from the hub. The devices are still listed but don’t receive any updates.
This results in reconnecting the switches.
What could be the reason for this behaviour?
Another thing is: I just connected a windows sensor from lidl. It’s there in the gui and also through the rest api, but does not appear on phoscon app. Any ideas on that?
No, if it happen it s not normal.
But battery device are lazy, some of them can stay in stand by during 1 hour.
Another thing is: I just connected a windows sensor from lidl. It’s there in the gui and also through the rest api, but does not appear on phoscon app. Any ideas on that
Yes this is normal too, phoscon is just an application that use the API, it don’t support all devices.
Right, but I have some sonoff device that pressing the button do nothing too.
Just wait 1 hour, if after that the device is not back, there is a real issue.
Ok, there is really something very strange in my network.
I again switched from headless to gui. Now I deactivated the headless service and activated the gui service.
The first result was, that my Conbee 2 didn’t get up - blocking my homebridge from starting. When reverted back to deconz service, the conbee came back.
And I again lost connection to a switch. I gave the thing now 5 hors to recover, but nothing.
The switch is still shown as reachable. But no button events are catched…
What is wrong here?