ASH_ERROR_TIMEOUTS

[flowcool]

What happened?

perpetual reboot

What did you expect to happen?

No response

How to reproduce it (minimal and precise)

No response

Zigbee2MQTT version

2.7.1-dev (same in latest)

Adapter firmware version

8.2.2

Adapter

EmberZNet

Setup

ha in docker

Device database.db entry

No response

Debug log

[2026-01-02 08:39:38] error: zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=45 Len=10].
[2026-01-02 08:39:38] error: z2m: Adapter disconnected, stopping
[2026-01-02 08:39:38] warning: z2m: Failed to ping 'Lampe Salon' (attempt 1/1, ZCL command 0xf0d1b800001da1fc/1 genBasic.read(["zclVersion"], {"timeout":10000,"disableResponse":false,"disableRecovery":true,"disableDefaultResponse":true,"direction":0,"reservedBits":0,"writeUndiv":false,"sendPolicy":"immediate"}) failed (x> [ZCL to=0xf0d1b800001da1fc:24306 apsFrame={"profileId":260,"clusterId":0,"sourceEndpoint":1,"destinationEndpoint":1,"options":4416,"groupId":0,"sequence":0}] Failed to send request with status=FAIL.))

Notes

No response

[Asmir1975]

Same issue here. I can confirm this behavior on SLZB-06M with EmberZNet 8.2.2 dev firmware.

My Setup:
Coordinator: SLZB-06M (EmberZNet 8.2.2 dev via OTA)

Zigbee2MQTT: 2.7.2 stable (also tested edge)

Environment: Home Assistant OS (Add-on)

Error: ASH_ERROR_TIMEOUTS loop + perpetual reboots

Observation:
System enters a reboot loop shortly after startup with transaction failures.
Only solution for me was to flash the coordinator back to EmberZNet 8.0.2 GA. Since downgrading, the network is 100% stable again.

It seems the current 8.2.2 dev firmware for SLZB-06M is not yet ready for production use with Z2M 2.7.x. Waiting for an official stable release from SMLight devs seems to be the only fix right now.