Z-Stack_3.x.0 coordinator 20250321 feedback #545

2025-03-23 18:34:34z2m: Failed to configure 'Датчик температуры на кухне', attempt 1 (Error: Bind 0xa4c1380b27b90459/1 msTemperatureMeasurement from '0x00124b0022810ef5/1' failed (Status 'TABLE_FULL') at Endpoint.bind (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:565:23) at Object.bind (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/lib/reporting.ts:42:9) at configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/devices/custom_devices_diy.ts:865:13) at Object.configure (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman-converters/src/index.ts:357:21) at Configure.configure (/app/lib/extension/configure.ts:124:13) at EventEmitter.wrappedCallback (/app/lib/eventBus.ts:204:17))

Zigbee2MQTT version
[2.1.3](https://github.com/Koenkk/zigbee2mqtt/releases/tag/2.1.3) commit: [unknown](https://github.com/Koenkk/zigbee2mqtt/commit/unknown)
Coordinator type
zStack3x0
Coordinator revision
20250321
Coordinator IEEE Address
0x00124b0022810ef5
Frontend version
0.9.4
zigbee-herdsman-converters version
23.2.0
zigbee-herdsman version
3.2.7

1 reply

Koenkk Mar 23, 2025
Maintainer Author

This has nothing to do with the coordinator firmware, it means the binding table of the device is full.

Testmangh · 2025-03-24T03:04:52Z

Testmangh
Mar 24, 2025

Amount of devices in network: 125
Bridge software (Zigbee2MQTT/ZHA): Zigbee2MQTT 2.1.3-1
Coordinator: SLZB-06
20240315 worked fine: Worked until one week ago, the network starded to respond slowly to automations, and randomly the network would go completely offilne

I have 8 mmwave presence sensor in another network to avoid their spamming, different channels.

There are a lot of errors during start up and the sensors, lights, switchs are not responding, the entire network is down...

LOGs

45df7312_zigbee2mqtt_2025-03-24T03-19-11.382Z.log

45df7312_zigbee2mqtt_2025-03-24T11-04-22.056Z.log

4 replies

Koenkk Mar 26, 2025
Maintainer Author

What firmware does work fine for you?

Testmangh Mar 26, 2025

I'm travelling for work, as soon as I arrive home I will answer will, probably Friday.

Testmangh Mar 28, 2025

@Koenkk 20250321 is the firmware currently running on coordinator, Zigbee2MQTT version: 2.1.0-1.
I'm getting erros still but the net is up and really responsive...

45df7312_zigbee2mqtt_2025-03-28T10-32-39.443Z.log

Koenkk Mar 30, 2025
Maintainer Author

Could be some interference maybe, but good to hear it is working

Arcaios · 2025-03-24T14:54:13Z

Arcaios
Mar 24, 2025

Zigbee2MQTT 2.1.3
Coordinator: SLZB06 2.8.0dev (2.8.2dev3 so many issue for me)
Previous revision: 20221226 (the only stable one for me so far)
this is the first update for me where everything is going well. everything works perfectly! great job!

1 reply

lux73 Mar 24, 2025

which Coordinator and from which FW upgraded?

GofranAy · 2025-03-25T07:40:50Z

GofranAy
Mar 25, 2025

Hey i got some issues mine says after update.
Coordinator: SLZB06 2.8.2dev3
Revision: 20250321
update
went back to all the way to.
Revision: 20230507 this one seems working for now again

[2025-03-25 08:33:52] error: z2m: Publish 'set' 'state' to 'slaapkamer licht' failed: 'Error: ZCL command 0x54ef4410000f4a1a/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":31686,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":26,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,20,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'
[2025-03-25 08:34:24] error: z2m: Publish 'set' 'state' to 'Gangpad licht schakelaar' failed: 'Error: ZCL command 0x54ef441000367476/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (--> 'SREQ: AF - dataRequest - {"dstaddr":30794,"destendpoint":1,"srcendpoint":1,"clusterid":6,"transid":29,"options":0,"radius":30,"len":3,"data":{"type":"Buffer","data":[1,23,1]}}' failed with status '(0x02: INVALID_PARAM)' (expected '(0x00: SUCCESS)'))'

1 reply

Koenkk Mar 30, 2025
Maintainer Author

Could you provide the debug log of these errors on 20250321?

See this on how to enable debug logging.

snhnic · 2025-03-25T14:56:23Z

snhnic
Mar 25, 2025

Update to current firmware revision: 20250321 killed my Z2MQTT
[2025-03-25 09:54:11] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[2025-03-25 09:55:17] error: z2m: Error while starting zigbee-herdsman
[2025-03-25 09:55:17] error: z2m: Failed to start zigbee-herdsman
[2025-03-25 09:55:17] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-03-25 09:55:17] error: z2m: Exiting...
[2025-03-25 09:55:17] error: z2m: Error: network commissioning timed out - most likely network with the same panId or extendedPanId already exists nearby (Error: AREQ - ZDO - stateChangeInd after 60000ms

device model: SLZB-06P7V2
FW type: 0
FW version: v2.8.2.dev3
ZB FW type: 0
ZB FW mode: 0
ZB FW version: 20250321

12 replies

euroman2007 Mar 30, 2025

I did the update thru the interface of the SLZB adapter. Without turning of Zigbee2mqtt in home assistant first.

euroman2007 Mar 31, 2025

After a day or 2, devices stoped functioning again. Cant do anything. They do appear online and connected but when i turn a light on or when a state of a device changes when i open a door for example, the state in Zigbee2mqtt stays closed. And the light stays of. So i have just downgraded the zigbee firmware on my SLZB again and now zigbee2mqtt wont connect anymore. Again.........

euroman2007 Mar 31, 2025

[11:49:07] INFO: Preparing to start...
[11:49:07] INFO: Socat not enabled
[11:49:08] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[31-03-2025 11:49:08] info: z2m: Logging to console, file (filename: log.log)
[31-03-2025 11:49:08] info: z2m: Starting Zigbee2MQTT version 2.1.3 (commit #unknown)
[31-03-2025 11:49:08] info: z2m: Starting zigbee-herdsman (3.2.7)
[31-03-2025 11:49:08] info: zh:zstack:znp: Opening TCP socket with 192.168.2.10:6638
[31-03-2025 11:49:08] info: zh:zstack:znp: Socket connected
[31-03-2025 11:49:08] info: zh:zstack:znp: Socket ready
[31-03-2025 11:49:08] info: zh:zstack:znp: Writing CC2530/CC2531 skip bootloader payload
[31-03-2025 11:49:09] info: zh:zstack:znp: Skip bootloader for CC2652/CC1352
[31-03-2025 11:50:33] error: z2m: Error while starting zigbee-herdsman
[31-03-2025 11:50:33] error: z2m: Failed to start zigbee-herdsman
[31-03-2025 11:50:33] error: z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[31-03-2025 11:50:33] error: z2m: Exiting...
[31-03-2025 11:50:33] error: z2m: Error: SRSP - ZDO - startupFromApp after 40000ms
at Object.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/waitress.ts:67:23)
at /app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:252:45
at Queue.execute (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26)
at Znp.request (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:245:27)
at ZnpAdapterManager.beginStartup (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:285:28)
at processTicksAndRejections (node:internal/process/task_queues:105:5)
at ZnpAdapterManager.beginRestore (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:337:9)
at ZnpAdapterManager.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/manager.ts:79:21)
at ZStackAdapter.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:158:16)
at Controller.start (/app/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/controller.ts:136:29)

