I have the same sensor so I just did your experiment...
I would agree the sensor seems to now report a model of Acurite-606TX
today, or at least mine does. If you set debug=2 and run weewx you'll see
syslog entries like the following that pretty clearly indicates that the
model isn't known
I think I got things mostly fixed. Here's what I think fixed it.
- started from scratch (multiple times) ended up going with the
Raspberry Pi Lite version
- in the weewx.conf file I have:
[SDR]
driver = user.sdr
cmd = "sudo /usr/local/bin/rtl_433 -M utc -F json"
- Note
you probably have, but it doesn’t hurt reminding: before even considering
weewx, make sure you repeated *all* the installation steps for rtl433, not just
dropped stuff in, and from a blank slate not from an earlier attempt. i have
had to do this several times (migrating hosts), and i have made
Not much luck.
The symlinks sorta worked - but then I was getting errors that showed the
RTL was already being used, it was like it was calling it twice.
I tried putting the full path in the command line in the SDR section of the
weewx.conf. That made weewx produce no errors, but nothing was
Just for a test, try putting a symlink in /usr/bin that points to the
binary's location in /usr/local/bin and see if that helps any.
sudo ln -s /usr/local/bin/rtl_433 /usr/bin/rtl_433
Normally I'd suggest putting the pathname to the binary in whatever config
file is defining it (weewx.conf
pi@raspberrypi:~ $ which rtl_433
/usr/local/bin/rtl_433
pi@raspberrypi:~ $ sudo which rtl_433
/usr/local/bin/rtl_433
>
>
--
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
Quick guess is $PATH for the boot sequence script does not include the path
to find the rtl_433 executable.
Where is your rtl_433 executable located in the filesystem ?
Try:
- which rtl_433
- sudo which rtl_433
And let us see what those commands return
--
You received this message
