-
Notifications
You must be signed in to change notification settings - Fork 0
Milight Binding
Documentation of the Milight binding bundle
The openHAB Milight binding allows to send commands to multiple Milight bridges. For installation of the binding, please see Wiki page Bindings.
##API v3.0 additions for RGBW bulbs are available with openHAB release 1.4.0
First of all you need to introduce your Milight bridge(s) in the openhab.cfg file (in the folder '${openhab_home}/configurations')
################################ Milight Binding #################################
# Host of the first Milight bridge to control
# milight:<MilightId1>.host=
# Port of the bridge to control (optional, defaults to 50000)
# milight:<MilightId1>.port=
#
# Host of the second Milight bridge to control
# milight:<MilightId2>.host=
# Port of the bridge to control (optional, defaults to 50000)
# milight:<MilightId2>.port=
The milight:<MilightId1>.host
value is the ip address of the Milight bridge.
The milight:<MilightId1>.port
value is UDP port address of the Milight bridge. Port value is an optional parameter but has to be changed for the V3.0 version of milight bridge.
Examples, how to configure your receiver device:
milight:bridge1.host=192.168.1.100
milight:bridge1.port=50000
In order to bind an item to the 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:
milight="<deviceId>;<channelNumber>;<commandType>;<steps>"
where <commandType>
is optional for switch items, unless you want to use commandType nightMode, whiteMode or set dimming steps.
The device-id corresponds to the bridge which is defined in openhab.cfg.
The channelNumber corresponds to the bulbs/channels on your bridge, where 0 reflects all white bulbs, 1-4 white bulb channels 1-4 and 5 all rgb bulbs. For the new RGBW bulbs uses channel numbers 6 (all RGBW bulbs), 7-10 (RGBW channels 1 to 4)
The deviceCommand corresponds to the way you want to control your Milight bulbs.
Valid command types for white bulbs:
brightness controls the brightness of your bulbs
colorTemperature changes from cold white to warm white and vice versa
nightMode dimms your bulbs to a very low level to use them as a night light
Command types for rgb bulbs:
rgb changes the color and brightness of your rgb bulbs
discoMode changes the discoMode for rgb bulbs
discoSpeed changes the speed of your chosen discoMode
The following command is valid vor RGBW bulbs only :
whiteMode sets RGBW bulbs to white mode
<steps>
is valid for RGBW bulbs only and has to be used with commandType=brightness
.
This optional setting can be used if your RGBW bulbs are not dimming in 30 steps as this is the default.
Limitations: The rgb bulbs do not support changing their saturation, so the colorpicker will only set the hue and brightness of it.
Examples, how to configure your items in your items file:
Switch Light_Groundfloor {milight="bridge1;0"} #Switch for all white bulbs on bridge1
Switch Light_GroundfloorN {milight="bridge1;0;nightMode"} #Activate the NightMode for all bulbs on bridge1
Dimmer Light_LivingroomB {milight="bridge1;1;brightness"} #Dimmer changing brightness for bulb1 on bridge1
Dimmer Light_LivingroomC {milight="bridge1;1;colorTemperature"} #Dimmer changing colorTemperature for bulb1 on bridge1
Dimmer RGBW_LivingroomB {milight="bridge1;7;brightness;27"} #Dimmer changing brightness for RGBW bulb1 on bridge1 with 27 dimming steps
Color Light_Party {milight="bridge2;5;rgb"} #Colorpicker for rgb bulbs at bridge2
The command types discoMode and discoSpeed should be configured as pushbuttons as they only support INCREASE and DECREASE commands:
items:
Dimmer DiscoMode {milight="bridge1;5;discoMode"}
Dimmer DiscoSpeed {milight="bridge1;5;discoSpeed"}
sitemap:
Switch item=DiscoMode mappings=[DECREASE='-', INCREASE='+']
Switch item=DiscoSpeed mappings=[DECREASE='-', INCREASE='+']
Disco Mode for RGBW bulbs can only be stepped in one direction, so please use INCREASE command only for those.
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