Feature request: minimum continous runtime for each deferrable load

[bsafh]

Scenario: a dumb tumble dryer with an on/off smart plug (or other household appliances like washing machines or dishwashers etc)

Problem: when the smart plug cuts the power, the tumble dryer not only stops, but opens the door as well (small electromagnetic lock opens when not supplied with power).

So when the dayahead-optim has found any number of operating timeslots for the dryer, which are not long enough to complete a run, the normally used automation from the EMHASS documentation shuts off the dryer in the middle of a run, leaving a batch of only half dried clothing in an open tumble dryer, as it obviously can't be switched on again.

The existing parameters only allow to set a summed up amount of time the deferrable load is allowed to run, in arbitrary chunks of time.

The optimizer should additionally be given a minimum runtime in one go for a deferrable load, e.g. 150 minutes in this example and find the optimal start for this minimum runtime a one block.

[davidusb-geek]

I think that setting set_def_constant=True for that specific type of load should get you the behavior that you expect. This will constraint your deferrable load to just one startup at a consrant load. Then setup enough def_total_hours for the tumble dryer to finish its cycle.