Re: [weewx-user] Unrecoverable error "no such table: forecast_day_wind"

[Graham Eddy]

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 that reports the last sqlite error not this error
⊣GE⊢

> On 16 Nov 2023, at 5:49 pm, 'Michael Waldor' via weewx-user 
>  wrote:
> 
> Normally, it uses the "wx_binding" database binding to do this, which is 
> normally pointed at the "archive" table. For whatever reason, your 
> installation is attempting to do this with the "forecast" table. It could be 
> that you are using the wrong binding, or it could be that the wx_binding is 
> pointing to the "forecast" table.
> 

-- 
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.com/d/msgid/weewx-user/ADE419CC-6E82-4A5E-B775-43845693D994%40geddy.au.

[weewx-user] Backfill missing data from Ecowitt

[michael.k...@gmx.at]

I have some Ecowitt hardware: several sensors, a HP2550_C and a GW2000.

I use the GW2000 with weewx, it also transmits to ecowitt.net, the HP2550_C 
is only used with ecowitt.net. The GW2000 missed some data from the wind 
sensor, both, my weewx graphs an ecowitt.net are missing these readings at 
the time the the GW2000 couldn't receive the data from the sensor. For 
the HP2550_C, both, the values in the device and ecowitt.net contain this 
data. Apart from the problem, that the GW2000 isn't located perfectly to 
receive the signals from the sensor, what is the best approach to get this 
missing data in?

Once before I did this manually (Update DB with the missing readings, calc 
missing and rebuild daily for the particular day)

Is there a tool for this?

I also was thinking of using both devices as a data source. This should 
work with the Interceptor driver and the Ecowitt gateway driver as a 
service... anyone with a setup like this here?

-- 
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.com/d/msgid/weewx-user/a51b9016-d868-4fe9-85f0-c217247c4810n%40googlegroups.com.

Re: [weewx-user] Unrecoverable error "no such table: forecast_day_wind"

['Michael Waldor' via weewx-user]

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 
updated and marked with the correct and current timestamp. To enforce 
recreation of monrh/year diagrams I intentonally cleared all diagrams 
within /var/www/html/weewx, and weewx creatwd all diagrams during next 
report generation cycle. 

Graham Eddy schrieb am Donnerstag, 16. November 2023 um 09:55:39 UTC+1:

> 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 that reports the last sqlite error not this error
> *⊣GE⊢*
>
> On 16 Nov 2023, at 5:49 pm, 'Michael Waldor' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
> Normally, it uses the "wx_binding" database binding to do this, which is 
> normally pointed at the "archive" table. For whatever reason, your 
> installation is attempting to do this with the "forecast" table. It could 
> be that you are using the wrong binding, or it could be that the wx_binding 
> is pointing to the "forecast" table.
>
>
>

-- 
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.com/d/msgid/weewx-user/6912d5ab-5ff5-4230-a41b-a768257cb8cen%40googlegroups.com.

[weewx-user] Colorize search list extension

['Steeple Ian' via weewx-user]

I have been looking at the colorize search list extensions in the examples 
folder, specifically colorize-3.py.

Am I correct in assuming that this extension only works with HTML color 
names and not with HEX, RGB, etc color codes?

-- 
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.com/d/msgid/weewx-user/e4ab8c76-d31b-4049-850b-00f17122f9d0n%40googlegroups.com.

[weewx-user] Re: Colorize search list extension

[vince]

(followup)

Ian and I talked via email - he got it working by specifying '#' 
for colors in skin.conf if he surrounded the value in single quotes.

On Thursday, November 16, 2023 at 9:49:33 AM UTC-8 Steeple Ian wrote:

> I have been looking at the colorize search list extensions in the examples 
> folder, specifically colorize-3.py.
>
> Am I correct in assuming that this extension only works with HTML color 
> names and not with HEX, RGB, etc color codes?
>

-- 
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.com/d/msgid/weewx-user/c2568ffa-8d53-4220-ba77-7c07ee1df0den%40googlegroups.com.

Re: [weewx-user] Errors Continue [was: Weewx fails in Fedora 39]

[Jonathan Ryshpan]

On Wed, 2023-11-15 at 14:20 -0800, Tom Keffer wrote:
> This is caused by upgrading to Pillow 10, which has removed the
> attribute "textsize". There have been several email threads about
> this. For
> example, https://groups.google.com/g/weewx-user/c/F1oLMD8_3MQ/m/Gir1m-9RAgAJ
> 
> You can either downgrade Pillow to 9.x, or cherry pick the fix as
> described in the email thread, or use the beta of WeeWX V5.

I tried cherry picking genplot.py, which broke other things; maybe I did
it wrong. Anyway I'd like to try V5. Where are instructions for
downloading and installing it? The only version I can find is a .deb,
and I run Fedora.

-- 
Sincerely Jonathan Ryshpan 

 The mind is not a vessel to be filled; it is 
 a fire to be kindled. -- Plutarch 

-- 
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.com/d/msgid/weewx-user/6952511a8dbc0dec82226d5bdb480034b1846ce3.camel%40pacbell.net.

[weewx-user] Matthew Wall's Lightning service extension and variable names

[Karen K]

There is an extension  
available created by Matthew Wall and reading the AS3935 lightning detector 
circuit. It sets 2 observation types:

   - avg_distance
   - lightning_strikes

In contrary to that, the wview_extended schema as well as units.py in WeeWX 
define other observation types for the same purpose:

   - lightning_distance
   - lightning_strike_count

Why they are different?

I found no assignment of a unit group to the observation types used by 
Matthew Wall's extension. Is that intended?

-- 
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.com/d/msgid/weewx-user/366b6420-d734-449f-a782-d9dc93a4e680n%40googlegroups.com.

Re: [weewx-user] Errors Continue [was: Weewx fails in Fedora 39]

[vince]

See https://www.weewx.com/docs.html and use the 5.0 link there for 
instructions, but there are no RHish packages available yet.

It might be easier to just grab the v5 genplot.py and drop it into place 
and see if you get further...
https://raw.githubusercontent.com/weewx/weewx/V5/src/weeplot/genplot.py

FWIW - I found one third-party extension yesterday that threw the same 
textsize error, but that was due to me running an old version.  Updating 
that extension fixed the issue for me on a new pi os.

On Thursday, November 16, 2023 at 11:26:44 AM UTC-8 Jonathan Ryshpan wrote:

> On Wed, 2023-11-15 at 14:20 -0800, Tom Keffer wrote:
>
> This is caused by upgrading to Pillow 10, which has removed the attribute 
> "textsize". There have been several email threads about this. For 
> example, 
> https://groups.google.com/g/weewx-user/c/F1oLMD8_3MQ/m/Gir1m-9RAgAJ
>
>
> You can either downgrade Pillow to 9.x, or cherry pick the fix as 
> described in the email thread, or use the beta of WeeWX V5.
>
>
> I tried cherry picking genplot.py, which broke other things; maybe I did 
> it wrong. Anyway I'd like to try V5. Where are instructions for downloading 
> and installing it? The only version I can find is a .deb, and I run Fedora.
>
> -- 
>
> Sincerely Jonathan Ryshpan 
>
>   The mind is not a vessel to be filled; it is 
>   a fire to be kindled. -- Plutarch 
>
>

-- 
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.com/d/msgid/weewx-user/0b843727-4902-452e-a304-17852c9ace61n%40googlegroups.com.

Re: [weewx-user] Unrecoverable error "no such table: forecast_day_wind"

[Tom Keffer]

>
> 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 include daily summaries, which is why you are
getting the error that the daily summary table forecast_day_wind is
missing. Is this intentional?

Nevertheless, it should be possible to calculate the wind vectors without
the daily summaries. It would be frightfully slow, but it would work.

Two questions:

1. What does the schema schemas.dwd.schema look like?
2. What is the actual schema used in the database used by forecast? You
didn't give enough information for me to determine the path to the actual
database, so you'll have to do that.

echo .schema | sqlite3 path-to-the-forecast-database

-tk

-- 
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.com/d/msgid/weewx-user/CAPq0zEAiMJXHH9RSb5Vkt7GXTb2mc-b2UX%3DyyquctQMT2UHe4Q%40mail.gmail.com.

[weewx-user] Re: Colorize search list extension

['Steeple Ian' via weewx-user]

Yes just to confirm and thanks to Vince for the clue that nudged me in the 
right direction, I can confirm that the hex code enclosed in single quotes 
works perfectly.

Here is an extract from my skin.conf: -

[Colorize]
[[group_temperature]]
unit_system = metricwx
default = '#eba141'
None = lightgray
[[[upper_bounds]]]
-10 = '#8781bd'
0 = '#487ea9'
5 = '#369cac'
10 = '#9aba2f'
20 = '#eba141'
25 = '#ec5a34'
30 = '#d05f2d'
35 = '#d65b4a'
40 = '#dc4953'
100 = '#e26870'

On Thursday, November 16, 2023 at 7:25:26 PM UTC vince wrote:

> (followup)
>
> Ian and I talked via email - he got it working by specifying '#' 
> for colors in skin.conf if he surrounded the value in single quotes.
>
> On Thursday, November 16, 2023 at 9:49:33 AM UTC-8 Steeple Ian wrote:
>
>> I have been looking at the colorize search list extensions in the 
>> examples folder, specifically colorize-3.py.
>>
>> Am I correct in assuming that this extension only works with HTML color 
>> names and not with HEX, RGB, etc color codes?
>>
>

-- 
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.com/d/msgid/weewx-user/217bf891-4aa0-47a4-9f03-b835959979f3n%40googlegroups.com.

[weewx-user] Re: Matthew Wall's Lightning service extension and variable names

[matthew wall]

On Thursday, November 16, 2023 at 2:42:43 PM UTC-5 kk44...@gmail.com wrote:

There is an extension  
available created by Matthew Wall and reading the AS3935 lightning detector 
circuit. It sets 2 observation types:

   - avg_distance
   - lightning_strikes

In contrary to that, the wview_extended schema as well as units.py in WeeWX 
define other observation types for the same purpose:

   - lightning_distance
   - lightning_strike_count

Why they are different?


because i am stupid.  i wrote the AS3935 code rather quickly, so i could 
compare that sensor with some other lightning detection equipment we were 
experimenting with.  only later did we create the wview_extended schema, 
and the intent there was to extend the schema with labels and structure 
that were general enough to accommodate a wide range of hardware.

i should probably modify the AS3935 code to use the wview extended schema 
names...
 

I found no assignment of a unit group to the observation types used by 
Matthew Wall's extension. Is that intended?


it is lazy coding on my part, not intentional.
 

-- 
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.com/d/msgid/weewx-user/e0d26a17-f74f-4b1a-b6cf-66e3ac51e095n%40googlegroups.com.

Re: [weewx-user] Cascading errors for the Seasons base skin.

[Sylvain M]

As my English is no longer correct as before, I use an online translator 
with the approximations that this entails. I am sorry for that.

Concerning erratic values.
I actually took the same approach as you recommend, that is to say 
monitoring the graphics of the WU pages which are correct and consistent 
with the values displayed by the console of my PWS. I deduce that the 
values sent by my PWS station are correct and correctly recorded by WU 
since the graphs correspond to reality. Note that I also send my station 
data to weathercloud.net whose graphics are identical to WU.

To import my data, I of course use wee_import in a simple bash script which 
retrieves the last recorded timestamp which is converted into dateTime 
which will serve as a variable for the dateFrom. The date of moment T is 
used for the dateTo variable.
I submit my script on pastbin for your study and the community in case I 
have made a programming error:
https://pastebin.com/biYjHe1E

The strange thing is that the values recorded in mysql for today 11/16/2023 
are correct except from 11:59 p.m. On the other hand, the graph of the 
outTemp column (outside temperature?) of weewx is completely erratic since 
it indicates temperatures of -5°C while the database indicates 8.27°C. Same 
after erasing and importing data.
Is there a problem interpreting the weewx script?
The second strange part is the recording of the outTemp temperature at 
0.32°C and the outHumidity which suddenly dropped from 95% to 79.99% at 
11:59 p.m.
>From a WU quota point of view, my 286 recordings for the day are far from 
1500. I don't understand.

Concerning the units.
Indeed, I use the season skin since I use weewx version 5.0.0b15.
My understanding is that weewx.conf settings take precedence over other 
settings in other files.
I think I understood your advice.
So that you have an overall view you will find my weewx.conf file
https://pastebin.com/BtUtTZzB

I hope it will be more meaningful this way.

Sylvain

Le jeudi 16 novembre 2023 à 00:17:13 UTC+1, gjr80 a écrit :

> My apologies for not replying to your previous post.
>
> I have no knowledge of any changes to the data being provided by WU. In 
> working on some wee_import. change over theist week I have done a number 
> of imports for my station and they have worked without error. I have not 
> checked the veracity of the actual PWS data though. In the past WU has been 
> somewhat flaky/unreliable/hit and miss, call it what you may. However, in 
> recent times they have been more stable. If you are having issues with 
> wildly inaccurate data you might like to do a few checks on your end before 
> taking the issue up with WU. Can you monitor the data that is being 
> uploaded by your station to WU and compare it against what is actually 
> recorded by WU (as opposed to what wee_import obtains via the WU API). If 
> you log onto WU and look at your station towards the bottom of the page you 
> should be able to display your stations historical data either graphically 
> or in tabular form. Does that data  look correct or does it show the 
> non-sense values. If the graphical/tabulated data is correct and 
> wee_import is receiving non-sense values then perhaps it is the WU API or 
> wee_import.
>
> On my diagrams, I no longer have hatched areas but still discontinuous 
> curved lines.
>
>  
> I am not sure what you mean by this, do you mean gaps in plot lines, do 
> you mean something like the second plot in the Line gaps section 
>  of the 
> Customisation Guide? Gaps are typically caused by a lack of data over a 
> period of time. Given you are importing data from WU this could be a lack 
> of data on WU or a problem with your import. It could also be that you have 
> archive records in the WeeWX database that cover that period but those 
> records are missing some data fields. I would suggest identifying the 
> time/period of the gap(s), looking at WU to see if the missing data exists 
> and re-importing if the WU data does exist. If this does not fix the 
> problem I would check your database to see if you do indeed have archive 
> records covering that period, if you do delete those records and then 
> re-import the same period. 
>
> I still can't convert my wind data from m/s to km/h as well as mbar to 
> hPa. However, I have read the documentation and forum threads which for 
> some no longer apply to version 5 of weewx.
> I used the settings recommended in weewx.conf:
> [[Defaults]]
> [[[Units]]]
> [[[Groups
>   group_altitude = meter # Options are 'foot' or 'meter'
>   group_pressure = hPa # Options are 'inHg', 'mmHg', 
> 'mbar', or 'hPa'
>   group_rain = mm # Options are 'inch', 'cm', or 'mm'
>   group_rainrate = mm_per_hour # Options are 
> 'inch_per_hour', 'cm_per_hour', or 'mm_per_hour'
>   group_temperature = degree_C # Options are 'degree_C', 
> '

Re: [weewx-user] Errors Continue [was: Weewx fails in Fedora 39]

[Lee Holstege]

The original post was mine.  I found that removing six.py allowed the 
system to start, as you did.  Everything was working fine EXCEPT the graphs 
were not being updated and I was getting the errors you reported..   In my 
case I fixed the problem by by replacing two files -- genplot.py and 
utilities.py -  with the equivalent files from the v5 b15 beta.   This has 
been working perfectly for me for the past three days.  Other options like 
downgrading pillow DID NOT work for me because the downgrade failed.  YMMV, 
but replacing the files above is worth a try.  Good luck.

On Thursday, November 16, 2023 at 3:24:40 PM UTC-5 vince wrote:

> See https://www.weewx.com/docs.html and use the 5.0 link there for 
> instructions, but there are no RHish packages available yet.
>
> It might be easier to just grab the v5 genplot.py and drop it into place 
> and see if you get further...
> https://raw.githubusercontent.com/weewx/weewx/V5/src/weeplot/genplot.py
>
> FWIW - I found one third-party extension yesterday that threw the same 
> textsize error, but that was due to me running an old version.  Updating 
> that extension fixed the issue for me on a new pi os.
>
> On Thursday, November 16, 2023 at 11:26:44 AM UTC-8 Jonathan Ryshpan wrote:
>
>> On Wed, 2023-11-15 at 14:20 -0800, Tom Keffer wrote:
>>
>> This is caused by upgrading to Pillow 10, which has removed the attribute 
>> "textsize". There have been several email threads about this. For 
>> example, 
>> https://groups.google.com/g/weewx-user/c/F1oLMD8_3MQ/m/Gir1m-9RAgAJ
>>
>>
>> You can either downgrade Pillow to 9.x, or cherry pick the fix as 
>> described in the email thread, or use the beta of WeeWX V5.
>>
>>
>> I tried cherry picking genplot.py, which broke other things; maybe I did 
>> it wrong. Anyway I'd like to try V5. Where are instructions for downloading 
>> and installing it? The only version I can find is a .deb, and I run Fedora.
>>
>> -- 
>>
>> Sincerely Jonathan Ryshpan 
>>
>>  The mind is not a vessel to be filled; it is 
>>  a fire to be kindled. -- Plutarch 
>>
>>

-- 
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.com/d/msgid/weewx-user/c9be6512-5435-4aac-96f6-ca244d93f8c0n%40googlegroups.com.

Re: [weewx-user] Unrecoverable error "no such table: forecast_day_wind"

['Michael Waldor' via weewx-user]

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 
diff with my private copy of weewx.conf each time when I update weewx to a 
new release).

Here the full part w.r.t. sqlite from my weewx.conf (comments dropped)
[DataBindings]
 [[wx_binding]]
 database = archive_sqlite
 table_name = archive
 manager = weewx.manager.DaySummaryManager
 schema = schemas.wview_extended.schema

[[dwd_binding]]
database = dwd_sqlite
table_name = forecast
manager = weewx.manager.Manager
schema = schemas.dwd.schema

[Databases]
[[archive_sqlite]]
database_name = weewx.sdb
database_type = SQLite

[[dwd_sqlite]]
database_name = dwd-forecast-K2714.sdb
database_type = SQLite

And the forecast schema /usr/share/weewx/schemas/dwd.py contains
schema = [('dateTime','INTEGER NOT NULL PRIMARY KEY'),
  ('usUnits','INTEGER NOT NULL'),
  ('interval','INTEGER NOT NULL')]

The sqlite DB itself is stored at /var/lib/weewx/dwd-forecast-K2714.sdb 
side by side with weewx.sdb
echo .schema | sqlite3 /var/lib/weewx/dwd-forecast-K2714.sdb  returns

CREATE TABLE forecast (dateTime INTEGER NOT NULL PRIMARY KEY,usUnits 
INTEGER NOT
NULL,interval INTEGER NOT NULL,hour INTEGER,outTemp REAL,dewpoint 
REAL,outHumid
ity REAL,windchill REAL,heatindex REAL,windDir REAL,windSpeed REAL,windGust 
REAL
,pop REAL,cloudcover REAL,barometer REAL,rain REAL,rainDur REAL,sunshineDur 
REAL
,visibility REAL,ww INTEGER);


Tom Keffer schrieb am Donnerstag, 16. November 2023 um 23:52:17 UTC+1:

> 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 include daily summaries, which is 
> why you are getting the error that the daily summary table 
> forecast_day_wind is missing. Is this intentional?
>
> Nevertheless, it should be possible to calculate the wind vectors without 
> the daily summaries. It would be frightfully slow, but it would work. 
>
> Two questions:
>
> 1. What does the schema schemas.dwd.schema look like?
> 2. What is the actual schema used in the database used by forecast? You 
> didn't give enough information for me to determine the path to the actual 
> database, so you'll have to do that.
>
> echo .schema | sqlite3 path-to-the-forecast-database
>
> -tk
>
>

-- 
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.com/d/msgid/weewx-user/7c1b30f5-638f-4d17-96e9-3a60e0559b03n%40googlegroups.com.