[weewx-user] Re: GUI date/time and current conditions frozen

After a month of trial and error, I'm still struggling with this issue. I've changed my VM from turnkey linux to a full ubuntu server, didn't help. Tried minimal installations, mysql vs sqlite, no joy. My date is being messed up somehow. -- You received this message because you are subscribed t

[weewx-user] Re: GUI date/time and current conditions frozen

As an update, I didn't restart or modified anything since my last message, and it just started working. I really don't understand what happened, now I'm afraid now to stop/restart it. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscrib

[weewx-user] Re: GUI date/time and current conditions frozen

I'm confident that the date/time will jump. I'm going to leave it run for the night. I went through Matthew's wiki/how to/issues multiple times, and this is the best what I was able to do. I wasn't able to make interceptor listen to my network traffic and sniff out the communication between my P

[weewx-user] Re: GUI date/time and current conditions frozen

Well I am stumped. The repeat packets seem to be in a reasonably regular routine, a few HTTP GETs followed by a HTTP POST. I can accept that since you are fooling your station into thinking the interceptor driver is WU your weather station may not be seeing the exact response it expects and t

[weewx-user] Re: GUI date/time and current conditions frozen

Here's the log -> https://pastebin.com/B2zFhnje -- 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 weewx-user+unsubscr...@googlegroups.com. To view this discussion on

[weewx-user] Re: GUI date/time and current conditions frozen

Ok, the multiple duplicate timestamped packets are still there as are the POST and GET. Your system stuck at 8pm but you log extract went to 7:59pm, would be useful seeing 7:55 to say 8:15. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. T

[weewx-user] Re: GUI date/time and current conditions frozen

We have 8:22PM, it stopped at last report wast generated at 8PM. Here's the log of the first 30 minutes, of the actual run https://pastebin.com/uhyCkPvX -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiv

[weewx-user] Re: GUI date/time and current conditions frozen

How about a log from startup for about 30 minutes, we should be able to see if those duplicate packets are gone. Gary -- 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

[weewx-user] Re: GUI date/time and current conditions frozen

Disabling WU didn't help. > > May 23 15:00:19 weewx weewx[10289] DEBUG user.interceptor: raw packet: { 'wind_speed': 2.0, 'humidity_in': 46.0, 'temperature_in': 72.9, 'solar_radiation': 134.81, 'windchill': 54.9, 'dewpoint': 47.8, 'humidity_out': 77.0, 'uv': 1.0, 'rain': 0.0, 'dateTime': 15902424

[weewx-user] Re: GUI date/time and current conditions frozen

OK, starting to test the limits of my networking knowledge. One last thing to try, let's make sure the interceptor is listening to the correct IP address (and only the correct IP address). In weewx.conf under [Interceptor] can you add and the address = 192,168.2.41, ie: [Interceptor]

[weewx-user] Re: GUI date/time and current conditions frozen

Update, disabling MQTT didn't help. My time just jumped 10 hours in advance. From 12PM to 10PM. > > Log 10 minutes +/- 12PM -> https://pastebin.com/FjkM7Mg8 Problem occurs here May 23 12:00:19 weewx weewx[9805] DEBUG user.interceptor: raw packet: { 'wind_speed': 1.8, 'humidity_in': 46.0, 'temperat

[weewx-user] Re: GUI date/time and current conditions frozen

Right now I've disabled MQTT in weewx.conf, cleaned the future records from the database, dropped and rebuild the daily stats. Last HTML generated is more than 30 minutes old. To paint a picture of my setup: I'm running this weather station -> https://www.jaycar.co.nz/7-inch-colour-wireless-wea

[weewx-user] Re: GUI date/time and current conditions frozen

Thanks. I am trying to get my head around what is going on here. There seems to be a lot of double handling (posting) of records, for example the 22 May 19:50:20 record is published by the MQTT uploader six times: May 22 19:50:28 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 2020-0

[weewx-user] Re: GUI date/time and current conditions frozen

It stopped updating the html at local 08:00PM, and in the log I see an MQTT message dated tomorrow. It's MQTT related: May 22 20:00:20 weewx weewx[5569] INFO weewx.restx: MQTT: Published record 2020-05-23 07:00:00 NZST (1590174000) Log from 10 minutes before until 10 minutes after 8PM -> https:

[weewx-user] Re: GUI date/time and current conditions frozen

Weird, I really don't know what's happening. This morning, I've deleted everything related to the past day from the database. 1. done 2. deleted two records, see attached image 3. I've deleted all the files from /var/www/html/weewx/ 4. ran wee_database --drop-daily and --rebuild-daily 5. debug i

[weewx-user] Re: GUI date/time and current conditions frozen

Just looked at your sire and you are now showing 0300 23 May so it has jumped again. If you look at the wind direction and wind vector plots you can clearly see individual points at around 0100 and 0300. It is hard to see but I believe all of the other plots have individual points at the same t

[weewx-user] Re: GUI date/time and current conditions frozen

Update, without any intervention time jumped to 6PM. 10hrs ahead. On Friday, May 22, 2020 at 7:22:48 AM UTC+12, Zsolt Máté wrote: > > Sorry, my bad. New Zealand is UTC+12. > > My issue didn't disappear. Now is showing the time is showing 2PM and not > updating, but local time is 07:15AM. > Data i

[weewx-user] Re: GUI date/time and current conditions frozen

Sorry, my bad. New Zealand is UTC+12. My issue didn't disappear. Now is showing the time is showing 2PM and not updating, but local time is 07:15AM. Data in the plots is scattered. I've double checked the date/time on my PWS and is correct. On Thursday, May 21, 2020 at 10:41:21 PM UTC+12, Jacqu

[weewx-user] Re: GUI date/time and current conditions frozen

Hi, You said on your top message that your timezone is UTC - 12 But below I see UTC + 12 Could it be the problem ? Le jeudi 21 mai 2020 10:08:43 UTC+2, Zsolt Máté a écrit : > > Your time zone: Friday, 22 May 2020 6:00:00 AM GMT+12:00 > > -- You received this message because you are subscrib

[weewx-user] Re: GUI date/time and current conditions frozen

Tried, twice. On Thursday, May 21, 2020 at 8:54:18 PM UTC+12, gjr80 wrote: > > Just force all your plots to be regenerated by deleting them from your > WeeWX machine. > > Gary > -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from

[weewx-user] Re: GUI date/time and current conditions frozen

Just force all your plots to be regenerated by deleting them from your WeeWX machine. Gary -- 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 weewx-user+unsubscr...

[weewx-user] Re: GUI date/time and current conditions frozen

Thank you, it worked. Interestingly that rogue spike is still showing up at the wind vector plot. On Thursday, May 21, 2020 at 8:42:17 PM UTC+12, gjr80 wrote: > > No, —check just checks a couple of unrelated things, will not help you at > all. You need to use —drop-daily before —rebuild-daily.

[weewx-user] Re: GUI date/time and current conditions frozen

No, —check just checks a couple of unrelated things, will not help you at all. You need to use —drop-daily before —rebuild-daily. Gary -- 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

[weewx-user] Re: GUI date/time and current conditions frozen

wee_database --check runs OK (I assume), but --rebuild-daily return an error root@weewx:~# wee_database --check Using configuration file /etc/weewx/weewx.conf Using database binding 'wx_binding', which is bound to database 'archive_mysql' Checking daily summary tables version... Daily summary tab

[weewx-user] Re: GUI date/time and current conditions frozen

Did you use wee_database to rebuild the daily summaries? Probably safest to drop them first then rebuild. Gary -- 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 we

[weewx-user] Re: GUI date/time and current conditions frozen

It looks like I messed up something. I've deleted the two rows from the "future", but now weewx wont start. root@weewx:~# service weewx restart root@weewx:~# tail -f /var/log/syslog May 21 20:30:32 weewx weewx[8599] CRITICAL __main__: File "/usr/share/weewx/weewx/engine.py", line 158,

[weewx-user] Re: GUI date/time and current conditions frozen

Brain fade on my part, I should have tweaked earlier. I would go in and delete the future records from the archive then rebuild the daily summaries. You could just let it be and it will (seemingly) fix itself come 6am tomorrow (albeit with a couple of duplicate index errors in the log) but those

[weewx-user] Re: GUI date/time and current conditions frozen

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, gjr

[weewx-user] Re: GUI date/time and current conditions frozen

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 /v

[weewx-user] Re: GUI date/time and current conditions frozen

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,

[weewx-user] Re: GUI date/time and current conditions frozen

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,

[weewx-user] Re: GUI date/time and current conditions frozen

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 >

[weewx-user] Re: GUI date/time and current conditions frozen

Hi, Could be any one of a number of causes, should be easily diagnosed with a debug log extract from WeeWX startup. Gary On Thursday, 21 May 2020 14:53:35 UTC+10, Zsolt Máté wrote: > > My current conditions are "frozen". > > Da