Hi all. I've got a bunch of Third Reality motion sensors, and their battery level is reporting weird numbers like 162% for one of them, and 170% for another. If accurate, that would be super badass. But I think something is inaccurate. Any suggestions for how to get these things to report correctly?
Be sure you're using the Generic Zigbee Motion Sensor (no temp) driver and click configure...
Yep done. I’ve tried both of these devices types, and hit “Configure,” but still seeing the odd battery numbers:
• Generic Zigbee Motion Sensor (no temp)
• Generic Zigbee Motion Sensor
Any thoughts on what I should try next?
Try a factory reset on the device then re include it, do not delete it from hubiyat
Mine is the same way on all my third reality motion sensors. Same driver. Generic zigbee motion no temp.
Such a pessimist 
I recently got one of these and my battery has been reporting properly.
I've been watching batt status closer than I normally do since this is the first device I'm trying some rechargeable batteries (Eneloops) with, but so far, things seem to be going as expected.
Are the motion events reporting properly? Maybe just try a different set of batteries for giggles?
can you post the manufacturer string that's shown in the data section?
ok, that explains alot, yes please try that...
Looks a bit better after the re-pair, but the battery is still reporting way too high.
dev:43262022-06-28 08:31:31.515 pm infoCloset Motion is active
dev:43262022-06-28 08:31:31.500 pm infoCloset Motion battery is 181%
dev:43262022-06-28 08:31:31.499 pm infoCloset Motion is inactive
dev:43262022-06-28 08:31:31.497 pm debugdescMap:[raw:7CDD01000108210020B5, dni:7CDD, endpoint:01, cluster:0001, size:08, attrId:0021, encoding:20, command:0A, value:B5, clusterInt:1, attrInt:33]
dev:43262022-06-28 08:31:31.482 pm debugdescMap:[raw:7CDD0100010820002020, dni:7CDD, endpoint:01, cluster:0001, size:08, attrId:0020, encoding:20, command:0A, value:20, clusterInt:1, attrInt:32]
dev:43262022-06-28 08:31:26.518 pm debugdescMap:[raw:catchall: 0000 0013 00 00 0040 00 7CDD 00 00 0000 00 00 00DD7C217CE7FFBF022C2880, profileId:0000, clusterId:0013, clusterInt:19, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, DD, 7C, 21, 7C, E7, FF, BF, 02, 2C, 28, 80]]
dev:43262022-06-28 08:31:02.627 pm debugdescMap:[raw:catchall: 0104 0500 01 01 0040 00 7CDD 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:43262022-06-28 08:30:44.552 pm warnconfigure...
dev:43262022-06-28 08:30:20.785 pm debugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 7CDD 00 00 0000 00 00 1900, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[19, 00]]
dev:43262022-06-28 08:30:19.693 pm infoGeneric Zigbee Motion Sensor (no temp) battery is 172%
dev:43262022-06-28 08:30:19.685 pm debugdescMap:[raw:7CDD0100010A210020AC, dni:7CDD, endpoint:01, cluster:0001, size:0A, attrId:0021, encoding:20, command:01, value:AC, clusterInt:1, attrInt:33]
dev:43262022-06-28 08:30:18.635 pm inforeporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute
dev:43262022-06-28 08:30:18.630 pm debugdescMap:[raw:catchall: 0104 0001 01 01 0040 00 7CDD 00 00 0000 07 01 86002100, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 21, 00]]
dev:43262022-06-28 08:30:16.628 pm debugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 7CDD 00 00 0000 00 00 1900, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[19, 00]]
dev:43262022-06-28 08:30:13.869 pm inforeporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute
dev:43262022-06-28 08:30:13.852 pm debugdescMap:[raw:catchall: 0104 0001 01 01 0040 00 7CDD 00 00 0000 07 01 86002000, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 20, 00]]
dev:43262022-06-28 08:30:13.838 pm debugdescMap:[raw:catchall: 0000 8021 00 00 0040 00 7CDD 00 00 0000 00 00 1700, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[17, 00]]
dev:43262022-06-28 08:30:11.748 pm debugdescMap:[raw:catchall: 0104 0500 01 01 0040 00 7CDD 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]
dev:43262022-06-28 08:30:10.869 pm infoGeneric Zigbee Motion Sensor (no temp) is active
dev:43262022-06-28 08:30:10.827 pm debugdescMap:[raw:catchall: 0104 0500 01 01 0040 00 7CDD 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:7CDD, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]
dev:43262022-06-28 08:30:09.666 pm infoGeneric Zigbee Motion Sensor (no temp) is inactive
dev:43262022-06-28 08:30:08.901 pm warnconfigure...
What platform version are you running?
2.3.2.131
found the issue with it.
@mike.maxwell — Nice! We're cheering for you guys. 
Holy bajeesus @mike.maxwell . Just 14 hours ago you said you found the issue. Then 10 hours later when I updated the firmware to 2.3.2.133 , all the motion sensors are now reporting accurate battery levels.
You guys are like the AVENGERS of home automation. You're like the MILLENIUM FALCON of software dev. You guys so good at this stuff that it makes all other teams in all other companies look like piles of garbage.
I ain't wearing a hat right now, but if I were, I'd be tipping it to you sir.
What is the manufacturer as listed in the device data section for this one?
Download the Hubitat app
