Add configurable optimizer area sensors

This commit is contained in:
2026-08-10 12:25:43 +02:00
parent dc6b2dc71a
commit 02bb4a831e
16 changed files with 643 additions and 21 deletions
@@ -43,6 +43,27 @@
"unknown": "Unexpected error"
}
},
"options": {
"step": {
"init": {
"title": "Configure optimizer areas",
"description": "Map area names to optimizer IDs as a JSON object. Available IDs: {optimizer_ids}",
"data": {
"area_mapping": "Area mapping"
},
"data_description": {
"area_mapping": "Example: assign IDs 1.1.1 and 1.1.2 to an area named west. Use an empty object to disable area sensors."
}
}
},
"error": {
"duplicate_area": "Area names must be unique",
"duplicate_optimizer": "An optimizer can only belong to one area",
"empty_area": "Every area must contain at least one optimizer",
"invalid_area_mapping": "Enter a JSON object containing area names and optimizer ID lists",
"unknown_optimizer": "The mapping contains an unknown optimizer ID"
}
},
"entity": {
"sensor": {
"daily_energy": {
@@ -50,6 +71,12 @@
},
"current_power": {
"name": "{optimizer_id} current power"
},
"area_daily_energy": {
"name": "{area} daily energy"
},
"area_current_power": {
"name": "{area} current power"
}
}
}