# Philips Hue Binding

This binding integrates the Philips Hue Lighting system. The integration happens through the Hue bridge, which acts as an IP gateway to the ZigBee devices.

# Supported Things

The Hue bridge is required as a "bridge" for accessing any other Hue devices.

Almost all available Hue devices are supported by this binding. This includes not only the "friends of Hue", but also products like the LivingWhites adapter. Additionally, it is possible to use OSRAM Lightify devices as well as other ZigBee LightLink compatible products. Please note that the devices need to be registered with the Hue bridge before it is possible for this binding to use them.

The Hue binding supports all seven types of lighting devices defined for ZigBee LightLink (see page 24, table 2. These are:

All different models of Hue, OSRAM, or other bulbs nicely fit into one of these seven types. This type also determines the capability of a device and with that the possible ways of interacting with it. The following matrix lists the capabilities (channels) for each type:

Beside bulbs and luminaires the Hue binding supports some ZigBee sensors. Currently only Hue specific sensors are tested successfully (e.g. Hue Motion Sensor and Hue Dimmer Switch). The Hue Motion Sensor registers a ZLLLightLevel sensor, a ZLLPresence sensor and a ZLLTemperature sensor in one device.

The type of a specific device can be found in the configuration section for things in the PaperUI. It is part of the unique thing id which could look like:

hue:0210:00178810d0dc:1

The thing type is the second string behind the first colon and in this example it is 0210.

# Discovery

The Hue bridge is discovered through UPnP in the local network. Once it is added as a Thing, its authentication button (in the middle) needs to be pressed in order to authorize the binding to access it. Once the binding is authorized, it automatically reads all devices that are set up on the Hue bridge and puts them into the Inbox.

# Thing Configuration

The Hue bridge requires the IP address as a configuration value in order for the binding to know where to access it. In the thing file, this looks e.g. like

Bridge hue:bridge:1 [ ipAddress="192.168.0.64" ]

A user to authenticate against the Hue bridge is automatically generated. Please note that the generated user name cannot be written automatically to the .thing file, and has to be set manually. The generated user name can be found in the log files after pressing the authentication button on the bridge. The user name can be set using the userName configuration value, e.g.:

Bridge hue:bridge:1 [ ipAddress="192.168.0.64", userName="qwertzuiopasdfghjklyxcvbnm1234" ]

# Devices

The devices are identified by the number that the Hue bridge assigns to them (also shown in the Hue App as an identifier). Thus, all it needs for manual configuration is this single value like

0210 bulb1 [ lightId="1" ]

or

0107 motion-sensor [ sensorId="4" ]

# Channels

The devices support some of the following channels:

# Trigger Channels

The dimmer switch additionally supports a trigger channel.

The event can trigger one of the following events:

# Full Example

In this example Bulb1 is a standard Philips Hue bulb (LCT001) which supports color and color_temperature. Therefore it is a thing of type 0210. Bulb2 is an OSRAM tunable white bulb (PAR16 50 TW) supporting color_temperature and so the type is 0220.

# demo.things:

Bridge hue:bridge:1 [ ipAddress="192.168.0.64" ] {
	0210 bulb1 [ lightId="1" ]
	0220 bulb2 [ lightId="2" ]
	0106 light-level-sensor [ sensorId="3" ]
	0107 motion-sensor [ sensorId="4" ]
	0302 temperature-sensor [ sensorId="5" ]
	0820 dimmer-switch [ sensorId="6" ]
}

# demo.items:

// Bulb1
Switch	Light1_Toggle		{ channel="hue:0210:1:bulb1:color" }
Dimmer	Light1_Dimmer		{ channel="hue:0210:1:bulb1:color" }
Color	Light1_Color		{ channel="hue:0210:1:bulb1:color" }
Dimmer	Light1_ColorTemp	{ channel="hue:0210:1:bulb1:color_temperature" }
String	Light1_Alert		{ channel="hue:0210:1:bulb1:alert" }
Switch	Light1_Effect		{ channel="hue:0210:1:bulb1:effect" }

// Bulb2
Switch	Light2_Toggle		{ channel="hue:0220:1:bulb2:brightness" }
Dimmer	Light2_Dimmer		{ channel="hue:0220:1:bulb2:brightness" }
Dimmer	Light2_ColorTemp	{ channel="hue:0220:1:bulb2:color_temperature" }

// Light Level Sensor
Number:Illuminance LightLevelSensorIlluminance { "channel="hue:0106:light-level-sensor:illuminance" }

// Motion Sensor
Switch   MotionSensorPresence     { channel="hue:0107:motion-sensor:presence" }
DateTime MotionSensorLastUpdate   { channel="hue:0107:motion-sensor:last_update" }
Number   MotionSensorBatteryLevel { channel="hue:0107:motion-sensor:battery_level" }
Switch   MotionSensorLowBattery   { channel="hue:0107:motion-sensor:battery_low" }

// Temperature Sensor
Number:Temperature TemperatureSensorTemperature { "channel="hue:0302:temperature-sensor:temperature" }

Note: The bridge ID is in this example 1 but can be different in each system.

# demo.sitemap:

sitemap demo label="Main Menu"
{
	Frame {
		// Bulb1
		Switch		item=		Light1_Toggle
		Slider		item=		Light1_Dimmer
		Colorpicker	item=		Light1_Color
		Slider		item=		Light1_ColorTemp
		Switch		item=		Light1_Alert		mappings=[NONE="None", SELECT="Alert", LSELECT="Long Alert"]
		Switch		item=		Light1_Effect

		// Bulb2
		Switch		item=		Light2_Toggle
		Slider		item=		Light2_Dimmer
		Slider		item=		Light2_ColorTemp

		// Motion Sensor
		Switch item=MotionSensorPresence
		Text item=MotionSensorLastUpdate
		Text item=MotionSensorBatteryLevel
		Switch item=MotionSensorLowBattery
	}
}

# Events

rule "example trigger rule"
when
   Channel "hue:0820:dimmer-switch:dimmer_switch_event" triggered <EVENT>
then
   ...
end