[weewx-user] Lots of rain Brisbane Aus

[Neville Davis]

For interest we have had a considerable amount of rain over the past 
week...several areas around us had in excess of 1000 (thousand)mm over a 
couple of days.

My local station had the following

[image: Screen Shot 2022-03-03 at 3.18.41 pm.png]
The bucket tips gave a max of 68mm/hr at one stage.

Nev

-- 
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/1b39a888-444f-4f75-b637-9826abcc3ad5n%40googlegroups.com.

[weewx-user] Re: Version 4.7.0

[Neville Davis]

Just updated my Pi to 4.7.0 from 4.5.1 with Belchertown skin 1.2 (with my 
extra pages and Aus BOM forecasts) without any hassles, all looks good so 
far

Nev

On Wednesday, March 2, 2022 at 4:06:20 PM UTC+10 jerry...@gmail.com wrote:

> Just upgraded my macOS and FreeBSD weather stations to 4.7 and all is good.
>
> On Tuesday, March 1, 2022 at 3:57:08 PM UTC-8 tke...@gmail.com wrote:
>
>> This version fixes a bunch of minor things, as well as introduces some 
>> minor new features.
>>
>> Change log:
>>
>> Introduced new option "generate_once". If True, templates will be generated
>> only on the first run of the reporting engine. Thanks to user Rich! PR #748.
>>
>> Added option wee_device --current for vantage.
>>
>> Fixed two typos in the Standard skin.
>>
>> Fixed spelling mistakes in the Norwegian translations.  Thanks to Aslak! 
>> PR#746
>>
>> Supply a sensible default context for group_deltatime when no context has 
>> been
>> specified.
>>
>> If windGustDir is missing, extract a value from the accumulators.
>>
>> Fixed typo that shows itself if no [Labels]/[[Generic]] section is supplied.
>> Fixes issue #752.
>>
>> Fixed calculation of field "bar_reduction" for Vantage type 2 LOOP packets.
>>
>> Fix problem that prevents windSpeed and windDir from being displayed in
>> the RSS feed. Fixes issue #755.
>>
>>

-- 
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/4ccc28d1-bb43-455c-87e0-5bdf13587d44n%40googlegroups.com.

Re: [weewx-user] wh23xx driver and weewx 4.6.2

[gjr80]

I should have tweaked before; whilst I realised the wh23xx driver had not 
been ported to python3 for some reason I had assumed it would still 
function under python2 and WeeWX4, this is not the case. I have done a 
quick port of the current wh23xx driver to python3/WeeWX 4 and it should 
now be compatible with WeeWX 4.x under python2 or python3. Could you try 
this version by replacing your current /usr/share/weewx/user/wh23xx.py with 
the attached file. Let me know how you go, in particular whether the driver 
functions correctly under WeeWX and I will submit a PR to the author.

Gary
On Tuesday, 1 March 2022 at 20:38:50 UTC+10 f4n...@gmail.com wrote:

> I tried to install it several times, and i have the wh23xx.py in 
> /usr/share/weewx/user
> but not sure if i copied it there by myself, as i couldn't see it after 
> installation. But i have install.py for sure in the installer directory 
> in the wh23xx directory
>
> Still, after *wee_config -- reconfigure /etc/weewx/weewx.conf* i just 
> get: 
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Installed drivers include:  0) Interceptor (user.interceptor)   
>1) SDR (user.sdr)  2) AcuRite 
> (weewx.drivers.acurite) 3) CC3000  (weewx.drivers.cc3000)  
> 4) FineOffsetUSB   (weewx.drivers.fousb)   5) Simulator   
> (weewx.drivers.simulator)   6) TE923   (weewx.drivers.te923)   
> 7) Ultimeter   (weewx.drivers.ultimeter)   8) Vantage 
> (weewx.drivers.vantage) 9) WMR100  (weewx.drivers.wmr100)   
>   10) WMR300  (weewx.drivers.wmr300) 11) WMR9x8 
>  (weewx.drivers.wmr9x8) 12) WS1 (weewx.drivers.ws1)   
>  13) WS23xx  (weewx.drivers.ws23xx) 14) WS28xx 
>  (weewx.drivers.ws28xx)*
>
> (I named my instances *weewx-sdr*, *weewx-interceptor* and the 3rd 
> instance for the local usb stations i just wanted to leave named *weewx *so 
> *weewx.conf*.)
>
> Regarding python versions, this is the output i get:
> root@raspi-wsdi1b:/# python --version
> Python 2.7.16
> root@raspi-wsdi1b:/# python3 --version
> Python 3.7.3
> root@raspi-wsdi1b:/# ps aux | grep weewx
> root   696  8.5  3.6  72104 34164 ?Sl   Feb27 287:07 python 
> /usr/share/weewx/weewxd --daemon --log-label weewx-weewx-sdr 
> --pidfile=/var/run/weewx-weewx-sdr.pid /etc/weewx/weewx-sdr.conf
> root  7766  9.5  3.6  62912 34240 ?Sl   11:05   2:26 python 
> /usr/share/weewx/weewxd --daemon --log-label weewx-weewx-interceptor 
> --pidfile=/var/run/weewx-weewx-interceptor.pid 
> /etc/weewx/weewx-interceptor.conf
> root  8088  0.0  0.0   7360   524 pts/6S+   11:30   0:00 grep weewx
>
> Shouldn't there be python2 or python3 before the weewx path? Or does this 
> mean it's running on python 1?
> gjr80 schrieb am Sonntag, 27. Februar 2022 um 10:30:19 UTC+1:
>
>> Regards the WH23xx driver, have you actually installed the WH23xx driver? 
>> Is the file wh23xx.py in the /home/weewx/user directory? If not you need 
>> to install the driver, if the file exists then something else is amiss. I 
>> note the wh23xx driver has not yet been ported to python 3, if the driver 
>> is installed what version of python are you running WeeWX under?
>>
>> Gary
>>
>> On Sunday, 27 February 2022 at 17:18:39 UTC+10 f4n...@gmail.com wrote:
>>
>>> Just to clarify what i'm trying to do:
>>>
>>> Reading out a WH65 -> 2 weewx instances (SDR, Interceptor)* -> this 
>>> works so far 
>>> Reading out a WH2310 -> 3rd weewx instance (wh23xx driver) -> doesn't 
>>> show up in driver menu if i do wee_config -reconfigure weewx-3.conf
>>>
>>> Hope this is possible without using multiple devices. Do i have to run 
>>> the 3rd weewx instance in docker or which ways to achieve this are possible?
>>>
>>> * [SDR for redundancy because of possible network downtimes with the 
>>> Interceptor solution when the wifi/router is down, loss of power or 
>>> rebooting]
>>>
>>> f4n...@gmail.com schrieb am Samstag, 26. Februar 2022 um 17:55:42 UTC+1:
>>>
 But could it work with weewx-multi? 

 tke...@gmail.com schrieb am Samstag, 26. Februar 2022 um 17:04:56 
 UTC+1:

