Re: [weewx-user] Error generating loop-data.txt with 4.6.2

[Marty b]

Thank you.  Problem resolved. :-)

On Monday, February 21, 2022 at 9:41:12 PM UTC-8 jo...@johnkline.com wrote:

> Yes, you must be running WeeWX 4.6.x.  Install the latest release of 
> loopdata (which is version 2.10).
>
> On Feb 21, 2022, at 6:49 PM, Marty b  wrote:
>
> 
>
> Hello everyone,
>
> My loop-data generation recently stopped working.  Here is a section from 
> my syslog that shows the error:
>
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
> '/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version 
> is 2.7.2.
> Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
> target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
> option "minute_label"  in interpolation.
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx 
> version 4.6.2
> F
>
> Any suggestion on resolving this?
>
> Thanks,
> Marty
>
> -- 
> 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+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/8228f6ce-270e-400f-a559-5320a59f13c4n%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/5be67d02-026b-4539-b11a-b28e736526f5n%40googlegroups.com.

Re: [weewx-user] Error generating loop-data.txt with 4.6.2

['John Kline' via weewx-user]

Yes, you must be running WeeWX 4.6.x.  Install the latest release of loopdata 
(which is version 2.10).

> On Feb 21, 2022, at 6:49 PM, Marty b  wrote:
> 
> 
> Hello everyone,
> 
> My loop-data generation recently stopped working.  Here is a section from my 
> syslog that shows the error:
> 
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
> '/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version is 
> 2.7.2.
> Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
> target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
> option "minute_label"  in interpolation.
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx version 
> 4.6.2
> F
> 
> Any suggestion on resolving this?
> 
> Thanks,
> Marty
> -- 
> 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/8228f6ce-270e-400f-a559-5320a59f13c4n%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/07B3E1D3-FFDD-41F8-8B34-344CDAB15648%40johnkline.com.

[weewx-user] Error generating loop-data.txt with 4.6.2

[Marty b]

Hello everyone,

My loop-data generation recently stopped working.  Here is a section from 
my syslog that shows the error:

Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
'/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version is 
2.7.2.
Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
option "minute_label"  in interpolation.
Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx 
version 4.6.2
F

Any suggestion on resolving this?

Thanks,
Marty

-- 
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/8228f6ce-270e-400f-a559-5320a59f13c4n%40googlegroups.com.

[weewx-user] Re: 4.6.2. update problem with wee_import

[gjr80]

Janne,

You've encountered a bug that shows when wee_import is run under python 2 
using a user defined field map. The fix required was not to wee_import but 
elsewhere in WeeWX and will appear in the next release (expected to be 
4.6.3). In the meantime since you are using WeeWX v4.6.2 you can safely 
just download the patched file, replace the corresponding file on your 
system and wee_import should work fine. To download and install the patched 
file:

1. move aside the file to be patched:
$ mv /usr/share/weewx/weeutil/weeutil.py 
/usr/share/weewx/weeutil/weeutil_orig.py

2. download the patched file:
$ wget -P /usr/share/weewx/weeutil/ 
https://raw.githubusercontent.com/weewx/weewx/master/bin/weeutil/weeutil.py

3. stop WeeWX (if it is running) and perform your import

I did a test import using the patched file, your import config file and 
your CSV data. The raw_datetime_format setting in your import config file 
needs to be changed to match the format of the date-time field your are 
using in your source data, it needs to be set as follows:

raw_datetime_format = "%d.%m.%y %H:%M"

With this change your data imported correctly and with out error. Note that 
you will likely receive the following message during the import:

Warning: Import field 'gustDir' is mapped to WeeWX field 'windGustDir' but 
the
 import field 'gustDir' could not be found in one or more records.
 WeeWX field 'windGustDir' will be set to 'None' in these records.

This is just a warning that you have a mapped field for which there is no 
source data. It can be safely ignored. 

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/0468043d-46dc-4238-a86b-0944b2938384n%40googlegroups.com.

Re: [weewx-user] RTLDavis windRun calculation and rain records

['John Kline' via weewx-user]

Thanks, Tom.

I don’t think that’s the problem as I add an interval to the (copy of) the 
packet.  That is needed because I keep my own set of accumulators so that 
loopdata can write out observations on every loop packet (in its own thread) 
and never have to access the database.  I can add an interval because the user 
specifies a LoopFrequency in seconds.

Indeed, on my VantagePro2 and RainWise weewx installs, I have no problem with 
windrun in loopdata.

I’ve seen issues at startup when I’ve tried the WeatherLinkUDP driver and I 
have code not checked in to catch and ignore errors to make it pass the 
startup, but I worry that loopdata won’t be accurate for drivers where loop 
packets don’t always contain all the data.  It’s not something I am likely to 
tackle anytime soon.

I’m guessing this driver is one of those cases, where loops don’t contain all 
the observations.  If so, it’s not a good candidate to use loopdata (at least, 
not at this time).

To the original OP, does everything work fine without loopdata?  Furthermore, 
does loopdata break the operation of weewx?  I’d be surprised if this is true 
as the loopdata thread should just die.


> On Feb 21, 2022, at 4:09 PM, Tom Keffer  wrote:
> 
> 
> loopdata is trying to calculate windrun, which requires a value for 
> 'interval'. You need it to multiply against velocity to get distance. 
> Unfortunately, 'interval' is not available in loop packets because they come 
> at irregular intervals. 
> 
> The source for loopdata could be modified to only calculate windrun if 
> possible. For example, this patch should work (NOT TESTED):
> 
> Index: bin/user/loopdata.py
> ===
> diff --git a/bin/user/loopdata.py b/bin/user/loopdata.py
> --- a/bin/user/loopdata.py (revision 0ee9d2ba94c53888154363aa412f1d5d5002ff12)
> +++ b/bin/user/loopdata.py (date 1645488401429)
> @@ -807,11 +807,14 @@
>  pkt_time: int   = to_int(pkt['dateTime'])
>  pkt['interval'] = self.cfg.loop_frequency / 60.0
>  
> -windrun_val = 
> weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
> -pkt['windrun'] = windrun_val[0]
> -if windrun_val[0] > 0.00 and 'windDir' in pkt and 
> pkt['windDir'] is not None:
> -bkt = LoopProcessor.get_windrun_bucket(pkt['windDir'])
> -pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] = 
> windrun_val[0]
> +try:
> +windrun_val = 
> weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
> +pkt['windrun'] = windrun_val[0]
> +if windrun_val[0] > 0.00 and 'windDir' in pkt and 
> pkt['windDir'] is not None:
> +bkt = 
> LoopProcessor.get_windrun_bucket(pkt['windDir'])
> +pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] = 
> windrun_val[0]
> +except weewx.CannotCalculate:
> +pass
>  
>  beaufort_val = 
> weewx.wxxtypes.WXXTypes.calc_beaufort('beaufort', pkt)
>  pkt['beaufort'] = beaufort_val[0]
> 
> 
>> On Sun, Feb 20, 2022 at 7:57 AM Andrew Roberts  
>> wrote:
>> Hi,
>> I'm after a steer as to where to look to fix/block this issue. I'm running 
>> RTLDavis with a Vantage Vue and weewx 4.6.1. The indoor temperature and 
>> pressure (BMP280) is coming through as a data service over a serial link.
>> 
>> When I start up weewx and use loopdata, syslog shows:
>> 
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  Traceback (most recent call last):
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>File "/usr/share/weewx/user/loopdata.py", line 810, in process_queue
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  windrun_val = weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>File "/usr/share/weewx/weewx/wxxtypes.py", line 303, in calc_windrun
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  raise weewx.CannotCalculate(key)
>> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:  
>>  weewx.CannotCalculate: windrun
>> 
>> 1. Looking into the code it seems to be a lack of interval data. I can not 
>> find a way of sorting this in weewx.conf and close inspection of the 
>> RTLDavis DEBUG data  in Syslog (attached) doesn't have any interval data in 
>> it.
>> 
>> 2. In spite of it raining, the console reporting rain and after tipping a 
>> cup of water into the bucket I'm not reliably getting rain data from the 
>> ISS. the DEBUG (all three debug options set to 3) log records:
>> 
>> DEBUG user.rtldavis:  data_pkt: {'channel': 1, 'bat_iss': 0, 
>> 'wind_speed_ec': 15, 'wind_speed_raw': 14, 'wind_dir': 273.9486166007905, 
>> 'wind_speed': 

Re: [weewx-user] RTLDavis windRun calculation and rain records

[Tom Keffer]

loopdata is trying to calculate windrun, which requires a value for
'interval'. You need it to multiply against velocity to get distance.
Unfortunately, 'interval' is not available in loop packets because they
come at irregular intervals.

The source for loopdata could be modified to only calculate windrun if
possible. For example, this patch should work (NOT TESTED):

Index: bin/user/loopdata.py
===
diff --git a/bin/user/loopdata.py b/bin/user/loopdata.py
--- a/bin/user/loopdata.py (revision
0ee9d2ba94c53888154363aa412f1d5d5002ff12)
+++ b/bin/user/loopdata.py (date 1645488401429)
@@ -807,11 +807,14 @@
 pkt_time: int   = to_int(pkt['dateTime'])
 pkt['interval'] = self.cfg.loop_frequency / 60.0

-windrun_val =
weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
-pkt['windrun'] = windrun_val[0]
-if windrun_val[0] > 0.00 and 'windDir' in pkt and
pkt['windDir'] is not None:
-bkt = LoopProcessor.get_windrun_bucket(pkt['windDir'])
-pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] =
windrun_val[0]
+try:
+windrun_val =
weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
+pkt['windrun'] = windrun_val[0]
+if windrun_val[0] > 0.00 and 'windDir' in pkt and
pkt['windDir'] is not None:
+bkt =
LoopProcessor.get_windrun_bucket(pkt['windDir'])
+pkt['windrun_%s' % windrun_bucket_suffixes[bkt]] =
windrun_val[0]
+except weewx.CannotCalculate:
+pass

 beaufort_val =
weewx.wxxtypes.WXXTypes.calc_beaufort('beaufort', pkt)
 pkt['beaufort'] = beaufort_val[0]


On Sun, Feb 20, 2022 at 7:57 AM Andrew Roberts 
wrote:

> Hi,
> I'm after a steer as to where to look to fix/block this issue. I'm running
> RTLDavis  with a Vantage Vue
> and weewx 4.6.1. The indoor temperature and pressure (BMP280) is coming
> through as a data service over a serial link.
>
> When I start up weewx and use loopdata
> , syslog shows:
>
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
>   Traceback (most recent call last):
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
> File "/usr/share/weewx/user/loopdata.py", line 810, in process_queue
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
>   windrun_val = weewx.wxxtypes.WXXTypes.calc_windrun('windrun', pkt)
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
> File "/usr/share/weewx/weewx/wxxtypes.py", line 303, in calc_windrun
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
>   raise weewx.CannotCalculate(key)
> Feb 20 12:01:23 Weather-Centre weewx[12537] CRITICAL user.loopdata:
>   weewx.CannotCalculate: windrun
>
> 1. Looking into the code it seems to be a lack of interval data. I can not
> find a way of sorting this in weewx.conf and close inspection of the
> RTLDavis DEBUG data  in Syslog (attached) doesn't have any interval data in
> it.
>
> 2. In spite of it raining, the console reporting rain and after tipping a
> cup of water into the bucket I'm not reliably getting rain data from the
> ISS. the DEBUG (all three debug options set to 3) log records:
>
> DEBUG user.rtldavis:  data_pkt: {'channel': 1, 'bat_iss': 0,
> 'wind_speed_ec': 15, 'wind_speed_raw': 14, 'wind_dir': 273.9486166007905,
> 'wind_speed': 6.7055833, 'rain_count': 37, 'curr_cnt0': 2982,
> 'curr_cnt1': 0, 'curr_cnt2': 0, 'curr_cnt3': 0}
> DEBUG user.rtldavis: rain=0.0 rain_count=0 last_rain_count=37
> DEBUG user.rtldavis: pkt= {'windSpeed': 6.7055833, 'windDir':
> 273.9486166007905, 'txBatteryStatus': 0, 'rain': 0.0, 'dateTime':
> 1645353107, 'usUnits': 17}
>
> Any suggestions as to next steps for me troubleshooting these would be
> welcome.
>
> Andrew
>
> --
> 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/a75644e9-5c1b-44a9-a345-70803e116d81n%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 

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

[Tom Keffer]

Upon reflection, I really didn't like the solution I posted earlier. The
reality is that for stations that do not supply windGustDir, such as the
Fine Offset stations, weewx was calculating a substitute just fine: the
vector average of the wind over an archive period was being extracted from
the accumulators. The problem is that because of the peculiarities of how
WXXTypes was set up, it was forcing windGustDir to None if windGustDir was
missing, which caused the calculated value not to get substituted. Then I
supplied a band-aid over this by substituting windDir instead.

A mess.

With commit 244a7f8
,
I've changed this to do nothing in WXXTypes if windGustDir is missing. This
causes a value to be successfully extracted from the accumulators.

A long-winded way to say that I think the new solution is a better, more
accurate one.

If you're comfortable using git, I'd appreciate it if one of you FO owners
could give it a try.

-tk



On Mon, Feb 14, 2022 at 3:46 AM paul...@gmail.com 
wrote:

> Checked this morning and pleased to say Max Wind direction is now
> reporting and updating in the Day tab of the Statistics section. Still N/A
> in Week but I'm guessing it will update in due course.
> Just out of interest I've noticed in the Statistics section the Year tab
> is blue and if you click on it you get the option of Year or Rain Year.
> What actually is the difference between these two? In my case the values
> reported are identical.
> Paul
>
> On Sunday, 13 February 2022 at 20:01:25 UTC remy.l...@gmail.com wrote:
>
>> Yes, it’s the good python file, same as me  (if standard installation...)
>> The Tom’s update/patch solves perfectly the problem and also min/max
>> windGustDir data base.
>> Try stop and start weewx (logicaly same thing as restart... !?)
>> Try to look for all wxxtype.py on your system to see if there is another
>> file ? Logicaly no...
>>
>>
>> Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a écrit :
>>
>>> Hi Remy
>>> Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it
>>> again but no change.
>>> Can I just check I swapped the correct wxxtypes.py file. I swapped the
>>> one in /usr/share/weewx/weewx
>>> Paul
>>>
>>> On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:
>>>
 Hi Paul.
 Have you triedto stop weewx and restart it ?
 You must do that if you modify python file.
 Cordialy


 Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a
 écrit :

> I don't report wind gust values/direction in the Current Conditions
> section of my Seasons skin (version 4.6.2) but in the Statistics
> (previously High/Low) section I've always had a Max Wind entry with both
> speed and direction reported. Since 4.6.2 the direction is reported as N/A
> so I've followed this thread and replaced the wxxtypes.py file with the 
> new
> one from Tom but it doesn't seem to have made any difference to my Max 
> Wind
> entry. If you look at the Statistics report below it still shows N/A for
> Max Wind degrees for Day and Week but for Month and Year (presumably data
> from 4.5.1) a degree value is reported.
>
> [image: Max Wind.jpg]
> Any suggestions?
>
> Paul
> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>
>> Brilliant, now it work just fine.
>> Thanks a lot.
>>
>> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com
>> wrote:
>>
>>> Yes !! Thank-you Tom it works great now :
>>>
>>> [image: Capture d’écran de 2022-02-13 15-26-27.png]
>>> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a
>>> écrit :
>>>
 I was able to replicate the problem. Pre V4.6, if windGustDir was
 missing, windDir was substituted. That behavior went away with v4.6. 
 This
 patch restores it.

 Index: bin/weewx/wxxtypes.py
 ===
 diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
 --- a/bin/weewx/wxxtypes.py (revision
 279bb450ab801c80a12b8ceadd0144e16c473bea)
 +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
 @@ -98,11 +98,18 @@
  return ValueTuple(val, 'degree_compass', 'group_direction')

  def calc_windGustDir(self, key, data, db_manager):
 -# Return the current gust direction if windGust is
 non-zero, otherwise, None
 -if 'windGust' not in data or 'windGustDir' not in data:
 +"""If windGustDir is missing, substitute windDir.
 +Set windGustDir to None if windGust is zero."""
 +if 'windGust' not in data:
  raise weewx.CannotCalculate
  if self.force_null and 

[weewx-user] Re: 4.6.2. update problem with wee_import

[gjr80]

Thank you Janne, let me see what I can do.

Gary

On Tuesday, 22 February 2022 at 08:16:13 UTC+10 jannep...@gmail.com wrote:

> Hi Gary
> I sent you PM
>
> Janne
>
> maanantai 21. helmikuuta 2022 klo 23.06.58 UTC+2 gjr80 kirjoitti:
>
>> Would you also please provide a copy of the import config file you are 
>> using and a sample of the data (at least the header line and a few lines of 
>> data) you are trying to import.
>>
>> I would also stop trying to patch the code to make it work; you will 
>> likely only continue to encounter other issues, most likely caused by your 
>> previous changes. Give me some time to work through the initial problem.
>>
>> Gary
>>
>> On Tuesday, 22 February 2022 at 06:06:04 UTC+10 jannep...@gmail.com 
>> wrote:
>>
>>> Hi, more info.
>>> I fixed with ducktape the first problem by commenting out the line 635 
>>> from weeimport.py 
>>>
>>> #and _val['units'] not in 
>>> weewx.units.USUnits.values()
>>>
>>> But this did not solve my import troubles. Now it looks that csv.conf 
>>> and weewx.conf does not understand each other. csv.conf is asking for 
>>> unkonwn units
>>>
>>>Using WeeWX configuration file /etc/weewx/weewx.conf
>>>Starting wee_import...
>>>A CSV import from source file '/var/tmp/data.csv' has been requested.
>>>Using database binding 'wx_binding', which is bound to database 
>>> 'weewx.sdb'
>>>Destination table 'archive' unit system is '0x11' (METRICWX).
>>>Missing derived observations will be calculated.
>>>This is a dry run, imported data will not be saved to archive.
>>>Starting dry run import ...
>>> Unknown units 'uv_index' specified for field 'UV' in 
>>> /var/tmp/csv.conf.
>>> Nothing done, exiting.
>>>
>>> If I comment out UV, from my csv.conf wee_import finds next unknown 
>>> unit... I also have tried to create group_uv to weewx.conf. The unkonwn 
>>> units are uv_index, percent, degree_compass.
>>>
>>> regards
>>> Janne
>>> maanantai 21. helmikuuta 2022 klo 14.44.40 UTC+2 jannep...@gmail.com 
>>> kirjoitti:
>>>
 hi
 python 2. Here is log. When I start weewx, LOOP is working. I can get 
 weather station info to terminal, but maybe not to database. I have a 
 Ventus weather station and I download data every now and then to windows. 
 From there I import the data in csv to weewx. 

 Janne

 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Initializing 
 weewx version 4.6.2
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using Python 
 2.7.17 (default, Feb 27 2021, 15:10:58) #012[GCC 7.5.0]
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Platform 
 Linux-5.4.0-99-generic-x86_64-with-LinuxMint-19.3-tricia
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Locale is 
 'fi_FI.UTF-8'
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using 
 configuration file /etc/weewx/weewx.conf
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Debug is 0
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Loading 
 station type WS6in1 (user.ws6in1)
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: StdConvert 
 target unit is 0x11
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.wxservices: 
 StdWXCalculate will use data binding wx_binding
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Archive will 
 use data binding wx_binding
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Record 
 generation will be attempted in 'hardware'
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using archive 
 interval of 300 seconds (specified in weewx configuration)
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: 
 StationRegistry: Registration not requested.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: Wunderground: 
 Posting not enabled.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: PWSweather: 
 Posting not enabled.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: CWOP: Posting 
 not enabled.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: WOW: Posting 
 not enabled.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: AWEKAS: 
 Posting not enabled.
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: 'pyephem' not 
 detected, extended almanac data is not available
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Starting up weewx 
 version 4.6.2
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using binding 
 'wx_binding' to database 'weewx.sdb'
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Starting 
 backfill of daily summaries
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Daily 
 summaries up to date
 Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Starting main 
 packet loop.

 

[weewx-user] Re: 4.6.2. update problem with wee_import

[jannep...@gmail.com]

Hi Gary
I sent you PM

Janne

maanantai 21. helmikuuta 2022 klo 23.06.58 UTC+2 gjr80 kirjoitti:

