-
-
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
zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO #25132
Comments
Hi guys, I upgraded from 1.35.1-1 to 1.42.0-2 I have a similar problem, but for me Permit Join (All) button does not work at all. The request sends successfully from frontend and no reaction - no counter. After playing with it I've found that the And I also see similar error in the logs about Timeout after 10000ms with similar payload, but in my case it belongs to
|
BTW, if I try to restart the addon then joining is allowed, but I cannot turn it off. Not sure if it's related or maybe just another symptome but I also cannot build the Map |
@cikaybe if you have @vlavrynovych that timeout is likely just the device being unavailable from time to time (passing interference?), don't think it's related at first glance. Try to remove the |
Hi @Nerivec, My problem is fixed. I removed advanced:
homeassistant_legacy_entity_attributes: false
homeassistant_legacy_triggers: false
legacy_api: false
legacy_availability_payload: false
device_options:
legacy: false Now even network map works!! So, means it was somehow related. |
@Nerivec thanks for taking the time for answering. About my configuration.yalm:
I have a fresh intallation with a SLZB-06 with lan on a raspberry 4 8gb. Today logs:
|
Are you turning on permit join before these start appearing (yourself or through automation)? |
I'm not adding anything not manually or through an automation. The code I get after restarting. Should I wait a couple of hours? The restart part starts at line 6195. Thank you |
@cikaybe could you provide the debug log from starting z2m until this error appears? The log is truncated and therefore I cannot see the root cause. |
I'm experiencing the similar problem, so I'm not sure should I open a new issue. Since I switched to Sonoff Dongle E and ember driver from ZB-GW04 and ezsp driver, after clicking "Permit join (all)" button, just after a couple of seconds showing "Disable join (All) 04:11" it freezes for a second or two and switches back to "Permit join (all)". I've put a log level to be debug, but all I see related to this issue is when I click "Permit join (all)". It shows these two info logs:
There's no logs when z2m freezes and switch back from "Disable join (All)" to "Permit join (all)". In I also see similar issue here #25164 edit: to expand on this, I switched to
Zigbee2MQTT version Coordinator type Coordinator revision Frontend version zigbee-herdsman-converters version zigbee-herdsman version |
What happened?
Hi,
I’m having this error. I’m using a slzb-06 dongle. How can I stop it?
What did you expect to happen?
The error to stop.
How to reproduce it (minimal and precise)
It’s a fresh installation with a slzb-06 dongle.
Zigbee2MQTT version
1.42.0-2
Adapter firmware version
20240315
Adapter
SLZB-06
Setup
Raspberry 4 8GB with Home Assistant
Debug log
[2024-12-08 07:55:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 08:28:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 09:15:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 11:15:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 11:38:45] error: z2m: Publish 'set' 'state' to 'L Z2 Corredor Baixo (2)' failed: 'Error: ZCL command 0xa4c1383be8ffde7e/1 genOnOff.on({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 54832 - 1 - 49 - 6 - 11 after 10000ms)'
[2024-12-08 11:55:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 11:58:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 13:45:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 15:15:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 16:05:08] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 16:41:48] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 17:18:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 18:38:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 18:48:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 19:58:28] error: zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-08 21:31:24] error: z2m: Publish 'set' 'state' to 'L Z2 Corredor Cima (2)' failed: 'Error: ZCL command 0xa4c1386962c430da/1 genOnOff.off({}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":false,"direction":0,"reservedBits":0,"writeUndiv":false}) failed (Timeout - 19287 - 1 - 36 - 6 - 11 after 10000ms)'
[2024-12-08 22:31:48] error:
The text was updated successfully, but these errors were encountered: