With my zip code manually entered last night (EST vs. the CST on "Where am I" map near Wichita), the program activated 9 hours before my designated wake time. It appears to be linked to my computer's clock, not the map. To test that, I manually entered a zip code in California this a.m., watched the "Where am I" map change to that city in California and clicked OK. The program saved the California zip but the "Where am I" map changed to Omaha, Nebraska. What's really interesting on the opening window of the program, sunrise was calculated at PST, but the wake time was calculated EST (evidently, based on my computer's clock). Exited, rebooted, opened program again and changed back to my East Coast zip code... the WAI map showed my general neighborhood until I clicked OK... retained the zip and back to Omaha. The sunrise and sunset setting keeps alternating, so I can't tell whether it's EST or CST... the wake time was based on EST.
Knowing now that the program is linked to my computer's clock (not map), my work-around is to designate my wake time on what hour I want f.lux to activate at night (not actual wake time). E.g., if bedtime is 11 p.m., and no blue light after 8 p.m., I'd set my wake time to 5 a.m. Guessing these anomalies might affect the sliders in "Adjust day and night colors together" but I will let the f. lux software engineers determine that.
