It has been x minutes since a websocket msg was received (Unofficial Ring Integration)

⚙️ Custom Apps and Drivers
1

Hey all,

Getting this error, a ton lately...

It has been 2895 minutes since a websocket msg was received, but websocket is still connected. This really shouldn't happen. Forcing a reconnect

After a reboot, I am now seeing this warning
warn

{"deviceType":"adapter.shadow","zid":"5e2f96ce-cbc9-44d8-8936-abc","name":"Shadow Adapter","commStatus":"ok","lastCommTime":0,"lastUpdate":1732729562845,"tamper":"clear"}

App version 2.4.1.155

Thanks, Rick

2

What app or driver is producing the error?

Post a screenshot of the logs so we can see the full context.

3

Device 5011 says Home Location, what ever that is b/c that is not one of mine

1000002473
10000024731080×2400 487 KB

At least since the update the the latest, I'm only seeing the warning and not the error for the same device

4

If you click the orange "warn" text it will open the device in a new tab. You need to see what device it is, and what driver it is using.

5

Looks like some problem with your Unofficial Ring Connect integration (or maybe not a problem, as I have no idea what logging is normal for that device or what options you have enabled) -- based on a cursory glance of its code and the fact that some of it matches log entries you provided. (But it's always good to share what device and driver this is, as the above posts tell you how to do. This was a lucky find on my part.)

This is a third-party integration you added to your hub, and all messages you provided appear to be coming from that. It is not anything built-in to the hub, so you'll need to work with this developer's documentation, the developer themself, or fellow users of that integration to figure out more. Developers often provide documentation and a topic (thread) on the forum you can use for such discussion, so I'd start by finding that from wherever you obtained this code (even if it was HPM, that's not a location per se and will usually have a way to link you to the same, or you can search here). If you can't find anything on your own, asking in the topic is often a good way to reach the attention of others who may be able to help -- or you can change your topic title to something more descriptive now that you know, and it might catch the attention of others.

1 Like
6

Thanks for the replies

I wasn't aware of selecting the warning to get to the device... yes it was Ring which I am not using so I deleted it

Thanks again

7

I am using the Unofficial Ring Integration and it's been working pretty flawlessly for a couple of weeks and then I too started getting this new error/warning a couple of days ago. I'm guessing that Ring may have changed their "API". I might try tracking down the developer in the app support page,

Thanks for the clue to click the orange warn text. It takes you back to the Ring device container - the top level container associated with your location.

image
image1750×214 57.5 KB

8

Reaching out to @ardichoke or @morse.caleb to see if anyone is still supporting the code base. I installed Caleb's (no version history I can refer to unfortunately) and my Ring Alarm integration has been working great except for the new error above "Cannot create a adapter.shadow device because it is unsupported".

9

Any updates on this?

The "zid" is of a different range (the first segment is in a totally different range than any of my other devices).

It appears that some part of the Ring system is spinning up a new virtual device (type "adapter.shadow") and the code for the integration doesn't know what it is.

@morse.caleb

Also, I stumbled on this code:

That seems to be getting attention currently--but I didn't see anything upon a quick glance about the Shadow Adapter. But, it could be a good reference for code updates.

10

Sorry, I haven't been able to look at this yet. I've had a lot of things going on.

I have some theories about what's going wrong. I'm hoping to get a chance to look at it this week.

1 Like