Rflink 868 + Delta Dore X2D Tyxia 253 remote & Tyxia 4630 receivers

[Antoine1]

Hello to all,

I have recently bought and built an Rflink for 868mhz devices in order to use to control my home shutters.

My installation is actually manage via a remote Delta Dore Tyxia 253 and receivers Tyxia 4630 plugged at each shutters.


Depending on the website you are looking at the receiver is sometimes described as working on X2D protocol and sometimes on X3D protocol.
I am pretty sure that it is an X2D one as it is clearly written on the remote that the protocol is X2D and as the receivers are dated from 2011.

After assembly and soldering of the different part of the Rflink, everything seems to work properly as when I press on a button of the remote, the Rflink receives data properly but unfortunately, I do not manage to associate the receivers with the Rflink when trying to send a command.

Here is what I have when I press one time on the remote while it is in association mode + debug mode on Rflink Loader:

20;06;DEBUG;Pulses=511;Pulses(uSec)=2550,300,330,300,330,300,330,300,330,90,120,90,120,90,120,90,120,90,120,90,120,300,120,90,330,300,330,300,330,300,120,90,330,300,330,90,120,300,330,90,120,300,330,120,120,300,330,90,120,300,120,120,330,300,330,300,330,300,330,300,330,120,120,300,120,90,330,300,330,300,120,90,330,300,330,300,120,120,330,300,120,90,330,120,120,300,330,300,120,90,330,300,120,90,330,300,330,300,330,300,120,90,330,300,330,300,330,90,120,300,330,90,120,90,120,300,330,90,120,300,330,120,120,300,330,120,120,90,120,90,120,90,120,90,120,300,120,90,330,90,120,300,120,90,120,90,120,90,120,90,330,90,120,90,120,120,120,90,120,90,120,90,120,90,120,90,120,300,120,90,120,90,120,90,120,90,120,90,120,90,330,120,120,300,330,300,330,300,330,90,120,330,330,300,120,90,330,330,120,90,330,300,120,90,330,300,120,90,330,90,120,300,330,300,330,300,330,300,330,300,120,90,330,120,120,300,330,300,330,90,120,300,330,300,330,120,120,300,330,90,120,300,120,90,330,300,330,120,120,300,330,90,120,300,330,330,330,300,330,90,120,300,330,300,330,300,120,90,330,300,120,90,120,120,330,300,120,90,330,300,120,120,330,300,120,120,120,90,120,120,120,90,120,90,330,90,120,300,120,120,330,90,120,90,120,90,120,90,120,300,120,90,120,90,120,120,120,90,120,90,120,90,120,120,120,90,330,90,120,90,120,90,120,90,120,90,120,90,120,300,120,120,330,330,330,300,330,300,120,90,330,300,360,60,120,300,330,90,120,300,330,120,120,300,330,90,120,300,120,120,330,300,330,300,330,300,330,300,330,120,120,300,120,90,330,300,330,300,120,90,330,300,330,300,120,90,330,300,120,90,330,90,120,300,330,300,120,90,330,300,120,90,330,300,330,300,330,300,120,90,330,300,330,300,330,90,120,300,330,120,120,90,120,300,330,90,120,300,330,90,120,300,330,90,120,90,120,90,120,90,120,90,120,300,120,90,330,90,120,300,120,90,120,90,120,90,120,90,330,90,120,90,120,120,120,90,120,90,120,90,120,90,120,90,120,300,120,90,120,90,120,90,120,90,120,90,120,90,330,120,120,300,330,300,330,300,330,90,120,300,330;
20;07;X2DDEBUG;81485200859022812093fc7aff
20;08;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=2093;S=2281;BAT=OK;
20;09;DEBUG;Pulses=511;Pulses(uSec)=210,90,330,300,120,90,120,90,120,90,120,90,120,90,330,120,120,300,120,90,330,120,120,90,120,120,120,90,120,300,120,90,120,120,120,90,120,90,120,90,120,90,120,90,120,120,330,120,90,120,120,90,120,90,120,90,120,90,120,300,120,120,330,300,330,300,330,300,120,90,330,300,330,120,120,300,330,90,120,300,330,90,120,300,330,90,120,300,120,90,330,300,330,330,330,300,330,300,330,90,120,300,120,90,330,300,330,300,120,90,330,300,330,300,120,90,330,300,120,90,330,90,120,300,330,300,120,90,330,300,120,90,330,300,330,300,330,300,120,90,330,300,330,300,330,90,120,300,330,120,120,90,120,300,330,90,120,300,330,90,120,300,330,90,120,90,120,90,120,90,120,90,120,300,120,90,330,90,120,300,120,90,120,90,120,90,120,90,330,120,120,90,120,90,120,90,120,90,120,90,120,90,120,90,120,300,120,120,120,90,120,90,120,90,120,90,120,120,330,90,120,300,330,300,330,300,330,90,120,300,330,300,120,90,330,300,120,90,330,300,120,90,330,300,120,90,330,90,120,300,330,300,330,300,330,300,330,300,120,90,330,120,120,300,330,300,330,120,120,300,330,300,330,90,120,300,330,90,120,330,120,90,330,300,330,90,120,300,330,90,120,300,330,300,330,300,330,90,120,300,330,300,330,300,120,90,330,300,120,90,120,90,330,300,120,90,330,300,120,90,330,300,120,90,120,90,120,90,120,90,120,90,330,90,120,330,120,90,330,120,120,90,120,90,120,90,120,300,120,90,120,90,120,120,120,90,120,90,120,90,120,90,120,120,330,90,120,120,120,90,120,120,120,90,120,90,120,300,120,90,330,300,330,300,330,300,120,90,330,300,330,120,120,300,330,90,120,300,330,90,120,300,330,90,120,300,120,90,330,300,330,300,330,300,330,300,330,90,120,300,120,90,330,300,330,300,120,90,330,300,330,300,120,90,330,300,120,90,330,90,120,300,330,330,120,90,330,300,120,90,330,300,330,300,330,330,120,90,330,330,330,330,330,90,120,300,330,90,120,90,120,300,330,90,120,330,330,90,120,300,330,120,120,90,120,90,120,90,120,90,120,300,120,90,330,90,120,300,120,90,120,90,120,90,120,90,330,120,120,90,120;
20;0A;DEBUG;Pulses=50;Pulses(uSec)=270,330,90,630,150,270,180,750,300,450,150,510,270,570,270,450,150,750,60,270,120,930,270,1470,90,150,210,1110,120,660,120,660,180,480,90,780,240,780,30,210,180,1020,270,720,150,660,60,840,60,6990;

