Primary/Secondary companion instance option

[Julusian]

It would be useful to be able to switch the companion ip in a couple of clicks.
This will allow for primary/backup flows, and other workflows.

I think it would be best implemented as having a submenu in the tray of known instances, being able to edit that list freely, and switching the active one by selecting in the list

[MeestorX]

I'd like to go one step further and allow for 2 simultaneous "sends" from Satellite, but select which IP to "receive" from, so you don't get into a feedback loop.

[Julusian]

I dont think that is a good idea.
Satellite has no idea what page it is currently on, so it will be relying on both companion machines keeping the page changes in sync. Meaning that if either you make changes in one and not the other, or the connection drops temporarily to one of them, then your streamdeck could end up on page 1 on A, and page 5 on B.

Also, if it is sending to both, does that mean that both companions will be expected to execute the actions for every press? That too will cause issues for anyone who has any buttons set to 'toggle' or similar behaviour

[MeestorX]

Fair enough. Trying to sort out how to set up a redundant system with the SD at a distance. Not easy!

[peternewman]

From a resilience/failover point of view (primary/backup), couldn't it just naïvely try to reconnect to the primary instance and if that fails try the secondary and continue retrying both until one works?

This would also be ideal for any headless usage. Obviously it could be extended to let you switch from the surface itself, but I'm aware that would risk introducing the issues you mentioned in #138 (comment)