-
Notifications
You must be signed in to change notification settings - Fork 0
Logitech Harmony Hub Binding
The Harmony Hub binding is used to enable communication between openHAB and multiple Logitech Harmony Hub devices. The API exposed by the Harmony Hub is relatively limited, but it does allow for reading the current activity as well as setting the activity and sending device commands.
Add the org.openhab.binding.harmonyhub.jar, org.openhab.io.harmonyhub.jar and optionally the org.openhab.action.harmonyhub.jar to the addons folder of an openHAB runtime installation and restart.
The IO bundle is required for the action or binding bundle to work.
The following configuration items are required to be set in openhab.cfg:
harmonyhub:host=<local ip address of your hub>
harmonyhub:username=<your logitech username>
harmonyhub:password=<your logitech password>
Optionally you may add a unique qualifier to your configuration to support multiple hubs
harmonyhub:qualifier.host=<local ip address of your hub>
harmonyhub:qualifier.username=<your logitech username>
harmonyhub:qualifier.password=<your logitech password>
replace 'qualifier' with a string that describes the hub (ex: familyroom )
The Harmony binding supports both outgoing and incoming item bindings of the form:
{ harmonyhub="<direction>[<optional qualifier>:<binding> ...]" }
<direction>
may be :
Incoming (IN) (read only)
<[....]
Outbound (OUT) (write only)
>[....]
Bi-Directional (BOTH) (read and write)
*[....]
and where <binding>
can be:
Current Activity supports both IN(<), OUT(>) and BOTH(*) directions.
Displays the current activity:
String Harmony_Activity "activity [%s]" { harmonyhub="<[currentActivity]" }
Displays the current activity for a named hub:
String Harmony_Activity "activity [%s]" { harmonyhub="<[familyroom:currentActivity]" }
Optionally a string from can be sent to a current activity binding (ex: from an button).
String Harmony_Activity "activity [%s]" { harmonyhub="*[familyroom:currentActivity]" }
And in the Sitemap.
Switch item=Harmony_Activity mappings=[PowerOff='PowerOff', Roku='Roku',TiVo='TiVo']
Start Activity supports the OUT(>) direction.
Start the specified activity (where activity can either be the activity id or label).
String HarmonyHubPowerOff "powerOff" { harmonyhub=">[start:PowerOff]" }
String HarmonyHubWatchTV "watchTV" { harmonyhub=">[start:Watch TV]" }
Start the specified activity on a named hub (where activity can either be the activity id or label).
String HarmonyHubPowerOff "powerOff" { harmonyhub=">[familyroom:start:PowerOff]" }
String HarmonyHubWatchTV "watchTV" { harmonyhub=">[familyroom:start:Watch TV]" }
Start Activity supports the OUT(>) direction.
Press the specified button on the given device (where device can either be the device id or label).
String HarmonyHubMute "mute" { harmonyhub=">[press:Denon AV Receiver:Mute]" }
Press the specified button on the given named device (where device can either be the device id or label).
String HarmonyHubMute "mute" { harmonyhub=">[familyroom:press:Denon AV Receiver:Mute]" }
The following actions are supported in rules:
harmonyPressButton(<device>, <command>)
harmonyPressButton(<qualifier>,<device>, <command>)
harmonyStartActivity(<activity>)
harmonyStartActivity(<qualifier>,<activity>)
Surround the activity name in quotes, for example:
harmonyStartActivity("PowerOff")
Under debug logging the IO bundle will print the list of devices, activities and the full JSON config for each hub. This can be used to populate items.
The JSON configuration can also be obtained using the Harmony Android app by syncing with the hub (Menu-> Harmony Setup - > Sync). The configuration will be saved in home/Harmony/userConfig.json.
The harmony-java-client project on GitHub provides a simple shell for querying a Harmony Hub, and can be used to retrieve the full configuration of the hub to determine ids of available activities and devices as well as device commands (buttons).
###Linux / OS X
###Windows
- Cosm Persistence
- db4o Persistence
- Exec Persistence
- InfluxDB Persistence
- JDBC Persistence
- JPA Persistence
- Logging Persistence
- mapdb Persistence
- MongoDB Persistence
- MQTT Persistence
- my.openHAB Persistence
- MySQL Persistence
- rrd4j Persistence
- Sen.Se Persistence
- SiteWhere Persistence
- AlarmDecoder Binding
- Anel Binding
- Arduino SmartHome Souliss Binding
- Asterisk Binding
- Astro Binding
- Autelis Pool Control Binding
- BenQ Projector Binding
- Bluetooth Binding
- Bticino Binding
- CalDAV Binding
- Comfo Air Binding
- Config Admin Binding
- CUL Binding
- CUL Intertechno Binding
- CUPS Binding
- DAIKIN Binding
- Davis Binding
- Denon Binding
- digitalSTROM Binding
- DMX512 Binding
- DSC Alarm Binding
- DSMR Binding
- eBUS Binding
- Ecobee Binding
- EDS OWSever Binding
- eKey Binding
- Energenie Binding
- EnOcean Binding
- Enphase Energy Binding
- Epson Projector Binding
- Exec Binding
- Freebox Binding
- Freeswitch Binding
- Frontier Silicon Radio 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
- IPX800 Binding
- IRtrans Binding
- jointSPACE-Binding
- KNX Binding
- Koubachi Binding
- LCN Binding
- LightwaveRF Binding
- Leviton/HAI Omnilink Binding
- Lg TV Binding
- Logitech Harmony Hub
- MailControl 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
- Panasonic TV Bindung
- panStamp Binding
- Philips Hue Binding
- Piface Binding
- pilight Binding
- Pioneer-AVR-Binding
- Plex Binding
- Plugwise Binding
- PLCBus Binding
- Primare Binding
- Pulseaudio Binding
- RFXCOM Binding
- RWE Smarthome Binding
- Sager WeatherCaster Binding
- Samsung AC Binding
- Samsung TV Binding
- Serial Binding
- Sallegra Binding
- Satel Alarm Binding
- Sinthesi Sapp Binding
- Snmp Binding
- Somfy URTSI II Binding
- Sonos Binding
- Squeezebox Binding
- Swegon ventilation Binding
- System Info Binding
- TA CMI Binding
- TCP/UDP Binding
- Tellstick Binding
- TinkerForge Binding
- Tivo Binding
- VDR Binding
- Velleman-K8055-Binding
- Wago 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
- Asterisk
- Google Calendar
- Linux Media Players
- ROS Robot Operating System
- Telldus Tellstick
- Zoneminder
- Wink Hub (rooted)
- Wink Monitoring
- Transformations
- XSLT
- JSON
- REST-API
- Security
- Service Discovery
- Voice Control
- BritishGasHive-Using-Ruby
- Dropbox Bundle
A good source of inspiration and tips from users gathered over the years. Be aware that things may have changed since they were written and some examples might not work correctly.
Please update the wiki if you do come across any out of date information.
- Comfo Air Binding
- Ecobee Examples
- Nest Examples
- Rollershutter Bindings
- Squeezebox
- WAC Binding
- WebSolarLog
- Alarm Clock
- Convert Farenheit to Celcius
- The mother of all lighting rules
- Reusable Rules via Functions
- Combining different Items
- Items, Rules and more Examples of a SmartHome
- Google Map
- Controlling openHAB with Android
- Usecase examples
- B-Control Manager
- Spell checking for foreign languages
- Flic via Tasker
- Chromecast via castnow