Read all these entries and I'm confused. I have a 3rd reality sensor that only reports 42% battery even with new batteries. I'm using the "Generic Zigbee Motion Sensor (no temp)" driver as recommended. I don't see the firmware version displayed and I don't know where to get new firmware. I found their website, but don't see anywhere to download it. Is there a solution to the wrong battery percentage issue?
So any updates on this? Anyone successfully work through this bad battery reporting?
So I tried a firmware update. I have hit configure. Refresh. I've tried a rain dance. Is there anything that can make this sucker stop reporting low battery? In my logs I'm seeing this when I did the above:
dev:19702023-09-06 06:53:06.603 AMinforeporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute
dev:19702023-09-06 06:53:01.868 AMwarnconfigure...
dev:19702023-09-06 06:49:14.106 AMinforeporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute
dev:19702023-09-06 06:49:13.863 AMinforeporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute
Well hot dog. Looks like the firmware update actually took. The clue was that 5 minutes later my Zigbee devices were not working and it occurred to me that maybe, just maybe the firmware update was in progress.
Just checked and the data/firmware/software build has changed and the battery is now reporting 100%. So either the firmware update fixed it or it was that rain dance. Unsure.
AND now: dev:19702023-09-06 07:06:01.625 AMinfoWorkshop Motion battery is 100%
3 Likes
I was getting a lot of false "Active" events, and battery said 12%. I put in new battery and it only showed 22%. I saw a lot of "reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute" entries in the log.
I updated the firmware which now shows - firmwareMT: 1233-D3A1-00000017
but battery is only up to 42% with new batteries 
and i am still getting
"reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute"
entries in the log file. color me concerned.
also, I have another of these units in service and am getting zero of these errors in the log files. Will check my daughter's house where i have 5 of them in service.
[updated - put device back in service and it later reported at 100% battery life. not sure what the delay in battery status is ? ( third reality engineer on battery logic needed ) . the next day the battery has dropped to 93%, which seems like a more likely reflection of reality.
My situation was also resolved by a Firmware Update. I was on softwareBuild: 000000017 and am now on 33. It seemed like nothing was happening after I clicked the update firmware button, but upon reading this message I waited about 10 minutes and then found the new build #.
Mine battery was always reporting 31-33 for battery for the last 2 battery changes that I just did once it died. Now it reports 90, so I hope to be able to know when it might run out before it does so.
I did the firmware upgrade on 3 of my 4 Third Reality water leak detectors and they went from v21 to v38. The 4th one was already on v38 so just for the heck of it I triggered a firmware update request and sure enough it upgraded from v38 to v42. So now I'm upgrading the other 3 to see if they come up from v38 to v42 as well.
I I guess the bottom line is it seems that the firmware update architecture in these Third Reality products requires you to update through some or all of the intermediate versions to get the latest and greatest.
1 Like
@steve.hoge
After reading about your success in updating your Third Reality water sensors, I wanted to do the same. I discovered that I have a mix of versions 34 and 38.
The problem is that I can't find anything under the device settings that looks like a FW Update button/option. In fact I can't find it under any device in my system. Am I looking in the right place (Device properties)? If so, then under which "tab".
I am running version 2.4.0.144
Thanks
Its on the main Commands tab. Not all drivers have the Update Firmware command, if its missing you can temporarily switch the driver (Type) to "Device" and then the command will be there. Switch back to what it was before once it is done.
1 Like
I'm using the "Generic Zigbee Moisture Sensor (no temp)" driver for my Third Reality model 3RWS18BZ Water Leak Sensor. The several other moisture or leak sensor drivers may or may not expose the FW Update button?
I should mention that I am also getting the log messages:
reporting configuration for Power Configuration (cluster 0x0001), attribute0x0020failed, unsupported attribute
and just sometimes :
reporting configuration for Power Configuration (cluster 0x0001), attribute0x0021failed, unsupported attribute
on 1 of these units, which is a real headscratcher, since I have 4 of these same model updated to the same firmware and identically configured except for their individual devices names. The particular unit generating these messages was silent until the firmware update. 
1 Like
Thank you both for your very prompt replies with the information that I needed.
I have been using the "Third Reality Water Sensor" driver, which apparently doesn't support the firmware update button.
Both of your suggested drivers did show the "Update Firmware" button.
Since I had never used Hubitat to perform a firmware update previously, I didn't know what to expect. At first I pressed the update button, then checked the version number, and it had not changed. After some time I rebooted the sensor, and finally the Live Logs said the firmware update had been started, but the version number still did not change. After more time, the Live Logs reported the update was 10% complete, and I realized the process was going to take some time, which ended up being much longer than I had expected.
Bottom line is, the update completed successfully, and I am grateful for your assistance.
Also my apologies for drifting away from the original subject of this thread.
Third Reality motion sensors incorrectly report "motion detected" when battery levels are updated or when batteries are removed/reinserted,
likely due to firmware issues or hub driver misinterpretation. Users often report false alerts alongside inaccurate battery readings (e.g., 39-44% with new batteries).
Troubleshooting Steps to Fix the Motion Issue:
- Re-pair the Device: Remove and re-add the sensor to your hub, which often corrects reporting errors.
- Update Firmware: Ensure the sensor is running the latest firmware, as updates have addressed battery reporting bugs.
- Reset/Configure: Perform a factory reset (without deleting it from your hub), or click "configure" or "refresh" in your hub's device driver page after changing batteries.
- Driver Switch: For Hubitat users, switching to the "with-temp" driver and disabling temperature reporting may resolve battery issues.
