EMHASS: An Energy Management for Home Assistant

[RT1080 (Ronald)]

I use shell command, but see my entso-e syntax:

Shellcommand : "curl -i -H \"Content-Type: application/json\" -X POST -d '{
  \"load_cost_forecast\":{{((state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list))[now().hour:][:24] }},
  \"prod_price_forecast\":{{((state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list))[now().hour:][:24] }},
  \"prediction_horizon\":{{min(24, ((state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.entso_e_api_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list)[now().hour:][:24]|list|length))}},
  \"soc_init\":{{((states('sensor.growatt_growatt_battery_soc') | float(0))) / 100 }},
  \"soc_final\":0.10,
  \"def_total_hours\":[2],
  \"pv_power_forecast\":{{([states('sensor.solcast_pv_forecast_power_now')|int(0)] + state_attr('sensor.solcast_pv_forecast_forecast_today', 'detailedHourly')|selectattr('period_start','gt',utcnow()) | map(attribute='pv_estimate')|map('multiply',1000)|map('int')|list + state_attr('sensor.solcast_pv_forecast_forecast_tomorrow', 'detailedHourly')|selectattr('period_start','gt',utcnow()) | map(attribute='pv_estimate')|map('multiply',1000)|map('int')|list)| tojson}}
  }' http://localhost:5000/action/naive-mpc-optim"

[markpurcell]

@ThorAlex

They do give the correct prices when i test them in the template editor so I think they should work.

It would help if you could also show the template editor output so we can see what is being fed into EMHASS.

[RT1080 (Ronald)]

The “prices” attribute of entso-e provides an array with time and prices as “sub attributes” for both today and tomorrow, similar to noordpool. If @ThorAlex follows my code that should work.

[markpurcell]

As you well know the format for yaml is very precise, a comma in the wrong place mucks every thing up.

Here is my rest command:

rest_command:
  naive_mpc_optim:
    url: http://localhost:5000/action/naive-mpc-optim
    method: POST
    content_type: 'application/json'
    payload: >-
      {
        "prod_price_forecast": {{
          ([states('sensor.amber_feed_in_price')|float(0)] +
          (state_attr('sensor.amber_feed_in_forecast', 'forecasts')|map(attribute='per_kwh')|list))
          | tojson 
        }},
        "load_cost_forecast": {{
          ([states('sensor.amber_general_price')|float(0)] + 
          state_attr('sensor.amber_general_forecast', 'forecasts') |map(attribute='per_kwh')|list) 
          | tojson 
        }},
        "load_power_forecast": {{
          ([states('sensor.power_load_no_var_loads')|int] +
          (states('input_text.fi_fo_buffer').split(', ')|map('multiply',1000)|map('int')|list)[1:]
          )| tojson 
        }},
        
        "pv_power_forecast": {{
          ([states('sensor.solaredge_nopowerlimit')|int(0)] +
          state_attr('sensor.solcast_pv_forecast_forecast_today', 'detailedForecast')|selectattr('period_start','gt',utcnow()) | map(attribute='pv_estimate')|map('multiply',1000)|map('int')|list +
          state_attr('sensor.solcast_pv_forecast_forecast_tomorrow', 'detailedForecast')|selectattr('period_start','gt',utcnow()) | map(attribute='pv_estimate')|map('multiply',1000)|map('int')|list
          )| tojson
        }},
        "prediction_horizon": {{
          min(48, (state_attr('sensor.amber_feed_in_forecast', 'forecasts')|map(attribute='per_kwh')|list|length)+1)
        }},
        "alpha": 1,
        "beta": 0,
        "num_def_loads": 6,
        "def_total_hours": {{[states('sensor.def_total_hours_pool_filter')|int(0),
                              states('sensor.def_total_hours_pool_heatpump')|int(0),
                              states('sensor.def_total_hours_ev')|int(0),
                              states('sensor.def_total_hours_hvac')|int(0),
                              states('sensor.def_total_hours_hws')|int(0),
                              states('sensor.def_total_hours_ev2')|int(0)]}},
        "P_deferrable_nom":  [945,5000, 
                              {{ states('sensor.p_nom_ev')}}, 
                              4000, 
                              600, 
                              {{ states('sensor.p_nom_ev2')}}],
        "treat_def_as_semi_cont": [1, 1, 0, 0, 1, 0],
        "set_def_constant": [0, 0, 0, 0, 0, 0],
        "soc_init": {{ (states('sensor.gateway_battery')|int(0))/100 }},
        "soc_final": {{ (states('sensor.gateway_battery')|int(0))/100 }}
      }

