Lock in specific ledmap upon receiving DDP

[spblat]

Is your feature request related to a problem? Please describe.

When DDP is received by a WLED from another WLED, the ledmap that is active on the target WLED at that time is the ledmap that applies. If the target has more than one ledmap, we have no way from the sending side to be sure that the LEDs will be mapped correctly during DDP.

Describe the solution you'd like

Establish a specific ledmap that we will adopt when receiving DDP as a client. It should be probably simply be the default ledmap on the target WLED unless you really want another preference in the UI.

Describe alternatives you've considered

If I’m sending DDP to a WLED that usually has a particular ledmap, I could rewrite the ledmap on the sending wled, but relying on nested ledmaps doesn’t make much sense, and the problem remains—depending on the active preset at the time DDP begins we can’t be sure what map will apply.

Or I could switch the target WLED to a preset with the right ledmap before sending DDP. But there’s no way to automate this from the sending side unless we add an API for telling the target WLED to switch to a specific preset (which I would also like).

Additional context

I’m using wled to decorate derelict wall-mounted pinball playfields. The physical ledmap is the best use of finite string. The second ledmap is a logical arrangement of lamps according to their original purpose on the playfield, so that “chase” on a particular segment looks like it did when the game was intact. A third ledmap relates to an effort to make a 2D matrix out of the arrangement of lamps on a playfield. DDP is used to make a matrix out of up to 5 playfields. I’ll post a demo to #showcase in Discord when I’m ready to share. https://github.com/spblat/wled-ncp/tree/main/Playfields

Thank you for working on WLED :-D

[blazoncek]

Will be solved by #3554

[blazoncek]

Available in 0.15.0 beta 1.

[spblat]

Initial test indicates #3554 fix was successful in my setup as of 0.15.0b1. Thank you!!