f.lux generates many Hue keys
-
I noticed in the user list, that f.lux has generated quite a lot keys. Only one of them is updated today, and all the others seem to be unused.
-
It should make one when you pair it (and only then). Are you seeing it try to pair frequently?
-
@herf said in f.lux generates many Hue keys:
Are you seeing it try to pair frequently?
No. The pairing popup only appears when I clear the whitelist of all f.lux entries. All those entries have a creation date within a 3 seconds time period.
-
We will generate multiple keys like that if we think you have multiple bridges. (We have two in our network at home.)
How many id's are in https://www.meethue.com/api/nupnp ?
-
@herf said in f.lux generates many Hue keys:
How many id's are in https://www.meethue.com/api/nupnp ?
That link shows me one id and the LAN IP of my one and only bridge.
In /api/key/config, I counted a total of 94 keys belonging to f.lux. -
I think this is it: f.lux keeps the "hue" preference turned on even when pairing fails, and so each time you restart it like this, it will try to make an account. It will tell you in a notifier that it's doing that...but of course you might not jump right up and hit the hue button right then.
We probably should not do this on startup, and instead turn the feature off if it fails... this is broken in the code because we allow you to pair with multiple bridges, and so if you wanted f.lux to control one and not another one, it is hard to show that in the UI.
Then, I think Hue is persisting those attempts forever, even if the pairing is unsuccessful. (The "old" protocol did not do this, so I have an excuse....)
Will take another look at it.
