home-assistant
Ring intercom has stopped detecting when the doorbell rings on the front door
The problem
I don't know what's been happening for 3 or 4 days, that the binary_sensor that detects when someone rings the doorbell on the street is NOT detected by Home Assistant.
Yesterday I got a message in Home Assistant informing me that the ring intercom binary_sensors were going to stop being used in version 2025.04, but they have already stopped working. Warning that the new "event" types should be used, but these events are not refreshing well.
So the automations are not working so if I detect activity on the doorbell button, I can open the portal automatically.
What version of Home Assistant Core has the issue?
core-2024.10.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Ring
Link to integration documentation on our website
No response
Diagnostics information
Detectado el uso de la entidad binary_sensor obsoleta Advertencia ⸱ Reportado por Ring Esto dejará de funcionar en la versión 2025.4.0. Por favor, trata este problema antes de actualizar. Detectamos que la entidad binary_sensor.portal_timbre se está utilizando en automation.3_click_abrir_portal_nuevo
Hemos creado una nueva entidad event y debes migrar automation.3_click_abrir_portal_nuevo para usar esta nueva entidad.
Cuando hayas terminado de migrar automation.3_click_abrir_portal_nuevo y estés listo para eliminar la entidad binary_sensor.portal_timbre obsoleta, deshabilita la entidad y reinicia Home Assistant.
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
And I have push the button to open 1 minute ago, not 18 hours
Hey there @sdb9696, mind taking a look at this issue as it has been labeled with an integration (ring) you are listed as a code owner for? Thanks!
Code owner commands
Code owners of ring can trigger bot actions by commenting:
-
@home-assistant closeCloses the issue. -
@home-assistant rename Awesome new titleRenames the issue. -
@home-assistant reopenReopen the issue. -
@home-assistant unassign ringRemoves the current integration label and assignees on the issue, add the integration domain after the command. -
@home-assistant add-label needs-more-informationAdd a label (needs-more-information, problem in dependency, problem in custom component) to the issue. -
@home-assistant remove-label needs-more-informationRemove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.
(message by CodeOwnersMention)
ring documentation ring source (message by IssueLinks)
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
2024.10.2 has a fix for this but you must clear out excess Authorised Devices before upgrading in order for the fix to work.
See docs here
2024.10.2 has a fix for this but you must clear out excess
Authorised Devicesbefore upgrading in order for the fix to work. See docs here
Thank you for your reply, I only have two devices there and today I also re-authorized the device today. I have all the updates done and it still doesn't work.
Could you enable debug logging for the integration by adding the following to your configuration.yaml and restarting and upload some logs?
logger:
default: warning
logs:
homeassistant.components.ring: debug
ring_doorbell: debug
firebase_messaging: debug
Of course and thank you for your help
2024-10-14 19:06:50.016 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-10-14 19:06:50.017 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-10-14 19:06:52.825 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/session method: POST json: {'device': {'hardware_id': '6e2e48e0-0f37-4e26-9b8e-056e5f5718e1', 'metadata': {'api_version': '11', 'device_model': 'ring-doorbell:HomeAssistant/ring-integration'}, 'os': 'android'}} data: None extra_params: None 2024-10-14 19:06:52.838 WARNING (MainThread) [homeassistant.components.emulated_hue.config] Emulated Hue running in legacy mode because type has been specified. More info at https://goo.gl/M6tgz8 2024-10-14 19:06:53.439 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/ring_devices method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.598 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/dings/active method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.816 DEBUG (MainThread) [ring_doorbell.ring] url: /groups/v1/locations/185a9437-2b5b-4af4-9d9b-7dfc7d5dfd59/groups method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.974 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Finished fetching devices data in 1.149 seconds (success: True) 2024-10-14 19:06:53.998 WARNING (MainThread) [samsungtvws.connection] SamsungTVWS websocket error message: {'event': 'ms.error', 'data': {'message': "unable to handle message : Cannot read property 'session' of null"}} 2024-10-14 19:06:54.108 WARNING (MainThread) [samsungtvws.connection] SamsungTVWS websocket error message: {'event': 'ms.error', 'data': {'message': "unable to handle message : Cannot read property 'session' of null"}} 2024-10-14 19:06:54.150 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Starting ring listener. 2024-10-14 19:06:54.572 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Started ring listener 2024-10-14 19:06:54.665 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Connected to MCS endpoint (mtalk.google.com,5228) 2024-10-14 19:06:54.665 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Sent login request 2024-10-14 19:06:54.700 INFO (MainThread) [firebase_messaging.fcmpushclient] Succesfully logged in to MCS endpoint 2024-10-14 19:07:25.119 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0
Yes, I rang the bell twice. Ring App showed me that someone was calling but HA unfortunately did not.
`2024-10-14 19:06:50.016 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration alexa_media which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-10-14 19:06:50.017 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hacs which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant 2024-10-14 19:06:52.825 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/session method: POST json: {'device': {'hardware_id': '6e2e48e0-0f37-4e26-9b8e-056e5f5718e1', 'metadata': {'api_version': '11', 'device_model': 'ring-doorbell:HomeAssistant/ring-integration'}, 'os': 'android'}} data: None extra_params: None 2024-10-14 19:06:52.838 WARNING (MainThread) [homeassistant.components.emulated_hue.config] Emulated Hue running in legacy mode because type has been specified. More info at https://goo.gl/M6tgz8 2024-10-14 19:06:53.439 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/ring_devices method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.598 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/dings/active method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.816 DEBUG (MainThread) [ring_doorbell.ring] url: /groups/v1/locations/185a9437-2b5b-4af4-9d9b-7dfc7d5dfd59/groups method: GET json: None data: None extra_params: None 2024-10-14 19:06:53.974 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Finished fetching devices data in 1.149 seconds (success: True) 2024-10-14 19:06:53.998 WARNING (MainThread) [samsungtvws.connection] SamsungTVWS websocket error message: {'event': 'ms.error', 'data': {'message': "unable to handle message : Cannot read property 'session' of null"}} 2024-10-14 19:06:54.108 WARNING (MainThread) [samsungtvws.connection] SamsungTVWS websocket error message: {'event': 'ms.error', 'data': {'message': "unable to handle message : Cannot read property 'session' of null"}} 2024-10-14 19:06:54.150 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Starting ring listener. 2024-10-14 19:06:54.572 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Started ring listener 2024-10-14 19:06:54.665 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Connected to MCS endpoint (mtalk.google.com,5228) 2024-10-14 19:06:54.665 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Sent login request 2024-10-14 19:06:54.700 INFO (MainThread) [firebase_messaging.fcmpushclient] Succesfully logged in to MCS endpoint 2024-10-14 19:07:25.119 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:08:55.618 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:09:06.542 ERROR (MainThread) [homeassistant.components.mqtt.models] Exception raised while updating state of sensor.luftentfeuchter_energy_totalstarttime, topic: 'tele/Luftentfeuchter_1A71AA/SENSOR' with payload: b'{"Time":"2024-10-14T19:09:06","ENERGY":{"TotalStartTime":"2024-02-04T12:07:29","Total":22.507,"Yesterday":0.016,"Today":0.013,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 657, in state numerical_value = int(value) ^^^^^^^^^^ ValueError: invalid literal for int() with base 10: '2024-02-04T12:07:29'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 660, in state numerical_value = float(value) ^^^^^^^^^^^^ ValueError: could not convert string to float: '2024-02-04T12:07:29'
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 366, in process_write_state_requests entity.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state self.__async_calculate_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 664, in state raise ValueError( ValueError: Sensor sensor.luftentfeuchter_energy_totalstarttime has device class 'None', state class 'None' unit ' ' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '2024-02-04T12:07:29' (<class 'str'>) 2024-10-14 19:09:06.544 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.luftentfeuchter_energy_today (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'kWh' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22 2024-10-14 19:09:06.545 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.luftentfeuchter_energy_reactivepower (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'VAr' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22 2024-10-14 19:09:06.545 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.luftentfeuchter_energy_total (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'kWh' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22 2024-10-14 19:09:06.545 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.luftentfeuchter_energy_apparentpower (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'VA' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22 2024-10-14 19:09:06.545 WARNING (MainThread) [homeassistant.components.sensor] Entity sensor.luftentfeuchter_energy_yesterday (<class 'homeassistant.components.mqtt.sensor.MqttSensor'>) is using native unit of measurement 'kWh' which is not a valid unit for the device class ('power') it is using; expected one of ['kW', 'W']; Please update your configuration if your entity is manually configured, otherwise create a bug report at https://github.com/home-assistant/core/issues?q=is%3Aopen+is%3Aissue+label%3A%22integration%3A+mqtt%22 2024-10-14 19:10:26.121 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:11:56.618 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:12:59.312 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/ring_devices method: GET json: None data: None extra_params: None 2024-10-14 19:12:59.855 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/history method: GET json: None data: None extra_params: {'limit': 10} 2024-10-14 19:12:59.856 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/health method: GET json: None data: None extra_params: None 2024-10-14 19:13:00.366 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Finished fetching devices data in 1.054 seconds (success: True) 2024-10-14 19:13:27.118 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:14:00.312 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/ring_devices method: GET json: None data: None extra_params: None 2024-10-14 19:14:00.868 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/history method: GET json: None data: None extra_params: {'limit': 10} 2024-10-14 19:14:00.869 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/health method: GET json: None data: None extra_params: None 2024-10-14 19:14:01.376 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Finished fetching devices data in 1.065 seconds (success: True) 2024-10-14 19:14:06.557 ERROR (MainThread) [homeassistant.components.mqtt.models] Exception raised while updating state of sensor.luftentfeuchter_energy_totalstarttime, topic: 'tele/Luftentfeuchter_1A71AA/SENSOR' with payload: b'{"Time":"2024-10-14T19:14:06","ENERGY":{"TotalStartTime":"2024-02-04T12:07:29","Total":22.507,"Yesterday":0.016,"Today":0.013,"Period":0,"Power":0,"ApparentPower":0,"ReactivePower":0,"Factor":0.00,"Voltage":0,"Current":0.000}}' Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 657, in state numerical_value = int(value) ^^^^^^^^^^ ValueError: invalid literal for int() with base 10: '2024-02-04T12:07:29'
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 660, in state numerical_value = float(value) ^^^^^^^^^^^^ ValueError: could not convert string to float: '2024-02-04T12:07:29'
The above exception was the direct cause of the following exception:
Traceback (most recent call last): File "/usr/src/homeassistant/homeassistant/components/mqtt/models.py", line 366, in process_write_state_requests entity.async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1005, in async_write_ha_state self._async_write_ha_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1130, in _async_write_ha_state self.__async_calculate_state() File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1067, in __async_calculate_state state = self._stringify_state(available) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 1011, in _stringify_state if (state := self.state) is None: ^^^^^^^^^^ File "/usr/src/homeassistant/homeassistant/components/sensor/init.py", line 664, in state raise ValueError( ValueError: Sensor sensor.luftentfeuchter_energy_totalstarttime has device class 'None', state class 'None' unit ' ' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: '2024-02-04T12:07:29' (<class 'str'>) 2024-10-14 19:14:30.942 WARNING (MainThread) [homeassistant.components.websocket_api.http.connection] [139846979407584] Tommy from 127.0.0.1 (Mozilla/5.0 (Linux; Android 14; SM-S901B Build/UP1A.231005.007; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/129.0.6668.82 Mobile Safari/537.36 Home Assistant/2024.9.4-13806 (Android 14; SM-S901B)): Disconnected: Received non-Text message. 2024-10-14 19:14:57.618 DEBUG (MainThread) [firebase_messaging.fcmpushclient] Received heartbeat ping, sending ack: Stream ID: 0, Last: 0, Status: 0 2024-10-14 19:15:01.312 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/ring_devices method: GET json: None data: None extra_params: None 2024-10-14 19:15:01.847 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/history method: GET json: None data: None extra_params: {'limit': 10} 2024-10-14 19:15:01.848 DEBUG (MainThread) [ring_doorbell.ring] url: /clients_api/doorbots/379944255/health method: GET json: None data: None extra_params: None 2024-10-14 19:15:02.385 DEBUG (MainThread) [homeassistant.components.ring.coordinator] Finished fetching devices data in 1.073 seconds (success: True)`
Ok it's connected but not getting the events. Did you have a lot of excess Authorised Device entries at some point? If yes did you clear these down before or after upgrading to 2024.10.2?
No, I never had a lot of devices, before the update I didn't remove anything but that screenshot I posted was after I removed only one device and re-added it. Maybe try deleting the integration, removing the device and adding it again?
That's what I did and deleted the cookies as well. I got this error even though my password and verification code were correct.
Logger: firebase_messaging.fcmregister Quelle: components/ring/coordinator.py:157 Erstmals aufgetreten: 20:39:05 (1 Vorkommnisse) Zuletzt protokolliert: 20:39:05
GCM register request attempt 1 out of 2 has failed with Error=PHONE_REGISTRATION_ERROR
Sorry to interfere but the issue as I can see is that the Entitets door bell push is gone from the Ring App in HA.
I have done all the same
Updatet to: 2024.10.2
- delete the Ring App before updating to 2024.10.2 and also removed all Authorized Devices on Ring Webpage. Then reinstall the app on HA and I still only have 5 Entitets available - my Entitets with doorbell button is still gone :)
Hope this can help you :)
i have noticed the same. over the last updates the ring device in HA changed a lot. The Automation option of "Device becomes occupied" disappeared aswell.. ive used it to let the device know that i pushed the bell.
Thank you for the hints, I reverted to version 2024.8.0, removed Ring integrations, removed authorized devices, rebooted HA and updated to 2024.10.2 At the moment I think the ring status is still unknown but at this late hour today I don't want to go downstairs and ring :D I'll check tomorrow.
This morning I tried it and unfortunately it does not detect my ringtone. I'm going on vacation today so I won't be able to test further for a week.
I have the very same problem here, ring the latest version of this integration.
I can open the door using the button, but event isn't fired anymore. This started to happen after the upgrade to 2024.10.1, when before everything was working as intended.
I have never got more than two devices settled into the authorized devices list.
I must say it works again for me but with a very different automation solution. Ive used the ding entity and let it trigger if anything changes with it and when my device is in the geofence. With a 2nd automation which cancels the first when the door open triggers since the first automation starts to loop if it gets triggered once. Kinda janky but it works
Same issue for me. Neither the ring binary sensor nor the new ring events are published. Sometimes the events are published after I manually open the door by pressing the open door button in the UI, but that isn't helpful at all.
Same problem for me. The events do not work at all, cant trigger an automation with those. The (deprecated) binary sensor works sometimes, sometimes not.
Thanks a lot @spetial, I wasn't aware of that addon. Got it installed and running in a couple of minutes, seems solid so far. This integration has already been deleted.
Seems like an update to the latest HA version fixes the issue for me and the binary sensor works again. But if there are issues again I'll also use the mqtt broker.
There’s another fix coming in 2024.11 that should help with the reliability of the events.
Do I understand correctly:
There will be a new fix in 2024.11
Does this fix the issue that the entity: Doorbell Push is gone?
Which disappeared after the 2024.10.1 update :)