How do we add this? Manually?
Safety & Security --> Cameras --> Ring? Is there another proper/better way?
I’M SO EXCITED.
Galaxy S6 Edge user here. I have the same issue as the screenshot above. The OAuth process resolution does not allow to get to the allow Authorization button on Ring’s site.
Since Smartthings is using an embedded browser, I recommend to disable the mobile view. Desktop rendering will allow users to use pinch zoom and see the entire page.
2 Likes
I just did is on a normal S6, the button was slightly cut off but I could tap it.
It has created a device but I can’t do anything with it, it just says “Ready”, there are no configuration options and I can’t seem to add it to a room?
Exactly the same thing here. Galaxy S6.
You should be able to add the Ring to a room through the room’s settings.
As for the cutoff button, I am looking into this. The button was not cut-off in the testing on our side. This appears to be the way that the login site is rendering in the device’s WebView – but that is my initial observation.
Regarding the button being used in automations… We are working to have a default assumption of 1 if the DTH does not define the number, and a default of 1 for buttonNumber if the event does not send a number. (Roughly – I would need to confirm the exact logic.) That release didn’t quite coincide with the Ring release, so we are looking to remedy the situation. I am also pushing to make sure that our documentation is properly updated to reference buttonNumber, since that isn’t mentioned.
1 Like
Temporary workaround for Galaxy S6 users:
Go to system settings and change system fonts to Tiny. You should see the Authorization button now appear. Authorize Ring and then revert font settings.
May work for other Android devices too.
6 Likes
Ah, that explains it, I have mine set to tiny and I could just about see the button.
@dckirker yeah I just hadn’t added anything recently and it looks like you removed the ability to select a room from within the device settings, so now you just add it to the room from the room settings.
Can use it as a motion sensor and button device! YAY!
1 Like
Does this mean automations won’t work with the button action?
What can we do with this. I added my ring. I see it, but no smart apps?
CoRE piston works for me for motion, but not for button presses yet. Also added battery monitoring fornmy Simple Device Viewer smart app.
It can be used as a motion sensor / button in SmartApps like Smart Lighting, CoRE, etc.
Are you saying you are about to modify the documentation to match this DTH? Lots of DTHs do not expose numberOfButtons because it wasn’t in the documentation at the time of creation. But they have 4 buttons. Hence the implied 4 default… Also, you are now changing the documentation to no longer require buttonNumber and assume 1 if it’s missing? How is that backwards compatible?
1 Like
They just left the tile out. Same for Ring regular version. Motion shows in activity.
1 Like
This is great - thanks! I had the problem with authorizing it on my iPad but could see a sliver of the button on my phone.
I added motion trigger for lighting control that previously went through IFTTT. Tested it and so far working great. This is a step in the right direction.
As a Software Developer, I can understand everyone wanting everything at once. However, I do like a phased rollout of features. Ultimately, it comes down to communication and setting proper expectations for end users.
3 Likes
Let me back track a little and better clarify (I was fielding a few different things when I wrote the first message): I am going to send a note to our technical writers that the buttonNumber data parameter is not defined in our documentation as it should be. To clarify about the use of numberOfButtons: The plan is to fix our code (for instance in the lighting automation) to be mindful of the numberOfButtons attribute, and not just assume 4 buttons without looking at this value (as it can confuse customers). Or even possibly prompt the user to enter a textual number. It would also make sense when we do that to make sure that the attribute is used properly in device handlers. But right now, the only mention of the “buttonNumber” data parameter (in only a comment in a snippet of sample code) is that it could be optional, so anything that doesn’t set it won’t work with things like CoRE or our Lighting Automations. The goal is to fix this. At this point, the developer is still looking into the work involved, so I don’t completely know the timeline or the exact results.
So, in short: I am going to send a note to make sure our documentation is updated and accurate, then we will be making sure we actually follow it.
(The back story is that this very generic capability was written for a very specific, 4 button ahemAeon minimotecough, device. Now we are trying to make sure that the generic capability properly applies to all devices in that class and that our code properly follows that.)
Hopefully that was more clear! I am trying to make sure that we, as SmartThings, provide the best definition and structure as we can for our capabilities so that we don’t hit little speed bumps like this during launches. 
TL;DR for everyone else:
At the moment, the Ring doorbell doesn’t send the button number, and I am working to get a fix pushed as quickly as I possibly can so that it will. My apologies for this trouble.
4 Likes
I got it integrated on an iPhone 6S. Added to a room through the room setup screen and automated through Core.
Thanks for working on this. Looking forward to the video integration.
Oh pfew then Thank you.
Modified CoRE a bit to allow early adopters of Ring to actually use the Ring 
v0.3.163.20161102 - RC - Adjustments to better fit the Ring integration - assuming 1 button if no numberOfButtons (may break other DTH implementations), assuming button #1 pushed if no buttonNumber is provided
2 Likes