You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work for Philips Hue Developer Support. In case you were not aware, in a few months time we will be changing the way usernames are created on the bridge (for security reasons). Custom whitelist usernames will no longer be allowed and the bridge randomly generated username must be used instead. Please see below link for more information: http://www.developers.meethue.com/documentation/important-whitelist-changes
I must confess I don't really understand Objective-C code, but I can see in the registerUser method (line 52 in DPHue.m) you are setting the username in your JSON body. After February 2016 this will have no effect. The username should be removed and instead the randomly generated username in the bridge response should be used instead (the above link should hopefully clarify the changes needed). Apologies for the inconvenience.
Thanks
Steve
The text was updated successfully, but these errors were encountered:
Hi Dan,
I work for Philips Hue Developer Support. In case you were not aware, in a few months time we will be changing the way usernames are created on the bridge (for security reasons). Custom whitelist usernames will no longer be allowed and the bridge randomly generated username must be used instead. Please see below link for more information:
http://www.developers.meethue.com/documentation/important-whitelist-changes
I must confess I don't really understand Objective-C code, but I can see in the registerUser method (line 52 in DPHue.m) you are setting the username in your JSON body. After February 2016 this will have no effect. The username should be removed and instead the randomly generated username in the bridge response should be used instead (the above link should hopefully clarify the changes needed). Apologies for the inconvenience.
Thanks
Steve
The text was updated successfully, but these errors were encountered: