Closed ericklein closed 1 year ago
would require re-arranging functions in setup(), e.g. one time run.
will not fix, OWM data is not real time accurate
since logging destination is timestamping independently, using OWM time on screen, even if off by ~ 1 minute, would not impact anything. As long as the AQ device isn't also being used as a clock :)
Bumping priority to address before Fall. I'll work on this when I open up more of the OWM data for the new UI.
Using OWM Current Weather API timezone field to get local UTC offset. If that is not available, use the backup time zone set in config.h.
I modified aq_network.cpp and aq_network.h to not automatically set UTC time when initializing a network connection, instead adding a new setTime function that allows the UTC offset to be passed in. We don't know the UTC offset until we call the OWM Current Weather API. One we have that, or not, we can set the time.
Could one use the timezone from OWM data to automatically set the time zone in the NTP set function?