Re: [weewx-user] Data export to csv

[Thomas Keffer]

If you need to export to CSV only once, then there is no need to convert
the database. Just make a copy, convert that, export to CSV, then throw the
copy away.

Otherwise, if you expect to do this regularly, then, yes, convert and use
the converted database.

There should be no problems with upgrades. Being able to support multiple
database systems is a key feature of WeeWX.

-tk

On Wed, Apr 22, 2020 at 7:39 AM Janne Prokkola 
wrote:

> hello
> sorry, I add more info.
>
> I have sqlite. In User's Guide it says:
>
> "Because of this, unless you have a special purpose application, there is
> really no good reason to change from the default, which is US"
>
> I want to keep the installation as default as possible. But on the other
> hand if I want to export sqlite as metrics, should we think this is a
> special purpose enough to start with (or convert to) metrics?
>
> And, if I choose to use metrics in database, will there be any problems in
> future upgrades like should I always make changes in conf-files after
> upgrade?
>
> Janne
>
>
> tiistai 21. huhtikuuta 2020 23.53.12 UTC+3 Tom Keffer kirjoitti:
>>
>> If you want the results in metric, it would be best to convert the
>> database first, then dump it to CSV. For how to convert the database, see
>> the section *Changing the database unit system
>> * in
>> the Customizing Guide.
>>
>> You didn't say what kind of database, but if you use sqlite, the utility
>> sqlite3 can export to CSV. You may need to download it first
>>
>> *sudo apt install sqlite3*
>>
>> Then
>>
>> *sqlite3 weewx.sdb*
>> sqlite> *.headers on*
>> sqlite> *.mode csv*
>> sqlite> *.output weewx.csv*
>> sqlite> *select * from archive;*
>>
>> This will create a file weewx.csv with the data. It will be in whatever
>> unit system your database is in. Hence, the need to convert first.
>>
>> Documentation for sqlite3 .
>>
>>
>>
>> On Tue, Apr 21, 2020 at 12:24 PM Janne Prokkola 
>> wrote:
>>
>>> hello
>>>
>>> I'd like to export my database to csv. Is there any easy way to export
>>> US format database to metrics units?
>>>
>>> I'm building my weather station set up. I'm thinking should I have the
>>> database in metrics format or should I stay in US. In Finland I have no use
>>> for imperial/US units.
>>>
>>> best regards
>>> Janne Prokkola
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/ba6c819d-a9c5-406e-9854-60af09e81b9b%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/79f911de-a153-4968-9dd7-0e35b4c19ba6%40googlegroups.com
> 
> .
>

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

Re: [weewx-user] Re: Need help with error message

[Thomas Keffer]

You want the IP address of the WeatherLinkIP, not your computer.

You may be able to figure it out by logging into your router and looking
for 'attached devices' (or something similar).

-tk

On Tue, Apr 21, 2020 at 4:17 PM Peter Ten Eyck  wrote:

> Not sure I follow... "WeatherLinux box in it"  ?
>
> What should this be? 192.168.1.122 is my Raspberry Pi
>
>  If the connection type is ethernet, an IP Address/hostname is required:
>   host = 192.168.1.122
>
> On Tuesday, April 21, 2020 at 5:56:30 PM UTC-4, vince wrote:
>>
>> On Tuesday, April 21, 2020 at 2:14:28 PM UTC-7, Peter Ten Eyck wrote
>>
>>> Apr 21 17:12:56 Weatherpi weewx[1285]: vantage: Socket error while
>>> opening port 2 to ethernet host 192.168.1.122.
>>> Apr 21 17:12:56 Weatherpi weewx[1285]: engine: Import of driver failed:
>>> [Errno 111] Connection refused (>> IOError'>)
>>>
>>>
>> Connnection refused is the computer you are trying to connect to
>> 'generally' is not listening on that port.
>>
>> You probably want your weewx.conf to have the ip address of the
>> WeatherLinux box in it, 'not' the ip address of the weewx host itself.
>> Lots of people make that mistake.
>>
> --
> 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/bced3a74-3dff-4b9e-a03b-6559e7b6056a%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/CAPq0zEDzd8ain0%3DmzsKCe5W-gx6Ay0xij%3DVb2rX-FVZZxhQxYQ%40mail.gmail.com.

Re: [weewx-user] Re: fileparse polling interval

[Thomas Keffer]

Sounds like an interesting project.

On Tue, Apr 21, 2020 at 5:53 AM jf42  wrote:

> My station is a german "MWS 55V", which is read out by a Python program,
> writing the data to a tcp port. Another computer
> collects the data, does a quality check, many other stuff, and writes a
> file. Weewx uses the file parser to get the data.
> The station provides the data every 2 secs, the file resolution is about 5
> secs. We use the data for a lidar instrument
> (light radar) for weather monitoring during atmospheric measurements.
> Thus: the faster the better ;-)
> That's for the background of my question.
>
>
> --
> 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/beae49e6-f7d2-472a-8a6b-efcab5d9fc0d%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/CAPq0zEAs1wn17cVp3ZSM4ctqytjHg5Lzp-hhg%2BXepS%3DkPWuRcw%40mail.gmail.com.

Re: [weewx-user] Current / daily graphs are empty...

[Thomas Keffer]

1. If you're going to customize your skin (and you should), then it's worth
reading through the *Customizing Guide
*. See the section
[[TimeFormats]]
 for how to
customize times.
2. On your station, the archive interval is set by the logging interval in
your hardware, the VP2. Either change it through the console, or use the
wee_device utility with the --set-interval
 option.
Be sure to stop weewx first.

-tk

On Tue, Apr 21, 2020 at 5:34 AM Tor Tveitane  wrote:

> Hi,
>
> You are absolutely correct!  I have a 4k screen so I had to literally use
> a magnifying glass to see them but you are right.  Thanks a lot!  I'm
> stopping and starting the service now to see the result :-)
> Btw I have tried to find where to edit the displayed datetime stamps in
> reports but only found a lot of info about timestamps in imports etc.  I
> need dd.mm. and 24h time format..  Also I haven't found how where I
> edit the 30 minutes polling time.  I want it to poll more often.
> I refreshed the default web page and now it works nicely!  Sorry for
> bugging you, I'm looking forward to getting more used to how weewx does its
> work now!
>
> best regards Tor
>
> --
> 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/c83166ab-3177-46bf-a493-f27653c6c866%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/CAPq0zEAOz_3vEeJ%2BfaDKZ0XfKPznGHP3UE75H7LdBahfCGp1HA%40mail.gmail.com.

Re: [weewx-user] Re: fileparse polling interval

[Thomas Keffer]

In theory, yes, you will be able to use an archive interval of less than a
minute. But, some weather stations emit data only every 30-60 seconds or so
and, even then, not all data.

On Tue, Apr 21, 2020 at 5:01 AM jf42  wrote:

> Thanks for the info.
>
> Seems that with Version 4 archive intervals less than 60 secs would be
> possible.
> I guess, my computer is fast enough to handle the neccessary tasks ...
>
> --
> 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/dcc3a091-dcd0-4934-9250-6e3f62cfa7ba%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/CAPq0zEAeD_y7sas8w4Sk9Dd-HB%3DsHkMjPPZGKWZDspxW_c0Vjw%40mail.gmail.com.

Re: [weewx-user] Current / daily graphs are empty...

[Thomas Keffer]

Gary's diagnosis is correct. If you look closely at your "Current" plots,
there are, in fact, dots in there. They are just not connected.

Change the option line_gap_fraction in skin.conf to 0.1. That should cure
the problem.

-tk

On Tue, Apr 21, 2020 at 5:05 AM Tor Tveitane  wrote:

> Sorry forgot the logfile.  Here it comes.
>
> I can add that our Vantage Pro 2 station is connected via network til a
> virtual debian machine under vmware.  As statedall text data is updated
> each 30 minutes to the current values.  See screenshot also in attached
> file.
>
> Tor
>
> --
> 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/5056d638-040b-4bce-94c0-89599d78acc9%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/CAPq0zEDiQ%3D16c3gqD9Q8xxKRiO%2BPvtUNUrza5%3D4ZjmgUfxdyvA%40mail.gmail.com.

Re: [weewx-user] Current / daily graphs are empty...

[Thomas Keffer]

Didn't see any attached log, but I suspect Gary is right: if your station
uses a 30 minute archive interval, it may not be generating enough data to
"connect the dots." Try changing the option "line_gap_fraction" in
skin.conf to, say, 0.1.

But, the log will give a more definitive answer.

-tk

On Tue, Apr 21, 2020 at 4:57 AM Tor Tveitane  wrote:

> Hi,
>
> I'm sorry for not including the log sample and more information about
> skins etc.  It will come below.  But if you read my post will you see that
> everything is working fine as expected and the data is updated nicely.  -
> Except for the contents of the daily graphs.  This means that all the files
> in /var/www/weewx are updated each half hour including index.html and all
> the.png files.  Also week*.png and month*.png files contains graph data as
> expected and they are displayed nicely in index.html.  However the day*.png
> files do not contain any graph data, only grid and background.  This
> despite that the week*.png files contain graph data for today.   I thought
> that this very special situation had nothing to do with which station I
> used.
>
> I haven't done any special customization of weewx.  No skins or
> exports/imports which can clutter up things.  Only displaying the
> /var/www/weewx/index.html file and click the Current button.  All textboxes
> display the correct current conditions so data fetching and saving works
> nicely, the only problem is that the daily graphs are empty when they are
> created.  I attach the log file sample of starting weewx, letting it run
> through a generation cycle, stopping it and then restarting it again.  I
> hope this can give a clue of what is going on for the day graphing problem.
>
> Thanks again for comments on this.
>
> best regards Tor
>
>
> tirsdag 21. april 2020 12.59.21 UTC+2 skrev Thomas Keffer følgende:
>>
>> Hello, Tor
>>
>> You're not giving us much information to go on.
>>
>> What kind of weather station?
>> Which skin? Have you modified it?
>> Have you checked the timestamps of the generated daily HTML files? Are
>> they, in fact, recent?
>> What kind of database (sqlite or MySQL)? Have you checked the database to
>> make sure you have recent data?
>>
>> Plus, of course, the log. See the wiki article *Help! Posting to
>> weewx-user
>> <https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user>* for
>> how to post a usable log.
>>
>> -tk
>>
>>
>> On Tue, Apr 21, 2020 at 2:25 AM Tor Tveitane  wrote:
>>
>>> Hi,
>>>
>>> We have had weewx installed on debian for some time so it has collected
>>> a fair amount of data and all graphs look nice - except for the default
>>> view's Current graphs.  They are empty (grid and background only).  The
>>> Daily graph files are generated at the same intervals as weekly and monthly
>>> graphs.  When looking at the weekly graph I also see that today's data is
>>> graphed.  So weather data is saved but somehow the current day's data is
>>> not graphed as into the day*.png files like with the other intervals.  What
>>> can be wrong here?
>>>
>>> Thanks a lot for help on this.
>>>
>>> regards
>>>
>>> Tor
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/ce99c9cb-c242-4708-8fbe-a635b1d25454%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/ce99c9cb-c242-4708-8fbe-a635b1d25454%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/48410025-ec4d-4fce-ba76-c67d053099a7%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/48410025-ec4d-4fce-ba76-c67d053099a7%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zECrMEutGR5H0BiwgH-uR_UNR%2BtG%2BQPtq8UOscG1oKQY6A%40mail.gmail.com.

Re: [weewx-user] Current / daily graphs are empty...

[Thomas Keffer]

Hello, Tor

You're not giving us much information to go on.

What kind of weather station?
Which skin? Have you modified it?
Have you checked the timestamps of the generated daily HTML files? Are
they, in fact, recent?
What kind of database (sqlite or MySQL)? Have you checked the database to
make sure you have recent data?

Plus, of course, the log. See the wiki article *Help! Posting to weewx-user
* for how
to post a usable log.

-tk


On Tue, Apr 21, 2020 at 2:25 AM Tor Tveitane  wrote:

> Hi,
>
> We have had weewx installed on debian for some time so it has collected a
> fair amount of data and all graphs look nice - except for the default
> view's Current graphs.  They are empty (grid and background only).  The
> Daily graph files are generated at the same intervals as weekly and monthly
> graphs.  When looking at the weekly graph I also see that today's data is
> graphed.  So weather data is saved but somehow the current day's data is
> not graphed as into the day*.png files like with the other intervals.  What
> can be wrong here?
>
> Thanks a lot for help on this.
>
> regards
>
> Tor
>
> --
> 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/ce99c9cb-c242-4708-8fbe-a635b1d25454%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/CAPq0zEBT_BfR5evUnM0HGejPFnez%3DDg%2BK9%3DMHEMN%3D7rKjMYncw%40mail.gmail.com.

Re: [weewx-user] wee_config not working

[Thomas Keffer]

1. The files in Skins/Standard are the *templates*, not the final HTML
files. The HTML files will appear in /home/weewx/public_html. If they did
not, then you need to send the log. See Help! Posting to weewx-user
 for how
to get a useful log.

2. Unless you are a Python programmer, do not alter the file wee_config.
The string you posted is used internally in wee_config to show the "usage"
hints if you ask for help.

*wee_config --help*


3. See the Wiki article *Understanding paths
*. It may help you
understand why your command did not run.

On Mon, Apr 20, 2020 at 4:51 PM Ellastonepaul 
wrote:

> Hi,
>
> I am setting up Weewx on a Raspberry-pi. Followed Download (3.9.2) and
> Install instructions using *setup-py.* and started with *Simulator* as
> Station. Eventually got it to run in the Browser (Despite no *public_html* 
> file..I
> finally tracked it to *skins/Standard !) *
>
>  I would now like to "Reconfigure" it for my Bresser station.  Following
> instructions I should be able to use *wee_config --reconfigure* but all I
> get is "command not found". I have checked Permissions and all are OK.
>
> Looking at the file *wee_config *I now see line
>
> 14 *usage = """Usage: wee_config --help*
> *15 etc*
> *16 etc*
> *17 wee_config --reconfigure  etc etc*
>
> and line 51 & 52
>
> 51   --altitude --location
> 52   """
>
> In other words this section has been commented out!  Why?  I have removed
> the " marks but it still is not recognised
>
> Have I missed somethingor...?
>
> Also I believe (hope!) that the Bresser 6-in-1 Art No 7002570 will run
> under the FineOffetUSB driver.  I see there have been some discussions on
> this unit but is there anything definitive?
>
>
>
>
>
>
> --
> 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/18a4f784-5863-437f-af05-722931d7360e%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/CAPq0zEAA9pxiqjGMYuWVsDn7p-8TzjLkhZXPmW5bOy-W8XCZOw%40mail.gmail.com.

Re: [weewx-user] Re: fileparse polling interval

[Thomas Keffer]

In V3.x, the option archive_interval must divide evenly into an hour.
Version 4.X will remove that restriction. See Issue #469
.

-tk

On Mon, Apr 20, 2020 at 6:58 AM jf42  wrote:

> Addition:
>
> I found my mistake: archive_interval was 60 in weewx.conf ... But:
>
> Values below 60 sec cause a crash of the software.
>
> Any ideas for that?
>
> --
> 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/6c8e638d-7aa5-4ae9-9a82-bcad43dcd6e7%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/CAPq0zEAbvqteK2nHOb85w7nZmKQhdpJPonDKJDurmt7Dvfz%2BMA%40mail.gmail.com.

Re: [weewx-user] Retrieving all archive records for the past 24 hours

[Thomas Keffer]

If you put the template in the [[ToDate]] section it should do what you
want. NB: $day is *since midnight*. If you want the last 24 hours, you
probably want $span($day_delta=1).records.

On Sat, Apr 18, 2020 at 8:17 PM Ken C  wrote:

>
> Hello,
>
> Is it possible to create a template that outputs archive records for the
> past 24 hours to a single file?
>
> The closest I've been able to find in the Customization Guide is using
> [[SummaryByDay]] and a #for $record in $day.records loop, but rather than
> generating a file for every day in the database, I want a single file that
> has the last 24 hours on a rolling basis.
>
> Just need a point in the right direction.
>
> Cheers,
> Ken C.
>
> --
> 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/ed09e52b-46e9-4905-b125-22814d9c5892%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/CAPq0zEAsc9A4egoKcKiNczSRsn3_duyHa33rfbkxxfRWcgSGeA%40mail.gmail.com.

Re: [weewx-user] Updating historical data in database?

[Thomas Keffer]

Why not just swap the columns around?

UPDATE archive SET outHumidity=inHumidity, inHumidity=outHumidity;

Then drop and rebuild the daily summaries.

-tk

On Sat, Apr 18, 2020 at 10:03 AM Steve Preston 
wrote:

> I just realized that I imported a few years of data from WLK files where I
> accidentally swapped the inside vs outside humidity (a bug which is now
> fixed in my wlkReader app).
> So now I would like to update these values in the database.
>
> Does wee_import "update" records which match the timestamp of existing
> records in the database or does it only ADD new records?  I'm assuming that
> it only adds records.  So I suspect that I will need to remove all the
> historical WLK data from my WeeWx database, then import the correct data
> again.  Does this make sense?
>
> Thanks
> Steve
>
> --
> 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/68aa3172-cce9-4b8b-8a3f-f872dbba1cb5%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/CAPq0zEAjRxiah8H%3DAu0G%3DByHGBeAuJXyww_u3yGYpi-hABR_pw%40mail.gmail.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Thomas Keffer]

Worked for me. Because you are using a 3 hour aggregation period, the
pictures will not be regenerated for 3 hours. Delete all your "yesterday"
plots to have them regenerated at the next reporting cycle.

[image: image.png]

On Sat, Apr 18, 2020 at 6:51 AM Messy Potamia 
wrote:

> in skin.conf:
> [[yesterday_images]]
> #   x_label_format = %H:%M
> #bottom_label_format = %x %H:%M
> #time_length = 97200# == 27 hours
> #axis_label_font_size = 8
>
> x_label_format = %d
> bottom_label_format = %m/%d/%y %H:%M
> time_length = 172800# == 2 days
> #aggregate_type = avg
> aggregate_interval = 10800# == 3 hours
> show_daynight = true
>
> [[[yesterdaybarometer]]]
> time_length = 172800# == 2 days
> barometer
>
> [[[yesterdaytempdew]]]
> time_length = 172800# == 2 days
> outTemp
> dewpoint
>
> [[[yesterdayrain]]]
> # Make sure the y-axis increment is at least 0.02 for the
> rain plot
> time_length = 172800# == 2 days
> yscale = None, None, 0.02
> plot_type = bar
> rain
> aggregate_type = sum
> aggregate_interval = 3600
> label = Rain (hourly total)
>
> [[[yesterdaypond]]]
> time_length = 172800# == 2 days
> yscale = None, None, 0.5
> extraTemp1
>
> [[[yesterdayDnldSpd]]]
> time_length = 172800# == 2 days
> yscale = 5, 50, 5
> leafTemp1
> label = Vega-Net MB/sec
>
> [[[yesterdaywind]]]
> time_length = 172800# == 2 days
> windSpeed
> windGust
>
> [[[yesterdayinside]]]
> time_length = 172800# == 2 days
> inTemp
> label = Fish Pond Temp
>
> [[[yesterdaywinddir]]]
> time_length = 172800# == 2 days
> # Hardwire in the y-axis scale for wind direction
> yscale = 0.0, 360.0, 45.0
> windDir
>
> and yesterday.html.tmpl:
> 
> 
> (48-hr Plots)
> 
> 
>   
>   
>   
>   
>   
>   
>   
>   #if $week.extraTemp1.has_data
>   
>   #end if
> 
> 
>
> But it seems to still be generating only 24-hr length plots:
>
> [image: yesterdaytempdew(only24hrs).png]
> I'm probably doing something wrong but after reading the cited docs I
> don't see what, maybe you do?
> Thx/Phil
>
>
> On Saturday, April 18, 2020 at 9:44:43 AM UTC+2, Andrew Milner wrote:
>>
>> set time_length to the required value (86400*2 for 48 hours) for the
>> required plot(s)
>> http://weewx.com/docs/customizing.htm#Time_periods
>>
>>
>>
>> On Saturday, 18 April 2020 06:51:03 UTC+3, Messy Potamia wrote:
>>>
>>> Then is it possible to generate plots that cover the current 48 hours?
>>> They would end with the current time but would span 2 days.
>>> Thanks
>>> Phil
>>>
>>> On Saturday, April 18, 2020 at 1:25:53 AM UTC+2, Thomas Keffer wrote:
>>>>
>>>> Unfortunately, no. The ImageGenerator can only make plots that end with
>>>> the current time.
>>>>
>>>> -tk
>>>>
>>>> On Fri, Apr 17, 2020 at 8:11 AM Messy Potamia 
>>>> wrote:
>>>>
>>>>> Thanks, the tables are great.
>>>>> - - -
>>>>> Reading through the .tmpls & skin.conf, and
>>>>> http://www.weewx.com/docs/customizing.htm, I cannot glean how to tell
>>>>> the plot generator to generate a plot that is from the same time period 24
>>>>> hours ago. Is there a way to get those?
>>>>> Thanks,
>>>>> Phil
>>>>>
>>>>> On Friday, April 17, 2020 at 4:23:24 PM UTC+2, Messy Potamia wrote:
>>>>>>
>>>>>> Thanks, trying that now...
>>>>>>
>>>>>> On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:
>>>>>>>
>>>>>>> The two tags serve different purposes. The tag $yesterday
>>>>>>> represents an *aggregation* over the day. The tag $current
>>>>>>> represents a single record. There is an undocumented feature in v3.9.2
>>&g

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Thomas Keffer]

Unfortunately, no. The ImageGenerator can only make plots that end with the
current time.

-tk

On Fri, Apr 17, 2020 at 8:11 AM Messy Potamia 
wrote:

> Thanks, the tables are great.
> - - -
> Reading through the .tmpls & skin.conf, and
> http://www.weewx.com/docs/customizing.htm, I cannot glean how to tell the
> plot generator to generate a plot that is from the same time period 24
> hours ago. Is there a way to get those?
> Thanks,
> Phil
>
> On Friday, April 17, 2020 at 4:23:24 PM UTC+2, Messy Potamia wrote:
>>
>> Thanks, trying that now...
>>
>> On Friday, April 17, 2020 at 4:18:33 PM UTC+2, Thomas Keffer wrote:
>>>
>>> The two tags serve different purposes. The tag $yesterday represents an
>>> *aggregation* over the day. The tag $current represents a single
>>> record. There is an undocumented feature in v3.9.2 (documented in V4.0)
>>> that gets you what you want:
>>>
>>> The temperature 24 hours ago was
>>> $current(timestamp=$current.dateTime.raw-86400).outTemp
>>>
>>>
>>> -tk
>>>
>>> On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia 
>>> wrote:
>>>
>>>> The high/low table is working, showing but I'd like to get the upper
>>>> table in yesterday.html.tmpl  to show the data from 86400 seconds ago,
>>>> or one day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be
>>>> working.
>>>> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd
>>>> like it to show the same data as if you looked at it exactly 24 hrs ago.
>>>> When I replace the $current.outTemp with $yesterday.outTemp,  it
>>>> generates an error.
>>>> Any ideas?   Thanks--
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx...@googlegroups.com.
>>>> To view this discussion on the web visit
>>>> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> --
> 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/207b4e40-894c-42d2-88bc-9e1b4a31d7eb%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/207b4e40-894c-42d2-88bc-9e1b4a31d7eb%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zECr1e9QFZXR9N%3DGqHZHUN5gOtVCwOY_icxqs7sAhqyXXQ%40mail.gmail.com.

Re: [weewx-user] "yesterday.outTemp" compared to "current.outTemp", et seq, for Yesterday page

[Thomas Keffer]

The two tags serve different purposes. The tag $yesterday represents an
*aggregation* over the day. The tag $current represents a single record.
There is an undocumented feature in v3.9.2 (documented in V4.0) that gets
you what you want:

The temperature 24 hours ago was
$current(timestamp=$current.dateTime.raw-86400).outTemp


-tk

On Fri, Apr 17, 2020 at 7:01 AM Messy Potamia 
wrote:

> The high/low table is working, showing but I'd like to get the upper table
> in yesterday.html.tmpl  to show the data from 86400 seconds ago, or one
> day ago, $day($days_ago=1), or $yesterday.  This doesn't seem to be working.
> In otherwords, on my Yesterday page, (weewx 3.9.2 Standard skins) I'd like
> it to show the same data as if you looked at it exactly 24 hrs ago.
> When I replace the $current.outTemp with $yesterday.outTemp,  it generates
> an error.
> Any ideas?   Thanks--
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/571e351c-cbbc-446a-8cc5-e7e96fa95a42%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/CAPq0zEDKtRv2tsEURbDMMR7_qCitit8pWj7ufi8Qj4W6r60GYA%40mail.gmail.com.

Re: [weewx-user] wee_import CSV interval = 1 vs. archive_interval = 300?

[Thomas Keffer]

Hi, Bill.

1. WeeWX can handle mixed intervals.
2. The time, field dateTime, is indexed, so it does not slow down reports
as much as you think. My database is about 1.5 M records and it performs
fine on a very slow machine. The exception is queries that
involving finding the min and max of the whole database.
3. If you decide you want to consolidate into 5 minute intervals, user
Cameron came up with a guide that uses some clever SELECT statements to do
the job. Find it on the Wiki

.

-tk

On Thu, Apr 16, 2020 at 1:47 AM William Burton  wrote:

> Hello,
>
> I've been testing a CSV import configuration with wee_import. The CSV data
> is in 1 minute intervals whereas weewx.conf has an archive_interval = 300
> for 5 minutes. my csv.conf has interval = 1 to match the data interval
> (which has a few gaps).
>
> What I'm finding is the imported data is still in one minute intervals
> while data archived from the driver has five minute intervals:
>
> sqlite> select interval, count(*) count from archive group by interval;
> intervalcount
> --  --
> 1   51234
> 5   12259
>
>1. Will having mixed intervals in the same database cause any issues
>with reporting such as incorrect time scales in graphs?
>2. Wouldn't archive records with a one minute interval slow down
>report generation?
>3. I calculated that I have around 900 files to import for a total of
>almost 1.3 million records. If these records could be averaged to only one
>record per five minutes, then it would be only 260,000 records which seems
>more reasonable.
>
> I'm using WeeWX 4.0.0b18.
>
> Thanks for any assistance,
> -Bill
>
> --
> 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/0151a436-a259-4c12-be92-c20c5e796711%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/CAPq0zEBY_YioiXhkJ150C9YhQoRhFgYfzjEpkWKMf3%2BepM92uA%40mail.gmail.com.

Re: [weewx-user] Re: No Rain Data in WeeWx

[Thomas Keffer]

Glad to hear it!

On Wed, Apr 15, 2020 at 8:14 AM  wrote:

> Resetting totals cleared the issue. I reset. Put some water through the
> gauge, rain amounts on the device and weewx now agree.
>
> Thank you, very much.
>
> Scott
>
> Sent from my iPhone
>
> On Apr 15, 2020, at 6:52 AM, Thomas Keffer  wrote:
>
> 
> The field "rain" is the total amount of rain that fell during an archive
> interval. It is calculated as the difference in total rain between the
> beginning and end of the interval. So, if total_rain does not change, then
> the "rain" field will show zero.
>
> Is there a way to "reset" your station? It's possible the total rain
> counter has simply overflowed and, instead of wrapping around, it just
> stays at 0x.
>
> -tk
>
> On Tue, Apr 14, 2020 at 10:29 PM  wrote:
>
>> If I may ask one more question.
>>
>> Rain is showing 0.0 in the direct run but field 11 is today's rain total.
>> The value for that field in the serial debug is 30 30 44 41 or 0x00da or
>> 218 decimal (2.18) inches, yet WeeWx is reporting 0.0
>>
>>
>> Sent from my iPhone
>>
>> > On Apr 13, 2020, at 6:41 PM, Thomas Keffer  wrote:
>> >
>> > 46 46 46 46
>>
>> --
>> 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/88BCE192-3DF6-46B1-ADEA-2E0CD5BDAF8F%40gmail.com
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/cKVU1Ot8Tz0/unsubscribe.
> To unsubscribe from this group and all its topics, 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/CAPq0zEB4z%3DEf%3D735ZTQTdnKawPJ7SzzCc1PV3XC-tCtvyqNuLg%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEB4z%3DEf%3D735ZTQTdnKawPJ7SzzCc1PV3XC-tCtvyqNuLg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> --
> 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/28709EE1-9731-4D45-88DC-45AD8AA5AFDB%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/28709EE1-9731-4D45-88DC-45AD8AA5AFDB%40gmail.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEAtTguqz-Qom4vsOM4PESJg6b__Mfs-%2B79fFcv%2BfY1DFA%40mail.gmail.com.

Re: [weewx-user] Re: FTP Error uploading to website

[Thomas Keffer]

The RPi generally does not come with a copy of the client "ftp". However,
you can install it

sudo apt install ftp

-tk

On Wed, Apr 15, 2020 at 12:43 AM chris op  wrote:

