Using a Conbee II, and I just noticed that a Osram E27-lamp was causing unusual behaviour in the network.
When this lamp was turned off, it sometimes - but not always - turned off other outlets and lights. This went on for a few weeks, and finally the device disappeard from phoscon.
It broke down.
And at the same time, the network went back to function normally again.
This implies that a device can poison the mesh if it’s “out of bounds”?
Or is there any safeguards within the protocol that marks a device as “broken”?
You can have some funny result with “zigbee group feature”, but the problem is permanent, not like you.
You can check event in Phoscon/help/Api Information, to see if it come from some (obscure) automation.
And yes there is "safeguards " in the protocol, but if the issue is not permanent, the device can be set as working again some minuts after. Some users use Zigbee device on electrical switch, so the device join when the switch is on, and leave when the switch is off, realy bad idea, but it work, the zigbee network is dynamic enought.
Make the test with another bulbs at same position.
the device disappeard from phoscon
Grayed (as unrechable) or disapear from the API and need to be included again ?
Ha ok, so it mean “not reachable”
But your issue is strange ^^, If a device freeze, I can understand it stop to react, but how it turn off other device than it when you try to turn this one off …
If it break the zigbee network, it can make others devices stop react too, but not turn them off in same time.