> Unfortunately, WeeWX can only use one driver at a time. The price we 
> pay for avoiding a complex, asynchronous engine.
>
> On Sat, Feb 26, 2022 at 6:32 AM f4n...@gmail.com  
> wrote:
>
>> Is anyone using the wh23xx driver (
>> https://github.com/matthewwall/weewx-wh23xx) on weewx 4.6.2? I can't 
>> choose the driver after installation. Or is only one user driver per 
>> installation possible?
>>
>> Thanks for any help or idea
>>
>> -- 
>> 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 
>> 

[weewx-user] Re: how to delete '#FTP.last' file

[vince]

escape the # sign with a backslash

cd into the directory then 
 rm -i ./\#FTP.last

The -i will prompt you juust in case you typo it and would otherwise do 
something unexpected/bad.

Tests ok on a pi here.

On Wednesday, March 2, 2022 at 1:27:16 PM UTC-8 n8a...@gmail.com wrote:

> Need to delete my #FTP.last file but I cannot get RM or UNLINK commands to 
> do the job.  I get "missing operand" for both commands.  The file name has 
> a  '   (single quote) in front and at the end of the name.  ??  
>

-- 
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/880d8605-48d5-4b13-93f1-555f8e803749n%40googlegroups.com.

[weewx-user] Re: Belchertown Radar

[bchap...@gmail.com]

I don't have aeris_map = 1

I will give this a try.

Thanks!

On Wednesday, March 2, 2022 at 6:22:16 PM UTC-5 bchap...@gmail.com wrote:

> radar_html = ""
>
> On Sunday, February 27, 2022 at 6:56:04 AM UTC-5 DaveStLou wrote:
>
>> What do you have under [Extras] for radar_html = ""?
>>
>> On Saturday, February 26, 2022 at 9:29:20 AM UTC-6 kk44...@gmail.com 
>> wrote:
>>
>>> You can create an index_radar.inc file to include whatever you want 
>>> instead of the radar image. Or you can set radar_html in skin.conf. 
>>>
>>> bchap...@gmail.com schrieb am Samstag, 26. Februar 2022 um 15:36:46 
>>> UTC+1:
>>>
 from everything I have read, it should be off by defaultI haven't 
 turned it on, however it is on.  I want to display on a browser that 
 doesn't support WebGL.


 On Saturday, February 26, 2022 at 8:31:24 AM UTC-5 bchap...@gmail.com 
 wrote:

> How do I turn off the radar display in belchertown? 



-- 
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/283893c0-4db8-4eeb-88f6-98f02e743c0cn%40googlegroups.com.

[weewx-user] Re: Belchertown Radar

[bchap...@gmail.com]

radar_html = ""

On Sunday, February 27, 2022 at 6:56:04 AM UTC-5 DaveStLou wrote:

> What do you have under [Extras] for radar_html = ""?
>
> On Saturday, February 26, 2022 at 9:29:20 AM UTC-6 kk44...@gmail.com 
> wrote:
>
>> You can create an index_radar.inc file to include whatever you want 
>> instead of the radar image. Or you can set radar_html in skin.conf. 
>>
>> bchap...@gmail.com schrieb am Samstag, 26. Februar 2022 um 15:36:46 
>> UTC+1:
>>
>>> from everything I have read, it should be off by defaultI haven't 
>>> turned it on, however it is on.  I want to display on a browser that 
>>> doesn't support WebGL.
>>>
>>>
>>> On Saturday, February 26, 2022 at 8:31:24 AM UTC-5 bchap...@gmail.com 
>>> wrote:
>>>
 How do I turn off the radar display in belchertown? 
>>>
>>>

-- 
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/2a5b0365-7b3c-4024-a589-f722a399ec18n%40googlegroups.com.

Re: [weewx-user] how to delete '#FTP.last' file

[cric...@pobox.com]

Even using wildcards fails sometimes.  Here's something I wrote years ago.  
It's meant for tweaking
when you run across a nasty file or directory name, so it won't solve your 
problem without a little work.
The foreach loop at the bottom is to print out non-printable characters are 
their ordinal value, which
is invaluable when you can't figure out what's going on.  The trick is not 
trying to handle the names
in a shell at all.  Even perl can fail in this regard using rename and 
unlink.  I may have something to
do with invoking a shell anyway when there are shell variables in the name, 
but that's what the added
backslashes are supposed to prevent.

Chris

#!/usr/bin/perl -w

# adjust as necessary.  This was written to delete a dir that included a 
0xA (\n)
# and square brackets in the actual name, so it was really tough to handle 
from the shell.

opendir(DIR, '.');

while(defined($dir_ent=readdir(DIR))) {
   #next if ( $dir_ent !~ /GetSubrDir/ );

   print " \$dir_ent [$dir_ent]\n";

   $dir_ent =~ s/([\[])/\\$1/g; # '\' protect the brackets so they aren't 
handled as special shell things
   $dir_ent =~ s/([\]])/\\$1/g;

   print " \$dir_ent [$dir_ent]\n";

#   rename( $dir_ent, 'bad_dir' ) or print "failed to rename: $!\n";

   @chars = split('',$dir_ent);  # the split is on a pair of single quotes 
with no space; you get a list of individual characters

   foreach $char(@chars) {
  $ord=ord($char);
  #print " \$ord [$ord], \$char [$char]\n";
  }
   }


On Wednesday, March 2, 2022 at 2:36:41 PM UTC-7 tke...@gmail.com wrote:

> What I use to delete hard to handle names is either a wild card, or the 
> Emacs "directory" mode.
>
> Try something like
>
> *rm *FTP**
>
> Adjust as necessary. Make sure you do an "ls *FTP*" first, so you know 
> what you're targeting!
>
>
> On Wed, Mar 2, 2022 at 1:27 PM Eric Gammeter  wrote:
>
>> Need to delete my #FTP.last file but I cannot get RM or UNLINK commands 
>> to do the job.  I get "missing operand" for both commands.  The file name 
>> has a  '   (single quote) in front and at the end of the name.  ??  
>>
>> -- 
>> 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/d5c3b71b-32e7-44c7-9961-bcf520731aden%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/b747bd9b-188e-4f8a-a8ce-56d2c58f85fbn%40googlegroups.com.

Re: [weewx-user] how to delete '#FTP.last' file

[Tom Keffer]

What I use to delete hard to handle names is either a wild card, or the
Emacs "directory" mode.

Try something like

*rm *FTP**

Adjust as necessary. Make sure you do an "ls *FTP*" first, so you know what
you're targeting!


On Wed, Mar 2, 2022 at 1:27 PM Eric Gammeter  wrote:

> Need to delete my #FTP.last file but I cannot get RM or UNLINK commands to
> do the job.  I get "missing operand" for both commands.  The file name has
> a  '   (single quote) in front and at the end of the name.  ??
>
> --
> 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/d5c3b71b-32e7-44c7-9961-bcf520731aden%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/CAPq0zEAc8aLEE1dLoLdgfF3CNAK19bk3TzaVy3aQzUEnNAH3GQ%40mail.gmail.com.

[weewx-user] how to delete '#FTP.last' file

[Eric Gammeter]

Need to delete my #FTP.last file but I cannot get RM or UNLINK commands to 
do the job.  I get "missing operand" for both commands.  The file name has 
a  '   (single quote) in front and at the end of the name.  ??  

-- 
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/d5c3b71b-32e7-44c7-9961-bcf520731aden%40googlegroups.com.

[weewx-user] Re: Weather34

[Steeple Ian]

w34realtime.txt which is your live data is updating correctly. I suspect 
you do not have the correct path set in the settings page: -

Assuming that you have set default home page for weewx to your webserver 
ROOT, I believe the path should be /var/www/html/weather34/serverdata

Ian

On Wednesday, March 2, 2022 at 7:36:20 PM UTC matthieu89...@gmail.com wrote:

> With weather 34 : www.meteo-champignyonne.fr/weather34
>
> Le mercredi 2 mars 2022 à 20:35:52 UTC+1, Matthieu Devigne a écrit :
>
>> Hi,
>>
>> Yes, weewx is running.
>>
>> My URL : www.meteo-champignyonne.fr
>>
>> Le mercredi 2 mars 2022 à 12:19:33 UTC+1, steep...@gmail.com a écrit :
>>
>>> Also make sure that WeeWX is actually running after you issued the 
>>> restart command.
>>>
>>> On Tuesday, March 1, 2022 at 9:53:40 PM UTC Steeple Ian wrote:
>>>
 Can you let me have your URL please, I need to check your realtime 
 data. The situation in your screen shot indicates that the template is not 
 getting live data from WeeWX.

 On Tuesday, March 1, 2022 at 7:28:01 PM UTC matthieu89...@gmail.com 
 wrote:

> Yes, I will watch for the file service.txt.
>
> For weewx.conf I add [Services]] section in the [Engine] stanza. : ,
> *user.w34_db_backup.W34_DB_Backup*
> And at the end :
> [W34_DB_Backup] * # database path(s) seperated by , rename this/these 
> database(s) to match your own databases = 
> /home/weewx/archive/weewx.sdb,/home/weewx/archive/another.sdb # backup 
> path(s) comma seperated backups = 
> [your_backup_path]/weewx_backup.sdb,[your_backup_path]/home/pi/another_backup.sdb
>  
> # set the daily time to backup comma seperated for multiple databases # 
> the 
> time must be set an to archive time so it runs immediately after the 
> archive interval processes are complete backup_times = 00:00,00:00*
>
>
> Yes, sorry but the data for the pression, temperature, and windy for 
> weather34 are not correct.
> Is not the real values
>
> What is the problem ?
> Le lundi 28 février 2022 à 23:02:26 UTC+1, steep...@gmail.com a 
> écrit :
>
>> I am glad the template is now running for you.
>>
>> Regarding the two errors: -
>>
>> 1. Metar, it looks as though you did not add your X-API-Key or Metar 
>> airport code when you generated your services.txt. Did you follow the 
>> instructions to obtain a key and find your nearest airport?
>> The three relevant lines in the web services section of weewx.conf 
>> should look something like this (ABCD represents the airport code and 
>> 123456789 represents the API Key: -
>>   me_url = https://api.checkwx.com/metar/ABCD/decoded
>>   me_header = X-API-Key:123456789
>>   me_interval = 3600
>>
>> 2. The file should already be in place, all you need to do is edit 
>> weewx.conf and restart as in the instructions. I have updated the 
>> install 
>> instructions to make this clearer>
>>
>> Ian
>>
>>
>>
>> On Monday, February 28, 2022 at 5:25:50 PM UTC 
>> matthieu89...@gmail.com wrote:
>>
>>> Thanks !
>>> Weather34 is running with weewx and debian ! :)
>>>
>>> But, I have a message error :
>>>
>>> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Failed 
>>> getting web service data. URL: 
>>> https://api.checkwx.com/metar//decoded Header: {'X-API-Key': ''}, 
>>> Error: HTTP Error 404: Not Found
>>> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Error 
>>> Invalid Webservice Data: None, {'User-Agent': 'Mozilla/5.0 (Macintosh; 
>>> U; 
>>> Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) 
>>> Chrome/51.0.2704.103 Safari/534.3'}
>>>
>>> And, I don't find a w34_db_backup.py file for put in 
>>> /home/weewx/bin/user 
>>> Where is he ?
>>>
>>>
>>>
>>>  
>>>
>>> Le dimanche 27 février 2022 à 23:31:13 UTC+1, steep...@gmail.com a 
>>> écrit :
>>>
 Vince is correct, it is looking for services.txt one level up from 
 the install folder.

 Assuming you downloaded the zip file from the repository into your 
 /home/pi folder and un zipped it, the install folder is 
 weewx-Weather34-main. The services.txt file should also be in your 
 /home/pi 
 folder.

 Therefore you should: -

 cd weewx-Weather34-main
 sudo python3 ./w34_installer.py

 On Sunday, February 27, 2022 at 8:44:58 PM UTC vince wrote:

> On Sunday, February 27, 2022 at 12:02:05 PM UTC-8 
> matthieu89...@gmail.com wrote:
>
>> When i use sudo python3 /home/pi/weewx-Weather34/w34_installer.py 
>
>
>> *Cannot find ../services.txt file INSTALL ABORTED*
>>
>
>> Whereas my file 

Re: [weewx-user] no rain data available

[jschoonh]

I do understand and I'm happy that there is support. Hope to "speak" to you 
soon
Op woensdag 2 maart 2022 om 22:40:01 UTC+3 schreef tke...@gmail.com:

> I think we're going to have to wait for Matthew to return. Sorry I 
> couldn't be of more help!
>
> On Wed, Mar 2, 2022 at 11:14 AM jschoonh  wrote:
>
>> hey tom,
>> I quickly made a kind of skin. The first line is from the tmpl file. The 
>> 2 lines below the result before water entered the rain gauge and after. The 
>> time is there. According to the console, about 1.5 mm of rain has entered 
>> the rain gauge. all "rain.sum" variants have not changed the 
>> "$hour,rain.sum" remains empty even after 10 minutes those values will not 
>> changed.
>> Below terminal log, The rainTotal value from 68.116 has 
>> changed to 68,272 = 0.155 a values I don't quite understand could be a 
>> decimal error?. "rain" remains "none" "rainrate" = 0.155.
>> At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0', 
>> 'rainTotal': '94.0688' and the time 2 minutes back?
>> Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'
>>
>> the last dabase record is the same time as "rec" loop 2022-03-02 21:18:21 
>> no change in the "rain = null"  rainrate = 0.0
>>
>>
>> -
>> neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw , 
>> $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw
>>
>> tijd , 21:08 , 02.03.2022
>> neerslag ,  , 21.2379886 , 21.2379886 , 
>> 21.2379886 , 496.762006
>>
>> tijd , 21:18 , 02.03.2022
>> neerslag ,  , 21.2379886 , 21.2379886 , 
>> 21.2379886 , 496.762006
>>
>>
>> 
>>
>> REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter': 
>> '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer': 
>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>> '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex': 
>> '16.542223', 'humidex': '18.189898859284828', 'inDewpoint': 
>> '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval': 
>> '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp': 
>> '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate': 
>> '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill': 
>> '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir': 
>> 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
>> LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter': 
>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>> '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>> 'windSpeed': '0.0'
>> LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter': 
>> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>> '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>> 'windSpeed': '0.0'
>> LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter': 
>> '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer': 
>> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
>> '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
>> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
>> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
>> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
>> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
>> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
>> '67.5', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
>> 'windSpeed': '2.8803'
>> LOOP:   2022-03-02 21:16:43 +03 (1646245003) 'altimeter': 
>> '1001.8299536233475', 'appTemp': 

Re: [weewx-user] no rain data available

[Tom Keffer]

I think we're going to have to wait for Matthew to return. Sorry I couldn't
be of more help!

On Wed, Mar 2, 2022 at 11:14 AM jschoonh  wrote:

