Nice catch. I'm using mysql as database. Via phpmyadmin I've managed to sort the database to date, max is 1590084000, converted: GMT: Thursday, 21 May 2020 6:00:00 PM Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00 Relative: In 10 hours
On Thursday, May 21, 2020 at 7:32:26 PM UTC+12, gjr80 wrote: > > Aha, look at your wind direction and wind vector plots, you have a wind > direction dot at midnight and likewise a vector. Are you using SQLite? If > so try the following (you may have to install the sqlite3 package first if > sqlite3 is not found - just use sudo apt-get install sqlite3): > > $ sqlite /var/lib/weewx/weewx.sdb > > SELECT MAX(datetime(dateTime,'unixepoch','localtime')) FROM archive; > > (.q to exit the sqlite3 command prompt) > > What does that show? > > Gary > > > I suspect There will be a data point in your archive for direction > > On Thursday, 21 May 2020 16:43:47 UTC+10, Zsolt Máté wrote: >> >> I've ruled out browser cache. Tested on multiple devices within my >> network and even asked friends abroad to test. You can give it a try, as >> well. https://weather.zmate.nz >> >> 1. 22nd of May, 12:00:00 is not changing. >> 2. I've deleted the contents of the www and it has been automatically >> regenerated, without forcing it. >> 3. plots are being generated correctly, and the hour/minute looks correct. >> 4. the timestamp below the plots is showing 05/22/2020 12:00:00 AM - good >> that you asked. >> On Thursday, May 21, 2020 at 6:13:44 PM UTC+12, gjr80 wrote: >>> >>> Thanks, that is bizarre, I expectedt to see something in the log about >>> record timestamps being less than the last, but no everything is normal. >>> Archive records are bing generated with the correct timestamps, reports are >>> being generated without issue. I can't see it being a browser cache issue, >>> it would be stuck in the past not the future. A few (random) things to >>> check: >>> >>> 1. does the time change or is it always 22 May 00:00 (guessing it stays >>> put). >>> 2. is the Seasons skin index.html file being generated every 5 minutes >>> (ie does its timestamp change) (again guessing it does as Seasons should >>> generate eight report files each report cycle and that is what it is doing) >>> 3. do the current observations on the Seasons page change and are they >>> correct. >>> 4. do the timestamps below the plots on the Seasons 'Day' tab show the >>> correct current time. >>> >>> Gary >>> >>> On Thursday, 21 May 2020 15:44:02 UTC+10, Zsolt Máté wrote: >>>> >>>> Thanks for the fast reply Gary. >>>> Here's the log -> https://pastebin.com/4zNJEJea >>>> >>>> On Thursday, May 21, 2020 at 5:07:37 PM UTC+12, gjr80 wrote: >>>>> >>>>> Hi, >>>>> >>>>> Could be any one of a number of causes, should be easily diagnosed >>>>> with a debug log extract >>>>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user> >>>>> from WeeWX startup. >>>>> >>>>> Gary >>>>> >>>>> On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote: >>>>>> >>>>>> My current conditions are "frozen". >>>>>> >>>>>> Date is waaay in the future. I'm located in NZ, local time/date is >>>>>> 4:47PM, the 21st of May. >>>>>> Since we're UTC-12, nobody passed the dateline yet. >>>>>> >>>>>> I've checkt the date/time and timezone and these are correct on my >>>>>> server. >>>>>> >>>>>> The graphs are correct. >>>>>> >>>>>> What could cause this? >>>>>> >>>>>> [image: 2020-05-21 16_50_44 chrome_4YMd0jl6nZ.png] >>>>>> I'm running weewx 4.0.0 and capturing my data using interceptor. >>>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/92e5453b-3715-41ae-ae8a-a96cba42a3ec%40googlegroups.com.
