oovy Any Z-Wave (First-Alert) smoke detector that connects to Ring Alarm (First Alert).oovy - Any Z-Wave switch that connects to Ring Alarm.
oovy - Any Z-wave (Dome) siren that conects to Ring Alarm.oovy - Any Z-Wave lock that connects to Ring Alarm.oovy - Ring Alarm Keypad (1st or 2nd Gen).oovy - Ring Alarm Motion Sensor (1st or 2nd Gen).Additionally used for contact sensors connected to the Retrofit Alarm Kit oovy - Ring Alarm Contact Sensor (1st and 2nd Gen) and any Z-Wave (Ecolink) tilt sensor that connect to Ring Alarm.oovy - Range Extender (1st and 2nd Gen).oovy - Indoor Cam, Stick Up CamĬhildren of the Ring API Virtual Device (websocket device) Ring Alarm.oovy - Spotlight Cam Battery (A few devices where the siren call is different and I haven't reverse engineered it yet.).Required if you have a Ring Alarm hub or a Ring Beams (Smart Lighting) bridge oovy - This is the "Ring API Virtual Device" or websocket device.Here are the device to driver mappings roughly: The app You should be able to get away with installing the drivers for just the devices you own and have registered. You do NOT need to install all of the device drivers in this repository. I don't ever need to know their light status therefore I don't care what it is and I don't poll for light status. I also added the ability for each light device to poll for its light status. (I have separate devices and I use the SmartThings integration with hublink). Finally, the third option is to use SmartThings and the hublink app and have separate devices for status. After you install the app you can navigate through to the IFTTT page and learn more. Then you create applets on Ring events that call into the "Unofficial Ring Connect" app using an OAuth token by way of web service calls from the "Webhooks" IFTTT service. You must enable OAuth on the app and authorize Ring to IFTTT. There is fairly robust documentation for how to do this within the app so I will only cover it briefly here. Option two is to setup IFTTT applets for each motion type (ring or motion) for each device. Now I will probably just spend forever explaining why you can't poll more often for dings or dings are missed. I know that I will spend forever explaining why I didn't add it if I don't. However, I added this functionality because it seems to work for the home bridge project. Yes, this is horrible and for that reason I do not poll myself. The dependency heirarchy will look like this a little:īefore you install any classic HTTP devices know that since we are not Ring partners we cannot get motion and ring notifications pushed to us. The driver for the API device is required for all of the websocket devices. The app can interact directly with the non-websocket devices. Security cameras, doorbells and chimes (classic HTTP devices).From there, there are two types of devices devices that communicate via classic HTTP calls and devices that communicate via websockets.
And they have A LOT of devices.Įveryone should start by installing the app. I don't expect this to be a perfect experience because I'm not providing a lot of direction and I don't have documented very well which drivers go to which devices beyond the names of the drivers and files. If that sounds okay then continue onwards. You agree to hold me unresponsible for what may happen to your home, personal property, self, family, etc. If you use this integration you agree to hold me unresponsible for what may happen to your Ring account in the event that Ring deems this type of usage of the API unreasonable. If some part of this integration does not work now or stops working in the future I make no gaurantees and this is provided "AS IS" without hope of service or warranty. On the hubitat side the hub slows down sometimes and drops the websocket connection but there is a watchdog that starts it back up.) (That said, it is well built and mostly stable. I wrote this integration for fun and I do not trust it with my safety. Ring are not official partners with Hubitat or myself and all of the interactions between the Hubitat hub and Ring's cloud servers in this integration are via the private API calls that Ring does not publish or give permission to use for this purpose. This integration is provided for fun without hope of warranty or safety or stable or permanent use. First and foremost I need to warn any who venture to use this integration.
0 kommentar(er)