and here is the output:

[ThorAlex (Thor)]

Ok, I updated it with Ronald’s example, still does not seem to work right.

  trigger_entsoe_forecast:
    url: http://localhost:5000/action/dayahead-optim
    method: POST
    content_type: "application/json"
    timeout: 300
    payload: >-
      {
        "load_cost_forecast\":{{((state_attr('sensor.strompriser_entso_e_nettleie_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.strompriser_entso_e_nettleie_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list))[now().hour:][:24] }},
        "prod_price_forecast\":{{((state_attr('sensor.strompriser_entso_e_salg_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.strompriser_entso_e_salg_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list))[now().hour:][:24] }},
        "prediction_horizon\":{{min(24, ((state_attr('sensor.strompriser_entso_e_nettleie_average_electricity_price_today', 'prices_today') | map(attribute='price') | list  + state_attr('sensor.strompriser_entso_e_nettleie_average_electricity_price_today', 'prices_tomorrow') | map(attribute='price') | list)[now().hour:][:24]|list|length))}}
      }

[haraldov (Harald)]

I think you need backslash before and after like this:

\"load_cost_forecast\":
\"prod_price_forecast\":

Do you get the emhass webpage when writing http://localhost:5000 in the browser?

[ThorAlex (Thor)]

Thanks, I should have seen that… No immediate reaction, but it might take a while?

[haraldov (Harald)]

@haraldov

Do you get the emhass webpage when writing http://localhost:5000 in the browser?

Do you get this webpage when writing http://localhost:5000 in the browser? Try with your Home Assistant server ip-adresse instead.

You can try without the backslash also like this: "load_cost_forecast":

You can also log rest commands in the log. You must first enable debug for rest commands. The you must search in the Home Assistant log for rest command you execute.

logger:
  default: info
  logs:
    homeassistant.components.rest: debug

[erikh (erik hajer)]

I came accros this EMHASS project a week ago and I beliefe this might be exactly what i’m looking for. I’m in the middle of an “energy transition”: full electric WP for heating just installed, second 3kWp solar system to be installed next month, 5kW battery underway and I’m about to change over from a (Dutch) peak/off-peak electricity contract to a dynamical contract with changing tariffs every hour.

On installing EMHASS I got stuck in the beginning of the proces:
I installed the Add-on via Supervisor. When I tried to start EMHASS I got a pop-up:
“Go to configuration. not a valid value.”
So I switched to the configuration UI and made some basic/default settings. Trying to save this configuration returns with an error: "Failed to save add-on configuration, not a valid value. "
Even when I change and unchange any setting in the default configuration and saving it after that I get the same error.

I hope anyone can point me in the right direction to find a solution for this.
I’m running HomeAssistant (2023.10.1) with Supervisor (2023.10) on a Raspberry Pi 4 ( OS 5.10.103)

[markpurcell]

@haraldov

You can also log rest commands in the log

This is great news, I have been seeing the rest command in the logs when I get an error, but this debug command will greatly assist debugging.

Btw, you can also access the web interface directly from the Add-On Web UI button now, both locally and remotely.

[markpurcell]

@erikh

Go to configuration. not a valid value.

Glad to have you here and let us know how we can help with your setup. It certainly is a game changer with dynamic pricing.

The syntax can get quirky, but there is a reset to defaults option if it isn’t behaving.

[erikh (erik hajer)]

Hi Mark,
Thanks for the fast reply.
I already tryied your solution to reset to dafaults, but even then EMHASS is not starting and pointing me back to the configuration. It seems the (default) configuration file(s) are not accessable or something like that.