> hey tom,
> I quickly made a kind of skin. The first line is from the tmpl file. The 2
> lines below the result before water entered the rain gauge and after. The
> time is there. According to the console, about 1.5 mm of rain has entered
> the rain gauge. all "rain.sum" variants have not changed the
> "$hour,rain.sum" remains empty even after 10 minutes those values will not
> changed.
> Below terminal log, The rainTotal value from 68.116 has
> changed to 68,272 = 0.155 a values I don't quite understand could be a
> decimal error?. "rain" remains "none" "rainrate" = 0.155.
> At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0',
> 'rainTotal': '94.0688' and the time 2 minutes back?
> Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'
>
> the last dabase record is the same time as "rec" loop 2022-03-02 21:18:21
> no change in the "rain = null"  rainrate = 0.0
>
>
> -
> neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw ,
> $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw
>
> tijd , 21:08 , 02.03.2022
> neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886
> , 496.762006
>
> tijd , 21:18 , 02.03.2022
> neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886
> , 496.762006
>
>
> 
>
> REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter':
> '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer':
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
> '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex':
> '16.542223', 'humidex': '18.189898859284828', 'inDewpoint':
> '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval':
> '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp':
> '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate':
> '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill':
> '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir':
> 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
> LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter':
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer':
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
> '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2',
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal':
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir':
> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None',
> 'windSpeed': '0.0'
> LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter':
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer':
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
> '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2',
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal':
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir':
> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None',
> 'windSpeed': '0.0'
> LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter':
> '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer':
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
> '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2',
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal':
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir':
> '67.5', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None',
> 'windSpeed': '2.8803'
> LOOP:   2022-03-02 21:16:43 +03 (1646245003) 'altimeter':
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer':
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime':
> '1646245003', 'dewpoint': '9.38', 'ET': 'None', 'heatindex':
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint':
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7',
> 

[weewx-user] Re: Weather34

[Matthieu Devigne]

With weather 34 : www.meteo-champignyonne.fr/weather34

Le mercredi 2 mars 2022 à 20:35:52 UTC+1, Matthieu Devigne a écrit :

> Hi,
>
> Yes, weewx is running.
>
> My URL : www.meteo-champignyonne.fr
>
> Le mercredi 2 mars 2022 à 12:19:33 UTC+1, steep...@gmail.com a écrit :
>
>> Also make sure that WeeWX is actually running after you issued the 
>> restart command.
>>
>> On Tuesday, March 1, 2022 at 9:53:40 PM UTC Steeple Ian wrote:
>>
>>> Can you let me have your URL please, I need to check your realtime data. 
>>> The situation in your screen shot indicates that the template is not 
>>> getting live data from WeeWX.
>>>
>>> On Tuesday, March 1, 2022 at 7:28:01 PM UTC matthieu89...@gmail.com 
>>> wrote:
>>>
 Yes, I will watch for the file service.txt.

 For weewx.conf I add [Services]] section in the [Engine] stanza. : ,
 *user.w34_db_backup.W34_DB_Backup*
 And at the end :
 [W34_DB_Backup] * # database path(s) seperated by , rename this/these 
 database(s) to match your own databases = 
 /home/weewx/archive/weewx.sdb,/home/weewx/archive/another.sdb # backup 
 path(s) comma seperated backups = 
 [your_backup_path]/weewx_backup.sdb,[your_backup_path]/home/pi/another_backup.sdb
  
 # set the daily time to backup comma seperated for multiple databases # 
 the 
 time must be set an to archive time so it runs immediately after the 
 archive interval processes are complete backup_times = 00:00,00:00*


 Yes, sorry but the data for the pression, temperature, and windy for 
 weather34 are not correct.
 Is not the real values

 What is the problem ?
 Le lundi 28 février 2022 à 23:02:26 UTC+1, steep...@gmail.com a écrit :

> I am glad the template is now running for you.
>
> Regarding the two errors: -
>
> 1. Metar, it looks as though you did not add your X-API-Key or Metar 
> airport code when you generated your services.txt. Did you follow the 
> instructions to obtain a key and find your nearest airport?
> The three relevant lines in the web services section of weewx.conf 
> should look something like this (ABCD represents the airport code and 
> 123456789 represents the API Key: -
>   me_url = https://api.checkwx.com/metar/ABCD/decoded
>   me_header = X-API-Key:123456789
>   me_interval = 3600
>
> 2. The file should already be in place, all you need to do is edit 
> weewx.conf and restart as in the instructions. I have updated the install 
> instructions to make this clearer>
>
> Ian
>
>
>
> On Monday, February 28, 2022 at 5:25:50 PM UTC matthieu89...@gmail.com 
> wrote:
>
>> Thanks !
>> Weather34 is running with weewx and debian ! :)
>>
>> But, I have a message error :
>>
>> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Failed 
>> getting web service data. URL: https://api.checkwx.com/metar//decoded 
>> Header: {'X-API-Key': ''}, Error: HTTP Error 404: Not Found
>> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Error 
>> Invalid Webservice Data: None, {'User-Agent': 'Mozilla/5.0 (Macintosh; 
>> U; 
>> Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) 
>> Chrome/51.0.2704.103 Safari/534.3'}
>>
>> And, I don't find a w34_db_backup.py file for put in 
>> /home/weewx/bin/user 
>> Where is he ?
>>
>>
>>
>>  
>>
>> Le dimanche 27 février 2022 à 23:31:13 UTC+1, steep...@gmail.com a 
>> écrit :
>>
>>> Vince is correct, it is looking for services.txt one level up from 
>>> the install folder.
>>>
>>> Assuming you downloaded the zip file from the repository into your 
>>> /home/pi folder and un zipped it, the install folder is 
>>> weewx-Weather34-main. The services.txt file should also be in your 
>>> /home/pi 
>>> folder.
>>>
>>> Therefore you should: -
>>>
>>> cd weewx-Weather34-main
>>> sudo python3 ./w34_installer.py
>>>
>>> On Sunday, February 27, 2022 at 8:44:58 PM UTC vince wrote:
>>>
 On Sunday, February 27, 2022 at 12:02:05 PM UTC-8 
 matthieu89...@gmail.com wrote:

> When i use sudo python3 /home/pi/weewx-Weather34/w34_installer.py 


> *Cannot find ../services.txt file INSTALL ABORTED*
>

> Whereas my file service.txt is in /home/pi
>
>
 It is trying to find services.txt using a relative path one level 
 up from the directory you are running the command in.

 Try:

- cd /home/pi/weewx-Weather34
- sudo python3 /home/pi/weewx-Weather34/w34_installer.py




-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails 

[weewx-user] Re: Weather34

[Matthieu Devigne]

Hi,

Yes, weewx is running.

My URL : www.meteo-champignyonne.fr

Le mercredi 2 mars 2022 à 12:19:33 UTC+1, steep...@gmail.com a écrit :

> Also make sure that WeeWX is actually running after you issued the restart 
> command.
>
> On Tuesday, March 1, 2022 at 9:53:40 PM UTC Steeple Ian wrote:
>
>> Can you let me have your URL please, I need to check your realtime data. 
>> The situation in your screen shot indicates that the template is not 
>> getting live data from WeeWX.
>>
>> On Tuesday, March 1, 2022 at 7:28:01 PM UTC matthieu89...@gmail.com 
>> wrote:
>>
>>> Yes, I will watch for the file service.txt.
>>>
>>> For weewx.conf I add [Services]] section in the [Engine] stanza. : ,
>>> *user.w34_db_backup.W34_DB_Backup*
>>> And at the end :
>>> [W34_DB_Backup] * # database path(s) seperated by , rename this/these 
>>> database(s) to match your own databases = 
>>> /home/weewx/archive/weewx.sdb,/home/weewx/archive/another.sdb # backup 
>>> path(s) comma seperated backups = 
>>> [your_backup_path]/weewx_backup.sdb,[your_backup_path]/home/pi/another_backup.sdb
>>>  
>>> # set the daily time to backup comma seperated for multiple databases # the 
>>> time must be set an to archive time so it runs immediately after the 
>>> archive interval processes are complete backup_times = 00:00,00:00*
>>>
>>>
>>> Yes, sorry but the data for the pression, temperature, and windy for 
>>> weather34 are not correct.
>>> Is not the real values
>>>
>>> What is the problem ?
>>> Le lundi 28 février 2022 à 23:02:26 UTC+1, steep...@gmail.com a écrit :
>>>
 I am glad the template is now running for you.

 Regarding the two errors: -

 1. Metar, it looks as though you did not add your X-API-Key or Metar 
 airport code when you generated your services.txt. Did you follow the 
 instructions to obtain a key and find your nearest airport?
 The three relevant lines in the web services section of weewx.conf 
 should look something like this (ABCD represents the airport code and 
 123456789 represents the API Key: -
   me_url = https://api.checkwx.com/metar/ABCD/decoded
   me_header = X-API-Key:123456789
   me_interval = 3600

 2. The file should already be in place, all you need to do is edit 
 weewx.conf and restart as in the instructions. I have updated the install 
 instructions to make this clearer>

 Ian



 On Monday, February 28, 2022 at 5:25:50 PM UTC matthieu89...@gmail.com 
 wrote:

> Thanks !
> Weather34 is running with weewx and debian ! :)
>
> But, I have a message error :
>
> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Failed 
> getting web service data. URL: https://api.checkwx.com/metar//decoded 
> Header: {'X-API-Key': ''}, Error: HTTP Error 404: Not Found
> Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Error 
> Invalid Webservice Data: None, {'User-Agent': 'Mozilla/5.0 (Macintosh; U; 
> Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) 
> Chrome/51.0.2704.103 Safari/534.3'}
>
> And, I don't find a w34_db_backup.py file for put in 
> /home/weewx/bin/user 
> Where is he ?
>
>
>
>  
>
> Le dimanche 27 février 2022 à 23:31:13 UTC+1, steep...@gmail.com a 
> écrit :
>
>> Vince is correct, it is looking for services.txt one level up from 
>> the install folder.
>>
>> Assuming you downloaded the zip file from the repository into your 
>> /home/pi folder and un zipped it, the install folder is 
>> weewx-Weather34-main. The services.txt file should also be in your 
>> /home/pi 
>> folder.
>>
>> Therefore you should: -
>>
>> cd weewx-Weather34-main
>> sudo python3 ./w34_installer.py
>>
>> On Sunday, February 27, 2022 at 8:44:58 PM UTC vince wrote:
>>
>>> On Sunday, February 27, 2022 at 12:02:05 PM UTC-8 
>>> matthieu89...@gmail.com wrote:
>>>
 When i use sudo python3 /home/pi/weewx-Weather34/w34_installer.py 
>>>
>>>
 *Cannot find ../services.txt file INSTALL ABORTED*

>>>
 Whereas my file service.txt is in /home/pi


>>> It is trying to find services.txt using a relative path one level up 
>>> from the directory you are running the command in.
>>>
>>> Try:
>>>
>>>- cd /home/pi/weewx-Weather34
>>>- sudo python3 /home/pi/weewx-Weather34/w34_installer.py
>>>
>>>
>>>

-- 
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/72156e52-e6e9-4f99-a718-0d753f834e6fn%40googlegroups.com.

Re: [weewx-user] no rain data available

[jschoonh]

I've only just now noticed that the "rainTotal value from 
68.116 who changed to 68,272" is the values the "la Crosse" 
console declares as Raintotal. Indeed, 682.2 mm of rain has already fallen 
this year.

Op woensdag 2 maart 2022 om 22:14:43 UTC+3 schreef jschoonh:

> hey tom,
> I quickly made a kind of skin. The first line is from the tmpl file. The 2 
> lines below the result before water entered the rain gauge and after. The 
> time is there. According to the console, about 1.5 mm of rain has entered 
> the rain gauge. all "rain.sum" variants have not changed the 
> "$hour,rain.sum" remains empty even after 10 minutes those values will not 
> changed.
> Below terminal log, The rainTotal value from 68.116 has 
> changed to 68,272 = 0.155 a values I don't quite understand could be a 
> decimal error?. "rain" remains "none" "rainrate" = 0.155.
> At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0', 
> 'rainTotal': '94.0688' and the time 2 minutes back?
> Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'
>
> the last dabase record is the same time as "rec" loop 2022-03-02 21:18:21 
> no change in the "rain = null"  rainrate = 0.0
>
>
> -
> neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw , 
> $day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw
>
> tijd , 21:08 , 02.03.2022
> neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886 
> , 496.762006
>
> tijd , 21:18 , 02.03.2022
> neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886 
> , 496.762006
>
>
> 
>
> REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter': 
> '1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer': 
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
> '1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex': 
> '16.542223', 'humidex': '18.189898859284828', 'inDewpoint': 
> '14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval': 
> '5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp': 
> '17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate': 
> '0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill': 
> '17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir': 
> 'None', 'windrun': '0.18002', 'windSpeed': '2.16'
> LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter': 
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
> '1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '0.0'
> LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter': 
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
> '1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
> 'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '0.0'
> LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter': 
> '1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer': 
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
> '1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
> '16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
> '14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
> 'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
> 'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
> '68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
> '67.5', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '2.8803'
> LOOP:   2022-03-02 21:16:43 +03 (1646245003) 'altimeter': 
> '1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
> '1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
> 

Re: [weewx-user] no rain data available

[jschoonh]

hey tom,
I quickly made a kind of skin. The first line is from the tmpl file. The 2 
lines below the result before water entered the rain gauge and after. The 
time is there. According to the console, about 1.5 mm of rain has entered 
the rain gauge. all "rain.sum" variants have not changed the 
"$hour,rain.sum" remains empty even after 10 minutes those values will not 
changed.
Below terminal log, The rainTotal value from 68.116 has changed 
to 68,272 = 0.155 a values I don't quite understand could be a decimal 
error?. "rain" remains "none" "rainrate" = 0.155.
At the time of the "rec" loop I see 'rain': 'None', 'rainRate': '0.0', 
'rainTotal': '94.0688' and the time 2 minutes back?
Next loop 'rain': 'None', 'rainRate': '0.155', 'rainTotal': '68.272'

the last dabase record is the same time as "rec" loop 2022-03-02 21:18:21 
no change in the "rain = null"  rainrate = 0.0

-
neerslag , $hour.rain.sum.raw , $span($day_delta=1).rain.sum.raw , 
$day.rain.sum.raw , $day.rain.sum.raw , $rainyear.rain.sum.raw

tijd , 21:08 , 02.03.2022
neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886 
, 496.762006

tijd , 21:18 , 02.03.2022
neerslag ,  , 21.2379886 , 21.2379886 , 21.2379886 
, 496.762006



REC:2022-03-02 21:13:08 +03 (1646244788) 'altimeter': 
'1001.8299536233475', 'appTemp': '16.656587610543724', 'barometer': 
'1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
'1646244788', 'dewpoint': '9.363369846724652', 'ET': 'None', 'heatindex': 
'16.542223', 'humidex': '18.189898859284828', 'inDewpoint': 
'14.573533344814903', 'inHumidity': '57.0', 'inTemp': '23.6', 'interval': 
'5', 'maxSolarRad': 'None', 'outHumidity': '60', 'outTemp': 
'17.203', 'pressure': '993.2', 'rain': 'None', 'rainRate': 
'0.0', 'rainTotal': '93.9134', 'usUnits': '16', 'windchill': 
'17.203', 'windDir': '67.5', 'windGust': 'None', 'windGustDir': 
'None', 'windrun': '0.18002', 'windSpeed': '2.16'
LOOP:   2022-03-02 21:16:11 +03 (1646244971) 'altimeter': 
'1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
'1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
'1646244971', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
'16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
'14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
'68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
'windSpeed': '0.0'
LOOP:   2022-03-02 21:16:20 +03 (1646244980) 'altimeter': 
'1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
'1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
'1646244980', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
'16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
'14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
'68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
'None', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
'windSpeed': '0.0'
LOOP:   2022-03-02 21:16:32 +03 (1646244992) 'altimeter': 
'1001.8299536233475', 'appTemp': '16.51658761043172', 'barometer': 
'1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
'1646244992', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
'16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
'14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
'68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
'67.5', 'windGust': 'None', 'windGustDir': 'None', 'windrun': 'None', 
'windSpeed': '2.8803'
LOOP:   2022-03-02 21:16:43 +03 (1646245003) 'altimeter': 
'1001.8299536233475', 'appTemp': '17.07658761087972', 'barometer': 
'1001.6522035818567', 'cloudbase': '1027.4395735509206', 'dateTime': 
'1646245003', 'dewpoint': '9.38', 'ET': 'None', 'heatindex': 
'16.545', 'humidex': '18.189898859284824', 'inDewpoint': 
'14.666742553088449', 'inHumidity': '57.0', 'inTemp': '23.7', 
'maxSolarRad': 'None', 'outHumidity': '60.0', 'outTemp': '17.2', 
'pressure': '993.2', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
'68.116999', 'usUnits': '16', 'windchill': '17.2', 'windDir': 
'None', 'windGust': 'None', 

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

I was mistaken, when i use --daemon it crashes - always
The import serial thing, i did that on the cmd line.
I removed StdPrint and --daemon and it works without excess logging 
I am in the process of upgrading to 4.7 now


On Wednesday, March 2, 2022 at 9:52:33 AM UTC-8 tke...@gmail.com wrote:

> I'm glad things are working, but just for my edification, what did we fix? 
> I thought the --daemon flag fixed the problem of LOOP packet data appearing 
> in the log. Why was it necessary to comment out StdPrint?
>
> And, what fixed the problem with the importation of "serial"?
>
> On Wed, Mar 2, 2022 at 9:28 AM Cat22  wrote:
>
>> python3 -c "import serial"
>> that works, return code is 0 (echo $?)
>>
>> On Wednesday, March 2, 2022 at 9:26:20 AM UTC-8 Cat22 wrote:
>>
>>> I made this change and it worked! At least it looks like it worked, I 
>>> need to watch it for awhile to be sure
>>> #report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport, 
>>> user.lowBattery.BatteryAlarm
>>> report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm
>>>
>>> On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote:
>>>
 That's basically what i did. When i add --daemon and restart i see this:
 Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished 
 from the unit file, execution of the command list won't be resumed.
 followed by some weather data then this:
 Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: 
 Initializing weewx version 4.0.0
 Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using 
 Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
 Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform 
 Linux-5.8.11-x86_64-with-glibc2.2.5
 Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale 
 is 'en_US.UTF-8'
 Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file 
 is /var/run/weewx.pid
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using 
 configuration file /usr/local/bin/weewx/weewx.conf
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: 
 Loading station type Vantage (weewx.drivers.vantage)
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received 
 signal TERM (15).
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: 
 Import of driver failed:  ()
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   Traceback (most recent call last):
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in 
 setupStation
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   self.console = loader_function(config_dict, self)
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
 39, in loader
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   return VantageService(engine, config_dict)
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
 1897, in __init__
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   Vantage.__init__(self, **config_dict[DRIVER_NAME])
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
 511, in __init__
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   self.port.openPort()
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
 305, in openPort
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   import serial
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "/usr/lib/python3.8/site-packages/serial/__init__.py", 
 line 14, in 
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
   from serial.serialutil import *
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "", line 991, in 
 _find_and_load
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "", line 975, in 
 _find_and_load_unlocked
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "", line 657, in 
 _load_unlocked
 Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
 File "", line 562, in 
 module_from_spec
 

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

I'm glad things are working, but just for my edification, what did we fix?
I thought the --daemon flag fixed the problem of LOOP packet data appearing
in the log. Why was it necessary to comment out StdPrint?

And, what fixed the problem with the importation of "serial"?

On Wed, Mar 2, 2022 at 9:28 AM Cat22  wrote:

> python3 -c "import serial"
> that works, return code is 0 (echo $?)
>
> On Wednesday, March 2, 2022 at 9:26:20 AM UTC-8 Cat22 wrote:
>
>> I made this change and it worked! At least it looks like it worked, I
>> need to watch it for awhile to be sure
>> #report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport,
>> user.lowBattery.BatteryAlarm
>> report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm
>>
>> On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote:
>>
>>> That's basically what i did. When i add --daemon and restart i see this:
>>> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished
>>> from the unit file, execution of the command list won't be resumed.
>>> followed by some weather data then this:
>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__:
>>> Initializing weewx version 4.0.0
>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using
>>> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform
>>> Linux-5.8.11-x86_64-with-glibc2.2.5
>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale is
>>> 'en_US.UTF-8'
>>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file
>>> is /var/run/weewx.pid
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using
>>> configuration file /usr/local/bin/weewx/weewx.conf
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine:
>>> Loading station type Vantage (weewx.drivers.vantage)
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received
>>> signal TERM (15).
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine:
>>> Import of driver failed:  ()
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     Traceback (most recent call last):
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in
>>> setupStation
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     self.console = loader_function(config_dict, self)
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line
>>> 39, in loader
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     return VantageService(engine, config_dict)
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line
>>> 1897, in __init__
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     Vantage.__init__(self, **config_dict[DRIVER_NAME])
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line
>>> 511, in __init__
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     self.port.openPort()
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line
>>> 305, in openPort
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     import serial
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/lib/python3.8/site-packages/serial/__init__.py", line
>>> 14, in 
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     from serial.serialutil import *
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "", line 991, in _find_and_load
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "", line 975, in
>>> _find_and_load_unlocked
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "", line 657, in _load_unlocked
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "", line 562, in
>>> module_from_spec
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "", line 481, in
>>> _init_module_attrs
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>   File "/usr/local/bin/weewx/bin/weewxd", line 257, in
>>> sigTERMhandler
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>>>     raise Terminate
>>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

python3 -c "import serial"
that works, return code is 0 (echo $?)

On Wednesday, March 2, 2022 at 9:26:20 AM UTC-8 Cat22 wrote:

> I made this change and it worked! At least it looks like it worked, I need 
> to watch it for awhile to be sure
> #report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport, 
> user.lowBattery.BatteryAlarm
> report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm
>
> On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote:
>
>> That's basically what i did. When i add --daemon and restart i see this:
>> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished 
>> from the unit file, execution of the command list won't be resumed.
>> followed by some weather data then this:
>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: 
>> Initializing weewx version 4.0.0
>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using 
>> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform 
>> Linux-5.8.11-x86_64-with-glibc2.2.5
>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale is 
>> 'en_US.UTF-8'
>> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file 
>> is /var/run/weewx.pid
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using 
>> configuration file /usr/local/bin/weewx/weewx.conf
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: 
>> Loading station type Vantage (weewx.drivers.vantage)
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received 
>> signal TERM (15).
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: 
>> Import of driver failed:  ()
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     Traceback (most recent call last):
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in 
>> setupStation
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     self.console = loader_function(config_dict, self)
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
>> 39, in loader
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     return VantageService(engine, config_dict)
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
>> 1897, in __init__
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
>> 511, in __init__
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     self.port.openPort()
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
>> 305, in openPort
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     import serial
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/lib/python3.8/site-packages/serial/__init__.py", line 
>> 14, in 
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     from serial.serialutil import *
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "", line 991, in _find_and_load
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "", line 975, in 
>> _find_and_load_unlocked
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "", line 657, in _load_unlocked
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "", line 562, in 
>> module_from_spec
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "", line 481, in 
>> _init_module_attrs
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>   File "/usr/local/bin/weewx/bin/weewxd", line 257, in 
>> sigTERMhandler
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     raise Terminate
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:   
>>     Terminate
>> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL __main__: Unable 
>> to load driver:
>> On Wednesday, March 2, 2022 at 8:47:31 AM UTC-8 tke...@gmail.com wrote:
>>
>>> "weewx crashed" doesn't give us very much information. 
>>>
>>> There are other command line flags that are normally used in 

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

I made this change and it worked! At least it looks like it worked, I need 
to watch it for awhile to be sure
#report_services = *weewx.engine.StdPrint*, weewx.engine.StdReport, 
user.lowBattery.BatteryAlarm
report_services = weewx.engine.StdReport, user.lowBattery.BatteryAlarm

On Wednesday, March 2, 2022 at 9:04:04 AM UTC-8 Cat22 wrote:

> That's basically what i did. When i add --daemon and restart i see this:
> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished 
> from the unit file, execution of the command list won't be resumed.
> followed by some weather data then this:
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: 
> Initializing weewx version 4.0.0
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using 
> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform 
> Linux-5.8.11-x86_64-with-glibc2.2.5
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale is 
> 'en_US.UTF-8'
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file is 
> /var/run/weewx.pid
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using 
> configuration file /usr/local/bin/weewx/weewx.conf
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: Loading 
> station type Vantage (weewx.drivers.vantage)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received 
> signal TERM (15).
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: Import 
> of driver failed:  ()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   Traceback (most recent call last):
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in 
> setupStation
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   self.console = loader_function(config_dict, self)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 39, 
> in loader
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   return VantageService(engine, config_dict)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
> 1897, in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 511, 
> in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   self.port.openPort()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 305, 
> in openPort
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   import serial
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/lib/python3.8/site-packages/serial/__init__.py", line 
> 14, in 
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   from serial.serialutil import *
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "", line 991, in _find_and_load
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "", line 975, in 
> _find_and_load_unlocked
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "", line 657, in _load_unlocked
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "", line 562, in module_from_spec
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "", line 481, in 
> _init_module_attrs
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
> File "/usr/local/bin/weewx/bin/weewxd", line 257, in sigTERMhandler
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   raise Terminate
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
>   Terminate
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL __main__: Unable 
> to load driver:
> On Wednesday, March 2, 2022 at 8:47:31 AM UTC-8 tke...@gmail.com wrote:
>
>> "weewx crashed" doesn't give us very much information. 
>>
>> There are other command line flags that are normally used in a systemd 
>> file.
>>
>> Why not use the weewx.service that comes with WeeWX? It's in the 
>> util/systemd directory. Modify as required.
>>
>> On Wed, Mar 2, 2022 at 8:30 AM Cat22  wrote:
>>
>>> Seems like the --daemon option 

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

>
> That's basically what i did.
>

You didn't have the --pidfile flag before, but now it seems that you've
added it. That's good, but you still have "Type=simple", while what you
want is "Type=forking". Really, you should just start with the
weewx.service file that came with your copy of WeeWX.

Speaking of which, I'm just now realizing that log_success was not honored
by v4.0.0. That came in with V4.5.0. So, you should upgrade. But I don't
think this is related to your problem below.


> When i add --daemon and restart i see this:
> Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished
> from the unit file, execution of the command list won't be resumed.
> followed by some weather data then this:
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__:
> Initializing weewx version 4.0.0
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using
> Python 3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform
> Linux-5.8.11-x86_64-with-glibc2.2.5
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale is
> 'en_US.UTF-8'
> Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file is
> /var/run/weewx.pid
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using
> configuration file /usr/local/bin/weewx/weewx.conf
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: Loading
> station type Vantage (weewx.drivers.vantage)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received
> signal TERM (15).
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: Import
> of driver failed:  ()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   Traceback (most recent call last):
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in
> setupStation
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   self.console = loader_function(config_dict, self)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 39,
> in loader
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   return VantageService(engine, config_dict)
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line
> 1897, in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 511,
> in __init__
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   self.port.openPort()
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 305,
> in openPort
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   import serial
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/lib/python3.8/site-packages/serial/__init__.py", line
> 14, in 
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   from serial.serialutil import *
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "", line 991, in _find_and_load
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "", line 975, in
> _find_and_load_unlocked
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "", line 657, in _load_unlocked
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "", line 562, in module_from_spec
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "", line 481, in
> _init_module_attrs
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
> File "/usr/local/bin/weewx/bin/weewxd", line 257, in sigTERMhandler
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   raise Terminate
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine:
>   Terminate
> Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL __main__: Unable
> to load driver:


This may be a bad install of the python library "serial".

Try this:

*python3 -c "import serial" *


See if that crashes. Also, upgrade!

-tk

-- 
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] weewx writing too much to systemd journal

[Cat22]

That's basically what i did. When i add --daemon and restart i see this:
Mar 02 08:53:52 pc2 systemd[1]: weewx.service: Current command vanished 
from the unit file, execution of the command list won't be resumed.
followed by some weather data then this:
Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Initializing 
weewx version 4.0.0
Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Using Python 
3.8.8 (default, Feb 19 2021, 16:53:21) [GCC]
Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Platform 
Linux-5.8.11-x86_64-with-glibc2.2.5
Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: Locale is 
'en_US.UTF-8'
Mar 02 08:54:10 pc2 python[16601]: weewx[16601] INFO __main__: PID file is 
/var/run/weewx.pid
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Using 
configuration file /usr/local/bin/weewx/weewx.conf
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO weewx.engine: Loading 
station type Vantage (weewx.drivers.vantage)
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] INFO __main__: Received 
signal TERM (15).
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] ERROR weewx.engine: Import 
of driver failed:  ()
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  Traceback (most recent call last):
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewx/engine.py", line 103, in 
setupStation
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  self.console = loader_function(config_dict, self)
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 39, 
in loader
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  return VantageService(engine, config_dict)
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 
1897, in __init__
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  Vantage.__init__(self, **config_dict[DRIVER_NAME])
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 511, 
in __init__
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  self.port.openPort()
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewx/drivers/vantage.py", line 305, 
in openPort
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  import serial
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/lib/python3.8/site-packages/serial/__init__.py", line 
14, in 
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  from serial.serialutil import *
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "", line 991, in _find_and_load
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "", line 975, in 
_find_and_load_unlocked
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "", line 657, in _load_unlocked
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "", line 562, in module_from_spec
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "", line 481, in 
_init_module_attrs
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
File "/usr/local/bin/weewx/bin/weewxd", line 257, in sigTERMhandler
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  raise Terminate
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL weewx.engine: 
  Terminate
Mar 02 08:54:10 pc2 python[16604]: weewx[16604] CRITICAL __main__: Unable 
to load driver:
On Wednesday, March 2, 2022 at 8:47:31 AM UTC-8 tke...@gmail.com wrote:

