Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread RobbH
squeezebox153 wrote: > I have 3 raspberry pi's each running picore & a LMS. Each RPi has a > dedicated amplifier. My dashboard runs via SmartThings to orchestrate > the player commands. I can now run independently & synchronized. > > Perhaps I could get away with 1 LMS but I achieved what I

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread squeezebox153
RobbH wrote: > Isn't that what you want? I have 3 raspberry pi's each running picore & a LMS. Each RPi has a dedicated amplifier. My dashboard runs via SmartThings to orchestrate the player commands. I can now run independently & synchronized. Perhaps I could get away with 1 LMS but I

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread RobbH
squeezebox153 wrote: > All of them have static IP's and work fine from my dashboard. The only > thing I need to do is get the primary player to manage the other > players. > > https://i.imgur.com/KNIqoSg.png Slartibartfast has already given you excellent advice. Just to elaborate a bit, in

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread Greg Erskine
I fear having multiple LMS servers may cause you more problems than it solves. Greg Erskine's Profile: http://forums.slimdevices.com/member.php?userid=7403 View this thread:

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread squeezebox153
RobbH wrote: > Do you power off your three players when they are not in use, or do you > leave them on? > > If you do power them off, would you be willing to leave one of them on > all the time, instead? The players are always on but reboot nightly. I was able to have the primary player

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread RobbH
squeezebox153 wrote: > All of them have static IP's and work fine from my dashboard. The only > thing I need to do is get the primary player to manage the other > players. > > https://i.imgur.com/KNIqoSg.png Do you power off your three players when they are not in use, or do you leave them

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread slartibartfast
squeezebox153 wrote: > All of them have static IP's and work fine from my dashboard. The only > thing I need to do is get the primary player to manage the other > players. > > https://i.imgur.com/KNIqoSg.pngIf the primary player is always the same one > just have LMS on that one and leave the

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread squeezebox153
All of them have static IP's and work fine from my dashboard. The only thing I need to do is get the primary player to manage the other players. https://i.imgur.com/KNIqoSg.png squeezebox153's Profile:

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread kidstypike
slartibartfast wrote: > It seems he wants to be able to turn on any individual Pi and have a > server and player. Never mind the chaos of having three different IP > addresses for the servers and having players that can attach to any one > of them. > > Sent from my Pixel 3a using Tapatalk

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread slartibartfast
kidstypike wrote: > You don't need LMS on each player for this.It seems he wants to be able to > turn on any individual Pi and have a server and player. Never mind the chaos of having three different IP addresses for the servers and having players that can attach to any one of them. Sent from

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread kidstypike
squeezebox153 wrote: > > > I have an instance of LMS on each of my picore players as I want to have > individual playing ability and synchronized. You don't need LMS on each player for this. *Server - LMS 8.3.0 *Pi4B 4GB/Argon one case/pCP 8.0.0 - 75K library, playlists & LMS cache on SSD

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread squeezebox153
RobbH wrote: > I think you are referring to something that's usually called > synchronizing players. You have several players playing the same thing > and all of them can be controlled at the same time from any of the > synchronized players. Is that correct?. One player to manage the other

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-08 Thread kidstypike
squeezebox153 wrote: > Sorry for not being clear. In LMS, when I go to Manage Players, I am > able to move players from my secondary players to my primary one. This > configuration is lost in a reboot. > > https://imgur.com/a/0zWZ2Pi Have you got more than one instance of LMS running? You

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-07 Thread RobbH
squeezebox153 wrote: > Sorry for not being clear. In LMS, when I go to Manage Players, I am > able to move players from my secondary players to my primary one. This > configuration is lost in a reboot. > > https://imgur.com/a/0zWZ2Pi I think you are referring to something that's usually

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-07 Thread squeezebox153
Sorry for not being clear. In LMS, when I go to Manage Players, I am able to move players from my secondary players to my primary one. This configuration is lost in a reboot. https://imgur.com/a/0zWZ2Pi squeezebox153's

Re: [SlimDevices: Unix] Programmatically manage PiCore players

2021-11-06 Thread Michael Herger
I have 3 picore's and each one reboots nightly. I have my primary picore managing the other two, but after a reboot, this association is lost. Is there a way to programmatically re-associate them after reboot instead of having to manually do it? Please elaborate a bit what "managing" means in

[SlimDevices: Unix] Programmatically manage PiCore players

2021-11-06 Thread squeezebox153
I have 3 picore's and each one reboots nightly. I have my primary picore managing the other two, but after a reboot, this association is lost. Is there a way to programmatically re-associate them after reboot instead of having to manually do it?