[weewx-user] Re: successful update to weewx 5.0.1 for driver WH23xx

Hi Michael, Is it possible to give more information about gpg key update and further on? Up to now, i run wh2310 meteo station only with 3.9.2 version. I tried 5.0, it worked for few minutes and after crashed. Thank you in advance. Kostas Στις Πέμπτη 8 Φεβρουαρίου 2024 στις 6:37:54 μ.μ.

[weewx-user] Re: successful update to weewx 5.0.1 for driver WH23xx

Kostas - if you post your logs when 5.0 crashed it is likely somebody can help you. Make sure to set debug=1 in weewx.conf On Tuesday, February 20, 2024 at 7:05:14 AM UTC-8 kostas costas wrote: > Hi Michael, > > Is it possible to give more information about gpg key update and further > on?

[weewx-user] Can no longer run a command with weewx v5

I am trying to use *sudo PYTHONPATH=/usr/share/weewx python /usr/share/weewx/user/sdr.py cmd="rtl_433 -M utc -F json"* to get the the full names of a sensors. When I run the line I get this *error python: can't open file '/usr/share/weewx/user/sdr.py': [Errno 2] No such file or directory*

Re: [weewx-user] Can no longer run a command with weewx v5

See the Upgrade Guide, in particular, the section *New location for user directory *. On Tue, Feb 20, 2024 at 12:29 PM Harley Welsh wrote: > I am trying to use *sudo PYTHONPATH=/usr/share/weewx python >

[weewx-user] Re: Catastrophic apt upgrade to V5.02 on Raspberry Pi

Well FWIW the error appears to be for the optional crt extension so I’d perhaps try disabling that and seeing if core weewx is ok. As always set debug=1 and provide logs from weewx startup through two archive periods. You could also try reinstalling the crt extension. Back your /etc/weewx

Re: [weewx-user] Weewx v5 fresh install Errno 13

Good it’s working. Weewx used to run as root so a lot of permission problems didn’t happen previously. With the switch to running as a unprivileged user, you need to ensure that user can attach to peripherals (your case) or listening ports (some interceptor and sdr users) as well as hook it

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

https://weewx.com/docs/5.0/usersguide/troubleshooting/what-to-do/ 1. Look at the log file . We are always happy to take questions, but the first thing someone will ask is, "What did you find in the log file?" On

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

That's the end of the log? Where is the crt error? The record timestamped 2024-02-20 20:30:00 was downloaded from the logger at 20:32:22. I would expect the next record to be processed at 20:35:16 or so. Did you terminate the program? Is there something later in the log? On Tue, Feb 20, 2024 at

Re: [weewx-user] Weewx v5 fresh install Errno 13

Hi Vince, et al, Yes, all working well. I was looking at it, from a device permissions point-of-view. Software weewx, for some reason, no-longer had rights to, in my case /dev/ttyUSB0 (which has been working for 11 years). Ownership of the device were set to root:dialout (as are the serial

[weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

I have had weewx 4.x (apt installed) running happily on my Pi 3b for years. A month ago, since 5.0 seemed to be stable, I allowed the upgrade to the then current release of 5.0. Since there had been a few concerns raised about it, I did a complete image backup of the Pi before allowing the

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

The "AttributeError" problem is a known problem with crt. See this thread . But, it is not the actual problem --- it's just a reporting problem. For the actual problem, we will need to see more of the log. On Tue, Feb 20, 2024

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

Here is the log from before I applied the apt update, through now. This includes one reboot. The last start was after setting debug=1 in the config file. I hope that it helps you more than it does me!: Feb 20 18:20:19 bullseyepi weewxd[447]: INFO weewx.cheetahgenerator: Generated 7 files for

Re: [weewx-user] Catastrophic apt upgrade to V5.02 on Raspberry Pi

That is the entire log from shortly before the update. I am guessing that the known bug in crt.py results in the crash not being properly reported. The good news is that I was able to figure out what was going on. I am using crt to produce a file that allows the display of current weather