zigbee2mqtt
zigbee2mqtt copied to clipboard
Koenkk
Z-Dongle E ember periodically error
What happened?
Zigbee2MQTT periodically report error zh:ember:uart:ash: Received ERROR from adapter, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT then restart.
What did you expect to happen?
The adapter gives an error several times a day, leading to loss of connection and stopping and restarting Zigbee2Mqtt.
How to reproduce it (minimal and precise)
No response
Zigbee2MQTT version
1.40.0
Adapter firmware version
7.4.3 [GA]
Adapter
SonOFF Dongle-E
Setup
HA on VM Synology DSM
Debug log
I removed the USB extension cable, switched to ezsp in the settings. Problem still occurs.
[2024-09-05 12:02:18] error: zh:ezsp:uart: --> Error: Error: {"sequence":4} after 4000ms [2024-09-05 12:02:18] error: zh:ezsp:uart: -!- break waiting (4) [2024-09-05 12:02:18] error: zh:ezsp:uart: Can't send DATA frame (3,0,0): 53000134000065ae040106000101000100009a9b0518880b0a00 [2024-09-05 12:02:19] debug: zh:ezsp:uart: ->> DATA (3,0,1): 53000134000065ae040106000101000100009a9b0518880b0a00 [2024-09-05 12:02:19] debug: zh:ezsp:uart: --> [387d3121a9602a15d7f7904b23aa5493499d4e273176cb7f03f6cc63c3787e] [2024-09-05 12:02:19] debug: zh:ezsp:uart: -?- rewaiting (4) [2024-09-05 12:02:20] debug: zh:ezsp:uart: <-- [c20251a8bd7e] [2024-09-05 12:02:20] debug: zh:ezsp:uart: <-- Error c20251a8bd7e [2024-09-05 12:02:20] debug: zh:ezsp:uart: Uart reseting [2024-09-05 12:02:20] debug: zh:ezsp:uart: --> Write reset [2024-09-05 12:02:20] debug: zh:ezsp:uart: --> [1ac038bc7e] [2024-09-05 12:02:20] debug: zh:ezsp:uart: -?- waiting reset [2024-09-05 12:02:23] error: zh:ezsp:uart: --> Error: Error: {"sequence":4} after 4000ms [2024-09-05 12:02:23] error: zh:ezsp:uart: -!- break rewaiting (4) [2024-09-05 12:02:23] error: zh:ezsp:uart: Can't resend DATA frame (3,0,1): 53000134000065ae040106000101000100009a9b0518880b0a00 [2024-09-05 12:02:23] debug: zh:ezsp:ezsp: onSerialReset() [2024-09-05 12:02:23] debug: zh:ezsp:driv: onEzspReset() [2024-09-05 12:02:23] debug: zh:ezsp:driv: Reset connection. [2024-09-05 12:02:23] debug: zh:ezsp:driv: Stopping driver [2024-09-05 12:02:23] debug: zh:ezsp:ezsp: Closing Ezsp [2024-09-05 12:02:23] debug: zh:ezsp:uart: Closing UART [2024-09-05 12:02:23] debug: zh:ezsp:driv: Request error Error: Failure send sendUnicast:{"type":"Buffer","data":[83,0,1,52,0,0,101,174,4,1,6,0,1,1,0,1,0,0,154,155,5,24,136,11,10,0]} [2024-09-05 12:02:23] debug: zh:controller:endpoint: Error: ZCL command 0x282c02bfffed898b/1 genOnOff.defaultRsp({"cmdId":10,"statusCode":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"reservedBits":0,"transactionSequenceNumber":136,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error) at EZSPAdapter.sendZclFrameToEndpointInternal (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/adapter/ezspAdapter.ts:515:19) at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:36:20) at Request.send (/app/node_modules/zigbee-herdsman/src/controller/helpers/request.ts:82:20) at Endpoint.zclCommand (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:911:28) at Endpoint.defaultResponse (/app/node_modules/zigbee-herdsman/src/controller/model/endpoint.ts:610:9) at Device.onZclData (/app/node_modules/zigbee-herdsman/src/controller/model/device.ts:498:17) at Controller.onZclPayload (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:841:13) [2024-09-05 12:02:23] debug: zh:controller:device: Default response to 0x282c02bfffed898b failed (Error: ZCL command 0x282c02bfffed898b/1 genOnOff.defaultRsp({"cmdId":10,"statusCode":0}, {"timeout":10000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":1,"reservedBits":0,"transactionSequenceNumber":136,"writeUndiv":false}) failed (sendZclFrameToEndpointInternal error)) [2024-09-05 12:02:30] error: zh:ezsp:uart: --> Error: Error: {"sequence":-1} after 10000ms [2024-09-05 12:02:30] debug: zh:ezsp:ezsp: onSerialReset() [2024-09-05 12:02:30] debug: zh:ezsp:driv: onEzspReset() [2024-09-05 12:02:30] debug: zh:ezsp:driv: Reset connection. [2024-09-05 12:02:30] debug: zh:ezsp:driv: Stopping driver [2024-09-05 12:02:30] debug: zh:ezsp:ezsp: Closing Ezsp [2024-09-05 12:02:30] debug: zh:ezsp:uart: Closing UART [2024-09-05 12:02:30] error: zh:ezsp:uart: Failed to reset on Error Frame: Error: Reset error: Error: {"sequence":-1} after 10000ms [2024-09-05 12:02:31] debug: zh:ezsp:driv: Startup again. [2024-09-05 12:02:31] debug: zh:ezsp:uart: RTS/CTS config is off, enabling software flow control. [2024-09-05 12:02:31] debug: zh:ezsp:uart: Opening SerialPort with {"path":"/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_186ff44314e2ed11b891eb5162c613ac-if00-port0","baudRate":115200,"rtscts":false,"autoOpen":false,"parity":"none","stopBits":1,"xon":true,"xoff":true} [2024-09-05 12:02:53] debug: zh:ezsp:uart: Port closed. Error? null [2024-09-05 12:02:53] debug: zh:ezsp:ezsp: onSerialClose() [2024-09-05 12:02:53] debug: zh:ezsp:uart: Serialport opened [2024-09-05 12:02:53] debug: zh:ezsp:uart: Uart reseting [2024-09-05 12:02:53] debug: zh:ezsp:uart: --> Write reset [2024-09-05 12:02:53] debug: zh:ezsp:uart: --> [1ac038bc7e] [2024-09-05 12:02:53] debug: zh:ezsp:uart: -?- waiting reset [2024-09-05 12:02:54] debug: zh:ezsp:driv: Startup again. [2024-09-05 12:02:54] debug: zh:ezsp:uart: RTS/CTS config is off, enabling software flow control. [2024-09-05 12:02:54] debug: zh:ezsp:uart: Opening SerialPort with {"path":"/dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_186ff44314e2ed11b891eb5162c613ac-if00-port0","baudRate":115200,"rtscts":false,"autoOpen":false,"parity":"none","stopBits":1,"xon":true,"xoff":true} [2024-09-05 12:02:54] error: zh:ezsp:ezsp: Connection attempt 1 error: Error: Error Resource temporarily unavailable Cannot lock port [2024-09-05 12:02:54] debug: zh:ezsp:uart: <-- [c1020b0a527e] [2024-09-05 12:02:54] debug: zh:ezsp:uart: <-- RSTACK c1020b0a527e [2024-09-05 12:02:54] debug: zh:ezsp:uart: RSTACK Version: 2 Reason: RESET_SOFTWARE frame: c1020b0a527e [2024-09-05 12:02:54] debug: zh:ezsp:uart: -+- waiting reset success [2024-09-05 12:02:56] debug: zh:ezsp:ezsp: ==> version: {"desiredProtocolVersion":4} [2024-09-05 12:02:56] debug: zh:ezsp:driv: Reset error Error: Connection not initialized [2024-09-05 12:02:56] debug: zh:ezsp:driv: Stopping driver [2024-09-05 12:02:56] debug: zh:ezsp:ezsp: Closing Ezsp [2024-09-05 12:02:56] debug: zh:ezsp:uart: Closing UART [2024-09-05 12:02:56] debug: zh:ezsp:ezsp: onSerialClose() [2024-09-05 12:02:56] debug: zh:ezsp:driv: onEzspClose() [2024-09-05 12:02:56] debug: zh:ezsp: onDriverClose() [2024-09-05 12:02:56] debug: zh:controller: Adapter disconnected [2024-09-05 12:02:56] debug: zh:ezsp:driv: Stopping driver [2024-09-05 12:02:56] debug: zh:ezsp:ezsp: Closing Ezsp [2024-09-05 12:02:56] debug: zh:ezsp:uart: Closing UART [2024-09-05 12:02:56] debug: zh:ezsp:ezsp: onSerialClose() [2024-09-05 12:02:56] debug: zh:ezsp:driv: onEzspClose() [2024-09-05 12:02:56] debug: zh:ezsp: onDriverClose() [2024-09-05 12:02:56] error: z2m: Adapter disconnected, stopping [2024-09-05 12:02:56] debug: z2m: Saving state to file /config/zigbee2mqtt/state.json [2024-09-05 12:02:56] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'offline' [2024-09-05 12:02:56] info: z2m: Disconnecting from MQTT server [2024-09-05 12:02:56] info: z2m: Stopping zigbee-herdsman... [2024-09-05 12:02:56] debug: zh:controller:database: Writing database to '/config/zigbee2mqtt/database.db' [2024-09-05 12:02:57] info: z2m: Stopped zigbee-herdsman [2024-09-05 12:02:57] info: z2m: Stopped Zigbee2MQTT
https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html#error-resource-temporarily-unavailable-cannot-lock-port might help
Do you have any other services running which access USB devices? I think the error happens because an other process tries to access the port
Do you have any other services running which access USB devices? I think the error happens because an other process tries to access the port
I have checked for this first. HA installed on Virtual Mashine, full oficial image. USB port mapped to VM ( and in case of disconnect i have to remap manually in VM settings).
I have no other stick for check if this stick is faulty.
Can you check on other hardware? e.g. your laptop
Unfortunately, no. I tried flashing with earlier firmware versions. With 7.4.1 Zegbee2MQTT doesn't start at all.
Can you check on other hardware? e.g. your laptop
So, after observations, I see that freezes occur when smart plugs are turned on. I have several temperature and humidity sensors in the system and three smart sockets that are turned on and off by events. At the same time, I now remember that freezes occurred several times when turning on from the dashboard.
Can you check on other hardware? e.g. your laptop
I caught it on video.
https://drive.google.com/file/d/1bIXjSlGxa923AWgXEgEgWkyd4Jod5G6-/view?usp=sharing
Can you try the firmware from this post in combination with the
emberdriver?
[2024-09-06 11:29:13] error: z2m: Adapter disconnected, stopping [11:29:21] INFO: Preparing to start... [11:29:21] INFO: Socat not enabled [11:29:22] INFO: Starting Zigbee2MQTT... Starting Zigbee2MQTT without watchdog. [2024-09-06 12:03:38] error: zh:ember:uart:ash: Received ERROR from adapter, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT. [2024-09-06 12:03:38] error: zh:ember:uart:ash: ASH disconnected | Adapter status: ASH_NCP_FATAL_ERROR [2024-09-06 12:03:38] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR. [2024-09-06 12:03:38] error: zh:ember: Adapter fatal error: HOST_FATAL_ERROR [2024-09-06 12:03:46] error: zh:ember:ezsp: ERROR Transaction failure; status=ASH_ERROR_TIMEOUTS. Last Frame: [FRAME: ID=52:"SEND_UNICAST" Seq=106 Len=7]. [2024-09-06 12:04:08] error: z2m: Adapter disconnected, stopping
Could you provide the debug log from starting z2m until the crash (resulting from turning on the plugs)?
See this on how to enable debug logging.
Can you try the firmware from this post in combination with the
emberdriver?
After the second adapter reflash it started but the problem did not disappear. It hangs-up then i switch on-off "smartplug salon" rapidly adout 10 times.. log (6).log
@Nerivec could you check this one? It's a bit interesting that this causes a crash, there are not too many messages.
Strange indeed, crash after only a couple requests in the queue. It should handle 80+ queue without issue with default concurrency (tested on Dongle-E with a generic Tuya RGB strip).
@EugenKomi From your last logs, it seems to happen only when toggling repeatedly in a short amount of time, correct?
Can you check if the same happens if you set adapter_concurrent: 1 see docs? Note: you will likely notice a slight delay when triggering.
I see all these smart plugs you have joined at the moment are zb+ble, any chance you have another device model you could join (even temporarily) to see if the same happens?
Since it happens with ezsp also, it does sound like some kind of weird interference.
Strange thing I noticed in the past few weeks, Dongle-E that have the ID format that does not have V2 in it, seem to be having more troubles... Any chance you can slide off the cover from your adapter (couple of tiny screws on the side) and take a picture of both sides when you have some time?
From your last logs, it seems to happen only when toggling repeatedly in a short amount of time, correct?
No, this effect seems to be cumulative. For example, when I go to bed, my fumigator turns on once an hour, and turns off after an hour. The first turn-on is at 10 p.m. Judging by the logs, the drop happened at 2 a.m. last night. During the day, the dehumidifier turns on about twice an hour. The drop is more frequent.
Ok, so, not a stress problem at all then.
Can you check your previous logs, see if the drops happen roughly around the same time of day (example: mostly around 4:30PM and around 2:00AM)? If not, can you see any kind of pattern if you put together "time of crashes + what's going on in the house + whatever else might affect the network or machine z2m is running on"?
Ok, so, not a stress problem at all then.
Can you check your previous logs, see if the drops happen roughly around the same time of day (example: mostly around 4:30PM and around 2:00AM)? If not, can you see any kind of pattern if you put together "time of crashes + what's going on in the house + whatever else might affect the network or machine z2m is running on"?
About 10 cicles on-off of smart plugs (all together commands).
This manual simulation: https://drive.google.com/file/d/1zuTz2ZBMPXkEEdC8q2k8QYFipDsIFcZ6/view?usp=sharing
I think it's a com port problem. I ordered HamGeek POE Zigbee 3.0 Coordinator, when it arrives I'll connect it via local network and I think the problem will go away.
Ok, so, not a stress problem at all then.
Can you check your previous logs, see if the drops happen roughly around the same time of day (example: mostly around 4:30PM and around 2:00AM)? If not, can you see any kind of pattern if you put together "time of crashes + what's going on in the house + whatever else might affect the network or machine z2m is running on"?
Some correlations:
Initially I had HA installed in a Docker container on Synology DSM 6.2.4. I bought Dongle-E, but the problem was that I couldn't find the serial port in the device directory. Drivers and all other methods found on the Internet did not help.
Then I tried to install a virtual machine, stop containers with HA.fnd Z2MQTT. After mapping in the virtual machine everything worked, but the adapter hung, as described above.
I bought zigstar uzg-01 (Chenese clon). In the virtual machine it didn't want to work at all. The USB port was mapped, but the Z2MQTT didn't start, the TะกP didn't work.
Then I stopped Z2MQTT in the VM and launched in the Docker container. And then everything worked fine without interruptions on the TCP. However, the Synology COM port still does not connect, but it is not necessary.
Well, I flashed Dongle - E to the router, installed HA in the neighboring container, and stopped the virtual machine. In this combination, everything works fine.
Mosquitto installed as Synology package.
There seems to be a few reports around the Dongle E and the same error behavior. Linking them here, hoping to provide/gather the information and potentially close this or the others to consolidate the issues. https://github.com/Koenkk/zigbee2mqtt/issues/23861 https://github.com/Koenkk/zigbee2mqtt/issues/23706 https://github.com/Koenkk/zigbee2mqtt/issues/23761
Thank you all for documenting and supporting this. Read through all about this, because I was experiencing the issue: the_boom.log In my case, I came across it while clicking away at this Moes 4 button switch. I noticed the comment about trying v8.0.1. Before trying it, I checked all the version in the reports and they are all 7.4.3 [GA]. I decided to move to 7.4.4 before going the experimental route. I no longer experience this issue, running the 7.4.4 version. I'm not that confident in this solution but would be interesting to see if it has any effect for others.
Several users affected by this problem have indeed reported that updating to 7.4.4 fixed the problem. If anyone is still affected, try to update, and report back if it still doesn't work for you.
Another user, I found this thread after switching from RFlink to Zigbee using the Sonoff Zigbee 3 ZB-Dongle-E. I flashed it to 7.4.3 and wasn't even aware of the firmware links above (7.4.3 was the highest I found).
Had the same problem, with the adapter crashing occasionally, but always when sending a lot of commands at once (ie when setting a scene with 10+ lights, using Home Assistant or Domoticz). Every time the ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT error, followed by adapter disconnected. Exactly as above.
So just to hopefully help others: for me, the update to 7.4.4 also fixed the issue! Thanks for everybody's efforts.
I'm experiencing this issue when trying to perform an OTA of my IKEA Styrbar light switches. The issue has been present on both 7.4.4 and 8.0.2
I am still having this problem with v7.4.4. I am running HAOS in a virtual machine using PROXMOX.
What can I do to help to solve this issue?
This is my latest config:
data_path: /config/zigbee2mqtt
socat:
enabled: false
master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
options: "-d -d"
log: false
mqtt: {}
serial:
port: /dev/ttyUSB0
adapter: ember
rtscts: false
advanced:
adapter_concurrent: 1
adapter_delay: 200
Here is a short log:
[2024-10-24 16:10:17] info: z2m: Zigbee2MQTT started!
[2024-10-24 16:10:17] error: zh:ember:uart:ash: Received ERROR from adapter, with code=ERROR_EXCEEDED_MAXIMUM_ACK_TIMEOUT_COUNT.
[2024-10-24 16:10:17] error: zh:ember:uart:ash: ASH disconnected | Adapter status: ASH_NCP_FATAL_ERROR
[2024-10-24 16:10:17] error: zh:ember:uart:ash: Error while parsing received frame, status=ASH_NCP_FATAL_ERROR.
[2024-10-24 16:10:17] error: zh:ember: Adapter fatal error: HOST_FATAL_ERROR
[2024-10-24 16:10:17] info: zh:ember:uart:ash: ASH COUNTERS since last clear:
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Total frames: RX=4020, TX=4654
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Cancelled : RX=0, TX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: DATA frames : RX=3965, TX=1019
[2024-10-24 16:10:17] info: zh:ember:uart:ash: DATA bytes : RX=100827, TX=26141
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Retry frames: RX=35, TX=2
[2024-10-24 16:10:17] info: zh:ember:uart:ash: ACK frames : RX=18, TX=3632
[2024-10-24 16:10:17] info: zh:ember:uart:ash: NAK frames : RX=0, TX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: nRdy frames : RX=0, TX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: CRC errors : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Comm errors : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Length < minimum: RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Length > maximum: RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Bad controls : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Bad lengths : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Bad ACK numbers : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Out of buffers : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Retry dupes : RX=35
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Out of sequence : RX=0
[2024-10-24 16:10:17] info: zh:ember:uart:ash: ACK timeouts : RX=2
[2024-10-24 16:10:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Innen/EG/Essen/sa_Thermostat_Fussbodenheizung', payload '{"child_lock":"UNLOCK","current_heating_setpoint":20,"deadzone_temperature":null,"heat":"OFF","linkquality":188,"local_temperature":23.5,"local_temperature_calibration":-3,"max_temperature":45,"max_temperature_limit":null,"min_temperature_limit":1,"preset":"hold","preset_mode":"hold","program":{"saturday_p1_hour":6,"saturday_p1_minute":0,"saturday_p1_temperature":24,"saturday_p2_hour":12,"saturday_p2_minute":0,"saturday_p2_temperature":23,"saturday_p3_hour":14,"saturday_p3_minute":30,"saturday_p3_temperature":22,"saturday_p4_hour":17,"saturday_p4_minute":30,"saturday_p4_temperature":21,"sunday_p1_hour":6,"sunday_p1_minute":0,"sunday_p1_temperature":19,"sunday_p2_hour":12,"sunday_p2_minute":30,"sunday_p2_temperature":20,"sunday_p3_hour":14,"sunday_p3_minute":30,"sunday_p3_temperature":21,"sunday_p4_hour":18,"sunday_p4_minute":30,"sunday_p4_temperature":20,"weekdays_p1_hour":6,"weekdays_p1_minute":0,"weekdays_p1_temperature":20,"weekdays_p2_hour":11,"weekdays_p2_minute":30,"weekdays_p2_temperature":21,"weekdays_p3_hour":13,"weekdays_p3_minute":30,"weekdays_p3_temperature":22,"weekdays_p4_hour":17,"weekdays_p4_minute":30,"weekdays_p4_temperature":23},"running_state":"idle","sensor":"AL","system_mode":"cool"}'
[2024-10-24 16:10:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/Innen/OG/BadEltern/sa_Thermostat_Fussbodenheizung', payload '{"child_lock":"UNLOCK","current_heating_setpoint":22,"deadzone_temperature":null,"heat":"OFF","linkquality":68,"local_temperature":22,"local_temperature_calibration":-3,"max_temperature":45,"max_temperature_limit":null,"min_temperature_limit":1,"preset":"hold","preset_mode":"hold","program":{"saturday_p1_hour":6,"saturday_p1_minute":0,"saturday_p1_temperature":24,"saturday_p2_hour":12,"saturday_p2_minute":0,"saturday_p2_temperature":23,"saturday_p3_hour":14,"saturday_p3_minute":30,"saturday_p3_temperature":22,"saturday_p4_hour":17,"saturday_p4_minute":30,"saturday_p4_temperature":21,"sunday_p1_hour":6,"sunday_p1_minute":0,"sunday_p1_temperature":19,"sunday_p2_hour":12,"sunday_p2_minute":30,"sunday_p2_temperature":20,"sunday_p3_hour":14,"sunday_p3_minute":30,"sunday_p3_temperature":21,"sunday_p4_hour":18,"sunday_p4_minute":30,"sunday_p4_temperature":20,"weekdays_p1_hour":6,"weekdays_p1_minute":0,"weekdays_p1_temperature":20,"weekdays_p2_hour":11,"weekdays_p2_minute":30,"weekdays_p2_temperature":21,"weekdays_p3_hour":13,"weekdays_p3_minute":30,"weekdays_p3_temperature":22,"weekdays_p4_hour":17,"weekdays_p4_minute":30,"weekdays_p4_temperature":23},"running_state":"idle","sensor":"AL","system_mode":"off"}'
[2024-10-24 16:10:17] info: zh:ember:uart:ash: Port closed.
[2024-10-24 16:10:17] info: zh:ember:uart:ash: ======== ASH stopped ========
[2024-10-24 16:10:17] info: zh:ember:ezsp: ======== EZSP stopped ========
[2024-10-24 16:10:17] info: zh:ember: ======== Ember Adapter Stopped ========
[2024-10-24 16:10:17] error: z2m: Adapter disconnected, stopping
[2024-10-24 16:10:17] info: z2m:mqtt: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload '{"state":"offline"}'
[2024-10-24 16:10:17] info: z2m: Disconnecting from MQTT server
[2024-10-24 16:10:17] info: z2m: Stopping zigbee-herdsman...
[2024-10-24 16:10:17] info: z2m: Stopped zigbee-herdsman
[2024-10-24 16:10:17] info: z2m: Stopped Zigbee2MQTT
@jan0o0sch Can you provide the full debug logs (most importantly the few minutes before the error)?
@Nerivec Here's a log from a few days ago where I started z2m, allowed join, and it then crashed when trying to pair with an IKEA Styrbar remote that is right next to the coordinator log.log
I have logs from a couple of situations, where this has happened (like updating and pairing with other devices). Let me know if you'd like me to send those or you need anything else I can provide
@jan0o0sch Can you provide the full
debuglogs (most importantly the few minutes before the error)?
I am sorry I set the log level to "debug" and restarted several times -- also the whole system, but it just won't show the debug entries. As it seems, "info" is the level Z2M prefers. What am I doing wrong?
advanced:
log_level: debug
adapter_concurrent: 1
adapter_delay: 200