Thanks, I was missing the "-1" at the end, that solved my problem I managed
to downgrade.
sudo apt install weewx=4.10.2-1
Axelle.
On Tuesday, February 6, 2024 at 8:31:56 PM UTC+1 Mks Mk wrote:
> Pierre-Yves
> we used these commands
> sudo apt remove weewx
> then
> sudo apt install
This solved my problem, adding user ‘weewx’ to the ‘plugdev’ group using
the usermod command.
'sudo usermod -aG plugdev weewx'
On Tuesday, February 6, 2024 at 10:23:15 AM UTC-5 matthew wall wrote:
> when you install rtl-sdr, it typically, but not always, installs udev
> rules for *many* sdr
As I don't know anything related to gpio, I was wondering, what may be
related to weewx. Aside of gw1000, forecast and zambretti, I do not have
installed anything else in weewx.conf.
As I plan to move to a raspi5 in a couple of months, I am considering to
come back to a Zigbee (or Matter)
If you do not need gpio for weewx, do not install anything related to gpio
in your weewx.conf file. Seems pretty simple to me.
On Friday, February 9, 2024 at 3:47:59 AM UTC-8 Vetti52 wrote:
> Concerning my v4 update process I should add some clarification:
> My Raspi crashed due to a SD card
Concerning my v4 update process I should add some clarification:
My Raspi crashed due to a SD card failure, which suddenly change it to read
only mode completely. Thus I had an "unerasable backup copy". I took a
brand new SD card, installed a brand new Raspian image with Bookworm lite
and
See if https://forums.raspberrypi.com/viewtopic.php?t=345917 helps any for
your gpio issue.
Again here, what user and group is weewx running as? That user needs
correct permissions to be able to access your attached hardware. My guess
is that you need to add the weewx user to the same groups
I have no idea what ".lgd-fy0" is, but it should probably be owned by
weewx:weewx.
I'm not sure what "v4 upgrade process" you're referring to. You certainly
did not have to offload any files. Same with the v5 upgrade.
The owner of the weewxd process had changed from "root" to "weewx", but the
After updating to from v5.0.0 to v5-0.1I got this log entry:
Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Deactivated successfully.
Feb 05 14:59:07 raspbee systemd[1]: Stopped weewx.service - WeeWX.
Feb 05 14:59:07 raspbee systemd[1]: weewx.service: Consumed 27min 28.104s
CPU time.
Feb 05
Thanks a lot, very interesting !
Yesterday, as I failed to have weewx 5.1 working properly, I reverted to
4.10.2.
My configuration is very similar :
- BME280 sensor
- AS3953 lightning sensor
- SDR driver
- Seasons skin
- Belchertown skin
I am tempted to give a new try...
Pierre-Yves
Le jeudi
today tried to update my other raspberry pi to weewx v5.01 and this pi is
different than the main weather pi that we use:
1-bme280 sensor.
2-sdr
3-weewx-wxobs skin.
after the weewx update we did the following:
sudo usermod -aG dialout weewx
sudo usermod -aG plugdev weewx
sudo systemctl restart
Matthew - agree with adding group dialout. Fortunately the raspi has the
default user in that group already which is why serial-connected VP2 worked
with no additions required for me (via serial2USB dongle). I think I sent
you guys some email mentioning that back in the pre-release testing
I would add "dialout" as well.
On Wed, Feb 7, 2024 at 11:49 AM matthew wall wrote:
> On Wednesday, February 7, 2024 at 11:58:36 AM UTC-5 tke...@gmail.com
> wrote:
>
> I'll add "plughw" to the troubleshooting section.
>
>
> tom, i have added sections to the 'permissions' wiki page with details
>
On Wednesday, February 7, 2024 at 11:58:36 AM UTC-5 tke...@gmail.com wrote:
I'll add "plughw" to the troubleshooting section.
tom, i have added sections to the 'permissions' wiki page with details like
this one. i suspect we will see more, since this is not specific to
rtl-sdr, nor is it
https://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user
On Wed, Feb 7, 2024 at 8:58 AM Tom Keffer wrote:
> I'll add "plughw" to the troubleshooting section.
>
> -tk
>
> On Wed, Feb 7, 2024 at 8:16 AM Steve Gee wrote:
>
>> I ended up adding the weewx user to the plughw group which
I'll add "plughw" to the troubleshooting section.
-tk
On Wed, Feb 7, 2024 at 8:16 AM Steve Gee wrote:
> I ended up adding the weewx user to the plughw group which fixed the
> problem with rtl_433 not starting:
>
> sudo adduser weewx plughw
> sudo systemctl restart weewx.service
>
> On
I ended up adding the weewx user to the plughw group which fixed the
problem with rtl_433 not starting:
sudo adduser weewx plughw
sudo systemctl restart weewx.service
On Wednesday, February 7, 2024 at 2:14:41 AM UTC-5 František Slimařík wrote:
> @Matthew:
>
> That makes sense yep. Thanks a lot
@Matthew:
That makes sense yep. Thanks a lot for detailed explanation. I cannot
change port 80 on my hardware so I will review other options :)
st 7. 2. 2024 v 8:08 odesílatel matthew wall napsal:
> another option is to put a proxy in front of interceptor. configure
> interceptor to listen on
another option is to put a proxy in front of interceptor. configure
interceptor to listen on a high port, say 8080, then run nginx binding to
port 80 as a reverse proxy to interceptor, proxying all traffic or just
specific requests.
m
--
You received this message because you are subscribed
Frantisek,
udev rules are for devices - USB or serial, not for network ports.
the permissions error you are experiencing is probably due the fact that
you are trying to listen on (bind to) port 80. only root is allowed to
bind to ports lower than 1024.
assuming that you are on a linux
@Matthew:
Any clue what should be modified (udev rules/group membership) for
interceptor driver? When I modify systemctl service to not run under
weewx:weewx everything is OK :)
*Feb 6 19:37:43 rocky-weather-machine weewxd[1612889]: INFO weewx.engine:
Loading station type Interceptor
Impossible to say what the issue is with such a short log extract. Please
edit weewx.conf, set debug =1, save weewx.conf and restart WeeWX. Let WeeWX
run for at least two archive intervals and then take a log extract showing
the full WeeWX startup through until the two archive intervals have
Yes, and data is being sent to CWOP and Wunderground.
On Tue, Feb 6, 2024, 12:26 Jeff A. D. wrote:
> Is your database being updated?
>
> On Tuesday, February 6, 2024 at 12:23:35 PM UTC-7 Philip Wolff wrote:
>
>> Thanks for that tip - it got me off the ground. All is now well except
>> that
Is your database being updated?
On Tuesday, February 6, 2024 at 12:23:35 PM UTC-7 Philip Wolff wrote:
> Thanks for that tip - it got me off the ground. All is now well except
> that /var/www/html/weewx hasn't been updated since just before I did the
> upgrade to 5.0.1. Anyone else seeing this?
Pierre-Yves
we used these commands
sudo apt remove weewx
then
sudo apt install weewx=4.10.2-1
On Tuesday, February 6, 2024 at 10:13:38 PM UTC+3 Pierre-Yves wrote:
> @ Mks Mk,
> Which command did you use to perform the downgrade from v5to v4.10.2 ?
> I tried "sudo apt install weewx=4.10.2" and
Pierre-Yves,
we used these commands
Pierre-Yves
sudo apt remove weewx
then
sudo apt install weewx=4.10.2-1
On Tuesday, February 6, 2024 at 10:13:38 PM UTC+3 Pierre-Yves wrote:
> @ Mks Mk,
> Which command did you use to perform the downgrade from v5to v4.10.2 ?
> I tried "sudo apt install
Thanks for that tip - it got me off the ground. All is now well except that
/var/www/html/weewx hasn't been updated since just before I did the upgrade
to 5.0.1. Anyone else seeing this?
On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:
> In case anyone else runs into this -
@ Mks Mk,
Which command did you use to perform the downgrade from v5to v4.10.2 ?
I tried "sudo apt install weewx=4.10.2" and "sudo apt install weewx 4.10.2"
but none of these work...
Thanks, Pierre-Yves
Le mardi 6 février 2024 à 19:44:41 UTC+1, Mks Mk a écrit :
> we just tried the upgrade
we just tried the upgrade again to weewx v5.0.1 (sudo apt update) and it
worked this time.
(we have not done any changes to the system after the downgrade to v4.10.2)
On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:
> @ Matthew, thanks. I need now to "digest" all this
@ Matthew, thanks. I need now to "digest" all this information, it's a bit
high level for me ;-)
@ Stefanos, thanks too, I tested my USB SDR key and obtain the same result
as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor Corp.
RTL2838 DVB-T"
Pierre-Yves
Le mardi 6 février
i forgot to write in my last message that when you finished you must
restart udev or restart the device you using( p.c , rpi ,... etc)
On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>
> It seems to be
On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
It seems to be a problem of rules change. In fact, I first upgraded from
4.10.2 to 5.0.0 and weewx worked perfectly.
weewx was running as root:root. weewx 5.0.0 did not modify any permissions
when it upgraded from 4.10.2.
I use a nooelec rtl-sdr. On a fresh install of bookworm 64bit in a
Raspberry pi 4 and weewx v5 i solved the error like this:
i run *lsusb*
and i saw a line similar to this
Bus 001 Device 008: ID 0bda:2838 Realtek Semiconductor Corp.
** "0bda" is the vendor id and "2838" is the product id
@ Matthew,
Thanks a lot for the feedback.
It seems to be a problem of rules change. In fact, I first upgraded from
4.10.2 to 5.0.0 and weewx worked perfectly. Then I went from 5.0.0 to 5.0.1
an weewx failed to start.
For Weewx,, I did a deb/rpm install and, as far I remember, I installed
In case anyone else runs into this - my Ubuntu server/Davis VP2 and serial
datalogger had ownership set to root:dialout, so I had to add the weewx
user to the dialout group for things to work.
On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
> when you install rtl-sdr, it
when you install rtl-sdr, it typically, but not always, installs udev rules
for *many* sdr devices. the udev rules that it installs make it possible
for anyone in the 'plugdev' group to read/write to the sdr device. (this
is true when you install rtl-sdr from source - if you install rtl-sdr
Hello all,
I just upgraded from 4.10 .2 to 5.0.1 and I seem to experiment a similar
behavior. I run weewx on a RPi4.
As Tom explained above, I put rtl-sdr.rules in udev directory and restarted
but no change
I tried to downgrade using "sudo apt install weewx=4.10.2" but that doesn't
work :
If you look in your log, you'll see that the rtl_433 process failed to run
because of permissions problems. The log also suggests fixing the problem
by installing the udev rules file "rtl-sir:rules". You can find this rules
file in the rtl-sdr repository:
Thanks a lot!
I will try this later ;)
On Tue, Feb 6, 2024 at 1:43 PM Dominic Reich wrote:
> 'michael.k...@gmx.at' via weewx-user wrote:
>
> >
> >sudo apt install weewx=4.10.2
>
> and to not upgrade again set it on hold:
>
> sudo apt-mark hold weewx
>
> >Stefan Gliessmann schrieb am Dienstag,
'michael.k...@gmx.at' via weewx-user wrote:
sudo apt install weewx=4.10.2
and to not upgrade again set it on hold:
sudo apt-mark hold weewx
Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:
I run weewx 4.10.2 on Ubuntu.
I did an sudo apt update, too, and
sudo apt install weewx=4.10.2
Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:
> I run weewx 4.10.2 on Ubuntu.
> I did an sudo apt update, too, and weewx 5.x got installed.
> Since then, weewx is no longer running.
>
> How did you revert back to weewx 4.10.2?
>
> TIA,
I run weewx 4.10.2 on Ubuntu.
I did an sudo apt update, too, and weewx 5.x got installed.
Since then, weewx is no longer running.
How did you revert back to weewx 4.10.2?
TIA,
Stefan
On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:
> I had the same error with sdr
I had the same error with sdr driver(weewx v5 ) running on debian 12 . The
problem solved by making udev rules ... maybe you are in the same situation
as i was.
Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk έγραψε:
> The system was running weewx v5.0.0 with no issue then we did the upgrade
> to
42 matches
Mail list logo
