Jump to content

Phillips Hue Support


ajiuo

Recommended Posts

  • 1 month later...
  • 3 weeks later...

I would like to add a me too to this thread. I am waiting for my ISY994iZS/IR PRO Smart Grid INSTEON / Zigbee Home Automation Controller to arrive tomorrow along with some INSTEON motion detectors and LEDs.

 

These hue bulbs are really cool in their ability to adjust the white temperature for different scenes (the colors are cool too, but more of a novelty IMO).

 

Correct me if I'm wrong but Zigbee compatibility seems to revolve around what Zigbee profiles are supported. In this case the ISY currently supports the Zigbee Smart Energy profile which should, theoretically make it compatible with any devices certified on that profile?

 

If that is basically the case then I would like to see Zigbee Light Link (which hue is certified under with only a couple of other devices), and then Zigbee Home Automation (which contains a bunch of certified sensors, switches, locks, and thermostats) added to the list of supported profiles.

 

Until then I would be happy to work with anyone on controlling the hues throughout their IP based controller and the ISY Network Module. There is definitely a web server present on the hue controller, but I am still waiting for Philips to release their SDK to open up the APIs. Does anybody here know if they exist yet, and if so, where I could get my hands on them?

Link to comment

Besides my front porch to change the lights for various holidays. And it might be cool to cycle the light through red white and blue for the 4th of july, green for saint patrics etc.

 

What other real world applications do you guys see using these under?

 

It was mentioned you could change the white color for various scenes.. don't know why I would want to do this.

 

Just need a little help seeing out of the box in my mind.

Link to comment

With the various white colors/temps you can make a big impact on the mood of the room. I will try to upload some pics once I get back to my PC and can shrink them down to meet the forum's 256k file limit.

 

I have one white to wake up to, another for the early evening and another when we are winding down and getting ready for bed.

 

With the proper programming, you should also be able to get them to flash different colors for "alarm" events. For example - strobe red if the alarm is triggered, or flash green when the alarm is disarmed, fade to an icy blue if the temp outside is below 40 and a window is open or a door left open for more than 30 seconds, flash yellow once an hour if a sensor sends a low battery event. There are a lot of possibilities in how the lights can communicate the status of the home/room.

 

I would imagine that the value would be even greater for people who are hearing impaired.

Link to comment

I got my ISY today and was able to control the HUE lights using the network module and the great help from the resources at everyhue.com

 

THING'S YOU'LL NEED:

1. You Hue Controller local IP address

 

You can get you Hue Controller IP by logging into your hue account at meethue.com, clicking on My Hue and My Settings in the upper right hand corner of the page.

 

Then click on My Bridge and look for "Internal IP address"

 

2. An API key from the controller for access

 

I got mine on my Mac by opening up the terminal and typing:

 

curl -d "{\"username\": \"yourname\", \"devicetype\": \"yourhuename\"}" http://YOUR_HUE_IP_HERE/api

 

Make sure you save the key that is returned as that will go in the path of ALL you http PUT/GETs.

 

Here is a snippet of the Network Resource export that might help others have similar success. This one turns on light #1:

PUT /api/YOUR_API_KEY_HERE/lights/1/state HTTP/1.1
Host: YOUR_HUE_IP_HERE:80
User-Agent: Mozilla/4.0
Connection: Close
Content-Type: application/x-www-form-urlencoded
Content-Length: 12

{"on": true}

 

The equivalent terminal command would be:

 

curl -X PUT -d '{"on": true}' http://YOUR_HUE_IP_HERE/api/YOUR_API_KEY_HERE/lights/1/state

 

You can turn on all of the lights by accessing the built in group 0 on the controller:

 

PUT /api/YOUR_API_KEY_HERE/groups/0/action HTTP/1.1
Host: YOUR_HUE_IP_HERE:80
User-Agent: Mozilla/4.0
Connection: Close
Content-Type: application/x-www-form-urlencoded
Content-Length: 12

{"on": true}

 

These settings will set ALL bulbs to the "Relax" settings in My Hue at max brightness. Please REMEMBER to replace your IP and KEY with the one's shown (mine):

 

Get_All_Warm.jpg

 

You can get the full state of the controller and all attached bulbs with the following command:

 

Get_State_All.jpg

 

 

I hope this helps you all get started!

Link to comment

So I guess the next question is ...

 

Since there IS a way to query AND set the state of the bulbs through HTTP, is there a way to parse that information back into the ISY so that it can show them as devices? If so, could I please get pointed in the right direction?

Link to comment

Absolutely, please link away.

 

Michel -

 

Is there any way to get data back into the ISY through the network module or some other method?

 

I wouldn't mind trying to do the coding if I could just get a gentle push in the right direction. My end-game would be to get the hue bulbs and controller represented as first-class devices just like their insteon counterparts.

Link to comment

