I installed weewx using the pip method and followed the instructions. I did a pip list before installing to get the list of what other dependencies I am using. When I installed paho-mqtt and pyephem I got these errors:
Installing collected packages: paho-mqtt DEPRECATION: paho-mqtt is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559 Running setup.py install for paho-mqtt ... done Successfully installed paho-mqtt-1.6.1 /opt/weewx$ python3 -m pip install pyephem Collecting pyephem Using cached pyephem-9.99.tar.gz (1.4 kB) Preparing metadata (setup.py) ... done Requirement already satisfied: ephem in ./weewx-venv/lib/python3.11/site-packages (from pyephem) (4.1.5) Installing collected packages: pyephem DEPRECATION: pyephem is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559 I am currently running it in simulation mode just to see what happens. On my real system I have installed all my environment and data under /opt eg /opt/weewx/weewx-venv and /opt/weewx/weewx-data Other than that it seems to run. My question is should I run the install of those packages above that had the error with the --use-pep517 option? I read the github information that was on the link contained in the error message but it made no sense to me. My pip version is: 3.11 On Friday 22 December 2023 at 17:05:49 UTC+11 Hartmut Schweidler wrote: > Guten Morgen, > > Zunächst einmal vielen Dank an alle, die an der Entwicklung von weewx V5 > beteiligt waren! > > Mein Installation erfolgte per "apt upgrade". auf einem Banana Pi + 1TB HDD > > Die folgenden Pakete werden aktualisiert (Upgrade): > weewx > 1 aktualisiert, 0 neu installiert, 0 zu entfernen und 2 nicht aktualisiert. > Es müssen 2.278 kB an Archiven heruntergeladen werden. > Nach dieser Operation werden 2.048 B Plattenplatz zusätzlich benutzt. > Holen:1 https://weewx.com/apt-test/python3 buster/main all weewx all > 5.0.0rc1-1 [2.278 kB] > Es wurden 2.278 kB in 2 s geholt (948 kB/s). > Preconfiguring packages ... > (Lese Datenbank ... 75361 Dateien und Verzeichnisse sind derzeit > installiert.) > Vorbereitung zum Entpacken von .../weewx_5.0.0rc1-1_all.deb ... > Entpacken von weewx (5.0.0rc1-1) über (5.0.0b17-4) ... > weewx (5.0.0rc1-1) wird eingerichtet ... > Neue Version der Konfigurationsdatei /etc/weewx/skins/Ftp/skin.conf wird > installiert ... > Neue Version der Konfigurationsdatei /etc/weewx/skins/Mobile/skin.conf > wird installiert ... > Neue Version der Konfigurationsdatei /etc/weewx/skins/Rsync/skin.conf wird > installiert ... > > Konfigurationsdatei »/etc/weewx/skins/Seasons/skin.conf« > ==> Geändert (von Ihnen oder von einem Skript) seit der Installation. > ==> Paketverteiler hat eine aktualisierte Version herausgegeben. > Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind: > Y oder I : Die Version des Paket-Betreuers installieren > N oder O : Die momentan installierte Version beibehalten > D : Die Unterschiede zwischen den Versionen anzeigen > Z : Eine Shell starten, um die Situation zu begutachten > Der Standardweg ist das Beibehalten der momentanen Version. > *** skin.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? n > ... > Neue Version der Konfigurationsdatei /etc/weewx/weewx.conf.dist wird > installiert ... > Copying previous config file to /etc/weewx/weewx.conf-5.0.0b18-5.0.0rc1 > Saving distribution config file as /etc/weewx/weewx.conf-5.0.0rc1 > Creating maintainer config as /etc/weewx/weewx.conf-5.0.0b18-5.0.0rc1 > Using configuration file /etc/weewx/weewx.conf-5.0.0b18-5.0.0rc1 > Finished upgrading configuration file > /etc/weewx/weewx.conf-5.0.0b18-5.0.0rc1 > Saving configuration file /etc/weewx/weewx.conf-5.0.0b18-5.0.0rc1 > Created symlink /etc/systemd/system/multi-user.target.wants/weewx.service > → /lib/systemd/system/weewx.service. > > root@ba002:/etc/weewx# systemctl restart weewx@weewx > Warning: The unit file, source configuration file or drop-ins of > [email protected] changed on disk. Run 'systemctl daemon-reload' to > reload units. > root@ba002:/etc/weewx# systemctl daemon-reload > root@ba002:/etc/weewx# systemctl restart weewx@weewx > root@ba002:/etc/weewx# systemctl restart weewx@weeusb > > Meine Anpassungen: > Anpassungen nur in [email protected] > > " > # systemd service template file for running multiple instances of weewxd > # > # Each instance XXX must have its own config, database, and HTML_ROOT: > # > # item name where to specify > # -------- ----------------------------- > ---------------------------- > # config /etc/weewx/XXX.conf configuration directory > # database_name /var/lib/weewx/XXX.sdb specified in XXX.conf > # HTML_ROOT /var/www/html/XXX specified in XXX.conf > > [Unit] > Description=WeeWX %i > Documentation=https://weewx.com/docs > Requires=time-sync.target > After=time-sync.target > PartOf=weewx.service > > [Service] > ExecStart=weewxd --log-label weewx5-%i /etc/weewx/%i.conf > StandardOutput=null > StandardError=journal+console > #User=weewx > #Group=weewx > > [Install] > WantedBy=multi-user.target > > " > > Es läuft hervorragend. > > 2023-12-22T07:00:24.155271+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.manager: Added record 2023-12-22 07:00:24 CET (1703224824) to > database 'weewxDavis' > 2023-12-22T07:00:24.393038+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.manager: Added record 2023-12-22 07:00:24 CET (1703224824) to daily > summary in 'weewxDavis' > 2023-12-22T07:00:25.032855+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.manager: Added record 2023-12-22 07:00:00 CET (1703224800) to > database 'weewxGW2000' > 2023-12-22T07:00:25.642882+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.manager: Added record 2023-12-22 07:00:00 CET (1703224800) to daily > summary in 'weewxGW2000' > 2023-12-22T07:00:34.314116+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.cheetahgenerator: Generated 9 files for report SeasonsReport in 8.51 > seconds > 2023-12-22T07:00:45.239521+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.imagegenerator: Generated 24 images for report SeasonsReport in 10.92 > seconds > 2023-12-22T07:00:45.241651+01:00 ba002 weewx5-weewx[5037]: INFO > weewx.reportengine: Copied 0 files to /var/www/html/weewx > 2023-12-22T07:00:48.646048+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.drivers.fousb: synchronising to the weather station (quality=1) > 2023-12-22T07:01:34.532773+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.manager: Added record 2023-12-22 06:57:00 CET (1703224620) to > database 'weewx.sdb' > 2023-12-22T07:01:34.687560+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.manager: Added record 2023-12-22 06:57:00 CET (1703224620) to daily > summary in 'weewx.sdb' > 2023-12-22T07:01:41.011145+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.cheetahgenerator: Generated 8 files for report StandardReport in 5.96 > seconds > 2023-12-22T07:01:43.778354+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.imagegenerator: Generated 13 images for report StandardReport in 2.76 > seconds > 2023-12-22T07:01:43.784111+01:00 ba002 weewx5-weeusb[4799]: INFO > weewx.reportengine: Copied 0 files to /var/www/html/weewx/wx2013 > > Noch einmal Danke und ein gesundes Weihnachtsfest, verbunden mit einem > Guten Rutsch in Jahr 2024 > > Hartmut > Al Barnes schrieb am Freitag, 22. Dezember 2023 um 06:46:58 UTC+1: > >> First off, many thanks to all involved in developing weewx V5! After >> reading the git logs for the past few months I can see that this has >> taken a ton of time and effort. >> >> I've finished a pip install and here are my findings. >> >> I'm running Raspberry Pi OS (Debian Bookworm) on a pi 3b that has been >> used for testing of the alpha versions of weewx. The station is a >> Vantage Pro2 with the official Davis logger. >> >> After deleting weewx-data and weewx-venv and a weewx.service file in >> /etc I followed the instructions at >> https://weewx.com/docs/5.0/quickstarts/pip/ and everything went as >> expected. I created the station with 'weectl station create'. The >> command 'sudo sh ~/weewx-data/scripts/setup-daemon.systemd' set up >> systemd logging. >> >> After this point I made no changes whatsoever to weewx.conf as I wanted >> to see how it would run with the default settings. Before starting >> weewx, I ran 'journalctl -f -u weewx in another terminal and first >> received a message that I've never seen before: >> >> /etc/systemd/system/weewx.service:15: Standard output type >> syslog+console is obsolete, automatically updating to journal+console. >> Please update your unit file, and consider removing the setting >> altogether. >> >> After starting weewx the logging was normal. >> >> As I had not copied over my old database, weewx faithfully starting >> downloading records from the Vantage Pro2 starting with 2023-12-12 >> 22:35:00 PST. >> >> It can take quite a while to download almost 9 days of data from the >> logger, and here is where I ran in to a serious problem. The downloading >> of records stopped at 2023-12-21 19:50:00 when the actual time was >> 20:38:44. At this point the next line in the logs was 'Starting main >> packet loop.' >> Shortly thereafter it added records at 20:38:00 and 20:40:00, so we are >> now missing all records from 19:50 through 20:35. >> A minute later I received the dreaded 'Expected to read 99 chars; got 0 >> instead' message, followed by 'Main loop exiting. Shutting engine down'. >> >> Weewx restarted on it's own and seems to be downloading a new archive >> record every five minutes, but of course we still have the problem of >> the missing records. I had the same problem in early version 5 alpha >> releases when weewx was downloading many records and couldn't complete >> everything within the five minute cycle. Not a problem if you are >> copying over your old database as you are most likely only downloading >> an hour or two of records from the logger, but this could bite someone >> who's station has been down for a long time due to a power outage or >> whatever. I've attached the log file so that you can see the details. >> >> Anyhow, hopefully this is helpful and thanks again for all of the hard >> work that has been done to come up with a new version of weewx! >> >> Al > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/3f813b17-0b9b-49b4-b9af-97dcd0a4f69bn%40googlegroups.com.
