RFXCOM RFXtrx Smart-Home-Integration, kostenlos und Open Source
RFXtrx433/433XL over ser2net: Oregon sensors, Chacon DiO remotes, Somfy RTS shutters, alarms.
Veröffentlicht von LM1LC3N7
- Geräte
- Version 0.1.1
- Erfordert Gladys >=5.1.0
- ★ 0
Die Dokumentation dieser Integration wird von ihrem Autor geschrieben und ist bisher nur auf Englisch verfügbar.
Connect an RFXCOM RFXtrx433, RFXtrx433E or RFXtrx433XL to Gladys: Oregon Scientific weather probes, OWL energy meters, door, motion and smoke detectors, remotes and wall switches (Chacon DiO / KlikAanKlikUit, X10, Blyss…), and the receivers the RFXtrx drives (Chacon DiO plugs and modules, lights, Somfy RTS shutters).
Unofficial integration, not affiliated with RFXCOM.
1. Expose the RFXtrx over TCP
The integration runs in a sandboxed container that cannot open a USB port. The RFXtrx stays plugged into a machine of your network (the Gladys machine, a Raspberry Pi…), and ser2net exposes its serial port on the network. The bytes are exactly those of the serial port, at 38400 bauds.
Find the stable name of the RFXtrx (it does not change when other USB devices are plugged in):
ls -l /dev/serial/by-id/
## usb-RFXCOM_RFXtrx433XL_XXXXXXXX-if00-port0 -> ../../ttyUSB0
With ser2net 4 (Debian 11+, Ubuntu 22.04+, Raspberry Pi OS)
sudo apt install ser2net
/etc/ser2net.yaml:
connection: &rfxtrx
accepter: tcp,4001
enable: on
options:
kickolduser: true
connector: serialdev,/dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_XXXXXXXX-if00-port0,38400n81,local
Replace the /dev/serial/by-id/... path with yours, then:
sudo systemctl restart ser2net
With ser2net 3 (older distributions)
/etc/ser2net.conf:
4001:raw:0:/dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_XXXXXXXX-if00-port0:38400 8DATABITS NONE 1STOPBIT
With socat (quick test)
socat TCP-LISTEN:4001,reuseaddr,fork FILE:/dev/serial/by-id/usb-RFXCOM_RFXtrx433XL_XXXXXXXX-if00-port0,b38400,raw,echo=0
The bridge has no password: whoever reaches the port drives your radio devices. Keep it on your local network, never open it to the Internet. Only one program at a time can talk to the RFXtrx: stop Domoticz, Home Assistant or RFXmngr if they use it (
kickolduserhands it to the latest connection).
2. Configure the integration
| Field | What to type |
|---|---|
| Bridge host | The IP of the ser2net machine. For the Gladys machine itself, its LAN IP: localhost is the container. |
| Bridge TCP port | 4001 in the examples above. |
| Protocols received | Nothing ticked: the RFXtrx keeps its own settings (made with RFXmngr). Otherwise the ticked protocols are sent at every connection. |
| Minimum signal | 0 offers everything. 3 or 4 keeps far emitters (the neighbours' probes) out of the new devices. |
| Actuators | The receivers the RFXtrx drives — see part 4. |
The connection status shows the receiver model, the firmware and the protocols received. Test the connection asks the RFXtrx again and gives its response time.
The ticked protocols are not saved in the memory of the RFXtrx (it takes a limited number of writes): the integration sends them at every connection. Turn on only what you use, the receiver hears better: AC for Chacon DiO, Oregon for the probes and OWL, Visonic for Visonic detectors, X10, ARC for code-wheel remotes, Blyss…
3. What is heard: the Discovery tab
Nothing to declare: as soon as the RFXtrx hears an emitter, it appears in the
Discovery tab. Create yours; values and scene triggers only go to the
devices created. The list is kept in /data across restarts.
- Oregon Scientific and compatible probes (THGR122, THGN132, THGR810, BTHR968, PCR800, WGR800, UVN800…): temperature, humidity, pressure, rain (total and rate), wind (direction, speed, gusts), UV.
- OWL meters: power and energy index (kWh) of the CM119/CM160 and CM180, current per phase and energy of the CM180i, currents of the CM113.
- Security1 detectors: opening (X10, Visonic PowerCode), motion (X10, Visonic, Meiantech) and smoke (KD101, SA30, RM174RF), with tamper. Motion and smoke detectors never say "it is over": their state goes back to 0 after 90 seconds.
- Remotes, wall switches and keyfobs (Chacon DiO / KlikAanKlikUit,
HomeEasy, X10, ARC, Blyss, LightwaveRF, X10 security, Visonic CodeSecure):
one button feature per button heard (
1,2…;groupfor group commands;allin X10;K4in Blyss;alarmon a keyfob). Its value is the command received (on, off, arm, disarm, panic…).
Every sensor has its battery (in %, 10 to 100; Oregon probes only know "good" 100 % and "low" 10 %) and its signal (0 to 5). A probe silent for an hour is shown unreachable.
Oregon probes pick a new address at every battery change: the probe shows up again as a new device in Discovery.
Scene trigger
An RFXCOM remote is pressed: filter on the remote, the button and the command. Variables: button, command, level (%), protocol, address. A press the remote repeats fires once.
4. What is driven: the actuators
A receiver (plug, light module, shutter motor) cannot be discovered over the air: it must be declared. The simplest way is the Pair an actuator button:
- put the receiver in learning mode: button held on a Chacon DiO plug (or power it up), PROG held on the original remote of a Somfy RTS shutter until it jogs;
- type a name, the kind, the protocol, and leave the address empty: a free address is chosen;
- run the action: the RFXtrx sends the pairing frame ("on", or "program" for Somfy RTS) and the receiver is added to the Actuators field. Create it from the Discovery tab.
| Kind | What it does |
|---|---|
switch | On / off. |
light | On / off, shown as a light. |
dimmer | On / off and brightness (AC / Chacon DiO, HomeEasy EU, LightwaveRF). |
shutter | Open / stop / close (Somfy RTS, RFY and RFYEXT protocols). |
You can also fill the field by hand, entries separated by ;:
Living room shutter = shutter RFY 10203/1; Desk lamp = dimmer AC 1A2B3C4/2; Hall = switch X10 A3
| Protocols | Address |
|---|---|
| AC, HOMEEASY_EU, ANSLUT | id/unit, e.g. 1A2B3C4/1 (0 = group) |
| RFY, RFYEXT (Somfy RTS) | id/unit, e.g. 10203/1 |
| LIGHTWAVERF, CONRAD, EMW100, BBSB, EURODOMEST, IT, KANGTAI | id/unit, e.g. F09AC8/1 |
| BLYSS | id/group/unit, e.g. F09A/A/1 |
| X10, ARC, CHACON, ELRO, WAVEMAN… | house+unit, e.g. A3, set on the receiver |
Driving a receiver already paired with your remote: declare the actuator
with the address of that remote (shown in the parameters of its device:
address 39AC7A1 and button 1 give 39AC7A1/1), with "Send the pairing
frame" unticked. When you use the remote, the state of the actuator follows
in Gladys.
Somfy RTS: the RFXtrx433E or 433XL plays a virtual remote whose rolling code it keeps; pair it once per shutter (step 1 above). Stop is the "my" button: it stops a moving shutter and sends a still one to its favourite position. The original RFXtrx433 (without E) does not transmit RFY.
Radio orders are never confirmed by the receiver: Gladys shows what was sent.
Troubleshooting
- "refused the connection": ser2net is not running, or not on this port
(
systemctl status ser2net). - "the bridge answers, but not the RFXtrx": the ser2net port is open but the RFXtrx does not answer — unplugged, wrong device path, wrong speed (it must be 38400), or another program uses it.
- "closed the connection": another program took over ser2net
(
kickolduser). - A remote or a probe does not show up: is its protocol received (connection status)? Is the minimum signal too high?
- Too many devices in Discovery: raise the minimum signal, tick only the protocols you use.
- A Somfy shutter does not move: it must be paired once, PROG held on its remote when pairing.
Not supported yet: other shutter motors (Blinds1), chimes, thermostats, Lighting4 (PT2262), Linky / Cartelectronic TIC meters and the 868 MHz models. Tell us what you miss on the Gladys forum.
Konfigurationseinstellungen
Diese Einstellungen fragt RFXCOM RFXtrx in seinem Konfigurationsbildschirm in Gladys ab.
| Einstellung | Typ | Pflichtfeld | Beschreibung |
|---|---|---|---|
| Your RFXtrx, reached through the network | section | Nein | The integration runs in a sandboxed container that cannot open a USB port: plug the RFXtrx433 or RFXtrx433XL into a machine of your network (the Gladys machine, a Raspberry Pi…) and expose its serial port over TCP with ser2net, at 38400 bauds. Type that machine's LAN IP address below, not localhost. Sensors, detectors and remotes heard on the air appear in the Discovery tab; the receivers the RFXtrx drives (plugs, lights, Somfy RTS shutters) are declared below or with the "Pair an actuator" button. Not affiliated with RFXCOM. |
| Bridge host | string | Ja | IP address or name of the machine running ser2net. For the Gladys machine itself, its LAN IP address: localhost is the container of the integration. |
| Bridge TCP port | number | Nein | The TCP port ser2net listens on for the RFXtrx (4001 in the documentation examples). |
| Protocols received | multi_select | Nein | Leave everything unticked to keep the protocols already set in the RFXtrx (with RFXmngr). Ticked protocols replace them at every connection (not saved in the RFXtrx). Turn on only what you use: the receiver hears better, and fewer neighbours. |
| Minimum signal of a new emitter (0-15) | number | Nein | An emitter heard for the first time with a weaker signal is not offered in Discovery: raise it to 3 or 4 to leave out the neighbours' probes. 0 offers everything. The devices already offered are never filtered. |
| Actuators | string | Nein | The receivers the RFXtrx drives, separated by ";": Name = kind PROTOCOL address. Kinds: switch, light, dimmer, shutter. Addresses: A1 (X10, ARC…), 1A2B3C4/1 (AC, HomeEasy, LightwaveRF, RFY), F09A/A/1 (Blyss). The "Pair an actuator" button fills this field for you. |
So installierst du RFXCOM RFXtrx in Gladys
- Öffne in Gladys Integrationen: RFXCOM RFXtrx erscheint im Katalog neben den nativen Integrationen, mit einem Community-Badge.
- Klicke auf Installieren. Gladys lädt das Docker-Image (
ghcr.io/lm1lc3n7/gladys-rfxcom:0.1.1) herunter, startet es in einer vom Kern isolierten Sandbox und erzeugt die Oberfläche der Integration (Geräte, Erkennung und Konfiguration). - Öffne den Bildschirm Konfiguration der Integration, fülle die Einstellungen aus und speichere.
- Du kannst sie auch direkt über die URL ihres Repositorys installieren: https://github.com/LM1LC3N7/gladys-rfxcom.
RFXCOM RFXtrx benötigt Gladys >=5.1.0. Der Katalog in Gladys wird stündlich aktualisiert, eine neue Version ist also spätestens eine Stunde nach ihrer Veröffentlichung verfügbar.
Du nutzt Gladys noch nicht? Es ist kostenlos und Open Source: folge der Installationsanleitung, um loszulegen.
Über externe Integrationen
RFXCOM RFXtrx ist eine externe Integration: eine Community-Integration, die als Docker-Container verpackt und auf GitHub veröffentlicht wird. Gladys installiert sie mit einem Klick und führt sie in einer vom Kern isolierten Sandbox aus. Sie wird von LM1LC3N7 veröffentlicht und gepflegt, nicht vom Gladys-Kernteam.
- Alle Integrationen durchsuchen, native und aus der Community
- Deine eigene externe Integration bauen und veröffentlichen
- Quellcode auf GitHub — Quelle dieser Dokumentation