Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-03-01 Thread Tom Keffer
Several files are affected. I'll try to do a dot-dot release soon. On Tue, Mar 1, 2022 at 8:52 AM f4n...@gmail.com wrote: > How can I download the single files from github, or could anyone upload > these here? > > asla...@gmail.com schrieb am Dienstag, 22. Februar 2022 um 19:48:08 UTC+1: > >>

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-03-01 Thread f4n...@gmail.com
How can I download the single files from github, or could anyone upload these here? asla...@gmail.com schrieb am Dienstag, 22. Februar 2022 um 19:48:08 UTC+1: > Thank you for the clarification. > > On Tuesday, February 22, 2022 at 7:43:22 PM UTC+1 tke...@gmail.com wrote: > >> The accumulators

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Aslak Vaa
Thank you for the clarification. On Tuesday, February 22, 2022 at 7:43:22 PM UTC+1 tke...@gmail.com wrote: > The accumulators for windDir and windGustDir are useless. If the wind > blows at 359° for an hour, then 1° for an hour, the windDir accumulator > would return 180°. They are there only

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Tom Keffer
The accumulators for windDir and windGustDir are useless. If the wind blows at 359° for an hour, then 1° for an hour, the windDir accumulator would return 180°. They are there only because it's easiest to just create an accumulator for everything. Same with the daily summaries for windDir and

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Aslak Vaa
Sorry, that was not my intended question. My issue is that I see wind speed and direction as a pair of values for any given time. When we speak of max wind, I am interested of the speed of wind and its direction at that time. The speed is the main issue, and direction is an attribute to the

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Tom Keffer
LOL! Well, I guess you could say it's a feature. max in archive_day_windSpeed is the maximum value seen for 'windSpeed'. max in archive_day_windGust is the maximum value seen for 'windGust'. They are not necessarily the same because archived windSpeed is typically the average wind seen over an

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Aslak Vaa
The enclosed file was not correct in my last reply. Please see this new file. Best Regards, Aslak On Tuesday, February 22, 2022 at 1:47:36 PM UTC+1 Aslak Vaa wrote: > I have installed your last update, and I will keep an eye on the results > for the next days. Thank you for following up the

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-22 Thread Aslak Vaa
I have installed your last update, and I will keep an eye on the results for the next days. Thank you for following up the issue. However, I performed queries from the accumulator tables for windSpeed, windDir, windGust and windGustDir. The mintime/maxtime for wind and direction are unequal

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-21 Thread Tom Keffer
Upon reflection, I really didn't like the solution I posted earlier. The reality is that for stations that do not supply windGustDir, such as the Fine Offset stations, weewx was calculating a substitute just fine: the vector average of the wind over an archive period was being extracted from the

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-16 Thread Fische Namenlos
Fische Namenlos schrieb am Mittwoch, 16. Februar 2022 um 10:52:28 UTC+1: > I've similar failures for the WindGust, but only in the *creation *of > "image" for the *stacked WindRose*. I use the blue sofaskin on a > renkforce WH2315, alias FineOffset. > > It was working nicely with 4.5.1... > >

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-16 Thread Fische Namenlos
I've similar failures for the WindGust, but only in the *creation *of "image" for the *stacked WindRose*. I use the blue sofaskin on a renkforce WH2315, alias FineOffset. It was working nicely with 4.5.1... remy.l...@gmail.com schrieb am Montag, 14. Februar 2022 um 13:37:41 UTC+1: > A

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-14 Thread Remy Lavabre
A *water year* (also called *hydrological year*, *discharge year* or *flow year*) is a term commonly used in hydrology to describe a time period of 12 months for which precipitation totals are

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-14 Thread paul...@gmail.com
Checked this morning and pleased to say Max Wind direction is now reporting and updating in the Day tab of the Statistics section. Still N/A in Week but I'm guessing it will update in due course. Just out of interest I've noticed in the Statistics section the Year tab is blue and if you click

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Remy Lavabre
Yes, it’s the good python file, same as me (if standard installation...) The Tom’s update/patch solves perfectly the problem and also min/max windGustDir data base. Try stop and start weewx (logicaly same thing as restart... !?) Try to look for all wxxtype.py on your system to see if there is

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread paul...@gmail.com
Hi Remy Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it again but no change. Can I just check I swapped the correct wxxtypes.py file. I swapped the one in /usr/share/weewx/weewx Paul On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote: > Hi Paul. > Have

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Remy Lavabre
Hi Paul. Have you triedto stop weewx and restart it ? You must do that if you modify python file. Cordialy Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a écrit : > I don't report wind gust values/direction in the Current Conditions > section of my Seasons skin (version

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread paul...@gmail.com
I don't report wind gust values/direction in the Current Conditions section of my Seasons skin (version 4.6.2) but in the Statistics (previously High/Low) section I've always had a Max Wind entry with both speed and direction reported. Since 4.6.2 the direction is reported as N/A so I've

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Aslak Vaa
Brilliant, now it work just fine. Thanks a lot. On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com wrote: > Yes !! Thank-you Tom it works great now : > > [image: Capture d’écran de 2022-02-13 15-26-27.png] > Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a écrit

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Remy Lavabre
Yes !! Thank-you Tom it works great now : [image: Capture d’écran de 2022-02-13 15-26-27.png] Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a écrit : > I was able to replicate the problem. Pre V4.6, if windGustDir was missing, > windDir was substituted. That behavior went away

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Tom Keffer
I was able to replicate the problem. Pre V4.6, if windGustDir was missing, windDir was substituted. That behavior went away with v4.6. This patch restores it. Index: bin/weewx/wxxtypes.py === diff --git a/bin/weewx/wxxtypes.py

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Remy Lavabre
[image: Capture d’écran de 2022-02-13 10-14-16.png] Same problem for me ! Since weewx 4.6.x windGustDir is always N/A but the value is correct. I never had this problem before with 4.5.x or before... Only since 4.6.x WindGustDir is always None in loop package values : LOOP: 2022-02-13

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-13 Thread Remy Lavabre
[image: Capture d’écran de 2022-02-13 10-14-16.png] Same problem for me ! Since weewx 4.6.x windGustDir is always N/A but the value is correct. I never had this problem before with 4.5.x or before... Only since 4.6.x Would it be possible to tell me how to get the loop packages so that I can

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Remy Lavabre
Same problem for me ! Since weewx 4.6.x windGustDir is always N/A. Nevers add this problem before with 4.5.x or later... Le samedi 12 février 2022 à 19:23:27 UTC+1, asla...@gmail.com a écrit : > The result with a couple of LOOP records. > Both windGust and windGustDir occur in both REC and Loop

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Aslak Vaa
The result with a couple of LOOP records. Both windGust and windGustDir occur in both REC and Loop records. REC:2022-02-12 19:15:49 CET (1644689749) 'altimeter': '29.447857403881475', 'appTemp': '20.60149362123522', 'barometer': '29.56391226224894', 'cloudbase': '3549.153942263896',

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Tom Keffer
Could you do the same again, except this time show the LOOP data as well? I'm not exactly sure what's happening, but my operating theory is that windGust and windDir never appear in the same LOOP packet. When the software sees windGust, but no windGustDir, it looks to substitute windDir, but it's

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Tom Keffer
Sorry, yes, that's what I meant. If windGustDir is missing, it should substitute windDir in its place. Let me think about this for a bit. On Sat, Feb 12, 2022 at 5:59 AM Aslak Vaa wrote: > Here is the result from running weewxd from the command line: > > REC:2022-02-12 14:45:49 CET

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Aslak Vaa
Here is the result from running weewxd from the command line: REC:2022-02-12 14:45:49 CET (1644673549) 'altimeter': '29.559632125170864', 'appTemp': '21.79815080002', 'barometer': '29.68039690383254', 'cloudbase': '3612.989261474405', 'dateTime': '1644673549', 'delay': '10',

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Tom Keffer
FO stations do not supply windGustDir, so the software should substitute windGust in its place. Could you please run weewxd directly from the command line ? Watch what it prints out for records (marked with "REC:"). What does it show for

[weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

2022-02-12 Thread Aslak Vaa
After upgrating to weewx version 4.6.0/4.6.2 is windGustDir is always set to NULL in database (sqlite3). Please see results of query from the database and extracts from the syslog file. I stopped the version 4.5.1 at feb 5 15:02:05, and I started the version 4.6.0 same date half an hour later