Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V1.37.0: Frame changeSourceRouteHandler parsing error #22444

Open
uwen70 opened this issue May 4, 2024 · 47 comments
Open

V1.37.0: Frame changeSourceRouteHandler parsing error #22444

uwen70 opened this issue May 4, 2024 · 47 comments
Labels
ezsp Issues related to deprecated ezsp driver problem Something isn't working

Comments

@uwen70
Copy link

uwen70 commented May 4, 2024

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. Skipped

The 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

@uwen70 uwen70 added the problem Something isn't working label May 4, 2024
@Laguite14
Copy link

Hello,
I have exactly the same error in chain.... but Zigbee devices seems to work.

@joaquinvacas
Copy link

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.

@Nerivec Nerivec added the ezsp Issues related to deprecated ezsp driver label May 4, 2024
@Nerivec
Copy link
Collaborator

Nerivec commented May 4, 2024

re #22443, #22436

@baskient80
Copy link

same here... everything seems to work correctly though.

@uwen70
Copy link
Author

uwen70 commented May 5, 2024

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.
An easy way to update is via WebFlasher (https://darkxst.github.io/silabs-firmware-builder/). It then also makes it possible to switch from the EZSP driver, which is now referred to as deprecated, to the new Ember. Going back is no problem either.

@Laguite14
Copy link

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. An easy way to update is via WebFlasher (https://darkxst.github.io/silabs-firmware-builder/). It then also makes it possible to switch from the EZSP driver, which is now referred to as deprecated, to the new Ember. Going back is no problem either.

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 ?
Want to be sure before flashing.

@Nerivec
Copy link
Collaborator

Nerivec commented May 5, 2024

@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.

@thombec
Copy link

thombec commented May 5, 2024

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".

@Laguite14
Copy link

Thanks for your feedback, I will flash mine to see if it resolves Z2M issues.

@sergeyshaklein
Copy link

sergeyshaklein commented May 6, 2024

Hello
After updating the firmware the errors disappeared. no device was lost.

@Ultraboss77
Copy link

And for users who does not have a compliant key ? Eg chip efr32mg13
What do you recommand @Koenkk for those users ? 😟

@joaquinvacas
Copy link

joaquinvacas commented May 6, 2024 via email

@Nerivec
Copy link
Collaborator

Nerivec commented May 6, 2024

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 ezsp, but you will remain on old software with no possibility for upgrade, and that will likely break as soon as devices supporting the latest Zigbee revision (R23) come out (6.10.x are already showing signs of trouble with newer devices). Best option is to migrate to a more recent adapter. With the MG24 now coming out, it should provide good options, first tests on these are very promising 😉

@Ultraboss77
Copy link

What about Zstack chips from TI ? They will be compliant with Zigbee R23, will be upgradable ?
If I do buy an other usb coordinator, which driver should I choose to be "future" proof ??

@MattWestb
Copy link

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.
Some MG32MG1 chips is still getting Thread / RCP firmware (EZSP 4.4.x is working OK) like IKEAs first gen module that using WFR32MG1P and tuya snot that is using EFR32MG1B chip.

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).

@djrm05
Copy link

djrm05 commented May 13, 2024

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.
Anyone know how to stop this error flodding the gui and the log? I have check the loggin options but "error" seems to be the lower loggin option.

@uwen70
Copy link
Author

uwen70 commented May 14, 2024

curiously I have 2 instances running with 2 zb-gw03 and only one of those have this issue

Probably one of the sticks has a newer firmware?

Anyone know how to stop this error flodding the gui and the log?

Update the stick's firmware. #22444 (comment)
On zb-gw04 the latest version 7.4.3.0 works for me. With Sonoff-E you should try 7.4.1.0.
After that you can also switch to the ember driver.

@djrm05
Copy link

djrm05 commented May 14, 2024

@uwen70 , thanks I would say it was the same version as I flashed both together, but maybe....
where did you get the 7.4.3.0 for the zb-gw03?

@uwen70
Copy link
Author

uwen70 commented May 14, 2024

@djrm05 Firmware: https://github.com/darkxst/silabs-firmware-builder/tree/main/firmware_builds
Check whether you have version 1.1 or 1.2 of zb-gw04

@djrm05
Copy link

djrm05 commented May 14, 2024

@uwen70 sorry but do you mean to use the existing for gw04? I don't see gw03 there

@uwen70
Copy link
Author

uwen70 commented May 14, 2024

@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.

@dev-2-4-h
Copy link

Same issue here. I can not switch to ember as I use the Sonoff Zigbee Bridge with tasmota and there is no update available.

@pioneer-01
Copy link

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

@uwen70
Copy link
Author

uwen70 commented Jun 1, 2024

New firmware 7.4.3.0 for ZB-GW03 available: https://github.com/xsp1989/zigbeeFirmware/tree/master/firmware/ZigbeeBridge_SM-011-signed
Firmware 7.4.3.0 supports Ember driver.

@didius62
Copy link

didius62 commented Jun 7, 2024

Hi all
I have the same error !

Z2m : 1.38.0
plugin : jeezigbee
coordinator : Elelabs ELR023 fw : 6.10.3-41

@jaspweowaale
Copy link

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)

@fransyozef
Copy link

fransyozef commented Jun 20, 2024

ah .. this explains why my frontend doesn't work anymore?

v 1.38.0-1

[2024-06-20 18:23:51] 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)

@jaspweowaale
Copy link

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
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240220163931-if00
Subsystem:
tty
Device path:
/dev/ttyACM0
ID:
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240220163931-if00
Attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240220163931-if00
/dev/serial/by-path/platform-xhci-hcd.1-usb-0:2:1.0
/dev/serial/by-path/platform-xhci-hcd.1-usbv2-0:2:1.0
DEVNAME: /dev/ttyACM0
DEVPATH: >-
/devices/platform/axi/1000120000.pcie/1f00300000.usb/xhci-hcd.1/usb3/3-2/3-2:1.0/tty/ttyACM0
ID_BUS: usb
ID_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_MODEL_ID: 55d4
ID_PATH: platform-xhci-hcd.1-usb-0:2:1.0
ID_PATH_TAG: platform-xhci-hcd_1-usb-0_2_1_0
ID_PATH_WITH_USB_REVISION: platform-xhci-hcd.1-usbv2-0:2:1.0
ID_REVISION: '0442'
ID_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240220163931
ID_SERIAL_SHORT: '20240220163931'
ID_TYPE: generic
ID_USB_DRIVER: cdc_acm
ID_USB_INTERFACES: ':020201:0a0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_USB_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_USB_MODEL_ID: 55d4
ID_USB_REVISION: '0442'
ID_USB_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240220163931
ID_USB_SERIAL_SHORT: '20240220163931'
ID_USB_TYPE: generic
ID_USB_VENDOR: ITEAD
ID_USB_VENDOR_ENC: ITEAD
ID_USB_VENDOR_ID: 1a86
ID_VENDOR: ITEAD
ID_VENDOR_ENC: ITEAD
ID_VENDOR_ID: 1a86
MAJOR: '166'
MINOR: '0'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '1365461'

ttyACM1
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240123115137-if00
Subsystem:
tty
Device path:
/dev/ttyACM1
ID:
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240123115137-if00
Attributes:
DEVLINKS: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240123115137-if00
/dev/serial/by-path/platform-xhci-hcd.0-usb-0:2:1.0
/dev/serial/by-path/platform-xhci-hcd.0-usbv2-0:2:1.0
DEVNAME: /dev/ttyACM1
DEVPATH: >-
/devices/platform/axi/1000120000.pcie/1f00200000.usb/xhci-hcd.0/usb1/1-2/1-2:1.0/tty/ttyACM1
ID_BUS: usb
ID_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_MODEL_ID: 55d4
ID_PATH: platform-xhci-hcd.0-usb-0:2:1.0
ID_PATH_TAG: platform-xhci-hcd_0-usb-0_2_1_0
ID_PATH_WITH_USB_REVISION: platform-xhci-hcd.0-usbv2-0:2:1.0
ID_REVISION: '0442'
ID_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240123115137
ID_SERIAL_SHORT: '20240123115137'
ID_TYPE: generic
ID_USB_DRIVER: cdc_acm
ID_USB_INTERFACES: ':020201:0a0000:'
ID_USB_INTERFACE_NUM: '00'
ID_USB_MODEL: SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
ID_USB_MODEL_ENC: SONOFF\x20Zigbee\x203.0\x20USB\x20Dongle\x20Plus\x20V2
ID_USB_MODEL_ID: 55d4
ID_USB_REVISION: '0442'
ID_USB_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20240123115137
ID_USB_SERIAL_SHORT: '20240123115137'
ID_USB_TYPE: generic
ID_USB_VENDOR: ITEAD
ID_USB_VENDOR_ENC: ITEAD
ID_USB_VENDOR_ID: 1a86
ID_VENDOR: ITEAD
ID_VENDOR_ENC: ITEAD
ID_VENDOR_ID: 1a86
MAJOR: '166'
MINOR: '1'
SUBSYSTEM: tty
TAGS: ':systemd:'
USEC_INITIALIZED: '1420613'

@uwen70
Copy link
Author

uwen70 commented Jun 21, 2024

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.
@jaspweowaale: Your ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2 are ZBDongle-E with EFR32MG21 and should be able to be updated via WebFlasher (https://darkxst.github.io/silabs-firmware-builder/).

@uwen70
Copy link
Author

uwen70 commented Jun 21, 2024

ah .. this explains why my frontend doesn't work anymore?

v 1.38.0-1

@fransyozef: No, I don't think so. Despite this error, my web frontend continued to work without any problems.
After updating z2m from 1.37.x to 1.38.0-1, my web frontend only worked after another restart.

@jaspweowaale
Copy link

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. However, there don't seem to be any more firmware updates for old chips like EFR32MG13P on Elelabs ELR023. @jaspweowaale: Your ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2 are ZBDongle-E with EFR32MG21 and should be able to be updated via WebFlasher (https://darkxst.github.io/silabs-firmware-builder/).

Yeps, testing with one of my spares thanks for the suggestion
,
image

@uwen70
Copy link
Author

uwen70 commented Jun 23, 2024

@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.

@joaquinvacas
Copy link

joaquinvacas commented Jun 23, 2024 via email

@jaspweowaale
Copy link

@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.

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

@uwen70
Copy link
Author

uwen70 commented Jun 24, 2024

@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.

@uwen70
Copy link
Author

uwen70 commented Jun 24, 2024

@jaspweowaale: ...what do you mean ember driver? ...

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.
In the z2m configuration, adapter: ezsp must be replaced by adapter: emberto change the driver. However, firmware 7.4.0.0 or higher is required.
I think what's new is that Ember will later support new Zigbee Green Power devices that don't require a power supply/battery.

@didius62
Copy link

didius62 commented Jun 24, 2024 via email

@uwen70
Copy link
Author

uwen70 commented Jun 25, 2024

@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.

@jaspweowaale
Copy link

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

@didius62
Copy link

didius62 commented Jun 25, 2024 via email

@jaspweowaale
Copy link

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

@didius62
Copy link

didius62 commented Jun 26, 2024 via email

@SashaAV
Copy link

SashaAV commented Jul 18, 2024

Hi!

Same error.
1.39.0 commit: 0326926
Here is stack trace:

image

@FloMeyer
Copy link

I get the same error:

error 2024-08-19 12:35:23zh: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:177:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:151:23 at Array.every (<anonymous>) at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:145:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:430:35)
error 2024-08-19 12:35:23zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
error 2024-08-19 12:35:23zh: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:177:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:151:23 at Array.every (<anonymous>) at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:145:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:430:35)
error 2024-08-19 12:35:23zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
error 2024-08-19 12:35:23zh: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:177:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:151:23 at Array.every (<anonymous>) at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:145:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:430:35)
error 2024-08-19 12:35:23zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
error 2024-08-19 12:35:23zh: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:177:54) at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:151:23 at Array.every (<anonymous>) at Function.createFrame (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:145:15) at Ezsp.onFrameReceived (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:430:35)
error 2024-08-19 12:35:23zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped

@jerome-73
Copy link

Hi

I get the same error.
tested with Version 1.38.0, 1.39.0 and 1.39.1.
Error message :
ezsp: Unparsed frame 0xc4. Skipped
Killed

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.
Regards

@didius62
Copy link

Hi all ,

i work with Z2m (1.40.1) under Jeezigbee (Plugin Jeedom) , my harware is a RP4 under Debian 11.11.
Up to the version Z2m 1.37.0 my configuration was steady , Coordinator Elelabs Popp (fw 6.10.3-41) , 4 routers cc2530 and 46 end devices .
since the latest Z2m updates , i receive the errors indicated above :
error 2024-08-19 12:35:23zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds at new NodeError (node:internal/errors:405:5) at boundsError...

I tried to replace the key Popp by A Sonoff Zdongle-E (Fw 7.4.3.0) , first i lost my 50 devices !!!!
With this coordinator i am not able to include my devices : the routers are included but not completely, same thing with Aqara devices.

i tried to downgrade the Zdongle-E to fw 6.10.3-41 but without devices , i received many errors.
i try to comeback to my key Popp (fw: 6.10.3-41) but i am not sure that is the good solution , because the inclusion of devices is not great.

What can i do ? (return to Z2m 1.37.0)
many thanks for any help

Didier Danel

@didius62
Copy link

didius62 commented Oct 1, 2024

Hi ,
Could it be possible that the cc2530 routers are responsible for these errors?

DD

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ezsp Issues related to deprecated ezsp driver problem Something isn't working
Projects
None yet
Development

No branches or pull requests