The third time I tried the Apt configuration, it found weewx.
The installation worked so far except for the dpkg: Warnung: Altes
Verzeichnis.
Unfortunately, weewx did not react after that and a reboot did not work
anymore.
Now I have to restore the backup and try again.
What went wrong?
pi@Wette
Hi folks,
Like others, I ran into a few issues upgrading to 5.0.1, which I've mostly
sorted, and it's up and running now as before - except - using my rtl_433
(matt wall) integration is leading to interesting sensor values. My
temperatures are wrong/seemingly random and I have no idea why. Ever
Details:
Acurite 5-in-1 sensor, RTL_433 to MQTT (matt wall) + Weewx.
Weewx conf sensors:
[SDR]
# This section is for the software-defined radio driver.
# The driver to use
driver = user.sdr
path = /usr/local/bin
log_unknown_sensors = True
log_unmapped_sensors = True
The only thing I would add is that if you're using the original "wview"
schema, there is no reason to switch to the "wview-extended" schema unless
you need the extra types. For a VantagePro, the original schema works fine.
Conversion is a lot of work.
-tk
On Mon, Feb 12, 2024 at 2:02 PM kutz...@
On Tuesday, February 13, 2024 at 4:13:27 AM UTC-5 geni08...@gmail.com wrote:
The third time I tried the Apt configuration, it found weewx.
The installation worked so far except for the dpkg: Warnung: Altes
Verzeichnis.
Unfortunately, weewx did not react after that and a reboot did not work
any
On Tuesday, February 13, 2024 at 7:42:35 AM UTC-5 Kingsclear Studios wrote:
No idea how to start picking this apart to find the root cause in V5.
i would be surprised if something in v5 is the root cause, but who knows?
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
d
re:
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
did you update weewx-mqtt?
Do you have suggestions on how to execute that properly - can do the
research if needed, just curious if there's a quick way to accomplish that
properly without impacting V5
On Tuesday, F
Matthew,
It worked! Thank you so much, and thanks to Werner as well.
Follow-up question: I am looking into getting one of those Misol stations
that have RS-485 connections. I prefer hardwired solutions instead of wifi.
Would you recommend that, or should I look for something else?
My ideal sol
On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote:
re:
did you update rtl-sdr?
did you update rtl_433?
did you update weewx-sdr?
did you update weewx-mqtt?
Do you have suggestions on how to execute that properly - can do the
research if needed, just curious if there's
Hi Matthew
As said I made e new installation (Raspi4, bullseye) now version 5.0.2-1
according installation guide.
Weewx installs:
Entpacken von weewx (5.0.2-1) ...
weewx (5.0.2-1) wird eingerichtet ...
Using weewx:weewx as user:group
Creating /etc/default/weewx
Using configuration file /etc/wee
On Tuesday, February 13, 2024 at 9:11:14 AM UTC-5 wagr...@gmail.com wrote:
Feb 13 12:40:54 hp weewxd[4425]: ERROR weewx.imagegenerator: Unable to save
to file '/var/www/html/weewx/yearrx.png' [Errno 13] Keine Berechtigung:
'/var/www/html/weewx/yearrx.png':
Feb 13 12:40:54 hp weewxd[4425]: INFO
I did not update those. Just a standard update to weewx v5___"Sent from my mobile device"On Feb 13, 2024, at 9:54 AM, matthew wall wrote:On Tuesday, February 13, 2024 at 8:41:31 AM UTC-5 Kingsclear Studios wrote:re:
did you update rtl-sdr?did you update rtl_433?did you up
Hello,
I experience very similar behavior to that described above.
Recently, I failed to upgrade my Weewx 4.10 to Weewx 5.0.x.
I reverted "temporarily" to 4.10 and decided to make a fresh install on a
spare set Pi4 + SDR stick.
I installed RTL_433 and sdr-rtl following the
https://github.com/w
Contents of several files to complete the previous post:
/etc/default/weewx :
WEEWX_PYTHON=python3
WEEWX_BINDIR=/usr/share/weewx
/etc/systemd/system/weewx.service :
no file named weewx.service
/etc/init.d/weewx
no file named weewx
PYB
Le mardi 13 février 2024 à 20:31:29 UTC+1, Pierre-Yves
I suggest you try to get weewx and your webserver working using the
Simulator driver first before trying to get the RTL/SDR configuration
working.
--
You received this message because you are subscribed to the Google Groups
"weewx-user" group.
To unsubscribe from this group and stop receiving
Thanks Vince for feedback.
Weewx and webserver are perfectly working in simulator mode with "sudo
systemctl start weewx" command
Feb 13 21:28:23 raspberrypi systemd[1]: Started WeeWX.
Feb 13 21:28:23 raspberrypi weewxd[17482]: INFO __main__: Initializing
weewxd version 5.0.2
Feb 13 21:28:23 ras
On Tuesday, February 13, 2024 at 12:31:54 PM UTC-8 Pierre-Yves wrote:
Weewx and webserver are perfectly working in simulator mode with "sudo
systemctl start weewx" command
Good. That means your problem appears to be related to getting weewx as a
non-privileged user to access your RTL-STR hard
Yes
With simulator, ps aux|grep weewxd shows that weewx user exixts...
pi@raspberrypi:~ $ ps aux|grep weewxd
weewx17482 1.0 1.6 52056 32100 ?Ss 21:28 0:06 python3
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
pi 19150 0.0 0.0 7460 592 pts/1S+ 21:38 0:00 g
oops, I meant running as 'weewx' or 'pi' or 'something else'
The reason I'm asking is that your systemctl log shows a sudo error that
means that the account you are trying to use sudo under is not permitted to
do so. The default dpkg installation creates a weewx user and group but
does not
Thanks Vince.
I'll try to find the way to do that
Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit :
> oops, I meant running as 'weewx' or 'pi' or 'something else'
>
> The reason I'm asking is that your systemctl log shows a sudo error that
> means that the account you are trying to
I haven't found any thread related to the creation of weewx user and
group...
PY
Le mardi 13 février 2024 à 22:14:40 UTC+1, Pierre-Yves a écrit :
> Thanks Vince.
> I'll try to find the way to do that
>
> Le mardi 13 février 2024 à 22:05:10 UTC+1, vince a écrit :
>
>> oops, I meant running as 'we
You want to look for 'rtl' or 'sdr' and adding the weewx user to the
appropriate group that has permissions to access the hardware.
https://groups.google.com/g/weewx-user/c/7CIRRoo6Qdk/m/8dwn6EBiAQAJ is one
link. Note that 'plugdev' is correct for that example. We cannot predict
what 'your'
22 matches
Mail list logo
