When I close it the music stops and I can no longer find the device on my Plex UIs
That sounds like the service isn’t working normally for whatever reason.
What you describe is what I would expect if you:
- didn’t have plexamp.service enabled and started
- logged in over ssh
- ran
node js/index.jsto start Plexamp - closed your SSH connection thus terminating the shell that’s running Plexamp and killing it.
You can try to fix (1) and avoid (3), or you can just format the sd-card and reinstall, carefully following the install instructions because I don’t know how installing a service would go wrong, but I know the instructions work when the admin is pi
commands that are helpful:
sudo systemctl status plexamp
journalctl -b -u plexamp
I’m a little bit confused because the guide says to use the command in #3 to start the service. Is it not good or not permanent?
I’ve got it to stay up and running now but just wondering where it went wrong.
Myself I only use node js/index.js once the very first time during install like the instructions describe. There’s nothing wrong with that command, but Plexamp won’t be running after reboot if that’s all you do. So the directions further explain how to avoid having to type it after every reboot and instead use a service. That make sense?
To know what went wrong is more difficult than making it work, but it could be if you used odinb1 script from a while back, your plexmp.service might have been constructed in a suboptimal way for today’s Plexamp.
The script cleans up the old service-config if it is there when you upgrade. So, should be no leftover.
2 Likes
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
