You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a SONOFF "Zigbee 3.0 USB Dongle Plus V2" coordinator, two ESP32-C6 routers and an ESP32-C6 end device. (There are also another 14 devices, half of them are routers.)
If I restart Home Assistant (i.e. the coordinator is restarted) then the ESP32-C6 end device will unconditionally change the parent router that it's connected to. The candidates for this are the two ESP32-C6 routers and the coordinator itself (because the other non-ESP routers have lower transmit power).
It then never changes to a different router unless that router or the coordinator is restarted again, even if the new parent router is further away. This can mean the end device is connected to a router that is too far away (in another building) for reliable communication.
I'd expect the end device to change back to the closer router that it preferred to use on startup.
Additional context.
I'm using zb_nwk_get_parent() and exposing that as an analog input value to monitor it.
I've tested with 0.9.4 and 1.0.0.
The text was updated successfully, but these errors were encountered:
github-actionsbot
changed the title
Unconditional change of router by the End Device when the Coordinator restarts
Unconditional change of router by the End Device when the Coordinator restarts (TZ-430)
Nov 25, 2023
Question
I have a SONOFF "Zigbee 3.0 USB Dongle Plus V2" coordinator, two ESP32-C6 routers and an ESP32-C6 end device. (There are also another 14 devices, half of them are routers.)
If I restart Home Assistant (i.e. the coordinator is restarted) then the ESP32-C6 end device will unconditionally change the parent router that it's connected to. The candidates for this are the two ESP32-C6 routers and the coordinator itself (because the other non-ESP routers have lower transmit power).
It then never changes to a different router unless that router or the coordinator is restarted again, even if the new parent router is further away. This can mean the end device is connected to a router that is too far away (in another building) for reliable communication.
I'd expect the end device to change back to the closer router that it preferred to use on startup.
Additional context.
I'm using
zb_nwk_get_parent()
and exposing that as an analog input value to monitor it.I've tested with 0.9.4 and 1.0.0.
The text was updated successfully, but these errors were encountered: