Search the Community

SEE https://emby.media/community/index.php?/topic/44781-plugin-for-controlling-hue-light/&do=findComment&comment=494774 for latest update I have a plugin to control Hue lights. There's a bit of manual setup that is required on the Hue bridge, but if there is an audience that would be interested I can add bridge discovery and light configuration to the plugin config page. You will need to get a User Id, Group Id and Scene Id from the Hue bridge to complete configuration: A. Get Bridge User API: (source: https://developers.meethue.com/documentation/getting-started ) Step 1 First make sure your bridge is connected to your network and is functioning properly. Test that the smartphone app can control the lights on the same network. Step 2 Then you need to discover the IP address of the bridge on your network. You can do this in a few ways. Use a UPnP discovery app to find Philips hue in your network. Use our broker server discover process by visiting www.meethue.com/api/nupnp Log into your wireless router and look Philips hue up in the DHCP table. Hue App method: Download the official Philips hue app. Connect your phone to the network the hue bridge is on. Start the hue app(iOS described here). Push link connect to the bridge. Use the app to find the bridge and try controlling lights. All working -- Go to the settings menu in the app. Go to My Bridge. Go to Network settings. Switch off the DHCP toggle. The ip address of the bridge will show. Note the ip address, then switch DHCP back on N.B When you are ready to make a production app you will need to discover the bridge automatically using the Hue Bridge Discovery Guide or the tools provided with the official Philips hue SDKs Step 3 Once you have the address load the test app by visiting the following address in your web browser. http://<bridge ip address>/debug/clip.html You should see an interface like this. Using this debugger utility you can populate the components of an HTTP call – the basis of all web traffic and of the hue RESTful interface. URL: this is actually the local address of a specific resource (thing) inside the hue system. It could be light, a group of lights or many more things. This is the object you’ll be interacting with in this command. A body: this is the part of the message which describes what you want to change and how. Here you enter, in JSON format, the resource name and value you’d like to change/add. A method: here you have a choice of the 4 HTTP methods the hue call can use. GET: this is the command to fetch all information about the addressed resource PUT: this is the command to modify an addressed resource POST: this is the command to create a new resource inside the addressed resource DELETE: this is the command to deleted the addressed resource Response: In this area you’ll see the response to your command. Also in JSON format. So let’s get started… First let’s do a very simple command and get information about your hue system. Fill in the details below leaving the body box empty and press the GET button. Address http://<bridge ip address>/api/newdeveloper Body Method GET You should see a response like below: Congratulations you’ve just sent you first CLIP command! Now this is the command to fetch all information in the bridge. You didn’t get much back and that’s because you’re using an unauthorized username “newdeveloper”. Currently it is possible to create your own usernames in the bridge (e.g. “newdeveloper”), however, this option will be removed in future bridge versions, so we need to use the randomly generated username that the bridge creates for you. Fill in the info below and press the POST button. Address http://<bridge ip address>/api Body {"devicetype":"my_hue_app#iphone peter"} Method POST This command is basically saying please create a new resource inside /api (where usernames sit) with the following properties. When you press the POST button you should get back an error message letting you know that you have to press the link button. This is our security step so that only apps you want to control your lights can. By pressing the button we prove that the user has physical access to the bridge. Go and press the button on the bridge and then press the POST button again and you should get a success response like below. Congratulations you’ve just created an authorized user (1028d66426293e821ecfd9ef1a0731df), which we’ll use from now on! Now if you do the first GET command again you should get a whole lot more information about what lights you have and their states. This data is all in JSON format so can be easily processed by your applications. B. Create Light Group Use the same CLIP application and send a GET request to http://<bridge ip address>/api/<username from step A>/lights to find the id numbers for the lights you want to control. Create the group by sending a POST request to http://<bridge ip address>/api/<username from step A>/groups With Message Body: { "lights": [ "1", "2" ], "name": "Theater", "type": "LightGroup" } where "lights" contains the light ids you want to control. The ID returned in the response body is the group ID to use. C. Create Scene ID Create the scene ID by sending a POST request to http://<bridge ip address>/api/<username>/scenes/ With a Message Body {"name":"EmbyCache", "lights":["1","2"], "recycle":true} with the same light ids used in b. Note the id in the response and use this as the scene id in the plugin configuration page. HueControl.zip

Hi guys! Just bought some philips hue lights (still waiting for them to arrive), and then I got this thing in my head: What if MB3 could controll these lights and make them change color based on the backdrops (picks 2-4 points in the picture to reproduce that color, like the philips app does) Automatically dims the lights off when a movie start, and turn them back on when the movie is finished. (when externalplayer closes / when MBT stops playing). This would be super cool, and would fit MB3 very good! There is also alot more we could do with this, with pre defined scenes etc.. What do you guys think?