Open morph166955 opened 8 months ago
Could you please tell us if this is still a problem with JUPnP 3.0.1 which is used by OH 4.2 milestone 2 ?
I just updated to snapshot 4092, I'll monitor for this. Updating the big system takes some effort these days so I don't do it as often.
+1 @lolodomo
I have the same issue on SNAPSHOT 4082, with a fairly large (>20) Sonos installation. All Sonos devices go into ERROR state, only restarting the jupnp bundle resolves the issue
I considered putting this under addons but it looks like it's impacting multiple addons and restarting jupnp seems to fix this. This has happened a few times now for reasons I can't explain. It looks like it just crashes from what I can tell. Restarting the bundle seems to make everything come back immediately. Usually my threads graph looks like the far left and right of the one below. As soon as it crashes the entire thing flatlines until the bundle is restarted. To note, in my config neeo and globalcache have the IPs set in the thing config which is why I assume they came back where sonos just has the udn.
To note, I'm on snapshot 3659 currently but this happened a few times on earlier versions as well. I can't remember if this happened prior to the 2.7.1 update. This didn't happen on the 4.0 snapshots or early on in the 4.1.