v2.4.3 - Retired Tesla Line Keys

The last of the duplicated line settings

v2.4.2 removed the two duplicate flow paths. This removes the config keys that existed only to drive them, so a saved config stops carrying settings that do nothing.

Gone:

• line_speeds.solar_tesla and line_speeds.grid_tesla are no longer written when you save from the editor. They were always copies of solar_ev and grid_ev, because the editor wrote the same value to both.
• colors.flow_solar_tesla_start / _end and colors.flow_grid_tesla_start / _end are no longer read as fallbacks, and the matching palette defaults are gone.

Unchanged: every line is still fully adjustable. The lines to the EV/Tesla are governed by:

Setting	YAML	Editor
Speed, solar to EV	line_speeds.solar_ev	Speed: Solar ➔ EV
Speed, grid to EV	line_speeds.grid_ev	Speed: Grid ➔ EV
Colours, solar to EV	colors.flow_solar_ev_start / _end	Color Studio, Solar ➔ EV
Colours, grid to EV	colors.flow_grid_ev_start / _end	Color Studio, Grid In ➔ EV

Plus the global speed_multiplier for everything.

If you hand-edited YAML

Rename those keys to the _ev equivalents: flow_solar_tesla_* becomes flow_solar_ev_*, flow_grid_tesla_* becomes flow_grid_ev_*, line_speeds.solar_tesla becomes line_speeds.solar_ev, line_speeds.grid_tesla becomes line_speeds.grid_ev. The values carry over as they are.

If you only ever used the visual editor, there is nothing to do: it always wrote the same value to both keys, so the surviving _ev key already holds your setting. The one case that changes behaviour is a config where the two were deliberately given different values, since only the _ev value counts now.

Verified

flow_solar_ev_* and flow_grid_ev_* still drive their gradients, both retired key sets are ignored and fall back to the palette colours, the SVG still holds 10 flow paths, and the battery row still renders.