Ring Doorbell, Camera and Alarm support for Homey

Apps
, , , ,
1053

Some more info:

Turning off the AI options (Video descriptions, Familar faces, Single event Alerts, Unusual Activity Alerts) dramatically increases the reporting by your app.

On the front drive I have a camera and front door bell. Both successfully recorded HUMAN/PERSON EVENTS but did NOT report VEHICLE or ‘Motion’ (unknown).

On the side of my house I left the AI features all on. It reported the FIRST human it saw but then did not report a further 6 human motions, 2 unknown motions and 1 ‘unusual’ motion.

I hope that this is of some help and please let me know if you want me to test anything else for you.

Andrew

1054

Thank you for your reply. - I’ve followed the FAQ procedure. I’ve been experimenting with up to 12 hours of down time on Mobile Ring app, the Homey Ring app, but no change. Yes, I always remove any connection between the Ring Account and the Homey Ring app. I’ve removed the Ring app in Homey and re-added all devices, but no change. The cameras always works as intended. Contact Sensors, Motion Sensors, KeyPad and BaseStation does not. All my Ring devices are working as intended on the mobile Ring app. - FYI I have 49 Ring devices including 2 Glass Break Sensors. All devices are updated to latest firmware. - Should I try to start over and remove all devices from the Ring Account and re-add them?

1055

Title: Ring Chime Gen 3 recognized by Homey, but not found when triggered by a Flow

Hi,

I have been using the RING app in Homey for quite some time, and the app is automatically kept up to date.

My RING Doorbell has two Chimes connected to it. One of the Chimes recently became defective, so I replaced it with a new one.

The new Chime is a 3rd-generation RING Chime.

Homey recognizes the new Chime immediately and allows me to add it as a device without any problems. The device also appears correctly in Homey.

However, when I create a simple Flow to test the Chime, I get the following error:

“Chime with id 768466153 not found”

This is a bit confusing because Homey clearly recognizes the Chime and is able to add it as a device. Apparently, however, the Chime cannot be found when the Flow tries to send a command to it.

The Chime itself is working correctly: it sounds normally when the RING Doorbell is pressed. The problem only occurs when I try to trigger the Chime through a Homey Flow.

Could this be related to the 3rd-generation Chime, or possibly to the way the RING app handles the Chime ID?

Is there a known issue with controlling a Gen 3 Chime through Homey Flows?

Thanks in advance for any help.

1056

Hi @Groetsels,

I don’t have the new 3rd generation Chime so I can not test device and I’m also not aware of any changes in how the Chime operates differently from the previous generations so I need your help to troubleshoot this.

Can you please stop the Homey Ring app, start it again and after waiting a bit trigger a flow that should activate the Chime. After that, please send a Diagnostics Report.

Thanks!

1057

Spotlight Cam 4K Pro – snapshot works when testing Flow, but not on real motion

Hi Danee,

I have a new Ring Spotlight Cam 4K Pro connected to a Homey Pro 2026, using the Ring app com.amazon.ring v2.14.26.

I have a strange issue with snapshots.

My Advanced Flow is basically:

Motion alarm turned on → Grab current snapshot → send the Snapshot image

When I manually test the Flow, the snapshot can work and the image is sent correctly.

However, when I actually walk in front of the camera and the Flow is triggered by real motion, the snapshot is not reliably available/sent.

Things I have checked:

  • Motion detection is enabled in Ring.
  • Motion events from the Spotlight Cam are received by Homey.
  • The camera is mains powered.
  • Live View in the Ring app works correctly.
  • The Ring connection is good.
  • An older Ring camera works with the same type of snapshot Flow.
  • Sometimes the Spotlight Cam 4K Pro snapshot appears correctly in Homey, but at other times the camera view shows “Stream Closed”.
  • The Snapshot image tag can then show as a broken/unavailable image.
  • Manually testing the Flow can succeed, while an actual motion event fails.

It therefore looks like there may be a timing/compatibility issue when retrieving a snapshot from the Spotlight Cam 4K Pro immediately after a real motion event.

Is the Spotlight Cam 4K Pro fully supported for snapshots in v2.14.26, or would you like me to send a diagnostics report?

Thanks!

1058

Please see this post on how to handle snapshots: Ring Doorbell, Camera and Alarm support for Homey - #477 by DaneedeKruyff

1059

Hi Danee,

Thanks. I have now rebuilt the flow exactly using the method from post #477.

Flow 1:
Spotlight Cam 4K Pro motion alarm → Grab current snapshot

Flow 2:
Snapshot is grabbed → send the Voor Tuin Snapshot image via WhatsApp

Unfortunately, this still does not work when real motion occurs.

Ring itself detects the person correctly and sends me the Ring notification, but Homey does not produce/send the new snapshot. Other Ring cameras on the same Homey and WhatsApp setup do work.

To be clear, this is the new Ring Spotlight Cam 4K Pro. Could this specific new 4K model not yet be fully supported by the Homey Ring app?

I can send a Diagnostics Report if that helps.

1060

Ok, to narrow it down, please add a notification card to the first flow to make sure it’s a missing trigger.
I am not aware of any changes for motion detection, untill now all camera devices use the exacts same method to detect motion, but you never know what Ring does :frowning:
Can you stop the app, start it again wait a bit and send a Diagnostics Report, that way I can see the initialization off the app on your Homey.

