Websocket ticket requests fail with 500 server error

[yieldhog]

Describe the Bug

No longer able to connect to ring

Steps to Reproduce

Reloaded add-on

Expected Behavior

NA

Log Output

2024-06-18T16:54:04.643Z ring-mqtt WARNING - Unhandled Promise Rejection
2024-06-18T16:54:04.643Z ring-mqtt Response code 500 (Server Error)
2024-06-18T16:54:04.643Z ring-mqtt HTTPError: Response code 500 (Server Error)
    at Request.<anonymous> (/app/ring-mqtt/node_modules/ring-client-api/node_modules/got/dist/source/as-promise/index.js:118:42)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Screenshots

No response

Config File

Na

Install Type

Home assistant add-on

Version

5.6.6

Operating System

Home assistant OS

Architecture

Na

Machine Details

Intel nuc

[zarzycki]

Same. Also forced a new authentication via the UI which succeeded, but the problem persists.

[TheLinuxTrucker]

Just wanted to add that I am having the same issue starting a couple of hours ago. Ran through the usual steps to fix and nothing seems to help. I’m using the separate docker container, updated today after problems started. So it isn’t just the add-on. Maybe Ring is having some issues today?

[calisro]

Please THUMBS up the original thread if you have hte same issue rather than adding "me too" comments.

[tsightler]

Please read my comments here:

dgreif/ring#1431 (comment)

As this is an issue coming from ring-client-api due to either a temporary outage or permanent change of the Ring server infrastructure, there is nothing that can be done with it here. I will continue to research and try to resolve it in ring-client-api. If anyone has unlimited time to go digging, feel free to use the information there to submit a PR.

[sofapi]

I’m still not able to get past the 500 error after multiple reboots/reloads etc. Any advice or is it a case of just waiting to see what happens now.

[tsightler]

I’m still not able to get past the 500 error after multiple reboots/reloads etc. Any advice or is it a case of just waiting to see what happens now.

It seems to be up and down, I'm also getting the error again. It had some period of up and down this morning as well. At this point, if you don't know how to manually change the URL as mentioned in the linked ring-client-api thread, then best bet is just to wait. Either it will stabilize, or we'll push out an update that uses the new URL.

[tsightler]

ring-mqtt v5.6.7 has been released with a fix for this issue.