Enabling the new Startup Penalty function

[purcell-lab]

@werdnum thanks for your contribution with the startup penalty function.

I too am running a pool filter pump & heat pump against Amber pricing so this feature could be useful, I currently have a delay automation so I don't call things more than every 15 minutes. With your start penalty function if I really need to stop or start without waiting the 15 minutes I still can.

I have dropped in some default values, but am interesting in tuning them:

        "def_current_state": {{[
                        iif(states('sensor.p_deferrable0')|int(0),1,0),
                        iif(states('sensor.p_deferrable1')|int(0),1,0),
                        iif(states('sensor.p_deferrable2')|int(0),1,0),
                        iif(states('sensor.p_deferrable3')|int(0),1,0),
                        iif(states('sensor.p_deferrable4')|int(0),1,0),
                        iif(states('sensor.p_deferrable5')|int(0),1,0)
                      ]}},
        "def_start_penalty":      [1, 1, 1, 1, 1, 1],

I couldn't see any debug entries (like the optimisation windows).

How can I tell the penalties have been applied and where would I see an effect?

2024-06-12 23:00:24,397 - web_server - INFO - Passed runtime parameters: {'load_cost_forecast': [0.29, 0.25, 0.25, 0.22, 0.24, 0.2, 0.18, 0.19, 0.17, 0.19, 0.17, 0.17, 0.17, 0.21, 0.44, 0.51, 0.9, 0.52, 0.41, 0.15, 0.12, 0.11, 0.05, 0.05, 0.05, 0.04, 0.04, 0.04, 0.04, 0.05, 0.06, 0.06, 0.12, 0.12, 0.29, 0.64, 8.06, 17.91, 17.91, 17.91, 16.32, 1.73, 1.23, 0.98, 0.52, 0.35, 0.44, 0.47, 0.44, 0.4, 0.34, 0.19, 0.21, 0.2, 0.2, 0.2, 0.18, 0.17], 'prod_price_forecast': [0.19, 0.16, 0.16, 0.13, 0.15, 0.1, 0.09, 0.1, 0.08, 0.1, 0.08, 0.08, 0.08, 0.12, 0.33, 0.39, 0.74, 0.4, 0.3, 0.06, 0.04, 0.04, -0.02, -0.02, -0.02, -0.03, -0.03, -0.03, -0.03, -0.02, -0.01, -0.01, 0.04, 0.04, 0.07, 0.39, 7.13, 16.09, 16.09, 16.09, 14.63, 1.37, 0.92, 0.7, 0.4, 0.25, 0.33, 0.35, 0.33, 0.29, 0.24, 0.1, 0.11, 0.11, 0.11, 0.11, 0.09, 0.08], 'pv_power_forecast': [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 60, 286, 1355, 3001, 4483, 5779, 6988, 7995, 8730, 9235, 9494, 9574, 9375, 8958, 8300, 7425, 6303, 4985, 3562, 1964, 539, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 107, 422, 1397, 2782, 4093, 5358, 6664, 7754, 8566, 9058, 9301, 9375, 9196, 8799, 8154, 7165, 5796, 4525, 3149, 1643, 348, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0], 'load_power_forecast': [1120, 1100, 400, 1100, 1100, 1000, 1300, 1400, 1300, 2000, 1500, 1600, 2000, 1600, 1700, 6800, 1500, 1600, 2000, 1700, 1800, 300, 300, 600, 1200, 1600, 2800, 1600, 400, 300, 2200, 500, 1000, 300, 300, 500, 400, 400, 600, 700, 1300, 1400, 1200, 1100, 1000, 1000, 1100, 1100, 1100, 1100, 400, 1100, 1100, 1000, 1300, 1400, 1300, 2000, 1500, 1600, 2000, 1600, 1700, 6800, 1500, 1600, 2000, 1700, 1800, 300, 300, 600, 1200, 1600, 2800, 1600, 400, 300, 2200, 500, 1000, 300, 300, 500, 400, 400, 600, 700, 1300, 1400, 1200, 1100, 1000, 1000, 1100, 1100], 'prediction_horizon': 58, 'alpha': 1, 'beta': 0, 'num_def_loads': 6, 'def_total_hours': [0, 5, 0, 0, 0, 0], 'def_end_timestep': [0, 0, 0, 0, 15, 0], 'P_deferrable_nom': [1232, 6333, 11520, 2500, 600, 11520], 'def_current_state': [0, 0, 0, 0, 0, 0], 'def_start_penalty': [1, 1, 1, 1, 1, 1], 'treat_def_as_semi_cont': [1, 1, 0, 0, 1, 0], 'set_def_constant': [0, 0, 0, 0, 0, 0], 'soc_init': 0.14, 'soc_final': 0}
2024-06-12 23:00:24,398 - web_server - INFO -  >> Setting input data dict
2024-06-12 23:00:24,398 - web_server - INFO - Setting up needed data
2024-06-12 23:00:24,404 - web_server - INFO - Retrieve hass get data method initiated...
2024-06-12 23:00:24,940 - web_server - INFO - Retrieving weather forecast data using method = list
2024-06-12 23:00:24,949 - web_server - INFO -  >> Performing naive MPC optimization...
2024-06-12 23:00:24,949 - web_server - INFO - Performing naive MPC optimization
2024-06-12 23:00:24,987 - web_server - INFO - Perform an iteration of a naive MPC controller
2024-06-12 23:00:25,199 - web_server - DEBUG - Deferrable load 0: Proposed optimization window: 0 --> 0
2024-06-12 23:00:25,199 - web_server - DEBUG - Deferrable load 0: Validated optimization window: 0 --> 0
2024-06-12 23:00:25,216 - web_server - DEBUG - Deferrable load 1: Proposed optimization window: 0 --> 0
2024-06-12 23:00:25,216 - web_server - DEBUG - Deferrable load 1: Validated optimization window: 0 --> 0
2024-06-12 23:00:25,233 - web_server - DEBUG - Deferrable load 2: Proposed optimization window: 0 --> 0
2024-06-12 23:00:25,233 - web_server - DEBUG - Deferrable load 2: Validated optimization window: 0 --> 0
2024-06-12 23:00:25,241 - web_server - DEBUG - Deferrable load 3: Proposed optimization window: 0 --> 0
2024-06-12 23:00:25,241 - web_server - DEBUG - Deferrable load 3: Validated optimization window: 0 --> 0
2024-06-12 23:00:25,254 - web_server - DEBUG - Deferrable load 4: Proposed optimization window: 0 --> 15
2024-06-12 23:00:25,254 - web_server - DEBUG - Deferrable load 4: Validated optimization window: 0 --> 15
2024-06-12 23:00:25,272 - web_server - DEBUG - Deferrable load 5: Proposed optimization window: 0 --> 0
2024-06-12 23:00:25,273 - web_server - DEBUG - Deferrable load 5: Validated optimization window: 0 --> 0
2024-06-12 23:00:26,354 - web_server - INFO - Status: Optimal
2024-06-12 23:00:26,354 - web_server - INFO - Total value of the Cost function = 476.25
2024-06-12 23:00:27,174 - web_server - INFO - Passed runtime parameters: {'custom_load_forecast_id': {'entity_id': 'sensor.p_load_forecast', 'unit_of_measurement': 'W', 'friendly_name': 'Load Power Forecast'}}
2024-06-12 23:00:27,174 - web_server - INFO -  >> Setting input data dict
2024-06-12 23:00:27,174 - web_server - INFO - Setting up needed data
2024-06-12 23:00:27,178 - web_server - INFO -  >> Publishing data...
2024-06-12 23:00:27,179 - web_server - INFO - Publishing data to HASS instance
2024-06-12 23:00:27,215 - web_server - INFO - Successfully posted to sensor.p_pv_forecast = 0
2024-06-12 23:00:27,243 - web_server - INFO - Successfully posted to sensor.p_load_forecast = 1120
2024-06-12 23:00:27,268 - web_server - INFO - Successfully posted to sensor.p_pv_curtailment = 0.0
2024-06-12 23:00:27,295 - web_server - INFO - Successfully posted to sensor.p_deferrable0 = 0.0
2024-06-12 23:00:27,322 - web_server - INFO - Successfully posted to sensor.p_deferrable1 = 0.0
2024-06-12 23:00:27,350 - web_server - INFO - Successfully posted to sensor.p_deferrable2 = 0.0
2024-06-12 23:00:27,386 - web_server - INFO - Successfully posted to sensor.p_deferrable3 = 0.0
2024-06-12 23:00:27,410 - web_server - INFO - Successfully posted to sensor.p_deferrable4 = 0.0
2024-06-12 23:00:27,437 - web_server - INFO - Successfully posted to sensor.p_deferrable5 = 0.0
2024-06-12 23:00:27,471 - web_server - INFO - Successfully posted to sensor.p_batt_forecast = 0.0
2024-06-12 23:00:27,499 - web_server - INFO - Successfully posted to sensor.soc_batt_forecast = 14.0
2024-06-12 23:00:27,530 - web_server - INFO - Successfully posted to sensor.p_grid_forecast = 1120.0
2024-06-12 23:00:27,557 - web_server - INFO - Successfully posted to sensor.total_cost_fun_value = 486.26
2024-06-12 23:00:27,577 - web_server - INFO - Successfully posted to sensor.optim_status = Optimal
2024-06-12 23:00:27,607 - web_server - INFO - Successfully posted to sensor.unit_load_cost = 0.29
2024-06-12 23:00:27,635 - web_server - INFO - Successfully posted to sensor.unit_prod_price = 0.19

I'm still seeing a 30 minute gap in the scheduling of my pool heater for tomorrow, which is probably OK. I'm hopeful this startup_penalty will prevent my high frequency MPC switching on/ off each minute. But how do I know it's functional?

Pool startup's look a lot smoother today compared to yesterday. Deferrable1 yesterday was starting and stopping a lot, today there has only been one start/stop cycle: