[weewx-user] Lightning Data Stored in weewx.sdb

[gjr80]

Hi,

A little background as to how WeeWX takes loop data and generates archive 
records to save to database. WeeWX accumulates the loop data seen during an 
archive interval and when using software record generation (as you are) WeeWX 
synthesises an archive record from the accumulated loop data at the end of the 
archive period. The value for each observation in the archive record is 
calculated from the accumulated values using an extractor function. The default 
extractor function is ‘average’. Average is fine for most observations (eg 
temperatures and pressures) but is unsuitable for something like rain. For rain 
we use ‘sum’ as the extractor function. WeeWX supports the following extractor 
functions; avg, count, last, max, min, noop, sum and wind. Each is pretty self 
explanatory except for noop and wind. Noop does nothing and wind is a special 
extractor that returns wind speed and direction as well as wind gust speed and 
wind gust direction.

So in your case you are seeing WeeWX apply the default average extractor to 
your lightning data. Clearly that is not what you want for lightning strike 
count, you want ‘sum’ just as for rain. Fortunately, you can tell WeeWX what 
extractor function to use for an observation. In weewx.conf look for an 
[Accumulator] stanza and add an entry as follows:

[Accumulator]
[[lightning_strike_count]]
extractor = sum

If you don’t have an [Accumulator] stanza just add it at the end of the file.

As for lightning_distance, it really depends what you want to extract. There 
would seem to be a few possibilities, avg and min seem the two most likely but 
you could also use last. I guess it comes down to what data you want to 
record/display. Once you’ve worked that out just add an appropriate extractor 
entry for lightning_distance.

Oh, and once you have finished your changes to weewx.conf you will need to 
restart WeeWX.

Gary

-- 
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/cbe3e1fd-b17f-4b04-9a22-df9e47f4fb04o%40googlegroups.com.

[weewx-user] Re: how to adda DP80 rainsensor to weewx?

['NanoG5Kite' via weewx-user]

For questions regarding WS View and shown or not shown data you might 
contact Lucy from the Ecowitt support by mail. In general she answers your 
questions within 24 hours.

Email: ecowittweat...@outlook.com

Regards,

Matthias

Am Mittwoch, 22. Juli 2020 15:56:42 UTC+2 schrieb RMiles:
>
> Hi,
>
> my current setup is this:
> - gateway: Froggit GW1000/Ecowitt DP1000: 
> https://www.froggit.de/product_info.php?info=p410_dp1500-wi-fi-wetterserver-usb-dongle.html
> - weather station: Froggit HP1000SE Pro:  
> https://www.froggit.de/product_info.php?info=p436_hp1000se-pro-wi-fi-internet-funkwetterstation.html
> - raingauge Froggit DP80/Ecowitt WH40: 
> https://www.froggit.de/product_info.php?info=p462_dp80-drahtloser-selbstentleerender-regenmesser-sensor.html
>
> The weather station comes with a raingauge already. So now I have 2 
> raingauges.
>
> I succesfully added the WH40 raingauge to the DP1000 gateway using the app 
> "WS View". It was added automatically once I powered it up.
>
> First problem:
> Now I would like to see the records of the WH40. 
> *How do I add the graph for the WH40 to the standard WeeWX skin?*
>
> Second problem:
> I also have the problem that I don't see the data from the WH40 in the "WS 
> View" application. Neither I see the data on ecowitt.net.
> My guess is that the DP1000 only shows the data from the integrated rain 
> sensor of the weather station in WS view and on the ecowitt site.
> Does someone know if this is correct?
>
> The WH40 is better than the integrated rain sensor, so I would like to 
> have this data in WS View and at ecowitt.net.
> Is there a workaround for this issue as you know?
>
> Thank you for your help.
>

-- 
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/298ac274-afdb-49e9-b952-fd3665b13a78o%40googlegroups.com.

[weewx-user] Re: Lightning Data Stored in weewx.sdb

[Troy Roberts]

>
> Thank you for the detailed explanation Gary! I have added the 
> [Accumulator] section to my weewx.conf for lightning_strike_count -> 
> extractor = sum and lightning_distance -> extractor = min. Now to wait for 
> another storm.


-Troy 

-- 
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/f8b305fc-4039-4ffb-953c-301fe272d299o%40googlegroups.com.

Re: [weewx-user] StdWXCalculate: beaufort = prefer_hardware

[Vetti52]

Hi, Gary!
Thanks for the hints. In deed, there is a value for beaufort in the loop:
LOOP:   2020-07-23 14:16:36 CEST (1595506596) altimeter: 
30.065488730750573, appTemp: 69.20122805363343, barometer: 30.014, 
beaufort: 1, cloudbase: 3824.7354273385445, dateTime: 1595506596, dewpoint: 
52.73310752508154, heatindex: 69.1, humidex: 72.72248011924633, inDewpoint: 
54.980122811806766, inHumidity: 64.0, inTemp: 67.6, maxSolarRad: 
820.4582989978796, outHumidity: 56.0, outTemp: 69.1, pressure: 29.949, 
radiation: 604.7, rain: None, rainEvent: 0.0, rainRate: 0.0, 
txBatteryStatus: 0.0, usUnits: 1, UV: 5.0, windchill: 69.1, windDir: 240.0, 
windGust: 3.36, windSpeed: 1.34

