[weewx-user] Re: Aeris forcast with belchertown

[bchap...@gmail.com]

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'm 
thinking I may need to delete my account with them and re-create a new 
one.  

On Wednesday, January 24, 2024 at 7:38:45 PM UTC-5 bchap...@gmail.com wrote:

> 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 
> these requests.  My aeris credits are racking up at an average of a few 
> hundred an hour, even with forcasting turned off.  I've contacted aeris 
> tech support which has not been helpful.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/81cd0958-11b9-41ec-9ad4-e225751a18e8n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 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, i am an idiot.
>
> if you look at the rules file, you will see that it is incorrect.  instead 
> of this:
>
> GROUP="weewx"
>
> we see this:
>
> GROUP="{weewx}"
>
> that is because there is a bug in the suse and redhat scriptlets that does 
> an incorrect substitution.
>
> fixed at commit b32ca406, to appear real-soon-now in 5.0.1
>
> meanwhile, you can fix it by editing /usr/lib/udev/rules.d/60-weewx.rules
>
> replace "{weewx}" with "weewx"
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8e77a62e-aabf-444a-8026-cbc99683a40dn%40googlegroups.com.

[weewx-user] Re: Aucrite sensor stopped working - does it need re-registration?

[matthew wall]

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. that made it very nice 
to work with and reverse engineer!

you might try power cycling the hub.  or try removing the batteries from 
your sensor, change the channel switch, then insert batteries. weewx uses 
only the identifier, not the channel, to figure out which sensor is which. 
but perhaps the hub gets confused...

i only ever tried multiple T/H sensors, never multiple weather stations or 
T/H/P sensors.  if you have more than one sensor sending a pressure, then 
maybe the smarthub/bridge is confusing/aggregating them?

also, beware the dark arts of radio frequencies.  i've had sensors 
disappear when they were a meter from a receiver, only to appear when moved 
a little bit further away.  some receiver antennas have lobes that result 
in blind spots.

m

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8b461052-d32a-4abe-a693-aa6f420c435en%40googlegroups.com.

[weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

[matthew wall]

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 following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY ED444FCCF0E2B09E


sorry about that.  i rearranged the key files before i finished the rest of 
the release.  keys have been restored.

for future reference: the current keys will always be in 
https://weewx.com/keys.html, while all of the keys (current and all 
previous keys) will be in https://weewx.com/keys-old.html.  if you need to 
install an older deb/rpm that was signed by an older key, use keys-old.  
use keys.html for recent systems, since they will probably reject the older 
keys we used to sign things before 2024.

m

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/39e925bb-a4f0-4b35-9b0c-03cc0364f717n%40googlegroups.com.

[weewx-user] Re: Aeris forcast with belchertown

[vince]

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 dashboard).

On Wednesday, January 24, 2024 at 4:38:45 PM UTC-8 bchap...@gmail.com wrote:

> 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 
> these requests.  My aeris credits are racking up at an average of a few 
> hundred an hour, even with forcasting turned off.  I've contacted aeris 
> tech support which has not been helpful.
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e25302e9-ce36-44ba-bcab-7be15bc9c661n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[matthew wall]

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, i am an idiot.

if you look at the rules file, you will see that it is incorrect.  instead 
of this:

GROUP="weewx"

we see this:

GROUP="{weewx}"

that is because there is a bug in the suse and redhat scriptlets that does 
an incorrect substitution.

fixed at commit b32ca406, to appear real-soon-now in 5.0.1

meanwhile, you can fix it by editing /usr/lib/udev/rules.d/60-weewx.rules

replace "{weewx}" with "weewx"

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/0c7f6e0f-890f-40ae-af43-2d77abd39756n%40googlegroups.com.

[weewx-user] Aeris forcast with belchertown

[bchap...@gmail.com]

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 
these requests.  My aeris credits are racking up at an average of a few 
hundred an hour, even with forcasting turned off.  I've contacted aeris 
tech support which has not been helpful.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8787f686-28fb-4373-9537-5127901fee78n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

... 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 to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/72c497f1-2b9f-48e0-9e6c-9a02aba148c7n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

... 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 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 
> install instructions for fedora 34+.  I had checked both passwd and group 
> prior to running the install and the user and group were not present.
> from grep weewx /etc/group I get:
> xps13-9305:~$ grep weewx /etc/group
> weewx:x:960:
>
> @xps13-9305:~$ ll /etc/group
> -rw-r--r--. 1 root root 1296 Jan 21 12:18 /etc/group
> @xps13-9305:~$ ll /etc/passwd
> -rw-r--r--. 1 root root 3400 Jan 21 12:18 /etc/passwd
> @xps13-9305:~$ sudo dnf history list weewx
> ID | Command line 
>   | Date and time| Action(s)  | 
> Altered
>
> -
>668 | install weewx 
>  | 2024-01-21 12:18 | Install| 
>5   
>
> joev.mi
> _ _ _ _ _ _ _ _ _ _
>
> On Wednesday, January 24, 2024 at 3:29:51 PM UTC-5 matthew wall wrote:
>
>> 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 tells me that this weewx 
>> user was not created by the weewx v5 installer and dnf.
>>
>> what do you get from this:
>>
>> grep weewx /etc/group
>>
>>  
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/49d04929-bc9a-45e9-a0a5-da60d1447389n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 
install instructions for fedora 34+.  I had checked both passwd and group 
prior to running the install and the user and group were not present.
from grep weewx /etc/group I get:
xps13-9305:~$ grep weewx /etc/group
weewx:x:960:

@xps13-9305:~$ ll /etc/group
-rw-r--r--. 1 root root 1296 Jan 21 12:18 /etc/group
@xps13-9305:~$ ll /etc/passwd
-rw-r--r--. 1 root root 3400 Jan 21 12:18 /etc/passwd
@xps13-9305:~$ sudo dnf history list weewx
ID | Command line   
| Date and time| Action(s)  | 
Altered
-
   668 | install weewx 
 | 2024-01-21 12:18 | Install| 
   5   

joev.mi
_ _ _ _ _ _ _ _ _ _

On Wednesday, January 24, 2024 at 3:29:51 PM UTC-5 matthew wall wrote:

> 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 tells me that this weewx user 
> was not created by the weewx v5 installer and dnf.
>
> what do you get from this:
>
> grep weewx /etc/group
>
>  
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b08d0ab3-ea98-4ed0-9b41-b815dd87af97n%40googlegroups.com.

Re: [weewx-user] Re: Why the rain 'spikes'?

[Ξ]

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 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 (the console itself 
> does 12 second updates), but recording at the same interval that weewx is 
> putting data into the database seems a good compromise.
>
> Hope this helps
>
> Bob
>
> On Wednesday 24 January 2024 at 08:35:25 UTC Ξ wrote:
>
>> 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, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/957be799-f737-48a0-94c7-e6cc891e5b26n%40googlegroups.com.

[weewx-user] Re: Driver permission error when starting Weewx

[vince]

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 see nothing basically in that 6-second pcap.  If running a sniffer on 
your computer sees no traffic being redirected from the station, then there 
is nothing for interceptor to intercept on the weewx computer.

Again, when you say "*But I hijacked DNS on my router*" that (to me) does 
not cause any traffic from your station to wunderground to be redirected to 
your weewx system unless I'm not understanding what you're saying.  Perhaps 
you should tell everybody what your system config is so those who do 
interceptor can try to help more. 

On Wednesday, January 24, 2024 at 1:38:25 PM UTC-8 Tomasz Lewicki wrote:

> 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 stycznia 2024 o 22:22:37 UTC+1 vince napisał(a):
>
>> 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 Wednesday, January 24, 2024 at 1:16:50 PM UTC-8 Tomasz Lewicki wrote:
>>
>>> 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 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:

> 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
> ttl=64 time=0.130 ms
> 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
> ttl=64 time=0.128 ms
>
> pi@meteo:~ $ dig rtupdate.wunderground.com
>
> ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> 
> rtupdate.wunderground.com
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;rtupdate.wunderground.com. IN A
>
> ;; ANSWER SECTION:
> rtupdate.wunderground.com. 0 IN A 192.168.0.106
>
> ;; Query time: 170 msec
> ;; SERVER: 192.168.0.10#53(192.168.0.10)
> ;; WHEN: śro sty 24 20:59:32 CET 2024
> ;; MSG SIZE  rcvd: 70
>
> I even updated console's firmware to the latest available version from 
> Ambient Weather website. In server.ini file I see only this:
>
> [Menu]
> default=www.wunderground.com
> web=1
> web1=www.wunderground.com
>
> [www.wunderground.com]
> Server=rtupdate.wunderground.com
> ServerType=php
> ServerPort=80
> UploadType=Customize
> ReadOnly=true
> środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):
>
>> 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 
>>> 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:~ $ python --version
>>> Python 3.7.3
>>>
>>>
>>> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>>>
 Here it comes:

 # systemd service configuration file for WeeWX

 [Unit]
 Description=WeeWX
 Documentation=https://weewx.com/docs

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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ł(a):

