jellyamp VS jellycli

I don’t know what specific features Plexamp has, but Jellyfin has https://github.com/m0ngr31/jellyamp

Jellyamp

Just updated to v1.1.1: https://github.com/m0ngr31/jellyamp/releases/tag/v1.1.1

It doesn't compare to plexamp, simply because it's not as far along as plex, most of the development is focused on getting the main features working. There is an app in infant stage right now called JellyAMP.

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.