jellycli VS jellyfin-expo

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.

Jellyfin Mobile issue

Yeah this is exactly right. I am hoping to have download support available as a user setting under a “beta” status in the next release of the expo app. Progress can be followed here.

The iOS app is open source, so you are welcome to contribute a PR: https://github.com/jellyfin/jellyfin-expo

It's maintaned by a single developer in his spare time, so I'm sure he'd appreciate it!

Timelines are hard, especially when it's an entirely volunteer ran project and there's effectively only one person working on the client in question (who also works on 2-3 other clients as well, and has a day job). So the "when" is basically whenever somebody with the time and skills is willing to work on implementing the things in the linked issue here, which would probably be the best place for you to follow if you want updates.

The current implementation in development is really barebones… additional work on it is being tracked here: https://github.com/jellyfin/jellyfin-expo/issues/372

Not yet, but it is in the works…