Re: [weewx-user] weewx v5.0.1 upgrade problem

[František Slimařík]

@Matthew:

That makes sense yep. Thanks a lot for detailed explanation. I cannot
change port 80 on my hardware so I will review other options :)

st 7. 2. 2024 v 8:08 odesílatel matthew wall  napsal:

> another option is to put a proxy in front of interceptor.  configure
> interceptor to listen on a high port, say 8080, then run nginx binding to
> port 80 as a reverse proxy to interceptor, proxying all traffic or just
> specific requests.
>
> m
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%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/CAPXATBWe2qQ2OMg5R3QfKmu8dgovSg%2BccgOXVDua20BthGNFUA%40mail.gmail.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[matthew wall]

another option is to put a proxy in front of interceptor.  configure 
interceptor to listen on a high port, say 8080, then run nginx binding to 
port 80 as a reverse proxy to interceptor, proxying all traffic or just 
specific requests.

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/e8a748e8-5008-4ecc-b5f2-59fad26e8b67n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[matthew wall]

Frantisek,

udev rules are for devices - USB or serial, not for network ports.

the permissions error you are experiencing is probably due the fact that 
you are trying to listen on (bind to) port 80.  only root is allowed to 
bind to ports lower than 1024.

assuming that you are on a linux system, your options include:
- run as root:root
- listen on a higher port (only works if you can change the port on 
whatever is sending data)
- use authbind to let weewx:weewx bind to port 80
- use iptables to REDIRECT traffic from port 80 to a high port
- use CAP_NET_BIND_SERVICE

here is the man page for authbind:

https://manpages.ubuntu.com/manpages/noble/en/man1/authbind.1.html

stack overflow and superuser have details about CAP_NET_BIND_SERVICE:


https://stackoverflow.com/questions/413807/is-there-a-way-for-non-root-processes-to-bind-to-privileged-ports-on-linux


https://superuser.com/questions/710253/allow-non-root-process-to-bind-to-port-80-and-443

serverfault shows how to do the iptables redirect:


https://serverfault.com/questions/112795/how-to-run-a-server-on-port-80-as-a-normal-user-on-linux

m

On Wednesday, February 7, 2024 at 12:57:45 AM UTC-5 xsli...@gmail.com wrote:

@Matthew:
Any clue what should be modified (udev rules/group membership) for 
interceptor driver? When I modify systemctl service to not run under 
weewx:weewx everything is OK :)

*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self.server_bind()*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/usr/lib64/python3.6/socketserver.py", line 
470, in server_bind*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self.socket.bind(self.server_address)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   PermissionError: [Errno 13] Operace zamítnuta*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__: 
Unable to load driver: [Errno 13] Operace zamítnuta*
*Feb  6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Main 
process exited, code=exited, status=4/NOPERMISSION*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__:  
     Exiting...*
*Feb  6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Failed 
with result 'exit-code*



-- 
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/0f771fc2-43b8-4c45-bee6-62dc93250aa2n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[František Slimařík]

@Matthew:
Any clue what should be modified (udev rules/group membership) for 
interceptor driver? When I modify systemctl service to not run under 
weewx:weewx everything is OK :)

*Feb  6 19:37:43 rocky-weather-machine weewxd[1612889]: INFO weewx.engine: 
Loading station type Interceptor (user.interceptor)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO 
user.interceptor: driver version is 0.53*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO 
user.interceptor: device type: observer*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO 
user.interceptor: mode is listen*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: INFO 
user.interceptor: listen on :80*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: ERROR weewx.engine: 
Import of driver failed: [Errno 13] Operace zamítnuta ()*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   Traceback (most recent call last):*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/usr/share/weewx/weewx/engine.py", line 
115, in setupStation*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self.console = loader_function(config_dict, 
self)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/etc/weewx/bin/user/interceptor.py", line 
315, in loader*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   return 
InterceptorDriver(**config_dict[DRIVER_NAME])*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/etc/weewx/bin/user/interceptor.py", line 
2522, in __init__*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self._device = 
self.DEVICE_TYPES.get(self._device_type)(**stn_dict)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/etc/weewx/bin/user/interceptor.py", line 
1285, in __init__*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   Observer.Parser(), handler=Observer.Handler, 
**stn_dict)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/etc/weewx/bin/user/interceptor.py", line 
429, in __init__*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self._server = Consumer.TCPServer(address, 
port, handler)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/etc/weewx/bin/user/interceptor.py", line 
584, in __init__*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   TCPServer.__init__(self, (address, int(port)), 
handler)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/usr/lib64/python3.6/socketserver.py", line 
456, in __init__*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self.server_bind()*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine: File "/usr/lib64/python3.6/socketserver.py", line 
470, in server_bind*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   self.socket.bind(self.server_address)*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL 
weewx.engine:   PermissionError: [Errno 13] Operace zamítnuta*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__: 
Unable to load driver: [Errno 13] Operace zamítnuta*
*Feb  6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Main 
process exited, code=exited, status=4/NOPERMISSION*
*Feb  6 19:37:44 rocky-weather-machine weewxd[1612889]: CRITICAL __main__:  
     Exiting...*
*Feb  6 19:37:44 rocky-weather-machine systemd[1]: weewx.service: Failed 
with result 'exit-code*

Dne úterý 6. února 2024 v 22:00:36 UTC+1 uživatel gjr80 napsal:

> Impossible to say what the issue is with such a short log extract. Please 
> edit weewx.conf, set debug =1, save weewx.conf and restart WeeWX. Let 
> WeeWX run for at least two archive intervals and then take a log extract 
> showing the full WeeWX startup through until the two archive intervals have 
> elapsed. Post the log extract here.
>
> Gary 
>
> On Wednesday 7 February 2024 at 05:23:35 UTC+10 philip...@gmail.com wrote:
>
>> Thanks for that tip - it got me off the ground. All is now well except 
>> that /var/www/html/weewx hasn't been updated since just before I did the 
>> upgrade to 5.0.1. Anyone else seeing this?
>>
>> On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:
>>
>>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and 
>>> serial datalogger had ownership set to root:dialout, so I had to add the 
>>> weewx user to the dialout group for things to work. 
>>>
>>> On Tues

[weewx-user] Re: updated to 5.0.1 still no joy

[vince]

Can't help with such minimal log data and no info from your weewx.conf file 
driver section for the driver you're using.   What os+version are you 
running ?

What is the weewx pi's address ?  What is an 'ip adaptor' ?  What is its 
address ? Can you ping it from the weewx pi ?  If you stop/start weewx 
'after' your network is stable does 'that' work ?

On Tuesday, February 6, 2024 at 7:51:18 PM UTC-8 Rich Strle wrote:

> I've been following the 5.0 issues. I have updated to 5.0.1 and done the 
> usermod but I'm still having issues. RaspberryPi 3 B+ My Vantage Pro is 
> connected via ethernet using the IP adaptor. I appreciate all the work 
> that's gone into this free product.
>
> vp2pi@rpivp2:~ $ sudo apt update
> vp2pi@rpivp2:~ $ sudo apt install weewx 
>  
> vp2pi@rpivp2:~ $ sudo usermod -aG dialout weewx
>
> vp2pi@rpivp2:~ $ sudo systemctl status weewx
> * weewx.service - WeeWX
>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
> preset: enabled)
>  Active: failed (Result: exit-code) since Tue 2024-02-06 21:19:31 CST; 
> 3min 18s ago
>Docs: https://weewx.com/docs
> Process: 460 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
> status=4)
>Main PID: 460 (code=exited, status=4)
> CPU: 966ms
>
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
>  Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:    
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
>  self.port.openPort()
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:    
>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 359, in openPort
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
>  raise weewx.WeeWxIOError(ex)
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
>  weewx.WeeWxIOError: [Errno 101] Network is unreachable
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL __main__: Unable to load 
> driver: [Errno 101] Network is unreachable
> Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL __main__:   Exiting...
> Feb 06 21:19:31 rpivp2 systemd[1]: weewx.service: Main process exited, 
> code=exited, status=4/NOPERMISSION
> Feb 06 21:19:31 rpivp2 systemd[1]: weewx.service: Failed with result 
> 'exit-code'.
> vp2pi@rpivp2:~ $ sudo usermod -aG dialout 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/0ab0c7f9-2435-4a53-8cae-dc9e63df9ec8n%40googlegroups.com.

[weewx-user] updated to 5.0.1 still no joy

[Rich Strle]

I've been following the 5.0 issues. I have updated to 5.0.1 and done the 
usermod but I'm still having issues. RaspberryPi 3 B+ My Vantage Pro is 
connected via ethernet using the IP adaptor. I appreciate all the work 
that's gone into this free product.

vp2pi@rpivp2:~ $ sudo apt update
vp2pi@rpivp2:~ $ sudo apt install weewx 
 
vp2pi@rpivp2:~ $ sudo usermod -aG dialout weewx

vp2pi@rpivp2:~ $ sudo systemctl status weewx
* weewx.service - WeeWX
 Loaded: loaded (/lib/systemd/system/weewx.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Tue 2024-02-06 21:19:31 CST; 
3min 18s ago
   Docs: https://weewx.com/docs
Process: 460 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
status=4)
   Main PID: 460 (code=exited, status=4)
CPU: 966ms

Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 536, in __init__
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
 self.port.openPort()
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine: File 
"/usr/share/weewx/weewx/drivers/vantage.py", line 359, in openPort
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
 raise weewx.WeeWxIOError(ex)
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL weewx.engine:  
 weewx.WeeWxIOError: [Errno 101] Network is unreachable
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL __main__: Unable to load 
driver: [Errno 101] Network is unreachable
Feb 06 21:19:31 rpivp2 weewxd[460]: CRITICAL __main__:   Exiting...
Feb 06 21:19:31 rpivp2 systemd[1]: weewx.service: Main process exited, 
code=exited, status=4/NOPERMISSION
Feb 06 21:19:31 rpivp2 systemd[1]: weewx.service: Failed with result 
'exit-code'.
vp2pi@rpivp2:~ $ sudo usermod -aG dialout 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/2c3336ab-72b9-49bb-a602-be652a00e531n%40googlegroups.com.

Re: [weewx-user] Re: No updates to /var/www/html/weewx

[Tom Keffer]

I'm very surprised. You didn't change anything?

On Tue, Feb 6, 2024 at 4:59 PM Philip Wolff  wrote:

> I did a cold restart and everything came up OK. Magic, I guess. Thanks for
> your help!
>
> On Tue, Feb 6, 2024 at 4:18 PM gjr80  wrote:
>
>> I can't see anything obviously wrong. WeeWX is looking in the right place
>> and the .conf files exist. read only permission is fine. Let me see if I
>> can replicate this, what Ubuntu version?
>>
>> Gary
>>
>> On Wednesday 7 February 2024 at 09:05:49 UTC+10 philip...@gmail.com
>> wrote:
>>
>>> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including
>>> the skins data, in /usr/share/weewx.
>>>
>>> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>>>
>>> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and
>>> veriified that Seasons/skin.conf is there. I restarted weewxk and it still
>>> claims that it can't read Seasons/skin.conf.
>>>
>>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
>>> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48
>>> /etc/weewx/skins/Seasons/skin.conf
>>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
>>> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48
>>> /etc/weewx/skins/Seasons/lang/en.conf
>>> philbert@inspiron:~$
>>>
>>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>>> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
>>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>>> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> reports for latest time in the database.
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> report 'SeasonsReport'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>>> 'SeasonsReport': Config file not found:
>>> "/etc/weewx/skins/Seasons/skin.conf".
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>>> 'SeasonsReport': Config file not found:
>>> "/etc/weewx/skins/Seasons/lang/en.conf".
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: 
>>> Using defaults instead.
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> generators for report 'SeasonsReport' in directory
>>> '/etc/weewx/skins/Seasons'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No
>>> generators specified for report 'SeasonsReport'
>>>
>>> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>>>
 So WeeWX cannot find the Seasons skin.conf, what is the contends of
 /etc/weewx/skins/Seasons?

 Also, you seem to be truncating some of the log lines, it would help if
 we could see the rest of the line:

 Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
 read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
 'SeasonsReport':>
 Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
 read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
 'SeasonsReport': Co>

 For info, a package install has the skins directory in /etc/weewx, it
 has never been in /usr/share/weewx, refer to Where to find things
  in the User's Guide.

 Gary

 On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com
 wrote:

> It thinks that the skins are still in /etc/weewx instead of
> /usr/share/weewx.
>
> -- Boot bc88a89987b645f18a3473d5771ebb26 --
> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing
> weewxd version 5.0.1
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line:
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python
> 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at
> /usr/bin/python3
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform
> Linux-6.5.0-15-generic-x86_64-with-glibc2.35
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale:
> 'en_US.UTF-8'
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path:
> /usr/share/weewx/weewxd.py
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT:
> /etc/weewx
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration
> file: /etc/weewx/weewx.conf
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module:
> /etc/weewx/bin/user
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
> Feb 06 13:23:00 inspi

[weewx-user] Re: V5.0.1 and rsyslog

[Tom Hogland]

