I seem to have found another solution, just disable weewx from updating the console's clock. It is a setting in the weewx configuration file.
On Sunday, June 2, 2019 at 8:55:45 AM UTC-5, John Canfield wrote: > > Yes, it does have something to do with timestamps. Boy was I chasing my > tail for several days - bought a new Davis logger and even bought the WiFi > logger to try. I was on the verge of rebuilding the entire Fitlet and then > stumbled on a solution (a blind chicken finds a piece of corn once in a > while <grin>.) > > My permanent (hopefully) 'fix' is I now have significantly more UPS > reserve minutes that should take me from about 60 minutes to 120-180 > minutes. > > John > WB5THT > On 6/1/2019 5:47 PM, John wrote: > > I think I chased the same ghost a couple times. What I believe the > underlying problem is has to do with weewx incorrectly changing the > console's clock to an earlier time. The result is that the console > eventually appends a record to the datalogger with an earlier timestamp > than the previous record. Weewx aborts reading the datalogger when it > comes across the out of order timestamp. Clearing the logger's memory, > changing the recording interval, etc ... gets around the problem, until it > happens again. > > > On Thursday, May 2, 2019 at 11:13:35 AM UTC-5, John Canfield wrote: >> >> Finally. I've fiddled around so much with this my head is spinning. >> weather.janeandjohn.org is current again. Hooray! >> >> The short story: >> >> - *the original Davis VP2 console is good* >> - *the original Davis USB logger is good* >> - did an upgrade to the latest weewx release >> - I performed a sudo wee_database --update which caught my webpage up to >> April 30, 2019 >> - restarted weewx and rebooted several times while trying database >> commands (wee_database --drop-daily, sudo wee_database --to=2019-05-02, >> sudo wee_device --set-interval=1) >> - the magic seemed to be sudo wee_device --set-interval=1 which Tom said >> in another thread cleared the data logger (and I rebooted again) >> >> So apparently if the database gets screwed up as in not current with the >> logger, you (at least me) can go off on a tangent chasing an interface >> problem >> >> John (WB5THT) >> >> On Wednesday, May 1, 2019 at 2:34:32 PM UTC-5, John Canfield wrote: >>> >>> *This is driving me CRAZY!* >>> >>> I thought I found the problem with a UPS monitor daemon running (I had >>> unplugged the USB cable from the CyberPower box) - I stopped the process >>> and set it to not start at boot. Then it looked like weewx was talking to >>> the console but we had some kind of database problem since I've been down >>> for several days. It was updating my web page with old data. Now I'm >>> getting errors like it can't talk to the logger. I did manage to do a >>> logger text dump but after fiddling around that won't work now. I'm really >>> frustrated and it's time to leave it alone and come back later. >>> >>> Sigh. >>> >>> On Wednesday, May 1, 2019 at 12:23:23 PM UTC-5, vince wrote: >>>> >>>> On Wednesday, May 1, 2019 at 10:21:15 AM UTC-7, John Canfield wrote: >>>>> >>>>> The enigma for me then is why does weewx report the console woke up? A >>>>> USB problem is the first thing I thought of as well but the Fitlet does >>>>> report when ttyUSB0 is attached to a new port. Grrrr. >>>>> >>>>> Thanks Vince, I need all of the help I can get even though I'm not a >>>>> weewx newbie - I was one of Tom's beta testers with one of his first >>>>> releases. >>>>> >>>>> >>>>> >>>> I think the minicom approach of trying to connect to the console >>>> 'without' weewx is a good one, it's just that the device might not match >>>> the one you're trying to use. >>>> >>>> Try disconnecting the usb then reconnecting it, then use 'dmesg' to see >>>> what device it allocated. >>>> >>> -- > You received this message because you are subscribed to a topic in the > Google Groups "weewx-user" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/weewx-user/-aw7xfmK7_4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/weewx-user/7469e457-d7df-4b4e-bdb5-7fc11de81f7f%40googlegroups.com > > <https://groups.google.com/d/msgid/weewx-user/7469e457-d7df-4b4e-bdb5-7fc11de81f7f%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/cd5188c9-06b3-4a85-a9ab-93a7e9f9b62f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
