Dear Community,
I am a little bit confused at the moment.
It´s an old topic: aqara-devices and Zigbee2MQTT in Home Assistant.
With this post I try to collect some information - hopefully to better involve manufacturers like Aqara.
My problem at the moment
I need to expand my zigbee-network in the basement (UG) and don´t know, if I should go with Sonoff as routers or IKEA Tradfri as repeaters.
Background information
In history I was definitly able to pair some aqara-devices directly to a (sonoff-) router by forcing the “Permit Join” only to a specific (sonoff-) router.
NOT the coordinator. And now it won´t work any more - I can do what I want: 30 times tried at minimum; no success. With no change to my network-setup (except software-updates).
If I go with the same aqara-end-device to the (sonoff-) coordinator I need a max. of 3 times and I get every aqara device connected.
Going with the same device in the near of a IKEA Tradfri repeater I can connect the aqara-device, too (if I force the “Permit Join” in Home Assistant).
Questions
What is going on here?
How can I debug that?
About my setup
This is a map-view of my zigbee-network. I have hidden the blue lines from all blue devices directly to the coordinator to get a better view of the connections. So please see a full blue line from every blue circle to the coordinator:
My network is operating rock solid. A device that is paired stays paired.
I never had any kind of drops or outages nor fastly empty batteries.
Except one device: the Aqara TVOC. This device dropped constantly when paired with a sonoff router (in OG). Since pairing it with the sonoff-coordinator it stays connected. Now it “only” throughs me an error when doing an OTA-request. The log to that:
Info 2023-02-04 11:15:03Checking if update available for 'Temp/Hum - EG | Wohnzimmer'
Info 2023-02-04 11:16:03MQTT publish: topic 'zigbee2mqtt/bridge/response/device/ota_update/check', payload '{"data":{"id":"Temp/Hum - EG | Wohnzimmer"},"error":"Failed to check if update available for 'Temp/Hum - EG | Wohnzimmer' (Device didn't respond to OTA request)","status":"error","transaction":"t2hv1-1"}'
Error 2023-02-04 11:16:03Failed to check if update available for 'Temp/Hum - EG | Wohnzimmer' (Device didn't respond to OTA request)
Debug 2023-02-04 11:16:03Error: Device didn't respond to OTA request at requestOTA (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:191:15) at Object.isUpdateAvailable (/app/node_modules/zigbee-herdsman-converters/lib/ota/common.js:246:25) at OTAUpdate.onMQTTMessage (/app/lib/extension/otaUpdate.ts:203:45)
Coordinator (1x) / Router (2x)
Repeater (3x)
Aqara-products
- motion sensor (RTCGQ11LM)
- door & window contact sensor (MCCGQ11LM)
- wireless switch (WXKG11LM)
- TVOC air quality monitor (VOCKQJK11LM)
- temperature, humidity and pressure sensor (WSDCGQ11LM)
- water leak sensor (SJCGQ11LM)
Other products
- Osram Smart+ plug (AB3257001NJ)
- Philips Hue White and Color Ambiance GU10 (929001953101)
- Philips Hue white GU10 (LWG004)
My zigbee-network coexists with a unifi-WLAN (5 accesspoints).
Zigbee at channel 11, unifi-2,4GHz-WLAN at channels 1 and 6.
The zigbee-network has an operating-age of about 2 month without longer interruptions.
So it should be called “settled”.
Debug Information
a. Home Assistant
Home Assistant 2023.2.1
Supervisor 2023.01.1
Operating System 9.5
Frontend 20230202.0 - latest
Zigbee2MQTT version: 1.30.0 commit: unknown
Coordinator type: EZSP v8
Coordinator revision: 6.7.9.0 build 405
Coordinator IEEE Address: 0x040d84fffe4da3da
Frontend version: 0.6.124
b. Zigbee-Coordinator: Sonoff ZBBridge
zigbee-bridge
Program Version 12.2.0.4(zbbridge)
Build Date & Time 2022-11-13T11:56:21
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 67T21:51:39
Flash write Count 36 at 0xFC000
Boot Count 18
Restart Reason Power On
AP1 SSId (RSSI) <SSID> (82%, -59 dBm) 11n
<IP-Settings>
HTTP API Enabled
MQTT Host
MQTT Port 1883
MQTT TLS Disabled
MQTT User DVES_USER
MQTT Client DVES_E17F47
MQTT Topic tasmota_%06X
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota_E17F47/
MQTT Fallback Topic cmnd/DVES_E17F47_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 14778183 (ESP8266EX)
Flash Chip Id 0x1540A1 (DOUT)
Flash Size 2048 KB
Program Flash Size 2048 KB
Program Size 716 KB
Free Program Space 1072 KB
Free Memory 25.6 KB
c. Zigbee-Router “OG”: Sonoff ZBBridge
Program Version 12.2.0(zbbridge)
Build Date & Time 2022-10-17T08:42:26
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 0T00:35:45
Flash write Count 56 at 0x1FB000
Boot Count 23
Restart Reason Power On
Friendly Name 1 zigbee-router-og
Friendly Name 2
AP1 SSId (RSSI) <SSID> (62%, -69 dBm) 11n
<IP-Settings>
HTTP API Enabled
MQTT Host
MQTT Port 1883
MQTT TLS Disabled
MQTT User DVES_USER
MQTT Client DVES_E187C4
MQTT Topic tasmota_%06X
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota_E187C4/
MQTT Fallback Topic cmnd/DVES_E187C4_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 14780356 (ESP8266EX)
Flash Chip Id 0x1540A1 (DOUT)
Flash Size 2048 KB
Program Flash Size 2048 KB
Program Size 714 KB
Free Program Space 1076 KB
Free Memory 26.4 KB
d. Zigbee-Router “UG”: Sonoff ZBBridge
Program Version 12.2.0(zbbridge)
Build Date & Time 2022-10-17T08:42:26
Core/SDK Version 2_7_4_9/2.2.2-dev(38a443e)
Uptime 77T21:53:01
Flash write Count 78 at 0xFD000
Boot Count 8
Restart Reason Power On
Friendly Name 1 zigbee-router-ug
Friendly Name 2
AP1 SSId (RSSI) <SSID> (90%, -55 dBm) 11n
<IP-Settings>
HTTP API Enabled
MQTT Host
MQTT Port 1883
MQTT TLS Disabled
MQTT User DVES_USER
MQTT Client DVES_E180BF
MQTT Topic tasmota_%06X
MQTT Group Topic 1 cmnd/tasmotas/
MQTT Full Topic cmnd/tasmota_E180BF/
MQTT Fallback Topic cmnd/DVES_E180BF_fb/
MQTT No Retain Disabled
Emulation None
ESP Chip Id 14778559 (ESP8266EX)
Flash Chip Id 0x1540A1 (DOUT)
Flash Size 2048 KB
Program Flash Size 2048 KB
Program Size 714 KB
Free Program Space 1076 KB
Free Memory 26.2 KB
Best matching topics found
I found some interesting infos here - FYI also:
- Aqara Devices only connect to the Coordinator #1608: Aqara Devices only connect to the Coordinator · Issue #1608 · ioBroker/ioBroker.zigbee · GitHub
- Cannot connect new devices to a TRADFRI repeater #2879: Cannot connect new devices to a TRADFRI repeater · Issue #2879 · Koenkk/zigbee2mqtt · GitHub
- Repairing Aqara Devices from Coordinator to Router: How to, Aqara Zigbee devices
- Aqara only paires with Coordinator: Pairing always happen at coordinator level, instead of router
- generally good information about a zigbee-network: Xiaomi & Aqara Devices - Pairing & Keeping them connected - Devices - Hubitat
- How to Build a Solid Zigbee Mesh | Hubitat Documentation
Conclusion
What do you think about that situation?
Any hints?
I would love to debug the problem of not pairing any more to my two sonoff-routers (which worked) as this would be my favorite setup to have 5 sonoff-devices in my house as backbone.
Attached to them the IKEA Tradfri and on all that devices the end-devices.
Cross-posts in other forums
Tasmota-Forum: https://github.com/arendst/Tasmota/discussions/17873
Thank you all and kind regards,
Markus.