[weewx-user] Your hardware experience (for running WeeWX, the service)

['michael.k...@gmx.at' via weewx-user]

I'm curious what hardware you are running WeeWX on, and your experience 
with it. So, this is not about the weather station and the sensors, but the 
device which is running the service. The reason I ask this here, is because 
the issues I experienced with my hardware might be related to weewx and 
writing it's logs, and we all know the first rule for posting a question 
here :D

Since my first WeeWX installation in 2015, I've been using every generation 
of the RaspberryPi B, except for the 5th. But looking back it, has 
sometimes has been a royal PITA. It's not that I consider the Pi being bad 
at all, but I've been having issues with whatever storage I've been using. 
SD-Cards were a total disaster, USB flash drives were slightly better, USB 
attached SSDs, at least, lasted more than two years before being attached 
to the Pi killed them. The only type that didn't fail so far, was a NFS 
provided by a QNAP NAS, but this Kind of setup is a bit complex to 
maintain, and starting the NAS over, means quite a bit of downtime for the 
Pi also.

The Pi never was intended to be a server running 24/7, considering this, 
it's success in being used as such, is beyond imagination. Anyway, my 
experience for the Pi being a storage killer, doesn't seem to be uncommon. 
It's original intention was satisfied: I learned a lot about how not to 
lose data with unreliable hardware. Since 2015, my database isn't missing 
more than one archive value a day in average and the longest gap is about 
two hours back in early 2016, using the standard interval of 5 minutes.

What hardware are you using, what is your experience?
Can you suggest hardware with low power consumption as a requirement?
What about the newest generation, like Intel n100 based systems? 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/69220248-dd7a-4e8a-a7bb-f3251017e0f5n%40googlegroups.com.

Re: [weewx-user] updated to 5.0.1 still no joy

[vince]

You're going to need to share your weewx.conf file for this one.
You have to be referencing gpio stuff somewhere under the hood.

Running 'weectl extension list' would help explain your setup too

On Thursday, February 22, 2024 at 2:18:28 AM UTC-8 Glen N wrote:

> After updating DietPi to version 9.1.1
>
> I am getting GPIOzero BadPinFactory errors again. I tried commenting out 
> the weewx user in the service file as above, but the error remains.
>
> ● weewx.service - WeeWX
>
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Thu 2024-02-22 21:02:32 
> AEDT; 12min ago
>Docs: https://weewx.com/docs
>Main PID: 23495 (code=exited, status=1/FAILURE)
> CPU: 1.834s
>
> Feb 22 21:02:32 NapsberryPi weewxd[23495]:   File 
> "/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in 
> _default_pin_factory
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: raise BadPinFactory('Unable 
> to load any default pin factory!')
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: gpiozero.exc.BadPinFactory: 
> Unable to load any default pin factory!
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:    
>  File "/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in 
> _default_pin_factory
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
>  raise BadPinFactory('Unable to load any default pin factory!')
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
>  gpiozero.exc.BadPinFactory: Unable to load any default pin factory!
> Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
>  Exiting.
> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Main process 
> exited, code=exited, status=1/FAILURE
> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
> Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Consumed 1.834s CPU 
> time.
>
> On Monday 12 February 2024 at 1:01:24 pm UTC+11 Glen N wrote:
>
>> I was having a no start problem after upgrading RPi3B running DietPi. I 
>> tried Tom's suggestion and it fixed the problem.
>>
>> Prior to the "fix" my log file showed:
>> -- Journal begins at Mon 2024-02-12 11:47:21 AEDT, ends at Mon 2024-02-12 
>> 12:40:34 AEDT. --
>> Feb 12 11:47:23 SystemName systemd[1]: Started WeeWX.
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Initializing 
>> weewxd version 5.0.1
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Using Python 3.9.2 
>> (default, Feb 28 2021, 17:03:44)
>>  [GCC 10.2.1 20210110]
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Platform 
>> Linux-6.1.21-v8+-aarch64-with-glibc2.31
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Locale: 
>> 'en_AU.UTF-8'
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Configuration 
>> file: /etc/weewx/weewx.conf
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Debug: 0
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.engine: Loading 
>> station type FineOffsetUSB (weewx.drivers.fousb)
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: driver 
>> version is 1.3
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: polling 
>> mode is PERIODIC
>> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: polling 
>> interval is 60
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.drivers.fousb: found 
>> station on USB bus= device=
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: StdConvert 
>> target unit is 0x11
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Record 
>> generation will be attempted in 'software'
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Using archive 
>> interval of 300 seconds (software record generation)
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: 
>> StationRegistry: Station will not be registered: no station_url specified.
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: 
>> Wunderground-PWS: Data for station ITEATR7 will be posted
>> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: PWSWeather: 
>> Data for station THISTLEWIND 

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

['Peter Fletcher' via weewx-user]

I'm not ignoring you, but today has been a bit busy! I will try to write 
something up and post it later today or tomorrow.

On Wednesday, February 21, 2024 at 7:13:08 PM UTC-5 matthew wall wrote:

> On Wednesday, February 21, 2024 at 6:50:52 PM UTC-5 Peter Fletcher wrote:
>
> There were essentially no issues with the 4.x->5.x update. What I wasn't 
> prepared for was an update *from 5.01 to 5.02* clobbering everything *that 
> was previously working in 5.01*. I don't think that it is reasonable to 
> expect the user to carefully (re-)read all the documentation before 
> doing/allowing a 'second decimal place' update.
>
>
> peter, it would be helpful if you could describe a bit more about your 
> configuration. 
>
> are you running with hardware that required separate installation (e.g., 
> sdr) or hardware drivers or kernel modules?
>
> are you running multiple instances of weewd?
>
> are your reports all within a single directory tree, or are they scattered?
>
> did you implement the various report locations using symlinks, or is it 
> all explicitly declared within your weewx config file?
>
> did you have any issues with weewx integration to a local web server?  if 
> so, how did you configure that?
>
> do you have ssh or other configurations for remote access that were 
> affected by the permissions changes?  where are those located, and how are 
> they used?
>
> i'm working on a handful of adjustments to the deb/rpm packaging that will 
> hopefully avoid some of the issues you ran into.  so description of systems 
> that are more extensive than just 'apt install' are very helpful.  in 
> hindsight, we probably should have done the root-to-weewx change in the 
> 5.0.0 release, not a dot-dot.  it was not until 5.0 went out that we 
> realized how many *more* issues there would be if some people end up with 
> weewx running as root while others run unprivileged.
>
> apologies for the disruption it caused.
>
> m
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/616a09d1-cd56-4796-901e-21ff9e25ab54n%40googlegroups.com.

Re: [weewx-user] How to upgrade from setup.py v4 install to pip v5 install

[vince]

gary - your (re)install upgrade will be quicker if you pre-seed your NOAA 
files (Belchertown has its own copy too if you use that).  Feel free to PM 
me if you want to hear my somewhat different way of getting from v4 setup 
to v5 pip (and multi).

On Thursday, February 22, 2024 at 6:28:15 AM UTC-8 gary@gmail.com wrote:

> Thanks for the options.
>
> I don't want to have a "hybrid" so won't be following the migration guide 
> method.
> Makes more sense to me to install new, install extensions and skins, edit 
> in my config from the existing (old) weewx.conf, copy the database over, 
> remove the old systemd service file, add the new systemd service, move the 
> old install to weewx.old, run the new.
>
> May be a tiny bit more effort but then should be easier for me to 
> maintain/update in the future.
>
>
>
> On Wednesday, February 21, 2024 at 11:07:46 AM UTC-5 Tom Keffer wrote:
>
>> Oh, I thought we were talking about upgrading from an alpha version of v5.
>>
>> Not much difference. Just set up a V5 virtual environment, then point it 
>> at /home/weewx. Follow the directions in the migration guide 
>> . 
>>
>> On Wed, Feb 21, 2024 at 7:44 AM gary@gmail.com  
>> wrote:
>>
>>> I understand coming from v5 that would be a way.
>>> I need to upgrade my v4 setup.py to v5 though.
>>>
>>>
>>> On Wednesday, February 21, 2024 at 10:39:47 AM UTC-5 Tom Keffer wrote:
>>>
>>> The pip installs are super easy to back up. Just copy ~/weewx-venv and 
>>> ~/weewx-data and you have everything you need.
>>>
>>> Then activate the virtual environment, then "pip install weewx 
>>> --upgrade". It should be that easy. If something fails, just roll things 
>>> back.
>>>
>>> On Wed, Feb 21, 2024 at 7:15 AM gary@gmail.com  
>>> wrote:
>>>
>>> I've had a test install of v5 since early alphas. Now, it is time to 
>>> upgrade my production install.
>>> I have a relatively simple install, Vantage Pro IP driver, weewx-mqtt. A 
>>> couple of additional internet uploaders (Windy and WeatherCloud). I run two 
>>> skins, Belchertown and weewx-wdc
>>>
>>> All is and has been quite stable. So, I hesitate to poke at it. But, v5 
>>> is the new standard, so I need to get this done.
>>>
>>> I don't see many who have trod this path. How to go about this?
>>>
>>> -- 
>>> 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/b2d73a89-3432-4ad4-8971-34ea51167f24n%40googlegroups.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/68e9b77e-5d25-492f-bfa5-448ac39b8cedn%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a037642a-ef0c-4f86-9bd0-f3547ca314bfn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[vince]

Jamie - I didn't change anything related to how the driver actually works. 
 I just added one line to hopefully get it to register vs. v5 weewx.  The 
map shows a few v5 sites using that driver now, so that part seems to be 
working.

On Thursday, February 22, 2024 at 7:24:23 AM UTC-8 Jamie Stephens wrote:

> Thanks Tom, this is the new updated driver that Vince got pushed on this 
> thread. maybe it was a one off 
>
> On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:
>
>> It looks like the author of the driver is trying to insert a string into 
>> a byte array. You should file an issue on the repository's issue list.
>>
>> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
>> wrote:
>>
>>> i manually restarted it and it's running right now just the registry 
>>> push error but not exited 
>>> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
>>> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>>>
>>> will report back if weewx crashes again
>>>
>>> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>>>
 Thanks for the fix, I didn't;t even noticed it was not working

 On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:

> Thank you for resolving the error message.
>
> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com <
> bell...@gmail.com>:
>
>> Thanks for pushing it over the goal line. Always the hardest part.
>>
>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>
>>> Update - the upstream author was nice enough to merge my PR for this 
>>> problem, so you can simply upgrade your driver to the latest version 
>>> and 
>>> your station registration should work again with weewx v5.
>>>
>>> weectl extension install 
>>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>>> sudo systemctl restart weewx
>>>
>>> After upgrading your driver you should see the following output from 
>>> 'weectl extension list':
>>>
>>> Extension NameVersion   Description
>>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
>>> UDP broadcast packets
>>>
>>> Thanks again Rich for the nudge(s) !!!
>>>
>>> -- 
>> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.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/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/cb6767a8-1305-4acf-a440-88ba583b39afn%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

Thanks Tom, this is the new updated driver that Vince got pushed on this 
thread. maybe it was a one off 

On Thursday, February 22, 2024 at 10:07:45 AM UTC-5 Tom Keffer wrote:

> It looks like the author of the driver is trying to insert a string into a 
> byte array. You should file an issue on the repository's issue list.
>
> On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens  
> wrote:
>
>> i manually restarted it and it's running right now just the registry push 
>> error but not exited 
>> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
>> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>>
>> will report back if weewx crashes again
>>
>> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>>
>>> Thanks for the fix, I didn't;t even noticed it was not working
>>>
>>> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>>>
 Thank you for resolving the error message.

 Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com >>> >:

> Thanks for pushing it over the goal line. Always the hardest part.
>
> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>
>> Update - the upstream author was nice enough to merge my PR for this 
>> problem, so you can simply upgrade your driver to the latest version and 
>> your station registration should work again with weewx v5.
>>
>> weectl extension install 
>> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
>> sudo systemctl restart weewx
>>
>> After upgrading your driver you should see the following output from 
>> 'weectl extension list':
>>
>> Extension NameVersion   Description
>> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
>> UDP broadcast packets
>>
>> Thanks again Rich for the nudge(s) !!!
>>
>> -- 
> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.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/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/79ece3db-b456-4744-b354-301c7e75023cn%40googlegroups.com.

Re: [weewx-user] How to upgrade from setup.py v4 install to pip v5 install

[Tom Keffer]

There's nothing special about /home/weewx. You could do

*cp -rp /home/weewx ~/weewx-data*
*cd ~/weewx-data*
*mv bin bin.old*
*mkdir bin*
*cp -r ./bin.old/user bin *


You'll have to adjust your systemd service file to reflect the new location.

-tk

On Thu, Feb 22, 2024 at 6:28 AM gary@gmail.com 
wrote:

> Thanks for the options.
>
> I don't want to have a "hybrid" so won't be following the migration guide
> method.
> Makes more sense to me to install new, install extensions and skins, edit
> in my config from the existing (old) weewx.conf, copy the database over,
> remove the old systemd service file, add the new systemd service, move the
> old install to weewx.old, run the new.
>
> May be a tiny bit more effort but then should be easier for me to
> maintain/update in the future.
>
>
>
> On Wednesday, February 21, 2024 at 11:07:46 AM UTC-5 Tom Keffer wrote:
>
>> Oh, I thought we were talking about upgrading from an alpha version of v5.
>>
>> Not much difference. Just set up a V5 virtual environment, then point it
>> at /home/weewx. Follow the directions in the migration guide
>> .
>>
>> On Wed, Feb 21, 2024 at 7:44 AM gary@gmail.com 
>> wrote:
>>
>>> I understand coming from v5 that would be a way.
>>> I need to upgrade my v4 setup.py to v5 though.
>>>
>>>
>>> On Wednesday, February 21, 2024 at 10:39:47 AM UTC-5 Tom Keffer wrote:
>>>
>>> The pip installs are super easy to back up. Just copy ~/weewx-venv and
>>> ~/weewx-data and you have everything you need.
>>>
>>> Then activate the virtual environment, then "pip install weewx
>>> --upgrade". It should be that easy. If something fails, just roll things
>>> back.
>>>
>>> On Wed, Feb 21, 2024 at 7:15 AM gary@gmail.com 
>>> wrote:
>>>
>>> I've had a test install of v5 since early alphas. Now, it is time to
>>> upgrade my production install.
>>> I have a relatively simple install, Vantage Pro IP driver, weewx-mqtt. A
>>> couple of additional internet uploaders (Windy and WeatherCloud). I run two
>>> skins, Belchertown and weewx-wdc
>>>
>>> All is and has been quite stable. So, I hesitate to poke at it. But, v5
>>> is the new standard, so I need to get this done.
>>>
>>> I don't see many who have trod this path. How to go about this?
>>>
>>> --
>>> 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/b2d73a89-3432-4ad4-8971-34ea51167f24n%40googlegroups.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/68e9b77e-5d25-492f-bfa5-448ac39b8cedn%40googlegroups.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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/fbb6b339-9284-4e54-a97b-85d99d787a61n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEAPDVs_e9_vy97Ca9gHSFqprOZsUbNQaXokidn%3DHE8DwA%40mail.gmail.com.

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

Ok Jeff nice. Sure, it couldn't work with a bad i2c address ;-)

PY

Le jeudi 22 février 2024 à 16:01:08 UTC+1, Pierre-Yves a écrit :

>
> I read this on your log: OSError: "[Errno 121] Remote I/O error"...
>
> Prior installing the BME280 extension, I installed the AS3935 one and I had 
> also to add gpio to weewx group to make my AS3935 lightining detector 
> working.
>
> Maybe try this: "sudo usermod -a -G gpio weewx"
>
> Pierre-Yves
>
>
>
>
>
>
> Le jeudi 22 février 2024 à 14:41:09 UTC+1, Jeff Chabot a écrit :
>
>> Hi Pierre-Yves,
>>
>> Thanks for the suggestion, I just ran that command, uninstalled the 
>> extension and reinstalled it.  Unfortunately, either it didn't help or I am 
>> seeing new issues.  Here are the new errors I am seeing when installing the 
>> bme280wx-master.zip extension:
>>
>> 2024-02-22T08:24:09.936591-05:00 raspberrypi weewxd[861]: Exception in 
>> thread stdout-thread:
>> 2024-02-22T08:24:09.937508-05:00 raspberrypi weewxd[861]: Traceback (most 
>> recent call last):
>> 2024-02-22T08:24:09.937920-05:00 raspberrypi weewxd[861]:   File 
>> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
>> 2024-02-22T08:24:09.939853-05:00 raspberrypi weewxd[861]: self.run()
>> 2024-02-22T08:24:09.940435-05:00 raspberrypi weewxd[861]:   File 
>> "/etc/weewx/bin/user/sdr.py", line 198, in run
>> 2024-02-22T08:24:09.940815-05:00 raspberrypi weewxd[861]: Exception in 
>> thread stderr-thread:
>> 2024-02-22T08:24:09.941172-05:00 raspberrypi weewxd[861]: Traceback (most 
>> recent call last):
>> 2024-02-22T08:24:09.941502-05:00 raspberrypi weewxd[861]:   File 
>> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
>> 2024-02-22T08:24:09.942416-05:00 raspberrypi weewxd[861]: for line in 
>> iter(self._fd.readline, ''):
>> 2024-02-22T08:24:09.943319-05:00 raspberrypi weewxd[861]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> 2024-02-22T08:24:09.944357-05:00 raspberrypi weewxd[861]: self.run()
>> 2024-02-22T08:24:09.945285-05:00 raspberrypi weewxd[861]:   File 
>> "/etc/weewx/bin/user/sdr.py", line 198, in run
>> 2024-02-22T08:24:09.946172-05:00 raspberrypi weewxd[861]: for line in 
>> iter(self._fd.readline, ''):
>> 2024-02-22T08:24:09.946998-05:00 raspberrypi weewxd[861]: ValueError: 
>> PyMemoryView_FromBuffer(): info->buf must not be NULL
>> 2024-02-22T08:24:09.947862-05:00 raspberrypi weewxd[861]: INFO user.sdr: 
>> shutdown complete
>> 2024-02-22T08:24:09.948348-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: Caught OSError: [Errno 121] Remote I/O error
>> 2024-02-22T08:24:09.952604-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   Traceback (most recent call last):
>> 2024-02-22T08:24:09.953116-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewxd.py", line 160, in main
>> 2024-02-22T08:24:09.953514-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   engine = weewx.engine.StdEngine(config_dict)
>> 2024-02-22T08:24:09.953891-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    ^^^
>> 2024-02-22T08:24:09.954261-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewx/engine.py", line 89, in 
>> __init__
>> 2024-02-22T08:24:09.954633-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   self.loadServices(config_dict)
>> 2024-02-22T08:24:09.955000-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/usr/share/weewx/weewx/engine.py", line 157, in 
>> loadServices
>> 2024-02-22T08:24:09.955366-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   obj = weeutil.weeutil.get_object(svc)(self, 
>> config_dict)
>> 2024-02-22T08:24:09.955737-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    
>>  ^^
>> 2024-02-22T08:24:09.956185-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File "/etc/weewx/bin/user/bme280wx.py", line 61, in 
>> __init__
>> 2024-02-22T08:24:09.956573-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   self.calibration_params = 
>> bme280.load_calibration_params(self.bus, self.address)
>> 2024-02-22T08:24:09.956997-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    
>>  ^^
>> 2024-02-22T08:24:09.957365-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__: File 
>> "/usr/lib/python3/dist-packages/bme280/__init__.py", line 154, in 
>> load_calibration_params
>> 2024-02-22T08:24:09.957686-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:   compensation_params.dig_T1 = 
>> read.unsigned_short(0x88)
>> 2024-02-22T08:24:09.958039-05:00 raspberrypi weewxd[861]: CRITICAL 
>> __main__:    
>> ^
>> 

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Tom Keffer]

It looks like the author of the driver is trying to insert a string into a
byte array. You should file an issue on the repository's issue list.

On Thu, Feb 22, 2024 at 6:00 AM Jamie Stephens 
wrote:

> i manually restarted it and it's running right now just the registry push
> error but not exited
> Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry:
> Failed to publish record 2024-02-22 08:50:00 EST (17086098>
>
> will report back if weewx crashes again
>
> On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:
>
>> Thanks for the fix, I didn't;t even noticed it was not working
>>
>> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>>
>>> Thank you for resolving the error message.
>>>
>>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com >> >:
>>>
 Thanks for pushing it over the goal line. Always the hardest part.

 On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:

> Update - the upstream author was nice enough to merge my PR for this
> problem, so you can simply upgrade your driver to the latest version and
> your station registration should work again with weewx v5.
>
> weectl extension install
> https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
> sudo systemctl restart weewx
>
> After upgrading your driver you should see the following output from
> 'weectl extension list':
>
> Extension NameVersion   Description
> weatherflowudp1.10.2Capture data from WeatherFlow Bridge via
> UDP broadcast packets
>
> Thanks again Rich for the nudge(s) !!!
>
> --
 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAPq0zEBgm3xQsYh%2BFH0T-XyHVK6DmxE64Ha2Xq1VZzhh-Z1ROg%40mail.gmail.com.

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

I read this on your log: OSError: "[Errno 121] Remote I/O error"...

Prior installing the BME280 extension, I installed the AS3935 one and I had 
also to add gpio to weewx group to make my AS3935 lightining detector 
working.

Maybe try this: "sudo usermod -a -G gpio weewx"

Pierre-Yves






Le jeudi 22 février 2024 à 14:41:09 UTC+1, Jeff Chabot a écrit :

> Hi Pierre-Yves,
>
> Thanks for the suggestion, I just ran that command, uninstalled the 
> extension and reinstalled it.  Unfortunately, either it didn't help or I am 
> seeing new issues.  Here are the new errors I am seeing when installing the 
> bme280wx-master.zip extension:
>
> 2024-02-22T08:24:09.936591-05:00 raspberrypi weewxd[861]: Exception in 
> thread stdout-thread:
> 2024-02-22T08:24:09.937508-05:00 raspberrypi weewxd[861]: Traceback (most 
> recent call last):
> 2024-02-22T08:24:09.937920-05:00 raspberrypi weewxd[861]:   File 
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
> 2024-02-22T08:24:09.939853-05:00 raspberrypi weewxd[861]: self.run()
> 2024-02-22T08:24:09.940435-05:00 raspberrypi weewxd[861]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> 2024-02-22T08:24:09.940815-05:00 raspberrypi weewxd[861]: Exception in 
> thread stderr-thread:
> 2024-02-22T08:24:09.941172-05:00 raspberrypi weewxd[861]: Traceback (most 
> recent call last):
> 2024-02-22T08:24:09.941502-05:00 raspberrypi weewxd[861]:   File 
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
> 2024-02-22T08:24:09.942416-05:00 raspberrypi weewxd[861]: for line in 
> iter(self._fd.readline, ''):
> 2024-02-22T08:24:09.943319-05:00 raspberrypi weewxd[861]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> 2024-02-22T08:24:09.944357-05:00 raspberrypi weewxd[861]: self.run()
> 2024-02-22T08:24:09.945285-05:00 raspberrypi weewxd[861]:   File 
> "/etc/weewx/bin/user/sdr.py", line 198, in run
> 2024-02-22T08:24:09.946172-05:00 raspberrypi weewxd[861]: for line in 
> iter(self._fd.readline, ''):
> 2024-02-22T08:24:09.946998-05:00 raspberrypi weewxd[861]: ValueError: 
> PyMemoryView_FromBuffer(): info->buf must not be NULL
> 2024-02-22T08:24:09.947862-05:00 raspberrypi weewxd[861]: INFO user.sdr: 
> shutdown complete
> 2024-02-22T08:24:09.948348-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: Caught OSError: [Errno 121] Remote I/O error
> 2024-02-22T08:24:09.952604-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   Traceback (most recent call last):
> 2024-02-22T08:24:09.953116-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewxd.py", line 160, in main
> 2024-02-22T08:24:09.953514-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   engine = weewx.engine.StdEngine(config_dict)
> 2024-02-22T08:24:09.953891-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    ^^^
> 2024-02-22T08:24:09.954261-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewx/engine.py", line 89, in 
> __init__
> 2024-02-22T08:24:09.954633-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   self.loadServices(config_dict)
> 2024-02-22T08:24:09.955000-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/usr/share/weewx/weewx/engine.py", line 157, in 
> loadServices
> 2024-02-22T08:24:09.955366-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   obj = weeutil.weeutil.get_object(svc)(self, 
> config_dict)
> 2024-02-22T08:24:09.955737-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    
>  ^^
> 2024-02-22T08:24:09.956185-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File "/etc/weewx/bin/user/bme280wx.py", line 61, in 
> __init__
> 2024-02-22T08:24:09.956573-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   self.calibration_params = 
> bme280.load_calibration_params(self.bus, self.address)
> 2024-02-22T08:24:09.956997-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    
>  ^^
> 2024-02-22T08:24:09.957365-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File 
> "/usr/lib/python3/dist-packages/bme280/__init__.py", line 154, in 
> load_calibration_params
> 2024-02-22T08:24:09.957686-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   compensation_params.dig_T1 = 
> read.unsigned_short(0x88)
> 2024-02-22T08:24:09.958039-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:    
> ^
> 2024-02-22T08:24:09.958418-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__: File 
> "/usr/lib/python3/dist-packages/bme280/reader.py", line 40, in 
> unsigned_short
> 2024-02-22T08:24:09.958786-05:00 raspberrypi weewxd[861]: CRITICAL 
> __main__:   

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Jeff Chabot]

I fixed my issue today by modifying the bme280wx-master/install.py script
to use the correct i2c_address: 'i2c_address': '0x77'.  It was set to
0x76.  I then uninstalled the extension and reinstalled it.

Thanks again!

Jeff

On Thu, Feb 22, 2024 at 8:08 AM Pierre-Yves  wrote:

> Hello Jeff,
>
> For having my BME280 working properly with Weewx 5.0.2.1, I had to add
> this permission: "sudo usermod -aG i2c weewx".
> Did you add it already ?
>
> Pierre-Yves
>
> Le jeudi 22 février 2024 à 08:12:08 UTC+1, meteo219 a écrit :
>
>> Hello Weewx Users,
>>
>> I upgraded weewx tonight on my raspberry pi to version 5.0.2-1 and since
>> doing so, I had some major reconfiguration issues to get things working
>> again.  I upgraded via apt upgrade -y and then choose Y when asked if I
>> wanted to upgrade weewx.conf.  I am thinking that I should have gone with
>> the default of N there.
>>
>> That said, I was able to fix most things myself by following instructions
>> I found here:
>>
>>
>> https://github.com/weewx/weewx/wiki/Understanding-permissions#the-weewx-user
>>
>> I am using SDR for most of my data and BME280 for pressure.
>>
>> The code that I am using for those products in /etc/weewx.conf looks like
>> this:
>>
>> [SDR]
>> # This section is for the software-defined radio driver.
>>
>> # The driver to use
>> driver = user.sdr
>>
>> cmd = /usr/bin/rtl_433 -M utc -F json -R 40
>>
>> [[sensor_map]]
>> outTemp = temperature.04A5.Acurite5n1PacketV2
>> outHumidity = humidity.04A5.Acurite5n1PacketV2
>> windDir = wind_dir.04A5.Acurite5n1PacketV2
>> windSpeed = wind_speed.04A5.Acurite5n1PacketV2
>> rain_total = rain_total.04A5.Acurite5n1PacketV2
>>
>> [Bme280wx]
>> i2c_port = 1
>> i2c_address = 0x77
>> usUnits = US
>> temperatureKeys = inTemp
>> temperature_must_have = ""
>> pressureKeys = pressure
>> pressure_must_have = outTemp
>> humidityKeys = inHumidity
>> humidity_must_have = ""
>>
>> I already installed modules using apt:
>>
>> apt install python3-smbus2
>> apt install python3-bme280
>>
>> That said, I am not seeing any pressure data from bme280.  I ran weectl
>> extension install  bme280wx-master.zip and that added under [[Services]]
>> this line:
>>
>> data_services = user.bme280wx.Bme280wx
>>
>> When I restart weewx, I see these errors with debug on:
>>
>> 2024-02-22T01:52:50.936407-05:00  weewxd[11578]: CRITICAL __main__:
>> File "/etc/weewx/bin/user/bme280wx.py", line 58, in __init__
>> 2024-02-22T01:53:00.940567-05:00  weewxd[11578]: DEBUG weewx.engine:
>> Loading service user.bme280wx.Bme280wx
>> 2024-02-22T01:53:00.941284-05:00 weewxd.py: bme280: bme280wx
>> configuration {'i2c_port': '1', 'i2c_address': '0x77', 'usUnits': 'US',
>> 'temperatureKeys': 'inTemp', 'temperature_must_have': '', 'pressureKeys':
>> 'pressure', 'pressure_must_have': 'outTemp', 'humidityKeys': 'inHumidity',
>> 'humidity_must_have': ''}
>>
>> Line 58 of the above file is: self.bus = smbus2.SMBus(self.port) if that
>> helps.
>>
>> i2c
>>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>> 00: -- -- -- -- -- -- -- --
>> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
>> 70: -- -- -- -- -- -- -- 77
>>
>> Any ideas on this one?  Things were working great before this upgrade.  I
>> am thinking that I need an updated version of the bme280 script but not
>> sure what is wrong.
>>
>> Thanks,
>>
>> Jeff
>>
>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/-qmJU5-ON1U/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/37300b2e-8d98-4a48-8a38-6314b736a5acn%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACeKy--yzkz%3D%3DDR2qaEsXfXaPU8Gikxt2MBiQG9bFSve6FmNLw%40mail.gmail.com.

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

[gary....@gmail.com]

Amen to that. Funny how things creep in and when you try to change one 
thing, others break.
I just did that with mosquitto. Didn't want it running as root anymore. I 
found it is quite picky about the SSL certs location and permissions.

Take the time to install properly with a fresh OS and weewx. Edit in your 
changes to weewx.conf and skins.
You'll thank yourself later.

On Wednesday, February 21, 2024 at 7:21:04 PM UTC-5 vince wrote:

FWIW, it's a good opportunity to (re)take control of your system a little 
and document what you have there.  Over time and a lot of hand tweaks it's 
easy to lose track of the configuration in good detail.  But yes having 
'before' backups always helps.



-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c7575837-9666-4a86-8a29-1680f108daa2n%40googlegroups.com.

Re: [weewx-user] How to upgrade from setup.py v4 install to pip v5 install

[gary....@gmail.com]

Thanks for the options.

I don't want to have a "hybrid" so won't be following the migration guide 
method.
Makes more sense to me to install new, install extensions and skins, edit 
in my config from the existing (old) weewx.conf, copy the database over, 
remove the old systemd service file, add the new systemd service, move the 
old install to weewx.old, run the new.

May be a tiny bit more effort but then should be easier for me to 
maintain/update in the future.



On Wednesday, February 21, 2024 at 11:07:46 AM UTC-5 Tom Keffer wrote:

> Oh, I thought we were talking about upgrading from an alpha version of v5.
>
> Not much difference. Just set up a V5 virtual environment, then point it 
> at /home/weewx. Follow the directions in the migration guide 
> . 
>
> On Wed, Feb 21, 2024 at 7:44 AM gary@gmail.com  
> wrote:
>
>> I understand coming from v5 that would be a way.
>> I need to upgrade my v4 setup.py to v5 though.
>>
>>
>> On Wednesday, February 21, 2024 at 10:39:47 AM UTC-5 Tom Keffer wrote:
>>
>> The pip installs are super easy to back up. Just copy ~/weewx-venv and 
>> ~/weewx-data and you have everything you need.
>>
>> Then activate the virtual environment, then "pip install weewx 
>> --upgrade". It should be that easy. If something fails, just roll things 
>> back.
>>
>> On Wed, Feb 21, 2024 at 7:15 AM gary@gmail.com  
>> wrote:
>>
>> I've had a test install of v5 since early alphas. Now, it is time to 
>> upgrade my production install.
>> I have a relatively simple install, Vantage Pro IP driver, weewx-mqtt. A 
>> couple of additional internet uploaders (Windy and WeatherCloud). I run two 
>> skins, Belchertown and weewx-wdc
>>
>> All is and has been quite stable. So, I hesitate to poke at it. But, v5 
>> is the new standard, so I need to get this done.
>>
>> I don't see many who have trod this path. How to go about this?
>>
>> -- 
>> 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/b2d73a89-3432-4ad4-8971-34ea51167f24n%40googlegroups.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/68e9b77e-5d25-492f-bfa5-448ac39b8cedn%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/fbb6b339-9284-4e54-a97b-85d99d787a61n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

