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.

Sign up for GitHub

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

Jump to bottom

Been getting some error logs since I updated Zigbee2Mqtt #22226

Open
felipejfc opened this issue Apr 16, 2024 · 31 comments
Open

Been getting some error logs since I updated Zigbee2Mqtt #22226

felipejfc opened this issue Apr 16, 2024 · 31 comments
Labels
ezsp Issues related to deprecated ezsp driver problem Something isn't working

Comments

@felipejfc
Copy link

What happened?

Everything was fine but then yesterday I decided to update z2m to latest dev image on docker hub and ever since updating I've been getting error like these in my logs:

[2024-04-16 10:18:48] 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-04-16 10:18:48] error:    zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped

[2024-04-16 10:20:46] info:     z2m: Zigbee: disabling joining new devices.
[2024-04-16 10:20:46] error:    zh:controller:greenpower: Received undefined command from '0'
[2024-04-16 10:20:46] info:     z2m: Zigbee: disabling joining new devices.
[2024-04-16 10:20:46] error:    zh:controller:greenpower: Received undefined command from '0'

Apart from updating z2m, the only other thing that changed is I added one of new sensor to my network:
https://www.zigbee2mqtt.io/devices/DY-RQ500A.html#dygsm-dy-rq500a

What did you expect to happen?

Errors stop happening.

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

1.36.1-dev commit: 172aa74

Adapter firmware version

6.10.3.0 build 297

Adapter

EZSP v8

Setup

Dockerized with latest dev image

Debug log

No response
@felipejfc felipejfc added the problem Something isn't working label Apr 16, 2024
@og-gh
Copy link

og-gh commented Apr 19, 2024

I'm facing the same after upgrade to latest DEV:
1.36.1-dev commit: [cdbbe0d]

@Koenkk
Copy link
Owner

Koenkk commented Apr 21, 2024

Could you check if this is fixed now in the dev branch?

@felipejfc
Copy link
Author

Updated today to "koenkk/zigbee2mqtt:latest-dev"
And the error seems to still be present:

Error 2024-04-23 14:23:20Received undefined command from '0'
Error 2024-04-23 14:24:17Frame 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)
Error 2024-04-23 14:24:17Unparsed frame 0xc4. Skipped

@Koenkk
Copy link
Owner

Koenkk commented Apr 25, 2024

could you provide the debug log of this?

See this on how to enable debug logging.

@localboast
Copy link

I'm seeing the same error when clikcing Permit Join, just destroyed and reinstalled z2m edge and same result on latest. @Koenkk I'm running HAOS in a VM in Proxmox, if you can give a little more detail around adding the debug to Herdsman at docker run I can try to debug there. Debug in z2m didn't show any additional details.

@og-gh
Copy link

og-gh commented Apr 26, 2024 via email

@harryba
Copy link

harryba commented May 2, 2024

45df7312_zigbee2mqtt_2024-05-02T10-26-23.784Z.log

Having the same issues after trying to add a door sensor

@fszalaj
Copy link

fszalaj commented May 2, 2024

same here

45df7312_zigbee2mqtt_2024-05-02T10-26-23.784Z.log

Having the same issues after trying to add a door sensor

@Chris0588
Copy link

Hi all.

I have recognized the same Issue as I wanted to add some devices.

Got the Error "Received undefined command from '0'", but was able to add the devices.
Then i saw i could not rename them, the blue button is missing in the App of the mobile phone.
Using a laptop, the Button is available, but not all Options when i rename them.

@xsrplayerx
Copy link

Hi all.

I have recognized the same Issue as I wanted to add some devices.

Got the Error "Received undefined command from '0'", but was able to add the devices.
Then i saw i could not rename them, the blue button is missing in the App of the mobile phone.
Using a laptop, the Button is available, but not all Options when i rename them.

I have the exact same issue...

@Pel1can111
Copy link

Same issue here, getting tons of these errors. Everything seems to be working except for power usage data for my sockets.

AU-A1ZBDSS

tried re-adding the sockets and now I just see "null" where the power measurement should be.

@EnzovdWetering
Copy link

EnzovdWetering commented May 3, 2024 •
edited

I think I have the same issue, however I'm not sure if this started since I upgraded or before since my installation of zigbee2mqtt keeps freezing and zigbee devices become unresponsive. After restarting zigbee2mqtt everything is fine again.. Anyway I also get similar logs:
[2024-05-03 06:01:37] 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-03 06:01:37] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped [2024-05-03 06:01:37] 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-03 06:01:37] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped

Current version: 1.37.0-1 (Changelog)

@robvanoostenrijk
Copy link

Confirming that I'm seeing the same issues after update:

[2024-05-03 10:41:47] error: 	zh:ezsp:ezsp: Frame changeSourceRouteHandler parsing error: RangeError: Attempt to access memory outside buffer bounds
    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 (/usr/local/share/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/types/basic.ts:19:67)
    at new EZSPFrameData (/usr/local/share/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:180:54)
    at /usr/local/share/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:154:23
    at Array.every (<anonymous>)
    at Function.createFrame (/usr/local/share/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:148:15)
    at Ezsp.onFrameReceived (/usr/local/share/zigbee2mqtt/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:439:35)
    at SerialDriver.emit (node:events:519:28)

Frontend version:

  • 0.6.165
  • 19.32.0
  • 0.45.0

Zigbee2MQTT version:

Coordinator type

  • EZSP v8

Coordinator revision

  • 6.7.10.0 build 423

@posul
Copy link

posul commented May 3, 2024

Confirming I see the same issue after update

@hhrocha000
Copy link

Same issue here, when i restart zigbee2mqtt fixes for a couple of hours but the issue returns randomly. Having issues with my devices since last 2 updates randomly they stop responding, couldn't find a fix yet

@DennisJohnsen
Copy link

I know, i know. Watchtower is usually bad practice on something you want stable. I see that now 😂

Disabled Watchtower for my Zigbee2MQTT container, pulled the previous image koenkk/zigbee2mqtt:1.36.1 and now my GreenPower devices work again.

I noticed something was wrong when 14 of my 17 switches suddenly stopped working.

@litecross91
Copy link

Same problem here. Is there any solution?

@EnzovdWetering
Copy link

EnzovdWetering commented May 3, 2024 •
edited

I upgraded my Sonoff ZBDongle-E adapter to: 7.4.0.0 (newer versions did not flash)
Since I've done this I don't have the issue anymore. My adapter was running version 6.10.3.0 build 297 before the upgrade.

To be specific, I've used this firmware: https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.0.0-zbdonglee-115200.gbl

With this command: universal-silabs-flasher --device /dev/tty.usbserial-202302201603421 --bootloader-reset sonoff flash --firmware /Users/enzovandewetering/Downloads/ncp-uart-hw-v7.4.0.0-zbdonglee-115200.gbl

I used --bootloader-reset because a newer version that I flashed stopt the adapter from booting. Perhaps you don't need this.

Let me know if it works.

Best regards,
Enzo

@litecross91
Copy link

litecross91 commented May 3, 2024 •
edited

