Philips Hue Lights

[starwarsmike]

Hi

I see frcor has delay problems in sending commands to the lights. I also had this problem, sometimes a delay of 3-4 seconds. I had commands routed through a centro 8m, so I changed it, so commands are being sent direct from iPad to Hue lights. Bingo, no delay whatsoever.

Hopefully this may help others.


I now fixed this, the content length was set to 1000, whereas it only required 12, so i presume the Centro is waiting for the rest, hence the delay.

[cv27]

I have the majority of my commands routed through the Centro-8M and have so far experienced no delay, but no Philips Hue Lights.

It would be interesting to track down whether it simply was the Centro-8M starting the communication late or some latency during the IP conversation.

[mukundan_k]

need help on feedback if any one has done it may help us also

PUT /api/*****************/groups/2/action HTTP/1.1\x0D\x0AHost:192.168.1.xx\x0D\x0AContent-Length: 24\x0A\x0A{"effect":"colorloop"}

all commands or working including color loop

The content is the character count in the string, since they started to add more capability to the API they must have changed the way the hub processes this. As long as the content length was longer than the string it was fine, now it requires the exact length or it waits for more info...

So then content length of this command:
lights/1/state HTTP/1.1\x0AContent-Length: 1000\x0A\x0A{"on": true}
would be 12 derived from the part of the command in curly brackets including the Brackets {"on": true}

There are several string function web sites that calculate it for you I have been using this one:
http://string-functions.com/length.aspx

All my commands are back to normal now.

I have also added an update to my original post for anyone new trying to setup a Hue

" hello it was working for me before but after update its not working any more i'm willing to send my program if needed

[hengenl]

Yes it is very confusing. Mine stopped working too. Commands work through the Clip API Debugger. I tried to link the hue bridge again through a new password in The Clip API Debugger. Commands don't get send through Demopad. I even tried to send them through the "Test Command" button in Demopad Software without any chance.

[AKWillows]

Control of my Hue lights via Demopad has worked fine for a long time.

However, since updating the software on the Hue Hub to version 1802201122, it suddenly stopped working and has not worked since. Nothing else has changed.

I've not changed the commands sent since my earlier post e.g.

PUT /api/****/lights/1/state HTTP/1.1\x0AContent-Length: 12\x0A\x0A{"on": true}

Has anyone been able to resolve this? Something must have changed in the Hue software, but I cannot identify it and I've looked through the Hue API documentation and forums.

[hengenl]

Yes, here is the solution:


PUT /api/yourusername/lights/3/state HTTP/1.1\x0D\x0AHost:yourhueipadress\x0D\x0AContent-Length: 12\x0A\x0A{"on":true}


Cheers

[AKWillows]

Thanks! Will give that a go!

[AKWillows]

Worked perfectly! Thanks

[hengenl]

Perfect, you are welcome

[[email protected]]

Hi guys, I've got the command working but only for one light at a time. How do I do group of lights - all lights on, all lights off?

[AKWillows]

Hi guys, I've got the command working but only for one light at a time. How do I do group of lights - all lights on, all lights off?

If you register at https://developers.meethue.com then you will get access to the API which will show you all of the commands available including how to access groups/scenes etc. I knew nothing about all of this, but have learnt a lot using the guide and tools available there as well as help on this forum.

For example, once you have grouped lights in the Hue app, you can use a command like this to turn off a group of lights (replace xxxxxxxxxx and the IP address with your own details)

PUT /api/xxxxxxxxxxxx/groups/13/action HTTP/1.1\x0D\x0AHost:xxx.xxx.x.xx\x0D\x0AContent-Length: 13\x0A\x0A{"on": false}

Good luck!