> Would you also please provide a copy of the import config file you are 
> using and a sample of the data (at least the header line and a few lines of 
> data) you are trying to import.
>
> I would also stop trying to patch the code to make it work; you will 
> likely only continue to encounter other issues, most likely caused by your 
> previous changes. Give me some time to work through the initial problem.
>
> Gary
>
> On Tuesday, 22 February 2022 at 06:06:04 UTC+10 jannep...@gmail.com wrote:
>
>> Hi, more info.
>> I fixed with ducktape the first problem by commenting out the line 635 
>> from weeimport.py 
>>
>> #and _val['units'] not in 
>> weewx.units.USUnits.values()
>>
>> But this did not solve my import troubles. Now it looks that csv.conf and 
>> weewx.conf does not understand each other. csv.conf is asking for unkonwn 
>> units
>>
>>Using WeeWX configuration file /etc/weewx/weewx.conf
>>Starting wee_import...
>>A CSV import from source file '/var/tmp/data.csv' has been requested.
>>Using database binding 'wx_binding', which is bound to database 
>> 'weewx.sdb'
>>Destination table 'archive' unit system is '0x11' (METRICWX).
>>Missing derived observations will be calculated.
>>This is a dry run, imported data will not be saved to archive.
>>Starting dry run import ...
>> Unknown units 'uv_index' specified for field 'UV' in 
>> /var/tmp/csv.conf.
>> Nothing done, exiting.
>>
>> If I comment out UV, from my csv.conf wee_import finds next unknown 
>> unit... I also have tried to create group_uv to weewx.conf. The unkonwn 
>> units are uv_index, percent, degree_compass.
>>
>> regards
>> Janne
>> maanantai 21. helmikuuta 2022 klo 14.44.40 UTC+2 jannep...@gmail.com 
>> kirjoitti:
>>
>>> hi
>>> python 2. Here is log. When I start weewx, LOOP is working. I can get 
>>> weather station info to terminal, but maybe not to database. I have a 
>>> Ventus weather station and I download data every now and then to windows. 
>>> From there I import the data in csv to weewx. 
>>>
>>> Janne
>>>
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Initializing weewx 
>>> version 4.6.2
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using Python 
>>> 2.7.17 (default, Feb 27 2021, 15:10:58) #012[GCC 7.5.0]
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Platform 
>>> Linux-5.4.0-99-generic-x86_64-with-LinuxMint-19.3-tricia
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Locale is 
>>> 'fi_FI.UTF-8'
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using 
>>> configuration file /etc/weewx/weewx.conf
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Debug is 0
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Loading 
>>> station type WS6in1 (user.ws6in1)
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: StdConvert 
>>> target unit is 0x11
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.wxservices: 
>>> StdWXCalculate will use data binding wx_binding
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Archive will 
>>> use data binding wx_binding
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Record 
>>> generation will be attempted in 'hardware'
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using archive 
>>> interval of 300 seconds (specified in weewx configuration)
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: 
>>> StationRegistry: Registration not requested.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: Wunderground: 
>>> Posting not enabled.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: PWSweather: 
>>> Posting not enabled.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: CWOP: Posting 
>>> not enabled.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: WOW: Posting 
>>> not enabled.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: AWEKAS: Posting 
>>> not enabled.
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: 'pyephem' not 
>>> detected, extended almanac data is not available
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Starting up weewx 
>>> version 4.6.2
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using binding 
>>> 'wx_binding' to database 'weewx.sdb'
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Starting 
>>> backfill of daily summaries
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Daily 
>>> summaries up to date
>>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Starting main 
>>> packet loop.
>>>
>>> maanantai 21. helmikuuta 2022 klo 9.37.18 UTC+2 gjr80 kirjoitti:
>>>
 Janne,

 Could you please let me know whether WeeWX is being run under python 2 
 or 3? You can tell by looking at the WeeWX log during WeeWX startup (the 
 

Re: [weewx-user] Vantage Vue wind cup size setting with wee_device

[Gary Strand]

Looks like the value can only be changed via the console if one has a VP2, 
not a VUE ISS. So, "large" they are!


On Monday, February 21, 2022 at 6:08:48 AM UTC-7 tke...@gmail.com wrote:

> The console has no way of knowing what size wind cup is mounted on the 
> ISS. Someone has to tell it. Generally, that is done by the factory when 
> they ship the unit out. Under "extraordinary circumstances" a user might 
> have to do this if, for example, s/he changed the cup size.
>
> I have only owned (and seen) the regular "large" size, so I don't have 
> anything to compare it to. You'd have to ask Davis what size cup you have.
>
> On Sun, Feb 20, 2022 at 8:03 PM Gary Strand  wrote:
>
>>
>> I know this is an old thread but is precisely the question I have. 
>> "wee_device" reports the cups as "large", but the cups on my sensor don't 
>> seem large to me. Are the "small" really tiny?
>>
>> Just curious because what counts as "extraordinary circumstances"? On the 
>> day of the Colorado Marshall Fire, I recorded a gust of 49 mph when other 
>> stations were reporting much higher numbers; is this such a circumstance?
>>
>> Thanks!
>>
>>
>> On Saturday, October 20, 2018 at 7:57:52 PM UTC-6 tke...@gmail.com wrote:
>>
>>> Thanks, Philip. That's the first reference I've seen to "Vue" cups. As I 
>>> said, you'd have to ask Davis.
>>>
>>> But, in any case, don't worry about it. Only under extraordinary 
>>> circumstances do you need to set it.
>>>
>>> -tk
>>>
>>> On Sat, Oct 20, 2018 at 6:51 PM Philip Kutzenco  
>>> wrote:
>>>
 Thomas,

 Thanks for the reply. I won't worry about it. The reason I asked is 
 that the help file for Davis' Weatherlink software shows three options. 
 See 
 the attached screen shot I took for setting that in the console with 
 Weatherlink. Evidently, you can set a VantagePro to use small cups or 
 Vue/Other cups. I'll just leave the value as it is set in the console 
 without setting it explicitly.
 phil

 On Saturday, October 20, 2018 at 8:22:26 PM UTC-4, Thomas Keffer wrote:
>
> A Vantage (whether a Vue or a VantagePro) ships with a value in the 
> EEPROM firmware that matches its cup size. Unless you change the cups, 
> there is no reason to mess with this value. The wee_device utility option 
> is there if, for some reason, you have to change the cups.
>
> To answer your question, the Davis documentation lists only two sizes: 
> small and large. If there's a third "Vue" sized, I haven't heard of it. 
> You'd have to ask Davis.
>
> -tk
>
> On Sat, Oct 20, 2018 at 7:35 AM Philip Kutzenco  
> wrote:
>
>> Now that I have my external website operational (
>> https://wx.kutzenco.com) with a Mosquitto MQTT broker and 
>> Belchertown skin, I'm spending a bit more time reviewing the weeWX 
>> documentation to get a deeper understanding of my system. I'm hoping to 
>> do 
>> some customization.
>>
>> I have a Davis Vantage Vue weather station and weeWX running on a 
>> Raspberry Pi Zero W. I see that the Davis Weatherlink software gives the 
>> options for wind cup size as Small, Large or Vue/Other. That Davis 
>> documentation says that Vantage Pro systems generally ship with large 
>> cups, 
>> and that (obviously) Vantage Vue systems ship with Vue cups.
>>
>> The wee_device --help command mentions only Small and Large options 
>> for wind cup size. Is there an option for Vue/other cups? I don't know 
>> what 
>> is adjusted in the readings/calculations by specifying different cup 
>> sizes. 
>> I didn't see that called out in the weeWX documention. I suspect the 
>> difference is minimal, but, just to ensure that everything can be set 
>> properly with weeWX does that option need to be added to wee_device for 
>> Vantage systems, if it isn't there?
>>
>> phil
>>
>> -- 
>> 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+...@googlegroups.com.
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
 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+...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> -- 
>> 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+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/c52c96d6-2b18-4768-b823-c5957e17bdb1n%40googlegroups.com
>>  
>> 

[weewx-user] Re: 4.6.2. update problem with wee_import

[gjr80]

Would you also please provide a copy of the import config file you are 
using and a sample of the data (at least the header line and a few lines of 
data) you are trying to import.

I would also stop trying to patch the code to make it work; you will likely 
only continue to encounter other issues, most likely caused by your 
previous changes. Give me some time to work through the initial problem.

Gary

On Tuesday, 22 February 2022 at 06:06:04 UTC+10 jannep...@gmail.com wrote:

> Hi, more info.
> I fixed with ducktape the first problem by commenting out the line 635 
> from weeimport.py 
>
> #and _val['units'] not in 
> weewx.units.USUnits.values()
>
> But this did not solve my import troubles. Now it looks that csv.conf and 
> weewx.conf does not understand each other. csv.conf is asking for unkonwn 
> units
>
>Using WeeWX configuration file /etc/weewx/weewx.conf
>Starting wee_import...
>A CSV import from source file '/var/tmp/data.csv' has been requested.
>Using database binding 'wx_binding', which is bound to database 
> 'weewx.sdb'
>Destination table 'archive' unit system is '0x11' (METRICWX).
>Missing derived observations will be calculated.
>This is a dry run, imported data will not be saved to archive.
>Starting dry run import ...
> Unknown units 'uv_index' specified for field 'UV' in 
> /var/tmp/csv.conf.
> Nothing done, exiting.
>
> If I comment out UV, from my csv.conf wee_import finds next unknown 
> unit... I also have tried to create group_uv to weewx.conf. The unkonwn 
> units are uv_index, percent, degree_compass.
>
> regards
> Janne
> maanantai 21. helmikuuta 2022 klo 14.44.40 UTC+2 jannep...@gmail.com 
> kirjoitti:
>
>> hi
>> python 2. Here is log. When I start weewx, LOOP is working. I can get 
>> weather station info to terminal, but maybe not to database. I have a 
>> Ventus weather station and I download data every now and then to windows. 
>> From there I import the data in csv to weewx. 
>>
>> Janne
>>
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Initializing weewx 
>> version 4.6.2
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using Python 2.7.17 
>> (default, Feb 27 2021, 15:10:58) #012[GCC 7.5.0]
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Platform 
>> Linux-5.4.0-99-generic-x86_64-with-LinuxMint-19.3-tricia
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Locale is 
>> 'fi_FI.UTF-8'
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Debug is 0
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Loading station 
>> type WS6in1 (user.ws6in1)
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: StdConvert 
>> target unit is 0x11
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using archive 
>> interval of 300 seconds (specified in weewx configuration)
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: StationRegistry: 
>> Registration not requested.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: Wunderground: 
>> Posting not enabled.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: PWSweather: 
>> Posting not enabled.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: CWOP: Posting 
>> not enabled.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: WOW: Posting not 
>> enabled.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: AWEKAS: Posting 
>> not enabled.
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: 'pyephem' not 
>> detected, extended almanac data is not available
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Starting up weewx 
>> version 4.6.2
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx.sdb'
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Starting 
>> backfill of daily summaries
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Daily 
>> summaries up to date
>> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Starting main 
>> packet loop.
>>
>> maanantai 21. helmikuuta 2022 klo 9.37.18 UTC+2 gjr80 kirjoitti:
>>
>>> Janne,
>>>
>>> Could you please let me know whether WeeWX is being run under python 2 
>>> or 3? You can tell by looking at the WeeWX log during WeeWX startup (the 
>>> python version is logged) or you can look at the first line of any of the 
>>> wee_xx (eg wee_database) utilities in the /usr/share/weewx 
>>> directory.
>>>
>>> If yo cannot work it out please restart WeeWX 

Re: [weewx-user] Re: Problem with Vantage Vue

[geo...@gmail.com]

Sorry, that's right. I reinstalled both the Raspi OS and weewx. Simulator 
works, when selecting Vantage, unfortunately the error message remains as 
in the first post, Connection refused. BTW, the other computer is 
Meteobridge. I'll ask around on the Meteobridge forum.

tke...@gmail.com schrieb am Montag, 21. Februar 2022 um 18:58:00 UTC+1:

> All of those log entries were put there by other services. There is 
> nothing in the log that indicates that weewxd is even running.
>
> On Mon, Feb 21, 2022 at 8:09 AM geo...@gmail.com  wrote:
>
>> IP is correct. After stop, start or restart showed no change, I restarted 
>> the Raspberry. Now this is in the log and apparently stops at Finished 
>> Clean php session files:
>>
>> pi@weewx:~ $ sudo tail -f /var/log/syslog
>> Feb 21 15:25:46 weewx systemd[856]: Startup finished in 1.866s.
>> Feb 21 15:25:46 weewx systemd[1]: Started User Manager for UID 1000.
>> Feb 21 15:25:46 weewx systemd[1]: Started Session 1 of user pi.
>> Feb 21 15:39:02 weewx CRON[1587]: (root) CMD (  [ -x 
>> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
>> /usr/lib/php/sessionclean; fi)
>> Feb 21 15:39:05 weewx systemd[1]: Starting Clean php session files...
>> Feb 21 15:39:05 weewx systemd[1]: Starting Cleanup of Temporary 
>> Directories...
>> Feb 21 15:39:05 weewx systemd[1]: systemd-tmpfiles-clean.service: 
>> Succeeded.
>> Feb 21 15:39:05 weewx systemd[1]: Finished Cleanup of Temporary 
>> Directories.
>> Feb 21 15:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
>> Feb 21 15:39:05 weewx systemd[1]: Finished Clean php session files.
>> Feb 21 16:09:01 weewx CRON[2515]: (root) CMD (  [ -x 
>> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
>> /usr/lib/php/sessionclean; fi)
>> Feb 21 16:09:05 weewx systemd[1]: Starting Clean php session files...
>> Feb 21 16:09:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
>> Feb 21 16:09:05 weewx systemd[1]: Finished Clean php session files.
>> Feb 21 16:17:01 weewx CRON[2806]: (root) CMD (   cd / && run-parts 
>> --report /etc/cron.hourly)
>> Feb 21 16:24:19 weewx rngd[378]: stats: bits received from HRNG source: 
>> 80064
>> Feb 21 16:24:19 weewx rngd[378]: stats: bits sent to kernel pool: 33824
>> Feb 21 16:24:19 weewx rngd[378]: stats: entropy added to kernel pool: 
>> 33824
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 successes: 4
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 failures: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Monobit: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Poker: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Runs: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Long run: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Continuous 
>> run: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: HRNG source speed: (min=748.295; 
>> avg=753.644; max=761.423)Kibits/s
>> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS tests speed: (min=16.909; 
>> avg=20.704; max=22.492)Mibits/s
>> Feb 21 16:24:19 weewx rngd[378]: stats: Lowest ready-buffers level: 2
>> Feb 21 16:24:19 weewx rngd[378]: stats: Entropy starvations: 0
>> Feb 21 16:24:19 weewx rngd[378]: stats: Time spent starving for entropy: 
>> (min=0; avg=0.000; max=0)us
>> Feb 21 16:39:01 weewx CRON[3443]: (root) CMD (  [ -x 
>> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
>> /usr/lib/php/sessionclean; fi)
>> Feb 21 16:39:05 weewx systemd[1]: Starting Clean php session files...
>> Feb 21 16:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
>> Feb 21 16:39:05 weewx systemd[1]: Finished Clean php session files.
>>
>> I used the weewx version 4.6.2 on a Raspberry 2.
>> vince schrieb am Sonntag, 20. Februar 2022 um 23:12:29 UTC+1:
>>
>>>
>>> Connection refused is the other computer isn't listening and accepting 
>>> traffic on that port.
>>> Check you have the right ip address set in your weewx.conf file
>>>
>>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/f92dc023-b2f6-4f36-953e-4a32a642ef21n%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/c65c921d-7c3f-484f-a45d-e0a3f45653dcn%40googlegroups.com.

[weewx-user] Re: 4.6.2. update problem with wee_import

[jannep...@gmail.com]

Hi, more info.
I fixed with ducktape the first problem by commenting out the line 635 from 
weeimport.py 

#and _val['units'] not in 
weewx.units.USUnits.values()

But this did not solve my import troubles. Now it looks that csv.conf and 
weewx.conf does not understand each other. csv.conf is asking for unkonwn 
units

   Using WeeWX configuration file /etc/weewx/weewx.conf
   Starting wee_import...
   A CSV import from source file '/var/tmp/data.csv' has been requested.
   Using database binding 'wx_binding', which is bound to database 
'weewx.sdb'
   Destination table 'archive' unit system is '0x11' (METRICWX).
   Missing derived observations will be calculated.
   This is a dry run, imported data will not be saved to archive.
   Starting dry run import ...
    Unknown units 'uv_index' specified for field 'UV' in 
/var/tmp/csv.conf.
    Nothing done, exiting.

If I comment out UV, from my csv.conf wee_import finds next unknown unit... 
I also have tried to create group_uv to weewx.conf. The unkonwn units are 
uv_index, percent, degree_compass.

regards
Janne
maanantai 21. helmikuuta 2022 klo 14.44.40 UTC+2 jannep...@gmail.com 
kirjoitti:

> hi
> python 2. Here is log. When I start weewx, LOOP is working. I can get 
> weather station info to terminal, but maybe not to database. I have a 
> Ventus weather station and I download data every now and then to windows. 
> From there I import the data in csv to weewx. 
>
> Janne
>
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Initializing weewx 
> version 4.6.2
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using Python 2.7.17 
> (default, Feb 27 2021, 15:10:58) #012[GCC 7.5.0]
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Platform 
> Linux-5.4.0-99-generic-x86_64-with-LinuxMint-19.3-tricia
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Locale is 
> 'fi_FI.UTF-8'
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Debug is 0
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Loading station 
> type WS6in1 (user.ws6in1)
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: StdConvert 
> target unit is 0x11
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Archive will use 
> data binding wx_binding
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using archive 
> interval of 300 seconds (specified in weewx configuration)
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: StationRegistry: 
> Registration not requested.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: Wunderground: 
> Posting not enabled.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: PWSweather: 
> Posting not enabled.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: CWOP: Posting not 
> enabled.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: WOW: Posting not 
> enabled.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: 'pyephem' not 
> detected, extended almanac data is not available
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Starting up weewx 
> version 4.6.2
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx.sdb'
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Starting 
> backfill of daily summaries
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Daily summaries 
> up to date
> Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Starting main 
> packet loop.
>
> maanantai 21. helmikuuta 2022 klo 9.37.18 UTC+2 gjr80 kirjoitti:
>
>> Janne,
>>
>> Could you please let me know whether WeeWX is being run under python 2 or 
>> 3? You can tell by looking at the WeeWX log during WeeWX startup (the 
>> python version is logged) or you can look at the first line of any of the 
>> wee_xx (eg wee_database) utilities in the /usr/share/weewx directory.
>>
>> If yo cannot work it out please restart WeeWX and post a log extract 
>> showing the full WeeWX startup.
>>
>> Gary
>>
>> On Monday, 21 February 2022 at 04:21:57 UTC+10 jannep...@gmail.com wrote:
>>
>>> Hi, I updated from 4.5 to 4.6.2 and my wee_import stop to next message:
>>>
>>> I use WS6in1-driver with my Ventus.
>>>
>>> ...
>>> Using WeeWX configuration file /etc/weewx/weewx.conf
>>> Starting wee_import...
>>> A CSV import from source file '/var/tmp/data.csv' has been requested.
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'weewx.sdb'
>>> Destination table 'archive' unit system is '0x11' (METRICWX).

[weewx-user] Re: Cheetah error after update to WeeWX 4.6.2

[František Slimařík]

OK, I see windGust issue is already discussed/solved here: 
https://groups.google.com/g/weewx-user/c/9N8gg44u8Q0/m/BjKbIuvcBQAJ

So all issues solved :)

Dne pondělí 21. února 2022 v 13:28:53 UTC+1 uživatel František Slimařík 
napsal:

> Ok, I found the issue. I was using following extension  
> vinceskahan/vds-weewx-lastrain-extension: 
> extension for weewx to generate some lastrain timestamps and delta time 
> reports (github.com) 
>  which was 
> updated recently for version 4.6.0. But I found also another interesting 
> thing, following tags are shown as N/A instead of value:
>
> $current.windGustDir.ordinal_compass
> $day.wind.gustdir.ordinal_compass
>
> Following tag is OK:
> $current.windDir.ordinal_compass
>
> I am using observer driver.
>
> Dne pondělí 21. února 2022 v 11:03:33 UTC+1 uživatel František Slimařík 
> napsal:
>
>> Hello, 
>>
>> can you gimme small hint what should be checked in cheetah template after 
>> updated to version 4.6.2? I am using python3 and after update all templates 
>> works fine except main one. Unfortunately for me I made much of 
>> customizations there so I ´d like to know to which part I should focus 
>> mainly :)
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator: Evaluation of template 
>> /etc/weewx/skins/neowx/index.html.tmpl failed with exception '> 'TypeError'>'Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
>> ERROR weewx.cheetahgenerator:  Ignoring template 
>> /etc/weewx/skins/neowx/index.html.tmplFeb 21 11:00:39 new-weather-machine 
>> journal: weewx[22334] ERROR weewx.cheetahgenerator:  Reason: %x format: 
>> an integer is required, not dictFeb 21 11:00:39 new-weather-machine 
>> journal: weewx[22334] ERROR weewx.cheetahgenerator:  Traceback (most 
>> recent call last):Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
>> ERROR weewx.cheetahgenerator:  File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generateFeb 21 
>> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  unicode_string = 
>> compiled_template.respond()Feb 21 11:00:39 new-weather-machine journal: 
>> weewx[22334] ERROR weewx.cheetahgenerator:  File 
>> "_etc_weewx_skins_neowx_index_html_tmpl.py", line 1273, in respondFeb 21 
>> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
>> 1005, in __str__Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
>> ERROR weewx.cheetahgenerator:  s = self.toString()Feb 21 11:00:39 
>> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>>  File "/usr/share/weewx/weewx/units.py", line 1000, in toStringFeb 21 
>> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  localize=localize)Feb 21 11:00:39 
>> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>>  File "/usr/share/weewx/weewx/units.py", line 688, in toStringFeb 21 
>> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  s = self._to_string(val_t, context, addLabel, 
>> useThisFormat, None_string, localize)Feb 21 11:00:39 new-weather-machine 
>> journal: weewx[22334] ERROR weewx.cheetahgenerator:  File 
>> "/usr/share/weewx/weewx/units.py", line 748, in _to_stringFeb 21 11:00:39 
>> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>>  val_str = self.delta_secs_to_string(val_t[0], format_string)Feb 21 
>> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
>> 796, in delta_secs_to_stringFeb 21 11:00:39 new-weather-machine journal: 
>> weewx[22334] ERROR weewx.cheetahgenerator:  ans = 
>> locale.format_string(label_format, etime_dict)Feb 21 11:00:39 
>> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>>  File "/usr/lib64/python3.6/locale.py", line 233, in format_stringFeb 
>> 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  new_val.append(format(perc.group(), val, 
>> grouping))Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
>> weewx.cheetahgenerator:  File "/usr/lib64/python3.6/locale.py", line 
>> 194, in formatFeb 21 11:00:39 new-weather-machine journal: weewx[22334] 
>> ERROR weewx.cheetahgenerator:  return _format(percent, value, grouping, 
>> monetary, *additional)Feb 21 11:00:39 new-weather-machine journal: 
>> weewx[22334] ERROR weewx.cheetahgenerator:  File 
>> "/usr/lib64/python3.6/locale.py", line 200, in _formatFeb 21 11:00:39 
>> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>>  formatted = percent % valueFeb 21 11:00:39 new-weather-machine 
>> journal: 

Re: [weewx-user] changing to metric system when using driver as a standalone program

[Tom Keffer]

The Vantage series reports measurements in the US Customary unit system.
Because you are printing packets directly from the driver, that's what
you're going to get.

One thing you can do is take advantage of one of the functions in units.py.
Try this:

import weewx.units
for packet in vantage.genDavisArchiveRecords(since_ts):
new_packet = weewx.units.to_METRICWX(packet)
print(new_packet)



On Mon, Feb 21, 2022 at 6:40 AM Saverio Guzzo  wrote:

> Hello community!
>
> I'm using the vantage's driver as a standalone program and I'm wondering
> if there is an way to convert the measurements to the metric system.
> I tried to edit the entry "*unit_system*" of the  file "
> *weewx-x.y.z/weewx.conf*" to 'metric', but when running the following
> piece of code
>
> *for packet in vantage.genDavisArchiveRecords(since_ts):*
> * print(packet)*
>
> I still get all the measurements in US system.
>
> What I am missing?
>
> Thank you very much for your help, I appreciate it :)
> Saverio
>
> --
> 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/9e5b1613-3b95-4696-aa40-f928d42d3c92n%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/CAPq0zEDMFo8cW1skxRBhGYmgr8%3DT%2BKZA5JU9VzSUO8afq9-Pqg%40mail.gmail.com.

Re: [weewx-user] Re: Problem with Vantage Vue

[Tom Keffer]

All of those log entries were put there by other services. There is nothing
in the log that indicates that weewxd is even running.

On Mon, Feb 21, 2022 at 8:09 AM geo...@gmail.com  wrote:

> IP is correct. After stop, start or restart showed no change, I restarted
> the Raspberry. Now this is in the log and apparently stops at Finished
> Clean php session files:
>
> pi@weewx:~ $ sudo tail -f /var/log/syslog
> Feb 21 15:25:46 weewx systemd[856]: Startup finished in 1.866s.
> Feb 21 15:25:46 weewx systemd[1]: Started User Manager for UID 1000.
> Feb 21 15:25:46 weewx systemd[1]: Started Session 1 of user pi.
> Feb 21 15:39:02 weewx CRON[1587]: (root) CMD (  [ -x
> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
> /usr/lib/php/sessionclean; fi)
> Feb 21 15:39:05 weewx systemd[1]: Starting Clean php session files...
> Feb 21 15:39:05 weewx systemd[1]: Starting Cleanup of Temporary
> Directories...
> Feb 21 15:39:05 weewx systemd[1]: systemd-tmpfiles-clean.service:
> Succeeded.
> Feb 21 15:39:05 weewx systemd[1]: Finished Cleanup of Temporary
> Directories.
> Feb 21 15:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
> Feb 21 15:39:05 weewx systemd[1]: Finished Clean php session files.
> Feb 21 16:09:01 weewx CRON[2515]: (root) CMD (  [ -x
> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
> /usr/lib/php/sessionclean; fi)
> Feb 21 16:09:05 weewx systemd[1]: Starting Clean php session files...
> Feb 21 16:09:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
> Feb 21 16:09:05 weewx systemd[1]: Finished Clean php session files.
> Feb 21 16:17:01 weewx CRON[2806]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Feb 21 16:24:19 weewx rngd[378]: stats: bits received from HRNG source:
> 80064
> Feb 21 16:24:19 weewx rngd[378]: stats: bits sent to kernel pool: 33824
> Feb 21 16:24:19 weewx rngd[378]: stats: entropy added to kernel pool: 33824
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 successes: 4
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 failures: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Monobit: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Poker: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Runs: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Long run: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Continuous
> run: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: HRNG source speed: (min=748.295;
> avg=753.644; max=761.423)Kibits/s
> Feb 21 16:24:19 weewx rngd[378]: stats: FIPS tests speed: (min=16.909;
> avg=20.704; max=22.492)Mibits/s
> Feb 21 16:24:19 weewx rngd[378]: stats: Lowest ready-buffers level: 2
> Feb 21 16:24:19 weewx rngd[378]: stats: Entropy starvations: 0
> Feb 21 16:24:19 weewx rngd[378]: stats: Time spent starving for entropy:
> (min=0; avg=0.000; max=0)us
> Feb 21 16:39:01 weewx CRON[3443]: (root) CMD (  [ -x
> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then
> /usr/lib/php/sessionclean; fi)
> Feb 21 16:39:05 weewx systemd[1]: Starting Clean php session files...
> Feb 21 16:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
> Feb 21 16:39:05 weewx systemd[1]: Finished Clean php session files.
>
> I used the weewx version 4.6.2 on a Raspberry 2.
> vince schrieb am Sonntag, 20. Februar 2022 um 23:12:29 UTC+1:
>
>>
>> Connection refused is the other computer isn't listening and accepting
>> traffic on that port.
>> Check you have the right ip address set in your weewx.conf file
>>
>> --
> 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/f92dc023-b2f6-4f36-953e-4a32a642ef21n%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/CAPq0zEC_HEq9bNo4UYVZcm%3DrpFRZZCmDyfz-qVMo39FiUSW0QQ%40mail.gmail.com.

[weewx-user] Re: Belchertown w/MQTT Temperature not updating?

[DaveStLou]

Bumping this since the issue still exists.
My own assessment of the lack of response to this thread:

   - I haven't provided enough or right information.
   - Not many users have expertise in Belchertown skin. 
   - Truly is a bug. 

If the first, please let me know what if any information would help in 
making suggestions to solve my issue. If the last two, I guess reporting on 
github is next step. Any other resources are appreciated as well.

Thanks!

On Friday, February 18, 2022 at 4:30:59 PM UTC-6 DaveStLou wrote:

> MQTT is sending data. I turned on debug. Logs shows the site reading the 
> data properly. Only fields changing are data received time, wind direction 
> and beaufort category. All other fields only updated by refreshing the 
> entire page.
>
> Seems unlikely to me that it's a bug. I looked at 
> https://belchertownweather.com/ and it is working correctly there.
>
> Anyone have any thoughts or direction? 
> On Friday, February 18, 2022 at 6:35:31 AM UTC-6 DaveStLou wrote:
>
>> Seems only the wind data is updating (direction and speed) from the mqtt 
>> data. In addition to temperature, I realize now that the barometer, dew 
>> point and humidity are also only updating when I refresh.
>>
>> Thanks for any assistance!
>>
>> On Friday, February 18, 2022 at 6:31:25 AM UTC-6 DaveStLou wrote:
>>
>>> I've attached logs, configs and mqtt data a couple of days ago. 
>>> Temperature and other data is in the mqtt file.
>>>
>>> Any thoughts on getting the live mqtt data to update temperature as 
>>> expected?
>>>
>>> Thanks!
>>>
>>> On Wednesday, February 16, 2022 at 6:53:56 AM UTC-6 DaveStLou wrote:
>>>
 Here's a sample from subscribing to weather/loop. Shows outside temp at 
 51.4. Meanwhile my weather page at https://OakvilleWX.com on my 
 browser was still showing 51.1 but wind was changing every three seconds 
 as 
 expected.

 When I refreshed page in browser it then showed 51.4 as well.

 On Wednesday, February 16, 2022 at 6:24:36 AM UTC-6 DaveStLou wrote:

> Attached is a clip from my log this morning with debug on and config 
> files. I'll subscribe to the topic and post that asap.
> Thanks
>
> On Tuesday, February 15, 2022 at 5:00:03 PM UTC-6 vince wrote:
>
>> On Tuesday, February 15, 2022 at 1:24:28 PM UTC-8 DaveStLou wrote:
>>
>>> On my station website OakvilleWX.com, I see MQTT updates most values 
>>> real-time as it's supposed to. If I leave it up for a time though, I've 
>>> noticed that the temperature doesn't update unless I refresh the page.
>>>
>>>
>> In the absence of any logs or config files or description of your 
>> station,   I can only suggest doing an external mqtt subscribe to the 
>> same 
>> topic you have weewx subscribing to and verify you are sending 
>> temperature 
>> data.
>>
>>

-- 
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/e6dd38a8-2d69-4f23-85ae-f485d85860d7n%40googlegroups.com.

[weewx-user] Re: Steinberg Systems Modell: SBS-WS-200

[Δημήτρης Βήχος]

your weather station seems like wh 1080 clone . weewx works fine with these 
weather stations with fineoffsetusb driver

Στις Δευτέρα 21 Φεβρουαρίου 2022 στις 4:59:01 μ.μ. UTC+2, ο χρήστης 
kalli...@gmail.com έγραψε:

> Hello everybody :-)
>
> I'm new here,my name is Karl and i am retiree. I install Weewx on my 
> Notebook HP8440p whit Ubuntu 20.04 and it's work.Bud is Weewx working whit 
> a Steinberg Systems  Modell: SBS-WS-200?
>
> best regards Karl
>

-- 
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/117cae79-a67f-494d-a95a-2815ced0114bn%40googlegroups.com.

[weewx-user] Re: Problem with Vantage Vue

[geo...@gmail.com]

IP is correct. After stop, start or restart showed no change, I restarted 
the Raspberry. Now this is in the log and apparently stops at Finished 
Clean php session files:

pi@weewx:~ $ sudo tail -f /var/log/syslog
Feb 21 15:25:46 weewx systemd[856]: Startup finished in 1.866s.
Feb 21 15:25:46 weewx systemd[1]: Started User Manager for UID 1000.
Feb 21 15:25:46 weewx systemd[1]: Started Session 1 of user pi.
Feb 21 15:39:02 weewx CRON[1587]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
/usr/lib/php/sessionclean; fi)
Feb 21 15:39:05 weewx systemd[1]: Starting Clean php session files...
Feb 21 15:39:05 weewx systemd[1]: Starting Cleanup of Temporary 
Directories...
Feb 21 15:39:05 weewx systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Feb 21 15:39:05 weewx systemd[1]: Finished Cleanup of Temporary Directories.
Feb 21 15:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
Feb 21 15:39:05 weewx systemd[1]: Finished Clean php session files.
Feb 21 16:09:01 weewx CRON[2515]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
/usr/lib/php/sessionclean; fi)
Feb 21 16:09:05 weewx systemd[1]: Starting Clean php session files...
Feb 21 16:09:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
Feb 21 16:09:05 weewx systemd[1]: Finished Clean php session files.
Feb 21 16:17:01 weewx CRON[2806]: (root) CMD (   cd / && run-parts --report 
/etc/cron.hourly)
Feb 21 16:24:19 weewx rngd[378]: stats: bits received from HRNG source: 
80064
Feb 21 16:24:19 weewx rngd[378]: stats: bits sent to kernel pool: 33824
Feb 21 16:24:19 weewx rngd[378]: stats: entropy added to kernel pool: 33824
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 successes: 4
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2 failures: 0
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Monobit: 0
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Poker: 0
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Runs: 0
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Long run: 0
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS 140-2(2001-10-10) Continuous 
run: 0
Feb 21 16:24:19 weewx rngd[378]: stats: HRNG source speed: (min=748.295; 
avg=753.644; max=761.423)Kibits/s
Feb 21 16:24:19 weewx rngd[378]: stats: FIPS tests speed: (min=16.909; 
avg=20.704; max=22.492)Mibits/s
Feb 21 16:24:19 weewx rngd[378]: stats: Lowest ready-buffers level: 2
Feb 21 16:24:19 weewx rngd[378]: stats: Entropy starvations: 0
Feb 21 16:24:19 weewx rngd[378]: stats: Time spent starving for entropy: 
(min=0; avg=0.000; max=0)us
Feb 21 16:39:01 weewx CRON[3443]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then 
/usr/lib/php/sessionclean; fi)
Feb 21 16:39:05 weewx systemd[1]: Starting Clean php session files...
Feb 21 16:39:05 weewx systemd[1]: phpsessionclean.service: Succeeded.
Feb 21 16:39:05 weewx systemd[1]: Finished Clean php session files.

I used the weewx version 4.6.2 on a Raspberry 2.
vince schrieb am Sonntag, 20. Februar 2022 um 23:12:29 UTC+1:

>
> Connection refused is the other computer isn't listening and accepting 
> traffic on that port.
> Check you have the right ip address set in your weewx.conf file
>
>

-- 
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/f92dc023-b2f6-4f36-953e-4a32a642ef21n%40googlegroups.com.

[weewx-user] Steinberg Systems Modell: SBS-WS-200

[Kalli Gøtze]

Hello everybody :-)

I'm new here,my name is Karl and i am retiree. I install Weewx on my 
Notebook HP8440p whit Ubuntu 20.04 and it's work.Bud is Weewx working whit 
a Steinberg Systems  Modell: SBS-WS-200?

best regards Karl

-- 
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/3595d05e-8190-4cd9-b829-0453b6ad8806n%40googlegroups.com.

[weewx-user] changing to metric system when using driver as a standalone program

[Saverio Guzzo]

Hello community!

I'm using the vantage's driver as a standalone program and I'm wondering if 
there is an way to convert the measurements to the metric system.
I tried to edit the entry "*unit_system*" of the  file "
*weewx-x.y.z/weewx.conf*" to 'metric', but when running the following piece 
of code

*for packet in vantage.genDavisArchiveRecords(since_ts):*
* print(packet)*

I still get all the measurements in US system.

What I am missing?

Thank you very much for your help, I appreciate it :)
Saverio

-- 
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/9e5b1613-3b95-4696-aa40-f928d42d3c92n%40googlegroups.com.

Re: [weewx-user] best way for running a driver program as standalone

[Saverio Guzzo]

P.S. I was trying with "python3 setup.py install" and pip but it was not a 
success in both cases.

On Monday, 21 February 2022 at 14:21:35 UTC Saverio Guzzo wrote:

> Brilliant! This works :) thank you so much Tom
>
> On Saturday, 19 February 2022 at 12:51:16 UTC tke...@gmail.com wrote:
>
>> We need a little more information. For example, you said you tried to 
>> install the requirements, but did not give the commands you tried. Did you 
>> use pip? Or apt-get? Or, something else?
>>
>> I am guessing that you probably got the 
>> distutils.errors.DistutilsOptionError error because you tried installing 
>> the prerequisites in the same directory as weewx. If you try this, venv 
>> will see the setup.cfg file and try and install the prerequisites in 
>> /home/weewx.
>>
>> This works for me with venv. 
>>
>> tkeffer@nuc:~$ *cd ~*
>> tkeffer@nuc:~$ *python3 -m venv py-weewx*
>> tkeffer@nuc:~$ *source py-weewx/bin/activate*
>> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install configobj*
>> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install Cheetah3*
>> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install Pillow*
>> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyserial*
>> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyusb*
>> (py-weewx) tkeffer@nuc:~$ *wget 
>> http://weewx.com/downloads/weewx-4.6.2.tar.gz 
>> *
>> (py-weewx) tkeffer@nuc:~$ *tar xvf weewx-4.6.2.tar.gz *
>> (py-weewx) tkeffer@nuc:~$ *cd weewx-4.6.2*
>> (py-weewx) tkeffer@nuc:~/weewx-4.6.2$ *PYTHONPATH=bin python3 -m 
>> weewx.drivers.vantage*
>> {'dateTime': 1645274802, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 
>> 68.9, 'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 
>> 3.0, 'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0, 
>> 'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2, 
>> 'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52, 
>> 'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0, 
>> 'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0, 
>> 'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0, 
>> 'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0, 
>> 'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0, 
>> 'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63, 
>> 'sunrise': 1645282920, 'sunset': 1645321140, 'rain': None}
>> {'dateTime': 1645274803, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 
>> 68.9, 'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 
>> 3.0, 'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0, 
>> 'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2, 
>> 'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52, 
>> 'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0, 
>> 'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0, 
>> 'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0, 
>> 'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0, 
>> 'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0, 
>> 'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63, 
>> 'sunrise': 1645282920, 'sunset': 1645321140, 'rain': 0.0}
>>
>>
>>
>> On Thu, Feb 17, 2022 at 9:36 AM Saverio Guzzo  wrote:
>>
>>> Hello community, this is my first post here! :)
>>>
>>> I am interested in running the vantage's driver program as standalone, 
>>> in order to integrate it in my application. Could you please give me some 
>>> suggestions on how to achieve that?
>>>
>>> I am struggling already at installing the requirements I tried to 
>>> install them using both venv and conda env, but I get the error 
>>> "distutils.errors.DistutilsOptionError: can't combine user with prefix, 
>>> exec_prefix/home, or install_(plat)base".
>>>
>>> Should I also export the env variable PYTHONPATH=bin python -m 
>>> weewx.drivers.vantage? When trying to do this, I get the errors "-bash: 
>>> export: not valid in this context: -m" and "-bash: export: 
>>> `weewx.drivers.vantage': not a valid identifier".
>>>
>>> Could you kindly give me some directions? I would really aprpeciate it :)
>>>
>>> Thanks,
>>> Saverio
>>>
>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/0bb1abeb-0ff2-4a65-b345-042e51d57482n%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 

Re: [weewx-user] best way for running a driver program as standalone

[Saverio Guzzo]

Brilliant! This works :) thank you so much Tom

On Saturday, 19 February 2022 at 12:51:16 UTC tke...@gmail.com wrote:

> We need a little more information. For example, you said you tried to 
> install the requirements, but did not give the commands you tried. Did you 
> use pip? Or apt-get? Or, something else?
>
> I am guessing that you probably got the 
> distutils.errors.DistutilsOptionError error because you tried installing 
> the prerequisites in the same directory as weewx. If you try this, venv 
> will see the setup.cfg file and try and install the prerequisites in 
> /home/weewx.
>
> This works for me with venv. 
>
> tkeffer@nuc:~$ *cd ~*
> tkeffer@nuc:~$ *python3 -m venv py-weewx*
> tkeffer@nuc:~$ *source py-weewx/bin/activate*
> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install configobj*
> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install Cheetah3*
> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install Pillow*
> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyserial*
> (py-weewx) tkeffer@nuc:~$ *python3 -m pip install pyusb*
> (py-weewx) tkeffer@nuc:~$ *wget 
> http://weewx.com/downloads/weewx-4.6.2.tar.gz 
> *
> (py-weewx) tkeffer@nuc:~$ *tar xvf weewx-4.6.2.tar.gz *
> (py-weewx) tkeffer@nuc:~$ *cd weewx-4.6.2*
> (py-weewx) tkeffer@nuc:~/weewx-4.6.2$ *PYTHONPATH=bin python3 -m 
> weewx.drivers.vantage*
> {'dateTime': 1645274802, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 
> 68.9, 'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 
> 3.0, 'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0, 
> 'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2, 
> 'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52, 
> 'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0, 
> 'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0, 
> 'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0, 
> 'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0, 
> 'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0, 
> 'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63, 
> 'sunrise': 1645282920, 'sunset': 1645321140, 'rain': None}
> {'dateTime': 1645274803, 'usUnits': 1, 'barometer': 30.141, 'inTemp': 
> 68.9, 'inHumidity': 41.0, 'outTemp': 42.1, 'windSpeed': 1.0, 'windSpeed10': 
> 3.0, 'windDir': 202.0, 'outHumidity': 80.0, 'rainRate': 0.0, 'UV': 0.0, 
> 'radiation': 0.0, 'stormRain': 0.0, 'dayRain': 0.0, 'monthRain': 0.2, 
> 'yearRain': 17.85, 'dayET': 0.004, 'monthET': 1.03, 'yearET': 1.52, 
> 'leafWet4': 0.0, 'insideAlarm': 0, 'rainAlarm': 0, 'outsideAlarm1': 0, 
> 'outsideAlarm2': 0, 'extraAlarm1': 0, 'extraAlarm2': 0, 'extraAlarm3': 0, 
> 'extraAlarm4': 0, 'extraAlarm5': 0, 'extraAlarm6': 0, 'extraAlarm7': 0, 
> 'extraAlarm8': 0, 'soilLeafAlarm1': 0, 'soilLeafAlarm2': 0, 
> 'soilLeafAlarm3': 0, 'soilLeafAlarm4': 0, 'txBatteryStatus': 0, 
> 'consBatteryVoltage': 3.83, 'forecastIcon': 6, 'forecastRule': 63, 
> 'sunrise': 1645282920, 'sunset': 1645321140, 'rain': 0.0}
>
>
>
> On Thu, Feb 17, 2022 at 9:36 AM Saverio Guzzo  wrote:
>
>> Hello community, this is my first post here! :)
>>
>> I am interested in running the vantage's driver program as standalone, in 
>> order to integrate it in my application. Could you please give me some 
>> suggestions on how to achieve that?
>>
>> I am struggling already at installing the requirements I tried to 
>> install them using both venv and conda env, but I get the error 
>> "distutils.errors.DistutilsOptionError: can't combine user with prefix, 
>> exec_prefix/home, or install_(plat)base".
>>
>> Should I also export the env variable PYTHONPATH=bin python -m 
>> weewx.drivers.vantage? When trying to do this, I get the errors "-bash: 
>> export: not valid in this context: -m" and "-bash: export: 
>> `weewx.drivers.vantage': not a valid identifier".
>>
>> Could you kindly give me some directions? I would really aprpeciate it :)
>>
>> Thanks,
>> Saverio
>>
>> -- 
>> 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+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/0bb1abeb-0ff2-4a65-b345-042e51d57482n%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/29286295-f69e-4639-b4b1-0be4eff44634n%40googlegroups.com.

Re: [weewx-user] 4.6.x RPMs fail PGP signature validation

[Tom Keffer]

Matthew Wall signed the last couple of releases. He may have used a
different signature. If he did, I don't have access to it, and he is on a
small boat in the Caribbean until the end of the month. I'll see if I can
contact him.

-tk

On Mon, Feb 21, 2022 at 12:24 AM Scott Shambarger <
scott.shambar...@gmail.com> wrote:

> Hi,
>
> FYI, all the 4.6.x rpms fail PGP signature validation. The tkeffer key on
> weewx.com/keys.html (keyid a0cb255b75bf977c) has signed all previous
> releases, but rpms since 4.6.0 are all signed with an unpublished keyid of
> 50abae5f15306a67.
>
> With a yum/dnf repo configured with gpgcheck=1 this prevents new releases
> from passing validation.  Is there a new source for the signing key?
>
> Thanks,
> Scott
>
> --
> 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/570ff1e2-6bbc-482f-9dea-e2a2f279511cn%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/CAPq0zECEvZOWs2n8ck4mY%2B8iFVcP_V9PN6-Qfnb4oyByjT6fdw%40mail.gmail.com.

Re: [weewx-user] Vantage Vue wind cup size setting with wee_device

[Tom Keffer]

The console has no way of knowing what size wind cup is mounted on the ISS.
Someone has to tell it. Generally, that is done by the factory when they
ship the unit out. Under "extraordinary circumstances" a user might have to
do this if, for example, s/he changed the cup size.

I have only owned (and seen) the regular "large" size, so I don't have
anything to compare it to. You'd have to ask Davis what size cup you have.

On Sun, Feb 20, 2022 at 8:03 PM Gary Strand  wrote:

>
> I know this is an old thread but is precisely the question I have.
> "wee_device" reports the cups as "large", but the cups on my sensor don't
> seem large to me. Are the "small" really tiny?
>
> Just curious because what counts as "extraordinary circumstances"? On the
> day of the Colorado Marshall Fire, I recorded a gust of 49 mph when other
> stations were reporting much higher numbers; is this such a circumstance?
>
> Thanks!
>
>
> On Saturday, October 20, 2018 at 7:57:52 PM UTC-6 tke...@gmail.com wrote:
>
>> Thanks, Philip. That's the first reference I've seen to "Vue" cups. As I
>> said, you'd have to ask Davis.
>>
>> But, in any case, don't worry about it. Only under extraordinary
>> circumstances do you need to set it.
>>
>> -tk
>>
>> On Sat, Oct 20, 2018 at 6:51 PM Philip Kutzenco 
>> wrote:
>>
>>> Thomas,
>>>
>>> Thanks for the reply. I won't worry about it. The reason I asked is that
>>> the help file for Davis' Weatherlink software shows three options. See the
>>> attached screen shot I took for setting that in the console with
>>> Weatherlink. Evidently, you can set a VantagePro to use small cups or
>>> Vue/Other cups. I'll just leave the value as it is set in the console
>>> without setting it explicitly.
>>> phil
>>>
>>> On Saturday, October 20, 2018 at 8:22:26 PM UTC-4, Thomas Keffer wrote:

 A Vantage (whether a Vue or a VantagePro) ships with a value in the
 EEPROM firmware that matches its cup size. Unless you change the cups,
 there is no reason to mess with this value. The wee_device utility option
 is there if, for some reason, you have to change the cups.

 To answer your question, the Davis documentation lists only two sizes:
 small and large. If there's a third "Vue" sized, I haven't heard of it.
 You'd have to ask Davis.

 -tk

 On Sat, Oct 20, 2018 at 7:35 AM Philip Kutzenco 
 wrote:

> Now that I have my external website operational (
> https://wx.kutzenco.com) with a Mosquitto MQTT broker and Belchertown
> skin, I'm spending a bit more time reviewing the weeWX documentation to 
> get
> a deeper understanding of my system. I'm hoping to do some customization.
>
> I have a Davis Vantage Vue weather station and weeWX running on a
> Raspberry Pi Zero W. I see that the Davis Weatherlink software gives the
> options for wind cup size as Small, Large or Vue/Other. That Davis
> documentation says that Vantage Pro systems generally ship with large 
> cups,
> and that (obviously) Vantage Vue systems ship with Vue cups.
>
> The wee_device --help command mentions only Small and Large options
> for wind cup size. Is there an option for Vue/other cups? I don't know 
> what
> is adjusted in the readings/calculations by specifying different cup 
> sizes.
> I didn't see that called out in the weeWX documention. I suspect the
> difference is minimal, but, just to ensure that everything can be set
> properly with weeWX does that option need to be added to wee_device for
> Vantage systems, if it isn't there?
>
> phil
>
> --
> 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+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 --
>>> 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+...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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/c52c96d6-2b18-4768-b823-c5957e17bdb1n%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 

[weewx-user] Re: 4.6.2. update problem with wee_import

[jannep...@gmail.com]

hi
python 2. Here is log. When I start weewx, LOOP is working. I can get 
weather station info to terminal, but maybe not to database. I have a 
Ventus weather station and I download data every now and then to windows. 
>From there I import the data in csv to weewx. 

Janne

Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Initializing weewx 
version 4.6.2
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using Python 2.7.17 
(default, Feb 27 2021, 15:10:58) #012[GCC 7.5.0]
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Platform 
Linux-5.4.0-99-generic-x86_64-with-LinuxMint-19.3-tricia
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Locale is 
'fi_FI.UTF-8'
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Debug is 0
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Loading station 
type WS6in1 (user.ws6in1)
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: StdConvert target 
unit is 0x11
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Archive will use 
data binding wx_binding
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: StationRegistry: 
Registration not requested.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: Wunderground: 
Posting not enabled.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: PWSweather: 
Posting not enabled.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: CWOP: Posting not 
enabled.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: WOW: Posting not 
enabled.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.restx: AWEKAS: Posting 
not enabled.
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: 'pyephem' not 
detected, extended almanac data is not available
Feb 21 14:31:09 janne-Lat weewx[21011] INFO __main__: Starting up weewx 
version 4.6.2
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Starting 
backfill of daily summaries
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.manager: Daily summaries 
up to date
Feb 21 14:31:09 janne-Lat weewx[21011] INFO weewx.engine: Starting main 
packet loop.

maanantai 21. helmikuuta 2022 klo 9.37.18 UTC+2 gjr80 kirjoitti:

> Janne,
>
> Could you please let me know whether WeeWX is being run under python 2 or 
> 3? You can tell by looking at the WeeWX log during WeeWX startup (the 
> python version is logged) or you can look at the first line of any of the 
> wee_xx (eg wee_database) utilities in the /usr/share/weewx directory.
>
> If yo cannot work it out please restart WeeWX and post a log extract 
> showing the full WeeWX startup.
>
> Gary
>
> On Monday, 21 February 2022 at 04:21:57 UTC+10 jannep...@gmail.com wrote:
>
>> Hi, I updated from 4.5 to 4.6.2 and my wee_import stop to next message:
>>
>> I use WS6in1-driver with my Ventus.
>>
>> ...
>> Using WeeWX configuration file /etc/weewx/weewx.conf
>> Starting wee_import...
>> A CSV import from source file '/var/tmp/data.csv' has been requested.
>> Using database binding 'wx_binding', which is bound to database 
>> 'weewx.sdb'
>> Destination table 'archive' unit system is '0x11' (METRICWX).
>> Missing derived observations will be calculated.
>> This is a dry run, imported data will not be saved to archive.
>> Starting dry run import ...
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_import", line 899, in 
>> main()
>>   File "/usr/share/weewx/wee_import", line 829, in main
>> source_obj.run()
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 372, in run
>> _raw_data = self.getRawData(period)
>>   File "/usr/share/weewx/weeimport/csvimport.py", line 246, in getRawData
>> self.map = self.parseMap('CSV', _csv_reader, self.csv_config_dict)
>>   File "/usr/share/weewx/weeimport/weeimport.py", line 635, in parseMap
>> and _val['units'] not in weewx.units.USUnits.values():
>> AttributeError: 'ListOfDicts' object has no attribute 'values'
>> ..
>>
>> What this does mean? Any help? 
>>
>> Is there easy way to get back to working configuration (4.5)? 
>>
>> regards
>> Janne
>>
>

-- 
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 

[weewx-user] Re: Cheetah error after update to WeeWX 4.6.2

[František Slimařík]

Ok, I found the issue. I was using following extension  
vinceskahan/vds-weewx-lastrain-extension: 
extension for weewx to generate some lastrain timestamps and delta time 
reports (github.com) 
 which was 
updated recently for version 4.6.0. But I found also another interesting 
thing, following tags are shown as N/A instead of value:

$current.windGustDir.ordinal_compass
$day.wind.gustdir.ordinal_compass

Following tag is OK:
$current.windDir.ordinal_compass

I am using observer driver.

Dne pondělí 21. února 2022 v 11:03:33 UTC+1 uživatel František Slimařík 
napsal:

> Hello, 
>
> can you gimme small hint what should be checked in cheetah template after 
> updated to version 4.6.2? I am using python3 and after update all templates 
> works fine except main one. Unfortunately for me I made much of 
> customizations there so I ´d like to know to which part I should focus 
> mainly :)
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator: Evaluation of template 
> /etc/weewx/skins/neowx/index.html.tmpl failed with exception ' 'TypeError'>'Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
> ERROR weewx.cheetahgenerator:  Ignoring template 
> /etc/weewx/skins/neowx/index.html.tmplFeb 21 11:00:39 new-weather-machine 
> journal: weewx[22334] ERROR weewx.cheetahgenerator:  Reason: %x format: 
> an integer is required, not dictFeb 21 11:00:39 new-weather-machine 
> journal: weewx[22334] ERROR weewx.cheetahgenerator:  Traceback (most 
> recent call last):Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
> ERROR weewx.cheetahgenerator:  File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generateFeb 21 
> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  unicode_string = 
> compiled_template.respond()Feb 21 11:00:39 new-weather-machine journal: 
> weewx[22334] ERROR weewx.cheetahgenerator:  File 
> "_etc_weewx_skins_neowx_index_html_tmpl.py", line 1273, in respondFeb 21 
> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
> 1005, in __str__Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
> ERROR weewx.cheetahgenerator:  s = self.toString()Feb 21 11:00:39 
> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>  File "/usr/share/weewx/weewx/units.py", line 1000, in toStringFeb 21 
> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  localize=localize)Feb 21 11:00:39 
> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>  File "/usr/share/weewx/weewx/units.py", line 688, in toStringFeb 21 
> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  s = self._to_string(val_t, context, addLabel, 
> useThisFormat, None_string, localize)Feb 21 11:00:39 new-weather-machine 
> journal: weewx[22334] ERROR weewx.cheetahgenerator:  File 
> "/usr/share/weewx/weewx/units.py", line 748, in _to_stringFeb 21 11:00:39 
> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>  val_str = self.delta_secs_to_string(val_t[0], format_string)Feb 21 
> 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
> 796, in delta_secs_to_stringFeb 21 11:00:39 new-weather-machine journal: 
> weewx[22334] ERROR weewx.cheetahgenerator:  ans = 
> locale.format_string(label_format, etime_dict)Feb 21 11:00:39 
> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>  File "/usr/lib64/python3.6/locale.py", line 233, in format_stringFeb 
> 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  new_val.append(format(perc.group(), val, 
> grouping))Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
> weewx.cheetahgenerator:  File "/usr/lib64/python3.6/locale.py", line 
> 194, in formatFeb 21 11:00:39 new-weather-machine journal: weewx[22334] 
> ERROR weewx.cheetahgenerator:  return _format(percent, value, grouping, 
> monetary, *additional)Feb 21 11:00:39 new-weather-machine journal: 
> weewx[22334] ERROR weewx.cheetahgenerator:  File 
> "/usr/lib64/python3.6/locale.py", line 200, in _formatFeb 21 11:00:39 
> new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
>  formatted = percent % valueFeb 21 11:00:39 new-weather-machine 
> journal: weewx[22334] ERROR weewx.cheetahgenerator:  TypeError: %x 
> format: an integer is required, not dict*
>

-- 
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 

Re: [weewx-user] Re: Sudden error running reports? Any help appreciated

[paul...@gmail.com]

Hi Andy

If you do want to have a Yesterday graph you can use:

time_length = days_ago
time_ago = 1

See 
https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#time-scales-for-charts

Paul

On Sunday, 20 February 2022 at 10:28:32 UTC andyhud...@googlemail.com wrote:

> Yep, it was the time in my yesterday graph.conf - much appreciated. I 
> decided to remove the 'yesterday' option and the reports all run fine now.
>
> Thanks again!
>
> Andy
> On Saturday, 19 February 2022 at 16:18:35 UTC tke...@gmail.com wrote:
>
>> Option "time_length 
>> " is set 
>> to the string 'yesterday', instead of a number. 
>>
>> On Sat, Feb 19, 2022 at 8:04 AM 'andyhud...@googlemail.com' via 
>> weewx-user  wrote:
>>
>>> Edit - noting it's not a sudden error, my Yesterday Graph has not 
>>> updated for 10 days, so i must be something in my graphs.conf ... :)
>>>
>>> Andy
>>>
>>> On Saturday, 19 February 2022 at 15:35:10 UTC andyhud...@googlemail.com 
>>> wrote:
>>>
 Afternoon - weewx has been happily running, i noticed when i run 
 reports i get an error (yet the website seems to be working ok? -  
 http://www.finchamweather.co.uk/) 

 Any help would be really appreciated:

 Using configuration file /etc/weewx/weewx.conf

 Generating for all time

 Traceback (most recent call last):

   File "/usr/share/weewx/weewx/reportengine.py", line 196, in run

 obj.start()

   File "/usr/share/weewx/weewx/reportengine.py", line 281, in start

 self.run()

   File "/usr/share/weewx/user/belchertown.py", line 2520, in run

 time_length = int(time_length)

 ValueError: invalid literal for int() with base 10: 'yesterday'


 Andy

>>> -- 
>>> 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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/fb81a4c6-39b6-4542-9d23-aff2ec4cefd5n%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/bb0e9c17-3a3b-4687-bf51-5e0e0f5dc74cn%40googlegroups.com.

[weewx-user] Cheetah error after update to WeeWX 4.6.2

[František Slimařík]

Hello, 

can you gimme small hint what should be checked in cheetah template after 
updated to version 4.6.2? I am using python3 and after update all templates 
works fine except main one. Unfortunately for me I made much of 
customizations there so I ´d like to know to which part I should focus 
mainly :)
























*Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator: Evaluation of template 
/etc/weewx/skins/neowx/index.html.tmpl failed with exception ''Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
ERROR weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/neowx/index.html.tmplFeb 21 11:00:39 new-weather-machine 
journal: weewx[22334] ERROR weewx.cheetahgenerator:  Reason: %x format: 
an integer is required, not dictFeb 21 11:00:39 new-weather-machine 
journal: weewx[22334] ERROR weewx.cheetahgenerator:  Traceback (most 
recent call last):Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
ERROR weewx.cheetahgenerator:  File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generateFeb 21 
11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  unicode_string = 
compiled_template.respond()Feb 21 11:00:39 new-weather-machine journal: 
weewx[22334] ERROR weewx.cheetahgenerator:  File 
"_etc_weewx_skins_neowx_index_html_tmpl.py", line 1273, in respondFeb 21 
11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
1005, in __str__Feb 21 11:00:39 new-weather-machine journal: weewx[22334] 
ERROR weewx.cheetahgenerator:  s = self.toString()Feb 21 11:00:39 
new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
 File "/usr/share/weewx/weewx/units.py", line 1000, in toStringFeb 21 
11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  localize=localize)Feb 21 11:00:39 
new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
 File "/usr/share/weewx/weewx/units.py", line 688, in toStringFeb 21 
11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  s = self._to_string(val_t, context, addLabel, 
useThisFormat, None_string, localize)Feb 21 11:00:39 new-weather-machine 
journal: weewx[22334] ERROR weewx.cheetahgenerator:  File 
"/usr/share/weewx/weewx/units.py", line 748, in _to_stringFeb 21 11:00:39 
new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
 val_str = self.delta_secs_to_string(val_t[0], format_string)Feb 21 
11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  File "/usr/share/weewx/weewx/units.py", line 
796, in delta_secs_to_stringFeb 21 11:00:39 new-weather-machine journal: 
weewx[22334] ERROR weewx.cheetahgenerator:  ans = 
locale.format_string(label_format, etime_dict)Feb 21 11:00:39 
new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
 File "/usr/lib64/python3.6/locale.py", line 233, in format_stringFeb 
21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  new_val.append(format(perc.group(), val, 
grouping))Feb 21 11:00:39 new-weather-machine journal: weewx[22334] ERROR 
weewx.cheetahgenerator:  File "/usr/lib64/python3.6/locale.py", line 
194, in formatFeb 21 11:00:39 new-weather-machine journal: weewx[22334] 
ERROR weewx.cheetahgenerator:  return _format(percent, value, grouping, 
monetary, *additional)Feb 21 11:00:39 new-weather-machine journal: 
weewx[22334] ERROR weewx.cheetahgenerator:  File 
"/usr/lib64/python3.6/locale.py", line 200, in _formatFeb 21 11:00:39 
new-weather-machine journal: weewx[22334] ERROR weewx.cheetahgenerator: 
 formatted = percent % valueFeb 21 11:00:39 new-weather-machine 
journal: weewx[22334] ERROR weewx.cheetahgenerator:  TypeError: %x 
format: an integer is required, not dict*

-- 
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/72053eab-540c-43c8-b148-5eaf34bd395en%40googlegroups.com.

[weewx-user] 4.6.x RPMs fail PGP signature validation

[Scott Shambarger]

Hi,

FYI, all the 4.6.x rpms fail PGP signature validation. The tkeffer key on 
weewx.com/keys.html (keyid a0cb255b75bf977c) has signed all previous 
releases, but rpms since 4.6.0 are all signed with an unpublished keyid of 
50abae5f15306a67.

With a yum/dnf repo configured with gpgcheck=1 this prevents new releases 
from passing validation.  Is there a new source for the signing key?

Thanks,
Scott

-- 
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/570ff1e2-6bbc-482f-9dea-e2a2f279511cn%40googlegroups.com.