rflink component support devices that use Rflink gateway firmware, for example the Nodo Rflink Gateway. Rflink gateway is an Arduino firmware that allows communication with 433Mhz devices using cheap hardware (Arduino + 433Mhz tranceiver).
First you have to set up your rflink hub.
After configuring the Rflink hub lights will be automatically discovered and added.
New/unknown lights can be assigned to a default group automatically by specifying the
new_devices_group option with a group name. If the group doesn’t exist it will be created.
# Example configuration.yaml entry sensor: platform: rflink new_devices_group: "New Rflink Lights"
Rflink switch/light ID’s are composed of: protocol, id, switch. For example:
Once the ID of a light is known it can be used to configure the light in HA, for example to add it to a different group, hide it or configure a nice name.
Configuring a device as light with a nice name:
# Example configuration.yaml entry light: platform: rflink devices: newkaku_0000c6c2_1: name: Living room
- devices (Optional): A list of devices with their name to use in the frontend.
- new_devices_group (Optional): Create group to add new/unknown devices to.
- device_defaults: (Optional)
- fire_event_ (Optional): Set default
fire_eventfor Rflink switch devices (see below).
- signal_repetitions (Optional): Set default
signal_repetitionsfor Rflink switch devices (see below).
- fire_event_ (Optional): Set default
Device configuration variables:
- name (Optional): Name for the device, defaults to Rflink ID.
- type (Optional): Override automatically detected type of the light device, can be: switchable, dimmable or hybrid. See ‘Light Types’ below.
- aliasses (Optional): Alternative Rflink ID’s this device is known by.
- fire_event_ (Optional): Fire an
button_pressedevent if this device is turned on or off (default: False).
- signal_repetitions (Optional): Repeat every Rflink command this number of times (default: 1)
Initially the state of a light is unknown. When the light is turned on or off (via frontend or 433Mhz remote) the state is known and will be shown in the frontend.
Sometimes a light is controlled by multiple 433Mhz remotes, each remote has its own code programmed in the light. To allow tracking of the state when switched via other remotes add the corresponding remote codes as aliasses:
# Example configuration.yaml entry light: platform: rflink devices: newkaku_0000c6c2_1: name: Living room aliasses: - newkaku_000000001_2 - kaku_000001_a
Any on/off command from any allias ID updates the current state of the light. However when sending a command through the frontend only the primary ID is used.
Light devices can come in different forms. Some only switch on and off, other support dimming. Dimmable devices might not always respond nicely to repeated
on command as they turn into a pulsating state until
on is pressed again (for example KlikAanKlikUit). The Rflink component support three types of lights to make things work in every situation:
- Hybrid: This type sends a
dimfollowed by an a
offcommands. This will make dimmable devices turn on at the requested dim level and on/off devices on. One caveat is this type is not compatible with signal repetition as multiple
onsignals will cause dimmers to go into disco mode.
- Switchable: Device type that sends only
offcommands. It work for both on/off and dimmable type switches. However dimmables might have issues with signal repetition (see above).
- Dimmable: Sends only
offcommands. This does not work on on/off type devices as they don’t understand the
dimcommand. For dimmers this does not cause issues with signal repetitions.
By default new lights are assigned the
switchable type. Protocol supporting dimming are assigned the
hybrid type. Currently only
newkaku protocol is detected as dimmable. Please refer to Device Support to get your dimmers supported.
Lights are added automatically when the Rflink gateway intercepts a 433Mhz command in the ether. To prevent cluttering the frontend use any of these methods:
- Configure a
new_devices_groupfor lights and optionally add it to a different
- Hide unwanted devices using customizations
- Ignore devices on a platform level
See device support