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

zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO #25132

Open
cikaybe opened this issue Dec 8, 2024 · 10 comments
Open

zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO #25132

cikaybe opened this issue Dec 8, 2024 · 10 comments
Labels
problem Something isn't working

Comments

@cikaybe
Copy link

cikaybe commented Dec 8, 2024

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:

@cikaybe cikaybe added the problem Something isn't working label Dec 8, 2024
@vlavrynovych
Copy link

vlavrynovych commented Dec 11, 2024

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 sensor.zigbee2mqtt_bridge_permit_join_timeout is Unknown.

And I also see similar error in the logs about Timeout after 10000ms with similar payload, but in my case it belongs to lumi.ctrl_neutral2 model. This error happens ocasionally and is not related to the attempt to permit joining

[2024-12-12 01:17:38] error: 	zh:controller:device: 
Read response to 0x00158d0002c569e5 failed (ZCL command 0x00158d0002c569e5/1 genTime.readRsp({"time":787274249}, 
{"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"srcEndpoint":1,"reservedBits":0,"transactionSequenceNumber":223,"writeUndiv":false}) 
failed (Data request failed with error: 'Timeout' (9999)))

@vlavrynovych
Copy link

BTW, if I try to restart the addon then joining is allowed, but I cannot turn it off.
Until I update lets say select.zigbee2mqtt_bridge_log_level to another value it's stuck in the selected position and now errors and no reaction.

Not sure if it's related or maybe just another symptome but I also cannot build the Map

@vlavrynovych
Copy link

I see that permit_join_timeout will be removed in #25082 (already see it in the changelog). I hope it will solve my problem(s).

@Nerivec
Copy link
Collaborator

Nerivec commented Dec 12, 2024

@cikaybe if you have permit_join: true in configuration.yaml, try removing the line (will default to false). That line will be gone in 2.0.0 anyway. Looks like you are having other issues though, since it seems everything is timing out. Did you go through the checklist for network stability?

@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 permit_join line from your configuration.yaml (same as above).

@vlavrynovych
Copy link

Hi @Nerivec,

My problem is fixed.

I removed permit_join and applied this config (from Zigbee2MQTT 2.0.0 breaking changes)

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.
Thank you @Nerivec , you saved me a lot of time.

@cikaybe
Copy link
Author

cikaybe commented Dec 12, 2024

@Nerivec thanks for taking the time for answering.

About my configuration.yalm:

homeassistant: true
advanced:
  network_key:
    - lots of numbers
  pan_id: 18035
  ext_pan_id:
    - lots of numbers
  homeassistant_legacy_entity_attributes: false
  legacy_api: false
  legacy_availability_payload: false
  log_level: error
mqtt:
  base_topic: zigbee2mqtt2
  server: mqtt://core-mosquitto
  user: *
  password: *
serial:
  port: tcp://192.168.68.126:6638
  adapter: zstack
  baudrate: 115200
frontend:
  port: 8099
device_options:
  legacy: false
devices:
  -75 devices
permit_join: false
availability: true
groups:
  '1':
    friendly_name: L Z Corredor Cima

I have a fresh intallation with a SLZB-06 with lan on a raspberry 4 8gb.

Today logs:

[2024-12-11 13:38:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 14:45:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 14:58:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 16:18:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 16:21:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 17:35:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 18:21:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 19:11:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 19:15:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 19:31:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 20:45:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 21:28:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 23:01:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 23:48:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-11 23:51:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 00:31:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 02:35:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 03:18:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 05:31:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 06:18:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 07:55:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 08:35:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 10:01:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 10:08:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 11:31:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 11:35:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 12:21:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 12:35:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 13:08:29] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 13:55:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 14:25:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 14:45:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 14:55:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 15:05:09] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms
[2024-12-12 15:21:49] error: 	zh:controller: Failed to keep permit join alive: Error: AREQ - ZDO - mgmtPermitJoinRsp after 10000ms

@Nerivec
Copy link
Collaborator

Nerivec commented Dec 12, 2024

Are you turning on permit join before these start appearing (yourself or through automation)?
Can you set log_level: debug and restart Z2M so we can get a bit more context?

@cikaybe
Copy link
Author

cikaybe commented Dec 12, 2024

I'm not adding anything not manually or through an automation.

The code I get after restarting. Should I wait a couple of hours?
45df7312_zigbee2mqtt_2024-12-12T20-39-44.220Z.log

The restart part starts at line 6195.

Thank you

@Koenkk
Copy link
Owner

Koenkk commented Dec 13, 2024

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

@netizeni
Copy link

netizeni commented Dec 14, 2024

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:

info 2024-12-14 14:11:46z2m: Zigbee: allowing new devices to join.
info 2024-12-14 14:11:46zh:ember: [STACK STATUS] Network opened.

There's no logs when z2m freezes and switch back from "Disable join (All)" to "Permit join (all)".

In configuration.yaml permit_join: false

I also see similar issue here #25164

edit: to expand on this, I switched to permit_join: true and managed to add a smart plug. This device is absolutely the same as a bunch of others which I added previously. It shows this in about page, so seems it's added normally, but states are constatly null for the fields I'm interested in like power, energy, state etc.

{
    "child_lock": null,
    "current": null,
    "energy": null,
    "indicator_mode": null,
    "linkquality": 196,
    "power": null,
    "power_outage_memory": null,
    "state": null,
    "update": {
        "installed_version": -1,
        "latest_version": -1,
        "state": null
    },
    "update_available": null,
    "voltage": 222
}

3

Zigbee2MQTT version
1.42.0 commit: bc6eccf

Coordinator type
EmberZNet

Coordinator revision
7.4.4 [GA]

Frontend version
0.7.6

zigbee-herdsman-converters version
20.58.0

zigbee-herdsman version
2.1.9

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

5 participants