I have the Philips Hue color lights and I'm very happy with them so I thought I'd share how I have them set up with F.lux on my Windows desktop computer and my Amazon Echo in the event anyone reading this might benefit from it.

So I have the Philips Hue lights programmed to turn on automatically when the sun sets through an If This Then That recipe on www.IFTTT.com. The recipe works with the Weather Channel and it knows my location so once the sun sets, it then triggers the Philips Hue Channel to send instructions to my Philips Hue bridge, which turns on all the Philips Hue lights in my apartment. The color of the lights is the standard bright white that those lights emit if a color isn't chosen, but that's okay (for me) since it's just providing light when walking in the door.

Once inside, though, I turn on my Windows desktop computer and F.lux overrides the system and changes the color of the lights to what can only be described as a soothing yellow/orange glow much like that soothing glow of a Himalayan salt lamp. (I have no idea how it does this, but I'm very happy with it and it's very relaxing. And it even dims as the night progresses.)

The problem I encounter, though, is that I don't always have my computer on, so once the computer goes to sleep or turns off, the Hue lights then remain at that level of brightness until I change them or turn them off. It's not a big deal, but after reading this forum and learning that red light doesn't affect our circadian rhythm like blue and green does, I made another recipe on IFTTT recipe for a darkroom mode. The Amazon Alexa Channel listens for my trigger word, which is darkroom, and it instructs the Philips Hue Channel to change the color of all my lights to red. (The Philips Hue Channel allows you to name a color as well or use a CSS hex code. I tried a variety of them and settled on this one: #A00000.)

So now, about an hour before going to bed I tell my Amazon Echo: "Alexa, trigger darkroom." And she changes all the lights to red. I feel the difference just like someone else mentioned here about how it made them feel and that's now my nightly routine. But hopefully, once F.lux becomes fully functional I won't have to do this and it will just take care of it all.

@ragnar said in New f.lux version:

@TwoCables said in New f.lux version:

@canuckken said in New f.lux version sucks:

WOW, I am glad I did not install version 4. I won't be updating to any new version that is not an improvement over version 3.

This forum is only seeing an extremely small fraction of the f.lux users. There are hundreds of thousands of users in total, and so far only a handful have complained. I recommend that you try it and to see what you think of it.

As with anything, the old saying applies that goes, "You can't please everyone".

Just registered to let you know. If the default settings of any software are unreasonable, its poorly designed. There is no need to justify mistakes but to improve upon them. If you do not see the orange screen of poop as a problem you are in denial. In what scenario would it be required? If you are Throttle in Biker Mice from Mars?

However, I really liked the idea why flux was created and what it should do. It also made my screen way too orange and since I was a first time user, I panicked and removed it. Thanks to this thread will try again with the newest version because the idea is great and I have problems with my eyes.

You're talking about opinions here, not facts. Orange screen of poop? Are you serious? That's your opinion and nothing more. I don't have that opinion. Instead, I happen to love the warmest color temperature I can set f.lux to. In fact, I set it to 800K since I can.

No, I didn't like it the first day I tried f.lux, but that's because I wasn't used to it. The FAQ addresses this very specifically, so yes, this is a normal reaction for a first-time user. Today though, I dive right into 800K at night and I love it. If you don't like the warmer color, then that's fine, but it's just your opinion.

@Tungsten_smooth said:

@David-wei We need 90+ CRI lights, not the same stuff that everyone else is making. Lets not flood the market with all of the same stuff. Make high quality competitive cost LED bulbs and push for higher quality light in our future!

I think he's just spamming (unwanted advertising). Look at his profile (look at the only 3 posts he has made), and look at how old this thread is. I think that posts like his aren't worth responding to and are better off being deleted.

No there have to be some reflective material, be that glassy mirror, shiny metal or whatever shiny. In case that sides of tunnel will be just white, it would lead much less light. So it would be inefficient and only wasted money and/or your work. Let the metal there to do it's purpose and just cover the hole with something that blurrs the view into the tube so you won't see the metal. I would do it this way.

@Become1 said:

I removed the compleet program

I removed the compleet program

@herf
Just updated to MacOS 12.6.1 but had this problem before; applied the fix and removed it via your instructions and voila -- everything works!


Thanks.

@mujomailinator

Thanks!

I created an account on here just to reply to say this also worked for me. My contrast wasn't set to Normal either, for some reason.

We found a way to check that our profile is installed efficiently, so the new beta is verifying it once per second.

To download, either join the beta (in "about") or download here:
https://justgetflux.com/flux-setup4.exe

In the future, we might adjust the system ICM/WCS file as we do on the Mac, but this would take a longer beta period to get right, so we are putting this one up to reduce the impact.

Thanks, Colt1855

Try this article:
https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink

Hi,

Any update on Hue integration for Mac? Or even a way to integrate Hue ourselves and get events from f.lux?

Thanks,

Josh

@Elhem-Enohpi Cool, very energy efficient!

@fckflux Lol, happened to see your reply a little late perhaps. I see your username and that's hilarious, why bother using f.lux anyways man you have a laptop with brightness hotkeys to change your brightness so no need! Also just use Windows night mode or use LightBulb instead for christ sike. Dude's probably still complaining about his washed out color's, sheeeeeeit if necessary reinstall darn Windows! Then simple don't ever reinstall f.lux on that laptop. Not hard.

I stand by F.lux and have been using it for years no problem with AMD & Nvidia GPU's, all kinds of different hardware. But hopefully by now you've already fixed your issue...

What really gets me is when you say "7 years later this issue still persists." I'm uncertain as to what to think about that. Do you mean you've been dealing with this same issue after installing F.lux from 7 years ago? If so dude, maybe you should get a new laptop. LMAO. But If I think what you really meant is that you've seen other threads from people 7 years ago with this same problem then that would obviously make more sense.

Just tried above method on my wife's 2011 MBP and it works for hers as well.

@lorna Thanks for reaching out @timpster and @TwoCables your feedback is awesome. Thanks folks!

The High Sierra bug has been reported to Apple. Mojave has a fix already. There is a f.lux build posted with a temporary workaround.

Thanks @crazydef! That did it for now :)