zigbee2mqtt icon indicating copy to clipboard operation
zigbee2mqtt copied to clipboard

Published 20 hours ago β€’ verified publisher icon Koenkk

Been getting some error logs since I updated Zigbee2Mqtt

Open felipejfc opened this issue 10 months ago β€’ 31 comments

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 avatar Apr 16 '24 13:04 felipejfc

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

og-gh avatar Apr 19 '24 09:04 og-gh

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

Koenkk avatar Apr 21 '24 19:04 Koenkk

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

felipejfc avatar Apr 23 '24 17:04 felipejfc

could you provide the debug log of this?

See this on how to enable debug logging.

Koenkk avatar Apr 25 '24 19:04 Koenkk

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.

localboast avatar Apr 25 '24 23:04 localboast

Hi Koen,

attached my DEBUG logs

Thanks!

Am Do., 25. Apr. 2024 um 21:31 Uhr schrieb Koen Kanters < @.***>:

could you provide the debug log of this?

See this https://www.zigbee2mqtt.io/guide/usage/debug.html on how to enable debug logging.

β€” Reply to this email directly, view it on GitHub https://github.com/Koenkk/zigbee2mqtt/issues/22226#issuecomment-2078032368, or unsubscribe https://github.com/notifications/unsubscribe-auth/AX7PQ2K6W3V6CEXAED2HJCLY7FKYXAVCNFSM6AAAAABGJLPHJCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYGAZTEMZWHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

[2024-04-26 07:47:22] [32minfo[39m: z2m: Successfully changed options [2024-04-26 07:47:22] [34mdebug[39m: z2m: MQTT publish: topic 'zigbee2mqtt/bridge/response/options', payload '{"data":{"restart_required":false},"status":"ok","transaction":"nzw96-1"}' [2024-04-26 07:47:25] [32minfo[39m: zh:ezsp:ezsp: Time to watchdog ... 0 [2024-04-26 07:47:25] [32minfo[39m: zh:ezsp:ezsp: ==> nop: null [2024-04-26 07:47:25] [32minfo[39m: zh:ezsp:ezsp: ==> {"cls":"nop","id":5,"isRequest":true} [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: --> DATA (7,3,0): 1f00010500 [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: --> [735d21a9512a6b757e] [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: -?- waiting (0) [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: <-- [305da1a9512a12bd7e] [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: <-- DATA (3,0,0): 305da1a9512a12bd7e [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: --> ACK (4) [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: --> [8430fc7e] [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: <-- ACK (0): 305da1a9512a12bd7e [2024-04-26 07:47:25] [32minfo[39m: zh:ezsp:ezsp: <== Frame: 1f80010500 [2024-04-26 07:47:25] [32minfo[39m: zh:ezsp:ezsp: <== 0x5: {"cls":"nop","id":5,"isRequest":false} [2024-04-26 07:47:25] [34mdebug[39m: zh:ezsp:uart: -+- waiting (0) success [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- [405db1a97d312a7d31b259924a25aa55] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- [93499ca97b7d3819c69874f4ba9e76f8] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- [7f3ebeebcdda85f17e] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- DATA (4,0,0): 405db1a9112a11b259924a25aa5593499ca97b1819c69874f4ba9e76f87f3ebeebcdda85f17e [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: --> ACK (5) [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: --> [8520dd7e] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- ACK (0): 405db1a9112a11b259924a25aa5593499ca97b1819c69874f4ba9e76f87f3ebeebcdda85f17e [2024-04-26 07:47:26] [32minfo[39m: zh:ezsp:ezsp: <== Frame: 1f900145000400000600000000010000e75cb3f408ffff097cfdff04010119000004 [2024-04-26 07:47:26] [32minfo[39m: zh:ezsp:ezsp: <== 0x45: {"cls":"incomingMessageHandler","id":69,"isRequest":false,"type":4,"apsFrame":{"profileId":0,"sequence":231,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"groupId":0,"options":256},"lastHopLqi":92,"lastHopRssi":-77,"sender":2292,"bindingIndex":255,"addressIndex":255,"message":{"type":"Buffer","data":[124,253,255,4,1,1,25,0,0]}} [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp: processMessage: {"messageType":4,"apsFrame":{"profileId":0,"sequence":231,"clusterId":6,"sourceEndpoint":0,"destinationEndpoint":0,"groupId":0,"options":256},"lqi":92,"rssi":-77,"sender":2292,"bindingIndex":255,"addressIndex":255,"message":{"type":"Buffer","data":[124,253,255,4,1,1,25,0,0]}} [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- [505db1a90d2ae1ba46df5625aaed43b9] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- [14f02616095e037e] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- DATA (5,0,0): 505db1a90d2ae1ba46df5625aaed43b914f02616095e037e [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: --> ACK (6) [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: --> [8610be7e] [2024-04-26 07:47:26] [34mdebug[39m: zh:ezsp:uart: <-- ACK (0): 505db1a90d2ae1ba46df5625aaed43b914f02616095e037e [2024-04-26 07:47:26] [32minfo[39m: zh:ezsp:ezsp: <== Frame: 1f90015900f4081f4b1c0000b8d1f088be01bde4 [2024-04-26 07:47:26] [32minfo[39m: zh:ezsp:ezsp: <== 0x59: {"cls":"incomingRouteRecordHandler","id":89,"isRequest":false,"source":2292,"longId":{"type":"Buffer","data":[240,209,184,0,0,28,75,31]},"lastHopLqi":136,"lastHopRssi":-66,"relay":{"type":"Buffer","data":[189]}} [2024-04-26 07:47:26] [32minfo[39m: zh:ezsp:driver: handleRouteRecord: nwk=2292, ieee=οΏ½ΡΈ

og-gh avatar Apr 26 '24 07:04 og-gh

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

Having the same issues after trying to add a door sensor

harryba avatar May 02 '24 10:05 harryba

same here

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

Having the same issues after trying to add a door sensor

fszalaj avatar May 02 '24 12:05 fszalaj

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.

Chris0588 avatar May 02 '24 18:05 Chris0588

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

xsrplayerx avatar May 02 '24 19:05 xsrplayerx

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.

Pel1can111 avatar May 02 '24 20:05 Pel1can111

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)

EnzovdWetering avatar May 03 '24 04:05 EnzovdWetering

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

robvanoostenrijk avatar May 03 '24 07:05 robvanoostenrijk

Confirming I see the same issue after update

posul avatar May 03 '24 07:05 posul

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

hhrocha000 avatar May 03 '24 07:05 hhrocha000

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.

DennisJohnsen avatar May 03 '24 09:05 DennisJohnsen

Same problem here. Is there any solution?

litecross91 avatar May 03 '24 10:05 litecross91

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

EnzovdWetering avatar May 03 '24 10:05 EnzovdWetering

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.

litecross91 avatar May 03 '24 13:05 litecross91

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.

hhrocha000 avatar May 03 '24 13:05 hhrocha000

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

Thanks! I also have that coordinator

xsrplayerx avatar May 03 '24 13:05 xsrplayerx

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

guidox avatar May 03 '24 19:05 guidox

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.

hhrocha000 avatar May 03 '24 23:05 hhrocha000

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?

thombec avatar May 05 '24 16:05 thombec

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

litecross91 avatar May 05 '24 16:05 litecross91

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!

xsrplayerx avatar May 05 '24 21:05 xsrplayerx

@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

Ltek avatar May 06 '24 15:05 Ltek

[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 https://github.com/Koenkk/zigbee2mqtt/discussions/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!

Catalin84 avatar May 08 '24 04:05 Catalin84

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

archont00 avatar May 12 '24 11:05 archont00

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.

Ltek avatar May 12 '24 14:05 Ltek