Re: [weewx-user] Is WeeWx 5.0 beta stable enough for non-experts to fool around with?

[Matthias Manhart]

Thanks Vince for the script - very helpful for testing. I could rebuild my 
weewx on a test raspberry pi 4 with the extensions cmon, mqtt, 
mqtt-subscribe and the Belchertown skin.

vince schrieb am Donnerstag, 31. August 2023 um 20:34:10 UTC+2:

FWIW, I have a github repo (here) 
 with a bash script 
that automates the v5 pip install, installs and configures nginx and my 
'mem' extension, hooks weewx into the nginx web, and starts it all up.  I 
use this on pi and vagrant virtual machines to fiddle with the v5 beta.

Works for me as a one-step installer on a 'clean' sacrificial system and 
it's tested on several os variants.

 Please read the toplevel readme file and do a quick read of the example 
logfile it generates to see what it does step-by-step.

-- 
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/54d3a850-b4db-4451-b203-f3e7a80dd1b4n%40googlegroups.com.

Re: [weewx-user] Barometer and pressure once again

[gszla...@gmail.com]

No wonder the OP is confused. 

In Europe, METARs generally don’t have SLP, they have QNH stated as a “Q 
code” in the actual METAR report. An Altimeter /QNH reading of 1022 would 
be Q1022 in the METAR report.

So typically, QNH > QFF when current or average outside temps are greater 
than the ISA temp for his elevation. That is the reason why the OP remarks 
that he is “missing” 7 hPa:

[I]> METAR for  EPWR airport shows 1015 hPa. So I need to "collect" 
additional ~7 hPa 
> (1015 from METAR minus 1007.8 from Weewx calculations)[/I]

The OP is smarter than us because WeeWX SLP is 1007.8 and Altimeter/QNH = 
1015.
Two different things entirely!

So let’s take a step back and try this again. We want to match 
Altimeter/QNH.

1. The OP is trying to calibrate by matching QNH at airport (EPWR)
2. You need to use an Altimeter calculator or ISA calculator, not a SLP 
calculator.

Let’s redo the REL offset for a 560m sensor elevation:

1013.25 – 947.760 = 65.49 (65.5 rounded)

The 947.76 is the fixed ISA pressure for any 560m elevation. You can use a 
standard atmosphere calculator or Altimeter calculator to calculate it.

Therefore, for a 560m elevation, QNH must always be 65.5 hPa higher than 
whatever the Fine Offset station pressure is at the moment or looking at it 
from a sea level perspective, station pressure must be 65.5 hPa lower than 
QNH.

EXAMPLE: 

If EPWR is showing Q1022 then:

1022(REL) – 65.5(REL offset) = 956.5 (ABS) station pressure.
i.e. REL= QNH at airport minus your offset = station pressure at your 
location (560m).

To calibrate, you can either:

1. Set REL = 1022 and set your ABS = 956.5.

or

2. Add 65.5 to your existing ABS value and then compare the REL value on 
your display to the QNH value at the airport. Adjust the ABS value up or 
down until the REL display is the same as QNH as the airport. ABS and REL 
on your display move lock-in-step. To change the REL value, you have to 
change the ABS value. REL must always show to be 65.5 higher than your 
current live ABS reading. There will be a lot of button pushing involved, 
but make sure the “spread” or pressure difference between REL and ABS is 
always 65.5.

The first method is obviously a shortcut method. It is the simplest, and 
you still have to lookup your ISA pressure for your elevation, but you 
won’t learn much about the process.

The second method is the method I usually recommend. I am assuming the OP 
is configuring his barometer on a display console and must be using the 
ABS/REL system instead of the offset system.
The Fine Offset manufactured WiFi gateways use a different system. They are 
a display-less console that uses a ABS offset/REL offset system.

If the OP is still running into calibration snags, I would encourage him to 
post his quesion at wxforum.net in the Ambient/Ecowitt/Fine Offset clone 
forum.

On Friday, September 1, 2023 at 8:44:11 PM UTC-4 Greg Troxel wrote:

