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

ERROR : zh:controller:greenpower: Received undefined command from '0' #22140

Closed
mrmaximas opened this issue Apr 8, 2024 · 33 comments
Closed
Labels
problem Something isn't working

Comments

@mrmaximas
Copy link

What happened?

I don't have any greenpower devices, but over the last week or more once or twice per day it shows up in the log:
[2024-04-08 20:09:28] error: zh:controller:greenpower: Received undefined command from '0'

What did you expect to happen?

How to reproduce it (minimal and precise)

install latest devs

Zigbee2MQTT version

1.36.1-dev commit: cabc9f5

Adapter firmware version

20240315

Adapter

CC2652P7

Setup

Mac OS Sonoma latest on M2

Debug log

@mrmaximas mrmaximas added the problem Something isn't working label Apr 8, 2024
@ghitab77
Copy link

ghitab77 commented May 1, 2024

Same issue with 1.37.1

@akhosha2
Copy link

akhosha2 commented May 2, 2024

Same issue with 1.37.1

Just updated to 1.37.0. getting this warning when allowing new items to pair. Tried to pair two GiEX GXO2s and could only get one to pair for a few minutes. I then got a message saying that the one I did get to join left my network. Now neither can join.

@sharpcodex
Copy link

Same issue with 1.37.0

@starz91
Copy link

starz91 commented May 2, 2024

Same issue with last version 1.37.0-1

@abastosjr
Copy link

I have the same problem, V 1.37.0

@akhosha2
Copy link

akhosha2 commented May 2, 2024

So I managed to 'trick' my way into adding a new device by deleting an existing device (including the MQTT device in the integration). Then I went to pair it again with the new device and they both paired. Interestingly the existing device I deleted and repaired went back to it's original device number and confirmation.

@GigiPompieru
Copy link

I have the same problem, V 1.37.0

same issue since upgrading.

@FingerlessGlov3s
Copy link

FingerlessGlov3s commented May 2, 2024

Same here

Zigbee2MQTT version
1.37.0 commit: unknown
Coordinator type
EZSP v12
Coordinator revision
7.3.1.0 build 176
Coordinator IEEE Address
0xe0798dfffeeaffcf
Frontend version
0.6.165
19.32.0
0.45.0

@Koenkk
Copy link
Owner

Koenkk commented May 2, 2024

Can someone provide the debug logs of this?

See this on how to enable debug logging.

@illiteratealliterator
Copy link

I'm only just installing zigbee2mqtt for the first time, and ran into this error when trying to add my first device. I'm running in docker, and I see the error in the UI (and the log) when I click the Disable/Permit Join button in the frontend.

Here's the debug logs surrounding the error, although they may not be related:

[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: ==> {"cls":"sendMulticast","id":56,"isRequest":true,"apsFrame":{"profileId":41440,"sequence":30,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":242,"groupId":65533,"options"
:256},"hops":0,"nonmemberRadius":3,"messageTag":31,"message":{"type":"Buffer","data":[25,10,2,11,254,0]}}
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> DATA (4,3,0): 8400013800e0a12100f2f20001fdff1e00031f06190a020bfe00
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> [43c621a96c2af57d337894b8d7aa546fb6824e24b4ebd76d89f6386362227e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: -?- waiting (5)
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- [34c1b1a94d2a89b90b7e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- DATA (3,4,0): 34c1b1a94d2a89b90b7e
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> ACK (4)
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> [8430fc7e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- ACK (4): 34c1b1a94d2a89b90b7e
[2024-05-03 14:18:13] debug: zh:ezsp:uart: Unexpected packet sequence 4 | 5
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== Frame: 83900119009c
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== 0x19: {"cls":"stackStatusHandler","id":25,"isRequest":false,"status":156}
[2024-05-03 14:18:13] debug: zh:ezsp:driv: stackStatusHandler:
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- [45c6a1a96c2a1543ad367e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- DATA (4,5,0): 45c6a1a96c2a1543ad367e
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> ACK (5)
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> [8520dd7e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- ACK (5): 45c6a1a96c2a1543ad367e
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== Frame: 848001380000f1
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== 0x38: {"cls":"sendMulticast","id":56,"isRequest":false,"status":0,"sequence":241}
[2024-05-03 14:18:13] debug: zh:ezsp:uart: -+- waiting (5) success
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- [55c6b1a97d312a1652f8b54ad7555593b463bfd8abedce9874fbdf698bf7803fa9ed7e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- DATA (5,5,0): 55c6b1a9112a1652f8b54ad7555593b463bfd8abedce9874fbdf698bf7803fa9ed7e
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> ACK (6)
[2024-05-03 14:18:13] debug: zh:ezsp:uart: --> [8610be7e]
[2024-05-03 14:18:13] debug: zh:ezsp:uart: <-- ACK (5): 55c6b1a9112a1652f8b54ad7555593b463bfd8abedce9874fbdf698bf7803fa9ed7e
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== Frame: 849001450003e0a12100f2ff0001fdfff1ff000000ffff06190a020bfe00
[2024-05-03 14:18:13] debug: zh:ezsp:ezsp: <== 0x45: {"cls":"incomingMessageHandler","id":69,"isRequest":false,"type":3,"apsFrame":{"profileId":41440,"sequence":241,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":255
,"groupId":65533,"options":256},"lastHopLqi":255,"lastHopRssi":0,"sender":0,"bindingIndex":255,"addressIndex":255,"message":{"type":"Buffer","data":[25,10,2,11,254,0]}}
[2024-05-03 14:18:13] debug: zh:ezsp: processMessage: {"messageType":3,"apsFrame":{"profileId":41440,"sequence":241,"clusterId":33,"sourceEndpoint":242,"destinationEndpoint":255,"groupId":65533,"options":256},"lqi":255,"rssi":0,"sen
der":0,"bindingIndex":255,"addressIndex":255,"message":{"type":"Buffer","data":[25,10,2,11,254,0]}}
[2024-05-03 14:18:13] error: zh:controller:greenpower: Received undefined command from '0'
[2024-05-03 14:18:13] debug: zh:controller: Received payload: clusterID=33, address=0, groupID=null, endpoint=242, destinationEndpoint=242, wasBroadcast=true, linkQuality=255, frame={"header":{"frameControl":{"frameType":1,"manufact
urerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0},"manufacturerCode":null,"transactionSequenceNumber":10,"commandIdentifier":2},"payload":{"options":11,"commisioningWindow":254},"command":{"ID":2,"parame
ters":[{"name":"options","type":32},{"name":"commisioningWindow","type":33}],"name":"commisioningMode"}}
[2024-05-03 14:18:13] debug: zh:controller: Skipping command 'commisioningMode' because it is missing from the lookup
[2024-05-03 14:18:14] debug: z2m: MQTT publish: topic 'zigbee2mqtt/bridge/response/permit_join', payload '{"data":{"time":254,"value":true},"status":"ok","transaction":"014pc-7"}'
[2024-05-03 14:18:14] debug: zh:ezsp:uart: <-- [65c6b1a96b2a164fa674eb04aaa76d499db3d85bf3ce6701b77e]
[2024-05-03 14:18:14] debug: zh:ezsp:uart: <-- DATA (6,5,0): 65c6b1a96b2a164fa674eb04aaa76d499db3d85bf3ce6701b77e
[2024-05-03 14:18:14] debug: zh:ezsp:uart: --> ACK (7)
[2024-05-03 14:18:14] debug: zh:ezsp:uart: --> [87009f7e]
[2024-05-03 14:18:14] debug: zh:ezsp:uart: <-- ACK (5): 65c6b1a96b2a164fa674eb04aaa76d499db3d85bf3ce6701b77e
[2024-05-03 14:18:14] debug: zh:ezsp:ezsp: <== Frame: 8490013f0003fdffe0a12100f2ff0001fdfff01e0000
[2024-05-03 14:18:14] debug: zh:ezsp:ezsp: <== 0x3f: {"cls":"messageSentHandler","id":63,"isRequest":false,"type":3,"indexOrDestination":65533,"apsFrame":{"profileId":41440,"sequence":240,"clusterId":33,"sourceEndpoint":242,"d
estinationEndpoint":255,"groupId":65533,"options":256},"messageTag":30,"status":0,"message":{"type":"Buffer","data":[]}}

@BitterHA
Copy link

BitterHA commented May 3, 2024

Can someone provide the debug logs of this?

See this on how to enable debug logging.

same error, here my log :
log.log

@lettore
Copy link

lettore commented May 3, 2024

Same for me when I start/stop pairing, pairing works well anyway.
Versione Zigbee2MQTT
1.37.0 commit: 46f34c8
Tipo Coordinator
EZSP v13
Revisione Coordinator
7.4.2.0 build 0
Indirizzo IEEE Coordinatore
0xe0798dfffeb31b38
Versione frontend
0.6.165
19.32.0
0.45.0

@litecross91
Copy link

same here
1.37.0-1
usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2
Coordinator firmware version: '{"meta":{"maintrel":"7 ","majorrel":"6","minorrel":"10","product":8,"revision":"6.10.7.0 build 435"},"type":"EZSP v8"}'
Core
2024.4.4
Supervisor
2024.04.4
Operating System
12.2
Frontend
20240404.2

@tibur79
Copy link

tibur79 commented May 4, 2024

Same issue since upgrading. Received undefined command from '0'

@litecross91
Copy link

Check this: #22226 (comment)

@Koenkk
Copy link
Owner

Koenkk commented May 4, 2024

  • Does this error disappear after using the ember drivers instead? (docs)
  • Is it just a log or did something actually break?

@tibur79
Copy link

tibur79 commented May 4, 2024 via email

@rafpigna
Copy link

rafpigna commented May 4, 2024

+1

1 similar comment
@xario
Copy link

xario commented May 4, 2024

+1

@VladislavVesely
Copy link

Same issue here

@rboutan
Copy link

rboutan commented May 5, 2024

Bonjour,
Voici le message depuis la dernière mise à jour.
Merci.

Capture

@tibur79
Copy link

tibur79 commented May 5, 2024 via email

@rboutan
Copy link

rboutan commented May 5, 2024

J'ai restauré l'ancienne version et l'erreur a disparu.
Je vais attendre un peu avant de refaire une MAJ.
Merci pour l'info.

@rafpigna
Copy link

rafpigna commented May 5, 2024

Any pairing works fine for me, no issues at all when adding new devices to the network, but the error is always there. I also have other bunch of errors in the log about CRC or other data related issues, but I will open a new issue for that.

@CoderJoeyMoment
Copy link

+1

Zigbee2MQTT version
1.37.0-dev commit: beedfae / 1.37.0 stable (both)
Coordinator type
EZSP v12
Coordinator revision
7.3.1.0 build 176
Coordinator IEEE Address
0xe0798dfffe999c5a

@Koenkk
Copy link
Owner

Koenkk commented May 5, 2024

Does this happen when permitting join or when you have permit_join: true in your configuration.yaml?

@akhosha2
Copy link

akhosha2 commented May 5, 2024

Does this happen when permitting join or when you have permit_join: true in your configuration.yaml?

When I'm permitting join.

@lordforall
Copy link

lordforall commented May 6, 2024

Same issue for me.

Latest updates for everything including firmware controller and also trying ember driver.
Can no longer add any devices and just get the error when clicking permit to join

EDIT:
I was able to fix it by making sure I actually had the right firmware on there for my ZBDongle-E

I used firmware:
https://github.com/darkxst/silabs-firmware-builder/blob/main/firmware_builds/zbdonglee/ncp-uart-hw-v7.4.2.0-zbdonglee-115200.gbl

Updated with online flashing tool:
https://darkxst.github.io/silabs-firmware-builder/

Changed my z2m config to ember:
serial:
port: >-
/dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20230218104706-if00
adapter: ember

@zhongqhang
Copy link

i use xiaomi gataway 3
same problem
Uploading 1706858417.png…

@Koenkk
Copy link
Owner

Koenkk commented May 6, 2024

Fixed!

Changes will be available in the dev branch in a few hours from now.

@litecross91
Copy link

Fixed!

Changes will be available in the dev branch in a few hours from now.

Sorry but how can we install it? In HACS I can "Redownload" it and choose it but in Addons doesn't. Where is the dev branch?

@GigiPompieru
Copy link

Fixed!
Changes will be available in the dev branch in a few hours from now.

Sorry but how can we install it? In HACS I can "Redownload" it and choose it but in Addons doesn't. Where is the dev branch?

you should wait for it to make it to the main one

@BelayFR
Copy link

BelayFR commented May 9, 2024

Fixed!

Changes will be available in the dev branch in a few hours from now.

Works here ! SONOFF_Zigbee_3.0_USB_Dongle_Plus 7.3.1.0 build 176 !
Thx a lot

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

No branches or pull requests