Checklist
Adaptive Cover Pro version
2.27.0
Is your enhancement related to a problem?
Context
The whole integration UI is properly translated (menu entries, field labels, help texts, etc.),
but the "Configuration summary" page remains entirely in English, even when the rest
of the UI is displayed in another language (French in my case).
Observation
The summary mixes a translated title ("Résumé de la configuration") with fully English content:
- Section headers: Your Cover, How It Decides, Position Limits, Proxy cover, Decision Priority
- Inline labels: first matching rule wins, highest wins, active, not configured
- Status messages: Manual override: pauses automatic control…, Sun tracking disabled — covers hold position…, After sunset (today ~21:29) → 0%, etc.
- Pipeline step names: Force, Weather, Manual, Motion, Cloud, Climate, Glare, Solar, Default
This is the most information-dense page of the integration — and arguably the most
important for understanding what ACP is actually doing. Leaving it untranslated makes it
hard to read for non-English-speaking users, even when they've configured everything else
in their own language.
Describe the solution you'd like
Some parts are dynamically composed (e.g. "After sunset (today ~21:29) → 0%") and will
need template strings with placeholders, but the structure looks compatible with the
standard HA translation system.
Alternatives you've considered
No response
Additional context
No response
Checklist
Adaptive Cover Pro version
2.27.0
Is your enhancement related to a problem?
Context
The whole integration UI is properly translated (menu entries, field labels, help texts, etc.),
but the "Configuration summary" page remains entirely in English, even when the rest
of the UI is displayed in another language (French in my case).
Observation
The summary mixes a translated title ("Résumé de la configuration") with fully English content:
This is the most information-dense page of the integration — and arguably the most
important for understanding what ACP is actually doing. Leaving it untranslated makes it
hard to read for non-English-speaking users, even when they've configured everything else
in their own language.
Describe the solution you'd like
Some parts are dynamically composed (e.g. "After sunset (today ~21:29) → 0%") and will
need template strings with placeholders, but the structure looks compatible with the
standard HA translation system.
Alternatives you've considered
No response
Additional context
No response