I know this is an old thread but I want to ask you about another possible solution. I have a Particle Photon based weather station that I have dumping sensor readings to a phant server I have running on my network. The phant server timestamps everything in UTC. I can then do a jsonp query with a cron job python script I have running then parse that into a format that fileparse.py likes. I also parse out and convert the EST corrected timestamp from the server into unix epoch format. Can weewx be set up to ignore it's own timestamps and just use the imported ones, which technically are more accurate because they represent the very moment the reading was taken? I tried using fileparse to import the timestamp into the dateTime label in weewx, but I think it didn't like that.
Another possible solution to the NTP problem is to use a server you have on your local network and configure it as an NTP relay. I have a freenas box running my phant server in a jail on it so would be easy to just set it up to act as an NTP relay and have the Pi sync from that rather than the internet, therefore I can operate completely in a net down situation and keep collecting data with proper timestamps. On Sunday, 20 March 2016 22:02:17 UTC-4, Tom Keffer wrote: > > Weewx now comes with a delay that prevents it from proceeding until the > date is after 1 January 2000. > > All you have to do is remove fake clock: > > > $ sudo apt-get remove fake-hwclock > > Then remove the old, recorded time: > > $ sudo rm /etc/fake-hwclock.data > > > > On Sun, Mar 20, 2016 at 6:59 PM, Ron Knapp <ron.s...@gmail.com > <javascript:>> wrote: > >> A very poor solution I used was to put a sleep 30 in the start function >> of Weewx init script. While this prevents Weewx from starting till the Pi >> has had a chance to correct the time, it causes >> the init system to report that weewx failed to start when in fact it >> started fine. I also changed the init start symlinks to S99weewx from >> S02weewx, this makes it the last thing to start giving >> the pi even more time to get its time fixed. >> >> >> >> On Sunday, March 20, 2016 at 9:53:31 PM UTC-4, Ron Knapp wrote: >>> >>> >>> I know this is old thread but has any solution been found to this issue? >>> From what I have observed the problem is when the pi comes up its time is >>> last shutdown. My issue is that when >>> it comes up with the wrong time weewx then sets the vantage console to >>> the wrong time. A few seconds later the pi's NTP corrects the computer time >>> but the records being retrieved >>> from the vantage now are time stamped with the wrong time. This is >>> solved by restarting weewx and it then sets the console time to the correct >>> time.if I understand this correctly the timestamp >>> of the entry in the database is the time of the vantage console, not >>> that of the pi, so the the console is still logging records with the >>> correct timestamp till weewx sets it wrong with bad time >>> from the Pi. If I understand this correctly then it seems the fix would >>> be to install a max delta limit on the setting the vantage console time, >>> NTP has something similar. I would set mine for 1 min. So when >>> weewx goes to set the time on the console, if the difference is more >>> then 1 minute it aborts and does not change the time. Later when the pi >>> has the correct time set it tries to set the time and finds >>> it is 2 seconds off, so it completes the time change on the console. If >>> this has been resolved please correct me as I happen today when I shut the >>> pi down for an image backup. >>> >>> >>> Rpm >>> >> -- >> 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+...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- 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. For more options, visit https://groups.google.com/d/optout.
