Can't control my roller shutter with rflink

I’ve set up rflink in HA. It works. I can control KAKU switches. And all rf devices show up in HA.
However, my roller shutter switch isn’t working.
I’ve received all the codes via rflink and the device is showing up in HA as light.rts_2157629_01. However when I create a switch, or call the service to switch on or off, the shutters are not going up or down.

The brand is ‘ASA’ and is supported bij rflink.

What am I doing wrong?
I call the service turn_off and turn_on for identity light.rts_2157629_01 , but that doesn’t work. I’ve placed the rflink next to the shutters.

This is my full log:

Received data when pressing buttons on the remote:

20;2D;RTS;ID=2157629;SWITCH=
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] got packet: 20;2C;Debug;RTS P1;88f302cc157629;
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'debug', 'rts_p1': '88f302cc157629'}
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'raw', 'value': None, 'tm': None, 'pulses': None}
2020-09-20 17:27:25 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'id': 'raw', 'value': None, 'tm': None, 'pulses': None}
2020-09-20 17:27:25 DEBUG (MainThread) [homeassistant.components.rflink] unhandled event of type: unknown
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] received data: 01;CMD=DOWN;
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] got packet: 20;2D;RTS;ID=2157629;SWITCH=01;CMD=DOWN;
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'rts', 'id': '2157629', 'switch': '01', 'command': 'down'}
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'rts_2157629_01', 'command': 'down'}
2020-09-20 17:27:25 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'id': 'rts_2157629_01', 'command': 'down'}
2020-09-20 17:27:25 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['light.rts_2157629_01']
2020-09-20 17:27:25 DEBUG (MainThread) [homeassistant.components.rflink] passing event to light.rts_2157629_01
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] received data: 20;2E;Debug;RTS P1;86fc02cd15762
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] received data: 9;
20;2F;RTS;ID=2157629;SWITCH=
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] got packet: 20;2E;Debug;RTS P1;86fc02cd157629;
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'debug', 'rts_p1': '86fc02cd157629'}
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'raw', 'value': None, 'tm': None, 'pulses': None}
2020-09-20 17:27:41 DEBUG (MainThread) [homeassistant.components.rflink] event of type unknown: {'id': 'raw', 'value': None, 'tm': None, 'pulses': None}
2020-09-20 17:27:41 DEBUG (MainThread) [homeassistant.components.rflink] unhandled event of type: unknown
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] received data: 01;CMD=UP;
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] got packet: 20;2F;RTS;ID=2157629;SWITCH=01;CMD=UP;
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'rts', 'id': '2157629', 'switch': '01', 'command': 'up'}
2020-09-20 17:27:41 DEBUG (MainThread) [rflink.protocol] got event: {'id': 'rts_2157629_01', 'command': 'up'}
2020-09-20 17:27:41 DEBUG (MainThread) [homeassistant.components.rflink] event of type command: {'id': 'rts_2157629_01', 'command': 'up'}
2020-09-20 17:27:41 DEBUG (MainThread) [homeassistant.components.rflink] entity_ids: ['light.rts_2157629_01']
2020-09-20 17:27:41 DEBUG (MainThread) [homeassistant.components.rflink] passing event to light.rts_2157629_01```

Log when trying to control the shutters via a switch in home assistant:

2020-09-20 17:26:56 DEBUG (MainThread) [rflink.protocol] sending command: {'protocol': 'rts', 'id': '2157629', 'switch': '01', 'command': 'off'}
2020-09-20 17:26:56 DEBUG (MainThread) [rflink.protocol] writing data: '10;rts;2157629;01;off;\r\n'
2020-09-20 17:26:56 DEBUG (MainThread) [rflink.protocol] waiting for acknowledgement
2020-09-20 17:27:00 DEBUG (MainThread) [rflink.protocol] received data: 20;2B;OK;
2020-09-20 17:27:00 DEBUG (MainThread) [rflink.protocol] got packet: 20;2B;OK;
2020-09-20 17:27:00 DEBUG (MainThread) [rflink.protocol] decoded packet: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-09-20 17:27:00 DEBUG (MainThread) [rflink.protocol] command response: {'node': 'gateway', 'protocol': 'unknown', 'ok': True}
2020-09-20 17:27:00 DEBUG (MainThread) [rflink.protocol] packet acknowledged
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] received data: 20;2C;Debug;RTS P1;88f302cc15762
2020-09-20 17:27:25 DEBUG (MainThread) [rflink.protocol] received data: 9;```

The only thing I’ve noticed which is different is that the remote has the command ‘down’ and ‘up’. But HA uses ‘on’ and ‘off’. But should that work?

RFLink automatic add ‘detects’ all the devices like sensor or light.
Once the device_id is detected, you can configure the device with the correct type.


Once you got the device_id from your remote you can configure it like a cover device in HA.

TL;DR Can you try the following test?
From the developer console invoke the cover.open_cover service with:

entity_id: cover.rts_2157629_01 

You can try also the cover.close_cover service.

Thanks. So I’ve putted this in my configuration.yaml:

cover:
  - platform: rflink
    devices:
      - rts_2157629_01:
        name: rolluik_voor

Or isn’t this the way to ‘configure the device with the correct type.’? Because I can’t see the identity in the identities list. But the cover service showed up under Developer Tools.

However, the cover doesn’t go down or up…

Also. My light switch isn’t showing in the identities after restarting HA until I hit the original switch again. I also can’t control them until I hit the original switch.

My config

rflink:
  port: /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0

light:
  - platform: rflink
    automatic_add: true
    devices:
      - newkaku_0227128a_2:
        name: tuinverlichting

cover:
  - platform: rflink
    devices:
      - rts_2157629_01:
        name: rolluik_voor
        
sensor:
  - platform: rflink
#    automatic_add: true

Knipsel

What am I’m doing wrong?

Edit:

I also get this message now when trying to restart:

Invalid config for [cover.rflink]: expected a dictionary for dictionary value @ data[‘devices’]. Got [OrderedDict([(‘rts_2157629_01’, None), (‘name’, ‘rolluik_voor’)])]. (See ?, line ?). Invalid config for [light.rflink]: expected a dictionary for dictionary value @ data[‘devices’]. Got [OrderedDict([(‘newkaku_0227128a_2’, None), (‘name’, ‘tuinverlichting’)])]. (See ?, line ?).

So I guess my configuration.yaml isn’t correct. I’ve tried to find the answers online, but I just can’t figure it out

It seems to me that there is a problem in your config.

It should be something like:

light:
  - platform: rflink
    automatic_add: true
    devices:
      newkaku_0227128a_2:
        name: tuinverlichting

cover:
  - platform: rflink
    devices:
      rts_2157629_01:
        name: rolluik_voor

Can you see the difference?

OMG. Staring for 3 minutes to spot the difference haha. But I’m gonna try this! Fingers crossed

Thank you

I should have given you some clue… :sweat_smile:

Also, you need to know that if you set a device name, HA will expose it with the name:

  • light.tuinverlichting
  • cover.rolluik_voor

My lights are working when calling turn_on or turn_off light.tuinverlichting
But my cover isn’t working when cover.open_cover

the entity id has also changed to rts_2bc3265_01 after rediscovering the remote. But also when adding this to devices in my config it doens’t work.

However, it’s showing up in identities:

The brand is ASA. Maybe it’s just like Somfy and the rflink gateway has to be paired with the shutter like explained here?:
https://www.letscontrolit.com/forum/viewtopic.php?t=3399

Ok, once your config seems correct, let’s look at the problem with the covers.

From what I have been able to find the ASA blinds should work with the RTS protocol:

You should know that the RTS protocol is a ‘rolling code’ type, so it is not recommended to use the same device_id as your remote.

The right thing to do would be to find a suitable device_id for your blind and pair it following your cover pairing procedure. According to the ‘letscontrolit’ link, maybe you will need a 7 digit code (similar to the one you get from your remote). It’s recommended to use a similar one to yours.

To do this, can be necessary to use the RFLinkLoader software from a computer and follow the procedure for pairing the blind:

Please note that all this is for ‘somfy’ blinds and may not be the same in your case.

You can use this guide, but I will try with a 7 character code.

What do you mean with I’ll try a 7 character code?

The documentation makes references to codes with 6 character (like the following):

  • 10;RTS;0F0F0F;0412;3;PAIR;

In HA, this will be referenced with: RTS_0F0F0F_03

According to the ‘letscontrolit’ link, for your ASA cover you need a 7 character code, therefore, something like:

  • 10;RTS;2bc3241;0412;3;PAIR;

I think that at this point the rolling code is not important and you can use any value.

Would it be possible to send the ‘pair’ command through HA with a custom service or something?

I don’t think so, but I haven’t tried.