Skip to content

EnOcean Custom v2.3.0 — YAML to UI import

Choose a tag to compare

View all tags
@szymkiewiczmathieu szymkiewiczmathieu released this 05 Aug 13:28
v2.3.0
36cd60d

EnOcean Custom 2.3.0 — YAML to UI import without losing entity ids

This release lets legacy YAML installations move their devices into the UI without breaking entity IDs, dashboards, or automations.

What it does

  • A new options-flow entry « Importer les équipements YAML » appears when importable YAML devices are detected.
  • binary_sensor and switch YAML blocks become UI devices with exactly the same unique ID as the YAML platform produced — including the historical {id}-None form when no device_class was declared — so Home Assistant keeps every existing entity ID.
  • Devices already managed in the UI are skipped; malformed YAML rows are counted, never half-imported; nothing is ever imported without explicit confirmation.
  • YAML sensor, light, and climate blocks are honestly counted as not importable and stay in YAML.
  • The tracking registry is in-memory only: never persisted, never logged, never exported in diagnostics, purged on unload.

Migration order

  1. Import from the UI (entities keep running from YAML; HA logs a benign duplicate-unique-ID warning per device until step 3).
  2. Remove the imported YAML blocks.
  3. Restart Home Assistant — UI devices take over the same entity IDs.
  4. Verify your entities and dashboards.

Validation

  • 179 unit and regression tests, including unique-ID parity tests for declared/undeclared device_class and channel/RPS switches
  • Home Assistant 2026.7.3 import and runtime smoke
  • HACS validation and Hassfest
  • Ruff lint/format and runtime dependency audit

Documentation: README — migration section

Assets 3
Loading