RFlink: Migrating legacy configuration format to new

Hi,

I've just migrated to the new RFlink configuration YAML format. The legacy format is deprecated and will be removed at the end of 2026. (See the official doc).

Your RFlink configuration might be split into separate YAML configurations for the domains: Sensor, Switch, Light, Cover, and Remote. When moving to the new configuration format while having a split configuration, pay attention to the following:

The current include syntax in your configuration.yaml will not work with the new RFlink configuration. However, with some simple changes, this can be solved.

Since the sensor domain is now nested inside the rflink: block rather than being a top-level platform entry, you can't use a top-level !include the same way you would for, say, sensor.yaml. However, you can still split it by including it at the devices: key level.

Your new configuration.yaml will look something like this:

rflink:
  port: /dev/serial/by-id/usb-Arduino__www.arduino.cc__0042_75130303735351A031C1-if00
  ignore_devices:
    - newkaku_000001_01 # example
    - digitech_* # example
  sensor: #domain
    devices: !include rflink_sensors.yaml
  light: #domain
    devices: !include rflink_lights.yaml
  switch: #domain
    devices: !include rflink_switches.yaml

The separate device configurations (such as rflink_lights.yaml) will now look like this:

# devices
  newkaku_000049cf_2:
    name: Hal en buitenlicht
  newkaku_0000343f_2:
    name: Keuken - plafond
  newkaku_0000693d_2:
    name: Tafel

Pay attention to the lines being indented!

The difference is that the new include files now contain devices only, instead of domains with nested devices.

For anyone interested, take a look at a new HACS integration: RFlink UI. OnGitHub, or this community post here. It's missing some bits and pieces still, but it looks great.

I hope this helps.

Definitely! Thanks. I'll change the post.

does it support learning and sending open and close signals for roller shutters?