@josh is this possible with Ring Doorbells?
I’ve seen people doing this on Amazon Fire Tablets and Android Tablets.
From what I understand, the basic concept is to use an automation app like AutomateIt (Fire OS) or Tasker (Android) to detect whenever a specific notification is received on the Ring App… then when that notification is received, automate clicking on the notification or opening the app.
Note: If I remember correctly, some people mentioned that the Ring app previously would launch the video stream right away when you opened the app (if a doorbell event was active), but Ring changed that in recent versions and it just loads the landing screen.
Others have mentioned that if you automate the clicking of the notification that is received, it will open directly to the video feed.
If you get it working let us know what approach you took!
On a related note - since people may find this post while searching or may just want to manually be able to open the Ring app, the following post includes details on the “URL Intent” for the Ring App and the new Rapid Ring app: Ring Doorbell on dashboard
Note that the way things are working in @Kent’s setup is he has a Sage Doorbell sensor to detect whenever the doorbell is rung.
From what I understand, these sensors are discontinued, but there’s a ton of them that hit ebay recently for dirt cheap. As Kent noted, the Nexia DB100Z seems to be a reasonable alternative as well.
In Kent’s case, his porch camera has a stream that’s compatible with being displayed in a SharpTools dashboard directly, so he’s setup a rule that whenever the doorbell is rung, it uses the Fully Kiosk Browser Controller integration to change to a dashboard which is showing his camera full screen.
Thanks for the detailed response. I have a Fire 8 tablet, so I’ll look into it.
How does one use the fully kiosk browser controller? I have the Sage doorbell sensor and installed it, works fine with Smarthings.
But not sure how to trigger it so that when the sensor goes off, to open up one of my media tiles that I have setup to stream my camera?
You would install the Fully Kiosk Browser Controller DTH and then setup a rule to use the
loadUrl() command to load your desired URL when the doorbell sensor is activated.
The Fully Kiosk Browser Controller device can open URLs, so you would want to have a dedicated dashboard with your stream as a large tile on it or even just open the stream URL directly.
As far as I’m aware, the Fully Kiosk DTH can’t ‘click’ a tile, so it can’t open an existing tile full screen… but you can use the trick of opening a different URL which has the media displayed in a large format.
Cool, and the “loadURL()” rule is inputted where/how?
You could do it in the SharpTools.io Rule Engine or in the rule editor of your choice.
Sorry, still learning at this. Tried that, but keep getting stumped. So I do the following:
- Create a Rule
- Select a trigger as my Sage Doorbell
- Not sure whether to select “Button”, “Presence”, or “Supported Values” (I’m assuming it’s not this one as there doesn’t seem to be any values)
- If “Button”, then there is a bunch of values in there like “down”, “Pushed”, double. I tried “down”.
- I then selected a Flow, being the Fully DTH and executed a load URL command with the video URL.
Unfortunately, nothing happened.
@S_D, try using “Button” and “pushed” as the trigger. See below for example where my trigger is a Ring, but it should be similar.
A couple of tips when troubleshooting rules.
- To verify if the trigger is configured properly, add an email notification in the flow, so you know if the rule was triggered based on if you received the email or not.
- To test the rule activities, add the rule to a dashboard using “rule tile” so you can tap the rule tile to “manually” trigger it and verify if it executes the desired activities.
Thanks, that was helpful. So I’m getting an email, but nothing is happening in Fully? Same thing when I press the Sage tile, nothing comes up.
Maybe a setting needs to be changed in Fully itself?
That’s a good progress knowing you received the email notification.
It does sound like the Fully device might not be configured properly. Please follow the “Settings” section in the post below to verify your settings.
Once done, you can open your SmartThings classic app and tap Screen On and Screen Off in the Fully device and it should be able to control your Fully Browser on your tablet and turn the tablet screen on/off.
Okay, had to change the password and resave.
So it works now, however when the URL is brought up, the screen size is enormous, larger than the 8" screen so I only see a small portion of the image. Is there a way to reduce the size of the image that comes up via the URL?
Also, the URL just stays up forever, and to remove it you have to left swipe and select “Goto Start URL”, doesn’t appear to be an “x” on the image to go back to the start URL without having to swipe first.
Thinking about it some more, is this doable instead?
- Use Sage doorbell sensor to trigger a rule
- Have the rule set so that when the sensor is triggered, it loads the “tincam monitor free” application (which I can set up to only show the front door camera)
I can then use Automateit to flip back to Fully say after a set time.
The above may be useful since tinycam monitor free offers the ability to use the mic an speaker from the camera.
I believe you should be able to accomplish that with the Fully Kiosk Controller
launchAppPackage() command, similar to what was done in this thread:
I believe the app package for TinyCam Pro is:
And the app package for TinyCam Free would be:
Thanks! So I’m changing the Sage rule to LaunchAppPackage instead of launchURL, but there is no ability to insert the app package name anywhere?
Try opening up the Fully Kiosk Browser Controller device that was created in SmartThings, edit the device preferences, and set the ‘Application to Launch’ to
Then you should be able to use the
launchAppPackage() command without specifying an app name as a parameter.
Perfect, that works! Curious, there is no way to set a String in the rule engine to do this? Would be awesome if there was, so that one could use it with various apps.
It looks like the Device Handler doesn’t define that it accepts a parameter in its metadata even though the command actually does.
The device handler could be updated so that it indicates that it accepts a parameter. To do this on your own, you could edit line 52 and add a single ‘String’ parameter.
Changing it from:
command "launchAppPackage", ["String"]
After making the change and then saving/publishing it, you would need to reauthorize the device in SharpTools to pull in the latest changes.
We’ve also noted a potential enhancement - updating the SharpTools Rule Engine to let the ‘Advanced’ toggle forcefully add parameters to devices even if the device doesn’t report that it accepts parameters.