Frequently Asked Questions

Thanks for visiting our frequently asked questions page.

Performance

Why is it taking so long for my hue lights to respond?

When you set the light state, and update color, brightness etc., the light will not respond immediately because by default there is a transition time to the new state of 400 milliseconds. If you want the light to respond quickly to a state change, set the transition time in the light state to zero milliseconds.

Why are only some of my lights responding to my app?

All the lights have to be in range. If you can control them from the hue app then you’re fine to play with them via the developer interface. Remember all lights act as a signal repeater, so if you want more range, put a light in between.

Why is the bridge response so slow?

Don’t always send ‘ON’ Once you have sent the ‘ON’ attribute to a light, it will stay on. Do not repeatedly send the ‘ON’ command as this will slow the responsiveness of the bridge.

How many commands you can send per second?

You can send commands to the lights too fast. If you stay roughly around 10 commands per second to the /lights resource as maximum you should be fine. For /groups commands you should keep to a maximum of 1 per second.

Color and state

How do I set color?

For more info on setting color, see our section on Color Theory.

I want to use RGB, how do I set color using RGB?

Please see our page on converting RGB to XY values

Tools and commands

What tools can I use to build my app?

There are multiple ways for your app to control the hue system. The hue API is a RESTful interface, which can be accessed by many languages. In addition, we provide SDKs for IOS, OSX, Java multi-platform and Android. Third party developers have created a number of other tools and SDKs for different languages. Refer to hue API documentation, IOS and OSX SDK, Java multi-platform and Android SDK, list of third party SDKs and tools.<<Make these links

Where is the API located?

The hue API in the bridge is accessible on your local network. That is to say, it is accessible on your local WiFi or wired network and cannot be accessed directly outside that network. This also makes your hue system secure. The hue bridge, once installed on your network, will have its own IP address set up by your local router. This is the IP address you will use when sending commands to the RESTful API.

Can I get remote access to hue (e.g. other than IFTTT)?

It is planned that we will have a remote API for accessing hue across the Internet. For now the only option available is to use the IFTTT interface.

How do I try out sending API commands to the bridge?

Every bridge has a debug tool, which you can use directly to send API commands to the bridge and see results. This can be found at http://<bridge ip address>/debug/clip.html. See Getting started for more information.

When do I use groups API vs lights API?

When updating light attributes, unless there are a dozen or more lights it is generally more efficient to use the lights API. With larger numbers of lights, it can be more efficient to access them as a group, using the groups API.

How can I make sure my app has access to the bridge?

The bridge secures access from apps by using a whitelist. To add your app to the whitelist you will need to request the bridge to do so using the create user command in the Configuration API, and then the push linking button must be pressed too. This is a way of securing access to the hue system and preventing apps that haven’t been given permission by push linking.