> 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 Wednesday, January 24, 2024 at 1:16:50 PM UTC-8 Tomasz Lewicki wrote:
>
>> 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 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:
>>>
 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
 ttl=64 time=0.130 ms
 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
 ttl=64 time=0.128 ms

 pi@meteo:~ $ dig rtupdate.wunderground.com

 ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> 
 rtupdate.wunderground.com
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 1232
 ;; QUESTION SECTION:
 ;rtupdate.wunderground.com. IN A

 ;; ANSWER SECTION:
 rtupdate.wunderground.com. 0 IN A 192.168.0.106

 ;; Query time: 170 msec
 ;; SERVER: 192.168.0.10#53(192.168.0.10)
 ;; WHEN: śro sty 24 20:59:32 CET 2024
 ;; MSG SIZE  rcvd: 70

 I even updated console's firmware to the latest available version from 
 Ambient Weather website. In server.ini file I see only this:

 [Menu]
 default=www.wunderground.com
 web=1
 web1=www.wunderground.com

 [www.wunderground.com]
 Server=rtupdate.wunderground.com
 ServerType=php
 ServerPort=80
 UploadType=Customize
 ReadOnly=true
 środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):

> 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 
>> 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:~ $ python --version
>> Python 3.7.3
>>
>>
>> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>>
>>> 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
>>> RuntimeDirectoryMode=775
>>> User=root
>>> Group=root
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>>>
 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 
> wu-client - I always get:
>
> weewxd[27966]: DEBUG user.interceptor: empty queue
>
> But I found this wiki article -> 
> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
> 

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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 stycznia 2024 o 22:22:37 UTC+1 vince napisał(a):

> 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 Wednesday, January 24, 2024 at 1:16:50 PM UTC-8 Tomasz Lewicki wrote:
>
>> 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 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:
>>>
 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
 ttl=64 time=0.130 ms
 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
 ttl=64 time=0.128 ms

 pi@meteo:~ $ dig rtupdate.wunderground.com

 ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> 
 rtupdate.wunderground.com
 ;; global options: +cmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

 ;; OPT PSEUDOSECTION:
 ; EDNS: version: 0, flags:; udp: 1232
 ;; QUESTION SECTION:
 ;rtupdate.wunderground.com. IN A

 ;; ANSWER SECTION:
 rtupdate.wunderground.com. 0 IN A 192.168.0.106

 ;; Query time: 170 msec
 ;; SERVER: 192.168.0.10#53(192.168.0.10)
 ;; WHEN: śro sty 24 20:59:32 CET 2024
 ;; MSG SIZE  rcvd: 70

 I even updated console's firmware to the latest available version from 
 Ambient Weather website. In server.ini file I see only this:

 [Menu]
 default=www.wunderground.com
 web=1
 web1=www.wunderground.com

 [www.wunderground.com]
 Server=rtupdate.wunderground.com
 ServerType=php
 ServerPort=80
 UploadType=Customize
 ReadOnly=true
 środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):

> 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 
>> 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:~ $ python --version
>> Python 3.7.3
>>
>>
>> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>>
>>> 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
>>> RuntimeDirectoryMode=775
>>> User=root
>>> Group=root
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>>>
 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 
> wu-client - I always get:
>
> weewxd[27966]: DEBUG user.interceptor: empty queue
>
> But I found this wiki article -> 
> 

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

[gjr80]

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 
independent LOOP packets after a few on my RPi4.


Sorry, but I don't understand this. The latest log you posted yesterday is 
very clearly from b4:

2024-01-23 19:46:51 weewxd[232660] INFO weewx.engine: Loading station type 
GW1000 (user.gw1000) 
2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: GatewayDriver: version 
is 0.6.0b4 
2024-01-23 19:46:51 weewxd[232660] INFO user.gw1000: device address is 
10.0.1.85:45000

b4 and b5 have not been published to releases, they have been produced to 
deal with this issue and I have kept them back until I know the issue is 
fixed. You need to re-download the driver from the link I provided earlier 
in order to get b5, b3 (releases) and b4 will never work. Here is the link 
again:

https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py

Gary

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/6c2192cf-0406-4e08-9e75-d354b0c68c54n%40googlegroups.com.

[weewx-user] Re: Driver permission error when starting Weewx

[vince]

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 Wednesday, January 24, 2024 at 1:16:50 PM UTC-8 Tomasz Lewicki wrote:

> 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 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:
>>
>>> 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
>>> ttl=64 time=0.130 ms
>>> 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
>>> ttl=64 time=0.128 ms
>>>
>>> pi@meteo:~ $ dig rtupdate.wunderground.com
>>>
>>> ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> rtupdate.wunderground.com
>>> ;; global options: +cmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
>>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>>
>>> ;; OPT PSEUDOSECTION:
>>> ; EDNS: version: 0, flags:; udp: 1232
>>> ;; QUESTION SECTION:
>>> ;rtupdate.wunderground.com. IN A
>>>
>>> ;; ANSWER SECTION:
>>> rtupdate.wunderground.com. 0 IN A 192.168.0.106
>>>
>>> ;; Query time: 170 msec
>>> ;; SERVER: 192.168.0.10#53(192.168.0.10)
>>> ;; WHEN: śro sty 24 20:59:32 CET 2024
>>> ;; MSG SIZE  rcvd: 70
>>>
>>> I even updated console's firmware to the latest available version from 
>>> Ambient Weather website. In server.ini file I see only this:
>>>
>>> [Menu]
>>> default=www.wunderground.com
>>> web=1
>>> web1=www.wunderground.com
>>>
>>> [www.wunderground.com]
>>> Server=rtupdate.wunderground.com
>>> ServerType=php
>>> ServerPort=80
>>> UploadType=Customize
>>> ReadOnly=true
>>> środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):
>>>
 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 
> 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:~ $ python --version
> Python 3.7.3
>
>
> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>
>> 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
>> RuntimeDirectoryMode=775
>> User=root
>> Group=root
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>>
>>> 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 
 wu-client - I always get:

 weewxd[27966]: DEBUG user.interceptor: empty queue

 But I found this wiki article -> 
 https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
 interceptor driver from command line:

 sudo PYTHONPATH=/usr/share/weewx python 
 /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
 --mode=listen

 Then - exactly  as this part of article says -> 
 https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
  
 I pasted to browser such query:


 

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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 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:
>
>> 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
>> ttl=64 time=0.130 ms
>> 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
>> ttl=64 time=0.128 ms
>>
>> pi@meteo:~ $ dig rtupdate.wunderground.com
>>
>> ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> rtupdate.wunderground.com
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 1232
>> ;; QUESTION SECTION:
>> ;rtupdate.wunderground.com. IN A
>>
>> ;; ANSWER SECTION:
>> rtupdate.wunderground.com. 0 IN A 192.168.0.106
>>
>> ;; Query time: 170 msec
>> ;; SERVER: 192.168.0.10#53(192.168.0.10)
>> ;; WHEN: śro sty 24 20:59:32 CET 2024
>> ;; MSG SIZE  rcvd: 70
>>
>> I even updated console's firmware to the latest available version from 
>> Ambient Weather website. In server.ini file I see only this:
>>
>> [Menu]
>> default=www.wunderground.com
>> web=1
>> web1=www.wunderground.com
>>
>> [www.wunderground.com]
>> Server=rtupdate.wunderground.com
>> ServerType=php
>> ServerPort=80
>> UploadType=Customize
>> ReadOnly=true
>> środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):
>>
>>> 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 
 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:~ $ python --version
 Python 3.7.3


 środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):

> 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
> RuntimeDirectoryMode=775
> User=root
> Group=root
>
> [Install]
> WantedBy=multi-user.target
>
> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>
>> 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 
>>> wu-client - I always get:
>>>
>>> weewxd[27966]: DEBUG user.interceptor: empty queue
>>>
>>> But I found this wiki article -> 
>>> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
>>> interceptor driver from command line:
>>>
>>> sudo PYTHONPATH=/usr/share/weewx python 
>>> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
>>> --mode=listen
>>>
>>> Then - exactly  as this part of article says -> 
>>> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>>>  
>>> I pasted to browser such query:
>>>
>>>
>>> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>>
>>> And I got an answer in terminal:
>>>
>>> raw data: 
>>> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
>>> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
>>> raw data: 
>>> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
>>> mapped packet: {'dateTime': 1706118216, 

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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 1b 12 00 00 80 06 9d 2a c0 a8 00 71 c0 a8   .*...q..
0020   00 6a c0 08 19 64 e3 81 0c 05 7e 63 ac 14 50 18   .j...d~c..P.
0030   00 44 fc 9d 00 00 48 50 32 30 30 30 00 00 57 52   .DHP2000..WR
0040   49 54 45 00 00 00 4e 4f 57 52 45 43 4f 52 44 00   ITE...NOWRECORD.
0050   00 00 00 00 00 00 68 00 00 00 8a 00 00 00 c5 00   ..h.
0060   2f 3d 33 33 b3 41 33 d3 73 44 00 c0 7d 44 9a 99   /=33.A3.sD..}D..
0070   e9 40 9a 99 99 3e 9a 99 e9 40 00 00 00 00 00 00   .@...>...@..
0080   00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00   
0090   00 00 00 00 00 00 00 00 00 00 00 ff 00 00 ..

But I don't know if it makes any sense :)   

środa, 24 stycznia 2024 o 21:06:53 UTC+1 vince napisał(a):

> 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:
>
>> 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
>> ttl=64 time=0.130 ms
>> 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
>> ttl=64 time=0.128 ms
>>
>> pi@meteo:~ $ dig rtupdate.wunderground.com
>>
>> ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> rtupdate.wunderground.com
>> ;; global options: +cmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>
>> ;; OPT PSEUDOSECTION:
>> ; EDNS: version: 0, flags:; udp: 1232
>> ;; QUESTION SECTION:
>> ;rtupdate.wunderground.com. IN A
>>
>> ;; ANSWER SECTION:
>> rtupdate.wunderground.com. 0 IN A 192.168.0.106
>>
>> ;; Query time: 170 msec
>> ;; SERVER: 192.168.0.10#53(192.168.0.10)
>> ;; WHEN: śro sty 24 20:59:32 CET 2024
>> ;; MSG SIZE  rcvd: 70
>>
>> I even updated console's firmware to the latest available version from 
>> Ambient Weather website. In server.ini file I see only this:
>>
>> [Menu]
>> default=www.wunderground.com
>> web=1
>> web1=www.wunderground.com
>>
>> [www.wunderground.com]
>> Server=rtupdate.wunderground.com
>> ServerType=php
>> ServerPort=80
>> UploadType=Customize
>> ReadOnly=true
>> środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):
>>
>>> 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 
 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:~ $ python --version
 Python 3.7.3


 środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):

> 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
> RuntimeDirectoryMode=775
> User=root
> Group=root
>
> [Install]
> WantedBy=multi-user.target
>
> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>
>> 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 
>>> wu-client - I always get:
>>>
>>> weewxd[27966]: DEBUG user.interceptor: empty queue
>>>
>>> But I found this wiki article -> 
>>> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
>>> interceptor driver from command line:
>>>
>>> sudo PYTHONPATH=/usr/share/weewx python 
>>> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 

[weewx-user] Re: Running Ecowitt Gateway Driver bith as a driver and a service at the same time?

['michael.k...@gmx.at' via weewx-user]

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. Januar 2024 um 00:01:14 UTC+1:

> It should just work. It works with a dual driver/service implementation on 
> my test VM. 
>
> Gary
>
> On Wednesday 24 January 2024 at 07:50:29 UTC+10 michael.k...@gmx.at wrote:
>
>> I will. Just curious: what to expect from b5? Will it behave differently 
>> or produce other logs?
>>
>> gjr80 schrieb am Dienstag, 23. Januar 2024 um 22:19:27 UTC+1:
>>
>>> Try b5, same link as my previous post to download.
>>>
>>> Gary
>>>
>>> On Wednesday 24 January 2024 at 04:55:16 UTC+10 michael.k...@gmx.at 
>>> wrote:
>>>
 I ran weewxd manually, weewxd_console.log is the console output, 
 weewxd.log is from the log file. 

 gjr80 schrieb am Montag, 22. Januar 2024 um 20:40:14 UTC+1:

> An old log entry remained after some earlier restructuring, try b4:
>
> wget 
> https://raw.githubusercontent.com/gjr80/weewx-gw1000/master/bin/user/gw1000.py
>
> Gary
>
> On Tuesday 23 January 2024 at 04:55:32 UTC+10 michael.k...@gmx.at 
> wrote:
>
>> When I configure like so
>> [GW1000]
>> debug_loop = True
>>
>> # This section is for the Ecowitt Gateway driver.
>> 
>> # How often to poll the API, default is every 20 seconds:
>> poll_interval = 10
>> ip_address = 10.0.1.85
>> max_tries = 360
>> 
>> # The driver to use:
>> driver = user.gw1000
>>
>> [GW1000Service]
>> *debug_loop = True*
>>
>> # This section is for the Ecowitt Gateway driver.
>> 
>> # How often to poll the API, default is every 20 seconds:
>> poll_interval = 10
>> ip_address = 10.0.1.86
>> max_tries = 360
>> 
>> # The driver to use:
>> driver = user.gw1000
>>
>> [[field_map]]
>> ws90_windDir = winddir
>> ws90_windSpeed = windspeed
>> ws90_windGust = gustspeed
>> ws90_daymaxwind = daymaxwind
>> ws90_uvradiation = uv
>> ws90_UV = uvi
>> ws90_luminosity = light
>> p_rain = p_rain
>> p_stormRain = p_rainevent
>> p_rainRate = p_rainrate
>> p_dayRain = p_rainday
>> p_weekRain = p_rainweek
>> p_monthRain = p_rainmonth
>> p_yearRain = p_rainyear
>>
>> WeeWX exits with
>>
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Initializing weewxd 
>> version 5.0.0
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Command line: 
>> /home/pi/weewx-venv/bin/weewxd
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Using Python 3.9.2 
>> (default, Feb 28 2021, 17:03:44)
>> [GCC 10.2.1 20210110]
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Located at 
>> /home/pi/weewx-venv/bin/python3
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Platform 
>> Linux-6.1.42-v8+-aarch64-with-glibc2.31
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Locale: 'de_AT.UTF-8'
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Entry path: 
>> /home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: WEEWX_ROOT: 
>> /home/pi/weewx-data
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Configuration file: 
>> /home/pi/weewx-data/weewx.conf
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: User module: 
>> /home/pi/weewx-data/bin/user
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewxd: Debug: 0
>> 2024-01-22 19:49:48 weewxd[119797] INFO weewx.engine: Loading station 
>> type GW1000 (user.gw1000)
>> 2024-01-22 19:49:48 weewxd[119797] INFO user.gw1000: GatewayDriver: 
>> version is 0.6.0b2
>> 2024-01-22 19:49:48 weewxd[119797] INFO user.gw1000:  device 
>> address is 10.0.1.85:45000
>> 2024-01-22 19:49:48 weewxd[119797] INFO user.gw1000:  poll 
>> interval is 10 seconds
>> 2024-01-22 19:49:48 weewxd[119797] INFO user.gw1000: GatewayService: 
>> version is 0.6.0b2
>> 2024-01-22 19:49:48 weewxd[119797] INFO user.gw1000:  max age of 
>> API data to be used is 60 seconds
>> 2024-01-22 19:49:50 weewxd[119797] INFO user.gw1000: GatewayCollector 
>> thread has been terminated
>> 2024-01-22 19:49:50 weewxd[119797] CRITICAL weewxd: Caught 
>> unrecoverable exception:
>> 2024-01-22 19:49:50 weewxd[119797] CRITICAL weewxd:  
>>  'GatewayService' object has no attribute 'field_map'
>> 2024-01-22 19:49:50 weewxd[119797] CRITICAL weewxd:  
>>  Traceback (most recent call last):
>>
>> 2024-01-22 19:49:50 

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[matthew wall]

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 tells me that this weewx user 
was not created by the weewx v5 installer and dnf.

what do you get from this:

grep weewx /etc/group

 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9853f985-fa97-4835-bf1f-a661aeadd0a9n%40googlegroups.com.

[weewx-user] Re: Driver permission error when starting Weewx

[vince]

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:

> 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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 
> ttl=64 time=0.130 ms
> 64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 
> ttl=64 time=0.128 ms
>
> pi@meteo:~ $ dig rtupdate.wunderground.com
>
> ; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> rtupdate.wunderground.com
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;rtupdate.wunderground.com. IN A
>
> ;; ANSWER SECTION:
> rtupdate.wunderground.com. 0 IN A 192.168.0.106
>
> ;; Query time: 170 msec
> ;; SERVER: 192.168.0.10#53(192.168.0.10)
> ;; WHEN: śro sty 24 20:59:32 CET 2024
> ;; MSG SIZE  rcvd: 70
>
> I even updated console's firmware to the latest available version from 
> Ambient Weather website. In server.ini file I see only this:
>
> [Menu]
> default=www.wunderground.com
> web=1
> web1=www.wunderground.com
>
> [www.wunderground.com]
> Server=rtupdate.wunderground.com
> ServerType=php
> ServerPort=80
> UploadType=Customize
> ReadOnly=true
> środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):
>
>> 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 
>>> 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:~ $ python --version
>>> Python 3.7.3
>>>
>>>
>>> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>>>
 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
 RuntimeDirectoryMode=775
 User=root
 Group=root

 [Install]
 WantedBy=multi-user.target

 środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):

> 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 
>> wu-client - I always get:
>>
>> weewxd[27966]: DEBUG user.interceptor: empty queue
>>
>> But I found this wiki article -> 
>> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
>> interceptor driver from command line:
>>
>> sudo PYTHONPATH=/usr/share/weewx python 
>> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
>> --mode=listen
>>
>> Then - exactly  as this part of article says -> 
>> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>>  
>> I pasted to browser such query:
>>
>>
>> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>
>> And I got an answer in terminal:
>>
>> raw data: 
>> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
>> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
>> raw data: 
>> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
>> mapped packet: {'dateTime': 1706118216, 'usUnits': 1}
>>
>> So it seems that driver is working when called explicitly from 
>> command line. So why I got "empty queue" when started by 'sudo systemctl 
>> start weewx'?
>> wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com 
>> napisał(a):
>>
>>> sudo only issues the command as root.
>>> What is in the service file for user and group?
>>> That is 

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=1 ttl=64 
time=0.130 ms
64 bytes from rtupdate.wunderground.com (192.168.0.106): icmp_seq=2 ttl=64 
time=0.128 ms

pi@meteo:~ $ dig rtupdate.wunderground.com

; <<>> DiG 9.11.5-P4-5.1+deb10u9-Raspbian <<>> rtupdate.wunderground.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48940
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;rtupdate.wunderground.com. IN A

;; ANSWER SECTION:
rtupdate.wunderground.com. 0 IN A 192.168.0.106

;; Query time: 170 msec
;; SERVER: 192.168.0.10#53(192.168.0.10)
;; WHEN: śro sty 24 20:59:32 CET 2024
;; MSG SIZE  rcvd: 70

I even updated console's firmware to the latest available version from 
Ambient Weather website. In server.ini file I see only this:

[Menu]
default=www.wunderground.com
web=1
web1=www.wunderground.com

[www.wunderground.com]
Server=rtupdate.wunderground.com
ServerType=php
ServerPort=80
UploadType=Customize
ReadOnly=true
środa, 24 stycznia 2024 o 20:48:31 UTC+1 vince napisał(a):

> 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 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:~ $ python --version
>> Python 3.7.3
>>
>>
>> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>>
>>> 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
>>> RuntimeDirectoryMode=775
>>> User=root
>>> Group=root
>>>
>>> [Install]
>>> WantedBy=multi-user.target
>>>
>>> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>>>
 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 
> wu-client - I always get:
>
> weewxd[27966]: DEBUG user.interceptor: empty queue
>
> But I found this wiki article -> 
> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
> interceptor driver from command line:
>
> sudo PYTHONPATH=/usr/share/weewx python 
> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
> --mode=listen
>
> Then - exactly  as this part of article says -> 
> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>  
> I pasted to browser such query:
>
>
> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>
> And I got an answer in terminal:
>
> raw data: 
> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
> raw data: 
> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
> mapped packet: {'dateTime': 1706118216, 'usUnits': 1}
>
> So it seems that driver is working when called explicitly from command 
> line. So why I got "empty queue" when started by 'sudo systemctl start 
> weewx'?
> wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com 
> napisał(a):
>
>> sudo only issues the command as root.
>> What is in the service file for user and group?
>> That is who weewx is running as.
>>
>> On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:
>>
>>> I run weewx as root:
>>>
>>> sudo systemctl start weewx
>>>
>>> If I set higher port (8080), weewx starts but I have empty queue for 
>>> interceptor.
>>>
>>> niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):
>>>
 On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki 
 wrote:

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 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 files therein.  I was tempted to conclude from 
> that change that the install would update the ownership and group of the 
> directory /var/lib/weewx if I hadn't deleted it.  I was tempted to merely 
> add user:group of weewx:weewx and assign them to /var/lib/weewx and the 
> database but I wasn't sure if there were special requirements for that user 
> and group.  
>I have rebooted since I ran the install.  Since then I get the error 
> about weewx group being unknown in sets of ten once per day.
>
>
> On Wednesday, January 24, 2024 at 2:40:30 PM UTC-5 Joseph Verreau wrote:
>
>> 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 import
>> drwxr-xr-x. 1 weewx weewx10 Jan 21 12:18 logrotate.d
>> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
>> drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
>> drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
>> drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
>> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 udev
>> -rw-r--r--. 1 weewx weewx 19474 Jan 23 18:15 weewx.conf
>> -rw-r--r--. 1 weewx weewx 23138 Jan 30  2023 weewx.conf-4.10.1
>> -rw-r--r--. 1 weewx weewx 23146 Jan 19 18:36 weewx.conf-4.10.2-5.0.0
>> -rw-r--r--. 1 weewx weewx 23142 Jun  8  2021 weewx.conf-4.5.1
>> -rw-r--r--. 1 weewx weewx 23137 Feb  6  2022 weewx.conf-4.6.0
>> -rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.1
>> -rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.2
>> -rw-r--r--. 1 weewx weewx 23137 Mar  5  2022 weewx.conf-4.7.0
>> -rw-r--r--. 1 weewx weewx 23137 Apr 24  2022 weewx.conf-4.8.0
>> -rw-r--r--. 1 weewx weewx 23220 Oct 25  2022 weewx.conf-4.9.1
>> -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf-5.0.0
>> -rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.prev
>> -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf.rpmnew
>> -rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.rpmsave
>>
>> joev.mi
>> _ _ _ _ _ _ _ _ _ _
>>
>> On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 Joseph Verreau wrote:
>>
>>> 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 no weewx files in /etc/init.d or /etc/sysetmd/system
>>> lrwxrwxrwx. 1 root root   37 Jan 21 12:18 weewx.service -> 
>>> /usr/lib/systemd/system/weewx.service
>>>
>>> 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd
>>> weewx:x:971:960::/home/weewx:/sbin/nologin
>>>
>>> 4) 60-weewx.rules attached
>>>
>>> and thank you for your response.
>>>
>>> joev.mi
>>> _ _ _ _ _ _ _ _ _ _
>>>
>>> On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote:
>>>
 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 
 would better prepare me for installing on my desktop that is actually 
 connected to my weather station.

 Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: 
 /usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring.


 1) what is User and Group in /usr/lib/systemd/system/weewx.service?

 2) do any of these files exist on your system:
 /etc/systemd/system/weewx.service
 /etc/init.d/weewx
 /etc/init.d/weewx-multi
  
 3) what do you see when you do this: 
 grep weewx /etc/passwd

 4) please post the contents of the file
 /usr/lib/udev/rules.d/60-weewx.rules

 installation history:

 initially installed on this server running fedora in 2014 via the 
 setup.py method. In 2020 I switched to the dnf repo method. When I first 
 ran this upgrade to ver 5.0 using dnf upgrade I noticed that I ended up 
 with the application using root:root for user:group assignments of 
 directories and files. Reading the installation guide some more I noted 
 there was a transition to 

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 files therein.  I was tempted to conclude from 
that change that the install would update the ownership and group of the 
directory /var/lib/weewx if I hadn't deleted it.  I was tempted to merely 
add user:group of weewx:weewx and assign them to /var/lib/weewx and the 
database but I wasn't sure if there were special requirements for that user 
and group.  
   I have rebooted since I ran the install.  Since then I get the error 
about weewx group being unknown in sets of ten once per day.


On Wednesday, January 24, 2024 at 2:40:30 PM UTC-5 Joseph Verreau wrote:

> 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 import
> drwxr-xr-x. 1 weewx weewx10 Jan 21 12:18 logrotate.d
> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
> drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
> drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
> drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
> drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 udev
> -rw-r--r--. 1 weewx weewx 19474 Jan 23 18:15 weewx.conf
> -rw-r--r--. 1 weewx weewx 23138 Jan 30  2023 weewx.conf-4.10.1
> -rw-r--r--. 1 weewx weewx 23146 Jan 19 18:36 weewx.conf-4.10.2-5.0.0
> -rw-r--r--. 1 weewx weewx 23142 Jun  8  2021 weewx.conf-4.5.1
> -rw-r--r--. 1 weewx weewx 23137 Feb  6  2022 weewx.conf-4.6.0
> -rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.1
> -rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.2
> -rw-r--r--. 1 weewx weewx 23137 Mar  5  2022 weewx.conf-4.7.0
> -rw-r--r--. 1 weewx weewx 23137 Apr 24  2022 weewx.conf-4.8.0
> -rw-r--r--. 1 weewx weewx 23220 Oct 25  2022 weewx.conf-4.9.1
> -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf-5.0.0
> -rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.prev
> -rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf.rpmnew
> -rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.rpmsave
>
> joev.mi
> _ _ _ _ _ _ _ _ _ _
>
> On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 Joseph Verreau wrote:
>
>> 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 no weewx files in /etc/init.d or /etc/sysetmd/system
>> lrwxrwxrwx. 1 root root   37 Jan 21 12:18 weewx.service -> 
>> /usr/lib/systemd/system/weewx.service
>>
>> 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd
>> weewx:x:971:960::/home/weewx:/sbin/nologin
>>
>> 4) 60-weewx.rules attached
>>
>> and thank you for your response.
>>
>> joev.mi
>> _ _ _ _ _ _ _ _ _ _
>>
>> On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote:
>>
>>> 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 
>>> would better prepare me for installing on my desktop that is actually 
>>> connected to my weather station.
>>>
>>> Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: 
>>> /usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring.
>>>
>>>
>>> 1) what is User and Group in /usr/lib/systemd/system/weewx.service?
>>>
>>> 2) do any of these files exist on your system:
>>> /etc/systemd/system/weewx.service
>>> /etc/init.d/weewx
>>> /etc/init.d/weewx-multi
>>>  
>>> 3) what do you see when you do this: 
>>> grep weewx /etc/passwd
>>>
>>> 4) please post the contents of the file
>>> /usr/lib/udev/rules.d/60-weewx.rules
>>>
>>> installation history:
>>>
>>> initially installed on this server running fedora in 2014 via the 
>>> setup.py method. In 2020 I switched to the dnf repo method. When I first 
>>> ran this upgrade to ver 5.0 using dnf upgrade I noticed that I ended up 
>>> with the application using root:root for user:group assignments of 
>>> directories and files. Reading the installation guide some more I noted 
>>> there was a transition to weewx:weewx for those assignments. So I erased 
>>> the application then ran dnf install weewx following along the instructions 
>>> for fedora versions 34+. That seemed to correct the issue of ownership by 
>>> creating the missing user and group. 
>>>
>>> I don’t observe anything else out of place. 

Re: [weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

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 extension pass wind value to wind gust ! I have the 0.1.7
version . All the others are working fine . See the last messages
https://groups.google.com/g/weewx-user/c/DiR9FEVYnb4
Thanks again

Στις Τετ 24 Ιαν 2024, 21:32 ο χρήστης vince  έγραψε:

> 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 deb12 install attempt just now.
>
> On Wednesday, January 24, 2024 at 9:48:33 AM UTC-8 Stefanos Kalaitzis
> wrote:
>
>> 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 other sd card everything from the
>> beginning (rasbian OS ,weewx 5, etc)
>> I follow the steps of debian installation (apt)  as described in official
>> weewx page and after step 2 i had the following error :
>>
>> sudo apt update
>> sudo apt install weewx
>>
>> Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
>> Hit:2 http://deb.debian.org/debian bookworm InRelease
>>
>> Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease
>>
>> Hit:4 http://deb.debian.org/debian bookworm-updates InRelease
>>
>> Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]
>> Err:5 https://weewx.com/apt/python3 buster InRelease
>>   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
>> following signatures couldn't be verified because the public key is not
>> available: NO_PUBKEY ED444FCCF0E2B09E
>> E: *The repository 'https://weewx.com/apt/python3
>>  buster InRelease' is not signed*.
>> N: Updating from such a repository can't be done securely, and is
>> therefore disabled by default.
>> N: See apt-secure(8) manpage for repository creation and user
>> configuration details.
>> Reading package lists... Done
>> Building dependency tree... Done
>> Reading state information... Done
>> E: *Unable to locate package weewx*
>>
>> I hope that i didnt miss something . As i wrote above because i have
>> already running weewx i am not in a hurry so if someone knows what i am
>> doing wrong i would be appreciated
>> Thank you in advanced
>>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/a9f195da-f8a7-4fdb-a6c1-39acb9f9cb2cn%40googlegroups.com
> 
> .
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CAERekb8c-SgfAKzrrprzFYFwzpGpSvEerBmkdvi9KqjjKOYXFQ%40mail.gmail.com.

[weewx-user] Re: Driver permission error when starting Weewx

[vince]

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 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:~ $ python --version
> Python 3.7.3
>
>
> środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):
>
>> 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
>> RuntimeDirectoryMode=775
>> User=root
>> Group=root
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>>
>>> 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 
 wu-client - I always get:

 weewxd[27966]: DEBUG user.interceptor: empty queue

 But I found this wiki article -> 
 https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
 interceptor driver from command line:

 sudo PYTHONPATH=/usr/share/weewx python 
 /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
 --mode=listen

 Then - exactly  as this part of article says -> 
 https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
  
 I pasted to browser such query:


 http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000

 And I got an answer in terminal:

 raw data: 
 PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
 raw packet: {'dateTime': 1577636847, 'usUnits': 1}
 mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
 raw data: 
 raw packet: {'dateTime': 1706118216, 'usUnits': 1}
 mapped packet: {'dateTime': 1706118216, 'usUnits': 1}

 So it seems that driver is working when called explicitly from command 
 line. So why I got "empty queue" when started by 'sudo systemctl start 
 weewx'?
 wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com 
 napisał(a):

> sudo only issues the command as root.
> What is in the service file for user and group?
> That is who weewx is running as.
>
> On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:
>
>> I run weewx as root:
>>
>> sudo systemctl start weewx
>>
>> If I set higher port (8080), weewx starts but I have empty queue for 
>> interceptor.
>>
>> niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):
>>
>>> On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki 
>>> wrote:
>>>
>>>
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading 
>>> station type Interceptor (user.interceptor)
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver 
>>> version is 0.60
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device 
>>> type: observer
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware 
>>> name: weatherstation via interceptor
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is 
>>> listen
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on 
>>> :80
>>>
>>>
>>> if you listen on port 80, then the process must run as root (only 
>>> root can listen on lower ports).
>>>
>>> so either run weewxd as root, or configure interceptor (and the 
>>> station) to communicate on a higher port.
>>>  
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/16908ceb-29f6-41f8-8659-512f89398df7n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 import
drwxr-xr-x. 1 weewx weewx10 Jan 21 12:18 logrotate.d
drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 logwatch
drwxr-xr-x. 1 weewx weewx20 Jan 21 12:18 rsyslog.d
drwxr-xr-x. 1 weewx weewx78 Jan 21 12:18 skins
drwxr-xr-x. 1 weewx weewx54 Jan 21 12:18 systemd
drwxr-xr-x. 1 weewx weewx22 Jan 21 12:18 udev
-rw-r--r--. 1 weewx weewx 19474 Jan 23 18:15 weewx.conf
-rw-r--r--. 1 weewx weewx 23138 Jan 30  2023 weewx.conf-4.10.1
-rw-r--r--. 1 weewx weewx 23146 Jan 19 18:36 weewx.conf-4.10.2-5.0.0
-rw-r--r--. 1 weewx weewx 23142 Jun  8  2021 weewx.conf-4.5.1
-rw-r--r--. 1 weewx weewx 23137 Feb  6  2022 weewx.conf-4.6.0
-rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.1
-rw-r--r--. 1 weewx weewx 23137 Feb 11  2022 weewx.conf-4.6.2
-rw-r--r--. 1 weewx weewx 23137 Mar  5  2022 weewx.conf-4.7.0
-rw-r--r--. 1 weewx weewx 23137 Apr 24  2022 weewx.conf-4.8.0
-rw-r--r--. 1 weewx weewx 23220 Oct 25  2022 weewx.conf-4.9.1
-rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf-5.0.0
-rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.prev
-rw-r--r--. 1 weewx weewx 19474 Jan 14 12:01 weewx.conf.rpmnew
-rw-r--r--. 1 weewx weewx 23138 Feb 23  2023 weewx.conf.rpmsave

joev.mi
_ _ _ _ _ _ _ _ _ _

On Wednesday, January 24, 2024 at 2:38:38 PM UTC-5 Joseph Verreau wrote:

> 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 no weewx files in /etc/init.d or /etc/sysetmd/system
> lrwxrwxrwx. 1 root root   37 Jan 21 12:18 weewx.service -> 
> /usr/lib/systemd/system/weewx.service
>
> 3) xps13-9305:/etc/init.d# grep weewx /etc/passwd
> weewx:x:971:960::/home/weewx:/sbin/nologin
>
> 4) 60-weewx.rules attached
>
> and thank you for your response.
>
> joev.mi
> _ _ _ _ _ _ _ _ _ _
>
> On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote:
>
>> 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 
>> would better prepare me for installing on my desktop that is actually 
>> connected to my weather station.
>>
>> Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: 
>> /usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring.
>>
>>
>> 1) what is User and Group in /usr/lib/systemd/system/weewx.service?
>>
>> 2) do any of these files exist on your system:
>> /etc/systemd/system/weewx.service
>> /etc/init.d/weewx
>> /etc/init.d/weewx-multi
>>  
>> 3) what do you see when you do this: 
>> grep weewx /etc/passwd
>>
>> 4) please post the contents of the file
>> /usr/lib/udev/rules.d/60-weewx.rules
>>
>> installation history:
>>
>> initially installed on this server running fedora in 2014 via the 
>> setup.py method. In 2020 I switched to the dnf repo method. When I first 
>> ran this upgrade to ver 5.0 using dnf upgrade I noticed that I ended up 
>> with the application using root:root for user:group assignments of 
>> directories and files. Reading the installation guide some more I noted 
>> there was a transition to weewx:weewx for those assignments. So I erased 
>> the application then ran dnf install weewx following along the instructions 
>> for fedora versions 34+. That seemed to correct the issue of ownership by 
>> creating the missing user and group. 
>>
>> I don’t observe anything else out of place. My install starts against the 
>> simulator device, and enters the main loop where it updates the database as 
>> I would expect. 
>>
>> Question: does the error reported above as in the journal imply a 
>> mis-configuration? Why is the group weewx identified as unknown?
>>
>>
>> when you upgrade from v4 to v5 using dnf, weewxd should run as 
>> root:root.  this is because the installer will try to respect your previous 
>> installation, and continue to run with the same user and permissions as the 
>> previous install.
>>
>> when you do a new install of v5 using dnf, weewxd should run as 
>> weewx:weewx.
>>
>> note that when you 'erase' an installation with dnf, the database, 
>> located in /var/lib/weewx, will not be deleted.  so if you were to run the 
>> v5 installer at this point, even though it is technically a new install, 
>> because of the /var/lib/weewx with root:root ownership, the 'new' install 
>> will run as root:root.
>>
>> if you saw that v5 was running as 

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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:~ $ python --version
Python 3.7.3
   

środa, 24 stycznia 2024 o 20:36:46 UTC+1 Tomasz Lewicki napisał(a):

> 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
> RuntimeDirectoryMode=775
> User=root
> Group=root
>
> [Install]
> WantedBy=multi-user.target
>
> środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):
>
>> 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 
>>> wu-client - I always get:
>>>
>>> weewxd[27966]: DEBUG user.interceptor: empty queue
>>>
>>> But I found this wiki article -> 
>>> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
>>> interceptor driver from command line:
>>>
>>> sudo PYTHONPATH=/usr/share/weewx python 
>>> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
>>> --mode=listen
>>>
>>> Then - exactly  as this part of article says -> 
>>> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>>>  
>>> I pasted to browser such query:
>>>
>>>
>>> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>>
>>> And I got an answer in terminal:
>>>
>>> raw data: 
>>> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
>>> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
>>> raw data: 
>>> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
>>> mapped packet: {'dateTime': 1706118216, 'usUnits': 1}
>>>
>>> So it seems that driver is working when called explicitly from command 
>>> line. So why I got "empty queue" when started by 'sudo systemctl start 
>>> weewx'?
>>> wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com napisał(a):
>>>
 sudo only issues the command as root.
 What is in the service file for user and group?
 That is who weewx is running as.

 On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:

> I run weewx as root:
>
> sudo systemctl start weewx
>
> If I set higher port (8080), weewx starts but I have empty queue for 
> interceptor.
>
> niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):
>
>> On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki wrote:
>>
>>
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading 
>> station type Interceptor (user.interceptor)
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver 
>> version is 0.60
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device 
>> type: observer
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware 
>> name: weatherstation via interceptor
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is 
>> listen
>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on 
>> :80
>>
>>
>> if you listen on port 80, then the process must run as root (only 
>> root can listen on lower ports).
>>
>> so either run weewxd as root, or configure interceptor (and the 
>> station) to communicate on a higher port.
>>  
>>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8a9bb3ef-45d4-47e1-a675-dc129e1bd2aan%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[Joseph Verreau]

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 no weewx files in /etc/init.d or /etc/sysetmd/system
lrwxrwxrwx. 1 root root   37 Jan 21 12:18 weewx.service -> 
/usr/lib/systemd/system/weewx.service

3) xps13-9305:/etc/init.d# grep weewx /etc/passwd
weewx:x:971:960::/home/weewx:/sbin/nologin

4) 60-weewx.rules attached

and thank you for your response.

joev.mi
_ _ _ _ _ _ _ _ _ _

On Wednesday, January 24, 2024 at 7:20:47 AM UTC-5 matthew wall wrote:

> 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 
> would better prepare me for installing on my desktop that is actually 
> connected to my weather station.
>
> Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: 
> /usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring.
>
>
> 1) what is User and Group in /usr/lib/systemd/system/weewx.service?
>
> 2) do any of these files exist on your system:
> /etc/systemd/system/weewx.service
> /etc/init.d/weewx
> /etc/init.d/weewx-multi
>  
> 3) what do you see when you do this: 
> grep weewx /etc/passwd
>
> 4) please post the contents of the file
> /usr/lib/udev/rules.d/60-weewx.rules
>
> installation history:
>
> initially installed on this server running fedora in 2014 via the setup.py 
> method. In 2020 I switched to the dnf repo method. When I first ran this 
> upgrade to ver 5.0 using dnf upgrade I noticed that I ended up with the 
> application using root:root for user:group assignments of directories and 
> files. Reading the installation guide some more I noted there was a 
> transition to weewx:weewx for those assignments. So I erased the 
> application then ran dnf install weewx following along the instructions for 
> fedora versions 34+. That seemed to correct the issue of ownership by 
> creating the missing user and group. 
>
> I don’t observe anything else out of place. My install starts against the 
> simulator device, and enters the main loop where it updates the database as 
> I would expect. 
>
> Question: does the error reported above as in the journal imply a 
> mis-configuration? Why is the group weewx identified as unknown?
>
>
> when you upgrade from v4 to v5 using dnf, weewxd should run as root:root.  
> this is because the installer will try to respect your previous 
> installation, and continue to run with the same user and permissions as the 
> previous install.
>
> when you do a new install of v5 using dnf, weewxd should run as 
> weewx:weewx.
>
> note that when you 'erase' an installation with dnf, the database, located 
> in /var/lib/weewx, will not be deleted.  so if you were to run the v5 
> installer at this point, even though it is technically a new install, 
> because of the /var/lib/weewx with root:root ownership, the 'new' install 
> will run as root:root.
>
> 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?
>
> m
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/af136a00-3a85-4b7e-b925-482928bebb77n%40googlegroups.com.


60-weewx.rules
Description: Binary data

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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
RuntimeDirectoryMode=775
User=root
Group=root

[Install]
WantedBy=multi-user.target

środa, 24 stycznia 2024 o 20:33:17 UTC+1 vince napisał(a):

