-
Notifications
You must be signed in to change notification settings - Fork 0
pilight Binding
Documentation for the pilight binding
This page describes the pilight binding, which allows openhab to communicate with a pilight instance:
pilight is a free open source full fledge domotica solution that runs on a Raspberry Pi, HummingBoard, BananaPi, Radxa, but also on *BSD and various linuxes (tested on Arch, Ubuntu and Debian). It's open source and freely available for anyone. pilight works with a great deal of devices and is frequency independent. Therefor, it can control devices working at 315Mhz, 433Mhz, 868Mhz etc. Support for these devices are dependent on community, because we as developers don't own them all.
pilight is a cheap way to control 'Click On Click Off' devices. It started as an application for the Raspberry Pi (using the GPIO interface) but it's also possible now to connect it to any other PC using an Arduino Nano. You will need a cheap 433Mhz transceiver in both cases. See the Pilight manual for more information.
There are some differences between version 1.6 and 1.7 of this binding:
openHAB version | Supported pilight version | Supported Items |
---|---|---|
1.6 | 5.0 | Switch, Dimmer, String, Number |
1.7 | >= 6.0 | Switch, Dimmer, Contact, String, Number |
In openHAB 1.6, pilight version 5 is supported. In the latest version of openHAB (1.7), only pilight versions 6 and later supported. Make sure you're running the right version of pilight, since the API between those two versions is quite different.
- Copy the pilight binding jar to your openhab addons directory
- Configure the pilight daemon in openhab.cfg
- Add controlable items to openhab .items file
- Use items in sitemap
This binding supports multiple pilight instances. You must set the .host and .port values. In pilight, you must explicitly configure this "port" or otherwise a random port will be used and the binding will not be able to connect.
#
# pilight:<instance name>.<parameter>=<value>
#
# IP address of the pilight daemon
#pilight:kaku.host=192.168.1.22
#
# Port of the pilight daemon
#pilight:kaku.port=5000
#
# Optional delay (in millisecond) between consecutive commands.
# Recommended value without band pass filter: 1000
# Recommended value with band pass filter: somewhere between 200-500
#pilight:kaku.delay=1000
openHAB 1.6
pilight="<instance>#<room>:<device>,property=value"
Room and device are the same as specified in your pilight config.json. The 'property=value' part is only needed for String and Number items.
Examples:
Switch KakuDeskLamp "Desk lamp" (Lamps) {pilight="kaku#study:desklamp"}
Switch KakuFloorLamp "Floor lamp" (Lamps) {pilight="kaku#study:floorlamp"}
Dimmer KakuCeiling "Ceiling" (Lamps) {pilight="kaku#living:ceiling"}
Number KakuTemperature "Temperature" (Sensors) {pilight="kaku#outside:weather,property=temperature"}
Number KakuHumidity "KakuHumidity [%.0f%%]" (Sensors) {pilight="kaku#outside:weather,property=humidity"}
String KakuBattery "Battery [%s]" (Sensors) {pilight="kaku#outside:weather,property=battery"}
openHAB 1.7
pilight="<instance>#<device>,property=value"
Device names are the same as specified in your pilight config.json. The 'property=value' part is only needed for String and Number items.
Examples:
Switch KakuDeskLamp "Desk lamp" (Lamps) {pilight="kaku#desklamp"}
Switch KakuFloorLamp "Floor lamp" (Lamps) {pilight="kaku#floorlamp"}
Dimmer KakuCeiling "Ceiling" (Lamps) {pilight="kaku#ceiling"}
Number KakuTemperature "Temperature" (Sensors) {pilight="kaku#weather,property=temperature"}
Number KakuHumidity "KakuHumidity [%.0f%%]" (Sensors) {pilight="kaku#weather,property=humidity"}
String KakuBattery "Battery [%s]" (Sensors) {pilight="kaku#weather,property=battery"}
Contact KakuDoorSensor "Door sensor [%s]" (Sensors) {pilight="kaku#doorsensor"}
Switch item=KakuDeskLamp
Switch item=KakuFloorLamp
Slider item=KakuCeiling
Text item=KakuTemperature
Text item=KakuHumidity
Text item=KakuBattery
Text item=KakuDoorSensor
For more information/questions:
###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