I've just realized that none of my ZigBee devices (Centralite flavors) update their Battery statuses. Unless I do a manual refresh, there is only one entry - when the device joined the network.
With only a couple of exclusions, the drivers are generic.
Meanwhile, Search on the Device/event pages does not work - Ajax error.
I noticed the same thing for some of my battery powered devices. So, I created a Periodic Rule Machine rule to call refresh() on each of these devices about twice a day. Seems to have helped to keep the battery reporting up to date without overworking the devices.
@mike.maxwell - How is battery reporting for these devices supposed to work? I would think that when they are paired and 'Configured', that the configuration data would tell the device how frequently to report its battery level... But, maybe that functionality is somehow hardware specific? Any insights you have would be appreciated. Thanks!
I have seen the same thing as the OP with my Centralite-based water leak detector and 2 motion detectors.
@mike.maxwell - I did some more Refreshing; this time, a little better organized. And:
Lightify Motion - in Logs, updates Temperature and Battery level with every Refresh but only once added a record to the Device Events.
ST Motion (2015) - on the first Refresh, I get Motion Active, Battery and 2xTemp in the Logs and Motion Active + Temp (but no Battery Level) in Device Events. A few seconds later, Batt + Temp are added to Logs again. No changes in the Device Events.
Iris - Batt+Temp in Logs, only Temp in Device Events.
Could it be that, among other things, deduplication is a little too aggressive in the Device events?
Not familiar with this device, what driver?
General notes on presence enabled sensors: for the most part the lot of these issue battery reports at 15 second intervals, thats how presence is determined.
Live logs vs event logs: these are not the same, live logging is always sent if those options are selected in the driver, these may or may not have corresponding events, events are somewhat more complex. If a given attribute on a given device has no subscriptions, only state changes will be committed to the db, irrespective to the number of events the device produces.
Config settings, if a given device has its discovered driver changed manually one must run the configure command in the driver so that all reporting and configuration command are sent to the device, this is particularly true when the device is initially discovered as device.
dev:42018-07-24 22:53:39.784:infoLightify Motion temperature is 26.70°C
dev:42018-07-24 22:53:39.739:infoLightify Motion battery is 77%
dev:42018-07-24 22:53:38.875:infoLightify Motion temperature is 26.70°C
dev:42018-07-24 22:53:38.853:infoLightify Motion battery is 77%
dev:42018-07-24 22:53:38.716:infoLightify Motion temperature is 26.70°C
and this:
temperature
26.70°C Lightify Motion temperature is 26.70°C DEVICE 2018-07-24 10:51:32.613 PM EDT
When I first connected the device (Feb 14), it did report 100% Battery but there were no updates until I manually executed the Refresh today. Subsequent refreshes generate only Temp records in the Device Events (and only if the device temperature is different from the previous reading).
You're right. Never paid attention because the battery consumption is really low on these. Mine checked in the day I installed it at 66% (it was a used unit) and it still reads 66%. Refresh doesn't update for me.
Nice, I hope this includes the Iris key fob, I have multiple and they were dead and I noticed because my wife used my car(never used, like spare car) and the automations did not work.
Was this fixed? I still have the same problem with Iris motion sensors, in some point the motion will false detect a person but changing the battery will fix the problem, and it had 99% with the old battery....