1061

Hi Danee,
I restarted the Ring app and sent a Diagnostics Report.
I also added the notification card as you suggested.

Ring itself detects the person/motion on the Spotlight Cam 4K Pro, but the Homey flow is not triggered at all. The Homey notification card does not fire either.

So it looks like Homey is not receiving the motion trigger from this specific Spotlight Cam 4K Pro.

1062

Getting this error message when trying to arm, it’s weird bc all sensors are closed, arming from keypad doesn’t require bypass

Failed to set alarm mode to “all”. Sensors may require bypass, which can only be done in the Ring app.

1063

Can you please stop the app, start it again. Next, wait a bit and select a Surveillance Mode. When it returns the message again, Pleas send me a Diagnostics Report.

1064

Were you able to take a look? Anything interesting happening?

1065

Hi Nick,

Sorry, I did indeed receive the report and looked into it, but it’s basically a pass through of an error encountered when arming. Unfortunately it’s not clear what exactly happened, so the API falls back to the most common cause, being a sensor that’s not ready.

Please check all sensors in your setup in the Ring app to see what’s going on. It can very well be a sensor on a very low battery that’s not reporting which the Ring app may ignore when arming because it’s not in use in a particular mode but still reports as a problem over the API.

1066

Thank you!

Interesting, not sure what it could be then. It’s a brand new system installed a little over a month ago. Arming and disarming broke once my trial ended for ring pro. I also cannot arm from the ring app only the keypads.

Is a subscription required for the api to work?

1067

Hi Nick,

No, a subscription should not be necessary. If the official mobile app from Ring also can’t switch an Alarm mode I suggest you contact Ring.

1068

Good morning, I am using a Ring Alarm kit with some Ring contact sensors.

After some days, I need to restart the Ring app inside Homey to get sensor status updates since the status remains frozen. After how many times does the token expire?

Is that a know issue or how can I solve it? Thanks in advance!

In case you need, this is my report 76c82d6e-0ac0-4f12-9587-556300cd6cd7

1069

Hi Danee, thanks for the app and all the work on the Alarm support.

I have a Ring Alarm Pro (the base station with the built-in eero Wi-Fi 6 router) on a Homey Self-Hosted Server, app version 2.14.27. Pairing works for the Keypad, Doorbells and Floodlight Cams, but adding a Basestation returns an empty device list.

I tried a few times and then pointed Claude Fable at my challenge to see if I was messing up. It came right back with a slight miss in the code and offered a patch.

I built this from your current master with the three edits below and installed it on my Self-Hosted Server with homey app install. The Alarm Pro now appears in the Basestation pairing list, pairs, and the mode and alarm cards work as expected.

----AI BELOW!----

The cause is that Ring reports the two base station models with different device types, and the app only matches the original one. The bundled ring-client-api defines both:

BaseStation:    'hub.redsky'
BaseStationPro: 'hub.kili'

The Alarm Pro comes back as hub.kili, so it is filtered out before the pairing list is built. Three places match only the original base station:

  1. drivers/basestation/driver.js, onPairListDevices(): if (device.data.deviceType === 'hub.redsky')
  2. lib/Api.js: alarmDeviceList only contains 'hub.redsky', so the app never subscribes to the Pro’s data events
  3. drivers/basestation/device.js: the block that reads tamper, power source, network connection and battery from the base station checks data.deviceType == RingDeviceType["BaseStation"] only

Adding the Pro type in each spot fixes it:

diff

--- a/drivers/basestation/driver.js
-            if (device.data.deviceType === 'hub.redsky') {
+            if (device.data.deviceType === 'hub.redsky' || device.data.deviceType === 'hub.kili') {

--- a/lib/Api.js
-const alarmDeviceList      = [ 'sensor.contact', 'sensor.motion', 'security-keypad', 'security-panel', 'hub.redsky' ];
+const alarmDeviceList      = [ 'sensor.contact', 'sensor.motion', 'security-keypad', 'security-panel', 'hub.redsky', 'hub.kili' ];

--- a/drivers/basestation/device.js
-        if ( data.deviceType == RingDeviceType["BaseStation"] ) {
+        if ( data.deviceType == RingDeviceType["BaseStation"] || data.deviceType == RingDeviceType["BaseStationPro"] ) {

Mode changes and the burglar/fire/medical/panic/entry delay triggers all come from the security-panel device, which is the same on both base stations, so nothing else needed to change.

1070

Hi Ed,

Thanks! The mentioned Ring Alarm Pro is not available in the Netherlands so, unknown to me. Ring’s website is made so smart it will only show information on products available in the country you’re visiting the site from, so it’s very hard for me to know about all Ring products and I have to rely upon users of the app informing me.

I’m glad you informed me and have taken the steps o figure out what needs to be changed in the app to have your device supported, thanks!

At this time I can not oversee when I have time to make the changes to the app and publish a new version but I will do my best to do it this weekend.

1071

No worries at all! Since you made the code public anyone can make the simple edits themselves and have it working.

I have the modified code loaded and it works perfectly. Thanks for making this available!!

1072

Promoted test version to live version

Version: 2.14.27

  • Additional logging

This version added additional logging making Diagnostics Reports more useful when troubleshooting an issue.