Edge Driver for Ring Alarm Range Extender 2nd Gen

Anyone know if there is an edge driver available for the Ring Zwave Range Extender (2nd Gen)?

As this device has a built in battery, it can be used to trigger power outage notifications.


My Ring devices (cameras, doorbells) are all integrated via the Cloud->Cloud integration without drivers. That may be the same with this device as well. Try linking your Ring account to ST by adding a device by brand name and see if it shows up as an available device.

Actually, I don’t have a Ring account, just trying to use this device as a Zwave device to strengthen Zwave network and enable power outage detection.

1 Like

Doesn’t look like the Ring range extender is included in the default driver.

Might want to check with @Mariano_Colmenarejo to see if any of his drivers could support it.

This stock beta driver only has the refesh capability and has no code.

Any device that has this generic fingerprint should be able to work with it.

   -id: "GenericRemote"
     deviceLabel: Z-Wave Remote
     genericType: 0x01
     deviceProfileName: range-extender
1 Like

Would be great if someone wrote a driver so that we could then setup an automation something like this:

1 Like

Not sure what you mean by “could support it.”

The device does work as a range extender. What I am trying to achieve is to get its battery status.
Once that’s possible an automation can be triggered on the condition when the device switches to battery power > notify about a power outage.

Hi @ukiews

What I mean is that the Z-Wave Range Extender driver can’t do what it wants because the profile only has the refresh capability and they don’t have any code and therefore it can’t do what it needs.

For what you want to work, you would have to add a profile with powerSource capability as a minimum, create a subdriver for this device and the code to handle the powerSource capability, since the default zwave libraries do not have a default handler for powerSource

How have folks gotten this onto an edge driver? If so, how? I’ve downloaded the ST beta z-wave range extender driver, and Mariano’s z-wave thing and z-wave device config, but it still keeps picking up a groovy DTH.

If you were using a custom Device Handler you will need to remove that first.

Thanks. Yes, not the case.

My experience with devices picking up DTH drivers when an Edge driver is installed is that the fingerprint hasn’t registered properly and is often all zeroes. This seems to happen for a few reasons:

  • the device gets into a strange state where it refuses to properly register. Factory reset generally solves that.

  • a device supports S2 security but was set up without security

  • fingerprint doesn’t match what’s in the driver

Use the CLI or the API Browser+ tools to check the fingerprint when the device is installed with the DTH driver.

The fingerprint doesn’t match any in the stock prod drivers. It’s just a range extender though, so I figured it would be picked up as a thing or some generic driver.

That will probably happen once Groovy is completely disabled. Right now, the default seems to be to fall back to a more specific DTH driver over a generic Edge driver.

1 Like

The range extender is a zwave device which is intended for the ring security system. Those aren’t available through the cloud to cloud integration, and as the OP noted, some community members use them paired directly to a smartthings hub.

This device is interesting because it’s one of the only range extenders available which normally operates on Mains power, but which will switch to a built-in battery if the power goes out. That allows your battery-powered security sensors to keep communicating to the hub as long as your hub also has backup power.

So while as you know from other conversations, I normally don’t like zwave range extenders for anything past third generation Z wave (and we are way past that now.) you can get the same functionality at better value with a dual purpose device like a smart plug.

But this particular one is an exception because of its ability to switch to battery power. It won’t run for longer than 24 hours or so on battery, but it’s useful in security set ups. :sunglasses:


As I understand it, during this transition phase it won’t be paired as a thing with a zwave edge driver until there are no available groovy DTHs that it can pair with. And since you can’t delete the stock Groovy DTHs, your best bet is to get someone to add its fingerprint to a custom edge driver. That said, it seems like quite a few people would like the ability to know when this particular device switches from power to battery or back again so they can run routines off of that. And may require a unique edge driver since other single purpose extenders mostly don’t have that capability. :thinking:

1 Like

I have one of these and can confirm it still pairs with a generic Z-Wave Device DTH.

It’s fingerprint if anyone would like to add it to an existing Z-Wave Edge driver is:

zw:L type:0F01 mfr:0346 prod:0401 model:0202 ver:3.05 zwv:6.04 lib:03 cc:5E,85,59,55,86,72,5A,73,9F,80,71,6C,70,7A

1 Like

Ditto, this is the last device I have using a DTH instead of edge driver.

Does anyone know if this can be done still with the new system? as you can’t input custom DTH’s anymore.