Suddenly since 18.40 ish BST im getting this error:
**
apiRequestTickets HTTP error. Status: 500, Error: Server Error. Body: {"error":860004,"msg":"No available app brokers"}
**
Has worked without a hitch for a year plus. App says still logged in, but websocket shows as closed of course.
Anyone else having similar issues indicating a blip at Rings end?
Failing that, any clues as to what the issue might suddenly be my end? Hub reboot didnt fix.
Thanks.
Answering my own question HA having the same issue, and it looks like it is an API change rings end. Changing API endpoint appaears to fix the issue.
Yep, changing the app API to https://prd-api-us.prd.rings.solutions/api/v1/ at around line 1694 (last line, that is https://app.ring.com/api/v1) fixes it and reconnects the websocket.
I just released v0.5.7 which should fix this.
I also released beta v0.6.0.3 with the same fix and a lot of other stuff I've been meaning to release. I've been using the new features myself for quite a while. If no one has issues, I'll move it out of beta.
Can you specify where the screenshot comes from? One of the devices, one section in the app, etc.?
Momentary HTTP virtual switch that @SoundersDude uses instead of IFTTT.
Here's how mine looks as an example with the token removed:
There should be instructions somewhere on this thread on how to set it up if you aren't sure.
Is the device IP the Hubitat hub or an Alexa device. I guess that is probably my real question. LOL
It’s the Hubitat IP
Hello everyone, is there anyway to access BOTH the camera and light attributes of the Ring Floodlight Camera Pros? I was able to setup the Cameras + Siren and pull the feeds into the dashboard, but I am failing to setup the Light controls as well.
Tagging @morse.caleb on your post, @Haven.
Hi all, this app has basically been rock solid for me since the start, but for some reason randomly stopped working in the early hours of this morning and I noticed that my house had not disarmed as it should have this am. My API logs show this message:
Cannot send request because socket is not connected: {"channel":"message","msg":{"dst":"35e6aa83-4c58-41ef-5f9d-d81ea8e337da","msg":"DeviceInfoDocGetList","seq":1}}
What I've done:
Logged back into my Ring account via the app.
Clicked initialise on the API screen
Tried a HPM repair
...these things have not worked and the API is incorrectly showing me as 'Home' instead of 'Disarmed' and the websocket as 'closed' - nothing changes this even when I manually select the mode change. Any ideas?
Further to the above it looks like none of my devices are responding at all. Pretty worried now, any idea on how to fix? If I uninstall and reinstall everything, will my devices and their associated automations just come back or am I firmly in re-do/re-setup everything turf?
Thanks again.
At the top of the app, does is show Ring Account Information (Successfully Logged In!)?
Does the parent device show websocket : connected?
@harmony7 's suggestion of re-booting the hub reconnected the websocket, many thaanks!
When was the last time you updated the app? The API update was fixed back in June.
App was fully uo to date. No idea why this suddenly happened
I just had the same issue as @mabstrategy ... websocket showed as closed. I tried initializing, re-signing in, etc... log shows the websocket would keep trying to reconnect every 5 minutes but never reconnected.
Rebooted the hub and now the websocket shows connected and everything is working.
I'm on 2.3.9.180 (latest platform version)
Same happened to me yesterday. Reboot fixed it.
I now have a RM automation that will notify me and reboot the hub if the websocket remains disconnected for more than 1 hour.
I have been relying on this integration to ensure my doors remain locked, so training my family to ensure they are otherwise locked doesn’t work very well unfortunately…
Mind sharing a screenshot of what that rule looks like?
Download the Hubitat app
