Set your wake time for 6:00 a.m. F.lux should always enter Bedtime Mode 9 hours prior to your wake up time.

Of course, also configure the temperature you want.

@gubblor said in Turn off Philips Hue lights:

@twocables Yeah, obviously, but it would be ever smarter if it was completely automated.

It can be. I don't know about Hue, but with LIFX, I see the ability to set it so that it's 100% automated to the point where I would no longer need to do any kind of manual control whatsoever. However, I don't have a life where I can have my lights turning on and off on a schedule because I don't really have a schedule. So, I just gladly control them manually.

Can't you just create the schedule you want in the Philips Hue app?

To be honest, I'm not seeing much of a problem either way. If you can't create the schedule you want but you know when you want the lights to be on or off, then I would just turn them on or off in the app or with voice control at that time.

Maybe I'm not sure what you mean by "completely automated". If you mean that you'd like the lights to just know when you will be working evenings and when you won't be so that the dog won't be in the dark for a few hours. I don't know what you can do with the Philips Hue app, but you can create multiple schedules that you can enable/disable whenever you want.

I'm having this trouble too Zansa, but cannot figure this out. When you say you "upgraded" to v4 after putting v3 back on, how did you go about that?

(If you don't want to rez this old thread, here is a new one I started:
https://forum.justgetflux.com/topic/6842/quickgamma-being-ignored-after-windows-10-re-install )

Thanks a lot! Solved the problem :)

Do you think "starts with" is sufficient for this?
Quite possibly, but I would let the user choose, because it might be the case that the program has something like what Eclipse does above, i.e. ends with the program name.

Grayscale doesn't reduce blue light at all. For proof and information on what the purpose of grayscale is, read this (source):

version 4.84: Grayscale mode, distraction-free reading

November 2018

This new version of f.lux has a grayscale mode and new key to turn it on: Windows + End.

You may already know about Tristan Harris and the Center for Humane Technology. They’ve explained how apps mess with our attention, so even the colors used on our screens are chosen to distract you. At first, we didn’t think this problem would be as bad on the desktop as it is on your phone.

The big surprise is how distracting the icons on the top and bottom of your screen are. These icon colors are the kind of thing you see in candy stores and on fire alarms, but we have to ignore them just to get work done. Without those colors, your computer looks more like a magazine that can help you focus on reading or thinking—it feels different, like a sheet of paper.

Also, turning your devices to grayscale does not remove blue light, so f.lux will continue to do what it does.

In this version, there’s also dusk-to-dawn support for people with Hue lights, so you can put Hue lights outside and use f.lux to turn them off during the day.

There are some bugfixes too.

Thanks for using f.lux. We hope you enjoy it.

Sorry, I can't help. I just wanted to add that I'm also having the same problem, on Windwoes 10. In my case, automatic, as well as manual color change (Shift-Alt-PgUp/PgDown) and also manual brightness control (Alt-PgUp/PgDown) no longer work. When I try to use the shortcuts, the notifications (e.g. for % brightness) show up the same as before, but nothing actually happens. This all worked for as long as I can remember, until a few months ago. I stopped using f.lux for a few weeks before that and when I tried to run it again, it was no longer working.

The only thing that still works is Vignette Mode. It may also be worth pointing out that the Night Light function built into Windows 10 also fails to work the same way (i.e. I can turn it on/off, change the setting, etc. but nothing happens).

I recently cleaned out the display drivers from safe mode -- although, come to thing of it, I've also performed an upgrade repair install of Windows (Insider Edition) since then. Only thing I haven't tried yet (since I only just thought of it) is to try from a different user account...and now I have. In fact, since the store app wanted me to log into an account, I downloaded the installer from the website instead (if that makes any difference) and installed it as regular software. The problem remains the same: hitting the shortcut keys brings up the usual notifications, but nothing happens.

I also don't recall there being anything in the event log -- but I'll check again...nothing.

Here's the driver info (copied via options):

NVIDIA 25.21.14.1735: NVIDIA GeForce GTX 1070 (20181211)
Intel Corporation 20.19.15.4549: Intel(R) HD Graphics 530 (20161110)

1 monitors

Generic PnP Monitor
Dimensions: 382 x 215
Year: 2016
Chroma:
R=0.636719 0.347656
G=0.333984 0.627930
B=0.154297 0.049805
W=0.313477 0.329102
sRGB gamut: 77%, AdobeRGB gamut: 54%

Sorry to awaken this two year old thread... but i’m Actually trying to get flux to appear on a screen recording. I want to record a video the way it appears with the darkroom filter on, but it doesn’t appear when I attempt a screen capture. What is a good way to get this to appear?

Thanks,
Spencer

@herf Yes!

@herf Is there any setting / regedit to disable the brightness changes for Hue at all? Or just set it once per period, so that manual changes via Hue App are not overwritten within few seconds?

@hounddogrock said in Windows 10 always starts with pop-up screen of f.lux.:

@twocables Great! That seems to have fixed it! Thanks a bunch!

You're welcome. The reason why it fixes it is, having f.lux in the Startup folder is identical to just double-clicking a shortcut to f.lux after Windows starts. That's how the Startup folder works.

When you install f.lux, it doesn't place a shortcut there because it creates an entry in the Registry for its startup because it uses a special command in the Registry called "NoShow" to keep the f.lux window from opening on Windows startup.

So, if it stops starting with Windows, then somehow that Registry entry was deleted. Usually, the only way to get it back is by reinstalling f.lux. Putting it in the Startup folder will only run the shortcut. To see what I mean, create a shortcut to f.lux and just double-click it. That's the same thing, only you're running the shortcut manually. The Startup folder runs shortcuts for you automatically, but it's not anywhere near the same thing as the way f.lux gets itself to start up with Windows without its window opening (that is, with the "NoShow" command in the Registry).

Same here, got a rather large screen, usually watch TV series in windowed mode and doing other stuff at the same time, so the changes are very annoying whenever the videoplayer is in focus or not.

An optional "disable even if app isn't focused" would be great.

Its also very annoying when switching to another app to maybe copy a needed file.