WeeWX v3.8.2 released

[Thomas Keffer]

This is a combined release, which includes changes for v3.8.1. 

In the usual place.

Change log:

3.8.2 08/15/2018

Added flag to weewx-multi init script to prevent systemd from breaking it.
Thanks to users Timo, Glenn McKechnie, and Paul Oversmith.

Fixed problem that caused wind direction in archive records to always be
calculated in software, even with stations that provide it in hardware.
Fixes issue #336.

3.8.1 06/27/2018

Map cc3000 backup battery to consBatteryVoltage and station battery to
supplyVoltage to more accurately reflect the battery functions.

Update the syntax in the rsyslog configuration sample

Significant overhaul to the WMR300 driver. The driver should now work reliably
on any version of pyusb and libusb. The driver will now delete history records
from the logger before the logger fills up (the WMR300 logger is not a circular
buffer). Thanks to users Markus Biewer and Cameron. Fixes issue #288.

Added automatic clearing of logger for CC3000 driver to prevent logger
overflow (the CC3000 logger is not a circular buffer). The default is to
not clear the history, but it is highly recommended that you add a logging
threshold once you are confident that all logger data have been captured to
the weewx database.

Improved the robustness of reading from the CC3000 logger.

Better CRC error message in Vantage driver.

Parameterize the configuration directory in weewx-multi init script.

In StdWXCalculate, use None for an observation only if the variables on which
the derived depends are available and None. Fixes issue #291.

Fixed bug that prevented specifying an explicit alamanac time from working.

Fixed bug that prevented historical records from being downloaded from ws23xx
stations. Thanks to user Matt Brown! Fixes issue #295

Fixed bug that crashed program if a sqlite permission error occurred.

If wind speed is zero, accumulators now return last known wind direction
(instead of None). Thanks to user DigitalDan05. PR #303.

Windrun calculations now include the "current" record. Fixes issue #294.

Fixed bug involving stations that report windGust, but not windGustDir, in
their LOOP data (e.g., Fine Offset), which prevented the direction of max
wind from appearing in statistics. Fixes issue #320.

The engine now waits until the system time is greater than the creation time
of the weewx.conf file before starting up. Fixes issue #330.

[Pat]

Great news!

I created 2 new virtual machines (Ubuntu 16.04 and Ubuntu 18.04) and did a clean install of weewx. It seems the apt repository isn't updated with 3.8.2 yet. Anything in addition I need besides the usual Debian install instructions?

root@weewxubuntu18lab:~# date
Thu Aug 16 17:54:20 UTC 2018

root@weewxubuntu18lab:~# apt-cache show weewx | grep Version
Version: 3.8.0-1

[Thomas Keffer]

I'm afraid Matthew is going to have to do that. Matthew?

-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+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Matthew Wall]

> On 16 Aug 2018, at 13:55, Pat <p...@obrienphoto.net> wrote:
>
> It seems the apt repository isn't updated with 3.8.2 yet. Anything in addition I need besides the usual Debian install instructions?

the apt repository at weewx.com has now been updated

[Alberto Sánchez]

Great job. Thank you very much to all the people who have collaborated.👏👏👏👏👏

[G Hammer]

Update changed my skin to default. Now looking for what else it may have changed.

setup.by install & upgrade method.

[Thomas Keffer]

Yes, this is a known bug. Issue #217.

-tk

On Thu, Aug 16, 2018 at 1:35 PM G Hammer <gary....@gmail.com> wrote:

Update changed my skin to default. Now looking for what else it may have changed.

setup.by install & upgrade method.

[G Hammer]

It would be nicer if either this were corrected or if the upgrade guide had a warning in it.

As there were no program changes in weewx.conf, I just moved the 3.8.1 version back in place and wiped the web of all files.

The scheduled ftp put the site back to the desired state/look.

[Thomas Keffer]

Yes, it would be nicer. How about a Pull Request that addresses the problem?

-tk

[Pat]

Standard disclaimer on being volunteers on an open source software project. If you spot the fix, you can submit the changes for the next version.

If you want to force an update to re-ftp your web files, you can run wee_reports and not wait until the archive period. 

[vince]

On Thursday, August 16, 2018 at 1:53:55 PM UTC-7, G Hammer wrote:

It would be nicer if either this were corrected or if the upgrade guide had a warning in it.

As there were no program changes in weewx.conf, I just moved the 3.8.1 version back in place and wiped the web of all files.

The scheduled ftp put the site back to the desired state/look.

Hmmmm - I did a 'setup.py build' and 'setup.py install' to upgrade mine and there was no ripple at all.

One thing I do that might be helpful as a risk prevention thing is change the location that the Standard_Skin writes to, so while it still runs, my actual site uses my modified local skin.  You might want to think about that as a risk prevention thing...

    [[StandardReport]]

        skin = Standard

        HTML_ROOT = public_html/Standard

        # units entries omitted for brevity...

        # units entries omitted for brevity...

        # units entries omitted for brevity...

    [[my-local]]

        skin = my-local

        HTML_ROOT = public_html

 

[G Hammer]

Ahhh, I compared the conf files and found what happened.

I do not use [[StandardReport]]and have the section commented out.

The upgrade added it back without commenting it out.

That, of course, caused the website to be completely changed.

No real issue as it was easy to recover from, just wanted to point out that it did change my conf file and that did change the website.

I'm using Weewx-WD to provide the data for a Saratoga templated site.

I shall look to see if I can spot and make a correction for this in setup. If so, I'll do a pull request.

[G Hammer]

I've had a quick look and it seems there is only the merge or leave it alone option.

I'd say to put a warning in the upgrade guide.

[James Greiner]

Updated my 3.8.1 to 3.8.2 no issues... Thanks for the hard work!

[John Clark]

I installed mine using the python method. do I update with apt-get or is there another "correct" way? BTW, I seem to have gotten weewx running on a Pi (after about 10 tries, keeping my fingers crossed) it took the upgrade first try. for some reason I can't see it with localhost, but was gonna sit it on the shelf anyhow. Now I need to copy my database.

--
John Clark