I got some issues getting Ring to work properly. I’ve tried both the “official” ring integration and ring-mqtt.
Official one works well after setup but randomly will stop updating the ding event … it will either turn unavailable or just not update anymore.
The ring mqtt addon appears to setup fine but I can’t get the “Ding” event sensor to work at all in this integration.
I’ve added and removed both integrations a couple of time and also removed any unnecessary authorizations from ring.
Has anyone encountered these issues before and can help me out?
I have not any issues with the Ring Integration, but to be fair I live in a condo building and the Ring doorbell is on my laundry room and is not often used.
The core Ring integration mimics the Ring app, using the same API/endpoints as the Android/iOS apps use.
The ring-mqtt add-on uses an unofficial API.
Both have their use cases and I do use both of them, but I’m careful and heed the warnings stated in the ring-mqtt github/wiki. The most important warning is that Ring cameras are not designed to be used for continuous 24/7 streaming. Doing so will mess up Ding events and Motion events. To circumvent this, use snapshots instead, along with ding/motion events, and only stream when necessary, via manual checking or via ding/motion events.
EDIT: As far as Ding/Motion events are concerned. The core integration will poll for that data, but Rings design is to null those sensors when there hasn’t been any event after a certain length of time. This will make the sensors appear as unknown. This is normal behavior from what I’ve experienced. As long as it doesn’t appear as unavailable, all is good.
Logger: firebase_messaging.fcmpushclient
Source: /usr/local/lib/python3.13/site-packages/firebase_messaging/fcmpushclient.py:717
First occurred: 06:39:36 (3 occurrences)
Last logged: 06:39:36
Unexpected exception during read
Traceback (most recent call last):
File “/usr/local/lib/python3.13/site-packages/firebase_messaging/fcmpushclient.py”, line 687, in _listen
elif msg := await self._receive_msg():
^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/site-packages/firebase_messaging/fcmpushclient.py”, line 300, in _receive_msg
r = await self.reader.readexactly(1) # type: ignore[union-attr]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/local/lib/python3.13/asyncio/streams.py”, line 758, in readexactly
raise self._exception
File “/usr/local/lib/python3.13/site-packages/firebase_messaging/fcmpushclient.py”, line 210, in _do_writer_close
await writer.wait_closed()
File “/usr/local/lib/python3.13/asyncio/streams.py”, line 358, in wait_closed
await self._protocol._get_close_waiter(self)
TimeoutError: SSL shutdown timed out
Logger: homeassistant.components.ring.coordinator
Source: helpers/update_coordinator.py:435
integration: Ring (documentation, issues)
First occurred: November 30, 2025 at 04:02:57 (5 occurrences)
Last logged: 13:17:20
Error fetching devices data: Error communicating with Ring API
You should report this on GitHub if you haven’t already. I do find it odd that the newer core integration for Alexa Devices has already reached Platinum status, despite it’s in active development and not fully featured and mature, yet the Ring integration is still at Bronze level. I wonder if it’s still being actively maintained…? But considering it’s a “security” system, one would think the developers would prioritize it to the highest level.
