mirror of
https://github.com/Akkudoktor-EOS/EOS.git
synced 2026-03-14 18:46:18 +00:00
feat: make home assistant add-on run optimization by default (#940)
When running as Home Assistant add-on the only viable usage is running with cyclic optimization. Make this the default to als propvide a better experience for first time users. The optimization will start with demo data, which also helps to configure Akkudoktor-EOS to the personal usage. The disabling of the automatic energy management is now an explicit mode "DISABLED". Signed-off-by: Bobby Noelte <b0661n0e17e@gmail.com>
This commit is contained in:
@@ -8,7 +8,7 @@
|
||||
| Name | Environment Variable | Type | Read-Only | Default | Description |
|
||||
| ---- | -------------------- | ---- | --------- | ------- | ----------- |
|
||||
| interval | `EOS_EMS__INTERVAL` | `float` | `rw` | `300.0` | Intervall between EOS energy management runs [seconds]. |
|
||||
| mode | `EOS_EMS__MODE` | `Optional[akkudoktoreos.core.emsettings.EnergyManagementMode]` | `rw` | `None` | Energy management mode [OPTIMIZATION | PREDICTION]. |
|
||||
| mode | `EOS_EMS__MODE` | `<enum 'EnergyManagementMode'>` | `rw` | `required` | Energy management mode [DISABLED | OPTIMIZATION | PREDICTION]. |
|
||||
| startup_delay | `EOS_EMS__STARTUP_DELAY` | `float` | `rw` | `5` | Startup delay in seconds for EOS energy management runs. |
|
||||
:::
|
||||
<!-- pyml enable line-length -->
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Akkudoktor-EOS
|
||||
|
||||
**Version**: `v0.2.0.dev2603130753300674`
|
||||
**Version**: `v0.2.0.dev2603131189846912`
|
||||
|
||||
<!-- pyml disable line-length -->
|
||||
**Description**: This project provides a comprehensive solution for simulating and optimizing an energy system based on renewable energy sources. With a focus on photovoltaic (PV) systems, battery storage (batteries), load management (consumer requirements), heat pumps, electric vehicles, and consideration of electricity price data, this system enables forecasting and optimization of energy flow and costs over a specified period.
|
||||
|
||||
@@ -107,10 +107,11 @@ If no interval is configured (`None`, `null`) there will be only one energy mana
|
||||
startup.
|
||||
:::
|
||||
|
||||
The energy management can be run in two modes:
|
||||
The energy management can be run in three modes:
|
||||
|
||||
- **OPTIMIZATION**: A full optimization is done. This includes update of predictions.
|
||||
- **PREDICTION**: Only the predictions are updated.
|
||||
- **DISABLED**: No energy management is run.
|
||||
|
||||
**Example:**
|
||||
|
||||
|
||||
@@ -17,6 +17,12 @@ The `POST /optimize` endpoint interface does not regard configurations set for t
|
||||
passed to the request. You have to set the parameters even if given in the configuration.
|
||||
:::
|
||||
|
||||
:::{admonition} Warning
|
||||
:class: warning
|
||||
To prevent automatic optimization from interfering with `POST /optimize` requests, set `ems.mode`
|
||||
to `DISABLED` in the configuration.
|
||||
:::
|
||||
|
||||
## Input Payload
|
||||
|
||||
### Sample Request
|
||||
@@ -86,6 +92,12 @@ passed to the request. You have to set the parameters even if given in the confi
|
||||
"initial_soc_percentage": 54,
|
||||
"min_soc_percentage": 0
|
||||
},
|
||||
"dishwasher": {
|
||||
"device_id": "dishwasher1",
|
||||
"consumption_wh": 2000,
|
||||
"duration_h": 3,
|
||||
"time_windows": null
|
||||
},
|
||||
"temperature_forecast": [
|
||||
18.3, 17.8, 16.9, 16.2, 15.6, 15.1, 14.6, 14.2, 14.3, 14.8, 15.7, 16.7, 17.4,
|
||||
18.0, 18.6, 19.2, 19.1, 18.7, 18.5, 17.7, 16.2, 14.6, 13.6, 13.0, 12.6, 12.2,
|
||||
|
||||
Reference in New Issue
Block a user