I did not wait for the REC: record.
So then I should have a look into the skin/skin config. However, I use the 
seasons skin with some translations of the descriptions into German and 
just added the value, as Tom posted above. I put it into current.inc here
  
  

  
$obs.label.outTemp
$current.outTemp
  
  
$obs.label.heatindex
$current.heatindex
  
  
$obs.label.windchill
$current.windchill
  
  
$obs.label.dewpoint
$current.dewpoint
  
  
$obs.label.outHumidity
$current.outHumidity
  
  
$obs.label.barometer
$current.barometer (Trend: 
$trend.barometer.formatted)
  
  
$obs.label.wind
$current.windSpeed ($current.beaufort bft) 
$current.windDir.ordinal_compass 
($current.windDir)$word_current_beaufortBöen 
$current_gust_beaufort
  


gjr80 schrieb am Mittwoch, 22. Juli 2020 um 04:54:16 UTC+2:

> Hi,
>
> If you have beaufort = prefer_hardware under [StdWXCalculate] then you 
> should be seeing field beaufort in loop packets and archive records 
> provided you have field windSpeed in the same packet/record. I would go 
> back to basics as far as you can and run WeeeWX directly 
>  for at least an 
> archive interval (you want to see at least one archive record) and observe 
> the loop packets (lines starting with LOOP:) and archive records (lines 
> starting with REC:) on the console. Do they have a field windSpeed and 
> what is its value, do they have a field beaufort and what is its value? 
> If you have windSpeed and no beaufort or have windSpeed and have an 
> incorrect beaufort value then something is wrong and we need to dig 
> deeper. If the loop packets/archive records are correct then the issue is 
> downstream in the skin/skin config.
>
> Gary
>
> On Tuesday, 21 July 2020 at 20:55:37 UTC+10 Vetti52 wrote:
>
>> Hi, Tom!
>>
>> As there was almost no wind last week, I just tried to activate 
>> $current.beaufort. I decided to show both values, such as $current_beaufort 
>> ($current.beaufort). However, the new value always shows (0), while the 
>> other one looks ok to me. Do I have to drive another screw somewhere in 
>> Weewx. The only place, I know, is the entry in [StdWXCalculate], which is 
>> set to "prefer_hardware" as by default.
>> It is not that bad, as the solution from @WindnFog 
>> works 
>> as well. But, at least, the new solution should work too.
>>
>> Am Mittwoch, 8. Juli 2020 18:25:06 UTC+2 schrieb Tom Keffer:
>>
>>> Beaufort is treated as a separate observation type, not an alternative 
>>> unit. So, you should be able to use it like any other type. For example,
>>>
>>>   The current wind speed is $current.windSpeed, which is beaufort 
>>> $current.beaufort.
>>>
>>> If you want to plot it, you would need to put 'beaufort' in your 
>>> database schema.
>>>
>>> -tk
>>>
>>>
>>>
>>> On Wed, Jul 8, 2020 at 6:42 AM Vetti52  wrote:
>>>
>> Hi you Weewx experts!

 first I would like to say, that my station ( a WS2900 clone) is not 
 that sophisticated, especially concerning wind speed and direction. There 
 are many tall trees around, being closer than their 10fold height, so that 
 the wind is often much smoother and more disturbed than on top of the 
 trees. However, I still would like to compare the data to the data 
 provided 
 by local weather forecasters. Commonly the wind is announced in the 
 literally equation of the predicted Beaufort value. So, they talk of 
 "fresh 
 breeze", when wind with 5 bft is expected. Therefore I wanted to display 
 the wind data in bft and its literal equivalent also. In Weewx 3 I adopted 
 the solution found here:
 https://groups.google.com/d/topic/weewx-user/b7TqpYD9sxY/discussion
 which works fine so far.
 After upgrading to Weewx 4 I found a new entry in 

 [StdWXCalculate]
 [[Calculations]]
   beaufort = prefer_hardware

 which raised the question, if I could replace the previous solution by 
 that introduced in version 4.
 I expected, that there would be an option in the [[[Units]]] sect

Re: [weewx-user] StdWXCalculate: beaufort = prefer_hardware

[gjr80]

If you have beaufort in the loop packets then you should end up with 
beaufort in archive records. Does it work now? If not $current.x tags 
come from the archive record hence the suggestion to run WeeWX directly for 
at least a full archive period to confirm that beaufort is appearing in 
archive records.

Gary

On Thursday, 23 July 2020 22:38:14 UTC+10, Vetti52 wrote:
>
> Hi, Gary!
> Thanks for the hints. In deed, there is a value for beaufort in the loop:
> LOOP:   2020-07-23 14:16:36 CEST (1595506596) altimeter: 
> 30.065488730750573, appTemp: 69.20122805363343, barometer: 30.014, 
> beaufort: 1, cloudbase: 3824.7354273385445, dateTime: 1595506596, dewpoint: 
> 52.73310752508154, heatindex: 69.1, humidex: 72.72248011924633, inDewpoint: 
> 54.980122811806766, inHumidity: 64.0, inTemp: 67.6, maxSolarRad: 
> 820.4582989978796, outHumidity: 56.0, outTemp: 69.1, pressure: 29.949, 
> radiation: 604.7, rain: None, rainEvent: 0.0, rainRate: 0.0, 
> txBatteryStatus: 0.0, usUnits: 1, UV: 5.0, windchill: 69.1, windDir: 240.0, 
> windGust: 3.36, windSpeed: 1.34
>
> I did not wait for the REC: record.
> So then I should have a look into the skin/skin config. However, I use the 
> seasons skin with some translations of the descriptions into German and 
> just added the value, as Tom posted above. I put it into current.inc here
>   
>   
> 
>   
> $obs.label.outTemp
> $current.outTemp
>   
>   
> $obs.label.heatindex
> $current.heatindex
>   
>   
> $obs.label.windchill
> $current.windchill
>   
>   
> $obs.label.dewpoint
> $current.dewpoint
>   
>   
> $obs.label.outHumidity
> $current.outHumidity
>   
>   
> $obs.label.barometer
> $current.barometer (Trend: 
> $trend.barometer.formatted)
>   
>   
> $obs.label.wind
> $current.windSpeed ($current.beaufort bft) 
> $current.windDir.ordinal_compass 
> ($current.windDir)$word_current_beaufortBöen 
> $current_gust_beaufort
>   
>
>
> gjr80 schrieb am Mittwoch, 22. Juli 2020 um 04:54:16 UTC+2:
>
>> Hi,
>>
>> If you have beaufort = prefer_hardware under [StdWXCalculate] then you 
>> should be seeing field beaufort in loop packets and archive records 
>> provided you have field windSpeed in the same packet/record. I would go 
>> back to basics as far as you can and run WeeeWX directly 
>>  for at least an 
>> archive interval (you want to see at least one archive record) and observe 
>> the loop packets (lines starting with LOOP:) and archive records (lines 
>> starting with REC:) on the console. Do they have a field windSpeed and 
>> what is its value, do they have a field beaufort and what is its value? 
>> If you have windSpeed and no beaufort or have windSpeed and have an 
>> incorrect beaufort value then something is wrong and we need to dig 
>> deeper. If the loop packets/archive records are correct then the issue is 
>> downstream in the skin/skin config.
>>
>> Gary
>>
>> On Tuesday, 21 July 2020 at 20:55:37 UTC+10 Vetti52 wrote:
>>
>>> Hi, Tom!
>>>
>>> As there was almost no wind last week, I just tried to activate 
>>> $current.beaufort. I decided to show both values, such as $current_beaufort 
>>> ($current.beaufort). However, the new value always shows (0), while the 
>>> other one looks ok to me. Do I have to drive another screw somewhere in 
>>> Weewx. The only place, I know, is the entry in [StdWXCalculate], which is 
>>> set to "prefer_hardware" as by default.
>>> It is not that bad, as the solution from @WindnFog 
>>> works 
>>> as well. But, at least, the new solution should work too.
>>>
>>> Am Mittwoch, 8. Juli 2020 18:25:06 UTC+2 schrieb Tom Keffer:
>>>
 Beaufort is treated as a separate observation type, not an alternative 
 unit. So, you should be able to use it like any other type. For example,

   The current wind speed is $current.windSpeed, which is beaufort 
 $current.beaufort.

 If you want to plot it, you would need to put 'beaufort' in your 
 database schema.

 -tk



 On Wed, Jul 8, 2020 at 6:42 AM Vetti52  wrote:

>>> Hi you Weewx experts!
>
> first I would like to say, that my station ( a WS2900 clone) is not 
> that sophisticated, especially concerning wind speed and direction. There 
> are many tall trees around, being closer than their 10fold height, so 
> that 
> the wind is often much smoother and more disturbed than on top of the 
> trees. However, I still would like to compare the data to the data 
> provided 
> by local weather forecasters. Commonly the wind is announced in the 
> literally equation of the predicted Beaufort value. So, they talk of 
> "fresh 
> breeze", when wind with 5 bft is expected. Therefore I wanted to display 

[weewx-user] Re: log message question

[Jamie Stephens]

thank you

On Wednesday, July 22, 2020 at 2:01:16 PM UTC-4, Jamie Stephens wrote:
>
> new user
>
> saw this in my logs today, anything i need to worry about?
>
> Jul 22 09:25:19 weewx systemd[1]: Starting Cleanup of Temporary 
>>> Directories...
>>
>> Jul 22 09:25:20 weewx systemd-tmpfiles[7707]: 
>>> /usr/lib/tmpfiles.d/vsftpd.conf:1: Line references path below legacy 
>>> directory /var/run/, updating /var/run/vsftpd/empty → /run/vsftpd/empty; 
>>> please update the tmpfiles.d/ drop-in file accordingly.
>>
>> Jul 22 09:25:20 weewx systemd[1]: systemd-tmpfiles-clean.service: 
>>> Succeeded.
>>
>> Jul 22 09:25:20 weewx systemd[1]: Finished Cleanup of Temporary 
>>> Directories.
>>
>>

-- 
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/1c30969b-4bb4-4da9-8c8c-750f5590e752o%40googlegroups.com.

[weewx-user] New GW1000 Driver available for testing

['NanoG5Kite' via weewx-user]

Just recocnized the very promising announcement in the developer forum...:

https://groups.google.com/forum/#!topic/weewx-development/bhtsW6WWtvQ

On Github:

https://github.com/gjr80/weewx-gw1000

Will test this API driven driver certainly during the weekend.

Matthias

-- 
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/8b05dbe8-74f1-4b0b-ac48-d8c8b0c1c3cdo%40googlegroups.com.

[weewx-user] Re: how to adda DP80 rainsensor to weewx?

[RMiles]

thank you Matthias, I already did, she told me I should remove the 5 all in 
1 sensor unit from WS view. Then I should be able to get the rain data from 
the new raingauge. I will loose all the other sensor data then though, as:
- external temp
- solar
- uv
- hum
- wind directory and wind speed

Not really a good option.
mbal...@googlemail.com schrieb am Donnerstag, 23. Juli 2020 um 12:49:37 
UTC+2:

>
> For questions regarding WS View and shown or not shown data you might 
> contact Lucy from the Ecowitt support by mail. In general she answers your 
> questions within 24 hours.
>
> Email: ecowitt...@outlook.com
>
> Regards,
>
> Matthias
>
> Am Mittwoch, 22. Juli 2020 15:56:42 UTC+2 schrieb RMiles:
>>
>> Hi,
>>
>> my current setup is this:
>> - gateway: Froggit GW1000/Ecowitt DP1000: 
>> https://www.froggit.de/product_info.php?info=p410_dp1500-wi-fi-wetterserver-usb-dongle.html
>> - weather station: Froggit HP1000SE Pro:  
>> https://www.froggit.de/product_info.php?info=p436_hp1000se-pro-wi-fi-internet-funkwetterstation.html
>> - raingauge Froggit DP80/Ecowitt WH40: 
>> https://www.froggit.de/product_info.php?info=p462_dp80-drahtloser-selbstentleerender-regenmesser-sensor.html
>>
>> The weather station comes with a raingauge already. So now I have 2 
>> raingauges.
>>
>> I succesfully added the WH40 raingauge to the DP1000 gateway using the 
>> app "WS View". It was added automatically once I powered it up.
>>
>> First problem:
>> Now I would like to see the records of the WH40. 
>> *How do I add the graph for the WH40 to the standard WeeWX skin?*
>>
>> Second problem:
>> I also have the problem that I don't see the data from the WH40 in the 
>> "WS View" application. Neither I see the data on ecowitt.net.
>> My guess is that the DP1000 only shows the data from the integrated rain 
>> sensor of the weather station in WS view and on the ecowitt site.
>> Does someone know if this is correct?
>>
>> The WH40 is better than the integrated rain sensor, so I would like to 
>> have this data in WS View and at ecowitt.net.
>> Is there a workaround for this issue as you know?
>>
>> Thank you for your help.
>>
>

-- 
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/5e1c7f19-e261-423c-97c3-8b6f64c7d588n%40googlegroups.com.

[weewx-user] Re: New GW1000 Driver available for testing

[galfert]

For anyone discussing this new GW1000 API driver in the WeeWX development 
section STOP. Use this user section instead to discuss its use.


-- 
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/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[steeple ian]

???

On Thu, 23 Jul 2020 at 19:39, galfert  wrote:

> For anyone discussing this new GW1000 API driver in the WeeWX development
> section STOP. Use this user section instead to discuss its use.
>
>
> --
> 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/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
> 
> .
>

-- 
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/CADASSaT6KbEg%2BGX5XcbXjD7SBDwQ7uAbKeVZn5HKt3OWPNJoEg%40mail.gmail.com.

Re: [weewx-user] StdWXCalculate: beaufort = prefer_hardware

[Vetti52]

Well, I had to wait for some wind first. Now, after sunset, wind seems to 
be growing. And this is the latest archive record:

REC:2020-07-23 20:50:00 CEST (1595530200) altimeter: 29.94844953418796, 
appTemp: 64.63492618774067, barometer: 29.8973336, beaufort: 
0., cloudbase: 2464.8536620841987, dateTime: 1595530200, 
dewpoint: 53.68325395886734, ET: 0.000133188221454822, extraTemp1: 
133.6604, heatindex: 64.06, humidex: 68.17774431413599, 
inDewpoint: 61.099461593234274, inHumidity: 75.77, inTemp: 
69.08, interval: 5.0, maxSolarRad: 10.611708312518399, 
outHumidity: 69.0, outTemp: 64.06, pressure: 29.832333, 
radiation: 15.478889, rain: 0.0, rainEvent: 0.0, rainRate: 0.0, 
txBatteryStatus: 0.0, usUnits: 1, UV: 0.0, windchill: 64.06, 
windDir: 171.3974954238297, windGust: 4.92, windGustDir: 202.0, windrun: 
0.08481481481481483, windSpeed: 1.018

At least, there is a value for beaufort. But it is still displayed as 0 bft 
in the skin. To be sure, I will have to wait for more wind, until tomorrow.

kind of curious
Peter

Am Donnerstag, 23. Juli 2020 15:20:06 UTC+2 schrieb gjr80:
>
> If you have beaufort in the loop packets then you should end up with 
> beaufort in archive records. Does it work now? If not $current.x tags 
> come from the archive record hence the suggestion to run WeeWX directly for 
> at least a full archive period to confirm that beaufort is appearing in 
> archive records.
>
> Gary
>
> On Thursday, 23 July 2020 22:38:14 UTC+10, Vetti52 wrote:
>>
>> Hi, Gary!
>> Thanks for the hints. In deed, there is a value for beaufort in the loop:
>> LOOP:   2020-07-23 14:16:36 CEST (1595506596) altimeter: 
>> 30.065488730750573, appTemp: 69.20122805363343, barometer: 30.014, 
>> beaufort: 1, cloudbase: 3824.7354273385445, dateTime: 1595506596, dewpoint: 
>> 52.73310752508154, heatindex: 69.1, humidex: 72.72248011924633, inDewpoint: 
>> 54.980122811806766, inHumidity: 64.0, inTemp: 67.6, maxSolarRad: 
>> 820.4582989978796, outHumidity: 56.0, outTemp: 69.1, pressure: 29.949, 
>> radiation: 604.7, rain: None, rainEvent: 0.0, rainRate: 0.0, 
>> txBatteryStatus: 0.0, usUnits: 1, UV: 5.0, windchill: 69.1, windDir: 240.0, 
>> windGust: 3.36, windSpeed: 1.34
>>
>> I did not wait for the REC: record.
>> So then I should have a look into the skin/skin config. However, I use 
>> the seasons skin with some translations of the descriptions into German and 
>> just added the value, as Tom posted above. I put it into current.inc here
>>   
>>   
>> 
>>   
>> $obs.label.outTemp
>> $current.outTemp
>>   
>>   
>> $obs.label.heatindex
>> $current.heatindex
>>   
>>   
>> $obs.label.windchill
>> $current.windchill
>>   
>>   
>> $obs.label.dewpoint
>> $current.dewpoint
>>   
>>   
>> $obs.label.outHumidity
>> $current.outHumidity
>>   
>>   
>> $obs.label.barometer
>> $current.barometer (Trend: 
>> $trend.barometer.formatted)
>>   
>>   
>> $obs.label.wind
>> $current.windSpeed ($current.beaufort bft) 
>> $current.windDir.ordinal_compass 
>> ($current.windDir)$word_current_beaufortBöen 
>> $current_gust_beaufort
>>   
>>
>>
>> gjr80 schrieb am Mittwoch, 22. Juli 2020 um 04:54:16 UTC+2:
>>
>>> Hi,
>>>
>>> If you have beaufort = prefer_hardware under [StdWXCalculate] then you 
>>> should be seeing field beaufort in loop packets and archive records 
>>> provided you have field windSpeed in the same packet/record. I would go 
>>> back to basics as far as you can and run WeeeWX directly 
>>>  for at least an 
>>> archive interval (you want to see at least one archive record) and observe 
>>> the loop packets (lines starting with LOOP:) and archive records (lines 
>>> starting with REC:) on the console. Do they have a field windSpeed and 
>>> what is its value, do they have a field beaufort and what is its value? 
>>> If you have windSpeed and no beaufort or have windSpeed and have an 
>>> incorrect beaufort value then something is wrong and we need to dig 
>>> deeper. If the loop packets/archive records are correct then the issue is 
>>> downstream in the skin/skin config.
>>>
>>> Gary
>>>
>>> On Tuesday, 21 July 2020 at 20:55:37 UTC+10 Vetti52 wrote:
>>>
 Hi, Tom!

 As there was almost no wind last week, I just tried to activate 
 $current.beaufort. I decided to show both values, such as 
 $current_beaufort 
 ($current.beaufort). However, the new value always shows (0), while the 
 other one looks ok to me. Do I have to drive another screw somewhere in 
 Weewx. The only place, I know, is the entry in [StdWXCalculate], which is 
 set to "prefer_hardware" as by default.
 It is not that bad, as the solution from @WindnFog 
 

Re: [weewx-user] Re: New GW1000 Driver available for testing

[galfert]

There is a thread in the developer section where some questions were asked 
that were not directly related to development. This thread is good. I'm 
just inviting people to ask their questions here in this thread rather than 
in the developer section.

On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>
> ???
>
> On Thu, 23 Jul 2020 at 19:39, galfert > 
> wrote:
>
>> For anyone discussing this new GW1000 API driver in the WeeWX development 
>> section STOP. Use this user section instead to discuss its use.
>>
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
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/510ca97a-ce6a-498a-90d4-2bdaa2eefa3co%40googlegroups.com.

[weewx-user] Bogus rain value - new WeeWX setup with Acurite 01035 through USB port

[Dave Schmidt]

Hello all.

For many many years, I've been pushing my Acurite 5n1/01035 data to WUND 
using VIS software running on a nettop pc.  It's been working fine except 
my system hangs whenever VIS pushes an update.

Because of the hanging problem, and the desire to host my station on my 
AREDN node, last week I switched to WeeWX on a Pi, connected it to my 01035 
display through the USB port (mode 4).  I've set up the configuration to 
push data to WUND, and knock on wood, everything seemed to work fine - 
until I saw a random, large rain event being reported.

https://www.wunderground.com/dashboard/pws/KCAVENTU59/graph/2020-07-19/2020-07-19/daily

At 11:49 pm there is a 8.56" of rain reported.  It wasn't raining, not even 
a little, and my 01035 didn't show that any precipitation occurred.

Anyone know what may have happened and how to prevent this from happening 
again?

Thanks,
Dave in So Cal (where I wish it would rain)
 


-- 
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/a9d57a89-6f05-4d29-9990-172c87135af3o%40googlegroups.com.

[weewx-user] Re: how to adda DP80 rainsensor to weewx?

[galfert]

You are getting ahead of yourself worrying about Ecowitt.net not having the 
data and WeeWX skins for the WH40...etc.

WS View needs to be happy first. Once everything is showing up correctly in 
WS View then you can move on to the other things...which you'll likely then 
see that these other things automatically get fixed once everything is 
working in WS View. So nothing else matters other than WS View showing all 
your sensors.

The sensors in WS View will be seen by your DP1500. Note it is a DP1500 not 
a DP1000.  You can use your WS View and go to the Sensors ID section to 
register the sensors. Make sure that the sensors properly have batteries 
installed. Check battery orientation. The sensor should show up on both WS 
View via the DP15000 and also on your HP1000SE PRO display. The DP80 will 
automatically supersede the rain gauge in your all-in-one sensor array. The 
rest of the sensors in the all-in-one will continue to be used though. 

Know this though... The DP80 / WH40 has recently been discovered to produce 
worse data than the all-in-one rain gauge. You can read more about this in 
wxforum.net as there are a few threads that mention this. It seems hard to 
believe at first but it seems that when the rain rate is high water jumps 
out as the slope of the funnel is too shallow and the rim too low compared 
to the all-in-one rain gauge design. Since you have the all-in-one 
alreadyI would just forget the DP80 / WH40 for now. Keep it around as 
Ecowitt is working on a redesign and maybe there will be a retrofit funnel.

-- 
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/b16cbefe-1d21-41cd-80b4-92af09008d0eo%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[Bill Arthur]

FYI:
wget -P /var/tmp 
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
 
gives me an Error 404 

On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:

> There is a thread in the developer section where some questions were asked 
> that were not directly related to development. This thread is good. I'm 
> just inviting people to ask their questions here in this thread rather than 
> in the developer section.
>
>
> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>
>> ???
>>
>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>
> For anyone discussing this new GW1000 API driver in the WeeWX development 
>>> section STOP. Use this user section instead to discuss its use.
>>>
>>>
>>> -- 
>>> 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...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>

-- 
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/eb5f0739-2fdb-4345-910a-81c4f6f69584n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[Bill Arthur]

This link 
works: 
https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz

On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:

> FYI:
> wget -P /var/tmp 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>  
> gives me an Error 404 
>
> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>
>> There is a thread in the developer section where some questions were 
>> asked that were not directly related to development. This thread is good. 
>> I'm just inviting people to ask their questions here in this thread rather 
>> than in the developer section.
>>
>>
>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>
>>> ???
>>>
>>> On Thu, 23 Jul 2020 at 19:39, galfert  wrote:
>>>
>> For anyone discussing this new GW1000 API driver in the WeeWX development 
 section STOP. Use this user section instead to discuss its use.


 -- 
 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...@googlegroups.com.
>>>
>>>
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
  
 
 .

>>>

-- 
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/dc6cb1a4-3e7d-45b2-8aaf-489d5c186380n%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[Bill Arthur]

I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.
But I'm scratching my head trying to find how to specify the IP address in 
weewx.conf
I have three GW1000s here, I have no idea which one is being used..

On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:

> This link works: 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>
> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>
>> FYI:
>> wget -P /var/tmp 
>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>  
>> gives me an Error 404 
>>
>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>
>>> There is a thread in the developer section where some questions were 
>>> asked that were not directly related to development. This thread is good. 
>>> I'm just inviting people to ask their questions here in this thread rather 
>>> than in the developer section.
>>>
>>>
>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>
 ???

 On Thu, 23 Jul 2020 at 19:39, galfert  wrote:

>>> For anyone discussing this new GW1000 API driver in the WeeWX 
> development section STOP. Use this user section instead to discuss its 
> use.
>
>
> -- 
> 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...@googlegroups.com.


> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>  
> 
> .
>


-- 
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/6760390b-8d52-4267-8a40-56ff89ef5b6cn%40googlegroups.com.

Re: [weewx-user] Re: New GW1000 Driver available for testing

[Bill Arthur]

I couldn't get it to run from the command line.
When I  did   python -m user.gw1000 --help
I get   /usr/bin/python: No module named user.gw1000

But I have it up and running, everything looks good on my Seasons page.
I'll give the data a closer look tomorrow.

But I'm scratching my head trying to find how to specify the IP address in 
weewx.conf
I have three GW1000s here, I have no idea which one is being used  
On Thursday, July 23, 2020 at 9:06:47 PM UTC-5 Bill Arthur wrote:

> This link works: 
> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/gw1000-0.1.0b4.tar.gz
>
> On Thursday, July 23, 2020 at 8:57:49 PM UTC-5 Bill Arthur wrote:
>
>> FYI:
>> wget -P /var/tmp 
>> https://github.com/gjr80/weewx-gw1000/releases/download/v0.1.0b4/weewx-gw1000-0.1.0b4.tar.gz
>>  
>> gives me an Error 404 
>>
>> On Thursday, July 23, 2020 at 3:22:07 PM UTC-5 galfert wrote:
>>
>>> There is a thread in the developer section where some questions were 
>>> asked that were not directly related to development. This thread is good. 
>>> I'm just inviting people to ask their questions here in this thread rather 
>>> than in the developer section.
>>>
>>>
>>> On Thursday, July 23, 2020 at 2:56:51 PM UTC-4, steeple ian wrote:
>>>
 ???

 On Thu, 23 Jul 2020 at 19:39, galfert  wrote:

>>> For anyone discussing this new GW1000 API driver in the WeeWX 
> development section STOP. Use this user section instead to discuss its 
> use.
>
>
> -- 
> 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...@googlegroups.com.


> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/91d513a8-cf9a-4cf2-8e16-261a02b67bebo%40googlegroups.com
>  
> 
> .
>


-- 
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/82d0a22f-2f73-43a9-b016-be349e19d221n%40googlegroups.com.

[weewx-user] NOAA error ?

[Olivier GARNIER]

How is it possible... Look at the total rain of mars...


The NOAA-2020-03.txt file :

   MONTHLY CLIMATOLOGICAL SUMMARY for mars 2020


NAME: Le Plessis Placy, France
ELEV: 130 mtresLAT: 49-03.48 NLONG: 002-59.22 E


   TEMPERATURE (C), RAIN (cm), WIND SPEED (km/h)

 HEAT   COOL AVG
  MEAN   DEGDEG  WIND   
DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
TIMEDIR
---
 01
 02
 03
 04
 05
 064,37,2  19:572,2  23:57   14,00,0   0,000,00,0  
19:57 90
 076,4   10,8  14:571,1  05:57   11,90,0   0,002,6   10,8  
13:57215
 088,2   10,3  16:445,9  23:25   10,10,0   0,368,6   37,4  
14:35198
 097,6   12,0  15:444,5  04:29   10,70,0   0,107,3   33,5  
11:37237
 10   11,1   14,1  16:567,0  02:057,30,0   0,31   12,4   37,8  
01:45201
 11   13,8   16,3  13:15   11,6  23:544,50,0   0,00   14,8   42,5  
11:40203
 12   10,3   12,9  15:326,0  23:578,00,0   0,15   12,8   35,3  
04:22243
 137,7   12,5  16:034,0  07:22   10,60,0   0,005,7   25,2  
09:25227
 148,0   10,3  17:165,6  07:35   10,30,0   0,104,2   29,5  
13:52172
 15   10,9   16,0  14:596,9  03:227,40,0   0,005,9   32,0  
14:35168
 169,2   12,0  11:216,0  05:309,20,0   0,000,8   15,8  
16:25328
 17   10,5   15,1  16:136,9  07:347,80,0   0,000,18,6  
01:25343
 18   12,7   17,9  15:599,0  00:595,60,0   0,000,3   11,9  
14:41191
 19   13,7   20,1  13:437,6  06:484,60,0   0,000,9   20,2  
13:25105
 20   11,8   16,9  13:387,9  23:576,50,0   0,004,5   30,6  
18:09 12
 217,18,3  14:395,7  07:42   11,20,0   0,057,8   26,6  
09:24 27
 227,6   12,2  17:194,5  08:24   10,70,0   0,007,4   49,0  
00:39 20
 236,4   12,2  15:331,1  07:01   11,90,0   0,003,3   20,5  
14:09 13
 246,4   13,1  17:250,0  06:10   11,90,0   0,001,8   16,2  
14:24 23
 256,6   12,2  16:230,6  06:55   11,80,0   0,002,9   17,6  
15:25 22
 266,2   11,0  15:561,1  06:50   12,10,0   0,004,3   34,6  
10:50 23
 278,0   14,1  15:201,8  07:25   10,40,0   0,002,6   20,2  
11:20346
 289,6   17,1  14:172,0  06:358,80,0   0,004,4   31,0  
21:34353
 296,19,0  14:003,6  07:50   12,20,0   0,009,6   51,8  
16:01 11
 304,8   10,0  16:35   -0,3  08:06   13,50,0   0,008,0   31,3  
15:06 24
 316,5   12,1  16:321,4  07:55   11,90,0   0,003,6   20,9  
12:32 24
---
   8,7   20,1 19   -0,3 30  255,00,0   1,095,4   51,8 
29265


=

The NOAA-2020.txt file :

  PRECIPITATION (mm)

  MAX ---DAYS OF RAIN---
  OBS.   OVER
 YR  MO  TOTALDAY  DATE   0.30   3.00  30.00

2020 01
2020 02
2020 03   10,93,608  6  2  0
2020 04   17,67,229  6  3  0
2020 05   16,19,310  5  2  0
2020 06   49,7   13,027 13  4  0
2020 073,62,102  2  0  0
2020 08
2020 09
2020 10
2020 11
2020 12

  97,9   13,0   juin 32 11  0


How can i correct this?

it's because it's the begening of the file ?


Thanks,

--
Olivier GARNIER
La ferme du pré
77440 Le Plessis Placy
+33 (0)6.11.99.92.62



