jellycli VS jellycon

If using mopidy is not the best way to approach this, I'm open to alternatives. I've tried jellycli, but it currently has some track selection issues that make it unworkable for me. (It also uses ~50% of my raspberry pi's CPU, while the python-based mopidy uses ~2%, so I really question what's going on with that go program.) I also have a Chromecast Audio available, but before I go to the effort of creating a letsencrypt cert and overriding DNS on my network I'd rather exhaust the Raspberry Pi options.

Another option could be to run jellycli (https://github.com/tryffel/jellycli) on the server. It has a headless option which looks like it should appear as an option on the Jellyfin "Play on" menu. This would allow you to use a common interface whether playing locally or via the NAS conneted speakers.

Jellycli - Terminal player written in Go with remote control abilities

JellyCLI

There's also jellycli or Preserve that are other options.

jellycon

JellyCon - Behaves more like a standard Kodi streaming addon. Media is accessed primarily by going through the Add-ons -> JellyCon menu, however you can set up menu options to link to it and show info on the home screen. It also allows easier switching between multiple Jellyfin servers or users since it doesn't have to rely on syncing all the metadata down. By not having metadata synced, it has to request info from the server which can take a bit more time when you're browsing (typically only a second or two in my testing), but you don't have to wait for the database to sync or keep it up to date.

This sounds familiar to something reported here. Right now my best guess is the skin is populating before the addon is fully loaded and then doesn't get updates, but I haven't had a chance to confirm that yet.

JellyCon - Behaves more like a standard Kodi streaming addon. Media is accessed primarily by going through the Add-ons -> JellyCon menu, however you can set up menu options to link to it and show info on the home screen. It also allows easier switching between multiple Jellyfin servers or users since it doesn't have to rely on syncing all the metadata down. By not having metadata synced, it has to request info from the server which can take a bit more time when you're browsing (typically only a second or two in my testing), but you don't have to wait for the database to sync or keep it up to date.

JellyCon - Behaves more like a standard Kodi streaming addon. Media is accessed primarily by going through the Add-ons -> JellyCon menu, however you can set up menu options to link to it and show info on the home screen. It also allows easier switching between multiple Jellyfin servers or users since it doesn't have to rely on syncing all the metadata down. By not having metadata synced, it has to request info from the server which can take a bit more time when you're browsing (typically only a second or two in my testing), but you don't have to wait for the database to sync or keep it up to date.