date:20240216

After the restore a new attempt, what is missing?

-- Journal begins at Fri 2024-02-02 10:19:01 CET. --
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.port.openPort()
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
openPort
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 
244, in __init__
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.open()
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
325, in open
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  raise SerialException(msg.errno, "could not open port {}: 
{}".format(self._port, msg))
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  serial.serialutil.SerialException: [Errno 13] could not open port 
/dev/ttyUSB0: [Errno 13] Keine Berechtigung: '/dev/ttyUSB0'
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__: Unable to 
load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Keine 
Berechtigung: '/dev/ttyUSB0'
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__:  
 Exiting...

matthew wall schrieb am Dienstag, 13. Februar 2024 um 14:32:41 UTC+1:

> On Tuesday, February 13, 2024 at 4:13:27 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> The third time I tried the Apt configuration, it found weewx.
> The installation worked so far except for the dpkg: Warnung: Altes 
> Verzeichnis.
> Unfortunately, weewx did not react after that and a reboot did not work 
> anymore.
> Now I have to restore the backup and try again.
> What went wrong?
>
>
> it looks like nothing is wrong with the upgrade.
>
> if weewx is not running, we must see the log messages from weewx.  these 
> will be in the system log (different from the installer log).  this should 
> give some hint about what is happening:
>
> sudo systermctl status weewx
>
> this wiki article has more information about logging:
>
> https://github.com/weewx/weewx/wiki/view-logs#journalctl
>
>

-- 
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/4b46e69d-83ec-419b-9e67-2c2cb2201075n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall

On Friday, February 16, 2024 at 7:43:26 AM UTC-5 geni08...@gmail.com wrote:

After the restore a new attempt, what is missing?

-- Journal begins at Fri 2024-02-02 10:19:01 CET. --
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.port.openPort()
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
openPort
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.serial_port = serial.Serial(self.port, self.baudrate, 
timeout=self.timeout)
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 
244, in __init__
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  self.open()
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
325, in open
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  raise SerialException(msg.errno, "could not open port {}: 
{}".format(self._port, msg))
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
  serial.serialutil.SerialException: [Errno 13] could not open port 
/dev/ttyUSB0: [Errno 13] Keine Berechtigung: '/dev/ttyUSB0'
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__: Unable to 
load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Keine 
Berechtigung: '/dev/ttyUSB0'
Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__:  
 Exiting...


the error indicates that the weewxd process does not have permission to 
read/write the USB-to-serial device.  make sure that the user running 
weewxd has read/write permission to /dev/ttyUSB0 (which is probably a 
USB-to-serial adapter).

for example, if user 'weewx' is running weewxd, then put the weewx user 
into the dialout group then restart weewxd:

sudo usermod -aG dialout weewx
sudo systemctl restart weewx

see the section about reading/writing to devices in the wiki article "what 
you need to know about permissions":

https://github.com/weewx/weewx/wiki/Understanding-permissions#readingwriting-data-to-a-device

-- 
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/77a3041b-1e87-4883-ae1e-943c74f90c1an%40googlegroups.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

where can i see which user starts weewxd?
It worked with weewx

matthew wall schrieb am Freitag, 16. Februar 2024 um 13:47:00 UTC+1:

> On Friday, February 16, 2024 at 7:43:26 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> After the restore a new attempt, what is missing?
>
> -- Journal begins at Fri 2024-02-02 10:19:01 CET. --
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
>   self.port.openPort()
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
> File "/usr/share/weewx/weewx/drivers/vantage.py", line 319, in 
> openPort
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
>   self.serial_port = serial.Serial(self.port, self.baudrate, 
> timeout=self.timeout)
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
> File "/usr/lib/python3/dist-packages/serial/serialutil.py", line 
> 244, in __init__
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
>   self.open()
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
> File "/usr/lib/python3/dist-packages/serial/serialposix.py", line 
> 325, in open
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
>   raise SerialException(msg.errno, "could not open port {}: 
> {}".format(self._port, msg))
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL weewx.engine: 
>   serial.serialutil.SerialException: [Errno 13] could not open port 
> /dev/ttyUSB0: [Errno 13] Keine Berechtigung: '/dev/ttyUSB0'
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__: Unable to 
> load driver: [Errno 13] could not open port /dev/ttyUSB0: [Errno 13] Keine 
> Berechtigung: '/dev/ttyUSB0'
> Feb 16 13:18:47 Wetter-Raspi4 weewxd[416320]: CRITICAL __main__:  
>  Exiting...
>
>
> the error indicates that the weewxd process does not have permission to 
> read/write the USB-to-serial device.  make sure that the user running 
> weewxd has read/write permission to /dev/ttyUSB0 (which is probably a 
> USB-to-serial adapter).
>
> for example, if user 'weewx' is running weewxd, then put the weewx user 
> into the dialout group then restart weewxd:
>
> sudo usermod -aG dialout weewx
> sudo systemctl restart weewx
>
> see the section about reading/writing to devices in the wiki article "what 
> you need to know about permissions":
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#readingwriting-data-to-a-device
>
>

-- 
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/c4cdf6d0-5d62-4aef-83dd-823fde416099n%40googlegroups.com.

[weewx-user] Display the first date entry in the database

Hello everyone
I would like to display the date of the first entry in the weexs.sdb in 
Belchertownskin. The reason for this is that you can see how long the 
weather station has been in operation. Since I operate several stations, 
this would make my work extremely easier. This could say something like 
"Operating since: 10/2023" or something like that. Can someone help me with 
that?
Thank you and sunny greetings

-- 
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/65e5faa2-2cda-4014-ae79-f236286b312fn%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

2024-02-16 Thread Dominic Reich


Meteo Oberwallis  wrote:


Hello everyone
I would like to display the date of the first entry in the weexs.sdb in
Belchertownskin. The reason for this is that you can see how long the weather
station has been in operation. Since I operate several stations, this would
make my work extremely easier. This could say something like "Operating since:
10/2023" or something like that. Can someone help me with that?
Thank you and sunny greetings


Just fetch the first entry from the database.

sqlite3 dbfile.db "SELECT dateTime FROM archive LIMIT 1;"

(untested)

--
The quieter you become, the more you can hear.
- Ram Dass

--
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/d9JLkt9bqdhx-73wMzL-0224%40odin.oe7drt.com.

Re: [weewx-user] Display the first date entry in the database

I haven't tried it, but I don't see why the following wouldn't work:

*$alltime.dateTime.min*

-tk

On Fri, Feb 16, 2024 at 4:59 AM Meteo Oberwallis 
wrote:

> Hello everyone
> I would like to display the date of the first entry in the weexs.sdb in
> Belchertownskin. The reason for this is that you can see how long the
> weather station has been in operation. Since I operate several stations,
> this would make my work extremely easier. This could say something like
> "Operating since: 10/2023" or something like that. Can someone help me with
> that?
> Thank you and sunny greetings
>
> --
> 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/65e5faa2-2cda-4014-ae79-f236286b312fn%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/CAPq0zEBdp6zguJhr0awrJ2RQPJUFitTYPWQF20Xnpr%2B_zBhqzw%40mail.gmail.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall



On Friday, February 16, 2024 at 7:57:08 AM UTC-5 geni08...@gmail.com wrote:

where can i see which user starts weewxd?


if weewxd is running, do this:

ps aux | grep weewxd

the first word is the user running weewxd

if weewxd is not running, then check the value for 'User' in the systemd 
unit file

# if you installed using DEB/RPM:
grep User /usr/lib/systemd/system/weewx.service

# if you installed using pip:
grep User /etc/systemd/system/weewx.service

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/3f428433-991a-4829-ba71-eafbe2c90e05n%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

2024-02-16 Thread 'steepleian' via weewx-user

This is what I use which works: -$alltime.outTemp.firsttime.raw";Ianhttps://claydonsweather.org.ukOn 16 Feb 2024, at 13:43, Tom Keffer wrote:I haven't tried it, but I don't see why the following wouldn't work:$alltime.dateTime.min-tkOn Fri, Feb 16, 2024 at 4:59 AM Meteo Oberwallis wrote:Hello everyoneI would like to display the date of the first entry in the weexs.sdb in Belchertownskin. The reason for this is that you can see how long the weather station has been in operation. Since I operate several stations, this would make my work extremely easier. This could say something like "Operating since: 10/2023" or something like that. Can someone help me with that?Thank you and sunny greetings

--
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/65e5faa2-2cda-4014-ae79-f236286b312fn%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/CAPq0zEBdp6zguJhr0awrJ2RQPJUFitTYPWQF20Xnpr%2B_zBhqzw%40mail.gmail.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/A6ACF2F1-5BDE-41CA-9B2C-C9685C60B0E9%40btinternet.com.

Re: [weewx-user] Display the first date entry in the database

Hello.
Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now I 
have to format the whole thing so that I can get it into a “normal date”. 
Can anyone else give me help?

steepleian schrieb am Freitag, 16. Februar 2024 um 15:30:43 UTC+1:

> This is what I use which works: -
>
> $alltime.outTemp.firsttime.raw";
>
> Ian
>
> https://claydonsweather.org.uk
>
> On 16 Feb 2024, at 13:43, Tom Keffer  wrote:
>
> 
>
> I haven't tried it, but I don't see why the following wouldn't work:
>
> *$alltime.dateTime.min*
>
> -tk
>
> On Fri, Feb 16, 2024 at 4:59 AM Meteo Oberwallis  
> wrote:
>
>> Hello everyone
>> I would like to display the date of the first entry in the weexs.sdb in 
>> Belchertownskin. The reason for this is that you can see how long the 
>> weather station has been in operation. Since I operate several stations, 
>> this would make my work extremely easier. This could say something like 
>> "Operating since: 10/2023" or something like that. Can someone help me with 
>> that?
>> Thank you and sunny greetings 
>>
>> -- 
>> 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/65e5faa2-2cda-4014-ae79-f236286b312fn%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+...@googlegroups.com.
>
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBdp6zguJhr0awrJ2RQPJUFitTYPWQF20Xnpr%2B_zBhqzw%40mail.gmail.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/ab3cda47-da42-43a2-98bb-388fc12c70cfn%40googlegroups.com.

[weewx-user] Re: weewx 5.02 crashes (and restarts) on trying to access a docker file?

2024-02-16 Thread valken...@gmail.com

Dear Gary,

No apologies needed. You just put me on the right track to solve the issue. 
Actually, there is no explicit need for the cmon plugin on this instance. I 
used the extension to monitor the hardwae when I first installed. However 
it is running whithout major issues for years now, and I didn't realy use 
the cmon extension very often. Anyway, thanks for your further explanation, 
good to know the ignnored_mounts are configurable after all. Maybe others 
can use this information as well.



Op vrijdag 16 februari 2024 om 00:21:30 UTC+1 schreef gjr80:

> Appreciate you have removed cmon and solved the problem; however, in 
> having a more leisurely look at the cmon source I see there already s the 
> ability for the user to add mounts to the ignore list via the 
> ignored_mounts config option. If the ignore list is not specified by the 
> user the default ignore list (hard coded in cmon.py) is used, 
> ignored_mounts is specified then that list is used in lieu of the 
> default. Furthermore, when checking a given mount point against the ignore 
> list, the check used is whether the mount point in question starts with any 
> of the entries in the ignore list. So using '/var/lib/docker' in the 
> ignore list *should* work and cause all docker overlays to be ignored 
> (the source used by cmon as the mount points universe on a system is the 
> contents of /proc/mounts with the mount points being the second entry on 
> each line). For info, the entries in the default ignore list are 
> '/lib/init/rw', 
> '/proc', '/sys', '/dev', '/afs', '/mit', '/run', '/var/lib/nfs'. So 
> something like:
>
> [ComputerMonitor]
> 
> ignored_mounts = 
> '/lib/init/rw', '/proc', '/sys', '/dev', '/afs', '/mit', '/run', 
> '/var/lib/nfs', 
> '/var/lib/docker'
>
> should work. Note, the apostrophes should not be required but leaving them 
> in won't hurt.
>
> My apologies for the earlier mis-information.
>
> Gary
>
> On Thursday 15 February 2024 at 22:47:17 UTC+10 valken...@gmail.com wrote:
>
>> Thanx Gary!
>> It didn't cross my mind that cmon scans for mounted file systems. I added 
>> /var/lib/docker/overlay2 to the ignore list, but the error persisted. To 
>> save me from further troubles I just removed the cmon extension for the 
>> time being. I will inform Matthew.
>>
>> Op donderdag 15 februari 2024 om 02:03:10 UTC+1 schreef gjr80:
>>
>>> Correct. Cmon will try to scan all mounted file systems except for those 
>>> in an ignore list. Problem is the ignore list is not user configurable via 
>>> a config file, rather it is hard coded in cmon.py. You have a few 
>>> options; (1) raise an issue against the weewx-cmon repo and ask for Matthew 
>>> to make the ignore list user configurable, (2) drop cmon from your system 
>>> or (3) manually change the ignore list in cmon.py to exclude your 
>>> docker overlays. I'd suggest a combination of (3) and (1).
>>>
>>> Have a look at line 266 in cmon.py 
>>> ,
>>>  
>>> just add your docker overlay to the list. Not sure you can add one wildcard 
>>> entry for all docker overlays but a bit of experimentation will get you 
>>> there. 
>>>
>>> Gary
>>>
>>> And do raise an issue for when Matthew does get some time for cmon.  
>>>
>>> On Thursday 15 February 2024 at 02:14:31 UTC+10 valken...@gmail.com 
>>> wrote:
>>>
 Since upgrading to weewx 5.02 on ubuntue 22.04, deb instaal. I had some 
 issues becuase weewx does not run as root user anymore. Most of the were 
 easy to solve. However on this ubuntu also a docker instance is running 
 for 
 another application. 
 My syslog now tells me this:

 INFO weewx.engine: Main loop exiting. Shutting engine down.
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: INFO weewx.engine: 
 Shutting down StdReport thread
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: Caught 
 OSError: [Errno 13] Toegang geweigerd: 
 '/var/lib/docker/overlay2/f40006ded3b1ca4e49c40cb408c89374b8b4a067f4de13711cf4be188137d355/merged'
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
   Traceback (most recent call last):
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 210, in run
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
   self.dispatchEvent(weewx.Event(weewx.CHECK_LOOP, packet=packet))
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
   callback(event)
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__: 
 File "/usr/share/weewx/weewx/engine.py", line 660, in check_loop
 Feb 14 16:55:15 kwsweerstation weewxd[9005]: CRITICAL __main__:

Re: [weewx-user] Display the first date entry in the database

On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis 
wrote:

> Hello.
> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now I
> have to format the whole thing so that I can get it into a “normal date”.
> Can anyone else give me help?
>


*$alltime.dateTime.mintime*

-- 
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/CAPq0zEA8K3NG-OTeLFi5LEOya%3DoUnN0909CPREXFo-t4QOy0xQ%40mail.gmail.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

I have used this

sudo usermod -aG dialout weewx
sudo systemctl restart weewx

Weewx is running but there is another authorization problem


Feb 16 16:10:27 Wetter-Raspi4 weewxd[440995]: DEBUG user.rainrate: 
new_loop(1708096227): Added/updated pkt[rainRate] of 0.00
Feb 16 16:10:27 Wetter-Raspi4 weewxd[440995]: DEBUG user.sunduration: 
Calculated LOOP sunshine_time = 2.00, based on radiation = 90.00, 
and threshold = 144.382899
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: DEBUG weewx.manager: Daily 
summary version is 4.0
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
Caught unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  [Errno 13] Keine Berechtigung: '/var/www/html/weewx/json/24h.json'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  Traceback (most recent call last):
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 220, in run
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  obj.start()
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 409, in 
start
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  self.run()
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
File "/etc/weewx/bin/user/belchertown.py", line 2817, in run
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: Traceback (most recent call 
last):
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
"/usr/share/weewx/weewx/reportengine.py", line 220, in run
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: obj.start()
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
"/usr/share/weewx/weewx/reportengine.py", line 409, in start
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: self.run()
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
"/etc/weewx/bin/user/belchertown.py", line 2817, in run
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: with open(json_filename, 
mode="w") as jf:
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] 
Keine Berechtigung: '/var/www/html/weewx/json/24h.json'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  with open(json_filename, mode="w") as jf:
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  PermissionError: [Errno 13] Keine Berechtigung: 
'/var/www/html/weewx/json/24h.json'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  Generator terminated


and
sudo wee_reports
sudo: wee_reports: Befehl nicht gefunden



matthew wall schrieb am Freitag, 16. Februar 2024 um 14:44:24 UTC+1:

> On Friday, February 16, 2024 at 7:57:08 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> where can i see which user starts weewxd?
>
>
> if weewxd is running, do this:
>
> ps aux | grep weewxd
>
> the first word is the user running weewxd
>
> if weewxd is not running, then check the value for 'User' in the systemd 
> unit file
>
> # if you installed using DEB/RPM:
> grep User /usr/lib/systemd/system/weewx.service
>
> # if you installed using pip:
> grep User /etc/systemd/system/weewx.service
>
> 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/08e0f5f5-1e00-4406-9c8a-da84a19e168dn%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

Hello Tom.

It`s not working

Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  Ignoring template 
/etc/weewx/skins/Belchertown/about/index.html.tmpl
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  Reason: cannot find 'mintime' while searching 
for 'alltime.dateTime.mintime  e'
Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR 
weewx.cheetahgenerator:  To debug, try inserting '#errorCatcher Echo' 
at top of template
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO 
weewx.cheetahgenerator: Generated 11 files for report Belchertown in 13.56 
seconds
Feb 16 16:14:32 wetterstation wee_reports[11564] INFO weewx.reportengine: 
Copied 39 files to /var/www/html/weewx/user


Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:

> On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis  
> wrote:
>
>> Hello.
>> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now 
>> I have to format the whole thing so that I can get it into a “normal date”. 
>> Can anyone else give me help?
>>
>
>
> *$alltime.dateTime.mintime*
>
>
>
>

-- 
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/930e7c83-39cd-4e8c-aa5d-07090aad8aedn%40googlegroups.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread 'michael.k...@gmx.at' via weewx-user

The user which ist running weewxd has no permission to generate/modify the 
resource  "/var/www/html/weewx/json/24h.json"

Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  [Errno 13] Keine Berechtigung: '/var/www/html/weewx/json/24h.json'


geni08...@gmail.com schrieb am Freitag, 16. Februar 2024 um 16:13:19 UTC+1:

> I have used this
>
> sudo usermod -aG dialout weewx
> sudo systemctl restart weewx
>
> Weewx is running but there is another authorization problem
>
>
> Feb 16 16:10:27 Wetter-Raspi4 weewxd[440995]: DEBUG user.rainrate: 
> new_loop(1708096227): Added/updated pkt[rainRate] of 0.00
> Feb 16 16:10:27 Wetter-Raspi4 weewxd[440995]: DEBUG user.sunduration: 
> Calculated LOOP sunshine_time = 2.00, based on radiation = 90.00, 
> and threshold = 144.382899
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: DEBUG weewx.manager: Daily 
> summary version is 4.0
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
> Caught unrecoverable exception in generator 
> 'user.belchertown.HighchartsJsonGenerator'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     [Errno 13] Keine Berechtigung: 
> '/var/www/html/weewx/json/24h.json'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     Traceback (most recent call last):
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/reportengine.py", line 220, in 
> run
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     obj.start()
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>   File "/usr/share/weewx/weewx/reportengine.py", line 409, in 
> start
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     self.run()
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>   File "/etc/weewx/bin/user/belchertown.py", line 2817, in run
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: Traceback (most recent call 
> last):
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 220, in run
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: obj.start()
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
> "/usr/share/weewx/weewx/reportengine.py", line 409, in start
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: self.run()
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]:   File 
> "/etc/weewx/bin/user/belchertown.py", line 2817, in run
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: with open(json_filename, 
> mode="w") as jf:
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] 
> Keine Berechtigung: '/var/www/html/weewx/json/24h.json'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     with open(json_filename, mode="w") as jf:
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     PermissionError: [Errno 13] Keine Berechtigung: 
> '/var/www/html/weewx/json/24h.json'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     Generator terminated
>
>
> and
> sudo wee_reports
> sudo: wee_reports: Befehl nicht gefunden
>
>
>
> matthew wall schrieb am Freitag, 16. Februar 2024 um 14:44:24 UTC+1:
>
>> On Friday, February 16, 2024 at 7:57:08 AM UTC-5 geni08...@gmail.com 
>> wrote:
>>
>> where can i see which user starts weewxd?
>>
>>
>> if weewxd is running, do this:
>>
>> ps aux | grep weewxd
>>
>> the first word is the user running weewxd
>>
>> if weewxd is not running, then check the value for 'User' in the systemd 
>> unit file
>>
>> # if you installed using DEB/RPM:
>> grep User /usr/lib/systemd/system/weewx.service
>>
>> # if you installed using pip:
>> grep User /etc/systemd/system/weewx.service
>>
>> 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/6582ee5e-b2d7-4369-bd96-60aed3c045e7n%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

This works

$alltime.outTemp.firsttime 

This is the Result: 01.02.2017 00:01:00 

@steepleian: Thanks 
Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:

> On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis  
> wrote:
>
>> Hello.
>> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now 
>> I have to format the whole thing so that I can get it into a “normal date”. 
>> Can anyone else give me help?
>>
>
>
> *$alltime.dateTime.mintime*
>
>
>
>

-- 
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/1de93286-6d9d-4ff7-b507-c5e144ad3170n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

2024-02-16 Thread matthew wall

On Friday, February 16, 2024 at 10:13:19 AM UTC-5 geni08...@gmail.com wrote:

Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] 
Keine Berechtigung: '/var/www/html/weewx/json/24h.json'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  with open(json_filename, mode="w") as jf:
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  PermissionError: [Errno 13] Keine Berechtigung: 
'/var/www/html/weewx/json/24h.json'
Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine: 
  Generator terminated


https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-file-permissions

 

sudo wee_reports
sudo: wee_reports: Befehl nicht gefunden


in WeeWX v5, the tool "wee_reports" has been replaced by "weectl report"

-- 
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/e83f2f17-f6dd-4e32-b997-6af04225cde1n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade to 5.0.x does not start

Thank you very much, everything seems to be working

matthew wall schrieb am Freitag, 16. Februar 2024 um 16:35:20 UTC+1:

> On Friday, February 16, 2024 at 10:13:19 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: PermissionError: [Errno 13] 
> Keine Berechtigung: '/var/www/html/weewx/json/24h.json'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     with open(json_filename, mode="w") as jf:
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     PermissionError: [Errno 13] Keine Berechtigung: 
> '/var/www/html/weewx/json/24h.json'
> Feb 16 16:10:28 Wetter-Raspi4 weewxd[440995]: ERROR weewx.reportengine:   
>     Generator terminated
>
>
>
> https://github.com/weewx/weewx/wiki/Understanding-permissions#how-to-fix-file-permissions
>
>  
>
> sudo wee_reports
> sudo: wee_reports: Befehl nicht gefunden
>
>
> in WeeWX v5, the tool "wee_reports" has been replaced by "weectl report"
>
>

-- 
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/75415e38-8ea0-44d0-83a2-c192a688300an%40googlegroups.com.

Re: [weewx-user] Display the first date entry in the database

Not sure why that doesn't work --- I'll have to investigate.

But, the sure fire way to do this is with

*$alltime.start*

See the section *start, end, and dateTime
*
.


On Fri, Feb 16, 2024 at 7:16 AM Meteo Oberwallis 
wrote:

> Hello Tom.
>
> It`s not working
>
> Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR
> weewx.cheetahgenerator:  Ignoring template
> /etc/weewx/skins/Belchertown/about/index.html.tmpl
> Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR
> weewx.cheetahgenerator:  Reason: cannot find 'mintime' while searching
> for 'alltime.dateTime.mintime  e'
> Feb 16 16:14:28 wetterstation wee_reports[11564] ERROR
> weewx.cheetahgenerator:  To debug, try inserting '#errorCatcher Echo'
> at top of template
> Feb 16 16:14:32 wetterstation wee_reports[11564] INFO
> weewx.cheetahgenerator: Generated 11 files for report Belchertown in 13.56
> seconds
> Feb 16 16:14:32 wetterstation wee_reports[11564] INFO weewx.reportengine:
> Copied 39 files to /var/www/html/weewx/user
>
>
> Tom Keffer schrieb am Freitag, 16. Februar 2024 um 16:12:14 UTC+1:
>
>> On Fri, Feb 16, 2024 at 6:37 AM Meteo Oberwallis 
>> wrote:
>>
>>> Hello.
>>> Thank you for the answers. The $alltime.outTemp.firsttime.raw works. Now
>>> I have to format the whole thing so that I can get it into a “normal date”.
>>> Can anyone else give me help?
>>>
>>
>>
>> *$alltime.dateTime.mintime*
>>
>>
>>
>> --
> 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/930e7c83-39cd-4e8c-aa5d-07090aad8aedn%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/CAPq0zEBPS9AgaLZ%3DvMJZAWA-LKhv_dMWiS5bdG%3DMC5wgsts7hQ%40mail.gmail.com.

[weewx-user] as3935 lightining module not detected by I2c on a Rpi4

2024-02-16 Thread Pierre-Yves

Hello All,

Maybe a bit off-topic. But just in case someone would have faced to this 
strange behavior of a Raspberry i2c address map.


Rpi4-1: usual address map from 0x03 to 7x76.
Config.:
Weewx 4.10.2,
Bresser 7in1,
sdr driver,
RTC clock (UU),
BME280 (0x76) (pressure, temperature, humidity)
AS3935 (0x03) (lightning detector)

Weewx on Rpi4-1 running without any error.

pi@weewx:~ $ sudo i2cdetect -y 1
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:  03 -- -- -- -- -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- 76 -- 
pi@weewx:~ $ 

Rpi4-2: "abnormal" map with addresses 0x03 to 0x07 non selectable.
Config.:
Weewx 5.0.2,
Bresser 7in1,
RTC clock (UU),
AS3935 (??)

Weewx on Rpi4-2 failing : File "/etc/weewx/bin/user/as3935.py", line 182, 
in __init__GPIO.setup(self.pin, GPIO.IN (see log below)

pi@raspberrypi:~ $ sudo i2cdetect -y 1
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: -- -- -- -- -- -- -- -- 
10: -- -- -- -- -- -- -- -- -- -- 1a -- -- -- -- -- 
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 
70: -- -- -- -- -- -- -- -- 
pi@raspberrypi:~ $

Clearly, the AS3935 is not identified because the 0x03 to 0x07 address 
range is not active. This AS3935 module works on the Rpi4-1

Any idea on where this problem of misconfiguration could come from, 
firmware, kernel ?
Is there a way to reset the I2c address map ? 

Thanks,

Pierre-Yves

-- 
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/84bae39e-6dc2-4efa-b6c5-a8d87d03e1bfn%40googlegroups.com.


I2c-address-map-bug-log
Description: Binary data

Re: [weewx-user] Display the first date entry in the database