Just a few updates, the bridge does apparently support grouping (there have been reports of bugs such as needing to reboot the controller after defining one). Both WinVue and Hue Lights Controller (about $10) now supports creating groups. Once created you can update the examples here to control a group at once instead of per device. Simply use the syntax /api/YOURKEY/groups/1/action and the same commands you were using before for the body. This seems to work much faster as group commands are broadcasted (much like an insteon scene) vs one device at a time.

Link to comment
  • 1 month later...

Very cool with lots of interesting possibilities.

 

Anyone know if I can use an insteon switch on a fixture with one or more of these bulbs? Specifically, am wondering if I can set a "hue" scene, i.e. bulb color, then turn off my insteon switch and have the same scene/color come on next time I turn the switch on, without having to use my ipod/iphone/ipad. What about setting it to a dim level?. I realize at minimum that a change of "hue" scenes would not work if the switch was off since the bulbs would not have power.

 

In part I'm wondering if I can turn my Hue lights on (or dim?) without pulling out my ipod/ipad; and in part I"m wondering if I can have a "failsafe" situation where I can turn my switch on and the lights work to the last setting/scene even if ISY or the Hue bridge is not working. (ISY not working would only be because I pulled it out, of course)

 

Does what I'm asking make sense?

Link to comment
Very cool with lots of interesting possibilities.

 

Anyone know if I can use an insteon switch on a fixture with one or more of these bulbs? Specifically, am wondering if I can set a "hue" scene, i.e. bulb color, then turn off my insteon switch and have the same scene/color come on next time I turn the switch on, without having to use my ipod/iphone/ipad. What about setting it to a dim level?. I realize at minimum that a change of "hue" scenes would not work if the switch was off since the bulbs would not have power.

 

In part I'm wondering if I can turn my Hue lights on (or dim?) without pulling out my ipod/ipad; and in part I"m wondering if I can have a "failsafe" situation where I can turn my switch on and the lights work to the last setting/scene even if ISY or the Hue bridge is not working. (ISY not working would only be because I pulled it out, of course)

 

Does what I'm asking make sense?

 

What your asking for makes total sense. I've been working on implementing a ISY to Hue interface running on a RaspberryPi. I have an initial version running controlling Hue lights at two homes. A couple thoughts on how I've approached this:

 

I took the existing switchlincs that controlled the light and rewired them so the load was always on. I then added a inlinelinc (and in two cases the micro on/off switches). These act as 'emergency' power control in case the bridge dies or I really want to turn power off the Hues. The first thing you have to wrap your head around is you really want power to the bulbs 24/7 since they form a mesh network, and then trust the automation system to the LED portion of the unit on/off as needed.

 

In my RaspeberryPi config code I define scenes (sets of light or groups of lights) and what their actions should be. I also define an ISY variable to 'track' the state of each room. I also tied in the switchlinc address into the config so I have two control options, if I use the switch linc the code sees this (it subscribes to events from the ISY). It takes the on/off commands and turn the Hues on/off. If the light is already on and you hit on again it cycles through to the next scene looping through all of the scenes if you continue to press 'on'.

 

For one keypad I programmed it to always on mode and then use each on to update the variable I mentioned above. When the variable changes the code does the same 'go to next scene'. For off I tied it to the rest of the room lights being off (or the off button on the same keypad linc being turned off twice (fast off)). If for some reason you need multiple bridges I current support an unlimited number (I may need to have separate ones at one house at some out buildings may not be worth getting zigbee repeaters vs just a second or third bridge for those areas)

 

If you don't mind throwing a RaspberryPi into your mix I should have a shareable version ready in a week or two. For the 100 or so a raspberry costs (unit, case, bluetooth, wireless) I find they are making the perfect little ISY companion.

 

Below is the actual config for the Hue system, it's developer friendly right now a little less end user friendly (I eventually plan to write an editor to help set everything up)

 

 

[Configuration]

Default=2

 

[Hue1]

IP=10.0.0.236

Key=6bae8d5b0a229b42669a129a6475bba20f79f94f

 

[Hue2]

IP=10.1.0.182

Key=5e18c2b33120289386bd6bd2b5242c084913e9eb

 

[Hue_Scenes]

Off=1:{"on":false}

Default=1:{"on":true,"bri":254,"ct":400}

Reading=1:{"on":true,"bri":198,"ct":469}

Concentration=1:{"on":true,"bri":219,"ct":233}

Energize=1:{"on":true,"bri":203,"ct":156}

Relax=1:{"on":true,"bri":144,"hue":13122,"sat":211,"xy":[0.5119,0.4147],"ct":469}

Sunset=1:{"on":true,"bri":110,"xy":[0.5913,0.3288]};2:{"on":true,"bri":165,"xy":[0.212,0.1286]};3:{"on":true,"bri":254,"xy":[0.5954,0.3717]}

Movie=1:{"on":true,"bri":54,"xy":[0.22,0.1445]}

Night=1:{"on":true,"bri":7,"xy":[0.6354,0.3260]}

DarkBlue=1:{"on":true,"colormode":"hs","bri":196,"hue":46421,"sat":254}

 

 

[Hue1_Control]

