Zigbee2mqtt crash frequently

Hi,
I have my Zigbee2mqtt who crash frequently and Watchdog won’t succeed to reboot it.
Zigbee2Mqtt log :

2024-04-19 08:45:32.112 INFO (SyncWorker_1) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-04-19 08:45:35.953 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.36.1-1
2024-04-19 08:46:57.329 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Zigbee2MQTT is failed, restarting...
2024-04-19 08:46:57.382 INFO (SyncWorker_3) [supervisor.docker.manager] Cleaning addon_45df7312_zigbee2mqtt application
2024-04-19 08:47:08.992 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-aarch64 with version 1.36.1-1
2024-04-19 08:48:22.828 ERROR (MainThread) [asyncio] Task exception was never retrieved
future: <Task finished name='Task-39837' coro=<Addon.watchdog_container() done, defined at /usr/src/supervisor/supervisor/addons/addon.py:1418> exception=AddonsJobError('Rate limit exceeded, more than 10 calls in 0:30:00')>
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/addons/addon.py", line 1432, in watchdog_container
    await self._restart_after_problem(event.state)
  File "/usr/src/supervisor/supervisor/jobs/decorator.py", line 290, in wrapper
    raise on_condition(
supervisor.exceptions.AddonsJobError: Rate limit exceeded, more than 10 calls in 0:30:00

My conf:

Core 2024.4.3
Supervisor 2024.04.0
Operating System 12.2
Frontend 20240404.2
Raspberry Pi 3
rpi3-64

My devices


My addons

My HAS integrations

Thanks.

Most important thing you forgot: the Zigbee2MQTT logs.

Zigbee2mqtt log:

info 2024-04-19 13:09:23: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-04-19.13-09-21’ filename: log.txt
info 2024-04-19 13:09:26: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
info 2024-04-19 13:09:26: Starting zigbee-herdsman (0.40.3)
info 2024-04-19 13:10:07: zigbee-herdsman started (resumed)
info 2024-04-19 13:10:07: Coordinator firmware version: ‘{“meta”:{“maintrel”:"3 ",“majorrel”:“6”,“minorrel”:“10”,“product”:8,“revision”:“6.10.3.0 build 297”},“type”:“EZSP v8”}’
info 2024-04-19 13:10:07: Currently 6 devices are joined:
info 2024-04-19 13:10:07: Température salon (0x54ef4410007def8b): VOCKQJK11LM - Aqara TVOC air quality monitor (EndDevice)
info 2024-04-19 13:10:07: Détecteur ouverture porte baie vitrée (0xa4c1387421845932): TS0203 - TuYa Door sensor (EndDevice)
info 2024-04-19 13:10:07: Radiateur Masterbedroom (0x90395efffe2763c2): SIN-4-FP-21 - NodOn Pilot wire heating module (Router)
info 2024-04-19 13:10:07: Radiateur chambre invité (0x90395efffe4b1c01): SIN-4-FP-21 - NodOn Pilot wire heating module (Router)
info 2024-04-19 13:10:07: Radiateur bureau (0x90395efffe4b1be9): SIN-4-FP-21 - NodOn Pilot wire heating module (Router)
info 2024-04-19 13:10:07: Radiateur salon (0xf4b3b1fffedd9a3c): SIN-4-FP-21 - NodOn Pilot wire heating module (Router)
info 2024-04-19 13:10:07: Zigbee: disabling joining new devices.
error 2024-04-19 13:11:48: Adapter disconnected, stopping
error 2024-04-19 13:11:50: Not connected to MQTT server!
error 2024-04-19 13:11:50: Cannot send message: topic: ‘zigbee2mqtt/bridge/state’, payload: '{“state”:“offline”}
info 2024-04-19 13:11:50: Disconnecting from MQTT server
error 2024-04-19 13:11:50: EventBus error ‘Controller/adapterDisconnected’: Cannot read properties of undefined (reading ‘end’)

Zigbee started.

This is your problem.

Mqtt is still up and accessible.
Z2M connect wel to mqtt and communicate also.
But sometimes, Z2M crash.

info 2024-04-19 13:56:17: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-04-19.13-56-16’ filename: log.txt
info 2024-04-19 13:56:19: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
info 2024-04-19 13:56:19: Starting zigbee-herdsman (0.40.3)
error 2024-04-19 13:56:54: Error while starting zigbee-herdsman
error 2024-04-19 13:56:55: Failed to start zigbee
error 2024-04-19 13:56:55: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
error 2024-04-19 13:56:55: Exiting…
error 2024-04-19 13:57:05: Error: Failure send getKey:{“type”:“Buffer”,“data”:[31,0,1,106,0,3]}
at /app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:664:23
at Queue.execute (/app/node_modules/zigbee-herdsman/src/utils/queue.ts:35:20)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:271:27)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:109:27)
at start (/app/index.js:107:5)

Or after a clean restart of HA

Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/binary_sensor/1221051039810110150109113116116_0xe0798dfffec6decb/restart_required/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“device_class”:“problem”,“enabled_by_default”:false,“entity_category”:“diagnostic”,“name”:“Restart required”,“object_id”:“zigbee2mqtt_bridge_restart_required”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“payload_off”:false,“payload_on”:true,“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_restart_required_zigbee2mqtt”,“value_template”:“{{ value_json.restart_required }}”}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/button/1221051039810110150109113116116_0xe0798dfffec6decb/restart/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“command_topic”:“zigbee2mqtt/bridge/request/restart”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“device_class”:“restart”,“name”:“Restart”,“object_id”:“zigbee2mqtt_bridge_restart”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“payload_press”:“”,“unique_id”:“bridge_0xe0798dfffec6decb_restart_zigbee2mqtt”}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/select/1221051039810110150109113116116_0xe0798dfffec6decb/log_level/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“command_template”:“{"options": {"advanced": {"log_level": "{{ value }}" } } }”,“command_topic”:“zigbee2mqtt/bridge/request/options”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“entity_category”:“config”,“name”:“Log level”,“object_id”:“zigbee2mqtt_bridge_log_level”,“options”:[“info”,“warn”,“error”,“debug”],“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_log_level_zigbee2mqtt”,“value_template”:“{{ value_json.log_level | lower }}”}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/sensor/1221051039810110150109113116116_0xe0798dfffec6decb/version/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“entity_category”:“diagnostic”,“icon”:“mdi:zigbee”,“name”:“Version”,“object_id”:“zigbee2mqtt_bridge_version”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_version_zigbee2mqtt”,“value_template”:“{{ value_json.version }}”}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/sensor/1221051039810110150109113116116_0xe0798dfffec6decb/coordinator_version/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“enabled_by_default”:false,“entity_category”:“diagnostic”,“icon”:“mdi:chip”,“name”:“Coordinator version”,“object_id”:“zigbee2mqtt_bridge_coordinator_version”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_coordinator_version_zigbee2mqtt”,“value_template”:“{{ value_json.coordinator.meta.revision }}”}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/sensor/1221051039810110150109113116116_0xe0798dfffec6decb/network_map/config’, payload ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“enabled_by_default”:false,“entity_category”:“diagnostic”,“json_attributes_template”:“{{ value_json.data.value | tojson }}”,“json_attributes_topic”:“zigbee2mqtt/bridge/response/networkmap”,“name”:“Network map”,“object_id”:“zigbee2mqtt_bridge_network_map”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/response/networkmap”,“unique_id”:“bridge_0xe0798dfffec6decb_network_map_zigbee2mqtt”,“value_template”:"{{ now().strftime(’%Y-%m-%d %H:%M:%S’) }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/sensor/1221051039810110150109113116116_0xe0798dfffec6decb/permit_join_timeout/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“availability_mode”:“all”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“device_class”:“duration”,“entity_category”:“diagnostic”,“name”:“Permit join timeout”,“object_id”:“zigbee2mqtt_bridge_permit_join_timeout”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_permit_join_timeout_zigbee2mqtt”,“unit_of_measurement”:“s”,“value_template”:”{{ iif(value_json.permit_join_timeout is defined, value_json.permit_join_timeout, None) }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:20: MQTT publish: topic ‘homeassistant/switch/1221051039810110150109113116116_0xe0798dfffec6decb/permit_join/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“availability_mode”:“all”,“command_topic”:“zigbee2mqtt/bridge/request/permit_join”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“icon”:“mdi:human-greeting-proximity”,“name”:“Permit join”,“object_id”:“zigbee2mqtt_bridge_permit_join”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“payload_off”:“false”,“payload_on”:“true”,“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_permit_join_zigbee2mqtt”,“value_template”:”{{ value_json.permit_join | lower }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/device_temperature/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“device_class”:“temperature”,“enabled_by_default”:true,“entity_category”:“diagnostic”,“object_id”:“température_salon_device_temperature”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_class”:“measurement”,“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_device_temperature_zigbee2mqtt”,“unit_of_measurement”:“°C”,“value_template”:”{{ value_json.device_temperature }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/battery/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“device_class”:“battery”,“enabled_by_default”:true,“entity_category”:“diagnostic”,“object_id”:“température_salon_battery”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_class”:“measurement”,“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_battery_zigbee2mqtt”,“unit_of_measurement”:”%“,“value_template”:”{{ value_json.battery }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/voltage/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“device_class”:“voltage”,“enabled_by_default”:false,“entity_category”:“diagnostic”,“object_id”:“température_salon_voltage”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_class”:“measurement”,“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_voltage_zigbee2mqtt”,“unit_of_measurement”:“mV”,“value_template”:”{{ value_json.voltage }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/air_quality/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“enabled_by_default”:true,“name”:“Air quality”,“object_id”:“température_salon_air_quality”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_air_quality_zigbee2mqtt”,“value_template”:”{{ value_json.air_quality }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/voc/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}“}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“enabled_by_default”:true,“name”:“Voc”,“object_id”:“température_salon_voc”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_class”:“measurement”,“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_voc_zigbee2mqtt”,“unit_of_measurement”:“ppb”,“value_template”:”{{ value_json.voc }}“}’
Zigbee2MQTT:info 2024-04-19 15:24:21: MQTT publish: topic ‘homeassistant/sensor/0x54ef4410007def8b/temperature/config’, payload '{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:”{{ value_json.state }}"}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“device_class”:“temperature”,“enabled_by_default”:true,“object_id”:“température_salon_temperature”,“origin”

Or

info 2024-04-19 15:15:08: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-04-19.15-15-08’ filename: log.txt
info 2024-04-19 15:15:09: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
info 2024-04-19 15:15:09: Starting zigbee-herdsman (0.40.3)
error 2024-04-19 15:17:44: Error while starting zigbee-herdsman
error 2024-04-19 15:17:48: Failed to start zigbee
error 2024-04-19 15:17:48: Check Zigbee2MQTT fails to start | Zigbee2MQTT for possible solutions
error 2024-04-19 15:17:48: Exiting…
error 2024-04-19 15:17:49: Error: Connection not initialized
at Ezsp.execCommand (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:648:19)
at Ezsp.setValue (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/ezsp.ts:566:32)
at Driver.startup (/app/node_modules/zigbee-herdsman/src/adapter/ezsp/driver/driver.ts:185:25)
at Controller.start (/app/node_modules/zigbee-herdsman/src/controller/controller.ts:132:29)
at Zigbee.start (/app/lib/zigbee.ts:62:27)
at Controller.start (/app/lib/controller.ts:109:27)
at start (/app/index.js:107:5)

And after that, HA don’t respond for few minutes

What dongle do you have ? And what firmware version does your dongle have ?

The dongle is : SONOFF ZigBee 3.0 USB Dongle Plus, EFR32MG21 Coordinator, Universelle USB ZigBee Hub, Passerelle ZigBee pour Home Assistant

You can try to update to a 7.3 or even a 7.4 firmware.

7.3 or 7.4 for the dongle ? Where do you see the installed version?
Do you know how to update ?

A new Z2M crash

