This is a fresh install of weewx 4.10 on a Raspberry Pi running Debian
bullseye. I'd had weewx 3.1.running since c.2015 on an older Pi with a much
older Debian, and finally upgraded everything to current releases.
If I run the executable (weewxd) from the shell in the foreground, it runs
fine a
tl --no-pager start weewx.service
Nothing in /var/log/syslog, either.
On Thursday, February 9, 2023 at 9:19:54 PM UTC-7 vince wrote:
> On Thursday, February 9, 2023 at 7:26:57 PM UTC-8 phxroa...@gmail.com
> wrote:
> If it helps I can post whatever log files would be helpful.
>
> We
When run in the foreground it's just "sudo weewxd". The output is, as
expected, lots of LOOP msgs, e.g.:
LOOP: 2023-02-13 14:02:25 MST (1676322145) 'altimeter':
'29.69994054581585', 'appTemp': '31.6819209717981', 'barometer': '29.744',
'cloudbase': '8389.073423533182', 'consBatteryVoltage': '
Ah, good thought. I didn't consider permissions. Unfortunately, it was
already 755:
pi@raspberrypi:~ $ ls -l /etc/init.d/weewx
-rwxr-xr-x 1 root root 5111 Oct 25 04:29 /etc/init.d/weewx
The more I think about this the more it feels like whoever developed the
script was on a system with some pac
The init.d style of startup is what I was familiar with back in my
pre-retirement days, so that's what I've been concentrating on. Probably
time I should learn the other style, though!
On Monday, February 13, 2023 at 4:11:33 PM UTC-7 Tom Keffer wrote:
> Why not dispose of the init.d script and
I'm having trouble getting my system (Vue sensor package, regular Davis
console, weewx on a Raspberry Pi) to use transmitter channel 2.
My station, installed several years ago, has some new neighbors. To avoid
all of us using the default channel 1, I changed mine to use channel 2. I
changed the
ce
>
> Note: the above is written with the weewx 5 command weectl. You’ll have
> to substitute wee_device for weectl.
>
>
>
> On Sep 13, 2025, at 1:19 PM, phxroa...@gmail.com
> wrote:
>
>
>
> I'm having trouble getting my system (Vue sensor package, reg
