Thanks Bob, I'll follow your advice from now on to regularly clear the
console data buffer.
btw, any particular reason why you recommended (in another thread) the 5
minute setting of the buffer as opposed to any other?
--
You received this message because you are subscribed to the Google Group
One more question if I may: I tried searching but I couldn't find
explanation why the loop data doesn't report the battery status?!
--
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,
Your problem is that you have deleted the column rxCheckPercent from your
database. I'm guessing your driver does not include the field in the
packets/records it emits so when the template attempts to process
rxCheckPercent it fails (rxCheckPercent cannot be found in the current
archive record
On Tuesday, January 23, 2024 at 10:49:43 PM UTC-5 joev...@gmail.com wrote:
My upgrade from 4.10 to 5.0 on my laptop, i.e. not connected to a real
weather station thus running with the simulator device, has actually gone
very nicely but for one puzzling report. I thought installing on my laptop
On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote:
if you saw that v5 was running as root:root, that means you must have
deleted /var/lib/weewx, or changed its permissions. could you verify this?
i mistyped. that line should have said:
if you saw that v5 was running as
Unfortunately the interface from the Bresser PC console doesn't include the
battery status - so not provided because its not available (i wish it was,
a silly oversight)
Why 5 minute intervals ... it seems a sensible compromise of providing
useful data while not filling the disk up too rapidly
OK, I changed user and group to root in /etc/weewx/systemd/weewx.service,
weewx now starts with port 80 and interceptor driver. But nevermind which
option I use - observer or wu-client - I always get:
weewxd[27966]: DEBUG user.interceptor: empty queue
But I found this wiki article
-> https://
Hi to all and many thanks to creators and to all that contribute to have
the best weather software by far
I have already running weewx 4.10.2 (2 stations , one sdr and the other
gw1000) with no problem at all and i am very happy . Today i had free time
so i decided to try an installation in an
As always, look up your exact error message "NO_PUBKEY ED444FCCF0E2B09E" in
the group archives, which points you to.
https://groups.google.com/g/weewx-user/c/AJlPGe61xVU/m/AuOh3oiZAAAJ
Looks like the keys.html file mentioned in the docs still has issues. I
got this error too on a clean de
Lets see your systemd service file.
On Wednesday, January 24, 2024 at 9:46:50 AM UTC-8 Tomasz Lewicki wrote:
> OK, I changed user and group to root in /etc/weewx/systemd/weewx.service,
> weewx now starts with port 80 and interceptor driver. But nevermind which
> option I use - observer or
Here it comes:
# systemd service configuration file for WeeWX
[Unit]
Description=WeeWX
Documentation=https://weewx.com/docs
Requires=time-sync.target
After=time-sync.target
[Service]
ExecStart=weewxd /etc/weewx/weewx.conf
StandardOutput=null
StandardError=journal+console
RuntimeDirectory=weewx
R
Matthew,
answers to above:
1) located in /usr/lib/systemd/system I have these two:
-rw-r--r--. 1 root root 368 Jan 21 12:18 weewx.service
-rw-r--r--. 1 root root 876 Jan 21 12:18 weewx@.service
2) located in xps13-9305:/etc/systemd/system/multi-user.target.wants/ I
have the following but
Previously I had strange problems with Python but finally I realized that I
have Python2 and Python3 installed. When I called commands begining with
'python', v2 was started. But 'sudo update-alternatives --install
/usr/bin/python python /usr/bin/python3 10' has made the trick:
pi@meteo:~ $ pyt
Matthew,
I might have included this information:
drwxr-xr-x. 1 weewx weewx 578 Jan 23 18:15 .
drwxr-xr-x. 1 root root 6320 Jan 23 12:06 ..
drwxr-xr-x. 1 weewx weewx 8 Jan 19 18:36 bin
drwxr-xr-x. 1 weewx weewx 160 Jan 21 12:18 examples
drwxr-xr-x. 1 weewx weewx 178 Jan 21 12:18 imp
Just a thought, but interceptor is 'listening' on port 80. Don't you need
to configure your hardware to 'send' to port 80 on your weewx computer ?
On Wednesday, January 24, 2024 at 11:39:31 AM UTC-8 Tomasz Lewicki wrote:
> Previously I had strange problems with Python but finally I realized tha
Oh 😱 ..!! First of all thank you for the quick reply ... The truth is that
i made several searches but not with the key value ..!! I apologise for
that !!
Also Something else ... a question to Gary ...
In weewx saratoga extension the wind and wind gust are always the same ..
probably the extensio
Matthew,
Ooops, i neglected my other response:
I neglected that detail, I did delete the directory /var/lib/weewx and
the database therein. I did not change the directory /etc/weewx and I
noticed that when I ran dnf install weewx it updated the ownership and
group of that directory and f
I see I didn't reference the container of the list of files above; the
directory is /etc/weewx/
On Wednesday, January 24, 2024 at 2:57:22 PM UTC-5 Joseph Verreau wrote:
> Matthew,
> Ooops, i neglected my other response:
>I neglected that detail, I did delete the directory /var/lib/weewx
By hardware do you mean WiFi console from my weather station? If yes, it
has very simple (almost none) configuration. It sends weather data to WU
only. But I hijacked DNS on my router:
pi@meteo:~ $ rtupdate.wunderground.com
PING rtupdate.wunderground.com (192.168.0.106) 56(84) bytes of data.
64
You need something to send traffic to intercept. Run wireshark on your
weewx computer and listen on port 80 and see if your computer is hearing
anything (and what). If it's http the payload should be decipherable.
On Wednesday, January 24, 2024 at 12:01:31 PM UTC-8 Tomasz Lewicki wrote:
> B
On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 joev...@gmail.com wrote:
3) xps13-9305:/etc/init.d# grep weewx /etc/passwd
weewx:x:971:960::/home/weewx:/sbin/nologin
it looks like your 'weewx' user has uid 971, and it is in group '960'. it
also has home directory '/home/weewx', which tell
The log is from latest logs I posted are from b5. Sorry, I forgot to
mention that I didn't use the file in your link above, I downloaded from
the releases, and for b4 it says: removed, go for b5. b5 is producing two
independent LOOP packets after a few on my RPi4.
gjr80 schrieb am Mittwoch, 24.
I used command line version of Wireshark - Tshark - and collected packets
for 15 minutes. Then loaded the PCAP file into Wireshark and filtered by
source IP of weather station console. Every 2 seconds I see:
b8 27 eb dd 86 34 08 d8 33 53 93 a9 08 00 45 00 .'...4..3SE.
0010 00 90
My mistake. These packets were captured when Weewx was running with HP1000
driver. When I changed the driver to interceptor, I didn't captured *any*
packets from WiFi console. I don't understand it...
środa, 24 stycznia 2024 o 21:06:53 UTC+1 vince napisał(a):
> You need something to send traffic
Stop weewx. Just run the packet capture and post the .pcap file so others
can take a look please. Be sure to capture only tcp/80. Compress the
pcap file if it's large or post it someplace online where others can
download it.
The gui version of wireshark is much easier to understand.
On Wed
On Thursday 25 January 2024 at 06:56:42 UTC+10 michael.k...@gmx.at wrote:
The log is from latest logs I posted are from b5. Sorry, I forgot to
mention that I didn't use the file in your link above, I downloaded from
the releases, and for b4 it says: removed, go for b5. b5 is producing two
inde
I attach PCAP file with packets captured for 120 seconds. TCP/80 only.
Weewx was shut down. No traffic on this port until I manually have done the
operation described in one of me previous posts (browser
query): https://groups.google.com/g/weewx-user/c/O8DTjzeeQcg/m/psrDaMHoAAAJ
środa, 24 styc
Just one more thought. Maybe interceptor driver is "too new" for my WiFi
console? Maybe I should try some older version? But unfortunately I don't
see any releases on driver's GitHub page
(https://github.com/matthewwall/weewx-interceptor).
środa, 24 stycznia 2024 o 22:22:37 UTC+1 vince napisał(
Difficult to answer with no info from you on exactly 'what' command you ran
for wireshark and whether your listening computer is wifi, ethernet, or
both. What kind of computer are you running on ? What os ? What version
? Which interfaces ? What was your 'exact' wireshark command ?
But I s
Ahh, so the console shows the battery status but it doesn't send the
message anywhere and it can't be read?
Alright, thanks for all the clarifications.
On Wednesday, January 24, 2024 at 7:38:20 PM UTC+2 Bob Atchley wrote:
> Unfortunately the interface from the Bresser PC console doesn't includ
Matthew,
actually I was afraid to create either user or group manually as I was
not confident about whether there might be specifications I was not
familiar with thus both the user and group resulted when I first deleted
the directory /var/lib/weewx then ran dnf install weewx following the
... none of that is to say I didn't get something else wrong in the
install.
joev.mi
_ _ _ _ _ _ _ _ _ _
On Wednesday, January 24, 2024 at 5:34:18 PM UTC-5 Joseph Verreau wrote:
> Matthew,
> actually I was afraid to create either user or group manually as I was
> not confident about wheth
... are you suggesting my plan to delete /var/lib/weewx and then erase
weewx 4.10 then following the instructions to install v5 should work? I
believe I can save the database and re-add it after installing.
joev.mi
_ _ _ _ _ _ _ _ _ _
--
You received this message because you are subscribed
Is anyone else having problems with aeris forcasting? For the past few
weeks my access credits have been running out resulting in my webpage not
being updated. I've turned off forcasting in weewx.conf and when I watch
my activity on aeris the hits keep coming. I don't know who is making
thes
i think i was mistaken about dnf not creating the weewx user. i thought we
had implemented useradd so that the HOME for a new weewx user is
/var/lib/weewx, but apparently we did that for debian, but not for
redhat/suse. i will fix that. however, that is not relevant to your
problem.
anyway,
Nope. Steady here.
Guessing you posted your forecast id and secret key somewhere at sometime
in the past. You might try going
to https://account.aerisweather.com/account/apps and registering a new app
there to use that in your weewx.conf (and disable your old app registration
via the aeris d
On Wednesday, January 24, 2024 at 12:48:33 PM UTC-5 stefanos...@gmail.com
wrote:
The following signatures couldn't be verified because the public key is
not available: NO_PUBKEY ED444FCCF0E2B09E
Reading package lists... Done
W: GPG error: https://weewx.com/apt/python3 buster InRelease: The fol
On Tuesday, January 23, 2024 at 3:24:13 PM UTC-5 ken.r...@gmail.com wrote:
That's why I wondered if the hub needs to have it registered, but you say
that the hub should pick up everything within range regardless,
Anything else I could try?
the smarthub/bridge is pretty dumb - just a relay. tha
Matthew,
that I can do. thank you for your time and very prompt responses.
joev.mi
_ _ _ _ _ _ _ _ _ _
On Wednesday, January 24, 2024 at 7:42:25 PM UTC-5 matthew wall wrote:
> i think i was mistaken about dnf not creating the weewx user. i thought
> we had implemented useradd so that the
I've done that. Should have mentioned in original post. I've changed my
password, deleted and created a new app. My hit count reset at 1900EST and
within an hour I was at ~600 hits, and that's with forcasting turned off in
the conf file. Aeris tech support has not been able to solve this. I
40 matches
Mail list logo
