Ring Z-Wave Plus Door/Window Contact Sensor - does this work with HA?

Hardware
21

I also figured it might be helpful to add some sample code to make the template entity work:

template: 
    - binary_sensor: 
    - name: "Ring_sensor_1"
      device_class: door
      state: > 
        {{ not(is_state("binary_sensor.ring_contact_sensor_1", "off")) }}

In this way, I have a new binary.sensor and it shows as a door, and it is closed when the magnet is near the sensor. This can just be added to your configuration.yaml file, then restart home assistant and you should have access to the new binary sensor entity. Make sure to put the name of the original binary sensor in the {{ not(is… part

22

I am considering purchasing a new Ring system - no video, just for the alarm monitoring. I see this thread about directly integrating the z-wave sensors, but is the HA ring integration able to expose the contact sensors, motion detectors and other Ring components natively? Arming and disarming via HA would also be a plus.

I’d love to get a solid answer on this before I shell out $$$ on a system. My fall back is a Honeywell panel with wireless sensors. I know that would be bombproof but the sensor and panel setup is just not fun at all as I’ve done it before. Having a slick iOS app to do the setup would be a plus. Just not sure if the tradeoff to have cloud versus local control is worth it. Plus I’m scared that Ring could pull the plug on the HA integration at some point.

Any suggestions/info on the above?

Thanks!

23

I was testing different Z wave sensors to use with the Alarmo panel to make a security sensor until yesterday. I ordered Fibaro, Aeotec, Aeon, Zooz, and Ring sensors. All worked great with Fibaro losing too much battery plus expensive (40$ a piece), Aeotec is pretty expensive but worked great. Zoon is cheap and good but it has only one 2032 battery so not sure how long it will last. I read some articles where people had luck with ring sensors so I purchased one for $20 from BestBuy and tried. Worked like charm. But binary sensor shows Safe and Unsafe so I configured it to be a window sensor in my case and restarted HASS. Now it showed up as Window with Open and Close. The biggest plus is the price of the Ring sensor. Gen 2 contact sensor 6 pack retails at 99 so about 16$ a piece and you can’t get any cheap sensor for that price and also comes with 2 CR2032 batteries. Ring says it will last about 3 years. I would be happy with a little over a year. I did not buy a Ring base, just the Ring sensors and Z wave stick(Aeotec gen 5+) on HASS OS on Raspberry PI 3B+. Works great, I wish I knew before I invested in all these sensors.

24

I was able to pair my sensor in ZWave JS using the steps above and it seems to be reporting safe/unsafe correctly. One question. When I look at the sensor on the ZWave JS dashboard, the security shows with a red circle with a dash for Security, is that expected? I was thinking these would connect with security as they are S2.

-Josh

25

I was also able to use the Ring G2 sensors. Grateful for the pairing tips above using the reset button. It’s probably obvious to most people here, but I will say it….to trigger an automation when the sensor is activated (door opened), you need to use the following under device trigger
“Patio Door Sensor: Home Security - Intrusion became unsafe”
Where Patio Door Sensor is the name I gave the device.

26

Youll need Samba Share activated to do this:
BACK UP FIRST
Navigate to \homeassistant\config.storage
You want to edit the core.entity_registry file
Search for the word “safety”
Change that device class to window or door. Depending on what you are using it for
Look for the string that contains the “Home Security - Intrusion”
it will look like this:
```{
“area_id”: null,
“capabilities”: null,
“config_entry_id”: “65135a145a10c203fc60af6b05da0ed1”,
“device_class”: “safety”,<-----Change this entry to “door” or "window"
“device_id”: “e327eba557771e251b8561b75b30dc16”,
“disabled_by”: null,
“entity_category”: null,
“entity_id”: “binary_sensor.YOUR SENSOR HERE”,
“icon”: null,
“id”: “6567a6981a389b65d1981d857670a656”,
“name”: “YOUR SENSOR NAME HERE”,
“options”: {},
“original_device_class”: “safety”,
“original_icon”: null,
“original_name”: “Contact Sensor Gen2: Home Security - Intrusion”,
“platform”: “zwave_js”,
“supported_features”: 0,
“unique_id”: “3444345620.64-113-0-Home Security-Sensor status.2”,
“unit_of_measurement”: null
},`
Save the restart after checking the config

2 Likes
27

Can anyone that has these (2nd gen) working reliably verify what security method they’re using?

I have about 4 of them and they paired using the S2 QR code, though it did take a few iterations of exclude/including them. But once they were fully added, they started acting more like tripwires - they’ll switch to insecure almost immediate and then won’t go back to secure (for at least some time). I’ve tried switching them to be door entities and have the same results. Next step was going to be trying with no security, but I didn’t have much luck getting one re-paired last night. Thanks

28

I tried adding one recently and didn’t have any luck adding it securely. Added it as non-secure and it works the way one would expect.

29

Interesting - I can add and remove them with the QR codewithout much fuss, but then they’re just laggy and unresponsive. I ran out of time to test insecure mode last night. For the record, I’m using a zooz 700 stick (and zwavejs).

Also of interest, I was looking into alternatives, and users of the Aeotec 700-series contact sensors are reporting the same issues I’m seeing when they securely pair them to Smartthings - major lag and/or never updating.

30

I have over a dozen of these working properly. This is how I get them to pair:

  • Factory reset by holding down button in small hole on back until it flashes red.
  • Start pairing in home assistant
  • Hold down main button for 5 seconds until it starts flashing faster
  • When pairing starts, it will hang up and flash red sometimes. Press reset button on back for a few seconds (don’t go past 9 seconds). Do this a couple times and it should pair properly
    Sometimes they wont operate. Do a re-interview. This usually fixes them.
    A couple posts up I go over how to get them to show as door/windows instead of safe/unsafe. Im not sure if the new UI options make that method obsolete though.
2 Likes
31

Rich, are you doing a secure or insecure pairing? And when you say sometimes they don’t operate, do you mean right after the pairing process, or do you mean that you have problems with them needing to be re-interviewed even after being installed for a while?

I take it from your second bullet point that you’re doing this from the HA interface - I’ve been working inside the zwavejs interface, so maybe that will make a difference.

I’m also wondering if there might be a few firmware versions out there like we encountered in the Ring Keypad thread because when I was following Roborobp’s instructions, step 5 got no reaction at all from the sensors. In fact, hitting the reset button after pairing pretty much leaves the sensors dead for me until doing a full reset. I do have another 6-pack that I haven’t opened yet, so I’ll try one of those and see if it behaves differently.

Thanks

32

I had the Gen 2 sensors setup flawlessly the first time, just with the reset on the back they went in to the triple blink then connected s2 auth, Just needed to put in that Pin# on the side and good to go.

Then I had to reset my Aeotec stick,{HA issue} and was unable to pair them no matter how many times I tried All my other Zwave items paired no issues. Rebuilt a New HA instance to try it to no avail.

****The way that worked with a little Hiccup was to take a picture of the Qr codes with my phone and crop them for HA and then used my phone to upload them in to the Queue for New items Via Z-Wave JS and then it would 90% of the time Create an unsecure Node and then while it’s still pairing i would press the Pin Button on the back and then it would then see “node 20 and being insecure then Zwave-JS would still be scanning and then it would re scan it and then make Node 21” after you would just remove the failed Nodes, and this has been after trying to many ways to get this to work .

But it looks like this has worked on All Nodes I put in tonight 6 Door Sensor re mounted and time for a Nap. lol
if you have HTTPS you can just scan them an not take a photo and upload them in. I wanted to make sure it worked before went back into HTTPS and bring it back online for remote access.

33

I know this thread is very old, but it is THE result on google. I am including my Ring Gen 1 sensors into my HA network and none of the instructions here or on Ring’s website helped. There is a (partly undocumented) reset button on the back of both the door and motion sensor. You have to hold down BOTH the reset and tamper buttons to get them to enter inclusion mode. It was still quite finnicky, but I managed through this.

34

The Gen 2 sensors now pair properly. You still need to reset them before pairing. There are about 30 entities to disable after pairing though.

35

Hey so I just got a ring door sensor to try. Been following this thread for a good while now and finally bit the bullet. (As an fyi this paired flawlessly once I reset it - Gen2)

So I have 2 questions-

  1. Has anyone successfully updated the firmware on the door sensors with z-wave.js in the home assistant integration?

    Screenshot_20230115-204344_Home Assistant
    Screenshot_20230115-204344_Home Assistant1440×3200 218 KB

  2. When I was cleaning up the extra entities that got added, I noticed one that said Software Problem. What does that refer to?

    Screenshot_20230115_204419
    Screenshot_20230115_2044191440×3045 383 KB

36

Hello all, once I’ve paired a Ring z-wave contact sensor G2 with the zwave-js integration is this sensor then still working with the Ring base itself or can a Sensor work only with one endpoint aka no multi pairing is possible?
I have not found any information so far here in the thread or on the web and maybe you can share your experience here. Thanks.

37

This; by design.
I suppose for security reasons.

38

You ever figure out why it says problem? The sensors work just fine, but yeah mine says that too.

39

Nope. I didn’t ever figure that out. Not sure. The sensors otherwise work fine. I just disabled that entity entirely

40

A few years passed now. Back in 2021 I indeed had gone through all 6 steps in order to properly include ring devices (contact sensor gen2 in my case), but now 2023/11, I verified step#4 (4. Press the pin hole button for 5 seconds.") onward can be skipped and yet HASS can interact with ring device (I actually verified with the same particular device that I factory-reset).

Z-Wave-js
Driver version: 12.3.0
Server version: 1.33.0