Something went wrong :(

I changed in the configuration.yaml
adapter: ember

[14:59:27] INFO: Preparing to start...
[14:59:27] INFO: Socat not enabled
[14:59:28] INFO: Starting Zigbee2MQTT...
[2024-05-03 14:59:29] info: 	z2m: Logging to console, file (filename: log.log)
[2024-05-03 14:59:30] info: 	z2m: Starting Zigbee2MQTT version 1.37.0 (commit #unknown)
[2024-05-03 14:59:30] info: 	z2m: Starting zigbee-herdsman (0.45.0)
[2024-05-03 14:59:30] info: 	zh:ember: ======== Ember Adapter Starting ========
[2024-05-03 14:59:30] info: 	zh:ember:ezsp: ======== EZSP starting ========
[2024-05-03 14:59:30] info: 	zh:ember:uart:ash: ======== ASH NCP reset ========
[2024-05-03 14:59:30] info: 	zh:ember:uart:ash: RTS/CTS config is off, enabling software flow control.
[2024-05-03 14:59:30] info: 	zh:ember:uart:ash: Serial port opened
[2024-05-03 14:59:30] info: 	zh:ember:uart:ash: ======== ASH starting ========
[2024-05-03 14:59:31] info: 	zh:ember:uart:ash: ======== ASH connected ========
[2024-05-03 14:59:31] info: 	zh:ember:uart:ash: ======== ASH started ========
[2024-05-03 14:59:31] info: 	zh:ember:ezsp: ======== EZSP started ========
[2024-05-03 14:59:31] info: 	zh:ember: [STACK STATUS] Network up.
[2024-05-03 14:59:31] error: 	z2m: Error while starting zigbee-herdsman
[2024-05-03 14:59:31] error: 	z2m: Failed to start zigbee
[2024-05-03 14:59:31] error: 	z2m: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
[2024-05-03 14:59:31] error: 	z2m: Exiting...
[2024-05-03 14:59:31] error: 	z2m: Error: [BACKUP] Current backup file is from an unsupported EZSP version (min: 12).
    at EmberAdapter.getStoredBackup (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1340:23)
    at EmberAdapter.initTrustCenter (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:1131:33)
    at EmberAdapter.initEzsp (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:813:19)
    at EmberAdapter.start (/app/node_modules/zigbee-herdsman/src/adapter/ember/adapter/emberAdapter.ts:2660:24)
    at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:124:29)
    at Zigbee.start (/app/lib/zigbee.ts:62:27)
    at Controller.start (/app/lib/controller.ts:108:27)
    at start (/app/index.js:107:5)
[15:02:17] INFO: Preparing to start...
[15:02:17] INFO: Socat not enabled

Solution:
In the configuration folder renamed the "coordinator_backup.json" to "coordinator_backup.json.old" and the z2m started.

@hhrocha000
Copy link

im using this coordinator
https://pt.aliexpress.com/item/1005005271016330.html?spm=a2g0o.productlist.main.89.6771bo3hbo3hjf&algo_pvid=b4a4e2e4-2201-4032-a882-92bd94fc27d7&algo_exp_id=b4a4e2e4-2201-4032-a882-92bd94fc27d7-44&pdp_npi=4%40dis%21EUR%218.38%217.78%21%21%218.79%218.16%21%402103146f17147401316211689eb723%2112000032433818442%21sea%21PT%211761271617%21&curPageLogUid=CeVxZYM7GWpw&utparam-url=scene%3Asearch%7Cquery_from%3A

i update from version 6.7.9.0 build 405 to 7.3.1.0 build 176 (EZSP updates from version 8 to 12 too) using this website:
https://darkxst.github.io/silabs-firmware-builder/

Will see if this fix my problem and i'll give you my feedback later.

@xsrplayerx
Copy link

xsrplayerx commented May 3, 2024 •
edited

Will see if this fix my problem and i'll give you my feedback later.

Thanks! I also have that coordinator

@guidox
Copy link

guidox commented May 3, 2024

I also have the same problem, I use the coordinator Sonoff v2 plus

@hhrocha000
Copy link

UPDATE: in my case update my coordinator solve the problem.

im using this coordinator https://pt.aliexpress.com/item/1005005271016330.html?spm=a2g0o.productlist.main.89.6771bo3hbo3hjf&algo_pvid=b4a4e2e4-2201-4032-a882-92bd94fc27d7&algo_exp_id=b4a4e2e4-2201-4032-a882-92bd94fc27d7-44&pdp_npi=4%40dis%21EUR%218.38%217.78%21%21%218.79%218.16%21%402103146f17147401316211689eb723%2112000032433818442%21sea%21PT%211761271617%21&curPageLogUid=CeVxZYM7GWpw&utparam-url=scene%3Asearch%7Cquery_from%3A

i update from version 6.7.9.0 build 405 to 7.3.1.0 build 176 (EZSP updates from version 8 to 12 too) using this website: https://darkxst.github.io/silabs-firmware-builder/

Will see if this fix my problem and i'll give you my feedback later.

@litecross91 litecross91 mentioned this issue May 4, 2024
Closed
@thombec
Copy link

thombec commented May 5, 2024 •
edited

sounds great :-)

my Sonoff ZB-Dongle-E has the firmware 6.10.3.0 - so I want to flash it too to solve this problem.

Short question: After flashing - do you have to re-pair all your Zigbee devices or Z2MQTT started again with all the devices?

@litecross91
Copy link

I did it and no, don't need repair. Worked all 22 devices as before.

@xsrplayerx
Copy link

UPDATE: in my case update my coordinator solve the problem.

