Koenkk
SONOFF Zigbee Dongle-P router doesn't rejoin
Hey,
I'm trying to include two additional Dongle-P as routers into my existing network. Tried CC1352P2_CC2652P_launchpad_router_20221102.hex and CC1352P2_CC2652P_launchpad_router_20250403.hex.
They join successfully, but once taken offline and plugged back in again, they never rejoin.
Is this by design? Any help would be greatly appreciated, thank you!
Edit: How often should such a router "ping" the network? After initially pairing, its "Last seen" time simply goes up. Edit 2: Also, joining the second router via the first one after successful pairing never succeeds. Edit 3: When selecting "Permit join (Router1)", it counts down, but when refreshing the Z2M page it says "Permit join (All)".
When trying to pair the second router via the first router, this always happens:
error 2025-09-16 12:40:41zh:controller: Interview failed for '0x00124b0032d41312 with error 'Error: Interview failed because can not get node descriptor ('0x00124b0032d41312')'
error 2025-09-16 12:40:41z2m: Failed to interview '0x00124b0032d41312', device has not successfully been paired
Their descriptors differ.
Z2M: 2.6.1 commit: e9889e5d20e8911550d5231bc0349567cc2bb9ce Coordinator type: ZStack3x0 Coordinator revision: 20240710 Coordinator: SONOFF Zigbee Dongle-P
Hey, Not that I can answer your question, but to advise how I have "resolved" the last seen you mentioned (i.e. it just been an ever increasing number / time).
I have added a reporting of a basic stat (the version) with a minimum of 10 and max of 3600 and change of 0. To ensure that once every hour the router reports back in. Yes it creates more traffic... But it means that I have a clear way to see if this is still up, as if the last seen ever goes above and hour I know it is not working.
I really don't think this helps towards yours, but wanted to flag
Mine just silently goes unresponsive after a day or two, there are no errors or anything in the logs that I can find, they simply stop responding. Power cycling one have sometimes made it start repeating again, but then after a day or two it jus stops responding again. Soft rebooting it from the UI of a szlb-06 does not make it reconnect. Using firmware 20221102 (and also tried with the custom smlight 2025 firmware flashable from their web ui for the szlb-06). If I reflash the router firmware of a Sonoff Dongle P I can interview it again as it goes into join mode automatically after flashing, but then after a day or so it goes silent.
This behavior is consistent with two different Sonoff Dongle P, and one szlb-06 with the CC2652P chip. Running CC2652P as a coordinator works just fine (I have 3 different zigbee networks in various locations, two with a Sonoff Dongle P as coordinator, one with a szlb-06). All other router devices in the network works just fine, it is only these router flashed CC2652Ps failing consistently.
The only conclusions I can make is that either its something wrong with the router firmware for this chip, or I have the worst luck in the world with getting bad devices. Edit: Or perhaps its a conflict with using the same chiptype as coordinator? I have checked the IEEE id, and they differ.
For the future I'm sticking with EFR32MG24 based routers where needed, they work flawlessly.
Same here. Just flashed spare slzb-06 with router firmware and it unable to join network at all. Have tried 2025 same as 2022. Also, did the same with SONOFF Zigbee Dongle-P and it also unable to join network at all. Also, worth to mention - nothing in z2m logs.
Update: Sorry for being slightly off-topic as my router is a slzb-06, and not a sonoff dongle, but they are based on the same chip.
After flashing the (proprietary?) development firmware 20250325 from the web UI of the szlb-06 it still behaved as before (disconnected to never report in again after a day or two. But then I removed it from the network and rejoined it by enabling router reconnect in the web ui, this time it correctly identified itself as the new firmware and also got a corresponding icon in the z2m web ui. So far its been running for more then a week without stopping to report. So my problems with the slzb-06 seemed to resolve itself through the custom 20250325 firmware. Unfortunately this firmware doesnt seem to be available for other CC2652P dongles.