1=18.0.b2.1;4.30.9e.1;20.4c.59.1, Familyroom

2=5.5.5.1, Masterbedroom

 

[Hue1_Params_Masterbedroom]

Variable=5

Favorite=7

 

[Hue1_Set_Masterbedroom]

1=Off,1

2=Default,1

3=Reading,1

4=Concentration,1

5=Relax,1

6=Sunset,2-4

7=Movie,1

8=Night,1

 

[Hue1_Params_Familyroom]

Variable=16

Favorite=7

 

[Hue1_Set_Familyroom]

1=Off,5

2=Default,5

3=Reading,5

4=Concentration,5

5=Relax,5

6=Sunset,6-8

7=Movie,5

8=Night,5

 

[Hue2_Control]

1=19.3e.0.5, TvRoom

2=1c.98.9d.1;1b5b.32.1, Masterbedroom

3=1c.8f.b5.1, ArtNook

 

[Hue2_Params_Masterbedroom]

Variable=54

Favorite=7

 

[Hue2_Set_Masterbedroom]

1=Off,1

2=Default,1

3=Reading,1

4=Concentration,1

5=Relax,1

6=Sunset,2-4

7=Movie,1

8=Night,1

 

[Hue2_Params_TvRoom]

Variable=55

Favorite=6

 

[Hue2_Set_TvRoom]

1=Off,5

2=Default,5

3=Reading,5

4=Concentration,5

5=Relax,5

6=Movie,5

7=Night,5

 

[Hue2_Params_ArtNook]

Variable=56

Favorite=1

 

[Hue2_Set_ArtNook]

1=Off,L9

2=DarkBlue,L9

Link to comment

Hi bsobel,

 

Yes I would be interested in what you have to share. In principle would I be able to run it on a different linux box? I do think the Pi is very cool and may very well get one but to get started I would like to try putting up a linux VM on my existing VMware "home lab", which runs the free version of ESXiServer 5.0.

 

One of the first things I queried was the possibility of having more than one bridge and the fact your setup can support that is also cool. I'm actually hoping that could make up for not having the bulbs on 24/7 to create the mesh network that would extend a single bridge's reach.

 

I'm not envisioning right now why one would need to add an inlinelinc and one or more micro switches. It seems kind of expensive to have to buy 3+ insteon devices for each Hue equipped fixture I want to control. I realize it's part of making things fail safe, but can you walk through how things would work when ISY/Pi/bridge are down so I can visualize the role of these extra device?

 

Thanks so much for the info.

Link to comment

I am interested too. My Pi is on order to cook in Lirc support so I can use non learning remotes with my isy and do some scenes and actions based on the real life buttons we use.

 

Maybe if enough of us go Pi, Michael can finish on his wishlist a conversion of the code to linux, drop his hardware costs, and increase the flexibility of the ISY ongoing. We could have mutliple "radio" support via a hub and usb to zigbee, zwave, wireless etc. :lol:

Link to comment
Hi bsobel,

Yes I would be interested in what you have to share. In principle would I be able to run it on a different linux box? I do think the Pi is very cool and may very well get one but to get started I would like to try putting up a linux VM on my existing VMware "home lab", which runs the free version of ESXiServer 5.0.

One of the first things I queried was the possibility of having more than one bridge and the fact your setup can support that is also cool. I'm actually hoping that could make up for not having the bulbs on 24/7 to create the mesh network that would extend a single bridge's reach.

I'm not envisioning right now why one would need to add an inlinelinc and one or more micro switches. It seems kind of expensive to have to buy 3+ insteon devices for each Hue equipped fixture I want to control. I realize it's part of making things fail safe, but can you walk through how things would work when ISY/Pi/bridge are down so I can visualize the role of these extra device?

Thanks so much for the info.

 

Hi,

 

First off, should run on any box with Python. Have only tested on the RPi so far (moving to that as my bluetooth detector platform so shoving as much else onto it as I can).

 

As for the inlinelinc or microswitches, I added one per group of lights (e.g. my master bedroom has 6 so I added one inline linc that controls power to all of them, not each bulb). The current Hue firmware does not resume to the last bulb state when power is applied but rather to a 'white' light. Its a bit jarring of an effect especially at night if you have something like a nightlight scene setup. If it is something like a table lamp (where you have a manual switch) then I'd just leave it powered 24/7 and rely on the switch or cord as the backup. They really are designed to be left powered and the integration is much much (much!) more seamless when they are. Any startup delays (while the zigbee network stablizes for example) go away. The effect from hitting the Insteon switch to 'on' is very natural, when I added the delays for when the power was off it took about 2 seconds (full bright light, then network stabilize, then switch to correct scene).

 

If the isy and bridge are down, currently you would be stuck. If bridge is down cycling the power (via isy or manually) gives you the normal white default state. If the ISY was down then you could use other apps (iphone etc) as a backup. I honestly don't have a better solution yet for if my ISY is down (all kinds of bad happens around here when that occurs ,))

Link to comment

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...