Battery changed on neo cool cam pir and now battery percentage is not correct

Hi all.

I changed the battery inside one of my neo cool cam pir sensor and now battery percentage is not correct.

I tried to reset the variable to 100, but when the device is polled, it is changed back to 25 (the value before I changed the battery).

Any hints? Will it be updated overnight? It’s not a real problem after all, I wrote the date I changed the battery in a log, but it’d helpful to have a more precise report.

The device is working OK with the new battery.

Hello,

We have created a trouble ticket for you. When you have the time, please reply.

Thank you and Have a nice day,

Having the same problem with a Neo Coolcam doorsensor and water sensor. After changing battery they are stuck at 4%. Please report back if it got resolved for you. Would really like to hear the solution.

I never received the e-mail with the ticket. I guess it was lost somewhere into then Junk Mail folder.

You can force the sensor to wake-up, to see if the battery level is changing.

Also you can try to run the following lupp code ( Apps>Develop Apps>Test Luup code ) , where you need to replace for the replace for node, the altid for the device:

luup.call_action(?urn:micasaverde-com:serviceId:ZWaveNetwork1?, ?SendData?, {Node=32, Data=?x80-2?}, 1)

I already tried to wake it up. When sending your suggested command, I get this in response:

02 12/28/18 17:31:44.488 ZWaveNode::HandlePollUpdate_Sensor_Binary_Report node 45 device 146 poll response <0x76cd9520>
04 12/28/18 17:31:44.489 <0x76cd9520>
02 12/28/18 17:31:44.490 Device_Basic::AddPoll 144 poll list full, deleting old one <0x76cd9520>
06 12/28/18 17:31:44.491 Device_Variable::m_szValue_set device: 144 service: urn:micasaverde-com:serviceId:HaDevice1 variable: PollRatings was: 4.90 now: 4.90 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x76cd9520>
06 12/28/18 17:31:44.491 Device_Variable::m_szValue_set device: 144 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: LastPollSuccess was: 1546013277 now: 1546014704 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76cd9520>
06 12/28/18 17:31:44.492 Device_Variable::m_szValue_set device: 144 service: urn:micasaverde-com:serviceId:ZWaveNetwork1 variable: ConsecutivePollFails was: 0 now: 0 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x76cd9520>
06 12/28/18 17:31:45.101 Device_Variable::m_szValue_set device: 144 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1546014704 now: 1546014705 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x76cd9520>
06 12/28/18 17:31:45.102 Device_Variable::m_szValue_set device: 144 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 25 now: 25 #hooks: 0 upnp: 0 skip: 0 v:0x13402d0/NONE duplicate:1 <0x76cd9520>

So, it seems the device is reporting the old battery value, and it’s not resetting to 100%.

You are correct.

Seems that the device is sending through z-wave 25 % for the battery level variable. The only thing that remains is to exclude and re-include the device and see if it’s doing the same.

I’ve a couple of scenes built using this device, so removing and adding it again it’s not an option at the moment. I’ll try later next week with a backup/restore and see what this will cause.

I try to avoid battery operated devices and this reminds me to continue with this. Too bad PIRs are not available in wired version, unless I want to hack a switch/universal sensor, as I did in other, more permanent solutions in the house.

I also sent a message to NeoCoolCam’s support. Hold on while I report their response.

So, I got no response and I was able to have it back to 100% by excluding and including again.
It seems a FW bug on NeoCoolCam part’s for me. Annoying as hell, since I had to redo a couple of scenes, but I switched back to the previous ID, so code is safe again.

Thanks for the follow up! :slight_smile:

How did you change the ID to the old one?

Take note of them and then change under parameters.