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
Am not sure if you are still actively maintaining this library but if so it looks like it may affect you also, as you appear to be passing in the username when creating (i.e. POSTing) a new username on the bridge (hue.py line 74). This should be removed and the randomly generated bridge username should be retrieved from the bridge response. Apologies for the inconvenience.
Thanks
Steve
The text was updated successfully, but these errors were encountered:
This will definitely need to be changed, yes. I don't really do much active maintenance, since up until this newest release things worked pretty well for me. Thanks for checking in!
Hi Issac,
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
Am not sure if you are still actively maintaining this library but if so it looks like it may affect you also, as you appear to be passing in the username when creating (i.e. POSTing) a new username on the bridge (hue.py line 74). This should be removed and the randomly generated bridge username should be retrieved from the bridge response. Apologies for the inconvenience.
Thanks
Steve
The text was updated successfully, but these errors were encountered: