Hi have you been able to sort this out? I;m dealing with the same issue here…
I set mine up manually… in switches.yaml
- platform: rflink
device_defaults:
fire_event: true
signal_repetitions: 1
devices:
eurodomest_25a44d_01:
name: RFL Greenhouse Door Open
Then in automations.yaml…
- alias: "Send notification upon Greenhouse Door Open"
initial_state: 'on'
trigger:
- platform: state
entity_id: switch.rfl_greenhouse_door_open
to: 'on'
for:
minutes: 10
condition:
condition: state
entity_id: input_boolean.keithhome
state: 'off'
action:
- service: notify.mypushbullet
data:
message: 'Greenhouse Door Open'I’ll give it a shot. Thanks in advance!
OK, no results.
Goal is to send a notifaction when the doorbell rings. Signal is received via RfLink, switch is turning on. It would be nice that it turns off autmatically after n seconds. My configuration:
switch:
# - platform: random
- platform: rflink
device_defaults:
fire_event: true
signal_repetitions: 1
devices:
selectplus_1fd7_01:
name: Hekbel
automation:
- alias: Stuur notificatie bij bellen hek
trigger:
platform: state
entity_id: switch.selectplus_1fd7_01
to: 'on'
action:
service: notify.Pushbullet
data:
message: "Er staat iemand aan het hek"
event via RFLink:
got event: {'id': 'selectplus_1fd7_01', 'doorbell_melody': 1, 'command': 'on'}
any idea how to get this running?
BTW, seems to me that this isn’t the right place for asking support. Do you recommend an other Forum to get support?
automation:
- alias: Stuur notificatie bij bellen hek
trigger:
platform: state
entity_id: switch.selectplus_1fd7_01
to: 'on'
action:
service: notify.Pushbullet
data:
message: "Er staat iemand aan het hek"
These need to be changed…
switch.selectplus_1fd7_01 -----> switch.hekbel <----- Note lowercase H
service: notify.Pushbullet ------> notify.pushbullet <----- Lowercase P
To turn off after a certain time…add a delay and then turn off the switch
action:
service: notify.Pushbullet
data:
message: "Er staat iemand aan het hek"
delay: 00:00:10 <-------- delay 10 secs
service: switch.turn_off
entity_id: switch.hekbel
How have you got the RFL connected? I have mine connected via usb.
Hi,
I’ve also connected it via USB.
Your solution worked partially. I’ve received the push message. Cool! But adding the second actions results in een config error: dublikate key service. My automation config:
- alias: Stuur notificatie bij bellen hek
trigger:
platform: state
entity_id: switch.hekbel
to: 'on'
action:
service: notify.pushbullet
data:
message: "Er staat iemand aan het hek"
delay: 00:00:10 <-------- delay 10 secs
service: switch.turn_off
entity_id: switch.hekbel
Am i missing some basic config?
Hi Keith, I figured out that your answer was missing some dashes at he service and delay lines. This config did the trick:
automation:
- alias: Stuur notificatie bij bellen hek
trigger:
platform: state
entity_id: switch.hekbel
to: 'on'
action:
- service: notify.pushbullet
data:
message: "Er staat iemand aan het hek"
- alias: auto_off doorbell
initial_state: 'on'
trigger:
platform: state
entity_id: switch.hekbel
to: 'on'
action:
- delay: '00:00:10'
- service: switch.turn_off
entity_id: switch.hekbel
1 Like
I allready posted this before, but apparently at the wrong spot. Now I found this threat I try again :
I have a remote control for my lights (Tristate bought at Dutch shop called Action)
Signals of these remote control are received by RFlink
When pressing button 5 this is in te log :
sending command: {‘id’: ‘8554aa’, ‘command’: ‘off’, ‘switch’: ‘5’, ‘protocol’: ‘tristate’}
for every button I press the same line appears, only the switch number changes
So I added 5 devices in light.yaml wtih id : tristate_8554aa_1 till …5
However, no matter what switch in HA I press, it switches the same light allthougd the command send seem to be right
(see log). Anyone has the same experience and found a solution ?
2017-10-03 21:13:49 DEBUG (MainThread) [homeassistant.components.rflink] Sending command: off to Rflink device: tristate_8554aa_5
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] sending command: {'id': '8554aa', 'command': 'off', 'switch': '5', 'protocol': 'tristate'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] writing data: '10;tristate;8554aa;5;off;\r\n'
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2017-10-03 21:13:49 DEBUG (MainThread) [homeassistant.components.rflink] Sending command: off to Rflink device: tristate_8554aa_2
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: 20;79;OK
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: ;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] got packet: 20;79;OK;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] packet acknowledged
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] sending command: {'id': '8554aa', 'command': 'off', 'switch': '2', 'protocol': 'tristate'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] writing data: '10;tristate;8554aa;2;off;\r\n'
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: 20
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: ;7A;OK;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] got packet: 20;7A;OK;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] packet acknowledged
2017-10-03 21:13:49 DEBUG (MainThread) [homeassistant.components.rflink] Sending command: off to Rflink device: tristate_8554aa_2
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] sending command: {'id': '8554aa', 'command': 'off', 'switch': '2', 'protocol': 'tristate'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] writing data: '10;tristate;8554aa;2;off;\r\n'
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: 2
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] received data: 0;7B;OK;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] got packet: 20;7B;OK;
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:49 DEBUG (MainThread) [rflink.protocol] packet acknowledged
2017-10-03 21:13:50 DEBUG (MainThread) [homeassistant.components.rflink] Sending command: off to Rflink device: tristate_8554aa_3
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] sending command: {'id': '8554aa', 'command': 'off', 'switch': '3', 'protocol': 'tristate'}
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] writing data: '10;tristate;8554aa;3;off;\r\n'
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] received data: 20;7C;OK;
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] got packet: 20;7C;OK;
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'ok': True, 'protocol': 'unknown'}
2017-10-03 21:13:50 DEBUG (MainThread) [rflink.protocol] packet acknowledged
20
Hi, do you have the yaml definitions of the lights for me?
This is what I have in light.yaml
device_defaults:
fire_event: true
signal_repetitions: 2
devices:
newkaku_011a078e_a:
name: Studeerkamer
newkaku_0099690e_b:
name: Slaapkamer kastlicht
newkaku_0099690e_c:
name: Slaapkamer schemerlamp
tristate_8554aa_1:
name: Schemerlamp bij muur
tristate_8554aa_2:
name: Schemerlamp vensterbank
tristate_8554aa_3:
name: Schemerlamp groot
tristate_8554aa_4:
name: Schakelaar ongebruikt (D)
tristate_8554aa_5:
name: Schemerlampen kast
newkaku_00cb9552_1:
name: Tuinverlichting
OK, looks fine to me. Did you try to use the automatic add feature?
light:
- platform: rflink
automatic_add: true
Press all the buttons and they will appear on your homescreen.
I added automatic_add to light.yaml and the buttons pressed appear as new devices/buttons.
Is there a reason for that ? The Tristate_xxxx were alleady recognized before, but with other names
You should stick to the names that appeared after the auto add. can you compare the old names with the new names and see what’s the difference?
It’s very quite here on the RFLink subject now. Has support or additions to RFLink Gateway finished ?
rflink is working quite well and is most rflink supported devices are integrated (lights/kaku/temp sensors/ somfy covers and more)
Only milight integration is still lacking afaik.
And support for unicode binary motion sensors. Tedious kludges required to make a uni-code PIR or door switch reset in HA. Tried most of them to make mine usable.
replying to an old question, this is solved by auto_off now see https://www.home-assistant.io/components/binary_sensor.mqtt/
For RFLink:
1 Like
Thanks for the heads-up scote.
Found the option called off_delay is available now in the binary_sensor link.
That will save a lot of the kludging for using the Sonoff RF bridge.
1 Like
Hi all,
Recently bought an RFlink and having some issues, hopefully someone can help.
Overall, HASS connects to RFLINK OK, following is my configuration entry:
Sending commands to my Kaku switches for my mechnical ventilation works very reliable, however, I’ve a major issue with receiving stuff from my Kaku doorbell.
I’ve added it as binary sensor in the configuration yaml (after finding ID via log):
Now it works after a fresh system start, but at some point in time (or after hass has been rebooted a few times), the RFLink integration is starting to drop the signals it receives from the doorbell. It will show:
DEBUG (MainThread) [rflink.protocol] received data: =c;CMD=ON;
WARNING (MainThread) [rflink.protocol] dropping invalid data: =c;CMD=ON;
A FULL system reboot (so not only HASS) seems to then be the only way to get it to function again, but after a while it will show the same behavior. When this pops-up, sending commands still works like a charm.
It is very annoying because the doorbell is now super unreliable and already made me miss some people at the door 
Did anyone experienced similar behavior or knows a solution or further debugging steps to this?