The problem comes back for me when I restart the computer

I think I have a similar problem, double click on the curve under the slider to run a 24h preview, after that it activates for me. https://i.imgur.com/oTxPnw9.png (double click anywhere in the red square)

there is a "disable by monitor" feature in the disable menu.

Same here

Is this forum dead? I posted here before and no one replied then either.

Strange, now it turns out to be the normal "/noshow" string. Solved.

@TwoCables Hello. My solar time is 1 hour before my clock time. It is 9 pm on the clock, but 8 pm solar time. f.lux is currently using the "warm at sunset" color due to the 8 pm solar time, but it should be using the warmest color at this time so I can fall asleep in an hour. Is my solar time working correctly? It seems like my solar time would want me to stay up later rather than fall asleep earlier (like the app used to do). It seems like the solar time should really be 8:30 pm at least, since it's already dark outside. Do you think it's working correctly? Thanks for helping me!

I figured out how to do this manually within the monitor (I de-installed f.lux), with Custom RGB settings (please see below). I'm doing ok with two monitors, and these two settings: 2400K and 3400K For more details, please see my post titled: Flickering screen, again, with the latest version: f.lux (v4.118) . . . (08/04/20 I accidentally put this in the V3 forum) Research suggests that f.lux must talk directly to display hardware to work – no remote desktops. I'm curious to see if you get good results also! 2400 K #ff9d3f Standard incandescent lamps . . . HP E272q 255,157,63 (255,157,63) rgb(255,157,63) rgb(100%,62%,25%) 3400 K #ffc184 HALOGEN . . . Per f.lux . . . HP 1755 . . . These settings work on the HP 1755, but aren't very orange on the HP E272q 255,193,132 (255,193,132) rgb(255,193,132) rgb(100%,76%,52%)

I figured out how to do it manually within the monitor, with Custom RGB settings (please see below) I'm doing ok with two monitors, and these two settings: 2400K and 3400K For more details, please see my post titled: Flickering screen, again, with the latest version: f.lux (v4.118) . . . (08/04/20 I accidentally put this in the V3 forum) Research suggests that f.lux must talk directly to display hardware to work – no remote desktops I'm curious to see if you get good results also! 2400 K #ff9d3f Standard incandescent lamps . . . HP E272q 255,157,63 (255,157,63) rgb(255,157,63) rgb(100%,62%,25%) 3400 K #ffc184 HALOGEN . . . Per f.lux . . . HP 1755 . . . These settings work on the HP 1755, but aren't very orange on the HP E272q 255,193,132 (255,193,132) rgb(255,193,132) rgb(100%,76%,52%)

And a correction to my first post, in case anyone else reads this. The conflict only goes from 9:00PM to 9:02PM (not 9:20) Andy