Ring Motion Sensors are Offline #815
Replies: 14 comments 21 replies
-
|
The logs you've provided indicate that the Ring to MQTT add-on for Home Assistant is encountering an HTTP 500 (Internal Server Error) when attempting to communicate with the Ring service. This error suggests an issue on the server side of the Ring service that the add-on is trying to access. Specifically, the error occurs when the add-on makes HTTP requests to the Ring server, and the server responds with an error status, indicating a problem with the Ring server itself or with the interaction between the add-on and the server. Several key points stand out from the logs: Repeated HTTP 500 Errors: The add-on consistently receives HTTP 500 errors over multiple attempts to communicate with the Ring service, indicating a persistent issue. |
Beta Was this translation helpful? Give feedback.
-
|
same here. since last update |
Beta Was this translation helpful? Give feedback.
-
|
did you try and restart the add on? |
Beta Was this translation helpful? Give feedback.
-
|
restarted, new login, reinstalled, but still no access to sensors of the alarm bases system. Where can I download the complete log file? 2024-03-29T09:04:09.852Z ring-mqtt New device: Melville Base Station (835bff7c-xxxx-4471-xxxx-edd4d505c130) |
Beta Was this translation helpful? Give feedback.
-
|
Addons are just Docker containers, so you get the full logs via standard docker commands from the HA CLI. A doc for getting logs is at https://github.com/tsightler/ring-mqtt-ha-addon/blob/main/GET-LOGS.md but there's plenty of info out there for HA addons, ring-mqtt is not special. Your logs indicated that discovery is not completing there's no "Device Discovery Complete" message, that means that discovery for at least one location is hanging. Most likely an offline device of some-sort. This situation is already described in the logs and troubleshooting notes, every hub device, including smart light hubs, alarms, smart lights and every location the account has access to must be online for discovery to complete, otherwise the code just waits forever for the device to come online. |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Please take look at these screen shots. For me as a novice it looks like it
gets information but doesn’t forward all the sensors to mqtt.
The device discovery complete message has been seen.
Thanks!
Joachim
tsightler ***@***.***> schrieb am Fr. 29. März 2024 um 13:29:
… Addons are just Docker containers, so you get the full logs via standard
docker commands from the HA CLI. A doc for getting logs is at
https://github.com/tsightler/ring-mqtt-ha-addon/blob/main/GET-LOGS.md but
there's plenty of info out there for HA addons, ring-mqtt is not special.
Your logs indicated that discovery is not completing there's no "Device
Discovery Complete" message, that means that discovery for at least one
location is hanging. Most likely an offline device of some-sort. This
situation is already described in the logs and troubleshooting notes, every
hub device, including smart light hubs, alarms, smart lights, must be
online for discovery to complete, otherwise the code just waits forever for
the device to come online.
—
Reply to this email directly, view it on GitHub
<#815 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEEOJBFXWMYFKCPDAD5HZCLY2U7APAVCNFSM6AAAAABFNAS3I2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJQG44TM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I don't see any screenshots, I can only go on the logs you posted, there are no "Device Discovery Complete" messages in the logs you posted to this point. It is mostly a waste of time to continue this discussion without full logs, but if you choose to post only log snippets I'm forced to make guesses on what you post. |
Beta Was this translation helpful? Give feedback.
-
|
This has also started happening with all of my sensors within the last few hours. Working on updating and restarting everything. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you!
spat ***@***.***> schrieb am Fr. 29. März 2024 um 17:02:
… This has also started happening with all of my sensors within the last few
hours. Working on updating and restarting everything.
—
Reply to this email directly, view it on GitHub
<#815 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEEOJBCQ45NPWRKBBMR4NYDY2V7BHAVCNFSM6AAAAABFNAS3I2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJSGYZDA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I think I'm also having a similar issue. I'm hesitant to post my full logs file because I have found sensitive information in it (passwords in plain text). But when I look through my logs I see a lot of the HTTPError like below: |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, didn't want to offend you. Does this help?
Best regards
Joachim
Am Fr., 29. März 2024 um 14:33 Uhr schrieb tsightler <
***@***.***>:
… I don't see any screenshots, I can only go on the logs you posted, there
are no "Device Discovery Complete" messages in the logs you posted to this
point. It is mostly a waste of time to continue this discussion without
full logs, but if you choose to post only log snippets I'm forced to make
guesses on what you post.
—
Reply to this email directly, view it on GitHub
<#815 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEEOJBCB3ZEK5M5FCIDYT23Y2VNSVAVCNFSM6AAAAABFNAS3I2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJRG44TM>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
No offense at all, just gets a little frustrating to try to help people without logs. Unfortunately, whatever you are sending is not coming through, you likely need to use the Github web UI vs sending via email. |
Beta Was this translation helpful? Give feedback.
-
|
Here is the log, hopefully . |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the logs! Unfortunately, the logs show a fully working ring-mqtt, so that means the problem has to be elsewhere, the MQTT broker or the HA MQTT component. As the problem is not with ring-mqtt itself, I unfortunately can't help further, you'll have to debug the other components in the chain. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for looking into it. I now checked on mqtt explorer and messages for the sensors arrive there. Where do I find the link/mapping from the mqtt id supplied by ring_mqtt to the homeassistant binary_sensor.name? There might be the problem. |
Beta Was this translation helpful? Give feedback.
-
|
If the messages are getting to the broker, which they'd pretty much have to be for ring-mqtt to not show an error, then the problem is almost certainly on the other side. HA also has to maintain a connection to the broker, so my guess is this is not working for some reason, there should be plenty of messages in the HA logs about MQTT, and you can always increase logging level. Helping people troubleshoot HA is beyond my time and expertise, I'm not an HA person, nor is this project related to HA in anyway, you should seek assistance in troubleshooting HA issues from the HA forums. |
Beta Was this translation helpful? Give feedback.
-
|
UPDATE: I'll leave this here as it may help others encountering the same issue. My fix is in my reply to this post. ORIGINAL: I've redacted some ids and things but I think this is the main info |
Beta Was this translation helpful? Give feedback.
-
|
I've managed to fix this for myself using @tsightler's great (and simple and obvious) guide here: https://community.home-assistant.io/t/ring-device-integration-via-mqtt-w-video-streaming/102105/1195 In fact, it was the first item (restart the ring-mqtt addon) that worked for me. Note to others stumbling across this: restarting Home Assistant using this: If you are having the same issue, read this first: https://community.home-assistant.io/t/ring-device-integration-via-mqtt-w-video-streaming/102105/1195 Hey @tsightler, If there's anything I could assist with to improve ring-mqtt to attempt to recover from the ring issues please shout as I'd be happy to help. |
Beta Was this translation helpful? Give feedback.
-
|
Can confirm...turning it off and on again worked for me... 😊 At least I learned something about home assistant.
|
Beta Was this translation helpful? Give feedback.
-
As ring-mqtt does not maintain the API connection itself, but rather is dependent on ring-client-api, feel free to submit any pull requests to improve the behavior there. Any improvements to ring-client-api will help all projects using it. I also attempt to help the maintainer of ring-client-api but, due to other personal responsibilities in the last 6 months, there just hasn't been much time to work on it and nobody else has stepped up to contribute anything other than complaints. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for hinting on the guide. Unfortunately neither restarting,
reauthorising nor reinstalling helped. However we have been able narrow the
problem. Message from ring are received by MQTT. It seems there is no
matching between the mqtt message and the binary.sensor-name.
Russell K ***@***.***> schrieb am Sa. 30. März 2024 um 12:11:
… I've managed to fix this for myself using @tsightler
<https://github.com/tsightler>'s great (and simple and obvious) guide
here:
https://community.home-assistant.io/t/ring-device-integration-via-mqtt-w-video-streaming/102105/1195
In fact, it was the first item (restart the ring-mqtt addon) that worked
for me.
Note to others stumbling across this: restarting Home Assistant using this:
image.png (view on web)
<https://github.com/tsightler/ring-mqtt/assets/4568306/711764af-709e-4dfc-bd4e-c34d3503262d>
doesn't fix the issue (as it doesn't actually restart the addons)
If you are having the same issue, read this first:
https://community.home-assistant.io/t/ring-device-integration-via-mqtt-w-video-streaming/102105/1195
Hey @tsightler <https://github.com/tsightler>,
I can imagine this gets very frustrating for you as this seems to be
largely due to an issue on the Ring side rather than with the ring-mqtt
code.
If there's anything I could assist with to improve ring-mqtt to attempt to
recover from the ring issues please shout as I'd be happy to help.
—
Reply to this email directly, view it on GitHub
<#815 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEEOJBAFBH4YUGNEN2V7XFDY2Z6TVAVCNFSM6AAAAABFNAS3I2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DSNJYGQ4TQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I am just trying to get the Ring-MQQT up and running. I cannot see any of my sensor either. Here are my logs. Can you please give me some guidance please?| Ring-MQTT with Video Streaming |
|
Beta Was this translation helpful? Give feedback.
-
|
Quite literally all you have to do is install everything and don't touch a single setting, everything will "just work" with automatic configuration. There's generally no reason to do anything other than defaults unless you are using something that requires something special. Even then, just create an HA user for any external consumers and the Mosquitto addon will allow those external clients to connect with the HA username/password. For some reason so many tutorials have people setup all kinds of user accounts manually, but it's just not needed in 99% of cases. You can just follow the steps in the HA documentation, and not change anything. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much for all your help. I appreciate it and I thank you for all you do for all the others. Have a great weekend. |
Beta Was this translation helpful? Give feedback.
-
|
Here is what I have done so far. I uninstalled MQTT in integration, then hit the reset to default on both Mosquitto broker and Ring-MQTT with Video Streaming. Then I restarted HA. The only thing I changed was mqqt_url in configuration to mqtt://mqtt-user:1234 @192.168.222:1883 of the Ring-MQTT. Below are the logs for you viewing and advice. The Ring MQTT:
|
Beta Was this translation helpful? Give feedback.
-
Why? Just leave it on auto detect, that was the entire point, no user needs to be created in Mosquitto, and no URL needs to be manually changed. When using the default configuration HA automatically generates an internal account for Mosquitto called "addons", with a cryptographically complex password, and then makes that account information available to addons via an internal API. The addon simply calls this API to get the MQTT connection and account information and uses that to connect. Using defaults there is zero reason to make any changes to the ring-mqtt at all for it to work. |
Beta Was this translation helpful? Give feedback.
-
|
Do you know why none of the Ring motion sensors are not showing up in HA? |
Beta Was this translation helpful? Give feedback.
-
|
You are a genius, everything is working. Thanks again for all you great help. Enjoy your week. |
Beta Was this translation helpful? Give feedback.
-
|
Using MQTT integration?
mikefrantz ***@***.***> schrieb am Sa. 8. Juni 2024 um 13:42:
… Do you know why none of the Ring motion sensors are not showing up in HA?
—
Reply to this email directly, view it on GitHub
<#815 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEEOJBHVY7TA3U3PLVKKEHDZGLU37AVCNFSM6AAAAABFNAS3I2VHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TOMJSHE2DS>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, all the cameras show up through the MQTT in integration, but I’m not seeing any of my motion sensors |
Beta Was this translation helpful? Give feedback.
-
As of 8 hours ago, my ring motion sensors have been offline.
I've tried rebooting, reconfiguring, and reinstalling the add on but nothing solves the issue.
Beta Was this translation helpful? Give feedback.
All reactions