Version 4.0 is (finally) here!

[Tom Keffer]

After months of waiting, Version 4 has finally arrived! The major new feature is that WeeWX will not run under either Python 2 or Python 3.

It took a long time to get the packaging right but now, thanks to Matthew Wall, WeeWX is easier than ever to install. Be sure to read the installation instructions for your specific operating system. As always, a setup.py install method is also supported.

Generally, the package installers will use Python 3, if its available. On older systems, the installers will use Python 2.

CHANGE LOG

Ported to Python 3. WeeWX should now run under Python 3.5 and greater, as well
as Python 2.7. Support for Python 2.5 and 2.6 has been dropped.

New facility for creating new user-defined derived types. See the Wiki article
https://github.com/weewx/weewx/wiki/WeeWX-V4-user-defined-types

WeeWX now uses the Python 'logging' facility. This means log, formats, and other
things can now be customized. Fixes issue #353.

Strings appearing in the data stream no longer cause a TypeError if they can be
converted to a number.

Strings can now be accumulated and extracted in the accumulators, making it
possible to include them in the database schemas.

The utility wee_reports now loads services, allowing it to use user-supplied
extensions. Fixes issue #95.

New default schema ("wview_extended") that offers many new types. The old schema
is still supported. Fixes issue #115.

Optional, more flexible, way of specifying schemas for the daily summaries. The
old way is still supported.

The install process now offers to register a user's station with weewx.com.

The package MySQL-python, which we used previously, is not always available on
Python 3. Ported the MySQL code to use the package mysqlclient as an
alternative.

The default for WOW no longer throttles posting frequency (the default used to
be no more than once every 15 minutes).

Added new aggregate types minsum, minsumtime, sum_le. PR #382.

Unit group group_distance is now a first-class group.

Added new tag $python_version.

Ported to Python2-PyMySQL package on OpenSUSE.

Added new aggregation types 'first' (similar to 'last'), 'diff' (the difference
between last and first value in the aggregation interval), and 'tderiv' (the
difference divided by the time difference).

Created new unit group 'group_energy2', defined as watt-seconds. Useful for high
resolution energy monitors.

An observation type known to the system, but not in a record, will now return a
proper ValueTuple, rather than UnknownType.

Type "stormStart" was added to the unit system. Fixes issue #380.

Added new aggregation type 'growdeg'. Similar to 'heatdeg', or 'cooldeg', it
measures growing degree-days. Basically, cooldeg, but with a different base.
Fixes issue #367. Thanks to user Clay Jackson for guidance!

Ported OS uptime to OpenBSD. Fixes issue #428. Thanks to user Jeff Ross!

Catch SSL certificate errors in uploaders. Retry after an hour. Fixes issue
#413.

Wunderfixer has been ported to the new WU API. This API requires an API key,
which you can get from the WU. Put it in weewx.conf. Added option --upload-only.
Thanks to user Leon Shaner! Fixes issues #414 and #445.

Wee_import can now import Weather Display monthly log files.

Fixed problem where sub-sections DegreeDays and Trend were located under the
wrong weewx.conf section. Fixes issue #432. Thanks to user mph for spotting
this!

Added new parameters to the Weather Underground uploader. Fixes issue #435.

Added new air quality types pm1_0, pm2_5, and pm10_0 to the unit system. Added
new unit microgram_per_meter_cubed. Added new unit group, group_concentration.

Plist for the Mac launcher now includes a log file for stderr.

Night-day transition in plots now uses shortest travel distance around color
wheel to minimize extra colors. Fixes issue #457. Thanks to user Alex Edwards!

Fixed bug that causes plots to fail when both min and max are zero. Fixes issue
#463.

Fixed problem with sqlite driver that can lead to memory growth. See PR #467.
Thanks to user Rich Bell!

Fixed bug that caused windrun to be calculated wrongly under METRICWX unit
system. Fixes issue #452.

If a bad value of 'interval' is encountered in a record, the program will simply
ignore it, rather than stopping. Address issue #375.

Change in how the archive timespan is calculated in the engine. This allows
oddball archive intervals. Fixes issue #469.

NOAA reports are now more tolerant of missing data. Fixes issue #300.

Use of strftime() date and time format codes in template file names is now
supported as an alternative to the legacy 'YYYY', 'MM' and 'DD'. The legacy
codes continue to be supported for backwards compatibility. Fixes issue #415.

New --calc-missing action added to wee_database to calculate and store derived
observations.

wee_import now calculates missing derived observations once all imported data
has been saved to archive. Fixes issue #443.

wee_import now tolerates periods that contain no source data. Fixes issue #499.

wee_import now accepts strings representing cardinal, intercardinal and
secondary intercardinal directions in CSV imports. Partially fixes issue #238.

The field delimiter character may now be defined for wee_import CSV imports.

Ignore historical records if the timestamp is in the future.

Can now recover from MariaDB-specific database connection error 1927.

Changed the name of the unit "litre" to "liter", making its spelling more
consistent with "meter". The spelling "litre" is still accepted.

Systemd type changed from "simple" to "forking". Thanks to user Jaap de Munck
for figuring this one out!

The configuration file is now an optional argument when running weewxd directly.
This means most users will be able to use the simple command line 'sudo weewxd'.

Use correct log path for netbsd and openbsd in logger setup.

StdWXCalculate no longer calculates anything by default. Instead, types to be
calculated must be listed in weewx.conf. See the Upgrade Guide.

setup.py install no longer saves the old 'bin' subdirectory. Instead, it simply
overwrites it.

[Tom]

Don't you mean NOW not NOT in 1st paragraph? 

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

[Tom Keffer]

I do! Damn autocorrect!

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CABBJzNi4%2BCy0o75qiUjA8ukp9-18rnf5hHGMkzBWdBtsLGiKqQ%40mail.gmail.com.

[Chris Alemany]

Having watched the threads on weewx-dev for months now I just want to say great work and thank you to Tom and Matt and *all* of the amazing people who contribute to this excellent software.

Congratulations on the release.

Really looking forward to trying it out!

Cheers

Chris

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

[vince]

Fabulous stuff !!!!

Updated my two sites via setup.py, one python3 one python2.

Works great !

[Redig]

Fantastic! thank you.

Maybe I'm doing something incorrectly, but it seems the apt-get package references the python 2 names for dependencies - 

Version: 4.0.0-1

Depends: python (>= 2.7), python (<< 3.0), python-configobj (>= 4.5), python-cheetah (>= 2.0), python-imaging (>= 1.1.6) | python-pil (>= 5.1.0) | python-pillow (>= 5.1.0), python-serial (>= 2.3), python-usb (>= 0.4), lsb-base

 

When I run apt-get install weewx  or apt-get install weewx=4.0.0-1 on Ubuntu 20.04 I get

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 weewx : Depends: python-configobj (>= 4.5) but it is not installable

         Depends: python-serial (>= 2.3) but it is not installable

E: Unable to correct problems, you have held broken packages.

python3-configobj 5.0.6-4 and python3-serial 3.4-5.1 are already installed.

[wysiwyg]

Very good news!

Congratulations & thank you !

I'll try it as soon as I can :)

[mwall]

On Thursday, April 30, 2020 at 2:23:26 PM UTC-4, Redig wrote:

Fantastic! thank you.

Maybe I'm doing something incorrectly, but it seems the apt-get package references the python 2 names for dependencies - 

Version: 4.0.0-1

Depends: python (>= 2.7), python (<< 3.0), python-configobj (>= 4.5), python-cheetah (>= 2.0), python-imaging (>= 1.1.6) | python-pil (>= 5.1.0) | python-pillow (>= 5.1.0), python-serial (>= 2.3), python-usb (>= 0.4), lsb-base

 

When I run apt-get install weewx  or apt-get install weewx=4.0.0-1 on Ubuntu 20.04 I get

Reading package lists... Done

Building dependency tree

Reading state information... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 weewx : Depends: python-configobj (>= 4.5) but it is not installable

         Depends: python-serial (>= 2.3) but it is not installable

E: Unable to correct problems, you have held broken packages.

python3-configobj 5.0.6-4 and python3-serial 3.4-5.1 are already installed.

for ubuntu 20.04, please use the python3 weewx list file, not the python2 file:

wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list

then do:

sudo apt-get update

sudo apt-get install weewx

[Redig]

Worked like a charm. Thank you.

[mwall]

for those interested in the python2/python3 details, as well as our strategy for supporting as many platforms as possible with minimal resources, these pages may help:

python3 strategy:

https://github.com/weewx/weewx/wiki/Python-3-strategy

dependency matrix and platform testing:

https://github.com/weewx/weewx/wiki/weewx4-compatibility-matrix

these are available from links on the weewx wiki

m

 

[Hyrules Hyrules]

Working well here too thanks alot.

[Greg from Oz]

Thanks Tom....It is sort of working.

My weather station batteries failed so I just fixed that and then I did an apt update && apt dist-upgrade and weewx was upgraded to version 4 but some parts are not working now.

Can I down grade if I can't work out how to fix the problems?

It is creating webpages etc 

Here is what isn't working.

May  1 10:10:39 jed164 weewx[12398] DEBUG weewx.cheetahgenerator: Using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']

May  1 10:10:39 jed164 weewx[12398] DEBUG weewx.manager: Daily summary version is 2.0

May  1 10:10:39 jed164 weewx[12398] INFO weewx.cheetahgenerator: Generated 2 files for report SteelSeries in 0.21 seconds

May  1 10:10:39 jed164 weewx[12398] DEBUG weewx.manager: Daily summary version is 2.0

May  1 10:10:39 jed164 weewx[12398] DEBUG PIL.PngImagePlugin: STREAM 'IHDR' 16 13

May  1 10:10:39 jed164 weewx[12398] DEBUG PIL.PngImagePlugin: STREAM 'IDAT' 41 1216

May  1 10:10:39 jed164 weewx[12398] DEBUG PIL.PngImagePlugin: STREAM 'IHDR' 16 13

May  1 10:10:39 jed164 weewx[12398] DEBUG PIL.PngImagePlugin: STREAM 'IDAT' 41 1216

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine: Caught unrecoverable exception in generator 'weewx.imagegenerator.ImageGenerator'

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****  rainrate

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****  Traceback (most recent call last):

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/reportengine.py", line 197, in run

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****      obj.start()

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/reportengine.py", line 280, in start

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****      self.run()

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/imagegenerator.py", line 41, in run

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****      self.genImages(self.gen_ts)

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/imagegenerator.py", line 180, in genImages

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****      aggregate_interval=aggregate_interval)

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****    File "/usr/share/weewx/weewx/xtypes.py", line 91, in get_series

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****      raise weewx.UnknownType(obs_type)

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****  UnknownType: rainrate

May  1 10:10:39 jed164 weewx[12398] ERROR weewx.reportengine:         ****  Generator terminated

May  1 10:10:39 je

[Tom Keffer]

Known problem, caused by the SteelGauge series using 'rainrate' instead of what is actually in the database, 'rainRate'. I'm not a SteelGauge expert, but I believe people have found solutions. Search through weewx-user and/or weewx-development.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/cf15dd3e-9d42-4086-aba3-59d3de08892b%40googlegroups.com.

[Greg from Oz]

Hi I did

 wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list

then :

sudo apt-get update

sudo apt-get install weewx 

Then I got the error below. I am running a fresh install of Ubuntu 20.04

W: GPG error: http://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E

E: The repository 'http://weewx.com/apt/python3 buster InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

x~$ sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys ED444FCCF0E2B09E

Executing: /tmp/apt-key-gpghome.gHg4hBX3CF/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys ED444FCCF0E2B09E

gpg: keyserver receive failed: No data

[mwall]

On Thursday, April 30, 2020 at 8:44:15 PM UTC-4, Greg from Oz wrote:

Then I got the error below. I am running a fresh install of Ubuntu 20.04

W: GPG error: http://weewx.com/apt/python3 buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY ED444FCCF0E2B09E

E: The repository 'http://weewx.com/apt/python3 buster InRelease' is not signed.

N: Updating from such a repository can't be done securely, and is therefore disabled by default.

N: See apt-secure(8) manpage for repository creation and user configuration details.

did you do this:

curl -s http://weewx.com/keys.html | sudo apt-key add -

the first step in the 'Configure apt' section here:

http://weewx.com/docs/debian.htm

[Greg from Oz]

That was it..........I missed that copy and paste.

I have updated my install script.

Is there a systemd script for starting and stopping instead of /etc/init.d/weewx ?

It is running. So far so good.

Great job! Thank you so much. Now to find out why steel series gauges don't work. If I can't figure it out I will just comment it out.

[mwall]

On Thursday, April 30, 2020 at 9:32:26 PM UTC-4, Greg from Oz wrote:

That was it..........I missed that copy and paste.

I have updated my install script.

Is there a systemd script for starting and stopping instead of /etc/init.d/weewx ?

just do any of these:

sudo systemctl start weewx

sudo systemctl status weewx

sudo systemctl stop weewx

beware that if you do not preface with 'sudo' you might get a cryptic message about 'org.freedesktop.PolicyKit1 was not provided by any .service files'

m

[Greg from Oz]

Thanks.

I looked in /etc/systemd/system and didn't see any weewx.service

[Gert Andersen]

Hi

I have version 3.9.2 running today. I'm a little unsure if I can update to 4.0 by following the installation description or I need to delete version 3.9.2 first and do a clean install of version 4.0. Have read through the guide and can't really find anything about it. If I can update, is there something to save, weewx.conf, weewx.dg, etc.

Thank you very much for Weewx and the great work you do.

Gert

[Greg from Oz]

I just upgraded mine from 3.9.2 to 4 and it was OK.

I had Steel series skin and that caused a problem but you just rename rainrate to rainRate in the skin and that was fixed.

I also have Belechertown skin running so I downloaded the latest version and that worked as well.

So it was fairly smooth upgrade and it is working.

Good luck, you should be fine but backup if you are concerned.

[Colin Larsen]

I've just updated from 3.9 to 4.0 on my RPi using Belchertown skins. Easy update - many thanks for all the work that's gone into this!

Cheers

Colin

41south.nz

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a3c29a0f-a2ab-45c9-a955-aea0a74d11d1%40googlegroups.com.

[Gert Andersen]

Hi

I'm running Ubuntu 18.04 and Weewx 3.9.2 updating to Weewx 4.0. I'm following the installation guide for Debian: http://www.weewx.com/docs/debian.htm

I get this error:

0 pakker kan opdateres.

0 opdateringer er sikkerhedsopdateringer.

ubuntu@gand:~$ wget -qO - http://weewx.com/keys.html | sudo apt-key add -

OK

ubuntu@gand:~$ wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list

deb [arch=all] http://weewx.com/apt/python3 buster main

ubuntu@gand:~$ sudo apt-get update

Hit:1 http://mirror.eu-fr.gand.com/ubuntu bionic InRelease

Hit:2 http://mirror.eu-fr.gand.com/ubuntu bionic-updates InRelease

Hit:3 http://mirror.eu-fr.gand.com/ubuntu bionic-backports InRelease

Hit:4 http://ppa.launchpad.net/certbot/certbot/ubuntu bionic InRelease

Hit:5 http://security.ubuntu.com/ubuntu bionic-security InRelease

Get:6 http://mirrors.ubuntu.com/mirrors.txt Mirrorlist [1.653 B]

Hit:10 http://ppa.launchpad.net/mosquitto-dev/mosquitto-ppa/ubuntu bionic InRelease

Hit:11 http://ppa.launchpad.net/ondrej/php/ubuntu bionic InRelease

Hit:8 http://ftp.fau.de/ubuntu bionic-updates InRelease

Hit:7 http://ubuntu.unitedcolo.de/ubuntu bionic InRelease

Hit:9 http://ftp.rz.tu-bs.de/pub/mirror/ubuntu-packages bionic-backports InRelease

Hit:12 http://weewx.com/apt/python3 buster InRelease

Hentede 1.653 B på 1s (1.608 B/s)

Reading package lists... Done

ubuntu@gand:~$ sudo apt-get install weewx

Reading package lists... Done

Building dependency tree

Reading state information... Done

Calculating upgrade... Done

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 weewx : Depends: python3-cheetah but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

I have tried:

sudo apt-get install -f python3-cheetah > No Luck

Any ideas?

Gert

On Thursday, April 30, 2020 at 7:09:47 PM UTC+2, Tom Keffer wrote:

[Greg from Oz]

I upgraded my 18.04 but I just did apt update

It asked to change the source list for weewx.

and it came back and said that weewx could be upgraded.

I did apt dist-upgrade

I didn't have to do anything else.

I think is you ran this:

wget -qO - http://weewx.com/apt/weewx-python2.list | sudo tee /etc/apt/sources.list.d/weewx.list

To get the python 2 files it would work...

[Manfred Maier]

Hmm ... I'm obviously doing something wrong.

I'm running Weewx on a RPi 4 (latest version of Rasbian). The original installation was done via the DEB package (at least I think that I did it that way).

I've now tried to update:

sudo apt-get update:   Runs fine

sudo apt-get install weewx:    Returns with a message, that I'm already on the latest version (3.9.2)

Where is my mistake?

Thanks! 

Manfred 

[Greg from Oz]

My guess would be when you ran the python3 instead of python2 

ubuntu@gand:~$ wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list

instead of

ubuntu@gand:~$ wget -qO - http://weewx.com/apt/weewx-python2.list | sudo tee /etc/apt/sources.list.d/weewx.list

[Manfred Maier]

OK. Now I've killed weewx on my system.

I've tried to run curl -s http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list before doing the update. 

The update itself was performed and 4.0 got installed.

But now weewx isn't running anymore. I can "start" it, but it doesn't start.

Any help will be highly appreciated!

Manfred 

[Gert Andersen]

Hi

@Greg from Oz

Thanks for looking.

I ran this :

ubuntu@gand:~$ wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee /etc/apt/sources.list.d/weewx.list

I just followed the guide.

Should I also run:

ubuntu@gand:~$ wget -qO - http://weewx.com/apt/weewx-python2.list | sudo tee /etc/apt/sources.list.d/weewx.list

Rgds

Gert

[Greg from Oz]

i don't know if you should run it or not but if it is already broken you can't make it any worse. 

[salinois]

hello

me too

Congratulations & thank you !

I'll try it as soon as I can :)

Patrick from FRANCE.

Le 30/04/2020 à 19:24, Tom Keffer a écrit :

I do! Damn autocorrect!

On Thu, Apr 30, 2020 at 10:20 AM Tom <nine...@gmail.com> wrote:

Don't you mean NOW not NOT in 1st paragraph? 

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zECyaH0t8F-2CvnBp0ew_ZYM-G1uBA_sTX1y%3DRsLGzH27Q%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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CABBJzNi4%2BCy0o75qiUjA8ukp9-18rnf5hHGMkzBWdBtsLGiKqQ%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+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBcDHV_K6BN88DtUkC_Yrf0UQCQCA6TSht1YMZYyCyRXg%40mail.gmail.com.

[Tom Keffer]

On Fri, May 1, 2020 at 1:14 AM Gert Andersen <gert.a...@gmail.com> wrote:

Hi

I'm running Ubuntu 18.04 and Weewx 3.9.2 updating to Weewx 4.0. I'm following the installation guide for Debian: http://www.weewx.com/docs/debian.htm

...

I have tried:

sudo apt-get install -f python3-cheetah > No Luck

 

Can you be more specific than "No Luck"?

[Tom Keffer]

EVERYONE: 

The default python for debian 9 and 10 is Python 3, not Python 2. This includes all debian stretch- and buster-based distributions, such as Raspbian, and Ubuntu. 

If for some reason you want to continue using Python 2 on these systems, you can do so, but you will have to (1) make sure the prerequisites are there, and (2) invoke the executables using the explicit version of Python.

-tk

[mwall]

On Friday, May 1, 2020 at 8:54:39 AM UTC-4, Tom Keffer wrote:

EVERYONE: 

The default python for debian 9 and 10 is Python 3, not Python 2. This includes all debian stretch- and buster-based distributions, such as Raspbian, and Ubuntu. 

slight correction:

the python3-weewx package is supported on debian10 (use the weewx-python3.list file)

the python-weewx package is supported on every debian back to 7, including debian10 (use the weewx-python2.list file)

if you were using any debian system and had installed weewx using apt, then all you have to do is 'sudo apt-get update; sudo apt-get install weewx'.  that will bring you to weewx4, still using python2.

if you are using debian10, then you can grab the weewx-python3.list file then do the 'sudo apt-get update; sudo apt-get install weewx' and you will get weewx4 and python3.

debian9 won't work out-of-the-box with the python3-weewx package because debian9 does not have a cheetah package for python3.  you would have to install cheetah for python3 yourself, then force apt to ignore the dependency.

the dependency matrix lists all of the details:

https://github.com/weewx/weewx/wiki/weewx4-compatibility-matrix

m

[G Hammer]

There is an extra space in the default weewx4.0.0.conf file

May or may not affect anything but after my go around with spaces vs python3, thought I'd mention it.

[Manfred Maier]

After some hiccups (incompatible extensions: SFTP, OWM, Wetter, WCloud) my system (python 3) is now up and running.

Thanks a lot to everyone involved in the development and the entire community that provides a fantastic support here!

[Phil Green]

Just updated to v4 using setup.py method. No problems.
One question, I am running python version 2.7.16, how easy is it to change over to python version 3 and to ensure Weewx continues to work?
Thanks for the great work.
Regards
Phil

[vince]

On Friday, May 1, 2020 at 2:43:50 PM UTC-7, Phil Green wrote:

Just updated to v4 using setup.py method. No problems.
One question, I am running python version 2.7.16, how easy is it to change over to python version 3 and to ensure Weewx continues to work?

Asked and answered probably 10 times in the last week here.

Just run the setup.py procedure using the python3 instructions and supersede your setup, much like you'd do a version update.   Be sure to have all python3-compliant extensions and skins, and be sure to have all the python3 prerequisite packages for your os.  Very straightforward. 

[Tom Keffer]

It's even easier than what Vince outlined. All you need to do is make sure the prerequisites for Python 3 are in place. Then you can run using python2 or python3.

python2 ./bin/weewxd weewx.conf

or

python3 ./bin/weewxd weewx.conf

The prerequisites for Python 3 are listed in the setup.py install instructions.

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

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e56278b1-a5c6-4050-8cd8-8eb253c9ac47%40googlegroups.com.

[Devonian]

Trying to upgrade from weewx-3.9.2 to weewx-4.0.0 on Debian Buster on intel 64bit system using setup.py and get...

nigel@debian10:~/weewx-4.0.0$ python3 ./setup.py build

Traceback (most recent call last):

  File "./setup.py", line 25, in <module>

    from distutils import log

ImportError: cannot import name 'log' from 'distutils' (/usr/lib/python3.7/distutils/__init__.py)

nigel@debian10:~/weewx-4.0.0$ python3 -V

Python 3.7.3

What's wrong?

Nigel

[Tom Keffer]

You're not the first to have this problem.

Solved with

sudo apt install python3-pip

Then try again.

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/52b4783a-aa20-4fee-9594-f9332e4e3085%40googlegroups.com.

[Devonian]

Thanks Tom - that did it.

It's not in the prerequisites - maybe worth a mention in there http://www.weewx.com/docs/setup.htm ??

Now to fix rtgd problem that's thrown up after the upgrade...

Nigel

[gjr80]

Nigel,

What rtgd version are you using? I have updated it for WeeWX 4 but it was tested against the betas not the release (should not make any difference though). Try the latest and if still a problem post the log showing the error.

Gary

[Devonian]

Hi Gary,

Not sure of version, but at least 18 months sice I touched it !!

Will update in the morning.

Just commented out the engine for now and will look in the morning after some zzzz's (it's 10 past midnight here).

Nigel

[gjr80]

Yep, that's the problem. Let us know how it goes.

Gary

[Gert Andersen]

Hi

@Tom Keffer, with no luck I mean, I get the error:

The following packages have unmet dependencies:

 weewx : Depends: python3-cheetah but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

@mwall

I'm running ubuntu 18.04 so I should use Debian 10.

I did the he weewx-python3.list and then "sudo apt-get update; sudo apt-get install weewx"

Result:

Some packages could not be installed. This may mean that you have

requested an impossible situation or if you are using the unstable

distribution that some required packages have not yet been created

or been moved out of Incoming.

The following information may help to resolve the situation:

The following packages have unmet dependencies:

 weewx : Depends: python3-cheetah but it is not going to be installed

E: Unable to correct problems, you have held broken packages.

I have also tried: apt-get install python3-cheetah

Result:

Package python3-cheetah is not available but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'python3-cheetah' has no installation candidate

Gert

[Greg from Oz]

Does /etc/apt/sources.list.d/weewx.list

look like this?

deb [arch=all] http://weewx.com/apt/ squeeze main

That is what mine looks like.

I just did 

sudo apt update

then it informed me there was a new versionof weewx and then I did:

sudo apt dist-upgrade

and that was it.

https://weather.ubeaut.work/

[Jaap de Munck]

@Gert: Try to install cheetah via pip3.

http://www.weewx.com/docs/setup.htm

Follow Ubuntu 16.04-17.10

python3-cheetah is not available for Ubuntu 18.04 (the exception)

//Jaap

Op zaterdag 2 mei 2020 07:40:00 UTC+2 schreef Greg from Oz:

[Phil Green]

Hello,

Yesterday I reported that I have successfully updated to Weewx 4.0 on my system running Vantage Vue. At that stage I did not upgrade the install to python3.

This morning I have followed the instructions and installed all the prerequisites for pythion3 and done the install again using python3 scripts.

System is working fine.

My question is there a way to easily identify that Weewx is running under python3, even though I used the python3 commands to install?

Regards

Phil.

[gjr80]

Phil,

Yes, as usual it's in the log:

