EnOcean integration: import your YAML devices to the UI, plus clickable device triggers for automations

Hi all,

I maintain the EnOcean Custom integration, the one in the default HACS store. Three releases went out recently that close two pain points anyone with an older EnOcean setup will recognize: getting legacy YAML devices into the UI without breaking anything, and building automations without copying four-byte radio IDs by hand.

Import YAML devices into the UI (v2.3.0)

If your EnOcean installation predates the UI config flow, your binary sensors and switches live in configuration.yaml. Adding or renaming a device meant editing that file and restarting Home Assistant.

The integration’s options now include an import step. You get a preview of what was detected, duplicates are skipped, and nothing is written until you confirm. Imported devices keep their original unique IDs, so entity IDs stay the same and dashboards and automations keep working. The YAML is never removed for you: review the result, then delete it yourself when satisfied. sensor, light and climate remain YAML-only for now and are refused explicitly instead of being imported blindly.

I ran it on my own house first: 36 YAML devices imported, one restart, every entity ID unchanged.

Device triggers (v2.4.0 and v2.4.1)

Rocker devices now expose native device triggers in the automation editor: button pressed, button released, channel 1, channel 2. You pick the device from a list instead of writing an event trigger with a hex ID, and the automation then shows up in the device’s “Used in” section, which never worked with raw event triggers.

The 2.4.1 update adds optional channel and position filters, because real EnOcean setups rely on them. My shutter controls fire on button release with a specific channel and position, and my lights use the position to tell on from off. With those filters, any existing button_pressed event trigger converts to a device trigger with identical matching. I converted 56 triggers across 31 automations at home using a script that verified each conversion against the original event data before writing anything. Everything fires as before. The script isn’t part of the release, but if you’re sitting on a large YAML-era install and want the same conversion, say so here.

The legacy event is untouched. Nothing forces you to migrate.

Get it

Update through HACS as usual. Changelogs and downloads: github.com/szymkiewiczmathieu/ha_enocean_custom/releases

Also in recent releases if you missed them: a passive radio inbox and local device catalog (v2.2.0), and Device Intelligence for identifying unknown senders (v2.1.0).

Bug reports go to GitHub, everything else here.