Any way to turn on/off a player's PSU from LMS (not just amp)?

[justi]

Hi all, As far as I can tell the current power control solutions just allow one to turn on/off an amplifier connected to an already-switched-on player. But what if we have an integrated player & amplifier, or a pair connected to the same mains power point which has a home automation power control (I'm doing this at the moment with schedules). It would be great to be able to control that situation from LMS somehow, so the server could turn on the player's PSU and wait a little while for it to power up, and similarly smoothly power it down. Might there be a way to make a "proxy" virtual player which would do this, or still display the UI for a currently disconnected/powered-down player somehow with a different power control for switching it on? Grateful for any ideas or pointers, thanks in advance.

[RobbH]

There is a plugin called LMS Event Trigger, described this way: "Execute external commands triggered by LMS events." I have no experience with it, so I cannot offer any guidance, but it sounds promising. You might be able to use it to do some of what you want to do.

[justi]

There is a plugin called LMS Event Trigger

Thanks for the pointer! I found the Event Trigger thread here - it looks like the player could be powered down this way with a disconnect notification, but not powered up before it is connected. It would be great to be able to get LMS to power up players as well.

[Roland0]

It would be great to be able to get LMS to power up players as well.

You could try the playlist open or newsong event. Not sure if this works if no player is connected.
But maybe you get a playlist cant_open event in this case, which would work as well.

[justi]

You could try the playlist open or newsong event. Not sure if this works if no player is connected.
But maybe you get a playlist cant_open event in this case, which would work as well.

Thanks for the idea! I haven't tried it but not sure how it would work from the UI? At the moment, once a client disconnects it is hidden from the UI and the panel switches to choose another player, so playlist plays etc go to a different player. This has sometimes caught me out, having a lot of players connected.

Ideally what I'd like to do is persist the powered-down/disconnected player(s) in the UI rather than have the player list dynamically shrink and grow. Perhaps some kind of "keep alive" setting for a player. I'm tempted to look at the server code to see if this could be done...

[Roland0]

not sure how it would work from the UI? At the moment, once a client disconnects it is hidden from the UI and the panel switches to choose another player, so playlist plays etc go to a different player.

The event is sent for any player, so depending on your set-up / use case the script run in response to that (which gets the player id as an argument) could implement some logic doing what you want.
Or as a work-around pair the real player with a virtual one (squeezelite -o null)

Ideally what I'd like to do is persist the powered-down/disconnected player(s) in the UI rather than have the player list dynamically shrink and grow. Perhaps some kind of "keep alive" setting for a player. I'm tempted to look at the server code to see if this could be done...

A plugin could keep track of players and add a menu to LMS
or it could modify server logic using the Sub::Override perl module

[gordonb3]

Seems to me you require some kind of integration with a home automation system that can e.g. send radio signals (433MHz/866MHz) or tuya commands. I think there may be one or two that have some support for LMS but I can't really tell if their interface is something you would want to use rather than either the default or Material.