Re: [weewx-user] comma in label in Seasons skin.conf causes failure

2023-08-30 Thread Graham Eddy 
for the forum search record, you can do a lot of stuff (especially using 
services) within one instance of weewx. you only *must* use separate instances 
when you need multiple drivers, or services conflict with each other. you *may* 
separate instances for operational or scalability purposes
⊣GE⊢

> On 31 Aug 2023, at 9:09 am, cric...@pobox.com  wrote:
> 
> I'm setting up yet another weewx instance, this time for plotting a solar 
> charge controller.

-- 
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/C6EEC707-1DBC-4DE6-9986-44F604492511%40geddy.au.

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

2023-08-30 Thread DR 

Thanks.  Dale


On 8/30/2023 8:11 PM, Tom Keffer wrote:
It's pretty stable. Most of the work now is about smoothing out the 
installation process.


-tk

On Wed, Aug 30, 2023 at 6:07 PM DR  wrote:

I have looked gitHub and see there is a 5.0 beta out there.


I am wondering if it is stable enough for a casual user to fiddle
around
with it before official release, or should only experts be using
it now
to test and give feedback to the developers?


Just curious.  Dale


-- 
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/98fdaa7f-ab40-26e7-326e-dd958fb6695c%40gmail.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/CAPq0zEBQ8tRZ6Nig-LZAw2xNx9mgqAngwDtXHqD0UBtKavnX4w%40mail.gmail.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/999bfae2-d365-0471-7562-5f001acf1a66%40gmail.com.

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

2023-08-30 Thread Tom Keffer 
It's pretty stable. Most of the work now is about smoothing out the
installation process.

-tk

On Wed, Aug 30, 2023 at 6:07 PM DR  wrote:

> I have looked gitHub and see there is a 5.0 beta out there.
>
>
> I am wondering if it is stable enough for a casual user to fiddle around
> with it before official release, or should only experts be using it now
> to test and give feedback to the developers?
>
>
> Just curious.  Dale
>
>
> --
> 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/98fdaa7f-ab40-26e7-326e-dd958fb6695c%40gmail.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/CAPq0zEBQ8tRZ6Nig-LZAw2xNx9mgqAngwDtXHqD0UBtKavnX4w%40mail.gmail.com.

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

2023-08-30 Thread DR 

I have looked gitHub and see there is a 5.0 beta out there.


I am wondering if it is stable enough for a casual user to fiddle around 
with it before official release, or should only experts be using it now 
to test and give feedback to the developers?



Just curious.  Dale


--
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/98fdaa7f-ab40-26e7-326e-dd958fb6695c%40gmail.com.

Re: [weewx-user] comma in label in Seasons skin.conf causes failure

2023-08-30 Thread Tom Keffer 
If a string has a comma in it, configobj
, the configuration manager,
interprets it as a list. That's why you have to quote it.

On Wed, Aug 30, 2023 at 4:09 PM cric...@pobox.com 
wrote:

> I'm setting up yet another weewx instance, this time for plotting a solar
> charge controller.
> Not stuck on this, but ran into an issue where having a comma in a label
> name causes
> the traceback below.  I didn't try quoting the string, but removing the
> comma cleared
> the issue.
> This is the latest version; 4.10.2.
>   Here's the config that causes the issue:
> [[[dayBatteryPwr]]]
> battV
> battC
>label = Battery Voltage, Current
> and the error:
> Traceback (most recent call last):
>   File "/home/crichmon/weewx/bin/weewx/reportengine.py", line 197, in run
> obj.start()
>   File "/home/crichmon/weewx/bin/weewx/reportengine.py", line 385, in start
> self.run()
>   File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 42, in run
> self.gen_images(self.gen_ts)
>   File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 107, in
> gen_images
> plot = self.gen_plot(plotgen_ts,
>   File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 293, in
> gen_plot
> label = self.text_dict.get(label, label)
>   File "/usr/lib/python3/dist-packages/configobj.py", line 642, in get
> return self[key]
>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in
> __getitem__
> val = dict.__getitem__(self, key)
> TypeError: unhashable type: 'list'
>
> Thx,Chris
>
> --
> 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/06808da0-95e7-4b9b-aad9-11fe17648360n%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/CAPq0zEDYC_pcw4XW22oMe1wqnhhOD%3D_wZS40_3jwCXZm7kvwzQ%40mail.gmail.com.

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

2023-08-30 Thread Greg Troxel 
from the wiki page I sent

  For example, the FineOffset consoles can display either the station
  pressure (called 'absolute' pressure) or the station pressure plus an
  offset (called 'relative' pressure). T

So Fine Offset equipment just does pressure badly.

So get station pressure into weewx, do software from that, and tape over
the "relative pressure" display on the console so nobody can see it!

-- 
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/rmir0nkf3kj.fsf%40s1.lexort.com.

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

2023-08-30 Thread Greg Troxel 
Tomasz Lewicki  writes:

> I'm trying to sort out barometer and pressure values. I own HP1001 clone. 
> Internal T/H/P sensor was calibrated with my friends certified barometer 
> before. Currently it sensor shows absolute pressure value 936,7 hPa and it 
> almost perfectly (+/- 1 hPa) aligns with very accurate numerical forecast 
> for my location. Same meteogram show also relative pressure 1007 (+/- 1 
> hPa) for my location. METAR for nearby (43 km) airport shows 1008 hPa. 
>
> Relative pressure displayed by my HP1001 is about 20 hPa higher than 
> absolute - obviously too low value because I'm located about 550 m AMSL.

I have not fully dealt with this and I don't know your hardware, but I
have thought about it a lot.  But some advice:

  do not just twiddle without understanding

  a station that reports other than station pressure and doesn't let you
  enter elevation/altitude (distance above the nominal 0 level at sea
  level ish*) is designed wrong.  The station might be near the ground
  and it might be in an upper floor.  There is no way to know elevation
  from horizontal location.

  use the proper terms when discussing and thinking.
  https://github.com/weewx/weewx/wiki/Barometer,-pressure,-and-altimeter

  understand the data flow of your station.  surely it is measuring
  station pressure, but often it will convert to one of the others and
  then that is all you can extract.

  understand that weewx can convert, but needs to have altitude

  understand that measuring altitude is quite difficult at the 1m level,
  and that 1 hPa is about 8.3 m.  reading a value from a non-RTK GNSS
  (GPS, Galileo etc.) is just not that accurate.

  There is a calibration for the sensor, which is perhaps adequately
  modeled as an offset in station pressure.

  you then have to get altitude right, and calculations right

  by adjusting altitude it is sort of like adjusting the station
  pressure offset.  This may be the best you can do, depending on what
  the unit reports and how it gets altitude.


Overall, I suspect your unit has got a bad elevation value for where you
are somehow, and you have made it display station pressure correctly.
It seems to think you are ~160m lower than you are.

I would look on forums to find out how your unit is supposed to work.

Or get a BME280, calibrate that with your friend's instrument (they are
pretty repeatable but have multi-hPa absolute calibration), and use that
as station pressure instead, and have weewx do it is software.



* the meaning of elevation remains unclear.  Probably the height
  according to your country's national vertical datum is appropriate.
  If you are really in .pl, that's probably in EVRF2007, but even if
  it's not, they are almost all very close.

-- 
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/rmiv8cwf3nh.fsf%40s1.lexort.com.

[weewx-user] comma in label in Seasons skin.conf causes failure

2023-08-30 Thread cric...@pobox.com 
I'm setting up yet another weewx instance, this time for plotting a solar 
charge controller.
Not stuck on this, but ran into an issue where having a comma in a label 
name causes
the traceback below.  I didn't try quoting the string, but removing the 
comma cleared
the issue.
This is the latest version; 4.10.2.
  Here's the config that causes the issue:
[[[dayBatteryPwr]]]
battV
battC
   label = Battery Voltage, Current
and the error:
Traceback (most recent call last):
  File "/home/crichmon/weewx/bin/weewx/reportengine.py", line 197, in run
obj.start()
  File "/home/crichmon/weewx/bin/weewx/reportengine.py", line 385, in start
self.run()
  File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 42, in run
self.gen_images(self.gen_ts)
  File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 107, in 
gen_images
plot = self.gen_plot(plotgen_ts,
  File "/home/crichmon/weewx/bin/weewx/imagegenerator.py", line 293, in 
gen_plot
label = self.text_dict.get(label, label)
  File "/usr/lib/python3/dist-packages/configobj.py", line 642, in get
return self[key]
  File "/usr/lib/python3/dist-packages/configobj.py", line 554, in 
__getitem__
val = dict.__getitem__(self, key)
TypeError: unhashable type: 'list'

Thx,Chris

-- 
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/06808da0-95e7-4b9b-aad9-11fe17648360n%40googlegroups.com.

Re: [weewx-user] How to get the daily rain sum

2023-08-30 Thread Invisible Man 
Ah, it looks like $day.rain.sum works in a template... :)

