@dhanselnh - And I'd add that I also believe a difference is the Pro has an SLA for fast delivery time and 'free' is not guaranteed to be real-time. From my experience I've never seen a delay from IFTTT, but imagine that language helps protect them and scale to prioritize Pro events first.
Thanks guys, Good point about getting what I pay for (or not). So far, so good though.
OK I have a NEW ISSUE with RING and I'm looking for possible answers.
- today, a first alert Zwave Smoke/CO triggered and set off the RING alarm based (which it is paired with). I got a quick call from the monitoring service, just as I expect. It was a false alarm thankfully, but when I attempted reset/clear it in the RING app, the Siren and alarm state on the base station continued trigger. I would silence/clear it, and then in 10 secs or so, off it would go again. complete with push notifications, etc. I then went and pulled the batteries from the offending smoke sensor to ensure there was no way the RING system was getting additional triggers from that device.
- For some reason, the RING alarm continues to trigger. By now I've gotten more calls from the monitoring company and I take it out of "pro monitored mode" while I get on the phone with customer support. Customer support is completely scratching their head, and cannot figure out why the alarm is still being triggered. It appears to be coming from the app itself or something they can't discern. In the end, the only way to stop the alarm from re-triggering every 10-15 seconds is to completely reboot the RING alarm base.
- So, i'm thinking to myself "I wonder if something to do with my HE integration can be constantly triggering the Ring alarm?" I go to HSM and sure enough, it is still in an ALERTED state which is causing all my HE controlled lights to stay on. So, I cancel it within HE. With the RING Alarm reboot, my websocket is now disconnected too. Which means HE is no longer talking to RING.
I didn't say anything to RING about my HE integration because that would give them an excuse to toss their hands up and blame something they don't understand. However, I would like to hear from anyone in the group if we think there's any possibility that the HE integration caused this Trigger Loop after the offending Smoke sensor was out of the picture? The thing that raised my eyebrows was when RING CS said they couldn't figure where the additional alarm triggers were coming from? TIA for any and all thoughts. Hope this description somewhat makes sense.
Doug
HSM will continue to ALERT until it has been told not to.
So, I think that you have to make a disarm in HSM when you do that in Ring. In other words, you have to manually keep them in sync.
Big question I have is do you have any rules or settings with the integration where Hubitat is able to trigger your Ring Alarm?
That answer will help determine if it's at all possibly an issue with HE and your state v.s. Ring itself.
When is this happening? If there isn't a websoccet, it's not possible for this integration to trigger your Ring.
Also, logs are our friend here to see if this integration is sending anything to your Ring.
You might want to enable this second setting that disarms your HSM when Ring Alarm is Disarmed.
Thanks SoundersDude,
I have no rules or settings where HE is able to trigger the RING system. Certainly not to my knowledge anyway.
I had both 'Sync Ring Alarm to HSM' and 'Cancel HSM alerts on Ring Disarm' enabled in my setup. I've now turned on logs to be able to investigate future issues.
I don't believe my HE Ring Integration could have caused this continuous Ring Alarm loop that I found myself in, but since Ring can't figure it out, I thought I would toss this out there in case.
1 Like
Thanks jtmpush18,
I did have the option checked to keep them in sync and to disarm HSM when Ring is disarmed. Didn't seem to work during this event, but it normally is fine.
The plot thickens:
Here's a followup I received from RING:
One of the session that was toggling the siren (and which was the first to do so at 12:20:45 (EDT) had been logged in as the owner's user id since 10:25:44 this morning using an android user agent with a version of 3.25 and no hardware id. IP address was same as where the base station is from (so from within the home) .
We have no 'physical' android devices in the house. Could the Android user agent be HE?
Probably, as if you still have this app connected it is reaching out to get the status of your alarm and devices, so that is very normal and expected.
What isn't expected is it triggering your alarm unless you set something else up.
While you are debugging with the Ring team I'd suggest disconnecting this integration (logout) so they don't flag it as the issue.
Thanks, yes, I am currently logged out of the integration while we look for clues.
UPDATE: OK, because I'm impatient, I logged back into the RING integration. When I did that, I got a standard message from RING about my log in:
Hi Doug,
Your Ring account was signed in to on a new device or browser. Here are the details:
• Device/App: Ring Official Android
• April 21, 2022 at 10:10 PM UTC †
• IP Address: 73.47.****
• Country: US
SOOOO, it seems like this could be the offending "Android device" that the Ring CS logs show repeatedly triggered the smoke alarm event even though it was repeatedly cleared in RING!? We simply don't have any other Android devices that are in play here.
I have no idea how to fix this if it happens again. But, I do have logging turned on just in case. So, if I get in some kind of constant alarm state, I will know to go and manually clear the event in HE since it's obviously not able to do it itself for a smoke event like this. Bug in the integration?
So I don't believe it is even possible for this integration to "trigger" smoke alarms, as all it can do is listen to their state from Ring.
From your response from Ring though, it seems they were talking about "toggling the siren" which is different than something triggering your smoke alarm or triggering Ring. Hope that makes sense.
From your comments, it sounds more likely that;
- Something caused a false alarm with Ring and your Smoke Detector
- This integration was toggling your Ring state each time you changed your HSM state since you had those options selected, and ring confirmed this was the device toggling the alarm.
Good news is you turned that sync off, and you will learn more now that you have logging on if this were to happen again.
Is anyone else running into an issue with adding new sensors to Ring Alarm on this integration? I'm on the latest beta update right now, seeing this on the logs:
Do we use the Create Devices on the Ring API Virtual Device or on the Ring Alarm Device? I tried on both but can't get this or any other sensor I added recently to add to this integration.
I added a smoke detector a few days ago without issues. I used the Ring Alarm device.
What version of the Ring Alarm do you have?
First generation. Do you have the 2nd generation one?
Yes I do have the 2nd Gen version. I already had to remove and readd the integration last week just to add 4 new contact sensors. I was hoping at that point maybe that the fix this issue for any new devices I wanted to add in the future. Adding new devices must be broke on the 2nd Gen Alarm.
Ah! Interesting… Probably related.
@morse.caleb I just tried adding my smoke/co listener using the latest HPM release version of the driver. The only states I'm getting are battery level and I see the following error in logs any recommendation?
EDIT Disregard
Any additional details you have would be fantastic.
e.g.
- How long did you wait after you added the devices to Ring, did you try adding to this integration
- Any errors, warnings, etc from logs if you turned those on when adding?
@kraig109 originally posted a while back a work-around found with the Gen2 Alarm
100% of them fail initially throwing the Null name error on line 748 (HPM version driver). Once I get the error, quickly edit the name in the Ring app and 100% of the time they join immediately without (so far) further issue.
It is not a fix, but it is a workflow that is working.
Workflow:
1 at a time If it fails, try the rename work around.Might save some headaches.
Would be great to know if that renaming trick solves it for you as well, as that could help narrow down the issue and if we can work around it.
