Localization

The integration ships translations for all generated entity names and states through Home Assistant's standard translation system, stored in custom_components/dreame_vacuum/translations/*.json. These files also serve as the base dictionary that downstream UIs use for their own interface text.

Fix or Improve Translations

If a typo or incorrect translation is identified, or support for a new language is needed, contributions go to this repository.

Translation Generalization

The official app frequently uses different terminology for identical parameters across various device generations. Translations must utilize logical, generalized names rather than strictly copying the exact wording from the App. This prevents translation conflicts where a correction tailored for one specific generation is subsequently overwritten by users with different device generations.

The update process involves the following steps:

1. Fork the Repository: Forking the Dreame Vacuum Home Assistant integration repository on GitHub.
2. Find the Translation File: Navigating to the custom_components/dreame_vacuum/translations/ directory in the forked repository to locate the translation file matching the language code, such as de.json or it.json.
3. Make the Changes: Updating the incorrect text. The config block manages config flow and options flow text. The entity block manages entity names, select options and their states.
4. Submit a Pull Request: Opening a Pull Request to the dev branch. After the Pull Request is reviewed and merged into a new release, Home Assistant automatically picks up the updated translations.

Frontend Translations

Frontend-specific translation keys and shared action labels are maintained within the entity_component block of the language files. For detailed information on how frontend translations are structured and utilized by downstream UI components, refer to the Dreame Vacuum Card translations documentation.