Anyone successfully running weewx with weewx-sdr?

234 views
Skip to first unread message

Charlie T

unread,
Mar 2, 2024, 3:42:14 PM3/2/24
to weewx-user
I have a mystery problem.....weewx runs fine in simulator mode and updates the html file regularly.  When I switch to using weewx-sdr I can see weewx call rtl_433 but the html file stops updating.  No errors posted in the messages file as shown below.  I'm thinking this is a configuration issue....somewhere?

/var/log/messages:

Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Initializing weewxd version 5.0.2
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Using Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Located at /usr/bin/python3
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Platform Linux-6.1.21-v7+-armv7l-with-glibc2.31
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Locale: 'en_US.UTF-8'
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Entry path: /usr/share/weewx/weewxd.py
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: WEEWX_ROOT: /etc/weewx
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Configuration file: /etc/weewx/weewx.conf
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: User module: /etc/weewx/bin/user
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO __main__: Debug: 1
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.engine: Loading station type SDR (user.sdr)
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO user.sdr: driver version is 0.87
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO user.sdr: model is SDR
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO user.sdr: sensor map is {}
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO user.sdr: deltas is {'rain': 'rain_total', 'strikes': 'strikes_total'}
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO user.sdr: startup process 'rtl_433 -M utc -F json -R 40'
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.engine: StdConvert target unit is 0x1
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.wxservices: StdWXCalculate will use data binding wx_binding
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.engine: Archive will use data binding wx_binding
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.engine: Record generation will be attempted in 'hardware'
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.engine: Using archive interval of 300 seconds (specified in weewx configuration)
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: StationRegistry: Registration not requested.
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: Wunderground: Posting not enabled.
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: PWSweather: Posting not enabled.
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: CWOP: Posting not enabled.
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: WOW: Posting not enabled.
Mar  2 09:40:25 raspberrypi weewxd[21061]: INFO weewx.restx: AWEKAS: Posting not enabled.
pi@raspberrypi:/var/log $



an oldman

unread,
Mar 2, 2024, 3:55:04 PM3/2/24
to weewx-user
yes
fedora 36
WeeWX version: 5.0.2
Seasons version: 5.0.2
Python version: 3.10.11
had to add weewx user to rtlsdr group so weewx could use it

Tom Keffer

unread,
Mar 2, 2024, 3:57:05 PM3/2/24
to weewx-user
You should check /var/log/syslog, not /var/log/messages. The latter usually does not include debug messages.)

This is almost surely a permissions problem. There are many threads on this topic. For example, this one. In that case, adding user weewx to group "plugdev" solved the problem:

sudo usermod -aG plugdev weewx

Also, see  the wiki article Understanding permissions. Pay particular attention to the section How to fix device permissions.

Charlie T

unread,
Mar 2, 2024, 4:57:55 PM3/2/24
to weewx-user
OK...well that's strange.  /var/log/syslog is NOT updating.  Even with a "chmod 777 syslog"...still no updates to syslog.

-Charlie

matthew wall

unread,
Mar 2, 2024, 5:14:06 PM3/2/24
to weewx-user
On Saturday, March 2, 2024 at 11:57:55 AM UTC-5 Charlie T wrote:
OK...well that's strange.  /var/log/syslog is NOT updating.  Even with a "chmod 777 syslog"...still no updates to syslog.

in general, redhat systems use /var/log/messages, debian systems use /var/log/syslog

systems that use systemd might swallow some or all of the system logging into systemd-journald, leaving you with nothing in /var/log/syslog or /var/log/messages.  if you are on one of those systems, then you'll have to use journalctl to view the log messages.

if you want to see the contents of /var/log/messages or /var/log/syslog without having to escalate privileges, you should change the permissions in the rsyslog configuration (/etc/rsyslog.conf) and/or logrotate configuration. i do not recall whether this is possible on systemd systems that have hijacked *all* of the system logging into journald.

your 'chmod 777' will go away at the next log rotation and/or rsyslog restart, and you really don't want to give world write privileges on system files like that anyway.

Tom Keffer

unread,
Mar 2, 2024, 8:00:21 PM3/2/24
to weewx...@googlegroups.com
m: He is on a Raspberry Pi

--
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/d35daf5a-9027-4eed-8957-03b153554bd9n%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages