-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Ember add installation code: Invalid code size #22446
Comments
Looks like this code doesn't have the CRC appended to it. I tested it locally, it seems to still be accepted by the adapter, so I'll modify the code to bypass the check in this scenario. I will mention this issue in the PR when that's available in dev, if you can then confirm it works, that would be great. 😉 |
Thanks a lot, I will Can you explain me what the CRC is? I am a bit of a newbie. After the code is sucessfully accepted by the adapter, we might still get the issue described here: #20169 Could this lacking data be the rootcause of it all? |
It's an error detection mechanism for data. Let me know if that works, and if you encounter the other problem you mentioned 😉 |
Thank you for the response, (Maybe this belongs more to the other ticket, but I am not really sure what I could do from here) logs [2024-05-05 14:58:31] info: z2m: Successfully added new install code
[2024-05-05 14:58:31] info: z2m: Zigbee: allowing new devices to join.
[2024-05-05 14:58:31] info: zh:ember: [STACK STATUS] Network opened.
[2024-05-05 14:58:48] info: zh:controller: Interview for '0x000d6f001910bced' started
[2024-05-05 14:58:48] info: z2m: Device '0x000d6f001910bced' joined
[2024-05-05 14:58:49] info: z2m: Starting interview of '0x000d6f001910bced'
[2024-05-05 14:58:57] warning: zhc:lixee: Failed to read zigbee attributes: Error: Cluster 'liXeePrivate' has no attribute 'motDEtat'
[2024-05-05 14:59:13] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "20262".
[2024-05-05 14:59:15] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "20262".
[2024-05-05 14:59:17] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "20262".
[2024-05-05 14:59:18] error: zh:controller: Interview failed for '0x000d6f001910bced with error 'Error: Interview failed because can not get node descriptor ('0x000d6f001910bced')'
[2024-05-05 14:59:18] error: z2m: Failed to interview '0x000d6f001910bced', device has not successfully been paired
[2024-05-05 14:59:22] info: zh:controller: Interview for '0x000d6f001910bced' started
[2024-05-05 14:59:22] info: z2m: Starting interview of '0x000d6f001910bced'
[2024-05-05 14:59:25] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "63572".
[2024-05-05 14:59:27] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "63572".
[2024-05-05 14:59:28] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "63572".
[2024-05-05 14:59:30] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "63572".
[2024-05-05 14:59:35] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "38021".
[2024-05-05 14:59:46] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "3342".
[2024-05-05 14:59:48] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "3342".
[2024-05-05 14:59:49] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "3342".
[2024-05-05 14:59:51] error: zh:controller: Interview failed for '0x000d6f001910bced with error 'Error: Interview failed because can not get node descriptor ('0x000d6f001910bced')'
[2024-05-05 14:59:51] error: z2m: Failed to interview '0x000d6f001910bced', device has not successfully been paired
[2024-05-05 14:59:55] info: zh:controller: Interview for '0x000d6f001910bced' started
[2024-05-05 14:59:55] info: z2m: Starting interview of '0x000d6f001910bced'
[2024-05-05 14:59:58] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "18900".
[2024-05-05 15:00:00] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "18900".
[2024-05-05 15:00:02] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "18900".
[2024-05-05 15:00:03] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "18900".
[2024-05-05 15:00:13] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "51606".
[2024-05-05 15:00:14] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "51606".
[2024-05-05 15:00:16] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "51606".
[2024-05-05 15:00:18] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "51606".
[2024-05-05 15:00:24] error: zh:controller: Interview failed for '0x000d6f001910bced with error 'Error: Interview failed because can not get node descriptor ('0x000d6f001910bced')'
[2024-05-05 15:00:24] error: z2m: Failed to interview '0x000d6f001910bced', device has not successfully been paired
[2024-05-05 15:00:28] info: zh:controller: Interview for '0x000d6f001910bced' started
[2024-05-05 15:00:28] info: z2m: Starting interview of '0x000d6f001910bced'
[2024-05-05 15:00:38] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "15596".
[2024-05-05 15:00:40] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "15596".
[2024-05-05 15:00:41] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "15596".
[2024-05-05 15:00:53] warning: zh:ember:ezsp: Received network/route error ROUTE_ERROR_SOURCE_ROUTE_FAILURE for "15285". Some logs are irrelevant:
Since they are linked with another device as explained in #22327 |
Indeed seems to be the same issue as that other thread. |
I am not exactly sure where the logs start and stop, also most likely there are other zigbee devices in here but you can see one failure loop as follows:
|
Closing since the issue here (install code) should be fixed in dev/next release. Will reply in the aforementioned issue for the twinguard pairing troubles. |
So it should be fine providing only the code of the QR from now on? (Without CRC) Also do you need me to repost in the other issue? |
After next release, it will be available yes, for now in dev. It's okay, I couldn't find anything in your logs, it seems the device is just not replying to the interview request from Z2M. I requested more info from other users in the other issue. |
What happened?
I have a Bosch Twinguard Zigbee device that I want to pair to z2m.
I am using the new
ember
adaptor with the Sonoff Dongle EIn the documentation I need to take a picture of the QR code on the device and Add an installation code before pairing.
My QR code:
RB01SG0D836591B3CC0010000000000000000000000D6F001910BCEDDLKDD7ED5CDAA8E2C708B67D2B1573DB684
z2m refuses to pair with the Invalid Code size error.
What did you expect to happen?
Continue to pairing
How to reproduce it (minimal and precise)
With an Ember adaptor,
Settings > Tools > Add installation code
RB01SG0D836591B3CC0010000000000000000000000D6F001910BCEDDLKDD7ED5CDAA8E2C708B67D2B1573DB684
The error will happen
Zigbee2MQTT version
1.37.0
Adapter firmware version
7.4.2
Adapter
Sonoff Zigbee Dongle E
Setup
Home assistant OS on Raspberrypi 5
Debug log
The text was updated successfully, but these errors were encountered: