Lot of errors "Error: Command ApsDataRequest failed with status: Busy"

[nbranquinho]

What happened?

After update to version 2.5.0, the system start giving a lot of errors and I don't let me control the devices in Zigbee2MQTT.
I updated to v2.5.1 but still happen

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.5.1

Adapter firmware version

0x26720700

Adapter

ConBee_II

Setup

I'm running as ADDon in HA

Debug log

45df7312_zigbee2mqtt_2025-07-02T21-46-44.714Z.log

[manup]

Busy status means the APS queue is full. This happens when there are too many requests to non responsive device which due the newly always enabled ACKs can take time to process until they timeout (e.g. offline devices or devices for which there is no route yet).

Can you try to unplug the ConBee and re-attach after 10 seconds to see if that helps?

[nbranquinho]

Busy status means the APS queue is full. This happens when there are too many requests to non responsive device which due the newly always enabled ACKs can take time to process until they timeout (e.g. offline devices or devices for which there is no route yet).

Can you try to unplug the ConBee and re-attach after 10 seconds to see if that helps?

ok, thx, I'll do your suggestion and later I leave feedback with results.

[pazzotranquillo]

Busy status means the APS queue is full. This happens when there are too many requests to non responsive device which due the newly always enabled ACKs can take time to process until they timeout (e.g. offline devices or devices for which there is no route yet).

Can you try to unplug the ConBee and re-attach after 10 seconds to see if that helps?

Hi, I'm experiencing the same issue. I've unplugged my Conbee III (updated to the last FW version) and that didn't help.

[nbranquinho]

Busy status means the APS queue is full. This happens when there are too many requests to non responsive device which due the newly always enabled ACKs can take time to process until they timeout (e.g. offline devices or devices for which there is no route yet).

Can you try to unplug the ConBee and re-attach after 10 seconds to see if that helps?

I've done the test but no success. Still have the error.

EDIT: This behavior does not happen in version 2.4.0-1, which I restored and everything went back to working normally.

[Koenkk]

Should be fixed now!

Changes will be available in the dev branch in a few hours from now and in the next release which is every 1st of the month.