-
Notifications
You must be signed in to change notification settings - Fork 0
Ir Trans Binding
Documentation of the IRtrans binding Bundle
The IRtrans binding bundle is available as a separate (optional) download.
If you want to let openHAB communicate with the infrared emitter/transceiver of IrTrans (www.irtrans.de), please place this bundle in the folder ${openhab_home}/addons
and add binding information to your configuration. See the following sections on how to do this. Note: the IRtrans binding makes use of the TCP/UDP binding, and therefore also the TCP binding has to be copied into the ${openhab_home}/addons
folder
The IRtrans binding currently supports the Ethernet version of the IRtrans transceiver and communicates with the transceiver over a TCP connection
In order to bind an item to an ethernet transceiver, 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 for the IrTrans binding configuration string is explained here:
The format of the binding configuration is simple and looks like this:
irtrans="[<command>:<ip address>:<port>:<led>:<device>:<ircommand>], [<command>:<ip address>:<port>:<led>:<device>:<ircommand>], ..."
where <ip address>
is the hostname or ip address in dotted notation of the remote host
where <led>
is the transceiver led to be used to send or receive the infrared command, and is one of the following values:
DEFAULT, INTERNAL, EXTERNAL, ALL, ONE, TWO, THREE, FOUR, FIVE, SIX, SEVEN, EIGHT. Note: It is up to the user to check that the led value is valid for the device installed, e.g. not all IRtrans transceivers have the same number of led transmitters or received built-in. See the documentation of your IRtrans device
where <device>
is the name of the device (category), as defined using the IRtrans LAN Server software
and where,finally, <ircommand>
is the name of the infrared command, as defined using the IRtrans LAN Server software, to be sent to the transceiver when <command>
is received. When an infrared command is received by the transceiver that matches the <device>
:<ircommand>
, then the Item will be updated with the <command>
It is possible to define 'wildcards' for <device>
and <ircommand>
: if either of them are equal to **
then respectively, any device that defines the given <ircommand>
, or any <ircommand>
for the given <device>
, will 'match' and will trigger the status update of the Item. If you would put **
for both <device>
and <ircommand>
then any infrared command received by the transceiver will cause the Item to be updated.
Note: the IRtrans device does not communicate which <led>
a command is received by, so that information can not be used to wildcard infrared commands received
Note: If the Item is of the type String, then any infrared command received by the transceiver will cause the Item to be updated with "<device>
,<ircommand>
". Likewise, any string passed on by the OpenHAB runtime will simply be parsed using the "<device>
,<ircommand>
" pattern. For such Items the <command>
element has to be omitted in the configuration string
Here are some examples of valid binding configuration strings:
irtrans="[ON:192.168.0.1:3000:1:pioneer:voldown]" // send the 'voldown' infrared command of remote type 'pioneer' when ON is received
irtrans="[ON:192.168.0.1:3000:1:pioneer:*]" // accept any command from remote of type Pioneer, e.g. any key press on the remote
irtrans="[ON:192.168.0.1:3000:*:pioneer:voldown]" // send command on all leds
irtrans="[ON:192.168.0.1:3000:1:*:*]" // accept all infrared commands from any type of remote
irtrans="[192.168.0.1:3000:1:*:*]" // for String Items, take or update 'remote,command' strings that match the pattern
As a result, your lines in the items file might look like the following: Switch PioneerReceiver_Vol "Pioneer" (AV) { irtrans="*[ON:192.168.0.1:3000:1:pioneer:volup], *[OFF:192.168.0.1:3000:1:pioneer:voldown]" }
Installation
Community
- Support
- News Archive
- Presentations
- How to Contribute
- IDE Setup
- How to Implement a Binding
- How to Implement an Action
- Projects using openHAB
- User Interfaces
- Classic UI
- iOS Client
- Android Client
- GreenT UI
- CometVisu
- Automation
- Scripts
- Rules
- Actions
- Bindings
- AlarmDecoder Binding
- Anel Binding
- Asterisk Binding
- Astro Binding
- BenQ Projector Binding
- Bluetooth Binding
- Comfo Air Binding
- Config Admin Binding
- CUL Binding
- CUPS Binding
- DAIKIN Binding
- Davis Binding
- digitalSTROM Binding
- DMX512 Binding
- DSC Alarm Binding
- DSMR Binding
- Ecobee Binding
- EDS OWSever Binding
- eKey Binding
- Energenie Binding
- EnOcean Binding
- Epson Projector Binding
- Exec Binding
- Freebox Binding
- Freeswitch Binding
- Fritz AHA Binding
- Fritz!Box Binding
- FS20 Binding
- Global Cache IR Binding
- GPIO Binding
- HAI/Leviton OmniLink Binding
- HDAnywhere Binding
- Heatmiser Binding
- Homematic / Homegear Binding
- HTTP Binding
- IEC 62056-21 Binding
- IHC / ELKO Binding
- ImperiHome Binding
- Insteon Hub Binding
- Insteon PLM Binding
- IRtrans Binding
- jointSPACE-Binding
- KNX Binding
- Koubachi Binding
- Leviton/HAI Omnilink Binding
- Lg TV Binding
- MAX!Cube-Binding
- MAX! CUL Binding
- MiLight Binding
- MiOS Binding
- Modbus TCP Binding
- MPD Binding
- MQTT Binding
- MQTTitude binding
- Neohub Binding
- Nest Binding
- Netatmo Binding
- Network Health Binding
- Network UPS Tools Binding
- Nibe Heatpump Binding
- Nikobus Binding
- Novelan/Luxtronic Heatpump Binding
- NTP Binding
- One-Wire Binding
- Onkyo AV Receiver Binding
- Open Energy Monitor Binding
- OpenPaths presence detection binding
- OpenSprinkler Binding
- OSGi Configuration Admin Binding
- Philips Hue Binding
- Piface Binding
- pilight Binding
- Pioneer-AVR-Binding
- Plugwise Binding
- PLCBus Binding
- Primare Binding
- Pulseaudio Binding
- RFXCOM Binding
- Samsung AC Binding
- Samsung TV Binding
- Serial Binding
- Satel Alarm Binding
- Snmp Binding
- Somfy URTSI II Binding
- Sonos Binding
- Squeezebox Binding
- Swegon ventilation Binding
- System Info Binding
- TCP/UDP Binding
- Tellstick Binding
- TinkerForge Binding
- Tivo Binding
- VDR Binding
- Velleman-K8055-Binding
- Wake-on-LAN Binding
- Waterkotte EcoTouch Heatpump Binding
- Weather Binding
- Wemo Binding
- Withings Binding
- XBMC Binding
- xPL Binding
- Yamahareceiver Binding
- Zibase Binding
- Z-Wave Binding
- Application Integration
- Asterisk
- Google Calendar
- Linux Media Players
- ROS Robot Operating System
- Telldus Tellstick
- Zoneminder
- Rooted Wink Hub
- Persistence
- db4o Persistence
- rrd4j Persistence
- MySQL Persistence
- MongoDB Persistence
- Sen.Se Persistence
- Cosm Persistence
- Logging Persistence
- Exec Persistence
- MQTT Persistence
- InfluxDB Persistence
- JPA Persistence
- Misc
- Transformations
- REST-API
- Security
- Service Discovery
- Dropbox Bundle
- Voice Control
Samples
- Item definitions
- Sitemap definitions
- Binding configurations
- Comfo Air Binding
- Nest Binding (new)
- Nest Thermostat
- Rollershutter Groups
- Squeezebox
- WAC Binding
- WebSolarLog
- Rules
- Misc. rule examples
- Alarm Clock
- Convert Farenheit to Celcius
- Taking Rules to New Heights
- Reusable Rules via Functions
- Items, Rules and more Examples of a SmartHome
- REST Examples
- Tips and Tricks
- Scripts
- Syntax highlighting for external editors
- Update-Scripts
- Controlling openHAB with Android
- Usecase examples
Release Notes