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
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
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
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
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
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
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
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
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
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
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,
>
>
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
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
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,
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
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:
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
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)
18 matches
Mail list logo
