19. Revision history ............................................................................................................. 36
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 2 / 39
2. RFXtrx general information
The RFXtrx transceivers and RFXrec receivers are communicating over an USB port with the
Home Automation application. The RFXtrx/rec is powered by the USB port.
At startup the RFXtrx enters for 2 seconds the boot loader (red LED is on) and after this it starts
the receive/transmit firmware. If valid (decode-able) packets are received the yellow LED will
blink.
The RFXtrx315 and the RFXrec433 are mainly for use in the US. The RFXtrx315 can receive
US X10 lighting and security sensors or US Visonic PowerCode sensors at 315MHz.
The RFXrec433 can receive weather sensors of different brands at 433.92MHz.
The RFXtrx433 is a transceiver (transmitter+receiver) and can receive and control a large
number of sensors and other devices.
The RFXtrx433E is an extended RFXtrx433 transceiver.
Note: the listed protocols and brands are supported!
- Y cent-a-meter Y Y Y Oregon Chacon (learning mode)
- http://www.chacon.be/
Y Y Y AC Y
Chacon (with address code wheels) Y Y Y ARC Y
Chacon EMW200 Y Y Y
Chacon 54660 (equal CoCo GDR2) Y Y Y
Chacon KD101 smoke detector Y Y Y always on Y
Chamberlain CS4330CN
- TS15C, TS34C,external temperature sensor 30.3133, anemometer
30.3149, UV sensor, rain sensor 30.3148, pool sensor 30.3160
UPM/Esic (very short receiving range)
- WT260,WT260H,WT440H,WT450,WT450H,WDS500,RG700
Viking
- 02035, 02038, 02811
Visonic CodeSecure Y Y Y
Y Y Y Hideki Y - - Hideki -
Y Y Y FineOffset -
(not received)
Visonic PowerCode Y Y Y Visonic Y
Waveman Y Y Y
WT0122 pool sensor
YOODA blind motors
- http://www.sukcesgroup.pl
- - Y FineOffset -
Y Y -
(not received)
(not received)
Y
Y
X10 Ninja/Robocam - Y - X10 Y
X10 PC Remote Y - Y X10 Y
X10 RTS10 / RFS10 Y Y Y X10 Y
X10 lighting Y Y Y X10 Y
X10 security Y Y Y X10 Y
Xdom Y Y Y X10 Y
Xiron
– EN6
Y - Y Rubicson -
2.3. undec on
This parameter is for internal use by RFXCOM!!!
If new sensor types are released they will most probably not be decoded by the RFXtrx
firmware. For this reason we have added the option to enable receive of undecoded messages.
This function is only to enable RFXCOM to add this new sensor type in the firmware if possible.
If “undec on” is enabled in normal use the application will receive a lot of undecoded messages
mostly as a result of RF noise or disturbed RF packets.
Important: For normal use “undec on” should be disabled
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 10 / 39
2.4. Sensitivity influenced by enabled protocols
The sensitivity of the receiver part is highly influenced by the number of protocols enabled.
Lesser protocols enabled will make the receiver more sensitive for the enabled protocols.
There are a few protocols that will reduce or even eliminate receiving of other protocols if
enabled.
For example:
If the AD (LightwaveRF, Siemens) protocol is enabled it can stop receiving of Meiantech /
Atlantic, Oregon 3.0,Visonic and Mertik.
All other protocols are disabled if BlindsT0 is enabled.
ARC is disabled if Lighting4 is enabled.
X10
ARC
AC
HomeEasy EU
Meiantech/Atlantic
Oregon
ATI
Visonic
Mertik
AD (LWRF)
Hideki/UPM
La Crosse
FS20
ProGuard
BlindsT0
BlindsT1/T2/T3
AE (Blyss)
Rubicson
FineOffset/Viking
Lighting4
RSL
Byron SX
Imagintronix
Green = enabled by default
/ OWL
(LWRF)
/T4
/Alecto
SL/Revolt
/Opus
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 11 / 39
2.5. RF range reduction
The RF signals operating distance is reduced when the signal has to pass through walls.
2.6. Home Automation software
For the list of Home Automation software that supports the RFXtrx see the web site
www.rfxcom.com
2.7. Dimensions
The dimensions of the RFXtrx/RFXrec are: 83.5 x 42 x 15 mm
Total height from bottom to antenna top is 122mm
The dimensions of the RFXtrx433E are: 83 x 59 x 22 mm
Total height from bottom to antenna top is 130mm
2.8. Electrical
The RFXtrx is powered by the 5 Volt of the USB interface.
Operating current;
Receive mode: 28 mA (0.14Watt)
Transmit mode: 45 mA
The RFXtrx Radiated RF power is 10dBm max.
2.9. Environmental conditions
Normal operating: 15°C to 35°C
Absolute min-max temperature: -10°C to 55°C
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 12 / 39
3. Install the USB driver
The RFXtrx has the FTDI FT232R USB interface chip installed.
The USB drivers are available at http://www.ftdichip.com/Drivers/VCP.htm
4. Run RFXflash on Linux under Mono
Open a Terminal screen in Linux (Ctrl-Alt-T)
Execute once:
Install Mono:
[sudo] apt-get install mono-runtime
Install VisualBasic support under Mono:
[sudo] apt-get install libmono-microsoft-visualbasic8.0-cil
If the USB device is created as ttyACMx you will need to create a link between
/dev/ttyACMx and a serial port /dev/ttySx.
This is not necessary if the device is created as /dev/ttyUSBx !!
[sudo] ln -sf /dev/ttyACM1 /dev/ttyS3
Note: sudo must be entered without brackets [ ]. sudo is required if not running as super user.
Launch the RFXflash.exe program.
[sudo] mono RFXflash.exe
Note: RFXmngr does not operate under mono!
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 13 / 39
5. RFXmngr test program
The RFXmngr program supports decoding of received data and allows you to transmit
commands.
After the connection the RFXmngr program transmits a Reset and Get Status command so that
it will know the RFXtrx type and configuration settings:
Transmitter protocols are always enabled but receiver protocols can be disabled. This is very
useful because the receiver will become more sensitive when protocols not used are disabled.
So select only the protocols to be used, click Set mode and click Save Settings.
Note that these settings are lost after a firmware update and need to be set again.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 14 / 39
5.1. Receiver
The RF protocols to be received can be configured on the Main tab at Set Mode.
Click Save Settings to save the selected protocols in non-volatile memory of the RFXtrx. This
configuration is now restored every time after a power up.
Note that these settings are lost after a firmware update and need to be set again.
Note: Protocol enabling is only necessary for receive. Transmit protocols are always enabled.
The received RF data is decoded and displayed in the yellow window.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 15 / 39
5.2. Transmitter
The tabs after the Main tab are used to send commands to the transmitter.
For example Lighting1 is used to send X10, ARC and some more.
Note: Protocol enabling is only necessary for receive. Transmit protocols are always enabled.
Select Type to see which protocols are supported on the different tabs.
The transmitted commands are displayed in the yellow window including the acknowledge send
by the RFXtrx, in the example above “ACK, data correct transmitted“.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 16 / 39
6. Flash update of the RFXtrx
6.1. Update firmware in the RFXtrx
Firmware is flashed in the RFXtrx using this procedure:
1. Depending on the RFXtrx type download the latest RFXtrx315_yy.hex,
RFXrec433_yy.hex or RFXtrx433_yy.hex firmware file.
2. Connect the RFXtrx to a Windows system or Linux under MONO
3. Stop any program that is connected to the RFXtrx.
4. Start the RFXflash program (version 4.0.0.0 or higher)
5. Select the USB RFXtrx COM port and click the CONNECT button,
(the red LED should switch on now)
6. Load the correct .hex firmware file for your RFXtrx,
7. Click the WRITE button,
8. Click the Normal Execution mode button.
IMPORTANT:
1. Do not interrupt the flash procedure when started.
2. It can happen that the flash procedure ends with a pop-up screen indicating errors.
Just disconnect the RFXtrx and start again at step 5 until the flash procedure if finished
without errors.
If the red LED does not switch on if you click the CONNECT button:
1. Check if you have selected the correct USB COM port.
2. If you have flashed the RFXtrx before and interrupted the flash procedure it is possible
that the RFXtrx does not enter the flash state. Contact support@rfxcom.com for help.
Note: Receiver Settings are lost after a firmware update and have to be set again.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 17 / 39
6.2. Update firmware in the RFXtrx step by step
•Click the Connect to Device button.
The RFXtrx will automatically switch from normal mode to the bootloader now.
•Click the Open HEX file button and load the RFXtrxyyy_xx.hex file
Be sure to load the latest firmware file for the RFXtrx.
yyy indicates the RFXtrx frequency, so load the RFXtrx433 for an RFXtrx433!
xx indicates the firmware version.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 18 / 39
• Click the Write device button and the RFXtrx is flashed.
• Click on the Normal Execution Mode button to set the RFXtrx to running mode.
Note: Receiver Settings are lost after a firmware update and have to be set again.
7.2. Harrison address conversion to switch settings
The address used is converted to the address selected in the Harrison curtain motor using the
table below.
switch 1 2 3 4 5 6 7 8
H H H H X X X X
A 0 1 1 0 1 0 0 0 0
B 0 1 1 1 2 0 0 0 1
C 0 1 0 0 3 0 0 1 0
D 0 1 0 1 4 0 0 1 1
E 1 0 0 0 5 0 1 0 0
F 1 0 0 1 6 0 1 0 1
G 1 0 1 0 7 0 1 1 0
H 1 0 1 1 8 0 1 1 1
I 1 1 1 0 9 1 0 0 0
J 1 1 1 1 10 1 0 0 1
K 1 1 0 0 11 1 0 1 0
L 1 1 0 1 12 1 0 1 1
M 0 0 0 0 13 1 1 0 0
N 0 0 0 1 14 1 1 0 1
O 0 0 1 0 15 1 1 1 0
P 0 0 1 1 16 1 1 1 1
H H H H = House code
X X X X = device code
Switch position in the motor:
Up = 1
Middle = not used!!!!
Down = 0
Examples:
If you assign the address E7 (1000 0110) to the curtain motor then set the switches to: 1=up,
2=down, 3=down, 4=down, 5=down, 6=up, 7=up, 8=down
If you assign the address A2 (0110 0001) to the curtain motor then set the switches to: 1=down,
2=up, 3=up, 4=down, 5=down, 6=down, 7=down, 8=up
Use type ELRO AB400D
Note that the HC (House Code A-P) is the house code used in programs and has no direct relation
with the A,B,C,D,E buttons on the remotes!
1 2 3 4 <== switches
HC==========
A 0 0 0 0
B 0 0 0 1
C 0 0 1 0
D 0 0 1 1
E 0 1 0 0
F 0 1 0 1
G 0 1 1 0
H 0 1 1 1
I 1 0 0 0
J 1 0 0 1
K 1 0 1 0
L 1 0 1 1
M 1 1 0 0
N 1 1 0 1
O 1 1 1 0
P 1 1 1 1
To know the codes to use open the remote and check the 1 to 5 jumpers connected.
If a jumper connection is open it is a 1. If connected it is a 0 (zero)
1 2 3 4 jumper setting in the remote
HC=========
A 0 0 0 0
B 0 0 0 1
C 0 0 1 0
D 0 0 1 1
E 0 1 0 0
F 0 1 0 1
G 0 1 1 0
H 0 1 1 1
I 1 0 0 0
J 1 0 0 1
K 1 0 1 0
L 1 0 1 1
M 1 1 0 0
N 1 1 0 1
O 1 1 1 0
P 1 1 1 1
If jumper 5 is open (1) than add 5 to the remote code.
Use type ELRO AB400D
Note that the HC (House Code A-P) is the house code used in programs and has no direct relation
with the A,B,C,D,E buttons on the remotes!
HC switch
1 2 3 4
============
A 0 0 0 0
B 0 0 0 1
C 0 0 1 0
D 0 0 1 1
E 0 1 0 0
F 0 1 0 1
G 0 1 1 0
H 0 1 1 1
I 1 0 0 0
J 1 0 0 1
K 1 0 1 0
L 1 0 1 1
M 1 1 0 0
N 1 1 0 1
O 1 1 1 0
P 1 1 1 1
The RFXtrx433 can only transmit MDREMOTE commands.
Procedure to find the ID of the MDREMOTE:
In RFXmngr enable the X10 protocol and enable “Undec on”
Press a button on the MDREMOTE remote.
The undecoded message contains the ID in the 2nd and 3rd byte, for example:
The 2 bytes after 20 is the MDREMOTE ID, in this example AF 68
7.8. Aoke relay
The Aoke 12V DC - 315MHz or 433.92MHz 1 channel relay is available at www.aliexpress.com
store No.110758. Indicate clearly the required frequency when ordering!
The 1 channel learning relays can be used, see the picture below.
For example, for 1 relay:
The jumper next to the learning button defines to operating mode:
Open = momentary
1-2 = toggle mode
2-3 = on/off mode (to be used with the RFXtrx)
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 29 / 39
8. Blyss commands
Some Blyss devices, like the Blyss motors, require a special command sequence number. To
simplify it; 0,1,2,3,4,0,1,…
This sequence number is normally created by the Blyss remote but now also by the RFXtrx433.
If you use a Blyss remote and the application (Domoticz, DomotiGa, Homeseer…) does not sync
with the received Blyss command you will see that you need to send multiple commands with the
RFXtrx433 before the Blyss device will respond.
For example,
The Blyss remote transmits with the sequence numbers 0,1,2
If the RFXtrx433 transmits now with sequence number 0 it will not be seen by the Blyss device as
a valid command and at the time the RFXtrx433 transmits the commands 1,2,3 the command will
be detected as valid when it receives the command with sequence number 3.
The same is true for the remote. If you transmit commands with the RFXtrx433 and after that with
a Blyss remote you need to transmit several commands with the remote before the Blyss device
responds.
I guess the same behaviour will show if you use multiple Blyss remotes.
9. How to find the dx.com RGB LED strip driver ID
Valid for the TRC02 remote with 2 batteries.
Flash the RFXtrx433 with Type2 firmware to be able to receive the remote ID in RFXmngr.
In RFXmngr enable only the LightwaveRF (AD) protocol.
You can assign a random ID to the Eurodomest. If you want to use the same ID as the remote you
can find the ID of the remote using RFXmngr.
Start RFXmngr and enable only the Lighting4 protocol.
Press a button on the remote and you will receive a message like:
Somfy RTS* devices can only be controlled by the RFXtrx433E. (not with the RFXtrx433)
The RFXtrx433E version is an RFXtrx433 with additional hardware to enable the RFY protocol
used to control Somfy RTS.
To pair the Somfy RTS device:
• Select a unique ID and unitcode for the RFXCOM RFY device.
• Disconnect power from all Somfy RTS devices except the device to pair.
• Press the Program button > 2 seconds on the original Somfy remote until the Somfy device
responds.
• Transmit a Program command with the RFXtrx433E. The Somfy RTS device should respond
indicating the pair command was successful.
The RFXCOM RFY remote is registered in the RFXtrx433E by sending a Program command.
Up to 30 RFXCOM RFY remotes can be registered in the RFXtrx433E.
Remotes can be erased from the RFXtrx433E using the RFXmngr program.
The Somfy RTS device can be controlled by any application as long as the same ID and Unit
Code are used.
For example if the RTS device is paired using RFXmngr with ID=1 02 03 and Unit Code 1, the
RTS device can be controlled with Homeseer using the same ID and unit code.
* Somfy RTS are registered trademarks of Somfy System, Inc.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 31 / 39
13. Transmit undecoded ARC commands.
Plug-in modules or other equipment with a PT2262 can be controlled using Lighting4.
There are a lot of brands using the PT2262 and some of them use the same timing (350) as used
by the ARC devices but a different protocol definition.
Messages will be received as undecoded ARC messages if the protocol definition does not match
the definition of the ARC protocol. Remote commands are received as ARC commands with a
wrong house and device code and/or command code or as undecoded ARC messages if “undec
on” is enabled. Decoding of these remotes is therefore not possible because they overlap the ARC
protocol partly.
But transmitting these commands is possible using the Lighting4 command.
So if we receive this command UNDECODED ARC:18014403:
(18 is not used)
And the Lighting4 command contains the same “undec code” 01 44 03:
Lighting4 command:09 13 00 04 01 44 03 01 5E 00
pulse timing is 350 = hex 015E
Another example:
For this command UNDECODED ARC:18014430 set on the Lighting4 tab in RFXmngr selection
box 1 to 24 to 0 1 4 4 3 0 = 0000 0001 0100 0100 0011 0000
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 32 / 39
14. Known Lighting4 devices
14.1. Proluxx projection screen
Use Lighting4 with a pulse timing of 360
UP 1110 1101 0101 1001 0101 0010 ED 5A 52
STOP 1110 1101 0101 1001 0101 1000 ED 5A 58
DOWN 1110 1101 0101 1001 0101 0100 ED 5A 54
RESET 1110 1101 0101 1001 0101 0001 ED 5A 51
EMC Directive 2004/108/EC EN 301 489-1 V1.9.2 (2011-09)
EN 301 489-3 V1.4.1 (2002-08)
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 34 / 39
16. Warning:
•RF signals are possible disturbed and it has not been justified for this equipment at uses in
circumstances where life-threatening or dangerous situations are possible.
•RFXCOM HARDWARE AND SOFTWARE IS NOT INTENDED FOR USE IN THE
OPERATION OF NUCLEAR FACILITIES, AIRCRAFT NAVIGATION OR COMMUNICATION
SYSTEMS, AIR TRAFFIC CONTROL SYSTEMS, LIFE SUPPORT MACHINES OR OTHER
EQUIPMENT IN WHICH THE FAILURE OF THE SOFTWARE COULD LEAD TO DEATH,
PERSONAL INJURY, OR SEVERE PHYSICAL OR ENVIRONMENTAL DAMAGE.
17. License
•You are allowed to use RFXCOM software, protocols and Written Materials with RFXCOM
hardware only.
•All copyright and other proprietary notices associated with RFXCOM software, protocols and
Written Materials shall be visible to all users.
•You may not sell, distribute, loan, rent, lease, license, sublicense or otherwise assign or
transfer RFXCOM software or RFXtrx protocols or Written Materials unless expressly
authorized in writing by RFXCOM.
•You may not use any RFXCOM device, software or protocol as part of an exclusive or
patented product without the express prior written permission of RFXCOM.
•You may not alter, modify, adapt or create derivative works based on any part of RFXCOM
software or protocols or Written Materials in any way, including translating, reverse
engineering, disassembling or decompiling the software.
18. Copyright notice
•All RFXCOM hardware, software, protocols and Written Materials are protected by copyright
laws, and may not be reproduced, republished, distributed, transmitted, displayed, broadcast
or otherwise exploited in any manner without the express prior written permission of RFXCOM.
•Netherlands Copyright and international treaty provisions protect the SOFTWARE,
HARDWARE, RFXtrx protocols and Written Materials and shall be subject to the exclusive
jurisdiction of the Netherlands Courts
•RFXCOM reserves all rights not expressly granted herein.
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 35 / 39
19. Revision history
Version 0.0 – August 18, 2011
Initial version.
Version 1.0 – October 30, 2011
RFXflash under Mono added.
Version 2.0 – December 30, 2011
Updated for the production version with FTDI USB chip
Version 2.1 – January 18, 2012
Link for ACM to serial port added in Linux instruction.
EC Declaration of Conformity added
Version 2.2 – February 8, 2012
Protocols overview added
Screen dumps updated
Version 2.3 – February 16, 2012
Novatys planned
Version 2.4 – February 25, 2012
General information updated
Version 2.5 – March 1, 2012
Chapter added how to run RFXmngr or RFXflash on Linux.
Version 2.6 – March 14, 2012
Code tables added
Cresta, UPM added
Version 2.7 – March 15, 2012
Flash procedure updated
Version 2.8 – March 31, 2012
Phenix table added
Version 2.9 – March 31, 2012
AB400 and Phenix address extended
Version 2.10 – April 16, 2012
Linux USB - tty configuration updated
Version 2.11 – May 14, 2012
List of supported protocols updated.
Version 2.12 – June 8, 2012
Chapter added how to run RFXmngr or RFXflash on Mac OS
Version 2.13 – July 15, 2012
List of supported protocols updated
Version 2.14 – August 4, 2012
List of enabled protocols influence added
RFXtrx315 added
Version 2.15 – August 18, 2012
Enabled protocols table changed
Version 2.16 – August 26, 2012
Rubicson stektermometer added
ATI Remote Wonder II added
Version 2.17 – August 28, 2012
Table “sensitivity influenced” updated
Version 2.18 – September 18, 2012
Chapter 2.3 updated: BlindsT0 disables all other protocols
Version 2.19 – September 25, 2012
RFXFlash version required changed to 4.0.0.0
Version 2.20 – September 28, 2012
RF range reduction guide added
Version 2.21 – October 18, 2012
BlindsT2 and BlindsT3 added
Version 2.22 – October 24, 2012
Sartano added
Version 2.23 – October 31, 2012
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 36 / 39
Sensitivity table updated
Version 2.24 – November 7, 2012
Protocol table extended with the protocols to enable for receive
Version 2.25 – November 14, 2012
HE105 switch settings added
Version 2.26 – November 28, 2012
undec on explained
Version 2.27 – December 4, 2012
Use of Lighting4 commands for undec ARC
Brennenstuhl added
Version 2.28 – December 18, 2012
Receiver tab removed from RFXmngr
Version 2.29 – December 27, 2012
Lighting4 receive added
Version 2.30 – January 1, 2013
Raex motor added
Version 3.00 – January 4, 2013
RFXtrx433 Type1/Type2 firmware added
Version 3.01 – February 4, 2013
Supported protocols list updated
Version 4.00 – February 21, 2013
Chapter 8 - Lighting4 screen updated for RFXmngr 11.0.0.0
Known Lighting4 chapter added
Version 4.01 – March 13, 2013
Receive of LaCrosse sometimes influenced by enabled Hideki
Version 4.02 – June 8, 2013
MDREMOTE LED dimmer added
Conrad RSL2 added
Energenie added
Version 4.03 – September 27, 2013
How to find the MDREMOTE ID (chapter 7.6)
WS1200 added
Byron SX Chime added
Version 4.04 – November 15, 2013
Maverick ET-732 added
Alecto SA30 added
Oregon EW109 added
Revolt added
Version 4.05 – December 5, 2013
Blyss command explanation added.
Lighting4 - Mercury added
Lighting5 – dx.com RGB LED controller added
Version 4.06 – December 27, 2013
Chapter 2.2 updated
Version 4.07 – February 10, 2014
Chapter 7.8 added: how to find the dx.com RGB LED strip driver ID
Version 4.08 – March 20, 2014
ARC and Oregon3.0 updated in table 2.4.
Energenie 5-gang 429.950 added
Version 4.09 – April 4, 2014
BlindsT6 - DC106, YOODA, Röhrmotor24 RMF added
Version 4.10 – April 7, 2014
BlindsT7 - Forest added
Version 4.11 – April 28, 2014
RGB LED – clarified AD is LightwaveRF
Version 4.12 – May 21, 2014
Kambrook RF3672 added
RFY protocol added
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 37 / 39
Somfy programming instructions added
Supported protocol list RFXtrx433 updated.
Protocol list by function added
Version 4.13 – May 31, 2014
Opus TX300/Imagintronix Soil sensor added
Version 4.14 – June 18, 2014
Prega sensor added
Conrad 34911 Lighting4 coding added
Version 4.15 – June 25, 2014
Kambrook, Rubicson, Viking supported in ext firmware
Number of RFY remotes increased from 16 to 30
Version 4.16 – June 29, 2014
RFXmngr cannot be used on Linux
Version 4.17 – July 3, 2014
CoCo GDR2 added
Version 4.18 – July 14, 2014
Opus TX300 link added
Version 4.19 – July 25, 2014
Aoke relay added
Version 4.20 – August 25, 2014
Enabling protocols clearified.
Version 4.21 – September 5, 2014
Meade sensors added
Oregon BTHGN129 sensor added
Version 4.22 – September 18, 2014
Eurodomest added (NL - Action)
Byron MP001 added
WT0122 added
Procedures added to find the Eurodomest and TRC02 ver2 ID
Version 4.23 – September 24, 2014
Proove TSS330 fridge/freezer sensor added
Version 4.24 – October 9, 2014
BlindsT0 added in ext firmware
Alecto WS1700 and compatibles added
Version 4.25 – December 13, 2014
Smartwares radiator valve added
Proove TSS320 sensor added
Version 4.26 – January 2, 2015
SelectPlus200689101 White Chime (Action NL) added
Version 4.27 – January 6, 2015
SelectPlus200689103 Black Chime (Action NL) added
Version 4.28 – January 7, 2015
Proove outdoor sensors 311346 & 311501 added
Etekcity Wireless Remote Control Outlet Switch (US)
Version 5.00 – January 10, 2015
Copyright message updated
License chapter added
RFXmngr information updated
Version 5.01 – February 27, 2015
Chapter 2.5 Lighting4 receive is reduced with HomeEasy EU enabled.
Chamberlain tubular motor added
Sunpery blind motors added
DEA Systems receivers added
Envivo ENV-1348 chime added
Alecto WS4500 added
Copyright 2011-2015, RFXCOM
RFXtrx Version 5.06 page 38 / 39
Version 5.02 – March 18, 2015
1byOne Easy Chime added
BTX blind motors added
Dolat DLM-1 blind motors added
OTIO added
Version 5.03 – March 19, 2015
TFA 30.3160 pool sensor added
Version 5.04 – April 14, 2015