Proposal: associate each 'Lineup' with a device instead of sometimes inferring the device(s) from the chosen dashboard

[partridgeworks]

I have about 8 Tesserae-enabled client panels in my house now.

I have set up multiple dashboards - sometimes a dashboard has multiple 'target' devices, for example:

Dashboard: "Mini-Calendar-Schedule"
Target Devices: reterminal-sticky1, reterminal-sticky-2

Dashboard: "Fun-XCKD-comic"
Target Devices reterminal-sticky1, reterminal-sticky-2, reterminal-sticky-3

Now let's say that I want to put together some interesting Lineups for reterminal-sticky-1.

• I click 'Lineups' > 'Set up a display'.
• I choose "Show one dashboard at a set time" > then choose a dashboard

But I never get to choose a device. Instead, the device is inferred from the selected dashboard, and if that dashboard has multiple target devices then multiple Lineups will be created - there is no way to override this behaviour, even if I don't want lots of lineups, I just want one device!

The mapping in the wizard is as follows:

Show one dashboard at a set time - NO DEVICE CAN BE CHOSEN
Keep one dashboard fresh - NO DEVICE CAN BE CHOSEN
Cycle through several dashboards - DEVICE CAN BE CHOSEN
Flip between dashboards by hand - DEVICE CAN BE CHOSEN

I propose that all the above options should allow a device to be chosen, and that it should never be inferred from the dashboard selection.

[dmellok]

Good catch, and you've described it accurately. The two single-dashboard modes never asked for a display, so the record was created unbound and delivery fell through to wherever the dashboard was bound. The engine already supported a timed lineup targeting specific displays, so the gap was only in the wizard and the schedule form.

Fixed in 0.405.1 (edge): all four wizard modes now ask which display to send to. For the single-dashboard modes it defaults to the dashboard's display when there is one, or to "every display it's on" when there are several, and you can pick a single display instead. The full schedule form has the same picker, so you can narrow an existing lineup too. Schedules also carry device_ids over the MCP API now.

One note on "never inferred": I kept the inference as the default so a single-display setup doesn't gain a mandatory question, but it's always visible and always overridable.