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)?