I went through and completely removed all the weewx leftovers from 
/etc/init.d, /etc/systemd etc. and restarted rsyslog. I now have *four* 
logs - both of the "correct" weewx-vp2 and weewx-tempest, plus weewxd.log 
and weewxd.py.log... weewxd-vp2.log and weexd-tempest.log appear to be the 
normal log messages. Weewxd.log contains an error (apparently from the 
weewx-sftp extension - it's from pysftp) about being unable to load keys 
from /var/lib/weewx/.ssh/known-hosts.

The host key error: 
Feb  6 12:20:17 tagon weewxd[1093044]: 
/usr/local/lib/python3.10/dist-packages/pysftp/__init__.py:61: UserWarning: 
Failed to load HostKeys from /var/lib/weewx/.ssh/known_hosts.  You will 
need to explicitly load HostKeys (cnopts.hostkeys.load(filename)) or 
disableHostKey checking (cnopts.hostkeys = None).

So, looks like weewx is logging correctly now - apparently the renamed 
entries (or a leftover in etc/init.d) were causing the original issue. I'm 
not using key pairs for SFTP - it uses a name/password. I created 
/var/lib/weewx/.ssh and copied the v4 known_hosts that I was using earlier 
for testing, but I can't imagine that's the right way to fix this... Also, 
the SFTP"report" is correctly uploading data, ad has been.

weewxd.py.log contains output from the weatherflowudp extension - the 
initial field maps, then "listening" lines. Looks like that's the only 
Tempest driver, and it's 4+ years old. Anyone familiar with this driver 
that might have an idea why it's not logging as part of weewx?

On Tuesday, February 6, 2024 at 11:32:34 AM UTC-9 matthew wall wrote:

> please take a look at the wiki page "How to configure logging"
>
> https://github.com/weewx/weewx/wiki/logging
>
> the "weewxd.py.log" smells like a mixed up systemd configuration.  be sure 
> that you are using the units installed by weewx (in /usr/lib/systemd) and 
> that there are not any units in /etc/systemd leftover from v4 or 
> inadvertently deployed somehow. also, be sure to remove anything related to 
> weewx from /etc/init.d and the corresponding /etc/rcN.d (those will be 
> symlinks). systemd silently ignores sysv links and files if they overlap 
> with definitions in the unit files, but you might have something leftover 
> from the weewx-multi script.
>
> 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/83e74e4c-0e8b-4fbd-acde-9ed8d34dd085n%40googlegroups.com.

Re: [weewx-user] Re: No updates to /var/www/html/weewx

[Philip Wolff]

Typo. The version is 5.*0*.1-3.

On Tue, Feb 6, 2024 at 5:03 PM Philip Wolff  wrote:

> I used Synaptic for the upgrade, so I don't have the commands that were
> used. The version shown in Synaptic is 5.o.1-3.
>
> On Tue, Feb 6, 2024 at 4:19 PM Tom Keffer  wrote:
>
>> Yes, it's true that there is a copy of the v5.0 skins in
>> /usr/share/weewx/weewx_data/skins. This is what Python calls "package
>> data ."
>> It is used by "weectl station create" to create a new station data area.
>> weectl copies it over from its obscure location to the new station data. It
>> is not intended to be used by the user, mostly because it's buried so deep
>> in the Python library.
>>
>> As for why weewxd cannot read a file which is plainly there, the only
>> thing I can think of is that the intervening directories in
>> /etc/weewx/skins are not giving it permission. Check that they are all
>> owned by user "weewx", and have 644 permissions
>>
>> Not sure what caused this, but I would guess it's because Debian
>> is treating the skins as config files, which it deleted on the upgrade.
>> Matthew would know more about this. It would help if you have the original
>> upgrade commands and response from apt.
>>
>> -tk
>>
>>
>> On Tue, Feb 6, 2024 at 3:05 PM Philip Wolff 
>> wrote:
>>
>>> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including
>>> the skins data, in /usr/share/weewx.
>>>
>>> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>>>
>>> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and
>>> veriified that Seasons/skin.conf is there. I restarted weewxk and it still
>>> claims that it can't read Seasons/skin.conf.
>>>
>>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
>>> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48
>>> /etc/weewx/skins/Seasons/skin.conf
>>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
>>> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48
>>> /etc/weewx/skins/Seasons/lang/en.conf
>>> philbert@inspiron:~$
>>>
>>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>>> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
>>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>>> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> reports for latest time in the database.
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> report 'SeasonsReport'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>>> 'SeasonsReport': Config file not found:
>>> "/etc/weewx/skins/Seasons/skin.conf".
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>>> 'SeasonsReport': Config file not found:
>>> "/etc/weewx/skins/Seasons/lang/en.conf".
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: 
>>> Using defaults instead.
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>>> generators for report 'SeasonsReport' in directory
>>> '/etc/weewx/skins/Seasons'
>>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No
>>> generators specified for report 'SeasonsReport'
>>>
>>> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>>>
 So WeeWX cannot find the Seasons skin.conf, what is the contends of
 /etc/weewx/skins/Seasons?

 Also, you seem to be truncating some of the log lines, it would help if
 we could see the rest of the line:

 Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
 read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
 'SeasonsReport':>
 Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
 read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
 'SeasonsReport': Co>

 For info, a package install has the skins directory in /etc/weewx, it
 has never been in /usr/share/weewx, refer to Where to find things
  in the User's Guide.

 Gary

 On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com
 wrote:

> It thinks that the skins are still in /etc/weewx instead of
> /usr/share/weewx.
>
> -- Boot bc88a89987b645f18a3473d5771ebb26 --
> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing
> weewxd version 5.0.1
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line:
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python
> 3.10.12 (main, Nov 20 2023, 15:14:05) [G

Re: [weewx-user] Re: No updates to /var/www/html/weewx

[Philip Wolff]

I used Synaptic for the upgrade, so I don't have the commands that were
used. The version shown in Synaptic is 5.o.1-3.

On Tue, Feb 6, 2024 at 4:19 PM Tom Keffer  wrote:

> Yes, it's true that there is a copy of the v5.0 skins in
> /usr/share/weewx/weewx_data/skins. This is what Python calls "package data
> ." It is
> used by "weectl station create" to create a new station data area. weectl
> copies it over from its obscure location to the new station data. It is not
> intended to be used by the user, mostly because it's buried so deep in the
> Python library.
>
> As for why weewxd cannot read a file which is plainly there, the only
> thing I can think of is that the intervening directories in
> /etc/weewx/skins are not giving it permission. Check that they are all
> owned by user "weewx", and have 644 permissions
>
> Not sure what caused this, but I would guess it's because Debian
> is treating the skins as config files, which it deleted on the upgrade.
> Matthew would know more about this. It would help if you have the original
> upgrade commands and response from apt.
>
> -tk
>
>
> On Tue, Feb 6, 2024 at 3:05 PM Philip Wolff 
> wrote:
>
>> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including
>> the skins data, in /usr/share/weewx.
>>
>> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>>
>> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and
>> veriified that Seasons/skin.conf is there. I restarted weewxk and it still
>> claims that it can't read Seasons/skin.conf.
>>
>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
>> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48
>> /etc/weewx/skins/Seasons/skin.conf
>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
>> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48
>> /etc/weewx/skins/Seasons/lang/en.conf
>> philbert@inspiron:~$
>>
>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> reports for latest time in the database.
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> report 'SeasonsReport'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>> 'SeasonsReport': Config file not found:
>> "/etc/weewx/skins/Seasons/skin.conf".
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>> 'SeasonsReport': Config file not found:
>> "/etc/weewx/skins/Seasons/lang/en.conf".
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: 
>> Using defaults instead.
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> generators for report 'SeasonsReport' in directory
>> '/etc/weewx/skins/Seasons'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No
>> generators specified for report 'SeasonsReport'
>>
>> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>>
>>> So WeeWX cannot find the Seasons skin.conf, what is the contends of
>>> /etc/weewx/skins/Seasons?
>>>
>>> Also, you seem to be truncating some of the log lines, it would help if
>>> we could see the rest of the line:
>>>
>>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>>> 'SeasonsReport':>
>>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>>> 'SeasonsReport': Co>
>>>
>>> For info, a package install has the skins directory in /etc/weewx, it
>>> has never been in /usr/share/weewx, refer to Where to find things
>>>  in the User's Guide.
>>>
>>> Gary
>>>
>>> On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com
>>> wrote:
>>>
 It thinks that the skins are still in /etc/weewx instead of
 /usr/share/weewx.

 -- Boot bc88a89987b645f18a3473d5771ebb26 --
 Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing
 weewxd version 5.0.1
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line:
 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python
 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at
 /usr/bin/python3
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform
 Linux-6.5.0-15-gener

Re: [weewx-user] Re: No updates to /var/www/html/weewx

[Philip Wolff]

I did a cold restart and everything came up OK. Magic, I guess. Thanks for
your help!

On Tue, Feb 6, 2024 at 4:18 PM gjr80  wrote:

> I can't see anything obviously wrong. WeeWX is looking in the right place
> and the .conf files exist. read only permission is fine. Let me see if I
> can replicate this, what Ubuntu version?
>
> Gary
>
> On Wednesday 7 February 2024 at 09:05:49 UTC+10 philip...@gmail.com wrote:
>
>> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including
>> the skins data, in /usr/share/weewx.
>>
>> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>>
>> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and
>> veriified that Seasons/skin.conf is there. I restarted weewxk and it still
>> claims that it can't read Seasons/skin.conf.
>>
>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
>> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48
>> /etc/weewx/skins/Seasons/skin.conf
>> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
>> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48
>> /etc/weewx/skins/Seasons/lang/en.conf
>> philbert@inspiron:~$
>>
>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
>> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
>> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> reports for latest time in the database.
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> report 'SeasonsReport'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>> 'SeasonsReport': Config file not found:
>> "/etc/weewx/skins/Seasons/skin.conf".
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>> 'SeasonsReport': Config file not found:
>> "/etc/weewx/skins/Seasons/lang/en.conf".
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: 
>> Using defaults instead.
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
>> generators for report 'SeasonsReport' in directory
>> '/etc/weewx/skins/Seasons'
>> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No
>> generators specified for report 'SeasonsReport'
>>
>> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>>
>>> So WeeWX cannot find the Seasons skin.conf, what is the contends of
>>> /etc/weewx/skins/Seasons?
>>>
>>> Also, you seem to be truncating some of the log lines, it would help if
>>> we could see the rest of the line:
>>>
>>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>>> 'SeasonsReport':>
>>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>>> 'SeasonsReport': Co>
>>>
>>> For info, a package install has the skins directory in /etc/weewx, it
>>> has never been in /usr/share/weewx, refer to Where to find things
>>>  in the User's Guide.
>>>
>>> Gary
>>>
>>> On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com
>>> wrote:
>>>
 It thinks that the skins are still in /etc/weewx instead of
 /usr/share/weewx.

 -- Boot bc88a89987b645f18a3473d5771ebb26 --
 Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing
 weewxd version 5.0.1
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line:
 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python
 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at
 /usr/bin/python3
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform
 Linux-6.5.0-15-generic-x86_64-with-glibc2.35
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale:
 'en_US.UTF-8'
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path:
 /usr/share/weewx/weewxd.py
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT:
 /etc/weewx
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration
 file: /etc/weewx/weewx.conf
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module:
 /etc/weewx/bin/user
 Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
 Feb 06 13:23:00 inspiron weewxd[692]: DEBUG __main__: Initializing
 engine
 Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Feb 06 13:23:00 inspiron weewx

Re: [weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Tom Keffer]

No, you're not hallucinating! That detail was changed between v5.0.0 and
v5.0.1. We should have called that out.

On Tue, Feb 6, 2024 at 3:11 PM Mark Conner  wrote:

> I see now that I misread the upgrade page, and indeed it was advertised -
> my apologies for saying it wasn't.  When I was reading the docs prior to
> the 5.0 upgrade, I thought it said that it would honor previous installs
> running as root and so I didn't worry about it for 5.0.  But it really says
> it will honor previous installs for a user *other than* root.
>
> - Mark
>
> On Tue, Feb 6, 2024 at 4:50 PM Tom Keffer  wrote:
>
>> See the Upgrade Guide section *WeeWX runs as the weewx user
>> *.
>>
>> On Tue, Feb 6, 2024 at 12:05 PM Mark Conner  wrote:
>>
>>> By chance, I just read the previous message thread and was able to use
>>> that to fix my issue.  The issue for me centered around the change from
>>> running weewx as 'root' in 5.0 and before, to running as user 'weewx' in
>>> 5.0.1.  I added user 'weewx' to the group 'dialout' so it could access
>>> /dev/ttyAMA0 and everything works again.
>>>
>>> sudo usermod -a -G dialout weewx
>>>
>>> I think this change in 5.0.1 from running as 'root' to running as
>>> 'weewx' needs to be more strongly advertised.  This may be problematic for
>>> users who upgraded from v4.x and still run weewx as root.
>>>
>>> - Mark
>>>
>>> On Tuesday, February 6, 2024 at 1:45:35 PM UTC-6 Mark Conner wrote:
>>>
 Hi,

 I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on
 my Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
 weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
 MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
 5.0.0 and still have the same issue.  Here are the weewxd related lines
 from startup from /var/log/syslog:

 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__:
> Initializing weewxd version 5.0.0
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command
> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using
> Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
> /usr/bin/python3
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
> Linux-6.1.21-v7+-armv7l-with-glibc2.31
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale:
> 'en_US'
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry
> path: /usr/share/weewx/weewxd.py
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__:
> WEEWX_ROOT: /
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__:
> Configuration file: /etc/weewx/weewx.conf
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User
> module: /etc/weewx/bin/user
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine:
> Loading station type Vantage (weewx.drivers.vantage)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine:
> Import of driver failed: [Errno 13] could not open port /dev/ttyAMA0:
> [Errno 13] Permission denied: '/dev/ttyAMA0' ( 'serial.serialutil.SerialException'>)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     Traceback (most recent call last):
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   File
> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
> in open
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
> os.O_NONBLOCK)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     During handling of the above exception, another exception 
> occurred:
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     Traceback (most recent call last):
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   File "/usr/share/weewx/weewx/engine.py", line 115, in 
> setupStation
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>     self.console = loader_function(config_dict, self)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   

Re: [weewx-user] Re: No updates to /var/www/html/weewx

[Tom Keffer]

Yes, it's true that there is a copy of the v5.0 skins in
/usr/share/weewx/weewx_data/skins. This is what Python calls "package data
." It is
used by "weectl station create" to create a new station data area. weectl
copies it over from its obscure location to the new station data. It is not
intended to be used by the user, mostly because it's buried so deep in the
Python library.

As for why weewxd cannot read a file which is plainly there, the only thing
I can think of is that the intervening directories in /etc/weewx/skins are
not giving it permission. Check that they are all owned by user "weewx",
and have 644 permissions

Not sure what caused this, but I would guess it's because Debian
is treating the skins as config files, which it deleted on the upgrade.
Matthew would know more about this. It would help if you have the original
upgrade commands and response from apt.

-tk


On Tue, Feb 6, 2024 at 3:05 PM Philip Wolff  wrote:

> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including
> the skins data, in /usr/share/weewx.
>
> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>
> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and
> veriified that Seasons/skin.conf is there. I restarted weewxk and it still
> claims that it can't read Seasons/skin.conf.
>
> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48
> /etc/weewx/skins/Seasons/skin.conf
> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48
> /etc/weewx/skins/Seasons/lang/en.conf
> philbert@inspiron:~$
>
> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record
> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
> reports for latest time in the database.
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
> report 'SeasonsReport'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
> 'SeasonsReport': Config file not found:
> "/etc/weewx/skins/Seasons/skin.conf".
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot
> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
> 'SeasonsReport': Config file not found:
> "/etc/weewx/skins/Seasons/lang/en.conf".
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine:  Using
> defaults instead.
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running
> generators for report 'SeasonsReport' in directory
> '/etc/weewx/skins/Seasons'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No
> generators specified for report 'SeasonsReport'
>
> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>
>> So WeeWX cannot find the Seasons skin.conf, what is the contends of
>> /etc/weewx/skins/Seasons?
>>
>> Also, you seem to be truncating some of the log lines, it would help if
>> we could see the rest of the line:
>>
>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report
>> 'SeasonsReport':>
>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot
>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report
>> 'SeasonsReport': Co>
>>
>> For info, a package install has the skins directory in /etc/weewx, it
>> has never been in /usr/share/weewx, refer to Where to find things
>>  in the User's Guide.
>>
>> Gary
>>
>> On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com
>> wrote:
>>
>>> It thinks that the skins are still in /etc/weewx instead of
>>> /usr/share/weewx.
>>>
>>> -- Boot bc88a89987b645f18a3473d5771ebb26 --
>>> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing weewxd
>>> version 5.0.1
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line:
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python
>>> 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at
>>> /usr/bin/python3
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform
>>> Linux-6.5.0-15-generic-x86_64-with-glibc2.35
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale:
>>> 'en_US.UTF-8'
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path:
>>> /usr/share/weewx/weewxd.py
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT:
>>> /etc/weewx
>>

[weewx-user] Re: No updates to /var/www/html/weewx

[gjr80]

I can't see anything obviously wrong. WeeWX is looking in the right place 
and the .conf files exist. read only permission is fine. Let me see if I 
can replicate this, what Ubuntu version?

Gary

On Wednesday 7 February 2024 at 09:05:49 UTC+10 philip...@gmail.com wrote:

> The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including 
> the skins data, in /usr/share/weewx.
>
> /etc/weewx/skins contains three empty folders: font, lang, and NOAA.
>
> I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and 
> veriified that Seasons/skin.conf is there. I restarted weewxk and it still 
> claims that it can't read Seasons/skin.conf.
>
> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
> -rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48 
> /etc/weewx/skins/Seasons/skin.conf
> philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
> -rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48 
> /etc/weewx/skins/Seasons/lang/en.conf
> philbert@inspiron:~$
>
> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record 
> 2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
> Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record 
> 2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
> reports for latest time in the database.
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
> report 'SeasonsReport'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot 
> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport': Config file not found: 
> "/etc/weewx/skins/Seasons/skin.conf".
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot 
> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report 
> 'SeasonsReport': Config file not found: 
> "/etc/weewx/skins/Seasons/lang/en.conf".
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine:  Using 
> defaults instead.
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
> generators for report 'SeasonsReport' in directory 
> '/etc/weewx/skins/Seasons'
> Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No 
> generators specified for report 'SeasonsReport'
>
> On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:
>
>> So WeeWX cannot find the Seasons skin.conf, what is the contends of 
>> /etc/weewx/skins/Seasons? 
>>
>> Also, you seem to be truncating some of the log lines, it would help if 
>> we could see the rest of the line:
>>
>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot 
>> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report 
>> 'SeasonsReport':>
>> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot 
>> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report 
>> 'SeasonsReport': Co>
>>
>> For info, a package install has the skins directory in /etc/weewx, it 
>> has never been in /usr/share/weewx, refer to Where to find things 
>>  in the User's Guide.
>>
>> Gary
>>
>> On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com 
>> wrote:
>>
>>> It thinks that the skins are still in /etc/weewx instead of 
>>> /usr/share/weewx.
>>>
>>> -- Boot bc88a89987b645f18a3473d5771ebb26 --
>>> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing weewxd 
>>> version 5.0.1
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line: 
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python 
>>> 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at 
>>> /usr/bin/python3
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform 
>>> Linux-6.5.0-15-generic-x86_64-with-glibc2.35
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale: 
>>> 'en_US.UTF-8'
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path: 
>>> /usr/share/weewx/weewxd.py
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT: 
>>> /etc/weewx
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration file: 
>>> /etc/weewx/weewx.conf
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module: 
>>> /etc/weewx/bin/user
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
>>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG __main__: Initializing engine
>>> Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Loading station 
>>> type Vantage (weewx.drivers.vantage)
>>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
>>> Driver version is 3.6.2
>>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
>>> Option loop_request=1
>>> Feb 06 13:23:00 inspiron weewxd[692

Re: [weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Mark Conner]

I see now that I misread the upgrade page, and indeed it was advertised -
my apologies for saying it wasn't.  When I was reading the docs prior to
the 5.0 upgrade, I thought it said that it would honor previous installs
running as root and so I didn't worry about it for 5.0.  But it really says
it will honor previous installs for a user *other than* root.

- Mark

On Tue, Feb 6, 2024 at 4:50 PM Tom Keffer  wrote:

> See the Upgrade Guide section *WeeWX runs as the weewx user
> *.
>
> On Tue, Feb 6, 2024 at 12:05 PM Mark Conner  wrote:
>
>> By chance, I just read the previous message thread and was able to use
>> that to fix my issue.  The issue for me centered around the change from
>> running weewx as 'root' in 5.0 and before, to running as user 'weewx' in
>> 5.0.1.  I added user 'weewx' to the group 'dialout' so it could access
>> /dev/ttyAMA0 and everything works again.
>>
>> sudo usermod -a -G dialout weewx
>>
>> I think this change in 5.0.1 from running as 'root' to running as 'weewx'
>> needs to be more strongly advertised.  This may be problematic for users
>> who upgraded from v4.x and still run weewx as root.
>>
>> - Mark
>>
>> On Tuesday, February 6, 2024 at 1:45:35 PM UTC-6 Mark Conner wrote:
>>
>>> Hi,
>>>
>>> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on
>>> my Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
>>> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
>>> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
>>> 5.0.0 and still have the same issue.  Here are the weewxd related lines
>>> from startup from /var/log/syslog:
>>>
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing
 weewxd version 5.0.0
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command
 line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using
 Python 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
 /usr/bin/python3
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
 Linux-6.1.21-v7+-armv7l-with-glibc2.31
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale:
 'en_US'
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path:
 /usr/share/weewx/weewxd.py
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT:
 /
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__:
 Configuration file: /etc/weewx/weewx.conf
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User
 module: /etc/weewx/bin/user
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading
 station type Vantage (weewx.drivers.vantage)
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import
 of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13]
 Permission denied: '/dev/ttyAMA0' (>>> 'serial.serialutil.SerialException'>)
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   Traceback (most recent call last):
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 File
 "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
 in open
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
 os.O_NONBLOCK)
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   During handling of the above exception, another exception occurred:
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   Traceback (most recent call last):
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   self.console = loader_function(config_dict, self)
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in 
 loader
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
   return VantageService(engine, config_dict)
 Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
 File "/us

[weewx-user] Re: No updates to /var/www/html/weewx

[Philip Wolff]

The Ubuntu package for weewx 5.0.1-3 installs a ton of stuff, including the 
skins data, in /usr/share/weewx.

/etc/weewx/skins contains three empty folders: font, lang, and NOAA.

I copied /usr/shared/weewx/weewx_data/skins to /etc/weewx/skins and 
veriified that Seasons/skin.conf is there. I restarted weewxk and it still 
claims that it can't read Seasons/skin.conf.

philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/skin.conf
-rw-r--r-- 1 weewx weewx 27403 Feb  4 18:48 
/etc/weewx/skins/Seasons/skin.conf
philbert@inspiron:~$ ll /etc/weewx/skins/Seasons/lang/en.conf
-rw-r--r-- 1 weewx weewx 9459 Feb  4 18:48 
/etc/weewx/skins/Seasons/lang/en.conf
philbert@inspiron:~$

Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record 
2024-02-06 14:15:00 PST (1707257700) to database 'weewx.sdb'
Feb 06 14:15:15 inspiron weewxd[700]: INFO weewx.manager: Added record 
2024-02-06 14:15:00 PST (1707257700) to daily summary in 'weewx.sdb'
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
reports for latest time in the database.
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
report 'SeasonsReport'
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot read 
skin configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport': Config file not found: 
"/etc/weewx/skins/Seasons/skin.conf".
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Cannot read 
localization file /etc/weewx/skins/Seasons/lang/en.conf for report 
'SeasonsReport': Config file not found: 
"/etc/weewx/skins/Seasons/lang/en.conf".
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine:  Using 
defaults instead.
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: Running 
generators for report 'SeasonsReport' in directory 
'/etc/weewx/skins/Seasons'
Feb 06 14:15:15 inspiron weewxd[700]: DEBUG weewx.reportengine: No 
generators specified for report 'SeasonsReport'

On Tuesday, February 6, 2024 at 2:10:19 PM UTC-8 gjr80 wrote:

> So WeeWX cannot find the Seasons skin.conf, what is the contends of 
> /etc/weewx/skins/Seasons? 
>
> Also, you seem to be truncating some of the log lines, it would help if we 
> could see the rest of the line:
>
> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot 
> read skin configuration file /etc/weewx/skins/Seasons/skin.conf for report 
> 'SeasonsReport':>
> Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot 
> read localization file /etc/weewx/skins/Seasons/lang/en.conf for report 
> 'SeasonsReport': Co>
>
> For info, a package install has the skins directory in /etc/weewx, it has 
> never been in /usr/share/weewx, refer to Where to find things 
>  in the User's Guide.
>
> Gary
>
> On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com wrote:
>
>> It thinks that the skins are still in /etc/weewx instead of 
>> /usr/share/weewx.
>>
>> -- Boot bc88a89987b645f18a3473d5771ebb26 --
>> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing weewxd 
>> version 5.0.1
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python 3.10.12 
>> (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform 
>> Linux-6.5.0-15-generic-x86_64-with-glibc2.35
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale: 'en_US.UTF-8'
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration file: 
>> /etc/weewx/weewx.conf
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG __main__: Initializing engine
>> Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Driver 
>> version is 3.6.2
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Option 
>> loop_request=1
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Opened 
>> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
>> Successfully woke up Vantage console
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
>> Hardware type is 16
>> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: ISS ID 
>> is 1
>> Feb 06 13:23:00 inspiron 

Re: [weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Tom Keffer]

See the Upgrade Guide section *WeeWX runs as the weewx user
*.

On Tue, Feb 6, 2024 at 12:05 PM Mark Conner  wrote:

> By chance, I just read the previous message thread and was able to use
> that to fix my issue.  The issue for me centered around the change from
> running weewx as 'root' in 5.0 and before, to running as user 'weewx' in
> 5.0.1.  I added user 'weewx' to the group 'dialout' so it could access
> /dev/ttyAMA0 and everything works again.
>
> sudo usermod -a -G dialout weewx
>
> I think this change in 5.0.1 from running as 'root' to running as 'weewx'
> needs to be more strongly advertised.  This may be problematic for users
> who upgraded from v4.x and still run weewx as root.
>
> - Mark
>
> On Tuesday, February 6, 2024 at 1:45:35 PM UTC-6 Mark Conner wrote:
>
>> Hi,
>>
>> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my
>> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
>> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
>> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
>> 5.0.0 and still have the same issue.  Here are the weewxd related lines
>> from startup from /var/log/syslog:
>>
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing
>>> weewxd version 5.0.0
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command
>>> line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python
>>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
>>> /usr/bin/python3
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
>>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale:
>>> 'en_US'
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path:
>>> /usr/share/weewx/weewxd.py
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__:
>>> Configuration file: /etc/weewx/weewx.conf
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module:
>>> /etc/weewx/bin/user
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading
>>> station type Vantage (weewx.drivers.vantage)
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import
>>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13]
>>> Permission denied: '/dev/ttyAMA0' (>> 'serial.serialutil.SerialException'>)
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   Traceback (most recent call last):
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> File
>>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
>>> in open
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
>>> os.O_NONBLOCK)
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> 
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   During handling of the above exception, another exception occurred:
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> 
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   Traceback (most recent call last):
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   self.console = loader_function(config_dict, self)
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   return VantageService(engine, config_dict)
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in
>>> __init__
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in
>>> __init__
>>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>>   self.port.openPort()
>>> Feb  6 13:29:00 raspberrypi110 weewxd[283

[weewx-user] Re: No updates to /var/www/html/weewx

[gjr80]

So WeeWX cannot find the Seasons skin.conf, what is the contends of 
/etc/weewx/skins/Seasons? 

Also, you seem to be truncating some of the log lines, it would help if we 
could see the rest of the line:

Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot read 
skin configuration file /etc/weewx/skins/Seasons/skin.conf for report 
'SeasonsReport':>
Feb 06 13:25:15 inspiron weewxd[692]: DEBUG weewx.reportengine: Cannot read 
localization file /etc/weewx/skins/Seasons/lang/en.conf for report 
'SeasonsReport': Co>

For info, a package install has the skins directory in /etc/weewx, it has 
never been in /usr/share/weewx, refer to Where to find things 
 in the User's Guide.

Gary

On Wednesday 7 February 2024 at 07:57:20 UTC+10 philip...@gmail.com wrote:

> It thinks that the skins are still in /etc/weewx instead of 
> /usr/share/weewx.
>
> -- Boot bc88a89987b645f18a3473d5771ebb26 --
> Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing weewxd 
> version 5.0.1
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line: 
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python 3.10.12 
> (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at 
> /usr/bin/python3
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform 
> Linux-6.5.0-15-generic-x86_64-with-glibc2.35
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale: 'en_US.UTF-8'
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path: 
> /usr/share/weewx/weewxd.py
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT: /etc/weewx
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration file: 
> /etc/weewx/weewx.conf
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module: 
> /etc/weewx/bin/user
> Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG __main__: Initializing engine
> Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Driver 
> version is 3.6.2
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Option 
> loop_request=1
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Opened 
> up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
> Successfully woke up Vantage console
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
> Hardware type is 16
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: ISS ID 
> is 1
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
> Hardware name: Vantage Pro2
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdTimeSynch
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdTimeSynch
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdConvert
> Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: StdConvert target 
> unit is 0x1
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdConvert
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdCalibrate
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdCalibrate
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.engine.StdQC
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.engine.StdQC
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.wxservices.StdWXCalculate
> Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.manager: Daily summary 
> version is 4.0
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.wxservices.StdWXCalculate
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdWXXTypes
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdWXXTypes
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdPressureCooker
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.wxxtypes.StdPressureCooker
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
> weewx.wxxtypes.StdRainRater
> Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
> service weewx.wxxty

[weewx-user] Re: No updates to /var/www/html/weewx

[Philip Wolff]

It thinks that the skins are still in /etc/weewx instead of 
/usr/share/weewx.

-- Boot bc88a89987b645f18a3473d5771ebb26 --
Feb 06 13:22:59 inspiron systemd[1]: Started WeeWX.
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Initializing weewxd 
version 5.0.1
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Command line: 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Using Python 3.10.12 
(main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Located at 
/usr/bin/python3
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Platform 
Linux-6.5.0-15-generic-x86_64-with-glibc2.35
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Locale: 'en_US.UTF-8'
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Entry path: 
/usr/share/weewx/weewxd.py
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: WEEWX_ROOT: /etc/weewx
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Configuration file: 
/etc/weewx/weewx.conf
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: User module: 
/etc/weewx/bin/user
Feb 06 13:23:00 inspiron weewxd[692]: INFO __main__: Debug: 1
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG __main__: Initializing engine
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Driver 
version is 3.6.2
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Option 
loop_request=1
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Opened 
up serial port /dev/ttyUSB0; baud 19200; timeout 4.00
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: 
Successfully woke up Vantage console
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Hardware 
type is 16
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: ISS ID 
is 1
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.drivers.vantage: Hardware 
name: Vantage Pro2
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.engine.StdTimeSynch
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.engine.StdTimeSynch
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.engine.StdConvert
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: StdConvert target 
unit is 0x1
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.engine.StdConvert
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.engine.StdCalibrate
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.engine.StdCalibrate
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.engine.StdQC
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.engine.StdQC
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.wxservices.StdWXCalculate
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.wxservices: StdWXCalculate 
will use data binding wx_binding
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.manager: Daily summary 
version is 4.0
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.wxservices.StdWXCalculate
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdWXXTypes
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdWXXTypes
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdPressureCooker
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdPressureCooker
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdRainRater
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdRainRater
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.wxxtypes.StdDelta
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.wxxtypes.StdDelta
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Loading service 
weewx.engine.StdArchive
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Archive will use 
data binding wx_binding
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Feb 06 13:23:00 inspiron weewxd[692]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Use LOOP data in 
hi/low calculations: 1
Feb 06 13:23:00 inspiron weewxd[692]: DEBUG weewx.engine: Finished loading 
service weewx.engine.StdArchive
Feb 06 

[weewx-user] Re: New User: First Problem

[gjr80]

This is unlikely to be a units problem, rather it is likely to be one of 
incorrect (or a lack of) data from the station. FineOffset stations provide 
the WeeWX field pressure and WeeWX will then calculate fields barometer and 
altimeter if possible. The log entry provided indicates that WeeWX has 
ended up with a pressure value of zero which is outside the (default) QC 
limits set in [StdQC] [[MinMax]] in weewx.conf. You need to be looking at 
what data is being emitted by the station/driver; with the fousb driver you 
should be able to use weectl device 
 to interrogate the 
station and, among other things, display live data from the station 
. The result 
may well give you an indication of where the problem is.

As an aside the units used within the [StdQC] [[MinMax]] stanza and the 
display units in reports (or on a station hardware display) bear no direct 
relationship. [[MinMax]] settings default to the units used in the WeeWX 
database; however, units can be specified. As it happens the default 
[[MinMax]] settings have US customary units specified. You may find it 
beneficial to read through the [StdQC] reference 
.

Gary
On Wednesday 7 February 2024 at 07:03:37 UTC+10 gszla...@gmail.com wrote:

> I'll take a wild guess..maybe it's a unit mismatch of some sort. Try 
> switching your console to inHg instead of hPa (temporarily) and see if that 
> works.
>
> On Tuesday, February 6, 2024 at 7:05:58 AM UTC-5 michael.k...@gmx.at 
> wrote:
>
>> The warning tells you: WeeWX is receiving 0.0 for "pressure". You say, 
>> "The hardware console is operating correctly as expected", so the problem 
>> is somewhere in between the hardware and the LOOP. It may be, that your 
>> hardware/driver combination doesn't supply a valid value for "pressure" (it 
>> should return "None" instead of "0.0" in this case), did you try 
>> "barometer" or "altimeter" instead? You can also check in your database, if 
>> there are values for these types. If so, take a look into this article 
>> , 
>> to make sure, you really use the correct type for your needs. Having only 
>> one out of the three "pressure", "altimeter" and "barometer", it should be 
>> possible to calculate the others, when you have the altitude, the 
>> temperature and humidity (or even something in addition to that).
>>
>> Alan Salmon schrieb am Dienstag, 6. Februar 2024 um 12:48:48 UTC+1:
>>
>>> Hello everyone.
>>>
>>> I installed weewx for the first time today on a Raspberry Pi Zero 2W, 
>>> using a Fine Offset 3081 station that I used for about 10 years until the 
>>> local cockatoos decided it would be fun to dismantle it!
>>>
>>> It came up on the second attempt after a few minor adjustments to the 
>>> config file, paths, etc. (I used the pip install method on Debian 11).
>>>
>>> The hardware console is operating correctly as expected, but weewx is 
>>> giving me the following error:
>>>
>>> Feb  6 22:26:01 bigfish-08 weewxd[1909]: WARNING weewx.qc: 2024-02-06 
>>> 22:26:02 AEDT (1707218762) LOOP value 'pressure' 0.0 outside limits (24.0, 
>>> 34.5)
>>>
>>> As the value displayed on the console (roughly) agrees with a BME680 I 
>>> have running, can anyone suggest where I should start trying to solve this?
>>>
>>> Note that I am configured for metric with barometric pressure in 
>>> hectopascals (hPa) which is currently just over 1010hPa, so I am at a bit 
>>> of a loss as to why it is showing '0.0' and where the range "24.0 to 34.5' 
>>> comes from.
>>>
>>> The error has been consistent for the 9 hours it has been running.
>>>
>>> Thanks for any advice you can offer.
>>>
>>>
>>>

-- 
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/1d99220d-4d18-42e6-802b-126bbf1ebc53n%40googlegroups.com.

[weewx-user] Re: New User: First Problem

[gszla...@gmail.com]

I'll take a wild guess..maybe it's a unit mismatch of some sort. Try 
switching your console to inHg instead of hPa (temporarily) and see if that 
works.

On Tuesday, February 6, 2024 at 7:05:58 AM UTC-5 michael.k...@gmx.at wrote:

> The warning tells you: WeeWX is receiving 0.0 for "pressure". You say, 
> "The hardware console is operating correctly as expected", so the problem 
> is somewhere in between the hardware and the LOOP. It may be, that your 
> hardware/driver combination doesn't supply a valid value for "pressure" (it 
> should return "None" instead of "0.0" in this case), did you try 
> "barometer" or "altimeter" instead? You can also check in your database, if 
> there are values for these types. If so, take a look into this article 
> , 
> to make sure, you really use the correct type for your needs. Having only 
> one out of the three "pressure", "altimeter" and "barometer", it should be 
> possible to calculate the others, when you have the altitude, the 
> temperature and humidity (or even something in addition to that).
>
> Alan Salmon schrieb am Dienstag, 6. Februar 2024 um 12:48:48 UTC+1:
>
>> Hello everyone.
>>
>> I installed weewx for the first time today on a Raspberry Pi Zero 2W, 
>> using a Fine Offset 3081 station that I used for about 10 years until the 
>> local cockatoos decided it would be fun to dismantle it!
>>
>> It came up on the second attempt after a few minor adjustments to the 
>> config file, paths, etc. (I used the pip install method on Debian 11).
>>
>> The hardware console is operating correctly as expected, but weewx is 
>> giving me the following error:
>>
>> Feb  6 22:26:01 bigfish-08 weewxd[1909]: WARNING weewx.qc: 2024-02-06 
>> 22:26:02 AEDT (1707218762) LOOP value 'pressure' 0.0 outside limits (24.0, 
>> 34.5)
>>
>> As the value displayed on the console (roughly) agrees with a BME680 I 
>> have running, can anyone suggest where I should start trying to solve this?
>>
>> Note that I am configured for metric with barometric pressure in 
>> hectopascals (hPa) which is currently just over 1010hPa, so I am at a bit 
>> of a loss as to why it is showing '0.0' and where the range "24.0 to 34.5' 
>> comes from.
>>
>> The error has been consistent for the 9 hours it has been running.
>>
>> Thanks for any advice you can offer.
>>
>>
>>

-- 
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/f4e0377e-2528-45c0-940f-e230ff61259en%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[gjr80]

Impossible to say what the issue is with such a short log extract. Please 
edit weewx.conf, set debug =1, save weewx.conf and restart WeeWX. Let WeeWX 
run for at least two archive intervals and then take a log extract showing 
the full WeeWX startup through until the two archive intervals have 
elapsed. Post the log extract here.

Gary 

On Wednesday 7 February 2024 at 05:23:35 UTC+10 philip...@gmail.com wrote:

> Thanks for that tip - it got me off the ground. All is now well except 
> that /var/www/html/weewx hasn't been updated since just before I did the 
> upgrade to 5.0.1. Anyone else seeing this?
>
> On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:
>
>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and 
>> serial datalogger had ownership set to root:dialout, so I had to add the 
>> weewx user to the dialout group for things to work. 
>>
>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>>
>>> when you install rtl-sdr, it typically, but not always, installs udev 
>>> rules for *many* sdr devices.  the udev rules that it installs make it 
>>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>>> device.  (this is true when you install rtl-sdr from source - if you 
>>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>>> this configuration please let us know)
>>>
>>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>>> what the udev rules might be
>>>
>>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>>> non-root user (for pip installs).  so udev rules are required.
>>>
>>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>>> (it would continue to run as root - we changed in 5.0.1 because overall 
>>> security and best practice)
>>>
>>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>>> since the user 'weewx' is not in the plugdev group.  you can either added 
>>> the user weewx to the plugdev group, or modify the udev rules to use 
>>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>>
>>> sudo usermod -aG plugdev weewx
>>>
>>> for a pip install, be sure that the user running weewx is in the 
>>> 'plugdev' group.
>>>
>>> restart of the weewxd daemon is almost certainly required so that the 
>>> daemon process has the right group.  reboot is not necessary.
>>>
>>> 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/f74ff6b5-238f-4823-b82f-c01864f4f00dn%40googlegroups.com.

[weewx-user] Re: No updates to /var/www/html/weewx

[gjr80]

Impossible to say what the issue is with such a short log extract. Please 
edit weewx.conf, set debug =1, save weewx.conf and restart WeeWX. Let WeeWX 
run for at least two archive intervals and then take a log extract showing 
the full WeeWX startup through until the two archive intervals have 
elapsed. Post the log extract here.

Gary 

On Wednesday 7 February 2024 at 06:33:54 UTC+10 philip...@gmail.com wrote:

> I'm configured for reports using the Seasons skin and data publishing to 
> CWOP and Wunderground.
>
> After updating from  4.10.2 to 5.0.1, I'm seeing the following in the 
> systemd journal every 5 minutes:
> Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.manager: Added record 
> 2024-02-06 12:10:00 PST (1707250200) to database 'weewx.sdb'
> Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.manager: Added record 
> 2024-02-06 12:10:00 PST (1707250200) to daily summary in 'weewx.sdb'
> Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.restx: CWOP: Published 
> record 2024-02-06 12:10:00 PST (1707250200)
> Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.restx: Wunderground-PWS: 
> Published record 2024-02-06 12:10:00 PST (1707250200)
>
> No mention of report generation, and the Seasons data displayed in Firefox 
> hasn't changed since I installed the update.
>
> What could I have done to cause this?
>
>

-- 
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/3c3e2314-6116-403b-a9c9-6b2ead05cf46n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Philip Wolff]

Yes, and data is being sent to CWOP and Wunderground.

On Tue, Feb 6, 2024, 12:26 Jeff A. D.  wrote:

> Is your database being updated?
>
> On Tuesday, February 6, 2024 at 12:23:35 PM UTC-7 Philip Wolff wrote:
>
>> Thanks for that tip - it got me off the ground. All is now well except
>> that /var/www/html/weewx hasn't been updated since just before I did the
>> upgrade to 5.0.1. Anyone else seeing this?
>>
>> On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:
>>
>>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and
>>> serial datalogger had ownership set to root:dialout, so I had to add the
>>> weewx user to the dialout group for things to work.
>>>
>>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>>>
 when you install rtl-sdr, it typically, but not always, installs udev
 rules for *many* sdr devices.  the udev rules that it installs make it
 possible for anyone in the 'plugdev' group to read/write to the sdr
 device.  (this is true when you install rtl-sdr from source - if you
 install rtl-sdr from a deb/rpm package, it might be different - anyone with
 this configuration please let us know)

 weewx v4 runs as root:root, so it has access to the sdr device no
 matter what the udev rules might be

 weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular
 non-root user (for pip installs).  so udev rules are required.

 btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did
 not (it would continue to run as root - we changed in 5.0.1 because overall
 security and best practice)

 the udev rules installed by rtl-sdr will not help for a deb/rpm
 install, since the user 'weewx' is not in the plugdev group.  you can
 either added the user weewx to the plugdev group, or modify the udev rules
 to use 'weewx' instead of 'plugdev' as the group.  this is how to do the
 former:

 sudo usermod -aG plugdev weewx

 for a pip install, be sure that the user running weewx is in the
 'plugdev' group.

 restart of the weewxd daemon is almost certainly required so that the
 daemon process has the right group.  reboot is not necessary.

 m

