I’m new to this, but I’m having the same issue using the Ring Alarm Outdoor Contact Sensor with Milan’s driver. Note - this is the large brown outdoor sensor, not the small white gen 2 indoor window/door sensor. The indoor gen 2 sensor works flawlessly with Milan’s driver.
When I select the device in the app, it states “This device hasn’t updated all of its status information yet. Check again later.” It also doesn’t seem to work as reliably or with as much range as the white gen 2 indoor window/door sensor. I have tried switching back and forth between the standard Smartthings Z-Wave Sensor driver and Milan’s driver, but this didn’t change how it works. I also tried deleting and re-pairing the device to the hub, but this also didn’t change how it works.
Is there a separate driver for the Ring Alarm Outdoor Contact Sensors? They’re different devices and seem to have additional sensors (at least additional sensors such as motion, smoke, water, etc.) appear in the app (like shown in the screenshots above). My guess is that there needs to be a different driver for the outdoor contact sensors - does that sound right?
This is not uncommon for “sleepy” devices–most battery operated sensors are in this category–which only “wake up” periodically and report things to the hub, often only battery level. You could try opening/closing whatever the contact sensor is mounted on, but you still may have to wait for a periodic update. (I’ve seen it take several wakeups before tamper status was reported correctly on one of my door sensors.)
How long have you waited without making any driver changes?
I’ve been fiddling with this for the last two days, so it’s been about 48 hours without any driver changes (the “This device hasn’t updated all of tis status information yet”) warning has been present the entire time.
This behavior is distinct from my experience using Milan’s drive with the white gen 2 indoor window/door contact sensors, which works perfectly and doesn’t have the “This device hasn’t updated” warnings. The white gen 2 contact sensors are also a lot more responsive and work at a greater range than I’m experiencing with the brown Ring Alarm Outdoor Contact Sensor (which is why I was thinking that a different driver may be needed).
With the white gen 2 indoor contact sensors, the only fields in the app are contact sensor, tamper alert, and battery. WIth the brown outdoor contact sensors, the app shows many more fields. In addition to contact sensor, tamper alert, and battery, it also has motion sensor, smoke detector, water sensor, atmospheric pressure, weight, illuminance, temperature and humidity, voltage, energy consumption, and power meter. This is also why I was wondering if a different driver was needed for the outdoor contact sensors.
Hopefully, this info makes sense. Again, I’m new to this so I’m still figuring things out.
The stock Z-Wave Sensor driver was made for all types of Z-Wave Sensors. When a devices pairs using an included fingerprint it spells out what capabilities the device has. So after it pair the resulting entry in the mobile app works.
When a device pairs using a generic fingerprint the system doesn’t always know what it is. This sounds like your problem.
You need to get someone like @milandjurovic71 to add your fingerprints to there driver and it might work for you.
Go into the Advanced Web App Samsung account and get the fingerprints (Mfg. Code & Model) and post them here.
I checked the device summary on the Advanced Web App and found the following information for the Ring Alarm Outdoor Contact Sensor:
Mfg. Code - 0346-0C01-0301
Model - 0C01-0301
Does this look like the correct information?
It sounds like this is the same issue that Andrew M. (TheGrizzlyWizard) has been having. I’ll try sending a message to Milan.
I am also having the issue with the Ring gen2 contact sensor showing all the unused additional fields (motion sensor, smoke detector, water sensor, atmospheric pressure, etc). The contact sensor, tamper sensor and battery do seem to be correct. This happens with both the normal and “test” versions of Milan’s drivers. I’m thinking there might be a new device/manufacturer ID in the newer sensors.
The ID for the sensors in the 6 pack I just picked up from Amazon are 0346-0201-0601. Can this be added to Milan’s drivers?
Can you try to reinstall device again. I just updated drivers
───────────────────────────────────────────────────
Driver Id 1516dc8e-b6bc-4039-adb3-50af08bc067c
Name Z-Wave Ring Sensor
Package Key zwave-sensor
Version 2024-05-04T15:43:38.525920712
───────────────────────────────────────────────────
Just added, please wait some time for driver to update.
Driver info:
───────────────────────────────────────────────────
Driver Id 1516dc8e-b6bc-4039-adb3-50af08bc067c
Name Z-Wave Ring Sensor
Package Key zwave-sensor
Version 2024-06-28T13:12:34.753052322
───────────────────────────────────────────────────
We can try Gen 1 too, It should work. Please provide fingerprints.
Just this second updated them all, all reporting perfectly
I had delivered today a Ring v1 motion sensor, this also appears to work with your driver, reporting tamper, motion and battery correctly. Plus other fields.
The sig for this is 0346-0301-0202 , if you can add that I’ll let you know if it has removed the extra fields.
For anyone interested in adding these, scan the QR code, it will take you to the extra step screen, you need to activate the tamper switch a couple of times and it should add it fine with these drivers.
Thanks again for this
Edit:
Doesn’t seem to be reporting motion very often, tamper works instantly, wondering if this is just a poor quality sensor or a driver issue.
