--soc-min --soc-max

[tnlrgn2]

Hi

Well maybe this is not a bug but lack of documentation but anyway here it goes:

1. When I run:

flexmeasures add schedule for-storage --sensor 3 --consumption-price-sensor 2 --start "${TOMORROW}T00:00+01:00" --duration PT24H --soc-at-start 50% --soc-target 50% --soc-min 10% --soc-max 90% --roundtrip-efficiency 95%

I got error: Error: Got unexpected extra argument (10%)

2. When I run:

flexmeasures add schedule for-storage --sensor 3 --consumption-price-sensor 2 --start "${TOMORROW}T00:00+01:00" --duration PT24H --soc-at-start 50% --soc-target 50% --soc-max 90% --roundtrip-efficiency 95%

I got error: Error: Got unexpected extra argument (10%)

3. When I run:

flexmeasures add schedule for-storage --sensor 3 --consumption-price-sensor 2 --start "${TOMORROW}T00:00+01:00" --duration PT24H --soc-at-start 50% --soc-target 50% --soc-min 0.1 --soc-max 0.9 --roundtrip-efficiency 95%

I got error: Error: Got unexpected extra argument (0.1)

The problem is with --soc-min and --soc-max validations. You need to run it like below:

flexmeasures add schedule for-storage --sensor 3 --consumption-price-sensor 2 --start "${TOMORROW}T00:00+01:00" --duration PT24H --soc-at-start 50% --soc-target 50% "${TOMORROW}T23:59:59+01:00" --soc-min=10% --soc-max=90% --roundtrip-efficiency 95%

This is confusing because some parameters are ok without =, but -soc-min and -soc-max requires =.

[Flix6x]

Alternatively, could the issue be that the soc-target in your first 3 examples doesn't define a target datetime yet, and only your last example does? That could explain that the next string (--soc-min) is interpreted as the missing datetime, and your minimum SoC value is then interpreted as a standalone and unsupported argument.

(Example 2 also doesn't mention a 10% in the command, so it's odd that it's reported back. Did you copy the exact commands you used?)