When Changing Streams, Zones move to the wrong stream

[TerribleTesla]

When changing a Stream source to another stream, zones that were previously attached to that zone move to a different stream and start playing.

"Default" Streams:

When trying to change the "AmpliPi Chromecast" Stream to something else, the zones that were previously attached there 'move' to a different stream (And if they were not muted, will start playing that stream, in this case Internet Radio)

"AmpliPi Chromecast" changed to the "Turntable" Input (Both RCA inputs). The zones now are moved to the "101.5 WIBA" stream (In addition to the previously attached zone [office], and the previously attached zones are no longer attached:

Also, when these streams rearrange, automations that I have leveraging the API get messed up too.

I expect something to be at id=0, but now after the streams rearrange, it's not at id=1.

[TerribleTesla]

Is this just expected behavior and it is what it is, or is this something that can be fixed to prevent the outputs from shifting between zones?

[TerribleTesla]

Just asking one more time, is this expected and something I should just 'deal with it'?

[SteveMicroNova]

Apologies for the radio silence on this, it seems my notification settings on this repo weren't set up correctly or got changed at some point

Is this expected behavior

Somewhat. We've implemented zones "following" their stream when their stream moves to a different source, though they shouldn't be auto unmuting

Should I expect to just deal with it

In the short term yes, but there's some potential that we make a setting to change that default behavior. We've been wanting to give more user settings lately and it's possible that we can make an argument to the team that this is a useful one to add.

Can I ask what sort of automations you have? There's some potential we can work together to make them more robust against this present default case in the meantime, or I could direct you to our home assistant plugin as that's been upgraded lately to make custom automations much easier, meaning you could track specific entities rather than relative ids.

[TerribleTesla]

Thanks for the update.

It's not something that happens often; for the most part the 4 inputs are set and aren't updated often. It would be nice if this was a customizable setting to not follow the stream, but not a deal breaker at all as that's such a niche request.

I had played around with Home Assistant prior to the recent update to leverage the AmpliPi API directly for some of the things I'd wanted to do (Adjust Volume / Move speakers to specific Zones with an Ikea Symfonisk). I had also put some time into creating an automation in HA to shuffle the speakers back to their 'normal' inputs; but had some odd issues trying to get that to work as expected.

I have taken a peek at the HA plugin again and did notice there were a bunch more options after the update. Pretty sure I can easily move my 'legacy' API commands over to an HA script now.

rest_command: amplipi_remove_garage_speaker: method: PATCH content_type: "application/json" url: http://10.50.50.251/api/zones payload: '{"zones": [10], "update": { "source_id": "-1" }}' amplipi_add_garage_speaker: method: PATCH content_type: "application/json" url: http://10.50.50.251/api/zones payload: '{"zones": [10], "update": { "source_id": "0" }}'