May  2 16:08:09 cockatoo weewx-ecowitt[11830] INFO __main__: Initializing weewx version 4.0.0
May  2 16:08:09 cockatoo weewx-ecowitt[11830] INFO __main__: Using Python 3.7.3 (default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
May  2 16:08:09 cockatoo weewx-ecowitt[11830] INFO __main__: Platform Linux-4.19.97-v7+-armv7l-with-debian-10.3
May  2 16:08:09 cockatoo weewx-ecowitt[11830] INFO __main__: Locale is 'en_AU.UTF-8'

Gary

[Greg from Oz]

ps -ef|grep weewx

  

root     29803     1  1 May01 ?        00:26:50 python2 /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid /etc/weewx/weewx.conf

On Saturday, 2 May 2020 19:05:08 UTC+10, Phil Green wrote:

[Phil Green]

That’s great. All running fine under python3.
Great software and excellent support.
Regards
Phil

[Graham Eddy]

that’s a lot simpler output than mine:

feral:~ $ ps -ef|grep -e weewx -e aqua
    0   168     1   0 12:05am ??         3:17.29 /System/Library/Frameworks/Python.framework/Versions/2.7/Resources/Python.app/Contents/MacOS/Python /opt/weewx/bin/weewxd /opt/weewx/weewx.conf --loop-on-init
    0   855     1   0 12:24am ??         0:23.85 /opt/local/Library/Frameworks/Python.framework/Versions/3.7/Resources/Python.app/Contents/MacOS/Python /opt/aquagauge/bin/aquagauged /opt/aquagauge/aquagauge.conf

  501  6232   611   0  7:53pm ttys000    0:00.00 grep -e weewx -e aqua

(included aquagauge server just to prove i’m running python3.7 via macports in preparation to moving weewx to 4.x :-)

____________

Graham Eddy

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d93c6115-52e0-4589-a4bd-54b5513bb0c7%40googlegroups.com.

[Devonian]

@ Gary,

I've updated my SteelSeries and rtgd and all working now.

One small thing has changed since my original install is that the scroller text is now missing (had to remove the old method that picked up local time as it didn't like that now).

How do I add some text to the scroller now?

Nigel.

[Gert Andersen]

Hi Greg from Oz

No my file looks like this:

deb [arch=all] http://weewx.com/apt/python3 buster main

Gert

[Gert Andersen]

Hi Jaap

Did and this message:

ubuntu@Kamatera:~$ sudo pip3 install cheetah3

The directory '/home/ubuntu/.cache/pip/http' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

The directory '/home/ubuntu/.cache/pip' or its parent directory is not owned by the current user and caching wheels has been disabled. check the permissions and owner of that directory. If executing pip with sudo, you may want sudo's -H flag.

Requirement already satisfied: cheetah3 in /usr/local/lib/python3.6/dist-packages

Gert

[vince]

On Friday, May 1, 2020 at 10:26:31 PM UTC-7, Gert Andersen wrote:

E: Unable to correct problems, you have held broken packages.

Please google that exact message and you will find dozens of hits with methods for how to clean this up.  Unfortunately, that particular mesage can be a bit painful to clean up, and occasionally comes with some risk.

FWIW, if you are on a raspberry pi, you 'might' find it simpler to put a new SD card in and simply build a clean system.

is not available but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

Again, if you google 'this' message you will get many hits describing what is going on.

 

[p q]

I upgraded from 3.5. Remarkably painless. Took maybe 15 minutes. 

Thanks!

I had previously set up a duplicate site on a VM and migrated that to 3.9 and then to 4.0. Doing all the prep work and testing took way longer than doing the actual upgrade.

Next job - upgrade Raspian from Stretch to Buster and then move the site to Python 3. I expect I'll have a few hiccoughs there due to some custom Python 2 code. But I've migrated other apps from 2 to 3, and I wrote the custom code to begin with.

[Bill M]

Finally got a few minutes to upgrade, still using Python 2.7 and Debian 9 but it went smoothly almost.

Must have missed comments that maxSolrRad is now maxSolarRad

Would have only taken 5 minutes if I'd seen that first

No biggie

[Devonian]

OK, I figured it for the scroller text - it doesn't like a comma (,) in the text.

I now have it running and picking up local time, by adding this to the [RealtimegaugeData] in weewx.conf

    [[Text]]

        text = Real Time Gauges - Local Time is %H:%M - Next gauge update in...

Nigel.

[Xant]

Tom

Just to report, that is "nothing" to report (and that's a good thing)....

WeeWx 4.0 working fine on my setup:

• rPi 4
• Python 3
• WeatherFlow
• QNAP NAS (as webserver)
• Belchertown skin 1.1

Update was smooth. I still keeps the original path (instead 'home'), but just edited 'setup.cfg'.

----------------------------------------------------------------------------------------------------------

For those that still keeps the original path, the following is my update 'howto' for rPi:

1) Backup

/etc/weewx

/usr/share/weewx

2) Download

# wget http://www.weewx.com/downloads/weewx-4.0.0.tar.gz (or other newer, if the case)

# tar zxvf [weewx-xxx.tar.gz]

3) Config

# cd weewx-xxx

# nano setup.cfg

- Edit to install locations
[install]
home = /etc/weewx
prefix =
exec-prefix =
install_lib = /usr/share/weewx
install_scripts = /usr/share/weewx

# ./setup.py build
# ./setup.py install

- copy old files from backup, if necessary (as weewx.conf, extensions.py, or other)
# cp extensions.py - to - /usr/share/weewx/user
# cp [driver].py* - to - /usr/share/weewx/user

# service weewx start
# tail -f /var/log/syslog
# wee_reports

Xant

[gjr80]

Nigel,

A comma can certainly cause a problem, the config file parser will treat the comma in the setting as a delimiter and return two settings. If you want your comma back you should be able to put it back if you enclose the entire setting in quotes, eg:

    [[Text]]
        text = "Real Time Gauges - Local Time is %H:%M, Next gauge update in..."

Gary

[Devonian]

Perfect, thanks Gary.

Keep well and stay safe.

Nigel

[Marius Schamschula]

Hi all,

I'm glad that version 4.0 supports python 3.x, although it is currently installed under python 2.7. The current pyephem broke the extended almanac, and I've held back that python 2.7 package. However, I'm planning to transition to python 3.8, with python 2.7 as fallback.

I'm having an issue with the annual "High Wind" speed value. Although the direction and time are there, the speed is the max speed for the current month (less than the earlier max wind speed event).

FYI: I've got weewx installed under FreeBSD 12.1.

[Tom Keffer]

The current pyephem broke the extended almanac, and I've held back that python 2.7 package. 

Sorry. I don't understand what you mean by "broke the extended almanac."

I'm having an issue with the annual "High Wind" speed value. Although the direction and time are there, the speed is the max speed for the current month (less than the earlier max wind speed event).

How about some details? Do you mean $year.wind.max gives a smaller value than $month.wind.max? Something else? 

What do you mean by "earlier max wind speed event? What was generated by earlier versions of weewx? Something else?

[James Berry]

Not sure if I have stuffed anything up, but I was able to follow just an apt-get update and upgrade to get from 3.9.2 to 4.0.0, continuing to run under python2.

