This shows you the differences between two versions of the page.
Next revision | Previous revision Last revision Both sides next revision | ||
philipshue [2016/07/07 13:19] wo_rasp created |
philipshue [2016/09/21 07:13] wo_rasp Added information regarding github source path |
||
---|---|---|---|
Line 8: | Line 8: | ||
Using the Hue Bridge allows smooth integration of pilight into the overall environment. | Using the Hue Bridge allows smooth integration of pilight into the overall environment. | ||
The concept of the Hue Bridge is found here: http://www.developers.meethue.com/documentation/core-concepts. | The concept of the Hue Bridge is found here: http://www.developers.meethue.com/documentation/core-concepts. | ||
- | The bridge itself is using the zigbee protocol to communicate with the Hue bulbs. This interface is currently not supported.\\ | + | The bridge itself is using the zigbee protocol to communicate with the Hue bulbs. The zigbee interface protocol is currently not supported directly, however this is not considered to be a shortcoming, as bypassing the Hue Bridge is basically not recommended.\\ |
+ | Until this protocol stack is integrated into the main pilight release, the updated development version is available at: | ||
+ | https://github.com/wo-rasp/pilight/tree/test_dev | ||
^Feature^Support^ | ^Feature^Support^ | ||
Line 16: | Line 18: | ||
To use all available settings for the bulbs you do need to use the CLI interface for the protocol ''philipshue'' and ''pilight-send'' or ''pilight-control''. \\ | To use all available settings for the bulbs you do need to use the CLI interface for the protocol ''philipshue'' and ''pilight-send'' or ''pilight-control''. \\ | ||
- | The pilight WEBGUI, supports a subset of the capabilities of Hue bulbs.\\ | ||
**Supported Brands** | **Supported Brands** | ||
Line 49: | Line 50: | ||
**Config** | **Config** | ||
+ | |||
+ | In the followng example, it is assumed that the IP address of the Hue Bridge is 192.168.0.252. | ||
1. Create a user on the Hue Bridge: | 1. Create a user on the Hue Bridge: | ||
Line 66: | Line 69: | ||
</code> | </code> | ||
- | or report the ''username'' generated: | + | or will report back the ''username'' generated: |
<code> | <code> | ||
- | $ pilight-send -p philipshue -i 192.168.1.252 --newuser | + | $ pilight-send -p philipshue -i 192.168.0.252 --newuser |
pilight-send: NOTICE: Create and authorize new user for pilight on Hue Bridge ... | pilight-send: NOTICE: Create and authorize new user for pilight on Hue Bridge ... | ||
pilight-send: NOTICE: philipshue - post data = {"devicetype":"pilight"} to url http://192.168.0.252/api | pilight-send: NOTICE: philipshue - post data = {"devicetype":"pilight"} to url http://192.168.0.252/api | ||
Line 76: | Line 79: | ||
You do need to copy the username to your config.json file. | You do need to copy the username to your config.json file. | ||
+ | <code> | ||
"devices": { | "devices": { | ||
"Hue1": { | "Hue1": { | ||
Line 154: | Line 158: | ||
$ pilight-control -d Hue1 -s off -v group=0 | $ pilight-control -d Hue1 -s off -v group=0 | ||
- | Apply scene | + | Apply a scene |
$ pilight-control -d Hue1 -s off -v scene=497b50d84-on-0 | $ pilight-control -d Hue1 -s off -v scene=497b50d84-on-0 | ||
Line 162: | Line 166: | ||
When you configure conflicting parameters, only one parameter is accepted, the priority is: | When you configure conflicting parameters, only one parameter is accepted, the priority is: | ||
- | - xy beats ct beats hue beats sat. | + | - xy beats ct, ct beats hue, hue beats sat. |
All lights act as a single repeater, if you need to extend your physical range, put a lamp inbetween. | All lights act as a single repeater, if you need to extend your physical range, put a lamp inbetween. | ||
- | Once a light is ON, it stays on, do not sent ON commands repetively, as it slows down the bridge. | + | Once a light is ON, it stays ON, do not sent ON commands repetively, as it slows down the bridge. |