Closed seniorm0ment closed 2 years ago
mcarlton00
commented
2 years ago Are you on the latest version? What's happening is that something has interrupted network communication to your server and the websocket connection has failed. In version 1.0.3 I added a retry system that should re-establish the websocket connection and allow casting to continue. (#115)
jonzobot
commented
1 year ago I thought I'd revive this issue as I seem to be having the same problem on 1.0.4. I'm not sure why, but it does not appear to have been fixed by the auto-reconnect, at least for me. I'll need to dig into the logs and report back.
For clarity, I can access Mopidy and Jellyfin separately, but somehow the cast option goes away after a couple of days.
The option to cast to Mopidy randomly disappears from Jellyfin. I'm unsure if this is related to Jellyfin, or Mopidy-Jellyfin, or something else. However if I click off and back on my Mopidy-Jellyfin device, it shows back up once it boots. I'm wondering if it just stops sending a signal to Jellyfin or something after being asleep for a certain amount of time I'm unsure.
DietPi on Raspberry Pi, Jellyfin on Windows 10, everything on latest stable. Doesn't matter which clients I'm casting from they all present this issue.