Plexamp as remote


#1

Which players can we control with plexamp? I was hoping I could control android from it, but my player doesn't appear in the list.


#2

In theory, any Plex player (but clearly they need to have the remote control option available). I’ve tested with Android and it seemed to work fine. If you select any of the player options in the menu (including the currently selected one) it’ll refresh the list, which can be helpful…


#3

Hmm that didn’t seem to work. Are there any other ways to get it to recognize it? Or something I can do to troubleshoot?


#4

Are you positive the remote control functionality is enabled on your Android device, and you’re signed in?


#5

Yep, double-checked. “Advertise as player” is enabled, and i’m signed in.


#6

In that case you’d need to check Application.log and see why it’s not able to find a connection for your Android player.


#7
Feb 09, 2018 18:07:14.963 INFO - APP: Switching to new player 
Feb 09, 2018 18:07:14.969 INFO - DEVICE: Fetching latest provider list from cloud.
Feb 09, 2018 18:07:14.969 INFO - DEVICE: Fetching latest list from cloud.
Feb 09, 2018 18:07:15.601 INFO - DEVICE: Fetched 7 devices from the cloud.
Feb 09, 2018 18:07:15.602 INFO - DEVICE: Finding best connection for Nexus 5X
Feb 09, 2018 18:07:15.603 INFO - HTTP: Issuing request to http://192.168.1.14:48606/resources
Feb 09, 2018 18:07:15.603 INFO - DEVICE: Finding best connection for Pixel 2
Feb 09, 2018 18:07:15.603 INFO - HTTP: Issuing request to http://<redacted>:41783/
Feb 09, 2018 18:07:20.606 WARN - DEVICE: Player connection http://192.168.1.14:48606 didn't work for Nexus 5X: timeout of 5000ms exceeded
Feb 09, 2018 18:07:20.606 WARN - DEVICE: Connection testing failed for Nexus 5X
Feb 09, 2018 18:07:20.607 WARN - DEVICE: Server connection http://<redacted>:41783 didn't work for Pixel 2: timeout of 5000ms exceeded
Feb 09, 2018 18:07:20.607 WARN - DEVICE: Connection testing failed for Pixel 2
Feb 09, 2018 18:07:20.607 INFO - APP: Refreshing player/server menu.
Feb 09, 2018 18:07:25.810 INFO - DEVICE: Persisting devices because Google Drive was dirty.
Feb 09, 2018 18:07:25.811 INFO - DEVICE: Persisting devices.

#8

To be clear, Pixel 2 is the one i’m trying to connect to


#9
DEVICE: Server connection http://<redacted>:41783 didn't work for Pixel

If you try to connect to/curl that URL, does it work?


#10

Nope. Can’t connect.


#11

Then it appears there’s some issue reaching the app on the Android phone; not sure why a priori, it works over here. You sure there’s no NAT aspect?


#12

I don’t believe so. Both devices are on the same subnet.


#13

I’ve attempted disabling and reenabling remote control, allowing secure connections, etc. on Android. I also attempted to connect with my laptop running plexamp connected via personal hotspot to my phone directly. No dice. Is it possible that the server is reporting a bad IP to connect to for the Android device?


#14

FWIW, PMP is able to control my phone just fine.


#15

Huh, I’m really confused; like I said, it works on my Android phone, so I’m confused as to what the issue could be. Per above, it looks like it’s using an incorrect URL to try to connect to the player. Any idea what PMP is using, and why it might be different?


#16

It seems to be using a 10.0.0.0 address, while the rest of my network is on 192.168.0.0. Not immediately clear why.


#17

To clarify ~ PMP is using 10.x and working?


#18

Whoops, that’s what Plexamp is checking. Not sure how to check on PMP, but Plex web shows the correct local address (192.168.1.4) in the response to the /clients request


#19

Also, the android device seems to stop being available for control by Plex web after it has been locked/the app has been in the background for awhile, even though it’s still playing music.


#20

If you can, hit https://plex.tv/api/v2/resources.xml?auth_token= and see how your Android device is showing up. This should explain how Plexamp is trying to find it. The web app might be availing itself of other indirect methods to find the phone. If the address coming from resources isn’t correct, this should be reported to the Android folk :sweat_smile: