Archive for the ‘Using’ Category

Updated RFXmngr and Pro1, Pro2 and ProXL1 firmware version 1033

Sunday, December 2nd, 2018

Firmware version 433_1033

  • Copy RFY device enabled

RFXmngr version

rfu1,2,3 added to enable RFY copy from one to another RFXtrx

See chapter 9.1 in the RFXtrx User Guide how to copy a RFY device

RFXtrx433XL information

Friday, October 19th, 2018

Large memory size:
The RFXtrx433XL has got a double size memory so that it can have now all currently supported protocols in one firmware version.

Pro firmware:
The protocol detection in the receiver is totally redesigned which makes it now possible to enable multiple protocols.
In the older Ext and Ext2 firmware for the RFXtrx433E some protocols were not received or not reliable received if another protocol was enabled. The ProXL firmware does not have this limitation. This firmware design is also available for the RFXtrx433E as Pro1 and Pro2. Because of the memory limitation there are still 2 versions for the RFXtrx433E.

RF noise level:
The new Pro firmware (Pro1, Pro2, ProXL) detects the RF noise level during startup of the receiver and RF signals above this level are processed. It is required to install the RFXtrx433XL on a good location with a low level of RF noise so that a good receive quality is guaranteed. The Noise level is displayed in RFXmngr on the Main tab. A value of 92 with the standard antenna is acceptable but lower is better. A general rule is to place the RFXtrx433XL not close to a Raspberry PI, routers or other electronic equipment, power cables or metal pipes.

Important note: The RFXtrx433XL must only be programmed with ProXL firmware. If an Ext or Pro2 is flashed in the RFXtrx433XL it will stay in the bootloader and it needs a special procedure to get it operational again, the enclosure must be opened and a temporary connection (without soldering) must be made on the Printed Circuit Board. The recovery procedure is available in the RFXtrx User Guide chapter 19.

Changed USB interface:
The RFXtrx433XL has another USB FTDI interface chip. It uses the same USB drivers as used by the RFXtrx433 and RFXtrx433E and needs no action in the operating systems.

Serial interface connection:
There is a connection available for a serial interface to replace the USB connection. This connection can be used to connect a RS232 or LAN interface. See chapter 18 in the RFXtrx User Guide. Select an interface that does not produce RF noise. As an example RFXCOM has tested the USR-TCP232 LAN interface but this interface module produces too much RF noise at 433MHz and the RFXtrx receives only sensor at a very short distance.

Smart meter interface:
There is a special serial interface connection on the RFXtrx433XL PCB to connect the Dutch P1 smart meter or an interface for the French Teleinfo meters. See chapter 16 & 17 in the RFXtrx User Guide. Support for this P1 connection is expected soon in Domoticz and Homeseer.

Multiple weather sensors

Tuesday, May 5th, 2015

Communication Failures will sometimes arise if you have 2 or more weather sensors of the same type and with the same channel selected. One or two sensors are sometimes not received for a few hours. The reason is that they transmit during this period on the same moment. The interval time differs a very little bit for each sensor and the transmit period shifts slowly and at a certain time both sensors transmit on a different time again and are received again.

The solution is to select another channel on each sensor of the same type or use different sensor types.
Note: TEMP1, TEMP2 are different types but THR128 and THC138 are the same types as they are both TEMP1 sensors!
The THGR810 is a 10 channel sensor and you can use 10 of these sensors without having the Communication Failure due to sensor transmission overlap.
If different channels are selected or different types are used and communication failures occur an out of range is the most expected problem. Don’t install the sensors near metal objects because this can limit the range too.

It can still happen that sensors transmit at the same time when having different sensor types or different channels selected but not for a long period and Communication Failures will not appear due to this.

For the list of supported weather sensor types see:

How to control HomeEasy HE8xx modules.

Friday, February 27th, 2015

RFXCOM supports the HomeEasy AB600 (ARC), HE2xx (AC) and HE4xx (HE EU) protocols.
The HE8xx protocol is not supported!
But the HE8xx modules can be controlled by RFXCOM using an ARC, AC or HE EU protocol.

The HE8xx remote transmits multiple protocols, eg HE8xx, HE EU, AC and ARC.
If a HE8xx dimmer is paired with a HE8xx remote the HE8xx protocol is used. The RFXCOM receives only the HE EU, AC and ARC protocols. If you try to control the HE8xx dimmer with one of these received codes is does not operate because the dimmer is using the HE8xx code.

Reset the HE8xx dimmer to remove all paired remotes from the dimmer,
Put the HE8xx dimmer in learning mode and transmit an ON command with the RFXCOM using one of the protocols and codes (house code, ID, unit code) as received by the RFXCOM from the HE8xx remote.
The HE8xx dimmer can now be controlled using the HE8xx remote and the RFXCOM.