> 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 wu-client - I always get:
>>
>> weewxd[27966]: DEBUG user.interceptor: empty queue
>>
>> But I found this wiki article -> 
>> https://github.com/weewx/weewx/wiki/gw1000-recipe and started 
>> interceptor driver from command line:
>>
>> sudo PYTHONPATH=/usr/share/weewx python 
>> /etc/weewx/bin/user/interceptor.py --port=80 --debug --device=observer 
>> --mode=listen
>>
>> Then - exactly  as this part of article says -> 
>> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>>  
>> I pasted to browser such query:
>>
>>
>> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>>
>> And I got an answer in terminal:
>>
>> raw data: 
>> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
>> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
>> raw data: 
>> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
>> mapped packet: {'dateTime': 1706118216, 'usUnits': 1}
>>
>> So it seems that driver is working when called explicitly from command 
>> line. So why I got "empty queue" when started by 'sudo systemctl start 
>> weewx'?
>> wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com napisał(a):
>>
>>> sudo only issues the command as root.
>>> What is in the service file for user and group?
>>> That is who weewx is running as.
>>>
>>> On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:
>>>
 I run weewx as root:

 sudo systemctl start weewx

 If I set higher port (8080), weewx starts but I have empty queue for 
 interceptor.

 niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):

> On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki wrote:
>
>
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading station 
> type Interceptor (user.interceptor)
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver 
> version is 0.60
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device 
> type: observer
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware 
> name: weatherstation via interceptor
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is 
> listen
> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on 
> :80
>
>
> if you listen on port 80, then the process must run as root (only root 
> can listen on lower ports).
>
> so either run weewxd as root, or configure interceptor (and the 
> station) to communicate on a higher port.
>  
>


-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/e88efabd-37d8-4bc1-9ca3-8e657a68ba8fn%40googlegroups.com.

[weewx-user] Re: Driver permission error when starting Weewx

[vince]

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 wu-client - I always get:
>
> weewxd[27966]: DEBUG user.interceptor: empty queue
>
> But I found this wiki article -> 
> https://github.com/weewx/weewx/wiki/gw1000-recipe and started interceptor 
> driver from command line:
>
> sudo PYTHONPATH=/usr/share/weewx python /etc/weewx/bin/user/interceptor.py 
> --port=80 --debug --device=observer --mode=listen
>
> Then - exactly  as this part of article says -> 
> https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
>  
> I pasted to browser such query:
>
>
> http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
>
> And I got an answer in terminal:
>
> raw data: 
> PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
> raw packet: {'dateTime': 1577636847, 'usUnits': 1}
> mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
> raw data: 
> raw packet: {'dateTime': 1706118216, 'usUnits': 1}
> mapped packet: {'dateTime': 1706118216, 'usUnits': 1}
>
> So it seems that driver is working when called explicitly from command 
> line. So why I got "empty queue" when started by 'sudo systemctl start 
> weewx'?
> wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com napisał(a):
>
>> sudo only issues the command as root.
>> What is in the service file for user and group?
>> That is who weewx is running as.
>>
>> On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:
>>
>>> I run weewx as root:
>>>
>>> sudo systemctl start weewx
>>>
>>> If I set higher port (8080), weewx starts but I have empty queue for 
>>> interceptor.
>>>
>>> niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):
>>>
 On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki wrote:


 Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading station 
 type Interceptor (user.interceptor)
 Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver 
 version is 0.60
 Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device type: 
 observer
 Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware 
 name: weatherstation via interceptor
 Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is 
 listen
 Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on :80


 if you listen on port 80, then the process must run as root (only root 
 can listen on lower ports).

 so either run weewxd as root, or configure interceptor (and the 
 station) to communicate on a higher port.
  

>>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/48b75de8-d8ef-4b93-9fd1-ab51819aaebbn%40googlegroups.com.

[weewx-user] Re: Weewx 5.0 with Rpi4 bookworm 64bit

[vince]

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 deb12 install attempt just now.

On Wednesday, January 24, 2024 at 9:48:33 AM UTC-8 Stefanos Kalaitzis wrote:

> 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 other sd card everything from the 
> beginning (rasbian OS ,weewx 5, etc)
> I follow the steps of debian installation (apt)  as described in official 
> weewx page and after step 2 i had the following error :
>
> sudo apt update
> sudo apt install weewx
>
> Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
> Hit:2 http://deb.debian.org/debian bookworm InRelease 
>  
> Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease   
>  
> Hit:4 http://deb.debian.org/debian bookworm-updates InRelease 
>  
> Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]
> Err:5 https://weewx.com/apt/python3 buster InRelease
>   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 
> following signatures couldn't be verified because the public key is not 
> available: NO_PUBKEY ED444FCCF0E2B09E
> E: *The repository 'https://weewx.com/apt/python3 
>  buster InRelease' is not signed*.
> N: Updating from such a repository can't be done securely, and is 
> therefore disabled by default.
> N: See apt-secure(8) manpage for repository creation and user 
> configuration details.
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> E: *Unable to locate package weewx*
>
> I hope that i didnt miss something . As i wrote above because i have 
> already running weewx i am not in a hurry so if someone knows what i am 
> doing wrong i would be appreciated
> Thank you in advanced 
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/a9f195da-f8a7-4fdb-a6c1-39acb9f9cb2cn%40googlegroups.com.

[weewx-user] Weewx 5.0 with Rpi4 bookworm 64bit

[Stefanos Kalaitzis]

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 other sd card everything from the 
beginning (rasbian OS ,weewx 5, etc)
I follow the steps of debian installation (apt)  as described in official 
weewx page and after step 2 i had the following error :

sudo apt update
sudo apt install weewx

Hit:1 http://archive.raspberrypi.com/debian bookworm InRelease
Hit:2 http://deb.debian.org/debian bookworm InRelease   
   
Hit:3 http://deb.debian.org/debian-security bookworm-security InRelease 
   
Hit:4 http://deb.debian.org/debian bookworm-updates InRelease   
   
Get:5 https://weewx.com/apt/python3 buster InRelease [3614 B]
Err:5 https://weewx.com/apt/python3 buster InRelease
  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 following 
signatures couldn't be verified because the public key is not available: 
NO_PUBKEY ED444FCCF0E2B09E
E: *The repository 'https://weewx.com/apt/python3 buster InRelease' is not 
signed*.
N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: *Unable to locate package weewx*

I hope that i didnt miss something . As i wrote above because i have 
already running weewx i am not in a hurry so if someone knows what i am 
doing wrong i would be appreciated
Thank you in advanced 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/eff9055d-cef6-42f6-86a8-8f46cb6e2045n%40googlegroups.com.

[weewx-user] Re: Driver permission error when starting Weewx

['Tomasz Lewicki' via weewx-user]

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://github.com/weewx/weewx/wiki/gw1000-recipe and started 
interceptor driver from command line:

sudo PYTHONPATH=/usr/share/weewx python /etc/weewx/bin/user/interceptor.py 
--port=80 --debug --device=observer --mode=listen

Then - exactly  as this part of article says -> 
https://github.com/weewx/weewx/wiki/gw1000-recipe#verify-that-the-interceptor-can-receive-data
 
I pasted to browser such query:

http://192.168.0.106/data/report?PASSKEY=XXX=GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000

And I got an answer in terminal:

raw data: 
PASSKEY==GW1000B_V1.5.5=2019-12-29+16:27:27=67.1=39=30.138=30.138=915M=GW1000
raw packet: {'dateTime': 1577636847, 'usUnits': 1}
mapped packet: {'dateTime': 1577636847, 'usUnits': 1}
raw data: 
raw packet: {'dateTime': 1706118216, 'usUnits': 1}
mapped packet: {'dateTime': 1706118216, 'usUnits': 1}

So it seems that driver is working when called explicitly from command 
line. So why I got "empty queue" when started by 'sudo systemctl start 
weewx'?
wtorek, 23 stycznia 2024 o 15:46:08 UTC+1 gary@gmail.com napisał(a):

> sudo only issues the command as root.
> What is in the service file for user and group?
> That is who weewx is running as.
>
> On Monday, January 22, 2024 at 11:43:48 AM UTC-5 Tomasz Lewicki wrote:
>
>> I run weewx as root:
>>
>> sudo systemctl start weewx
>>
>> If I set higher port (8080), weewx starts but I have empty queue for 
>> interceptor.
>>
>> niedziela, 21 stycznia 2024 o 18:49:48 UTC+1 matthew wall napisał(a):
>>
>>> On Sunday, January 21, 2024 at 12:23:34 PM UTC-5 Tomasz Lewicki wrote:
>>>
>>>
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO weewx.engine: Loading station 
>>> type Interceptor (user.interceptor)
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: driver 
>>> version is 0.60
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: device type: 
>>> observer
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: hardware 
>>> name: weatherstation via interceptor
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: mode is listen
>>> Jan 21 18:14:17 FR24 weewxd[14285]: INFO user.interceptor: listen on :80
>>>
>>>
>>> if you listen on port 80, then the process must run as root (only root 
>>> can listen on lower ports).
>>>
>>> so either run weewxd as root, or configure interceptor (and the station) 
>>> to communicate on a higher port.
>>>  
>>>
>>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9ab3f1c3-8096-4066-8544-dae133762d8cn%40googlegroups.com.

Re: [weewx-user] Re: Why the rain 'spikes'?

[Bob Atchley]

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 (the console itself 
does 12 second updates), but recording at the same interval that weewx is 
putting data into the database seems a good compromise.

Hope this helps

Bob

On Wednesday 24 January 2024 at 08:35:25 UTC Ξ wrote:

> 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, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8650a53d-3b6e-45be-b67c-10cda11b28cen%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[matthew wall]

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 weewx:weewx, that means you must have 
deleted /var/lib/weewx or changed its permissions.

could you verify whether you deleted the database and /var/lib/weewx before 
you did the new install to v5?

m 

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/769a3c81-a567-4a1d-8584-fe46d2eee4d1n%40googlegroups.com.

[weewx-user] Re: errors related to udevd after upgrade to weewx 5.0.0

[matthew wall]

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 
would better prepare me for installing on my desktop that is actually 
connected to my weather station.

Jan 23 12:06:12 xps13-9305 systemd-udevd[632]: 
/usr/lib/udev/rules.d/60-weewx.rules:4 Unknown group '{weewx}', ignoring.


1) what is User and Group in /usr/lib/systemd/system/weewx.service?

2) do any of these files exist on your system:
/etc/systemd/system/weewx.service
/etc/init.d/weewx
/etc/init.d/weewx-multi
 
3) what do you see when you do this: 
grep weewx /etc/passwd

4) please post the contents of the file
/usr/lib/udev/rules.d/60-weewx.rules

installation history:

initially installed on this server running fedora in 2014 via the setup.py 
method. In 2020 I switched to the dnf repo method. When I first ran this 
upgrade to ver 5.0 using dnf upgrade I noticed that I ended up with the 
application using root:root for user:group assignments of directories and 
files. Reading the installation guide some more I noted there was a 
transition to weewx:weewx for those assignments. So I erased the 
application then ran dnf install weewx following along the instructions for 
fedora versions 34+. That seemed to correct the issue of ownership by 
creating the missing user and group. 

I don’t observe anything else out of place. My install starts against the 
simulator device, and enters the main loop where it updates the database as 
I would expect. 

Question: does the error reported above as in the journal imply a 
mis-configuration? Why is the group weewx identified as unknown?


when you upgrade from v4 to v5 using dnf, weewxd should run as root:root.  
this is because the installer will try to respect your previous 
installation, and continue to run with the same user and permissions as the 
previous install.

when you do a new install of v5 using dnf, weewxd should run as weewx:weewx.

note that when you 'erase' an installation with dnf, the database, located 
in /var/lib/weewx, will not be deleted.  so if you were to run the v5 
installer at this point, even though it is technically a new install, 
because of the /var/lib/weewx with root:root ownership, the 'new' install 
will run as root:root.

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?

m

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/16e985cb-2eec-4472-af79-6d919c0256f8n%40googlegroups.com.

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[gjr80]

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 of the database archive table). You have a few options:

1. put the column back with --add-columns, I suspect this is the easiest 
solution
2. have your driver emit the field rxCheckPercent 
3. modify the template 

I would suggest you just add the missing column back in. 

Gary

On Tuesday 23 January 2024 at 18:30:10 UTC+10 remy.l...@gmail.com wrote:

> If it helps you, I'll leave you a link to my database. weewx.sdb -> 
> https://transfert.free.fr/FgCL7wI
>
> But once again, I don't think I have deleted any "basic" fields (inTemp, 
> Barometer, outTemp etc...) for weewx.
>
> The SteelSeries skin tells me it hasn't been updated in 178 days, so it 
> appears to be from July 29, 2023 (a timestamp >= 1690581600).
> And around this date, I didn't notice anything particular in my 
> database... :-(
>
> Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :
>
>> Hello Gary,
>>
>> I've put what you asked for below.
>>
>> The problem is systematic (this is an advantage in some way...)
>>
>> I think you are right about the problem of a field in the database... But 
>> which one?
>> SteelSeries was working perfectly BEFORE I added/deleted the data base. I 
>> didn't notice the problem immediately since I mainly use the Seasons skin. 
>> But there is a good chance that the problem is linked to the modification 
>> of the structure of the base.
>> Unfortunately, I can't find ! :-(
>>
>>
>> LOOP:   2024-01-22 15:09:07 CET (1705932547) 'altimeter': 'None', 
>> 'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5', 
>> 'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388', 
>> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '0', 
>> 'cpu_user': '0', 'dateTime': '1705932547', 'dewpoint': '37.94', 
>> 'disk_total': '20425850880', 'disk_used': '10535763968', 
>> 'electricityLinky': '0', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
>> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': 
>> '50.1080004', 'extraTemp2': '52.7', 'extraTemp3': 'None', 
>> 'extraTemp4': '66.506', 'extraTemp6': 'None', 'heatindex': '43.228', 
>> 'humidex': '45.5', 'inDewpoint': '51.726318793965625', 'inHumidity': '54', 
>> 'inTemp': '69.080001', 'inTempDaikin': '68.0', 'kWhPAC': '0.0', 
>> 'maxSolarRad': '255.46907895483838', 'mem_total': '8286392320', 'mem_used': 
>> '1683726336', 'outHumidity': '74', 'outTemp': '45.5', 'outTempDaikin': 
>> '44.6', 'pressure': 'None', 'radiation': '48', 'rain': '0.0', 'rainRate': 
>> '0.0', 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 
>> 'waterSensus': '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.684', 
>> 'windchill': '45.5', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 
>> 'None', 'windrun': 'None', 'windSpeed': '0.0'
>>
>> LOOP:   2024-01-22 15:10:07 CET (1705932607) 'altimeter': 'None', 
>> 'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '42.0', 
>> 'charge5': '27.5', 'charge15': '14.0', 'cloudbase': '3342.900026403866', 
>> 'cpu_io': '1', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '27', 
>> 'cpu_user': '28', 'dateTime': '1705932607', 'dewpoint': '38.3', 
>> 'disk_total': '20425850880', 'disk_used': '10592305152', 
>> 'electricityLinky': '12', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
>> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0', 
>> 'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4': '66.506', 
>> 'extraTemp6': 'None', 'heatindex': '43.4730006', 'humidex': 
>> '45.68', 'inDewpoint': '51.55950246316422', 'inHumidity': '54', 'inTemp': 
>> '68.9', 'inTempDaikin': '68.0', 'kWhPAC': '0.827', 'maxSolarRad': 
>> '253.53718615434911', 'mem_total': '8286392320', 'mem_used': '1643642880', 
>> 'outHumidity': '75', 'outTemp': '45.68', 'outTempDaikin': '44.6', 
>> 'pressure': 'None', 'radiation': '50', 'rain': '0.0', 'rainRate': '0.0', 
>> 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 'waterSensus': 
>> '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.99', 'windchill': 
>> '45.68', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 'None', 
>> 'windrun': 'None', 'windSpeed': '0.0'
>>
>> LOOP:   2024-01-22 15:11:06 CET (1705932666) 'altimeter': 'None', 
>> 'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '39.5', 
>> 'charge5': '30.0', 'charge15': '15.5', 'cloudbase': '3342.900026403866', 
>> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '2', 
>> 'cpu_user': '4', 'dateTime': '1705932666', 'dewpoint': '38.3', 
>> 'disk_total': '20425850880', 'disk_used': '10592309248', 
>> 'electricityLinky': '13', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
>> '92', 'extraHumid3': 

Re: [weewx-user] Re: Why the rain 'spikes'?

[Ξ]

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, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c2e34a42-c692-4b0d-b2c4-0fc6ac53f60cn%40googlegroups.com.

Re: [weewx-user] Re: Why the rain 'spikes'?

[Ξ]

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 Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/b57f0432-2858-4204-abbe-265be03cbbban%40googlegroups.com.