Replies: 4 comments 2 replies
-
Pretty cool stuff! EOS actually already has the PV and elecricity price forecast part so all the third party accounts are not required. Currently we plan on a more straightforward integration with evcc (maybe via MQTT/HA). For the API docs, check out EOS OpenAPI Spec |
Beta Was this translation helpful? Give feedback.
-
Thanks, thats really cool. Ist there a way to get this available for other Users? Maybe WE Could integrate a direct API? Gesamtlast can be predicted by the inhouse Tool in EOS. You Just need some historical Data + yearly consumption (Look at the Open API in the readme bottom) |
Beta Was this translation helpful? Give feedback.
-
4.: It starts with the start hour of the simulation (default is current hour of the day, e.g. 8pm = 20). Currently we are working on improved PDF-report #267 (which would start at 0 for the socs). |
Beta Was this translation helpful? Give feedback.
-
Hey, thank you very much! Works great. |
Beta Was this translation helpful? Give feedback.
-
Hi all,
I'm using EVCC to control my wallbox and my inverter to load the home battery today. This is working fine, but I would like to use EOS to get it more automated. Here I want to share the current status and ask for support to get this done. Maybe it helps others as well.
Basic Setup
Here is the planned setup
All these connections are working (technically).
Warning
Let me know if I missed any sensitive data in the text. This guide is still only for experienced users.
Please make sure to follow all security guidelines which are may be relevant.
Create all needed accounts
For this setup you need accounts on
Tibber
Tibber is used to get the next day "market" prices. The API can used more frequently but the available timespan is max 24h. That's why this "source" is not enough for me.
affiliate link- if I get any savings (in their shop) I will spent them to this project (mods can maybe also change the link if they want)standard link
Create a API Token here
Energyforecast
Energyforcast fill the "tibber"-gap...a bit. Here we can get every day at around 15:00 a forecast for the next 48h which should reduce our issue. The API provides also the market prices but I want to consider the prices direct at 13:00, not 2h later.
Get a free account here
Get the API Key here
Solcast
I use Solcast to get the PV Power Forecast for my installation.
You can get a free account for "home hobbyist access" here
If you have more than 1 pv strings consider these workarounds. I have 4 pv strings and two inverter and that's why I created two sites and tried to combine the values.
You get the API Token here
Installation - EOS
Important
If docker is not installed, follow these guides
Installation - Node-RED
Important
If docker is not installed, follow these guides
See here for running Node-RED via docker
If you can see the Node-RED interface on
http://[YOUR-SERVER-IPADDRESS]:1880
you can proceed.Installation - Influx DB
Important
If docker is not installed, follow these guides
See here for running Influx DB via docker
If you can see the Influx DB interface on
http://[YOUR-SERVER-IPADDRESS]:8086
you can proceed.Configuration - Influx DB
You should adjust at least these values
click here to see the config
Installation - Telegraf
See here
Run the following command to make the API Token accessabile for this session
export INFLUX_TOKEN=YOUR-INFLUX-API-TOKEN
Then you can check the config
telegraf --config http://YOUR-SERVER-IPADDRESS:8086/api/v2/telegrafs/YOUR-INFLUX-TELEGRAF-CONFIG-ID --test --debug
Then create a service file
sudo nano /etc/systemd/system/telegraf.service
with this content
click here
Installation - EVCC
See here
After that you need to configer and integrate your PV Installation (Smartmeter, Inverter, Wallbox etc). The documentation is very easy to understand. I have Kostal inverters & smartmeters, GO-e wallbox installed. For my setup, a sponsor token was needed. There is also a free one for limited time (enough to test the system).
Last step is the integration of the influx db. See here
EOS Usage
Goal - Start the first optimization
The goal is to sent a message body like this via POST to http://YOUR-SERVER-IPADDRESS:8503/optimize
To get such a body we collect the data from our Influx DB, slice, transform, merge and add some small configuration details and wait for the response which should be something like this and can also be viewed as PDF http://YOUR-SERVER-IPADDRESS:8503/visualization_results.pdf
Setup a Node-RED Flow to prepare the data
Go to your Node-RED instance http://YOUR-SERVER-IPADDRESS:1880
I used the template from meintechblog.de where I found this template. But I had to adjust this for various reasons (maybe wrong).
The result is here
You should review all "Read xy" nodes and the "function rule them all" nodes especially the part at the bottom of the code. The "Tesla" stuff is hardcoded. I didn't integrated the car API yet. And I didn't touched the nodes after the optimization yet.
click here
Run the optimization
Click on "Go shorty" and wait for the response.
Questions
Open steps
Beta Was this translation helpful? Give feedback.
All reactions