On Wednesday, August 30, 2023 at 7:00:17 PM UTC+2 Invisible Man wrote:

> Ok, so I'm switching to templates, but I'm doing something wrong, because 
> I can't get that rain sum. In my case it just prints 
> "$since($hour=0).rain.sum.format("%.3f")" instead of showing the value.
> How did you do it?
> This is my `mastodon.txt.tmpl` (there are a few errors in my template e.g 
> I shouldn't add C etc, but nevermind) :
>
> ```
> #errorCatcher Echo
> ## Template file for providing data to weewx-mastodon
> ## https://github.com/glennmckechnie/weewx-mastodon
> ##
> ## Tag information at...
> ## https://weewx.com/docs/customizing.htm#Tags
>
> Temprature: $current.outTempC (min: $day.outTemp.min, max: 
> $day.outTemp.max)
> Humidex: $current.heatindex (min: $day.heatindex.min, max: 
> $day.heatindex.max)
> Humidit: $current.outHumidity % (min: $day.outHumidity.min, max: 
> $day.outHumidity.max)
> Pression: $current.barometer
> Pluie
> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
> - Anne: $year.rain.sum
> Vent:
> - Direction: $current.windDir.ordinal_compass ($current.windDir deg)
> -Vitesse: $current.windSpeed (moyenne), $current.windGust (rafale)
> 
> $current.dateTime.format("%d-%b-%Y %H:%M")
> ``
>
> This is the generated mastodon.txt : 
>
> Temprature: 23.2CC (min: 16.0C, max: 27.0C)
> Humidex: 23.4C (min: 15.6C, max: 27.9C)
> Humidit: 70% % (min: 48%, max: 78%)
> Pression: 1008.9 hPa
> Pluie
> - Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
> - Anne: 201.3 mm
> Vent:
> - Direction: E (97 deg)
> - Vitesse: 0 km/h (moyenne), 4 km/h (rafale)
> 
> 30-Aug-2023 18:50
>
> On Wednesday, August 30, 2023 at 12:07:00 AM UTC+2 Glenn McKechnie wrote:
>
>> On 30/08/2023, Invisible Man  wrote: 
>> > Thanks to both of you for your replies. 
>> > 
>> > - since.py etc are in /usr/share/weewx/user already so indeed I can try 
>> and 
>>
>> since.py is part of the weewx-mastodon install. 
>>
>> > use them. I tried to directly use since in the format line of 
>> > weewx-mastodon, but haven't succeeded yet: 
>> > `{since($hour=24).rain.sum:%.3f}` , `{since(hour=24).rain.sum:%.3f}`... 
>> not 
>> > sure I can do it like that. 
>>
>> As you found, these won't work on the raw (archive) data. 
>>
>> > - I'll look in the template file. 
>>
>> The example template I mentioned already uses since.py to format the 
>> rain value as ... 
>> $since($hour=9).rain.sum (Australian reporting times) 
>>
>> According to the weewx manual at 
>> http://www.weewx.com/docs.html/latest/customizing.htm#Formatting_examples 
>> A format method to use for your example could be... 
>> $since($hour=9).rain.sum.format("%.3f") 
>> I just tested that method and it works. Apparently we've had 7.429 mm of 
>> rain! 
>>
>> > - final option is that I directly tweak wxtoot.py ... 
>> > I'll investigate and post back if I have a question... or with my 
>> solution 
>> > if I succeed :) 
>>
>> Done :) 
>>
>> -- 
>>
>>
>> Cheers 
>> Glenn 
>>
>> rorpi - read only raspberry pi & various weewx addons 
>> https://github.com/glennmckechnie 
>>
>

-- 
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/cb2d2c64-4778-4f86-a070-f7c8f0ca59fan%40googlegroups.com.

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

2023-08-30 Thread gjr80 
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/02fc300d-5449-4831-b6a9-2ebba3f83ce0n%40googlegroups.com.

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

2023-08-30 Thread 'Rainer Lang' via weewx-user 

yes - why not calibrate your console first
when you see that the offset between absolute and relative pressure for 
your location used is wrong, just adjust it 

the the first basic step I'd say

even though, when your absolute (=local) pressure reading is correct, 
and your have the weewx option in weewx.conf set to software, weewx 
should calculate the proper relative value (taking into account the 
average temperature of the past 12 hours afaik).


"When calculated by Weewx itself ("software" option enabled in 
weewx.conf), my weather station shows 1001 hPa - still too low. " - I 
guess what you want to say is not that your station shows too low a 
value, but that weewx caluclates too low a value for your station (these 
are two different things) - your station will continue to show what its 
reads and what it is calibrated for. Weewx has no feedback to you station.


On 30.08.2023 20:21, Tomasz Lewicki wrote:
I'm trying to sort out barometer and pressure values. I own HP1001 
clone. Internal T/H/P sensor was calibrated with my friends certified 
barometer before. Currently it sensor shows absolute pressure value 
936,7 hPa and it almost perfectly (+/- 1 hPa) aligns with very 
accurate numerical forecast for my location. Same meteogram show also 
relative pressure 1007 (+/- 1 hPa) for my location. METAR for nearby 
(43 km) airport shows 1008 hPa.


Relative pressure displayed by my HP1001 is about 20 hPa higher than 
absolute - obviously too low value because I'm located about 550 m AMSL.


When calculated by Weewx itself ("software" option enabled in 
weewx.conf), my weather station shows 1001 hPa - still too low. Of 
course I checked location setting and AMSL value and unit - in my 
opinion they are properly set. Should I change something in weather 
station settings? I can set only coordinates, not the AMSL height.

--
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/db197c6f-dd1e-485c-9627-5cf5e12f1f3cn%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/77643a76-bba6-9026-7f1d-654be1391738%40gmail.com.

[weewx-user] Barometer and pressure once again

2023-08-30 Thread Tomasz Lewicki 
I'm trying to sort out barometer and pressure values. I own HP1001 clone. 
Internal T/H/P sensor was calibrated with my friends certified barometer 
before. Currently it sensor shows absolute pressure value 936,7 hPa and it 
almost perfectly (+/- 1 hPa) aligns with very accurate numerical forecast 
for my location. Same meteogram show also relative pressure 1007 (+/- 1 
hPa) for my location. METAR for nearby (43 km) airport shows 1008 hPa. 

Relative pressure displayed by my HP1001 is about 20 hPa higher than 
absolute - obviously too low value because I'm located about 550 m AMSL.

When calculated by Weewx itself ("software" option enabled in weewx.conf), 
my weather station shows 1001 hPa - still too low. Of course I checked 
location setting and AMSL value and unit - in my opinion they are properly 
set. Should I change something in weather station settings? I can set only 
coordinates, not the AMSL height. 

-- 
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/db197c6f-dd1e-485c-9627-5cf5e12f1f3cn%40googlegroups.com.

Re: [weewx-user] How to Stop Posting Results from Bad Sensor

2023-08-30 Thread Chuck Rhode 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wed, 30 Aug 2023 07:46:21 -0700
Tom Keffer  wrote:

> [StdCalibrate]
>   [[Corrections]]
> ...
> windDir = None

Easy Peasy!  Thanks!

- -- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 65° — Wind NE 12 mph — Sky mostly clear.

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCZO+HGgAKCRBg2/xipKOW
Urg5AJ0WwJOrA8xbsiOQWnEywig9ap5EzQCbBKvtErNVTkxNpPWsqhQHucimQS0=
=99KO
-END PGP SIGNATURE-

-- 
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/20230830131450.5a866c56%40BigTimber.LacusVeris.com.

Re: [weewx-user] How to get the daily rain sum

2023-08-30 Thread Invisible Man 
Ok, so I'm switching to templates, but I'm doing something wrong, because I 
can't get that rain sum. In my case it just prints 
"$since($hour=0).rain.sum.format("%.3f")" instead of showing the value.
How did you do it?
This is my `mastodon.txt.tmpl` (there are a few errors in my template e.g I 
shouldn't add C etc, but nevermind) :

```
#errorCatcher Echo
## Template file for providing data to weewx-mastodon
## https://github.com/glennmckechnie/weewx-mastodon
##
## Tag information at...
## https://weewx.com/docs/customizing.htm#Tags

Temprature: $current.outTempC (min: $day.outTemp.min, max: 
$day.outTemp.max)
Humidex: $current.heatindex (min: $day.heatindex.min, max: 
$day.heatindex.max)
Humidit: $current.outHumidity % (min: $day.outHumidity.min, max: 
$day.outHumidity.max)
Pression: $current.barometer
Pluie
- Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
- Anne: $year.rain.sum
Vent:
- Direction: $current.windDir.ordinal_compass ($current.windDir deg)
-Vitesse: $current.windSpeed (moyenne), $current.windGust (rafale)

$current.dateTime.format("%d-%b-%Y %H:%M")
``

This is the generated mastodon.txt : 

Temprature: 23.2CC (min: 16.0C, max: 27.0C)
Humidex: 23.4C (min: 15.6C, max: 27.9C)
Humidit: 70% % (min: 48%, max: 78%)
Pression: 1008.9 hPa
Pluie
- Aujourd'hui: $since($hour=0).rain.sum.format("%.3f")
- Anne: 201.3 mm
Vent:
- Direction: E (97 deg)
- Vitesse: 0 km/h (moyenne), 4 km/h (rafale)

30-Aug-2023 18:50

On Wednesday, August 30, 2023 at 12:07:00 AM UTC+2 Glenn McKechnie wrote:

> On 30/08/2023, Invisible Man  wrote:
> > Thanks to both of you for your replies.
> >
> > - since.py etc are in /usr/share/weewx/user already so indeed I can try 
> and
>
> since.py is part of the weewx-mastodon install.
>
> > use them. I tried to directly use since in the format line of
> > weewx-mastodon, but haven't succeeded yet:
> > `{since($hour=24).rain.sum:%.3f}` , `{since(hour=24).rain.sum:%.3f}`... 
> not
> > sure I can do it like that.
>
> As you found, these won't work on the raw (archive) data.
>
> > - I'll look in the template file.
>
> The example template I mentioned already uses since.py to format the
> rain value as ...
> $since($hour=9).rain.sum (Australian reporting times)
>
> According to the weewx manual at
> http://www.weewx.com/docs.html/latest/customizing.htm#Formatting_examples
> A format method to use for your example could be...
> $since($hour=9).rain.sum.format("%.3f")
> I just tested that method and it works. Apparently we've had 7.429 mm of 
> rain!
>
> > - final option is that I directly tweak wxtoot.py ...
> > I'll investigate and post back if I have a question... or with my 
> solution
> > if I succeed :)
>
> Done :)
>
> -- 
>
>
> Cheers
> Glenn
>
> rorpi - read only raspberry pi & various weewx addons
> https://github.com/glennmckechnie
>

-- 
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/c9ac9016-3780-465f-ada5-ddbb046a4341n%40googlegroups.com.

Re: [weewx-user] How to Stop Posting Results from Bad Sensor

2023-08-30 Thread Tom Keffer 
Use StdCalibrate
 to set
the value to None

[StdCalibrate]
  [[Corrections]]
...
windDir = None



On Wed, Aug 30, 2023 at 7:34 AM Chuck Rhode 
wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> "Wind direction" has gone bad.  "The South Wind's the North Wind's
> baker."  Until I can replace (or clean) the sensor, is there an easy
> way to begin posting null readings without deleting previously
> recorded historical data?
>
> - --
> .. Be Seeing You,
> .. Chuck Rhode, Sheboygan, WI, USA
> .. Weather:  http://LacusVeris.com/WX
> .. 61° — Wind N 13 mph — Sky mostly cloudy.
>
> -BEGIN PGP SIGNATURE-
>
> iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCZO9TZwAKCRBg2/xipKOW
> UqfVAJ4tyj698nmaWUb6GStx82xhfTdSTACdE+VRDiysmbpYu25ztnhe3J10RM0=
> =4Z0u
> -END PGP SIGNATURE-
>
> --
> 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/20230830093415.60815976%40BigTimber.LacusVeris.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/CAPq0zEDDzCuM48cvdbnkCM1s%3DztTPxdU4DsKzAfLe%2B3aXCQc%3DA%40mail.gmail.com.

[weewx-user] How to Stop Posting Results from Bad Sensor

2023-08-30 Thread Chuck Rhode 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

"Wind direction" has gone bad.  "The South Wind's the North Wind's
baker."  Until I can replace (or clean) the sensor, is there an easy
way to begin posting null readings without deleting previously
recorded historical data?

- -- 
.. Be Seeing You,
.. Chuck Rhode, Sheboygan, WI, USA
.. Weather:  http://LacusVeris.com/WX
.. 61° — Wind N 13 mph — Sky mostly cloudy.

-BEGIN PGP SIGNATURE-

iF0EARECAB0WIQT+MY/5I/LMPSswTbVg2/xipKOWUgUCZO9TZwAKCRBg2/xipKOW
UqfVAJ4tyj698nmaWUb6GStx82xhfTdSTACdE+VRDiysmbpYu25ztnhe3J10RM0=
=4Z0u
-END PGP SIGNATURE-

-- 
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/20230830093415.60815976%40BigTimber.LacusVeris.com.

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

2023-08-30 Thread Remy LAVABRE 
Thank you very much for your patience Gary,

Indeed I did not provide you with all the data from the CSV file in order
to simplify.
However, the fields were in the correct order with the correct wording.

Regarding the --dry-run command, I actually remove it for integration. This
is why all my fields are saved in the database with the timestamp (except
for rain).

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.

The other day after the changes you told me about there was a very light
rain.
I had this rain over two 5-minute time periods with a correct rain rate in
the CSV file.
However in the weewx database nothing...

This morning, I did another test manually and put a value of 2mm in the
rain field and 4mm/h in the rainRate. I manually tried the wee_import
command (exactly the same one that is in the crontab) and I had a correct
import this time!
So the problem really comes from me and not from weewx...

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 will first try to artificially simulate a rain in python in the CSV file
and see if this value now integrates correctly or not automatically with
the crontab.
Secondly, I will monitor the actual conditions (rain is normally forecast
this weekend...) and keep you informed.
*Thank you Gary for helping me out and giving me the solution! ;-)*

*Rémy LAVABRE*


Le mar. 29 août 2023 à 22:42, gjr80  a écrit :

> I just setup a WeeWX instance with your import config file in your first
> post but using rain = discrete and a csv data file using the two records
> in your last post. I ran wee_import using these files and --dry-run and
> --verbose and received somewhat different output to what you posted, in
> my case there were warnings of missing fields in the csv data file:
>
> $ sudo /home/weewx/bin/wee_import --import-config=/var/tmp/csv.conf
> --verbose
> /home/weewx/bin/wee_import:719: DeprecationWarning: The distutils package
> is deprecated and slated for removal in Python 3.12. Use setuptools or
> check PEP 632 for potential alternatives
>   from distutils.version import StrictVersion
> Using WeeWX configuration file /home/weewx/weewx.conf
> Starting wee_import...
> A CSV import from source file '/var/tmp/remy.csv' has been requested.
> The following options will be used:
>  config=/home/weewx/weewx.conf, import-config=/var/tmp/csv.conf
>  source=/var/tmp/remy.csv, from=None, to=None
>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>  tranche=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
>  delimiter=',', rain=discrete, wind_direction=[-360.0, 360.0]
>  UV=True, radiation=True
> Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> Starting import ...
> Obtaining raw import data for period 1 ...
> The following imported field-to-WeeWX field map will be used:
>  source field 'dateTime' in units 'unix_epoch' --> WeeWX field
> 'dateTime'
>  source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
>  source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
>  source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
>  source field 'inHumidity' in units 'percent' --> WeeWX field
> 'inHumidity'
>  source field 'outHumidity' in units 'percent' --> WeeWX field
> 'outHumidity'
>  source field 'windSpeed' in units 'km_per_hour' --> WeeWX field
> 'windSpeed'
>  source field 'windDir' in units 'degree_compass' --> WeeWX field
> 'windDir'
>  source field 'windGust' in units 'km_per_hour' --> WeeWX field
> 'windGust'
>  source field 'rainRate' in units 'mm_per_hour' --> WeeWX field
> 'rainRate'
>  source field 'rain' in units 'mm' --> WeeWX field 'rain'
>  source field 'dewpoint' in units 'degree_C' --> WeeWX field 'dewpoint'
>  source field 'windchill' in units 'degree_C' --> WeeWX field
> 'windchill'
>  source field 'radiation' in units 'watt_per_meter_squared' --> WeeWX
> field 'radiation'
>  source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
>  source field 'extraTemp1' in units 'degree_C' --> WeeWX field
> 'extraTemp1'
> Raw import data read successfully for period 1.
> Mapping raw import data for period