>>> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/5BuR3BSQfeY/unsubscribe.
> To unsubscribe from this group and all its topics, 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/872b0b73-d942-487d-bbe3-61883e3d00aen%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/CAP14646WOxWrdymeyj_JATGnSFjcNdYPW%3DGAv1EzzFSSZ2iDCA%40mail.gmail.com.

[weewx-user] No updates to /var/www/html/weewx

[Philip Wolff]

I'm configured for reports using the Seasons skin and data publishing to 
CWOP and Wunderground.

After updating from  4.10.2 to 5.0.1, I'm seeing the following in the 
systemd journal every 5 minutes:
Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.manager: Added record 
2024-02-06 12:10:00 PST (1707250200) to database 'weewx.sdb'
Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.manager: Added record 
2024-02-06 12:10:00 PST (1707250200) to daily summary in 'weewx.sdb'
Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.restx: CWOP: Published 
record 2024-02-06 12:10:00 PST (1707250200)
Feb 06 12:10:17 inspiron weewxd[680]: INFO weewx.restx: Wunderground-PWS: 
Published record 2024-02-06 12:10:00 PST (1707250200)

No mention of report generation, and the Seasons data displayed in Firefox 
hasn't changed since I installed the update.

What could I have done to cause this?

-- 
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/cd6a49cf-8a80-4fe9-9ff1-49c03a9fec61n%40googlegroups.com.

[weewx-user] Re: V5.0.1 and rsyslog

[matthew wall]

please take a look at the wiki page "How to configure logging"

https://github.com/weewx/weewx/wiki/logging

the "weewxd.py.log" smells like a mixed up systemd configuration.  be sure 
that you are using the units installed by weewx (in /usr/lib/systemd) and 
that there are not any units in /etc/systemd leftover from v4 or 
inadvertently deployed somehow. also, be sure to remove anything related to 
weewx from /etc/init.d and the corresponding /etc/rcN.d (those will be 
symlinks). systemd silently ignores sysv links and files if they overlap 
with definitions in the unit files, but you might have something leftover 
from the weewx-multi script.

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/2d5d9cfe-42e5-4e4b-9274-05a513af0669n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Jeff A. D.]

Is your database being updated?

On Tuesday, February 6, 2024 at 12:23:35 PM UTC-7 Philip Wolff wrote:

> Thanks for that tip - it got me off the ground. All is now well except 
> that /var/www/html/weewx hasn't been updated since just before I did the 
> upgrade to 5.0.1. Anyone else seeing this?
>
> On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:
>
>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and 
>> serial datalogger had ownership set to root:dialout, so I had to add the 
>> weewx user to the dialout group for things to work. 
>>
>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>>
>>> when you install rtl-sdr, it typically, but not always, installs udev 
>>> rules for *many* sdr devices.  the udev rules that it installs make it 
>>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>>> device.  (this is true when you install rtl-sdr from source - if you 
>>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>>> this configuration please let us know)
>>>
>>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>>> what the udev rules might be
>>>
>>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>>> non-root user (for pip installs).  so udev rules are required.
>>>
>>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>>> (it would continue to run as root - we changed in 5.0.1 because overall 
>>> security and best practice)
>>>
>>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>>> since the user 'weewx' is not in the plugdev group.  you can either added 
>>> the user weewx to the plugdev group, or modify the udev rules to use 
>>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>>
>>> sudo usermod -aG plugdev weewx
>>>
>>> for a pip install, be sure that the user running weewx is in the 
>>> 'plugdev' group.
>>>
>>> restart of the weewxd daemon is almost certainly required so that the 
>>> daemon process has the right group.  reboot is not necessary.
>>>
>>> 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/872b0b73-d942-487d-bbe3-61883e3d00aen%40googlegroups.com.

[weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Karen K]

WeeWX 4.* runs as root. WeeWX 5.* does not run as root. As you write the 
permissions of /dev/ttyAMA0 are user root and group dialout. You may 
include the user weewx into group dialout or follow the instructions Tom 
and Matthew gave in several of the previous threads regarding this issue.

Mark Conner schrieb am Dienstag, 6. Februar 2024 um 20:45:35 UTC+1:

> Hi,
>
> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my 
> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start 
> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a 
> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to 
> 5.0.0 and still have the same issue.  Here are the weewxd related lines 
> from startup from /var/log/syslog: 
>
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing 
>> weewxd version 5.0.0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python 
>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform 
>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale: 
>> 'en_US'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration 
>> file: /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13] 
>> Permission denied: '/dev/ttyAMA0' (> 'serial.serialutil.SerialException'>)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File 
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322, 
>> in open
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
>> os.O_NONBLOCK)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.port.openPort()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
>> openPort
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.serial_port = serial.Serial(self.port, self.baudrate, 
>> timeout=self.timeout)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/local/lib/python3.9/dist-packages/serial/serialutil.py", 
>> line 2

Re: [weewx-user] Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Warren Gill]

Try adding weewx user to the dialout group and restarting weewx:

sudo usermod -aG dialout weewx
sudo systemctl restart weewx



On Tue, Feb 6, 2024 at 1:45 PM Mark Conner  wrote:

> Hi,
>
> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my
> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
> 5.0.0 and still have the same issue.  Here are the weewxd related lines
> from startup from /var/log/syslog:
>
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing
>> weewxd version 5.0.0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line:
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python
>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
>> /usr/bin/python3
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale:
>> 'en_US'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path:
>> /usr/share/weewx/weewxd.py
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration
>> file: /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module:
>> /etc/weewx/bin/user
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading
>> station type Vantage (weewx.drivers.vantage)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import
>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13]
>> Permission denied: '/dev/ttyAMA0' (> 'serial.serialutil.SerialException'>)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
>> in open
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
>> os.O_NONBLOCK)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> 
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   During handling of the above exception, another exception occurred:
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> 
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.console = loader_function(config_dict, self)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   return VantageService(engine, config_dict)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.port.openPort()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in
>> openPort
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.serial_port = serial.Serial(self.port, self.baudrate,
>> timeout=self.timeout)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/local/lib/python3.9/dist-packages/serial/serialutil.py",
>> line 244, in __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.open()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 325,
>> in open
>> Feb  6 13:29:00 

[weewx-user] Re: Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Mark Conner]

By chance, I just read the previous message thread and was able to use that 
to fix my issue.  The issue for me centered around the change from running 
weewx as 'root' in 5.0 and before, to running as user 'weewx' in 5.0.1.  I 
added user 'weewx' to the group 'dialout' so it could access /dev/ttyAMA0 
and everything works again.

sudo usermod -a -G dialout weewx 

I think this change in 5.0.1 from running as 'root' to running as 'weewx' 
needs to be more strongly advertised.  This may be problematic for users 
who upgraded from v4.x and still run weewx as root.

- Mark

On Tuesday, February 6, 2024 at 1:45:35 PM UTC-6 Mark Conner wrote:

> Hi,
>
> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my 
> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start 
> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a 
> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to 
> 5.0.0 and still have the same issue.  Here are the weewxd related lines 
> from startup from /var/log/syslog: 
>
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing 
>> weewxd version 5.0.0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python 
>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform 
>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale: 
>> 'en_US'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration 
>> file: /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading 
>> station type Vantage (weewx.drivers.vantage)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import 
>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13] 
>> Permission denied: '/dev/ttyAMA0' (> 'serial.serialutil.SerialException'>)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File 
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322, 
>> in open
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | 
>> os.O_NONBLOCK)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   During handling of the above exception, another exception occurred:
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.console = loader_function(config_dict, self)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   return VantageService(engine, config_dict)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in 
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>>   self.port.openPort()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine: 
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
>> openPort
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITIC

Re: [weewx-user] Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Tom Keffer]

I’m typing this on a phone, so my directions are necessarily incomplete,
but this is probably caused by the user weewx not having the necessary
permissions. Try following the instructions at this link:

http://www.weewx.com/docs/5.0/upgrade/#weewx-runs-as-the-weewx-user


-tk


On Tue, Feb 6, 2024 at 11:45 AM Mark Conner  wrote:

> Hi,
>
> I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my
> Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
> weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
> MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
> 5.0.0 and still have the same issue.  Here are the weewxd related lines
> from startup from /var/log/syslog:
>
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing
>> weewxd version 5.0.0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line:
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python
>> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
>> /usr/bin/python3
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
>> Linux-6.1.21-v7+-armv7l-with-glibc2.31
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale:
>> 'en_US'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path:
>> /usr/share/weewx/weewxd.py
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration
>> file: /etc/weewx/weewx.conf
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module:
>> /etc/weewx/bin/user
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading
>> station type Vantage (weewx.drivers.vantage)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import
>> of driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13]
>> Permission denied: '/dev/ttyAMA0' (> 'serial.serialutil.SerialException'>)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File
>> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
>> in open
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
>> os.O_NONBLOCK)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> 
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   During handling of the above exception, another exception occurred:
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> 
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Traceback (most recent call last):
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.console = loader_function(config_dict, self)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   return VantageService(engine, config_dict)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in
>> __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.port.openPort()
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in
>> openPort
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.serial_port = serial.Serial(self.port, self.baudrate,
>> timeout=self.timeout)
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>> File "/usr/local/lib/python3.9/dist-packages/serial/serialutil.py",
>> line 244, in __init__
>> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>>   self.open()
>> Feb  6 13:29:00 raspberrypi110 weewxd[28

[weewx-user] Permissions issue for /dev/ttyAMA0 after upgrade attempt from 5.0 to 5.0.1

[Mark Conner]

Hi,

I recently tried to upgrade my weewx installation from 5.0 to 5.0.1 on my
Raspberry Pi 2 using 'sudo apt-get' and afterwards I was unable to start
weewxd.  I am reading from a Davis Vantage Pro2 with a serial logger via a
MeteoPi interface.  Thinking it was an upgrade problem, I downgraded to
5.0.0 and still have the same issue.  Here are the weewxd related lines
from startup from /var/log/syslog:

Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Initializing
> weewxd version 5.0.0
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Command line:
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Using Python
> 3.9.2 (default, Mar 12 2021, 04:06:34) #012[GCC 10.2.1 20210110]
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Located at
> /usr/bin/python3
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Platform
> Linux-6.1.21-v7+-armv7l-with-glibc2.31
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Locale: 'en_US'
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Entry path:
> /usr/share/weewx/weewxd.py
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: WEEWX_ROOT: /
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Configuration
> file: /etc/weewx/weewx.conf
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: User module:
> /etc/weewx/bin/user
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO __main__: Debug: 0
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: INFO weewx.engine: Loading
> station type Vantage (weewx.drivers.vantage)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: ERROR weewx.engine: Import of
> driver failed: [Errno 13] could not open port /dev/ttyAMA0: [Errno 13]
> Permission denied: '/dev/ttyAMA0' ( 'serial.serialutil.SerialException'>)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   Traceback (most recent call last):
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File
> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 322,
> in open
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY |
> os.O_NONBLOCK)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   PermissionError: [Errno 13] Permission denied: '/dev/ttyAMA0'
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> 
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   During handling of the above exception, another exception occurred:
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> 
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   Traceback (most recent call last):
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   self.console = loader_function(config_dict, self)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 32, in loader
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   return VantageService(engine, config_dict)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 2046, in
> __init__
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   Vantage.__init__(self, **config_dict[DRIVER_NAME])
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 536, in
> __init__
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   self.port.openPort()
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in
> openPort
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   self.serial_port = serial.Serial(self.port, self.baudrate,
> timeout=self.timeout)
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File "/usr/local/lib/python3.9/dist-packages/serial/serialutil.py",
> line 244, in __init__
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   self.open()
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
> File
> "/usr/local/lib/python3.9/dist-packages/serial/serialposix.py", line 325,
> in open
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   raise SerialException(msg.errno, "could not open port {}:
> {}".format(self._port, msg))
> Feb  6 13:29:00 raspberrypi110 weewxd[2836]: CRITICAL weewx.engine:
>   serial.serialutil.SerialException: [Errno 13] co

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Mks Mk]

Pierre-Yves
we used these commands
sudo apt remove weewx
then
sudo apt install weewx=4.10.2-1

On Tuesday, February 6, 2024 at 10:13:38 PM UTC+3 Pierre-Yves wrote:

> @ Mks Mk,
> Which command did you use to perform the downgrade from v5to v4.10.2 ?
> I tried "sudo apt install weewx=4.10.2" and "sudo apt install weewx 
> 4.10.2" but none of these work...
>
> Thanks, Pierre-Yves
>
> Le mardi 6 février 2024 à 19:44:41 UTC+1, Mks Mk a écrit :
>
>> we just tried the upgrade again to weewx  v5.0.1 (sudo apt update) and 
>> it worked this time.
>> (we have not done any changes to the system after the downgrade to 
>> v4.10.2) 
>>
>> On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:
>>
>>> @ Matthew, thanks. I need now to "digest" all this information, it's a 
>>> bit high level for me ;-)
>>>
>>> @ Stefanos, thanks too, I tested my USB SDR key and obtain the same 
>>> result as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor 
>>> Corp. RTL2838 DVB-T"
>>>
>>> Pierre-Yves
>>> Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :
>>>
 i forgot to write in my last message  that when you finished you must 
 restart udev or restart the device you using( p.c , rpi ,... etc)

 On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:

> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>
> It seems to be a problem of rules change. In fact, I first upgraded 
> from 4.10.2 to 5.0.0 and weewx worked perfectly. 
>
>
> weewx was running as root:root. weewx 5.0.0 did not modify any 
> permissions when it upgraded from 4.10.2.
>  
>
> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>
>
> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>  
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I 
> installed rtl-sdr following your Git (
> https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
> that doesn't solve the problem.
>
>
> is there a udev rules file for sdr?  (it is a separate step when you 
> build rtl-sdr from source)
> if there is a udev rules file for sdr, how are the permissions set?
> did the usermod for weewx succeed?
> is weewx in the plugdev group?  (grep weewx /etc/group)
> did you restart weewxd after putting weewx into the plugdev group?
>  
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
>
> packages install to /usr/lib/udev/rules.d
>
> system administrators (or end-users acting as system administrators) 
> put things in /etc/udev/rules.d
>
> that way you can override whatever a package installs, and your 
> changes will not be overwritten by the package when you upgrade/update.
>  
>


-- 
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/4280ab96-dbe3-4acc-b201-ebe8977e5f17n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Mks Mk]

Pierre-Yves,
we used these commands
Pierre-Yves
sudo apt remove weewx
then
sudo apt install weewx=4.10.2-1

On Tuesday, February 6, 2024 at 10:13:38 PM UTC+3 Pierre-Yves wrote:

> @ Mks Mk,
> Which command did you use to perform the downgrade from v5to v4.10.2 ?
> I tried "sudo apt install weewx=4.10.2" and "sudo apt install weewx 
> 4.10.2" but none of these work...
>
> Thanks, Pierre-Yves
>
> Le mardi 6 février 2024 à 19:44:41 UTC+1, Mks Mk a écrit :
>
>> we just tried the upgrade again to weewx  v5.0.1 (sudo apt update) and 
>> it worked this time.
>> (we have not done any changes to the system after the downgrade to 
>> v4.10.2) 
>>
>> On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:
>>
>>> @ Matthew, thanks. I need now to "digest" all this information, it's a 
>>> bit high level for me ;-)
>>>
>>> @ Stefanos, thanks too, I tested my USB SDR key and obtain the same 
>>> result as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor 
>>> Corp. RTL2838 DVB-T"
>>>
>>> Pierre-Yves
>>> Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :
>>>
 i forgot to write in my last message  that when you finished you must 
 restart udev or restart the device you using( p.c , rpi ,... etc)

 On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:

> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>
> It seems to be a problem of rules change. In fact, I first upgraded 
> from 4.10.2 to 5.0.0 and weewx worked perfectly. 
>
>
> weewx was running as root:root. weewx 5.0.0 did not modify any 
> permissions when it upgraded from 4.10.2.
>  
>
> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>
>
> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>  
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I 
> installed rtl-sdr following your Git (
> https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
> that doesn't solve the problem.
>
>
> is there a udev rules file for sdr?  (it is a separate step when you 
> build rtl-sdr from source)
> if there is a udev rules file for sdr, how are the permissions set?
> did the usermod for weewx succeed?
> is weewx in the plugdev group?  (grep weewx /etc/group)
> did you restart weewxd after putting weewx into the plugdev group?
>  
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
>
> packages install to /usr/lib/udev/rules.d
>
> system administrators (or end-users acting as system administrators) 
> put things in /etc/udev/rules.d
>
> that way you can override whatever a package installs, and your 
> changes will not be overwritten by the package when you upgrade/update.
>  
>


-- 
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/094e0aff-74e7-4d3c-814a-4aa2197acd60n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Philip Wolff]

Thanks for that tip - it got me off the ground. All is now well except that 
/var/www/html/weewx hasn't been updated since just before I did the upgrade 
to 5.0.1. Anyone else seeing this?

On Tuesday, February 6, 2024 at 8:09:36 AM UTC-8 Tom Hogland wrote:

> In case anyone else runs into this - my Ubuntu server/Davis VP2 and serial 
> datalogger had ownership set to root:dialout, so I had to add the weewx 
> user to the dialout group for things to work. 
>
> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>
>> when you install rtl-sdr, it typically, but not always, installs udev 
>> rules for *many* sdr devices.  the udev rules that it installs make it 
>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>> device.  (this is true when you install rtl-sdr from source - if you 
>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>> this configuration please let us know)
>>
>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>> what the udev rules might be
>>
>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>> non-root user (for pip installs).  so udev rules are required.
>>
>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>> (it would continue to run as root - we changed in 5.0.1 because overall 
>> security and best practice)
>>
>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>> since the user 'weewx' is not in the plugdev group.  you can either added 
>> the user weewx to the plugdev group, or modify the udev rules to use 
>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>
>> sudo usermod -aG plugdev weewx
>>
>> for a pip install, be sure that the user running weewx is in the 
>> 'plugdev' group.
>>
>> restart of the weewxd daemon is almost certainly required so that the 
>> daemon process has the right group.  reboot is not necessary.
>>
>> 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/e2f0fc25-2eb2-4af1-853e-160b0121493en%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Mks Mk,
Which command did you use to perform the downgrade from v5to v4.10.2 ?
I tried "sudo apt install weewx=4.10.2" and "sudo apt install weewx 4.10.2" 
but none of these work...

Thanks, Pierre-Yves

Le mardi 6 février 2024 à 19:44:41 UTC+1, Mks Mk a écrit :

> we just tried the upgrade again to weewx  v5.0.1 (sudo apt update) and it 
> worked this time.
> (we have not done any changes to the system after the downgrade to 
> v4.10.2) 
>
> On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:
>
>> @ Matthew, thanks. I need now to "digest" all this information, it's a 
>> bit high level for me ;-)
>>
>> @ Stefanos, thanks too, I tested my USB SDR key and obtain the same 
>> result as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor 
>> Corp. RTL2838 DVB-T"
>>
>> Pierre-Yves
>> Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :
>>
>>> i forgot to write in my last message  that when you finished you must 
>>> restart udev or restart the device you using( p.c , rpi ,... etc)
>>>
>>> On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
>>>
 On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:

 It seems to be a problem of rules change. In fact, I first upgraded 
 from 4.10.2 to 5.0.0 and weewx worked perfectly. 


 weewx was running as root:root. weewx 5.0.0 did not modify any 
 permissions when it upgraded from 4.10.2.
  

 Then I went from 5.0.0 to 5.0.1 an weewx failed to start.


 weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
 permissions to weewx:weewx permissions, and runs the daemon as weewx.
  

 For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
 rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).

 I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
 that doesn't solve the problem.


 is there a udev rules file for sdr?  (it is a separate step when you 
 build rtl-sdr from source)
 if there is a udev rules file for sdr, how are the permissions set?
 did the usermod for weewx succeed?
 is weewx in the plugdev group?  (grep weewx /etc/group)
 did you restart weewxd after putting weewx into the plugdev group?
  

 Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
 /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
 thread that it should be in /usr/lib/udev/rules.d... What about ?


 packages install to /usr/lib/udev/rules.d

 system administrators (or end-users acting as system administrators) 
 put things in /etc/udev/rules.d

 that way you can override whatever a package installs, and your changes 
 will not be overwritten by the package when you upgrade/update.
  

>>>

-- 
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/9fad728e-e665-4db7-a99b-8b3c129ea164n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Mks Mk]

we just tried the upgrade again to weewx  v5.0.1 (sudo apt update) and it 
worked this time.
(we have not done any changes to the system after the downgrade to v4.10.2) 

On Tuesday, February 6, 2024 at 8:32:36 PM UTC+3 Pierre-Yves wrote:

> @ Matthew, thanks. I need now to "digest" all this information, it's a bit 
> high level for me ;-)
>
> @ Stefanos, thanks too, I tested my USB SDR key and obtain the same result 
> as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. 
> RTL2838 DVB-T"
>
> Pierre-Yves
> Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :
>
>> i forgot to write in my last message  that when you finished you must 
>> restart udev or restart the device you using( p.c , rpi ,... etc)
>>
>> On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
>>
>>> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>>>
>>> It seems to be a problem of rules change. In fact, I first upgraded from 
>>> 4.10.2 to 5.0.0 and weewx worked perfectly. 
>>>
>>>
>>> weewx was running as root:root. weewx 5.0.0 did not modify any 
>>> permissions when it upgraded from 4.10.2.
>>>  
>>>
>>> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>>>
>>>
>>> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
>>> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>>>  
>>>
>>> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
>>> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>>>
>>> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
>>> that doesn't solve the problem.
>>>
>>>
>>> is there a udev rules file for sdr?  (it is a separate step when you 
>>> build rtl-sdr from source)
>>> if there is a udev rules file for sdr, how are the permissions set?
>>> did the usermod for weewx succeed?
>>> is weewx in the plugdev group?  (grep weewx /etc/group)
>>> did you restart weewxd after putting weewx into the plugdev group?
>>>  
>>>
>>> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
>>> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
>>> thread that it should be in /usr/lib/udev/rules.d... What about ?
>>>
>>>
>>> packages install to /usr/lib/udev/rules.d
>>>
>>> system administrators (or end-users acting as system administrators) put 
>>> things in /etc/udev/rules.d
>>>
>>> that way you can override whatever a package installs, and your changes 
>>> will not be overwritten by the package when you upgrade/update.
>>>  
>>>
>>

-- 
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/eccc3ce1-dcb3-4835-977d-82c2b9683c07n%40googlegroups.com.

[weewx-user] V5.0.1 and rsyslog

[Tom Hogland]

Odd change - I converted my v4 weewx-multi setup to the new v5 weewx@ 
service, and all is well, except logging. I have rsyslog set up to put my 
weewx-vp2 and weewx-tempest output into individual logs, using the .conf 
provided. Both services have --log-label specified and 'ps -ax' output 
shows them as '--log-label weewxd-vp2' and'--log-label weewxd-tempest'. The 
logs, however, are showing up as "weewxd-vp2.log" and "weewxd.py.log".  The 
actual log messages are the same - the VP2 messages are from weewxd-vp2 and 
the weewx-tempest messages are from weewxd.py. 

I looked through the rsyslog and weewx docs but can't find anything that 
sheds any light on it. Has anyone seen this behavior? This is an Ubuntu 
server, installed and upgraded via apt. Both instances start from the same 
weewx@.service file, and I can't find anything related to logging in either 
.conf except that log_success is false and log_failure is true.

-- 
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/9a634716-e44d-41e1-a025-bc0d74ccbe76n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Matthew, thanks. I need now to "digest" all this information, it's a bit 
high level for me ;-)

@ Stefanos, thanks too, I tested my USB SDR key and obtain the same result 
as yours : "Bus 003 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. 
RTL2838 DVB-T"

Pierre-Yves
Le mardi 6 février 2024 à 18:17:07 UTC+1, Stefanos Kalaitzis a écrit :

> i forgot to write in my last message  that when you finished you must 
> restart udev or restart the device you using( p.c , rpi ,... etc)
>
> On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:
>
>> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>>
>> It seems to be a problem of rules change. In fact, I first upgraded from 
>> 4.10.2 to 5.0.0 and weewx worked perfectly. 
>>
>>
>> weewx was running as root:root. weewx 5.0.0 did not modify any 
>> permissions when it upgraded from 4.10.2.
>>  
>>
>> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>>
>>
>> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
>> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>>  
>>
>> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
>> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>>
>> I tried the command you proposed (sudo usermod -aG plugdev weewx) but 
>> that doesn't solve the problem.
>>
>>
>> is there a udev rules file for sdr?  (it is a separate step when you 
>> build rtl-sdr from source)
>> if there is a udev rules file for sdr, how are the permissions set?
>> did the usermod for weewx succeed?
>> is weewx in the plugdev group?  (grep weewx /etc/group)
>> did you restart weewxd after putting weewx into the plugdev group?
>>  
>>
>> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
>> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
>> thread that it should be in /usr/lib/udev/rules.d... What about ?
>>
>>
>> packages install to /usr/lib/udev/rules.d
>>
>> system administrators (or end-users acting as system administrators) put 
>> things in /etc/udev/rules.d
>>
>> that way you can override whatever a package installs, and your changes 
>> will not be overwritten by the package when you upgrade/update.
>>  
>>
>

-- 
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/329d0ee7-1c59-4d7c-be42-45d5957ced69n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

i forgot to write in my last message  that when you finished you must 
restart udev or restart the device you using( p.c , rpi ,... etc)

On Tuesday, February 6, 2024 at 7:11:07 PM UTC+2 matthew wall wrote:

> On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:
>
> It seems to be a problem of rules change. In fact, I first upgraded from 
> 4.10.2 to 5.0.0 and weewx worked perfectly. 
>
>
> weewx was running as root:root. weewx 5.0.0 did not modify any permissions 
> when it upgraded from 4.10.2.
>  
>
> Then I went from 5.0.0 to 5.0.1 an weewx failed to start.
>
>
> weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
> permissions to weewx:weewx permissions, and runs the daemon as weewx.
>  
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
> doesn't solve the problem.
>
>
> is there a udev rules file for sdr?  (it is a separate step when you build 
> rtl-sdr from source)
> if there is a udev rules file for sdr, how are the permissions set?
> did the usermod for weewx succeed?
> is weewx in the plugdev group?  (grep weewx /etc/group)
> did you restart weewxd after putting weewx into the plugdev group?
>  
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
>
> packages install to /usr/lib/udev/rules.d
>
> system administrators (or end-users acting as system administrators) put 
> things in /etc/udev/rules.d
>
> that way you can override whatever a package installs, and your changes 
> will not be overwritten by the package when you upgrade/update.
>  
>

-- 
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/a48a3432-f9a6-422e-9cd2-827379e7e557n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[matthew wall]

On Tuesday, February 6, 2024 at 11:38:24 AM UTC-5 Pierre-Yves wrote:

It seems to be a problem of rules change. In fact, I first upgraded from 
4.10.2 to 5.0.0 and weewx worked perfectly. 


weewx was running as root:root. weewx 5.0.0 did not modify any permissions 
when it upgraded from 4.10.2.
 

Then I went from 5.0.0 to 5.0.1 an weewx failed to start.


weewx was running as weewx:weewx.  weewx 5.0.1 converts from root:root 
permissions to weewx:weewx permissions, and runs the daemon as weewx.
 

For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).

I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
doesn't solve the problem.


is there a udev rules file for sdr?  (it is a separate step when you build 
rtl-sdr from source)
if there is a udev rules file for sdr, how are the permissions set?
did the usermod for weewx succeed?
is weewx in the plugdev group?  (grep weewx /etc/group)
did you restart weewxd after putting weewx into the plugdev group?
 

Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
/etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
thread that it should be in /usr/lib/udev/rules.d... What about ?


packages install to /usr/lib/udev/rules.d

system administrators (or end-users acting as system administrators) put 
things in /etc/udev/rules.d

that way you can override whatever a package installs, and your changes 
will not be overwritten by the package when you upgrade/update.
 

-- 
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/bc624a71-320b-46e5-9b28-c3a813f5b447n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

I use a nooelec rtl-sdr.  On a fresh install  of bookworm 64bit in a 
Raspberry pi 4 and weewx v5  i solved the error like this:
i run  *lsusb*
and i saw a line similar to this 
 Bus 001 Device 008: ID 0bda:2838 Realtek Semiconductor Corp.

**  "0bda" is the vendor id and "2838" is the product id (maybe yours are 
different)**

then i made a new file as root in  /etc/udev/rules.d/rtl-sdr.rules
next i modifyed this: *sudo nano  /etc/udev/rules.d/rtl-sdr.rules*
and i added this line :
 SUBSYSTEM=="usb", ATTRS{idVendor}=="0bda", ATTRS{idProduct}=="2838", 
GROUP="adm", MODE="0666", SYMLINK+="rtl_sdr"  

hope this will help you 

On Tuesday, February 6, 2024 at 6:38:24 PM UTC+2 Pierre-Yves wrote:

> @ Matthew,
>
> Thanks a lot for the feedback.
>
> It seems to be a problem of rules change. In fact, I first upgraded from 
> 4.10.2 to 5.0.0 and weewx worked perfectly. Then I went from 5.0.0 to 5.0.1 
> an weewx failed to start.
>
> For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
> rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).
>
> I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
> doesn't solve the problem.
>
> Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
> /etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
> thread that it should be in /usr/lib/udev/rules.d... What about ?
>
> Pierre-Yves
>
>
>
> Le mardi 6 février 2024 à 17:09:36 UTC+1, Tom Hogland a écrit :
>
>> In case anyone else runs into this - my Ubuntu server/Davis VP2 and 
>> serial datalogger had ownership set to root:dialout, so I had to add the 
>> weewx user to the dialout group for things to work. 
>>
>> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>>
>>> when you install rtl-sdr, it typically, but not always, installs udev 
>>> rules for *many* sdr devices.  the udev rules that it installs make it 
>>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>>> device.  (this is true when you install rtl-sdr from source - if you 
>>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>>> this configuration please let us know)
>>>
>>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>>> what the udev rules might be
>>>
>>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>>> non-root user (for pip installs).  so udev rules are required.
>>>
>>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>>> (it would continue to run as root - we changed in 5.0.1 because overall 
>>> security and best practice)
>>>
>>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>>> since the user 'weewx' is not in the plugdev group.  you can either added 
>>> the user weewx to the plugdev group, or modify the udev rules to use 
>>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>>
>>> sudo usermod -aG plugdev weewx
>>>
>>> for a pip install, be sure that the user running weewx is in the 
>>> 'plugdev' group.
>>>
>>> restart of the weewxd daemon is almost certainly required so that the 
>>> daemon process has the right group.  reboot is not necessary.
>>>
>>> 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/b009ccff-87bc-4c60-b003-23389a098724n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

@ Matthew,

Thanks a lot for the feedback.

It seems to be a problem of rules change. In fact, I first upgraded from 
4.10.2 to 5.0.0 and weewx worked perfectly. Then I went from 5.0.0 to 5.0.1 
an weewx failed to start.

For Weewx,, I did a deb/rpm install and, as far I remember, I installed 
rtl-sdr following your Git (https://github.com/matthewwall/weewx-sdr).

I tried the command you proposed (sudo usermod -aG plugdev weewx) but that 
doesn't solve the problem.

Regarding the rtl-sdr rules, I have a doubt. I installed the file in 
/etc/weewx/udev/rules.d. Maybe it is a wrong place... I read in another 
thread that it should be in /usr/lib/udev/rules.d... What about ?

Pierre-Yves



Le mardi 6 février 2024 à 17:09:36 UTC+1, Tom Hogland a écrit :

> In case anyone else runs into this - my Ubuntu server/Davis VP2 and serial 
> datalogger had ownership set to root:dialout, so I had to add the weewx 
> user to the dialout group for things to work. 
>
> On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:
>
>> when you install rtl-sdr, it typically, but not always, installs udev 
>> rules for *many* sdr devices.  the udev rules that it installs make it 
>> possible for anyone in the 'plugdev' group to read/write to the sdr 
>> device.  (this is true when you install rtl-sdr from source - if you 
>> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
>> this configuration please let us know)
>>
>> weewx v4 runs as root:root, so it has access to the sdr device no matter 
>> what the udev rules might be
>>
>> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
>> non-root user (for pip installs).  so udev rules are required.
>>
>> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
>> (it would continue to run as root - we changed in 5.0.1 because overall 
>> security and best practice)
>>
>> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
>> since the user 'weewx' is not in the plugdev group.  you can either added 
>> the user weewx to the plugdev group, or modify the udev rules to use 
>> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>>
>> sudo usermod -aG plugdev weewx
>>
>> for a pip install, be sure that the user running weewx is in the 
>> 'plugdev' group.
>>
>> restart of the weewxd daemon is almost certainly required so that the 
>> daemon process has the right group.  reboot is not necessary.
>>
>> 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/851d8cfc-0ce2-4758-b160-22a983dbd897n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Tom Hogland]

In case anyone else runs into this - my Ubuntu server/Davis VP2 and serial 
datalogger had ownership set to root:dialout, so I had to add the weewx 
user to the dialout group for things to work. 

On Tuesday, February 6, 2024 at 6:23:15 AM UTC-9 matthew wall wrote:

> when you install rtl-sdr, it typically, but not always, installs udev 
> rules for *many* sdr devices.  the udev rules that it installs make it 
> possible for anyone in the 'plugdev' group to read/write to the sdr 
> device.  (this is true when you install rtl-sdr from source - if you 
> install rtl-sdr from a deb/rpm package, it might be different - anyone with 
> this configuration please let us know)
>
> weewx v4 runs as root:root, so it has access to the sdr device no matter 
> what the udev rules might be
>
> weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
> non-root user (for pip installs).  so udev rules are required.
>
> btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
> (it would continue to run as root - we changed in 5.0.1 because overall 
> security and best practice)
>
> the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
> since the user 'weewx' is not in the plugdev group.  you can either added 
> the user weewx to the plugdev group, or modify the udev rules to use 
> 'weewx' instead of 'plugdev' as the group.  this is how to do the former:
>
> sudo usermod -aG plugdev weewx
>
> for a pip install, be sure that the user running weewx is in the 'plugdev' 
> group.
>
> restart of the weewxd daemon is almost certainly required so that the 
> daemon process has the right group.  reboot is not necessary.
>
> 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/92fc5b8c-08e3-490c-94fa-73ae14e7661an%40googlegroups.com.

Re: [weewx-user] Another Davis Vantage unable to start concern

[matthew wall]

as i understand it, the "systemd way" is one of these two:

1) override.  to change behavior of a systemd unit that was installed by a 
deb/rpm package, use the ".d" pattern.

in this case, create the overrides directory:
sudo mkdir /etc/systemd/system/weewx.service.d

then put this into the file 
/etc/systemd/system/weewx.service.d/waitfornetwork.conf
[Unit]
Wants=network-online.target
After=network-online.target

2) modify. to change the beavior of a systemd unit that was installed by 
the user/sysadmin, modify the systemd unit in /etc/systemd/system

in this case, add two lines to the [Unit] section of 
/etc/systemd/system/weewx.service

Wants=network-online.target
After=network-online.target

the other pattern is to use environment variables, but (a) systemd 
explicitly discourages doing that the standard way by using /etc/default 
(any linux) or /etc/sysconfig (redhat-specific), and (b) the weewx devs 
prefer to have everything in a single conf file since environment variables 
can be difficult to diagnose/support.

i have not done extensive testing with either (1) or (2) above, so 
apologies for providing examples without solid testing.  but there are just 
too many systemd variations out there.  maybe when systemd has gotten past 
its toddler years...

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/0edd7cdb-5247-45a1-89d6-2e8086cf4f44n%40googlegroups.com.

[weewx-user] Re: Klimalogg driver fails after update to weewx 5.0.0.1

[matthew wall]

On Tuesday, February 6, 2024 at 4:02:18 AM UTC-5 michael.k...@gmx.at wrote:

So this is a package install? Did you do try restating already? A friend 
had the same error with a package install update 5.0.0 =>  5.0.1 on 
Raspberry Pi OS, but with the ws23xx driver. He restarted the OS, then it 
worked. Maybe restarting udev or another daemon is sufficient also, I don't 
know.


reboot is not necessary.  however, it might be the easiest thing to do.  on 
most recent operating systems, the udev rules will take effect 
immediately.  if they do not, then unplug-then-replug the device will make 
them take effect, even on older operating systems.  the other part is 
ensuring that the owner of the daemon user is in the right group.  
restarting the daemon process is sufficient to make that happen.

this should explain the ws23xx case, since the udev rule for that device is 
included in a weewx install.

in the case of klimalogg, the udev rule is also included with weewx, even 
though the kl.py driver is not.

if you install weewx using deb/rpm, it should just work.  check the udev 
file at /usr/lib/udev/rules.d/60-weewx.rules.

