RFLink Switch

The rflink component support devices that use RFLink gateway firmware, for example the Nodo RFLink Gateway. RFLink gateway is an Arduino firmware that allows two-way communication with a multitude of RF wireless devices using cheap hardware (Arduino + transceiver).

First you have to set up your rflink hub.

The RFLink component does not know the difference between a switch and a light. Therefore all switchable devices are automatically added as light by default.

RFLink switch/light ID’s are composed of: protocol, id, switch. For example: newkaku_0000c6c2_1.

Once the ID of a switch is known it can be used to configure it as a switch type in HA, for example to add it to a different group, hide it or configure a nice name.

Configuring a device as switch with a nice name:

# Example configuration.yaml entry
  platform: rflink
    fire_event: true
    signal_repetitions: 2
      name: Ceiling fan
      name: Motion sensor kitchen

Configuration variables:

  • devices (Optional): A list of devices with their name to use in the frontend.
  • device_defaults: (Optional)
    • fire_event (Optional): Set default fire_event for RFLink switch devices (see below).
    • signal_repetitions (Optional): Set default signal_repetitions for RFLink switch devices (see below).

Device configuration variables:

  • name (Optional): Name for the device, defaults to RFLink ID.
  • aliases (Optional): Alternative RFLink ID’s this device is known by.
  • fire_event (Optional): Fire a button_pressed event if this device is turned on or off (default: False).
  • signal_repetitions (Optional): Repeat every RFLink command this number of times (default: 1)
  • group (Optional): Allow switch to respond to group commands (ALLON/ALLOFF). (default: yes)
  • group_aliases (Optional): aliases which only respond to group commands.
  • no_group_aliases (Optional): aliases which do not respond to group commands.

Switch state

Initially the state of a switch is unknown. When the switch is turned on or off (via frontend or wireless remote) the state is known and will be shown in the frontend.

Sometimes a switch is controlled by multiple wireless remotes, each remote has its own code programmed in the switch. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliases:

# Example configuration.yaml entry
  platform: rflink
      name: Ceiling fan
      icon: mdi:fan
        - newkaku_000000001_2
        - kaku_000001_a

Any on/off command from any alias ID updates the current state of the switch. However when sending a command through the frontend only the primary ID is used.

Device support

See device support