thanks for the prompt.. just noticed there is something wrong with the driver in this f/w version as all my ring extenders say on battery and they are not i will report it.
1 Like
Ring extender v1 working as it should here with 2.3.1.135 firmware. Will update and see if .140 will break it!
used the custom ring extender driver from now that HAS option to create child reporting device and changed to that for now till the problem can be sorted out..
here is the new rule.. other rule stays the same.
Updated to latest Hub Firmware (2.3.1.140) V1 still reporting correctly
I'm not sure I understand which part is doing the polling. Also, is this only on restart of the of Hubitat or is it always running after Hubitat starts? I set something up similar to the first rule which after Systemstart it refreshes the extender every 10 minutes.
No polling is necessary. There are two unrelated issues.
The first issue is that refresh is broken in the built-in Ring Extender v2 driver. The fix for this is to switch to Denny Page’s (@dennypage’s) driver.
The second issue is that, when a power fail occurs and the hub shuts down, and then later reboots when power returns, the Ring Extender switches from battery to mains before the hub has rebooted, causing the “switch to mains” event to be missed (discarded), so the Ring Extender’s power source state in the driver still indicates that power source is “battery”. The fix for this is to have a Rule triggered on the systemStart location event, and have an action in that rule do a refresh on the Ring Extender. No polling is needed, just that single refresh when the hub boots.
1 Like
I'm already using the Dennypage driver and still it doesn't refresh. My hub isn't losing power, its on a UPS and my home has a whole home battery backup. I have two rooms that aren't tied into this so I'm just trying to determine when I've lost grid power and failed to battery since its seemless and I never notice. I then will have routines run to turn off non-critical stuff around the house to preserve power when I don't have solar recharging the batteries.
Ok, let’s test methodically. Open the device page for the Ring Extender. Pull the Ring Extender out of the wall socket. Does the powerSource change to battery? Then, put the Ring Extender back into the socket. Does the powerSource change to mains?
The only way to test refresh is to open the device page for the Ring Extender, remove the Ring Extender from the wall socket (observe powerSource change to battery), power your hub down (safely, from Settings, Shutdown), put the Ring Extender back into the wall socket (so the hub misses the switch to mains event), power up your hub, allow it to boot, open up the device page for the Ring Extender, observe that the powerSource is battery (because the change to mains event was missed), hit refresh, observe powerSource change to mains. This assumes that you don’t have any systemStart routine that refreshes the Ring Extender.
First of all, very clever use case. Secondly:
Are you saying that if you simulate a power outage by unplugging your Ring Extender (simulating loss of power in one of your non-UPS’d rooms, then plug it back in, that your Ring Extender keeps reporting “power source battery” and does not report “power source mains” (assuming of course that your Hub remains powered all during the test)?
What firmware version are you on (both hub and device)? I am curious as I am on 2.3.1.130 and 1.2.1 and my RE seems to change power source state back and forth virtually instantaneously on my device page without any refresh necessary. I only need to send a refresh when my hub restarts as per @672southmain.
As I was typing this, @672southmain already beat me to it, lol!!! Follow his instructions (and make sure you are actually using Dennypage’s driver as someone in a previous post mistakenly thought they were using his driver when they were actually using the built-in driver).
1 Like
I'm definitely on the proper driver because it shows the Power Test and Range Test options which aren't on the base driver. I installed it through Hubitat Package Manager and then changed to that driver. My hub is on 2.3.1.141 after the update I installed yesterday.
For testing I just have the Ring Externder V2 plugged into a surge protector that I'm power cycling to simulate power loss till I get it configured. At that point it will be in a room that is not on battery backup of any type. When I turn off the power to it the device page does not change to "battery" unless I hit Refresh on the device commands page. The same happens if I Refresh it to "battery" and then plug it back in. It will not change to "mains" until I do Refresh on the commands page of the device.
This was the same result when I did the test that 672southmain recommended.
I wish that it showed that I click the Refresh command to get these results but this is what I got. Can I just create a rule to check the device every 5-10 minutes?
While you could as a work around, I think there is obviously some other issue going on as you should not have to if everything is working as designed. The device should not have to be “polled” manually in this manner as it changes state based on an event (the switch to battery power or mains).
One other thing you can try that @thebearmay once helped me with in another topic: I was once getting some error messages when I had switched device drivers as one of the characteristics from the old driver stayed “linked” to the device. In your specific case, it may be that the built-in driver with its characteristic of not having the ability to automatically refresh is getting in the way of the Dennypage driver? I was able to fix this by switching my device driver to “device” (without hitting configure), saving then closing the device, then switching the driver from “device” to my new driver (in your case, back to Ring Alarm Range Extender gen2). Then hit configure. I am certainly no expert in this but this worked for me (@thebearmay has bailed me out many times) and it could not hurt to give it a try.
Also check your device pairing via Z-wave (exclude then re-enroll). You can factory reset between exclusion and inclusion by holding a paper clip in the reset hole in the back of the device (the internal battery has to be charged to do this) and pressing for 10 seconds then releasing when the flashing green light stops). Also, I also saw somewhere that it has to be paired using S2. Good luck with this. I remember it being very frustrating for me to even get it to pair initially as the instructions to pair that were given in this community was very confusing with several convoluted steps. I found a link to the official Ring device manual that was very clear and simple (factory reset instructions and pairing in SmartStart and Classic modes) which seemed to help a lot (I was able to get it to pair the first time using these simple and clear instrutions). I will try to find the link and post for you. Hope these suggestions help.
Edit: here’s the link:
https://manuals.plus/ring/ring-alarm-range-extender-2nd-generation-manual
Perhaps it’s a bad pairing. I would suggest that you exclude it, do a factory reset, re-include.
I assume that you have a Ring Extender v2, not the v1. Right?
I followed the directions from the manual and excluded, factory reset, and then added the device back. It re-added back as Ring Alarm Range Extender gen2. I conducted the test again and received the same result that it doesn't update without the refresh. Does everyone have their "Heartbeat interval in minutes" set to the default 70 minutes? I tried changing this also but didn't help.
Well, then, I’m baffled.
I've just pushed an update (1.3.0) that addresses this in the driver itself, which makes the Rule unnecessary.
2 Likes
Hi @Nitr0 ,
Sorry to hear nothing has helped. Perhaps try eliminating your current driver and try to reload with @dennypage’s updated driver (1.3.0) and just start from scratch again. I am at a loss as mine is working without a hitch. Then exclude and re-include your device. Let us know if you get any resolution with the new driver.
I just updated the driver. Do I need to exclude, factory reset, and include again? Tried to just update the driver and disable my refresh rule but same result as before.
nice change.. i made a slight edit as i think running in 1 sec after restart may be too soon..i changed mine to 20 sec.
thanks.. except other stuff is done for me as well like restarting the various thermostats that requirement periodic polling etc.
You do not need to exclude/re-include.
One thing that does come to mind... if you are using the device page to follow transitions, make sure to refresh the page in the browser whenever you reboot the hub.
I would recommend enabling debug logging in the driver and monitoring the log. If you would like me to take a look, please do the following:
- start with the ring on mains
- enable debug logging in device preferences and save
- run refresh on the device page
- wait 30 seconds
- run configure on the device page
- wait 30 seconds
- run refresh on the device page
- wait 30 seconds
- unplug the ring
- wait 30 seconds
- run refresh on the device page
- wait 30 seconds
- plug the ring back in
- wait 30 seconds
- run refresh on the device page
And send me the log entries.