[haraldov (Harald)]

@erikh

I installed the Add-on via Supervisor.

I install the emhass addon from Settings → Add-ons → Add-on Store.
First I add the url https://github.com/davidusb-geek/emhass-add-on from here: GitHub - davidusb-geek/emhass-add-on: The Home Assistant Add-on for EMHASS: Energy Management Optimization for Home Assistant

Then I install the emhass addon (a docker container):

Try to only choose “Start on Boot” first:

[ThorAlex (Thor)]

@haraldov

Do you get this webpage when writing http://localhost:5000 in the browser? Try with your Home Assistant server ip-adresse instead.

I did not, but changed it ti the IP last night.

@haraldov

You can try without the backslash also like this: "load_cost_forecast":

Tried that, still no change.

@haraldov

You can also log rest commands in the log. You must first enable debug for rest commands. The you must search in the Home Assistant log for rest command you execute.

Did that, but can’t seem to find anything in the logs. Might be looking in the wrong place?

Also checked the EMHASS logs, nothing there.

[erikh (erik hajer)]

I installed EMHASS exactly like you describe. Even with only the default configuration it does not start. I tried activating “Start on boot” and then rebooting the complete system: when Home Assistants is up and running again the Emhass addon did not start.
I also tried to uninstall and re-install the addon a few times but still the same: EMPASS does not start.
Only thing a see in the supervisor logs is:

INFO (MainThread) [supervisor.jobs] 'MountManager.reload' blocked from execution, mounting not supported on system

23-10-12 11:36:19 ERROR (MainThread) [supervisor.addons.addon] Add-on 5b918bf2_emhass has invalid options: not a valid value. Got {'hass_url': 'empty', 'long_lived_token': 'empty', 'costfun': 'profit', 'logging_level': 'INFO', 'optimization_time_step': 30, 'historic_days_to_retrieve': 2, 'method_ts_round': 'nearest', 'set_total_pv_sell': False, 'lp_solver': 'COIN_CMD', 'lp_solver_path': '/usr/bin/cbc', 'set_nocharge_from_grid': False, 'set_nodischarge_to_grid': False, 'set_battery_dynamic': False, 'battery_dynamic_max': 0.9, 'battery_dynamic_min': -0.9, 'load_forecast_method': 'naive', 'sensor_power_photovoltaics': 'sen...

I’m not a HomeAssistant specialist. So, I’m stuck here.

[Jeza]

Hey Mark,

Being on Amber, have you worked out how to add the value of what you generated and profited through the day? Example being my screenshot?

[markpurcell]

@Jeza

Being on Amber, have you worked out how to add the value of what you generated and profited through the day?

I would take your earnings of $13.45 and add to that the cost of your household consumption multiplied by your default market rate.

If your consumption was about average at 20 kW at a default market offer of 30¢/ kWh, then that is an additional $6 of savings, for a total of $20 savings for the day ~ $600 pre month or ~ $7,000 per year!

If your consumption was 100 kW at a default market offer of 30¢/ kWh, then that is an additional $30 of savings, for a total of $33.45 savings for the day ~ $1000 pre month or ~ $12,000 per year!

[haraldov (Harald)]

@ThorAlex

I did not, but changed it ti the IP last night.

If the webserver is not responding on TCP port 5000 the rest command will fail. You can try to change the port to 5001 and see if it works. The web adresse will then be: http://:5001/

[Jeza]

I Ment the actual calculator itself,

As amber is variable i wouldnt know how your supposed to add the calculator to a rolling value,

Ive looked around to see on abmber and all that, but im trying to combine everything to too 1 app.

[ThorAlex (Thor)]

@haraldov

If the webserver is not responding on TCP port 5000 the rest command will fail. You can try to change the port to 5001 and see if it works. The web adresse will then be: http://:5001/

Just to try to understand how things work: Is the rest communicating through my lan/router and not internally in the software on the rpi? In that case I’ll probably have firewall issues, but why would home assistant need to communicate over lan with it’s own addon? And why would the port matter if not? Makes no sense to me…

I’ll try anyways, I really appreciate the help!