And here is what I have when I press several times the "up" button when the remote is in association mode with debug mode disabled:

20;0C;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=1e2b;S=2281;BAT=OK;
20;0D;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=c62a;S=2281;BAT=OK;
20;0E;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=69b0;S=2281;BAT=OK;
20;0F;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=f12b;S=2281;BAT=OK;
20;10;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=1a2b;S=2281;BAT=OK;
20;11;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=08b0;S=2281;BAT=OK;
20;12;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=b692;S=2281;BAT=OK;
20;13;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=c12a;S=2281;BAT=OK;
20;14;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=d092;S=2281;BAT=OK;
20;15;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=3692;S=2281;BAT=OK;
20;16;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=c52a;S=2281;BAT=OK;
20;17;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=e92a;S=2281;BAT=OK;
20;18;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=09b0;S=2281;BAT=OK;
20;19;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=b392;S=2281;BAT=OK;
20;1A;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=1c92;S=2281;BAT=OK;
20;1B;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=1c2b;S=2281;BAT=OK;
20;1C;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=ce2b;S=2281;BAT=OK;
20;1D;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=d692;S=2281;BAT=OK;
20;1E;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=0393;S=2281;BAT=OK;
20;1F;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=3893;S=2281;BAT=OK;
20;20;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=1493;S=2281;BAT=OK;
20;21;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=46b0;S=2281;BAT=OK;
20;22;X2D;ID=0014881;SWITCH=12;CMD=ON;EXT=TYXIA;RC=8892;S=2281;BAT=OK;

Do you think there is a chance to get it working or not?
In case you need additional logs tell me!

Many thanks in advance for your potential help (or not), I know X2D is tricky and that due to rolling code it might not be possible to make it working but I still have a little hope...

Regards

[molki]

I'm also interested in this, but don't have the 868 hardware yet. What 868 module did you use ?

For the protocol, are you sure this is the good way to go ?
For my shutters, when I want to associate a new remote, I have to use the old remote to set the shutter receiver to "associating mode", and then I have to press 2 buttons on the new remote for the receiver to accept and register it. (special command sent by the remote)

I think this is what we must decode before decoding how actions work. (decoding how the pairing with receivers work)

[Antoine1]

Hi,

In order to put the receivers in association mode, it is necessary to press a button at the back of the receiver.
In order to put the remote in learning mode I have to hold on the button in the middle of the remote for few secondes, then I have to select the area I want to associate this receiver with and finally press up or down button.

The logs I have posted are captures of the signal received by the RFlink when press up or down when both receiver and remote are in association.
What looks strange for me is that the signal received seems to be exactly the same than the one the remote is sending when it is not in association mode.

I could post more logs and do more tests if it can help.

Regarding the hardware, I bought it on Nodo shop, in a complete package.

Regards

[Stuntteam]

Association (Pairing) mode is already supported for some X2D models.. We are working on others.

[SuperCed]

Hi,

I try to command a Driver 220 CPL with a Tydom 520 inside.
The manufacturer told me that I need a Tydom 310 or 315 to control it, but I don't have that.
So I think I cannot sniff packets...

I am trying with a rflink 868.
How can I find the right command to pair my rflink with the Driver 200 and how can I find command in order to change in moon or sun etc ?

Thanks a lot!

[cyfm]

Just to revive this thread again ... What is the status of X2D/X3D support in firmware r48 ? I'm new to this forum and came across RFLink to access my Delta Dore X2D/X3D driven thermostats/heaters. Unfortunately my 868 RFLink doesn't receive anything at all of the RF traffic. Is there any documentation on how to get access ? Does it only work if I associate the RFLink somehow and there is no way to "listen" to the traffic ? I understand that not all models are supported but I assumed that I at least would be able to record some of the traffic.
Thanks for any related info.

Frank

[SuperCed]

I was able to listen to events on the rflink 868 using a open door detector (COX ref 6412202).
When the door is open, heater controller (driver 220 CPL with Tydom 520 module inside) sets up the anti freeze mode (I cannot remember the exact name in english... "hors gel" in french).
And when the door id closed, then the normal programmated mode is set up.

I was able to get this message between the door detector and the tydom receptor and I am able to modify it by code now.

But I think there are better ways to completely take control of driver 220 CPL.

Somewhere I read that if you have a Tydom 315 or 320, you can listen to different signals and then control your driver.
But I personally did not use this solution because of the price and my needs was just to put on or off the controller.

I got this kind of message:

Code: Select all

20;2D;X2D;ID=003e8ea;SWITCH=29;CMD=OFF;EXT=Contact;BAT=OK;

and I was able to control it via this kind of command:

Code: Select all

echo '10;X2D;03e8ea;29;ON;' > /dev/ttyACM0

In order to listen /dev/ttyACM0 on a raspbery pi, you need to set this dev to :

Code: Select all

/bin/stty -F /dev/ttyACM0 57600 sane -cstopb -parenb cs8 > /dev/null &
cat /dev/ttyACM0

[cyfm]

Also, what is the deal with the 868MHz frequency range ? I guess if the RFLink transceiver (mine is a Aurel 868.3 MHz Transceiver) works at 868.3Mhz, it also uses this as the center frequency and wouldn't work out of that range ? My X3D thermostat technical info mentions 868,7 to 869.2 MHz, so I guess they slightly moved the frequency and that silences any signal reception for me ?

[SuperCed]

I don't know how rflink works exactly. I ordered minel on https://www.nodo-shop.nl/nl/21-rflink-gateway .

I use X2D and not X3D, so I don't know what's happen with this protocol...

[cyfm]

Yea, I got mine prebuilt from nodo-shop.nl as well. Unfortunately, I have no clue if the rflink is properly working at all or is there some kind of selftest/loopback mode which could achieve the check/test ? At least the firmware seems to work as expected.
I probably was a bit too optimistic when I saw that the firmware changelog reported X2D/X3D protocol support.
I also have an older X2D thermostat which works in the 868MHz range but this doesn't show up as well.
Maybe I simply misunderstood how rflink is supposed to work in context of the X2D/X3D protocol. My (probably) naive idea was that it should at least be able to log any transmissions from the thermostat, albeit in some kind of unsupported debug mode once that is enabled in the firmware.

[SuperCed]

Plug your rflink on a raspberry and thy that :

Code: Select all

/bin/stty -F /dev/ttyACM0 57600 sane -cstopb -parenb cs8 > /dev/null &
cat /dev/ttyACM0

Let this code run some hours and then take a look if something is logged.
Maybe your sensor is not recognized if this is empty.

[cyfm]

Thanks, actually modified the line to

Code: Select all

/bin/stty -F /dev/ttyACM0 57600 sane -cstopb -parenb cs8 > /dev/null & miniterm /dev/ttyACM0 57600

in order to have some i/o terminal and to be able to send commands to RFLink as well but the channel stays pretty much silent ...

