The symptoms are that plex works fine across multiple devices when used locally. Plex server running on QNAP 251+ runs fine and shares to samsung TV, plus windows 10 pcs or android S20+ and S21. Use plexamp to play a song locally on any system and it works fine. The moment you try to cast from one device to another, most importantly from plexamp 4…2.3 on a Samsung S20 to plexamp 4.2.2 on an RPI 4 8GB running the latest PiOS 64 bit, and a couple of windows 10 PCs…
Plexamp cannot cast to any other device reliably. All devices worked well at one point as a proof of concept. Playing plex content from the server on the local plexamp device always works, but almost always fails when casting from one device to another. I either get the message “could not connect to device” or just an endless spinning wheel" or just sits at the music selection screen but pressing play just gives a flash of playing before stopping and leaving you at the song play selection screen. It has worked at one moment or another across all systems, but those moments were fleeting.
The ideal usage scenario is to play on android mobile or windows PC plexamp and cast to RPi4 that outputs to USB DAC and onto hi-fi system.
I’m trying to cast from android or windows to RPi4. I’m trying to figure out how to extract the RPI logs to append here. Can you tell me how to extract the RPi logs?
I’m still learning how best to interpret these logs, but I don’t see the Pi ever registering successfully … I had an issue recently that required some changes to the plexamp.service file to wait for IP address … @elan described in this post
I appreciate the help. I tried the help in the article you mentioned. No luck. No change. But while fiddling with it, I noticed something odd. The last line seems like something might be out of place.
~ $ sudo systemctl status plexamp
● plexamp.service - Plexamp
Loaded: loaded (/lib/systemd/system/plexamp.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-08-01 16:40:09 EDT; 12min ago
Main PID: 4147 (node)
Tasks: 21 (limit: 8986)
CPU: 8.814s
CGroup: /system.slice/plexamp.service
└─4147 /usr/bin/node /home/drvrage/plexamp/js/index.js
Aug 01 16:40:09 raspberrypi systemd[1]: Started Plexamp.
Aug 01 16:40:10 raspberrypi node[4147]: Starting Plexamp.
Aug 01 16:40:10 raspberrypi node[4147]: DEVICE: No provider for source 2376252119e1b1d975a00e47e2ae9b60d3db434e
I think the core issue is that the Pi isn’t registering a valid address, which likely implies it’s trying to do so before the network is up.
Aug 01, 2022 12:17:09.880 [Javascript] INFO - Companion: Registering device at .
The next release (out today!) will fix that (and other issues). If you’re impatient, just restart the plexamp service as that should ensure it’s registered after the network is up.
I’m not having a good day. I did restart the service and got it working for a wee bit. Left the house on an errand and when I can back, my android was out of sync (likely because I left the wifi-network) and it never came back. Even after clearing android appdata and starting from scratch.
I tried to install 4.3 and screwed up something so I restarted from a clean 64 bit image. might be a step back for me. The good news is it looks like 4,3 installed ok and it cleaned up the previous error I mentioned in the last line.
sudo systemctl status plexamp
● plexamp.service - Plexamp
Loaded: loaded (/lib/systemd/system/plexamp.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-08-01 23:09:06 EDT; 10s ago
Main PID: 1749 (node)
Tasks: 16 (limit: 8986)
CPU: 2.719s
CGroup: /system.slice/plexamp.service
└─1749 /usr/bin/node /home/pi/plexamp/js/index.js
Aug 01 23:09:06 raspberrypi systemd[1]: Started Plexamp.
Aug 01 23:09:08 raspberrypi node[1749]: Starting Plexamp 4.3.0
But now I can’t hit the web ui at http://[ip]:32500
None of my devices can even see the RPi at all.
I can’t find the logs in ~/.cache/Plexamp/log the .cache folder only has chromium, lxsessions and menus folders even when looking at hidden folders. So no updated logs to offer.
