After pairing, all of the entity vales go to Unavailable greyed out
Pairing works, for a second, device entity values populate, then to to Unavailable
Zigbee Device RECONFIGURE starts, but doesn’t ever complete.
Adding to the mesh coverage, waiting, Factory reset - no difference.
I tried a custom “quirks” file for the Aqara E1 curtain driver - looked visually better, but still really Unavailable so removed it.
GitHub seemed to have some Aqara quirk updates in the last few months, but merged and (presumably) released.
I then repeated the tests on a pre-production HA install (spare kit, same software) with an old Sonoff Zigbee coordinator - all my Aqara products worked first time!
The test system is not perfect (T1 Battery Unknown, Curtain Luminance 0 - it is dark though!), however controls work and the main sensors report (better than Unavailable).
Now, I’ve looked about the forum and found ZHA issues, Z2M issues, specific coordinator issues, specific coordinator firmware updates, but not quite this combination of OK/ FAIL.
Anyone else seen this before I go into full logs / microscope / GitHub issue mode please?
HAOS updates ZBT-1 firmware automatically on the failing test rig.
I’ve not updated the Sonoff 3.0 (TI CC2652) - BUT it works!
On the Sonoff coordinator, Aqara devices report Firmware: Up-to-date
If anything should work with ZHA, it’s a ZBT-1 right?
I’ve read several articles and reviews of Aqara kit which were positive - and they seem to work with the community (e.g. HA firmware updates) so was expecting a positive experience.
1x Aqara Zigbee Temperature and Humidity Sensor T1 (also includes pressure)
Other details
UK 240V 50Hz, no known RF issues.
Stable, working HAOS install.
HACS limited to Spook, Dyson and a front-end Horizon card.
Lots of Z-Wave, Lots of Zigbee, decent WLAN, ESPhome, Tasmota, custom kit.
EST deliver very quickly (when Scotland isn’t in the middle of a 1:100 year storm!).
Engineer , years of HA/ openHAB/ MisterHouse, etc.
No hair (pulled out after too many 5-second button holds for factory reset on a precarious chair! ).
Don’t want to move from ZHA to Z2M, especially now the coordinator hardware seems to be a possible root-cause (and the Yellow has been otherwise great).
No delays nor latency on either Zigbee mesh (so far…) so the expected interference isn’t showing up.
The test System 2 only has the 3x Aqara devices on the mesh, and paired immediately from many meters away (unlike the production System 1). Yes, there’s probably more mesh traffic, but also a load more mains routers.
After some research, the Yellow / ZBT1 / SkyConnect coordinator appears to NOT upgrade firmware automatically, and the shipped 6.10.3.0 build 297 is very old compared to the current 7.4.0.0, and from my testing DOES NOT WORK with Aqara kit in my home.
Check the Zigbee coordinator firmware version
Settings → Integrations → Zigbee Home Automation → Devices → Nabu Casa Yellow v1.2
Yellow v1.2
by Nabu Casa
Connected via Nabu Casa Yellow v1.2
Firmware: 6.10.3.0 build 297
Check the Latest firmware release (early 2025 was 7.4.4.0)
I have a Yellow, so copied the URL for the latest version:
TRAP: The firmware URL needed to link to the actual firmware file you want to install isn’t shown be default. Turn Show unused configuration options = ON, and past in the URL from the firmware page above.
Save
(re)Start
Check the Logs page…
# BEFORE
INFO Detected ApplicationType.EZSP, version '6.10.3.0 build 297' (6.10.3.0.297) at 115200 baudrate (bootloader baudrate 115200)
# AFTER
INFO Detected ApplicationType.EZSP, version '7.4.4.0 build 0' (7.4.4.0.0) at 115200 baudrate (bootloader baudrate 115200)
STOP the Silicon Labs Flasher to free the hardware device again.
(Check Start on Boot is OFF to prevent conflicts)
Enable your Zigbee integration
Settings → Integrations → SHOW DISABLED
Enable Zigbee Home Automation (or Z2MQTT)
After this Zigbee coordinator firmware update from 6.10.3.0 to 7.4.4.0, my Aqara kit paired with my Yellow and started working, just as it had with ONLY the Sonoff 3.0 radio.
TL;DR: Aqara Zigbee Curtain Driver E1 Zigbee factory reset is a TRAP. Keep the button pressed until you hear TWO beeps to re-pair with ZHA.
After another 2W of fiddling, the Aqara factory reset doesn’t work as described in the manual. After some further HAOS15 / ZHA issues, I couldn’t get either of my curtain drivers to work, so followed the “press for 5S” instructions for a factory reset. After this, the ZHA pairing did not complete - just sat there interviewing.
It appears a factory reset ISN’T.
You need to keep a button pressed for 5S to get a first beep, THEN keep it pressed for a further few seconds to get a second beep.
Only then will it re-pair with ZHA.
Hope this appears with a forum search, and helps someone!
, years of HA/ openHAB/ MisterHouse, etc.
).
this post!