Interesting alternative "power monitoring solution" I'm gonna grab one of these for testing it. Thanks for posting this!
I have tried including the device twice now and it joins as a "device" and the circle turns red. I can go in and change the device "type" after it installs and I only get battery level (1%). However doing this I do not see...
* AC Status
* Battery Status
* Power Source
Thoughts?
EDIT: After manually switching the driver to this one, I had to unplug the unit and plug it back it to mains. Once I did that the errors went away and it began reporting everything correctly.
I had installed the above driver first. Then pressed for z wave inclusion. At first the Ring extender didn't connect so I tried a second time pressing the button on the side of ring. Instantly it connected AND it automatically chose the above driver and has worked perfectly. I was worried, at first, that nothing was appearing in the status section but within a short time everything in the status field populated after pressing configure and refresh. With the help of many in the Hubitat community, I now have a device that reports a power failure and a rule that shuts down my hub safely after 30 minutes when a power failure has occurred. I feel the Ring zwave extender was worth the $26 on Amazon.
Is it normal for the battery to charge at a snails pace? It has been an hour and still at 1%. Or does it only report in like 25% increments?
EDIT: It says it's charging so I guess I'll give it a few hours and see.
I believe when it first was plugged in, it showed battery status of 35% but did take quite a long time to reach 100%. I also noticed when testing my rule for reporting a power failure and hub shutdown that for the few minutes it was unplugged the battery drained 1% but quickly recharged to 100%
Was wondering, did you ever open the back and look at the battery? Wondering if it's replaceable and its size
@tony3286 Thanks it seems to be moving now and reporting better. It does not seem to be repeating yet. I am going to do another zwave repair and give it a while to see how it goes.
It is removable, here you go.
1 Like
I've found this device to charge extremely slowly but also to discharge fairly slowly. I believe I had mine sitting a couple of days unplugged before it ever read less than 100% and then went very slowly from there.
On include if it doesn't ask for battery life I can change that so that it does. I have a feeling it did ask though and your device had just been completely discharged especially now that you see it charging from 1%.
*edit: I checked and I wasn't requesting battery level on configure. I am now. When a device is updated it will call configure. When the device installs it calls updated. Once I push the new code to the repo the device should report battery level immediately on include and every time after somebody hits configure.
2 Likes
@codahq, thanks for this driver! (And the HomeSeer dimmer & fan (and switch 
) drivers, too. I'm a fairly new HE user and they have been a great help in getting me started.)
I ordered one of these extenders and set it up yesterday. I switched to your driver and I am still getting the "not the correct device driver" warning when I press the refresh tile on the device page. It seems to be working correctly otherwise.
If I'm reading your driver code correctly, it appears that some of the identification parameters are different. Here are my device details:
- deviceType: 1025
- inClusters: 0x5E,0x85,0x59,0x55,0x86,0x72,0x5A,0x73,0x9F,0x80,0x71,0x6C,0x70,0x7A
- manufacturerName: Ring
- deviceId: 513
- firmware: 3.4
- MSR: 0346-0401-0201
- manufacturer: 838
The device signature being different would explain why it didn't pick the correct driver for you. The only reason it would tell you it wasn't the correct device is if the device talked to the hub in a way the driver didn't understand. Would you mind turning on all of the logging (description, debug and trace) and taking a peek to see what type of message isn't handled and what happened right before (and potentially after)?
1 Like
Certainly. Like I said, the driver seems to work fine except for that. I have already set up a rule that notifies me on power loss and restoration, and that rule triggers without an issue in my testing.
The easiest way to get the error is to press the 'Refresh' tile on the device page, and that appears to be a sure-fire way to get it. Beyond that, I have only seen it in the log one other time, and that didn't have any 'outside' events that appeared to cause it, just some sort of reporting it was doing. Here's the error from the Refresh. I'll leave the detailed logs running for now to see if I get the reporting error again.
Weird, I haven't ever seen that before.
That's an undocumented event in the most current Z-Wave certified extender. There are two Ring extender firmwares listed on Z-Wave Alliance's site and neither has mention of event 254 for notification type 8.
I've never seen that fingerprint or firmware either. If you can figure out what event that is or what it means it would be great. Then I can handle the event in the driver.
There must be something different with your hardware as well. I have a few extenders, some connected to Ring's base station, and they've never been updated beyond 2.4 firmware version. That leads me to believe they are different devices physically. I wonder what they changed in your device aka 0346-0401-0201 instead of 0346-0401-0101
1 Like
254 is literally unknown.. It probably at that point didn't have information stored for power management..
From the z-wave spec: "Unknown event/state" 0xFE (254)
Funky firmware glitch?
Just received my Ring z wave the other day from Amazon, as you know, and mine also 0346-0401-0101 and firmware 1.70 with no issues
- deviceType: 1025
- inClusters: 0x5E,0x85,0x59,0x55,0x86,0x72,0x5A,0x73,0x98,0x9F,0x6C,0x71,0x70,0x80,0x7A
- manufacturerName: Ring
- deviceId: 257
- firmware: 1.70
- MSR: 0346-0401-0101
- manufacturer: 838
Could be. I captured it with a warning for now so that the driver doesn't tell the user it is the wrong driver. I also added a new fingerprint for the 201 device.
If you join that device to a Ring hub it will update to 2.4 I think. My guess is they didn't fix much though. If you look at their new firmwares they've just added parameters to fine tune routing (Supervision Command Class). They may have started doing that. I can't see any functional difference between 1.5, 1.7 and 2.4 on device 101.
2 Likes
@JB_TX Where did you buy yours from? It sounds like a different source other than Amazon and they potentially have new/different stock than everybody else.
@codahq It looks like I got the same batch as @JB_TX.
I did get it from Amazon just this week.
Slightly newer model maybe?
EDIT: Is that why mine came in as "device", and I had to assign the driver manually.
Yes, that should be fixed now though.
2 Likes
Mine came from Amazon this week, as well. I’ll look at the box later and see if it has any sort of new/improved markings, dates, firmware printed on the box, or anything like it.
ETA: Nothing obvious on the box, just the device serial# and the S2 DSK. Doesn't look like much, if anything, on the unit either. It does have a SKU# of 4AR1S70EN0.
I went back and reviewed my logs, though they have rolled since I installed the device.
The two errors in my log both happened about 1 second on either side (1 before, 1 after) of a battery report, with no other information in the log. (And I did nothing to knowingly cause the report in these two cases.)
I will keep the detailed logging enabled and hope it happens again, but I think this lends some credence to the 'funky firmware' theory.
