Just to report to other users and follow up, inform that a possible change in RFLink STATUS messages has been reported. In RFLink versions R50 and R51, the HA integration (with the Aequitas library) causes a WARNING log parsing the gateway's STATUS message: 2025-03-13 11:15:13.283 DEBUG (MainThread)...

Some RTS motors have that behavior. According to the docs: Press the MY button on the Telis RTS remote control for 5 seconds, the blind will confirm to indicate the change of mode. References: * https://www.letscontrolit.com/forum/viewtopic.php?t=8151 * https://www.somfy-profesional.es/documents/193...

I would use just RC until all the covers are paired. With RFLink Loader, the PAIR command would 'save' the record you give to them. Let's focus on the 'new' code to control all the cover at once and forget about all the other existing ones. When you call the RFLink command, the record in the RFLink ...

If all triggers are movement from the PIR sensor, you can configure in HA the entities as alias of the same device. This is something common in RFLink integration. It would be something like: binary_sensor: - platform: rflink devices: friedland_1472f4_22: name: my PIR sensor device_class: motion off...

It may be an unsupported blind model, but if you've managed to get it to work with the remote's code, it should be possible to match another code. Can you try using a slightly different remote code? Taking into account that your remote code is 'B70E28' you could try with 'B70E38' or with 'B70E20' an...

Some comments that I hope will help you. Most important! Don't use the same code from remote in RFLink. If you do, you can cause the blind rolling code to increase and that you can no longer control the blind with the remote control (with a minor rolling code). This may be the reason why the blind s...

Good!
Thanks for letting us know

There are several reports detailing the behavior you comment on. It seems clear that the blinds have 2 working modes: 10.2 Using a Telis RTS remote control By default, the Mod/Var receiver is delivered in “US” mode . When Telis RTS remote control is being used: Briefly pressing (< 0.5 seconds) on th...

Yes, first a patch in @aequitas library is needed. You can ask him in github.

Once new version is available, an upgrade in HA must be done. Also can be asked in HA github.

Not quite.

It is fixed for protocol:

Your problem is with protocol To be addressed the same way that in the 'dooya_v4' case, this protocol must be fixed in @aequitas rflink library, and then upgraded in RFLink dependencies.

I think it's related to this other bug in Home Assistant: https://community.home-assistant.io/t/wth-is-rflink-doing-with-underscores-resolved/221658/4 The @aequitas library don't support protocols ID with underscores and exceptions must be made in the library: * https://github.com/aequitas/python-rf...

The problem I see is that I don't know how to simulate the "hold down the key" part with RFLink, I suppose you can repeatedly send one command in RFLink, but I don't know if it will be the same behavior. I always have set my devices with a 0 for the switch value, but my remotes (somfy tell...

The PAIR command is just to add it to RFLink's memory (if I'm not wrong) not to pair it with the SGS switchboard. I may ask a silly question, but have you put the SGS switchboard in pairing mode (power button> 2s)? I would try the UP command or changing the switch number, for example: 10;RTS;288b4f8...

I do not have the SGS mechanism (I did not even know it before reading this post), but from what I have read, I would follow the somfy pairing procedure for the 3 button remote control. To do this, I would first add a new remote in RFLink with a slightly different code than the one that can be read ...

I'm glad you were able to get it working (more or less) ;) . I would say it may be related to the code you were trying to use. I suggest you do a test with a slightly different code than the ones your remote uses. If you have already tested with 4 codes, it will be easy for you to use a new code tha...

What you can to try is to test the RFLink with the remote's code. You can do it, recording in your RFLink the same address and a slightly bigger rolling code from your remote. No need to put your cover in 'PAIRING MODE'. Once you verify that RFLink list the remote code and a few bigger rolling code,...

I recommend you to use an "slightly changed address" for the new remote. In your case maybe something like 8cda33 or 8cdb31.

Cheers.

Ref:

• http://www.rflink.nl/blog2/faq#RTS

If I'm not mistaken, your config should be as follows: