You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
iOS device model, version and app version
Model Name: iPhone 15 Pro
Software Version: 18.3.1
App version: 2025.1 (2025.1073)
Home Assistant Core Version
2025.2.5
Describe the bug
The cover entity in HA Core has four states (open, closed, opening, closing) of which the last two are not supported in the Carplay item (I have this under Quick Access). The Carplay interface falls back to the 'raw' states (without capitals). I searched the code through Github and think these states are not present in the strings file
Exerpt from 'Core.strings' (in this case Dutch/NL)
Addiotinal Info
I have not tried to reproduce this in Safari. The interface (Mushroom Cover Card and native Tile Card) shows the correct and translated values on the dashboard.
The text was updated successfully, but these errors were encountered:
iOS device model, version and app version
Model Name: iPhone 15 Pro
Software Version: 18.3.1
App version: 2025.1 (2025.1073)
Home Assistant Core Version
2025.2.5
Describe the bug
The cover entity in HA Core has four states (open, closed, opening, closing) of which the last two are not supported in the Carplay item (I have this under Quick Access). The Carplay interface falls back to the 'raw' states (without capitals). I searched the code through Github and think these states are not present in the strings file
Exerpt from 'Core.strings' (in this case Dutch/NL)
To Reproduce
Pin a cover (e.g. Garagedoor) witch supports al fout states to quick access and use the Carplay app to control the entity.
Expected behavior
All four states should be natively displayed and be present in the translatable strings. For Dutch/NL these should be:
Addiotinal Info
I have not tried to reproduce this in Safari. The interface (Mushroom Cover Card and native Tile Card) shows the correct and translated values on the dashboard.
The text was updated successfully, but these errors were encountered: