JohanAlvedal
commented
2 weeks ago Got it working here. https://github.com/JohanAlvedal/homeautomation/tree/main/Emhass/Shell
Open renaatdb opened 2 weeks ago
JohanAlvedal
commented
2 weeks ago Got it working here. https://github.com/JohanAlvedal/homeautomation/tree/main/Emhass/Shell
renaatdb
commented
2 weeks ago https://github.com/JohanAlvedal/homeautomation/tree/main/Emhass/Shell
Thanks, I'm going to study it
renaatdb
commented
2 weeks ago @JohanAlvedal Looks too complicated for me. tried to change this
shell_command:
dayahead_optim: "curl -i -H \"Content-Type:application/json\" -X POST -d '{\"pv_power_forecast\":{{states('sensor.solcast_24hrs_forecast')}}}' http://localhost:5001/action/dayahead-optim"
into
dayahead_optim_v2: 'curl -i -H ''Content-Type: application/json'' -X POST -d ''{
"load_cost_forecast":{{ ((state_attr("sensor.nordpool_tibber", "raw_today") | map(attribute="value") | list) + (state_attr("sensor.nordpool_tibber", "raw_tomorrow") | map(attribute="value") | list))[now().hour:][:24] }},
"prod_price_forecast":{{ ((state_attr("sensor.nordpool_tibber", "raw_today") | map(attribute="value") | list) + (state_attr("sensor.nordpool_tibber", "raw_tomorrow") | map(attribute="value") | list))[now().hour:][:24] }},
"prediction_horizon":{{ min(24, (((state_attr("sensor.nordpool_tibber", "raw_today") | map(attribute="value") | list) + (state_attr("sensor.nordpool_tibber", "raw_tomorrow") | map(attribute="value") | list))[now().hour:][:48] | list | length)) }},
"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 }},
"delta_forecast":2
}'' http://localhost:5000/action/dayahead-optim'i'm trying to find simple configurations
purcell-lab
commented
2 weeks ago There is no doubt adding in these additional forecasts with some json foo can get quite complex quickly.
It would be useful if we could provide a blueprint/ template for some of the standard suppliers; nordpool, Amber, octopus. So the end user could just tick a check box, rather than having all this yaml fun.
The other consideration is each time you modify the shell_command or rest_command you need to restart HA, it would also reduce complexity if you could just reload a template/ script each time you needed to modify the payload.
JohanAlvedal
commented
2 weeks ago Absolutely, I agree with you. Someone talented who could create a blueprint so you can enter your electricity supplier solcast and the most relevant parts, I think it would help many users of emhass. It was/is the part that many users struggle with to get emhass up and running, because it is precisely that part that is extremely complex. When and how should all scripts be run and how should they be configured.
renaatdb
commented
2 weeks ago Thanks, I thought I was the only one having trouble with this. It's amazing how Emhass was made. However, it is difficult for a beginner to get started and difficult to understand the manual. Hopefully I'll manage to get everything working in the future. I want to purchase a battery in the future and see what a dynamic rate (with Nordpool) can teach me. I am now trying to predict what the use of a battery can bring me. I assume Emhass can help me with this. Thanks
renaatdb
commented
1 week ago Hello, This is also an interesting tool from Thermia . https://classiconlinestorage.blob.core.windows.net/web-resources/SmartPrice_Info_and_FAQ_NL.pdf
Hello, I am running emhass and nordpool. generic-x86-64 core-2024.6.0 Home Assistant OS 12.3 EMHASS Current version: 0.10.1 Nordpool 0.0.14
What I have to fill in when I use nordpool? I want to use dynamic prices
I used the actually a working example for using Nordpool: https://emhass.readthedocs.io/en/latest/forecasts.html#example-using-the-nordpool-integration
P PV is ok Load_cost NOT ok
Logs
Is there something I do not see?
Thanks ``