if you install weewx using pip, then you must install the udev rules that 
came with weewx (the setup-daemon.sh script will do this for you).  check 
for the udev rules at /etc/udev/rules.d/60-weewx.rules

NB: klimalogg uses the same usb transceiver used by the lacrosse ws28xx 
stations.  that transceiver uses product/vendor identifiers of /.  
those identifiers are the equivalent of using 'example.com' - ok for 
testing, but not what you should ship in your product.  but they did.

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/16eadc62-cf94-4171-81ed-dc4225a8db1an%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[matthew wall]

when you install rtl-sdr, it typically, but not always, installs udev rules 
for *many* sdr devices.  the udev rules that it installs make it possible 
for anyone in the 'plugdev' group to read/write to the sdr device.  (this 
is true when you install rtl-sdr from source - if you install rtl-sdr from 
a deb/rpm package, it might be different - anyone with this configuration 
please let us know)

weewx v4 runs as root:root, so it has access to the sdr device no matter 
what the udev rules might be

weewx v5 runs as weewx:weewx (for a deb/rpm install) or as a regular 
non-root user (for pip installs).  so udev rules are required.

btw, weewx 5.0.1 *always* converts to weewx:weewx, whereas 5.0.0 did not 
(it would continue to run as root - we changed in 5.0.1 because overall 
security and best practice)

the udev rules installed by rtl-sdr will not help for a deb/rpm install, 
since the user 'weewx' is not in the plugdev group.  you can either added 
the user weewx to the plugdev group, or modify the udev rules to use 
'weewx' instead of 'plugdev' as the group.  this is how to do the former:

sudo usermod -aG plugdev weewx

for a pip install, be sure that the user running weewx is in the 'plugdev' 
group.

restart of the weewxd daemon is almost certainly required so that the 
daemon process has the right group.  reboot is not necessary.

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/26551b2f-d7d8-4b25-b09b-8ecff2d47afan%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Pierre-Yves]

Hello all,

I just upgraded from 4.10 .2 to 5.0.1 and I seem to experiment a similar 
behavior. I run weewx on a RPi4.

As Tom explained above, I put rtl-sdr.rules in udev directory and restarted 
but no change
 
I tried to downgrade using "sudo apt install weewx=4.10.2" but that doesn't 
work :

:~ $ sudo apt install weewx=4.10.2
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances   
Lecture des informations d'état... Fait
E: La version « 4.10.2 » de « weewx » n'a pu être trouvée ??

Now I am stuck

Below the log when weewx 5.0.1 is started.

Any idea ?

Thanks, Pierre-Yves


Le mardi 6 février 2024 à 14:35:19 UTC+1, Tom Keffer a écrit :

> If you look in your log, you'll see that the rtl_433 process failed to run 
> because of permissions problems. The log also suggests fixing the problem 
> by installing the udev rules file "rtl-sir:rules". You can find this rules 
> file in the rtl-sdr repository: 
> https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules
>
> V4.10 ran as user "root". Fresh V5 installs run as user "weewx", which may 
> not have the permissions necessary to access your device. The rules file 
> gives it these permissions.
>
> Alternatively, you could change your install to run under "root".
>
> On Tue, Feb 6, 2024 at 1:29 AM Mks Mk  wrote:
>
>> The system was running weewx v5.0.0 with no issue then we did the upgrade 
>> to v5.0.1 (sudo apt update) and weewx failed to run.
>> we downgraded weewx to v5.0.0 but it did not work this time, so we went 
>> back to v4.10.2 and it run just fine.
>> did the upgrade again and got the same error.so we are back to v4.10.2
>> we tested the sdr hardware using rtl_433 and it is working fine.
>> we are not sure of what to do next!
>>
>> log:
>> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
>> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
>> 'weewx.sdb'
>> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
>> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
>> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
>> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
>> master at 202402051043 inputs file rtl_tcp RTL-SDR
>> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
>> warnings, and errors in the console.
>> weewxd[2386]: ERROR user.sdr: usb_open error -3
>> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
>> installing the udev rules file rtl-sdr.rules
>> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
>> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k 
>> -R 40
>> weewxd[2386]: Exception in thread stdout-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: Exception in thread stderr-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: INFO user.sdr: shutdown complete
>> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
>> not running
>> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
>> retrying...
>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/2fe00d3b-9f50-4bae-90c4-98c9f57298f6n%40googlegroups.com.


upgrade 4-10-2 to 5-0-1-log
Description: Binary data

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Tom Keffer]

If you look in your log, you'll see that the rtl_433 process failed to run
because of permissions problems. The log also suggests fixing the problem
by installing the udev rules file "rtl-sir:rules". You can find this rules
file in the rtl-sdr repository:
https://raw.githubusercontent.com/osmocom/rtl-sdr/master/rtl-sdr.rules

V4.10 ran as user "root". Fresh V5 installs run as user "weewx", which may
not have the permissions necessary to access your device. The rules file
gives it these permissions.

Alternatively, you could change your install to run under "root".

On Tue, Feb 6, 2024 at 1:29 AM Mks Mk  wrote:

> The system was running weewx v5.0.0 with no issue then we did the upgrade
> to v5.0.1 (sudo apt update) and weewx failed to run.
> we downgraded weewx to v5.0.0 but it did not work this time, so we went
> back to v4.10.2 and it run just fine.
> did the upgrade again and got the same error.so we are back to v4.10.2
> we tested the sdr hardware using rtl_433 and it is working fine.
> we are not sure of what to do next!
>
> log:
> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database
> 'weewx.sdb'
> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch
> master at 202402051043 inputs file rtl_tcp RTL-SDR
> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages,
> warnings, and errors in the console.
> weewxd[2386]: ERROR user.sdr: usb_open error -3
> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by
> installing the udev rules file rtl-sdr.rules
> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k
> -R 40
> weewxd[2386]: Exception in thread stdout-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: Exception in thread stderr-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: INFO user.sdr: shutdown complete
> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is
> not running
> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then
> retrying...
>
> --
> 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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/CAPq0zEDiCDBds_YEHWc_HvxOB%2B4C1mnke3XG41mzt%3DKqwX2sqg%40mail.gmail.com.

Re: [weewx-user] Which driver should i target for my custom weather station?

[p q]

Yeah. I'm assuming you will be running Weewx on some computer other than
the ESP and have a network connection between the ESP and the computer. I
would use MQTT to publish the sensor data to a MQTT broker running
somewhere on your network, likely Mosquitto running on the same machine as
Weewx. Weewx would subscribe to the sensor data and go from there. I am not
up on the Weewx MQTT driver, but I would look into using it. I personally
use the Accurite driver as my original system is an Accurite. Over time as
I've added new sensors or replaced crummy ones, I've started to use MQTT as
my preferred method of sending data from microcontrollers to Weewx
with various hacks on the Accurite driver.

On Tue, Feb 6, 2024 at 2:51 AM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> A few thoughts:
>
> Building the "station" on a ESP8266 doesn't sound like you are planning to
> get too far with your project. Compared to it's successor, it is very
> limited and has some really weird flaws.
> Why would you connect the station with a serial interface, when it has
> WIFI on board?
> p q's MQTT suggestion is a not a bad one. Let your station emit every
> single sensor reading as a MQTT message, and let weewx receive it with MQTT
> Subscribe 
> Either MQTT Subscribe as a service, augmenting any off-the-shelf station
> supported by weewx with your sensors data, or use it as a driver.
> Encapsulating sensor data in JSON for the MQTT payload is commonly done and
> supported by MQTT Subscribe.
> Pavocracy schrieb am Dienstag, 6. Februar 2024 um 11:07:05 UTC+1:
>
>> I'm not sure if im misunderstanding what you are saying, or if i am not
>> doing a good job at explaining my question, but even if i choose mqtt as my
>> location to push the data, the data still needs to be in some specific
>> format for weewx to understand it no?
>>
>> So on the esp8266, that has a bunch of sensors attached to it, in my
>> embedded code i need to collect the data point for the sensor, and then put
>> it in some specific format to send along somewhere that weewx will read.
>> Reading through the source code it looked like the drivers are where these
>> message formats are interrupted, but i could be wrong?
>>
>> On Monday 5 February 2024 at 23:45:25 UTC+10 p q wrote:
>>
>>> If I was going to do this, I would look into mqtt options.
>>>
>>> On Sun, Feb 4, 2024, 11:03 PM 'Pavocracy' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
 Hello all,

 I am working on a hobby project where i am trying to build my own
 "weather station" from an esp8266 and a bunch of sensors. I am very keen on
 using weewx to display the post the data, and so i am looking at the
 supported drivers and wondering if there is an obvious answer to which
 driver i should be targeting for my weather station output.

 Is there an obvious choice for which driver supports the most data, or
 perhaps is the easiest data to read or is there a driver that is the most
 robust? (particularly for serial connections)

 any thoughts or experience on the matter would be greatly appreciated
 :)

 --
 You received this message because you are subscribed to the Google
 Groups "weewx-user" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit
 https://groups.google.com/d/msgid/weewx-user/831bd64d-0271-459c-9b52-929817b02319n%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/f0733294-4828-4b22-941a-33de46a803fbn%40googlegroups.com
> 
> .
>


-- 
Peter Quinn
(415)794-2264

-- 
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/CAA1SM23NQaW5yUAc9Ma%2B7yRwcpqucZ%2BxS6LCT-VGhWC4o_H6fw%40mail.gmail.com.

Re: [weewx-user] Re: New User: First Problem

[Tom Keffer]

Good suggestions from Michael. All I can add is to be sure and read the
wiki article *Barometer, pressure, altimeter
* on
the differences between the three.

On Tue, Feb 6, 2024 at 4:06 AM 'michael.k...@gmx.at' via weewx-user <
weewx-user@googlegroups.com> wrote:

> The warning tells you: WeeWX is receiving 0.0 for "pressure". You say,
> "The hardware console is operating correctly as expected", so the problem
> is somewhere in between the hardware and the LOOP. It may be, that your
> hardware/driver combination doesn't supply a valid value for "pressure" (it
> should return "None" instead of "0.0" in this case), did you try
> "barometer" or "altimeter" instead? You can also check in your database, if
> there are values for these types. If so, take a look into this article
> ,
> to make sure, you really use the correct type for your needs. Having only
> one out of the three "pressure", "altimeter" and "barometer", it should be
> possible to calculate the others, when you have the altitude, the
> temperature and humidity (or even something in addition to that).
>
> Alan Salmon schrieb am Dienstag, 6. Februar 2024 um 12:48:48 UTC+1:
>
>> Hello everyone.
>>
>> I installed weewx for the first time today on a Raspberry Pi Zero 2W,
>> using a Fine Offset 3081 station that I used for about 10 years until the
>> local cockatoos decided it would be fun to dismantle it!
>>
>> It came up on the second attempt after a few minor adjustments to the
>> config file, paths, etc. (I used the pip install method on Debian 11).
>>
>> The hardware console is operating correctly as expected, but weewx is
>> giving me the following error:
>>
>> Feb  6 22:26:01 bigfish-08 weewxd[1909]: WARNING weewx.qc: 2024-02-06
>> 22:26:02 AEDT (1707218762) LOOP value 'pressure' 0.0 outside limits (24.0,
>> 34.5)
>>
>> As the value displayed on the console (roughly) agrees with a BME680 I
>> have running, can anyone suggest where I should start trying to solve this?
>>
>> Note that I am configured for metric with barometric pressure in
>> hectopascals (hPa) which is currently just over 1010hPa, so I am at a bit
>> of a loss as to why it is showing '0.0' and where the range "24.0 to 34.5'
>> comes from.
>>
>> The error has been consistent for the 9 hours it has been running.
>>
>> Thanks for any advice you can offer.
>>
>>
>> --
> 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/31ad1404-a6ee-4245-868b-15f75bd7e73bn%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/CAPq0zEB-Msjez%3DjV%2By7BxxVMymH_XJz%2Bar2cJ%3Db%2BgTtGE%2B_hcA%40mail.gmail.com.

Re: [weewx-user] Re: Klimalogg driver fails after update to weewx 5.0.0.1

[Tom Keffer]

With new Version 5 installs, the user owning the daemon has changed. That
sometimes requires logging out, then logging back in. A reboot should not
be necessary.

On Tue, Feb 6, 2024 at 1:34 AM Marco Biner  wrote:

> Hi Michael
> thanks for your hint, after a reboot it works, I did not assume that
> debian adapts wind*ws style to do a reboot after updates.
> Regards
> Marco
>
> michael.k...@gmx.at schrieb am Dienstag, 6. Februar 2024 um 10:02:18
> UTC+1:
>
>> So this is a package install? Did you do try restating already? A friend
>> had the same error with a package install update 5.0.0 =>  5.0.1 on
>> Raspberry Pi OS, but with the ws23xx driver. He restarted the OS, then it
>> worked. Maybe restarting udev or another daemon is sufficient also, I don't
>> know.
>>
>> Marco Biner schrieb am Dienstag, 6. Februar 2024 um 09:40:51 UTC+1:
>>
>>> Hello
>>> seems that I am one of the rare users of the kl.py application from
>>> Matthew Wall.
>>> As google does not help me with a solution here my problem.
>>> After the last update of weewx to version 5.0.0.1 kl.py fails importing
>>> the driver:
>>>
>>> the log file reports:
>>>
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Initializing
>>> weewxd version 5.0.1
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Command line:
>>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Using Python
>>> 3.9.2 (default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Located at
>>> /usr/bin/python3
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Platform
>>> Linux-6.1.21-v8+-aarch64-with-glibc2.31
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Locale:
>>> 'en_US.UTF-8'
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Entry path:
>>> /usr/share/weewx/weewxd.py
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: WEEWX_ROOT:
>>> /etc/weewx
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Configuration
>>> file: /etc/weewx/weewx.conf
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: User module:
>>> /etc/weewx/bin/user
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Debug: 1
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG __main__: Initializing
>>> engine
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO weewx.engine: Loading
>>> station type KlimaLogg (user.kl)
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: driver version
>>> is 1.4.2
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: channel is 1
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: frequency is EU
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: using custom
>>> sensor map
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: sensor map is:
>>> {'temp0': 'Temp0', 'humidity0': 'Humidity0', 'heatindex0': 'heatindex0',
>>> 'dewpoint0': 'dewpoint0', 'temp1': 'Temp1', 'humidity1': 'Humidity1',
>>> 'heatindex1': 'heatindex1', 'dewpoint1': 'dewpoint1', 'temp2': 'Temp2',
>>> 'humidity2': 'Humidity2', 'heatindex2': 'heatindex2', 'dewpoint2':
>>> 'dewpoint2', 'temp3': 'Temp3', 'humidity3': 'Humidity3', 'heatindex3':
>>> 'heatindex3', 'dewpoint3': 'dewpoint3', 'temp4': 'Temp4', 'humidity4':
>>> 'Humidity4', 'heatindex4': 'heatindex4', 'dewpoint4': 'dewpoint4', 'temp5':
>>> 'Temp5', 'humidity5': 'Humidity5', 'temp6': 'Temp6', 'humidity6':
>>> 'Humidity6', 'temp7': 'Temp7', 'humidity7': 'Humidity7', 'temp8': 'Temp8',
>>> 'humidity8': 'Humidity8', 'rxCheckPercent': 'SignalQuality',
>>> 'batteryStatus0': 'BatteryStatus0', 'batteryStatus1': 'BatteryStatus1',
>>> 'batteryStatus2': 'BatteryStatus2', 'batteryStatus3': 'BatteryStatus3',
>>> 'batteryStatus4': 'BatteryStatus4', 'batteryStatus5': 'BatteryStatus5',
>>> 'batteryStatus6': 'BatteryStatus6', 'batteryStatus7': 'BatteryStatus7',
>>> 'batteryStatus8': 'BatteryStatus8', 'Sensor1': 'Kollektor warm aus',
>>> 'Sensor2': 'Kollektor kalt in', 'Sensor3': 'Speicher unten', 'Sensor4':
>>> 'Waermepumpe Ruecklauf', 'Sensor5': 'Boiler warm aus', 'Sensor6': 'Boiler
>>> kalt in', 'Sensor7': 'Speicher Mitte', 'Sensor8': 'Speicher oben',
>>> 'Sensor9': 'Speicher Brauchwasser', 'Sensor10': 'Schacht', 'Sensor11':
>>> 'Erdsonde 1', 'Sensor12': 'Erdsonde 2', 'Sensor13': 'Heizung Vorlauf',
>>> 'Sensor14': 'Temperatur 5Zi Wohnug', 'Sensor15': 'Temperatur Aussen',
>>> 'Sensor16': 'Warmwasser', 'Sensor17': 'Drehzahl Pumpe Brauchwasser'}
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: catchup limited
>>> to 51200 records
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: timing is 300 ms
>>> (0.300 s)
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl:
>>> CommunicationService.init
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: comm_interval is
>>> 8
>>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: logger_channel
>>> is 1
>>> Feb  6 08:46:44 curlevon weewxd[3865888]

Re: [weewx-user] Another Davis Vantage unable to start concern

[Tom Keffer]

One other thing to try: ask systemd to wait until the network is up before
trying to start weewxd.

Because you did a DEB install, your systemd unit file should be located in
/lib/systemd/system/weewx.service. Under the [Unit] section, add the
following two lines:




*[Unit]Wants=network-online.targetAfter=network-online.target*

-tk


On Tue, Feb 6, 2024 at 12:15 AM Neil B  wrote:

> Morning.
>
> Good suggestion on "loop on init", however I already have this setting
> enabled (and have for a long time). I believe this setting applies once the
> main loop starts, which is much later in the process.
>
> The idea of delaying the start up of WEEWX is good, and I am in favour of
> this approach. Question is (for the Linux novice) - how can you implement
> this? Any thoughts?
>
> Thanks
> Neil
>
> On Tuesday 6 February 2024 at 00:13:55 UTC Tom Keffer wrote:
>
>> All good suggestions.
>>
>> For *loop_on_init*, see this link
>> 
>> .
>>
>> On Mon, Feb 5, 2024 at 3:29 PM Graham Eddy  wrote:
>>
>>> vantage device is on LAN. wireless interface normally not ready until
>>> long after weewx tries to start, unusual (but not impossible) for ethernet
>>> interface to be so late. try the ‘loop-on-init = 1’ in weewx.conf, or
>>> insert a delay in the startup file
>>> *⊣GE⊢*
>>>
>>> On 6 Feb 2024, at 8:08 am, Neil B  wrote:
>>>
>>> Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Opened
>>> up ethernet host 192.168.1.249 on port 2. timeout=4.0,
>>> tcp_send_delay=0.5
>>>
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/F018B0FD-2319-41C3-88B1-10EC577E47FB%40geddy.au
>>> 
>>> .
>>>
>> --
> 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/b223aeb6-4150-4644-9d41-bc39bbed268en%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/CAPq0zEBYGzhzS9%3Da6jkxzQQCT2Jt5qgRzaqFjR5RGt%2B4O9_JZA%40mail.gmail.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefan Gliessmann]

Thanks a lot!
I will try this later ;)


On Tue, Feb 6, 2024 at 1:43 PM Dominic Reich  wrote:

> 'michael.k...@gmx.at' via weewx-user  wrote:
>
> >
> >sudo apt install weewx=4.10.2
>
> and to not upgrade again set it on hold:
>
> sudo apt-mark hold weewx
>
> >Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:
> >
> >I run weewx 4.10.2 on Ubuntu.
> >I did an sudo apt update, too,  and weewx 5.x got installed.
> >Since then, weewx is no longer running.
> >
> >How did you revert back to weewx 4.10.2?
> >
> >TIA,
> >Stefan
> >
> >On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis
> wrote:
> >
> >
> >I had the same error with sdr driver(weewx v5 )  running on
> debian 12 .
> >The problem solved by making udev rules ... maybe you are in the
> same
> >situation as i was.
> >
> >
> >Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk 
> έγραψε:
> >
> >The system was running weewx v5.0.0 with no issue then we did
> the
> >upgrade to v5.0.1 (sudo apt update) and weewx failed to run.
> >we downgraded weewx to v5.0.0 but it did not work this time,
> so we
> >went back to v4.10.2 and it run just fine.
> >did the upgrade again and got the same error.so we are back to
> >v4.10.2
> >we tested the sdr hardware using rtl_433 and it is working
> fine.
> >we are not sure of what to do next!
> >
> >log:
> >weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
> >weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to
> >database 'weewx.sdb'
> >weewxd[2386]: INFO weewx.manager: Starting backfill of daily
> >summaries
> >weewxd[2386]: INFO weewx.manager: Daily summaries up to date
> >weewxd[2386]: INFO weewx.engine: Starting main packet loop.
> >weewxd[2386]: ERROR user.sdr: rtl_433 version
> 23.11-41-g06b03b7a
> >branch master at 202402051043 inputs file rtl_tcp RTL-SDR
> >weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any
> >messages, warnings, and errors in the console.
> >weewxd[2386]: ERROR user.sdr: usb_open error -3
> >weewxd[2386]: ERROR user.sdr: Please fix the device
> permissions,
> >e.g. by installing the udev rules file rtl-sdr.rules
> >weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting
> engine
> >down.
> >weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f
> 433.7M -s
> >1024k -R 40
> >weewxd[2386]: Exception in thread stdout-thread:
> >weewxd[2386]: Traceback (most recent call last):
> >weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line
> 954,
> >in _bootstrap_inner
> >weewxd[2386]: Exception in thread stderr-thread:
> >weewxd[2386]: Traceback (most recent call last):
> >weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line
> 954,
> >in _bootstrap_inner
> >weewxd[2386]: self.run()
> >weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197,
> in run
> >weewxd[2386]: for line in iter(self._fd.readline, ''):
> >weewxd[2386]: ValueError: PyMemoryView_FromBuffer():
> info->buf must
> >not be NULL
> >weewxd[2386]: self.run()
> >weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197,
> in run
> >weewxd[2386]: for line in iter(self._fd.readline, ''):
> >weewxd[2386]: ValueError: PyMemoryView_FromBuffer():
> info->buf must
> >not be NULL
> >weewxd[2386]: INFO user.sdr: shutdown complete
> >weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433
> >process is not running
> >weewxd[2386]: CRITICAL __main__:   Waiting 60.0
> seconds
> >then retrying...
> >
> >--
> >You received this message because you are subscribed to the
> Google
> >Groups "weewx-user" group.
> >To unsubscribe from this group and stop receiving emails from
> it,
> >send an email to weewx-user+...@googlegroups.com.
> >To view this discussion on the web visit
> https://groups.google.com/
> >d/msgid/weewx-user/
> >4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/3eff3ae3-8343-437e-a259-ae24753baa61n%40googlegroups.com.
>
>
> --
> If you tell the truth, y

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Dominic Reich]

'michael.k...@gmx.at' via weewx-user  wrote:



sudo apt install weewx=4.10.2


and to not upgrade again set it on hold:

sudo apt-mark hold weewx


Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:

   I run weewx 4.10.2 on Ubuntu.
   I did an sudo apt update, too,  and weewx 5.x got installed.
   Since then, weewx is no longer running.

   How did you revert back to weewx 4.10.2? 

   TIA,
   Stefan

   On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:


   I had the same error with sdr driver(weewx v5 )  running on debian 12 .
   The problem solved by making udev rules ... maybe you are in the same
   situation as i was.


   Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:

   The system was running weewx v5.0.0 with no issue then we did the
   upgrade to v5.0.1 (sudo apt update) and weewx failed to run.
   we downgraded weewx to v5.0.0 but it did not work this time, so we
   went back to v4.10.2 and it run just fine.
   did the upgrade again and got the same error.so we are back to
   v4.10.2
   we tested the sdr hardware using rtl_433 and it is working fine.
   we are not sure of what to do next!

   log:
   weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
   weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to
   database 'weewx.sdb'
   weewxd[2386]: INFO weewx.manager: Starting backfill of daily
   summaries
   weewxd[2386]: INFO weewx.manager: Daily summaries up to date
   weewxd[2386]: INFO weewx.engine: Starting main packet loop.
   weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a
   branch master at 202402051043 inputs file rtl_tcp RTL-SDR
   weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any
   messages, warnings, and errors in the console.
   weewxd[2386]: ERROR user.sdr: usb_open error -3
   weewxd[2386]: ERROR user.sdr: Please fix the device permissions,
   e.g. by installing the udev rules file rtl-sdr.rules
   weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine
   down.
   weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s
   1024k -R 40
   weewxd[2386]: Exception in thread stdout-thread:
   weewxd[2386]: Traceback (most recent call last):
   weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954,
   in _bootstrap_inner
   weewxd[2386]: Exception in thread stderr-thread:
   weewxd[2386]: Traceback (most recent call last):
   weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954,
   in _bootstrap_inner
   weewxd[2386]:     self.run()
   weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
   weewxd[2386]:     for line in iter(self._fd.readline, ''):
   weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must
   not be NULL
   weewxd[2386]:     self.run()
   weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
   weewxd[2386]:     for line in iter(self._fd.readline, ''):
   weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must
   not be NULL
   weewxd[2386]: INFO user.sdr: shutdown complete
   weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433
   process is not running
   weewxd[2386]: CRITICAL __main__:       Waiting 60.0 seconds
   then retrying...

   --
   You received this message because you are subscribed to the Google
   Groups "weewx-user" group.
   To unsubscribe from this group and stop receiving emails from it,
   send an email to weewx-user+...@googlegroups.com.
   To view this discussion on the web visit https://groups.google.com/
   d/msgid/weewx-user/
   4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/3eff3ae3-8343-437e-a259-ae24753baa61n%40googlegroups.com.



--
If you tell the truth, you don't have to remember anything.
- Mark Twain

--
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/%24kwshnkklb-%24RmhmQzk-%24qdrNT-2024%40odin.oe7drt.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

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

sudo apt install weewx=4.10.2
Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:

> I run weewx 4.10.2 on Ubuntu.
> I did an sudo apt update, too,  and weewx 5.x got installed.
> Since then, weewx is no longer running.
>
> How did you revert back to weewx 4.10.2? 
>
> TIA,
> Stefan
>
> On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:
>
>> I had the same error with sdr driver(weewx v5 )  running on debian 12 . 
>> The problem solved by making udev rules ... maybe you are in the same 
>> situation as i was. 
>>
>> Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:
>>
>>> The system was running weewx v5.0.0 with no issue then we did the 
>>> upgrade to v5.0.1 (sudo apt update) and weewx failed to run.
>>> we downgraded weewx to v5.0.0 but it did not work this time, so we went 
>>> back to v4.10.2 and it run just fine.
>>> did the upgrade again and got the same error.so we are back to v4.10.2
>>> we tested the sdr hardware using rtl_433 and it is working fine.
>>> we are not sure of what to do next!
>>>
>>> log:
>>> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
>>> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
>>> 'weewx.sdb'
>>> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
>>> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
>>> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
>>> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
>>> master at 202402051043 inputs file rtl_tcp RTL-SDR
>>> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
>>> warnings, and errors in the console.
>>> weewxd[2386]: ERROR user.sdr: usb_open error -3
>>> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
>>> installing the udev rules file rtl-sdr.rules
>>> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
>>> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k 
>>> -R 40
>>> weewxd[2386]: Exception in thread stdout-thread:
>>> weewxd[2386]: Traceback (most recent call last):
>>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>>> _bootstrap_inner
>>> weewxd[2386]: Exception in thread stderr-thread:
>>> weewxd[2386]: Traceback (most recent call last):
>>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>>> _bootstrap_inner
>>> weewxd[2386]: self.run()
>>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>>> be NULL
>>> weewxd[2386]: self.run()
>>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>>> be NULL
>>> weewxd[2386]: INFO user.sdr: shutdown complete
>>> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
>>> not running
>>> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
>>> retrying...
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/3eff3ae3-8343-437e-a259-ae24753baa61n%40googlegroups.com.

[weewx-user] Re: New User: First Problem

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

The warning tells you: WeeWX is receiving 0.0 for "pressure". You say, "The 
hardware console is operating correctly as expected", so the problem is 
somewhere in between the hardware and the LOOP. It may be, that your 
hardware/driver combination doesn't supply a valid value for "pressure" (it 
should return "None" instead of "0.0" in this case), did you try 
"barometer" or "altimeter" instead? You can also check in your database, if 
there are values for these types. If so, take a look into this article 
, 
to make sure, you really use the correct type for your needs. Having only 
one out of the three "pressure", "altimeter" and "barometer", it should be 
possible to calculate the others, when you have the altitude, the 
temperature and humidity (or even something in addition to that).

Alan Salmon schrieb am Dienstag, 6. Februar 2024 um 12:48:48 UTC+1:

> Hello everyone.
>
> I installed weewx for the first time today on a Raspberry Pi Zero 2W, 
> using a Fine Offset 3081 station that I used for about 10 years until the 
> local cockatoos decided it would be fun to dismantle it!
>
> It came up on the second attempt after a few minor adjustments to the 
> config file, paths, etc. (I used the pip install method on Debian 11).
>
> The hardware console is operating correctly as expected, but weewx is 
> giving me the following error:
>
> Feb  6 22:26:01 bigfish-08 weewxd[1909]: WARNING weewx.qc: 2024-02-06 
> 22:26:02 AEDT (1707218762) LOOP value 'pressure' 0.0 outside limits (24.0, 
> 34.5)
>
> As the value displayed on the console (roughly) agrees with a BME680 I 
> have running, can anyone suggest where I should start trying to solve this?
>
> Note that I am configured for metric with barometric pressure in 
> hectopascals (hPa) which is currently just over 1010hPa, so I am at a bit 
> of a loss as to why it is showing '0.0' and where the range "24.0 to 34.5' 
> comes from.
>
> The error has been consistent for the 9 hours it has been running.
>
> Thanks for any advice you can offer.
>
>
>

-- 
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/31ad1404-a6ee-4245-868b-15f75bd7e73bn%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefan Gliessmann]

I run weewx 4.10.2 on Ubuntu.
I did an sudo apt update, too,  and weewx 5.x got installed.
Since then, weewx is no longer running.

How did you revert back to weewx 4.10.2? 

TIA,
Stefan

On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:

> I had the same error with sdr driver(weewx v5 )  running on debian 12 . 
> The problem solved by making udev rules ... maybe you are in the same 
> situation as i was. 
>
> Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:
>
>> The system was running weewx v5.0.0 with no issue then we did the upgrade 
>> to v5.0.1 (sudo apt update) and weewx failed to run.
>> we downgraded weewx to v5.0.0 but it did not work this time, so we went 
>> back to v4.10.2 and it run just fine.
>> did the upgrade again and got the same error.so we are back to v4.10.2
>> we tested the sdr hardware using rtl_433 and it is working fine.
>> we are not sure of what to do next!
>>
>> log:
>> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
>> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
>> 'weewx.sdb'
>> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
>> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
>> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
>> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
>> master at 202402051043 inputs file rtl_tcp RTL-SDR
>> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
>> warnings, and errors in the console.
>> weewxd[2386]: ERROR user.sdr: usb_open error -3
>> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
>> installing the udev rules file rtl-sdr.rules
>> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
>> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k 
>> -R 40
>> weewxd[2386]: Exception in thread stdout-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: Exception in thread stderr-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: INFO user.sdr: shutdown complete
>> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
>> not running
>> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
>> retrying...
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/ab729bc6-195f-498e-b0db-e404297666den%40googlegroups.com.

[weewx-user] New User: First Problem

[Alan Salmon]

Hello everyone.

I installed weewx for the first time today on a Raspberry Pi Zero 2W, using 
a Fine Offset 3081 station that I used for about 10 years until the local 
cockatoos decided it would be fun to dismantle it!

It came up on the second attempt after a few minor adjustments to the 
config file, paths, etc. (I used the pip install method on Debian 11).

The hardware console is operating correctly as expected, but weewx is 
giving me the following error:

Feb  6 22:26:01 bigfish-08 weewxd[1909]: WARNING weewx.qc: 2024-02-06 
22:26:02 AEDT (1707218762) LOOP value 'pressure' 0.0 outside limits (24.0, 
34.5)

As the value displayed on the console (roughly) agrees with a BME680 I have 
running, can anyone suggest where I should start trying to solve this?

Note that I am configured for metric with barometric pressure in 
hectopascals (hPa) which is currently just over 1010hPa, so I am at a bit 
of a loss as to why it is showing '0.0' and where the range "24.0 to 34.5' 
comes from.

The error has been consistent for the 9 hours it has been running.

Thanks for any advice you can offer.


-- 
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/f49665de-94c1-4217-bb14-87ad6e0c51b8n%40googlegroups.com.

Re: [weewx-user] Which driver should i target for my custom weather station?

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

A few thoughts:

Building the "station" on a ESP8266 doesn't sound like you are planning to 
get too far with your project. Compared to it's successor, it is very 
limited and has some really weird flaws.
Why would you connect the station with a serial interface, when it has WIFI 
on board?
p q's MQTT suggestion is a not a bad one. Let your station emit every 
single sensor reading as a MQTT message, and let weewx receive it with MQTT 
Subscribe 
Either MQTT Subscribe as a service, augmenting any off-the-shelf station 
supported by weewx with your sensors data, or use it as a driver. 
Encapsulating sensor data in JSON for the MQTT payload is commonly done and 
supported by MQTT Subscribe.
Pavocracy schrieb am Dienstag, 6. Februar 2024 um 11:07:05 UTC+1:

> I'm not sure if im misunderstanding what you are saying, or if i am not 
> doing a good job at explaining my question, but even if i choose mqtt as my 
> location to push the data, the data still needs to be in some specific 
> format for weewx to understand it no?
>
> So on the esp8266, that has a bunch of sensors attached to it, in my 
> embedded code i need to collect the data point for the sensor, and then put 
> it in some specific format to send along somewhere that weewx will read. 
> Reading through the source code it looked like the drivers are where these 
> message formats are interrupted, but i could be wrong?
>
> On Monday 5 February 2024 at 23:45:25 UTC+10 p q wrote:
>
>> If I was going to do this, I would look into mqtt options. 
>>
>> On Sun, Feb 4, 2024, 11:03 PM 'Pavocracy' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Hello all,
>>>
>>> I am working on a hobby project where i am trying to build my own 
>>> "weather station" from an esp8266 and a bunch of sensors. I am very keen on 
>>> using weewx to display the post the data, and so i am looking at the 
>>> supported drivers and wondering if there is an obvious answer to which 
>>> driver i should be targeting for my weather station output. 
>>>
>>> Is there an obvious choice for which driver supports the most data, or 
>>> perhaps is the easiest data to read or is there a driver that is the most 
>>> robust? (particularly for serial connections)
>>>
>>> any thoughts or experience on the matter would be greatly appreciated :) 
>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/831bd64d-0271-459c-9b52-929817b02319n%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/f0733294-4828-4b22-941a-33de46a803fbn%40googlegroups.com.

Re: [weewx-user] Which driver should i target for my custom weather station?

['Pavocracy' via weewx-user]

I'm not sure if im misunderstanding what you are saying, or if i am not 
doing a good job at explaining my question, but even if i choose mqtt as my 
location to push the data, the data still needs to be in some specific 
format for weewx to understand it no?

So on the esp8266, that has a bunch of sensors attached to it, in my 
embedded code i need to collect the data point for the sensor, and then put 
it in some specific format to send along somewhere that weewx will read. 
Reading through the source code it looked like the drivers are where these 
message formats are interrupted, but i could be wrong?

On Monday 5 February 2024 at 23:45:25 UTC+10 p q wrote:

> If I was going to do this, I would look into mqtt options. 
>
> On Sun, Feb 4, 2024, 11:03 PM 'Pavocracy' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Hello all,
>>
>> I am working on a hobby project where i am trying to build my own 
>> "weather station" from an esp8266 and a bunch of sensors. I am very keen on 
>> using weewx to display the post the data, and so i am looking at the 
>> supported drivers and wondering if there is an obvious answer to which 
>> driver i should be targeting for my weather station output. 
>>
>> Is there an obvious choice for which driver supports the most data, or 
>> perhaps is the easiest data to read or is there a driver that is the most 
>> robust? (particularly for serial connections)
>>
>> any thoughts or experience on the matter would be greatly appreciated :) 
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/831bd64d-0271-459c-9b52-929817b02319n%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/a72db002-f719-4060-9a18-08b60a27fd1en%40googlegroups.com.

[weewx-user] MQTT publish time after upgrade to weewx 5.0.1

[Mario Wesolek]

hi there!

i use weewx with belchertown skin and publish the data via mqtt. in 
versions < 5.0.1 mqtt publish the data to every full minute, like 10:01:00, 
10:02:00 and so on... after upgrade the time is uneven, like:

Feb  6 09:56:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 09:56:50 CET (1707209810)
Feb  6 09:57:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 09:57:50 CET (1707209870)
Feb  6 09:58:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 09:58:51 CET (1707209931)
Feb  6 09:59:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 09:59:51 CET (1707209991)
Feb  6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 10:00:00 CET (170721)
Feb  6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published 
record 2024-02-06 10:00:52 CET (1707210052)

this is not really a problem but i will understand the reason. have anybody 
a explanation? 

thank you very much!
mario 

-- 
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/84563b0d-0e91-4e65-91e6-65691d6685c6n%40googlegroups.com.

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefanos Kalaitzis]