Jaegerstefan Mar 31, 2025

> After a day or 2, devices stoped functioning again. Cant do anything. They do appear online and connected but when i turn a light on or when a state of a device changes when i open a door for example, the state in Zigbee2mqtt stays closed. And the light stays of. So i have just downgraded the zigbee firmware on my SLZB again and now zigbee2mqtt wont connect anymore. Again.........

The same behaviour for me. 90% of the devices are shown as online in Z2M but pairing foails for a lot of devices and i have constant errors like this in my z2m log
[2025-03-31 11:45:43] debug: zh:controller:endpoint: Error: ZCL command 0xa4c13817c6650311/1 genPollCtrl.checkinRsp({"startFastPolling":false,"fastPollTimeout":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"re> at Object.start (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/waitress.ts:67:23) at /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:252:45 at Queue.execute (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/queue.ts:36:26) at Znp.request (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:245:27) at Znp.requestWithReply (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:224:34) at ZStackAdapter.sendZclFrameToEndpointInternal (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:671:50) at /opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:443:20 at Queue.execute (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20) at ZStackAdapter.sendZclFrameToEndpoint (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/adapter/z-stack/adapter/zStackAdapter.ts:441:16) at Request.send (/opt/zigbee2mqtt/node_modules/.pnpm/[email protected]/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:82:20) [2025-03-31 11:45:43] error: zh:controller:device: Handling of poll check-in from 0xa4c13817c6650311 failed (ZCL command 0xa4c13817c6650311/1 genPollCtrl.checkinRsp({"startFastPolling":false,"fastPollTimeout":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false>

Koenkk Apr 2, 2025
Maintainer Author

@snhnic How did you upgrade the firmware, can you reproduce it by re-flashing the firmware?

Sergi-CP · 2025-03-25T23:14:28Z

Sergi-CP
Mar 25, 2025

Hi! Sorry for my question but where I can find 20250318 revision?
Thanks

1 reply

Koenkk Mar 26, 2025
Maintainer Author

There is no such revision, only 20250321 (you can find it in the OP)

SkIIr · 2025-03-26T12:20:17Z

SkIIr
Mar 26, 2025

Sonoff-P and 20250321 running smoothly since yesterday. Currently no BUFFER_FULL errors with that one.

0 replies

napalmz · 2025-03-26T14:30:43Z

napalmz
Mar 26, 2025

Upgraded from 20240710 to 20250321.
Home Assistant + ZHA on SLZB-06 in Coordinator mode.
Routing problems, devices expose status but you cannot send commands (it fails 90% time).
Rolled back to 20240710 and everything is fine now.

Registratore: zigpy.zcl
Fonte: runner.py:154
Prima occorrenza: 12:16:49 (3 occorrenze)
Ultimo accesso: 13:36:15

[0xBD20:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zigpy/zcl/__init__.py", line 425, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<9 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/endpoint.py", line 304, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ ...<11 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 558, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ ...<11 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 373, in request await send_request() File "/usr/local/lib/python3.13/site-packages/zigpy/application.py", line 835, in request await self.send_packet( ...<14 lines>... ) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 959, in send_packet await self._send_request_raw( ...<11 lines>... ) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 850, in _send_request_raw response = await asyncio.shield( ^^^^^^^^^^^^^^^^^^^^^ ...<13 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy_znp/api.py", line 1112, in request_callback_rsp await self.request(request, timeout=timeout, **response_params) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/api.py", line 1066, in request self._uart.send(frame) ^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'send'
[0xBD20:1:0xef00] Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zigpy/zcl/__init__.py", line 425, in reply return await self._endpoint.reply( ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<9 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/endpoint.py", line 304, in reply return await self.device.reply( ^^^^^^^^^^^^^^^^^^^^^^^^ ...<11 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 558, in reply return await self.request( ^^^^^^^^^^^^^^^^^^^ ...<11 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 373, in request await send_request() File "/usr/local/lib/python3.13/site-packages/zigpy/application.py", line 835, in request await self.send_packet( ...<14 lines>... ) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 959, in send_packet await self._send_request_raw( ...<11 lines>... ) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 748, in _send_request_raw src_ep = self._find_endpoint(dst_ep=dst_ep, profile=profile, cluster=cluster) File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 700, in _find_endpoint self._zstack_build_id >= 20210708 ^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.13/site-packages/zigpy_znp/zigbee/application.py", line 610, in _zstack_build_id if self._version_rsp.CodeRevision is None: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'CodeRevision'
[0xEAEF:1:0x0020] Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 381, in request return await req.result ^^^^^^^^^^^^^^^^ asyncio.exceptions.CancelledError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zigpy/zcl/__init__.py", line 378, in request return await self._endpoint.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<9 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/endpoint.py", line 270, in request return await self.device.request( ^^^^^^^^^^^^^^^^^^^^^^^^^^ ...<11 lines>... ) ^ File "/usr/local/lib/python3.13/site-packages/zigpy/device.py", line 380, in request async with asyncio_timeout(timeout): ~~~~~~~~~~~~~~~^^^^^^^^^ File "/usr/local/lib/python3.13/asyncio/timeouts.py", line 116, in __aexit__ raise TimeoutError from exc_val TimeoutError The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/general.py", line 630, in check_in_response await self.checkin_response(True, self.CHECKIN_FAST_POLL_TIMEOUT, tsn=tsn) File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 85, in wrapper with wrap_zigpy_exceptions(): ~~~~~~~~~~~~~~~~~~~~~^^ File "/usr/local/lib/python3.13/contextlib.py", line 162, in __exit__ self.gen.throw(value) ~~~~~~~~~~~~~~^^^^^^^ File "/usr/local/lib/python3.13/site-packages/zha/zigbee/cluster_handlers/__init__.py", line 70, in wrap_zigpy_exceptions raise ZHAException("Failed to send request: device did not respond") from exc zha.exceptions.ZHAException: Failed to send request: device did not respond

1 reply

Testmangh Mar 26, 2025

I almost went crazy, downgraded the coordinator firmware, then the add on firmware tried several firmware combinations (add on <> coordinator) and nothing worked. I kinda gave up and was planning to delete everything and repair all devices (125). I left it alone, later that day the network started working again, I changed the coordinator firmware so much that I don't even remember the last firmware installed, it was either the 2024 or 2025 one... I don't know what happened but decide to accepted the unexplained victory 😂 I'm away from home.

lux73 · 2025-03-27T07:06:34Z

lux73
Mar 27, 2025

CC2652RB (slae.sh) upgraded to 20250321 without any issues - Network is up'n'running after Firmware upgrade

never experienced any Problem with old 20240710

System up with new FW since ~48h

Devices:
- Total 62
- End devices: 39 / TUYA, Danfoss, XIAOMI, Aqara, Moes
- Router:      23 / Philips, Signify, iluminize, TUYA, HEIMAN

3 replies

YellowNest Mar 27, 2025

I flashed my slae.sh stick but now get this

z2m: Error: SRSP - SYS - stackTune after 6000ms

YellowNest Mar 27, 2025

OK, After a few hours of troubleshooting, I managed to fix the issue. I had a line: 'disable_led: true' which I removed. I also uninstalled ModemManager, which was preventing zigbee2mqtt from starting after a reboot.

lux73 Apr 3, 2025

CC2652RB (slae.sh) upgraded to 20250321 without any issues - Network is up'n'running after Firmware upgrade

never experienced any Problem with old 20240710

System up with new FW since ~48h
Devices:
- Total 62
- End devices: 39 / TUYA, Danfoss, XIAOMI, Aqara, Moes
- Router:      23 / Philips, Signify, iluminize, TUYA, HEIMAN

After the upgrade 1 week ago, my system is still responsive and stable - I have not noticed any problems so far

snhnic · 2025-03-27T07:23:09Z

snhnic
Mar 27, 2025

I now got almost everything working again with 20250321 on one slzb-07 I changed panid and paired all devices again and on the other slzb-07 I changed the channel and got an empty z2mqqt then moved back to previous channel, got some devices returned by them self, but from the 111 devices still needed to pair most of them. This morning one of the devices disappeared. Still have a lot of repairing to do, mostly automations. But I get it done. It a shame an update can destroy our setup this way!

1 reply

lux73 Mar 27, 2025

weird... never had such any issue by upgrading my Coordinator FW

elmr91 · 2025-03-27T09:55:46Z

elmr91
Mar 27, 2025

Sonoff-P upgraded from 20240710 to 20250321.
Sonoff-E as router (old last router firmware)
20+ devices.
No problem since 24h (but never experienced BUFFER_FULL problem).

0 replies

alex-v-fraser · 2025-03-29T06:26:30Z

alex-v-fraser
Mar 29, 2025

hello!
I flashed Sonoff Zigbee USB stick CC2652P from 20230507 to 20250321 with CC1352P2_CC2652P_launchpad_coordinator_20250321.hex
It cannot start.

host log:

~ sudo dmesg | grep ttyUSB
[    3.984068] usb 2-1: cp210x converter now attached to ttyUSB0
[122327.043972] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[207883.664435] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[383494.995451] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[545893.055305] cp210x ttyUSB0: usb_serial_generic_read_bulk_callback - urb stopped: -32
[676940.986518] cp210x ttyUSB0: failed set request 0x0 status: -71
[676940.987512] cp210x ttyUSB0: cp210x_open - Unable to enable UART
[676940.990518] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0

Z2M log:

[09:24:30] INFO: Preparing to start...
[09:24:30] INFO: Socat not enabled
[09:24:30] INFO: Enabled Zigbee2MQTT watchdog with value 'default'
[09:24:30] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT with watchdog (2000,60000,300000,900000,1800000,3600000).
[2025-03-29 09:24:33] error: 	z2m: Error while starting zigbee-herdsman
[2025-03-29 09:24:33] error: 	z2m: Failed to start zigbee-herdsman
[2025-03-29 09:24:33] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start_crashes-runtime.html for possible solutions
[2025-03-29 09:24:33] error: 	z2m: Exiting...
[2025-03-29 09:24:33] error: 	z2m: Error: Error: No such file or directory, cannot open /dev/ttyUSB0

Z2M settings:

data_path: /config/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: "-d -d"
  log: false
mqtt:
  server: mqtt://33618668-mosquitto-custom-build
  user: mqtt
  password: mqtt
serial:
  adapter: zstack
  port: /dev/ttyUSB0
watchdog: default

1 reply

YellowNest Mar 29, 2025

Type

ls /dev/serial/by-id

Take that value and replace your port in configuration.yaml. Restart z2m

alex-v-fraser · 2025-03-29T07:43:37Z

alex-v-fraser
Mar 29, 2025

@YellowNest Thank you. It works.

0 replies

SkIIr · 2025-03-31T06:19:44Z

SkIIr
Mar 31, 2025

Sonoff-P and 20250321 with 96 devices, many China / Tuya stuff, running well since 6 days now.

Only some smoke detectors Tuya TS0205_smoke_2 / _TZ3210_up3pngle been shown as offline. But they are not much communicating that should not be related to the firmware. With one elder Z2M release they worked properly but with the last ones went back to be shown offline after a day or so. They come online again when devices button is being pressed for short (device test).

2 replies

Jaegerstefan Mar 31, 2025

i can confirm this with the TS0205_smoke_2 devices

Weltherrscher Apr 2, 2025

Which file did you use for flashing the zigbee chip on sonoff pro?
I have a Sonoff ZB Pro with Tasmota and would like to contribute.

raveit65 · 2025-04-01T14:56:42Z

raveit65
Apr 1, 2025

More than a week my uzg-01 (CC1352P7) runs fine with 20250321 fw. Seems the fw is stable here.
Update was from 99250304 fw.
Now i flashed one slzb-01(CC2652P) in a little test network (20 devices) from 20221226 to 20250321 and did run in the pan_id or ext-pan_id issue. :/
After generating new id's with pan_id: GENERATE and ext_pan_id: GENERATE the adapter starts well.
Of course repairing was needed.
In general i am thinking the new fw is a progress for the slzb, eg. faster pairing.
Hopefully it will run stable.
Anyway, the pan_id issue is annoying especially for bigger networks and should be investigate.
I never noticed this with the uzg-01 when updating.

2 replies

lux73 Apr 1, 2025

upgraded from 20240710 to 20250321 - had over 60 Devices in my Network and no need to re-pair neither had any PanID issues

Coordinator: CC2652RB (slae.sh) - plain z2m install

raveit65 Apr 5, 2025

I tested the update process again with my little test-network. Back from 20250321 --> 20221226 and again from 20221226 --> 20250321.
Surprise, i didn't run in pan_id / ext-pan_id issue or any other issue, for both directions. Update was done with the device web-interface. Only different was that slzb-06(CC2652P) was in usb-mode now. I will verify this again the next days.
@Koenkk
Could this be the reason for the pan_id or ext-pan_id issue?

Tee86 · 2025-04-01T18:55:48Z

Tee86
Apr 1, 2025

I updated FW last Monday, so I'm on 20250321 for 8 days (before I was a week on 99 version with various issues). Here's my feedback:

I've had zero "buffer full" errors so far
Battery operated devices seem to operate more reliably, I had just one SNZB-04 sensor offline twice after the availability timeout ran out (as it hadn't been used during that period), but as soon as I closed that door it went back to online status, so all good on this front.
LQI is not the best, some devices report LQI 3 or 5. I just got one Moes thermostat offline (mains powered), which had LQI 3 before it went off grid [edit/ it's back online already, literally 2minutes after I noticed it offline]... but so far when this happened with any device, they always came back. I'll try to manually re-pair some devices this week, hopefuly it helps with LQI. Maybe I'll add one or two router sockets, although I think the device density is okay within the flat. Will keep you posted on this.
It also seems that reaction time of devices is quite good, def better than with 2024 FW. That goes especially for battery-operated devices like scene buttons / switches

My original issue

0 replies

Bjk8kds · 2025-04-02T13:54:50Z

Bjk8kds
Apr 2, 2025
Sponsor

For some reason, it always failed to update the firmware on my coordinator (custom product from the seller iothings.io).
Tried using the ZigStar app or Flash Programmer v2, then finally I tried the Zigstar add-on from @mercenaruss, for some reason the add-on failed to extract the zip from the link above (utf-8 error), but it worked when using the default firmware option.
Finally I tried again with the ZigStar app and miraculously it worked!
I started Z2M but failed with an error like @2proof4u above, changed the channel and reverted it back as suggested by @drbartek solved the problem.
Thank you very much!
I will monitor my device for any abnormalities.

0 replies

wildekek · 2025-04-02T19:19:35Z

wildekek
Apr 2, 2025

Would be so much less hassle if the firmware would be updateable from the z2m interface.

0 replies

YellowNest · 2025-04-02T19:46:05Z

YellowNest
Apr 2, 2025

I’ve been running on 20250321 firmware now for about five days. No issues or whatsoever.

0 replies

KoKolaj · 2025-04-03T18:16:07Z

KoKolaj
Apr 3, 2025

Let's update (20250321). My system is up and running since 5 days now. No errors at all!

Coordinator: SLZB-06 (v2.7.1)
devices: 94

2 replies

Koenkk Apr 3, 2025
Maintainer Author

@KoKolaj how did you update it?

KoKolaj Apr 6, 2025

Zigbee OTA

45Commando · 2025-04-03T20:05:03Z

45Commando
Apr 3, 2025

BUFFER FULL problem also.

ADAPTER: SLZB-06P7 Ethernet
CPU Model CC2652P7
Firmware: 20240716

[20:37:54] INFO: Preparing to start...
[20:37:55] INFO: Socat not enabled
[20:37:55] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[03-04-252025 20:44:59] error: zh:controller: Failed to disable join on stop: Error: --> 'SREQ: AF - dataRequestExt - {"dstaddrmode":2,"dstaddr":"0x000000000000fffd","destendpoint":242,"dstpanid":0,"srcendpoint":242,"clusterid":33,"transid":1,"options":0,"radius":30,"len":6,"data":{"type":"Buffer","data":[25,2,2,10,0,0]}}' failed with status '(0x11: BUFFER_FULL)' (expected '(0x00: SUCCESS)')

is the recommendation to try 20250321 ? i dont seea version for CC2652P7

7 replies

45Commando Apr 3, 2025

also am i doing this via the "flash custom core firmware" ? thanks

Koenkk Apr 3, 2025
Maintainer Author

You need to flash the zigbee firmware, I think with core firmware you flash the ESP32 chip. But please consult the smlight manuals.

45Commando Apr 3, 2025

ok thanks...

45Commando Apr 3, 2025

Upgraded... simply wont start now..

[21:27:37] INFO: Preparing to start...
[21:27:37] INFO: Socat not enabled
[21:27:38] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.
[21:49:39] INFO: Preparing to start...
[21:49:39] INFO: Socat not enabled
[21:49:40] INFO: Starting Zigbee2MQTT...
Starting Zigbee2MQTT without watchdog.

Gues ill have to downgrade and take it from there...

Koenkk Apr 4, 2025
Maintainer Author

Could you provide the debug log of this?

See this on how to enable debug logging.

kennymc-c · 2025-04-04T19:59:24Z

kennymc-c
Apr 4, 2025

Any reason why the updated firmware files are only avaible here and not in the repo itself? Is this still a dev version to be tested? I would be supprised as this discussion is linked in the latest release notes.

1 reply

lux73 Apr 5, 2025

culdaraul · 2025-04-05T06:53:57Z

culdaraul
Apr 5, 2025

Been having lots of issues before this update. I have around 80 devices in my network and before performing this update, the adapter used to crash after one or two days withouth having the possibility to perform any remote action to have it back - I always had to manually perform a power-cycle in order to have the damn thing to start again (tried two identical adapters - same behaviour).

But with this version, after a while, my entire setup is very laggy - especially when there are multiple entities commanded - for instance - I have 9xGU10 + 1xE27 lamps in my kitchen commanded via a philips HUE dimmer switch. Same setup behaves flawlessly with a Sonoff USB DongleP (with original firmware shipped in 2021). Other 6xGU10 lamps in another room behaves very weird in some conditions (commanded via a zigbee presence sensor) - sometimes only 2 out of 6 lamps are switched on, the rest of them restores to the desired light settings after 10 seconds - which is ridiculous.

1 reply

xekil Apr 7, 2025

I had a similar problem that lasted more than 2 years (I have 170 devices), I even changed the key, but without success (SonOff Model P), I was forced to unplug and reconnect the key physically. Then one day I looked at the devices that often broke down a little more in detail and I had two sockets that were causing problems, after having discarded them my network was for the first time stable for more than two weeks (no disconnected devices). To check on your side, but there may be a device that is causing problems on your installation.

msaphoto06 · 2025-04-05T18:59:03Z

msaphoto06
Apr 5, 2025

Unfortunately, I can't update with the Zigstar add-on.
ERROR: 'utf-8' codec can't decode byte 0xa3 in position 939: invalid start byte
[21:15:53] INFO: cc2652-flasher-up script exited with code 1

3 replies

raveit65 Apr 5, 2025

For me the zigstar tool works without any problem with my uzg-01.

msaphoto06 Apr 5, 2025

I have a Sonoff.
I even tried copying the RAW link "in the developer section" and the same problem.
The 07.2024 RAW file works.

Bjk8kds Apr 7, 2025
Sponsor

This error also happened to me.
In fact, I previously failed when using the Zigstar Windows app. But after using the Zigstar add-on (failed) I tried again with the Windows app and it worked (I also re-extracted the file).

kovaga · 2025-04-06T11:21:55Z

kovaga
Apr 6, 2025

I've been running this version of firmware on UZG-01 with 68 devices for several days now.
All seems to run fine, but the excessive lagginess is noticeable sometimes. This wasnt observed on the 20240710
z2m ver: 2.2.1

0 replies

Onepamopa · 2025-04-06T16:34:53Z

Onepamopa
Apr 6, 2025

Does ember work with this firmware @ zigbee2mqtt ?

1 reply

Matriciel Apr 6, 2025

No, Ember is not for TI chips (Zstack)

Z-Stack_3.x.0 coordinator 20250321 feedback #545

Koenkk Mar 22, 2025 Maintainer

Changelog (compared to 20240710)

Firmwares

Replies: 35 comments · 57 replies

Koenkk Mar 23, 2025 Maintainer Author

Koenkk Mar 23, 2025 Maintainer Author

Koenkk Mar 23, 2025 Maintainer Author

LOGs

Koenkk Mar 26, 2025 Maintainer Author

Koenkk Mar 30, 2025 Maintainer Author

Koenkk Mar 30, 2025 Maintainer Author

Koenkk Apr 2, 2025 Maintainer Author

Koenkk Mar 26, 2025 Maintainer Author

Bjk8kds Apr 2, 2025 Sponsor

Koenkk Apr 3, 2025 Maintainer Author

Koenkk
Mar 22, 2025
Maintainer

Changelog (compared to `20240710`)

Replies: 35 comments 57 replies

Koenkk Mar 23, 2025
Maintainer Author

Koenkk Mar 23, 2025
Maintainer Author

Koenkk Mar 23, 2025
Maintainer Author

Koenkk Mar 26, 2025
Maintainer Author

Koenkk Mar 30, 2025
Maintainer Author

Koenkk Mar 30, 2025
Maintainer Author

Koenkk Apr 2, 2025
Maintainer Author

Koenkk Mar 26, 2025
Maintainer Author

Bjk8kds
Apr 2, 2025
Sponsor

Koenkk Apr 3, 2025
Maintainer Author