V1.37.0: Frame changeSourceRouteHandler parsing error #22444
Comments
|
Hello, |
|
Same here, my adapter (Tuya/LIDL converted LAN coordinator) doesn't have a compatible EmberZnet firmware AFAIK so I can't switch to the new driver. |
|
same here... everything seems to work correctly though. |
|
After updating Zigbee firmware from EZSP v8 6.10.3.0 build 297 to EZSP v13 7.4.2.0 the parsing error no longer occurred. |
Thanks, I think I saw that when flashing the new firmware on the coordinator you should have to redo all the pairing of the devices. Did you get this issue after flashing your dongle or Z2MQTT started again with all the devices ? |
|
@Laguite14 Most people reported having no issues with upgrading from 6.10.3 to 7.x.x, but a few had to re-pair devices. |
|
today I flashed my Dongle-E from 6.10.3.0 to the current version. I have >60 devices already paired. All devices are paired after flashing. I have no issues with the upgrade - no dev was "lost". |
|
Thanks for your feedback, I will flash mine to see if it resolves Z2M issues. |
|
Hello |
|
And for users who does not have a compliant key ? Eg chip efr32mg13 |
|
I'm on the same boat, using a 256k chip which doesn't support newer
versions, not even 6.10 (stable)
El lun, 6 may 2024, 18:37, Gérald Gatesoupe ***@***.***>
escribió:
… And for users who does not have a compliant key ? Eg chip efr32mg13
What do you recommand @Koenkk <https://github.com/Koenkk> for those users
? 😟
—
Reply to this email directly, view it on GitHub
<#22444 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEJUAJIMFOK4JW77C6F3ZA6WSZAVCNFSM6AAAAABHGZQUE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGQ2TQNRWGA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Silabs is splitting support for those old chips (Series 0 & 1) in the next firmware release. darkxst mentioned that support will be dropped in new firmware releases because of this. You can continue to use |
|
What about Zstack chips from TI ? They will be compliant with Zigbee R23, will be upgradable ? |
|
EMx and EFR32MG1X is only supported until 6.10.X and EFR32MG2X is still full supported so its only splitting the code then its no use implanting functions that cant being used in the hardware. I cant see some use ditching V8 then its not much changes only some commands / rev and better keep the backward compatibility (ZHA is still having support from early V5.X). |
|
curiously I have 2 instances running with 2 zb-gw03 and only one of those have this issue, prompting a lot of red errors in the gui even all devices seems to work properly. |
Probably one of the sticks has a newer firmware?
Update the stick's firmware. #22444 (comment) |
|
@uwen70 , thanks I would say it was the same version as I flashed both together, but maybe.... |
|
@djrm05 Firmware: https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds |
|
@uwen70 sorry but do you mean to use the existing for gw04? I don't see gw03 there |
Sorry, I mixed up the gw03 and gw04. For ZB-GW03 is currently no new firmware available. Follow xsp1989/zigbeeFirmware#49 for updates. |
|
Same issue here. I can not switch to ember as I use the Sonoff Zigbee Bridge with tasmota and there is no update available. |
here as well. Using Sonoff ZBBridge Zigbee Gateway (ZBBridge) with Tasmota |
|
New firmware 7.4.3.0 for ZB-GW03 available: https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/ZigbeeBridge_SM-011-signed |
|
Hi all Z2m : 1.38.0 |
|
Same issue, Unparsed frame 0xc4. Skipped And this Error 2024-06-19 08:14:53Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds at new NodeError (node:internal/errors:405:5) at boundsError (node:internal/buffer:86:11) at Buffer.readUInt16LE (node:internal/buffer:245:5) at Buffer.readUIntLE (node:internal/buffer:182:17) at Function.deserialize (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67) at new EZSPFrameData (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23 at Array.every () at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35) |
|
ah .. this explains why my frontend doesn't work anymore? v 1.38.0-1
|
|
I'm not sure if helps but below are my USB's Im new to this and running both ZAH and Zigbee2Mqtt, just to make it more fun Zwave I used to work with GPS modems and Use teraterm-4.106 and see the boot, but then crickets, all info and videos related to Version E and P Perhaps my error is not related but its the same error on different models of USB sticks, to me it sounds like it is not a firmware issue, when possible to replicate the problem with Sonoff USB's ttyACM0 ttyACM1 |
|
I think the "changeSourceRouteHandler parsing error" occurs with all Zigbee USB sticks that work with an EFR32MGxx chip, provided the firmware of the stick is still version 6.x.x.x. An update to 7.4.x.x should fix the problem. |
@fransyozef: No, I don't think so. Despite this error, my web frontend continued to work without any problems. |
Yeps, testing with one of my spares thanks for the suggestion |
|
@jaspweowaale: You should update to version 7.4.2.0 right away. The firmware (ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl) can be found at https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds/zbdonglee. With this version you can also switch to the new Ember driver in z2m. |
|
The issue with MG13 chips is that those do not support newer firmware
builds than 6.10.x, I think mainly because of the chip only allowing 256k
firmwares.
El dom, 23 jun 2024, 14:13, uwen70 ***@***.***> escribió:
… @jaspweowaale <https://github.com/jaspweowaale>: You should update to
version 7.4.2.0 right away. The firmware
(ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl) can be found at
https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds/zbdonglee.
With this version you can also switch to the Ember driver in z2m.
—
Reply to this email directly, view it on GitHub
<#22444 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBTEJT2GLXCGUUIEOYUPSTZI23YHAVCNFSM6AAAAABHGZQUE2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBUHE3DKMBYGU>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Yah I did do the update and all my 4 devices, what do you mean ember driver? I will need to google a bit related to that I think |
|
@joaquinvacas: You can try the firmware here: https://github.com/darkxst/silabs-firmware-builder/tree/main |
The new Ember driver has been available since z2m 1.37.0. The release notes state: The ezsp driver is now deprecated in favor of the new ember driver. The ember driver will become the officially supported driver for EmberZNet adapters in the future. |
|
Hi all ,
the Elelabs ELR023 is very stable, i am very satisfied with this adaptor.
I have 4 routers CC2530+CC2591 and 45 equipments , all is runing fine .
change the adapter is a very big work !
To day what adapter is recommanded ?
@uwen70 : do you have tested the ncp-uart-hw-v7.4.2.0-elelabs-elx0x3-115200.gbl ? is it possible to downgrade the fw withot any lose ?
many thanks
DD
…----- Mail original -----
De: "uwen70" ***@***.***>
À: "Koenkk/zigbee2mqtt" ***@***.***>
Cc: "didius62" ***@***.***>, "Comment" ***@***.***>
Envoyé: Lundi 24 Juin 2024 13:49:07
Objet: Re: [Koenkk/zigbee2mqtt] V1.37.0: Frame changeSourceRouteHandler parsing error (Issue #22444)
@joaquinvacas : You can try the firmware here: https://github.com/darkxst/silabs-firmware-builder/tree/main
It should support Elelabs Zigbee USB Adapter ELU013 and Elelabs Zigbee Raspberry Pi Shield ELR023 (both based on EFR32MG13P). The file is at least smaller than 256kb.
I recommend the ncp-uart-hw-v7.4.2.0-elelabs-elx0x3-115200.gbl, which also supports the Ember driver in z2m.
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you commented. Message ID: <Koenkk/zigbee2mqtt/issues/22444/2186389438 @ github . com>
|
|
@didius62: There is no compelling reason to update a running system with new firmware at this point in time. I think an update is quite tricky. I don't have an Elelabs adapter, but an EasyIot ZB-GW04. My first attempt at an update failed because I chose the faster baud rate of 230400 and I first had to learn how to access the adapter at this speed. However, you can install a different, even older firmware image. There is also firmware for OpenThread and for Zigbee and OpenThread at the same time. However, only the Zigbee firmware is supported under z2m. |
|
Yah that ember thing did not work for, swapped out ezsp in the config part of the addon , and made a restart and and crickets zigbee2mqtt never came back, bit late in the evening to play with this so have look tomorrow |
|
Thank you .
DD
…----- Mail original -----
De: "uwen70" ***@***.***>
À: "Koenkk/zigbee2mqtt" ***@***.***>
Cc: "didius62" ***@***.***>, "Mention" ***@***.***>
Envoyé: Mardi 25 Juin 2024 13:02:44
Objet: Re: [Koenkk/zigbee2mqtt] V1.37.0: Frame changeSourceRouteHandler parsing error (Issue #22444)
@didius62 : There is no compelling reason to update a running system with new firmware at this point in time. I think an update is quite tricky. I don't have an Elelabs adapter, but an EasyIot ZB-GW04. My first attempt at an update failed because I chose the faster baud rate of 230400 and I first had to learn how to access the adapter at this speed. However, you can install a different, even older firmware image. There is also firmware for OpenThread and for Zigbee and OpenThread at the same time. However, only the Zigbee firmware is supported under z2m.
Some adapters save some configuration variables in addition to the firmware image. Sometimes these have to be reinitialized after an update. I don't know if this is necessary for your adapter and how to do it.
I have used versions 6.10.x, 7.3.1.0, 7.4.2.0 and have been using version 7.4.3.0 for a few weeks.
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <Koenkk/zigbee2mqtt/issues/22444/2188634822 @ github . com>
|
|
I did get a UZG-01 today and Im so early in my HA setup, that I wonder what is best, drop the Sonoff's use it as a coordinator or POE it on a different floor as a router, I see the Berded Thinking he review it but also at some point suggest running more than one zigbee2mqtt I think I will open a treat on HA forum to get some general feedback, but the ember thing did not work despite the updates made to Sonoff USB stick |
|
Hi
Ok I think i will keep my Popp Elelabs key.
i have a sonoff ZBDongle-E but never tested ! (For that i need to buy another Raspberry to avoid problem !)
DD
…----- Mail original -----
De: "jaspweowaale" ***@***.***>
À: "Koenkk/zigbee2mqtt" ***@***.***>
Cc: "didius62" ***@***.***>, "Mention" ***@***.***>
Envoyé: Mercredi 26 Juin 2024 03:38:22
Objet: Re: [Koenkk/zigbee2mqtt] V1.37.0: Frame changeSourceRouteHandler parsing error (Issue #22444)
I did get a UZG-01 today and Im so early in my HA setup, that I wonder what is best, drop the Sonoff's use it as a coordinator or POE it on a different floor as a router, I see the Berded Thinking he review it but also at some point suggest running more than one zigbee2mqtt
I think I will open a treat on HA forum to get some general feedback, but the ember thing did not work despite the updates made to Sonoff USB stick
—
Reply to this email directly, view it on GitHub , or unsubscribe .
You are receiving this because you were mentioned. Message ID: <Koenkk/zigbee2mqtt/issues/22444/2190366399 @ github . com>
|
|
I get the same error: |
|
Hi I get the same error. Controller Sonoff ZB USB dongle-E. It crash after some minutes 2-3. I tried to unplug and replug the USB dongle. message 0xc4 appear again, but without crashing z2m. now running since 15 minutes without crash. Hope this comment can help a little. |
|
Hi all , i work with Z2m (1.40.1) under Jeezigbee (Plugin Jeedom) , my harware is a RP4 under Debian 11.11. I tried to replace the key Popp by A Sonoff Zdongle-E (Fw 7.4.3.0) , first i lost my 50 devices !!!! i tried to downgrade the Zdongle-E to fw 6.10.3-41 but without devices , i received many errors. What can i do ? (return to Z2m 1.37.0) Didier Danel |
|
Hi , DD |
|
Hi! I have the same Error with an Aeotec Zi-Stick https://aeotec.com/aeotec-z-stick-zigbee/ Is it possible to do a firmware update for this Stick?
|
|
Hi , Sorry i dont't known . Didier |
|
I am using on my Homeassistant the Zi Stick. 
Can somebody tell me if it is possible to update this stick to solve the issues? |
|
@Uschix2000: In principle, the stick can be updated. But I didn't see Coordinator version 7.x (or 8.x) on the manufacturer's website. |
What happened?
After updating zigbee2mqtt to version 1.37.0 in HA I fond repeated frame parsing error in the log:
[2024-05-04 11:50:24] error: zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds at new NodeError (node:internal/errors:405:5) at boundsError (node:internal/buffer:86:11) at Buffer.readUInt16LE (node:internal/buffer:245:5) at Buffer.readUIntLE (node:internal/buffer:182:17) at Function.deserialize (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67) at new EZSPFrameData (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23 at Array.every (<anonymous>) at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35) [2024-05-04 11:50:24] error: zh:ezsp:ezsp: Unparsed frame 0xc4. SkippedThe error repeats itself sporadically (6 times in 24h).
What did you expect to happen?
No response
How to reproduce it (minimal and precise)
I don't know any way to provoke the error.
Zigbee2MQTT version
1.37.0 commit: unknown
Adapter firmware version
EZSP v8 6.10.3.0 build 297
Adapter
ZB-GW04
Setup
Add-on on Homeassistant on Debian, VM x86-64, VMware
Debug log
No response
The text was updated successfully, but these errors were encountered: