Some of my Aqara devices state their battery status as "-396%", for example the Xiaomi Aqara Leak Sensor with driver version 0.8 shows this:
Or the "Xiaomi Aqara Door/Window Sensor" with driver version 0.7.2:
I have reset the battery status but no luck.
The percentage is just calculated from the raw voltage reading received from the sensor, which is clearly incorrect (0.522 V for your Leak Sensor, and 0.01 V for the Door/Window Sensor).
That voltage value is derived from values of specific bytes in a custom-formatted message, so what's probably happening here is that either the wrong bytes are being read, or they are in the wrong order.
The Reset Battery Replaced Date doesn't affect any of the voltage / percentage reporting. It just exactly what it named, changing batteryLastReplaced to the date when you click that button, so that a user can refer to that date for record keeping.
Since my Aqara Leak Sensor and Aqara Door/Window Sensors are all reporting correctly, and I haven't heard from other users about incorrect voltage values, my guess is that either you might either still be using Hubitat firmware 2.0.4 or older, or if using the latest Hubitat firmware, the DISABLE 2.0.5 firmware compatibility fix setting is turned on in the preferences for the devices:
If my guesses are incorrect, the only way I can help troubleshoot this is to see debug log output from the time of a battery report.
@veeceeoh Keith- Have you released the update to the driver that asked for sensitivity adjustment of the vibration sensor? Thanks for everything?
I'm afraid not yet. I was working out a user-friendly method to implement it (because of course, Xiaomi does it in a non-standard way!) However, I've had technical difficulties with my new ZigBee sniffer and family visiting the last few weeks. Although I can reply in the forums here in between things at workout times, any code changes and testing can only be done at home...
I hope to have an update in the next week, though.
Sorry everyone! Thanks for your patience.
Please help
i am new with hubitat and setting up things. I have few aqara contact sensors which are working excellent. 1 temp sensor also working very well. 1 aqara motion sensor ( placed near temp sensor ) does not report activity ( reported last activity about 12 hours ago). I can still see this in devices.
Okay, the explanation, in a nutshell as there are hundreds of posts on this, is you likely have xiaomi incompatible repeaters. Likely an Iris plug I bet..ge zigbee wall switch, smartthings outlet..
See this thread, it's an excellent resource
Anyone have any tips for keeping the Aqara temp sensors online? For the life of me they keep dropping off. I have one that works fine, but one that's very close to my Hubitat hub and one that's upstairs (basically directly through the floor) from hub will not stay online after pairing...
Not other than have a strong mesh, and ensure all repeating devices are Xiaomi compatible.
I have never had any of my 10 temp sensors drop out - other than when my hub locked up for a few days when out of town. Then I had to hit the button on each sensor to get them reporting again.
good to know. I'll try hitting the button and see if they come back online. repairing them repeatedly is getting annoying.
and I probably do have xiaomi incompatible repeaters. =/ do we have a list handy?
This may not be 100% exhaustive, though.
https://community.hubitat.com/t/compatible-devices-list/113?u=veeceeoh
sorry, I meant more, do we know which devices are incompatible repeaters with xiaomi stuff?
All my window sensors, and one of the temp sensors are fine is the odd part...
Adding an XBee to the mix might be a good idea. They keep much better signal than the one built into HE
DOH. Yes, there is a list around here somewhere. It is definitely not 100% complete, though, as last I checked the ikea tradfri outlet and repeater were not on it.
Not sure I know what you mean. How would that tie in (or would it just act as a repeater)? I mean, at that point, I should just buy stuff better than the Xiaomi stuff. I bought it all because it was super cheap for what it did...
It would act as a repeater.
I'll try waking them up and see what they do. will then look into Xbee option, or perhaps one of the Ikea repeaters (since they seem like they work well for this).
I updated it after your last mention:
Well, I and a bunch of people have laid out all the facts as we know it, so that users can make an educated decision as to whether they want to try to use Xiaomi / Aqara devices. There are concessions you'd have to make if you do decide to use them (e.g., only use "compatible" repeaters such as the Xbee or IKEA Outlet, etc., or get a second Hubitat hub to isolate all Xiaomi / Aqara devices).
As for the budget / economics argument, it mostly boils down to numbers of scale. If you save X per device across 40+ devices, having to buy a second hub may make more sense than buying the same number of more expensive devices.
I will be no part of any argument of that sort, however, because it really depends on each user's situation, budget, tolerance, patience, technical abilities, etc.
That's what I get for not checking first! Thanks!!!
Of course. and generally, I've been happy with the Xiaomi stuff. Hubitat so far has worked quite well with the contact sensors. Heck, I've had more issues addressing weak Zwave mesh with Hubitat than my Zigbee mesh.
It's just these two devices that are being butts.
Mind you, I wouldn't mind a Xbee anyway since I've wondered about how my mesh is laid out. I just kinda want go limp through until I can let my wallet recover. =)
Download the Hubitat app
