RFLink, NEXA (NewKaku) and group commands

Configuration
6

I think I have already seen the full picture of how the aliases and groups full thing works in RFLink.

First we must know that in RFLink there is 2 kinds of ‘command signals’: entity and group commands.
At the moment the group signals are: allon and alloff.
The entity command are for any kind of device: on, off, open, close, toggle, …

Ok, let’s suppose that we have a configuration like the yours:

light:
  - platform: rflink
    automatic_add: true
    devices:
      newkaku_006d7076_1:
        name: Main Button 1
        aliases:
          - newkaku_006d7076_0
        group_aliases:
          - newkaku_33333333_0
        no_group_aliases:
          - newkaku_33333333_1

The several RFLink configurations have the following behavior:

  • group: defines if your RFLink device will change its state if a ‘group signal’ is received for that device. This will define the behavior in HA if a signal like this is received:
[rflink.protocol] received data: 20;01;NewKaku;ID=006d7076;SWITCH=1;CMD=ALLON;
  • aliases: defines if your device will react to signals from other device. The typical example is when you want that your HA device state changes with signals from a physical remote control. Your device will react to entity and group commands. In our example, the HA state for newkaku_006d7076_1 will change with any entity or group command from newkaku_006d7076_0.
  • group_aliases: this is for when your device must reacts to group commands but not for entity commands for another device. In our example, the HA state for newkaku_006d7076_1 will change with a allon command from newkaku_33333333_0, but not if a entity command is received.
  • newkaku_33333333_1: the opposite one. Device newkaku_006d7076_1 will react to entity commands from newkaku_33333333_1 (and not for group commands)

As you can see, the parameters only serve to model the behavior in HA to the external signals for the diverse combinations of entity group commands.
In most cases, it is enough to correctly define the alias of our device since (for example) it is not likely that you will receive an on signal from the newkaku_006d7076_0 device.
For most people this is enought. All the other people can play with all this parameters.

You can test what is in your case the behavior of your device and model it according to your needs, making use of the utility services in the developer tools.

Cheers.

1 Like