Zigbee2MQTT:debug 2024-04-19 19:46:24: Received MQTT message on ‘homeassistant/sensor/0x54ef4410007def8b/update_state/config’ with data ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“device”:{“identifiers”:[“zigbee2mqtt_0x54ef4410007def8b”],“manufacturer”:“Aqara”,“model”:“TVOC air quality monitor (VOCKQJK11LM)”,“name”:“Température salon”,“sw_version”:“2020\u0000www.”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“enabled_by_default”:false,“entity_category”:“diagnostic”,“icon”:“mdi:update”,“name”:“Update state”,“object_id”:“température_salon_update_state”,“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/Température salon”,“unique_id”:“0x54ef4410007def8b_update_state_zigbee2mqtt”,“value_template”:“{{ value_json[‘update’][‘state’] }}”}’
Zigbee2MQTT:debug 2024-04-19 19:46:24: Received MQTT message on ‘homeassistant/select/1221051039810110150109113116116_0xe0798dfffec6decb/log_level/config’ with data ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“availability_mode”:“all”,“command_template”:“{"options": {"advanced": {"log_level": "{{ value }}" } } }”,“command_topic”:“zigbee2mqtt/bridge/request/options”,“device”:{“hw_version”:“EZSP v8 6.10.3.0 build 297”,“identifiers”:[“zigbee2mqtt_bridge_0xe0798dfffec6decb”],“manufacturer”:“Zigbee2MQTT”,“model”:“Bridge”,“name”:“Zigbee2MQTT Bridge”,“sw_version”:“1.36.1”},“entity_category”:“config”,“name”:“Log level”,“object_id”:“zigbee2mqtt_bridge_log_level”,“options”:[“info”,“warn”,“error”,“debug”],“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/bridge/info”,“unique_id”:“bridge_0xe0798dfffec6decb_log_level_zigbee2mqtt”,“value_template”:“{{ value_json.log_level | lower }}”}’
Zigbee2MQTT:debug 2024-04-19 19:46:24: Received MQTT message on ‘homeassistant/select/0x90395efffe2763c2/pilot_wire_mode/config’ with data ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“command_topic”:“zigbee2mqtt/Radiateur Masterbedroom/set/pilot_wire_mode”,“device”:{“identifiers”:[“zigbee2mqtt_0x90395efffe2763c2”],“manufacturer”:“NodOn”,“model”:“Pilot wire heating module (SIN-4-FP-21)”,“name”:“Radiateur Masterbedroom”,“sw_version”:“3.0.0-1.4.5”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“enabled_by_default”:true,“name”:“Pilot wire mode”,“object_id”:“radiateur_masterbedroom_pilot_wire_mode”,“options”:[“comfort”,“eco”,“frost_protection”,“off”,“comfort_-1”,“comfort_-2”],“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/Radiateur Masterbedroom”,“unique_id”:“0x90395efffe2763c2_pilot_wire_mode_zigbee2mqtt”,“value_template”:“{{ value_json.pilot_wire_mode }}”}’
Zigbee2MQTT:debug 2024-04-19 19:46:24: Received MQTT message on ‘homeassistant/select/0x90395efffe4b1c01/pilot_wire_mode/config’ with data ‘{“availability”:[{“topic”:“zigbee2mqtt/bridge/state”,“value_template”:“{{ value_json.state }}”}],“command_topic”:“zigbee2mqtt/Radiateur chambre invité/set/pilot_wire_mode”,“device”:{“identifiers”:[“zigbee2mqtt_0x90395efffe4b1c01”],“manufacturer”:“NodOn”,“model”:“Pilot wire heating module (SIN-4-FP-21)”,“name”:“Radiateur chambre invité”,“sw_version”:“3.0.0-1.4.5”,“via_device”:“zigbee2mqtt_bridge_0xe0798dfffec6decb”},“enabled_by_default”:true,“name”:“Pilot wire mode”,“object_id”:“radiateur_chambre_invité_pilot_wire_mode”,“options”:[“comfort”,“eco”,“frost_protection”,“off”,“comfort_-1”,“comfort_-2”],“origin”:{“name”:“Zigbee2MQTT”,“sw”:“1.36.1”,“url”:“https://www.zigbee2mqtt.io”},“state_topic”:“zigbee2mqtt/Radiateur chambre invité”,“unique_id”:“0x90395efffe4b1c01_pilot_wire_mode_zigbee2mqtt”,“value_template”:“{{ value_json.pilot_wire_mode }}”}’
Zigbee2MQTT:debug 2024-04-19 19:46:24: Received MQTT message on

Did you update the firmware?

I’m searching how to.

Here, this should give you all the reasons why the crashes can occur, including a link on how to update firmware on your specific device.

2 Likes

SONOFF Dongle-E, ZB-GW04, SMLIGHT SLZB07

7.4 firmware

I updated the firmware, reboot HA but still Z2B crash.

2024-04-20T09:45:46.277Z zigbee-herdsman:adapter:ezsp:debg processMessage: {“messageType”:0,“apsFrame”:{“profileId”:260,“sequence”:5,“clusterId”:64512,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:320},“lqi”:224,“rssi”:-44,“sender”:4401,“bindingIndex”:255,“addressIndex”:255,“message”:{“type”:“Buffer”,“data”:[12,139,18,33,10,0,0,32,2]}}
2024-04-20T09:45:46.635Z zigbee-herdsman:controller:log Received ‘zcl’ data ‘{“frame”:{“Header”:{“frameControl”:{“frameType”:0,“manufacturerSpecific”:true,“direction”:1,“disableDefaultResponse”:false,“reservedBits”:0},“transactionSequenceNumber”:33,“manufacturerCode”:4747,“commandIdentifier”:10},“Payload”:[{“attrId”:0,“dataType”:32,“attrData”:2}],“Command”:{“ID”:10,“name”:“report”,“parameters”:[{“name”:“attrId”,“type”:33},{“name”:“dataType”,“type”:32},{“name”:“attrData”,“type”:1000}]}},“address”:4401,“endpoint”:1,“linkquality”:224,“groupID”:0,“wasBroadcast”:false,“destinationEndpoint”:1}’
2024-04-20T09:45:46.774Z zigbee-herdsman:controller:endpoint ZCL command 0xf4b3b1fffedd9a3c/1 manuSpecificUbisysDeviceSetup.defaultRsp({“cmdId”:10,“statusCode”:0}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:1,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:33,“writeUndiv”:false})
2024-04-20T09:45:46.805Z zigbee-herdsman:adapter:ezsp:uart ← DATA (2,6,1): 2e7fb1a90d2a24a3650e97db55e421bd7c9a278dd47e
2024-04-20T09:45:46.805Z zigbee-herdsman:adapter:ezsp:uart Unexpected DATA packet sequence 2 | 5: packet replay
2024-04-20T09:45:46.805Z zigbee-herdsman:adapter:ezsp:uart → ACK (3)
2024-04-20T09:45:46.806Z zigbee-herdsman:adapter:ezsp:uart → [83401b7e]
2024-04-20T09:45:46.806Z zigbee-herdsman:adapter:ezsp:uart ← ACK (6): 2e7fb1a90d2a24a3650e97db55e421bd7c9a278dd47e
2024-04-20T09:45:46.807Z zigbee-herdsman:adapter:ezsp:uart Unexpected packet sequence 6 | 7
2024-04-20T09:45:46.807Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (3)
2024-04-20T09:45:46.808Z zigbee-herdsman:adapter:ezsp:uart ← DATA (3,6,1): 3e7fb1a9112a15b658974a24ab1593499c4ac77fdcdf9874f5ce4383fc7e1ea7ebcfe2437e
2024-04-20T09:45:46.808Z zigbee-herdsman:adapter:ezsp:uart → ACK (4)
2024-04-20T09:45:46.809Z zigbee-herdsman:adapter:ezsp:uart → [8430fc7e]
2024-04-20T09:45:46.809Z zigbee-herdsman:adapter:ezsp:uart ← ACK (6): 3e7fb1a9112a15b658974a24ab1593499c4ac77fdcdf9874f5ce4383fc7e1ea7ebcfe2437e
2024-04-20T09:45:46.809Z zigbee-herdsman:adapter:ezsp:uart Unexpected packet sequence 6 | 7
2024-04-20T09:45:46.810Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (4)
2024-04-20T09:45:46.811Z zigbee-herdsman:adapter:ezsp:uart ← DATA (4,6,1): 4e7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc52f27e
2024-04-20T09:45:46.811Z zigbee-herdsman:adapter:ezsp:uart → ACK (5)
2024-04-20T09:45:46.812Z zigbee-herdsman:adapter:ezsp:uart → [8520dd7e]
2024-04-20T09:45:46.812Z zigbee-herdsman:adapter:ezsp:uart ← ACK (6): 4e7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc52f27e
2024-04-20T09:45:46.813Z zigbee-herdsman:adapter:ezsp:uart Unexpected packet sequence 6 | 7
2024-04-20T09:45:46.813Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (5)
Zigbee2MQTT:debug 2024-04-20 11:45:46: Received Zigbee message from ‘Radiateur salon’, type ‘attributeReport’, cluster ‘manuSpecificNodOnPilotWire’, data ‘{“mode”:2}’ from endpoint 1 with groupID 0
Zigbee2MQTT:info 2024-04-20 11:45:50: MQTT publish: topic ‘zigbee2mqtt/Radiateur salon’, payload ‘{“energy”:314.73,“linkquality”:224,“pilot_wire_mode”:“eco”,“power”:1853,“state”:“ON”,“update”:{“installed_version”:768,“latest_version”:769,“state”:“available”},“update_available”:null}’
2024-04-20T09:45:52.786Z zigbee-herdsman:adapter:ezsp:ezsp Time to watchdog … 0
2024-04-20T09:45:53.159Z zigbee-herdsman:adapter:ezsp:ezsp ==> nop: null
2024-04-20T09:45:54.756Z zigbee-herdsman:adapter:ezsp:uart → Error: Error: {“sequence”:7} after 4000ms
2024-04-20T09:45:54.882Z zigbee-herdsman:adapter:ezsp:uart -!- break waiting (7)
2024-04-20T09:45:54.954Z zigbee-herdsman:adapter:ezsp:uart Can’t send DATA frame (6,4,0): 3e00013400003111040103000101000100000a0b0518200b0a00
2024-04-20T09:45:55.429Z zigbee-herdsman:adapter:ezsp:uart ← [577ca1a9602a151cfa367e677cb1a96b2a158348904b26aa5493499d4e2705e6ce67ee2a7e777cb1a90d2a6e99588801db550babd9609527c7827e077cb1a97d312a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7d5e1ea7ebcfe8687e4f7fb1a97d312a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e5f7ca1a9602a151ce4ec7e6f7cb1a96b2a158348904b26aa5493499d4e2705e6ce67f67d317e7f7cb1a90d2a6e99588801db550babd960952757bc7e0f7cb1a97d312a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7d5e1ea7ebcf49c47e]
2024-04-20T09:45:55.481Z zigbee-herdsman:adapter:ezsp:uart ← DATA (5,7,0): 577ca1a9602a151cfa367e
2024-04-20T09:45:55.481Z zigbee-herdsman:adapter:ezsp:uart → ACK (6)
2024-04-20T09:45:55.482Z zigbee-herdsman:adapter:ezsp:uart → [8610be7e]
2024-04-20T09:45:55.482Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 577ca1a9602a151cfa367e
2024-04-20T09:45:55.614Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 3e8001340000ae
2024-04-20T09:45:55.763Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x34: {“cls”:“sendUnicast”,“id”:52,“isRequest”:false,“status”:0,“sequence”:174}
2024-04-20T09:45:55.781Z zigbee-herdsman:adapter:ezsp:uart ← DATA (6,7,0): 677cb1a96b2a158348904b26aa5493499d4e2705e6ce67ee2a7e
2024-04-20T09:45:55.782Z zigbee-herdsman:adapter:ezsp:uart → ACK (7)
2024-04-20T09:45:55.782Z zigbee-herdsman:adapter:ezsp:uart → [87009f7e]
2024-04-20T09:45:55.782Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 677cb1a96b2a158348904b26aa5493499d4e2705e6ce67ee2a7e
2024-04-20T09:45:55.783Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 3e90013f0000311104010300010100010000ae0b0000
2024-04-20T09:45:55.819Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x3f: {“cls”:“messageSentHandler”,“id”:63,“isRequest”:false,“type”:0,“indexOrDestination”:4401,“apsFrame”:{“profileId”:260,“sequence”:174,“clusterId”:3,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:256},“messageTag”:11,“status”:0,“message”:{“type”:“Buffer”,“data”:}}
2024-04-20T09:45:55.833Z zigbee-herdsman:adapter:ezsp:uart ← DATA (7,7,0): 777cb1a90d2a6e99588801db550babd9609527c7827e
2024-04-20T09:45:55.833Z zigbee-herdsman:adapter:ezsp:uart → ACK (0)
2024-04-20T09:45:55.891Z zigbee-herdsman:adapter:ezsp:uart → [8070787e]
2024-04-20T09:45:56.284Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 777cb1a90d2a6e99588801db550babd9609527c7827e
2024-04-20T09:45:56.284Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 3e900159007b2b011c4bfeff5e3990fcdb00
2024-04-20T09:45:56.448Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x59: {“cls”:“incomingRouteRecordHandler”,“id”:89,“isRequest”:false,“source”:11131,“longId”:{“type”:“Buffer”,“data”:[144,57,94,255,254,75,28,1]},“lastHopLqi”:252,“lastHopRssi”:-37,“relay”:{“type”:“Buffer”,“data”:}}
2024-04-20T09:45:56.502Z zigbee-herdsman:adapter:ezsp:driv handleRouteRecord: nwk=11131, ieee=�9^��K, lqi=252, rssi=-37, relays=
2024-04-20T09:45:56.602Z zigbee-herdsman:adapter:ezsp:uart ← DATA (0,7,0): 077cb1a9112a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7e1ea7ebcfe8687e
2024-04-20T09:45:56.603Z zigbee-herdsman:adapter:ezsp:uart → ACK (1)
2024-04-20T09:45:56.603Z zigbee-herdsman:adapter:ezsp:uart → [8160597e]
2024-04-20T09:45:56.604Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 077cb1a9112a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7e1ea7ebcfe8687e
2024-04-20T09:45:56.604Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 3e90014500000401030001014001000061fcdb7b2bffff0808340a000021000002
2024-04-20T09:45:56.606Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x45: {“cls”:“incomingMessageHandler”,“id”:69,“isRequest”:false,“type”:0,“apsFrame”:{“profileId”:260,“sequence”:97,“clusterId”:3,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:320},“lastHopLqi”:252,“lastHopRssi”:-37,“sender”:11131,“bindingIndex”:255,“addressIndex”:255,“message”:{“type”:“Buffer”,“data”:[8,52,10,0,0,33,0,0]}}
2024-04-20T09:45:56.639Z zigbee-herdsman:adapter:ezsp:debg processMessage: {“messageType”:0,“apsFrame”:{“profileId”:260,“sequence”:97,“clusterId”:3,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:320},“lqi”:252,“rssi”:-37,“sender”:11131,“bindingIndex”:255,“addressIndex”:255,“message”:{“type”:“Buffer”,“data”:[8,52,10,0,0,33,0,0]}}
2024-04-20T09:45:56.953Z zigbee-herdsman:controller:log Received ‘zcl’ data ‘{“frame”:{“Header”:{“frameControl”:{“frameType”:0,“manufacturerSpecific”:false,“direction”:1,“disableDefaultResponse”:false,“reservedBits”:0},“transactionSequenceNumber”:52,“manufacturerCode”:null,“commandIdentifier”:10},“Payload”:[{“attrId”:0,“dataType”:33,“attrData”:0}],“Command”:{“ID”:10,“name”:“report”,“parameters”:[{“name”:“attrId”,“type”:33},{“name”:“dataType”,“type”:32},{“name”:“attrData”,“type”:1000}]}},“address”:11131,“endpoint”:1,“linkquality”:252,“groupID”:0,“wasBroadcast”:false,“destinationEndpoint”:1}’
2024-04-20T09:45:57.179Z zigbee-herdsman:controller:endpoint ZCL command 0x90395efffe4b1c01/1 genIdentify.defaultRsp({“cmdId”:10,“statusCode”:0}, {“timeout”:10000,“disableResponse”:false,“disableRecovery”:false,“disableDefaultResponse”:true,“direction”:1,“srcEndpoint”:null,“reservedBits”:0,“manufacturerCode”:null,“transactionSequenceNumber”:52,“writeUndiv”:false})
2024-04-20T09:45:57.349Z zigbee-herdsman:adapter:ezsp:debg sendZclFrameToEndpointInternal 0x90395efffe4b1c01:11131/1 (0,0,3), timeout=10000
2024-04-20T09:45:57.482Z zigbee-herdsman:adapter:ezsp:uart ← DATA (4,7,1): 4f7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e
2024-04-20T09:45:57.482Z zigbee-herdsman:adapter:ezsp:uart Unexpected DATA packet sequence 4 | 1: packet replay
2024-04-20T09:45:57.482Z zigbee-herdsman:adapter:ezsp:uart → ACK (5)
2024-04-20T09:45:57.483Z zigbee-herdsman:adapter:ezsp:uart → [8520dd7e]
2024-04-20T09:45:57.484Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 4f7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e
2024-04-20T09:45:57.484Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (5)
2024-04-20T09:45:57.485Z zigbee-herdsman:adapter:ezsp:uart ← DATA (5,7,1): 5f7ca1a9602a151ce4ec7e
2024-04-20T09:45:57.485Z zigbee-herdsman:adapter:ezsp:uart → ACK (6)
2024-04-20T09:45:57.485Z zigbee-herdsman:adapter:ezsp:uart → [8610be7e]
2024-04-20T09:45:57.486Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 5f7ca1a9602a151ce4ec7e
2024-04-20T09:45:57.486Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (6)
2024-04-20T09:45:57.487Z zigbee-herdsman:adapter:ezsp:uart ← DATA (6,7,1): 6f7cb1a96b2a158348904b26aa5493499d4e2705e6ce67f6117e
2024-04-20T09:45:57.487Z zigbee-herdsman:adapter:ezsp:uart → ACK (7)
2024-04-20T09:45:57.488Z zigbee-herdsman:adapter:ezsp:uart → [87009f7e]
2024-04-20T09:45:57.488Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 6f7cb1a96b2a158348904b26aa5493499d4e2705e6ce67f6117e
2024-04-20T09:45:57.489Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (7)
2024-04-20T09:45:57.489Z zigbee-herdsman:adapter:ezsp:uart ← DATA (7,7,1): 7f7cb1a90d2a6e99588801db550babd960952757bc7e
2024-04-20T09:45:57.490Z zigbee-herdsman:adapter:ezsp:uart → ACK (0)
2024-04-20T09:45:57.490Z zigbee-herdsman:adapter:ezsp:uart → [8070787e]
2024-04-20T09:45:57.491Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 7f7cb1a90d2a6e99588801db550babd960952757bc7e
2024-04-20T09:45:57.491Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (0)
2024-04-20T09:45:57.492Z zigbee-herdsman:adapter:ezsp:uart ← DATA (0,7,1): 0f7cb1a9112a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7e1ea7ebcf49c47e
2024-04-20T09:45:57.492Z zigbee-herdsman:adapter:ezsp:uart → ACK (1)
2024-04-20T09:45:57.493Z zigbee-herdsman:adapter:ezsp:uart → [8160597e]
2024-04-20T09:45:57.493Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 0f7cb1a9112a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7e1ea7ebcf49c47e
2024-04-20T09:45:57.494Z zigbee-herdsman:adapter:ezsp:uart Skipping the packet as repeated (1)
Zigbee2MQTT:debug 2024-04-20 11:45:57: Received Zigbee message from ‘Radiateur chambre invité’, type ‘attributeReport’, cluster ‘genIdentify’, data ‘{“identifyTime”:0}’ from endpoint 1 with groupID 0
Zigbee2MQTT:debug 2024-04-20 11:45:57: No converter available for ‘SIN-4-FP-21’ with cluster ‘genIdentify’ and type ‘attributeReport’ and data ‘{“identifyTime”:0}’
2024-04-20T09:45:57.807Z zigbee-herdsman:adapter:ezsp:ezsp ==> sendUnicast: {“type”:0,“indexOrDestination”:11131,“apsFrame”:{“profileId”:260,“sequence”:11,“clusterId”:3,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:256},“messageTag”:12,“message”:{“type”:“Buffer”,“data”:[24,52,11,10,0]}}
2024-04-20T09:45:59.334Z zigbee-herdsman:adapter:ezsp:uart ->> DATA (6,4,1): 3e00013400003111040103000101000100000a0b0518200b0a00
2024-04-20T09:45:59.356Z zigbee-herdsman:adapter:ezsp:uart → [6c7c21a9602a158348904b26aa5493499d4e27a1e6cb7fabf6cc63e77a7e]
2024-04-20T09:45:59.356Z zigbee-herdsman:adapter:ezsp:uart -?- rewaiting (7)
2024-04-20T09:45:59.729Z zigbee-herdsman:adapter:ezsp:uart ← [4f7fb1a97d312a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e5f7ca1a9602a151ce4ec7e6f7cb1a96b2a158348904b26aa5493499d4e2705e6ce67f67d317e7f7cb1a90d2a6e99588801db550babd960952757bc7e0f7cb1a97d312a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7d5e1ea7ebcf49c47e4f7fb1a97d312a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e5f7ca1a9602a151ce4ec7e6f7cb1a96b2a158348904b26aa5493499d4e2705e6ce67f67d317e7f7cb1a90d2a6e99588801db550babd960952757bc7e0f7cb1a97d312a15b658974a24ab1593499c2fdb7096e59874f5ce5783fc7d5e1ea7ebcf49c47e177cb1a97d312a15b65894b624ab1593499c2cdb7096e59874f4cae89bca743fa7cbcedc93907e]
2024-04-20T09:45:59.750Z zigbee-herdsman:adapter:ezsp:uart ← DATA (4,7,1): 4f7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e
2024-04-20T09:45:59.781Z zigbee-herdsman:adapter:ezsp:uart Unexpected DATA packet sequence 4 | 1: packet replay
2024-04-20T09:45:59.781Z zigbee-herdsman:adapter:ezsp:uart → ACK (5)
2024-04-20T09:45:59.782Z zigbee-herdsman:adapter:ezsp:uart → [8520dd7e]
2024-04-20T09:45:59.782Z zigbee-herdsman:adapter:ezsp:uart ← ACK (7): 4f7fb1a9112a15b65894b624ab1593499c4bc77fdcdf9874f4cae89bdd743fa7cbcfdc35c77e
2024-04-20T09:45:59.854Z zigbee-herdsman:adapter:ezsp:ezsp <== Frame: 3d9001450000040100fc01014001000005e0d43111ffff090c8b12210a0000200202
2024-04-20T09:46:00.030Z zigbee-herdsman:adapter:ezsp:ezsp <== 0x45: {“cls”:“incomingMessageHandler”,“id”:69,“isRequest”:false,“type”:0,“apsFrame”:{“profileId”:260,“sequence”:5,“clusterId”:64512,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:320},“lastHopLqi”:224,“lastHopRssi”:-44,“sender”:4401,“bindingIndex”:255,“addressIndex”:255,“message”:{“type”:“Buffer”,“data”:[12,139,18,33,10,0,0,32,2]}}
2024-04-20T09:46:00.064Z zigbee-herdsman:adapter:ezsp:debg processMessage: {“messageType”:0,“apsFrame”:{“profileId”:260,“sequence”:5,“clusterId”:64512,“sourceEndpoint”:1,“destinationEndpoint”:1,“groupId”:0,“options”:320},“lqi”:224,“rssi”:-44,“sender”:4401,“bindingIndex”:255,“addressIndex”:255,“message”:{“type”:“Buffer”,“data”:[12,139,18,33,10,0,0,32,2]}}

Maybe I’ll try with another firmware.

Really don’t know the issue, with last firmware


I don’t have the connection with my temperature sensor.

Z2M log

This morning, I’m trying with RCP Multi-PAN firmware.



Change my Z2B conf like :

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:
  server: mqtt://core-mosquitto:1883
  user: mqtt
  password: PWD
serial:
  port: tcp://core-silabs-multiprotocol:9999
  adapter: ezsp
zigbee_herdsman_debug: false

But I can’t start Silicon lab and Z2M
Silicon lab log:

[10:39:18:724020] Info : Secondary APP vUNDEFINED
[10:39:18:724354] Info : Daemon startup was successful. Waiting for client connections
[10:39:20] INFO: Starting zigbeed…
[10:39:21] INFO: Setup OTBR firewall…
[10:39:21:247152] Info : New client connection using library v4.3.1.0
[10:39:21:250787] Info : Opened connection socket for ep#12
[10:39:21:251071] Info : Endpoint socket #12: Client connected. 1 connections
[10:39:22] INFO: Starting otbr-agent…
otbr-agent[318]: [NOTE]-AGENT—: Running 0.3.0
otbr-agent[318]: [NOTE]-AGENT—: Thread version: 1.3.0
otbr-agent[318]: [NOTE]-AGENT—: Thread interface: wpan0
otbr-agent[318]: [NOTE]-AGENT—: Radio URL: spinel+cpc://cpcd_0?iid=2&iid-list=0
otbr-agent[318]: [NOTE]-ILS-----: Infra link selected: enu1u1
otbr-agent[318]: 49d.17:04:07.734 [C] Platform------: mCpcBusSpeed = 115200
[10:39:22:226396] Info : New client connection using library v4.3.1.0
[10:39:22:229689] Info : Endpoint socket #12: Client connected. 2 connections
otbr-agent[318]: 00:00:00.081 [N] RoutingManager: BR ULA prefix: fd74:4196:ed63::/48 (loaded)
otbr-agent[318]: 00:00:00.081 [N] RoutingManager: Local on-link prefix: fdf0:2384:17f1:4f38::/64
otbr-agent[318]: 00:00:00.155 [N] Mle-----------: Role disabled → detached
otbr-agent[318]: 00:00:00.180 [N] Platform------: [netif] Changing interface state to up.
s6-rc: info: service otbr-agent successfully started
s6-rc: info: service otbr-agent-rest-discovery: starting
Listening on port 9999 for connection…
Accepting connection.
[10:39:26] INFO: Successfully sent discovery information to Home Assistant.
s6-rc: info: service otbr-agent-rest-discovery successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
otbr-agent[318]: 00:00:26.124 [N] Mle-----------: RLOC16 f000 → fffe
otbr-agent[318]: 00:00:26.130 [W] Platform------: [netif] Failed to process request#5: Unknown error -95
otbr-agent[318]: 00:00:26.790 [N] Mle-----------: Attach attempt 1, AnyPartition reattaching with Active Dataset
otbr-agent[318]: 00:00:33.295 [N] RouterTable—: Allocate router id 60
otbr-agent[318]: 00:00:33.295 [N] Mle-----------: RLOC16 fffe → f000
otbr-agent[318]: 00:00:33.299 [N] Mle-----------: Role detached → leader
otbr-agent[318]: 00:00:33.301 [N] Mle-----------: Partition ID 0x68e1f0ca
otbr-agent[318]: 00:00:33.412 [W] Platform------: [netif] Failed to process request#6: Unknown error -17
otbr-agent[318]: [NOTE]-BBA-----: BackboneAgent: Backbone Router becomes Primary!
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::acf6:79ff:fedb:9dd2/vethe6be2a6/22
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::8c7e:fcff:feea:2135/veth7258363/24
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::bc08:94ff:fea2:94ae/veth18e474a/26
Accepted connection 7.
Restarting
[10:42:33:577290] Info : Endpoint socket #12: Client disconnected. 1 connections
[10:42:33:678816] Info : Client disconnected
[10:42:35:865422] Info : New client connection using library v4.3.1.0
[10:42:35:880646] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
WARNING in function ‘core_process_rx_s_frame’ in file /usr/src/cpc-daemon/server_core/core/core.c at line #818 : Remote received a packet with an invalid checksum
[10:42:54:460042] WARNING : In function ‘core_process_rx_s_frame’ in file /usr/src/cpc-daemon/server_core/core/core.c at line #818 : Remote received a packet with an invalid checksum
Socket connection has been closed, restarting…
Listening on port 9999 for connection…
Accepting connection.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::349d:11ff:feab:78ba/veth837e0b4/28
Accepted connection 8.
Restarting
[10:44:45:407389] Info : Endpoint socket #12: Client disconnected. 1 connections
[10:44:45:423582] Info : Client disconnected
[10:44:46:890109] Info : New client connection using library v4.3.1.0
[10:44:46:894562] Info : Endpoint socket #12: Client connected. 2 connections
Reusing socket from previous instance.
[10:45:29:980281] Info : Endpoint socket #12: Client disconnected. 1 connections
[10:45:30:136257] Info : Client disconnected
[10:45:31:871081] Info : New client connection using library v4.3.1.0
[10:45:31:874763] Info : Endpoint socket #12: Client connected. 2 connections
Restarting
Reusing socket from previous instance.
[10:45:33:126271] Info : Endpoint socket #12: Client disconnected. 1 connections
[10:45:33:126434] Info : Client disconnected
[10:45:34] INFO: zigbeed ended with exit code 256 (signal 13)…
[10:45:43] INFO: Starting zigbeed…
[10:45:45:308946] Info : New client connection using library v4.3.1.0
[10:45:45:315269] Info : Endpoint socket #12: Client connected. 2 connections
Listening on port 9999 for connection…
Accepting connection.
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30
Default: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to ff02::fb on interface fe80::7cb7:49ff:fe72:8778/veth81590b6/30

Z2M log:

[10:53:11] INFO: Preparing to start…
[10:53:14] INFO: Socat not enabled
[10:53:21] INFO: Starting Zigbee2MQTT…
Zigbee2MQTT:info 2024-04-21 10:54:16: Logging to console and directory: ‘/config/zigbee2mqtt/log/2024-04-21.10-54-07’ filename: log.txt
Zigbee2MQTT:info 2024-04-21 10:54:22: Starting Zigbee2MQTT version 1.36.1 (commit #unknown)
Zigbee2MQTT:info 2024-04-21 10:54:23: Starting zigbee-herdsman (0.40.3)
Assertion failed: Command (setValue(EzspValueId.VALUE_CCA_THRESHOLD, 0)) returned unexpected state: {“cls”:“setValue”,“id”:171,“isRequest”:false,“status”:55}

I’m losing my mind with the issue.

Also, I’m using official power supply RPI and not USB hardware connect to RPI, only the SonOff Dongle.

I’m trying a rollback to official firmware on last update.
Rollback is ok.
But I’ve still crash of Z2B.



Could it be simply running out of memory ? A Pi 3 only has 1 Gb.

1 Like