I had the same error with sdr driver(weewx v5 )  running on debian 12 . The
problem solved by making udev rules ... maybe you are in the same situation
as i was.

Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:

> The system was running weewx v5.0.0 with no issue then we did the upgrade
> to v5.0.1 (sudo apt update) and weewx failed to run.
> we downgraded weewx to v5.0.0 but it did not work this time, so we went
> back to v4.10.2 and it run just fine.
> did the upgrade again and got the same error.so we are back to v4.10.2
> we tested the sdr hardware using rtl_433 and it is working fine.
> we are not sure of what to do next!
>
> log:
> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database
> 'weewx.sdb'
> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch
> master at 202402051043 inputs file rtl_tcp RTL-SDR
> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages,
> warnings, and errors in the console.
> weewxd[2386]: ERROR user.sdr: usb_open error -3
> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by
> installing the udev rules file rtl-sdr.rules
> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k
> -R 40
> weewxd[2386]: Exception in thread stdout-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: Exception in thread stderr-thread:
> weewxd[2386]: Traceback (most recent call last):
> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in
> _bootstrap_inner
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: self.run()
> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
> weewxd[2386]: for line in iter(self._fd.readline, ''):
> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be
> NULL
> weewxd[2386]: INFO user.sdr: shutdown complete
> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is
> not running
> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then
> retrying...
>
> --
> 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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%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/CAERekb9xjoLYZAFcRMLwVCEHPHqaqMvEmGUFCY2EyheB2FdugA%40mail.gmail.com.

[weewx-user] Re: Klimalogg driver fails after update to weewx 5.0.0.1

[Marco Biner]

Hi Michael
thanks for your hint, after a reboot it works, I did not assume that debian 
adapts wind*ws style to do a reboot after updates.
Regards
Marco

michael.k...@gmx.at schrieb am Dienstag, 6. Februar 2024 um 10:02:18 UTC+1:

> So this is a package install? Did you do try restating already? A friend 
> had the same error with a package install update 5.0.0 =>  5.0.1 on 
> Raspberry Pi OS, but with the ws23xx driver. He restarted the OS, then it 
> worked. Maybe restarting udev or another daemon is sufficient also, I don't 
> know.
>
> Marco Biner schrieb am Dienstag, 6. Februar 2024 um 09:40:51 UTC+1:
>
>> Hello
>> seems that I am one of the rare users of the kl.py application from 
>> Matthew Wall.
>> As google does not help me with a solution here my problem.
>> After the last update of weewx to version 5.0.0.1 kl.py fails importing 
>> the driver:
>>
>> the log file reports:
>>
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Initializing 
>> weewxd version 5.0.1
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Command line: 
>> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Using Python 
>> 3.9.2 (default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Located at 
>> /usr/bin/python3
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Platform 
>> Linux-6.1.21-v8+-aarch64-with-glibc2.31
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Locale: 
>> 'en_US.UTF-8'
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Entry path: 
>> /usr/share/weewx/weewxd.py
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: WEEWX_ROOT: 
>> /etc/weewx
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Configuration 
>> file: /etc/weewx/weewx.conf
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: User module: 
>> /etc/weewx/bin/user
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Debug: 1
>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG __main__: Initializing 
>> engine
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO weewx.engine: Loading 
>> station type KlimaLogg (user.kl)
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: driver version is 
>> 1.4.2
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: channel is 1
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: frequency is EU
>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: using custom 
>> sensor map
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: sensor map is: 
>> {'temp0': 'Temp0', 'humidity0': 'Humidity0', 'heatindex0': 'heatindex0', 
>> 'dewpoint0': 'dewpoint0', 'temp1': 'Temp1', 'humidity1': 'Humidity1', 
>> 'heatindex1': 'heatindex1', 'dewpoint1': 'dewpoint1', 'temp2': 'Temp2', 
>> 'humidity2': 'Humidity2', 'heatindex2': 'heatindex2', 'dewpoint2': 
>> 'dewpoint2', 'temp3': 'Temp3', 'humidity3': 'Humidity3', 'heatindex3': 
>> 'heatindex3', 'dewpoint3': 'dewpoint3', 'temp4': 'Temp4', 'humidity4': 
>> 'Humidity4', 'heatindex4': 'heatindex4', 'dewpoint4': 'dewpoint4', 'temp5': 
>> 'Temp5', 'humidity5': 'Humidity5', 'temp6': 'Temp6', 'humidity6': 
>> 'Humidity6', 'temp7': 'Temp7', 'humidity7': 'Humidity7', 'temp8': 'Temp8', 
>> 'humidity8': 'Humidity8', 'rxCheckPercent': 'SignalQuality', 
>> 'batteryStatus0': 'BatteryStatus0', 'batteryStatus1': 'BatteryStatus1', 
>> 'batteryStatus2': 'BatteryStatus2', 'batteryStatus3': 'BatteryStatus3', 
>> 'batteryStatus4': 'BatteryStatus4', 'batteryStatus5': 'BatteryStatus5', 
>> 'batteryStatus6': 'BatteryStatus6', 'batteryStatus7': 'BatteryStatus7', 
>> 'batteryStatus8': 'BatteryStatus8', 'Sensor1': 'Kollektor warm aus', 
>> 'Sensor2': 'Kollektor kalt in', 'Sensor3': 'Speicher unten', 'Sensor4': 
>> 'Waermepumpe Ruecklauf', 'Sensor5': 'Boiler warm aus', 'Sensor6': 'Boiler 
>> kalt in', 'Sensor7': 'Speicher Mitte', 'Sensor8': 'Speicher oben', 
>> 'Sensor9': 'Speicher Brauchwasser', 'Sensor10': 'Schacht', 'Sensor11': 
>> 'Erdsonde 1', 'Sensor12': 'Erdsonde 2', 'Sensor13': 'Heizung Vorlauf', 
>> 'Sensor14': 'Temperatur 5Zi Wohnug', 'Sensor15': 'Temperatur Aussen', 
>> 'Sensor16': 'Warmwasser', 'Sensor17': 'Drehzahl Pumpe Brauchwasser'}
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: catchup limited 
>> to 51200 records
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: timing is 300 ms 
>> (0.300 s)
>> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: 
>> CommunicationService.init
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: comm_interval is 8
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: logger_channel is 
>> 1
>> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: found transceiver 
>> at bus= device=
>> Feb  6 08:46:44 curlevon weewxd[3865888]: ERROR weewx.engine: Import of 
>> driver failed: The device has no langid ()
>> Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:  
>>  Traceback (

[weewx-user] weewx v5.0.1 upgrade problem

[Mks Mk]

The system was running weewx v5.0.0 with no issue then we did the upgrade 
to v5.0.1 (sudo apt update) and weewx failed to run.
we downgraded weewx to v5.0.0 but it did not work this time, so we went 
back to v4.10.2 and it run just fine.
did the upgrade again and got the same error.so we are back to v4.10.2
we tested the sdr hardware using rtl_433 and it is working fine.
we are not sure of what to do next!

log:
weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
'weewx.sdb'
weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
weewxd[2386]: INFO weewx.manager: Daily summaries up to date
weewxd[2386]: INFO weewx.engine: Starting main packet loop.
weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
master at 202402051043 inputs file rtl_tcp RTL-SDR
weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
warnings, and errors in the console.
weewxd[2386]: ERROR user.sdr: usb_open error -3
weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
installing the udev rules file rtl-sdr.rules
weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k -R 
40
weewxd[2386]: Exception in thread stdout-thread:
weewxd[2386]: Traceback (most recent call last):
weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
_bootstrap_inner
weewxd[2386]: Exception in thread stderr-thread:
weewxd[2386]: Traceback (most recent call last):
weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
_bootstrap_inner
weewxd[2386]: self.run()
weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
weewxd[2386]: for line in iter(self._fd.readline, ''):
weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be 
NULL
weewxd[2386]: self.run()
weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
weewxd[2386]: for line in iter(self._fd.readline, ''):
weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not be 
NULL
weewxd[2386]: INFO user.sdr: shutdown complete
weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
not running
weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
retrying...

-- 
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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%40googlegroups.com.

[weewx-user] Re: Klimalogg driver fails after update to weewx 5.0.0.1

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

So this is a package install? Did you do try restating already? A friend 
had the same error with a package install update 5.0.0 =>  5.0.1 on 
Raspberry Pi OS, but with the ws23xx driver. He restarted the OS, then it 
worked. Maybe restarting udev or another daemon is sufficient also, I don't 
know.

Marco Biner schrieb am Dienstag, 6. Februar 2024 um 09:40:51 UTC+1:

> Hello
> seems that I am one of the rare users of the kl.py application from 
> Matthew Wall.
> As google does not help me with a solution here my problem.
> After the last update of weewx to version 5.0.0.1 kl.py fails importing 
> the driver:
>
> the log file reports:
>
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Initializing 
> weewxd version 5.0.1
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Command line: 
> /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Using Python 
> 3.9.2 (default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Located at 
> /usr/bin/python3
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Platform 
> Linux-6.1.21-v8+-aarch64-with-glibc2.31
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Locale: 
> 'en_US.UTF-8'
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Entry path: 
> /usr/share/weewx/weewxd.py
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: WEEWX_ROOT: 
> /etc/weewx
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Configuration 
> file: /etc/weewx/weewx.conf
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: User module: 
> /etc/weewx/bin/user
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Debug: 1
> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG __main__: Initializing 
> engine
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO weewx.engine: Loading 
> station type KlimaLogg (user.kl)
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: driver version is 
> 1.4.2
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: channel is 1
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: frequency is EU
> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: using custom 
> sensor map
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: sensor map is: 
> {'temp0': 'Temp0', 'humidity0': 'Humidity0', 'heatindex0': 'heatindex0', 
> 'dewpoint0': 'dewpoint0', 'temp1': 'Temp1', 'humidity1': 'Humidity1', 
> 'heatindex1': 'heatindex1', 'dewpoint1': 'dewpoint1', 'temp2': 'Temp2', 
> 'humidity2': 'Humidity2', 'heatindex2': 'heatindex2', 'dewpoint2': 
> 'dewpoint2', 'temp3': 'Temp3', 'humidity3': 'Humidity3', 'heatindex3': 
> 'heatindex3', 'dewpoint3': 'dewpoint3', 'temp4': 'Temp4', 'humidity4': 
> 'Humidity4', 'heatindex4': 'heatindex4', 'dewpoint4': 'dewpoint4', 'temp5': 
> 'Temp5', 'humidity5': 'Humidity5', 'temp6': 'Temp6', 'humidity6': 
> 'Humidity6', 'temp7': 'Temp7', 'humidity7': 'Humidity7', 'temp8': 'Temp8', 
> 'humidity8': 'Humidity8', 'rxCheckPercent': 'SignalQuality', 
> 'batteryStatus0': 'BatteryStatus0', 'batteryStatus1': 'BatteryStatus1', 
> 'batteryStatus2': 'BatteryStatus2', 'batteryStatus3': 'BatteryStatus3', 
> 'batteryStatus4': 'BatteryStatus4', 'batteryStatus5': 'BatteryStatus5', 
> 'batteryStatus6': 'BatteryStatus6', 'batteryStatus7': 'BatteryStatus7', 
> 'batteryStatus8': 'BatteryStatus8', 'Sensor1': 'Kollektor warm aus', 
> 'Sensor2': 'Kollektor kalt in', 'Sensor3': 'Speicher unten', 'Sensor4': 
> 'Waermepumpe Ruecklauf', 'Sensor5': 'Boiler warm aus', 'Sensor6': 'Boiler 
> kalt in', 'Sensor7': 'Speicher Mitte', 'Sensor8': 'Speicher oben', 
> 'Sensor9': 'Speicher Brauchwasser', 'Sensor10': 'Schacht', 'Sensor11': 
> 'Erdsonde 1', 'Sensor12': 'Erdsonde 2', 'Sensor13': 'Heizung Vorlauf', 
> 'Sensor14': 'Temperatur 5Zi Wohnug', 'Sensor15': 'Temperatur Aussen', 
> 'Sensor16': 'Warmwasser', 'Sensor17': 'Drehzahl Pumpe Brauchwasser'}
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: catchup limited to 
> 51200 records
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: timing is 300 ms 
> (0.300 s)
> Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: 
> CommunicationService.init
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: comm_interval is 8
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: logger_channel is 1
> Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: found transceiver 
> at bus= device=
> Feb  6 08:46:44 curlevon weewxd[3865888]: ERROR weewx.engine: Import of 
> driver failed: The device has no langid ()
> Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:  
>  Traceback (most recent call last):
> Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:  
>File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
> Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:  
>  self.console = loader_function(config_dict, self)
> Feb  6 08:46:44 c

[weewx-user] Klimalogg driver fails after update to weewx 5.0.0.1

[Marco Biner]

Hello
seems that I am one of the rare users of the kl.py application from Matthew 
Wall.
As google does not help me with a solution here my problem.
After the last update of weewx to version 5.0.0.1 kl.py fails importing the 
driver:

the log file reports:

Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Initializing 
weewxd version 5.0.1
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Command line: 
/usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Using Python 3.9.2 
(default, Feb 28 2021, 17:03:44) #012[GCC 10.2.1 20210110]
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Located at 
/usr/bin/python3
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Platform 
Linux-6.1.21-v8+-aarch64-with-glibc2.31
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Locale: 
'en_US.UTF-8'
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Entry path: 
/usr/share/weewx/weewxd.py
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: WEEWX_ROOT: 
/etc/weewx
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Configuration 
file: /etc/weewx/weewx.conf
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: User module: 
/etc/weewx/bin/user
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO __main__: Debug: 1
Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG __main__: Initializing 
engine
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO weewx.engine: Loading 
station type KlimaLogg (user.kl)
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: driver version is 
1.4.2
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: channel is 1
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: frequency is EU
Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: using custom 
sensor map
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: sensor map is: 
{'temp0': 'Temp0', 'humidity0': 'Humidity0', 'heatindex0': 'heatindex0', 
'dewpoint0': 'dewpoint0', 'temp1': 'Temp1', 'humidity1': 'Humidity1', 
'heatindex1': 'heatindex1', 'dewpoint1': 'dewpoint1', 'temp2': 'Temp2', 
'humidity2': 'Humidity2', 'heatindex2': 'heatindex2', 'dewpoint2': 
'dewpoint2', 'temp3': 'Temp3', 'humidity3': 'Humidity3', 'heatindex3': 
'heatindex3', 'dewpoint3': 'dewpoint3', 'temp4': 'Temp4', 'humidity4': 
'Humidity4', 'heatindex4': 'heatindex4', 'dewpoint4': 'dewpoint4', 'temp5': 
'Temp5', 'humidity5': 'Humidity5', 'temp6': 'Temp6', 'humidity6': 
'Humidity6', 'temp7': 'Temp7', 'humidity7': 'Humidity7', 'temp8': 'Temp8', 
'humidity8': 'Humidity8', 'rxCheckPercent': 'SignalQuality', 
'batteryStatus0': 'BatteryStatus0', 'batteryStatus1': 'BatteryStatus1', 
'batteryStatus2': 'BatteryStatus2', 'batteryStatus3': 'BatteryStatus3', 
'batteryStatus4': 'BatteryStatus4', 'batteryStatus5': 'BatteryStatus5', 
'batteryStatus6': 'BatteryStatus6', 'batteryStatus7': 'BatteryStatus7', 
'batteryStatus8': 'BatteryStatus8', 'Sensor1': 'Kollektor warm aus', 
'Sensor2': 'Kollektor kalt in', 'Sensor3': 'Speicher unten', 'Sensor4': 
'Waermepumpe Ruecklauf', 'Sensor5': 'Boiler warm aus', 'Sensor6': 'Boiler 
kalt in', 'Sensor7': 'Speicher Mitte', 'Sensor8': 'Speicher oben', 
'Sensor9': 'Speicher Brauchwasser', 'Sensor10': 'Schacht', 'Sensor11': 
'Erdsonde 1', 'Sensor12': 'Erdsonde 2', 'Sensor13': 'Heizung Vorlauf', 
'Sensor14': 'Temperatur 5Zi Wohnug', 'Sensor15': 'Temperatur Aussen', 
'Sensor16': 'Warmwasser', 'Sensor17': 'Drehzahl Pumpe Brauchwasser'}
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: catchup limited to 
51200 records
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: timing is 300 ms 
(0.300 s)
Feb  6 08:46:44 curlevon weewxd[3865888]: DEBUG user.kl: 
CommunicationService.init
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: comm_interval is 8
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: logger_channel is 1
Feb  6 08:46:44 curlevon weewxd[3865888]: INFO user.kl: found transceiver 
at bus= device=
Feb  6 08:46:44 curlevon weewxd[3865888]: ERROR weewx.engine: Import of 
driver failed: The device has no langid ()
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:  
 Traceback (most recent call last):
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 115, in setupStation
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
   self.console = loader_function(config_dict, self)
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
 File "/etc/weewx/bin/user/kl.py", line 1242, in loader
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
   return KlimaLoggDriver(**config_dict[DRIVER_NAME])
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
 File "/etc/weewx/bin/user/kl.py", line 1796, in __init__
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx.engine:    
   self.startUp()
Feb  6 08:46:44 curlevon weewxd[3865888]: CRITICAL weewx

Re: [weewx-user] Another Davis Vantage unable to start concern

[Neil B]

Morning.

Good suggestion on "loop on init", however I already have this setting 
enabled (and have for a long time). I believe this setting applies once the 
main loop starts, which is much later in the process.

The idea of delaying the start up of WEEWX is good, and I am in favour of 
this approach. Question is (for the Linux novice) - how can you implement 
this? Any thoughts?

Thanks
Neil

On Tuesday 6 February 2024 at 00:13:55 UTC Tom Keffer wrote:

> All good suggestions.
>
> For *loop_on_init*, see this link 
> 
> .
>
> On Mon, Feb 5, 2024 at 3:29 PM Graham Eddy  wrote:
>
>> vantage device is on LAN. wireless interface normally not ready until 
>> long after weewx tries to start, unusual (but not impossible) for ethernet 
>> interface to be so late. try the ‘loop-on-init = 1’ in weewx.conf, or 
>> insert a delay in the startup file
>> *⊣GE⊢*
>>
>> On 6 Feb 2024, at 8:08 am, Neil B  wrote:
>>
>> Feb 05 20:54:10 WEATHER weewxd[877]: DEBUG weewx.drivers.vantage: Opened 
>> up ethernet host 192.168.1.249 on port 2. timeout=4.0, 
>> tcp_send_delay=0.5
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/F018B0FD-2319-41C3-88B1-10EC577E47FB%40geddy.au
>>  
>> 
>> .
>>
>

-- 
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/b223aeb6-4150-4644-9d41-bc39bbed268en%40googlegroups.com.