القائمة
Home Assistant translation_key and identifier practices—entity/device naming via translations, stable unique IDs, and migration tips.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | ha-translations-and-ids |
| description | Home Assistant translation_key and identifier practices—entity/device naming via translations, stable unique IDs, and migration tips. |
| license | Complete terms in LICENSE.txt |
Use when fixing names/IDs in a custom component.
_attr_translation_key and _attr_has_entity_name=True; keep code names minimal.entity.<platform>.<translation_key>.name in translations JSON.Home Assistant ConfigFlow/OptionsFlow patterns—single-instance guard, schema validation, reload listeners, safe options handling without recursion.
Layered Home Assistant custom entity architecture—CoordinatorEntity bases, platform/category bases, registry-only platform files, translation-backed naming, stable IDs, and options reload wiring.
Patterns for building Home Assistant custom integrations that talk Modbus (TCP/RTU-over-TCP/serial): pymodbus device_id usage, safe polling/writing, pacing/backoff, encoding multi-register values, cached fallback, and translation-backed entities.
Testing patterns for Home Assistant custom components—coordinator and entity unit tests, register map coverage, write-path tests, and unique_id/device stability checks.
Diagnostics for Modbus in Home Assistant custom components—framing/extra-data errors, unit_id mismatches, pacing/timeouts, write contention, and logging patterns.