Skip to content

EnOcean Custom v2.1.0 — Device Intelligence

Choose a tag to compare

View all tags
@szymkiewiczmathieu szymkiewiczmathieu released this 05 Aug 10:05
v2.1.0
aca8bc9

EnOcean Custom 2.1.0 — Device Intelligence

This release adds local, evidence-based device identification without pretending that a radio sender ID is a commercial product reference.

Highlights

  • Extracts exact RORG/FUNC/TYPE and manufacturer ID from UTE and enriched 4BS teach-in telegrams.
  • Parses EnOcean Alliance 30S / 1P labels with strict 32-bit EURID and Product ID validation.
  • Adds explicit evidence and compatibility levels: exact, assisted, manual, profile unknown; supported, manual, unsupported, unknown.
  • Adds a strict manual EEP field that cannot overwrite radio- or product-declared evidence.
  • Groups UI and legacy YAML entities in the Home Assistant Device Registry by radio sender.
  • Resolves manufacturer/model only from an exact local Product ID catalogue match.
  • Adds French and English radio identity cards and a documented EEP-to-platform implementation matrix.

Radio safety and privacy

  • Automatic background UTE acknowledgement is disabled. Unsolicited UTE telegrams are observed for identity evidence but never answered on the radio.
  • QR security containers 10Z, 11Z, and 13Z, raw QR payloads, sender IDs, Product IDs, and radio metadata are excluded from exportable diagnostics.
  • Device intelligence is fully local and requires no runtime network service.

Initial implementation matrix

Implemented profiles include F6-02-01/02, F6-10-00, D5-00-01, A5-10-06, A5-12-01, A5-20-04, A5-38-08, D2-01-0B, and D2-01-12. Configuration mode and receive/transmit limitations are shown separately in the UI and documentation.

Validation

  • 159 unit and regression tests
  • Home Assistant 2026.7.3 import and runtime smoke
  • HACS validation and Hassfest
  • Ruff formatting/lint and runtime dependency audit

Honest limitations

  • A sender ID alone never identifies a manufacturer or model.
  • Passive F6/D5 devices can legitimately remain profile-unknown.
  • Existing YAML entities are grouped but are not assigned retroactive identity claims.
  • A catalogued product can still be unsupported when no exact decoder exists.

Full design, privacy model, sources, and compatibility matrix: Device Intelligence documentation

Assets 3
Loading