jeans/developers.home-assistant
jeans/developers.home-assistant
1
0
Fork 0
mirror of https://github.com/home-assistant/developers.home-assistant.git synced 2025-07-12 20:06:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add blog about support for strings.platform_name.json will be removed (#2103)

Browse Source
This commit is contained in:
Erik Montnemery 2024-03-05 09:41:21 +01:00 committed by GitHub
parent 416475f08d
commit 1179d61779
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
blog/2024-03-05-platform_entity_translations_deprecation.md Normal file
View File

@ -0,0 +1,30 @@
---
author: Erik Montnemery
authorURL: https://github.com/emontnemery
title: "Support for platform translations in separate files will be removed"
---
The method for integrations to provide translations for states of its entities under other integrations, for example to translate an integration's sensors was changed in November 2022, and support for the old method will be removed in Home Assistant Core 2024.5.0.
Once Home Assistant Core 2024.5.0 is released, integrations can no longer use custom device classes together with a `strings.<platform name>.json` file. Instead, entities must set the `translation_key` property on an entity and include that `translation_key` in the integration's `strings.json`.
The following example `strings.json` is for a Moon domain `sensor` entity with its `translation_key` property set to `phase`:
```json
{
"entity": {
"sensor": {
"phase": {
"state": {
"new_moon": "New moon",
"first_quarter": "First quarter",
"full_moon": "Full moon",
"last_quarter": "Last quarter"
}
}
}
}
}
```
For more details, see the [`translation`](/docs/internationalization/core/#state-of-entities) and [`entity`](/docs/core/entity#generic-properties) documentation.