I suppose the command was rather to be done in the nodered flow to have the configuration of the old system. I don’t realize what is the simplest:
I re-paired one of my shutters, and the re-pairing went well. However, it does not respond to the commands sent and does not create a new remote control. The same happens if I use a command that I use in Node-RED and that works. The only devices created are those when using the physical remote controls.
Gosh, do you have information in the logs (integration and gladys)?
RFlink accepts pairing, the shutter goes up and down when you put it in prog and goes up and down when it validates the pairing. You can see the pairing in the logs and the sending of the test command.
[2026-08-16T14:20:58.590Z] [INFO] RFLink <- 20;AE;RTS;ID=26d460;SWITCH=01;CMD=STOP;
[2026-08-16T14:20:58.866Z] [INFO] RFLink <- 20;AF;Debug;RTS P1;a38710f326d460;
[2026-08-16T14:20:58.869Z] [INFO] RFLink <- 20;B0;RTS;ID=26d460;SWITCH=01;CMD=STOP;
[2026-08-16T14:20:59.644Z] [INFO] [actions] Action send_command -> 10;RTS;A00001;0;PAIR;
[2026-08-16T14:21:02.894Z] [INFO] RFLink <- 20;B1;OK;
[2026-08-16T14:21:23.715Z] [INFO] [actions] Action send_command -> 10;RTS;A00001;0;DOWN;
[2026-08-16T14:21:26.987Z] [INFO] RFLink <- 20;B2;OK;
[2026-08-16T14:21:36.822Z] [INFO] RFLink <- 20;B3;PONG;
[2026-08-16T14:22:14.070Z] [INFO] [pipeline] Replaying the last known reading of ext:ext-philippema-gladys-rflink:rts:26d460-01
[2026-08-16T14:22:29.389Z] [INFO] [pipeline] Replaying the last known reading of ext:ext-philippema-gladys-
But when I do 10;RTSSHOW; there is no new pairing in RFlink. The new pairing is not in RFlink.
[2026-08-16T14:51:27.138Z] [INFO] [actions] Action send_command -> 10;RTSSHOW;
[2026-08-16T14:51:27.168Z] [INFO] RFLink <- RTS Record: 0 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.174Z] [INFO] RFLink <- RTS Record: 1 Address: F00010 RC: 0EDF
[2026-08-16T14:51:27.179Z] [INFO] RFLink <- RTS Record: 2 Address: F00020 RC: 0A9B
[2026-08-16T14:51:27.185Z] [INFO] RFLink <- RTS Record: 3 Address: F00030 RC: 0501
[2026-08-16T14:51:27.196Z] [INFO] RFLink <- RTS Record: 4 Address: F00040 RC: 0B6C
[2026-08-16T14:51:27.201Z] [INFO] RFLink <- RTS Record: 5 Address: F00050 RC: 0007
[2026-08-16T14:51:27.207Z] [INFO] RFLink <- RTS Record: 6 Address: F00060 RC: 041F
[2026-08-16T14:51:27.212Z] [INFO] RFLink <- RTS Record: 7 Address: F00070 RC: 064B
[2026-08-16T14:51:27.223Z] [INFO] RFLink <- RTS Record: 8 Address: F00080 RC: 032C
[2026-08-16T14:51:27.228Z] [INFO] RFLink <- RTS Record: 9 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.234Z] [INFO] RFLink <- RTS Record: 10 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.245Z] [INFO] RFLink <- RTS Record: 11 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.250Z] [INFO] RFLink <- RTS Record: 12 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.256Z] [INFO] RFLink <- RTS Record: 13 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.261Z] [INFO] RFLink <- RTS Record: 14 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.270Z] [INFO] RFLink <- RTS Record: 15 Address: FFFFFF RC: FFFF
Addresses 1 to 8 are the ones configured for my Node-RED flow.
Have you tried sending a new command:
10;RTS;A00001;0;UP;
And then immediately go to the discovery section. If you still don’t have the shutter, there must be something wrong. Do you have automatic discovery enabled in the configuration? If yes, and still no discovered shutter, I’ll escalate the issue to Claude. I’d like the integration logs 
Thanks for your patience, we’ll get there.
yes several times. automatic discovery is checked and a new device is created every time I use a physical remote control.
[2026-08-16T15:46:34.716Z] [INFO] RFLink <- 20;3B;PONG;
[2026-08-16T15:46:57.418Z] [INFO] [actions] Action send_command -> 10;RTS;A00001;0;UP;
[2026-08-16T15:47:00.657Z] [INFO] RFLink <- 20;3C;OK;
[2026-08-16T15:47:34.719Z] [INFO] RFLink <- 20;3D;PONG;
[2026-08-16T15:48:34.751Z] [INFO] RFLink <- 20;3E;PONG;
[2026-08-16T15:49:34.728Z] [INFO] RFLink <- 20;3F;PONG;
[2026-08-16T15:50:34.709Z] [INFO] RFLink <- 20;40;PONG;
[2026-08-16T15:51:34.729Z] [INFO] RFLink <- 20;41;PONG;
Okay, I’ll run Claude on the analysis.
Hello @elfedagger
There was probably an error in the pairing command that didn’t have the correct structure:
| Form | Syntax |
|---|---|
| Simple Pairing | 10;RTS;<address>;<rolling code>;PAIR; |
| Extended Pairing | 10;RTS;<address>;<rolling code>;<EEPROM slot>;PAIR; |
We worked on simple pairing when we should have used extended pairing. I found this by looking at what was done in other home automation solutions: Domoticz, RFLink et Somfy
To verify that this is the right track, can you in the integration send the following raw commands right after starting the shutter pairing (you have little time to send the command, <10 seconds):
10;RTS;A00001;0412;10;PAIR; (A00001 as you defined it earlier, 0412 for the rolling code initialization, 10 for the EEPROM address);10;RTS;A00001;0;DOWN; Can you tell me if this command made the shutter go down?And send me the logs.
If it worked, by typing the command 10;RTSSHOW; you should have (cf. slot 10):
[2026-08-16T14:51:27.138Z] [INFO] [actions] Action send_command -> 10;RTSSHOW;
[2026-08-16T14:51:27.168Z] [INFO] RFLink <- RTS Record: 0 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.174Z] [INFO] RFLink <- RTS Record: 1 Address: F00010 RC: 0EDF
[2026-08-16T14:51:27.179Z] [INFO] RFLink <- RTS Record: 2 Address: F00020 RC: 0A9B
[2026-08-16T14:51:27.185Z] [INFO] RFLink <- RTS Record: 3 Address: F00030 RC: 0501
[2026-08-16T14:51:27.196Z] [INFO] RFLink <- RTS Record: 4 Address: F00040 RC: 0B6C
[2026-08-16T14:51:27.201Z] [INFO] RFLink <- RTS Record: 5 Address: F00050 RC: 0007
[2026-08-16T14:51:27.207Z] [INFO] RFLink <- RTS Record: 6 Address: F00060 RC: 041F
[2026-08-16T14:51:27.212Z] [INFO] RFLink <- RTS Record: 7 Address: F00070 RC: 064B
[2026-08-16T14:51:27.223Z] [INFO] RFLink <- RTS Record: 8 Address: F00080 RC: 032C
[2026-08-16T14:51:27.228Z] [INFO] RFLink <- RTS Record: 9 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.234Z] [INFO] RFLink <- RTS Record: 10 Address: A00001 RC: 0412
[2026-08-16T14:51:27.245Z] [INFO] RFLink <- RTS Record: 11 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.250Z] [INFO] RFLink <- RTS Record: 12 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.256Z] [INFO] RFLink <- RTS Record: 13 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.261Z] [INFO] RFLink <- RTS Record: 14 Address: FFFFFF RC: FFFF
[2026-08-16T14:51:27.270Z] [INFO] RFLink <- RTS Record: 15 Address: FFFFFF RC: FFFF
Sorry for the delay in performing this test.
Here is the response I received after putting my shutter in programming mode and sending your extended pairing command.
The gateway refused « 10;RTS;A00001;0412;10;PAIR; » (CMD UNKNOWN).
The shutter should have gone up and down to validate the pairing, but it does not react.
Here is what the log shows.
[2026-08-19T15:07:39.757Z] [INFO] RFLink <- 20;DD;PONG;
[2026-08-19T15:07:40.764Z] [INFO] [actions] Action send_command -> 10;RTS;A00001;0412;10;PAIR;
[2026-08-19T15:07:40.790Z] [INFO] RFLink <- 20;DE;CMD UNKNOWN;
[2026-08-19T15:08:39.761Z] [INFO] RFLink <- 20;DF;PONG;
[2026-08-19T15:09:39.750Z] [INFO] RFLink <- 20;E0;PONG;
[2026-08-19T15:10:39.756Z] [INFO] RFLink <- 20;E1;PONG;
[2026-08-19T15:11:39.768Z] [INFO] RFLink <- 20;E2;PONG;
[2026-08-19T15:12:39.749Z] [INFO] RFLink <- 20;E3;PONG;
[2026-08-19T15:13:39.736Z] [INFO] RFLink <- 20;E4;PONG;
[2026-08-19T15:14:39.754Z] [INFO] RFLink <- 20;E5;PONG;
[2026-08-19T15:15:12.941Z] [INFO] [actions] Action send_command -> 10;RTSSHOW;
[2026-08-19T15:15:12.988Z] [INFO] RFLink <- RTS Record: 0 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:12.993Z] [INFO] RFLink <- RTS Record: 1 Address: F00010 RC: 0EDF
[2026-08-19T15:15:12.999Z] [INFO] RFLink <- RTS Record: 2 Address: F00020 RC: 0A9B
[2026-08-19T15:15:13.004Z] [INFO] RFLink <- RTS Record: 3 Address: F00030 RC: 0501
[2026-08-19T15:15:13.015Z] [INFO] RFLink <- RTS Record: 4 Address: F00040 RC: 0B6C
[2026-08-19T15:15:13.021Z] [INFO] RFLink <- RTS Record: 5 Address: F00050 RC: 0007
[2026-08-19T15:15:13.026Z] [INFO] RFLink <- RTS Record: 6 Address: F00060 RC: 041F
[2026-08-19T15:15:13.032Z] [INFO] RFLink <- RTS Record: 7 Address: F00070 RC: 064B
[2026-08-19T15:15:13.043Z] [INFO] RFLink <- RTS Record: 8 Address: F00080 RC: 032C
[2026-08-19T15:15:13.048Z] [INFO] RFLink <- RTS Record: 9 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.054Z] [INFO] RFLink <- RTS Record: 10 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.065Z] [INFO] RFLink <- RTS Record: 11 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.070Z] [INFO] RFLink <- RTS Record: 12 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.075Z] [INFO] RFLink <- RTS Record: 13 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.081Z] [INFO] RFLink <- RTS Record: 14 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:13.089Z] [INFO] RFLink <- RTS Record: 15 Address: FFFFFF RC: FFFF
[2026-08-19T15:15:39.749Z] [INFO] RFLink <- 20;E6;PONG;
ok, thanks. I’ll follow up with Claude on the topic; not today, I’m out of credits 
Your new update 1.0.4 works very well. I used one of the paired addresses in my RFlink and it created a shutter in discovery. The shutter responds to all commands. I will be able to create my 5 shutters, rename them like the ones I used in Node Red, and my Gladys scenes should work directly. Thank you.
Great news!
For the peer command I gave you, it was the slot that was broken. Apparently, the usable slots are between 0 and 9 even if the rtsshow shows more. Claude has no explanation.
I asked Gemini and got this answer.
How many max addresses in an RFlink?
There is no theoretical limit on the number of addresses recorded in RFLink itself, as it acts as a « transparent » gateway.
RFLink does not store a fixed list of your sensors or outlets in memory: it simply decodes the radio frames it intercepts (433 MHz, 868 MHz, etc.) and transmits them to your home automation system (Home Assistant, Jeedom, Domoticz, etc.).
The maximum number of addresses depends on two main criteria :
Each radio protocol managed by RFLink has its own address encoding:
Chacon / Blyss / RTS (Somfy) : The address is usually encoded on 24 to 32 bits (over 16 million to 4 billion unique addresses possible).
Oregon Scientific : The address depends on the channel IDs / rolling codes (often limited from 0 to 15 or according to the probe model).
Kaku / Coco (TriState) : Often limited by physical switches (A to P and 1 to 16, or 256 addresses).
If you accumulate too many radio devices on the same frequency (especially at 433 MHz), signal collisions will occur. In practice, beyond 50 to 100 wireless devices in frequent transmission/reception, the radio network becomes unstable.
RFLink Gateway
If your question concerns a specific protocol (e.g., Somfy RTS, Chacon, Oregon) or the use of a particular chip (e.g., NRF24L01 for MiLight), specify it to get the exact details of the protocol.
rts
For the Somfy RTS protocol in RFLink, the operation includes 16 configurable transmission addresses simultaneously.
Unlike simple fixed code protocols, RTS uses a rolling code (dynamic rotating code for security). RFLink must therefore store in EEPROM the counter of each virtual remote control it emulates.
| Element | RTS limit in RFLink |
|---|---|
| Transmission addresses (RFLink remotes) | 16 addresses (000001 to 000010 in hexadecimal) |
| Reception (Decoding) | Unlimited (RFLink reads all Telis/Smoove remotes that pass by) |
| Rolling Code Management | Stored in EEPROM (3 bytes per address) |
Somfy RTS type remote. Source: rozdemir01 / Getty Images
You must also consider the memory integrated into each Somfy blind or receiver:
A Somfy RTS motor or receiver can record up to 12 different remotes (or RFLink addresses) maximum.
If you exceed 12 paired transmitters on the same motor, the oldest one is automatically overwritten or the motor refuses the new pairing.
Pair by groups : A single RFLink address can be assigned to several blinds (e.g., one address for « All ground floor blinds »).
Use secondary RFLink commands : To manage more than 16 distinct virtual remotes in transmission, you need to compile a custom version of the firmware or use an extension like RTS RFPlayer or RRFBridge.
What are the RFLink commands to pair a Somfy RTS blind?
To pair a Somfy RTS blind with RFLink, the procedure is done directly via the serial console (or your home automation interface) by sending an association frame.
The command to be sent to the serial port is written as follows:
Plaintext
20;XX;RTS;123456;0;PAIR;
20 : RFLink command sending identifier.
XX : Sequential number (e.g., 0B, any two-digit hexadecimal number).
RTS : Targeted protocol.
123456 : Chosen virtual RTS address (hexadecimal from 000001 to 000010).
0 : Unit/button number (always 0 for Somfy RTS).
PAIR : Association command.
1
Put the blind in programming mode
Use the original Somfy remote control
Take the Somfy remote control already associated with the blind (e.g., Telis 1). Hold down the PROG button on the back of the remote control for about 2 to 3 seconds, until the blind makes a short back-and-forth movement (back-and-forth movement).
2
Send the PAIR command from RFLink
Within the minute following the back-and-forth movement, send the command with the virtual address assigned to this blind (for example, address 000001):
20;01;RTS;000001;0;PAIR;
3
Check the blind confirmation
If the order is well received, the blind makes a second back-and-forth movement. The address 000001 is now stored in the blind receiver.
Once the blind is paired, use the following standard commands:
| Action | RFLink Command |
|---|---|
| Up | 20;02;RTS;000001;0;UP; |
| Down | 20;03;RTS;000001;0;DOWN; |
| Stop / My Position | 20;04;RTS;000001;0;STOP; |
| Unpair the address | Repeat the procedure with PAIR (the blind disconnects) |