I’m finding that the leak sensor is dropping off. I’ve repaired it a few times. Have just tried it again now. Once paired, if I press the top of the leak sensor I can see battery information appear in the logs - but this info isn’t appearing on the “events” tab of the device. Odd. @chirpy ?
dev:11212021-03-03 08:02:37.991 infoLeak sensor 1 voltage changed to 3.01 volts
dev:11212021-03-03 08:02:37.990 infoLeak sensor 1 battery changed to 100%
dev:11212021-03-03 08:02:37.985 debugProcessing Xiaomi data (cluster:0000, attrId:0005, encoding:42)
The events should only update if there is a change in the state of the event (this is the HE preferred way). The fact you are seeing it in the logs does mean it is working as expected
I was going to say, if you re-pair the device (but do not remove the device from HE) and once done, hit Configure on the device page, that usually sorts these devices out.
I added an Aqara door and window sensor (MCCGQ11LM). When I add that switch to the HE alexa skill, the alexa app shows that as a temp sensor, and not a open/close sensor.
That's a side-effect of using a combined driver, unfortunately. The simplest workaround might be to create a Virtual contact sensor and use that on alexa and then map the physical device to the virtual device using Rule Machine.
Not sure if the original Xiaomi button is supported fully. Seems to work but I do get this: dev:3492021-03-15 22:59:44.148 errorjava.lang.NullPointerException: null on line 316 (parse)
dev:3492021-03-15 22:58:04.115 errorjava.lang.NullPointerException: null on line 316 (parse)
That's odd. That line number in the latest driver would suggest that there's no value in the Hold Duration preference setting. Try hitting "Configure" on the drivers page and then make sure Hold Duration is set (default is 1) and Save Preferences.
All mine are happy and present. I wonder if your zigbee mesh has been upset after the upgrade and reboot and needs to settle down? I'd watch it for 24 hours to see if it improves. Is it only the Xiaomi sensors playing up?
30 Aqara devices + 5 repeaters.
8 devices switching from present to not present and back, some no connection on different repeaters.
After restart my 5 Ikea repeaters the devices came back online. As mentioned by you, It looks the mesh was a upset indeed.
I did have one motion sensor ignore me this morning but it was reporting "present".
It's been dead ever since 8:21. I re-paired it and it rejoined as previously joined so we'll see. The other devices I have checked so far are working.