i manually restarted it and it's running right now just the registry push 
error but not exited 
Feb 22 08:50:19 weewx weewxd[68909]: ERROR weewx.restx: StationRegistry: 
Failed to publish record 2024-02-22 08:50:00 EST (17086098>

will report back if weewx crashes again

On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for this 
 problem, so you can simply upgrade your driver to the latest version and 
 your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output from 
 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
 UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2f38f991-b58b-4a9c-ad95-21a63311bb90n%40googlegroups.com.

Re: [weewx-user] Re: WeatherFlowUDP driver for Tempest Weatherstations

[Jamie Stephens]

 thread exited last night and won't restart
Feb 21 17:08:31 weewx weewxd[763]:   File "/usr/share/weewx/weewxd.py", 
line 166, in main
Feb 21 17:08:31 weewx weewxd[763]: engine.run()
Feb 21 17:08:31 weewx weewxd[763]:   File 
"/usr/share/weewx/weewx/engine.py", line 204, in run
Feb 21 17:08:31 weewx weewxd[763]: for packet in 
self.console.genLoopPackets():
Feb 21 17:08:31 weewx weewxd[763]:   File 
"/etc/weewx/bin/user/weatherflowudp.py", line 313, in genLoopPackets
Feb 21 17:08:31 weewx weewxd[763]: m0 = m[0].replace(",null",",None")   
  # Python 2
Feb 21 17:08:31 weewx weewxd[763]: TypeError: a bytes-like object is 
required, not 'str'
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Failed with result 
'exit-code'.
Feb 21 17:08:31 weewx systemd[1]: weewx.service: Consumed 39min 16.609s CPU 
time.

On Monday, February 19, 2024 at 7:09:16 PM UTC-5 Jamie Stephens wrote:

> Thanks for the fix, I didn't;t even noticed it was not working
>
> On Monday, February 19, 2024 at 4:25:28 AM UTC-5 Ton Karsten wrote:
>
>> Thank you for resolving the error message.
>>
>> Op ma 19 feb 2024 om 01:36 schreef bell...@gmail.com :
>>
>>> Thanks for pushing it over the goal line. Always the hardest part.
>>>
>>> On Sunday 18 February 2024 at 19:33:41 UTC-5 vince wrote:
>>>
 Update - the upstream author was nice enough to merge my PR for this 
 problem, so you can simply upgrade your driver to the latest version and 
 your station registration should work again with weewx v5.

 weectl extension install 
 https://github.com/captain-coredump/weatherflow-udp/archive/master.zip
 sudo systemctl restart weewx

 After upgrading your driver you should see the following output from 
 'weectl extension list':

 Extension NameVersion   Description
 weatherflowudp1.10.2Capture data from WeatherFlow Bridge via 
 UDP broadcast packets

 Thanks again Rich for the nudge(s) !!!

 -- 
>>> 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/9c2ecfe9-0b41-4b33-9295-fc6e9edf0db3n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a18f61c4-9bbd-4f03-b868-95f954cfacaan%40googlegroups.com.

Re: [weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Jeff Chabot]

Hi Pierre-Yves,

Thanks for the suggestion, I just ran that command, uninstalled the
extension and reinstalled it.  Unfortunately, either it didn't help or I am
seeing new issues.  Here are the new errors I am seeing when installing the
bme280wx-master.zip extension:

2024-02-22T08:24:09.936591-05:00 raspberrypi weewxd[861]: Exception in
thread stdout-thread:
2024-02-22T08:24:09.937508-05:00 raspberrypi weewxd[861]: Traceback (most
recent call last):
2024-02-22T08:24:09.937920-05:00 raspberrypi weewxd[861]:   File
"/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
2024-02-22T08:24:09.939853-05:00 raspberrypi weewxd[861]: self.run()
2024-02-22T08:24:09.940435-05:00 raspberrypi weewxd[861]:   File
"/etc/weewx/bin/user/sdr.py", line 198, in run
2024-02-22T08:24:09.940815-05:00 raspberrypi weewxd[861]: Exception in
thread stderr-thread:
2024-02-22T08:24:09.941172-05:00 raspberrypi weewxd[861]: Traceback (most
recent call last):
2024-02-22T08:24:09.941502-05:00 raspberrypi weewxd[861]:   File
"/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
2024-02-22T08:24:09.942416-05:00 raspberrypi weewxd[861]: for line in
iter(self._fd.readline, ''):
2024-02-22T08:24:09.943319-05:00 raspberrypi weewxd[861]: ValueError:
PyMemoryView_FromBuffer(): info->buf must not be NULL
2024-02-22T08:24:09.944357-05:00 raspberrypi weewxd[861]: self.run()
2024-02-22T08:24:09.945285-05:00 raspberrypi weewxd[861]:   File
"/etc/weewx/bin/user/sdr.py", line 198, in run
2024-02-22T08:24:09.946172-05:00 raspberrypi weewxd[861]: for line in
iter(self._fd.readline, ''):
2024-02-22T08:24:09.946998-05:00 raspberrypi weewxd[861]: ValueError:
PyMemoryView_FromBuffer(): info->buf must not be NULL
2024-02-22T08:24:09.947862-05:00 raspberrypi weewxd[861]: INFO user.sdr:
shutdown complete
2024-02-22T08:24:09.948348-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: Caught OSError: [Errno 121] Remote I/O error
2024-02-22T08:24:09.952604-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   Traceback (most recent call last):
2024-02-22T08:24:09.953116-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File "/usr/share/weewx/weewxd.py", line 160, in main
2024-02-22T08:24:09.953514-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   engine = weewx.engine.StdEngine(config_dict)
2024-02-22T08:24:09.953891-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:    ^^^
2024-02-22T08:24:09.954261-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File "/usr/share/weewx/weewx/engine.py", line 89, in
__init__
2024-02-22T08:24:09.954633-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   self.loadServices(config_dict)
2024-02-22T08:24:09.955000-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File "/usr/share/weewx/weewx/engine.py", line 157, in
loadServices
2024-02-22T08:24:09.955366-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   obj = weeutil.weeutil.get_object(svc)(self,
config_dict)
2024-02-22T08:24:09.955737-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: 
 ^^
2024-02-22T08:24:09.956185-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File "/etc/weewx/bin/user/bme280wx.py", line 61, in
__init__
2024-02-22T08:24:09.956573-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   self.calibration_params =
bme280.load_calibration_params(self.bus, self.address)
2024-02-22T08:24:09.956997-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: 
 ^^
2024-02-22T08:24:09.957365-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File
"/usr/lib/python3/dist-packages/bme280/__init__.py", line 154, in
load_calibration_params
2024-02-22T08:24:09.957686-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   compensation_params.dig_T1 =
read.unsigned_short(0x88)
2024-02-22T08:24:09.958039-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: 
^
2024-02-22T08:24:09.958418-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File
"/usr/lib/python3/dist-packages/bme280/reader.py", line 40, in
unsigned_short
2024-02-22T08:24:09.958786-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   return self._bus.read_word_data(self._address,
register) & 0x
2024-02-22T08:24:09.959133-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: 
^
2024-02-22T08:24:09.959500-05:00 raspberrypi weewxd[861]: CRITICAL
__main__: File
"/usr/lib/python3/dist-packages/smbus2/smbus2.py", line 474, in
read_word_data
2024-02-22T08:24:09.959849-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   ioctl(self.fd, I2C_SMBUS, msg)
2024-02-22T08:24:09.960296-05:00 raspberrypi weewxd[861]: CRITICAL
__main__:   OSError: [Errno 121] Remote I/O error

[weewx-user] Re: Weewx Version: 5.0.2-1 issues post upgrade

[Pierre-Yves]

Hello Jeff,

For having my BME280 working properly with Weewx 5.0.2.1, I had to add this 
permission: "sudo usermod -aG i2c weewx".
Did you add it already ?

Pierre-Yves

Le jeudi 22 février 2024 à 08:12:08 UTC+1, meteo219 a écrit :

> Hello Weewx Users,
>
> I upgraded weewx tonight on my raspberry pi to version 5.0.2-1 and since 
> doing so, I had some major reconfiguration issues to get things working 
> again.  I upgraded via apt upgrade -y and then choose Y when asked if I 
> wanted to upgrade weewx.conf.  I am thinking that I should have gone with 
> the default of N there.
>
> That said, I was able to fix most things myself by following instructions 
> I found here:
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#the-weewx-user
>
> I am using SDR for most of my data and BME280 for pressure.
>
> The code that I am using for those products in /etc/weewx.conf looks like 
> this:
>
> [SDR]
> # This section is for the software-defined radio driver.
>
> # The driver to use
> driver = user.sdr
>
> cmd = /usr/bin/rtl_433 -M utc -F json -R 40
>
> [[sensor_map]]
> outTemp = temperature.04A5.Acurite5n1PacketV2
> outHumidity = humidity.04A5.Acurite5n1PacketV2
> windDir = wind_dir.04A5.Acurite5n1PacketV2
> windSpeed = wind_speed.04A5.Acurite5n1PacketV2
> rain_total = rain_total.04A5.Acurite5n1PacketV2
>
> [Bme280wx]
> i2c_port = 1
> i2c_address = 0x77
> usUnits = US
> temperatureKeys = inTemp
> temperature_must_have = ""
> pressureKeys = pressure
> pressure_must_have = outTemp
> humidityKeys = inHumidity
> humidity_must_have = ""
>
> I already installed modules using apt:
>
> apt install python3-smbus2
> apt install python3-bme280
>
> That said, I am not seeing any pressure data from bme280.  I ran weectl 
> extension install  bme280wx-master.zip and that added under [[Services]] 
> this line:
>
> data_services = user.bme280wx.Bme280wx
>
> When I restart weewx, I see these errors with debug on:
>
> 2024-02-22T01:52:50.936407-05:00  weewxd[11578]: CRITICAL __main__: 
> File "/etc/weewx/bin/user/bme280wx.py", line 58, in __init__
> 2024-02-22T01:53:00.940567-05:00  weewxd[11578]: DEBUG weewx.engine: 
> Loading service user.bme280wx.Bme280wx
> 2024-02-22T01:53:00.941284-05:00 weewxd.py: bme280: bme280wx configuration 
> {'i2c_port': '1', 'i2c_address': '0x77', 'usUnits': 'US', 
> 'temperatureKeys': 'inTemp', 'temperature_must_have': '', 'pressureKeys': 
> 'pressure', 'pressure_must_have': 'outTemp', 'humidityKeys': 'inHumidity', 
> 'humidity_must_have': ''}
>
> Line 58 of the above file is: self.bus = smbus2.SMBus(self.port) if that 
> helps.
>
> i2c
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00: -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- 77
>
> Any ideas on this one?  Things were working great before this upgrade.  I 
> am thinking that I need an updated version of the bme280 script but not 
> sure what is wrong.
>
> Thanks,
>
> Jeff
>
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/37300b2e-8d98-4a48-8a38-6314b736a5acn%40googlegroups.com.

Re: [weewx-user] updated to 5.0.1 still no joy

[Glen N]

After updating DietPi to version 9.1.1

I am getting GPIOzero BadPinFactory errors again. I tried commenting out 
the weewx user in the service file as above, but the error remains.

● weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Thu 2024-02-22 21:02:32 AEDT; 
12min ago
   Docs: https://weewx.com/docs
   Main PID: 23495 (code=exited, status=1/FAILURE)
CPU: 1.834s

Feb 22 21:02:32 NapsberryPi weewxd[23495]:   File 
"/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in 
_default_pin_factory
Feb 22 21:02:32 NapsberryPi weewxd[23495]: raise BadPinFactory('Unable 
to load any default pin factory!')
Feb 22 21:02:32 NapsberryPi weewxd[23495]: gpiozero.exc.BadPinFactory: 
Unable to load any default pin factory!
Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:    
 File "/usr/lib/python3/dist-packages/gpiozero/devices.py", line 291, in 
_default_pin_factory
Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
 raise BadPinFactory('Unable to load any default pin factory!')
Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
 gpiozero.exc.BadPinFactory: Unable to load any default pin factory!
Feb 22 21:02:32 NapsberryPi weewxd[23495]: CRITICAL __main__:  
 Exiting.
Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Main process exited, 
code=exited, status=1/FAILURE
Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Failed with result 
'exit-code'.
Feb 22 21:02:32 NapsberryPi systemd[1]: weewx.service: Consumed 1.834s CPU 
time.

On Monday 12 February 2024 at 1:01:24 pm UTC+11 Glen N wrote:

> I was having a no start problem after upgrading RPi3B running DietPi. I 
> tried Tom's suggestion and it fixed the problem.
>
> Prior to the "fix" my log file showed:
> -- Journal begins at Mon 2024-02-12 11:47:21 AEDT, ends at Mon 2024-02-12 
> 12:40:34 AEDT. --
> Feb 12 11:47:23 SystemName systemd[1]: Started WeeWX.
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Initializing weewxd 
> version 5.0.1
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Command line: 
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Using Python 3.9.2 
> (default, Feb 28 2021, 17:03:44)
>  [GCC 10.2.1 20210110]
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Located at 
> /usr/bin/python3
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Platform 
> Linux-6.1.21-v8+-aarch64-with-glibc2.31
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Locale: 
> 'en_AU.UTF-8'
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Entry path: 
> /usr/share/weewx/weewxd.py
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: WEEWX_ROOT: 
> /etc/weewx
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Configuration file: 
> /etc/weewx/weewx.conf
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: User module: 
> /etc/weewx/bin/user
> Feb 12 11:47:24 SystemName weewxd[309]: INFO __main__: Debug: 0
> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.engine: Loading station 
> type FineOffsetUSB (weewx.drivers.fousb)
> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: driver 
> version is 1.3
> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: polling 
> mode is PERIODIC
> Feb 12 11:47:24 SystemName weewxd[309]: INFO weewx.drivers.fousb: polling 
> interval is 60
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.drivers.fousb: found 
> station on USB bus= device=
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: StdConvert 
> target unit is 0x11
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Archive will 
> use data binding wx_binding
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Record 
> generation will be attempted in 'software'
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: Using archive 
> interval of 300 seconds (software record generation)
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: StationRegistry: 
> Station will not be registered: no station_url specified.
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: 
> Wunderground-PWS: Data for station ITEATR7 will be posted
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: PWSWeather: Data 
> for station THISTLEWIND will be posted
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: CWOP: Posting 
> not enabled.
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: WOW: Posting not 
> enabled.
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> Feb 12 11:47:25 SystemName weewxd[309]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is