[Marius Schamschula]

On Monday, May 4, 2020 at 4:31:15 PM UTC-5, Tom Keffer wrote:

The current pyephem broke the extended almanac, and I've held back that python 2.7 package. 

 

Sorry. I don't understand what you mean by "broke the extended almanac."

weewx 3.9.2 just ignored the updated Freshports pyephem package and only provided the default information provided by weewx itself, as if pyephem had not been installed. When I went back to the previous version I again had the full almanac output. I have not dared to update pyephem since.

 

I'm having an issue with the annual "High Wind" speed value. Although the direction and time are there, the speed is the max speed for the current month (less than the earlier max wind speed event).

How about some details? Do you mean $year.wind.max gives a smaller value than $month.wind.max? Something else? 

 

What do you mean by "earlier max wind speed event? What was generated by earlier versions of weewx? Something else?

 

Exactly that:  $year.wind.max gives me the same value as $month.wind.max for the current month, even thought there was a higher value recorded in an earlier month (in this case January of this year).

 weewx 3.9.2 gave the correct output.

[re...@eau.net]

I am very cautious and don't want to goof things up (well, too much) so today I make sure the RaspPi4 is running the latest Buster, and updated all the Python 3 files and prerequisites that are listed.

In the Update Guide, there is a red-highlighted admonition that one must use the same update method that was used for initial installation. 

I do not recall how I did it, so I'm reading to see that one comment Tom made to another user implied that if one looked in /etc/weewx for the config file it must have been installed via the DEB package and to use

sudo apt-get update
sudo apt-get install weewx

to update.

I did look in /etc/apt/sources.list.d/weewx.list and it is there.

So can I assume then that I used the DEB process to install initially, and I can relatively comfortably proceed with using
the sudo commands above are the right ones to do my update?


Thanks for the hand holding.  Dale

[Tom Keffer]

Yes, you did use the Debian package installer.

You should be able to just do

sudo apt-get update
sudo apt-get install weewx

If you're concerned about breaking things, make a backup of your database file /var/lib/weewx/weewx.sdb. It's the only thing that's irreplaceable. But, you've been doing that anyway, right? :-)

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

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d3a598a5-73bd-4ad1-a046-1a27d35ec4e8%40googlegroups.com.

[Paul Bartholdi]

Hello,

The move from python2 to python3 is a mess because of the way python is designed and the many incompatibilities between them.

I think what was done by the weewx developer was the right one, even the necessary one. But user need to be careful that just installing python3 does not mean that all libraries/package are updated at the same time.

pyephem is a python package, but not part of the python package. It must be installed independently. 

I had to install (I use mysql/mariadb not sqlite3 as support dB):

     sudo apt install python-mysqldb

     sudo apt install python3-mysqldb

Hope this helps.

Thanks again to the installers!      Paul

[Keimpe Bleeker]

Hi Tom, All,

From December I had Weewx V3 with Belchertown running on the Simulator without any problems. Because of the import of the Wunderground history I have been waiting for the transition from WeatherDisplay & WordPerss to Weewx to V4.

I've been fiddling for days now to get things going; tried upgrading from V3 (/etc/weewx/ ...) to V4, of course with all the Python prerequisites and the setup.py method but without success. I cleaned up the RPi from A to Z and tried the standard installation without any changes in the Setup.cfg but no success. 

Today I made a fresh start with a clean RPi and Weewx installed by default in /home/weewx/. Weewx seems to run well -basic skin, without Belchertown-, but now the utilities don't work: 'sudo / home / weewx / bin / wee_debug verbosity = 1' results in 'sudo: wee_debug: command not found'. This applies to all utillities. I only have one thing left for Weewx: HELP!

One problem with Belchertown is that Cheetah can't find the /home/weewx/var/www/html/weewx/json/darksky_forecast.json and that's right, the file is not there. So also here: HELP!

Thanks in advance for any suggestion.

Regards, Keimpe

After running since Decemwaiting for V4 

Op donderdag 30 april 2020 19:09:47 UTC+2 schreef Tom Keffer:

[Tom Keffer]

Keimpe

Trying to clarify what you tried. You said you tried 'sudo / home / weewx / bin / wee_debug verbosity = 1'  Is that a typo, or did you literally type that? There should not be spaces in there. I should be something like

/home/weewx/bin/wee_debug --verbosity=1

Or, maybe it was just a typo. Let us know.

--

You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/a88221df-a89e-4396-8552-a9fa8ff4956a%40googlegroups.com.

[Keimpe Bleeker]

Sorry, typo... use the command exactly as you mentioned. 

 

Op dinsdag 5 mei 2020 14:02:12 UTC+2 schreef Tom Keffer:

To unsubscribe from this group and stop receiving emails from it, send an email to weewx...@googlegroups.com.

[Tom Keffer]

So, what is in /home/weewx/bin?

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dc055be6-b186-4a6a-9fcd-971bf2459fc6%40googlegroups.com.

[Keimpe Bleeker]

See attached screenshot, all the necessary files and folders, as it appears.

Op dinsdag 5 mei 2020 14:16:42 UTC+2 schreef Tom Keffer:

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/dc055be6-b186-4a6a-9fcd-971bf2459fc6%40googlegroups.com.

[Tom Keffer]

OK. So, you're telling me that running a program /home/weewx/bin/wee_debug, that clearly exists in a directory listing, results in an error "wee_debug not found". That doesn't make sense.

I'd like to see the actual console output. Run the command, then copy and paste from the console output into your post. DO NOT TAKE A SCREENSHOT. Just highlight the resultant text, right click, select "Copy", then paste into your post.

-tk

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d7a9d9d2-8ba9-4559-afcc-6b344e193a83%40googlegroups.com.

[Keimpe Bleeker]

Wee_debug --verbostity=1 results in help-info:

pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --verbosity=1

Usage: wee_debug --help

       wee_debug --info

            [CONFIG_FILE|--config=CONFIG_FILE]

            [--output|--output DEBUG_PATH]

            [--verbosity=0|1|2]

       wee_debug --version

Description:

Generate a standard suite of system/weewx information to aid in remote

debugging. The wee_debug output consists of two parts, the first part containing

a snapshot of relevant system/weewx information and the second part a parsed and

obfuscated copy of weewx.conf. This output can be redirected to file and posted

when seeking assistance via forums or email.

Actions:

--info           Generate a debug report.

Options:

  -h, --help            show this help message and exit

  --config=CONFIG_FILE  Use configuration file CONFIG_FILE.

  --info                Generate weewx debug output.

  --output              Write wee_debug output to DEBUG_PATH. DEBUG_PATH

                        includes path and file name. Default is

                        /var/tmp/weewx.debug.

  --verbosity=N         How much detail to display, 0-2, default=1.

  --version             Display wee_debug version number.

wee_debug will attempt to obfuscate obvious personal/private information in

weewx.conf such as user names, passwords and API keys; however, the user

should thoroughly check the generated output for personal/private information

before posting the information publicly.

pi@Pi4Weewx:/home/weewx $

Or for wee_config ends in:

 

pi@Pi4Weewx:/home/weewx $ pi@Pi4Weewx:/home/weewx $ 

bash: pi@Pi4Weewx:/home/weewx: Bestand of map bestaat niet

pi@Pi4Weewx:/home/weewx $ 

NL > EN: Bestand of map bestaat niet > File or directory doesn't exist)

 

Op dinsdag 5 mei 2020 16:52:09 UTC+2 schreef Tom Keffer:

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/d7a9d9d2-8ba9-4559-afcc-6b344e193a83%40googlegroups.com.

[John Kline]

You are missing the “—info” flag (as shown in the Usage message printed).

Try /home/weewx/bin/wee_debug —info --verbosity=1

On May 5, 2020, at 8:29 AM, Keimpe Bleeker <blee...@xs4all.nl> wrote:



To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/de75e3b5-e031-4036-ace4-845b4e6d4812%40googlegroups.com.

[Tom Keffer]

OK. That looks normal.  There is no "wee_debug not found" error.

You have to give it something to do. You probably want a --info flag

/home/weewx/bin/wee_debug --verbosity=1 --info

Be sure to read the manual!

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/de75e3b5-e031-4036-ace4-845b4e6d4812%40googlegroups.com.

[Tom Keffer]

Oh, one other thing: you said this applies to "all utilities." Example?

-tk

[Keimpe Bleeker]

Thanks, wee_debug is working!

pi@Pi4Weewx:/home/weewx $ /home/weewx/bin/wee_debug --info --verbosity=1

Using verbosity=1, displaying most info

wee_debug output will be sent to stdout(console)

Using configuration file /home/weewx/weewx.conf

Using database binding 'wx_binding', which is bound to database 'archive_sqlite'

System info

  Platform:       Linux-4.19.97-v7l+-armv7l-with-debian-10.3

  Python Version: 3.7.3

Load Information

  1 minute load average:  0.01

  5 minute load average:  0.02

  15 minute load average: 0.00

General Weewx info

  Weewx version 4.0.0 detected.

Station info

  Station type: Simulator

  Driver:       weewx.drivers.simulator

Driver info

[Simulator]

    # This section is for the weewx weather station simulator

   ..... 

But the important wee_config, to change from Simulator to Vantage still says:

pi@Pi4Weewx:/home/weewx $ wee_config --config=/home/weewx/weewx.conf

bash: wee_config: opdracht niet gevonden

pi@Pi4Weewx:/home/weewx $ 

Op dinsdag 5 mei 2020 17:41:44 UTC+2 schreef Tom Keffer:

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/de75e3b5-e031-4036-ace4-845b4e6d4812%40googlegroups.com.

[gjr80]

With a setup.py install you need to include the path to the utilities unless you happen to be in the /home/weewx/bin directory (which in this case you are not). wee_debug worked because you included the path, with wee_device you did not. Use /home/weewx/bin/wee_device and it will work.

Gary

[Tom Keffer]

Keimpe, please see the Wiki article Understanding paths.

To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/eb152ae8-3f64-4ed0-8a74-08646438f861%40googlegroups.com.

[Clay Croom]

Thank you Tom for all the work on this project.  Just wanted to let you know that my upgrade went just fine but I took what felt to me as the safe route to upgrade to Python3.  I elected to purge the 3.9 installation keeping the data file.  I updated the repository for python3 as instructed and then did a new install.  I made a printed copy of my config file and followed the prompts creating a new config file since this was a major upgrade.  It started and ran just fine without a hick-up.  Once running normally I edited the config file to my previous settings.  Sometimes simple is good.  Took about 10 minutes.  Thanks, again.  Clay

ps.  I had backup copies of the important files.

[Keimpe Bleeker]

Hi Tom, many thanks for the tips and hints, everything is very much OK now! Just one minor issue for which I don't know if that comes from Weex or the Belchertown skin: the date / time of receiving the latest data is a mess. I'll ask Pat about that too. (http://oentsjerk.eu/)

Op dinsdag 5 mei 2020 23:25:09 UTC+2 schreef Tom Keffer:

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/eb152ae8-3f64-4ed0-8a74-08646438f861%40googlegroups.com.