I had three NYCE door/window sensors batteries go dead while they were still showing 80% in vera. I checked the “BatteryDate” variable for the sensors and ran it through the epoch converter and it showed a recent date/time of within minutes of the current time.
I currently have one sensor reporting 80% battery that is still working but Vera is sending a low battery alert for the device. I’ve also had a similar issue with the NYCE tilt sensor.
After changing the battery on the devices that had the dead batteries they show 100%. Is there something wrong with the devices or is there an issue with the battery level in Vera?
I added some log entries. The only thing I see is that sl_BatteryAlarm went from 0 to 10.
What does this variable represent?
| 06 | 04/27/22 13:22:40.648 | Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:ZigbeeDevice1 variable: VoltageLevel was: 24 now: 24 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x75d4a520> |
|---|---|---|
| 06 | 04/27/22 13:22:40.648 | Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 80 now: 80 #hooks: 0 upnp: 0 skip: 0 v:0xbbaa38/NONE duplicate:1 <0x75d4a520> |
| 06 | 04/27/22 13:22:40.649 | Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1651080084 now: 1651080160 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x75d4a520> |
| 06 | 04/27/22 13:22:54.480 | Device_Variable::m_szValue_set device: 102 service: urn:micasaverde-com:serviceId:HaDevice1 variable: sl_BatteryAlarm was: 0 now: 10 #hooks: 0 upnp: 0 skip: 0 v:0xbbad98/SL_BATTERYALARM duplicate:0 <0x75d4a520> |
| 07 | 04/27/22 13:22:55.263 | RAServerSync::SendAlert 0x1761a48 PK_Event 42685230732 retries 0 URL age: 1 file: err: 0 sess: 000000017A1600626A82021633FC333326B742 serv: vera-us-oem-event11.mios.com/vera-us-oem-event11.mios.com <0x76b4a520> |