mirror of
https://github.com/Akkudoktor-EOS/EOS.git
synced 2026-01-01 00:06:18 +00:00
Adapters for Home Assistant and NodeRED integration are added. Akkudoktor-EOS can now be run as Home Assistant add-on and standalone. As Home Assistant add-on EOS uses ingress to fully integrate the EOSdash dashboard in Home Assistant. The fix includes several bug fixes that are not directly related to the adapter implementation but are necessary to keep EOS running properly and to test and document the changes. * fix: development version scheme The development versioning scheme is adaptet to fit to docker and home assistant expectations. The new scheme is x.y.z and x.y.z.dev<hash>. Hash is only digits as expected by home assistant. Development version is appended by .dev as expected by docker. * fix: use mean value in interval on resampling for array When downsampling data use the mean value of all values within the new sampling interval. * fix: default battery ev soc and appliance wh Make the genetic simulation return default values for the battery SoC, electric vehicle SoC and appliance load if these assets are not used. * fix: import json string Strip outer quotes from JSON strings on import to be compliant to json.loads() expectation. * fix: default interval definition for import data Default interval must be defined in lowercase human definition to be accepted by pendulum. * fix: clearoutside schema change * feat: add adapters for integrations Adapters for Home Assistant and NodeRED integration are added. Akkudoktor-EOS can now be run as Home Assistant add-on and standalone. As Home Assistant add-on EOS uses ingress to fully integrate the EOSdash dashboard in Home Assistant. * feat: allow eos to be started with root permissions and drop priviledges Home assistant starts all add-ons with root permissions. Eos now drops root permissions if an applicable user is defined by paramter --run_as_user. The docker image defines the user eos to be used. * feat: make eos supervise and monitor EOSdash Eos now not only starts EOSdash but also monitors EOSdash during runtime and restarts EOSdash on fault. EOSdash logging is captured by EOS and forwarded to the EOS log to provide better visibility. * feat: add duration to string conversion Make to_duration to also return the duration as string on request. * chore: Use info logging to report missing optimization parameters In parameter preparation for automatic optimization an error was logged for missing paramters. Log is now down using the info level. * chore: make EOSdash use the EOS data directory for file import/ export EOSdash use the EOS data directory for file import/ export by default. This allows to use the configuration import/ export function also within docker images. * chore: improve EOSdash config tab display Improve display of JSON code and add more forms for config value update. * chore: make docker image file system layout similar to home assistant Only use /data directory for persistent data. This is handled as a docker volume. The /data volume is mapped to ~/.local/share/net.akkudoktor.eos if using docker compose. * chore: add home assistant add-on development environment Add VSCode devcontainer and task definition for home assistant add-on development. * chore: improve documentation
7.8 KiB
7.8 KiB
Adapter Configuration
:::{table} adapter :widths: 10 20 10 5 5 30 :align: left
| Name | Environment Variable | Type | Read-Only | Default | Description |
|---|---|---|---|---|---|
| homeassistant | EOS_ADAPTER__HOMEASSISTANT |
HomeAssistantAdapterCommonSettings |
rw |
required |
Home Assistant adapter settings. |
| nodered | EOS_ADAPTER__NODERED |
NodeREDAdapterCommonSettings |
rw |
required |
NodeRED adapter settings. |
| provider | EOS_ADAPTER__PROVIDER |
Optional[list[str]] |
rw |
None |
List of adapter provider id(s) of provider(s) to be used. |
| providers | list[str] |
ro |
N/A |
Available electricity price provider ids. | |
| ::: |
Example Input
{
"adapter": {
"provider": [
"HomeAssistant"
],
"homeassistant": {
"config_entity_ids": null,
"load_emr_entity_ids": null,
"pv_production_emr_entity_ids": null,
"device_measurement_entity_ids": null,
"device_instruction_entity_ids": null,
"solution_entity_ids": null,
"homeassistant_entity_ids": [],
"eos_solution_entity_ids": [],
"eos_device_instruction_entity_ids": []
},
"nodered": {
"host": "127.0.0.1",
"port": 1880
}
}
}
Example Output
{
"adapter": {
"provider": [
"HomeAssistant"
],
"homeassistant": {
"config_entity_ids": null,
"load_emr_entity_ids": null,
"pv_production_emr_entity_ids": null,
"device_measurement_entity_ids": null,
"device_instruction_entity_ids": null,
"solution_entity_ids": null,
"homeassistant_entity_ids": [],
"eos_solution_entity_ids": [],
"eos_device_instruction_entity_ids": []
},
"nodered": {
"host": "127.0.0.1",
"port": 1880
},
"providers": [
"HomeAssistant",
"NodeRED"
]
}
}
Common settings for the NodeRED adapter
The Node-RED adapter sends to HTTP IN nodes.
This is the example flow:
[HTTP In \<URL\>] -> [Function (parse payload)] -> [Debug] -> [HTTP Response]
There are two URLs that are used:
- GET /eos/data_aquisition The GET is issued before the optimization.
- POST /eos/control_dispatch The POST is issued after the optimization.
:::{table} adapter::nodered :widths: 10 10 5 5 30 :align: left
| Name | Type | Read-Only | Default | Description |
|---|---|---|---|---|
| host | Optional[str] |
rw |
127.0.0.1 |
Node-RED server IP address. Defaults to 127.0.0.1. |
| port | Optional[int] |
rw |
1880 |
Node-RED server IP port number. Defaults to 1880. |
| ::: |
Example Input/Output
{
"adapter": {
"nodered": {
"host": "127.0.0.1",
"port": 1880
}
}
}
Common settings for the home assistant adapter
:::{table} adapter::homeassistant :widths: 10 10 5 5 30 :align: left
| Name | Type | Read-Only | Default | Description |
|---|---|---|---|---|
| config_entity_ids | Optional[dict[str, str]] |
rw |
None |
Mapping of EOS config keys to Home Assistant entity IDs. |
| The config key has to be given by a ‘/’-separated path | ||||
| e.g. devices/batteries/0/capacity_wh | ||||
| device_instruction_entity_ids | Optional[list[str]] |
rw |
None |
Entity IDs for device (resource) instructions to be updated by EOS. |
| The device ids (resource ids) have to be prepended by 'sensor.eos_' to build the entity_id. | ||||
| E.g. The instruction for device id 'battery1' becomes the entity_id 'sensor.eos_battery1'. | ||||
| device_measurement_entity_ids | Optional[dict[str, str]] |
rw |
None |
Mapping of EOS measurement keys used by device (resource) simulations to Home Assistant entity IDs. |
| eos_device_instruction_entity_ids | list[str] |
ro |
N/A |
Entity IDs for energy management instructions available at EOS. |
| eos_solution_entity_ids | list[str] |
ro |
N/A |
Entity IDs for optimization solution available at EOS. |
| homeassistant_entity_ids | list[str] |
ro |
N/A |
Entity IDs available at Home Assistant. |
| load_emr_entity_ids | Optional[list[str]] |
rw |
None |
Entity ID(s) of load energy meter reading [kWh] |
| pv_production_emr_entity_ids | Optional[list[str]] |
rw |
None |
Entity ID(s) of PV production energy meter reading [kWh] |
| solution_entity_ids | Optional[list[str]] |
rw |
None |
Entity IDs for optimization solution keys to be updated by EOS. |
| The solution keys have to be prepended by 'sensor.eos_' to build the entity_id. | ||||
| E.g. solution key 'battery1_idle_op_mode' becomes the entity_id 'sensor.eos_battery1_idle_op_mode'. | ||||
| ::: |
Example Input
{
"adapter": {
"homeassistant": {
"config_entity_ids": {
"devices/batteries/0/capacity_wh": "sensor.battery1_capacity"
},
"load_emr_entity_ids": [
"sensor.load_energy_total_kwh"
],
"pv_production_emr_entity_ids": [
"sensor.pv_energy_total_kwh"
],
"device_measurement_entity_ids": {
"ev11_soc_factor": "sensor.ev11_soc_factor",
"battery1_soc_factor": "sensor.battery1_soc_factor"
},
"device_instruction_entity_ids": [
"sensor.eos_battery1"
],
"solution_entity_ids": [
"sensor.eos_battery1_idle_mode_mode"
]
}
}
}
Example Output
{
"adapter": {
"homeassistant": {
"config_entity_ids": {
"devices/batteries/0/capacity_wh": "sensor.battery1_capacity"
},
"load_emr_entity_ids": [
"sensor.load_energy_total_kwh"
],
"pv_production_emr_entity_ids": [
"sensor.pv_energy_total_kwh"
],
"device_measurement_entity_ids": {
"ev11_soc_factor": "sensor.ev11_soc_factor",
"battery1_soc_factor": "sensor.battery1_soc_factor"
},
"device_instruction_entity_ids": [
"sensor.eos_battery1"
],
"solution_entity_ids": [
"sensor.eos_battery1_idle_mode_mode"
],
"homeassistant_entity_ids": [],
"eos_solution_entity_ids": [],
"eos_device_instruction_entity_ids": []
}
}
}