Z-Stack_3.x.0 router 20250403 feedback

[Koenkk]

Update 2025-07-10: this firmware has now officially been released

Caution

This is a router firmware, for the coordinator variant see #545

Warning

After flashing 20250403 it might still show 20221102 in the Z2M frontend, pressing the re-interview button on the device page will fix this

Changelog (compared to 20221102)

• Updated SimpleLink SDK to 8.30.01.01
• Enable child ageing (but not for older Xiaomi devices which don't support it)

Firmwares

• CC1352P2_CC2652P_launchpad_router_20250403.zip
• CC1352P2_CC2652P_other_router_20250403.zip
• CC1352P7_router_20250403.zip
• CC2652R_router_20250403.zip
• CC2652R7_router_20250403.zip
• CC2652RB_router_20250403.zip
• CC2674P10_router_20250403.hex.zip: not available for now, wip

[Joylancer]

Sonoff Dongle-P
updatet from 20221102 to 20250403
with ti-flasher (.bin) and with https://dongle.sonoff.tech/sonoff-dongle-quick-flasher/ (.hex)
flash successfully, new connectetd, after flash shows always firmware 20221102

[chris-1243]

Try to interview your device to force the update of the information.

I flashed a SLZB07P7 and everything is fine

[Koenkk]

@chris-1243 thanks, added to the OP

[backlink-market]

same here

[backlink-market]

already tried this one.
It says: Installation success
Firmware has been successfully installed.

But debug log:
2025-04-13 19:02:46 emscripten smlight_cc_flasher.command[42] DEBUG *** Wrote 0/2 bytes
Means nothing has been written in my eyes
smlight_flasher (9).log
I already tried different sticks because I have 3 repeater.
I already tried:
-ZigStarGW-MT.exe (86er) with error: timeout waiting for ack/nack after sync (0x55 0x55)
-https://smlight.tech/flasher/#other_cc says success but log shos 0 Bytes written

• Smart Flash programer 2 (1.8.2) Success but version does not update
• https://dongle.sonoff.tech/sonoff-dongle-quick-flasher/ says success but version stays the same

[Joylancer]

re-interview sucessfully ?

[backlink-market]

Iobroker does not have such a button, just a re-configure button. When I push it:

zigbee.0 | 2025-04-13 19:38:33.808 | info | DeviceConfigure successful 0x00124b002a2e21fb ti.router
zigbee.0 | 2025-04-13 19:38:33.709 | info | Configuring 0x00124b002a2e21fb ti.router

[Koenkk]

@backlink-market try to force remove, restart io broker and pair it again.

[backlink-market]

@backlink-market try to force remove, restart io broker and pair it again.
Great :) that works !!!

[Joylancer]

force re-interview work, now show correct Firmware

[backlink-market]

what system?

[Joylancer]

Sonoff Dongle-P as Router 20250403, Debian stable, Z2M current dev
Coordinanor: Sonoff Dongle-P 20240710
flashed with: https://dongle.sonoff.tech/sonoff-dongle-quick-flasher/

[raveit65]

I tried to update my slzb-06 (CC2652P) with ti-flasher2 v1.82 and following this guide https://smlight.tech/manual/slzb-06/guide/flashing-and-updating/updating-zigbee.html#over-the-usb-update-slzb-06 . CP210x_Universal_Windows_Driver usb driver is installed and i pressed button Zigbee Flash Mode in slzb webinterface.
But i get always this error.

>Initiate access to target: COM3 using 2-pin cJTAG.
>Reading file: C:/Users/Rave it/Downloads/slzb-06_firmware/router/CC1352P2_CC2652P_other_router_20250403/CC1352P2_CC2652P_other_router_20250403.hex.
>Unknown record type: 3.
>Reset target ...
>Reset of target successful.

What does unknown record type:3 mean, btw. how can i fix it?

[backlink-market]

Check this: #397 (comment)
srec_cat.exe "CC1352P2_CC2652P_launchpad_coordinator_20240710.hex" -intel -o CC1352P2_CC2652P_launchpad_coordinator_20240710.bin -binary

Here is the .bin file so you can skip the step above with srec: CC1352P2_CC2652P_launchpad_router_20250403.zip

Use the .bin then it works with this tool
alternative you can use the browser tools:

https://dongle.sonoff.tech/sonoff-dongle-quick-flasher/
https://smlight.tech/flasher/#other_cc

[raveit65]

Thanks, converting to .bin and flashing with ti-flasher was successful. Of course old version was shown in slzb web interface.
But i couldn't pair the router anymore with my zigbee network! So i flashed back to old version for the moment and got the device working again :-)
I am still confused about the fw version. I thought i had to use CC1352P2_CC2652P_other_router_20250403 for slzb-06 (CC2652P) because i used CC1352P2_CC2652P_other_coordinator_20250321 to flash the device as coordinator. But maybe that is wrong for router mode?

[backlink-market]

did you use my bin file? because thats the launchpad and not other_coordinator version

[raveit65]

I didn't used yours, because smlight mentioned ....other_coordinators in their manual, see https://smlight.tech/manual/slzb-06/guide/flashing-and-updating/updating-zigbee.html#over-the-usb-update-slzb-06. For this reason i created a bin from CC1352P2_CC2652P_other_router_20250403.hex for myself.
Did you use your CC1352P2_CC2652P_launchpad_router_20250403.zip for a slzb-06 or for another coordinator?
I don't want to use the wrong fw.

Edit: this list mentioned CC1352P2_CC2652P_other_*.zip for SMLIGHT SLZB-06 POE Ethernet WiFi USB Zigbee adapter https://github.com/Koenkk/Z-Stack-firmware/blob/master/coordinator/Z-Stack_3.x.0/bin/README.md

[raveit65]

I tried flashing again using HA-addon TubesZB TI CC2652 FW Flasher. Same result.
Flashing seems successful.

....
....
 Write 248 bytes at 0x0002FA68
 Write 248 bytes at 0x0002FB60
 Write 248 bytes at 0x0002FC58
Write 104 bytes at 0x00057F98
    Write done                                
Verifying by comparing CRC32 calculations.
    Verified (match: 0x5f2c1af6)
[23:55:50] INFO: cc2652-flasher-up script exited with code 0
s6-rc: info: service cc2652-flasher successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service cc2652-flasher: stopping
s6-rc: info: service cc2652-flasher successfully stopped
s6-rc: info: service banner: stopping
s6-rc: info: service banner successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping

Full log here: https://www.dropbox.com/scl/fi/818a5qw9ie45d79hcg5l7/log-flasher.txt?rlkey=8loep3z5npuw28qa04wfx84cw&dl=0
Then i restarted device with web-interface but device isn't connect anymore with zigbee network.
Force re-interview ended up in...

[2025-04-16 00:03:10] error: 	z2m: Request 'zigbee2mqtt/bridge/request/device/interview' failed with error: 'interview of 'Router Wohnz' (0x00124b002e1e1056) failed: Error: Interview failed because can not get active endpoints ('0x00124b002e1e1056')'

No idea what is wrong. Maybe new fw doesn't work with my adapter?

[mamrai1]

Sonoff dongle p flashed with web flasher and working as expected….3 days now…

[Onepamopa]

So, there's newer router firmware, it's just SLZB-06 developers not "offering" it via the "Check for newer zigbee firmware" menu....

[pierrepinon]

No errors for me after many days

[an333]

I have a SMLIGTH SLZB-07p7. After flashing with this firmware, it works fine, but falls off every 2-3 days. z2m was v2.2, today I updated to 2.3

[Nik71git]

Just flash my zstack router (sonoff dongle P), I need to pair it again and did again the interview to read the correct firmware release.
Now I'm doing test but seems to work well as expected.
Now the signal range is -20 to 20 (I assume dB) but as far as I know that hardware antenna (sonoff dongle 3.0 P) is fixed at 5 dB or I'm wrong?

[Koenkk]

Firmware is now officially released! https://github.com/Koenkk/Z-Stack-firmware/releases/tag/Z-Stack_3.x.0_router_20250403

[mrmaximas]

@Koenkk Is it possible to change the IEEE address of the Dongle P 2652P2 router, as it was originally copied to my current HMG-01 PoE 2652P7 coordinator?

[Koenkk]

Some flashing tools allow for it, e.g. Uniflash.

[mrmaximas]

Some flashing tools allow for it, e.g. Uniflash.

@Koenkk thanks! solved with the ZigStar GW Multi tool