Skip to content

bfara83/hubitat_ring_integration

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Hubitat Ring Integration (Unofficial)

Notice!!!

First and foremost I need to warn any who venture to use this integration. This integration is provided for fun without hope of warranty or safety or stable or permanent use. 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. I wrote this integration for fun and I do not trust it with my safety. It's a hobby project. (That said, it is well built and mostly stable. On the hubitat side the hub slows down sometimes and drops the websocket connection but there is a watchdog that starts it back up.)

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. 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. You agree to hold me unresponsible for what may happen to your home, personal property, self, family, etc. You agree to hold me unresponsible. End of story.

If that sounds okay then continue onwards...

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. And they have A LOT of devices.

Everyone should start by installing the app. From there, there are two types of devices; devices that communicate via classic HTTP calls and devices that communicate via websockets. It roughly breaks down like this:

  • Security cameras, doorbells and chimes (classic HTTP devices)
  • Beams devices (websocket devices)
  • Security devices (websocket devices)

The app can interact directly with the non-websocket devices. The driver for the API device is required for all of the websocket devices. The dependency heirarchy will look like this a little:

                     App
         /                        \
    websocket                cameras/chimes/doorbells
      device
    /                \
 security          beams
 devices          devices

Before you install any classic HTTP devices know that since we are not Ring partners we cannot get motion and ring notifications pushed to us. Because of this you have three options. One option is to poll for them. Yes, this is horrible and for that reason I do not poll myself. However, I added this functionality because it seems to work for the home bridge project. AND... I know that I will spend forever explaining why I didn't add it if I don't. Now I will probably just spend forever explaining why you can't poll more often for dings or dings are missed... Option two is to setup IFTTT applets for each motion type (ring or motion) for each device. There is fairly robust documentation for how to do this within the app so I will only cover it briefly here. You must enable OAuth on the app and authorize Ring to IFTTT. 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. If it sounds complicated, don't worry. After you install the app you can navigate through to the IFTTT page and learn more. Finally, the third option is to use SmartThings and the hublink app and have separate devices for status. (I have separate devices and I use the SmartThings integration with hublink).

I also added the ability for each light device to poll for its light status. I don't use this either. I use these devices for control. I do not use them for status. 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.

You do NOT need to install all of the device drivers in this repository. You should be able to get away with installing the drivers for just the devices you own and have registered. Here are the device to driver mappings roughly:

The app

Children of the app

Children of the Ring API Virtual Device (websocket device)

Ring Alarm

Ring Security Lighting (Ring Bridge/Beams)

The app will create the camera, chime and doorbell devices automatically. However, because it was far easier the security and beams devices are NOT created automatically via the app's discover devices functionality. Once you add the "Ring API Virtual Device" from the app you must go and click "Create Devices" on your respective device to get its websocket children device(s) to create. For example, if you have alarm devices go to the alarm hub device's edit page and click the "Create Devices" command.

Brief Installation Instructions (IF YOU ONLY READ ONE THING LET IT BE THIS SECTION)

The packages can be installed either manually or through the Hubitat Package Manager.

Using Hubitat Package Manager

  • Make sure Hubitat Package Manager is installed and working. See hubitat-packagemanager
  • This package can be found in the Integrations section, or you can install by URL using this link: packageManifest.json
  • Make sure to select the optional device drivers that you will need when prompted

Manual Install

  • Go to github.com via the links above and install the custom app code. (Install custom apps using the "Apps Code" link in the left navigation of the Hubitat hub.)
  • Also on github.com get the code for all of the devices you need using the list above. If you have alarm or security lighting devices you also need the "Ring API Virtual Device" driver. (Install custom drivers using the "Drivers Code" link in the left navigation of the Hubitat hub.)

Configuration

  • Create an instance of the app. (Create instances of custom apps using the "Apps" link in the left navigation of the Hubitat hub.)
  • Authenticate to Ring in the app by giving it your Ring credentials and choose your location.
  • Click the "Discover Devices" link in the app. If you have alarm or security devices be sure to also pick to install the "Ring Virtual API Device". The app will create any devices you select here for you.
  • You won't get motion or ring notifications or events on cameras and doorbells until you configure them. There are instructions in the app to set them up under the "Configure the way that Hubitat will get motion alert and ring events" link. It is highly recommended to use IFTTT for notifications. You can poll for events but it is often unreliable.
  • You are done if you do not have alarm or security lighting devices.
  • If you have alarm or security lighting devices you will need to go to the "Ring Virtual API Device" and make sure it is connected by looking at its current state for websocket.
  • If it isn't connected, hit the "Initialize" command button
  • If it is connected, the API device should have up to two children devices already created. If you have alarm devices, the alarm hub should be created. If you have security lighting devices the beams bridge should be created. Go to each of these devices and click its "Create Devices" command button. This will automatically create the alarm and security devices.
  • At no point should you create a device yourself. The only thing you need to create is the app instance. The app and API device create everything else.

About

Unofficial Ring integration for Hubitat home hub

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Groovy 100.0%