> "weewx crashed" doesn't give us very much information. 
>
> There are other command line flags that are normally used in a systemd 
> file.
>
> Why not use the weewx.service that comes with WeeWX? It's in the 
> util/systemd directory. Modify as required.
>
> On Wed, Mar 2, 2022 at 8:30 AM Cat22  wrote:
>
>> Seems like the --daemon option fixed things
>> my service file looks like this (in part()
>> [Service] 
>>  
>>  
>> 
>>  
>> ExecStart=/usr/local/bin/weewx/bin/weewxd 
>> /usr/local/bin/weewx/weewx.conf --daemon 
>>  
>> 

Re: [weewx-user] no rain data available

[Tom Keffer]

>
> Your workaround to calculate the rain doesn't work. Because there is no
> data to calculate anything. none of the "rain.sum" ($day , $week etc. shows
> new data. The rain data $week, $month, etc, comes from stored data and not
> from new data.
>

How about some more information besides "doesn't work"? What does it do?
What's in the log? If you run it directly from the command line, what does
it show for rain?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBv8GrgtFnO1%2B2hbb%2BL1_e102GYdnKG47pZg9pv_Q_ppQ%40mail.gmail.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

"weewx crashed" doesn't give us very much information.

There are other command line flags that are normally used in a systemd file.

Why not use the weewx.service that comes with WeeWX? It's in the
util/systemd directory. Modify as required.

On Wed, Mar 2, 2022 at 8:30 AM Cat22  wrote:

> Seems like the --daemon option fixed things
> my service file looks like this (in part()
> [Service]
>
>
> ExecStart=/usr/local/bin/weewx/bin/weewxd /usr/local/bin/weewx/weewx.conf
> --daemon
>
>
> ExecReload=/usr/bin/killall -TERM $MAINPID
>
>
> Type=simple
>
>
> Restart=on-failure
>
>
> RestartSec=100s
>
> Good grief this google thing here is hard to use!
>
> ok, i just checked before posting and weewx crashed  -  it never does
> tthat but the --daemon opt was the only thing that changed
>
> On Wednesday, March 2, 2022 at 8:23:51 AM UTC-8 Cat22 wrote:
>
>> I thought systemd asked services not to demonize as systemd does that for
>> them. Ami right about this?
>> However, I will try it.
>>
>> On Wednesday, March 2, 2022 at 8:20:32 AM UTC-8 Cat22 wrote:
>>
>>> weewx version 4.0.0
>>> I am having trouble posting here, my posts seem to just disappear.
>>> Hopefully this one will make it.
>>> I found log_success in 2 places in weewx.conf I set that to False also,
>>> but it doesnt make a bit of differrence
>>>
>>> Here is a sample:
>>> Mar 02 08:18:20 pc2 weewxd[14910]: LOOP:   2022-03-02 08:18:19 PST
>>> (1646237899) altimeter etc etc, the line is very long
>>> On Wednesday, March 2, 2022 at 8:15:48 AM UTC-8 tke...@gmail.com wrote:
>>>
 Thanks, i just tried that and restarted wewx but it's still printing
> that loop data.


 I'm not sure what you mean by "printing that loop data." Are we talking
 about the log? Or, printing to a console through standard output?

 If the former, the Vantage driver logs no data in the system log ---
 only control information. StdArchive does log successful and unsuccessful
 insertions into the database, but these should be controlled by log_success
 and log_failure, respectively, at least on modern versions of WeeWX (what
 version are you using?).

 If the latter (printing to the console), then you shouldn't see this if
 you are running weewxd as a daemon.

 Perhaps an excerpt of the log so we can see what you're concerned about?

 On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer  wrote:

> Just set option log_success
>  to False.
>
> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>
>> debug=0 but weewx writes over a thousand lines to the systemd
>> journal. Its writing the data it read from the Vantage Pro II mostly 
>> LOOP:
>> lines. I would rather it didn't do that. None of it is error data.
>> Any idea how to prevent it?
>>
>> --
>> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it,
>> send an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/5c5be090-439b-4fcd-9b23-b7172e606515n%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/CAPq0zECHQCq3AR4XbmLf1P97wLMJGxX7_inaF7Qm%3Dv4AAZNdEQ%40mail.gmail.com.

Re: [weewx-user] no rain data available

[jschoonh]

hey tom,
I've tried a few more things. A think twirl, weewx-csv was installed. I 
didn't took any chances and removed all the extras. Of course no 
difference. Your reasoning that "historical data" coming in from Lacrosse 
gives an accurate rainfall reading is correct. In a "normal" run I kept the 
database locked for one archive loop. In the next archive loop, two 
archival records were written, the 2nd of which was "rain data" available. 
So calculation of two records was possible?
Your workaround to calculate the rain doesn't work. Because there is no 
data to calculate anything. none of the "rain.sum" ($day , $week etc. shows 
new data. The rain data $week, $month, etc, comes from stored data and not 
from new data.
I'm back with at my old setup for now, but that doesn't "live" long 
anymore. I hope there is a solution PLEASE!!. If I can be of any help, let 
me know

Op woensdag 2 maart 2022 om 00:19:29 UTC+3 schreef tke...@gmail.com:

> I think I see what's going on. When weewxd first starts up, it goes into a 
> "catch up" mode, where it downloads all archive records available in the 
> console. In this case, there may be many records, so the differences 
> between values of totalRain can be easily calculated.
>
> However, once catch up mode is over, only single archive records are 
> retrieved from the console. The driver does not save the old value of 
> totalRain, so it has to start anew every time, resulting in 'rain' being 
> set to null.
>
> I'll have to bring this up with the driver author. I've posted issue #756 
>  to track.
>
> In the meantime, there may be a simple fix. Not sure if it will work. Go 
> into your copy of weewx.conf and add the highlighted lines to section 
> [StdWXCalculate]. When you're all done, it will look something like the 
> below. Note that your section may differ from what's shown below. The 
> important thing is to add the highlighted lines at the bottom of the 
> section.
>
> What this will do is cause 'rain' to be calculated in software, rather 
> than downloaded from the console. I haven't tried this, so I'm not sure 
> it's going to work, but it's worth a try. Make the changes, then restart 
> weewxd. Try putting a little water in the bucket and see what shows up on 
> your webpage and in the database.
>
> [StdWXCalculate]
> 
> [[Calculations]]
> # How to calculate derived quantities.  Possible values are:
> #  hardware- use the value provided by hardware
> #  software- use the value calculated by weewx
> #  prefer_hardware - use value provide by hardware if available,
> #  otherwise use value calculated by weewx
> 
> pressure = prefer_hardware
> altimeter = prefer_hardware
> appTemp = prefer_hardware
> barometer = prefer_hardware
> cloudbase = prefer_hardware
> dewpoint = prefer_hardware
> ET = prefer_hardware
> heatindex = prefer_hardware
> humidex = prefer_hardware
> inDewpoint = prefer_hardware
> maxSolarRad = prefer_hardware
> rainRate = prefer_hardware
> windchill = prefer_hardware
> windrun = prefer_hardware
> rain = software
> [[Delta]]
> [[[rain]]]
> input = totalRain
>
>
>
> On Tue, Mar 1, 2022 at 11:47 AM jschoonh  wrote:
>
>> wow i feel a bit stupid here. I try to understand what I see. Sorry it 
>> took a little longer I wasn't home and I have to re-plug the configuration 
>> every time. I first let weewx retrieve the history of the ws2359. Then let 
>> it run 4 time' s the archive loop (20 min) 4 times. Which gives 4 times a 
>> NULL in the rain column of the weewx.sdb.
>> Stop of weewx.
>> Then sqlite3 command as specified. (I had to install sqlite3 first) I 
>> normally use a GUI browser.
>> After that run the weewxd / log.
>> What strikes me in the weewxd log everything goes well until the archive 
>> loop and then rain = "NULL"
>> I am curious if you have an explanation.
>>
>> sqlite3 /home/weewx/Weewx/weewx.sdb
>> SQLite version 3.31.1 2020-01-27 19:55:54
>> Enter ".help" for usage hints.
>> sqlite> select dateTime, datetime(dateTime, 'unixepoch', 'localtime'), 
>> rain from archive order by dateTime desc limit 20;
>> 1646160501|2022-03-01 21:48:21|
>> 1646160197|2022-03-01 21:43:17|
>> 1646159898|2022-03-01 21:38:18|
>> 1646159603|2022-03-01 21:33:23|
>> 1646159343|2022-03-01 21:29:03|0.0
>> 1646159043|2022-03-01 21:24:03|0.0
>> 1646158743|2022-03-01 21:19:03|
>> 1646158399|2022-03-01 21:13:19|
>> 1646158127|2022-03-01 21:08:47|
>> 1646158101|2022-03-01 21:08:21|
>> 1646157788|2022-03-01 21:03:08|0.0
>> 1646157488|2022-03-01 20:58:08|0.05180001
>> 1646157188|2022-03-01 20:53:08|0.0
>> 1646156888|2022-03-01 20:48:08|0.0
>> 1646156588|2022-03-01 20:43:08|0.05180143
>> 1646156288|2022-03-01 20:38:08|0.0
>> 1646155988|2022-03-01 20:33:08|0.0
>> 

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

Seems like the --daemon option fixed things
my service file looks like this (in part()
[Service] 


  
 
ExecStart=/usr/local/bin/weewx/bin/weewxd /usr/local/bin/weewx/weewx.conf 
--daemon 

 
 
ExecReload=/usr/bin/killall -TERM $MAINPID 


 
 
Type=simple 



 
Restart=on-failure 


 
 
RestartSec=100s  

Good grief this google thing here is hard to use!

ok, i just checked before posting and weewx crashed  -  it never does tthat 
but the --daemon opt was the only thing that changed

On Wednesday, March 2, 2022 at 8:23:51 AM UTC-8 Cat22 wrote:

> I thought systemd asked services not to demonize as systemd does that for 
> them. Ami right about this?
> However, I will try it.
>
> On Wednesday, March 2, 2022 at 8:20:32 AM UTC-8 Cat22 wrote:
>
>> weewx version 4.0.0
>> I am having trouble posting here, my posts seem to just disappear. 
>> Hopefully this one will make it.
>> I found log_success in 2 places in weewx.conf I set that to False also, 
>> but it doesnt make a bit of differrence
>>
>> Here is a sample:
>> Mar 02 08:18:20 pc2 weewxd[14910]: LOOP:   2022-03-02 08:18:19 PST 
>> (1646237899) altimeter etc etc, the line is very long
>> On Wednesday, March 2, 2022 at 8:15:48 AM UTC-8 tke...@gmail.com wrote:
>>
>>> Thanks, i just tried that and restarted wewx but it's still printing 
 that loop data.
>>>
>>>
>>> I'm not sure what you mean by "printing that loop data." Are we talking 
>>> about the log? Or, printing to a console through standard output?
>>>
>>> If the former, the Vantage driver logs no data in the system log --- 
>>> only control information. StdArchive does log successful and unsuccessful 
>>> insertions into the database, but these should be controlled by log_success 
>>> and log_failure, respectively, at least on modern versions of WeeWX (what 
>>> version are you using?).
>>>
>>> If the latter (printing to the console), then you shouldn't see this if 
>>> you are running weewxd as a daemon.
>>>
>>> Perhaps an excerpt of the log so we can see what you're concerned about?
>>>
>>> On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer  wrote:
>>>
 Just set option log_success 
  to False.

 On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:

> debug=0 but weewx writes over a thousand lines to the systemd journal. 
> Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. 
> I 
> would rather it didn't do that. None of it is error data.
> Any idea how to prevent it?
>
> -- 
> You received this message because you are subscribed to the Google 
> Groups "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send 
> an email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/5c5be090-439b-4fcd-9b23-b7172e606515n%40googlegroups.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

I thought systemd asked services not to demonize as systemd does that for 
them. Ami right about this?
However, I will try it.

On Wednesday, March 2, 2022 at 8:20:32 AM UTC-8 Cat22 wrote:

> weewx version 4.0.0
> I am having trouble posting here, my posts seem to just disappear. 
> Hopefully this one will make it.
> I found log_success in 2 places in weewx.conf I set that to False also, 
> but it doesnt make a bit of differrence
>
> Here is a sample:
> Mar 02 08:18:20 pc2 weewxd[14910]: LOOP:   2022-03-02 08:18:19 PST 
> (1646237899) altimeter etc etc, the line is very long
> On Wednesday, March 2, 2022 at 8:15:48 AM UTC-8 tke...@gmail.com wrote:
>
>> Thanks, i just tried that and restarted wewx but it's still printing that 
>>> loop data.
>>
>>
>> I'm not sure what you mean by "printing that loop data." Are we talking 
>> about the log? Or, printing to a console through standard output?
>>
>> If the former, the Vantage driver logs no data in the system log --- only 
>> control information. StdArchive does log successful and unsuccessful 
>> insertions into the database, but these should be controlled by log_success 
>> and log_failure, respectively, at least on modern versions of WeeWX (what 
>> version are you using?).
>>
>> If the latter (printing to the console), then you shouldn't see this if 
>> you are running weewxd as a daemon.
>>
>> Perhaps an excerpt of the log so we can see what you're concerned about?
>>
>> On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer  wrote:
>>
>>> Just set option log_success 
>>>  to False.
>>>
>>> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>>>
 debug=0 but weewx writes over a thousand lines to the systemd journal. 
 Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. 
 I 
 would rather it didn't do that. None of it is error data.
 Any idea how to prevent it?

 -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/8455335d-09e6-4055-89ea-7b7a6f22a7f9n%40googlegroups.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

weewx version 4.0.0
I am having trouble posting here, my posts seem to just disappear. 
Hopefully this one will make it.
I found log_success in 2 places in weewx.conf I set that to False also, but 
it doesnt make a bit of differrence

Here is a sample:
Mar 02 08:18:20 pc2 weewxd[14910]: LOOP:   2022-03-02 08:18:19 PST 
(1646237899) altimeter etc etc, the line is very long
On Wednesday, March 2, 2022 at 8:15:48 AM UTC-8 tke...@gmail.com wrote:

> Thanks, i just tried that and restarted wewx but it's still printing that 
>> loop data.
>
>
> I'm not sure what you mean by "printing that loop data." Are we talking 
> about the log? Or, printing to a console through standard output?
>
> If the former, the Vantage driver logs no data in the system log --- only 
> control information. StdArchive does log successful and unsuccessful 
> insertions into the database, but these should be controlled by log_success 
> and log_failure, respectively, at least on modern versions of WeeWX (what 
> version are you using?).
>
> If the latter (printing to the console), then you shouldn't see this if 
> you are running weewxd as a daemon.
>
> Perhaps an excerpt of the log so we can see what you're concerned about?
>
> On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer  wrote:
>
>> Just set option log_success 
>>  to False.
>>
>> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>>
>>> debug=0 but weewx writes over a thousand lines to the systemd journal. 
>>> Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. I 
>>> would rather it didn't do that. None of it is error data.
>>> Any idea how to prevent it?
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/973de960-764f-4e29-ab60-736294b0eebbn%40googlegroups.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

Oh, just saw the excerpt you posted. Looks like you forgot the --daemon
flag in the command line.

On Wed, Mar 2, 2022 at 8:13 AM Cat22  wrote:

> I just tried  log_success = False in weewx.conf and restarted weewx but
> its still doing it
> # systemctl status weewx
> ● weewx.service - weewx 4.0.0 weather system
> Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor
> preset: disabled)
> Active: active (running) since Wed 2022-03-02 08:02:23 PST; 2min 44s
> ago
>   Main PID: 24371 (python)
>  Tasks: 4 (limit: 4915)
> CGroup: /system.slice/weewx.service
> └─24371 python /usr/local/bin/weewx/bin/weewxd
> /usr/local/bin/weewx/weewx.conf
> Sample of lines logged
> Mar 02 08:04:44 pc2 weewxd[24371]: LOOP:   2022-03-02 08:04:41 PST
> (1646237081) altimeter:  etc etc the line is very long
> Mar 02 08:04:44 pc2 weewxd[24371]: LOOP:   2022-03-02 08:04:43 PST
> (1646237083) altimeter:  etc etc
>
>
> On Wednesday, March 2, 2022 at 7:55:54 AM UTC-8 tke...@gmail.com wrote:
>
>> Just set option log_success
>>  to False.
>>
>> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>>
>>> debug=0 but weewx writes over a thousand lines to the systemd journal.
>>> Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. I
>>> would rather it didn't do that. None of it is error data.
>>> Any idea how to prevent it?
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/804709e9-0496-43c2-9568-45962ba3b6c6n%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/CAPq0zEBjBmrqqtN8bk9h1%2BTEeVkzG2NvmKWfNu%2B7eB_vCQEaHA%40mail.gmail.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

>
> Thanks, i just tried that and restarted wewx but it's still printing that
> loop data.


I'm not sure what you mean by "printing that loop data." Are we talking
about the log? Or, printing to a console through standard output?

If the former, the Vantage driver logs no data in the system log --- only
control information. StdArchive does log successful and unsuccessful
insertions into the database, but these should be controlled by log_success
and log_failure, respectively, at least on modern versions of WeeWX (what
version are you using?).

If the latter (printing to the console), then you shouldn't see this if you
are running weewxd as a daemon.

Perhaps an excerpt of the log so we can see what you're concerned about?

On Wed, Mar 2, 2022 at 7:55 AM Tom Keffer  wrote:

> Just set option log_success
>  to False.
>
> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>
>> debug=0 but weewx writes over a thousand lines to the systemd journal.
>> Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. I
>> would rather it didn't do that. None of it is error data.
>> Any idea how to prevent it?
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/CAPq0zEBEHkydD848oier3vmE-ae8RRDhfB2bmVkNc0CKLVS9TA%40mail.gmail.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Cat22]

I just tried  log_success = False in weewx.conf and restarted weewx but its 
still doing it
# systemctl status weewx   
● weewx.service - weewx 4.0.0 weather system 
Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: disabled) 
Active: active (running) since Wed 2022-03-02 08:02:23 PST; 2min 44s 
ago 
  Main PID: 24371 (python) 
 Tasks: 4 (limit: 4915) 
CGroup: /system.slice/weewx.service 
└─24371 python /usr/local/bin/weewx/bin/weewxd 
/usr/local/bin/weewx/weewx.conf
Sample of lines logged
Mar 02 08:04:44 pc2 weewxd[24371]: LOOP:   2022-03-02 08:04:41 PST 
(1646237081) altimeter:  etc etc the line is very long
Mar 02 08:04:44 pc2 weewxd[24371]: LOOP:   2022-03-02 08:04:43 PST 
(1646237083) altimeter:  etc etc


On Wednesday, March 2, 2022 at 7:55:54 AM UTC-8 tke...@gmail.com wrote:

> Just set option log_success 
>  to False.
>
> On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:
>
>> debug=0 but weewx writes over a thousand lines to the systemd journal. 
>> Its writing the data it read from the Vantage Pro II mostly LOOP:  lines. I 
>> would rather it didn't do that. None of it is error data.
>> Any idea how to prevent it?
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/804709e9-0496-43c2-9568-45962ba3b6c6n%40googlegroups.com.

Re: [weewx-user] weewx writing too much to systemd journal

[Tom Keffer]

Just set option log_success
 to False.

On Wed, Mar 2, 2022 at 7:50 AM Cat22  wrote:

> debug=0 but weewx writes over a thousand lines to the systemd journal. Its
> writing the data it read from the Vantage Pro II mostly LOOP:  lines. I
> would rather it didn't do that. None of it is error data.
> Any idea how to prevent it?
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%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/CAPq0zECijgyC4YjxJ3bk-nCWw%2BFqiktt4ehrGsoUVhnmBrUiCw%40mail.gmail.com.

[weewx-user] weewx writing too much to systemd journal

[Cat22]

debug=0 but weewx writes over a thousand lines to the systemd journal. Its 
writing the data it read from the Vantage Pro II mostly LOOP:  lines. I 
would rather it didn't do that. None of it is error data.
Any idea how to prevent it?

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/7f3c7019-ea57-40c6-a6f0-c0799b8a5ce7n%40googlegroups.com.

[weewx-user] Re: Weather34

[Steeple Ian]

Also make sure that WeeWX is actually running after you issued the restart 
command.

On Tuesday, March 1, 2022 at 9:53:40 PM UTC Steeple Ian wrote:

> Can you let me have your URL please, I need to check your realtime data. 
> The situation in your screen shot indicates that the template is not 
> getting live data from WeeWX.
>
> On Tuesday, March 1, 2022 at 7:28:01 PM UTC matthieu89...@gmail.com wrote:
>
>> Yes, I will watch for the file service.txt.
>>
>> For weewx.conf I add [Services]] section in the [Engine] stanza. : ,
>> *user.w34_db_backup.W34_DB_Backup*
>> And at the end :
>> [W34_DB_Backup] * # database path(s) seperated by , rename this/these 
>> database(s) to match your own databases = 
>> /home/weewx/archive/weewx.sdb,/home/weewx/archive/another.sdb # backup 
>> path(s) comma seperated backups = 
>> [your_backup_path]/weewx_backup.sdb,[your_backup_path]/home/pi/another_backup.sdb
>>  
>> # set the daily time to backup comma seperated for multiple databases # the 
>> time must be set an to archive time so it runs immediately after the 
>> archive interval processes are complete backup_times = 00:00,00:00*
>>
>>
>> Yes, sorry but the data for the pression, temperature, and windy for 
>> weather34 are not correct.
>> Is not the real values
>>
>> What is the problem ?
>> Le lundi 28 février 2022 à 23:02:26 UTC+1, steep...@gmail.com a écrit :
>>
>>> I am glad the template is now running for you.
>>>
>>> Regarding the two errors: -
>>>
>>> 1. Metar, it looks as though you did not add your X-API-Key or Metar 
>>> airport code when you generated your services.txt. Did you follow the 
>>> instructions to obtain a key and find your nearest airport?
>>> The three relevant lines in the web services section of weewx.conf 
>>> should look something like this (ABCD represents the airport code and 
>>> 123456789 represents the API Key: -
>>>   me_url = https://api.checkwx.com/metar/ABCD/decoded
>>>   me_header = X-API-Key:123456789
>>>   me_interval = 3600
>>>
>>> 2. The file should already be in place, all you need to do is edit 
>>> weewx.conf and restart as in the instructions. I have updated the install 
>>> instructions to make this clearer>
>>>
>>> Ian
>>>
>>>
>>>
>>> On Monday, February 28, 2022 at 5:25:50 PM UTC matthieu89...@gmail.com 
>>> wrote:
>>>
 Thanks !
 Weather34 is running with weewx and debian ! :)

 But, I have a message error :

 Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Failed 
 getting web service data. URL: https://api.checkwx.com/metar//decoded 
 Header: {'X-API-Key': ''}, Error: HTTP Error 404: Not Found
 Feb 28 16:56:38 raspberrypi weewx[2897] ERROR user.weather34: Error 
 Invalid Webservice Data: None, {'User-Agent': 'Mozilla/5.0 (Macintosh; U; 
 Intel Mac OS X 10_6_4; en-US) AppleWebKit/534.3 (KHTML, like Gecko) 
 Chrome/51.0.2704.103 Safari/534.3'}

 And, I don't find a w34_db_backup.py file for put in 
 /home/weewx/bin/user 
 Where is he ?



  

 Le dimanche 27 février 2022 à 23:31:13 UTC+1, steep...@gmail.com a 
 écrit :

> Vince is correct, it is looking for services.txt one level up from the 
> install folder.
>
> Assuming you downloaded the zip file from the repository into your 
> /home/pi folder and un zipped it, the install folder is 
> weewx-Weather34-main. The services.txt file should also be in your 
> /home/pi 
> folder.
>
> Therefore you should: -
>
> cd weewx-Weather34-main
> sudo python3 ./w34_installer.py
>
> On Sunday, February 27, 2022 at 8:44:58 PM UTC vince wrote:
>
>> On Sunday, February 27, 2022 at 12:02:05 PM UTC-8 
>> matthieu89...@gmail.com wrote:
>>
>>> When i use sudo python3 /home/pi/weewx-Weather34/w34_installer.py 
>>
>>
>>> *Cannot find ../services.txt file INSTALL ABORTED*
>>>
>>
>>> Whereas my file service.txt is in /home/pi
>>>
>>>
>> It is trying to find services.txt using a relative path one level up 
>> from the directory you are running the command in.
>>
>> Try:
>>
>>- cd /home/pi/weewx-Weather34
>>- sudo python3 /home/pi/weewx-Weather34/w34_installer.py
>>
>>
>>

-- 
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/d65136a9-58b2-4beb-be35-d04d71244538n%40googlegroups.com.

[weewx-user] Re: import csv file from weatherlink davis to weewx

[gjr80]

OK, this should be easy enough to import with wee_import, worst case you 
may need to do a global search and replace to change the field delimiter (I 
suspect the python csv reader will choke on a comma as decimal separator 
and field separator even with the quotes). Let me work through this.

Gary

On Wednesday, 2 March 2022 at 18:38:28 UTC+10 Artvd wrote:

> @gary I am sorry that the line a posted did not include N,S etc because 
> there had been no wind reported. 
> I had been changing all kind of things the last couple of days. Converted 
> the Davis file in excel etc.
> In the meantime i have gained some more insight. As I would like to import 
> 13 months, i probably better go back to the original import file. I will 
> have to amend the import config file, which will take some time.
>
> Below you will find (part of) this original file exported from 
> Weatherlink.com. As you can see in the first 5 line it uses SW WSW W W. *I 
> am looking for the correct unit name for weewx of such data (instead of 
> degree_compass)* 
>  
>
> "Date & Time","Inside Temp - °C","High Inside Temp - °C","Low Inside Temp 
> - °C","Inside Hum - %","High Inside Hum - %","Low Inside Hum - %","Inside 
> Dew Point - °C","Inside Heat Index - °C","Barometer - hPa","High Bar - 
> hPa","Low Bar - hPa","Absolute Pressure - hPa","Temp - °C","High Temp - 
> °C","Low Temp - °C","Hum - %","High Hum - %","Low Hum - %","Dew Point - 
> °C","High Dew Point - °C","Low Dew Point - °C","Wet Bulb - °C","High Wet 
> Bulb - °C","Low Wet Bulb - °C","Avg Wind Speed - m/s","Prevailing Wind 
> Direction","High Wind Speed - m/s","High Wind Direction","Wind Chill - 
> °C","Low Wind Chill - °C","Heat Index - °C","High Heat Index - °C","THW 
> Index - °C","High THW Index - °C","Low THW Index - °C","Rain - mm","High 
> Rain Rate - mm/h","Heating Degree Days","Cooling Degree Days"
> "1/1/21 
> 00:00","20,7","21,1","20,7","42,1","42,2","41,8","7,4","19,7","1004,2","1004,2","1004,2","950,3","0,2","0,2","0,1","98,7","98,8","98,7","0,0","0,0","-0,1","0,1","0,1","0,1","0,0","","0,0","","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
> "1/1/21 
> 00:15","20,5","20,8","20,5","41,9","42,6","41,6","7,1","19,4","1004,2","1004,3","1004,2","950,3","0,2","0,2","0,1","98,5","98,7","98,5","-0,1","0,0","-0,1","0,1","0,1","0,0","0,0","","0,7","SW","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
> "1/1/21 
> 00:30","20,3","20,6","20,3","42,4","42,8","41,8","7,1","19,3","1004,2","1004,3","1004,2","950,3","0,2","0,2","0,1","98,4","98,6","98,4","-0,1","0,0","-0,1","0,1","0,1","0,0","0,0","","0,3","WSW","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
> "1/1/21 
> 00:45","20,3","20,4","20,2","41,8","42,5","41,6","6,9","19,3","1004,3","1004,4","1004,2","950,4","0,1","0,2","0,1","98,2","98,3","98,1","-0,2","-0,1","-0,2","0,0","0,1","-0,1","0,0","","0,2","W","0,1","0,1","0,1","0,2","0,1","0,2","0,1","0,0","0,0","0,190","0,000"
> "1/1/21 
> 01:00","20,2","20,3","20,1","41,8","42,6","41,6","6,8","19,2","1004,4","1004,4","1004,3","950,5","0,0","0,1","0,0","97,9","98,2","97,9","-0,3","-0,2","-0,3","-0,1","0,0","-0,1","0,0","","0,4","W","0,0","0,0","0,0","0,1","0,0","0,1","0,0","0,0","0,0","0,191","0,000"
> "1/1/21 
> 01:15","20,1","20,3","20,1","41,6","41,9","41,4","6,6","19,1","1004,5","1004,6","1004,4","950,6","0,0","0,1","-0,1","98,1","98,1","97,9","-0,3","-0,2","-0,3","-0,1","-0,1","-0,2","0,0","","0,0","","0,0","-0,1","0,0","0,1","0,0","0,1","-0,1","0,0","0,0","0,191","0,000"
> "1/1/21 
> 01:30","19,8","20,1","19,8","42,1","42,2","41,4","6,6","18,8","1004,6","1004,6","1004,5","950,7","-0,1","0,0","-0,1","98,0","98,1","97,9","-0,4","-0,3","-0,4","-0,2","-0,1","-0,2","0,0","","0,0","","-0,1","-0,1","-0,1","0,0","-0,1","0,0","-0,1","0,0","0,0","0,192","0,000"
> "1/1/21 
> 01:45","19,4","19,8","19,4","42,0","42,0","41,6","6,2","18,3","1004,6","1004,7","1004,6","950,7","-0,2","-0,1","-0,2","98,1","98,1","98,0","-0,4","-0,3","-0,4","-0,3","-0,2","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,1","-0,2","-0,1","-0,2","0,0","0,0","0,193","0,000"
> "1/1/21 
> 02:00","19,1","19,4","19,1","42,3","42,3","41,8","5,9","17,9","1004,6","1004,6","1004,6","950,7","-0,1","-0,1","-0,2","98,2","98,2","98,1","-0,3","-0,3","-0,4","-0,2","-0,2","-0,3","0,0","","0,0","","-0,1","-0,2","-0,1","-0,1","-0,1","-0,1","-0,2","0,0","0,0","0,192","0,000"
> "1/1/21 
> 02:15","18,9","19,2","18,9","42,1","42,3","41,9","5,8","17,8","1004,7","1004,7","1004,6","950,8","-0,2","-0,1","-0,2","98,3","98,3","98,2","-0,4","-0,3","-0,4","-0,3","-0,2","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,1","-0,2","-0,1","-0,2","0,0","0,0","0,193","0,000"
> "1/1/21 
> 02:30","18,7","18,9","18,6","42,6","42,6","42,1","5,7","17,5","1004,8","1004,8","1004,7","950,9","-0,2","-0,2","-0,2","98,3","98,3","98,3","-0,4","-0,4","-0,4","-0,3","-0,3","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","0,0","0,0","0,193","0,000"
> "1/1/21 
> 

[weewx-user] Re: import csv file from weatherlink davis to weewx

[Artvd]

@gary I am sorry that the line a posted did not include N,S etc because 
there had been no wind reported. 
I had been changing all kind of things the last couple of days. Converted 
the Davis file in excel etc.
In the meantime i have gained some more insight. As I would like to import 
13 months, i probably better go back to the original import file. I will 
have to amend the import config file, which will take some time.

Below you will find (part of) this original file exported from 
Weatherlink.com. As you can see in the first 5 line it uses SW WSW W W. *I 
am looking for the correct unit name for weewx of such data (instead of 
degree_compass)* 
 

"Date & Time","Inside Temp - °C","High Inside Temp - °C","Low Inside Temp - 
°C","Inside Hum - %","High Inside Hum - %","Low Inside Hum - %","Inside Dew 
Point - °C","Inside Heat Index - °C","Barometer - hPa","High Bar - 
hPa","Low Bar - hPa","Absolute Pressure - hPa","Temp - °C","High Temp - 
°C","Low Temp - °C","Hum - %","High Hum - %","Low Hum - %","Dew Point - 
°C","High Dew Point - °C","Low Dew Point - °C","Wet Bulb - °C","High Wet 
Bulb - °C","Low Wet Bulb - °C","Avg Wind Speed - m/s","Prevailing Wind 
Direction","High Wind Speed - m/s","High Wind Direction","Wind Chill - 
°C","Low Wind Chill - °C","Heat Index - °C","High Heat Index - °C","THW 
Index - °C","High THW Index - °C","Low THW Index - °C","Rain - mm","High 
Rain Rate - mm/h","Heating Degree Days","Cooling Degree Days"
"1/1/21 
00:00","20,7","21,1","20,7","42,1","42,2","41,8","7,4","19,7","1004,2","1004,2","1004,2","950,3","0,2","0,2","0,1","98,7","98,8","98,7","0,0","0,0","-0,1","0,1","0,1","0,1","0,0","","0,0","","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
"1/1/21 
00:15","20,5","20,8","20,5","41,9","42,6","41,6","7,1","19,4","1004,2","1004,3","1004,2","950,3","0,2","0,2","0,1","98,5","98,7","98,5","-0,1","0,0","-0,1","0,1","0,1","0,0","0,0","","0,7","SW","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
"1/1/21 
00:30","20,3","20,6","20,3","42,4","42,8","41,8","7,1","19,3","1004,2","1004,3","1004,2","950,3","0,2","0,2","0,1","98,4","98,6","98,4","-0,1","0,0","-0,1","0,1","0,1","0,0","0,0","","0,3","WSW","0,2","0,1","0,2","0,2","0,2","0,2","0,1","0,0","0,0","0,189","0,000"
"1/1/21 
00:45","20,3","20,4","20,2","41,8","42,5","41,6","6,9","19,3","1004,3","1004,4","1004,2","950,4","0,1","0,2","0,1","98,2","98,3","98,1","-0,2","-0,1","-0,2","0,0","0,1","-0,1","0,0","","0,2","W","0,1","0,1","0,1","0,2","0,1","0,2","0,1","0,0","0,0","0,190","0,000"
"1/1/21 
01:00","20,2","20,3","20,1","41,8","42,6","41,6","6,8","19,2","1004,4","1004,4","1004,3","950,5","0,0","0,1","0,0","97,9","98,2","97,9","-0,3","-0,2","-0,3","-0,1","0,0","-0,1","0,0","","0,4","W","0,0","0,0","0,0","0,1","0,0","0,1","0,0","0,0","0,0","0,191","0,000"
"1/1/21 
01:15","20,1","20,3","20,1","41,6","41,9","41,4","6,6","19,1","1004,5","1004,6","1004,4","950,6","0,0","0,1","-0,1","98,1","98,1","97,9","-0,3","-0,2","-0,3","-0,1","-0,1","-0,2","0,0","","0,0","","0,0","-0,1","0,0","0,1","0,0","0,1","-0,1","0,0","0,0","0,191","0,000"
"1/1/21 
01:30","19,8","20,1","19,8","42,1","42,2","41,4","6,6","18,8","1004,6","1004,6","1004,5","950,7","-0,1","0,0","-0,1","98,0","98,1","97,9","-0,4","-0,3","-0,4","-0,2","-0,1","-0,2","0,0","","0,0","","-0,1","-0,1","-0,1","0,0","-0,1","0,0","-0,1","0,0","0,0","0,192","0,000"
"1/1/21 
01:45","19,4","19,8","19,4","42,0","42,0","41,6","6,2","18,3","1004,6","1004,7","1004,6","950,7","-0,2","-0,1","-0,2","98,1","98,1","98,0","-0,4","-0,3","-0,4","-0,3","-0,2","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,1","-0,2","-0,1","-0,2","0,0","0,0","0,193","0,000"
"1/1/21 
02:00","19,1","19,4","19,1","42,3","42,3","41,8","5,9","17,9","1004,6","1004,6","1004,6","950,7","-0,1","-0,1","-0,2","98,2","98,2","98,1","-0,3","-0,3","-0,4","-0,2","-0,2","-0,3","0,0","","0,0","","-0,1","-0,2","-0,1","-0,1","-0,1","-0,1","-0,2","0,0","0,0","0,192","0,000"
"1/1/21 
02:15","18,9","19,2","18,9","42,1","42,3","41,9","5,8","17,8","1004,7","1004,7","1004,6","950,8","-0,2","-0,1","-0,2","98,3","98,3","98,2","-0,4","-0,3","-0,4","-0,3","-0,2","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,1","-0,2","-0,1","-0,2","0,0","0,0","0,193","0,000"
"1/1/21 
02:30","18,7","18,9","18,6","42,6","42,6","42,1","5,7","17,5","1004,8","1004,8","1004,7","950,9","-0,2","-0,2","-0,2","98,3","98,3","98,3","-0,4","-0,4","-0,4","-0,3","-0,3","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","0,0","0,0","0,193","0,000"
"1/1/21 
02:45","18,3","18,7","18,3","42,9","42,9","42,3","5,5","17,0","1005,1","1005,1","1004,8","951,1","-0,2","-0,2","-0,2","98,4","98,4","98,3","-0,4","-0,4","-0,4","-0,3","-0,3","-0,3","0,0","","0,0","","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","-0,2","0,0","0,0","0,193","0,000"
"1/1/21