[Re-release] Hubitat Ring Integration (Unofficial)

⚙️ Custom Apps and Drivers
1669

I've sent you a PM so we can collaborate on getting things integrated.

1 Like
1670

Update: The problem is resolved. I can't actually say what fixed it.

I had a range extender that the hub seemed to refuse to use. I decided to remove and add it back to Ring, using the Ring Android App. As one might expect, the corresponding device in Hubitat was no longer being updated. I then took the following steps:

  • Removed the virtual device from Hubitat.
  • In "unofficial ring integration app" I clicked on "Manage installed child devices" -> Location -> "Create devices".

The virtual device now updates when I unplug and plug back in the range extender, but no matter where I place the extender, the RSSI reading in signalStrength to the hub always records as -61. Interestingly, the signal strength to another once of the range extenders does change as I move it around. The lastUpdated time also changes.

Did I handle the situation properly with the app? Any insights / thoughts on what might be going on?

Thanks!

Marc

1671

This app works great for me and exposes the alarm modes properly. I just tried the new built in integration, and although you can initiate a mode change via the integration, the mode can't be read or seen by any automation you set up, so its presently useless for me.

2 Likes
1672

I have started seeing the following warnings in my logs:

apiRequestTickets (retryable) http error: 408, Connect to prd-api-us.prd.rings.solutions:443 [prd-api-us.prd.rings.solutions/52.21.120.109, prd-api-us.prd.rings.solutions/23.20.28.222, prd-api-us.prd.rings.solutions/3.211.186.78, prd-api-us.prd.rings.solutions/52.72.232.85, prd-api-us.prd.rings.solutions/3.212.48.92, prd-api-us.prd.rings.solutions/184.73.185.109] failed: Network is unreachable (connect failed), null

When this happens, I also see this error starting to show up:
PM

Cannot send request because socket is not connected: {"channel":"message","msg":{"dst":"redacted","msg":"DeviceInfoDocGetList","seq":1}}

It seems to happen whenever my router goes offlines for a bit. (I've been taking it offline to do some upgrades).

It seems to resolve if I "Initialize" the location device and then reboot the hub.

In a similar timeframe I upgraded to hubitat platform version 2.5.0.126.

Is this to be expected?

Marc