--
L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel 
antivirus Avast.
https://www.avast.com/antivirus

--
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/a0851048-5667-297b-89ad-5b4eb2e7c293%40gmail.com.

[weewx-user] Re: NOAA error ?

[Andrew Milner]

Your monthly summary is in mm and the daily details are in cm.  What 
exactily is your problem?
Have you been making changes to the NOAA reports??



On Friday, 24 July 2020 07:30:34 UTC+3, Olivier GARNIER wrote:
>
> How is it possible... Look at the total rain of mars...
>
>
> The NOAA-2020-03.txt file :
>
>MONTHLY CLIMATOLOGICAL SUMMARY for mars 2020
>
>
> NAME: Le Plessis Placy, France  
> ELEV: 130 mtresLAT: 49-03.48 NLONG: 002-59.22 E
>
>
>TEMPERATURE (C), RAIN (cm), WIND SPEED (km/h)
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND 
>   DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH   
> TIMEDIR
> ---
>  01
>  02
>  03
>  04
>  05
>  064,37,2  19:572,2  23:57   14,00,0   0,000,00,0  
> 19:57 90
>  076,4   10,8  14:571,1  05:57   11,90,0   0,002,6   10,8  
> 13:57215
>  088,2   10,3  16:445,9  23:25   10,10,0   0,368,6   37,4  
> 14:35198
>  097,6   12,0  15:444,5  04:29   10,70,0   0,107,3   33,5  
> 11:37237
>  10   11,1   14,1  16:567,0  02:057,30,0   0,31   12,4   37,8  
> 01:45201
>  11   13,8   16,3  13:15   11,6  23:544,50,0   0,00   14,8   42,5  
> 11:40203
>  12   10,3   12,9  15:326,0  23:578,00,0   0,15   12,8   35,3  
> 04:22243
>  137,7   12,5  16:034,0  07:22   10,60,0   0,005,7   25,2  
> 09:25227
>  148,0   10,3  17:165,6  07:35   10,30,0   0,104,2   29,5  
> 13:52172
>  15   10,9   16,0  14:596,9  03:227,40,0   0,005,9   32,0  
> 14:35168
>  169,2   12,0  11:216,0  05:309,20,0   0,000,8   15,8  
> 16:25328
>  17   10,5   15,1  16:136,9  07:347,80,0   0,000,18,6  
> 01:25343
>  18   12,7   17,9  15:599,0  00:595,60,0   0,000,3   11,9  
> 14:41191
>  19   13,7   20,1  13:437,6  06:484,60,0   0,000,9   20,2  
> 13:25105
>  20   11,8   16,9  13:387,9  23:576,50,0   0,004,5   30,6  
> 18:09 12
>  217,18,3  14:395,7  07:42   11,20,0   0,057,8   26,6  
> 09:24 27
>  227,6   12,2  17:194,5  08:24   10,70,0   0,007,4   49,0  
> 00:39 20
>  236,4   12,2  15:331,1  07:01   11,90,0   0,003,3   20,5  
> 14:09 13
>  246,4   13,1  17:250,0  06:10   11,90,0   0,001,8   16,2  
> 14:24 23
>  256,6   12,2  16:230,6  06:55   11,80,0   0,002,9   17,6  
> 15:25 22
>  266,2   11,0  15:561,1  06:50   12,10,0   0,004,3   34,6  
> 10:50 23
>  278,0   14,1  15:201,8  07:25   10,40,0   0,002,6   20,2  
> 11:20346
>  289,6   17,1  14:172,0  06:358,80,0   0,004,4   31,0  
> 21:34353
>  296,19,0  14:003,6  07:50   12,20,0   0,009,6   51,8  
> 16:01 11
>  304,8   10,0  16:35   -0,3  08:06   13,50,0   0,008,0   31,3  
> 15:06 24
>  316,5   12,1  16:321,4  07:55   11,90,0   0,003,6   20,9  
> 12:32 24
> ---
>8,7   20,1 19   -0,3 30  255,00,0   1,095,4   51,8 
> 29265
>
>
>
> =
>
> The NOAA-2020.txt file :
>
>   PRECIPITATION (mm)
>
>   MAX ---DAYS OF RAIN---
>   OBS.   OVER
>  YR  MO  TOTALDAY  DATE   0.30   3.00  30.00
> 
> 2020 01
> 2020 02
> 2020 03   10,93,608  6  2  0
> 2020 04   17,67,229  6  3  0
> 2020 05   16,19,310  5  2  0
> 2020 06   49,7   13,027 13  4  0
> 2020 073,62,102  2  0  0
> 2020 08
> 2020 09
> 2020 10
> 2020 11
> 2020 12
> 
>   97,9   13,0   juin 32 11  0
>
>
>
> How can i correct this?
>
> it's because it's the begening of the file ?
>
>
> Thanks,
>
> -- 
> Olivier GARNIER
> La ferme du pré
> 77440 Le Plessis Placy
> +33 (0)6.11.99.92.62
>
>
>
> 
>  Garanti 
> sans virus. www.avast.com 
> 
>  
> <#a0851048-5667-297b-89ad-5b4eb2e7c293@gmail.com_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To u