Headless Pi: Remote control issues

Plex Labs
1

Server Version#: 1.25.5.5492
Player Version#: 4.7.4
<If providing server logs please do NOT turn on verbose logging, only debug logging should be enabled>

I have PlexAmp headless on a Pi and PlexAmp on Windows and iOS. Each day I have to rename the headless plexamp player for the remote plexamps (the Windows and iOS apps) to be able to control the headless player. On the apps I have to open the cast dialog, refresh it to get the new player name from the headless player, then the app can control the player. Very annoying.

I also find that in the web UI for the headless player, I can play an album, but when I click on track or the 3-dot icon, nothing happens.

Anyone else seeing these issues? Any ideas?

2

Where and how are you renaming it?

Most likely thing is that the IP address of the PI is changing for some reason (aggressive DHCP server?)

3

In the web gui, settings, advanced, player name
I use DHCP reservations on my router, so the Pi PlexAmp effectively has a static DHCP address.

4

That would trigger a refresh of publishing the IP to plex.tv, which could explain why connectivity started working, but not why the address changed.

If you could zip up your Plexamp logs on headless, I’ll have a look.

5

OK, you’re prompt for the logs had me look at them (sorry I didn’t before), and I discovered my second headless pi on the network as well. Once I got PlexAmp working on one pi, I cloned it to another pi. My guess is that is a no-no. I’m guessing some unique ID for the device is part of the token, and a second headless pi needs to get its own token. Am I close?

6

ding ding ding ding.

7

Thanks. Is there a way, a file to delete, so I can reset the token?

8

Nuke ~/.local/share/Plexamp/Settings

1 Like
9

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.