Am Mittwoch, 7. August 2019 21:11:04 UTC+2 schrieb gjr80:
>
>
> Remember that an archive record value is an average over a period of say 5
> minutes so the need for 1 degree precision in the case of wind direction
> seems somewhat less important.
>
> Gary
I wouldn't consider it important in
Am Mittwoch, 7. August 2019 21:11:04 UTC+2 schrieb gjr80:
>
>
> Remember that an archive record value is an average over a period of say 5
> minutes so the need for 1 degree precision in the case of wind direction
> seems somewhat less important.
>
> Gary
I wouldn't consider it import in a sta
Didn’t pickup on that. The ws28xx driver has no genArchiveRecords method, there
is a comment in the driver to the effect that hardware record generation should
not be implemented until archive records can be read at a faster rate than they
are currently.
Gary
--
You received this message beca
Just a clarification: on startup, weewx does indeed call the
genStartRecords() method on the driver. However, the default implementation
is to just call genArchiveRecords() with the last good timestamp in the
database as an argument. If the driver supports it, this effectively means
a "catch up" is
Not sure the WeeWX engine behaviour (backfill only requested during WeeWX
startup/restart) will change, you probably have more chance of changing the
driver behaviour.
Regarding your loop data question. Unfortunately there is little that can be
done if the station does not maintain the same lev
Thank you for the explanation, Gary, everything now seems perfectly logical
to me. Being a software developer myself I have a feeling that it probably
isn't an easy change task to let weewx backfill values under such
circumstances, nevertheless I'll write that on my christmas wishlist ;)
Maybe
Thank you for the explanation, Gary, everything now seems perfectly logical
to me. Being a software developer myself I have a feeling that it probably
isn't an easy change task to let weewx backfill values under such
circumstances, nevertheless I'll write that on my christmas wishlist ;)
@Gary:
If you call the ‘top of the hour’ archive records rogue records then yes they
had a hand in preventing backfill, provided a restart occurred only those
archive records stored in the station after the most recent ‘top of the hour’
archive record would be downloaded. Arguably though the reason the
Gary - thanks for that good description of when backfilling occurs although
I have a feeling that the original poster had to restore an old copy of the
database in order for backfilling to occur - hence my suspicion about a
rogue dateTime in the database which would not backfill.
On Wednesday
Hi,
The backfill behaviour you are seeing is expected behaviour for the current
codebase, in a nutshell WeeWX only attempts to download historical records when
WeeWX starts.
Explanation. Drivers for stations that have the ability to store archive
records may implement a genStartupRecords metho
Am Mittwoch, 7. August 2019 13:49:00 UTC+2 schrieb Andrew Milner:
>
> You never said that it recovered by itself after 0100 - in fact you gave
> the impression that it only started working again after you stopped weewx,
> restored an old database and restarted weew and that then it did the
> b
You never said that it recovered by itself after 0100 - in fact you gave
the impression that it only started working again after you stopped weewx,
restored an old database and restarted weew and that then it did the
backfill and recovered. Well that is how I understood your posts anyway.
On
Am Mittwoch, 7. August 2019 09:20:27 UTC+2 schrieb Andrew Milner:
>
> do you have a rogue dateTime in the database?
>
>
Not that I'm aware of.
> The log you posted ONLY has database records added at 22:00, 23:00, 24:00
> and a message every 10 minutes saying there is no new data - press SET t
do you have a rogue dateTime in the database?
The log you posted ONLY has database records added at 22:00, 23:00, 24:00
and a message every 10 minutes saying there is no new data - press SET to
resynch. I repeat - how do you know that it has reconnected?? No new data
implies that it has NOT co
Am Montag, 29. Juli 2019 13:19:05 UTC+2 schrieb Andrew Milner:
>
> are you certain it has reconnected??
>
>
Yes. The log portion above is copied "as is" from weewx.log and I didn't
touch anything before or after.
> the archive records are only being generated at 1 hr intervals - is this
> co
are you certain it has reconnected??
the archive records are only being generated at 1 hr intervals - is this
correct??
there does not appear to be any communication between archive events - very
strange.
The log message instructs you to resynch by pressing SET - did you do that??
I am far fro
Nothing?
--
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 the web visit
https://groups.google.c
[image: daytempdew.png]
--
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 the web visit
https:
18 matches
Mail list logo
