Xiaomi / Aqara ZigBee device drivers (possibly may no longer be maintained)

Running the same version. I have a spare new sensor so I will try that tomorrow

I don't know if this is appropriate but GearBest has the Original Xiaomi RTCGQ11LM Smart Home Aqara Human Motion Sensor - White 217027701 on sale for $11.99 USD each. I Ordered a few, seems like a good price. If not appropriate please remove the post.

https://us.gearbest.com/alarm-systems/pp_659226.html

It's fine I've seen it/done it without any complaints.
I have 2 of those, they report motion & lux and work very well, and the price-dam! Keth's driver works great. There's even a hack to make it reset to detect motion every 5 seconds

Yup - I bought some Aqara temperature/humidity sensors (WSDCGQ11LM) earlier today for $9.99, and some Aqara smart motion (vibration) sensors (DJT11LM) for $10.99.

Just make sure you have Aqara-compatible zigbee repeaters -- the Tradfri outlets work well for this.

Do you happen to know if the Cree connected bulbs are Aqara compatible ZigBee repeaters? I have several of those throughout the house.

@tom2

This thread has great information on getting Xiaomi Aqara zigbee devices to work with HE. It includes information about zigbee repeaters that work, and more importantly, ones that don't work with Aqara devices.

Edit - at $9.99, the Tradfri outlets were the cheapest xiaomi-compatible repeaters that I could find.

1 Like

OK,

So I replaced one of the sensors with a new one and humidity is now working fine.

Strange that all 3 sensors stopped reliably updating humidity and all on the same day!

This is a usefull tool to know what is working as a repeater and what isn't.

goto: http://yourHubIP/hub/zigbee/getChildAndRouteInfo (yourHubIp = IP address of your hub)

You will then be able to see what is acting as a repeater in your setup.

2 Likes

If only that were true. It worked a few times for me initially but hasn't worked since.

I have just tried it again and it appears to only show recently added Zigbee battery devices, the mains powered devices are all showing.

Shame, this could be a really useful tool

All I get is a load of code displayed.

This is what I see, but I have a lot more zigbee devices than shown.

Parent child parameters
EzspGetParentChildParametersResponse [childCount=3, parentEui64=0000000000000000, parentNodeId=65535]

Child Data
child:[Garage PIR, 91FE, type:EMBER_SLEEPY_END_DEVICE]
child:[Office door, 6862, type:EMBER_SLEEPY_END_DEVICE]
child:[Garage door, F303, type:EMBER_SLEEPY_END_DEVICE]

Neighbor Table Entry
[Guirlande , 0D0D], LQI:46, age:7, inCost:7, outCost:0
[Kitchen bulb, 18F5], LQI:252, age:6, inCost:3, outCost:3
[Vero Bed, BA68], LQI:252, age:4, inCost:3, outCost:7
[Garage workbench light , BF41], LQI:237, age:4, inCost:5, outCost:3
[Bed LEDs, F771], LQI:92, age:7, inCost:7, outCost:0

Route Table Entry
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kitchen bulb, 18F5] via [Kitchen bulb, 18F5]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Garage workbench light , BF41] via [Garage workbench light , BF41]
status:Unused
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kids Bath TH 2, C177] via [Vero Bed, BA68]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Vero Bed, BA68] via [Kitchen bulb, 18F5]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Kitchen door, 7BD1] via [Kitchen bulb, 18F5]
status:Active, age:64, routeRecordState:0, concentratorType:None, [Guirlande , 0D0D] via [Garage workbench light , BF41]
status:Active, age:0, routeRecordState:0, concentratorType:None, [Bed LEDs, F771] via [Kitchen bulb, 18F5]
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused
status:Unused

Yep. I used to get the same. Not anymore.

It works on/off for me. Haven't bothered to figure out why. Maybe on my hubs it only works for a while after a reboot? Not sure.

But a few weeks ago it wasn't working... Last week it was working... Tried last night, wasn't working again.

has anyone had false notification issues with their aqara contact sensors? I'm having an issue here: False notifications from contact sensors?

I'm wondering if it is more sensor related than something in the Notifications App. I'm comparing and it seems the multiple rapid open/close in the logs only happens with that sensor.

These "harmless" errors are from a type of non-useful message typically occurring during the pairing process that the driver isn't coded to handle.

I will be updating the drivers to ignore that type of message without throwing an error. Thanks for the report!

Yes, I've seen the same, in past when I changed my hub's ZigBee channel, though a couple of Xiaomi / Aqara devices managed to change over by themselves. Manually rejoining the devices sped up the process of bringing them all over onto the new channel.



One thing to realize is that a repeated value will not generate an event. Only when a newly reported value is different from the previously reported value will an event be generated.

Otherwise, the frequency of temperature / humidity / pressure reports is entirely set by the hardware, and completely out of the control of the device driver as the sensors won't accept any normal ZigBee commands to adjust reporting.

Also, I can say that in my experience, some ZigBee Repeater devices drop messages from Xiaomi / Aqara devices, despite allowing those Xiaomi / Aqara devices to remain connected to the ZigBee network. This issue can even manifest in only some messages being dropped, particularly when a number of messages are sent rapid fire, as is the case with the Temp/Humidity sensors, which normally send temperature / humidity / pressure reports at the same time.

I notice from your post with the output from getChildAndRouteInfo that for example, your "Kids Bath TH 2" is routing via a "Vero bed". I don't know what the "Vero bed" is, but if it's not in the list of reported compatible routers/repeaters in the OP of my other thread here, I'd be suspect of that router device possibly dropping some of the Temp/Humidity sensor's messages.



The multiple rapid open/close issue has been mentioned before, by @gavincampbell, here.

I explained some possible reasons for this in the next post, and after that I tried some modifications to the code to filter out extra unnecessary open/close events. @gavincampbell came up with a better solution that seemed to work, but I never had a chance to roll it into a full release update of the driver code.

It sounds like I should revisit that modified code...

2 Likes

Thanks for that, I picked up half a dozen of the Tradfri outlets from IKEA. They've already helped with some of the Cree bulbs as well.

2 Likes

@tom2

:+1:

The Hubitat community is just a wealth of information.

Strangely enough Bath TH 2 is the new sensor which is working well and "Vero bed" is an Osram Smart+ socket. The sensor which is updating slowely is called Bath TH but only on humidity the temp probe is working fine

Oh! What is the model of OSRAM Smart+ socket you're using? I should add that to the list of router devices that are known to work with Xiaomi / Aqara devices.

I don't see "Bath TH" in your getChildAndRouteInfo output. I don't suppose you know if it's connected to your ZigBee network through a router device?

Download the Hubitat app