Well, I went outside for coffee, posted my post, came back in to try it again, and it was magically working now. Weird!
1 Like
Has anyone been able to get this to pair in S2 authenticated and then report open/close states? I can get mine paired S2 auth, but the device status never changes to reflect if it is open or closed. Just stays on closed. If I pair it with no S2 it pairs just fine and reports all state changes.
Yes...I installed 3 of the Ring alarm contact sensors V2 about a month ago, They all paired as S2 authenticated and they do report the correct states. What driver are you using? I am using Ring Alarm Contact Sensor G2.
The only suggestion I have is to click on Configure in devices and then click Save Preferences. Enable debug and see what the logs say.
Ok, so I excluded it and then paired it in S2 Class 1 Authenticated. I then went into the device and saved the preferences. I had the contacts open, then closed it. Logs show the close, but then when I open it, nothing. If I wait and then close it, it will show the close, but then not the next open.
Device is using the builtin "Ring Alarm Contact Sensor G2" driver.
Here is a snipit of the logs:
2021-01-08 09:20:56.032 pm infoRing Contact Sensor 1 contact became open
dev:412021-01-08 09:20:56.027 pm debugSupervision Get - SessionID: 5, CC: 113, Command: 5
dev:412021-01-08 09:20:56.021 pm debugparse:zw device: 19, command: 6C01, payload: 05 09 71 05 00 00 00 FF 07 02 00 , isMulticast: false
dev:412021-01-08 09:19:27.584 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:19:27.575 pm debugSupervision Get - SessionID: 4, CC: 113, Command: 5
dev:412021-01-08 09:19:27.570 pm debugparse:zw device: 19, command: 6C01, payload: 04 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:19:05.565 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:19:05.554 pm debugSupervision Get - SessionID: 3, CC: 113, Command: 5
dev:412021-01-08 09:19:05.548 pm debugparse:zw device: 19, command: 6C01, payload: 03 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:17:05.734 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:17:05.727 pm debugSupervision Get - SessionID: 2, CC: 113, Command: 5
dev:412021-01-08 09:17:05.722 pm debugparse:zw device: 19, command: 6C01, payload: 02 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:16:43.729 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:16:43.721 pm debugSupervision Get - SessionID: 1, CC: 113, Command: 5
dev:412021-01-08 09:16:43.715 pm debugparse:zw device: 19, command: 6C01, payload: 01 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:15:52.867 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:15:52.862 pm debugSupervision Get - SessionID: 63, CC: 113, Command: 5
dev:412021-01-08 09:15:52.856 pm debugparse:zw device: 19, command: 6C01, payload: 3F 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:15:31.504 pm infoRing Contact Sensor 1 contact became closed
dev:412021-01-08 09:15:31.499 pm debugSupervision Get - SessionID: 62, CC: 113, Command: 5
dev:412021-01-08 09:15:31.495 pm debugparse:zw device: 19, command: 6C01, payload: 3E 0A 71 05 00 00 00 FF 07 00 01 02 , isMulticast: false
dev:412021-01-08 09:15:17.400 pm warndescription logging is: true
dev:412021-01-08 09:15:17.397 pm warndebug logging is: true
dev:412021-01-08 09:15:17.395 pm infoupdated...
dev:412021-01-08 09:15:01.623 pm debugAssociation Report - Group: 1, Nodes: [01]
dev:412021-01-08 09:15:01.614 pm debugparse:zw device: 19, command: 8503, payload: 01 05 00 01 , isMulticast: false
dev:412021-01-08 09:15:01.251 pm debugparse:zw device: 19, command: 8406, payload: 00 A8 C0 01 , isMulticast: false
dev:412021-01-08 09:14:59.807 pm infoRing Alarm Contact Sensor G2 battery is 100%
dev:412021-01-08 09:14:59.803 pm debugparse:zw device: 19, command: 8003, payload: 64 00 00 , isMulticast: false
dev:412021-01-08 09:14:59.515 pm debugDevice Specific Report - DeviceIdType: 1, DeviceIdFormat: 0, Data: [71, 55, 81, 49, 68, 50, 48, 51, 48, 51, 56, 54, 48, 71, 69, 53]
dev:412021-01-08 09:14:59.510 pm debugparse:zw device: 19, command: 7207, payload: 01 10 47 37 51 31 44 32 30 33 30 33 38 36 30 47 45 35 , isMulticast: false
dev:412021-01-08 09:14:59.191 pm debugVersion Report - FirmwareVersion: 1.15, ProtocolVersion: 7.12, HardwareVersion: 1
dev:412021-01-08 09:14:59.187 pm debugparse:zw device: 19, command: 8612, payload: 03 07 0C 01 0F 01 00 , isMulticast: false
sys:12021-01-08 09:14:54.663 pm warnZ-Wave Inclusion timed out, status:7
sys:12021-01-08 09:14:54.650 pm infoZ-Wave Discovery Stopped
sys:12021-01-08 09:14:11.472 pm infoZ-Wave Discovery Running
I think it should actually be the opposite. I cannot get it working on to my C7 with S2 security. It connects with S2, but doesn't function properly at all. If I connect it to my C7 with no S2 security it works perfectly. With S2 it just sits in one state and maybe every 1-20+ open/closes, it will change the contact state.
I have 15 of these working perfectly with S2 authenticated.
1 Like
Then I am not sure what is going on here. Brand new hub sitting on my desk next to me. it connects with S2 auth, but doesn't update the state. I can open and close it many times and it just sees the first open and then never updates until I leave it for a few minutes. I have tried it many many times and with the same result. What firmware do your units have?
1.15 and 1.13
1.13 is running on my busiest door
Are you connecting them with S2 Class 1 - Authenticated only selected?
Yes.. Ring devices don't typically like it if you change any grants they request.. So just click ok..
I am and they do not work. I just opened a 2nd Ring Gen 2 contact sensor and paired it S2 C1 and it created the device like it should, but it is not seeing that open/closes happening.
Hang on.. Going to include a new one..
This is what I am seeing in the logs when i pair the new unit:
dev:472021-01-09 06:14:01.268 pm debugAssociation Report - Group: 1, Nodes: [01]
dev:472021-01-09 06:14:01.260 pm debugparse:zw device: 20, command: 8503, payload: 01 05 00 01 , isMulticast: false
dev:472021-01-09 06:14:00.892 pm debugparse:zw device: 20, command: 8406, payload: 00 A8 C0 01 , isMulticast: false
dev:472021-01-09 06:13:59.399 pm infoRing Alarm Contact Sensor G2 battery is 100%
dev:472021-01-09 06:13:59.394 pm debugparse:zw device: 20, command: 8003, payload: 64 00 00 , isMulticast: false
dev:472021-01-09 06:13:59.120 pm debugDevice Specific Report - DeviceIdType: 1, DeviceIdFormat: 0, Data: [71, 55, 81, 49, 68, 50, 48, 51, 48, 51, 48, 50, 48, 72, 52, 52]
dev:472021-01-09 06:13:59.115 pm debugparse:zw device: 20, command: 7207, payload: 01 10 47 37 51 31 44 32 30 33 30 33 30 32 30 48 34 34 , isMulticast: false
dev:472021-01-09 06:13:58.769 pm debugVersion Report - FirmwareVersion: 1.15, ProtocolVersion: 7.12, HardwareVersion: 1
dev:472021-01-09 06:13:58.763 pm debugparse:zw device: 20, command: 8612, payload: 03 07 0C 01 0F 01 00 , isMulticast: false
In case you are curious .. the one I just included shows to be firmware version 1.15
So I removed all devices from my C7 (zwave and hub mesh). I had a Honeywell T6 Pro thermostat and a Ring Range Extender paired directly to the C7 and 2 mesh devices. I then did a zwave repair and rebooted the hub.
Then I attempted the pairing of the 1st contact sensor using S2 Class 1. This device now works perfectly. Paired the 2nd sensor and this one works also. I then paired the Honeywell and the Range Extender back and the contact sensors work.
I wonder if the zwave mesh was messed up somehow?
Thanks for looking into this for me.
1 Like
I just went through this same fiasco. Mine was working fine for weeks and then both just stopped i had to reset and repair multiple times to get them to work again
Odd.. I have a ton and they have never given me any trouble
I think its a hub issue as both of mine went out at the same time and would not report. I did a repair zwave and reboot and that did nothing, factory reset one and paired and unpaired a bunch of times and just when I was about to give up I went to the back door took it off the mount and I noticed it flashed green. the back door started working again. I then paired the front door again and it started working again. I think it could be an issue with the tamper detection.
I really want these to work they worked for about a month with zero issue
they seem to be back working fine now time will tell
I have four of the Ring Contact Sensors V2 that I installed in early December. They all stopped responding about a week ago. At first, I thought I had bad batteries. After replacing all batteries, they started working again - for about a day. Then totally unresponsive again.
I was about to give up on them and then found this thread and read @bcopeland's comments about these sensors being very temperamental. So I gave it another shot. I rebooted the hub (a C7) and pulled the batteries on each sensor. They all started reporting again and that was about 3 days ago. They are all still working, but we'll see how long that lasts. I really have to wonder what it was that they didn't like. It seems like the hub reboot was key, at least for me, to getting them to respond again.
