RFXCom Support

RXFCOM is the name for a Dutch company selling hardware that make it possible to connect many different sensors and actors. The name is also used to indicate an RFXCom interface set up using one of these interface products in Domotiga.

Currently supported RFXCOM hardware includes the RFXtrx433(E) USB transceiver, USB+LAN Receivers 433 and 868Mhz, RFXLan with xPL or native RFXLan firmware.


If you still have a Windows machine around, it is a good idea to first check the interface using the RFXmngr.exe application which is supported by RFXCOM.

Although RFXflash.exe (for flashing newer firmware) can be started using mono on Linux (see RFXflash-under-Linux), RFXMngr.exe (for checking incoming packets, and test RF transmits) doesn't run under Linux, you need a Windows system to use it, but you can also use DomotiGa's builtin RFXCommander to do most tasks.


  1. Check that the device is installed and recognized, the latest version of the RFXcom Transceiver connects to the USB port
    $ ls -l /dev/ttyUSB*
    crw-rw-rw- 1 root dialout 188, 0 Apr 24 20:07 /dev/ttyUSB0
  2. You need to make sure the user you're running DomotiGa as is a member of the dialout group:
    $ sudo useradd -G dialout domotiga
  1. Open DomotiGa and select under Interfaces "RFXCom"
  2. Choose Receiver/Transmitter/Transceiver RFXTrx/XPL based on the hardware and the way the hardware is connected, see below which Plugin is for which hardware.
  3. Enable and configure the Setup in the RFXCom Setting window:

With newer versions of DomotiGa it is possible to select the USB port also by-id:

This is in general a better choice as /dev/tty* assignments can change over time.

If things do not work, see the Debug section below.

RFXCom Commander

To experiment with RFXCom you can use the RFXCom commander you can find under the Tool menu:

Supported hardware

[Transceiver RFXtrx] RFXtrx433 USB transceiver or RFXrec433 receiver

RFXCom web site

Support for RFXtrx Tranceiver was added in version 0.1.204.

Supported Devices

The following list are the supported devices by RFXCom RFXtrx433, depending on the type it can transmit and/or receive.

Device Name Transmit Receive
Alecto WS1200 Yes
A-OK Roller Blind Motor Yes
ATI Remote Wonder* Yes Yes
ATI Remote Wonder II* Yes Yes
ATI Remote Wonder Plus* Yes Yes
Atlantic Yes Yes
Blyss (Lighting) Yes Yes
Brennenstuhl Yes
ByeByeStandby Yes Yes
Byron SX Chime Yes Yes
Cent-a-meter, Electrisave Yes
Chanon Yes Yes
COCO Yes Yes
Cresta Weather Sensors – TX2, TX3, TX4, TX7, TX17, WS2300 Yes
DI.O Yes Yes
Digimax Yes
Digimax – RTS10, RFS10, TLX1206* Yes
DomiaLite Yes Yes
Düwi Yes Yes
Ebode – XDOM Yes Yes
ELRO AB400 Yes
ELRO AB600 Yes Yes
Ematronic Roller Blind Motor Yes
Energenie ENER010 Yes
Harrison Curtain Yes
Hasta Motor Yes
Hideki, TFA Weather Sensors Yes
HomeEasy Yes Yes
HomeEasy EU Yes Yes
Ikea Koppla* Yes
Impuls Yes
Intertechno Yes Yes
KD101 (Avidsen, Chanon, NEXA, Flamingo, Blyss, Proove)* Yes Yes
KlikAanKlikUit Yes Yes
La Cross Weather Sensors Yes
Lexibook – SM883 Yes
LightwaveRF, Siemens (Lighting & Power) Yes Yes
Media Mount Projection Screen Yes
Meiantech Yes Yes
Mertik Maxitrol – G6R-H4T1, G6R-H4TB* Yes Yes
NEXA Yes Yes
Next Design IW008T Yes
Oregon Scientific Weather Sensors (all 1.0, 2.1 & 3.0) – AW129, AW131, BTHR918, BTHR918N, BTHR968, PCR800, RGR126, RGR682, RGR918, RTGR328N, RTGR328N, STR918, THC138, THC238, THC268, THGN122N, THGN123N, THGN500, THGR122NX, THGR228N, THGR238, THGR268, THGR328N, THGR810, THGR918, THGRN228NX, THN122N/132N, THR128, THR138, THRN122N, THWR288A, UV138, UVN128, UVN800, WGR800, WGR918, WTGR800, WTGR800 Yes
Oregon Scientific – BWR101, BWR102, GR101 Yes
OWL – CM113, CM119, CM160, CM180, Intuition CM180i Yes
PC Remote* Yes Yes
Phenix Yes
Philips SBCSP370, SBCSP375 Yes
Proove Yes Yes
PT2262 Receivers Yes
Raex Roller Blind Motor Yes
RFXMeter Yes
RFXSensor Yes
Rising Sun Yes
RollerTrol Blinds Yes
RUBiCSON – 48659, 48695 Yes
Sartano Yes
Techno line TX95-TH Yes
UPM/Esic Clas Ohlson (very short receive range) Yes
Viking, FineOffset – 02035, 02038, 02811 Yes
Waveman Yes
X10 Lighting Yes Yes
X10 Security* Yes Yes
X10 Ninja/Robocam* Yes
X10 Remotes Yes

*Transmitting of these protocols not yet supported in 0.1.204 but will be added later, request if needed.

[Receiver] for 433Mhz receiver USB, LAN or WLAN interface, or RFXLan with RFXLan firmware.

Configure the IP address or USB port of your interface.
Port number for tcp is 10001 for RFXLan receiver.

  • X10 motion sensors and remotes
RF X10 Type
MS13 Motion Sensor
Many Others
  • X10 security sensors
RF X10Security Type
Marmitek DS90 Door/Window Sensor
Many Others
  • Digimax
  • !KlikOn-!KlikOff (wall switches and remotes)
  • NEXA
  • Proove
  • Domia Lite
  • !ByeByeStandBye
  • ELRO AB600
  • RFXSensor devices
  • RFXPower & RFXMeter devices
RFXMeter with RFXPwr
RFXMeter with RFXPulse (Gas/Water)
RFXSensor* Temp
RFXSensor* Temp/Humid
  • RFXSensor support is limited to 1 sensor.
  • Oregon Scientific weather sensors (selected sensors, not all)
Sensor Values
Oregon THR128 Inside Temp
Oregon THR138 Inside Temp
Oregon THC138 Inside Temp
Oregon THC238 Outside/Water Temp
Oregon THN132N Outside/Water Temp
Oregon THWR288A Outside/Water Temp
Oregon THRN122N Outside/Water Temp
Oregon THN122N Outside/Water Temp
Oregon AW129 Outside/Water Temp
Oregon AW131 Outside/Water Temp
Oregon THWR800 Water Temp
Oregon THGN122N Inside Temp-Hygro
Oregon THGN123N Inside Temp-Hygro
Oregon THGR122NX Inside Temp-Hygro
Oregon THGR228N Inside Temp-Hygro
Oregon THGR238 Inside Temp-Hygro
Oregon THGR268 Inside Temp-Hygro
Oregon THGR810 Inside Temp-Hygro
Oregon RTGR328N Outside Temp-Hygro
Oregon THGR328N Outside Temp-Hygro
Oregon WTGR800 Outside Temp-Hygro
Oregon THGR918 Outside Temp-Hygro
Oregon THGRN228NX Outside Temp-Hygro
Huger BTHR918 Inside Temp-Hygro-Baro
Oregon BTHR918N Inside Temp-Hygro-Baro
Oregon BTHR968 Inside Temp-Hygro-Baro
Oregon RGR126 Rain Gauge
Oregon RGR682 Rain Gauge
Oregon RGR918 Rain Gauge
Oregon PCR800 Rain Gauge
Oregon WTGR800 Anemometer
Oregon WGR800 Anemometer
Huger STR918 Anemometer
Oregon WGR918 Anemometer
Oregon UVN128 UV Sensor
Oregon UV138 UV Sensor
Oregon UVN800 UV Sensor
Oregon RTGR328N Date & Time
cent-a-meter Ampere Meter
OWL CM113 Ampere Meter
Electrisave Ampere Meter
OWL CM119 Power Meter
Oregon BWR102 Body Weight Monitor
Oregon GR101 Body Weight Monitor

Startup Log Entries:

2008/11/11 22:56:29  RFXComRX TCP/Serial interface enabled.
2008/11/11 22:56:29  RFXComRX serial interface connected to Port /dev/ttyUSB3

[Transmitter] for 433Mhz transmitter or xmitter USB, LAN or WLAN interface, or RFXLan with RFXLan firmware.

Configure the IP address or USB port of your interface.
Port number for tcp is 10001 for RFXLan receiver.
Enable xmitter of that's the transmitter type used.
Handshake is used if you use 2 USB devices, one receive, and the other transmit, with a handshake cable connected.

RFXCom Protocol Overview


Protocols to be enabled
Enable only the protocols necessary to be received!
Too many protocols enabled make the receiver less sensitive.

Protocols to be enabled for:
X10 X10, RFX
TLX1206 X10, RFX
RFXPower X10, RFX
RFXMeter X10, RFX
RFXSensor X10, RFX
KlikAanKlikUit with address wheels ARC
DomiaLite ARC
NEXA with address wheels ARC
Proove ARC
Intertechno ARC
Düwi ARC
Oregon Scientific OS
Electrisave OS
Cent-a-meter OS
KlikAanKlikUit with program button AC
HomeEasy UK with program button AC
ANSLUT with program button AC
NEXA with program button AC
Chacon with program button AC
HomeEasy Heater AC
HomeEasy EU HEU
ATI Remote Wonder (Plus) ATI
RF Remote ATI
Medion Remote

[Transmitter] for 433Mhz transmitter USB, LAN or WLAN interface, or RFXLan with RFXLan firmware.

Protocols to be enabled
These selections are only used for the standard transmitter!
The RFXmitter has all protocols enabled by default. This RFXmitter is using a different technique so that it operates faster than the standard transmitter.

Enable only the protocols necessary to control your RF modules in the standard transmitter!
Too many protocols enabled will reduce the transmitter speed and also create too much RF traffic.

Protocols to be enabled in the standard transmitter for:
X10 X10, RFX
RTS10 X10, RFX
KlikAanKlikUit with address wheels ARC
DomiaLite ARC
NEXA with address wheels ARC
Proove ARC
Intertechno ARC
Düwi ARC
Harrison curtain Harrison
Default enabled:
KlikAanKlikUit with program button AC
HomeEasy UK with program button AC
ANSLUT with program button AC
NEXA with program button AC
Chacon with program button AC
HomeEasy Heater AC


This transmitter supports these protocols:
X10 (lighting, security, Robocam/Ninja), ARC, Waveman, Harrison, IKEA Koppla, AC, HomeEasy EU and Flamingo. Individual protocol have not to be selected. If you experience problems with some units you can increase the number of transmitted RF packets. The number of repeated RF packets can be configured for each protocol individually using the RFXmitter program. This setting is saved in the transmitter. You can also test to decrease the number of transmitted packets. But remember: range problems cannot be solved by increasing the number of transmitted RF packets.

Handshake connected

The 2 port RFXCOM Ethernet interfaces have the handshake connection inside the box. For the 1 port RFXCOM Ethernet interface and the USB interface an external handshake cable is necessary. See the Handshake installation.pdf for details how to install this cable connection.
This handshake function will only function correctly with a Master receiver connected having the same frequency as the transmitter. Normally 433.92MHz.
The function of this handshake is:
The transmitter is only allowed to transmit if the receiver does not receive data. This avoids RF collisions as much as possible.
The receiver stops receiving during the time the transmitter is active. So data transmitted is not received back and endless loops are eliminated.

[xPL] for receiver and/or transmitter using RFXLan with xPL firmware

Configure the xPL address of your interface, if it's not correct you will see the correct one displayed in the xPL debug output.


The RFXtrx433E version is an RFXtrx433 with additional hardware to enable the RFY protocol used to control Somfy RTS1 and with this you can control your Somfy blinds etc.


To pair a Somfy RTS device using the RFXmngr program under Windows see chapter 12 of the RFXtrx User Guide; to do it using DomotiGa under Linux:
  • Open the DomotiGa RFXCom Commander
  • Select the Somfy RTS / RTY tab
  • Set an unique Device / Unit address using the four pull-down boxes after Device
  • Take the original Somfy remote control and, if it controls multiple devices, select the device you want to control
  • Find the program button on the remote control and press it until the Somfy device "jogs":
  • Now press the Program button in the Somfy RTS / RTY tab. The Somfy device should "jog" indicating the pair command was successful.

Adding a device

If you want to control the RTS devices using an event/action, add a device with:
  • Protocol = RFY
  • DeviceType = Somfy Blind
  • Interface = RFXCom Transceiver

The address should be the address you programmed using the RFXmngr program or using the procedure above.

Also enable either "Device can be switched" or "Device can be dimmed or has a setpoint" in the Device Options tab otherwise value with be only written to the database and not send to the Somfy RTS device.

Adding an action

Once you have added a DomotiGa device representing the Somfy RTS device you can add a Set device value action.
Select the device you added, Value1.

Relevant values for the To Value you can use are:
  • STOP
  • UP
  • DOWN
  • ENSUNFLAG - Enable sun+wind detector
  • DISSUNFLAG - Disable sun detector


Some tips:
  • Enable the RFXCom and Device debug and have a look at the (server) debug log.
  • If you can control things using the RFXCom Commander but not using an action:
    • Check the address and the if the device is set to be switchable or dimmable, see above.
    • Compare the log for the RFXCom Commander and the action
  • With the Remotes you can get a list of known/programmed remotes in the RFXCom unit
    • The list is written to the (server) debug log

[1] Somfy RTS are registered trademarks of Somfy System, Inc.


If things do not work, enable Debug in the RFXCom settings window (Interface -> RFXCom -> [Chose interface]):

(Re)start things and study the Debug messages:
  • Press the Logfiles icon in the Main menu bar on the left and then the Debug button
  • Open the either the debug-<year>-<month>.log file or server-debug-<year>-<month>.log file you can find in ~/domotiga/logs/ in an editor

If you see in the logs something like:

13:44:17 [RFXComTRX] ERROR: Unknown Packet type: 05
13:44:27 [RFXComTRX] Error reading data from the serial port! -> End of file (Count: 1)

It is likely you selected the USB port belonging to another device.

If you still have a Windows machine around, it is a good idea to check the interface using the RFXmgnr.exe application which you can download from the RFXCOM website. Be sure to read also the User Guide that can be downloaded from the Downloads page

RFXflash under Linux

For RFXtrx

$ wget
$ unzip
$ sudo apt-get install mono-runtime libmono-microsoft-visualbasic8.0-cil
$ mono ./RFXflash.exe

For RFXLan

If you need to flash a RFXLan interface (for xPL firmware for example) you need to perform this extra step (it uses another serial driver)

Press the reset button, and hold it, then apply power to the interface and wait 5 seconds.
After that the Linux kernel should have seen the device:

$ dmesg | grep ttyACM
[ 2224.292385] cdc_acm 1-1.6:1.0: ttyACM0: USB ACM device

Now create a symbolic link so you can enter it in RFXflash

$ sudo rm /dev/ttyS4
$ sudo ln -s /dev/serial/by-id/usb-RFXCOM_CDC_RS-232_RFXLAN-if00 /dev/ttyS4

Then enter /dev/ttyS4 in RFXflash and load firmware to flash.

Visit your rfxlan's web page to check version and firmware type.

Surf to http://rfxlan

RFXMngr.exe does not run under Linux/mono, see RFXmngr under mono: menu partly greyed out

Related Resources

  • Added by johanvandyck almost 4 years ago


    I succesfully programmed a cheap creasol remote control (, but it wasn't easy. Some tips:
    - watch the video delivered on the creasol website. Notice the "old remote" is held AGAINST the creasol device. --> hold the creasol device pressed against the rfxcom antenna.
    - The antenna could be alined with the creasol device buttons but also 90°. In my case I had more success when the antenna was 90° between button 1 and 2.
    - Spam the creasol device with commands. I used the windows rfcxom manager to do so.
    - It took about 20 retries before I get success to program one button: keep trying!
    - although the binary code changes every sequence, the creasol device reacts with two red pings for a "fixed code" device if programming went well.
    example: code 08 20 08 / 07 / 02 14 08 / 0D /00
    -- 080208: kind of preamble
    -- 07 + 00: rolling code changing with every sequence. Counting up.
    -- 02 14 08: adress I choose as identifier. Is will be the meiantech device adress in your device on DomotiGa
    -- 0D: encoding for "disarm" command
    - currently only the "disarm" command is recognised in DomotiGa. Other commands are "not received". See also the forum:
    - After programming, the device is not very reactive. I need to press about 5s a button before RfxCom reacts. Definitivly not "one push".

    note: I use rfxcom firmware 247, DomotiGa 1.0.21 on cubieboard.

    Kind regards


  • Added by johanvandyck almost 4 years ago

    RFXCom - use of Byron SX 6 or 7


    I succesfully added a Byron SX7 chime to DomotiGa.
    It seems trivial, but it isn't.

    Receive ByronSX in DomotiGa:
    - Pair the push button to the Byron. See manual. In my case ID 00B8 is used; sound is set to Big Ben.
    - connect RFXCom to windows RFXCommander.exe, enable the Byron protocol, save settings.
    - push button. You should receive

    Packettype    = Chime
    subtype       = Byron SX
    Sequence nbr  = 34
    ID            = 00B8
    Sound         = Big Ben
    Signal level  = 7

    Note the ID: "B8"

    - reconnect RFXCom to Domotiga. Open menu, interface RFXTRX and enable checkbox "debug".
    - enable auto device create (menu Setup > Main, check checkbox "auto device create"
    - push the button. Debug log shows:

    2015/09/03 20:12:32 [RFXComTRX] < 0716000000B80370
    2015/09/03 20:12:32 [RFXComTRX] Packettype    = Chime
    2015/09/03 20:12:32 [RFXComTRX] Subtype       = Byron SX
    2015/09/03 20:12:32 [RFXComTRX] Sequence no.  = 0
    2015/09/03 20:12:32 [RFXComTRX] ID            = 00B8
    2015/09/03 20:12:32 [RFXComTRX] Sound         = Big Ben
    2015/09/03 20:12:32 [RFXComTRX] Signal level  = 7
    2015/09/03 20:12:32 [Devices] Device with type 'ByronSX', address '00B8', instance 1' and interface 'RFXCom Transceiver' not found!
    2015/09/03 20:12:32 [Devices] Auto created device 'ByronSX device #1' with address '00B8' of type 'Byron SX Doorbell' with interface 'RFXCom Transceiver' and instance '1'
    2015/09/03 20:12:32 [Devices] ValueUpdate called for device with id '60' valuenum '1' and value 'Big Ben'
    2015/09/03 20:12:32 [Devices] Device change triggered for device 'ByronSX device #1' with 'value1' = 'Big Ben'

    - Device ID 60 is created with address 00B8. The first value contains the sound name. In my case "Big Ben" (receiving) or "BIGBEN" (transmitting).

    Transmit ByronSX in DomotiGa
    - When the button is pushed, the value1 is overwritten with the sound. In order to use this value to trigger other actions, create an event "Test ByronSX"
    - Create Trigger of type Cron "59 18 * * 1,4,7" (every day, at 18h59 on monday, thursday and sunday)
    - Create an action to set value1 of device 60 to "BIGBEN"

    Note: on DomotiGa 1.0.21 the chime implementation is buggy. See and
    - to solve this, you need to change and recompile. Don't be afraid, it is not difficult.
    - Edit ~/domotiga/DomotiGa3/.src/Tools/FToolsRFXComCmdr.class, and replace line 1406:

    cData["address"] = Format(cmbChimeUnit.Text, "00")
    cData["address"] = cmbChimeUnit.Text

    - Edit:
    If you are running DomotiGa then edit ./Domotiga/Domotiga3/.src/CRFXComTRX.class
    If you are running DomotiGaServer then edit ./Domotiga/DomotigaServer3/.src/CRFXComTRX.class around line 5336:

     If (Len(sAddress) <> 2) Then
        Main.WriteDebugLog(LogLabel & "Not a valid Chime address: " & sAddress)
        sAddress = right$(sAddress,2)
        Main.WriteDebugLog(LogLabel & "corrected Chime address: " & sAddress)

    - Recompile
    cd ~/domotiga

    - restart server

    create device with on/off value.
    - When the button is pushed, the value1 is overwritten with the sound. In order to use this value to trigger other actions, create an event "Someone on the door"
    - Create a virtual device "vBel"
    - Create a trigger "Chime" of type "multi-trigger" with 2 triggers in th details: "dev_60_lastchanged" and "dev_60_lastseen"
    - Create an action to set 1) value1 of vBel 2)wait 5 seconds 3) set value1 of vBel to off.

    Kind regards


Updated by: rdnzl, Updated over 4 years ago
Access count: 119275 since 2011-08-25

Also available in: PDF HTML TXT