If that doesn’t work post here and I’ll dig in tomorrow. Unfortunately the person who wrote this app stopped using hubitat so no one here is an expert in the code!
1 Like
Before re-installing everything, have you tried looking at the applets that are working and check in the URL you pasted in there has the access_token? It should if they are working properly. An dit should be the exact same URL for all of your applets as the only things that really change are the "kind", "motion"=true/false and the "Id"
The other next step could be to 'refresh' the oauth token here:
Just pay attention to that warning, you'll need to re-setup all your IFTTT applets to the new URL+token.
I do try those two things first before I do a full reinstall if the rest is working for you.
1 Like
Thanks! I had already uninstalled before I saw your post. So I uninstalled and reinstallled. Made sure that OAuth was enabled and then started the app.
Logged into Ring, re-discovered my devices, and then went to the IFTTT setup page in the app and the URL still shows up w/the "null" ending and tells me if the link isn't right to enable OAuth.
However, what is really bizarre is that I went back to look at all of my IFTTT applets that I had created before I uninstalled, and all of the applets except the door bell applet had valid normal looking tokens. So I don't get that at all...how all of them but the dining room would have the same token. No idea how I could have done that.
I tried to refresh the client secret in OAuth in the app code section, but that didn't help. Where is the "toggle" for the OAuth option you are showing above?
The toggle is behind the IFTTT page
Step 1:
Screenshot ..........
..........
Step 2:
Screenshot ..........
..........
If you aren't seeing it, I wonder if you somehow disabled OAUTH on the app itself, or didn't allow it again post install.
Go to App Code -> Locate the main Unofficial Ring Connect groovy app, open it and click the OAuth button to grant the app OAuth access.
Screenshot ..........
..........
Hope this helps. Headed to bed as well.
Ack, so most likely just using the URL for the Doorbell ring would have worked for you.
So now that you re-installed you'll need to get back into that state.
I'd suggest making sure the app code has Oauth access, I'd go into the app and make sure you are signed into Ring.
I'd then reboot the HE device, check and if it's still not there, sign back into Ring again.
I recall I hit the "null" issue as well, and it was something weird about timing and when the app authenticated.
So the original thread talks about this.
Someone hit it here:
And a few replies below they talk about where they manually pulled the token from:
I just checked on mine and in the app gear I can see my token there. It's the second shorter one:
1 Like
And it's working!!
@SoundersDude, I saw your replies earlier briefly but my wife had pulled me into some "urgent" late evening "Move this furniture over here, and move that over there" activities for a while. As soon as I was free I I went back into the IFTTT section to check for the OAuth reset, and loe and behold, my access token looked normal! So maybe the OAuth reset I did the Apps code section for the app earlier tonight took some time to filter to the Ring Connect app? Whatever the reason at some point the app found the right info and had a good token.
So I updated all the IFTTT applets, reconnected the Ring devices into my Motion Lighting app in HE, and it worked. 
Thanks very much for all the help, really appreciate the info and advice and support you and @dman2306 provided.
1 Like
What you have is awesome!! I appreciate it!
One thing I noticed: I don't seem to see any "status" for my First Alert CO/Smoke detectors hooked up to my Ring system. Do you know if these are able to "trigger" events and, if so, what value(s) are set?
Thanks!
I've gotten this successfully installed, but I seem to be having difficulty figuring out how to set up a Rule for "Ring Armed". I'd like to have my garage door go down and the doors lock when I arm the system. There is nothing Ring related in the Trigger Events.
What am I missing?
You'll need to trigger on the custom attribute "mode" associated with the alarm hub.
off
home
away
Off being disarmed, home being armed home, away being home-away.
Trigger action
"Custom Attribute"
click on the radio button for your alarm hub
click on attribute
select mode
then--chose your desired comparisons and values.
1 Like
Thank you! Worked like a charm! I love me some Hubitat!
Glad I read this thread. In the process of setting up a hubitat, initially for outdoor motion lighting and intrusion alerts but thinking about smoke /co also. If the Zcombo smoke/co doesnt interconnect it won't meet most local codes, except as a purely additional device. It had occurred to me that the interconnect wire on a hard wired smoke should provide an ac hot rail to turn the others on and could be used with ac detection to get notification in hubitat. the relay module (either BRK or KIDDE) is a simple inexpensive solution. I have plenty of ecolink door sensors that have the external connection to be set up with one. I also have some Wyze cameras which have the smoke audio detection built in which would require an IFTTT push.
Zooz has a multirelay that works with the BRK/Kidde relay module (it actually does many other things).
Interesting device, as you say many uses. Always good to know about special devices to have in the arsenal. I just got the Zooz v2 outdoor motion but yet to install.
Upon request of @bfara83, I've merged a large piece of code that was being worked on previously to add support for snapshots.
See: Add Snapshots Code by ardichoke · Pull Request #4 · ardichoke/hubitat_ring_integration · GitHub
Will be bumping the HPM version number later tonight most likely.
2 Likes
I just tried to install the re-release package via Package Manager and I received the following error:
" Error Occurred During Installation
An error occurred while installing the package: Failed to install app https://raw.githubusercontent.com/ardichoke/hubitat_ring_integration/master/src/apps/unofficial-ring-connect.groovy. Please notify the package developer.."
I tried with just the Virtual API driver by itself and again with a camera but but gave me the same error.
Package Manager is pretty straightforward so I assume I'm making a noob mistake?
What are "snapshots" in this context? Thx!
Im having the same issue, no matter what sensors I try to add. Im not sure if its something Im doing wrong, but there isnt much to do wrong once Package manager is up and running 
After getting the same error in HPM, I tried to manually import the main app and got the following error:
unexpected token: === @ line 876, column 1.
Yeah, sorry about that, I missed some merge conflicts. Should be fixed now.
