Ring Ding does not change state

[MaxK99]

The problem

The _binarysensor.ding entity does not change state (from clear to on) when the ring doorbell button is pressed. A reload of the Ring integration would temporarily solve this issue in 2023.1.7 but a reload does not solve the problem in 2023.2.5.

The _sensor.lastding does update correctly.

What version of Home Assistant Core has the issue?

2023.2.5

What was the last working version of Home Assistant Core?

2023.1.7

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Ring

Link to integration documentation on our website

https://www.home-assistant.io/integrations/ring/

Diagnostics information

None

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: homeassistant.components.ring
Source: components/ring/__init__.py:219
Integration: Ring (documentation, issues)
First occurred: 12:09:17 PM (2 occurrences)
Last logged: 2:23:07 PM

Error fetching Ring active dings data: 502 Server Error: Bad Gateway for url: https://api.ring.com/clients_api/dings/active?api_version=9
Error fetching Ring active dings data: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))

Additional information

No response

[home-assistant[bot]]

ring documentation ring source

[clicky73]

Same issue here.

Running HA 2023.2.5

[jg-uk]

Unfortunately I seem to be having the same issue - although curiously it's only with the battery powered doorbell.

My Ring Pro mains powered doorbell appears to be reporting dings correctly, not sure if this helps debug ?

[MaxK99]

My Ring Pro mains powered doorbell appears to be reporting dings correctly, not sure if this helps debug ?

I can confirm that my ring pro powered also reports dings correctly but my battery powered ring does not.

[78wesley]

I can confirm that for the "Ring Video Doorbell Wired" the binary_sensor.ding does work again in the Home Assistant 2023.3.0.

Edit:

Some times it did work after a restart of home assistant

[palvarez89]

EDIT: This wasn't right, see other comments below.

Also works for me again with the latest update 2023.3.0 with a battery powered ring doorbell

[jg-uk]

Unfortunately 2023.3.0 hasn't changed anything for me - my wired doorbell reports the dings correctly, whereas the battery powered one does not.

Interestingly the "last ding" updates itself just fine with the battery powered doorbell - but seeing as it updates a few minutes after the ding it's not suitable for use in an automation.

[palvarez89]

I noticed today it didn't work again, so maybe it only works once, and then back to not working?

Interestingly the "last ding" updates itself just fine with the battery powered doorbell - but seeing as it updates a few minutes after the ding it's not suitable for use in an automation.

Tried that workaround too, but it's just too slow as you say

[PeterHoge]

Ding does not work since mid January 2023 for my Ring Doorbell 2, wired and with battery. My HA has always the actual version. now 2023.3.1. In Alexa it works.

[LouisMT]

I'm having the same issue, and I'm also seeing an error in the log sometimes. Something like "timeout fetching active Dings".

Wondering if anyone is seeing the same error? It's not the exact error, I restarted HASS to fix the issue and forgot to copy it.

[MaxK99]

@LouisMT I think you saw the same error message as in the original post above.

[postaanerik]

Home Assistant 2023.3.4 - issue with binary sensor of wired Ring doorbell

[reypm]

I am running into the same issue with HA 2023.3.4 and Ring Video Doorbell 3 (with batteries). Wonder how are you guys using the sensor.front_door_last_ding I was checking against new_state.attributes.recording_status=ready but not sure if is it the right way to use it 🤔

[jg-uk]

Hey Everyone,

Just to follow this one up - so far I seem to have had quite a bit of success in clearing out my list of authorised devices - https://account.ring.com/account/control-center/authorized-devices and then deleting and re-enabling the ring integration. My "authorised devices" list had hundreds of logins from the Python/Android user agent that home assistant reports as.

So far so good - all of my dings are back to reporting instantly - I wonder if there is some limit on the authorised devices that was causing this ? Would be great if others could see if it works for them !

[reypm]

Just to follow this one up - so far I seem to have had quite a bit of success in clearing out my list of authorised devices - account.ring.com/account/control-center/authorized-devices and then deleting and re-enabling the ring integration. My "authorised devices" list had hundreds of logins from the Python/Android user agent that home assistant reports as.

This did not work for me, I cleared all of them and tried and binary_sensor.front_door_ding never changed the state :(

[MaxK99]

@3guk Didn't work for me.

Before trying your solution I confirmed I could get first ding on reboot but none after that. Then I tried your solution and cleared authorized devices, deleted integration, rebooted, added integration - still no ding. Then rebooted again, no ding. Tried solution a second time and still no ding change of state.

[erlendsellie]

Same issue here. Tried deleting authorized devices.

[kevincdhouston]

I have the same issue. I noticed that if motion is detected before the doorbell is rung then the ring doesn't activate but if there is no motion (reaching around from inside to test) then ring activates correctly.

[DirkFace]

I have the same issue too. Follwing to see if a solution is found.

[Coldvibe]

Hi all, i have se same issue here. Still no solution ?

[LouisMT]

I couldn't get it to work, the suggestions above also didn't work for me.

So I tried switching to ring-mqtt, initially to check if Ring stopped providing dings through the API.

I've been using ring-mqtt for weeks now (almost 3 months), and it's working perfectly. Setup is also really straight forward - especially if you're already using MQTT in HASS. If you need the dings, this is the fastest/easiest way to get them working for now, I think.

[Coldvibe]

Thank you for answering, i downloaded the MQTT add on and Will try ot tomorrow

[amiranees]

Still not fixed :(

[ytugarev]

@amiranees as @LouisMT mentioned above - ring-mqtt is a perfect replacement. I've been using this for few days - works like a charm.

[palvarez89]

Has anybody else noticed this working again?

[MercuryxHQ]

I have the same issue. I noticed that if motion is detected before the doorbell is rung then the ring doesn't activate but if there is no motion (reaching around from inside to test) then ring activates correctly.

I can confirm this is the case as well on 2023.8.2.

[jackkitley]

Just to follow this one up - so far I seem to have had quite a bit of success in clearing out my list of authorised devices - account.ring.com/account/control-center/authorized-devices and then deleting and re-enabling the ring integration. My "authorised devices" list had hundreds of logins from the Python/Android user agent that home assistant reports as.

This did not work for me, I cleared all of them and tried and binary_sensor.front_door_ding never changed the state :(

Same here, The last ding is very hit and miss. Sometimes it works sometimes not. i rely on it for my automations to alert me but seems to be very delayed.

[jackkitley]

Has anybody else noticed this working again?

Nope, not working. thought it may be because it rang on my app. i uninstalled it and tried the doorbell again. It still says last ding was yesterday...

[jjaammhh]

It's sad but still it doesn't update the ding sensor, so its main functionality is broken.

Considering it seems to be so since several months ago, I think it would be honest to advertise it on the main integration page.

[hughsaunders]

I worked around this by exposing a button to Alexa and then having an Alexa routine press the button when the doorbell is pressed. Bit backwards but at least home assistant now knows when the doorbell has been pressed.

[MaxK99]

@sdb9696 I see you Bumped ring-doorbell to 0.7.3. Glad to see the integration getting some attention. Thank you very much! Any possibility of getting this issue resolved?

[fynnsh]

Same here Home Assistant 2023.8.1

[sdb9696]

I will start looking at it. I might need some help from people affected if I can’t reproduce it on my own doorbell. Will let you know.

[swimboy46163]

I will start looking at it. I might need some help from people affected if I can’t reproduce it on my own doorbell. Will let you know.

I am seeing this on my wired ring doorbell pro 2 as well.

[snothub]

Following too, have the same issue.

[mikesalz]

So this is weird. I guess it is happening to me intermittently. I also have the Pro 2. It recorded a ding event earlier in the week, but missed one today. But the Last Ding sensor shows today's ding.

[jackkitley]

Yes. It's intermittent. Works and then doesn't work. Almost like a delay

On Fri, 06 Oct 2023, 21:12 _Mike, @.***> wrote:

So this is weird. I guess it is happening to me intermittently. I also have the Pro 2. It recorded a ding event earlier in the week, but missed one today. But the Last Ding sensor shows today's ding.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/88705#issuecomment-1751291519, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYXYBT2XCCHZRYEA7CFZODX6BJ3HAVCNFSM6AAAAAAVG7D3JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRGI4TCNJRHE . You are receiving this because you commented.Message ID: @.***>

[sdb9696]

Hi, so I’ve been looking at this and I think I’ve gotten to the cause. If the doorbell starts off recording motion and then receives a ding, the ring cloud api doesn’t return the ding in its standard ding query (depending on how long the motion goes on for before the ding). This seems to be a change on the ring api side as nothing changed between HA 2023.1.7 and 2023.2.5 to impact this.

I tried a fix to query the device immediately after receiving a motion alert to get the ding alert but it didn’t really work because the ding alert is only returned from the cloud api once the motion recording has finished which is no good. 🙁

I’m now working on a fix to get realtime ding alerts from Firebase cloud messaging (the thing that sends to your phone) instead of the ring cloud api. This is non-trivial but I seem to have finally got it working, so with a bit more testing and some other stuff that needs to happen, I may have a proper fix soon. Fingers crossed.

[jackkitley]

Great. Good find!

On Sat, 07 Oct 2023, 20:37 sdb9696, @.***> wrote:

Hi, so I’ve been looking at this and I think I’ve gotten to the cause. If the doorbell starts off recording motion and then receives a ding, the ring cloud api doesn’t return the ding in its standard ding query (depending on how long the motion goes on for before the ding). This seems to be a change on the ring api side as nothing changed between HA 2023.1.7 and 2023.2.5 to impact this.

I tried a fix to query the device immediately after receiving a motion alert to get the ding alert but it didn’t really work because the ding alert is only returned from the cloud api once the motion recording has finished which is no good. 🙁

I’m now working on a fix to get realtime ding alerts from Firebase cloud messaging (the thing that sends to your phone) instead of the ring cloud api. This is non-trivial but I seem to have finally got it working, so with a bit more testing and some other stuff that needs to happen, I may have a proper fix soon. Fingers crossed.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/88705#issuecomment-1751790881, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYXYBW6GWAQWBODDDM3KK3X6GONHAVCNFSM6AAAAAAVG7D3JKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONJRG44TAOBYGE . You are receiving this because you commented.Message ID: @.***>

[jjaammhh]

Exciting news!

Just one thing. You are talking about the recordings, and, at least in my case, I don't have them enabled. However, as long as phone alerts work like a charm, switching to Firebase Cloud Msg sounds very promising

Please, let us know when a new operative version is released

Tons of thanks for your effort

[joostbijl]

Hi, so I’ve been looking at this and I think I’ve gotten to the cause. If the doorbell starts off recording motion and then receives a ding, the ring cloud api doesn’t return the ding in its standard ding query (depending on how long the motion goes on for before the ding). This seems to be a change on the ring api side as nothing changed between HA 2023.1.7 and 2023.2.5 to impact this.

I tried a fix to query the device immediately after receiving a motion alert to get the ding alert but it didn’t really work because the ding alert is only returned from the cloud api once the motion recording has finished which is no good. 🙁

I’m now working on a fix to get realtime ding alerts from Firebase cloud messaging (the thing that sends to your phone) instead of the ring cloud api. This is non-trivial but I seem to have finally got it working, so with a bit more testing and some other stuff that needs to happen, I may have a proper fix soon. Fingers crossed.

Thanks for looking into this! My new ring doorbell worked for the first few days, but not anymore. The ding state does not update, yet the last activity does.

[sdb9696]

So I now have a PR in draft to pickup changes to the ring-doorbell library that HA uses for this component. Those changes get realtime alerts from Google/Firebase Cloud Messaging (same as our phones). It works with my doorbell but I would appreciate if some others having the issue could spend a bit of time testing the fix with their devices. The PR is here https://github.com/home-assistant/core/pull/103134.

To get and test the fix you will need to be familiar with running HA from source code. To get the code after you have forked and cloned:

git fetch upstream pull/103134/head:ABRANCHNAMEYOUCHOOSE
git checkout ABRANCHNAMEYOUCHOOSE

Please bear in mind if testing that this fix specifically addresses dings not firing if they are preceded by a motion alert. It may or may not fix other issues with getting alerts. Also if alerts aren't reaching your phone you can assume the issues is elsewhere rather than with HA.

Another thing that might help with testing is to use the ring-doorbell cli to see what it's getting from ring. Preferably in a virtual environment run:

pip install ring-doorbell[listen]==0.7.7
ring-doorbell listen

You should then see alerts being printed to the screen as they happen.

Fingers crossed and many thanks in advance to anyone who's able help with testing!

[MaxK99]

I would love to help test this prior to release but I am not familiar with running HA from source code. I will test it when it is released.

Thank you very much!!!

[SaltyBart]

My girlfriend missed the christmas tree yesterday because no signal in house, DHL took it back 😁 I'm going to try to become familiar with HA from source code and test. Thanks for your efforts!

[gusch88]

Is there any new status about the test results?

[willsmarthome]

Still problems with Ring Ding state change, almost a year now. :-(

[sdb9696]

I have fixes in the pull request queue waiting to be reviewed. I've been chasing them up and I'll update this thread as soon as they're ready.

[delboydell]

just found this post after my tv not turning over to a camera on a ding, and only looked here after finding the issue with the motion 1st then no state change, but as someone posted reaching round and presing it worked. Looing forward to you working out a solution. thanks for your hard work.

[SaltyBart]

I have fixes in the pull request queue waiting to be reviewed. I've been chasing them up and I'll update this thread as soon as they're ready.

Thanks a lot!

[pifma]

I have the same problem too! but is there no way to interface directly without using the cloud?