Currently there is just a single string for the "Cleared" log entry under
ui::components::logbook::messages::cleared_device_class
"cleared (no {device_class} detected)"
In many languages there is no single translation that fits all device classes, so the log entries look really strange.
In German "cleared" is currently translated as "zurückgesetzt" ("reset") which makes this even worse.. But to fix this for all device classes we do need separate strings.
For the state shown in the dashboard this is solved as there are different strings defined, so the "off" state can have a proper translation.
The problem
Currently there is just a single string for the "Cleared" log entry under
ui::components::logbook::messages::cleared_device_class "cleared (no {device_class} detected)"
In many languages there is no single translation that fits all device classes, so the log entries look really strange. In German "cleared" is currently translated as "zurückgesetzt" ("reset") which makes this even worse.. But to fix this for all device classes we do need separate strings.
For the state shown in the dashboard this is solved as there are different strings defined, so the "off" state can have a proper translation.
Many can have identical translations following:
So by defaut all other were dirived from the above, which works OK for similar sensors like:
But for other this needs to be adapted, for example:
Here "clear" or "cleared" need a completely different wording, in some cases in English, too.
Therefore this differentiation needs to be extended to the corresponding log entries, making them match the status displayed.
What version of Home Assistant Core has the issue?
core-2024.10.1
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response