The 2nd gen Ring devices are going to want to smart include by default which HE does not support at this time. If you look at the top in the comments of my driver that @SoundersDudelinked there are very brief instructions to include the 2nd gen extender.
To get the 2nd gen device to start classic inclusion you have to exclude it (if you've played with it at all it requires a fresh exclude). Do that by unplugging it, putting the hub in exclusion mode and pressing the pinhole button on the back of the extender. Once it is excluded successfully you plug it in. You should see it immediately start to blink the LED green. This means it went into smart inclusion. To steer it to classic inclusion you hold the front button down for about 3 seconds. It will pair after that.
I started with this driver and it paired but only as "device" (I tried a dozen times)
Following Soundersdudes advice, I used this driver and it paired right.
I needed the "switch" feature though to make my dashboard view the way I preferred, so I switched back to the first driver by bcopeland and then it worked. Strange, but it worked.
Thanks to the developers here for their hard work. I had a cobbled solution for a power failure before this (using a power failure sensor combined with a water leak detector), but this is an elegant solution now. Very pleased
That doesn't make any sense to me. That's easy to do without adding use-case specific clutter to the driver. You can monitor an attribute in rule machine and toggle a virtual switch. To each his own I guess.
When I used the Ring Range Extender without the switch function, in my dashboard I couldn't figure out a way to change the tile color to red when the power was out, and have it green when the power was on. With bcopelands driver, I could do it by creating a tile using the switch attribute. If there was another way of doing the same thing, I couldn't figure it out- but this way works perfectly. I'm tickled pink to have this functionality
As previously mentioned you can create your own virtual switch using the OOB driver. Then you can create a rule in Rule Machine that drives the switch state based on the acStatus attribute. Then you can show the virtual switch on the dashboard as you have with the child switch device on @bcopeland's driver.
The second way is modify the dashboard's attribute template. From the dashboard click the cog settings then "Advanced". In the layout find:
And replace it with whatever you want. For example:
Hi guys, just got one of the green 2 extenders. Using @bcopeland driver. Device paired fine, grabbed Bryan's driver. However since it's paired I don't see anything in the device events, but do see errors in the log, and the button on the front doesn't do anything, like the led is totally off, even after pressing the front button. Is it possible the pairing affected the functionality?
My experience is that Bryan's driver doesn't setup associations reliably (device fault/quirk really, and not really a driver fault).
I tried 10+ times with Bryan's driver, but could only get it to fully communicate when using codahq's driver, and hitting configure repeatedly while waking the device by short pressing the pinhole button on the back.
coadahq and Bryan's driver do very different things in the configure section (namely codahq's tries to re-setup associations every time configure is hit, Bryan's does not), so I don't think that same trick works with Bryan's as currently written.
Is this on C5 or C7? the Gen2 was always a pain on the C5 it would stop reporting for no apparent reason. Most of Ring’s gen2 stuff if you can get it to pair without S2, it usually doesn’t last long. They work great on C7 if you include it with S2.