[SuperCed]

So maybe rflink firmware does not support these hardware.

And it's quite difficult to check without the developers because now the code is not open source anymore...

But I read somewhere that there is an old based version fork so maybe you'll find more devices supported.

I don't know if rflink firmware is often updated now.
I had the version 48 for a while and I did not check anymore.

[Stuntteam]

Obviously the fact that a protocol is supported does not mean each and every device using that protocol is supported.
You first need to receive data. If that is not happening you need to check if the receiver hardware is the issue.
If nothing is received the hardware needs to be checked.
If other devices are received then there might be a protocol issue.
When a device is received but you can not transmit then there is most likely a protocol issue as well.
Within the protocol there are several device type specific markers that need to be handled correctly.
Since I do not have all device flavors this can be difficult without debug data..

[cyfm]

Yea, thanks for feedback, understood.
Unfortunately, it is a bit difficult to create debug data without any reception at all. So either there is some problem with the 868.3 MHz Aurel transceiver which doesn't receive anything at all or the actual X2D/X3D thermostat/heater uses a slightly different frequency which the receiver doesn't care about.
Maybe I try to get hold of some 868.3MHz remote to check if the h/w works at all. At least I have no other idea how to check the hardware otherwise.

[Stuntteam]

What is the model number/type of your x2d (transmitting) device?
I can check if I have received data for it in the past..

[cyfm]

It's a DeltaDore OEM thermostat Device which has a TAP PILE OEM RETRO BLEU 7719934 product sticker attached.

Some reference I found is at

https://www.heizstrahler-shop24.de/heiz ... mostat.pdf

There is also a companion control unit attached to the heater.
Unfortunately, I don't have much more technical details.

I also own some newer models which seem to use the later X3D protocol, they look pretty similar and operate in the 868MHz band as well. I already tried to set the thermostat units into some test and scan mode but it still didn't show anything in the log, unfortunately.

I'll try to figure out some more details but it seems that Delta Dore removed much of the older product information.

[cyfm]

I think I give up on the 868MHz X2D/X3D stuff for now. I got a 433MHz rflink instead which at least works nicely with my Oregon Scientific temp/humidity sensors and my motor controlled roller shutters instead.
The Delta Dore modules probably use a different modulation or slightly off frequency which the Aurel 868.3MHz OOK? transceiver on my 868MHz rflink is unable to deal with.

BTW - it might be a matter of modulation of the signal in the end. I noticed that I also have a Ritto doorbell that operates on the 868MHz band but uses FSK aka Frequency Shift Keying modulation. As far as I remember, the 868MHz Aurel transceiver I ordered from nodoshop mentioned OOK aka OnOffKeying modulation. Is it likely that the receiver is unable to "sample" the signal then or does it only matter for sending signals ?

[cyfm]

I guess I'm trying to get hold of an Aurel FM/FSK 868MHz transceiver instead of the AM/OOK one and see if I can get anywhere with it.
It seems to be difficult to get those as a drop-in replacement for the AM/OOK one on the rflink as 5V version lately, though.

[Stuntteam]

That will not work...

[cyfm]

That will not work...

Mhh, ok, too bad, good to know, guess I will give up on tinkering with the 868Mhz rflink then.

[mr_sven]

Hi,

I was able to extend the RTL-SDR Project rtl_433 https://github.com/merbanan/rtl_433 with X3D decoding. I also has successful connection via a RFM69 (Semtech SX1231) module.
I have only a Thermostat and a Switch actor, so not much to decode.
Maybe someone has more payload of other actors or things? Like a Tydom, at the moment it is not clear how the Communication flow is. As far as I know the Tydom and Thermostat are communicating with the actor the but not between Tydom and Thermostat.

Regards Sven

[cyfm]

Oh, that indeed sounds interesting.

I also bought additional X3D window sensors for my thermostat/heater combos which are assigned via the heater.
I probably could get hold of some RTL-SDR compatible h/w to help with that project. I just need to figure out what I need to be compatible with the 868MHz range that the DeltaDore X3D modules use.

[mr_sven]

My PR#1911 is waiting for approval but you can checkout my branch.
Everything I know at the moment I've documented in the source file https://github.com/mr-sven/rtl_433/blob ... dore_x3d.c.
You only have to tune to the frequecy:

Code: Select all

./rtl_433 -f 868.95M

I'm using a Nooelec NESDR SMArt with a Wifi antenna for scanning.

It would be nice to get logs from pairing and open/close messages.