Just as a final conclusion - during this night the weekwindvec diagram has
been created also at 3:00 as expected (no longer error messages within
journalctl).
[image: weekwindvec.png]
Its timestamp 03:00:00 proves it (to be compared with 23:00:00 some posts
ago without the xtypes.py fix).
Heureka - your fix within xtypes.py did the trick. I no longer get errors
during the night. Sadly, I forgot to store nightly copies of the weewx HTML
output, thus I currently can't confirm if the weekwindvec is really
created. But I'm quite sure:-)
Thank you very much, Michael
Karen K
Tom Keffer schrieb am Freitag, 17. November 2023 um 14:43:37 UTC+1:
I don't know why this is working for Karen, but not Michael.
In any case, try this version of xtypes.py. It explicitly tests whether a
daily summary is available when calculating wind vectors.
I guess, because I do not plot
Thanks for your fix. It's now activated within my environment (I did
restart weewx afterwards).
Tomorrow I'll report back...
Tom Keffer schrieb am Freitag, 17. November 2023 um 14:43:37 UTC+1:
> I don't know why this is working for Karen, but not Michael.
>
> In any case, try this version of
I don't know why this is working for Karen, but not Michael.
In any case, try this version of xtypes.py. It explicitly tests whether a
daily summary is available when calculating wind vectors.
-tk
On Thu, Nov 16, 2023 at 10:54 PM 'Michael Waldor' via weewx-user <
weewx-user@googlegroups.com>
@Tom Keffer: I would like to add that the table dwd-forecast-K2714.sdb is
created outside WeeWX by a separate program. It creates the core table
only, no daily summaries. That is the reason, weewx.manager.Manager is
used. I use it myself, and I never got an error message like that the
thread
I have to admit that I do not understand the details howto setup sqlite
databases within weewx - I've tried to follow the recipe for DWD forecasts
as given within https://github.com/roe-dl/weewx-DWD , and I did retain all
database settings as given by standard delivery weewx.conf (I do a manual
>
> First weewx.conf:
> [[dwd_binding]]
> database = dwd_sqlite
> table_name = forecast
> manager = weewx.manager.Manager
> schema = schemas.dwd.schema
>
You are using the database manager weewx.manager.Manager for the "forecast"
table. That manager will not
I believe that your item (1) can't be my problem because all diagrams have
the correct (and current) timestamp below their time axis. Within my
failing sample diagram in my previous post you can see the timestamp 23:00
where it should be 03:00. And of course after 5:15 even that diagram is
suggestions:
(1) maybe the weekly graph is only being calculated in your 0-5 daily hour
interval → really failing all the time. try hourly or daily graph to verify it
works during those & other hours
(2) maybe another deeper exception is happening which happens to be percolated
up as sqlError
One additional hint: I've checked if there is forecast info available at
the right border of my timeline. Sadly, it is - the forcast roughly covers
10 days into the future w.r.t. current date. And most other week diagrams
are rendered correctly when weekwindvec is failing.
Michael Waldor
During this night I did save the weewx HTML output from 3 o'clock. And now
I know what images are not updated - the weekwindvec diagram (and all week
diagrams being rendered "afterwards").
The time axis of all diagrams are fine, i.e. my tweak of utilities.py seems
NOT to be the cause of my
Hard to say. Plots are regenerated only as often as their aggregation
interval. Perhaps it is the "year" windvec plot that is failing: it would
be regenerated only once a day.
Just guessing. You have a complicated configuration and we haven't seen
your configuration files.
On Wed, Nov 15, 2023
Thanks for your quick reply. But why does my setup work fine after 5:15 all
over the day? From my perspective a wrong configuration should fail always.
Tom Keffer schrieb am Mittwoch, 15. November 2023 um 14:12:31 UTC+1:
> Imagegenerator is trying to calculate a wind vector. This typically
>
Imagegenerator is trying to calculate a wind vector. This typically happens
for a plot with a spec that looks something like this:
*[[[weekwindvec]]]windvecplot_type = vector*
Normally, it uses the "wx_binding" database binding to do this, which is
normally pointed at the
I seem to have a very specific problem due to my complex changes within
weewx. First I'll shortly describe my problem, then I'll explain my weewx
environment:
My problem: weewx 4.10.2 is working fine during daytimes, but
imagegenerator fails daily between 0:00 and 5:15 all 5min with the same
Sent: Wednesday, December 19, 2018 12:18 PM
To: weewx-user
Subject: [weewx-user] Unrecoverable Error
Well I have somehow managed to change something that is causing my system not
to work. It was working fine. I imported several years worth of record from
Weather Underground.
I get this message
Well I have somehow managed to change something that is causing my system
not to work. It was working fine. I imported several years worth of
record from Weather Underground.
I get this message:
weewx[481]: engine: Caught unrecoverable exception in engine:
Dec 19 11:50:37 weewx weewx[481]:
18 matches
Mail list logo
