CLI: ability to provide dynamic SoC values from sensor in scheduling

[nhoening]

Discussed in https://github.com/FlexMeasures/flexmeasures/discussions/916

^{Originally posted by kyros32 November 29, 2023} Hello Flexers,

1) I was wondering, how can I use SoC data --soc-at-start from a sensor?

Instead of this:

flexmeasures add schedule for-storage --sensor-id 2 --consumption-price-sensor 1 \
    --start ${TOMORROW}T07:00+01:00 --duration PT12H \
    --soc-at-start 50% --roundtrip-efficiency 90%

Something like this, so SoC is pulled dynamically everytime I force rescheduling via CRON for example or API call.

flexmeasures add schedule for-storage --sensor-id 2 --consumption-price-sensor 1 \
    --start ${TOMORROW}T07:00+01:00 --duration PT12H \
    --soc-at-start sensor-id 14 --roundtrip-efficiency 90%

I could fill it as a variable for in a call, but I think, why not to use an associated sensor with it. More simplex...

Any help much appreciated. Robert