Federation, explained - smart-underworld/seestar_alp GitHub Wiki

In federation mode, once a schedule is sent to the connected Seestars, this schedule is deemed to have pushed out. In order to interact with it again, one will need to reference the schedule id to stop it.

This also implies one can start creating another schedule and push out to other available instances of Seestars that are readied to do the federation's bidding. There is a parameter in start schedule in federation mode to limit the maximum number of Seestars to support this schedule, so one can divide up the federation of Seestars into multiple units.

One way to think of it is each Seestar is a worker thread, and the federation is the controller

To execute a mosaic, each worker Seestar can either duplicate each other for the panels, or the panels are further divided up within this group of Seestars.

I tried to make this federation as flexible as I could.

In theory, this model can support thousands of Seestars.