[Re-release] Hubitat Ring Integration (Unofficial)

⚙️ Custom Apps and Drivers
1067

@rob9, fix for me was to refresh the Client Secret on OAuth in Apps Code for the Unofficial Ring Connect app.

image
image996×708 22.5 KB

I had the exact same issue when updating from the old code to the new code initially (I posted that a bit ago above on this thread).

This didn't seem to change the URLs at all if you use IFTTT/Alexa to do the Motion/Ring notifications from what I can tell.

1 Like
1068

OMG! You're a miracle worker!

That helped immensely! I think it's talking now!

2 Likes
1069

@bfara83 @rob9 I recently upgraded my hub from 2.3.0.X to 2.3.1.X and I am now able to reproduce the auth bug you were having. I released a new version that should fix the issue. I also reported this a Hubitat bug here: Since 2.3.1.X app semi-permanently modifies a '@Field static final Map' variable.

3 Likes
1070

So far that update seemed to of fixed it for me. I used to be able to replicate this issue when on 2.3.1 by removing the integration, reinstall it then log in again and would get that error but now it seems to work when I do this after this update you did.

1071

So i have been using hubitat ring intergration and worked well up to recently. IF the hub reboots It doesnt seem to be able to connect to Ring again. I saw you posted a fix. I just took your code and passed it replaceing the exsiting code. Still have the issue.
I then delete all the code and created fresh with your code. I can auth but it will not build any devices. Not sure what is going on. Any help would be appreciated

1072

I need to know what version you're running and any log messages from when this happened. Also, it sounds like you're still installing code manually. I would highly recommend using Hubitat Package Manager instead: [BETA] Hubitat Package Manager

1073

Quick Q for the Ring Integration crew.
Just need a reminder. There's no reason I need a 'pro' version of IFTTT for my basic ring integration setup is there? I was playing around with IFTTT in the beginning, but I'm not really doing anything with it (other than the Ring integration), so I'm hoping to drop the monthly payment now.
TIA,
Doug

1074

I think the IFTTT stuff is mostly needed for direct integration with motion & cameras.

For basic alarm and device (door sensor, fire/CO alarm, etc.) stuff, the app works by itself.

I've not done it--but I think others have indicated you can use Amazon/Alexa actions like "upon motion turn on light" (where "light" is a VIRTUAL light/switch in the HE that actually does what you want).

1 Like
1075

Thanks Rob9. I went ahead and cancelled my "pro" subscription with IFTTT. All it's doing currently is turning on my front porch lights when the Ring doorbell detects motion. (Front porch lights being controlled by HE of course) I'll assume it's going to keep working!

1076

Well, that might stop. Not sure how iFTTT works in the free mode (I think you can have a few things for free).

If that doesn't work, you can create a virtual or light in Hubitat--then tell Alexa about it and set up an Alexa rule to "turn on the light/push the button" when it detects motion.

1077

I think without a subscription you get 4 routines for free, so you should be good. I have way to many things going on, so I'm just staying put. lol

1 Like
1078

@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.

1079

Thanks guys, Good point about getting what I pay for (or not). So far, so good though.

1080

OK I have a NEW ISSUE with RING and I'm looking for possible answers.

  1. 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.
  1. 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.
  2. 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

1081

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.

1082

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.

image
image1339×439 37.3 KB

1083

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
1084

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.

1085

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?

1086

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.