> Tomasz Lewicki  writes:
>
> > I'm back and starting my reply from Rainer's last question. Yes, I've
> > read this topic:
> > https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter
> > on the very beginning. I use only 'pressure' and 'barometer' terms
> > below, according to definitions from wiki.
> >
> > So, I'm even more confused than before. I've made the calculations
> > with the calculator listed in
> > https://www.wxforum.net/index.php?topic=40730.0 (direct link:
> > https://keisan.casio.com/exec/system/1224575267 - BTW they will close
> > at September 20) with my current conditions (pressure 944.5 hPa,
> > temperature 20*C, height of sensor 560 m AMSL) and got result 1007.8
> > hPa - this is perfectly equal to what I see on my webpage - 1007.7 hPa
> > calculated by Weewx algorithm (difference of 1/10th of hPa is
> > neglible). I recall that I use 'software' option in weewx.conf for
> > 'barometer' but 'prefer_hardware' for 'pressure'.
>
> This confirms that weewx's calculation matches the web calculator, that
> IF your station pressure is 944.5 hPa then the barometric pressure is
> 1007.7 or .8 hPa. It has ZERO information about whether the station
> pressure measurement is accurate.
>
> > But very accurate numerical forecast for my location *and* METAR for
> > EPWR airport shows 1015 hPa. So I need to "collect" additional ~7 hPa
> > (1015 from METAR minus 1007.8 from Weewx calculations). Does it mean I
> > should:
>
> This means that it is likely that the station pressure at your location
> is about 7 hPa higher than the sensor reads.
>
> > a) add whole calculated offset - ~70 hPa (1015 from METAR minus ~945
> > of absolute pressure) - in my PWS console
>
> This will result in wrong station pressure readings, because you are
> using the console to go from wrong station pressure to fake barometric
> pressure. I would advise against this.
>
> > or
> >
> > b) add smaller offset - 63.3 hPa (1007.8 calculated by Weewx minus
> > 944.5 read by sensor) PLUS use relevant section in weewx.conf:
>
> This is confusing, but if weewx

Re: [weewx-user] Re: Problem with wee_import utility (rain field)

[Remy Lavabre]

Thanks Gary,

My fields, including for rain, incremented automatically yesterday for the 
first time!
Your solution was the right one and I still don't understand why the 
previous time the rain was not taken into account in my weewx database

However, thank you for your explanations which helped me progress and 
allowed me to resolve my problem!

[image: Capture d’écran du 2023-09-03 14-27-35.png]



Le mercredi 30 août 2023 à 22:27:29 UTC+2, gjr80 a écrit :

> Some comments below.
>
> Gary
>
> On Wednesday, 30 August 2023 at 20:02:01 UTC+10 remy.l...@gmail.com wrote:
>
> Actually, to make it simple for you, I have a weather station that doesn't 
> have a USB output. The data is sent to AWEKAS. So in python, for 5 minutes 
> I retrieve this data regularly, make an average for certain fields 
> (temperatures, hygrometry etc.) and for others take the maximum (rain rate) 
> during these 5 minutes. For rain, the station gives me the total since 
> 00:00 which I calculate into rain over the 5 minute time slot.
> After 5 minutes, I generate a CSV which will be integrated into the weewx 
> database with Wee_import.
> Weewx recalculates all the data, generates the html page and the csv file 
> is deleted.
> We start again every 5 minutes.
>
>  
> You have a complex, automated system for using wee_import. I would be 
> looking very carefully at what data wee_import is actually being fed, it 
> might not be what you think it is.
>  
>
> Do you think that a rainRate at 0 with a rain value in the rain field 
> could cause a problem during the integration and set both fields to 0?
>
>
> I don't think this is likely. wee_import will import data if the field 
> map is valid and consistent, the field map fields are found in the source 
> data and the field value is (in this case) numeric. 0 is nothing special, 
> just another number. The import processing of one imported field has no 
> impact on any other imported field.
>
>

