[weewx-user] Re: Availability of v5.0.0rc3

2024-01-13 Thread WindnFog
Works well: https://ve1dx.net/ Is it worth mentioning in the documentation that if you delete your virtual environment, you also delete any python3 modules specific to your setup? In my case, I needed to reinstall 'dateutils' and 'pysftp'. This was intuitive when I saw the errors, but maybe

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-12 Thread matthew wall
On Friday, January 12, 2024 at 7:53:24 PM UTC-5 sab...@gmail.com wrote: After some troubleshooting, I found the acurite idVendor code has a typo. Once I changed this the string to "24c0" instead of 24C0", I was able to get the permissions working and all was good. nice catch! fixed at

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-12 Thread sab...@gmail.com
I just tried a new install of 5.0RC3 on a RPi4 using the latest released Rasbian lite and used the PIP install for weewx. The install process was pretty smooth, but I did hit a small snag with the udev file assigning the permissions for my acurite console. Despite multiple attempts to

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-10 Thread 'michael.k...@gmx.at' via weewx-user
Thanks! Patched the file, it's working again. Tom Keffer schrieb am Mittwoch, 10. Januar 2024 um 15:23:11 UTC+1: > Michael, > > I've reverted the StdCalibrate behavior back to the way it was in V4.10. > To appear in the next V5 release. > > On Tue, Jan 9, 2024 at 8:43 PM 'michael.k...@gmx.at'

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-10 Thread Tom Keffer
Michael, I've reverted the StdCalibrate behavior back to the way it was in V4.10. To appear in the next V5 release. On Tue, Jan 9, 2024 at 8:43 PM 'michael.k...@gmx.at' via weewx-user < weewx-user@googlegroups.com> wrote: > It looks very much like it's the loop in my case. For instance, >

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-09 Thread 'michael.k...@gmx.at' via weewx-user
It looks very much like it's the loop in my case. For instance, extraHumid1 is coming from a different device using the mqttSubscribe Service. So it is not in the loop packet from ws28xx. The same with supplyVoltage, BTW I messed up the ws28xx stanza, this one is correct, failing on both,

Re: [weewx-user] Re: Availability of v5.0.0rc3

2024-01-09 Thread Tom Keffer
Michael, I think the issue is that extraHumid1 and/or lightning_strike_count do not appear *at all* in at least some of the loop packers and/or archive records. Version 4.10 swallowed NameErrors, this one does not. Perhaps that's a mistake. Let me think if there's a better solution. -tk On Tue,

[weewx-user] Re: Availability of v5.0.0rc3

2024-01-09 Thread 'michael.k...@gmx.at' via weewx-user
I did a pip upgrade from b13 (no new install, no new venv). I run 3 drivers: ws28xx, interceptor and ecowitt gateway driver from the same installations, using 3 different weewx.conf files and three databases After upgrading, two installations are crashing, when having certain corrections

[weewx-user] Re: Availability of v5.0.0rc3

2024-01-09 Thread 'michael.k...@gmx.at' via weewx-user
I did a pip upgrade. I run 3 drivers: ws28xx, interceptor and ecowitt gateway driver from the same installations, using 3 different weewx.conf files and three databases After upgrading, two installations are crashing, when having certain corrections configured. Interestingly, one station