{"id":8065,"date":"2020-04-03T21:22:54","date_gmt":"2020-04-03T21:22:54","guid":{"rendered":"http:\/\/putridparrot.com\/blog\/?p=8065"},"modified":"2020-04-03T21:22:54","modified_gmt":"2020-04-03T21:22:54","slug":"controlling-a-philips-hue","status":"publish","type":"post","link":"https:\/\/putridparrot.com\/blog\/controlling-a-philips-hue\/","title":{"rendered":"Controlling a Philips Hue"},"content":{"rendered":"

First off, the Philips Hue bridge exposes a web server, so take a look at the wireless connections on your network (see also How to develop for Hue<\/a>) for other methods of locating your Hue bridge on the network.<\/p>\n

Much of the information in this post is taken from How to develop for Hue?<\/a>. More information is available if you register as a Philips Hue developer.<\/p>\n

Once you’ve located your bridge IP address you can use a web browser to connect the CLIP API Debugger, i.e.<\/p>\n

\r\nhttps:\/\/<bridge ip address>\/debug\/clip.html\r\n<\/pre>\n
The Hue bridge API<\/strong><\/p>\n
The first thing we need to do is a key for interacting with the device. The Hue actually calls this your username and it’s a randomly generated string, once we have this we have an authorise user. <\/p>\n
So for example if you try to use any command without a key you’ll get a response along the following lines<\/p>\n
\r\n[\r\n  {\r\n    "error": {\r\n      "type": 1,\r\n      "address": "\/",\r\n      "description": "unauthorized user"\r\n    }\r\n  }\r\n]\r\n<\/pre>\n
Creating our user<\/em><\/strong><\/p>\n
To get our username and thus create an authorized user, we use the following API<\/p>\n