Use a door sensor with RFLink

Configuration
1

Hi,

If a Kerui door sensor that shows up in RFLinkLoader :

2017-11-09 21:52:20 - 20;03;Eurodomest;ID=28a105;SWITCH=01;CMD=ON;
2017-11-09 21:52:26 - 20;04;Eurodomest;ID=28a105;SWITCH=00;CMD=OFF;

I’ve automatic_add: true in my configuration, but the sensor doesn’t show up in HA:

2017-11-09 23:44:16 INFO (MainThread) [homeassistant.components.rflink] Initiating Rflink connection
2017-11-09 23:44:16 INFO (MainThread) [homeassistant.components.rflink] Connected to Rflink
2017-11-09 23:44:16 DEBUG (MainThread) [rflink.protocol] connected
2017-11-09 23:44:17 DEBUG (MainThread) [rflink.protocol] received data: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R48;
2017-11-09 23:44:17 DEBUG (MainThread) [rflink.protocol] got packet: 20;00;Nodo RadioFrequencyLink - RFLink Gateway V1.1 - R48;
2017-11-09 23:44:17 DEBUG (MainThread) [rflink.protocol] decoded packet: {'firmware': 'RFLink Gateway', 'version': '1.1', 'hardware': 'Nodo RadioFrequencyLink', 'revision': '48', 'protocol': 'unknown', 'node': 'gateway'}
2017-11-09 23:44:17 DEBUG (MainThread) [rflink.protocol] got event: {'firmware': 'RFLink Gateway', 'version': '1.1', 'hardware': 'Nodo RadioFrequencyLink', 'revision': '48', 'id': 'rflink'}
2017-11-09 23:44:17 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'firmware': 'RFLink Gateway', 'version': '1.1', 'hardware': 'Nodo RadioFrequencyLink', 'revision': '48', 'id': 'rflink'}
2017-11-09 23:44:17 DEBUG (MainThread) [homeassistant.components.rflink] unhandled event of type: unknown
2017-11-10 06:51:31 ERROR (Thread-14) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2017-11-10 06:53:11 DEBUG (MainThread) [homeassistant.components.rflink] Sending command: UP to Rflink device: RTS_0F0F0F_0
2017-11-10 06:53:11 DEBUG (MainThread) [rflink.protocol] sending command: {'switch': '0', 'command': 'UP', 'protocol': 'RTS', 'id': '0F0F0F'}
2017-11-10 06:53:11 DEBUG (MainThread) [rflink.protocol] writing data: '10;RTS;0F0F0F;0;UP;\r\n'
2017-11-10 06:53:11 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2017-11-10 06:53:14 DEBUG (MainThread) [rflink.protocol] received data: 20;01;OK;
2017-11-10 06:53:14 DEBUG (MainThread) [rflink.protocol] got packet: 20;01;OK;
2017-11-10 06:53:14 DEBUG (MainThread) [rflink.protocol] decoded packet: {'ok': True, 'protocol': 'unknown', 'node': 'gateway'}
2017-11-10 06:53:14 DEBUG (MainThread) [rflink.protocol] command response: {'ok': True, 'protocol': 'unknown', 'node': 'gateway'}
2017-11-10 06:53:14 DEBUG (MainThread) [rflink.protocol] packet acknowledged

As you can see, the RTS cover I set up works fine.

Any one has an idea how I can use the data I got from the RFLinkLoader to use in HA as a door sensor/switch/light to trigger automation?

Thanks

1 Like
2

I set mine up manually… in switches.yaml

- platform: rflink
  device_defaults:
    fire_event: true
    signal_repetitions: 1
  devices:
    eurodomest_25a44d:
      name: RFL Greenhouse Door

you can then use
rfl_greenhouse_door as the entity_id in your automations etc.

1 Like
3

Thanks,
and finally I found out that my RFLink was to far away from the sensor…
So now the sensor shows up, but I get

2017-11-10 21:37:35 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'id': 'eurodomest_002c75_00', 'command': 'off'}
2017-11-10 21:38:41 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'id': 'eurodomest_28a105_01', 'command': 'on'}

So, it switches one always on, and the other always off… So I need to toggle the other when one event is fired.

1 Like
4

Yep I have the same thing with Fuer’s door sensors it’s a bit of a pain but it may be possible to remedy it with the RFLink Learning procedure…

RFlink ‘RF Signal Learning’ mechanism
Q: My device is recognized differently multiple times or is detected with different protocols or ON/OFF is swapped, can this be fixed?
A: Yes, from R46 RFlink has a ‘RF Signal learning’ ability for some protocols.

What you need to do (once):

  • Use RFLink Loader - enter command: 10;rffind=on;

Press the ‘ON’ button on your remote control.
RFlink will display something like:
20;22;RFFind;x;151557;B;1E;1;

Press the ‘OFF’ button on your remote control.
RFlink will display something like:
20;2D;RFFind;x;151554;B;1F;1;

change the above commands into
10;RFFind;0;151557;B;1E;1;
10;RFFind;1;151554;B;1F;1;
send both commands to RFLink.

Check if the data was written correctly with command:
10;rfshow;

RFLink should display something like: (of course with with your values/numbers)
RF Record: 0 ID: 151557 S: 0B L: 1E T: 01 - ON
RF Record: 1 ID: 151554 S: 0B L: 1F T: 01 - OFF

Disable the learn mode with:
10;rffind=off;

After that RFLink will automatically recognize the signal.

I’m going to give it a try later today if I get time.

2 Likes
5

yes I found this FAQ on their site, will try this too :slight_smile: (if I can get my hands on the Windows PC).
I wonder how this works as the Kerui sensors have also an “Alarm” state (the button at the back that gets off when you unstick the sensor). In my case it was switch=03 which goes “on”.

6

I would just use that in a separate automation to inform of tampering.