When my player works, it works great.
But sometimes, it gets in a funk where it doesn’t want to do anything. I think there’s some ghost players showing up causing interference.
So today at 3:30ish I take a ride to run some errands:
- Start my car, Pi powers on
- Start phone hotspot - Pi joins it
- Start plexamp - select TaurusX player - play tunes
- works great
- Get to destination, power down Pi, power off car
After my errand, at 4ish, I get back in the car
- start car, pi powers on, rejoins hotspot
- go to plexamp, it shows the player cycling through songs without playing them - doing like a dance of “can’t play that one, what’s next? can’t play that one, what’s next?”…
What unfolded was a series of restarts, and an inability to get it to play anything. I could only ever get it to do the constant skipping/cycling, or not connect to the player, or appear to be playing but not.
Confirmed plexamp app on phone could play from my device.
What I observed that is a red flag to me is that when I powered off the pi, and force stopped the plexamp app on my phone, and then restarted the plexamp app on the phone, when viewing devices to cast to, the TaurusX player would never disappear, despite it being powered off.
Even 15 minutes later when it was still off, it still showed as a device to try and connect to.
I suspect for some reason plex is hanging onto the Pi after it turns off, and it requires some time for something to cycle for the ghost player to disappear, otherwise it’ll try to play to the ghost player and fail, and not see the real restarted player.
Now it is 4:41, Pi is still off, and when I open the app it only shows this device - ghost is gone.
I pulled the SD card and grabbed the logs, which I have attached. Not sure if Pi player logs will be adequate, or if you’ll need other logs. Let me know.
