-
Notifications
You must be signed in to change notification settings - Fork 0
RFXCOM Binding
Documentation of the RFXCOM binding Bundle
Binding should be compatible at least with RFXtrx433 USB 433.92MHz transceiver, which contains both receiver and transmitter functions.
See further information from http://www.rfxcom.com
RFXCOM binding support currently TemperatureHumidity, Lighting1, Lighting2 and Curtain1 packet types.
For installation of the binding, please see Wiki page Bindings.
First of all you need to configure the following values in the openhab.cfg file (in the folder '${openhab_home}/configurations').
############################### RFXCOM Binding #########################################
# Serial port of RFXCOM interface
# Valid values are e.g. COM1 for Windows and /dev/ttyS0 or /dev/ttyUSB0 for Linux
rfxcom:serialPort=
# Set mode command for controller (optional)
# E.g. rfxcom:setMode=0D000000035300000C2F00000000
rfxcom:setMode=
The rfxcom:serialPort
value is the identification of the serial port on the host system where RFXCOM controller is connected, e.g. "COM1" on Windows, "/dev/ttyS0" on Linux or "/dev/tty.PL2303-0000103D" on Mac.
The rfxcom:setMode
value is is optional. Set mode command can be used to configure RFXCOM controller to listening various receiver protocols. This is very useful because the receiver will become more sensitive when protocols not used are disabled. You can use RFXmngr application to configure controller and get valid configuration command. Command must be 28 characters (14 bytes) hexadecimal string.
In order to bind an item to RFXCOM device, you need to provide configuration settings. The easiest way to do so is to add some binding information in your item file (in the folder configurations/items). The syntax of the binding configuration strings accepted is the following:
in: rfxcom="<DeviceId:ValueSelector"
out: rfxcom=">DeviceId:PacketType.SubType:ValueSelector"
where DeviceID
is a valid wireless device identifier.
-
Lighting1 format:
SensorId.UnitCode
e.g. B.1, B.2 or B.G for group functions -
Lighting2 format:
SensorId.UnitCode
e.g. 636602.1 -
Curtain1 format:
SensorId.UnitCode
e.g. P.1 see RFXCOM documentation -
TemperatureHumidity format:
SensorId
e.g. 2561
Examples, how to configure your items:
Number OutdoorTemperature { rfxcom="<2561:Temperature" }
Number OutdoorHumidity { rfxcom="<2561:Humidity" }
Switch Btn1 { rfxcom="<636602.1:Command" }
Number Btn1SignalLevel { rfxcom="<636602.1:SignalLevel" }
Dimmer Btn1DimLevel { rfxcom="<636602.1:DimmingLevel" }
String Btn2RawData { rfxcom="<636602.2:RawData" }
Switch ChristmasTreeLights { rfxcom">636602.1:LIGHTING2.AC:Command" }
Rollershutter CurtainDownstairs { rfxcom=">P.1:CURTAIN1.HARRISON:Shutter" }
PacketType.SubType
specify packet and sub type information ...
PacketType.SubType | Description | ValueSelector |
LIGHTING1.X10 | Untested | |
LIGHTING1.ARC | tested and working | Command |
LIGHTING1.AB400D | Untested | |
LIGHTING1.WAVEMAN | Untested | |
LIGHTING1.EMW200 | Untested | |
LIGHTING1.IMPULS | Untested | |
LIGHTING1.RISINGSUN | Untested | |
LIGHTING1.PHILIPS | Untested | |
LIGHTING2.AC | tested and working | Command, DimmingLevel |
LIGHTING2.HOME_EASY_EU | Untested | |
LIGHTING2.ANSLUT | Untested | |
CURTAIN1.HARRISON | Harrison curtain rail, e.g. Neta 12 | Shutter |
TEMPERATUREHUMIDITY.THGN122_123_132_THGR122_228_238_268 | Untested | |
TEMPERATUREHUMIDITY.THGN800_THGR810 | Untested | |
TEMPERATUREHUMIDITY.RTGR328 | Untested | |
TEMPERATUREHUMIDITY.THGR328 | Untested | |
TEMPERATUREHUMIDITY.WTGR800 | Untested | |
TEMPERATUREHUMIDITY.THGR918_THGRN228_THGN50 | Untested | |
TEMPERATUREHUMIDITY.TFA_TS34C__CRESTA | Untested | |
TEMPERATUREHUMIDITY.WT260_WT260H_WT440H_WT450_WT450H | Untested | |
TEMPERATUREHUMIDITY.VIKING_02035_02038 | Untested |
ValueSelector
specify ...
Value selector | Valid OpenHAB data type | Information |
RawData | StringItem | |
Command | SwitchItem | ON, OFF, GROUP_ON, GROUP_OFF |
SignalLevel | NumberItem | |
DimmingLevel | DimmerItem | UP, DOWN, PERCENTAGE |
Temperature | NumberItem | |
Humidity | NumberItem | |
HumidityStatus | StringItem | |
BatteryLevel | NumberItem | |
Shutter | RollershutterItem | OPEN, CLOSE, STOP |
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Actions
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- CometVisu
- Bindings
- Asterisk Binding
- Bluetooth Binding
- Comfo Air Binding
- CUPS Binding
- digitalSTROM Binding
- DMX512 Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Fritz!Box Binding
- Fritz AHA Binding
- Heatmiser Binding
- Homematic Binding
- HTTP Binding
- IHC / ELKO Binding
- Insteon Hub Binding
- KNX Binding
- Koubachi Binding
- MAX!Cube-Binding
- MiLight Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- Network Health Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver Binding
- OpenSprinkler Binding
- OSGi Configuration Admin Binding
- Philips Hue Binding
- Piface Binding
- Pioneer-AVR-Binding
- Plugwise Binding
- PLCBus Binding
- Pulseaudio Binding
- RFXCOM Binding
- Samsung TV Binding
- Serial Binding
- Snmp Binding
- Squeezebox Binding
- System Info Binding
- Somfy URTSI II Binding
- Sonos Binding
- TCP/UDP Binding
- TinkerForge Binding
- VDR Binding
- Wake-on-LAN Binding
- Z-Wave Binding
- Persistence
- db4o Persistence
- rrd4j Persistence
- Sql Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec Persistence
- Automation
- Scripts
- Rules
- Actions
- Misc
- REST-API
- Security
- Google Calendar Support
- Twitter Action
- Service Discovery
- Dropbox Bundle
Samples
- Item definitions
- Sitemap definitions
- Binding configurations
- Rules
- REST Examples
- Tips & Tricks
- FAQ
- XSLT Transforms
- Scripts
- Integration with other applications
- Syntax highlighting for external editors
- Update-Scripts
- Samples-Comfo-Air-Binding
Release Notes