Battery reporting 200%

🛎️ Get Help Devices
50

MIne are not sending on there own. Refresh usually works though. I've set up a scheduled refresh for every 12 hours to "check in" on the affected devices. Here and there the refresh doesn't result in a battery event but as long as 1 comes through in a 24hr period, I'm OK with that for now. Still getting contact sensor 200% battery level though.

here's the debug resulting from 2 scheduled refreshes...

image
image994×73 18.9 KB

...and the device events
image
image1393×327 42.6 KB

@ThirdReality I'd rather have the firmware send the battery reports like it used to. Contact and motion sensors both stopped reporting after firmware update as well as shortened motion cool down which I don't understand why anyone would want that. 3 to 4 sec cool down has to affect battery life I would think.

51

It doesn't look like it is sending any reports for battery on its own

52

Can you post a screen shot of the data section of the driver details?, thanks!

1 Like
54

image

55

the 200% reporting should be fixed in the upcomming 2.3.9 release

4 Likes
56

@ThirdReality Could you chime in here and let us know what needs to be done to get battery reporting working on your devices for Hubitat? As it stands now the latest firmware does not report battery at regular intervals. Seems Version 31 worked but Hubitat never had this firmware for us to test, rather it came on new devices. 30 was the latest until they received Version 34 which doesn't work.

3 Likes
57

@ThirdReality Any feedback on this issue?

58

Seemed like this was the best post to ask about two new Zigbee contact sensors I bought that are showing 200% battery. Had been using about 30 Visonic sensors for years and they are starting to die off, bought a few Zooz sensors as replacements but the battery life is all over the place and they are not the cheapest. So... I bought a handful of different ones from Ali Express to test out. All seem to work fine, but two are reporting 200%...

This one is cool since it is pretty small and uses a CR2032 battery. It pairs as a "Device". I have changed it to the Generic Zigbee Contact Sensor (no temp).

https://www.aliexpress.us/item/3256806131336251.html

endpointId: 01
application: 90
inClusters: 0000,0003,0500,0001,0400
manufacturer: _TZE200_pay2byax
model: TS0601
softwareBuild: 0122052017

This next one is cool since it is not that big, comes in black, and uses a two AAA batteries. It pairs as a "Tuya NEO Coolcam Zigbee Water Leak Sensor" which I have the 3rd party driver installed for. I have changed it to the Generic Zigbee Contact Sensor (no temp).

https://www.aliexpress.us/item/3256806724593291.html

endpointId: 01
application: 46
manufacturer: _TZ3000_rcuyhwe3
model: TS0203

Both seem to bounce between 100% and 200% battery as they report in, and was just wondering if these have come across anyone's radar? Or if there was anything I could do?

I have a C-7 running 2.3.9.147

Thanks!

59

If the two Tuya devices do not report consistently and regularly the battery status when using the Tuya driver, let me know and will fix it. All Zigbee contact sensors that I have (including ThirdReality 3RDS17BZ) are reporting the battery status regularly and correctly.

1 Like
60

Thank you - Hadn't noticed that before - will try now!

1 Like
61

I am getting the following error with some of my Third Reality devices on version 0034

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

  • endpointId: 01
  • firmwareMT: 1233-D3A1-00000034
  • inClusters: 0000,FF01,FF00,0001,0500
  • manufacturer: Third Reality, Inc
  • model: 3RMS16BZ
  • outClusters: 0019
  • softwareBuild: v1.00.52
62

Just to confirm -- that model # corresponds to a motion sensor -- is that correct?

63

Yes that’s correct.

64

If you wish the battery reporting to be sorted using the stock driver, I'll need the device fingerprints for both of these

1 Like
65

image
image1550×185 31.6 KB

66

is this a contact sensor?

1 Like
67

Yes, no temp

68

The device reports that it supports temperature (cluster 0x0402), have you tried the Generic Zigbee Contact Sensor with it?

69

I have not, I'll take look :+1:t2:

70

Yes you are right, it must have just picked the non temp one? Looks like battery reporting has also gone to 100 as well. So could add its finger print to the genetic contact driver.

1 Like