I have seperate vlans for IOT devices and my personal network. I’d like to understand what port/protocol plexamp announces on so that I can figureout how to relay between the IoT network where my docker plexamp players live and my private network.
I’d like to be able to control the plexamps from my phone.
Plexamps don’t register per se, except via the cloud; this allows other players to find them w/o using sometimes unreliable broadcast/multicast.
Thanks for the reply, I’m aware of the cloud registration, but I assumed there was some sort of local announcement, because I can only see the plexamps on my phone if I connect to the IoT wifi network.
I’d like to control them while connected to the regular network, am I not understanding something about how players find eachother
They do connection testing to make sure they can reach before displaying. You can see logs of this in the Plexamp logs.
You should be able to do that. You can fetch devices from the cloud the same way Plexamp does, and then use that to get a list of players and addresses.
Typically this means your router doesn’t have mDNS or SSDP reflectors\relay enabled on that vlan - at least that’s the common cause when trying to cast\airplay\send media around your network and you can’t see media centric devices. Common hiccup with vlans for things like chromecasts and Sonos speakers. Even if the cloud\internet access is managing that for PlexAmp, it might be causing some issues locally. Most consumer devices have that enabled by default, but you might need to enable the mDNS setting on your IoT vlan in your router. For example, Firewalla and Omada have that setting but you have to specifically enable it and that’s usually the missing checkbox when folks can’t “see” media devices on separate vlans. Just a thought for something to check anyways.
Plexamp uses neither.
Thanks this narrows my search significantly
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