> Can I edit my posts here?
>
> Thanks, Greg!
>
> I was able to connect to the ftp server and to place the correct
> index.html there. However, I connected from my linux ubuntu terminal. And
> after installing ftp on the raspberry I was also able to the same from
> there. The upload from weewx does still not work, unfortunaltey.
>
> Can you or anyone comment on the type of FTP errors I receive?
>
> Should I also be able to connect to the raspberry pi with shh and
> connect to the ftp server from there? Because when I try this I get the
> error message that the ftp command is unknown.
>
>
>
> Am Mittwoch, 15. April 2020 01:39:02 UTC+2 schrieb Greg from Oz:
>>
>> See if ftp works manually.
>>
>> from a terminal:
>>
>> ftp  sxyz.xyzserver.host
>>
>> when name prompt comes back enter in your user web83
>> then type in the password
>>
>> assuming this works type pwd to see what folder you are in
>>
>> change to /home/www/xyz.de by typing cd /home/www/xyz.de
>>
>> you can put a local file into /home/www/xyz.de by typing put > of a local file>
>>
>> or you can get files from /home/www/xyz.de by typing get > remote file>
>>
>> If all of that works then the weex in theory should work.
>> On Wednesday, 15 April 2020 02:06:06 UTC+10, chris op wrote:
>>>
>>> Hi!
>>>
>>> All was working fine with uploading the weewx weather data to my
>>> website. However, this suddenly stopped a couple of weeks ago. I was
>>> realizing one day, that the website was not updated anymore.
>>>
>>> Looking into the syslog what happens and I found the following errors:
>>> Apr 14 17:46:03 raspberrypi weewx[27105]: ftpupload: Attempt #1. Failed
>>> uploading /home/www/xyz.de/daywind.png to sxyz.xyzserver.host. Reason:
>>> 425 Unable to build data connection: Operation not permitted
>>> This changes during to process into:
>>> Apr 14 17:46:13 raspberrypi weewx[27105]: ftpupload: Attempt #3. Failed
>>> uploading /home/www/xyz.de/neowx/daywind.png to sxyz.xyzserver.host.
>>> Reason: 200 Type set to I
>>> or
>>> Apr 14 17:51:20 raspberrypi weewx[27105]: ftpupload: Attempt #1. Failed
>>> uploading /home/www/xyz.de/belchertown/graphs/index.html to
>>> sxyz.xyzserver.host. Reason: 550 /home/www/xyz.de/belchertown/graphs:
>>> File exists
>>>
>>> I have tried to play around in the file weewx.conf and changed the
>>> parameters there but this only led to other error messages like 550 or 500.
>>>
>>> My configuration looks as follows:
>>> >
>>> # FTP'ing the results to a webserver is treated as just another report,
>>> # albeit one with an unusual report generator!
>>> skin = Ftp
>>>
>>> # If you wish to use FTP, uncomment and fill out the next four
>>> lines.
>>> # Use quotes around passwords to guard against parsing errors.
>>> user = web83
>>>
>>> password = 'xyz'
>>> server = sxyz.xyzserver.host
>>> path = /home/www/xyz.de/
>>>
>>> # Set to True for an FTP over TLS (FTPS) connection. Not all
>>> servers
>>> # support this.
>>>  secure_ftp = True
>>>
>>> # To upload files from something other than what HTML_ROOT is set
>>> # to above, specify a different HTML_ROOT here.
>>> # HTML_ROOT = /var/www/html/weewx
>>>
>>> # Most FTP servers use port 21
>>> port = 21
>>>
>>> # Set to 1 to use passive mode, zero for active mode
>>> passive = 1
>>> >>
>>>
>>> Can anyone help? I am a rooky but trying hard to become better with
>>> linux and this kind of software and programming.
>>>
>>> Thank you!
>>>
>> --
> 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/a3397bc8-224a-41be-b85a-f0aa55aa73f0%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/CAPq0zEDPP6tneRsDgSAVKzKesdmhUU7z369cY%3DOSVZ_3UBSdsg%40mail.gmail.com.

Re: [weewx-user] Re: No Rain Data in WeeWx

[Thomas Keffer]

The field "rain" is the total amount of rain that fell during an archive
interval. It is calculated as the difference in total rain between the
beginning and end of the interval. So, if total_rain does not change, then
the "rain" field will show zero.

Is there a way to "reset" your station? It's possible the total rain
counter has simply overflowed and, instead of wrapping around, it just
stays at 0x.

-tk

On Tue, Apr 14, 2020 at 10:29 PM  wrote:

> If I may ask one more question.
>
> Rain is showing 0.0 in the direct run but field 11 is today's rain total.
> The value for that field in the serial debug is 30 30 44 41 or 0x00da or
> 218 decimal (2.18) inches, yet WeeWx is reporting 0.0
>
>
> Sent from my iPhone
>
> > On Apr 13, 2020, at 6:41 PM, Thomas Keffer  wrote:
> >
> > 46 46 46 46
>
> --
> 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/88BCE192-3DF6-46B1-ADEA-2E0CD5BDAF8F%40gmail.com
> .
>

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

Re: [weewx-user] Importing WLK files from Davis Instruments WeatherLink software

[Thomas Keffer]

That's great, Steve! The old way was to use a very out-of-date utility that
came with wview. Nice to have something more modern.

Could you make an entry in the wiki 
about your app?

-tk

On Tue, Apr 14, 2020 at 3:24 PM Steve Preston  wrote:

> This is just a FYI for the group.  After using WeatherLink for 15+ years,
> I have finally switched to WeeWx!
>
> I wrote a basic Windows app for converting the WLK files into CSV format
> for importing the data into WeeWx.  This app is pretty basic - no real data
> checks and no attempt to adjust for differences in the archive interval (my
> station was already logging at 5 minute intervals).  And it is setup to
> import one month at a time: reads one *.wlk file and writes one *.csv
> file.  But I've moved over a few years of data to WeeWx without any
> problems (so far).  The app is written in C# with visual studio and I'm
> happy to share code and/or executables.
>
> Steve
>
> --
> 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/6d172d9f-d0f1-422c-9af2-31ed1c47d12f%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/CAPq0zEC9tNBK6rNZ90PTW30jq6-UH7-1b2Xntb-AW_G%2BedZ%2BSQ%40mail.gmail.com.

Re: [weewx-user] Re: No Rain Data in WeeWx

[Thomas Keffer]

The debug serial line you included is:

Apr 12 17:53:05 raspberrypi weewx[5222]: ultimeter: station said: 21 21 30
30 35 46 30 30 33 32 30 32 32 39 46 46 46 46 32 37 30 34 30 32 46 37 30 33
41 30 2D 2D 2D 2D 30 30 36 36 30 33 46 35 30 30 44 41 30 30 30 30 0D 0A

These are hexadecimal values coded in ASCII. The part for "long-term rain"
is highlighted.

The ASCII values "46 46 46 46", is "F F F F", or hex 0x, or decimal
65535. Scaled by 0.01" per count, that gives 655.35.

I don't know why your Ultimeter is emitting 0x for total rain. Perhaps
Peet Bros can answer that?

-tk


On Sun, Apr 12, 2020 at 7:42 PM Scott Gray  wrote:

> Gary,
>
> I have not found a solution, but I have taken the additional steps.
> Attached is the syslog after debug serial was enabled, a screenshot of the
> results of direct run of weewx, and a photo of the rain display of the
> station.
>
> The display is showing 2.23in total for the day.
>
> The direct run shows rain: 0.0 and rain_total:655.35
>
> The debug serial shows the following returns from the station:
>
> Apr 12 17:53:05 raspberrypi weewx[5222]: ultimeter: station said: 21 21 30
> 30 35 46 30 30 33 32 30 32 32 39 46 46 46 46 32 37 30 34 30 32 46 37 30 33
> 41 30 2D 2D 2D 2D 30 30 36 36 30 33 46 35 30 30 44 41 30 30 30 30 0D 0A
> Apr 12 17:53:06 raspberrypi weewx[5222]: ultimeter: station said: 21 21 30
> 30 35 46 30 30 33 32 30 32 32 39 46 46 46 46 32 37 30 34 30 32 46 37 30 33
> 41 30 2D 2D 2D 2D 30 30 36 36 30 33 46 35 30 30 44 41 30 30 30 30 0D 0A
> Apr 12 17:53:07 raspberrypi weewx[5222]: ultimeter: station said: 21 21 30
> 30 35 45 30 30 35 33 30 32 32 39 46 46 46 46 32 37 30 34 30 32 46 37 30 33
> 41 30 2D 2D 2D 2D 30 30 36 36 30 33 46 35 30 30 44 41 30 30 30 30 0D 0A
> Apr 12 17:53:08 raspberrypi weewx[5222]: ultimeter: station said: 21 21 30
> 30 35 45 30 30 35 33 30 32 32 39 46 46 46 46 32 37 30 34 30 32 46 37 30 33
> 41 30 2D 2D 2D 2D 30 30 36 36 30 33 46 35 30 30 44 41 30 30 30 30 0D 0A
>
> I am goign to check with Peet to see if they have any clues, but the
> station is in the Data Logger mode, as it should be. I have not updated the
> station, and this was working earlier.  I cannot say with certainty that it
> worked on version 3.9.2. It worked previously for a long period of time,
> but my raspbian os corrupted and I rebuilt the device and reinstalled.
>
> Would anything in the Ultimeter driver have changed in the latest build?
>
>
>
>
> On Tuesday, March 10, 2020 at 9:21:05 PM UTC-5, gjr80 wrote:
>>
>> Hi,
>>
>> I have no experience with the ultimeter so can offer no help with the
>> hardware. You mention an error in the log, do you mean this:
>>
>> Feb 27 07:05:17 raspberrypi weewx[11354]: ultimeter: Failed attempt 1 of
>> 5 to get readings: Unexpected buffer length 59
>>
>> If so I don't believe it will be the cause, I only saw the failure on
>> attempt 1 of 5 to get the readings, on the face of it it woudl appear that
>> attempt 2 of 5 worked (or another fail wouls have been logged).
>>
>> About all I can suggest is enabling the serial debug option in the
>> ultimeter driver, that will log the raw data the driver obtains from your
>> station, not sure what that will show and it may take a bit of decoding. If
>> there is no rain data there then the driver won't be passing anything on to
>> WeeWX. To enable serial debug edit wewx.conf, locate the [Ultimeter]
>> stanza and add the option debug_serial = 1. It shoudl look something
>> like:
>>
>> [Ultimeter]
>>
>> 
>> debug_serial = 1
>> 
>>
>> Also make sure you keep debug = 1. Save weewx.conf and restart WeeWX.
>> Have a look at the log and see what data is being logged from your station?
>> what shows when its raining?
>>
>> You could also try running WeeWX directly
>>  when itis
>> raining, that will show you the loop and archive data that WeeWX is seeing,
>> though if WeeWX is notreporting any rain there may well be no rain data
>> there.
>>
>> Gary
>>
>>
>> On Wednesday, 11 March 2020 00:45:10 UTC+10, Scott Gray wrote:
>>>
>>> Is anyone able to offer any assistance?
>>>
>>> On Friday, March 6, 2020 at 9:50:10 PM UTC-6, Scott Gray wrote:

 I am running weewx 3.9.2 on a Raspberry Pi. I have a Peet Bro’s.
 Ultimeter 2000. It has stopped sending, or weewx has stopped reporting my
 rain data. It did show a while back, but then stopped reporting to
 Wunderground. It is also not showing on local index.html page.it shows
 all other data, temp, wind, barometric pressure, and humidity.

 The head unit shows rain totals for the day, for instance today .6 inch

 I have the Ultimeter set to send the data in “data logging” mode.

 Has anyone encountered this? Any suggestions for solutions or further
 troubleshooting?

 I have been running in debug mode. I have attached some logs from a
 period of time in which we did have rain and rain amount was shown on
 weather 

Re: [weewx-user] Simplest method to read in an external data element and apply it to an existing Archive type

[Thomas Keffer]

I see.

The schema is only used when the database is *created*. So, if you're using
an existing database, it doesn't matter what you put there.

If you do not have an existing database, then it will be used. However,
because you're using a type that's already in the wview schema, leafTemp1,
then there is no need to add a new type. Personally, if I didn't have an
existing database, I would add the new type: it's easier to tell what that
observation type is, rather than remembering that leafTemp1 is actually,
say, "tank level."

Where it is really useful to recycle a name such as leafTemp1 is if you
have an existing database and you don't want  to go to the trouble of
rebuilding it with a new type. Then reusing a name is a lot easier.

Hope that's clear.

-tk


On Mon, Apr 13, 2020 at 6:51 AM Messy Potamia 
wrote:

> I didn't have any problem reading the data in via my existing python code
> (although I suspect your sample may be cleaner, I'll try that too).
> What I was concerned with is the schema ***  =  schema *** + schema ***.
> Since I'm not extending this schema, I commented out that line. Added the
> service to weewx.conf, restarted weewx w/ debug=1, saw it add the service
> (and now the new .pyc exists in user), and it's reading the data into
> weewx.sdb.  Now it's a simple matter of editing my skins to add the
> parameter.
> Thanks  --Phil
>
> On Monday, April 13, 2020 at 2:42:05 PM UTC+2, Thomas Keffer wrote:
>>
>> You want something like:
>>
>> with open('/path/to/file') as f:
>> value = f.readline().strip()
>> event.record['leafTemp1'] = float(value) if value != '' else None
>>
>> Or, use filepile <https://github.com/tkeffer/filepile>, although that
>> would require you to change the format of your data file.
>>
>> -tk
>>
>> On Mon, Apr 13, 2020 at 4:35 AM Messy Potamia 
>> wrote:
>>
>>> I want to read in a single %2.2f  from a file "special.dat" and store it
>>> in something I'll never otherwise use, "leafTemp1".
>>>
>>> My weewx is 3.6.2.  I have read the suggestion to use a 2nd database,
>>> however I do not want to do that. I have written a custom .py before to
>>> read data from a 2-element data file, but I extended the schema to do that
>>> (and I remember Tom asking why, and it was because I thought that was the
>>> thing to do, anyway I don't want to do that this time)
>>>
>>> pi@RPI3:~ $ cat /home/weewx/special.dat
>>> 32.67
>>> pi@RPI3:~ $
>>>
>>> Here is the python I copied & modified a few years ago, which works for
>>> that system:
>>> #!/usr/bin/env python
>>>
>>> #file user/lakedata.py
>>> import weewx
>>> from weewx.engine import StdService
>>>
>>> class AddLakedata(StdService):
>>>
>>> def __init__(self, engine, config_dict):
>>>   # Initialize my superclass first:
>>>   super(AddLakedata, self).__init__(engine, config_dict)
>>>   # Bind to any new archive record events:
>>>   self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_packet)
>>>
>>> def new_archive_packet(self, event):
>>>
>>> #(code that reads two measurements from a file)
>>> with open("/mnt/wxdata/weewxmbdata.dat") as f:
>>> for line in f:
>>> numbers_str = line.split()
>>> numbers_float = [float(x) for x in numbers_str]
>>> value1 = numbers_float[0]
>>> value2 = numbers_float[1]
>>>
>>> event.record['lakeElevation'] = value1
>>> event.record['lakeWaveheight'] = value2
>>>
>>> import schemas.wview
>>> schema_with_lakedata = schemas.wview.schema + [('lakeElevation', 'REAL'
>>> )] + [('lakeWaveheight', 'REAL')] + [('lightning', 'REAL')]
>>>
>>> #
>>>
>>> The above code works fine on a previous installation and I'm not going
>>> to mess with it. This install however, I will be reading a single value,
>>> and applying it into an existing field in the default existing database. My
>>> concern is, in the above lakedata.py, which represents an extended schema,
>>> what changes when I'm using the existing schema?
>>>
>>> Thanks for clarifying this for me.
>>>
>>> Phil
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe f

Re: [weewx-user] Simplest method to read in an external data element and apply it to an existing Archive type

[Thomas Keffer]

You want something like:

with open('/path/to/file') as f:
value = f.readline().strip()
event.record['leafTemp1'] = float(value) if value != '' else None

Or, use filepile , although that would
require you to change the format of your data file.

-tk

On Mon, Apr 13, 2020 at 4:35 AM Messy Potamia 
wrote:

> I want to read in a single %2.2f  from a file "special.dat" and store it
> in something I'll never otherwise use, "leafTemp1".
>
> My weewx is 3.6.2.  I have read the suggestion to use a 2nd database,
> however I do not want to do that. I have written a custom .py before to
> read data from a 2-element data file, but I extended the schema to do that
> (and I remember Tom asking why, and it was because I thought that was the
> thing to do, anyway I don't want to do that this time)
>
> pi@RPI3:~ $ cat /home/weewx/special.dat
> 32.67
> pi@RPI3:~ $
>
> Here is the python I copied & modified a few years ago, which works for
> that system:
> #!/usr/bin/env python
>
> #file user/lakedata.py
> import weewx
> from weewx.engine import StdService
>
> class AddLakedata(StdService):
>
> def __init__(self, engine, config_dict):
>   # Initialize my superclass first:
>   super(AddLakedata, self).__init__(engine, config_dict)
>   # Bind to any new archive record events:
>   self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_packet)
>
> def new_archive_packet(self, event):
>
> #(code that reads two measurements from a file)
> with open("/mnt/wxdata/weewxmbdata.dat") as f:
> for line in f:
> numbers_str = line.split()
> numbers_float = [float(x) for x in numbers_str]
> value1 = numbers_float[0]
> value2 = numbers_float[1]
>
> event.record['lakeElevation'] = value1
> event.record['lakeWaveheight'] = value2
>
> import schemas.wview
> schema_with_lakedata = schemas.wview.schema + [('lakeElevation', 'REAL')]
> + [('lakeWaveheight', 'REAL')] + [('lightning', 'REAL')]
>
> #
>
> The above code works fine on a previous installation and I'm not going to
> mess with it. This install however, I will be reading a single value, and
> applying it into an existing field in the default existing database. My
> concern is, in the above lakedata.py, which represents an extended schema,
> what changes when I'm using the existing schema?
>
> Thanks for clarifying this for me.
>
> Phil
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a7495c2d-f450-46cf-a88f-c75e696f1940%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/CAPq0zEAszDV87q37CTGrcTF%3DScm0YQube%2BdqkdY86wLFH_6dqw%40mail.gmail.com.

Re: [weewx-user] Too many NOAA reports

[Thomas Keffer]

I'm not familiar with the Belchertown skin, but if it works like other
skins, the NOAA reports are generated from the earliest timestamp in the
database to the last timestamp.

So, you must have a very early timestamp in your database.

-tk

On Sun, Apr 12, 2020 at 7:46 AM Duncan Wilson  wrote:

> My NOAA reports have been running fine since Feb 2017 but I also have
> empty records going back to Jan 2000. I have looked all through the forums
> and .conf files and cannot find where the years to run to generate the
> files are being set. Any suggestions on where to look?
>
> Weewx 3.9.1 and Belchertown 1.0.1
>
> http://drdunc.duckdns.org/weewx/reports/
>
> Thanks!
> Duncan]
>
> London, UK
>
> --
> 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/3b0de916-431c-4547-a797-53153a10584d%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/CAPq0zEBEBmTjSEiQ-4uQvQcYzDU0n3b9fP%2BuHZ0DsySqp%2B%3DkaQ%40mail.gmail.com.

Re: [weewx-user] Future date/times into database resulting in loss of data

[Thomas Keffer]

Hi, Ken

Problem #1 is almost surely a hardware problem. Have you put ferrite coils
around the cable from your logger to the computer? A UPS also helps. If you
are still getting random corruption in the logger memory, then the logger
may be defective.

Problem #2: a graphic is regenerated only as often as its aggregation
interval. For example, if a month plot uses a 3 hour aggregation interval,
then it will be regenerated only after it is 3 hours old. To force
regeneration, delete the graphic.

-tk

On Thu, Apr 9, 2020 at 11:05 AM Ken Waters  wrote:

> Hello,
>
> Sorry if this seems long but I tried to put everything in here that might
> help explain the situation.
>
> Here is my setup:
>   Weewx version: 3.9.2
>   Weather station: Davis Vantage Pro 2 connected thru DB9 serial port
>   Hardware: HP Pro 6000 SFF dual Pentium RAM: 4 GB, WD 1 TB drive
> (currently only 2% usage)
>   O/S: Ubuntu 18.04.4 LTS
>   Website: http://satwatcher.us/satwatcher.us/wxstation/
>
> I've been running WeeWx for about 9-10 years and previously used WxView.
>
> Here is the problem:
>
> Periodically and randomly the SQLite database gets corrupted with the most
> recent update showing a future day/time. There seems to be no obvious
> trigger that causes this and it's been happening to me for several years
> including with other hardware setups. When this happens it basically
> "locks" up the database so that current observations can no longer be
> stored and results in a loss of data after the database corruption. In the
> past I have had to resort to:
>
>   a) stopping the service
>   b) clearing the memory (sudo /usr/share/weewx/wee_device -y
> --clear-memory)
>   c) renaming the .sdb
>   d) restarting the service
>
> in effect, starting with a new database.  This has been happening every
> 2-4 weeks randomly and not as a result of anything done by me to the server.
>
> Here is a sample snippet from syslog that shows the issue:
>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Getting
> archive packets since 2020-04-09 07:37:00 MST (1586443020)
>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Gentle wake up
> of console successful
>   Apr  9 07:38:15 WeewxWeatherServer weewx[28253]: vantage: Retrieving 1
> page(s); starting index= 0
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: manager: Added record
> 2020-04-22 23:06:00 MST (1587621960) to database 'weewx.sdb'
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: manager: Added record
> 2020-04-22 23:06:00 MST (1587621960) to daily summary in 'weewx.sdb'
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: *vantage: DMPAFT
> complete: page timestamp 2020-04-07 12:59:00 MST (1586289540) less than
> final timestamp 2020-04-22 23:06:00 MST (1587621960)*
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: vantage: Catch up
> complete.
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: vantage: Requesting 200
> LOOP packets.
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Running
> reports for latest time in the database.
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Running
> report 'SeasonsReport'
>   Apr  9 07:38:16 WeewxWeatherServer weewx[28253]: reportengine: Found
> configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
>
> Here is output captured this morning from a sqlite3 select command that
> shows the erroneous timestamp in the database:
>
>   $ sqlite3 /var/lib/weewx/weewx.sdb "select
> datetime(dateTime,'unixepoch','localtime') from archive where
> dateTime>155;"
>   2020-04-09 07:30:00
>   2020-04-09 07:31:00
>   2020-04-09 07:32:00
>   2020-04-09 07:33:00
>   2020-04-09 07:34:00
>   2020-04-09 07:35:00
>   2020-04-09 07:36:00
>   2020-04-09 07:37:00
>   *2020-04-22 23:06:00* <<< erroneous future entry
>
> These date/times are local MST (Z-7) and the problem actually occurred at
> 2306 MST last night resulting in loss of data for about 8 hours.  It seems
> as if WeeWx is skipping recording the observation because it thinks this is
> an old observation due to the last entry being "newer".
>
> Problem #2:
> In addition, after stopping, clearing, removing the .sdb, and restarting I
> now see that the graphics being produced are not current and are
> time-stamped 4/22/2029 23:06 although the data on the left-side of the page
> at http://satwatcher.us/satwatcher.us/wxstation/ are current.  Why are
> the graphics still keying off the erroneous time in the future?
>
> This has been driving me nuts for several years now.  Does anybody have
> any idea what may be causing this and how to fix it so it no longer happens?
>
> Thank you ever so much!
>
> (ps...I did post something to the list back in 2015 about this but it was
> not resolved at the time)
>
> Ken
>
>
> --
> 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 

Re: [weewx-user] Auto refresh page.

[Thomas Keffer]

If the Refresh meta directive is in your template, but it's not appearing
in the corresponding generated HTML page, then either the page is not
actually getting regenerated, or you're looking at the wrong page.

You will have to post the log. See the Wiki article *Help!
* on how
to get a good log.

On Wed, Apr 8, 2020 at 5:58 AM Richard Whittaker 
wrote:

> Hi all.
>
> I realize this may have been covered before, and I have, I believe
> followed the instructions, but auto refresh isn't working, and I don't see
> the refresh string in the page source.
>
> My /etc/weewx/skins/Standard/index.html.tmpl  upper section looks
> like this:
>
>   
> ## This choice should match the #encoding directive above
> 
> 
> ... (more stuff)
>
>
> Have tried reloading weewx, confirmed the pages are being regenerated, and
> am kinda at a loss.
>
> My index.html header looks like this:
>
>   
> 
> Noel Shore, Nova Scotia, Canada
> ... (more stuff)
> 
>
> Thanks in advance
> Richard.
>
> --
> 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/76aab4c3-9543-4aef-9a8f-a8628a413648%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/CAPq0zEBtpByUEButBSm2i09aNoYq7Y6fSiZvteTeu11%2BeCwjEQ%40mail.gmail.com.

Re: [weewx-user] Get average or previous value?

[Thomas Keffer]

Hello, Jens

Unfortunately, no, the StdQC service can only detect out of bounds, not big
changes or spikes. You would have to modify it, or write your own service
to do that.

On Tue, Apr 7, 2020 at 6:28 AM 'Jens-Jørgen Kjærgaard' via weewx-user <
weewx-user@googlegroups.com> wrote:

> I have been a user for many years, and the software is usually running
> smoothly.
> Some years back, I added the temperature of my lake as extraTemp1 - also
> fine.
> Now, I also monitor the water level, by means of ultrasound, using the
> HC-SR04. I have added this as extraTemp2, and don't min it shows as C in
> the graphs.
> I have a little problem with that sensor, though. Sometimes it will show a
> far off reading, which has to be ignored, ie if it is more than 2 cm off
> the previous reading.
> But I can't figure out how to do that. Is there a way to store the
> previous reading and use that (temporarily) for comparison? Or the average
> of the readings up to that point?
>
> Jens-Jørgen Kjærgaard
> Tuenvej 818
> 9870 Sindal
> Denmark
> +45 21204417
> www.jensjk.dk
>
> --
> 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/CAJPduSSUyb7_XSAPyXs-dSJkbfVzsZUmDJVpbgamFVw%3DkL00hg%40mail.gmail.com
> 
> .
>

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

Re: [weewx-user] Re: weewx beta version 4.0.0b18

[Thomas Keffer]

Either way of specifying a schema should work with V4. If it's not, that's
a bug.

On Tue, Apr 7, 2020 at 6:36 AM gjr80  wrote:

> V4 actually uses the wview_extended schema which is specified in a
> slightly different format to that used in V3. Pat's instructions are V3
> specific. Try using the following as the step 2 code (untested):
>
> import schemas.wview_extended
>
> schema_extended = {'table': schemas.wview_extended.table + [('appTemp',
> 'REAL'), ('windrun', 'REAL')],
>'day_summaries' : schemas.wview_extended.day_summaries}
>
> Other steps should be fine as is.
>
> Gary
>
> On Tuesday, 7 April 2020 22:55:07 UTC+10, Phil Owers wrote:
>>
>> Hi Guys
>> With Garys help with getting a gauge-data.txt file to generate I decided
>> to try the next step (Logs were all clear) and add 'appTemp' and 'windrun'
>> using Pat O Brien ADDING A NEW OBSERVATION TYPE TO THE WEEWX DATABASE
>> I did this on 3.9.2 and it worked fine but on 4.0.0b18 and after using
>> wee_databse --rebuild- daily which was successful
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: Generate failed with exception '> folowing loNameMapper.NotFound'>'
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Ignoring template
>> /home/weewx/skins/Seasons/NOAA/NOAA-%Y-%m.txt.tmpl
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Reason: cannot find 'count' while searching
>> for 'day.wind.count.raw'
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   unicode_string =
>> compiled_template.respond()
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "_home_weewx_skins_Seasons_NOAA_NOAA__Y__m_txt_tmpl.py", line 431, in
>> respond
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   NameMapper.NotFound: cannot find 'count'
>> while searching for 'day.wind.count.raw'
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: Generate failed with exception '> 'NameMapper.NotFound'>'
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Ignoring template
>> /home/weewx/skins/Seasons/NOAA/NOAA-%Y.txt.tmpl
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Reason: cannot find 'count' while searching
>> for 'month.wind.count.raw'
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   unicode_string =
>> compiled_template.respond()
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "_home_weewx_skins_Seasons_NOAA_NOAA__Y_txt_tmpl.py", line 862, in respond
>> Apr  7 13:38:09 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   NameMapper.NotFound: cannot find 'count'
>> while searching for 'month.wind.count.raw'
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: Generate failed with exception '> 'NameMapper.NotFound'>'
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Ignoring template
>> /home/weewx/skins/Seasons/rss.xml.tmpl
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:  Reason: cannot find 'max' while searching for
>> 'day.wind.max'
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 322, in generate
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   unicode_string =
>> compiled_template.respond()
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator: File
>> "_home_weewx_skins_Seasons_rss_xml_tmpl.py", line 268, in respond
>> Apr  7 13:38:11 raspberrypi wee_reports[974] ERROR
>> weewx.cheetahgenerator:   NameMapper.NotFound: cannot find 'max' while
>> searching for 'day.wind.max'
>> Apr  7 13:38:11 raspberrypi wee_reports[974] INFO weewx.cheetahgenerator:
>> Generated 5 files for report SeasonsReport in 2.74 seconds
>> Apr  7 13:38:15 raspberrypi wee_reports[974] INFO weewx.imagegenerator:
>> Generated 30 images for report SeasonsReport in 3.64 seconds
>> Apr  7 13:38:15 raspberrypi 

Re: [weewx-user] Alltime/ skins

[Thomas Keffer]

You actually already have it! It's located in your examples subdirectory,
file /usr/share/doc/weewx/examples/stats.py. Documentation is in the
section *Extending the list
* in the
Customization Guide.

