Feature Request: ramp rate constraints

[ArdJonker]

For both charger and battery it is considered harmful to switch from (full power) charge to (full power) discharge and vv. It is better to have 30 second (or so) decrease in power to 0 and a similar period to increase the power again. Can this be (optionally) build into the schedule some how? A practical way would be to always have a min. 5 minute 0 power period between charge and discharge and vv.

[Flix6x]

Given that you are scheduling in a 5-minute resolution, can I break up your request into two parts?

1. Scheduling in a more fine-grained resolution, or even in a variable resolution.
2. Constraining the ramp rate such that it takes two steps to go from max charge to max discharge and vice versa.

[nhoening]

Alternatively, this could be resolved locally (e.g. by the client)

[ArdJonker]

Given that you are scheduling in a 5-minute resolution, can I break up your request into two parts?

1. Scheduling in a more fine-grained resolution, or even in a variable resolution.

2. Constraining the ramp rate such that it takes two steps to go from max charge to max discharge and vice versa.

1. From a broader perspective I don't think making scheduling more fine grained adds much , so i would not do this just for this usecase.
2. This helps but it would still not have a small period of 0 power.

be reminded that this only applies when going from charging to discharging or v.v. directly. It is not applicable from charging to idle or v.v.

[ArdJonker]

Alternatively, this could be resolved locally (e.g. by the client)

Interesting if it where hardware dependant but i think this applies to all types of chargers/batteries.

[Flix6x]

@ArdJonker What would you expect the schedule to look like in the API response?