ZRC-90 battery level

Community Playground General Discussions
#1

Hi all
I have a couple of ZRC-90 remotes at home. Pretty neat little things once I finally got them working.
One of them started reporting low battery (i.e. 20%) so I figured let’s swap them out.
So I did.
Still reporting 20% which is hardly the end of the world, but a tad irritating.
Mios support (rather predictably) suggested excluding and re-including (which is hardly a solution) and would be a royal PITA since clearly I’d have to set up all the scenes again.
On this though, I’m bit stumped at what else they could suggest. The ZRC is getting polled and appears to be reporting that it only has 20% battery still:

06 02/12/19 22:28:10.830 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0x11ba3d8/NONE duplicate:1 <0x76e2c520>
06 02/12/19 22:28:10.831 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: Configured was: 1 now: 1 #hooks: 0 upnp: 0 skip: 0 v:0x11ba3d8/NONE duplicate:1 <0x76e2c520>
06 02/12/19 22:28:11.038 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:SceneController1 variable: Scenes was: now: #hooks: 0 upnp: 0 skip: 0 v:0x11b8ab0/NONE duplicate:1 <0x76e2c520>
06 02/12/19 22:28:14.139 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: ManufacturerInfo was: 21076,1,34064 now: 21076,1,34064 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7762c520>
06 02/12/19 22:28:14.139 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:ZWaveDevice1 variable: Capabilities was: 19,150,1,1,1,6,B,|33,89,90,91,94,114,115,128,132:2,133,134, now: 19,150,1,1,1,6,B,|33,89,90,91,94,114,115,128,132:2,133,134, #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:1 <0x7762c520>
06 02/12/19 23:03:34.167 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_CentralScene was: 3 now: 15 #hooks: 5 upnp: 0 skip: 0 v:0x1039670/NONE duplicate:0 <0x7762c520>
06 02/12/19 23:03:36.101 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1549949631 now: 1550012616 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7762c520>
06 02/12/19 23:03:36.101 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 20 now: 20 #hooks: 0 upnp: 0 skip: 0 v:0x11cee38/NONE duplicate:1 <0x7762c520>
06 02/13/19 5:31:30.101 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:SceneController1 variable: sl_CentralScene was: 15 now: 3 #hooks: 5 upnp: 0 skip: 0 v:0x1039670/NONE duplicate:0 <0x7762c520>
06 02/13/19 5:31:30.793 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryDate was: 1550012616 now: 1550035890 #hooks: 0 upnp: 0 skip: 0 v:(nil)/NONE duplicate:0 <0x7762c520>
06 02/13/19 5:31:30.794 Device_Variable::m_szValue_set device: 7 service: urn:micasaverde-com:serviceId:HaDevice1 variable: BatteryLevel was: 20 now: 20 #hooks: 0 upnp: 0 skip: 0 v:0x11cee38/NONE duplicate:1 <0x7762c520>

So any suggestions from the assembled wise ones?

Cheers

C

#2

I’ve observed my ZRC-90s (US) take as much as 24 hours before the battery level updates after a battery replacement.

From the ZRC-90 data sheet:

Battery low indication
The unit will detect battery status after key pressed, the LED will flashes 3 times
rapidly then stay off when battery low is detected. Meanwhile, it will report battery
low status to gateway automatically.

#3

Thanks. This has been more like 10 days :frowning:

C

#4

I managed to fix another device with similar by

  1. taking a backup
  2. excluding
  3. reincluding using replace

A PITA since it will involve dozen Luup restart, but it worked for me.

#5

You also change the device id. If the scenes are all set up based on id 250, for instance, and you exclude/include the device, you can edit is new id to 250 and things should work again.

#6

Last time I had some troubles with this procedure. The scenes lost all the triggers and I had to start over again. Maybe it was me fiddling a lot, but I suggest a backup anyway, you’ll be on the safe side.

#7

Thanks. Certainly doesn’t match my experience of scenes when deleting associated devices. They just vanish. I’ll give it a try if I get really desparate :slight_smile:

C

#8

[quote=“therealdb, post:4, topic:200603”]I managed to fix another device with similar by

  1. taking a backup
  2. excluding
  3. reincluding using replace

A PITA since it will involve dozen Luup restart, but it worked for me.[/quote]

I assume there’s a ‘Restore’ in there somewhere? Step 4?
Can you give me some more detail on what step 3 is?

Cheers!

C

#9

Ok, so, correct steps are

  1. backup
  2. exclude
  3. restore backup, including zwave
  4. replace failed, under advanced, commands

Basically, you are including it as a new device, but taking the place of the old one, that you previously excluded. Worked for me, but YMMV.

#10

[quote=“therealdb, post:9, topic:200603”]Ok, so, correct steps are

  1. backup
  2. exclude
  3. restore backup, including zwave
  4. replace failed, under advanced, commands

Basically, you are including it as a new device, but taking the place of the old one, that you previously excluded. Worked for me, but YMMV.[/quote]

Thanks! I’ll look at this when I have some time to dedicate to fixing things :slight_smile:

C