-
Notifications
You must be signed in to change notification settings - Fork 37
Manual bridge configuration
There may be cases where the automatic bridge discovery fails and you will have to manually provide the information for Kelvin to talk to your hue bridge. This information consists of two parts:
- The
IP Address
of the hue bridge in your local network - A
Username
for authentication that was generated by the Hue bridge
The following sections will help you to obtain the two bits of information. Once you acquired them you will have to enter then into your config.json
manually.
Since network configurations can be vastly different, there is more than one way to identify the address of your bridge. I would recommend you try the following steps in their particular order.
- Open http://www.meethue.com/api/nupnp in your browser.
- Get the address from the hue app on your smartphone (Navigate to "Settings" -> "Hue bridges" -> "Info" -> "Network settings" -> toggle the button "DHCP", don't forget to switch "DHCP" back on.)
- Check the configuration in your wireless router.
Kelvin will need the username to authenticate itself at your hue bridge. This way only valid applications will be allowed to read and modify your light states. To manually register a valid user on your bridge you should take the following steps:
- Enter
http://<bridge ip address>/debug/clip.html
into your internet browser. - Enter the string
/api
into the "URL" field. - Enter the string
{"devicetype":"kelvin"}
into the "Message Body" field. - Press the blue link button on your physical hue bridge.
- Back in your browser click on the "POST" button.
- The "Command Response" field should now contain a text similar to:
[
{
"success":{
"username": "1028d66426293e821ecfd9ef1a0731df"
}
}
]
- Copy the string after
username
(in this example1028d66426293e821ecfd9ef1a0731df
) into yourconfig.json
.