Thanks,
I got it to run again, by restarting weewx???
I will keep an eye on it and it if plays up again come back for help.
Glen
On Fri, 23 Feb 2024 at 05:44, vince wrote:
> You're going to need to share your weewx.conf file for this one.
> You have to be referencing gpio stuff somewhere under
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
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)
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]:
On Thu, 8 Feb 2024 at 02:12, Tom Keffer wrote:
> Something to try: edit the weewx service file and change permissions back
> to root. The service file should be located at
> /lib/systemd/system/weewx.service. Comment out the User and Group lines.
> When you're done, it will look something like
Something to try: edit the weewx service file and change permissions back
to root. The service file should be located at
/lib/systemd/system/weewx.service. Comment out the User and Group lines.
When you're done, it will look something like this:
[Service]
ExecStart=weewxd /etc/weewx/weewx.conf
Hi Tom, it happens every time. Attached is a log of what happened when I
turned off the Pi, restarted the Pi, shut down weewx, and restarted weewx.
I running a fresh RasberryPi Debian install. Vantage Pro2 with a
WeatherLinkIP attached to a VantagePro2 console.
Attached is what happened with
Rich,
One other question: does this happen after a reboot? Or, every time?
If it's only after a reboot, the problem could be that the network isn't
ready by the time the VP2 needs it.
On Tue, Feb 6, 2024 at 7:51 PM Rich Strle wrote:
> I've been following the 5.0 issues. I have updated to
I've been following the 5.0 issues. I have updated to 5.0.1 and done the
usermod but I'm still having issues. RaspberryPi 3 B+ My Vantage Pro is
connected via ethernet using the IP adaptor. I appreciate all the work
that's gone into this free product.
vp2pi@rpivp2:~ $ sudo apt update
