My recollection is that the 'incorrect system time at startup' issue has
been one that seems to rear its head every now and then. Whilst the
preferred solution is to have a battery backed RTC there have been various
approaches taken in the WeeWX code base to ameliorate the situation where a
On Thu, 30 May 2019 04:58:37 -0700 (PDT)
mwall wrote:
> i am sure there are other scenarios...
>
> m
Thankyou mwall for a better discussion of the options.
Liz
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group
Andrew,
I am not having a problem with records in the weewx database with incorrect
timestamps. I am having a problem with weewx not downloading data from the
console after an extended power outage. The underlying problem seems to be
that if weewx updates the console clock to something
On Tuesday, May 28, 2019 at 11:00:09 AM UTC-4, John wrote:
>
> I propose changing the vantage driver to avert setting the console time,
> during a routine sync, earlier than the last record in the console. This
> should prevent weewx from adjusting the console time until the weewx host
> has
Just my 2 Cent as the thread opener:
I solved my problem by removing the batteries from my Vantage Pro2 and
having just the powercord. Do not ask my why this solved it …
On 28 May 2019, at 17:15, Andrew Milner wrote:
I would recommend you doing the CORRECT solution and installing an RTC
John
the issue is not with syncing the clock as such. The issues are caused by
records in the database with weewx generated timestamps which will be
incorrect if weewx is started with an incorrect time set on the rpi. The
solution is to install an rtc on the rpi and to be honest I just do not
I've disabled weewx from syncing the vantage console's clock. I had an
another power outage yesterday for a bit over an hour and everything seemed
to eventually recover without intervention. The battery backed clock in the
vantage console seems to be adequate. Most routines for syncing battery
fitting a RTC is the best solution to make the RPi more like a 'normal'
computer - especially when used for real world production use.
On Tuesday, 28 May 2019 22:44:38 UTC+3, John wrote:
>
> The instructions for delaying weewx from starting on the Raspberry Pi
> until time is synced don't
The instructions for delaying weewx from starting on the Raspberry Pi until
time is synced don't seem to be working with stretch and timesyncd as the
network time client. If I "systemctl disable systemd-timesyncd" it never
updates from the ntp server and weewx spins away with "engine: Waiting
I would recommend you doing the CORRECT solution and installing an RTC on
your Pi zero. Weewx relies HEAVILY on accurate time synchronisation
between weather station and controlling PC - so ensuring your pi EITHER has
an RTC onboard OR prevents weewx starting until time has been synchronised
so looking at the vantage driver it seems that if the weewx host (raspberry
pi zero without a RTC) has an incorrect time like after a restart and syncs
it's bad (early) time with the vantage console, then records being added to
the vantage console will have an earlier timestamp than existing
I spent a fair bit of time on what I believe is the same issue. I even
installed an Adafruit RTC and that didn't seem to solve the issue. At the
moment, I have the system on a UPS (which is huge and probably uses more
power than my Console, Adapter/Logger module and the RPi Zero W). My UPS
I have been experiencing similar problems recently with my Vantage Pro 2
console and RPI (Zero W) setup, typically after a prolonged (1+ hours)
power outage. My only recovery method so far has been to clear the logger
which unfortunately leaves me without the storm data that initiated the
When you changed the logging interval to one minute, you also cleared the
memory in the logger. It's possible that your problem all along was corrupt
logger memory, but I would be surprised if that showed itself as an unknown
hardware type.
If it fails again, you probably have a bad logger. It's
I just had success with
wee_device --set-interval=1
as it cleans all the old data. Now weewx does get the new data. Might it be
that my USB Logger has a defect? I will keep you posted.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To
Unfortunately this did not help. I removed batteries, power and and the usb
data logger overnight, restarted my Pi and still get
wee_device --info
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Your logger is responding with an unknown hardware type. I doubt this has
anything to do with the upgrade.
Try power cycling: unplug the power supply from your Vantage and take out
its batteries. While you are at it, reseat the logger. Then put everything
back together and try again.
-tk
On
Hi,
after an update to the lastet version of weewx it does not get any data from my
station anymore. With —info I get
Using configuration file /etc/weewx/weewx.conf
Using Vantage driver version 3.1.1 (weewx.drivers.vantage)
Unable to wake up console... sleeping
Unable to wake up console...
18 matches
Mail list logo