im using this coordinator https://pt.aliexpress.com/item/1005005271016330.html?spm=a2g0o.productlist.main.89.6771bo3hbo3hjf&algo_pvid=b4a4e2e4-2201-4032-a882-92bd94fc27d7&algo_exp_id=b4a4e2e4-2201-4032-a882-92bd94fc27d7-44&pdp_npi=4%40dis%21EUR%218.38%217.78%21%21%218.79%218.16%21%402103146f17147401316211689eb723%2112000032433818442%21sea%21PT%211761271617%21&curPageLogUid=CeVxZYM7GWpw&utparam-url=scene%3Asearch%7Cquery_from%3A
i update from version 6.7.9.0 build 405 to 7.3.1.0 build 176 (EZSP updates from version 8 to 12 too) using this website: https://darkxst.github.io/silabs-firmware-builder/
Will see if this fix my problem and i'll give you my feedback later.

Thanks!

@Ltek
Copy link

Ltek commented May 6, 2024

@Koenkk a few Debug Logs attached
Only started getting this error after just updating from FW v6.7.9.0 to 7.3.1.0 and to Z2M 1.37

Now using Sonoff ZB-Dongle-E w/ FW 7.3.1.0

image

Z2M_DebugLogs.zip

@Catalin84
Copy link

[2024-05-08 06:31:31] warning: zh:ezsp: Deprecated driver 'ezsp' currently in use, 'ember' will become the officially supported EmberZNet driver in next release. If using Zigbee2MQTT see #21462
[2024-05-08 06:32:07] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:35:27] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:38:47] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:42:07] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:45:27] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:48:47] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:52:07] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:55:27] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 06:58:47] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 07:02:07] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 07:05:27] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 07:08:47] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-08 07:12:07] error: zh:controller:greenpower: Received undefined command from '0'

Same issue after updateing Zigbee app and firmware!

@archont00
Copy link

@EnzovdWetering

I upgraded my Sonoff ZBDongle-E adapter to: 7.4.0.0 (newer versions did not flash) Since I've done this I don't have the issue anymore. My adapter was running version 6.10.3.0 build 297 before the upgrade.

Did the same, no more error in logs - and afterwards, I could run OTA update for IKEA E2001/2002.

I used --bootloader-reset because a newer version that I flashed stopt the adapter from booting. Perhaps you don't need this.

I have updated the dongle via web flasher (Google Chrome, Ubuntu Linux) with fw: ncp-uart-hw-v7.4.0.0-zbdonglee-115200.gbl. The web flasher does not allow user to set options.

All devices were connected after HAOS reboot.

@Ltek
Copy link

Ltek commented May 12, 2024 •
edited

Did the same, no more error in logs - and afterwards, I could run OTA update for IKEA E2001/2002.

I have updated the dongle via web flasher (Google Chrome, Ubuntu Linux) with fw: ncp-uart-hw-v7.4.0.0-zbdonglee-115200.gbl. The web flasher does not allow user to set options.

All devices were connected after HAOS reboot.

updated to 7.4.3 and no more Z2M errors -but- many of the devices did not reconnect on their own.

Z2M also has serious problems re-pairing Bosch and Aqara Motion Sensors even with the sensor being 4 ft from the Dongle... so its really hard to blame the dongle. I have to restart Z2M (dongle stays plugged/powered the entire time) multiple times before it will initiate the pairing.

Pairing a brand new device (Bosch or Aqara - new out of box) works super quick. This leads me to thing Z2M has a problem with pairing devices after they have already been paired (Deconz or Z2M), then factory reset... even if they have never been in Z2M.

@Gazarob63
Copy link

Same issue, I haven't seen any definitive answer to this problem. The error repeats every few seconds, eventually (randomly) Zigbee2MQTT will stop leaving all devices unavailable until restarted.

Info:

Zigbee2MQTT Current version: 1.37.1-1

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-fd500000.pcie-pci-0000:01:00.0-usb-0:1.3:1.0
ID_PATH_TAG: platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_3_1_0
ID_PATH_WITH_USB_REVISION: platform-fd500000.pcie-pci-0000:01:00.0-usbv2-0:1.3:1.0
ID_REVISION: '0442'
ID_SERIAL: ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20221201164229
ID_SERIAL_SHORT: '20221201164229'
ID_TYPE: generic
ID_USB_DRIVER: cdc_acm

Log Error: (Repeats)
2024-05-13 06:00:13] error: zh:ezsp:ezsp: Unparsed frame 0xc4. Skipped
[2024-05-13 06:00:19] 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 ()
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)

@Nerivec Nerivec added the ezsp Issues related to deprecated ezsp driver label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ezsp Issues related to deprecated ezsp driver problem Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests