soc-at-start cannot be percentages when sent in the API

[nhoening]

Making schedules in the CLI, the --soc-at-start option can be "50%".

The schedule trigger endpoints accept soc-at-start as part of the flex model, and "50%" leads to an error. Only exact units (e.g. "75 kWh" work).

• Should the CLI not also accept it as a part of flex-model, actually?
• Find out why the soc-at-start is not parsed as we thought it would need to be. Do we need a capacity field somewhere as 100% reference? Or do we simply do what the CLI is doing (moving it over)?

[copilot-swe-agent]

The agent encountered an error and was unable to start working on this issue: This may be caused by a repository ruleset violation. See granting bypass permissions for the agent, or please contact support if the issue persists. (Request id: EA28:3F29F7:14D1EEB:FA8F37:69DE5B0E)

[Flix6x]

Any PR addressing this issue should imo now also deal with a % sensor referenced in the state-of-charge field (when that field is used as a starting SoC, i.e. in absence of the soc-at-start field).