Hue-connection not working

Avatar
Peter Edwards
  • updated
  • Under review

Got my hue-lights home today and started connecting them towards bOS. Sadly, the integration is broken.


When doing a wireshark-trace it´s obvious that bOS tries to connect to the hue bridge with user "ComfortClick" - no matter what username you specify in the configure-wizard.


The HUE API states that fixed usernames should not be used anymore as the are "soon" to be deprecated from the API. I guess that day has arrived - I tried to create a new user manually through the API but only got a json back with "username is not a valid command" or something like that.

Replies 15
Avatar
0
Peter Edwards

Also - only to verify I connected the bridge against my OpenHAB deployment. That worked out of the box - was up and running in less than 30 seconds.


I believe that the user-creation part of the connection needs to be rewritten.

Avatar
0
ComfortClick Support
  • Under review

Hello,


try using the user name "ComfortClick". We will fix this issue in the next update.


Regards,

Avatar
0
Peter Edwards

The problem is that its not possible to create a user with a fixed/user-defined name anymore. The correct method is to declare an application & device and then let the Hue-bridge return a random username to the application. This is done by doing a POST with body like {"devicetype": "ComfortClick_app#ComfortClick_srv"} to http://<bridge-ip>/api


A random username will be returned in the 200 response from the bridge. This should be used by the application.


I got this to work by creating a user manually through the API and specifyed the username i got in return in bOS. After a reload of the server I saw that the correct user was used when accessing the bridge - and my devices could be discovered and used. So, currently there is a workaround, but its far from pretty.. ;)


Regards,

Peter


Avatar
0
Vidar Vestbø

I can't connect to my Hue. I have 2'nd generation bridge. I upgraded bOS to the newest version recently. The funny thing is that bOS found my bridge the first time I tried, but the config stopped after a few steps. Then I had to manually shut down. After I've got it up and running again the Hue bridge is not discovered anymore


I got my Hue light's to work using HTTP: device PUT command. But it not ideal.

My put command:

Host url: http://192.168.1.201/api/ltqwwQjAVp5I88s9fcCAHUvvlIxcNyugeZGN5UE4/lights/1/state

PUT command: {"on":%0, "bri":%1}


Best regards

Vidar Vestbø

Avatar
0
Tilen Suhadolnik

What do you get when you visit https://www.meethue.com/api/nupnp ?

Avatar
0
Vidar Vestbø
Quote from Tilen Suhadolnik

What do you get when you visit https://www.meethue.com/api/nupnp ?

[{"id":"xxxxxxxxxxxxxxxxx","internalipaddress":"192.168.1.201"}]

Avatar
0
Tilen Suhadolnik

Are you using Windows XP?

If so, please try it on the newest version of Windows as Windows XP is not supported anymore.

Avatar
0
Vidar Vestbø
Quote from Tilen Suhadolnik

Are you using Windows XP?

If so, please try it on the newest version of Windows as Windows XP is not supported anymore.

No. I'm using Win7

Avatar
0
Fred Hartman

I'm not sure if this helping you, but did you disable DHCP in het HUE bridge software. In case you've another device set to DHCP server, it will conflict with the HUE bridge.

Avatar
0
Vidar Vestbø
Quote from Fred Hartman

I'm not sure if this helping you, but did you disable DHCP in het HUE bridge software. In case you've another device set to DHCP server, it will conflict with the HUE bridge.

I disabled DHCP in Hue bridge, still no connection.


Customer support portal powered by UserEcho