danparsons / dphue Goto Github PK

In DPHue.m I see that the "deviceType" is hardcoded as "QuickHue". I suppose this doesn't affect anything, but it seems like it shouldn't be done that way. Or should it?

[!] The platform of the target Pods (OS X 10.8) is not compatible with DPHue (0.0.1) which has a minimum requirement of iOS 5.0.

Looks like the spec file sets the Deployment target to iOS
s.ios.deployment_target = '5.0'

Description:
If you have a preset that has some bulbs that are dimmed down to "off", when applying this preset later, the 'off' light bulbs will display at full brightness in white.

Steps to Repro:

1. Using an mobile app, set lights in a pattern so one of them is dimmed down to where the led's turn off completely. (Example, one red full brightness, one blue half brightness, one green 0 brightness)
2. Save pattern as preset using QuickHue (Example, Preset 1)
3. Select preset from QuickHue menu.

Actual Result:
All lights that had brightness in the preset will be applied correctly, any that were 'off' will turn on as white full brightness. (For this example: one red full brightness, one blue half brightness, one WHITE FULL BRIGHTNESS)

Expected Result:
Lights dimmed down to 'off' should apply that state when applying presets.

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