Thirdreality motion sensor battery reporting?

🛎️ Get Help
1

C-8
2.4.2.143

I have a thirdreality motion sensor. I left the house and realized it was stuck in an active state when I left (which blocked my alarm from arming).

The battery on it has always reported 100%

I read other threads on here, tried switching the driver back and forth from Generic Zigbee Motion to the no-temp driver (clicked configure each time I switched), but I keep seeing this in the logs:

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:27:52.713 PM
info
reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:27:51.707 PM
info
reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute

So I enabled debug logging and installed new batteries, and I saw this in the logs:
dev:222025-09-10 11:26:45.769 PM

info

Apt Motion battery is 92%

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:26:45.262 PM
info
reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:26:44.506 PM
info
reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute

New batteries - but now I'm at 92%, even though it's showing some power configuration error?

Debug logs:

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:29:39.818 PM

debug

descMap:[raw:68B00100010A210020B9, dni:68B0, endpoint:01, cluster:0001, size:0A, attrId:0021, encoding:20, command:01, value:B9, clusterInt:1, attrInt:33]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:29:39.540 PM

debug

descMap:[raw:68B00100010A2000201D, dni:68B0, endpoint:01, cluster:0001, size:0A, attrId:0020, encoding:20, command:01, value:1D, clusterInt:1, attrInt:32]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:55.103 PM

debug

descMap:[raw:68B00100010A210020B9, dni:68B0, endpoint:01, cluster:0001, size:0A, attrId:0021, encoding:20, command:01, value:B9, clusterInt:1, attrInt:33]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:54.839 PM

info

reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0021 failed, unsupported attribute

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:54.836 PM

debug

descMap:[raw:catchall: 0104 0001 01 01 0040 00 68B0 00 00 0000 07 01 86002100, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 21, 00]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:54.340 PM

debug

descMap:[raw:catchall: 0000 8021 00 00 0040 00 68B0 00 00 0000 00 00 E48C, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[E4, 8C]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:54.089 PM

info

reporting configuration for Power Configuration (cluster 0x0001), attribute 0x0020 failed, unsupported attribute

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:54.086 PM

debug

descMap:[raw:catchall: 0104 0001 01 01 0040 00 68B0 00 00 0000 07 01 86002000, profileId:0104, clusterId:0001, clusterInt:1, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:07, direction:01, data:[86, 00, 20, 00]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:53.571 PM

debug

descMap:[raw:catchall: 0000 8021 00 00 0040 00 68B0 00 00 0000 00 00 E28C, profileId:0000, clusterId:8021, clusterInt:32801, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[E2, 8C]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:51.542 PM

debug

descMap:[raw:catchall: 0104 0500 01 01 0040 00 68B0 00 00 0000 0B 01 0000, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:0B, direction:01, data:[00, 00]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:49.525 PM

debug

descMap:[raw:catchall: 0104 0500 01 01 0040 00 68B0 00 00 0000 04 01 00, profileId:0104, clusterId:0500, clusterInt:1280, sourceEndpoint:01, destinationEndpoint:01, options:0040, messageType:00, dni:68B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:04, direction:01, data:[00]]

[dev:22](http://10.0.1.190/device/list#)2025-09-10 11:28:49.360 PM

warn

configure...

Any ideas?

2

Looks like the sensor is still reporting battery just fine, it just doesn’t support the attributes the driver is trying to configure. That’s why you see the “unsupported attribute” messages. The 92% reading after new batteries seems normal. If it’s getting stuck active, that’s more likely a device/firmware quirk than the battery reporting itself.

3

This may not be relevant. I have a bunch of Third Reality flood sensors. They have never reported a battery change. They do report wet/dry hourly. I use device activity check to notify if they fail to report for more than 1 day. If your motion sensor reports hourly you might want to set activity check for a couple of hours so you know when the battery dies. Or, proactively change the battery a month earlier than its previous failure interval.

4

attribute 0x0021 of the power management cluster is "battery percentage remaining" It looks like your motion sensors don't support this capability.