To explain in too much detail: Philips moved their discovery endpoint recently, but this new endpoint does not work with v1 bridges. So if we use the new one we lose support for v1 bridges. f.lux can also use uPNP on the LAN to find hue bridges, but this tends to be slower and more error prone (firewalls can break it - so this may be what's going on). This is what basically every f.lux install is doing right now. We have been trying to keep support for v1 bridges but may give it up soon, or we may just make an option you turn on to use uPNP to support them--but breaking anything in an update is something to avoid.

Hello, I got some Yeelight Smart led Bulb 1s(color) Model YLDP13YL, I have f.lux and can someone help me how to connect this? I Have Lan option marked in yeelight app.

@yesinkatle6 At sunset remove blue from light / increase the orange Decrease brightness up until bedtime but not to turn off completely until I decide to go to bed To repeat every day without me having to change the start time i.e. automatically adjusts to sunset time throughout the ye

There are some hidden settings for this. See also: https://forum.justgetflux.com/topic/6653/no-ability-to-adjust-brightness-for-hue?_=1602123697674

Actually, this may be a bug report - I think my light (a lifx) is getting the exact color temp that f.lux is giving out, not warmer, even though I have it set to warmer.

Day= 6500K Sunset & Bedtime = 4800K 7.30 am is my earliest wake time @NonBad said in What's your f.lux configuration?: Is it good? We cannot say if it's good or bad because it's your personal feeling :)

@alex said in Feature Request: MQTT Support: Bit late to the party, but I've only just got started with MQTT and automation. If you're using Node-RED, you can use it to receive the data from f.lux with the built-in nodes. I was inspired by this reddit thread - https://www.reddit.com/r/tasker/comments/a6q8vl/looking_for_better_mqtt_integration/ejrgl2l/ - which discusses Tasker, but the pertinent information is the post which describes using Node-RED and the "http in" node. f.lux uses HTTP POST to send "?ct=xxxx&bri=x.xxxxxx" (replacing "x" with appropriate values). For example, "Working Late" sends "?ct=6500&bri=0.800000", while "Cave Painting" sends "?ct=2300&bri=0.800000". The appropriate Node-RED objects for them are "msg.req.query.ct" and "msg.req.query.bri". Looks like the "bri" values are computer-dependent. One of my computers sends "0.800000", but the one next to it sends "0.275000". Still, Node-RED captures both quite happily.

Actually, now that I'm looking at it in more detail, I can't even adjust sunrise time... I can only adjust my earliest waking time. What I'd like is to actually set sunrise and sunset based upon the summer solstice, and keep those settings regardless of my time of year. So basically I want to have a custom sunrise and sunset time that never changes.