-- 
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/4a8e03a6-e0f0-44b9-832b-572c339d04bdn%40googlegroups.com.

[weewx-user] Rain days from current year on homepage of Berlchertown skin

[Matthias Manhart]

The original file "\skins\Belchertown\index.html.tmpl" shows the max/min 
values of the current month:

  
  
  
  
  
  
  
  $obs.label.snapshot_high:$month.outTemp.max
  $obs.label.snapshot_low:$month.outTemp.min
  
  
  $obs.label.snapshot_month_avg_wind:   
 $month.wind.avg
  $obs.label.snapshot_month_high_wind:   
 $month.wind.max
  
  
  $obs.label.snapshot_month_rain:   
 $month.rain.sum
  $obs.label.snapshot_month_rainrate:   
 $month.rainRate.max
  
  
  

I modified this section to show the max/min values of the current year:

  
  
  
  
  
  
  
  $obs.label.snapshot_low:$year.outTemp.min
  $obs.label.snapshot_high:$year.outTemp.max
  
  
  $obs.label.snapshot_month_avg_wind:$year.wind.avg
  $obs.label.snapshot_month_high_wind:   
 $year.wind.max
  
  
  $obs.label.snapshot_month_rain:$year.rain.sum
  $obs.label.snapshot_month_rainrate:$year.rainRate.max
  
  
  $obs.label.snapshot_baro_low:$year.barometer.min
  $obs.label.snapshot_baro_high:$year.barometer.max
  
  
  

I would like to show the number of rain days of the current year instead of 
the max rain rate. How can i show this value ?

Regards

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/a16ae8b7-5a8d-4636-9067-5902efb5ccfbn%40googlegroups.com.

Re: [weewx-user] Rain days from current year on homepage of Berlchertown skin

[Tom Keffer]

To show the number of days with more than 1mm of rain so far this year:

*$year.rain.sum_ge((1, "mm"))*



On Sun, Sep 3, 2023 at 12:48 PM Matthias Manhart 
wrote:

> The original file "\skins\Belchertown\index.html.tmpl" shows the max/min
> values of the current month:
>
>   
>   
>   
>   
>   
>   
>   
>   $obs.label.snapshot_high: class="monthstatshigh">$month.outTemp.max
>   $obs.label.snapshot_low: class="monthstatslow">$month.outTemp.min
>   
>   
>   $obs.label.snapshot_month_avg_wind:
>  $month.wind.avg
>   $obs.label.snapshot_month_high_wind:
>  $month.wind.max
>   
>   
>   $obs.label.snapshot_month_rain:
>  $month.rain.sum
>   $obs.label.snapshot_month_rainrate:
>  $month.rainRate.max
>   
>   
>   
>
> I modified this section to show the max/min values of the current year:
>
>   
>   
>   
>   
>   
>   
>   
>   $obs.label.snapshot_low: class="yearstatslow">$year.outTemp.min
>   $obs.label.snapshot_high: class="yearstatshigh">$year.outTemp.max
>   
>   
>   $obs.label.snapshot_month_avg_wind: class="yearstatswindavg">$year.wind.avg
>   $obs.label.snapshot_month_high_wind:
>  $year.wind.max
>   
>   
>   $obs.label.snapshot_month_rain: class="yearstatsrain">$year.rain.sum
>   $obs.label.snapshot_month_rainrate: class="yearstatsrainrate">$year.rainRate.max
>   
>   
>   $obs.label.snapshot_baro_low: class="yearstatsblow">$year.barometer.min
>   $obs.label.snapshot_baro_high: class="yearstatsbhigh">$year.barometer.max
>   
>   
>   
>
> I would like to show the number of rain days of the current year instead
> of the max rain rate. How can i show this value ?
>
> Regards
>
> 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/a16ae8b7-5a8d-4636-9067-5902efb5ccfbn%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/CAPq0zEDcXCiZDWHB63ptxeL7RDU2qJ8zWnGj5jikE8x6wGyrag%40mail.gmail.com.

[weewx-user] weewx V5 report not updating

[Greg from Oz]

I have noticed lately that the time on my weather page was not updating and 
it used to update every 5 minutes but now it is showing anytime 15 minutes 
or 20 minutes.
I found this in my log files:

Sep  4 11:00:27 moonbi weewx[2360287] INFO weewx.engine: Launch of report 
thread aborted: existing report thread still running

Is there a way to see the report has finished?
I have looked at htop and have notice /usr/sbin/mariadbd is at the top of 
the list. Maybe the database is slow.
I will look at that now
Thanks

-- 
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/e695e948-b5ae-40d1-83e5-25e932916a20n%40googlegroups.com.

[weewx-user] Re: weewx V5 report not updating

[Greg from Oz]

I had wdc skin enabled as well as Responsive skin.
I disabled wdc skin an does seems to have generated the report every 5 
minutes now.
Will keep monitoring it further.

I guess it was wdc:
Sep  3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: 
Generated 11 files for report WdcReport in 330.15 seconds


On Monday, 4 September 2023 at 11:09:29 UTC+10 Greg from Oz wrote:

> I have noticed lately that the time on my weather page was not updating 
> and it used to update every 5 minutes but now it is showing anytime 15 
> minutes or 20 minutes.
> I found this in my log files:
>
> Sep  4 11:00:27 moonbi weewx[2360287] INFO weewx.engine: Launch of report 
> thread aborted: existing report thread still running
>
> Is there a way to see the report has finished?
> I have looked at htop and have notice /usr/sbin/mariadbd is at the top of 
> the list. Maybe the database is slow.
> I will look at that now
> Thanks
>

-- 
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/5d0af068-6a61-4e43-b96b-feacb663b1fan%40googlegroups.com.

Re: [weewx-user] weewx V5 report not updating

[Graham Eddy]

perhaps it was generating all reports, as from a clean slate, and in future it 
could just be incremental and less of an issue
⊣GE⊢

> On 4 Sep 2023, at 12:10 pm, Greg from Oz  wrote:
> 
> I guess it was wdc:
> Sep  3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: Generated 
> 11 files for report WdcReport in 330.15 seconds
> 

-- 
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/13A10622-1DBF-4572-97B4-76EE2EB57FD5%40geddy.au.

Re: [weewx-user] weewx V5 report not updating

[Greg from Oz]

It has been doing it days
There were a lot of entries in the syslog.


On Monday, 4 September 2023 at 12:32:27 UTC+10 Graham Eddy wrote:

> perhaps it was generating all reports, as from a clean slate, and in 
> future it could just be incremental and less of an issue
> *⊣GE⊢*
>
> On 4 Sep 2023, at 12:10 pm, Greg from Oz  wrote:
>
> I guess it was wdc:
> Sep  3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: 
> Generated 11 files for report WdcReport in 330.15 seconds
>
>
>

-- 
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/b0985838-f629-4663-b0ab-fc92ccb5c340n%40googlegroups.com.

Re: [weewx-user] weewx V5 report not updating

[vince]

Perhaps try turning WDC off and see if the problem goes away.  Certainly a 
skin taking longer than your archive period to complete is going to cause 
havoc for your setup

On Sunday, September 3, 2023 at 7:34:39 PM UTC-7 Greg from Oz wrote:

> It has been doing it days
> There were a lot of entries in the syslog.
>
>
> On Monday, 4 September 2023 at 12:32:27 UTC+10 Graham Eddy wrote:
>
>> perhaps it was generating all reports, as from a clean slate, and in 
>> future it could just be incremental and less of an issue
>> *⊣GE⊢*
>>
>> On 4 Sep 2023, at 12:10 pm, Greg from Oz  wrote:
>>
>> I guess it was wdc:
>> Sep  3 00:21:24 moonbi weewx[1440347] INFO weewx.cheetahgenerator: 
>> Generated 11 files for report WdcReport in 330.15 seconds
>>
>>
>>

-- 
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/645eca08-45ee-43b5-a0b6-c11a2be211d5n%40googlegroups.com.