On Tue, Apr 7, 2020 at 2:57 AM 'Richard O' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi
>
> There was an extension piece of software, a few years back,  for the
> standard skin that could be downloaded from Sourceforge that would give the
> alltime stats ie the highs and lows since the software had been running. It
> does not seem available these days from my research but believe the command
> was tar xvf alltime-skin-0.0.1.tgz.
>
> Does anyone know if this still works or has been updated as there seems to
> be no trace of it?
>
>  I think it is an attractive and fun feature to have and see that
> meteobridge do all sorts of stats like this. Whilst I do not have any
> intention of changing I wondered if anyone perhaps, in the absence of the
> software, knows a way round this apart from designing it all myself. Is
> there an available skin that would give longer term stats for instance?
>
> many thanks Richard
>
> --
> 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/21b23111-6099-49e8-a638-5dceb834d34e%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/CAPq0zEBPD9sAZ8nh8Zq%2BXe3_8qHuYS1B8rmA%2B0dgZAYVz%2B5ANA%40mail.gmail.com.

Re: [weewx-user] Re: weewx beta version 4.0.0b18

[Thomas Keffer]

Gary,

Makes sense.

To gather data for a plot, version 3.9 called Manager.getSqlVectors(),
which hit the database. Only types that appear in the database schema can
be plotted. Because many databases are case-insensitive, rainRate and
rainrate are treated the same, so it works.

By contrast, version 4.0 calls weewx.xtypes.get_series(). This function
allows new types to be introduced, which are not necessarily in the
database. If no extension has been registered that knows how to deal with a
type, then xtypes consults the schema. If the type is not in there, an
exception weewx.UnknownType is raised. The schema consultation is done in
Python in a case-sensitive manner, so rainrate and rainRate are different.

This explains the difference in behavior.

-tk



On Mon, Apr 6, 2020 at 6:27 PM gjr80  wrote:

> Well looking into the rainrate/rainRate issue has been most interesting.
> First up rainrate has been used in skin.conf for the rain rate plot as
> follows since the SteelSeries Weather Gauges first directly supported WeeWX:
>
>[[images]]
>x_label_format = %H:%M
>show_daynight = true
>[[[daybarometer]]]
>barometer
>[[[dayrain]]]
>yscale = None, None, 0.02
>plot_type = bar
>rain
>aggregate_type = sum
>aggregate_interval = 3600
>label = Rain (hourly total)
> [[[dayrainrate]]]
> rainrate
>
> But why has this never caused a problem or been noticed before? I think
> the way in which plot data is obtained and the introduction of xtypes holds
> the answer. Before WeeWX v4 plot data was obtained via a call to
> manager.getSqlVectors() which itself is encapsulated in a try...finally
> statement. The result being that any error (for example a non-existant obs
> type) was effectively swallowed and no data returned by
> manager.getSqlVectors(). The image generator would then plot this
> non-data which resulted in a plot devoid of data. Given that rain rate
> plots are seldom looked at, quite often show no data, and also as this plot
> was only used as a mouseover on the SteelSeries rain rate gauge, it is not
> surprising it's lack of data was never noticed. Now consider the new xtypes
> regime, plot data now comes from xtypes and if my xtypes understanding is
> correct, the xtypes are searched until one is found that can return the
> required data. In this case no xtype can return data for field rainrate
> which results in a weewx.UnknownType error which is highlighted in the
> log and painfully obvious to the user.
>
> Of course the fix is simple, replace rainrate with the correct field
> rainRate. This then got me wondering about the $hour.rain.sum.raw issue.
> I am still convinced this is tied to an underlying lack of rain data for at
> least one full hour in the day. My testing yesterday showed the
> gauge-data.txt template would handle such a lack of rain data without
> problem, which is counter to Phil's experience. But I was running under
> WeeWX 3.9.2 which does not use xtypes, I am now thinking there is a subtle
> difference in the data returned by xtypes in some corner cases. So far my
> understanding of xtypes has been fairly limited to just what I have needed
> to bget by in working on WeeWX 4.0 (which has not been much). Clearly I
> have a bit more reading to do (@tkeffer - warning there will be some xtypes
> questions inbound) and I will spend some time today seeing if I can
> replicate the issue.
>
> Gary
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/cf119004-27b4-4415-9c93-cc823bee6c75%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/CAPq0zEBTmd%2B9%3DEnS0h7fpyFbHubQcFujVvtaidnCgocJpzOGGQ%40mail.gmail.com.

Re: [weewx-user] Re: weewx beta version 4.0.0b18

[Thomas Keffer]

As far as weewx is concerned, it's always been rainRate.

I don't know how Steelgauges works, but it's possible it's only used in
case-insensitive database queries.

-tk

On Mon, Apr 6, 2020 at 8:12 AM Phil Owers  wrote:

> This is interesting
> I have a pi running 3.9.2 (Python2) which runs OK with rainrate
> (Steelgauges 2.7.4) ( yes all lower case)
>
> But on a pi running v4.0.0.b18 (Python3) with Steelgauges 2.7.4 rainrate
> generates an error in the log which is corrected if its changed to rainRate.
>
> Phil
>
>
>
> On Saturday, April 4, 2020 at 10:40:41 AM UTC+1, Phil Owers wrote:
>>
>> Hi Guys
>>
>> First of all I hope everybody is staying safe and well
>>
>> Before I go into to many details  should weewx v4.0.0b18 work on its own.
>>
>> Followed the Installation using setup.py, loaded all the prerequisites
>> for Debian 10(Buster)
>> Installed using python3 ./setup.py build  , sudo python3 ./setup.py
>> install
>>
>> Entered the name, vantage (6), serial , metric, ttyusb0  etc.
>>
>> Then started weewx using sudo ./bin/weewx
>> It downloaded all the data from my test console (This works fine plug
>> into another rasp pi v 3.9.2) then failed continuously overnight with no
>> graphs being generated.
>> The weewx.sdb was generated.
>>
>> Apr  4 10:22:20 raspberrypi weewx[1030] INFO weewx.manager: Starting
>> backfill of daily summaries
>> Apr  4 10:22:22 raspberrypi weewx[1030] INFO weewx.engine: Starting main
>> packet loop.
>> Apr  4 10:22:26 raspberrypi weewx[1030] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: Caught
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Traceback (most recent call last):
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "./bin/weewxd", line 154, in main
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> engine.run()
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 191, in run
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> callback(event)
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 740, in new_loop_packet
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> to_sorted_string(event.packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Waiting 10 seconds then retrying...
>> Apr  4 10:22:28 raspberrypi kernel: [38075.324656] usb 1-1.3: new
>> high-speed USB device number 6 using xhci_hcd
>>
>> No extensions have been added . Apologies if Ive jumped the gun and this
>> doesn't work yet as a standalone
>> Phil
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/8720d1b3-1d3f-4c78-9aec-5896b1b0e63e%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/CAPq0zEBL528s6%3D1SodmDsHQGDbMLW8h4aq-P3J7OaxKVfZumEQ%40mail.gmail.com.

Re: [weewx-user] Re: weewx beta version 4.0.0b18

[Thomas Keffer]

As Gary noted, it's rainRate, not rainrate. Case matters.

-tk

On Mon, Apr 6, 2020 at 6:44 AM Phil Owers  wrote:

> Here is the log
>
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine: Caught
> unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   rainrate
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   Traceback (most recent call last):
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/reportengine.py", line 197, in run
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   obj.start()
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/reportengine.py", line 280, in start
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   self.run()
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/imagegenerator.py", line 41, in run
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   self.genImages(self.gen_ts)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/imagegenerator.py", line 180, in
> genImages
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   aggregate_interval=aggregate_interval)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/xtypes.py", line 91, in get_series
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   raise weewx.UnknownType(obs_type)
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   weewx.UnknownType: rainrate
> Apr  6 14:40:17 raspberrypi weewx[612] ERROR weewx.reportengine:
>   Generator terminated
>
> On Saturday, April 4, 2020 at 10:40:41 AM UTC+1, Phil Owers wrote:
>>
>> Hi Guys
>>
>> First of all I hope everybody is staying safe and well
>>
>> Before I go into to many details  should weewx v4.0.0b18 work on its own.
>>
>> Followed the Installation using setup.py, loaded all the prerequisites
>> for Debian 10(Buster)
>> Installed using python3 ./setup.py build  , sudo python3 ./setup.py
>> install
>>
>> Entered the name, vantage (6), serial , metric, ttyusb0  etc.
>>
>> Then started weewx using sudo ./bin/weewx
>> It downloaded all the data from my test console (This works fine plug
>> into another rasp pi v 3.9.2) then failed continuously overnight with no
>> graphs being generated.
>> The weewx.sdb was generated.
>>
>> Apr  4 10:22:20 raspberrypi weewx[1030] INFO weewx.manager: Starting
>> backfill of daily summaries
>> Apr  4 10:22:22 raspberrypi weewx[1030] INFO weewx.engine: Starting main
>> packet loop.
>> Apr  4 10:22:26 raspberrypi weewx[1030] INFO weewx.engine: Main loop
>> exiting. Shutting engine down.
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: Caught
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Traceback (most recent call last):
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "./bin/weewxd", line 154, in main
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> engine.run()
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 191, in run
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> callback(event)
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> File "/home/weewx/bin/weewx/engine.py", line 740, in new_loop_packet
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> to_sorted_string(event.packet))
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> OSError: [Errno 5] Input/output error
>> Apr  4 10:22:26 raspberrypi weewx[1030] CRITICAL __main__: 
>> Waiting 10 seconds then retrying...
>> Apr  4 10:22:28 raspberrypi kernel: [38075.324656] usb 1-1.3: new
>> high-speed USB device number 6 using xhci_hcd
>>
>> No extensions have been added . Apologies if Ive jumped the gun and this
>> doesn't work yet as a standalone
>> Phil
>>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a1fd90ae-45c5-42f7-a2a5-f4eb7a96f6cb%40googlegroups.com
> 

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Thomas Keffer]

With all respect Steve, but what did you pay for the Dark Sky API services?
It was certainly a nice service, but they don't owe us anything.

And I, for one, am a very happy Apple customer.



On Sun, Apr 5, 2020 at 9:24 AM Steve2Q  wrote:

> I have been using Darksky for over a year now and have an API which is
> linked to my SteelGuages. It has always given me quite accurate results.
> Today I received notice that "Darksky is now part of Apple". The app will
> now continue on my Android phone till July 1, 2020, and the API will
> function through the end of 2021.I do not now nor will I ever use anything
> tied to Apple..but I dont want to get into that now! I am sure the
> developers of Darksky walked away with a boat load of cash...so Apple and
> Darksky...FU!
>
> --
> 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/b982e3e4-20a8-437f-9c6c-f74ed05fd7e5%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/CAPq0zEDQBE-y%2BChCWuHcxP6pmK9VRvbW38KHjx6OLGh5x5tYaQ%40mail.gmail.com.

Re: [weewx-user] Modifying pyephem Date format on Celestial page?

[Thomas Keffer]

Hello, Pete

See section [[TimeFormats]]
 in the
Customizing Guide. In particular, options ephem_day and ephem_year.

On Fri, Apr 3, 2020 at 9:38 AM pbartko  wrote:

> Longtime weewx user, but just reinstalled weewx 3.9.2 on Raspberry pi due
> to hardware failure on my previous server.  I'm using the Seasons skin and
> installed pyephem.
>
> Everything is working well, but I can not figure out one thing.  How to
> change the date format of the Solstice, Equinox, Full moon and New moon?
> I'm in the US and we always try to be confusing by having things like our
> dates different the the rest of the world.  I'd like the those dates to be
> in MM/DD/ format instead of DD/MM/ format.  I was able to modify
> the report generator and image generator to change the date formats, but
> I'm stumped with the Celestial data from pyephem.
>
> site is here: http://www.boxhillweather.com
>
>
> Thanks
>
> Pete
>
> --
> 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/4e1f9a72-b163-4293-ae33-9c14c6da7751%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/CAPq0zEA5sKchP%2BvoS2wNggLORFEL3WJVbmAFhKRABNOP1knXBQ%40mail.gmail.com.

Re: [weewx-user] Davis Vantage Problem

[Thomas Keffer]

Things to try:

1. It's possible the the logger was disturbed when you replaced the
batteries. Try reseating it in the Envoy.

2. Your symptoms don't quite fit the usual pattern of corrupt memory, but
it's worth trying to clear the memory of the logger anyway. Follow the
directions under Corrupt station memory

to
clear the memory.

-tk


On Thu, Apr 2, 2020 at 2:35 AM Steve Shuff  wrote:

> Hi All,
> I am hopeful someone can shed some light on this error .
>
> My setup consist of a RPi 3 (Raspbian) running WeeWX 3.9.2 to which is
> connected a Davis Envoy logger, The ISS is transmitting OK as can be
> verified on the indoor console.
>
> The setup runs fine until the Envoy batteries died, these were replaced
> and the Pi rebooted and the system restarted.
> Now my data is not being produced on the graphs etc , Upon looking at the
> syslog I see two errors,
>
> Apr  2 10:12:10 raspberrypi weewx[1195]: vantage: LOOP try #1; error:
> Expected to read 99 chars; got 0 instead
>
> Apr  2 10:11:56 raspberrypi weewx[1195]: vantage: DMPAFT try #2; error:
> Unable to pass CRC16 check while sending data to Vantage console
>
> Has anyone experienced this problem and what was the cure ? It has done it
> before when the batteries previously failed but I dont know what I did to
> remedy the situation.
> Thanks for any help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9b1973cc-a646-421c-85c0-44e58ece7f93%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/CAPq0zEB8CXqvToL7BSaRBB0Oe6SkMUGy-ggoMeh3Ym0DFLEsNw%40mail.gmail.com.

Re: [weewx-user] Re: weewx 4.0.0b16 stopped working at 02:00 this morning

[Thomas Keffer]

Ian: did you look at the Wiki article *Troubleshooting the Davis Vantage
stations*, specifically the section *WeeWX generates HTML pages but does
not update them
*
?

On Sun, Mar 29, 2020 at 5:33 AM ian kitchen  wrote:

> I'm getting similar results to Mike Revitt - no html updates.
> Can anyone explain the workaround - I don't know if I have "overnight
> backup"
>
> IK
>
> On Sunday, 29 March 2020 12:21:12 UTC+1, Mike Revitt wrote:
>>
>> when the clocks changed this morning weewx stopped downloading data from
>> my Vantage Pro, or at least appeared to
>>
>> Mar 29 00:59:54 weewx vncserver-x11[450,root]: AgentInitCheck: no
>> response from agent
>> Mar 29 00:59:59 weewx vncserver-x11[450,root]: AgentInitCheck: agent
>> comms failure
>> Mar 29 02:00:04 weewx vncserver-x11[450,root]: AgentInitCheck: no
>> response from agent
>> Mar 29 02:00:09 weewx vncserver-x11[450,root]: AgentInitCheck: agent
>> comms failure
>> Mar 29 02:00:14 weewx vncserver-x11[450,root]: AgentInitCheck: no
>> response from agent
>> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.manager: Added record
>> 2020-03-29 02:00:00 BST (1585443600) to database 'weewx.sdb'
>> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.manager: Added record
>> 2020-03-29 02:00:00 BST (1585443600) to daily summary in 'weewx.sdb'
>> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.restx: PWSWeather:
>> Published record 2020-03-29 02:00:00 BST (1585443600)
>> Mar 29 02:00:16 weewx weewx[31007] INFO weewx.restx: Wunderground-PWS:
>> Published record 2020-03-29 02:00:00 BST (1585443600)
>> Mar 29 02:00:16 weewx weewx[31007] INFO weewx.cheetahgenerator: Generated
>> 8 files for report SeasonsReport in 0.95 seconds
>> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.restx: AWEKAS: Published
>> record 2020-03-29 02:00:00 BST (1585443600)
>> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.imagegenerator: Generated
>> 20 images for report SeasonsReport in 1.71 seconds
>> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.reportengine: Copied 0
>> files to /var/www/html/MountWeather
>> Mar 29 02:00:18 weewx weewx[31007] INFO botocore.credentials: Found
>> credentials in shared credentials file: ~/.aws/credentials
>> Mar 29 02:00:18 weewx weewx[31007] INFO weewx.restx: WOW: Published
>> record 2020-03-29 02:00:00 BST (1585443600)
>>
>>
>>
>> Was still running perfectly at 11:45, just not downloading data.
>>
>> Mar 29 11:45:23 weewx weewx[31007] INFO weewx.engine: Clock error is 2.75
>> seconds (positive is fast)
>> Mar 29 11:45:24 weewx weewx[31007] INFO weewx.cheetahgenerator: Generated
>> 7 files for report SeasonsReport in 0.91 seconds
>> Mar 29 11:45:25 weewx weewx[31007] INFO weewx.imagegenerator: Generated
>> 20 images for report SeasonsReport in 1.61 seconds
>> Mar 29 11:45:25 weewx weewx[31007] INFO weewx.reportengine: Copied 0
>> files to /var/www/html/MountWeather
>> Mar 29 11:45:25 weewx weewx[31007] INFO botocore.credentials: Found
>> credentials in shared credentials file: ~/.aws/credentials
>> Mar 29 11:45:26 weewx vncserver-x11[450,root]: AgentInitCheck: agent
>> comms failure
>> Mar 29 11:45:31 weewx vncserver-x11[450,root]: AgentInitCheck: no
>> response from agent
>> Mar 29 11:45:36 weewx vncserver-x11[450,root]: AgentInitCheck: agent
>> comms failure
>> Mar 29 11:45:36 weewx weewx[31007] INFO user.s3upload: S3UploadGenerator:
>> AWS-S3 copied 27 files to S3 in 11.17 seconds
>>
>>
>> So I thought that this was the known daylight savings issue so ran
>>
>> /home/Weewx/bin/wee_device --dump
>>
>> But this resulted in this issue
>>
>> Mar 29 11:58:28 weewx weewxd[23444]: weewx[23444] INFO weewx.engine:
>> Starting main packet loop.
>> Mar 29 11:59:12 weewx weewxd[23444]: weewx[23444] ERROR
>> weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0
>> Mar 29 12:00:21 weewx weewxd[23444]: weewx[23444] INFO weewx.manager:
>> Added record 2020-03-29 12:00:00 BST (1585479600) to database
>> Mar 29 12:00:21 weewx weewxd[23444]: weewx[23444] INFO weewx.manager:
>> Added record 2020-03-29 12:00:00 BST (1585479600) to daily sum
>>
>> So I  restored my overnight database backup and restarted weewx.
>>
>> And now all is working perfectly.
>>
>> Don't know if this is something to do with weewx 4.0.0 or the Raspberry
>> Pi, but have not had an issue with the clocks going forward since I started
>> using weewx in 2014
>>
> --
> 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/d2bf1c8b-f3d9-4774-abd7-236b37464cf8%40googlegroups.com
> 
> .
>

Re: [weewx-user] weewx 4.0.0b16 stopped working at 02:00 this morning

[Thomas Keffer]

I'm not sure what I'm looking at here. I see none of the familiar Vantage
chatter, just something about vncserver? What's that?

On Sun, Mar 29, 2020 at 4:21 AM Mike Revitt  wrote:

> when the clocks changed this morning weewx stopped downloading data from
> my Vantage Pro, or at least appeared to
>
> Mar 29 00:59:54 weewx vncserver-x11[450,root]: AgentInitCheck: no response
> from agent
> Mar 29 00:59:59 weewx vncserver-x11[450,root]: AgentInitCheck: agent comms
> failure
> Mar 29 02:00:04 weewx vncserver-x11[450,root]: AgentInitCheck: no response
> from agent
> Mar 29 02:00:09 weewx vncserver-x11[450,root]: AgentInitCheck: agent comms
> failure
> Mar 29 02:00:14 weewx vncserver-x11[450,root]: AgentInitCheck: no response
> from agent
> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.manager: Added record
> 2020-03-29 02:00:00 BST (1585443600) to database 'weewx.sdb'
> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.manager: Added record
> 2020-03-29 02:00:00 BST (1585443600) to daily summary in 'weewx.sdb'
> Mar 29 02:00:15 weewx weewx[31007] INFO weewx.restx: PWSWeather: Published
> record 2020-03-29 02:00:00 BST (1585443600)
> Mar 29 02:00:16 weewx weewx[31007] INFO weewx.restx: Wunderground-PWS:
> Published record 2020-03-29 02:00:00 BST (1585443600)
> Mar 29 02:00:16 weewx weewx[31007] INFO weewx.cheetahgenerator: Generated
> 8 files for report SeasonsReport in 0.95 seconds
> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.restx: AWEKAS: Published
> record 2020-03-29 02:00:00 BST (1585443600)
> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.imagegenerator: Generated 20
> images for report SeasonsReport in 1.71 seconds
> Mar 29 02:00:17 weewx weewx[31007] INFO weewx.reportengine: Copied 0 files
> to /var/www/html/MountWeather
> Mar 29 02:00:18 weewx weewx[31007] INFO botocore.credentials: Found
> credentials in shared credentials file: ~/.aws/credentials
> Mar 29 02:00:18 weewx weewx[31007] INFO weewx.restx: WOW: Published record
> 2020-03-29 02:00:00 BST (1585443600)
>
>
>
> Was still running perfectly at 11:45, just not downloading data.
>
> Mar 29 11:45:23 weewx weewx[31007] INFO weewx.engine: Clock error is 2.75
> seconds (positive is fast)
> Mar 29 11:45:24 weewx weewx[31007] INFO weewx.cheetahgenerator: Generated
> 7 files for report SeasonsReport in 0.91 seconds
> Mar 29 11:45:25 weewx weewx[31007] INFO weewx.imagegenerator: Generated 20
> images for report SeasonsReport in 1.61 seconds
> Mar 29 11:45:25 weewx weewx[31007] INFO weewx.reportengine: Copied 0 files
> to /var/www/html/MountWeather
> Mar 29 11:45:25 weewx weewx[31007] INFO botocore.credentials: Found
> credentials in shared credentials file: ~/.aws/credentials
> Mar 29 11:45:26 weewx vncserver-x11[450,root]: AgentInitCheck: agent comms
> failure
> Mar 29 11:45:31 weewx vncserver-x11[450,root]: AgentInitCheck: no response
> from agent
> Mar 29 11:45:36 weewx vncserver-x11[450,root]: AgentInitCheck: agent comms
> failure
> Mar 29 11:45:36 weewx weewx[31007] INFO user.s3upload: S3UploadGenerator:
> AWS-S3 copied 27 files to S3 in 11.17 seconds
>
>
> So I thought that this was the known daylight savings issue so ran
>
> /home/Weewx/bin/wee_device --dump
>
> But this resulted in this issue
>
> Mar 29 11:58:28 weewx weewxd[23444]: weewx[23444] INFO weewx.engine:
> Starting main packet loop.
> Mar 29 11:59:12 weewx weewxd[23444]: weewx[23444] ERROR
> weewx.drivers.vantage: LOOP try #1; error: Expected to read 99 chars; got 0
> Mar 29 12:00:21 weewx weewxd[23444]: weewx[23444] INFO weewx.manager:
> Added record 2020-03-29 12:00:00 BST (1585479600) to database
> Mar 29 12:00:21 weewx weewxd[23444]: weewx[23444] INFO weewx.manager:
> Added record 2020-03-29 12:00:00 BST (1585479600) to daily sum
>
> So I  restored my overnight database backup and restarted weewx.
>
> And now all is working perfectly.
>
> Don't know if this is something to do with weewx 4.0.0 or the Raspberry
> Pi, but have not had an issue with the clocks going forward since I started
> using weewx in 2014
>
> --
> 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/ee4b37c4-96be-43c6-afe0-1c9ba28ed125%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/CAPq0zED2oh_TBay8oc_T9TGQrBpT-AfLEYadjCLYRLazMPYLbQ%40mail.gmail.com.

Re: [weewx-user] Re: wee_import csv problem "csv.Error: line contains NULL byte"

[Thomas Keffer]

Good sleuthing, Bob!

With Gary's modifications, the user will be able to specify the encoding of
the import file, avoiding the need to translate it.

On Sat, Mar 28, 2020 at 10:31 AM Bob Atchley  wrote:

> Hi Janne,
>
> I've carried out a similar import from my Youshiko weather station  and
> came across exactly the same issue.  I'm an Emacs user and looking at the
> csv  file exported from the Youshiko software in hexl-mode it would appear
> that the csv file is exported in UTF-16 format rather than ASCII.  I can
> think of no conceivable reason for doing this and assume it is a bug (of
> course LibreOffice and even emacs render this perfectly, so quite difficult
> to detect).  If you open the file in a simpler editor such as nano it is
> much clearer that something is very wrong.
>
> So a conversion from UTF-16 to ASCII is needed before attempting to use
> the weewx import utility.
>
> I found 2 ways of doing this
> 1) open a new file in nano.  Open the the csv file in Emacs (or probably
> any editor that renders it correctly) and copy the contents of the file and
> paste it into the nano editor and save
> 2) From the command line:
> $ iconv -f UTF-16 -t ASCII//TRANSLIT input.csv -o output.csv
>
> I used method 1) (I expect you did  something similar as well even if
> accidentally).  Method 2 is not perfect, and probably needs more work.
>
> But to be clear a CSV file would normally be expected to be ASCII, so this
> is not a weewx import issue.
>
> Hope this helps if you need to do another import in the future
>
> Regards
>
> Bob
>
> --
> 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/6c5e21fc-21e8-483d-8646-64ec2f605080%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/CAPq0zEAYtPJeYNSd_2GTnZGiLv9rGgb%3DEX_%3DbORiT-nbrpxZ8g%40mail.gmail.com.

Re: [weewx-user] Re: ephem does not work

[Thomas Keffer]

WeeWX V4, which will support Python 3, has not been released yet. While a
beta version is available, it can only be installed using the setup.py
method.

You should wait.

-tk

On Sat, Mar 28, 2020 at 5:18 AM Astrid  wrote:

> Hello!
>
> Thank you very much for your hints. :)
> I want to deinstall in yast2 all python2, because it
> is outdated and not longer supported.
> But then the system told me, that it will deinstall
> weewx too...
> Is weewx is running with python3 too?
>
> I try to switch manually to python3 is python, but
> it dont work... :(
>
> Regards, Astrid
>
> --
> 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/17106cd2-f9f5-41ca-92e8-9d879bafce29%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/CAPq0zEDScNggg%2BnGBQzHRCnKVrqaPAoePGN%3DpKuiX4_UNpcCzw%40mail.gmail.com.

Re: [weewx-user] Re: ephem does not work

[Thomas Keffer]

Thanks, Astrid. I was able to replicated this on my Leap 15.1 machine.

It comes with Python 3, which sets "pip" to point to the Python 3 version
of pip. If you then install Python 2, the command "python" now points to
the Python 2 version. So, you end up with one pointing one way, the other
the other way. Poor choice on the part of the OpenSUSE designers!

Suggestion: always be explicit about which version of pip you want. Instead
of

*pip pyephem*

use

*python2 -m pip pyephem*

-tk


On Fri, Mar 27, 2020 at 8:21 PM Astrid  wrote:

> Hello!
>
> Yes, I think so...?
> But I dont understand, why this is so...?? :(
>
> But I am happy, that ephem is working now. :)
>
> Thanx a lot. :)
>
> Regards, Astrid
>
> --
> 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/cf46eb20-d83e-414a-9e20-49d370c40738%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/CAPq0zEDBV%2Bz0JsQW%2BqMkX4_yy5mxZTHyoBBCbSo5t3xGqTcyMQ%40mail.gmail.com.

Re: [weewx-user] WeeWX on RPi with custom hardware based on I2C sensors

[Thomas Keffer]

WeeWX blocks on queries to the sensors, so it responds as fast as the
sensor emits data. Once per second should be fine on all but the slowest of
platforms.

WeeWX V3.9 runs on Python 2.x only. Version 4.x (due RSN), runs on either.
It's pretty stable. You can find betas in the development download area
.

-t



On Fri, Mar 27, 2020 at 3:30 PM Sergio Alejandro González <
sergio.alejandro.gonza...@gmail.com> wrote:

> Ok guys..I have a couple of doubts:
>
> I'm completely new to WeeWX but I think that I can use it for a complete
> custom weather station that I've created and is based on I2C sensors,
> specifically, atmospheric radiance sensors. Now my question is I need to
> query those sensors every second. WeeWX is able to be customized to be able
> to do that?
>
> I currently have the custom hardware working on a RPI3 with Python 3.6
> code...I know WeeWX works in Pyhton 2.7...could this be a problem ?
>
> Warmest regard to all in this forums and tanks in advance to any help...
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/3b630c01-c50d-4729-bbb6-ea895fe83cb8%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/CAPq0zECapTVuQ35n5rSnLyXrcm2H%3DcZaVgcdqrxDCPk4UKZ2LQ%40mail.gmail.com.

Re: [weewx-user] Re: ephem does not work

[Thomas Keffer]

Are you saying that "pip" installed pyephem in a Python 3.x location, but
the command "python" invokes Python 2.x?

-tk

On Fri, Mar 27, 2020 at 11:22 AM Astrid  wrote:

> Hello!
>
> I got it. :)
> I found that there is a pip2.7.
> I am a little bit confused with the version...
> If I say pyton it calls pyton2.7, but if I say pip, it calls pip3.6...
> It is suse Leap 15.1.
>
> But now with the command
> pip2.7 install ephem
>
> I got it. :)
>
> Thank you very much for your hints in the
> right direction.
> I am a newbee on here...
>
> Regards, Astrid
>
> --
> 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/2c166d8e-d5d3-4b19-b576-676069214ffe%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/CAPq0zECRhc8f437qak39KAaE_dfrN%2B0s1MxJZmxTP46iMZNFAw%40mail.gmail.com.

Re: [weewx-user] ephem does not work

[Thomas Keffer]

You're not giving a lot of information, but it's possible that pip
installed pyephem a different version of python that the version you are
using to run weewxd. Try this:

*pip show pyephem*

It will show you where pip installed pyephem. Then try this:

*python -c "import sys; print(sys.path)"*

There must be a match between them.

Also, how are you running weewxd? We need to know what version of Python it
is using. Try this:

*head /usr/bin/weewxd*

or

*head /home/weewx/bin/weewxd*

depending on how you installed WeeWX.

Finally, what is your PATH?

*env echo $PATH*

-tk

On Fri, Mar 27, 2020 at 7:04 AM Astrid  wrote:

> Hello!
>
> I have weewx 3.9.2 installed.
> PyEphem is installed via pip.
>
> pip list | grep ephem
> ephem   3.7.7.0
> pyephem 3.7.7.0
>
> I put
> import ephem
> to local weewx-installation into
> extensions.py
>
> but if I restart weewx, it said that it
> ephem not found
>
> If I ommit this line in extensions.py and
> and restart weewx and
> print $almanac.hasExtra to a report, it
> said: false.
>
> I want to add moonrise and moonset to my
> almanach.
>
> How I can get ephem for this getting work?
>
> Regards, Astrid
>
> --
> 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/cc3e7973-99cd-4bfd-b7d1-e58c6463873f%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/CAPq0zEAn6288C2nAom2DAjKLimi%2BN65E_M%3Df2REwCJ8AwQya%3Dw%40mail.gmail.com.

Re: [weewx-user] Average WX local historical data to compare?

[Thomas Keffer]

This would be a useful feature but, unfortunately, it does not exist in
WeeWX. You would have to write a search list extension.

-tk

On Thu, Mar 26, 2020 at 6:46 PM Xant  wrote:

>
> I'm in the UpstateNY, where weather behaviour indeed awkward (specially
> recently) Mix of warm days, recent snow and freezing temps besides
> clear sunny days.
>
> Historically, what is the temp I was expected to see today? Under
> freezing, above freezing, warm? Are the Seasons changing due to "Global
> Warming"?
>
> In another words, is there average WX local historical data that can be
> retrieved and compared and plotted to WeeWX graphs?
>
> Xant
>
> --
> 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/1d64607d-f584-4363-b6a7-11ec67b96411%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/CAPq0zEAXGCqwvG-dPfkoWHt2sCGFf1H3NNtG90MFvrNM86T1jg%40mail.gmail.com.

Re: [weewx-user] Re: weewx division by zero error

[Thomas Keffer]

WeeWX V3.x does not support archive intervals less than 60 seconds.

WeeWX V4 will.

However, very few weather stations have LOOP packets that come fast enough
to allow that short of an interval.

-tk

On Wed, Mar 25, 2020 at 4:09 PM Jeff Ross  wrote:

> 30 seconds
>
> On Wednesday, March 25, 2020 at 4:52:09 PM UTC-6, Jeff Ross wrote:
>>
>> Getting the following error on weewx 3.9.2:
>>
>> 2020-03-25 16:25:39.975468500 127.0.0.1: user.debug: Mar 25 16:25:39
>> weewx[17898]: interceptor: MainThread: raw packet: {'wind_speed': 5.1,
>> 'humidity_in': 30.0, 'temperature_in': 70.3, 'barometer': 25.609,
>> 'windchill': 29.7, 'dewpoint': 28.2, 'humidity_out': 78.0, 'uv': 0.0,
>> 'radiation': 52.85, 'rain': None, 'dateTime': 1585175109, 'pressure':
>> 25.609, 'temperature_out': 34.3, 'wind_dir': 237.0, 'rain_total': 0.331,
>> 'usUnits': 1, 'wind_gust': 5.8}
>> 2020-03-25 16:25:39.975558500 127.0.0.1: user.debug: Mar 25 16:25:39
>> weewx[17898]: interceptor: MainThread: mapped packet: {'barometer': 25.609,
>> 'windchill': 29.7, 'dewpoint': 28.2, 'pressure': 25.609, 'outHumidity':
>> 78.0, 'UV': 0.0, 'radiation': 52.85, 'rain': None, 'dateTime': 1585175109,
>> 'windDir': 237.0, 'outTemp': 34.3, 'windSpeed': 5.1, 'inHumidity': 30.0,
>> 'inTemp': 70.3, 'windGust': 5.8, 'usUnits': 1}
>> 2020-03-25 16:25:40.089632500 127.0.0.1: user.info: Mar 25 16:25:40
>> weewx[17898]: engine: Main loop exiting. Shutting engine down.
>> 2020-03-25 16:25:40.109860500 127.0.0.1: user.debug: Mar 25 16:25:40
>> weewx[17898]: restx: Shut down Windy thread.
>> 2020-03-25 16:25:40.129892500 127.0.0.1: user.debug: Mar 25 16:25:40
>> weewx[17898]: restx: Shut down PWSWeather thread.
>> 2020-03-25 16:25:40.149827500 127.0.0.1: user.debug: Mar 25 16:25:40
>> weewx[17898]: restx: Shut down StationRegistry thread.
>> 2020-03-25 16:25:40.150077500 127.0.0.1: user.info: Mar 25 16:25:40
>> weewx[17898]: interceptor: MainThread: shutting down server thread
>> 2020-03-25 16:25:40.150189500 127.0.0.1: user.debug: Mar 25 16:25:40
>> weewx[17898]: interceptor: MainThread: stop sniff server
>> 2020-03-25 16:25:40.151404500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: engine: Caught unrecoverable exception in engine:
>> 2020-03-25 16:25:40.151596500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   integer division or modulo by zero
>> 2020-03-25 16:25:40.192081500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   Traceback (most recent call last):
>> 2020-03-25 16:25:40.192281500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 894,
>> in main
>> 2020-03-25 16:25:40.192286500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   engine.run()
>> 2020-03-25 16:25:40.192501500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 191,
>> in run
>> 2020-03-25 16:25:40.192506500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: 
>> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
>> 2020-03-25 16:25:40.193301500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 224,
>> in dispatchEvent
>> 2020-03-25 16:25:40.193324500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   callback(event)
>> 2020-03-25 16:25:40.193328500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 540,
>> in new_loop_packet
>> 2020-03-25 16:25:40.193332500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   self.accumulator =
>> self._new_accumulator(event.packet['dateTime'])
>> 2020-03-25 16:25:40.193336500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 650,
>> in _new_accumulator
>> 2020-03-25 16:25:40.193345500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   self.archive_interval)
>> 2020-03-25 16:25:40.193348500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]: File "/home/weewx/bin/weeutil/weeutil.py", line
>> 197, in startOfInterval
>> 2020-03-25 16:25:40.193353500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   m = int(time_tt.tm_min // interval_m *
>> interval_m)
>> 2020-03-25 16:25:40.193361500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   ZeroDivisionError: integer division or modulo by
>> zero
>> 2020-03-25 16:25:40.193365500 127.0.0.1: user.crit: Mar 25 16:25:40
>> weewx[17898]:   Exiting.
>>
>> If I'm reading the above correctly, the error occurs here in
>> home/weewx/bin/weeutil/weeutil.py:
>> def startOfInterval(time_ts, interval):
>> """Find the start time of an interval.
>>
>> This algorithm assumes the day is divided up into
>> intervals of 'interval' length. Given a timestamp, it
>> figures out which interval it lies in, returning the start
>> 

Re: [weewx-user] weewx division by zero error

[Thomas Keffer]

What are you using for an archive interval?

To check, set debug=1, then restart the program. Look for a line such as

Using archive interval of 60 seconds (specified in weewx configuration)

-tk

On Wed, Mar 25, 2020 at 3:52 PM Jeff Ross  wrote:

> Getting the following error on weewx 3.9.2:
>
> 2020-03-25 16:25:39.975468500 127.0.0.1: user.debug: Mar 25 16:25:39
> weewx[17898]: interceptor: MainThread: raw packet: {'wind_speed': 5.1,
> 'humidity_in': 30.0, 'temperature_in': 70.3, 'barometer': 25.609,
> 'windchill': 29.7, 'dewpoint': 28.2, 'humidity_out': 78.0, 'uv': 0.0,
> 'radiation': 52.85, 'rain': None, 'dateTime': 1585175109, 'pressure':
> 25.609, 'temperature_out': 34.3, 'wind_dir': 237.0, 'rain_total': 0.331,
> 'usUnits': 1, 'wind_gust': 5.8}
> 2020-03-25 16:25:39.975558500 127.0.0.1: user.debug: Mar 25 16:25:39
> weewx[17898]: interceptor: MainThread: mapped packet: {'barometer': 25.609,
> 'windchill': 29.7, 'dewpoint': 28.2, 'pressure': 25.609, 'outHumidity':
> 78.0, 'UV': 0.0, 'radiation': 52.85, 'rain': None, 'dateTime': 1585175109,
> 'windDir': 237.0, 'outTemp': 34.3, 'windSpeed': 5.1, 'inHumidity': 30.0,
> 'inTemp': 70.3, 'windGust': 5.8, 'usUnits': 1}
> 2020-03-25 16:25:40.089632500 127.0.0.1: user.info: Mar 25 16:25:40
> weewx[17898]: engine: Main loop exiting. Shutting engine down.
> 2020-03-25 16:25:40.109860500 127.0.0.1: user.debug: Mar 25 16:25:40
> weewx[17898]: restx: Shut down Windy thread.
> 2020-03-25 16:25:40.129892500 127.0.0.1: user.debug: Mar 25 16:25:40
> weewx[17898]: restx: Shut down PWSWeather thread.
> 2020-03-25 16:25:40.149827500 127.0.0.1: user.debug: Mar 25 16:25:40
> weewx[17898]: restx: Shut down StationRegistry thread.
> 2020-03-25 16:25:40.150077500 127.0.0.1: user.info: Mar 25 16:25:40
> weewx[17898]: interceptor: MainThread: shutting down server thread
> 2020-03-25 16:25:40.150189500 127.0.0.1: user.debug: Mar 25 16:25:40
> weewx[17898]: interceptor: MainThread: stop sniff server
> 2020-03-25 16:25:40.151404500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: engine: Caught unrecoverable exception in engine:
> 2020-03-25 16:25:40.151596500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   integer division or modulo by zero
> 2020-03-25 16:25:40.192081500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   Traceback (most recent call last):
> 2020-03-25 16:25:40.192281500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 894,
> in main
> 2020-03-25 16:25:40.192286500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   engine.run()
> 2020-03-25 16:25:40.192501500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 191,
> in run
> 2020-03-25 16:25:40.192506500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: 
> self.dispatchEvent(weewx.Event(weewx.NEW_LOOP_PACKET, packet=packet))
> 2020-03-25 16:25:40.193301500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 224,
> in dispatchEvent
> 2020-03-25 16:25:40.193324500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   callback(event)
> 2020-03-25 16:25:40.193328500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 540,
> in new_loop_packet
> 2020-03-25 16:25:40.193332500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   self.accumulator =
> self._new_accumulator(event.packet['dateTime'])
> 2020-03-25 16:25:40.193336500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weewx/engine.py", line 650,
> in _new_accumulator
> 2020-03-25 16:25:40.193345500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   self.archive_interval)
> 2020-03-25 16:25:40.193348500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]: File "/home/weewx/bin/weeutil/weeutil.py", line
> 197, in startOfInterval
> 2020-03-25 16:25:40.193353500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   m = int(time_tt.tm_min // interval_m *
> interval_m)
> 2020-03-25 16:25:40.193361500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   ZeroDivisionError: integer division or modulo by
> zero
> 2020-03-25 16:25:40.193365500 127.0.0.1: user.crit: Mar 25 16:25:40
> weewx[17898]:   Exiting.
>
> If I'm reading the above correctly, the error occurs here in
> home/weewx/bin/weeutil/weeutil.py:
> def startOfInterval(time_ts, interval):
> """Find the start time of an interval.
>
> This algorithm assumes the day is divided up into
> intervals of 'interval' length. Given a timestamp, it
> figures out which interval it lies in, returning the start
> time.
>
> time_ts: A timestamp. The start of the interval containing this
> timestamp will be returned.
>
> interval: An interval length in seconds.
>
> 

Re: [weewx-user] Re: different behaiviour of manually wee_reports and automatic generation,

[Thomas Keffer]

I suspect the environment variable LANG is not being set by whatever shell
is starting your daemon.

An easy fix is to go into /usr/share/weewx/user/extension.py and change this

import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, '')

to this

import locale
# This will use the locale specified by the environment variable 'LANG'
# Other options are possible. See:
# http://docs.python.org/2/library/locale.html#locale.setlocale
locale.setlocale(locale.LC_ALL, 'de_DE.UTF-8')




On Wed, Mar 25, 2020 at 9:44 AM Astrid  wrote:

> P.S.:
>
> Mär 25 17:41:57 linux systemd[1]: Started weewx weather system.
> Mär 25 17:41:57 linux weewx[6]: engine: Initializing weewx version
> 3.9.2
> Mär 25 17:41:57 linux weewx[6]: engine: Using Python 2.7.14 (default,
> Oct 12 2017, 15:50:02) [GCC]
> Mär 25 17:41:57 linux weewx[6]: engine: Platform
> Linux-4.12.14-lp151.28.40-default-x86_64-with-glibc2.2.5
> Mär 25 17:41:57 linux weewx[6]: engine: Locale is
> 'LC_CTYPE=de_DE.UTF-8;LC_NUMERIC=C;LC_TIME=C;LC_COLLATE=C;LC_MONETARY=C;LC_MESSAGES=C;LC_PAPER=C;LC_NAME=C;LC_ADDRESS=C;LC_TELEPHONE=C;LC_MEASUREMENT=C;LC_IDENTIFICATION=C'
>
>
> --
> 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/d5a0c0c7-ed39-41fa-a49c-6959c4c24ac0%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/CAPq0zEBKYSrOFkLM%2B2s7Kf9hS8%2BkkaiwibLCoQCgHF%2BeJEfY9w%40mail.gmail.com.

Re: [weewx-user] different behaiviour of manually wee_reports and automatic generation,

[Thomas Keffer]

Did you set the environment variable LANG? See the manual
.

-tk

On Wed, Mar 25, 2020 at 7:54 AM Astrid  wrote:

> Hello!
>
> I am using weex 3.9.2 and Standard-Skin.
> German location.
>
> If I use from commandline "wee_reports" the date is printed
> in my reports on /var/www/weewx in
> german notation:
> 25.03.2020 15:20:00
> and in the weekoverview there
> is standing
> 18,6°C um 14:45:00 (Mittwoch)
>
> If the archive-intervall is over and
> the reports in /var/www/weewx are
> generated automaticially there is standing:
>
> 03/25/20 15:50:00
> and
> 18.6°C um 14:45:00 (Wednesday)
>
> Where can I change, that it will be
> during automated generated reports
> the german notation too?
>
> Regards, Astrid
>
>
>
> --
> 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/23627ab1-9aac-4913-80cc-75a22b71bcd9%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/CAPq0zEByMx72c7xMX0Y39SEhZMNzGMHMab867u%2B7C58kFXaf8A%40mail.gmail.com.

Re: [weewx-user] Re: ftp does not work

[Thomas Keffer]

The FTP "skin" is not a regular "skin". Unlike other skins, such as
Standard, it does not produce graphs and HTML pages. Instead, it uses the
reportgenerator machinery to move files via FTP.

The option "skin" under [[FTP]] is there so reportgenerator can find what
it needs to run FTP. It does NOT specify the skin that will be the source.
That is specified by HTML_ROOT.

Again, this is all in the documentation. It pays to read it.

-tk



On Tue, Mar 24, 2020 at 5:33 AM Astrid  wrote:

> Hello!
>
> Thanx a lot, now it works. :)
>
> But I do not understand.
> There is standing in FTP-section: skin=Ftp
> But it takes the Standard-Skin.
> But no matter, that I do not understand.
> This it, what I want, the Standard-Skin. ;)
> (In the moment, perhaps changing someone
> to another.)
>
> Regards, Astrid
>
> --
> 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/bc5a5529-0836-45f9-9f35-24dbfe949627%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/CAPq0zECgDMjmHTWtEG-P_XrkGZYcjz2NLWupyRjfAAGuiW%2BEtw%40mail.gmail.com.

Re: [weewx-user] Re: ftp does not work

[Thomas Keffer]

Sorry. That link did not take. Let me try again.

Read the [[FTP]] <http://www.weewx.com/docs/usersguide.htm#config_FTP> section
of the manual.

On Mon, Mar 23, 2020 at 1:51 PM Thomas Keffer  wrote:

> I understand your point. Read the [[FTP]] section of the manual.
>
> On Mon, Mar 23, 2020 at 12:49 PM Astrid  wrote:
>
>> Hello!
>>
>> Thanx. I will try it.
>> But I want the skin "Standard" for uploding to ftp.
>> I do _not_ want to use the skin Ftp.
>> How can I get this?
>>
>> Regards, Astrid
>>
>> --
>> 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/c4c9bdee-fb6a-41e1-bbea-26d4f1495140%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/c4c9bdee-fb6a-41e1-bbea-26d4f1495140%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CAPq0zEDKSK6QjZmuUn9CbRzO1FbfLjhexeqYqCiByuCxNRj0-A%40mail.gmail.com.

Re: [weewx-user] Re: ftp does not work

[Thomas Keffer]

I understand your point. Read the [[FTP]]
 section of
the manual.

On Mon, Mar 23, 2020 at 12:49 PM Astrid  wrote:

> Hello!
>
> Thanx. I will try it.
> But I want the skin "Standard" for uploding to ftp.
> I do _not_ want to use the skin Ftp.
> How can I get this?
>
> Regards, Astrid
>
> --
> 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/c4c9bdee-fb6a-41e1-bbea-26d4f1495140%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/CAPq0zEDFVzfx0b5yR5%3Dao4T6RUpzuBD9t6jGVY1ptwojhK%3D3iA%40mail.gmail.com.

Re: [weewx-user] Re: ftp does not work

[Thomas Keffer]

Astrid, slow down there! You're just changing things randomly. Start with
the copy of weewx.conf that was installed, then follow the directions in
the User's Guide.

You should end up with something like...

[[FTP]]
# FTP'ing the results to a webserver is treated as just another
report,
# albeit one with an unusual report generator!
skin = Ftp

# If you wish to use FTP, set "enable" to "true", then
# fill out the next four lines.
# Use quotes around passwords to guard against parsing errors.
enable = true
user = myuser
password = mypw
server = mysubserver# The ftp server name, e.g, www.myserver.org
path = /  # The destination directory, e.g., /weather

You must *not* change the values in yellow.

Change the values in blue.

-tk

On Mon, Mar 23, 2020 at 10:41 AM Astrid  wrote:

> Hello!
>
> Ok, thanx. :) so I switch back to systemd-logger-package.
>
> I hope, this helps:
>
> Mär 23 17:30:26 linux weewx[20473]: manager: Added record 2020-03-23
> 17:30:00 CET (1584981000) to daily summary in 'weewx.sdb'
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Running reports for
> latest time in the database.
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Report 'SeasonsReport'
> not enabled. Skipping.
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Report
> 'SmartphoneReport' not enabled. Skipping.
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Report 'MobileReport'
> not enabled. Skipping.
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Running report
> 'StandardReport'
> Mär 23 17:30:26 linux weewx[20473]: reportengine: Found configuration file
> /etc/weewx/skins/Standard/skin.conf for report 'StandardReport'
> Mär 23 17:30:26 linux weewx[20473]: cheetahgenerator: using search list
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> Mär 23 17:30:26 linux weewx[20473]: manager: Daily summary version is 2.0
> Mär 23 17:30:28 linux weewx[20473]: cheetahgenerator: Generated 14 files
> for report StandardReport in 2.42 seconds
> Mär 23 17:30:28 linux weewx[20473]: manager: Daily summary version is 2.0
> Mär 23 17:30:30 linux weewx[20473]: imagegenerator: Generated 12 images
> for StandardReport in 1.39 seconds
> Mär 23 17:30:30 linux weewx[20473]: copygenerator: copied 0 files to
> /var/www/htdocs/weewx
> Mär 23 17:30:30 linux weewx[20473]: reportengine: Running report 'FTP'
> Mär 23 17:30:30 linux weewx[20473]: reportengine: Cannot read skin
> configuration file /etc/weewx/skins/skin.conf for report 'FTP': Config file
> not found: "/etc/weewx/skins/skin.conf".
> Mär 23 17:30:30 linux weewx[20473]: reportengine: No generators specified
> for report 'FTP'
> Mär 23 17:30:30 linux weewx[20473]: reportengine: Report 'RSYNC' not
> enabled. Skipping.
>
> The foldername in
> /etc/weewx/skins
> is
> Ftp
> not FTP
>
> In weewx.conf I change now to:
> [[FTP]]
> skin = Standard
> before I comment the line.
>
> Now the journalctl looks better at this place:
>
> Mär 23 18:35:26 linux weewx[4564]: reportengine: Running report 'FTP'
> Mär 23 18:35:26 linux weewx[4564]: reportengine: Found configuration file
> /etc/weewx/skins/Standard/skin.conf for report 'FTP'
> Mär 23 18:35:26 linux weewx[4564]: cheetahgenerator: using search list
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> Mär 23 18:35:26 linux weewx[4564]: manager: Daily summary version is 2.0
> Mär 23 18:35:28 linux weewx[4564]: cheetahgenerator: Generated 14 files
> for report FTP in 1.93 seconds
> Mär 23 18:35:28 linux weewx[4564]: manager: Daily summary version is 2.0
> Mär 23 18:35:30 linux weewx[4564]: imagegenerator: Generated 12 images for
> FTP in 1.20 seconds
> Mär 23 18:35:30 linux weewx[4564]: copygenerator: copied 14 files to
> /var/www/htdocs/weewx
> Mär 23 18:35:30 linux weewx[4564]: reportengine: Report 'RSYNC' not
> enabled. Skipping.
>
> But still nothing is uploaded... :(
>
> Regards, Astrid
>
> --
> 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/b99c0cfe-d534-47ec-9267-38263c23fec1%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 

Re: [weewx-user] Re: 4.0.0b16 - No diagrams - No module named 'Image'

[Thomas Keffer]

Nothing unusual there.

Best guess is that this is a Debian dependency bug in python-pil
, that carried
over into python3-pil.

Cheers,

-tk

On Mon, Mar 23, 2020 at 9:36 AM Michael  wrote:

> *apt list python3-pil*
>
> pi@raspi02:~ $ apt list python3-pil
> Auflistung... Fertig
> python3-pil/stable,now 5.4.1-2+deb10u1 armhf  [installiert]
>
>
> *apt show python3-pil*
>
> pi@raspi02:~ $ apt show python3-pil
> Package: python3-pil
> Version: 5.4.1-2+deb10u1
> Priority: optional
> Section: python
> Source: pillow
> Maintainer: Matthias Klose 
> Installed-Size: 1.348 kB
> Provides: python3-pillow
> Depends: python3 (<< 3.8), python3 (>= 3.7~), python3:any, mime-support |
> python3-pil.imagetk, libc6 (>= 2.11), libfreetype6 (>= 2.2.1),
> libimagequant0 (>= 2.1
> 1.10), libjpeg62-turbo (>= 1.3.1), liblcms2-2 (>= 2.2+git20110628),
> libtiff5 (>= 4.0.3), libwebp6 (>= 0.5.1), libwebpdemux2 (>= 0.5.1),
> libwebpmux3 (>= 0.6.1-2
> ), zlib1g (>= 1:1.1.4)
> Recommends: python3-olefile
> Suggests: python-pil-doc, python3-pil-dbg
> Conflicts: python3-imaging (<< 1.1.7+2.0.0-1.1)
> Breaks: python3-imaging (<< 1.1.7+2.0.0-1.1)
> Replaces: python3-imaging (<< 1.1.7+2.0.0-1.1)
> Homepage: http://python-pillow.github.io/
> Download-Size: 364 kB
> APT-Manual-Installed: yes
> APT-Sources: http://raspbian.raspberrypi.org/raspbian buster/main armhf
> Packages
> Description: Python Imaging Library (Python3)
>  The Python Imaging Library (PIL) adds an image object to your Python
>  interpreter. You can load images from a variety of file formats, and
>  apply a rich set of image operations to them.
>  .
>  Image Objects:
>   o Bilevel, greyscale, palette, true colour (RGB), true colour with
> transparency (RGBA).
>   o colour separation (CMYK).
>   o Copy, cut, paste operations.
>   o Flip, transpose, resize, rotate, and arbitrary affine transforms.
>   o Transparency operations.
>   o Channel and point operations.
>   o Colour transforms, including matrix operations.
>   o Image enhancement, including convolution filters.
>  .
>  File Formats:
>   o Full (Open/Load/Save): BMP, EPS (with ghostscript), GIF, IM, JPEG,
> MSP, PDF, PNG, PPM, TIFF, XBM.
>   o Read only (Open/Load): ARG, CUR, DCX, FLI, FPX, GBR, GD, ICO, IMT,
> IPTC,
> MCIDAS, MPEG, PhotoCD, PCX, PIXAR, PSD, TGA, SGI, SUN, TGA, WMF, XPM.
>   o Save only: PDF, EPS (without ghostscript).
>
>
> *cat /etc/issue*
>
> pi@raspi02:~ $ cat /etc/issue
> Raspbian GNU/Linux 10 \n \l
>
> --
> 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/cc84e15a-5920-4d4a-902e-ada1d6588aef%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/CAPq0zEC8E4852%3D-LnR%3DFGiCKt5YjOFupGA%3Df%2BVq8iPSt5MHfLg%40mail.gmail.com.

Re: [weewx-user] Re: ftp does not work

[Thomas Keffer]

I really do not know. I am not an OpenSUSE expert, but I assume "journalctl
-b" would show you messages since the last boot.

However, if you changed your logging facility, then I have no way of
knowing.

On Mon, Mar 23, 2020 at 9:18 AM Astrid  wrote:

> Hello!
>
> Thanx for your reply.
> In weewx.conf I set DEBUG=1 now.
> My local system I changed journalctl to old rsyslog.
> So that I hope, that I will find something in /var/log/messages
> But nothing inside from weewx, ftp or so on.
>
> I looked on logs at serviceprovider, but I found no
> hints there too... :(
> I found no errormessages there too.
>
> Do you can give me a hint, where I should look?
>
> On local system or on external webserver?
>
> Reagards, Astrid
>
>
>
> --
> 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/abadb61a-e274-43ed-8fd6-e274f8862d0b%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/CAPq0zEDKxw9PiHSuPSphSBG_5SREUcGbTcdtBHR1mrjbMoG-rg%40mail.gmail.com.

Re: [weewx-user] Re: 4.0.0b16 - No diagrams - No module named 'Image'

[Thomas Keffer]

Hmm, I wonder where the dependency on libopenjp2 came from? Could you run
these commands?

apt list python3-pil
apt show python3-pil
cat /etc/issue

On Mon, Mar 23, 2020 at 8:09 AM Michael  wrote:

> here it is...:
>
> pi@raspi02:~ $ python3 -c "import Image"
> Traceback (most recent call last):
> File "", line 1, in 
> ModuleNotFoundError: No module named 'Image'
> pi@raspi02:~ $ python3 -c "from PIL import Image"
> Traceback (most recent call last):
> File "", line 1, in 
> File "/usr/local/lib/python3.7/dist-packages/PIL/Image.py", line 69, in
> 
> from . import _imaging as core
> ImportError: libopenjp2.so.7: cannot open shared object file: No such file
> or directory
> pi@raspi02:~ $ python3 -c "import sys; print(sys.path)"
> ['', '/usr/lib/python37.zip', '/usr/lib/python3.7',
> '/usr/lib/python3.7/lib-dynload', '/usr/local/lib/python3.7/dist-packages',
> '/usr/lib/python3/dist-packages
> ']
>
> with this result google fed.
> and then installed libopenjp2-7.
> And the diagrams are displayed.
> Thanks for the support.
>
> --
> 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/76dcf777-0fbf-437f-947a-c7c8a266af38%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/CAPq0zEBHqTJ4bWqu_u6n4sXJCBUJYbG-wvRLXY6Me%2B7KFCK6Sg%40mail.gmail.com.

Re: [weewx-user] fileparse.py does not work

[Thomas Keffer]

You are using fileparse.py from the master branch on GitHub, which is part
of WeeWX V4, not WeeWX V3. Either use the version that came with your
distribution (should be found in /usr/share/doc/weewx/examples/), or get
the archived V3.9.2 version using the v3.9.2 tag:
https://github.com/weewx/weewx/tree/v3.9.2/examples/fileparse

On Mon, Mar 23, 2020 at 7:49 AM Astrid  wrote:

> Hello!
>
> I want to use fileparse for my weewx 3.9.2.
> I copy it from
> https://github.com/weewx/weewx/tree/master/examples/fileparse
> I choose manually-installation and put the
> fileparse.py into
> /usr/share/weewx/user
> on my local installation at leap 15.1
>
> I want to test it locally as described in the
> py-file, but:
>
> linux:/usr/share/weewx/user # PYTHONPATH=/usr/share/weewx python
> /usr/share/weewx/user/fileparse.py
> Traceback (most recent call last):
>   File "/usr/share/weewx/user/fileparse.py", line 119, in 
> import weeutil.logger
> ImportError: No module named logger
>
> How I can get it work?
>
> Regards, Astrid
>
> --
> 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/5ff3791c-6ced-45b4-8415-2060e081cfed%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/CAPq0zEDd4g9xaONuBsamMpudwsrTsVy-6t5Zm5AQu_SaPt8pEQ%40mail.gmail.com.

Re: [weewx-user] ftp does not work

[Thomas Keffer]

We will need to see the log file. See the Wiki article *Help! Posting to
weewx-user
* for how
to post a useful log file.

To answer your questions:

   1. HTML_ROOT is where the files are coming *from*. It is usually
   specified under the [StdReport] section.  It should not be necessary to
   specify it again in the [[FTP]] section,
   2. How 'path' is interpreted depends on the FTP server. Usually it is
   the path relative to the FTP user ('myuser' in your case). It may or may
   not need a leading slash.

-tk

On Mon, Mar 23, 2020 at 7:36 AM Astrid  wrote:

> Hello!
>
> I am using weewx 3.9.2 on leap 15.1
>
> In the moment I want to use the
> Standard-skin, not the ftp-skin.
> (I will decide the skin later on.)
>
> On my computer the files are
> put on /var/www/htdocs/weewx folder
> very well and updatet.
>
> But it does not work, that the files
> are put to external webserver via ftp.
>
> A subset of lines from my weewx.conf:
>
> WEEWX_ROOT = /
> [StdReport]
> HTML_ROOT = /var/www/htdocs/weewx # -> this works
> [[StandardReport]]
> skin = Standard
> enable = true
> [[FTP]]
> ##skin = Ftp # -> to keep the Standard-Skin
> enable = true
> user = myuser
> password = mypw
> server = mysubserver
> path = / # -> this is ok to, there is a special
> ftpuser, which points to the correct folder
>
> HTML_ROOT = /   # ??? is this where it goes on my subserver, or
> where it copy from local?
>
> port = 21
> passive = 1
>
> If I did on commandline
> ftp myuser@mysubserver
> it works and I am in correct folder, where the weewx-files
> should be placed.
> I did
> put test.file
> and it works too.
> So I think, the default-ftp-parameter port 21 and passive are ok?
>
> But why the weewx did not put on ftp... :(
> How I can get it work?
>
> Regards, Astrid
>
>
> --
> 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/1e2e5583-03a8-44a0-aa86-8f1ee197096b%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/CAPq0zEBz94KVXTMW4hLDshryJv4A0AvasamX7_kwZ05QuwEfng%40mail.gmail.com.

Re: [weewx-user] Re: 4.0.0b16 - No diagrams - No module named 'Image'

[Thomas Keffer]

Let's make sure python-pil installed where the interpreter can find it. One
of these two should work.

*python3 -c "import Image"*
*python3 -c "from PIL import Image"*

If neither works, and you're sure you installed python3-pil, then python3
is searching in some non-standard place. Here is where it's searching:

*python3 -c "import sys; print(sys.path)"*

-tk

On Sun, Mar 22, 2020 at 9:02 AM Michael  wrote:

> python3-pil was already installed
>
> pi@raspi02:~ $ sudo apt install python3-pil
> Paketlisten werden gelesen... Fertig
> Abhängigkeitsbaum wird aufgebaut.
> Statusinformationen werden eingelesen Fertig
> python3-pil ist schon die neueste Version (5.4.1-2+deb10u1).
> 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 4 nicht aktualisiert.
>
>> --
> 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/d31d54e0-5502-4c4d-8f49-54adc0126deb%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/CAPq0zEA%2BUbktGsNYSOMWEOTHXPJPgmX9HGjUg_uSr64EYka88A%40mail.gmail.com.

Re: [weewx-user] 4.0.0b16 - No diagrams - No module named 'Image'

[Thomas Keffer]

You need to install either PIL or pillow.

*sudo apt install python3-pil*

-tk

On Sun, Mar 22, 2020 at 7:01 AM Michael  wrote:

> Hello,
>
> i'm trying to get a weewx 4.0.0b16 running in conjunction with python3
> installation.
>
> Unfortunately no diagrams are drawn in Skin Seasons.
>
> Enclosed is an extract from the log. I guess I made a mistake during the
> installation or forgot something. Only what...?
>
>
>
>
>
>
>
> Mar 22 14:46:24 raspi02 weewx[19089] DEBUG user.sdr: packet={'extraTemp1':
> 17.1, 'extraHumid1': 54.0, 'dateTime': 1584884781, 'usUnits': 16}
>
> Mar 22 14:46:25 raspi02 weewx[19089] INFO weewx.manager: Added record
> 2020-03-22 14:45:00 CET (1584884700) to database 'weewx_sdr2'
>
> Mar 22 14:46:25 raspi02 weewx[19089] INFO weewx.manager: Added record
> 2020-03-22 14:45:00 CET (1584884700) to daily summary in 'weewx_sdr2'
>
> Mar 22 14:46:25 raspi02 weewx[19089] DEBUG weewx.reportengine: Running
> reports for latest time in the database.
>
> Mar 22 14:46:25 raspi02 weewx[19089] DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
>
> Mar 22 14:46:25 raspi02 weewx[19089] DEBUG weewx.reportengine: Found
> configuration file /home/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport'
>
> Mar 22 14:46:25 raspi02 weewx[19089] DEBUG weewx.cheetahgenerator: Using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras']
>
> Mar 22 14:46:25 raspi02 weewx[19089] DEBUG weewx.manager: Daily summary
> version is 2.0
>
> Mar 22 14:46:27 raspi02 weewx[19089] INFO weewx.cheetahgenerator:
> Generated 8 files for report SeasonsReport in 2.21 seconds
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine: Unable to
> instantiate generator 'weewx.imagegenerator.ImageGenerator'
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   No module named 'Image'
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   Traceback (most recent call last):
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/home/weewx/bin/weeplot/genplot.py", line 15, in 
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   from PIL import Image, ImageDraw
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/usr/local/lib/python3.7/dist-packages/PIL/Image.py", line
> 69, inMar 22 14:46:27 raspi02 weewx[19089] ERROR
> weewx.reportengine:   from . import _imaging as core
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   ImportError: libopenjp2.so.7: Kann die Shared-Object-Datei nicht
> öffnen: Datei oder Verzeichnis nicht gefunden
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> 
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   During handling of the above exception, another exception occurred:
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> 
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   Traceback (most recent call last):
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/reportengine.py", line 180, in run
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   obj = weeutil.weeutil.get_object(generator)(
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in
> get_object
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   mod = __import__(module)
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/home/weewx/bin/weewx/imagegenerator.py", line 19, in
> 
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   import weeplot.genplot
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
> File "/home/weewx/bin/weeplot/genplot.py", line 17, in 
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   import Image, ImageDraw
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   ModuleNotFoundError: No module named 'Image'
>
> Mar 22 14:46:27 raspi02 weewx[19089] ERROR weewx.reportengine:
>   Generator ignored
>
> Mar 22 14:46:27 raspi02 weewx[19089] INFO weewx.reportengine: Copied 0
> files to /var/www/html/weewx-sdr2
>
> Mar 22 14:46:27 raspi02 weewx[19089] DEBUG weewx.reportengine: Report
> 'SmartphoneReport' not enabled. Skipping.
>
> Mar 22 14:46:27 raspi02 weewx[19089] DEBUG weewx.reportengine: Report
> 'MobileReport' not enabled. Skipping.
>
> Mar 22 14:46:27 raspi02 weewx[19089] DEBUG weewx.reportengine: Report
> 'StandardReport' not enabled. Skipping.
>
> Mar 22 14:46:27 raspi02 weewx[19089] DEBUG weewx.reportengine: Report
> 'FTP' not enabled. Skipping.
>
> Mar 22 14:46:27 

Re: [weewx-user] Davis VP 2 and raw data with weewx 3.9.2-1

[Thomas Keffer]

The data emitted by a Davis Vantage is in coded binary. It would look like
gibberish.

The data that is printed by weewxd when run from the command line is fairly
raw. I say "fairly" because StdWXCalculate may have added some values to
it. However, if you set all the options in [StdWXCalculate]/[[Calculations]]
 to 'hardware',
then it will just pass the hardware values along.



On Sat, Mar 21, 2020 at 10:59 AM Ernest Jillson  wrote:

> Is there a way to save off the raw data exactly as it comes out of the
> data logger? I'm having an issue with wind direction using an ultrasonic
> anemometer. I understand when there is no wind, it probably can't give a
> direction (but seems to end up defaulting to 360), but even when there is
> wind sometimes, it is reading exactly 360 although wind direction was
> clearly not that.
>
> I need to show the manufacturer "raw data" from the data logger.  It can't
> be processed by any drivers.  Thanks
>
> Ernie
>
> --
> 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/3fb89021-6bfa-42be-b184-1f0bd562e1fc%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/CAPq0zECqHMmmq2YUfp_gM-tUkvzVO4hdg8H2%2BxPMx6ZbCE6ndw%40mail.gmail.com.

Re: [weewx-user] reports = local time & PC = UTC

[Thomas Keffer]

(By "computer clock" I think he means what is in /etc/timezone, that is,
the 'local' time.)

Unfortunately, this is not possible with the present architecture of WeeWX.
Issue #301  outlines why.

On Fri, Mar 20, 2020 at 8:09 PM John Kline  wrote:

> For Unix/Linux, setting the clock to UTC is the norm and no tricks are
> needed to get WeeWX to show times in the local time zone.
>
> What OS are you running?  If it is NOT Windows, try running the following
> command and reply with the output.
>
> timedatectl -a
>
> On Mar 20, 2020, at 7:33 PM, GCC Observatory 
> wrote:
>
> 
> Hello,
>
> Been using weewx for a while now and have always wondered if there's a way
> to configure it to generate reports that use local time (UTC-5 for me) when
> the PC clock is set to UTC.  I'm asking because my weewx runs on the same
> PC as my observatory control software - I'd prefer to set the computer
> clock to UTC, but the last time I did that, it messed up the weewx
> reports.  Can anyone tell me if it's possible to "trick" weewx into
> generating local time reports while keeping the computer clock set to UTC?
>
> Thanks
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/53687f2e-30ed-418a-8ef7-cff65a4353be%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/6F04D87B-CA86-4FF7-9BE7-F040529F777D%40johnkline.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/CAPq0zEA%2BLZ7%3DLNwo3d_Zf93e2-zEL9%2BXYH6uc8RMLDXOY1ud6A%40mail.gmail.com.

Re: [weewx-user] Re: New Weewx/W34 install works OK, but with error msgs

[Thomas Keffer]

This is almost surely a problem in the skin "Weather34Report." Somewhere in
the template Weather34/w34charts/chartdata/result.csv.tmpl is some
arithmetic, where two numbers are getting added together. One of them is
value Python None, rather than a number.

In general, when writing code or templates for weewx, one must be vigilant
to the possibility that a value might be None, and test for it.

-tk

On Wed, Mar 18, 2020 at 12:05 PM Bill Arthur  wrote:

> Thanks for the quick response!
>
> 3.9.2   Downloaded and installed last night.
>
>
> On Wednesday, March 18, 2020 at 1:56:56 PM UTC-5, Bill Arthur wrote:
>>
>> I just reinstalled Weewx and Weather34. It's working OK, but I get the
>> following error messages. Any idea where the problem lies?
>>
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generate failed with
>> exception ''
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Ignoring
>> template /etc/weewx/skins/Weather34/w34charts/chartdata/result.csv.tmpl
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator:  Reason:
>> unsupported operand type(s) for +: 'float' and 'NoneType'
>> Mar 18 13:50:27 OpiQ-2 weewx[498]:   Traceback (most recent call
>> last):
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 332, in generate
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: 
>> fd.write(str(compiled_template))
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: File
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1045, in
>> __str__
>> Mar 18 13:50:27 OpiQ-2 weewx[498]:   rc = getattr(self,
>> mainMethName)()
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: File
>> "_etc_weewx_skins_Weather34_w34charts_chartdata_result_csv_tmpl.py", line
>> 251, in respond
>> Mar 18 13:50:27 OpiQ-2 weewx[498]:   TypeError: unsupported operand
>> type(s) for +: 'float' and 'NoneType'
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: cheetahgenerator: Generated 3 files
>> for report Weather34Report in 0.70 seconds
>> Mar 18 13:50:27 OpiQ-2 weewx[498]: copygenerator: copied 0 files to
>> /var/weewx/reports
>>
> --
> 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/2f63ba12-4ee2-49eb-9f20-210d11056b58%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/CAPq0zECwH19K3m%2BgninkFi2dTErUsWh3FoTv8f3MYj5WWyRuUw%40mail.gmail.com.

Re: [weewx-user] Dato nuevo en la estructura de la tabla mysql

[Thomas Keffer]

See the section *Adding a new type to the database
* in the
Customizing Guide for instructions on how to add new fields to the database.

On Wed, Mar 18, 2020 at 8:38 AM jose riaño  wrote:

> Buenos días
>
>
> Quiero agregar un dato nuevo a la estructura de la tabla  weewx:
>
> por ejemplo
> mi tabla
>
>
> CREATE TABLE Tabla (`dateTime` INTEGER NOT NULL UNIQUE PRIMARY KEY,
> `usUnits` INTEGER NOT NULL, `interval` INTEGER NOT NULL,  `barometer` REAL,
> `pressure` REAL, `altimeter` REAL, `inTemp` REAL, `outTemp` REAL,
> `inHumidity` REAL, `outHumidity` REAL, `windSpeed` REAL, `windDir` REAL,
> `windGust` REAL, `windGustDir` REAL, `rainRate` REAL, `rain` REAL,
> `dewpoint` REAL, `windchill` REAL, `heatindex` REAL,  `ET` REAL,
> `radiation` REAL, `UV` REAL, `extraTemp1` REAL,  `extraTemp2` REAL,
> `extraTemp3` REAL, `soilTemp1` REAL,  `soilTemp2` REAL, `soilTemp3` REAL,
> `soilTemp4` REAL,  `leafTemp1` REAL, `leafTemp2` REAL, `extraHumid1` REAL,
> `extraHumid2` REAL, `soilMoist1` REAL, `soilMoist2` REAL,  `soilMoist3`
> REAL, `soilMoist4` REAL, `leafWet1` REAL, `leafWet2` REAL,
> `rxCheckPercent` REAL, `txBatteryStatus` REAL,  `consBatteryVoltage` REAL,
> `hail` REAL, `hailRate` REAL,  `heatingTemp` REAL, `heatingVoltage` REAL,
> `supplyVoltage` REAL,  `referenceVoltage` REAL, `windBatteryStatus` REAL,
> `rainBatteryStatus` REAL, `outTempBatteryStatus` REAL,
> `inTempBatteryStatus` REAL);
>
> en que archivo de código fuente encuentro esta estructura ??
>
>
> lo que quiero es que tenga un identificador la tabla  para si identificar
> mi estación..
>
>
> gracias
>
>
>
>
>
>
> --
> 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/f2867ab5-6787-43a8-a251-77efc6977923%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/CAPq0zEBmYgWhO7bnGArCu4Csp9WwEDMGERepiaMgiETNmcHrrA%40mail.gmail.com.

Re: [weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Thomas Keffer]

import weewx

if event.record['usUnits'] == weewx.US:
event.record['extraTemp1'] = ( cpu.temperature * 1.8 ) + 32
else:
event.record['extraTemp1'] = cpu.temperature

-tk


On Wed, Mar 18, 2020 at 8:38 AM Mike Revitt  wrote:

> Thanks Thomas,
>
> Was looking at that but didn't know how, my Raspberry Pi reports the
> temperature in Celsius and the database is in Fahrenheit and obviously a
> check would be best.
>
> But how to do that easily?
>
>
> On Wednesday, March 18, 2020 at 2:14:32 PM UTC, Thomas Keffer wrote:
>>
>> Well done!
>>
>> However, your extension makes the assumption that the archive record is
>> always in US Customary. Best to put a check in there before doing the
>> conversion.
>>
>> -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
> https://groups.google.com/d/msgid/weewx-user/0cd4a4b2-bf30-4f34-a567-4bff9120903f%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/0cd4a4b2-bf30-4f34-a567-4bff9120903f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDHdLg3cUT5yvXo2fdPXYU_kq9rRTUA_8jS8PHbjT_MTw%40mail.gmail.com.

Re: [weewx-user] Re: weewx4 - vantagepro issue

[Thomas Keffer]

In addition to Vince's recommendation:

   1. you should also set debug=1 in weewx.conf, then restart. It may give
   you more clues as to what is going on.
   2. Run the command "dmesg". This will show you if anything is going on
   with the kernel. Long shot, but worth checking.
   3. Is your console connected to AC, or running just on batteries? Low
   batteries can show these symptoms (although the 4.47 V you are seeing is
   pretty normal).

-tk



On Wed, Mar 18, 2020 at 10:10 AM vince  wrote:

> On Wednesday, March 18, 2020 at 9:02:49 AM UTC-7, weerstation Maurik wrote:
>
>> How can a RPi loose 6 seonds when not running weewx for maybe 15min
>>
>>
> All computers can do this if they are starting to fail.
>
> You should be running ntp or systemd equivalent to keep the clock in sync
> with reality.
>
> --
> 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/e10c1057-d745-475d-90e0-03f53dd65a7d%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/CAPq0zEAfdmVPi4T0DeRj5OmGu3tFmjFMxnhwjkG_OqZ%2BZuRhaA%40mail.gmail.com.

Re: [weewx-user] Re: how to insert additional data (cpu temp) into skins?

[Thomas Keffer]

Well done!

However, your extension makes the assumption that the archive record is
always in US Customary. Best to put a check in there before doing the
conversion.

-tk

On Wed, Mar 18, 2020 at 6:34 AM Mike Revitt  wrote:

> Not sure if you are still looking for solutions, but I liked you idea so
> had a look at implementing it in Python.
>
> Turns out it was easier than I thought.
>
> 1) create a python file and put it into the bin/user directory, this file
> gets the CPU temperature, coverts it to Fahrenheit and puts it into the
> extraTemp1 column in the database
>
> import  weewx
> fromweewx.engineimport  StdService
> fromgpiozeroimport  CPUTemperature
>
> class AddCpuTemp(StdService):
>
> def __init__(self, engine, config_dict):
>
>   # Initialize my superclass first:
>   super(AddCpuTemp, self).__init__(engine, config_dict)
>
>   # Bind to any new archive record events:
>   self.bind(weewx.NEW_ARCHIVE_RECORD, self.new_archive_record)
>
> def new_archive_record(self, event):
>
> cpu = CPUTemperature()
>
> event.record['extraTemp1'] = ( cpu.temperature * 1.8 ) + 32
>
>
> 2) modify weewx.conf to call the new file
> [Engine]
>
> [[Services]]
> # This section specifies the services that should be run. They are
> # grouped by type, and the order of services within each group
> # determines the order in which the services will be run.
> prep_services = weewx.engine.StdTimeSynch
> data_services = user.cputemp.AddCpuTemp
>
>
> Now the value can be obtained anywhere you want by
> referencing $current.extraTemp1
> I modified about.inc in the seasons skin with the following
>
> 
>   Server uptime
>   $station.os_uptime
> 
> 
>   Server CPU Temp
>   $current.extraTemp1
> 
> 
>   WeeWX uptime
>   $station.uptime
> 
>
>
> Also you can now access the dayTemp graph to see the plots over time
>
> On Thursday, February 20, 2020 at 4:55:00 PM UTC, Vetti52 wrote:
>>
>> Sorry for being too dumb for python...
>>
>> I want to show the actual cpu temperature in the "About this weather
>> station" section. On my Raspberry Pi I get the result:
>>
>> $ vcgencmd measure_temp
>> temp=53.0'C
>>
>> However, I do not know, how to enter this into a skin file.
>> I gave a first try to
>>
>> > echo exec('vcgencmd measure_temp|sed "s/'/ °/"');
>> ?>
>>
>> resulting in
>> VCHI initialization failed
>>
>> I have added www-data to the video group, but this did not help. But, may
>> be, it is much easier to realize. Please help!
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/51911b10-1bd3-4c73-89cd-22532f89eb63%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/CAPq0zEBTjb0FB4jzqMG0u5Q2%2BhTC6uw8Cb-XeSMCAGCY8fMJaw%40mail.gmail.com.

Re: [weewx-user] Very bad performance leading to "lost connection to mysql server" and weewx endless loop

[Thomas Keffer]

If you are using a database connection to a remote server in the cloud, you
can almost surely expect poor performance.

MySQL servers typically have logs for queries. Can't speak for where your
data center put them, but they are usually in /var/log/mysql or something
similar.

-tk

On Wed, Mar 18, 2020 at 5:51 AM Luftfahrtverein Grünstadt <
webmas...@luftfahrtverein-gruenstadt.de> wrote:

> okay, since it is a paid service in a large data center I will give them a
> call.
> Is there a way for getting more debug information, e.g. log the fired sql
> queries to fire them manually directly on the database?
>
> Am Mittwoch, 18. März 2020 13:16:23 UTC+1 schrieb Thomas Keffer:
>>
>> Well, there is something wrong on the external server or, possibly, the
>> connection between.
>>
>> In general, installations that use MySQL are less reliable than those
>> using SQLite. See the Wiki article *SQLite vs MySQL
>> <https://github.com/weewx/weewx/wiki/SQLite-vs-MySQL>*.
>>
>> -tk
>>
>> On Wed, Mar 18, 2020 at 5:02 AM Luftfahrtverein Grünstadt <
>> webm...@luftfahrtverein-gruenstadt.de> wrote:
>>
>>> Hi Thomas,
>>> thank you for your answer.
>>> No, the MySQL database is not on the pi, it is externally hosted.
>>>
>>> Am Mittwoch, 18. März 2020 12:16:20 UTC+1 schrieb Thomas Keffer:
>>>>
>>>> I take it you are running MySQL on a Raspberry Pi? Could be that the SD
>>>> card is failing.
>>>>
>>>> On Wed, Mar 18, 2020 at 12:23 AM Luftfahrtverein Grünstadt <
>>>> webm...@luftfahrtverein-gruenstadt.de> wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> after updating our raspberry pi (apt-get update & upgrade) I
>>>>> experience very bad performance of weewx resulting in an endless loop of
>>>>> retrying.
>>>>> Here is an excerpt of the log:
>>>>> Mar 18 08:10:18 raspberrypi weewx[467]: manager: Added record
>>>>> 2020-03-18 08:10:00 CET (1584515400) to database 'd0222d5f'
>>>>> Mar 18 08:10:21 raspberrypi weewx[467]: manager: Added record
>>>>> 2020-03-18 08:10:00 CET (1584515400) to daily summary in 'd0222d5f'
>>>>> Mar 18 08:11:00 raspberrypi weewx[467]: cheetahgenerator: Generated 8
>>>>> files for report SeasonsReport in 39.21 seconds
>>>>> ^[[AMar 18 08:14:36 raspberrypi weewx[467]: imagegenerator: Generated
>>>>> 42 images for SeasonsReport in 215.72 seconds
>>>>> Mar 18 08:14:36 raspberrypi weewx[467]: copygenerator: copied 5 files
>>>>> to /var/www/html/weewx
>>>>> Mar 18 08:14:40 raspberrypi weewx[467]: GaugeGenerator: Generated 7
>>>>> images for HTMLPages in 3.42 seconds
>>>>> Mar 18 08:14:40 raspberrypi weewx[467]: translategenerator.pyc:
>>>>> Language is german
>>>>> Mar 18 08:14:48 raspberrypi weewx[467]: historygenerator.pyc:
>>>>> Generated 6 tables in 7.08 seconds
>>>>> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Main loop exiting.
>>>>> Shutting engine down.
>>>>> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Shutting down
>>>>> StdReport thread
>>>>> Mar 18 08:15:14 raspberrypi weewx[467]: cheetahgenerator: Generated 10
>>>>> files for report HTMLPages in 33.72 seconds
>>>>> Mar 18 08:15:14 raspberrypi weewx[467]: copygenerator: copied 3 files
>>>>> to /var/www/html/weewx/Bootstrap
>>>>> Mar 18 08:15:14 raspberrypi weewx[467]: translategenerator.pyc:
>>>>> Language is german
>>>>> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Unable to shut down
>>>>> StdReport thread
>>>>> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Database connection
>>>>> exception: (2013, 'Lost connection to MySQL server during query')
>>>>> Mar 18 08:15:22 raspberrypi weewx[467]:   Waiting 2 minutes
>>>>> then retrying...
>>>>>
>>>>>
>>>>> As you can see generating images / files took very very long (e.g. 215
>>>>> seconds for seasonsreport). I successfully run weewx for 4 years now and 
>>>>> It
>>>>> was never that slow.
>>>>> A few weeks ago I moved from sqlite to mysql without any issues and it
>>>>> worked well, so I do not hink this has any relation to the problem.
>>>>>
>>>>> In addition to the bad performance (i think it is a folllow-up
>>&g

Re: [weewx-user] Installation issues on Synology DS918+ -- No module named configobj

[Thomas Keffer]

Because you installed configobj using pip, but *without root privileges*,
pip did what's called a "user" install. Because "sudo" was not specified,
it could not install configobj in the system directories, so, instead, it
installed in a subdirectory (usually ".local") of your home directory.

Then, when you ran setup.py, it either used a different version of python,
or it used the wrong PYTHONPATH.

There are two possible solutions:

   1. Do the pip installs using "sudo". E.g., "sudo python2 -m pip install
   configobj"
   2. Use the same version of Python when running setup.py:

*python2 setup.py build*

See if that helps.

-tk

On Wed, Mar 18, 2020 at 5:21 AM Ivan Schrooyen 
wrote:

> Hello,
>
> I would like to become a new user of Weewx and install it on my Synology
> NAS (DS918+).
>
> The NAS is running the latest OS from Synology: DSM 6.2.2-24922.
>
> The installation procedure to be followed is according to me the one with
> python.
>
> The NAS has 2 versions of python installed: 2.7.12 (python2) and 3.5.1
> (python3).
>
> I have done the prerequisites:
> - python2 -m pip install configobj
> - python2 -m pip install Cheetah
> - python2 -m pip install pillow
> - python2 -m pip install pyserial
> - python2 -m pip install pyusb
>
> I have downloaded the package (3.9.2), then uncompressed, and I am finally
> stuck at the "./setup.py build" command that does not run.
>
> The error message is the following:
> root@NAS:~/weewx/weewx-3.9.2# ./setup.py build
> Traceback (most recent call last):
>   File "./setup.py", line 19, in 
> import configobj
> ImportError: No module named configobj
>
> For information, the installation of configobj returns the following:
> root@NAS:~/weewx/weewx-3.9.2# python2 -m pip install configobj
> DEPRECATION: Python 2.7 reached the end of its life on January 1st, 2020.
> Please upgrade your Python as Python 2.7 is no longer maintained. A future
> version of pip will drop support for Python 2.7. More details about Python
> 2 support in pip, can be found at
> https://pip.pypa.io/en/latest/development/release-process/#python-2-support
> Processing
> /root/.cache/pip/wheels/c1/12/7a/c676d85d30d1aa17f3882dab925a777ab1f651c4072cccefd7/configobj-5.0.6-py2-none-any.whl
> Requirement already satisfied: six in /usr/lib/python2.7/site-packages
> (from configobj) (1.12.0)
> Installing collected packages: configobj
> Successfully installed configobj-5.0.6
>
> Does anyone know what I should do or try?
>
> Thanks in advance,
> Ivan
>
>
>
> --
> 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/378728d5-fe58-4bdc-acb6-102dcbeac6fe%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/CAPq0zECzAAvrsf-g%3DWEjjuLiWuTru2Kd_eD-t_Z3HKfkagh9mQ%40mail.gmail.com.

Re: [weewx-user] Very bad performance leading to "lost connection to mysql server" and weewx endless loop

[Thomas Keffer]

Well, there is something wrong on the external server or, possibly, the
connection between.

In general, installations that use MySQL are less reliable than those using
SQLite. See the Wiki article *SQLite vs MySQL
<https://github.com/weewx/weewx/wiki/SQLite-vs-MySQL>*.

-tk

On Wed, Mar 18, 2020 at 5:02 AM Luftfahrtverein Grünstadt <
webmas...@luftfahrtverein-gruenstadt.de> wrote:

> Hi Thomas,
> thank you for your answer.
> No, the MySQL database is not on the pi, it is externally hosted.
>
> Am Mittwoch, 18. März 2020 12:16:20 UTC+1 schrieb Thomas Keffer:
>>
>> I take it you are running MySQL on a Raspberry Pi? Could be that the SD
>> card is failing.
>>
>> On Wed, Mar 18, 2020 at 12:23 AM Luftfahrtverein Grünstadt <
>> webm...@luftfahrtverein-gruenstadt.de> wrote:
>>
>>> Hi all,
>>>
>>> after updating our raspberry pi (apt-get update & upgrade) I experience
>>> very bad performance of weewx resulting in an endless loop of retrying.
>>> Here is an excerpt of the log:
>>> Mar 18 08:10:18 raspberrypi weewx[467]: manager: Added record 2020-03-18
>>> 08:10:00 CET (1584515400) to database 'd0222d5f'
>>> Mar 18 08:10:21 raspberrypi weewx[467]: manager: Added record 2020-03-18
>>> 08:10:00 CET (1584515400) to daily summary in 'd0222d5f'
>>> Mar 18 08:11:00 raspberrypi weewx[467]: cheetahgenerator: Generated 8
>>> files for report SeasonsReport in 39.21 seconds
>>> ^[[AMar 18 08:14:36 raspberrypi weewx[467]: imagegenerator: Generated 42
>>> images for SeasonsReport in 215.72 seconds
>>> Mar 18 08:14:36 raspberrypi weewx[467]: copygenerator: copied 5 files to
>>> /var/www/html/weewx
>>> Mar 18 08:14:40 raspberrypi weewx[467]: GaugeGenerator: Generated 7
>>> images for HTMLPages in 3.42 seconds
>>> Mar 18 08:14:40 raspberrypi weewx[467]: translategenerator.pyc: Language
>>> is german
>>> Mar 18 08:14:48 raspberrypi weewx[467]: historygenerator.pyc: Generated
>>> 6 tables in 7.08 seconds
>>> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Main loop exiting.
>>> Shutting engine down.
>>> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Shutting down StdReport
>>> thread
>>> Mar 18 08:15:14 raspberrypi weewx[467]: cheetahgenerator: Generated 10
>>> files for report HTMLPages in 33.72 seconds
>>> Mar 18 08:15:14 raspberrypi weewx[467]: copygenerator: copied 3 files to
>>> /var/www/html/weewx/Bootstrap
>>> Mar 18 08:15:14 raspberrypi weewx[467]: translategenerator.pyc: Language
>>> is german
>>> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Unable to shut down
>>> StdReport thread
>>> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Database connection
>>> exception: (2013, 'Lost connection to MySQL server during query')
>>> Mar 18 08:15:22 raspberrypi weewx[467]:   Waiting 2 minutes then
>>> retrying...
>>>
>>>
>>> As you can see generating images / files took very very long (e.g. 215
>>> seconds for seasonsreport). I successfully run weewx for 4 years now and It
>>> was never that slow.
>>> A few weeks ago I moved from sqlite to mysql without any issues and it
>>> worked well, so I do not hink this has any relation to the problem.
>>>
>>> In addition to the bad performance (i think it is a folllow-up problem)
>>> I got database connection exceptions (2013, lost connection during query),
>>> but adding records to the database work fine. Is there a way to set a
>>> higher connection timeout value?
>>>
>>> I tried already rebuilding the daily values several times, setting the
>>> archive interval to 5 min (before it was 1 min) but nothing helps.
>>>
>>> Any help is really appreciated! What do you need to know?
>>>
>>> Thank you so much!
>>>
>>> Sebastian
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/570b85ea-14ce-4dd0-b5c7-354d72e7b7d1%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/570b85ea-14ce-4dd0-b5c7-354d72e7b7d1%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To 

Re: [weewx-user] weewx4 - vantagepro issue

[Thomas Keffer]

I think WeeWX is probably working fine when you ran it from the command
line. It's just that its archive interval is 10 minutes, and you did not
let it run that long, so you did not see any new reports.

As for the I/O errors while running as a daemon: I noticed that the time on
the Vantage clock was 640 seconds fast, then two minutes later it was 641
seconds slow. Not sure what happened there. Had the RPi just been booted,
and had not settled on a time? If you let the RPi run for a few minutes,
*then* start the daemon, what happens?

On Wed, Mar 18, 2020 at 4:56 AM weerstation Maurik <
l...@weerstationmaurik.nl> wrote:

> I have installed version 4 according to the docs in the install archive on
> my RPi.
> Added my old databases (54MB) in the weewx/archive folder and started
> weewx from the command line.
> A full import of the database took place and it grew to 60MB.
>
> I have however problems getting data in the system as the connection to
> the vantag pro seems off.
>
> When running as a daemon I get
> ERROR weewx.drivers.vantage: LOOP try #1; error: Expected to read 99
> chars; got 0 instead
> and later
>ERROR weewx.drivers.vantage: DMPAFT try #1; error: Timeout in
> get_data_with_crc16
>
> If I run it from the command line after issuing the command I get the loop
> packets visible and this continues till ctrl-c
> LOOP:   2020-03-18 11:47:10 CET (1584528430) altimeter: None, appTemp:
> 55.1173360971, barometer: 30.288, beaufort: 0, cloudbase: 3768.61590836,
> consBatteryVoltage: 4.47, dateTime: 1584528430, dayET: 0.021, dayRain: 0.0,
> dewpoint: 40.7060900032, extraAlarm1: 0, extraAlarm2: 0, extraAlarm3: 0,
> extraAlarm4: 0, extraAlarm5: 0, extraAlarm6: 0, extraAlarm7: 0,
> extraAlarm8: 0, forecastIcon: 6, forecastRule: 9, heatindex: 57.2, humidex:
> 57.2, inDewpoint: 45.1749354896, inHumidity: 44.0, insideAlarm: 0, inTemp:
> 67.9, leafWet4: 0.0, maxSolarRad: 554.161850926, monthET: 0.71, monthRain:
> 2.5039369926, outHumidity: 54.0, outsideAlarm1: 0, outsideAlarm2: 0,
> outTemp: 57.2, pressure: None, radiation: 322.0, rain: None, rainAlarm: 0,
> rainRate: 0.0, soilLeafAlarm1: 0, soilLeafAlarm2: 0, soilLeafAlarm3: 0,
> soilLeafAlarm4: 0, stormRain: 0.0, sunrise: 1584511920.0, sunset:
> 158404.0, txBatteryStatus: 0, usUnits: 1, UV: 1.5, windchill: 57.2,
> windDir: None, windGust: 0.0, windGustDir: None, windSpeed: 0.0, yearET:
> 2.2, yearRain: 19.4015746848
>
> The website build remains stuck at the last date from the old database
> (altough it is refreshed in the new layout).
>
> I added relevant sections from the syslog
> Anybody any ideas where to look?
> Thanks,
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/1f91fe4b-340c-47cb-94df-1aa5d32585e4%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/CAPq0zEDLQ0uQ%3DmeR%3DG3v9VHU15BELYW16pmP0PTkv3z%2BMH%2BW-w%40mail.gmail.com.

Re: [weewx-user] Very bad performance leading to "lost connection to mysql server" and weewx endless loop

[Thomas Keffer]

I take it you are running MySQL on a Raspberry Pi? Could be that the SD
card is failing.

On Wed, Mar 18, 2020 at 12:23 AM Luftfahrtverein Grünstadt <
webmas...@luftfahrtverein-gruenstadt.de> wrote:

> Hi all,
>
> after updating our raspberry pi (apt-get update & upgrade) I experience
> very bad performance of weewx resulting in an endless loop of retrying.
> Here is an excerpt of the log:
> Mar 18 08:10:18 raspberrypi weewx[467]: manager: Added record 2020-03-18
> 08:10:00 CET (1584515400) to database 'd0222d5f'
> Mar 18 08:10:21 raspberrypi weewx[467]: manager: Added record 2020-03-18
> 08:10:00 CET (1584515400) to daily summary in 'd0222d5f'
> Mar 18 08:11:00 raspberrypi weewx[467]: cheetahgenerator: Generated 8
> files for report SeasonsReport in 39.21 seconds
> ^[[AMar 18 08:14:36 raspberrypi weewx[467]: imagegenerator: Generated 42
> images for SeasonsReport in 215.72 seconds
> Mar 18 08:14:36 raspberrypi weewx[467]: copygenerator: copied 5 files to
> /var/www/html/weewx
> Mar 18 08:14:40 raspberrypi weewx[467]: GaugeGenerator: Generated 7 images
> for HTMLPages in 3.42 seconds
> Mar 18 08:14:40 raspberrypi weewx[467]: translategenerator.pyc: Language
> is german
> Mar 18 08:14:48 raspberrypi weewx[467]: historygenerator.pyc: Generated 6
> tables in 7.08 seconds
> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Main loop exiting.
> Shutting engine down.
> Mar 18 08:15:02 raspberrypi weewx[467]: engine: Shutting down StdReport
> thread
> Mar 18 08:15:14 raspberrypi weewx[467]: cheetahgenerator: Generated 10
> files for report HTMLPages in 33.72 seconds
> Mar 18 08:15:14 raspberrypi weewx[467]: copygenerator: copied 3 files to
> /var/www/html/weewx/Bootstrap
> Mar 18 08:15:14 raspberrypi weewx[467]: translategenerator.pyc: Language
> is german
> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Unable to shut down
> StdReport thread
> Mar 18 08:15:22 raspberrypi weewx[467]: engine: Database connection
> exception: (2013, 'Lost connection to MySQL server during query')
> Mar 18 08:15:22 raspberrypi weewx[467]:   Waiting 2 minutes then
> retrying...
>
>
> As you can see generating images / files took very very long (e.g. 215
> seconds for seasonsreport). I successfully run weewx for 4 years now and It
> was never that slow.
> A few weeks ago I moved from sqlite to mysql without any issues and it
> worked well, so I do not hink this has any relation to the problem.
>
> In addition to the bad performance (i think it is a folllow-up problem) I
> got database connection exceptions (2013, lost connection during query),
> but adding records to the database work fine. Is there a way to set a
> higher connection timeout value?
>
> I tried already rebuilding the daily values several times, setting the
> archive interval to 5 min (before it was 1 min) but nothing helps.
>
> Any help is really appreciated! What do you need to know?
>
> Thank you so much!
>
> Sebastian
>
> --
> 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/570b85ea-14ce-4dd0-b5c7-354d72e7b7d1%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/CAPq0zED8y0h6O28x%2BTb3G43Cb7QOjr05XOwdM-6Fc1DdDWtG9g%40mail.gmail.com.

Re: [weewx-user] Version 4

[Thomas Keffer]

It looks like the Cumulus extension has not been ported to Python 3.

You'll have to talk to the extension author about that.

On Tue, Mar 17, 2020 at 12:10 AM Ξ  wrote:

> Thanks, it installed OK now but it run into a problem with
> CumulusRealTime: # $Id: crt.py 1477 2016-04-10 13:19:56Z mwall $
>
>
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] DEBUG weewx.engine:
> Loading service user.crt.CumulusRealTime
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__: Caught
> unrecoverable exception:
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   invalid syntax (crt.py, line 376)
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   Traceback (most recent call last):
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
> File "/home/weewx/bin/weewxd", line 148, in main
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   engine = weewx.engine.StdEngine(config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
> File "/home/weewx/bin/weewx/engine.py", line 75, in __init__
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   self.loadServices(config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
> File "/home/weewx/bin/weewx/engine.py", line 136, in loadServices
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   obj = weeutil.weeutil.get_object(svc)(self,config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
> File "/home/weewx/bin/weeutil/weeutil.py", line 1093, in
> get_object
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   mod = __import__(module)
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
> File "/home/weewx/bin/user/crt.py", line 376
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   except Exception, e:
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   ^
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   SyntaxError: invalid syntax
> Mar 17 08:55:50 alarmpi weewxd[415]: weewx[415] CRITICAL __main__:
>   Exiting.
> Mar 17 08:55:50 alarmpi weewxd[415]: Traceback (most recent call last):
> Mar 17 08:55:50 alarmpi weewxd[415]:   File "/home/weewx/bin/weewxd",
> line 261, in 
> Mar 17 08:55:50 alarmpi weewxd[415]: main()
> Mar 17 08:55:50 alarmpi weewxd[415]:   File "/home/weewx/bin/weewxd",
> line 148, in main
> Mar 17 08:55:50 alarmpi weewxd[415]: engine = weewx.engine.StdEngine(
> config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]:   File
> "/home/weewx/bin/weewx/engine.py", line 75, in __init__
> Mar 17 08:55:50 alarmpi weewxd[415]: self.loadServices(config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]:   File
> "/home/weewx/bin/weewx/engine.py", line 136, in loadServices
> Mar 17 08:55:50 alarmpi weewxd[415]: obj = weeutil.weeutil.get_object(
> svc)(self,config_dict)
> Mar 17 08:55:50 alarmpi weewxd[415]:   File
> "/home/weewx/bin/weeutil/weeutil.py", line 1093, in get_object
> Mar 17 08:55:50 alarmpi weewxd[415]: mod = __import__(module)
> Mar 17 08:55:50 alarmpi weewxd[415]:   File "/home/weewx/bin/user/crt.py",
> line 376
> Mar 17 08:55:50 alarmpi weewxd[415]: except Exception, e:
> Mar 17 08:55:50 alarmpi weewxd[415]: ^
> Mar 17 08:55:50 alarmpi weewxd[415]: SyntaxError: invalid syntax
> Mar 17 08:55:50 alarmpi systemd[1]: weewx.service: Main process exited,
> code=exited, status=1/FAILURE
> Mar 17 08:55:50 alarmpi systemd[1]: weewx.service: Failed with result
> 'exit-code'.
>
>
>
> --
> 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/941747c7-2fb6-4833-9115-684b2cefa306%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/CAPq0zEC9x-a9ok3yYXAUvTJGNrKU-ab32tK2frNucyNc1bi1Yg%40mail.gmail.com.

Re: [weewx-user] Version 4

[Thomas Keffer]

Take a look at the (beta version) of the instructions for setup.py
installations. You can find it at /home/weewx/docs/setup.htm. You must use
pip, which will install setuptools for you.

-tk

On Mon, Mar 16, 2020 at 3:11 PM Ξ  wrote:

> So I currently have 4.0.0b14, I tried installing belchertown-1.0.1 and I
> got the following:
>
> [root@alarmpi weewx]# /home/weewx/bin/wee_extension --install
> weewx-belchertown-release-1.0.1.tar.gz
> Request to install 'weewx-belchertown-release-1.0.1.tar.gz'
> Extracting from tar archive weewx-belchertown-release-1.0.1.tar.gz
> Traceback (most recent call last):
>   File "/home/weewx/bin/wee_extension", line 88, in 
> main()
>   File "/home/weewx/bin/wee_extension", line 80, in main
> ext.install_extension(options.install)
>   File "/home/weewx/bin/weecfg/extension.py", line 116, in
> install_extension
> self.tmpdir, self.logger)
>   File "/home/weewx/bin/weecfg/__init__.py", line 1645, in extract_tar
> tar_archive = tarfile.open(filename, mode='r')
>   File "/usr/lib/python2.7/tarfile.py", line 1680, in open
> raise ReadError("file could not be opened successfully")
> tarfile.ReadError: file could not be opened successfully
>
>
>
> I thought of upgrading to 4.0.0b16 and this is what happened:
> [root@alarmpi weewx-4.0.0b16]# ./setup.py build
> Traceback (most recent call last):
>   File "./setup.py", line 31, in 
> from setuptools import setup, find_packages
> ImportError: No module named setuptools
>
>
> Linux alarmpi 4.9.61-1-ARCH #1 SMP Sun Nov 12 00:26:55 UTC 2017 armv6l
> GNU/Linux
>
> --
> 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/d7037cd5-6dc1-41b8-8b97-7ef050375772%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/CAPq0zEAuvz2Mj48q8x-bKp9-HcadrDB59z5s31azYTgDYopJJw%40mail.gmail.com.

Re: [weewx-user] Whew as a service on Raspberry Pi

[Thomas Keffer]

You should still try to figure out the root causes of the crashes. WeeWX is
capable of going weeks without a reboot. Here's an example where it's been
running continuously for well over a year:
http://www.threefools.org/weewx/status/index.html

-tk

On Mon, Mar 16, 2020 at 8:47 AM Mike Revitt  wrote:

> Thanks Thomas,
>
> I found a parameter I can set in the service file which I am currently
> testing. Should know in a day or 2 if it has worked
>
> [Service]
> Restart=always
> RestartSec=30
>
>
>
>
> On Monday, March 16, 2020 at 12:33:15 PM UTC, Thomas Keffer wrote:
>>
>> I would suggest looking directly at the log at /var/log/syslog, rather
>> than rely on status commands. This may give you clues. For example, systemd
>> may be harvesting weewxd for memory.
>>
>> 'Enabling' a process means it will get started *when the system boots,* not
>> after a crash.
>>
>> -tk
>>
>> On Mon, Mar 16, 2020 at 1:02 AM Mike Revitt  wrote:
>>
>>> I am running weewx as a service on my Raspberry Pi and have been having
>>> problems with durability.
>>>
>>> Having been running weewx for several years on my Mac I know that from
>>> time to time the service will stop,  but on my Mac they are always
>>> restarted by the daemon service.
>>>
>>> But on the Raspberry Pi, whenever it stops it just stays stopped.
>>>
>>> I originally followed the directions in the Debian section of WeeWX:
>>> Installation using setup.py but when this stopped it gave no useful
>>> information. I then found a method for using systems.service at
>>> https://github.com/weewx/weewx/wiki/systemd and gave that a goe.
>>>
>>> This has also failed to keep the service running but has a little more
>>> info to go on.
>>>
>>> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl status weewx
>>> ● weewx.service - weewx weather system
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
>>> preset: enabled)
>>>Active: inactive (dead) since Sat 2020-03-14 02:51:14 GMT; 2 days ago
>>>  Main PID: 25401
>>>
>>> Mar 14 02:50:14 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> weewx.manager: Added record 2020-03-14 02:50:00 GMT (1584154200) to dai
>>> Mar 14 02:50:16 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> weewx.cheetahgenerator: Generated 7 files for report SeasonsReport in 1
>>> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> weewx.imagegenerator: Generated 9 images for report SeasonsReport in 0.
>>> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> weewx.reportengine: Copied 0 files to /var/www/html/MountWeather
>>> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> botocore.credentials: Found credentials in shared credentials file: ~/.
>>> Mar 14 02:50:20 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> user.s3upload: S3UploadGenerator: AWS-S3 copied 16 files to S3 in 3.32
>>> Mar 14 02:50:21 raspberrypi weewxd[25401]: weewx[25401] INFO
>>> botocore.credentials: Found credentials in shared credentials file: ~/.
>>> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Killing process
>>> 25401 (weewxd) with signal SIGKILL.
>>> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Killing process
>>> 25401 (weewxd) with signal SIGKILL.
>>> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Succeeded.
>>>
>>>
>>> The process has died during the boto copy to S3, and I am wondering if
>>> this is a network timeout or something, and this does appear to be where it
>>> normally stops.
>>>
>>> However I am also using the command sudo systemctl enable weewx which is
>>> supposed to restart dead processes, but as you can see it isn't.
>>>
>>> If I restart it it works perfectly for the next several hours then does
>>> this again.
>>>
>>> Anyone got any experience of setting this up on a Raspberry Pi
>>>
>>> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl start weewx
>>> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl status weewx
>>> ● weewx.service - weewx weather system
>>>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
>>> preset: enabled)
>>>Active: active (running) since Mon 2020-03-16 08:01:30 GMT; 1s ago
>>>  Main PID: 18479 (weewxd)
>>> Tasks: 1 (limit: 2200)
>>>Memory: 7.5M
>>>CGroup: /system.slice/weewx.

Re: [weewx-user] Formatting stats.py extension

[Thomas Keffer]

For this to work, you would need to specify your new 'contexts' in the
constructor to TimespanBinder. Something like this (NOT TESTED):

# First, create TimespanBinder object for all time. This one is easy
# because the object timespan already holds all valid times to be
# used in the report.
all_stats = TimespanBinder(timespan,
   db_lookup,
   context='alltime',
   formatter=self.generator.formatter,
   converter=self.generator.converter,
   skin_dict=self.generator.skin_dict)
  # 4

See if that helps.

-tk



On Mon, Mar 16, 2020 at 7:35 AM Mike Revitt  wrote:

> I am successfully running the stats.py extension as detailed here
> http://www.weewx.com/docs/customizing.htm#defining_new_tags and am now
> trying to format the output.
>
>
> The output is displayed in statistics.html using the syntax shown below
>
> 
> 
> Maximum temperature to date: 
> $alltime.outTemp.max
> 
> 
> Minimum temperature to date: 
> $alltime.outTemp.min
> 
> 
> Rain over the last seven days: 
> $seven_day.rain.sum
> 
> 
>
> and I created 2 new tags in weewx.conf expecting this to change the format
> as shown below
>
> TimeFormats
>
> hour= %H:%M
> day = %H:%M
> seven_day   = %H:%M on %a
> week= %H:%M on %a
> month   = %a %d %H:%M
> year= %a %d-%b %H:%M
> rainyear= %d-%b-%Y %H:%M
> alltime = %A %d-%b-%Y %H:%M
> current = %a %d-%b-%Y %H:%M
> ephem_day   = %H:%M
> ephem_year  = %d-%b-%Y %H:%M
>
>
> However whilst the day, week and year tags are being used seven_day and
> alltime are being ignored. The output that is using used is the current
> format.
>
> Anyone know what I am doing wrong?
>
> --
> 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/9ec3620f-4154-4506-9194-4b880a318776%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/CAPq0zEDB-97YoE6Y641k_Bw-Y7q%3DPuQPPNPCUaQcRbm0Yabb2Q%40mail.gmail.com.

Re: [weewx-user] Whew as a service on Raspberry Pi

[Thomas Keffer]

I would suggest looking directly at the log at /var/log/syslog, rather than
rely on status commands. This may give you clues. For example, systemd may
be harvesting weewxd for memory.

'Enabling' a process means it will get started *when the system boots,* not
after a crash.

-tk

On Mon, Mar 16, 2020 at 1:02 AM Mike Revitt  wrote:

> I am running weewx as a service on my Raspberry Pi and have been having
> problems with durability.
>
> Having been running weewx for several years on my Mac I know that from
> time to time the service will stop,  but on my Mac they are always
> restarted by the daemon service.
>
> But on the Raspberry Pi, whenever it stops it just stays stopped.
>
> I originally followed the directions in the Debian section of WeeWX:
> Installation using setup.py but when this stopped it gave no useful
> information. I then found a method for using systems.service at
> https://github.com/weewx/weewx/wiki/systemd and gave that a goe.
>
> This has also failed to keep the service running but has a little more
> info to go on.
>
> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl status weewx
> ● weewx.service - weewx weather system
>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>Active: inactive (dead) since Sat 2020-03-14 02:51:14 GMT; 2 days ago
>  Main PID: 25401
>
> Mar 14 02:50:14 raspberrypi weewxd[25401]: weewx[25401] INFO
> weewx.manager: Added record 2020-03-14 02:50:00 GMT (1584154200) to dai
> Mar 14 02:50:16 raspberrypi weewxd[25401]: weewx[25401] INFO
> weewx.cheetahgenerator: Generated 7 files for report SeasonsReport in 1
> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
> weewx.imagegenerator: Generated 9 images for report SeasonsReport in 0.
> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
> weewx.reportengine: Copied 0 files to /var/www/html/MountWeather
> Mar 14 02:50:17 raspberrypi weewxd[25401]: weewx[25401] INFO
> botocore.credentials: Found credentials in shared credentials file: ~/.
> Mar 14 02:50:20 raspberrypi weewxd[25401]: weewx[25401] INFO
> user.s3upload: S3UploadGenerator: AWS-S3 copied 16 files to S3 in 3.32
> Mar 14 02:50:21 raspberrypi weewxd[25401]: weewx[25401] INFO
> botocore.credentials: Found credentials in shared credentials file: ~/.
> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Killing process
> 25401 (weewxd) with signal SIGKILL.
> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Killing process
> 25401 (weewxd) with signal SIGKILL.
> Mar 14 02:51:14 raspberrypi systemd[1]: weewx.service: Succeeded.
>
>
> The process has died during the boto copy to S3, and I am wondering if
> this is a network timeout or something, and this does appear to be where it
> normally stops.
>
> However I am also using the command sudo systemctl enable weewx which is
> supposed to restart dead processes, but as you can see it isn't.
>
> If I restart it it works perfectly for the next several hours then does
> this again.
>
> Anyone got any experience of setting this up on a Raspberry Pi
>
> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl start weewx
> pi@raspberrypi:/var/www/html/MountWeather $ sudo systemctl status weewx
> ● weewx.service - weewx weather system
>Loaded: loaded (/etc/systemd/system/weewx.service; enabled; vendor
> preset: enabled)
>Active: active (running) since Mon 2020-03-16 08:01:30 GMT; 1s ago
>  Main PID: 18479 (weewxd)
> Tasks: 1 (limit: 2200)
>Memory: 7.5M
>CGroup: /system.slice/weewx.service
>└─18479 /usr/bin/python /home/weewx/bin/weewxd --daemon
> --pidfile=/run/weewx.pid /home/weewx/weewx.conf
>
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.restx:
> Wunderground: Posting not enabled.
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.restx:
> PWSweather: Posting not enabled.
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.restx:
> CWOP: Posting not enabled.
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.restx:
> WOW: Posting not enabled.
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.restx:
> AWEKAS: Posting not enabled.
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO __main__:
> Starting up weewx version 4.0.0b14
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.engine:
> Clock error is -0.12 seconds (positive is fast)
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.engine:
> Using binding 'wx_binding' to database 'weewx.sdb'
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO
> weewx.manager: Starting backfill of daily summaries
> Mar 16 08:01:31 raspberrypi weewxd[18479]: weewx[18479] INFO weewx.engine:
> Starting main packet loop.
>
>
>
> --
> 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 

Re: [weewx-user] Version 4

[Thomas Keffer]

Yes. The weewx.conf specifications take precedence. See the section *How
options work <http://www.weewx.com/docs/customizing.htm#How_options_work>* in
the Customizing Guide.

On Fri, Mar 13, 2020 at 12:40 AM Ξ  wrote:

> Forgot to specify: Standard skin.
> The skin.conf files are identical but it's the TimeFormats section
> in weewx.conf which is different and takes precedence I suppose:
> This is from skin.conf
> [[TimeFormats]]
> # This section sets the string format to be used for each time
> scale.
> # The values below will work in every locale, but may not look
> # particularly attractive. See the Customizing Guide for
> alternatives.
>
> day= %X
> week   = %X (%A)
> month  = %d/%b/%Y %X
> year   = %d/%b/%Y %X
> rainyear   = %d/%b/%Y %X
> current= %d/%b/%Y %X
> ephem_day  = %X
> ephem_year = %d/%b/%Y %X
>
> and weewx.conf
> TimeFormats
>
> hour = %H:%M
> day = %X
> week = %X (%A)
> month = %x %X
> year = %x %X
> rainyear = %x %X
> current = %x %X
> ephem_day = %X
> ephem_year = %x %X
>
>
>
> On Thursday, March 12, 2020 at 3:21:05 PM UTC+2, Thomas Keffer wrote:
>>
>> Which skin?
>>
>> The formatting should be as before: set in skin.conf, possibly overridden
>> in weewx.conf.
>>
>> Look for section [[TimeFormats]] in skin.conf and TimeFormats in
>> weewx.conf. What do they show?
>>
>> -tk
>>
>> On Thu, Mar 12, 2020 at 3:10 AM Ξ  wrote:
>>
>>> I installed it yesterday and I wonder where the value for
>>> $current.dateTime is taken from because now the date appears
>>> in the m/d/ format, I've set it to dd/mmm/ and that's how it
>>> appears under plots, but in the title it's changed, so far this is the only
>>> setting I've noticed it didn't inherit from the old config v3.7.1, I
>>> upgraded using setup.py
>>>
>>> Ivo
>>>
>>> On Thursday, March 12, 2020 at 2:25:18 AM UTC+2, Thomas Keffer wrote:
>>>>
>>>> It's pretty much ready to go. The problem is packaging. We're trying to
>>>> simplify the support matrix to something we can handle, and it's not
>>>> proving to be easy.
>>>>
>>>> On Wed, Mar 11, 2020 at 1:01 PM Keimpe Bleeker 
>>>> wrote:
>>>>
>>>>> Hi Tom, others, After many using W##%##, based on a PC-server,
>>>>> for many years now, I'm waiting for some month to get my wx-station
>>>>> up-and-running with Weewx 4.#, based on RaspberryPi. Everything prepared 
>>>>> on
>>>>> Weewx 3.9.2, but that version is not able to import the station history
>>>>> from WU. Tthat is the reason I'm waiting for the release of 4.#. Any idea
>>>>> when this will happen? Regards from Friesland (sneak preview:
>>>>> https://oentsjerk.eu/wwx/)
>>>>>
>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups "weewx-user" group.
>>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>>> an email to weewx...@googlegroups.com.
>>>>> To view this discussion on the web visit
>>>>> https://groups.google.com/d/msgid/weewx-user/cc1ee19c-03b7-499c-a719-094af13240ea%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/weewx-user/cc1ee19c-03b7-499c-a719-094af13240ea%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/2f501a7d-2971-44c3-939c-5850f35bb1c8%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/2f501a7d-2971-44c3-939c-5850f35bb1c8%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/34d7e1ec-c9e7-4fd8-8288-97cbd84a2366%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/34d7e1ec-c9e7-4fd8-8288-97cbd84a2366%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEBFkovFSVK_2eA83YOivSJBk-gwvY1XiFkOyXogBa26Ww%40mail.gmail.com.

Re: [weewx-user] Version 4

[Thomas Keffer]

Which skin?

The formatting should be as before: set in skin.conf, possibly overridden
in weewx.conf.

Look for section [[TimeFormats]] in skin.conf and TimeFormats in
weewx.conf. What do they show?

-tk

On Thu, Mar 12, 2020 at 3:10 AM Ξ  wrote:

> I installed it yesterday and I wonder where the value for
> $current.dateTime is taken from because now the date appears in
> the m/d/ format, I've set it to dd/mmm/ and that's how it appears
> under plots, but in the title it's changed, so far this is the only setting
> I've noticed it didn't inherit from the old config v3.7.1, I upgraded
> using setup.py
>
> Ivo
>
> On Thursday, March 12, 2020 at 2:25:18 AM UTC+2, Thomas Keffer wrote:
>>
>> It's pretty much ready to go. The problem is packaging. We're trying to
>> simplify the support matrix to something we can handle, and it's not
>> proving to be easy.
>>
>> On Wed, Mar 11, 2020 at 1:01 PM Keimpe Bleeker  wrote:
>>
>>> Hi Tom, others, After many using W##%##, based on a PC-server, for
>>> many years now, I'm waiting for some month to get my wx-station
>>> up-and-running with Weewx 4.#, based on RaspberryPi. Everything prepared on
>>> Weewx 3.9.2, but that version is not able to import the station history
>>> from WU. Tthat is the reason I'm waiting for the release of 4.#. Any idea
>>> when this will happen? Regards from Friesland (sneak preview:
>>> https://oentsjerk.eu/wwx/)
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/cc1ee19c-03b7-499c-a719-094af13240ea%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/cc1ee19c-03b7-499c-a719-094af13240ea%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/2f501a7d-2971-44c3-939c-5850f35bb1c8%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/2f501a7d-2971-44c3-939c-5850f35bb1c8%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDGpBZYgkBa4P99F9SLzxDEZa8yK_QaXXjxtYao9DRDMw%40mail.gmail.com.

Re: [weewx-user] Version 4

[Thomas Keffer]

It's pretty much ready to go. The problem is packaging. We're trying to
simplify the support matrix to something we can handle, and it's not
proving to be easy.

On Wed, Mar 11, 2020 at 1:01 PM Keimpe Bleeker  wrote:

> Hi Tom, others, After many using W##%##, based on a PC-server, for
> many years now, I'm waiting for some month to get my wx-station
> up-and-running with Weewx 4.#, based on RaspberryPi. Everything prepared on
> Weewx 3.9.2, but that version is not able to import the station history
> from WU. Tthat is the reason I'm waiting for the release of 4.#. Any idea
> when this will happen? Regards from Friesland (sneak preview:
> https://oentsjerk.eu/wwx/)
>
> --
> 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/cc1ee19c-03b7-499c-a719-094af13240ea%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/CAPq0zECL3JCJ1ih5G9k0Uh6tLQ3MHQjV70uw%2BBPAWM68h2CQJQ%40mail.gmail.com.

Re: [weewx-user] 4 beta test report

[Thomas Keffer]

LOL! Good eye! I've replaced it with something more general.

On Mon, Mar 9, 2020 at 1:09 PM vince  wrote:

> On Monday, March 9, 2020 at 12:55:43 PM UTC-7, Thomas Keffer wrote:
>>
>> It's all in the Wiki white paper
>> <https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging>.
>>
>>
> Interesting stuff - thanks.
>
> At the very bottom of the wiki there is a line saying "filepile:"  (?)
> You might want to make it a little clearer that is just an example, before
> folks copy+paste that literally as-is
>
> Nice writeup !
>
>
>
> --
> 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/724e1e5b-b2b3-428f-8db4-20e78b2cc05f%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/724e1e5b-b2b3-428f-8db4-20e78b2cc05f%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEA9-7iggHxSvE1_v%3D4h9d6kLzYOO-UksPUtDGD6zbrZsQ%40mail.gmail.com.

Re: [weewx-user] 4 beta test report

[Thomas Keffer]

It's all in the Wiki white paper
<https://github.com/weewx/weewx/wiki/WeeWX-v4-and-logging>.

-tk

On Mon, Mar 9, 2020 at 9:30 AM vince  wrote:

> On Sunday, March 8, 2020 at 7:50:51 PM UTC-7, Thomas Keffer wrote:
>
>> I want to see how this interface works out before documenting it.
>>
>>
> Just curious, but could you explain what changed re: logging in v4 vs. v3 ?
>
> Typically userspace apps just let the os's syslog functionfigure things
> out based on the facility/severity of the message being loggedor they
> write directly to their own logfile someplace.
>
> What problems did switching gears attempt to solve ?
>
>
> --
> 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/d5780813-e152-46ec-ba7f-978348e077a5%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/d5780813-e152-46ec-ba7f-978348e077a5%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEB9iQb0M%3DqRcr5oyZRwB7bhuGZBzT1q88ON%2B12L0DToGA%40mail.gmail.com.

Re: [weewx-user] 4 beta test report

[Thomas Keffer]

The problem is that the OS is not generally known until runtime. Well, you
could pick it at install time, but then that would require the same
branching "if statement," done earlier, which is not a better deal. Or, you
could make the user pick it in weewx.conf, but most users wouldn't have a
clue what to pick.

Nevertheless, the user can change these options by using an undocumented
feature to override the handlers. For example, you could have put this in
weewx.conf and ended up in the same place:

[Logging]
[[handlers]]
# System logger
[[[syslog]]]
address = '/dev/log/user'
facility = 'user'

I want to see how this interface works out before documenting it.

-tk

On Sun, Mar 8, 2020 at 4:15 PM Greg Troxel  wrote:

> vince  writes:
>
> > On Sunday, March 8, 2020 at 10:50:20 AM UTC-7, mwall wrote:
> >>
> >> port 514 is the default for remote system logging (rsyslog).  not sure
> why
> >> anyone would ever do localhost:514...
> >>
> > rsyslog to me doesn't mean remote, it's just one of many possible syslog
> > daemons you could have installed, so I could see it being used that way
> if
> > you wanted to force logging through a daemon that can do rewrite rules
> etc.
>
> So I don't understand why it makes sense to have this compiled in, if
> it's sysadmin's choice vs the standard interface on a particular OS.
>
> FWIW, on NetBSD syslogd can be made to listen on UDP port 514.  Actually,
> this is the default beahvior of syslogd, but the standard startup
> scripts pass -s ("secure") to not listen to the network.
>
> (This being in weewx at all is surprising to me; I would expect the
> logging module to have any necessary per-os defaults.  But I am very
> likely not understanding something.  On BSDs there is syslog(3), a
> library interface to syslog, and programs using that do not have to know
> how to talk to syslogd.  But that is not in POSIX, I'm pretty sure.)
>
> --
> 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/rmimu8qxwtz.fsf%40s1.lexort.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/CAPq0zEDDfNzersj1jxsQ3xCELOJ%2B3f5X%2BCVRzRsw-bfgcaLb4g%40mail.gmail.com.

Re: [weewx-user] Re: Weewx ERROR in weewx.cheetahgenerator Weewx 4.0 Python3

[Thomas Keffer]

>
> So is if fair to say Python3 is more stringent when it comes to these
> types of comparisons?
>

Yes, and that's a good thing. Under Python 2, None always tests less than
any number. Under Python 3, such a comparison is an error:

None < -1
Python 2: True
Python 3: Error

-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 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3Dwh-6QOFJv4D-f68jS9xUSK88QbdLRf%2BWoHcnY0%3DvGQ%40mail.gmail.com.

Re: [weewx-user] Re: Weewx ERROR in weewx.cheetahgenerator Weewx 4.0 Python3

[Thomas Keffer]

Some comments that might help you debug.

1. The error message

TypeError: '>' not supported between instances of 'NoneType' and 'float'


is not to be taken literally. It means that you are comparing two
variables, one of which has Python value None, the other a floating point
number.

2. Most likely, there is some comparison in the file
skins/Seasons/index.html.tmpl that is not checking first whether one of the
numbers might be None. I know you say that you have not changed the
templates, but a comparison of this sort must be in there, somewhere.

3. The file _home_weewx_skins_Seasons_index_html_tmpl.py is a temporary
file generated by Cheetah from the template index.html.tmpl. You will not
find it in your directory structure, as it is deleted by Cheetah
immediately after use.

4. The error

KeyError: 'unspecified'


is because you tried to run weewxd from the unpacked tar file. The type of
weather station has not been specified yet in the tar file, hence the
error. You must do "setup install" first.

-tk




On Sun, Mar 8, 2020 at 4:34 AM Mike Revitt  wrote:

> Thanks for the suggestion, but I need Python3 for my extensions which is
> forcing me to Weewx v4
>
> On Sunday, March 8, 2020 at 11:26:55 AM UTC, Andrew Milner wrote:
>>
>> You can always go live on the RPI by installing the current version of
>> weewx - v3.9.2 I believe.  Version 4 has not yet been released, but is in
>> beta test.  So your V4 weewx should be regarded as a beta test version
>> (which may be being compared to a live V3.9 version), rather than your sole
>> live version.
>>
>> Well, that is my opinion anyway
>>
>>
>>
>> On Sunday, 8 March 2020 12:32:48 UTC+2, Mike Revitt wrote:
>>>
>>> Further update
>>>
>>> After trying all combinations of file refresh I kept getting the same
>>> error so I renamed the weewx directory to weewx.broken and attempted to
>>> reinstall weewx from my previous build, with some interesting results. Bear
>>> in mind that nothing has been changed in the environment since I installed
>>> it yesterday
>>>
>>> pi@raspberrypi:~ $ sudo mv /home/weewx /home/weewx.broken
>>> pi@raspberrypi:~ $ ls -al /home
>>> total 16
>>> drwxr-xr-x  4 root root 4096 Mar  8 10:12 .
>>> drwxr-xr-x 21 root root 4096 Feb 13 16:32 ..
>>> drwxr-xr-x 21 pi   pi   4096 Mar  6 18:18 pi
>>> drwxr-xr-x  8 pi   root 4096 Mar  8 10:08 weewx.broken
>>>
>>> pi@raspberrypi:~ $ cd weewx-4.0.0b14/
>>> pi@raspberrypi:~/weewx-4.0.0b14 $ ./setup.py build
>>> running build
>>> running build_py
>>> running build_scripts
>>> pi@raspberrypi:~/weewx-4.0.0b14 $ sudo ./bin/weewxd weewx.conf
>>> Traceback (most recent call last):
>>>   File "./bin/weewxd", line 261, in 
>>> main()
>>>   File "./bin/weewxd", line 148, in main
>>> engine = weewx.engine.StdEngine(config_dict)
>>>   File "/home/pi/weewx-4.0.0b14/bin/weewx/engine.py", line 69, in
>>> __init__
>>> self.setupStation(config_dict)
>>>   File "/home/pi/weewx-4.0.0b14/bin/weewx/engine.py", line 87, in
>>> setupStation
>>> driver = config_dict[station_type]['driver']
>>>   File "/usr/lib/python3/dist-packages/configobj.py", line 554, in
>>> __getitem__
>>> val = dict.__getitem__(self, key)
>>> KeyError: 'unspecified'
>>> pi@raspberrypi:~/weewx-4.0.0b14 $ python -V
>>> Python 3.7.3
>>>
>>>
>>>
>>> So I logged out and back in, you never know it might have  been
>>> something in memory, but that made no difference
>>>
>>> So I deleted the directory weewx-4.0.0b14 and reinstalled it from the
>>> zip file already on disk which is the one I used yesterday
>>>
>>> pi@raspberrypi:~ $ sudo rm -fr weewx-4.0.0b14
>>>
>>> pi@raspberrypi:~ $ tar xvfz weewx-4.0.0b14.tar.gz
>>>
>>> pi@raspberrypi:~ $ cd weewx-4.0.0b14/
>>> pi@raspberrypi:~/weewx-4.0.0b14 $ ./setup.py build
>>> running build
>>> running build_py
>>> creating build
>>>
>>> pi@raspberrypi:~/weewx-4.0.0b14 $ sudo ./setup.py install
>>> running install
>>> running build
>>> running build_py
>>> running build_scripts
>>> running install_lib
>>> creating /home/weewx
>>>
>>> I then copied my modified files back , started weewx and compared the
>>> broken directory to the one that is now working
>>>
>>> pi@raspberrypi:/home $ diff -qr weewx weewx.broken/
>>> Files weewx/archive/weewx.sdb and weewx.broken/archive/weewx.sdb differ
>>> Only in weewx.broken/bin/user/__pycache__: s3backup.cpython-37.pyc
>>> Only in weewx.broken/bin/user/__pycache__: s3upload.cpython-37.pyc
>>> Only in weewx.broken/bin/user/__pycache__: stats.cpython-37.pyc
>>>
>>> pi@raspberrypi:/home $ sudo /etc/init.d/weewx status
>>> ● weewx.service - LSB: weewx weather system
>>>Loaded: loaded (/etc/init.d/weewx; generated)
>>>Active: active (running) since Sun 2020-03-08 10:18:18 GMT; 10min ago
>>>  Docs: man:systemd-sysv-generator(8)
>>>   Process: 12254 ExecStart=/etc/init.d/weewx start (code=exited,
>>> status=0/SUCCESS)
>>> Tasks: 1 (limit: 2200)
>>>Memory: 37.8M
>>>CGroup: /system.slice/weewx.service
>>>└─12269 /usr/bin/python 

Re: [weewx-user] Re: wind speed wrong (kph/miles)

[Thomas Keffer]

I live in the Columbia River Gorge, an extremely windy area in the summer.
About 5 years ago, I moved the wind sensor from the top of my roof to a 3
meter post in a back field. Wind speeds dropped by half.

Kestrel  makes very high quality
hand-held meters. Their model 2000

measures wind and temperature and is under $100. Mine is over 20 years old
and still functions perfectly.

-tk

On Sun, Mar 8, 2020 at 4:55 AM Stefan Pachlina  wrote:

> Hello,
>
> hmm, i will do following.
> 1) i will buy a hand-held-windmeter to check windspeed at the current
> position of my weather-sensors ... maybe you are right and the position of
> the windsensor is not perfect.
> 2) I will move my weatherstation-outsensors to the top of the roof.
> (currently its not at the top, 3m lower, but no slipstream from west, north
> and south)
>
> You should know that I see many kilometers to the mountains.
> There is nothing higher in sight (from the west) than my house. So the
> wind loves my roof :D
>
> i am just wondering why all other stations i checked have the same
> "problem".
>
> lets see :)
>
> thx for you help 
>
> Am Sonntag, 8. März 2020 02:50:12 UTC+1 schrieb Cameron D:
>>
>> Hello Stephan,
>> I am still not sure why you think your station was reading 100km/h. I
>> wonder if the following could explain the discrepancy...
>>
>> If that speed came from official weather reports, then their standard (in
>> many countries) requires that they are measured in open flat areas with the
>> anemometer 10m above ground level.  Wind speed decreases as you get closer
>> to the ground.
>>
>> Also, the presence of buildings, trees and so on, creates a much more
>> turbulent flow. The wind can have as much energy but lower measured speeds
>> are recorded since vertical components are not normally measured by home
>> instruments.
>>
>>
>> Cameron.
>>
>>
>> On Thursday, 5 March 2020 03:32:24 UTC+10, Stefan Pachlina wrote:
>>>
>>> Hello,
>>>
>>> feb 24 2020, it was a stormy day in austria ... but most weatherstations
>>> (weewx-map, wunderground-map) show windspeed like 64kph.
>>> but on this day wind speed was ~103kph
>>> i have the same problem with my weather-site.
>>> http://wetter.pachlina.net/
>>>
>>> *i configured weewx.config to see kph:*
>>> Groups
>>>   
>>>   group_speed = km_per_hour
>>>   group_speed2 = km_per_hour2
>>>   
>>>
>>> but what i see are miles and not kph.
>>> cause if i multiplicate the wind-speed with 1,61 i get the right
>>> wind-speed of 103 kph
>>>
>>> so what is to do to get the right values?
>>> is there something more to do?
>>> i read the manual again and again, but i cant find the solution to see
>>> right wind speed.
>>> all other values are ok .. like temperature in celsius.
>>>
>>> and this is what i see on many many weatherstation around austria,
>>> germany  with weewx-map, wunderground, ...
>>>
>>> h any idea?
>>> thx
>>>
>>> Stefan
>>>
>>> --
> 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/f6ee460c-bd4a-42b3-9adb-af70cc51c413%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/CAPq0zECHqyeRjz1F4B6jaQe8WGznFhZO1gBys4v9cd67cTt%3DOg%40mail.gmail.com.

Re: [weewx-user] 4 beta test report

[Thomas Keffer]

Hi, Greg

weewx V4 uses a new logging facility, Python's module 'logging', which
requires that one set up logging handlers. The handler "syslog" is designed
to (roughly) emulate the previous syslog logging. To set it up, you must
specify a destination (called 'address') and a 'facility', which vary from
OS to OS. I suspect that the defaults that weewx is picking for NetBSD are
wrong.

Take a look at the top of file weeutil/logger.py where these destinations
are coded in. It looks like:

if sys.platform == "darwin":
address = '/var/run/syslog'
facility = 'local1'
elif sys.platform.startswith('linux'):
address = '/dev/log'
facility = 'user'
elif sys.platform.startswith('freebsd'):
address = '/var/run/log'
facility = 'user'
else:
address = ('localhost', 514)
facility = 'user'

I don't know which branch NetBSD would take. Either 'freebsd' or the
default, I imagine. Obviously, what it's choosing isn't working out.
Perhaps you can supply an alternative for NetBSD? It may be as simple as a
different file path for 'address'.

-tk


On Sat, Mar 7, 2020 at 5:44 PM Greg Troxel  wrote:

> I just updated to the tip of master (plus a local commit to change
> prefix to /usr/weewx).  After installing, weewxd crashes on boot trying
> to set up the backup logger.  I am unclear on what's going on here and
> starting to read code.
>
> I wonder if there are some Linux path assumptions hard-coded in, but
> that's an unsubstantiated guess.  Does this work ok for everybody else?
>
> My system in NetBSD8, earmv7hf-el (RPI3), and has been running weewx
> 3.9.x and earlier just fine for just over 2 years.
>
> The system does have working syslog, and lines have been appearing in
> /var/log/messages via syslog, when I was running 3.9.2:
>
>   Mar  7 20:25:28 wx weewx[1249]: rsyncupload: rsync'd 17 files (83,033
> bytes) in 0.82 seconds
>   Mar  7 20:30:14 wx weewx[1249]: engine: Main loop exiting. Shutting
> engine down.
>   Mar  7 20:30:14 wx weewx[1249]: engine: Shutting down StdReport thread
>   Mar  7 20:30:15 wx weewx[1249]: engine: Terminating weewx version 3.9.2
>
> The crash looks like:
>
>   $ bin/weewxd
>   Traceback (most recent call last):
> File "bin/weewxd", line 261, in 
>   main()
> File "bin/weewxd", line 80, in main
>   weeutil.logger.setup(options.log_label, {})
> File "/usr/home/gdt/SOFTWARE/WEEWX/weewx/bin/weeutil/logger.py", line
> 148, in setup
>   logging.config.dictConfig(log_dict)
> File "/usr/pkg/lib/python2.7/logging/config.py", line 794, in
> dictConfig
>   dictConfigClass(config).configure()
> File "/usr/pkg/lib/python2.7/logging/config.py", line 576, in configure
>   '%r: %s' % (name, e))
>   ValueError: Unable to configure handler 'syslog': [Errno 2] No such file
> or directory
>
> --
> 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/rmiwo7v1uzc.fsf%40s1.lexort.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/CAPq0zEBa%3DcnV8TZRb%2BQoB%2BVsmSP30y9LHzo5FiC4jVLXa8Es_w%40mail.gmail.com.

Re: [weewx-user] Re: weewx v4 new extended schema - so good !

[Thomas Keffer]

I thought a release of V4 would be real soon, but we ran into lots of
packaging hassles supporting such a wide matrix of possibilities. Now I'm
looking at a much simpler strategy, but it will take time. Patience!

-tk

On Sat, Mar 7, 2020 at 11:03 AM Steve Koone  wrote:

> This looks great Vince, and thanks for sharing your results!
>
> Is this something that we can apply our existing v3 systems now, or do we
> have to wait until v4 is released?
>
> Speaking of which, can anyone (developers perhaps?) advise as to an
> official release time frame for weewx v4?  Is it soon or still down the
> road a ways?
>
> -Stephen
>
> --
> 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/3279a602-a0b4-4690-9903-e8c582d8f910%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/CAPq0zECnm3xcfr237sZz-YxkphPbFCco19g9D_1bW%3DskOt%3Driw%40mail.gmail.com.

Re: [weewx-user] Graphs with command in the Bottom Label

[Thomas Keffer]

Unfortunately, no. The Cheetah template engine is not used for graph
labels, only to generate files.

On Sat, Mar 7, 2020 at 7:18 AM Meteo Oberwallis 
wrote:

>
> Hi there.Is it possible to insert the station and the height in the graphic 
> based on these variables? Then the template could also be used for other 
> stations without having to adjust everything every time.
>
>
> [image: daywindgust.png]
>
>
> Thx for Help
> Stefan
>
> --
> 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/bd3a2592-a090-43da-a357-437a62a5fc3c%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/CAPq0zED%2BQzbOwD6j_KxQLVwX2af%3DzcZ2kO4A812qL1vfcKmLEw%40mail.gmail.com.

Re: [weewx-user] Add an additional sensor

[Thomas Keffer]

Don't have time to debug your code, but, as written, it will open and read
the socket only once, when your module is loaded. Then, never again. Maybe
that's what you want, maybe it isn't.

Open the socket in the __init__() function, then read it in the
new_archive_record() function.

-tk

On Fri, Mar 6, 2020 at 11:01 PM rimas petronis  wrote:

> Hi!
>
> I have a controller connected to many sensors and want to read the sensor
> data from the controller
>
> I'm trying to create a WEEWX plugin for additional sensors
>
> Based on the examples I created, the plugin does not work properly
>
> when you start WEEWX, it reads data from the controller and writes the
> same values to the database at the same time
>
> By no means do I find mistakes
>
> Maybe someone could help solve this problem
>
>
> syslog
>
>
> Mar  7 08:35:15 raspberrypi weewx[30344]: Scans controller: {u'O28': 0,
> u'O29': 3, u'O26': 0, u'O27': 3, u'O24': 0, u'O25': 0, u'O22': 3, u'O23':
> 0, u'O20': 0, u'O21': 0, u'Sk5': 0, u'Sk4': 0, u'Sk1': 1348585, u'D':
> u'2020-03-07 08:35:03', u'Sk3': 283659, u'Sk2': 264208, u'T49': 998.3,
> u'T07': 39.7, u'T06': 12.6, u'T05': 59.5, u'T04': 40.2, u'T03': 65.4,
> u'T02': 3.1, u'T01': 3.3, u'T09': 29.6, u'T08': 37.0, u'Spp': 0, u'PID1':
> {u'Pv': 26, u'Tu': 40.0, u'Tp': 40.0, u'St': 0, u'To': 1.3, u'Ti': 0.0,
> u'Fk': 0.0}, u'PID2': {u'Pv': 20, u'Tu': 30.0, u'Tp': 29.7, u'St': 0,
> u'To': 0.3, u'Ti': 0.0, u'Fk': 0.0}, u'T14': 21.8, u'T15': 43.8, u'T16':
> 20.3, u'T17': 21.0, u'T10': 28.6, u'T11': 21.8, u'T12': 23.1, u'T13': 44.4,
> u'T18': 20.3, u'T19': 21.0, u'PkW': 0, u'Cpm': 0.0, u'T29': 24.7, u'T28':
> 64.0, u'T21': 21.1, u'T20': 21.0, u'T23': 43.3, u'T22': 19.2, u'T25': 39.4,
> u'T24': 63.5, u'T27': 64.6, u'T26': 36.5, u'DAC8': 0.0, u'Gl': 0, u'Fl9':
> {u'On': 1, u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl8': {u'On':
> 1, u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'D10': 0, u'Acu': 0,
> u'Fl1': {u'On': 1, u'Fz': 23.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl3':
> {u'On': 0, u'Fz': 19.8, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl2': {u'On':
> 0, u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl5': {u'On': 0,
> u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl4': {u'On': 0, u'Fz':
> 20.3, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl7': {u'On': 0, u'Fz': 0.0,
> u'Ti': 0.0, u'GK': 7, u'To': 0.0}, u'Fl6': {u'On': 1, u'Fz': 21.0, u'Ti':
> 3.2, u'GK': 6, u'To': -1.3}, u'T38': 21.1, u'T39': 14.0, u'T36': 21.2,
> u'T34': 27.1, u'T35': 27.5, u'T32': 3.7, u'T33': 67.8, u'T30': 20.1,
> u'T31': 19.9, u'Hup': 1, u'DAC6': 0.0, u'DAC7': 0.0, u'Stp': 58, u'O17': 3,
> u'O16': 3, u'O15': 3, u'O14': 0, u'O13': 0, u'O12': 0, u'O11': 0, u'O10':
> 8, u'T40': 20.3, u'T46': 999.5, u'O19': 0, u'O18': 3, u'Tl': 3.3, u'O04':
> 3, u'O05': 0, u'O06': 0, u'O07': 0, u'O01': 0, u'O02': 3, u'O03': 3,
> u'O08': 0, u'O09': 0, u'KwB': 0, u'BoPr': 0, u'Fl15': {u'On': 1, u'Fz':
> 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl14': {u'On': 1, u'Fz': 24.0,
> u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl16': {u'On': 0, u'Fz': 61.5, u'Ti':
> 0.0, u'GK': 6, u'To': 0.0}, u'Fl11': {u'On': 1, u'Fz': 21.0, u'Ti': 0.0,
> u'GK': 6, u'To': 0.0}, u'Fl10': {u'On': 0, u'Fz': 20.0, u'Ti': 0.0, u'GK':
> 6, u'To': 0.0}, u'Fl13': {u'On': 0, u'Fz': 20.2, u'Ti': 0.0, u'GK': 6,
> u'To': 0.0}, u'Fl12': {u'On': 0, u'Fz': 21.0, u'Ti': 0.8, u'GK': 6, u'To':
> 0.0}, u'DAC1': 7.3, u'DAC2': 7.9, u'DAC3': 0.0, u'DAC4': 0.0, u'DAC5': 0.0,
> u'Coo': 0, u'Cgl': 8, u'AcOn': 0, u'O31': 0, u'O30': 3, u'O32': 8, u'D8':
> 1, u'D9': 0, u'D6': 0, u'D7': 0, u'D4': 0, u'D5': 0, u'D2': 0, u'D3': 0,
> u'D1': 0}
>
> Mar  7 08:35:15 raspberrypi weewx[30344]: Send data T05 59.5
>
> Mar  7 08:35:15 raspberrypi weewx[30344]: Send data T03 65.4
>
>
> Mar  7 08:59:15 raspberrypi weewx[30344]: Scans controller: {u'O28': 0,
> u'O29': 3, u'O26': 0, u'O27': 3, u'O24': 0, u'O25': 0, u'O22': 3, u'O23':
> 0, u'O20': 0, u'O21': 0, u'Sk5': 0, u'Sk4': 0, u'Sk1': 1348585, u'D':
> u'2020-03-07 08:35:03', u'Sk3': 283659, u'Sk2': 264208, u'T49': 998.3,
> u'T07': 39.7, u'T06': 12.6, u'T05': 59.5, u'T04': 40.2, u'T03': 65.4,
> u'T02': 3.1, u'T01': 3.3, u'T09': 29.6, u'T08': 37.0, u'Spp': 0, u'PID1':
> {u'Pv': 26, u'Tu': 40.0, u'Tp': 40.0, u'St': 0, u'To': 1.3, u'Ti': 0.0,
> u'Fk': 0.0}, u'PID2': {u'Pv': 20, u'Tu': 30.0, u'Tp': 29.7, u'St': 0,
> u'To': 0.3, u'Ti': 0.0, u'Fk': 0.0}, u'T14': 21.8, u'T15': 43.8, u'T16':
> 20.3, u'T17': 21.0, u'T10': 28.6, u'T11': 21.8, u'T12': 23.1, u'T13': 44.4,
> u'T18': 20.3, u'T19': 21.0, u'PkW': 0, u'Cpm': 0.0, u'T29': 24.7, u'T28':
> 64.0, u'T21': 21.1, u'T20': 21.0, u'T23': 43.3, u'T22': 19.2, u'T25': 39.4,
> u'T24': 63.5, u'T27': 64.6, u'T26': 36.5, u'DAC8': 0.0, u'Gl': 0, u'Fl9':
> {u'On': 1, u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl8': {u'On':
> 1, u'Fz': 21.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'D10': 0, u'Acu': 0,
> u'Fl1': {u'On': 1, u'Fz': 23.0, u'Ti': 0.0, u'GK': 6, u'To': 0.0}, u'Fl3':
> {u'On': 0, u'Fz': 19.8, u'Ti': 0.0, u'GK': 6, u'To': 

Re: [weewx-user] Re: Weewx stops at Midnight

[Thomas Keffer]

> 17:16:00 CET (1583424960) to database 'SMA.sdb'
> Mar  5 17:16:42 WeeWxPi weewx-SMA[751]: manager: Added record 2020-03-05
> 17:16:00 CET (1583424960) to daily summary in 'SMA.sdb'
> Mar  5 17:16:42 WeeWxPi weewx-SMA[751]: cheetahgenerator: Generated 1
> files for report StandardReport in 0.26 seconds
> Mar  5 17:16:43 WeeWxPi weewx-SMA[751]: imagegenerator: Generated 2 images
> for StandardReport in 0.73 seconds
> Mar  5 17:17:01 WeeWxPi CRON[13945]: (root) CMD (   cd / && run-parts
> --report /etc/cron.hourly)
> Mar  5 17:16:10 WeeWxPi weewx-WH1080[13835]: reportengine: Running reports
> for latest time in the database.
> Mar  5 17:16:10 WeeWxPi weewx-WH1080[13835]: reportengine: Running report
> 'StandardReport'
> Mar  5 17:16:10 WeeWxPi weewx-WH1080[13835]: reportengine: Found
> configuration file /home/weewx/skins/WH1080/skin.conf for report
> 'StandardReport'
> Mar  5 17:16:10 WeeWxPi weewx-WH1080[13835]: cheetahgenerator: using
> search list ['weewx.cheetahgenerator.Almanac',
> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
> 'weewx.cheetahgenerator.Extras', 'user.forecast.ForecastVariables']
> Mar  5 17:16:10 WeeWxPi weewx-WH1080[13835]: manager: Daily summary
> version is 2.0
> Mar  5 17:16:12 WeeWxPi weewx-WH1080[13835]: manager: Daily summary
> version is 2.0
> Mar  5 17:16:14 WeeWxPi weewx-WH1080[13835]: cheetahgenerator: Generated 3
> files for report StandardReport in 3.26 seconds
> Mar  5 17:16:14 WeeWxPi weewx-WH1080[13835]: manager: Daily summary
> version is 2.0
> Mar  5 17:16:17 WeeWxPi weewx-WH1080[13835]: imagegenerator: Generated 7
> images for StandardReport in 3.40 seconds
> Mar  5 17:16:17 WeeWxPi weewx-WH1080[13835]: reportengine: Running report
> 'FTP'
> Mar  5 17:16:17 WeeWxPi weewx-WH1080[13835]: reportengine: Found
> configuration file /home/weewx/skins/Ftp/skin.conf for report 'FTP'
> Mar  5 17:16:17 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempting
> connection to www.lockter.de
> Mar  5 17:16:18 WeeWxPi weewx-WH1080[13835]: ftpupload: Connected to
> www.lockter.de
> Mar  5 17:16:18 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/daybarometer.png
> Mar  5 17:16:18 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #1. Failed
> uploading /wsb4344958101/dayenergybarmax.png to www.lockter.de. Reason:
> [Errno 111] Verbindungsaufbau abgelehnt
> Mar  5 17:16:18 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/dayenergybarmax.png
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/dayinouthum.png
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/dayouttempchill.png
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #1. Failed
> uploading /wsb4344958101/dayrain.png to www.lockter.de. Reason: [Errno
> 111] Verbindungsaufbau abgelehnt
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #2. Failed
> uploading /wsb4344958101/dayrain.png to www.lockter.de. Reason: [Errno
> 111] Verbindungsaufbau abgelehnt
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #3. Failed
> uploading /wsb4344958101/dayrain.png to www.lockter.de. Reason: [Errno
> 111] Verbindungsaufbau abgelehnt
> Mar  5 17:16:19 WeeWxPi weewx-WH1080[13835]: ftpupload: Failed to upload
> file /wsb4344958101/dayrain.png
> Mar  5 17:16:20 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/daywind.png
> Mar  5 17:16:20 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/daywinddir.png
> Mar  5 17:16:20 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/daywindvec.png
> Mar  5 17:16:20 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/tempsday.png
> Mar  5 17:16:21 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/tempsmonth.png
> Mar  5 17:16:21 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/tempsweek.png
> Mar  5 17:16:21 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #1. Failed
> uploading /wsb4344958101/weekenergybarmax.png to www.lockter.de. Reason:
> [Errno 111] Verbindungsaufbau abgelehnt
> Mar  5 17:16:21 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/weekenergybarmax.png
> Mar  5 17:16:22 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/pressure24h.png
> Mar  5 17:16:22 WeeWxPi weewx-WH1080[13835]: ftpupload: Uploaded file
> /wsb4344958101/SMA.html
> Mar  5 17:16:22 WeeWxPi weewx-WH1080[13835]: ftpupload: Attempt #1. Failed
> uploading /wsb4344958101/index.html to www.lockter.de. Reason: [Errno
> 111] Verbindungsaufbau abgelehnt
&

Re: [weewx-user] wind speed wrong (kph/miles)

[Thomas Keffer]

According to the database, you saw a max gust of 39.6 mph, or 63.7 kph,
which is exactly what was reported on your website.

It is always possible there is a bug in the driver for the WH1080, but
unlikely. A bug this fundamental would have been discovered a long time
ago.

Perhaps Matthew has an opinion...?

-tk

On Thu, Mar 5, 2020 at 11:06 AM Stefan Pachlina  wrote:

> Hello,
>
> in austria was a stormwarning of storm "Sabine" by weather-service
> https://warnungen.zamg.at    but yes, we are talking about wind-gust
> ~100kph
> Heavy roof tiles were dropped from the roof and crashed on the street, etc
>  it was a terrible night.
> Cause of that ... wind-gust was greater then 63.7 kph ;)
>
> *so what i see in dB is frustrating:*
> 2020-02-23 22:01:00|1|13.6453452968298|20.5798650378416
> 2020-02-23 22:31:00|1|22.8168068897809|39.5938707793257  <-- parts of my
> roof flew away :D
> 2020-02-23 23:01:00|1|17.4481464451266|27.2906905936595
> 2020-02-23 23:31:00|1|9.17146159295115|14.5401220376055
> 2020-02-24 00:01:00|1|14.5401220376055|25.0537487417202
> 2020-02-24 00:31:00|1|21.2509475934234|34.8962928902531
> 2020-02-24 01:01:00|1|19.0140057414841|31.0934917419563
>
> are these values the one directly from my weatherstation? unformatted by
> weewx?
>
> i found a very interesting section in weewx.conf an in customers guide.
> [[Corrections]]
>
> i think i can do something like that in that section:
> windSpeed = windSpeed * 1.61
>
> but i dont undestand what my weatherstation is doing with the windspeed
> hm
>
> regards
> Stefan
>
> Am Mittwoch, 4. März 2020 23:56:55 UTC+1 schrieb Thomas Keffer:
>>
>> Hello,
>>
>> Looking through your website, it looks like the max wind you saw was 63.7
>> kph. How do you know it was really 103 kph?
>>
>> It would also be worth looking in your database. Try this:
>>
>> *sqlite3 weewx.sdb*
>> sqlite> *select datetime(dateTime,'unixepoch','localtime'), usUnits,
>> windSpeed, windGust from archive where dateTime>=1582491600 and
>> dateTime<=1582502400;*
>>
>> Hopefully, if I got the time zone right, this will print out wind values
>> in your database from 23-feb-2020 2200 to 24-feb-2020 0100 local time.
>>
>> -tk
>>
>>
>>
>> On Wed, Mar 4, 2020 at 9:32 AM Stefan Pachlina 
>> wrote:
>>
>>> Hello,
>>>
>>> feb 24 2020, it was a stormy day in austria ... but most weatherstations
>>> (weewx-map, wunderground-map) show windspeed like 64kph.
>>> but on this day wind speed was ~103kph
>>> i have the same problem with my weather-site.
>>> http://wetter.pachlina.net/
>>>
>>> *i configured weewx.config to see kph:*
>>> Groups
>>>   
>>>   group_speed = km_per_hour
>>>   group_speed2 = km_per_hour2
>>>   
>>>
>>> but what i see are miles and not kph.
>>> cause if i multiplicate the wind-speed with 1,61 i get the right
>>> wind-speed of 103 kph
>>>
>>> so what is to do to get the right values?
>>> is there something more to do?
>>> i read the manual again and again, but i cant find the solution to see
>>> right wind speed.
>>> all other values are ok .. like temperature in celsius.
>>>
>>> and this is what i see on many many weatherstation around austria,
>>> germany  with weewx-map, wunderground, ...
>>>
>>> h any idea?
>>> thx
>>>
>>> Stefan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/298dc427-566d-481b-ba62-94b571cb8ea9%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/298dc427-566d-481b-ba62-94b571cb8ea9%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/614b154e-d937-4d10-b0e0-96f0d1764aef%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/614b154e-d937-4d10-b0e0-96f0d1764aef%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zEDuQ-Yxd5XesMysKYNpJrCyyxiX-x_OUGB27CLdYoSWcw%40mail.gmail.com.

Re: [weewx-user] Re: Weewx stops at Midnight

[Thomas Keffer]

Let's be sure.

Please set debug=1 (in weewx.conf), then restart weewx. Let it run for two
reporting cycles. Then post the log from startup through the second cycle.

-tk

On Thu, Mar 5, 2020 at 4:37 AM 'angry tux' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi,
> 1. The version is 3.9.2.1.
> 2. That´s strange, it looks like it runs the report every two minutes. No
> idea where I changed it.
>
> Dieter
>
> Am Mittwoch, 4. März 2020 18:02:39 UTC+1 schrieb angry tux:
>>
>> Hi,
>> most of the nights weewx stops with the first routine after midnight. I
>> have two instances running, WH1080.conf and SMA.conf. While the SMA
>> continues the WH1080 stops with the following message:
>>
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Main loop exiting.
>> Shutting engine down.
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Shutting down
>> StdReport thread
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: StdReport thread has
>> been terminated
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: restx: Shut down
>> StationRegistry thread.
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Caught unrecoverable
>> exception in engine:
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Attempt to merge an
>> accumulator whose timespan is not a subset
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Traceback (most recent
>> call last):
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 894, in main
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  engine.run()
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 202, in run
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
>> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  callback(event)
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 574, in post_loop
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  self._software_catchup()
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 646, in _software_catchup
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
>> self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
>> record=record, origin='software'))
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  callback(event)
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
>> dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/manager.py", line 243, in addRecord
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
>> self._updateHiLo(accumulator, cursor)
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/manager.py", line 1231, in _updateHiLo
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
>> _stats_dict.updateHiLo(accumulator)
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
>> "/home/weewx/bin/weewx/accum.py", line 265, in updateHiLo
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  raise OutOfSpan("Attempt
>> to merge an accumulator whose timespan is not a subset")
>>
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  OutOfSpan: Attempt to
>> merge an accumulator whose timespan is not a subset
>> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Exiting.
>>
>> I made a cronjob for 00:02 to start WH1080 again, but this should nor be
>> the final solution.
>> Does somebody has an idea what causes the stopping?
>>
>> Regards
>>
>> --
> 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/d717b1b0-d827-4031-b837-1cae8ab5c241%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/CAPq0zEBXwcDN0pGwDh_PRCc%3D1VxiYswSfnOCC%3Do%2BKCYHie3%2BMw%40mail.gmail.com.

Re: [weewx-user] Weewx stops at Midnight

[Thomas Keffer]

Hello,

Two questions:
1. What version of weewx?
2. What is your archive interval?

-tk



On Wed, Mar 4, 2020 at 9:02 AM 'angry tux' via weewx-user <
weewx-user@googlegroups.com> wrote:

> Hi,
> most of the nights weewx stops with the first routine after midnight. I
> have two instances running, WH1080.conf and SMA.conf. While the SMA
> continues the WH1080 stops with the following message:
>
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Main loop exiting.
> Shutting engine down.
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Shutting down
> StdReport thread
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: StdReport thread has
> been terminated
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: restx: Shut down
> StationRegistry thread.
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: engine: Caught unrecoverable
> exception in engine:
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Attempt to merge an
> accumulator whose timespan is not a subset
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Traceback (most recent
> call last):
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 894, in main
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  engine.run()
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 202, in run
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
> self.dispatchEvent(weewx.Event(weewx.POST_LOOP))
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  callback(event)
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 574, in post_loop
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  self._software_catchup()
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 646, in _software_catchup
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
> self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,
> record=record, origin='software'))
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 224, in dispatchEvent
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  callback(event)
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/engine.py", line 601, in new_archive_record
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
> dbmanager.addRecord(event.record, accumulator=self.old_accumulator)
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/manager.py", line 243, in addRecord
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
> self._updateHiLo(accumulator, cursor)
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/manager.py", line 1231, in _updateHiLo
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]: 
> _stats_dict.updateHiLo(accumulator)
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  File
> "/home/weewx/bin/weewx/accum.py", line 265, in updateHiLo
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  raise OutOfSpan("Attempt
> to merge an accumulator whose timespan is not a subset")
>
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  OutOfSpan: Attempt to
> merge an accumulator whose timespan is not a subset
> Feb 22 00:00:56 WeeWxPi weewx-WH1080[6852]:  Exiting.
>
> I made a cronjob for 00:02 to start WH1080 again, but this should nor be
> the final solution.
> Does somebody has an idea what causes the stopping?
>
> Regards
>
> --
> 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/80ef77b0-6eff-4e60-b9e6-e042d49a0535%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/CAPq0zEDz60H1yhmE_us0JkGUtLDJ2N-_hjSRxhoi9gKtK3bL%2BA%40mail.gmail.com.

Re: [weewx-user] wind speed wrong (kph/miles)

[Thomas Keffer]

Hello,

Looking through your website, it looks like the max wind you saw was 63.7
kph. How do you know it was really 103 kph?

It would also be worth looking in your database. Try this:

*sqlite3 weewx.sdb*
sqlite> *select datetime(dateTime,'unixepoch','localtime'), usUnits,
windSpeed, windGust from archive where dateTime>=1582491600 and
dateTime<=1582502400;*

Hopefully, if I got the time zone right, this will print out wind values in
your database from 23-feb-2020 2200 to 24-feb-2020 0100 local time.

-tk



On Wed, Mar 4, 2020 at 9:32 AM Stefan Pachlina  wrote:

> Hello,
>
> feb 24 2020, it was a stormy day in austria ... but most weatherstations
> (weewx-map, wunderground-map) show windspeed like 64kph.
> but on this day wind speed was ~103kph
> i have the same problem with my weather-site.
> http://wetter.pachlina.net/
>
> *i configured weewx.config to see kph:*
> Groups
>   
>   group_speed = km_per_hour
>   group_speed2 = km_per_hour2
>   
>
> but what i see are miles and not kph.
> cause if i multiplicate the wind-speed with 1,61 i get the right
> wind-speed of 103 kph
>
> so what is to do to get the right values?
> is there something more to do?
> i read the manual again and again, but i cant find the solution to see
> right wind speed.
> all other values are ok .. like temperature in celsius.
>
> and this is what i see on many many weatherstation around austria, germany
>  with weewx-map, wunderground, ...
>
> h any idea?
> thx
>
> Stefan
>
> --
> 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/298dc427-566d-481b-ba62-94b571cb8ea9%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/CAPq0zEDMdsvyG7Uc9gJA7JRDsg5YdSuh_v8CF02Hr-6XWRb0OA%40mail.gmail.com.

Re: [weewx-user] Re: draw user-defined lines in graphics

[Thomas Keffer]

As user "Mic G77" pointed out
, you
can also do math in the configuration file, skin.conf:

 [[[dayPoid]]]
   yscale = None, None, None
   extraTemp2
   extraTest
 data_type = 18.3+0.03*extraHumid2

-tk

On Wed, Mar 4, 2020 at 9:19 AM vince  wrote:

> On Wednesday, March 4, 2020 at 7:42:05 AM UTC-8, Ralph Underwood wrote:
>>
>> I like to see the freezing level on many of my charts so I set soilTemp4
>> to 32 degrees in the StdCalibrate section of weewx.conf
>>
>
> That is absurdly clever !!!
>
> --
> 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/c57f23fa-9981-40cc-8c84-3c4f3d5b2bfe%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/CAPq0zEAq_MXPYsfZWjwECuoFsSeWJ7Gdj%3DLzOxXgVqiUexUZ4g%40mail.gmail.com.

Re: [weewx-user] Almanac Extras....

[Thomas Keffer]

Not sure I understand your question.

You are using WeeWX V3.9.2, which will run only under Python 2 so, unless
you installed pyephem under Python 3, it should not be a factor. Try this
to see where pyephem ended up:

This will tell us what version of Python is the default:
*python -V*

This will test whether pyephem was installed for the default version:
*python -c "import ephem"*

This will test whether pyephem was accidentally installed for Python 3:
*python3 -c "import ephem"*

-tk

On Tue, Mar 3, 2020 at 10:55 PM Jason Gill  wrote:

> Thanks for this.
>
> You were correct - when I run with the explicit python I get the same
> result on both.
>
> I have python 2.7.17 and python 3.6.9 from what I can see. Do you mean
> multiple versions of 2.x.x (or 3.x.x) or would having 2 and 3 versions
> installed cause this problem?
>
> Regards,
> Jason.
>
> On Tuesday, March 3, 2020 at 3:27:47 AM UTC+13, Thomas Keffer wrote:
>>
>> Do you have several versions of Python on your machine? It's possible
>> pyephem was installed using one version, but you're trying to run weewxd
>> under another.
>>
>> Try invoking python explicitly when you run wee_reports and weewxd. This
>> will guarantee that they are using the same version of Python:
>>
>> *sudo python /usr/share/weewx/weewxd /etc/weewx/weewx.conf*
>> *sudo python /usr/share/weewx/wee_reports /etc/weewx/weewx.conf*
>>
>> See if those give the same results.
>>
>> -tk
>>
>> On Sun, Mar 1, 2020 at 11:55 PM Jason Gill  wrote:
>>
>>> Hello,
>>>
>>> I added pyephem to show extra almanac info on my main page. When I moved
>>> weewx between servers this stopped working although the setup seems the
>>> same.
>>>
>>> Version Info:
>>> pyephem version is 3.7.7.0
>>> weewx version is v3.9.2
>>>
>>> When I run "sudo wee_reports  /etc/weewx/weewx.conf" (seen in another
>>> post) the main page reports the following extended almanac info after
>>> wee_reports completes
>>>
>>> Sun
>>> Start civil twilight: 06:40:25 AM
>>> Sunrise: 07:07:13 AM
>>> Transit: 01:33:21 PM
>>> Sunset: 07:58:52 PM
>>> End civil twilight: 08:25:36 PM
>>> Equinox: 03/20/2020 04:49:32 PM
>>> Solstice: 06/21/2020 09:43:46 AM
>>>
>>> Moon
>>> Rise: 01:41:29 PM
>>> Transit: 06:55:13 PM
>>> Set: 12:04:19 AM
>>> Full moon: 03/10/2020 06:47:42 AM
>>> New moon: 03/24/2020 10:28:11 PM
>>> Phase: First quarter (45% full)
>>>
>>> When the next periods data arrives the almanac returns to this:
>>>
>>> Sunrise: 07:07:36
>>> Sunset: 19:59:08
>>> Moon Phase: First quarter (50% full)
>>>
>>> The same config file is used for both wee_reports and when I restart
>>> weewx. Any ideas - I must have missed something?
>>>
>>> Regards,
>>> Jason.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/c2f7ae08-3eb7-403d-a68e-0a2439f9e4e5%40googlegroups.com
>>> <https://groups.google.com/d/msgid/weewx-user/c2f7ae08-3eb7-403d-a68e-0a2439f9e4e5%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>> --
> 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/44f9ef1e-8082-416d-bcbc-4fc3f749d179%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/44f9ef1e-8082-416d-bcbc-4fc3f749d179%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAPq0zECreMxZ%2B7UQwFauUy_Oh2qDoJ%3DgSTHUoDPg9XdZfC7nkQ%40mail.gmail.com.

Re: [weewx-user] Re: wee_database: ImportError

[Thomas Keffer]

Looking a little bit closer at the command you used, the syntax is not
quite right. Instead of


*sudo wee_database --transfer --dest-binding = dest_binding --dry-run*

your want


*sudo wee_database --transfer --dest-binding=dest_binding --dry-run*

-tk

On Tue, Mar 3, 2020 at 10:07 AM Eric Gammeter  wrote:

> Yes: here it is from weewx.conf file:
>
>
>[[dest_binding]]
> database = archive_mysql
> table_name = archive
> manager = weewx.wxmanager.WXDaySummaryManager
> schema = schemas.wview.schema
>
>
>
> On Tuesday, February 25, 2020 at 9:11:40 AM UTC-5, Eric Gammeter wrote:
>>
>>
>> Goal:
>> Wanting to switch from sqlite to MySql database.
>>
>> I am consulting the github /weewx/wiki "Usingwee_database".
>>
>> The --dry-run doesn't show any error.
>>
>>
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding
>> --dry-run
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination
>> database 'weewx'.
>> Dry run, nothing done.
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination
>> database 'weewx' (y/n)? y
>> Error accessing destination database 'weewx'.
>> Nothing done. Aborting.
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_database", line 794, in 
>> main()
>>   File "/usr/bin/wee_database", line 159, in main
>> transferDatabase(config_dict, db_binding, options)
>>   File "/usr/bin/wee_database", line 410, in transferDatabase
>> schema=dest_manager_dict['schema']) as dest_manager:
>>   File "/usr/share/weewx/weewx/manager.py", line 128, in open_with_create
>> connection = weedb.connect(database_dict)
>>   File "/usr/share/weewx/weedb/__init__.py", line 86, in connect
>> __import__(db_dict['driver'])
>>   File "/usr/share/weewx/weedb/mysql.py", line 10, in 
>> import MySQLdb
>> ImportError: No module named MySQLdb
>>
>> --
> 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/f990a6c7-8b77-446c-9f42-c57a49fd16ac%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/CAPq0zEBUXeygC8J7vwEhQu4J2ejuMBm0BW9iffk3WYUWp6NcRQ%40mail.gmail.com.

Re: [weewx-user] Re: wee_database: ImportError

[Thomas Keffer]

>
> $ sudo wee_database --transfer --dest-binding = dest_binding --dry-run
> Traceback (most recent call last):
>   File "/usr/bin/wee_database", line 794, in 
> main()
>   File "/usr/bin/wee_database", line 133, in main
> config_path, config_dict = weecfg.read_config(options.config_path,
> args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 173, in read_config
> locations=locations, file_name=file_name)
>   File "/usr/share/weewx/weecfg/__init__.py", line 147, in find_file
> raise IOError("%s is not a file" % file_path)
> IOError: dest_binding is not a file
>

Is dest_binding defined in your configuration file?

 $ sudo python -c "import weedb.mysql"
> Traceback (most recent call last):
>   File "", line 1, in 
> ImportError: No module named weedb.mysql


This is probably a PYTHONPATH problem.

-tk

On Tue, Mar 3, 2020 at 8:47 AM Eric Gammeter  wrote:

> My error:  I was wrong on my situation-  it is not fixed.
>
> I have attached debug.info file with all the particulars.
>
> I am attempting to convert my existing sqlite weewx db file to MySQL and
> then migrate it over to a new RaspberryPi 4 platform.
> /EG
>
>
>
>
>
> On Tuesday, February 25, 2020 at 9:11:40 AM UTC-5, Eric Gammeter wrote:
>>
>>
>> Goal:
>> Wanting to switch from sqlite to MySql database.
>>
>> I am consulting the github /weewx/wiki "Usingwee_database".
>>
>> The --dry-run doesn't show any error.
>>
>>
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding
>> --dry-run
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination
>> database 'weewx'.
>> Dry run, nothing done.
>> pi@raspberrypi:~ $ wee_database --transfer --dest-binding=dest_binding
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database
>> 'archive_sqlite'
>> Transfer 9177 records from source database 'weewx.sdb' to destination
>> database 'weewx' (y/n)? y
>> Error accessing destination database 'weewx'.
>> Nothing done. Aborting.
>> Traceback (most recent call last):
>>   File "/usr/bin/wee_database", line 794, in 
>> main()
>>   File "/usr/bin/wee_database", line 159, in main
>> transferDatabase(config_dict, db_binding, options)
>>   File "/usr/bin/wee_database", line 410, in transferDatabase
>> schema=dest_manager_dict['schema']) as dest_manager:
>>   File "/usr/share/weewx/weewx/manager.py", line 128, in open_with_create
>> connection = weedb.connect(database_dict)
>>   File "/usr/share/weewx/weedb/__init__.py", line 86, in connect
>> __import__(db_dict['driver'])
>>   File "/usr/share/weewx/weedb/mysql.py", line 10, in 
>> import MySQLdb
>> ImportError: No module named MySQLdb
>>
>> --
> 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/160ebdf6-3c35-4c85-9902-85d0685b9034%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/CAPq0zEAUUDSZTBFQSLcRasFiWOSkyxwKpogCFO%3DJGmjcXtPAUQ%40mail.gmail.com.

Re: [weewx-user] Almanac Extras....

[Thomas Keffer]

Do you have several versions of Python on your machine? It's possible
pyephem was installed using one version, but you're trying to run weewxd
under another.

Try invoking python explicitly when you run wee_reports and weewxd. This
will guarantee that they are using the same version of Python:

*sudo python /usr/share/weewx/weewxd /etc/weewx/weewx.conf*
*sudo python /usr/share/weewx/wee_reports /etc/weewx/weewx.conf*

See if those give the same results.

-tk

On Sun, Mar 1, 2020 at 11:55 PM Jason Gill  wrote:

> Hello,
>
> I added pyephem to show extra almanac info on my main page. When I moved
> weewx between servers this stopped working although the setup seems the
> same.
>
> Version Info:
> pyephem version is 3.7.7.0
> weewx version is v3.9.2
>
> When I run "sudo wee_reports  /etc/weewx/weewx.conf" (seen in another
> post) the main page reports the following extended almanac info after
> wee_reports completes
>
> Sun
> Start civil twilight: 06:40:25 AM
> Sunrise: 07:07:13 AM
> Transit: 01:33:21 PM
> Sunset: 07:58:52 PM
> End civil twilight: 08:25:36 PM
> Equinox: 03/20/2020 04:49:32 PM
> Solstice: 06/21/2020 09:43:46 AM
>
> Moon
> Rise: 01:41:29 PM
> Transit: 06:55:13 PM
> Set: 12:04:19 AM
> Full moon: 03/10/2020 06:47:42 AM
> New moon: 03/24/2020 10:28:11 PM
> Phase: First quarter (45% full)
>
> When the next periods data arrives the almanac returns to this:
>
> Sunrise: 07:07:36
> Sunset: 19:59:08
> Moon Phase: First quarter (50% full)
>
> The same config file is used for both wee_reports and when I restart
> weewx. Any ideas - I must have missed something?
>
> Regards,
> Jason.
>
>
>
>
>
> --
> 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/c2f7ae08-3eb7-403d-a68e-0a2439f9e4e5%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/CAPq0zEC8seRefDyyP3tBM5twuj6iWjsgLteU6tBwXF0WSg%3D-dA%40mail.gmail.com.

Re: [weewx-user] ImportError: No module named _mysql_exceptions

[Thomas Keffer]

Which platform are you using?

Looks like you did some kind of non-standard install of WeeWX, which is
fine. I doubt it is the problem.

However, how did you install the mysql driver?

-tk

On Sat, Feb 29, 2020 at 12:06 PM Cat22  wrote:

> Hi,
> weewx 3.9.2
>   I am adding the mysql capability to my weewx install and having some
> trouble getting it going. (sqlite is working though)
> I have verified the username and password work ok from a command prompt
> and the table(s) are there imported from a previous system and they are
> readable
> The issue sems to be the proper python files but I have installed what
> looked right (I am on openSuse Tumbleweed x86_64)
> TIA
> Cat22
> Here is the relevant parts of my weewx.conf:
>
> #   This section binds a data store to a database.
>
> [DataBindings]
>
> [[wx_binding]]
> # The database must match one of the sections in [Databases].
> # This is likely to be the only option you would want to change.
> #database = archive_sqlite
> database = archive_mysql
> # The name of the table within the database
> table_name = archive
> # The manager handles aggregation of data for historical summaries
> manager = weewx.wxmanager.WXDaySummaryManager
> # The schema defines the structure of the database.
> # It is *only* used when the database is created.
> schema = schemas.wview.schema
>
>
> ##
>
> #   This section defines various databases.
>
> [Databases]
>
> # A SQLite database is simply a single file
> [[archive_sqlite]]
> database_type = SQLite
> database_name = weewx.sdb
>
> # MySQL
> [[archive_mysql]]
> database_type = MySQL
> database_name = weewx
>
>
> ##
>
> #   This section defines defaults for the different types of databases.
>
> [DatabaseTypes]
>
> # Defaults for SQLite databases
> [[SQLite]]
> driver = weedb.sqlite
> # Directory in which the database files are located
> SQLITE_ROOT = %(WEEWX_ROOT)s/archive
>
> # Defaults for MySQL databases
> [[MySQL]]
> driver = weedb.mysql
> # The host where the database is located
> host = localhost
> # The user name for logging in to the host
> user = 
> # The password for the user name
> password = 
>
>
>
> And here is the error from journalctl:
>
>  engine: Using Python 2.7.17 (default, Oct 24 2019, 12:43:41) [GCC]
>  engine: Platform Linux-5.4.14-x86_64-with-glibc2.2.5
>  engine: Locale is 'en_US.UTF-8'
>  engine: Using configuration file /usr/local/bin/weewx/weewx.conf
>  engine: Loading station type Vantage (weewx.drivers.vantage)
>  engine: StdConvert target unit is 0x1
>  wxcalculate: The following values will be calculated: barometer=
> prefer_hardware, windchill=prefer_hardware, dewpoint=prefer_hardware,
> appTemp=prefer_hardware, rainRate=prefer_hardware, windrun=prefer_hardware
> , heatindex=prefer_hardware>
>  wxcalculate: The following algorithms will be used for calculations:
> altimeter=aaNOAA, maxSolarRad=RS
>  engine: Archive will use data binding wx_binding
>  engine: Record generation will be attempted in 'hardware'
>  engine: Using archive interval of 300 seconds (specified by hardware)
>  engine: Caught unrecoverable exception in engine:
>    No module named _mysql_exceptions
>    Traceback (most recent call last):
>  File "/usr/local/bin/weewx/bin/weewx/engine.py", line 888, in
> main
>    engine = engine_class(config_dict)
>  File "/usr/local/bin/weewx/bin/weewx/engine.py", line 78, in
> __init__
>   Traceback (most recent call last):
> File "/usr/local/bin/weewx/bin/weewxd", line 64, in 
>   weewx.engine.main(options, args)
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 888, in main
>    self.loadServices(config_dict)
>   engine = engine_class(config_dict)
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 78, in __init__
>   self.loadServices(config_dict)
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 142, in
> loadServices
>   self.service_obj.append(weeutil.weeutil._get_object(svc)(self,
> config_dict))
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 500, in __init__
>   self.setup_database(config_dict)
> File "/usr/local/bin/weewx/bin/weewx/engine.py", line 608, in
> setup_database
>  File "/usr/local/bin/weewx/bin/weewx/engine.py", line 142, in
> loadServices
>   dbmanager = self.engine.db_binder.get_manager(self.data_binding,
> initialize=True)
> File "/usr/local/bin/weewx/bin/weewx/manager.py", line 872, in
> get_manager
>   self.manager_cache[data_binding] = open_manager(manager_dict,
> initialize)
> File "/usr/local/bin/weewx/bin/weewx/manager.py",