Re: [weewx-user] Sunshine Duration

[geni08...@gmail.com]

I can't find “is_sunshine” in the MQTT stream.
I have replaced the “sunduration.py” and restarted weewx
Do I have to enter this somewhere?

Jacques Terrettaz schrieb am Donnerstag, 2. Mai 2024 um 18:05:49 UTC+2:

I have added a new field in my extension : *is_sunshine*

At each record generation,, the *is_sunshine* value will be 1 if there is 
sunshine, otherwise it will be 0.
This field is also published in the MQTT stream.

See https://github.com/Jterrettaz/sunduration/tree/master


Le 2 mai 2024 à 14:54, geni08...@gmail.com  a écrit :

I would like to get the attribute sunshine yes/no or a value in the MQTT 
stream to control my shutters if I already have a Davis Pro.
I can only find the value of "maxSolarRad_Wpm2". Please give me some advice 
on how I could evaluate this, or how could the sunshine value per minute be 
entered in MQTT?


-- 
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/25b158d2-31c2-4713-b43c-ce355343db99n%40googlegroups.com.

Re: [weewx-user] Sunshine Duration

[geni08...@gmail.com]

I would like to get the attribute sunshine yes/no or a value in the MQTT 
stream to control my shutters if I already have a Davis Pro.
I can only find the value of "maxSolarRad_Wpm2". Please give me some advice 
on how I could evaluate this, or how could the sunshine value per minute be 
entered in MQTT?

Karen K schrieb am Donnerstag, 2. Mai 2024 um 09:03:15 UTC+2:

> n7uv...@gmail.com schrieb am Donnerstag, 2. Mai 2024 um 01:01:52 UTC+2:
>
> When I hear "sunshine duration", I'm not sure whether that means the 
> duration that the scary fiery (I live in PHX %^) ball of plasma is at and 
> above the horizon (which is already provided under the Celestial tab) 
> [image: Screenshot 2024-05-01 155959.png]
> or something about the total energy delivered to a square meter of the 
> ground over the period of a day. 
>
>
> Sunshine duration means the time the sun is really seen in the sky and 
> typically casts a shadow. The standard instrument to measure sunshine 
> duration is the Campbell-Stokes sunshine recorder 
> . 
>
> Sunshine duration is *not* total daylight time.
>
> If a cloud is situated before the sun, this is considered no sunshine. If 
> clouds are elsewhere in the sky it does not matter.
>
>

-- 
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/c9afdf60-3529-4502-a8d2-558bf975cca2n%40googlegroups.com.

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

[geni08...@gmail.com]

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] Re: Upgrade to 5.0.x does not start

[geni08...@gmail.com]

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] Re: Upgrade to 5.0.x does not start

[geni08...@gmail.com]

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.

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

[geni08...@gmail.com]

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

[geni08...@gmail.com]

tc/weewx/skins/Rsync« kann nicht 
gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Mobile/lang« kann nicht 
gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Mobile« kann nicht 
gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins/Ftp« kann nicht gelöscht 
werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/skins« kann nicht gelöscht 
werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/scripts« kann nicht gelöscht 
werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/apache/conf.d« kann nicht 
gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/apache/conf-available« kann 
nicht gelöscht werden: Das Verzeichnis ist nicht leer
dpkg: Warnung: Altes Verzeichnis »/etc/weewx/apache« kann nicht gelöscht 
werden: Das Verzeichnis ist nicht leer
weewx (5.0.2-1) wird eingerichtet ...
Neue Version der Konfigurationsdatei /etc/weewx/import/csv-example.conf 
wird installiert ...
Neue Version der Konfigurationsdatei /etc/weewx/import/cumulus-example.conf 
wird installiert ...
Neue Version der Konfigurationsdatei /etc/weewx/import/wd-example.conf wird 
installiert ...
Neue Version der Konfigurationsdatei 
/etc/weewx/import/weathercat-example.conf wird installiert ...
Neue Version der Konfigurationsdatei /etc/weewx/import/wu-example.conf wird 
installiert ...
Neue Version der Konfigurationsdatei /etc/weewx/logrotate.d/weewx wird 
installiert ...
Neue Version der Konfigurationsdatei /etc/weewx/rsyslog.d/weewx.conf wird 
installiert ...

Konfigurationsdatei »/etc/weewx/weewx.conf«
 ==> Geändert (von Ihnen oder von einem Skript) seit der Installation.
 ==> Paketverteiler hat eine aktualisierte Version herausgegeben.
   Wie möchten Sie vorgehen? Ihre Wahlmöglichkeiten sind:
Y oder I : Die Version des Paket-Betreuers installieren
N oder O : Die momentan installierte Version beibehalten
   D : Die Unterschiede zwischen den Versionen anzeigen
   Z : Eine Shell starten, um die Situation zu begutachten
 Der Standardweg ist das Beibehalten der momentanen Version.
*** weewx.conf (Y/I/N/O/D/Z) [Vorgabe=N] ? y
Neue Version der Konfigurationsdatei /etc/weewx/weewx.conf wird installiert 
...
Using weewx:weewx as user:group
Saving old defaults to /etc/default/weewx-20240212181854
Creating /etc/default/weewx
Using debconf configuration values from previous install
Using configuration file /etc/weewx/weewx.conf
Processing configuration file /etc/weewx/weewx.conf
Saving configuration file /etc/weewx/weewx.conf
Migrating old extensions to /etc/weewx/bin/user
Saving old extensions to /usr/share/weewx/user-20240212181854
Adding system group weewx...done
Adding system user weewx...done
Adding user pi to group weewx
Installing systemd units
Installing udev rules
Configuring database directory /var/lib/weewx
Configuring reporting directory /var/www/html/weewx
Setting permissions weewx:weewx on /etc/weewx
Enabling startup using systemd
Synchronizing state of weewx.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable weewx
Created symlink /etc/systemd/system/multi-user.target.wants/weewx.service → 
/lib/systemd/system/weewx.service.
Starting weewxd using systemd
The following files might interfere with the init configuration:
  /etc/init.d/weewx

Tom Keffer schrieb am Montag, 12. Februar 2024 um 18:07:14 UTC+1:

> It would be easiest if you just followed the directions in the Debian 
> quick start guide <https://www.weewx.com/docs/5.0/quickstarts/debian/> 
> again. It will cause the correct line to be put in /etc/apt/sources.list.d
>
> -tk
>
> On Mon, Feb 12, 2024 at 9:00 AM geni08...@gmail.com  
> wrote:
>
>> @vince
>> Which line should I uncomment in which file
>>
>> vince schrieb am Montag, 12. Februar 2024 um 17:49:04 UTC+1:
>>
>>> Uncomment that line in the file
>>>
>>> On Monday, February 12, 2024 at 6:53:19 AM UTC-8 geni08...@gmail.com 
>>> wrote:
>>>
>>>> How can I fix this?
>>>>
>>>> gary@gmail.com schrieb am Montag, 12. Februar 2024 um 15:21:08 
>>>> UTC+1:
>>>>
>>>>> Your weewx repository has been disabled.
>>>>> I'd remove the entry and re-create it. From what I've read, you may 
>>>>> need to get the signing keys as well.
>>>>>
>>>>> On Monday, February 12, 2024 at 9:01:52 AM UTC-5 geni08...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> # deb [arch=all] http://weewx.com/apt/python3 buster main # disabled 
>>>>>> on upgrade to jammy
>>>>&g

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

[geni08...@gmail.com]

@vince
Which line should I uncomment in which file

vince schrieb am Montag, 12. Februar 2024 um 17:49:04 UTC+1:

> Uncomment that line in the file
>
> On Monday, February 12, 2024 at 6:53:19 AM UTC-8 geni08...@gmail.com 
> wrote:
>
>> How can I fix this?
>>
>> gary@gmail.com schrieb am Montag, 12. Februar 2024 um 15:21:08 UTC+1:
>>
>>> Your weewx repository has been disabled.
>>> I'd remove the entry and re-create it. From what I've read, you may need 
>>> to get the signing keys as well.
>>>
>>> On Monday, February 12, 2024 at 9:01:52 AM UTC-5 geni08...@gmail.com 
>>> wrote:
>>>
>>>> # deb [arch=all] http://weewx.com/apt/python3 buster main # disabled 
>>>> on upgrade to jammy
>>>> and
>>>> Paketdateien:
>>>>  100 /var/lib/dpkg/status
>>>>  release a=now
>>>>  500 http://archive.raspberrypi.org/debian bullseye/main armhf Packages
>>>>  release o=Raspberry Pi 
>>>> Foundation,a=oldstable,n=bullseye,l=Raspberry Pi Foundation,c=main,b=armhf
>>>>  origin archive.raspberrypi.org
>>>>  500 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages
>>>>  release o=Raspberry Pi 
>>>> Foundation,a=oldstable,n=bullseye,l=Raspberry Pi Foundation,c=main,b=arm64
>>>>  origin archive.raspberrypi.org
>>>>  500 http://deb.debian.org/debian bullseye-updates/main armhf Packages
>>>>  release 
>>>> v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=armhf
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye-updates/main arm64 Packages
>>>>  release 
>>>> v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=arm64
>>>>  origin deb.debian.org
>>>>  500 http://security.debian.org/debian-security bullseye-security/main 
>>>> armhf Packages
>>>>  release 
>>>> v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=armhf
>>>>  origin security.debian.org
>>>>  500 http://security.debian.org/debian-security bullseye-security/main 
>>>> arm64 Packages
>>>>  release 
>>>> v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=arm64
>>>>  origin security.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/non-free armhf Packages
>>>>  release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=armhf
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/non-free arm64 Packages
>>>>  release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=arm64
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/contrib armhf Packages
>>>>  release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=armhf
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/contrib arm64 Packages
>>>>      release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=arm64
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/main armhf Packages
>>>>  release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=armhf
>>>>  origin deb.debian.org
>>>>  500 http://deb.debian.org/debian bullseye/main arm64 Packages
>>>>  release 
>>>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=arm64
>>>>  origin deb.debian.org
>>>> Mit Pinning verwaltete Pakete:
>>>> matthew wall schrieb am Montag, 12. Februar 2024 um 13:25:03 UTC+1:
>>>>
>>>>> On Monday, February 12, 2024 at 3:35:38 AM UTC-5 geni08...@gmail.com 
>>>>> wrote:
>>>>>
>>>>> PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
>>>>>
>>>>>
>>>>> good! and what is the content of weewx.list?
>>>>>
>>>>> cat /etc/apt/sources.list.d/weewx.list
>>>>>
>>>>>  and what is the upgrade/update policy for yoiur machine?
>>>>>
>>>>> apt-cache policy
>>>>>
>>>>>

-- 
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/52f1d268-f38d-41d6-a387-b679f29e881an%40googlegroups.com.

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

[geni08...@gmail.com]

How can I fix this?

gary@gmail.com schrieb am Montag, 12. Februar 2024 um 15:21:08 UTC+1:

> Your weewx repository has been disabled.
> I'd remove the entry and re-create it. From what I've read, you may need 
> to get the signing keys as well.
>
> On Monday, February 12, 2024 at 9:01:52 AM UTC-5 geni08...@gmail.com 
> wrote:
>
>> # deb [arch=all] http://weewx.com/apt/python3 buster main # disabled on 
>> upgrade to jammy
>> and
>> Paketdateien:
>>  100 /var/lib/dpkg/status
>>  release a=now
>>  500 http://archive.raspberrypi.org/debian bullseye/main armhf Packages
>>  release o=Raspberry Pi Foundation,a=oldstable,n=bullseye,l=Raspberry 
>> Pi Foundation,c=main,b=armhf
>>  origin archive.raspberrypi.org
>>  500 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages
>>  release o=Raspberry Pi Foundation,a=oldstable,n=bullseye,l=Raspberry 
>> Pi Foundation,c=main,b=arm64
>>  origin archive.raspberrypi.org
>>  500 http://deb.debian.org/debian bullseye-updates/main armhf Packages
>>  release 
>> v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=armhf
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye-updates/main arm64 Packages
>>  release 
>> v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=arm64
>>  origin deb.debian.org
>>  500 http://security.debian.org/debian-security bullseye-security/main 
>> armhf Packages
>>  release 
>> v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=armhf
>>  origin security.debian.org
>>  500 http://security.debian.org/debian-security bullseye-security/main 
>> arm64 Packages
>>  release 
>> v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=arm64
>>  origin security.debian.org
>>  500 http://deb.debian.org/debian bullseye/non-free armhf Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=armhf
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye/non-free arm64 Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=arm64
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye/contrib armhf Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=armhf
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye/contrib arm64 Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=arm64
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye/main armhf Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=armhf
>>  origin deb.debian.org
>>  500 http://deb.debian.org/debian bullseye/main arm64 Packages
>>  release 
>> v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=arm64
>>  origin deb.debian.org
>> Mit Pinning verwaltete Pakete:
>> matthew wall schrieb am Montag, 12. Februar 2024 um 13:25:03 UTC+1:
>>
>>> On Monday, February 12, 2024 at 3:35:38 AM UTC-5 geni08...@gmail.com 
>>> wrote:
>>>
>>> PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
>>>
>>>
>>> good! and what is the content of weewx.list?
>>>
>>> cat /etc/apt/sources.list.d/weewx.list
>>>
>>>  and what is the upgrade/update policy for yoiur machine?
>>>
>>> apt-cache policy
>>>
>>>

-- 
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/6b9f5206-a5f5-40d2-97eb-fc8307558c76n%40googlegroups.com.

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

[geni08...@gmail.com]

# deb [arch=all] http://weewx.com/apt/python3 buster main # disabled on 
upgrade to jammy
and
Paketdateien:
 100 /var/lib/dpkg/status
 release a=now
 500 http://archive.raspberrypi.org/debian bullseye/main armhf Packages
 release o=Raspberry Pi Foundation,a=oldstable,n=bullseye,l=Raspberry 
Pi Foundation,c=main,b=armhf
 origin archive.raspberrypi.org
 500 http://archive.raspberrypi.org/debian bullseye/main arm64 Packages
 release o=Raspberry Pi Foundation,a=oldstable,n=bullseye,l=Raspberry 
Pi Foundation,c=main,b=arm64
 origin archive.raspberrypi.org
 500 http://deb.debian.org/debian bullseye-updates/main armhf Packages
 release 
v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=armhf
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye-updates/main arm64 Packages
 release 
v=11-updates,o=Debian,a=oldstable-updates,n=bullseye-updates,l=Debian,c=main,b=arm64
 origin deb.debian.org
 500 http://security.debian.org/debian-security bullseye-security/main 
armhf Packages
 release 
v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=armhf
 origin security.debian.org
 500 http://security.debian.org/debian-security bullseye-security/main 
arm64 Packages
 release 
v=11,o=Debian,a=oldstable-security,n=bullseye-security,l=Debian-Security,c=main,b=arm64
 origin security.debian.org
 500 http://deb.debian.org/debian bullseye/non-free armhf Packages
 release 
v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=armhf
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/non-free arm64 Packages
 release 
v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=non-free,b=arm64
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/contrib armhf Packages
 release 
v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=armhf
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/contrib arm64 Packages
 release 
v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=contrib,b=arm64
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/main armhf Packages
 release v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=armhf
 origin deb.debian.org
 500 http://deb.debian.org/debian bullseye/main arm64 Packages
 release v=11.9,o=Debian,a=oldstable,n=bullseye,l=Debian,c=main,b=arm64
 origin deb.debian.org
Mit Pinning verwaltete Pakete:
matthew wall schrieb am Montag, 12. Februar 2024 um 13:25:03 UTC+1:

> On Monday, February 12, 2024 at 3:35:38 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
>
>
> good! and what is the content of weewx.list?
>
> cat /etc/apt/sources.list.d/weewx.list
>
>  and what is the upgrade/update policy for yoiur machine?
>
> apt-cache policy
>
>

-- 
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/aa021222-1a43-470b-98ed-d2bca68faacfn%40googlegroups.com.

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

[geni08...@gmail.com]

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/";
SUPPORT_URL="https://www.debian.org/support";
BUG_REPORT_URL="https://bugs.debian.org/";


matthew wall schrieb am Sonntag, 11. Februar 2024 um 18:34:03 UTC+1:

> On Sunday, February 11, 2024 at 10:59:41 AM UTC-5 geni08...@gmail.com 
> wrote:
>
> weewx ist schon die neueste Version (4.10.2-1).
> 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
>
>
> which operating system are you using?
>
> weewx v5 will install from a debian package only on debian 10 or later.  
> if you are using debian 10 or later, be sure that your apt config 
> (/etc/apt/sources.list.d/weewx.list) refers to python3, not python2.
>
> 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/57bd92ee-f38c-4f7a-9169-7a683e816e48n%40googlegroups.com.

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

[geni08...@gmail.com]

My input on Raspi4

sudo apt update
sudo apt install weewx
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
weewx ist schon die neueste Version (4.10.2-1).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.

What am I doing wrong

-- 
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/8f27377c-590a-443e-9b57-af4ddf82a56fn%40googlegroups.com.

Re: [weewx-user] Re: sudo wee_database --rebuild-daily does not work.

[geni08...@gmail.com]

OK, the correct syntax is:
pi@Wetter-Raspi4:~ $ *sudo wee_database --rebuild-daily --from=2023-04-01 
--to=2023-05-02*
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Daily summaries from 2023-04-01 through 2023-05-02 inclusive will be 
rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx_new' ...
Records processed: 4000; time: 2023-04-28 19:30:00 CEST (1682703000)
Processed 4603 records to rebuild 32 daily summaries in 9.26 seconds
Rebuild of daily summaries in database 'weewx_new' complete
pi@Wetter-Raspi4:~ $ 

many thanks
gjr80 schrieb am Samstag, 6. Mai 2023 um 08:20:50 UTC+2:

> Did you run wee_database --rebuild_daily as suggested by Tom? When 
> running wee_database --rebuild-daily you can use the optional --date by 
> itself to specify a single day, you can use --to by itself to specify a 
> date range from the first record in the database to a give date, you can 
> use --from by itself to specify a date range from a given record through 
> until the last record in the database or you can use --from and --to to 
> specify a date range. You cannot use --date with --to or --date with 
> --from, if you read the error message in you most recent post that is 
> what it is telling you.
>
> Gary
>
> On Saturday, 6 May 2023 at 15:33:34 UTC+10 geni08...@gmail.com wrote:
>
>> sudo wee_database --rebuild-daily was executed after sudo wee_database 
>> --reconfigure.
>>
>> And now this result, is from to not allowed?
>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01 
>> --to=2023-05-02
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_mysql'
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_database", line 1168, in 
>> main()
>>   File "/usr/share/weewx/wee_database", line 247, in main
>> rebuildDaily(config_dict, db_binding, options)
>>   File "/usr/share/weewx/wee_database", line 314, in rebuildDaily
>> from_dt, to_dt = _parse_dates(options)
>>   File "/usr/share/weewx/wee_database", line 1088, in _parse_dates
>> raise ValueError("Specify either --date or a --from and --to 
>> combination; not both")
>> ValueError: Specify either --date or a --from and --to combination; not 
>> both
>> pi@Wetter-Raspi4:~ $ 
>>
>> Tom Keffer schrieb am Samstag, 6. Mai 2023 um 01:56:37 UTC+2:
>>
>>> Sorry. The error description is not the best. What it is saying is that 
>>> you cannot rebuild a single day unless the daily summaries are complete. 
>>> So, you will have to finish rebuilding all the summaries first.
>>>
>>> Try
>>>
>>> *wee_database --rebuild-daily*
>>>
>>>
>>>
>>> On Wed, May 3, 2023 at 4:41 AM geni08...@gmail.com  
>>> wrote:
>>>
>>>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01
>>>> Using configuration file /etc/weewx/weewx.conf
>>>> Using database binding 'wx_binding', which is bound to database 
>>>> 'archive_mysql'
>>>> Daily summary for 2023-04-01 will be rebuilt.
>>>> Proceed (y/n)? y
>>>> Rebuilding daily summaries in database 'weewx_new' ...
>>>> Traceback (most recent call last):
>>>>   File "/usr/share/weewx/wee_database", line 1168, in 
>>>> main()
>>>>   File "/usr/share/weewx/wee_database", line 247, in main
>>>> rebuildDaily(config_dict, db_binding, options)
>>>>   File "/usr/share/weewx/wee_database", line 356, in rebuildDaily
>>>> nrecs, ndays = dbmanager.backfill_day_summary(start_d=from_d,
>>>>   File "/usr/share/weewx/weewx/manager.py", line 1249, in 
>>>> backfill_day_summary
>>>> raise weewx.ViolatedPrecondition("Daily summaries are not complete. 
>>>> "
>>>> weewx.ViolatedPrecondition: Daily summaries are not complete. Try again 
>>>> without from/to dates.
>>>> pi@Wetter-Raspi4:~ $ 
>>>>
>>>>
>>>> geni08...@gmail.com schrieb am Mittwoch, 3. Mai 2023 um 13:34:43 UTC+2:
>>>>
>>>>> Raspi4, weewx 4.10.2, MariaDB 10 on Synology, Belchertown 1.3.1
>>>>>
>>>>> What am I doing wrong?
>>>>>
>>>>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --dry-

Re: [weewx-user] Re: sudo wee_database --rebuild-daily does not work.

[geni08...@gmail.com]

sudo wee_database --rebuild-daily was executed after sudo wee_database 
--reconfigure.

And now this result, is from to not allowed?
pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01 
--to=2023-05-02
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
main()
  File "/usr/share/weewx/wee_database", line 247, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 314, in rebuildDaily
from_dt, to_dt = _parse_dates(options)
  File "/usr/share/weewx/wee_database", line 1088, in _parse_dates
raise ValueError("Specify either --date or a --from and --to 
combination; not both")
ValueError: Specify either --date or a --from and --to combination; not both
pi@Wetter-Raspi4:~ $ 

Tom Keffer schrieb am Samstag, 6. Mai 2023 um 01:56:37 UTC+2:

> Sorry. The error description is not the best. What it is saying is that 
> you cannot rebuild a single day unless the daily summaries are complete. 
> So, you will have to finish rebuilding all the summaries first.
>
> Try
>
> *wee_database --rebuild-daily*
>
>
>
> On Wed, May 3, 2023 at 4:41 AM geni08...@gmail.com  
> wrote:
>
>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01
>> Using configuration file /etc/weewx/weewx.conf
>> Using database binding 'wx_binding', which is bound to database 
>> 'archive_mysql'
>> Daily summary for 2023-04-01 will be rebuilt.
>> Proceed (y/n)? y
>> Rebuilding daily summaries in database 'weewx_new' ...
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_database", line 1168, in 
>> main()
>>   File "/usr/share/weewx/wee_database", line 247, in main
>> rebuildDaily(config_dict, db_binding, options)
>>   File "/usr/share/weewx/wee_database", line 356, in rebuildDaily
>> nrecs, ndays = dbmanager.backfill_day_summary(start_d=from_d,
>>   File "/usr/share/weewx/weewx/manager.py", line 1249, in 
>> backfill_day_summary
>> raise weewx.ViolatedPrecondition("Daily summaries are not complete. "
>> weewx.ViolatedPrecondition: Daily summaries are not complete. Try again 
>> without from/to dates.
>> pi@Wetter-Raspi4:~ $ 
>>
>>
>> geni08...@gmail.com schrieb am Mittwoch, 3. Mai 2023 um 13:34:43 UTC+2:
>>
>>> Raspi4, weewx 4.10.2, MariaDB 10 on Synology, Belchertown 1.3.1
>>>
>>> What am I doing wrong?
>>>
>>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --dry-run
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'archive_mysql'
>>> All daily summaries will be rebuilt.
>>> Proceed (y/n)? y
>>> Rebuilding daily summaries in database 'weewx_new' ...
>>> Dry run. Nothing done.
>>> pi@Wetter-Raspi4:~ $ 
>>>
>>>
>>>
>>> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01 
>>> --to=2023-05-02 --dry-run
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'archive_mysql'
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_database", line 1168, in 
>>> main()
>>>   File "/usr/share/weewx/wee_database", line 247, in main
>>> rebuildDaily(config_dict, db_binding, options)
>>>   File "/usr/share/weewx/wee_database", line 314, in rebuildDaily
>>> from_dt, to_dt = _parse_dates(options)
>>>   File "/usr/share/weewx/wee_database", line 1088, in _parse_dates
>>> raise ValueError("Specify either --date or a --from and --to 
>>> combination; not both")
>>> ValueError: Specify either --date or a --from and --to combination; not 
>>> both
>>> pi@Wetter-Raspi4:~ $ 
>>>
>> -- 
>> 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/489fd6ec-7658-43bc-9a11-91b438901275n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/489fd6ec-7658-43bc-9a11-91b438901275n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/83f8438c-66d7-4309-b89c-56104e6a4d88n%40googlegroups.com.

[weewx-user] Re: sudo wee_database --rebuild-daily does not work.

[geni08...@gmail.com]

pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Daily summary for 2023-04-01 will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx_new' ...
Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
main()
  File "/usr/share/weewx/wee_database", line 247, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 356, in rebuildDaily
nrecs, ndays = dbmanager.backfill_day_summary(start_d=from_d,
  File "/usr/share/weewx/weewx/manager.py", line 1249, in 
backfill_day_summary
raise weewx.ViolatedPrecondition("Daily summaries are not complete. "
weewx.ViolatedPrecondition: Daily summaries are not complete. Try again 
without from/to dates.
pi@Wetter-Raspi4:~ $ 


geni08...@gmail.com schrieb am Mittwoch, 3. Mai 2023 um 13:34:43 UTC+2:

> Raspi4, weewx 4.10.2, MariaDB 10 on Synology, Belchertown 1.3.1
>
> What am I doing wrong?
>
> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --dry-run
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_mysql'
> All daily summaries will be rebuilt.
> Proceed (y/n)? y
> Rebuilding daily summaries in database 'weewx_new' ...
> Dry run. Nothing done.
> pi@Wetter-Raspi4:~ $ 
>
>
>
> pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01 
> --to=2023-05-02 --dry-run
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_mysql'
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_database", line 1168, in 
> main()
>   File "/usr/share/weewx/wee_database", line 247, in main
> rebuildDaily(config_dict, db_binding, options)
>   File "/usr/share/weewx/wee_database", line 314, in rebuildDaily
> from_dt, to_dt = _parse_dates(options)
>   File "/usr/share/weewx/wee_database", line 1088, in _parse_dates
> raise ValueError("Specify either --date or a --from and --to 
> combination; not both")
> ValueError: Specify either --date or a --from and --to combination; not 
> both
> pi@Wetter-Raspi4:~ $ 
>

-- 
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/489fd6ec-7658-43bc-9a11-91b438901275n%40googlegroups.com.

[weewx-user] sudo wee_database --rebuild-daily does not work.

[geni08...@gmail.com]

Raspi4, weewx 4.10.2, MariaDB 10 on Synology, Belchertown 1.3.1

What am I doing wrong?

pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --dry-run
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
All daily summaries will be rebuilt.
Proceed (y/n)? y
Rebuilding daily summaries in database 'weewx_new' ...
Dry run. Nothing done.
pi@Wetter-Raspi4:~ $ 



pi@Wetter-Raspi4:~ $ sudo wee_database --rebuild-daily --date=2023-04-01 
--to=2023-05-02 --dry-run
Using configuration file /etc/weewx/weewx.conf
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
Traceback (most recent call last):
  File "/usr/share/weewx/wee_database", line 1168, in 
main()
  File "/usr/share/weewx/wee_database", line 247, in main
rebuildDaily(config_dict, db_binding, options)
  File "/usr/share/weewx/wee_database", line 314, in rebuildDaily
from_dt, to_dt = _parse_dates(options)
  File "/usr/share/weewx/wee_database", line 1088, in _parse_dates
raise ValueError("Specify either --date or a --from and --to 
combination; not both")
ValueError: Specify either --date or a --from and --to combination; not both
pi@Wetter-Raspi4:~ $ 

-- 
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/d4de1516-3be1-4ad7-8999-2d5c9d93de4an%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?
[image: weewx2.jpg]

Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/7cbf95ff-94cd-46ba-bc9f-ee437bffe703n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?
[image: weewx2.jpg]

Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/76486108-6fe0-49a1-b53a-01a736896fcen%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?

Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/7aeca426-50bd-4570-b7b2-ac672dd41ef1n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line


Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/2e4f52f3-e758-4253-9d7e-127f612699b4n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?
[image: weewx2.jpg]
Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/b4188469-7e6d-49b6-97ae-f466bf147185n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?[image: 
weewx2.jpg]

Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/54966989-759c-468f-819e-85ff2e6d3ce5n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, but where does the label text come from? 
 [image: weewx2.jpg]This setting causes the error message:

Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/dc53d0bb-7d6d-4996-b486-6dfaed605884n%40googlegroups.com.

Re: [weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

This graphic definition causes the error

[month]
# Chart Timespan Defaults
title = Letzte 30 Tage
show_button = true
button_text = Letzte 30 Tage
type = spline
time_length = month_ago_to_now
time_ago = 1
tooltip_date_format = ""
aggregate_type = max
aggregate_interval = 3600 # 1 hour
gapsize = 86400  # 1 day in seconds

[[chart1]]
title = Temperatur
[[[outTemp]]]
zIndex = 1
name = Temperatur
[[[appTemp]]]
name = "Gefühlte Temperatur"
[[[dewpoint]]]
name = "Taupunkt"
color = "#8085e8"
type = line

This graphic is generated, where does the label text come from?
[image: weewx2.jpg]
Tom Keffer schrieb am Donnerstag, 30. März 2023 um 02:06:17 UTC+2:

> I can't be sure, but I suspect the Belchertown skin fell victim to this 
> issue: https://github.com/weewx/weewx/issues/436
>
> On Wed, Mar 29, 2023 at 8:37 AM geni08...@gmail.com  
> wrote:
>
>> I see this error since today!
>>
>> Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 
>> 1.3
>> Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
>> forecast file downloaded to /home/nfs/wetter/json/forecast.json
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'user.belchertown.HighchartsJsonGenerator'
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Traceback (most recent call last):
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     obj.start()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     self.run()
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/user/belchertown.py", line 2517, in run
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     minstamp, maxstamp = archiveSpanSpan(
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
>> archiveSpanSpan
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     start_dt = time_dt.replace(year=year, month=month)
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     ValueError: day is out of range for month
>> Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine:   
>>     Generator terminated
>>
>>
>> -- 
>> 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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/6dde821e-d161-4d0e-b5ef-e0d89d262bb5n%40googlegroups.com.

[weewx-user] Error since 29.03 at 00:01

[geni08...@gmail.com]

I see this error since today!

Mar 29 17:00:28 Wetter-Raspi4 weewx[629] INFO user.belchertown: version 1.3
Mar 29 17:00:29 Wetter-Raspi4 weewx[629] INFO user.belchertown: New 
forecast file downloaded to /home/nfs/wetter/json/forecast.json
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'user.belchertown.HighchartsJsonGenerator'
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  day is out of range for month
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 197, in run
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  obj.start()
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 385, in start
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  self.run()
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
File "/usr/share/weewx/user/belchertown.py", line 2517, in run
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  minstamp, maxstamp = archiveSpanSpan(
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
File "/usr/share/weewx/weeutil/weeutil.py", line 341, in 
archiveSpanSpan
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  start_dt = time_dt.replace(year=year, month=month)
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  ValueError: day is out of range for month
Mar 29 17:00:37 Wetter-Raspi4 weewx[629] ERROR weewx.reportengine: 
  Generator terminated


-- 
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/f3f788e0-7a80-4c3a-920b-5cf673fef580n%40googlegroups.com.

[weewx-user] Re: No display of ISS Receive Stats data

[geni08...@gmail.com]

I have found the error:
there was software defined and so it doesn't work, once hardware is defined 
it's OK.

correct
[StdArchive]
record_generation = hardware


gjr80 schrieb am Mittwoch, 15. März 2023 um 21:12:39 UTC+1:

> I suggest the first step is to run WeeWX directly 
> <http://weewx.com/docs/usersguide.htm#Running_directly> to see exactly 
> what is being included in the archive records. When run directly WeeWX will 
> display loop packets (LOOP:) and archive records (REC:) to the console. 
> rxCheckPrecent will (should) appear in archive records only. Let WeeWX 
> run for at least a couple of archive periods to ensure you see at least one 
> archive record and then post the entire console output here. 
>
> Gary
> On Thursday, 16 March 2023 at 02:14:33 UTC+10 geni08...@gmail.com wrote:
>
>> no rxCheckPercent data is read and written to the database. But on the 
>> Davis Console the diagnostic screen shows a quality of 100%?
>> Where do I have to look further?
>> Any hints would be most welcome!
>> Geni
>
>

-- 
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/4451b9d8-b79c-4a71-a3c8-799f3c30da2en%40googlegroups.com.

Re: [weewx-user] Re: Questions about weewx-loopdata 2.x

[geni08...@gmail.com]

 week_start = 0

jo...@johnkline.com schrieb am Dienstag, 11. August 2020 um 16:08:18 UTC+2:

> When does your week start?
>
> You should see something like this is weewx.conf:
> # Start of week (0=Monday, 6=Sunday)
> week_start = 6
>
> What value do you have for week_start?
>
> On Aug 11, 2020, at 3:20 AM, geni08...@gmail.com  
> wrote:
>
> I found a syntax.
>
>
> Question: for example "Hi Out Temp, week", shouldn't it be the highest 
> temp since Monday? But this is not true for me! Why?
>
> geni08...@gmail.com schrieb am Dienstag, 11. August 2020 um 10:57:03 
> UTC+2:
>
>> @John: I installed version 2.6.
>> how do i get the values:
>> > style='white-space:pre;'>
>> > style='white-space:pre;'>
>> > style='white-space:pre;'>
>> > style='white-space:pre;'>
>> > style='white-space:pre;'>
>
> -- 
> 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/282de9d8-ff84-4c29-b302-2893aded408fn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/282de9d8-ff84-4c29-b302-2893aded408fn%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
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/40bdd07b-16f1-4413-b532-05222b4a8b5en%40googlegroups.com.

Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[geni08...@gmail.com]

pi@raspberrypi:~ $ sudo apt install weewx
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut.
Statusinformationen werden eingelesen Fertig
Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
nicht erstellt wurden oder Incoming noch nicht verlassen haben.
Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu lösen:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 weewx : Hängt ab von: python3-cheetah ist aber nicht installierbar
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene 
defekte Pakete.
pi@raspberrypi:~ $

tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 14:30:02 UTC+2:

> I'm sorry: I just realized that your post is unrelated to the original 
> post. We need some context to understand what you are trying to do. The 
> screenshot you sent does not match your description of what you did. Are 
> you truly upgrading? If so, from what version?
>
> What happens when you do a simple install:
>
>
> *wget -qO - http://weewx.com/apt/weewx-python3.list 
> <http://weewx.com/apt/weewx-python3.list> | sudo tee 
> /etc/apt/sources.list.d/weewx.list*
> *sudo apt update*
> *sudo apt install weewx*
>
> -tk
>
> On Mon, Aug 10, 2020 at 10:44 PM geni08...@gmail.com  
> wrote:
>
>> I did this:
>> wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee 
>> /etc/apt/sources.list.d/weewx.list
>> sudo apt-get update
>> sudo apt-get upgrade
>> sudo apt install python3-mysqldb 
>> sudo apt install python3-ephem
>> sudo apt-get update
>> sudo apt-get upgrade
>>
>>
>> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 02:56:50 UTC+2:
>>
>>> (Please do not send a screen shot. They are hard to read, include only a 
>>> few lines, and cannot be translated. Cut and paste instead.)
>>>
>>> Did you do
>>>
>>> *sudo apt-get update*
>>>
>>> first?
>>>
>>> On Mon, Aug 10, 2020 at 10:02 AM geni08...@gmail.com <
>>> geni08...@gmail.com> wrote:
>>>
>>>> Update gets stuck with errors from missing packages
>>>> [image: weewx1.jpg]
>>>>
>>>> Jlou 43 schrieb am Dienstag, 4. August 2020 um 23:13:53 UTC+2:
>>>>
>>>>>  Thanks for your reply, but I solved my problem by reinstalling this 
>>>>> way:
>>>>>
>>>>>
>>>>> 3. Install WeeWX 
>>>>>
>>>>> After installing the prerequisites, you can install WeeWX itself.
>>>>>
>>>>>1. 
>>>>>
>>>>>Expand the source archive:
>>>>>
>>>>>tar xvfz weewx-X.Y.Z.tar.gz
>>>>>
>>>>>2. 
>>>>>
>>>>>Change directory into the expanded archive:
>>>>>
>>>>>cd weewx-X.Y.Z
>>>>>
>>>>>3. 
>>>>>
>>>>>To specify an install location different from the default 
>>>>>/home/weewx, modify the parameter home in the setup.cfg file. Mac 
>>>>>users will want to change it to /Users/Shared/weewx. 
>>>>>4. 
>>>>>
>>>>>Then build and install. Python 2 users: substitute python2 for 
>>>>>python3. 
>>>>>
>>>>>python3 ./setup.py build
>>>>>sudo python3 ./setup.py install
>>>>>
>>>>>
>>>>> I replace python3 by python2 and now everything works perfectly, but 
>>>>> if i have to switch to python3 your advice will be helpful.
>>>>> Thank you.
>>>>>
>>>>>
>>>>> -- 
>>>> 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/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>> .
>>>>
>>> -- 
>> 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/58117a25-289e-41f0-922c-1e1b7320f51dn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/58117a25-289e-41f0-922c-1e1b7320f51dn%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/8083aade-6ec3-4e8a-bf4a-6c5b6bf4c2c1n%40googlegroups.com.

[weewx-user] Re: Questions about weewx-loopdata 2.x

[geni08...@gmail.com]

I found a syntax.
Question: for example "Hi Out Temp, week", shouldn't it be the highest temp 
since Monday? But this is not true for me! Why?

geni08...@gmail.com schrieb am Dienstag, 11. August 2020 um 10:57:03 UTC+2:

> @John: I installed version 2.6.
> how do i get the values:
>  style='white-space:pre;'>
>  style='white-space:pre;'>
>  style='white-space:pre;'>
>  style='white-space:pre;'>
>  style='white-space:pre;'>

-- 
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/282de9d8-ff84-4c29-b302-2893aded408fn%40googlegroups.com.

[weewx-user] Questions about weewx-loopdata 2.x

[geni08...@gmail.com]

@John: I installed version 2.6.
how do i get the values:






-- 
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/5d1c2f04-9a44-4397-aecd-86adaa497239n%40googlegroups.com.

Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[geni08...@gmail.com]

I did this:
wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee 
/etc/apt/sources.list.d/weewx.list
sudo apt-get update
sudo apt-get upgrade
sudo apt install python3-mysqldb 
sudo apt install python3-ephem
sudo apt-get update
sudo apt-get upgrade


tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 02:56:50 UTC+2:

> (Please do not send a screen shot. They are hard to read, include only a 
> few lines, and cannot be translated. Cut and paste instead.)
>
> Did you do
>
> *sudo apt-get update*
>
> first?
>
> On Mon, Aug 10, 2020 at 10:02 AM geni08...@gmail.com  
> wrote:
>
>> Update gets stuck with errors from missing packages
>> [image: weewx1.jpg]
>>
>> Jlou 43 schrieb am Dienstag, 4. August 2020 um 23:13:53 UTC+2:
>>
>>>  Thanks for your reply, but I solved my problem by reinstalling this 
>>> way:
>>>
>>>
>>> 3. Install WeeWX 
>>>
>>> After installing the prerequisites, you can install WeeWX itself.
>>>
>>>1. 
>>>
>>>Expand the source archive:
>>>
>>>tar xvfz weewx-X.Y.Z.tar.gz
>>>
>>>2. 
>>>
>>>Change directory into the expanded archive:
>>>
>>>cd weewx-X.Y.Z
>>>
>>>3. 
>>>
>>>To specify an install location different from the default /home/weewx, 
>>>modify the parameter home in the setup.cfg file. Mac users will want 
>>>to change it to /Users/Shared/weewx. 
>>>4. 
>>>
>>>Then build and install. Python 2 users: substitute python2 for 
>>>python3. 
>>>
>>>python3 ./setup.py build
>>>sudo python3 ./setup.py install
>>>
>>>
>>> I replace python3 by python2 and now everything works perfectly, but if 
>>> i have to switch to python3 your advice will be helpful.
>>> Thank you.
>>>
>>>
>>> -- 
>> 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/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
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/58117a25-289e-41f0-922c-1e1b7320f51dn%40googlegroups.com.

Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[geni08...@gmail.com]

Update gets stuck with errors from missing packages
[image: weewx1.jpg]

Jlou 43 schrieb am Dienstag, 4. August 2020 um 23:13:53 UTC+2:

>  Thanks for your reply, but I solved my problem by reinstalling this way:
>
>
> 3. Install WeeWX 
>
> After installing the prerequisites, you can install WeeWX itself.
>
>1. 
>
>Expand the source archive:
>
>tar xvfz weewx-X.Y.Z.tar.gz
>
>2. 
>
>Change directory into the expanded archive:
>
>cd weewx-X.Y.Z
>
>3. 
>
>To specify an install location different from the default /home/weewx, 
>modify the parameter home in the setup.cfg file. Mac users will want 
>to change it to /Users/Shared/weewx. 
>4. 
>
>Then build and install. Python 2 users: substitute python2 for python3. 
>
>
>python3 ./setup.py build
>sudo python3 ./setup.py install
>
>
> I replace python3 by python2 and now everything works perfectly, but if i 
> have to switch to python3 your advice will be helpful.
> Thank you.
>
>
>

-- 
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/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com.

Re: [weewx-user] Belchertown Question about "yAxis_tickinterval"

[geni08...@gmail.com]

Hi Didier,
the lowercase "I" was like you noticed, Small cause big effect, thank you 
very much
Geni

didier@gmail.com schrieb am Sonntag, 26. Juli 2020 um 15:17:54 UTC+2:

> Hi
>
> I think you have a mistake in the name, this is "yAxis_tickInterval"
>
>   [[[barometer]]]
> yAxis_label = ( mbar )
> decimals = 0
> color = "#e4d354"
> yAxis_tickInterval = 2
> yAxis_softMin = 1000
> yAxis_softMax = 1030
>
> Didier
>
> Le dim. 26 juil. 2020 à 12:41, Geni 0815  a écrit :
>
>> I have Belchertown Skin Version: 1.2rc2
>> "YAxis_tickinterval" doesn't work for me.
>>
>>  [[chart4]]
>>  title = air pressure
>>  type = spline
>>  [[[barometer]]]
>>  yAxis_tickinterval = 2
>>  color = "# BECC00"
>>
>>   still produces the following graphic:
>>
>> [image: belch06.jpg]
>>
>> I expect this
>>
>> [image: belch07.jpg]
>>
>>
>>
>> -- 
>> 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/d2356b6f-5bd4-4f13-9fe6-a9ce708a9d10o%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/a7420a49-d460-489e-8a09-bfc5af019a4cn%40googlegroups.com.

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

Hi PAT, I have version 1.2rc2 since yesterday. So now "start_at_midnight = 
true" also works. *Very important*, this is the only way that the daily 
rain sums are correct.

geni08...@gmail.com schrieb am Sonntag, 12. Juli 2020 um 10:47:51 UTC+2:

> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 0mm, 
> 15mm and 3.2mm on the corresponding days. The sum is correct but wrongly 
> divided. Where is the mistake?
> [image: belch10.jpg]
> [image: belch11.jpg]
> [month]
> # Chart Timespan Defaults
> title = "Letzte 30 Tage"
> show_button = true
> button_text = "Letzte 30 Tage"
> type = spline
> time_length = 2592000 # Last 30 days
> tooltip_date_format = " LL"
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640 # 1 day in milliseconds
> 
> [[chart3]]
> title = Regenx
> type = line
> aggregate_type=sum
> [[[rainTotal]]]
> name = Regen Total
> [[[rain]]]
> yAxis = 1
> type = column
> 
> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>

-- 
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/10e67914-be44-4870-bbf9-efd6579e5957n%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

Hi John, since version 2.0.b8 the display works as expected. I have just 
installed 2.0.b10 and see no difference on the fast.
What I don't understand is why the documented field 
"trend.barometerRate.formatted" does not provide any information in the 
loop-data.txt. Do I get my information from "trend.barometer.formatted"?

jo...@johnkline.com schrieb am Samstag, 18. Juli 2020 um 22:23:49 UTC+2:

> Give 2.0.b7 a spin.
>
> trend has now been generalized (as opposed to only working with 
> barometer).  It will also honor the time_span configured for the target 
> report.
>
> If the numbers don’t look right to you, the last 36 records in the archive 
> table would be more helpful than sending screenshots of the value differing 
> from what report generation produces.
>
> trend.barometer.desc (i.e, the .desc suffix) is still an oddball.  It 
> shouldn’t be part of LoopData.  I’m going to remove it, but I need to move 
> the code (to produce the description) to JavasSript (for one of my personal 
> reports, not as part of LoopData).
>
> On Jul 18, 2020, at 6:05 AM, John Kline  wrote:
>
> 
>
> I’ve already well on my way to replacing this.  Trend will work for all 
> scalar values, not just barometer.  The code is done, but I need to add it 
> to the tests.
>
> On Jul 17, 2020, at 11:17 PM, geni08...@gmail.com  
> wrote:
>
>  I don't think there are any errors in the database, the barometer trend 
> is displayed in my season <https://affolter.familyds.net/wetter/Seasons/>with 
> a credible value that also matches the value in the index.html from the 
> weatherboard (as documented in the older answer).
> I also attached the file loop-data-xxx.txt, in the upper part you can see 
> the values generated by loop-data in the lower part my entry in weewx.conf. 
> It 
> is striking that the values "trend.barometerRate.desc" and 
> "trend.barometerRate" are missing.
> Yesterday at noon I noticed that the value of the 
> "trend.barometer.formatted", which is now> 300 is exactly at 12h (GTM + 2) 
> on the expected value. Will watch this today). 
>
> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 16:23:27 UTC+2:
>
>> 
>> As the documentation states, trend.barometer and 10m.windGust are special 
>> cases.
>>
>> In this case, where we are talking about trend.barometer, it is alway the 
>> delta from three hours ago and uses archive records to compute the starting 
>> reading.  Also, it is expressed as a per hour rate.  Thus, it would be 1/3 
>> of the three hour delta.  I did it this way because my sole purpose was to 
>> compute the text description (e.g., rising slowly).
>>
>> Perhaps you have some bad data in your database?  Have you checked that 
>> to see what the actual delta and per hour delta should be?
>>
>> In any event, I need to make trend less special.  I think I’ll do that 
>> this weekend.  It should honor the $delta.time_delta for the skin and 
>> report the actual delta, not on a per hour basis.  While I’m doing that, 
>> I’ll make sure my tests around trend.barometer are good enough.  If there 
>> is a bug, I should find it then.
>>
>>
>> On Jul 16, 2020, at 11:07 PM, geni08...@gmail.com  
>> wrote:
>>
>> Thank you very much, the script is a good idea.
>>
>>
>>
>> There was another question regarding "trend.barometerRate.formatted". At 
>> the beginning this gave plausible values, from yesterday evening it 
>> delivers impossible values.
>> Is it possible that 2 sources supply data and interfere?
>> I tried to keep a momentary status.
>>
>> Display liveboard
>>
>> 
>>
>>
>> index.html
>> 
>>
>>
>> loop-data.txt
>>
>> 
>>
>>
>> index.html.tmpl
>> 
>> 
>> $current.barometer (> id="trend.barometer.formatted">$trend.barometer.formatted) - >  
>> id="current.outHumidity">$current.outHumidity 
>> 
>> 
>>
>>
>> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 00:02:36 UTC+2:
>>
>>> I’m not sure which parts of Bechlertown rely on MQTT and which parts 
>>> rely on auto refreshing the page.  For the former, if the info is available 
>>> in LoopData, you would need to add an id to the HTML element and then set 
>>> the contents via javascript in the same way as WeatherBoard does it.
>>>
>>> Bechlertown appears to be a well supported skin with frequent updates. 
>>>  You do need to worry about taking updates of the skin since you’ll be 
>>> making modif

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 I don't think there are any errors in the database, the barometer trend is 
displayed in my season <https://affolter.familyds.net/wetter/Seasons/>with 
a credible value that also matches the value in the index.html from the 
weatherboard (as documented in the older answer).
I also attached the file loop-data-xxx.txt, in the upper part you can see 
the values generated by loop-data in the lower part my entry in weewx.conf. It 
is striking that the values "trend.barometerRate.desc" and 
"trend.barometerRate" are missing.
Yesterday at noon I noticed that the value of the 
"trend.barometer.formatted", which is now> 300 is exactly at 12h (GTM + 2) 
on the expected value. Will watch this today). 

jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 16:23:27 UTC+2:

> 
> As the documentation states, trend.barometer and 10m.windGust are special 
> cases.
>
> In this case, where we are talking about trend.barometer, it is alway the 
> delta from three hours ago and uses archive records to compute the starting 
> reading.  Also, it is expressed as a per hour rate.  Thus, it would be 1/3 
> of the three hour delta.  I did it this way because my sole purpose was to 
> compute the text description (e.g., rising slowly).
>
> Perhaps you have some bad data in your database?  Have you checked that to 
> see what the actual delta and per hour delta should be?
>
> In any event, I need to make trend less special.  I think I’ll do that 
> this weekend.  It should honor the $delta.time_delta for the skin and 
> report the actual delta, not on a per hour basis.  While I’m doing that, 
> I’ll make sure my tests around trend.barometer are good enough.  If there 
> is a bug, I should find it then.
>
>
> On Jul 16, 2020, at 11:07 PM, geni08...@gmail.com  
> wrote:
>
> Thank you very much, the script is a good idea.
>
>
>
> There was another question regarding "trend.barometerRate.formatted". At 
> the beginning this gave plausible values, from yesterday evening it 
> delivers impossible values.
> Is it possible that 2 sources supply data and interfere?
> I tried to keep a momentary status.
>
> Display liveboard
>
> 
>
>
> index.html
> 
>
>
> loop-data.txt
>
> 
>
>
> index.html.tmpl
> 
> 
> $current.barometer ( id="trend.barometer.formatted">$trend.barometer.formatted) -   
> id="current.outHumidity">$current.outHumidity 
> 
> 
>
>
> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 00:02:36 UTC+2:
>
>> I’m not sure which parts of Bechlertown rely on MQTT and which parts rely 
>> on auto refreshing the page.  For the former, if the info is available in 
>> LoopData, you would need to add an id to the HTML element and then set the 
>> contents via javascript in the same way as WeatherBoard does it.
>>
>> Bechlertown appears to be a well supported skin with frequent updates. 
>>  You do need to worry about taking updates of the skin since you’ll be 
>> making modifications.  Ideally, you would write a script to add the ids in 
>> the right place and add a line to include the javascript.
>>
>> On Jul 16, 2020, at 8:18 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>>
>> Hi John, Thank you for your help so far, my next goal is to update the 
>> Belchertown template with weewx-loopdata.
>> MQTT needs an infrastructure there ... I find your solution really 
>> elegant. Do you have a tip for me where to start?
>>
>>
>> jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um 15:46:28 
>> UTC+2:
>>
>>> It looks like you are on a roll!
>>>
>>> I think you are asking why I don’t have the actual values filled in for 
>>> windGust in the template.
>>>
>>> The answer for $10m.windGust.max is that the $10m period is only 
>>> understood by LoopData.  If you put $10m.windGust.max in the template, it 
>>> would cause an error.  There is probably a way to compute the 10 minute 
>>> high gust, but I didn’t bother to figure that out since the value will 
>>> appear anyway on the next loop.
>>>
>>> For $day.windGust.max, adding it to the template should work just fine. 
>>>  It’s not needed.  In fact, none of the values are needed since they are 
>>> overwritten by the JavaScript.
>>>
>>>
>>>
>>> On Jul 16, 2020, at 5:26 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>>  Hi John, it could even add winDir and barometer and humidity!
>>>
>>> What I would like to know why is enough for the two windGust values only 
>>> the id in index.ht

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

 that's not what i want, your 30 day version is correct 
https://www.affolter.familyds.net/wetter/graphs/?graph=25h

Pat schrieb am Donnerstag, 16. Juli 2020 um 18:58:29 UTC+2:

> Looking at the source code of Seasons, try this in your graphs.conf. I 
> think this is what you're looking for with the aggregations you want. 
>
> [testrainpage]
> title = "Rain Test"
> show_button = true
> button_text = "Rain Test"
> tooltip_date_format = "LLL"
>
> 
> [[rain25h]]
> title = "Rain 25h"
> time_length = 9 # 25 hours
> [[[rain]]]
> name = Rain (hourly total)
> type = column
> aggregate_type = sum
> aggregate_interval = 3600
>
> [[[rainTotal]]]
> name = Rain Total
>
>
>
> [[rain7d]]
> title = "Rain Last 7 Days"
> time_length = 604800 # Last 7 days
> gapsize = 360
> [[[rain]]]
> name = Rain (daily total)
> type = column
> aggregate_type = sum
> aggregate_interval = 86400
>
> [[[rainTotal]]]
> name = Rain Total
>
>
>
> [[rain30d]]
>
> title = "Rain Last 30 Days"
> time_length = 2592000 # Last 30 days
>
> gapsize = 8640
> [[[rain]]]
> name = Rain (daily total)
>     type = column
> aggregate_type = sum
> aggregate_interval = 86400
>
> [[[rainTotal]]]
> name = Rain Total
>
>
>
> On Thursday, July 16, 2020 at 12:36:01 PM UTC-4, geni08...@gmail.com 
> wrote:
>
>> How does this season do it? 
>> [image: belch01.jpg]
>> [image: belch02.jpg]
>>
>> Pat schrieb am Donnerstag, 16. Juli 2020 um 18:30:19 UTC+2:
>>
>>> 1. Don't think this is possible. The graphs do not do any 
>>> additional math. They show what is in the database and aggregate those 
>>> values if needed (such as max, min, sum, etc.). 
>>> 2. Don't think this is possible. The graphs do not do any additional 
>>> math. They show what is in the database and aggregate those values if 
>>> needed (such as max, min, sum, etc.). 
>>>
>>> 3. Rain last 30 days is:
>>>
>>> [testrainpage]
>>> title = "Rain Test"
>>> show_button = true
>>> button_text = "Rain Test"
>>> tooltip_date_format = "LLL"
>>>
>>>
>>> [[rain30d]]
>>> title = "Rain Last 30 Days"
>>>
>>> time_length = 2592000 # Last 30 days
>>>
>>> aggregate_type = sum
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640
>>> [[[rain]]]
>>> name = Rain
>>> type = column
>>> [[[rainTotal]]]
>>> name = Rain Total
>>>
>>>
>>> On Thursday, July 16, 2020 at 12:27:05 PM UTC-4, geni08...@gmail.com 
>>> wrote:
>>>>
>>>> I would like to:
>>>> 1. Rain 25h -> mm per h, not every 5 min
>>>> 2 Rain Last 7 Day -> mm per day, not per hour
>>>> 3 Rain Last 30 Day -> is what I want 
>>>>
>>>> Pat schrieb am Donnerstag, 16. Juli 2020 um 17:35:35 UTC+2:
>>>>
>>>>> So on 1 page, you want 3 charts?
>>>>>
>>>>> 1. Rain for 25 hours
>>>>> 2. Rain for 7 days
>>>>> 3. Rain for 30 days
>>>>>
>>>>> Yes, we need to use seconds for this as that is the rolling time 
>>>>> period. The time_ago does not do a rolling period, only the calendar day 
>>>>> for that time ago. 
>>>>>
>>>>> Is this what you want? 
>>>>> https://belchertownweather.com/graphs/?graph=testrainpage
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thursday, July 16, 2020 at 10:59:28 AM UTC-4, geni08...@gmail.com 
>>>>> wrote:
>>>>>>
>>>>>> Hi Pat, the Wicki doesn't get me any further because I don't 
>>>>>> understand some things and I can't get any graphics as I wish. I want 
>>>>>> three 
>>>>>> examples
>>>>>> each the amount of rain per unit of time in mm as a column and the 
>>>>>> cumulative total as a line.
>>>

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

 How does this season do it? 
[image: belch01.jpg]
[image: belch02.jpg]

Pat schrieb am Donnerstag, 16. Juli 2020 um 18:30:19 UTC+2:

> 1. Don't think this is possible. The graphs do not do any additional math. 
> They show what is in the database and aggregate those values if needed 
> (such as max, min, sum, etc.). 
> 2. Don't think this is possible. The graphs do not do any additional math. 
> They show what is in the database and aggregate those values if needed 
> (such as max, min, sum, etc.). 
>
> 3. Rain last 30 days is:
>
> [testrainpage]
> title = "Rain Test"
> show_button = true
> button_text = "Rain Test"
> tooltip_date_format = "LLL"
>
>
> [[rain30d]]
> title = "Rain Last 30 Days"
>
> time_length = 2592000 # Last 30 days
>
> aggregate_type = sum
> aggregate_interval = 86400 # 1 day
> gapsize = 8640
> [[[rain]]]
> name = Rain
> type = column
> [[[rainTotal]]]
> name = Rain Total
>
>
> On Thursday, July 16, 2020 at 12:27:05 PM UTC-4, geni08...@gmail.com 
> wrote:
>>
>> I would like to:
>> 1. Rain 25h -> mm per h, not every 5 min
>> 2 Rain Last 7 Day -> mm per day, not per hour
>> 3 Rain Last 30 Day -> is what I want 
>>
>> Pat schrieb am Donnerstag, 16. Juli 2020 um 17:35:35 UTC+2:
>>
>>> So on 1 page, you want 3 charts?
>>>
>>> 1. Rain for 25 hours
>>> 2. Rain for 7 days
>>> 3. Rain for 30 days
>>>
>>> Yes, we need to use seconds for this as that is the rolling time period. 
>>> The time_ago does not do a rolling period, only the calendar day for that 
>>> time ago. 
>>>
>>> Is this what you want? 
>>> https://belchertownweather.com/graphs/?graph=testrainpage
>>>
>>>
>>>
>>>
>>> On Thursday, July 16, 2020 at 10:59:28 AM UTC-4, geni08...@gmail.com 
>>> wrote:
>>>>
>>>> Hi Pat, the Wicki doesn't get me any further because I don't understand 
>>>> some things and I can't get any graphics as I wish. I want three examples
>>>> each the amount of rain per unit of time in mm as a column and the 
>>>> cumulative total as a line.
>>>> Example 25h: The variant with mm / 10min works, but the variant with mm 
>>>> / h only results in nonsense.
>>>> [25h]
>>>> # Chart Timespan Defaults
>>>> title = "Letzte 25h"
>>>> show_button = true
>>>> button_text = "Letzte 25h"
>>>> time_length = 9
>>>> tooltip_date_format = "LLL"
>>>> gapsize = 60 # This should be your archive_interval from 
>>>> weewx.conf multiplied by 1000 to get milliseconds. Standard is 5 minutes
>>>>
>>>> [[chart1]]
>>>> title = Regen
>>>> [[[rain]]]
>>>>   yAxis = 1
>>>>   type = column
>>>>   name = Regen mm/10min
>>>> [[[rainTotal]]]
>>>>   name = Regen Total
>>>> 
>>>> [[chart2]]
>>>> title = Regen
>>>> aggregate_interval = 86400
>>>> [[[rain]]]
>>>>   aggregate_type = sum
>>>>   yAxis = 1
>>>>   type = column
>>>>   name = Regen mm/h
>>>> [[[rainTotal]]]
>>>>   name = Regen Total
>>>> [image: high-25h.jpg]
>>>>
>>>> The two variants "Last 7 days" and "Last 30 days", because nothing is 
>>>> plotted during my attempt.
>>>> Can I get the corrected samples?
>>>> Thank you for your help
>>>>
>>>> Pat schrieb am Mittwoch, 15. Juli 2020 um 16:32:01 UTC+2:
>>>>
>>>>> So if you don't want the last 2592000 seconds, maybe you want "the 
>>>>> last 30 days" as a rolling window?
>>>>>
>>>>> In that case, use time_length = days_ago 
>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#time_length>
>>>>>  
>>>>> and time_ago = 30 
>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#to-graph-days-ago>
>>>>>
>>>>> Please do read the charts wiki 
>>>>> 

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

 I would like to:
1. Rain 25h -> mm per h, not every 5 min
2 Rain Last 7 Day -> mm per day, not per hour
3 Rain Last 30 Day -> is what I want 

Pat schrieb am Donnerstag, 16. Juli 2020 um 17:35:35 UTC+2:

> So on 1 page, you want 3 charts?
>
> 1. Rain for 25 hours
> 2. Rain for 7 days
> 3. Rain for 30 days
>
> Yes, we need to use seconds for this as that is the rolling time period. 
> The time_ago does not do a rolling period, only the calendar day for that 
> time ago. 
>
> Is this what you want? 
> https://belchertownweather.com/graphs/?graph=testrainpage
>
>
>
>
> On Thursday, July 16, 2020 at 10:59:28 AM UTC-4, geni08...@gmail.com 
> wrote:
>>
>> Hi Pat, the Wicki doesn't get me any further because I don't understand 
>> some things and I can't get any graphics as I wish. I want three examples
>> each the amount of rain per unit of time in mm as a column and the 
>> cumulative total as a line.
>> Example 25h: The variant with mm / 10min works, but the variant with mm / 
>> h only results in nonsense.
>> [25h]
>> # Chart Timespan Defaults
>> title = "Letzte 25h"
>> show_button = true
>> button_text = "Letzte 25h"
>> time_length = 9
>> tooltip_date_format = "LLL"
>> gapsize = 60 # This should be your archive_interval from 
>> weewx.conf multiplied by 1000 to get milliseconds. Standard is 5 minutes
>>
>> [[chart1]]
>> title = Regen
>> [[[rain]]]
>>   yAxis = 1
>>   type = column
>>   name = Regen mm/10min
>> [[[rainTotal]]]
>>   name = Regen Total
>> 
>> [[chart2]]
>> title = Regen
>> aggregate_interval = 86400
>> [[[rain]]]
>>   aggregate_type = sum
>>   yAxis = 1
>>   type = column
>>   name = Regen mm/h
>> [[[rainTotal]]]
>>   name = Regen Total
>> [image: high-25h.jpg]
>>
>> The two variants "Last 7 days" and "Last 30 days", because nothing is 
>> plotted during my attempt.
>> Can I get the corrected samples?
>> Thank you for your help
>>
>> Pat schrieb am Mittwoch, 15. Juli 2020 um 16:32:01 UTC+2:
>>
>>> So if you don't want the last 2592000 seconds, maybe you want "the last 
>>> 30 days" as a rolling window?
>>>
>>> In that case, use time_length = days_ago 
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#time_length>
>>>  
>>> and time_ago = 30 
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#to-graph-days-ago>
>>>
>>> Please do read the charts wiki 
>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation>,
>>>  
>>> everything is covered there. 
>>>
>>>
>>> On Wednesday, July 15, 2020 at 10:26:52 AM UTC-4, Andre wrote:
>>>>
>>>> It was just a thought, because with "time_length = 2592000" we do not 
>>>> get the desired values.
>>>>
>>>> Am Mittwoch, 15. Juli 2020 16:00:51 UTC+2 schrieb Pat:
>>>>>
>>>>> What do you mean real calendar days? The 2592000 is the previous 2592000 
>>>>> seconds. This number can be anything you want. 
>>>>>
>>>>> On Wednesday, July 15, 2020 at 9:47:21 AM UTC-4, Andre wrote:
>>>>>>
>>>>>> With "time_length = month" the values are correct of course.
>>>>>> Maybe we need a fix to generate real calendar days for "time_length 
>>>>>> = 2592000".
>>>>>>
>>>>>> Am Mittwoch, 15. Juli 2020 15:08:23 UTC+2 schrieb Pat:
>>>>>>>
>>>>>>> Great point Manfred. If you guys change your time_length to month 
>>>>>>> <https://github.com/poblabs/weewx-belchertown/wiki/Belchertown-Charts-Documentation#time_length>,
>>>>>>>  
>>>>>>> do the values match?
>>>>>>>
>>>>>>> On Wednesday, July 15, 2020 at 8:59:08 AM UTC-4, Manfred Maier wrote:
>>>>>>>>
>>>>>>>> Couldn't this just be an issue with how the timespan for the chart 
>>>>>>>> is defined?
>>>>>>>> The chart displays the past 2592000 seconds and splits it into 
>>>

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 Hi John, Thank you for your help so far, my next goal is to update the 
Belchertown template with weewx-loopdata.
MQTT needs an infrastructure there ... I find your solution really elegant. Do 
you have a tip for me where to start?


jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um 15:46:28 UTC+2:

> It looks like you are on a roll!
>
> I think you are asking why I don’t have the actual values filled in for 
> windGust in the template.
>
> The answer for $10m.windGust.max is that the $10m period is only 
> understood by LoopData.  If you put $10m.windGust.max in the template, it 
> would cause an error.  There is probably a way to compute the 10 minute 
> high gust, but I didn’t bother to figure that out since the value will 
> appear anyway on the next loop.
>
> For $day.windGust.max, adding it to the template should work just fine. 
>  It’s not needed.  In fact, none of the values are needed since they are 
> overwritten by the JavaScript.
>
>
>
> On Jul 16, 2020, at 5:26 AM, geni08...@gmail.com  
> wrote:
>
>  Hi John, it could even add winDir and barometer and humidity!
>
> What I would like to know why is enough for the two windGust values only 
> the id in index.html.tmpl 
> https://affolter.familyds.net/wetter/live/
>
> 
>
>
> jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 22:32:15 UTC+2:
>
>> Thanks for sending those links.
>>
>> Again, I don’t think it’s necessary to move the file to ram disk.  With 
>> modern SSDs and wear leveling, and especially with a file this size.  You 
>> might want to do some web searches before deciding if its worth the effort.
>>
>> On Jul 15, 2020, at 1:14 PM, 'hctp...@googlemail.com' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>> John,
>>
>> so maybe a project for the next days to put the loop-data.tx into ram and 
>> serve it via apache2. 
>> The WeatherBoard site:
>>
>> https://livewetter.hcpeters.de
>>
>> and my main weather site:
>>
>> https://wetter.hcpeters.de/
>>
>> .
>> The gauges you see on the main site seems to use Javascript so that's why 
>> I asked...! :-D 
>> At the moment I just give a fixed value and render the entire site every 
>> minute...near realtime... ;-) 
>>
>> But diving into java would be a big task not sure I'm ready for 
>> thatalready fighting with Python...! :-D
>>
>> Regards,
>>
>> Christian 
>>
>>
>>
>> jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 21:59:47 UTC+2:
>>
>>> I do not personally regard it as a problem.  Others may have a different 
>>> opinion.
>>>
>>> It certainly is not necessary to have it on the SSD, but you would have 
>>> to configure apache2 (or whatever web server you are using), to be able to 
>>> serve loop-data.txt.
>>>
>>> BTW, is your site visible externally?  If so, would you send a link?
>>>
>>> On Jul 15, 2020, at 12:46 PM, 'hctp...@googlemail.com' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
>>> John,
>>>
>>>
>>> is this a problem to write the loop-data.txt file every 2sec on a SSD 
>>> regarding durability!?
>>> Or would it be better to place it on a ramdisk (tmpfs) like /dev/shm ...
>>>
>>> Regards,
>>>
>>> Christian 
>>>
>>> jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 21:35:27 
>>> UTC+2:
>>>
>>>> Great news!
>>>>
>>>> The purpose of LoopData is to be able to add to any skin, but it does 
>>>> require knowledge of JavaScript.
>>>>
>>>> On Jul 15, 2020, at 12:33 PM, John Kline  wrote:
>>>>
>>>> 
>>>>
>>>> 
>>>> tail -f loop-data.txt won’t work because a new file is created on every 
>>>> loop.
>>>>
>>>> You can use:
>>>> watch cat loop-data.txt
>>>>
>>>> You screen shots are not of any javascript errors that might be on the 
>>>> page.
>>>>
>>>> Would you send me the following file?
>>>> /var/www/html/weewx/weatherboard/index.html
>>>>
>>>> On Jul 15, 2020, at 12:07 PM, 'hctp...@googlemail.com' via weewx-user <
>>>> weewx...@googlegroups.com> wrote:
>>>>
>>>> ok...last post for now...maybe this is the problem, see screenshot...
>>>>
>>>> hctp...@googlemail.com schrieb am Mittwoch,

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

Hi Pat, the Wicki doesn't get me any further because I don't understand 
some things and I can't get any graphics as I wish. I want three examples
each the amount of rain per unit of time in mm as a column and the 
cumulative total as a line.
Example 25h: The variant with mm / 10min works, but the variant with mm / h 
only results in nonsense.
[25h]
# Chart Timespan Defaults
title = "Letzte 25h"
show_button = true
button_text = "Letzte 25h"
time_length = 9
tooltip_date_format = "LLL"
gapsize = 60 # This should be your archive_interval from weewx.conf 
multiplied by 1000 to get milliseconds. Standard is 5 minutes

[[chart1]]
title = Regen
[[[rain]]]
  yAxis = 1
  type = column
  name = Regen mm/10min
[[[rainTotal]]]
  name = Regen Total

[[chart2]]
title = Regen
aggregate_interval = 86400
[[[rain]]]
  aggregate_type = sum
  yAxis = 1
  type = column
  name = Regen mm/h
[[[rainTotal]]]
  name = Regen Total
[image: high-25h.jpg]

The two variants "Last 7 days" and "Last 30 days", because nothing is 
plotted during my attempt.
Can I get the corrected samples?
Thank you for your help

Pat schrieb am Mittwoch, 15. Juli 2020 um 16:32:01 UTC+2:

> So if you don't want the last 2592000 seconds, maybe you want "the last 30 
> days" as a rolling window?
>
> In that case, use time_length = days_ago 
> 
>  
> and time_ago = 30 
> 
>
> Please do read the charts wiki 
> ,
>  
> everything is covered there. 
>
>
> On Wednesday, July 15, 2020 at 10:26:52 AM UTC-4, Andre wrote:
>>
>> It was just a thought, because with "time_length = 2592000" we do not get 
>> the desired values.
>>
>> Am Mittwoch, 15. Juli 2020 16:00:51 UTC+2 schrieb Pat:
>>>
>>> What do you mean real calendar days? The 2592000 is the previous 2592000 
>>> seconds. This number can be anything you want. 
>>>
>>> On Wednesday, July 15, 2020 at 9:47:21 AM UTC-4, Andre wrote:

 With "time_length = month" the values are correct of course.
 Maybe we need a fix to generate real calendar days for "time_length = 
 2592000".

 Am Mittwoch, 15. Juli 2020 15:08:23 UTC+2 schrieb Pat:
>
> Great point Manfred. If you guys change your time_length to month 
> ,
>  
> do the values match?
>
> On Wednesday, July 15, 2020 at 8:59:08 AM UTC-4, Manfred Maier wrote:
>>
>> Couldn't this just be an issue with how the timespan for the chart is 
>> defined?
>> The chart displays the past 2592000 seconds and splits it into pieces 
>> of 86400 seconds (24 hours). But those 24 hours might go from 11am - 
>> 11am.
>>
>> Just a thought and probably wrong ...
>>
>> Pat schrieb am Mittwoch, 15. Juli 2020 um 14:48:25 UTC+2:
>>
>>> I'm at a loss because I can't recreate this. 
>>>
>>> Please send me a copy of your database as well as your graphs.conf, 
>>> and public_html/belchertown/json/weewx_data.json
>>>
>>> My time to dedicate to this is slim right now, so if anyone else 
>>> finds the problem that'd be helpful and I can merge it to development 
>>> branch. 
>>>
>>>
>>> On Wednesday, July 15, 2020 at 8:44:58 AM UTC-4, Andre wrote:

 I can reproduce the display issues.
 I have dropped all daily reports and rebuild daily.

 [image: noaa_2020-07.png]


 Last 7 days

 [image: last_7_days.png]

 [image: last_30_days.png]
 Last 30 days...

 Am Mittwoch, 15. Juli 2020 14:19:19 UTC+2 schrieb Pat:
>
> Sounds like you may have some problems with your database. I 
> suggest you take a backup and follow the database drop-daily 
> and 
> rebuild-daily 
> and 
> see if that helps
>
> The graphs uses your archive table
>
> The reports uses your daily tables. 
>
> Seems like those aren't in sync for you.
>
> On Wednesday, July 15, 2020 at 6:16:48 AM UTC-4, Geni 0815 wrote:
>>
>> Hi Pat, I just noticed the following:
>> As an example in the graphic "last 30 days", "rain per day". 
>> These values sometimes change every hour!
>> For my understanding, the amount of rain per day is to be 
>> understood on a calendar day 

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

That's correct, I have a problem understanding the JavaScript entries and 
the WeatherBord template.
I started again with the original files.
As soon as I make the smallest change, the wind update no longer works. I 
work with Notepad++ and then copy the file into the skin folder via the 
console. Could this have an impact? Are there rules about the encoding of 
the file? UTF-8 or UTF-8-BOM or something else?

jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 16:21:06 UTC+2:

> 
> 
> You need to be care as to how you state things.  I can clearly see that 
> you have added current.inHumidity to LoopData and you show that it is 
> appearing correctly in the loop-data.txt.
>
> inHumidity is not part of the WeatherBoard skin.  You have added it.  You 
> have a JavaScript error that says inHumidity not defined.  Perhaps you 
> should restate your question.  Are you having problems with the JavaScript 
> changes you have made to WeatherBoard?
>
> On Jul 15, 2020, at 5:54 AM, geni08...@gmail.com  
> wrote:
>
> 
>
>Also, why are you using 2.0.b3?  Please use the latest on master as 
> I’ve merged it in.  It is 2.0.b6 (which happens to be what you were 
> claiming to use in the last email). 
> this was watherboard version
>
> 
>
>
> my loop-data.txt:
> {"current.dateTime.raw": 1594817282, "current.windchill": "17.6\u00b0C", 
> "current.windSpeed": "0.0 km/h", "current.windSpeed.raw": 0.0, 
> "day.windGust.max": "12.9 km/h", "10m.windGust.max": "8.0 km/h", 
> "10m.windGust.max.formatted": "8.0", "current.barometer": "1013.5 hPa", 
> "trend.barometer.formatted": "0.3", "current.rain": "0.0 mm", 
> "current.rainRate": "0 mm/h", "day.rain.sum": "0.8 mm", "current.appTemp": 
> "18.9\u00b0C", "current.outTemp": "17.6\u00b0C", "current.inTemp": 
> "24.2\u00b0C", "current.inHumidity": "50%", "current.outHumidity": "81%"}
>
> 
>
>
> I still have problems with version 2, the update no longer works as in 
> version 1.xx. 
>
> jo...@johnkline.com schrieb am Dienstag, 14. Juli 2020 um 18:35:21 UTC+2:
>
> Of course inHumidity is not defined. You need to read the doc and 
>> specifically the part about upgrading.
>>
>> inHumidity is now current.inHumidity.formatted
>> It’s in the doc.
>>
>> Also, why are you using 2.0.b3?  Please use the latest on master as I’ve 
>> merged it in.  It is 2.0.b6 (which happens to be what you were claiming to 
>> use in the last email).
>>
>> Again, please read the upgrade section of LoopData.  The names changed. 
>>  There is ample warning about that at the top:
>>
>> LoopData 2.x is a breaking change from 1.x. See "How to Upgrade from 
>> LoopData 1.x." below.
>>
>> inHumidity would fall under this conversion rule:
>>
>>-  -> current..formatted
>>
>>
>> On Jul 14, 2020, at 8:29 AM, Geni 0815  wrote:
>>
>> 
>>
>> @John: WeaterBoard 2.0b3 causes problems. everything worked until the 
>> time with the old version.
>> With version 2 I get the error: Uncaught ReferenceError: inHumidity is 
>> not defined, and refreshing doesn't seem to work properly.
>> The syntax also seems different?
>>
>> I'll test that with current.dateTime.raw in a moment
>>
>> Am Dienstag, 14. Juli 2020 15:52:13 UTC+2 schrieb John Kline:
>>
>> It looks like you are missing the following in the fields line:
>>>
>>> current.dateTime.raw
>>>
>>> That is, to upgrade, dateTime needs to be changed to 
>>> current.dateTime.raw
>>>
>>> I’ll update the How to Upgrade section to reflect that.
>>>
>>> On Jul 14, 2020, at 6:01 AM, Geni 0815  wrote:
>>>
>>> 
>>>
>>> @John: I installed version 2.0.b6, almost everything worked right away, 
>>> congratulations.
>>> What is not yet running is the label: Live and the clock at the bottom 
>>> right.
>>>
>>>
>>> Am Freitag, 10. Juli 2020 20:09:30 UTC+2 schrieb John Kline:
>>>
>>> I had a look.  You never actually write FMT_windDir in the JavaScript. 
>>>>  Just add:
>>>> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
>>>> on the appropriate line in realtime_updater.inc.
>>>>
>>>> As for barometerRate.  I do see it.  I just spills over to the next 
>>>> line

[weewx-user] Re: Belchertown, graphics are faulty

[geni08...@gmail.com]

 @Pat: The error is not only with me, also with @Andre. I see the error 
when the graphic "last 30 days" has been selected and the rain is selected 
as the daily total bar. The graphics are one day late. No daily value is 
correct, the sum of 3-4 days is correct again. In my opinion the graphic 
has problems to calculate the correct local start and end of the day. 

geni08...@gmail.com schrieb am Sonntag, 12. Juli 2020 um 10:47:51 UTC+2:

> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 0mm, 
> 15mm and 3.2mm on the corresponding days. The sum is correct but wrongly 
> divided. Where is the mistake?
> [image: belch10.jpg]
> [image: belch11.jpg]
> [month]
> # Chart Timespan Defaults
> title = "Letzte 30 Tage"
> show_button = true
> button_text = "Letzte 30 Tage"
> type = spline
> time_length = 2592000 # Last 30 days
> tooltip_date_format = " LL"
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640 # 1 day in milliseconds
> 
> [[chart3]]
> title = Regenx
> type = line
> aggregate_type=sum
> [[[rainTotal]]]
> name = Regen Total
> [[[rain]]]
> yAxis = 1
> type = column
> 
> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>

-- 
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/541c20c3-7fe2-4ccf-9a7b-8666e12febefn%40googlegroups.com.

[weewx-user] Belchertown, graphics are faulty

[geni08...@gmail.com]

On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 0mm, 
15mm and 3.2mm on the corresponding days. The sum is correct but wrongly 
divided. Where is the mistake?
[image: belch10.jpg]
[image: belch11.jpg]
[month]
# Chart Timespan Defaults
title = "Letzte 30 Tage"
show_button = true
button_text = "Letzte 30 Tage"
type = spline
time_length = 2592000 # Last 30 days
tooltip_date_format = " LL"
aggregate_type = max
aggregate_interval = 86400 # 1 day
gapsize = 8640 # 1 day in milliseconds

[[chart3]]
title = Regenx
type = line
aggregate_type=sum
[[[rainTotal]]]
name = Regen Total
[[[rain]]]
yAxis = 1
type = column

Live: https://affolter.familyds.net/wetter/graphs/?graph=month

-- 
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/806eca65-1ade-4192-ac54-f13900ccf1a3n%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

The loop-data.txt file is not created with all fields!

The entry: $current.barometer ($trend.barometer.formatted)
in the index.html.tmpl results in the correct formatting.


jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 20:09:30 UTC+2:

> I had a look.  You never actually write FMT_windDir in the JavaScript. 
>  Just add:
> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
> on the appropriate line in realtime_updater.inc.
>
> As for barometerRate.  I do see it.  I just spills over to the next line. 
>  It looks like I am not properly formatting barometerRate.  I will fix that 
> as part of the 2.0 release which I am working on and hope to have out this 
> weekend.
>
> On Jul 10, 2020, at 9:03 AM, geni08...@gmail.com  
> wrote:
>
>  
>
> Hi John, I'm on the mountain, there was more. Can you please keep an eye 
> on the two files?
>
>
> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:
>
>> You need to add the fields:
>> barometerRate
>> FMT_windDir
>> to the fields line in the LoopData section of weewx.conf.
>>
>> After you do that and restart WeeWX, verify that you see these readings 
>> in loop-data.txt.
>>
>> Finally, you need to set these values in the JavaScript.
>>
>> If you have already done all of the above, perhaps you have a JavaScript 
>> error.  Have a look in the JavaScript console in your browser (note: it may 
>> be called something else, search for how to see JavaScript errors).
>>
>> BTW, this weekend, I should have a version of LoopData out that uses the 
>> same naming scheme as cheetah.  As such, you will then specify 
>> $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
>> (for example) in the fields line in weewx.conf and those keys will show up 
>> in loop-data.txt.  There was no good reason to invent a new language for 
>> this. 
>>
>> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>>
>> what do I have to change so that the two values (in the yellow circle) 
>> are always displayed? Now they only flash briefly during a manual 
>> refresh.
>>
>> 
>>
>> in index.html.templ:
>>  > style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>>  
>> $current.windDir.ordinal_compass ($current.windDir)
>> $current.barometer 
>> ($trend.barometer.formatted) - > id="FMT_outHumidity">$current.outHumidity
>>
>> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 
>> UTC+2:
>>
>>>
>>>
>>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>> Question for my understanding:
>>>
>>>
>>> If or why is the id = string supplemented with $current, $day or not at 
>>> all?
>>>
>>> 
>>>
>>>
>>> In the examples, no IDs is supplemented with current, day or none at 
>>> all.  Some values say $current, which means the current observation.  Some 
>>> say day, which would be for the day and have an aggregator ($day.rain.sum). 
>>>  In any event, all of these values are overwritten every couple of seconds 
>>> by the javascript.  As such, they could be removed.
>>>
>>> As for the ids.  They could be anything you wish.  They just are used by 
>>> the JavaScript to look up the element.  As a naming scheme for ids, I chose 
>>> to to name them for the corresponding key in loop-data.txt.
>>>
>>> For example, FMT_HI_windGust.  The JavaScript will get lookup the 
>>> element with the id FMT_HI_windGust.  It will then lookup the value in 
>>> loop-data.txt for the key FMT_HI_windGust and set the contents of the HTML 
>>> tag (innerHTML property) to that value.
>>>
>>> If the id was foo on this element, the JavaScript would have to find the 
>>> foo element in the DOM.  Of course, it will still need to use the key 
>>> FMT_HI_windGust for looking up the loop-data value.
>>>
>>> As for the naming scheme in loop-data.txt:
>>> FMT_HI_windGust
>>> The FMT_ means include the label.
>>> The HI_ means give me today’s high.
>>>
>>> FMT_windGust would be for the current observation and would include the 
>>> label.
>>>
>>> windGust would be for the current observation. It would NOT include a 
>>> label, but it would still be formatted.  That is, if wind should have 1 
>>> decimal place, it be formatted as such (e.g., 4.0).
>>>
>>> The README has

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 Hi John, I'm on the mountain, there was more. Can you please keep an eye 
on the two files?


jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:

> You need to add the fields:
> barometerRate
> FMT_windDir
> to the fields line in the LoopData section of weewx.conf.
>
> After you do that and restart WeeWX, verify that you see these readings in 
> loop-data.txt.
>
> Finally, you need to set these values in the JavaScript.
>
> If you have already done all of the above, perhaps you have a JavaScript 
> error.  Have a look in the JavaScript console in your browser (note: it may 
> be called something else, search for how to see JavaScript errors).
>
> BTW, this weekend, I should have a version of LoopData out that uses the 
> same naming scheme as cheetah.  As such, you will then specify 
> $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
> (for example) in the fields line in weewx.conf and those keys will show up 
> in loop-data.txt.  There was no good reason to invent a new language for 
> this. 
>
> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
> wrote:
>
>  
>
> what do I have to change so that the two values (in the yellow circle) are 
> always displayed? Now they only flash briefly during a manual refresh.
>
> 
>
> in index.html.templ:
>   style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>  
> $current.windDir.ordinal_compass ($current.windDir)
> $current.barometer 
> ($trend.barometer.formatted) -  id="FMT_outHumidity">$current.outHumidity
>
> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 UTC+2:
>
>>
>>
>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>> wrote:
>>
>> Question for my understanding:
>>
>>
>> If or why is the id = string supplemented with $current, $day or not at 
>> all?
>>
>> 
>>
>>
>> In the examples, no IDs is supplemented with current, day or none at all. 
>>  Some values say $current, which means the current observation.  Some say 
>> day, which would be for the day and have an aggregator ($day.rain.sum).  In 
>> any event, all of these values are overwritten every couple of seconds by 
>> the javascript.  As such, they could be removed.
>>
>> As for the ids.  They could be anything you wish.  They just are used by 
>> the JavaScript to look up the element.  As a naming scheme for ids, I chose 
>> to to name them for the corresponding key in loop-data.txt.
>>
>> For example, FMT_HI_windGust.  The JavaScript will get lookup the element 
>> with the id FMT_HI_windGust.  It will then lookup the value in 
>> loop-data.txt for the key FMT_HI_windGust and set the contents of the HTML 
>> tag (innerHTML property) to that value.
>>
>> If the id was foo on this element, the JavaScript would have to find the 
>> foo element in the DOM.  Of course, it will still need to use the key 
>> FMT_HI_windGust for looking up the loop-data value.
>>
>> As for the naming scheme in loop-data.txt:
>> FMT_HI_windGust
>> The FMT_ means include the label.
>> The HI_ means give me today’s high.
>>
>> FMT_windGust would be for the current observation and would include the 
>> label.
>>
>> windGust would be for the current observation. It would NOT include a 
>> label, but it would still be formatted.  That is, if wind should have 1 
>> decimal place, it be formatted as such (e.g., 4.0).
>>
>> The README has this info, but to summarize:
>>
>> If the key is missing an aggregator (HI, LO, AVG, WAVG, SUM, RMS, 
>> VEC_AVG, VEC_DIR), it is the current observation.  If it has an aggregator 
>> prefix, it is for the day.  Exceptions are the items I made up 10mMaxGust 
>> (which is 10 minutes) and barometerRate (which is a delta from 3 hours ago) 
>> and windRose.
>>
>> FMT_ includes the label.
>>
>> UNITS_ is the unit for the observation.
>>
>> LABEL_ is the label for the observation.
>>
>> COMPASS_ for windDIr and windGustDir gives compass (text) direction.
>>
>> DESC_ for barometer rate gives a text description of the rate (and 
>> probably needs to be internationalized).
>>
>> T_ is the time of the observation.  For example, T_HI_ would be the 
>> time today that the high was reached for the observation.
>>
>> Just to mention the other things you pointed to:
>> FMT_SUM_rain is today’s rain with a label.  The FMT_ gives the label. 
>>  Since SUM_ is an aggregator, it is for today.
>>
>> FMT_rainRate is the current rate of rain (si

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

Question for my understanding:
If or why is the id = string supplemented with $current, $day or not at all?
[image: loop1.jpg]

jo...@johnkline.com schrieb am Mittwoch, 8. Juli 2020 um 20:35:22 UTC+2:

>
>
> On Jul 8, 2020, at 1:36 AM, geni08...@gmail.com  
> wrote:
>
>  weewx-weatherboard 1.3a the label entries are implemented.
>
>
> What is the easiest way now
> Indoor temperature
> barometer
> Indoor and outdoor humidity
> to show signs on the display?
>
>
>
> To get these readings in loop-data.txt, add the following to the end of 
> the fields line in the LoopData section of weewx.conf:
> , FMT_inTemp, FMT_barometer, FMT_inHumidity, FMT_outHumidity
>
> As for adding them to a skin, it would be helpful to know your end goal 
> and your familiarity with the technologies.
>
> WeatherBoard is designed for display on a tablet sitting on a bookshelf or 
> hanging on a wall.  It’s meant to be viewed from across the room.  That’s 
> why there’s a small amount of data in large fonts and why I chose the color 
> scheme.
>
> Are you trying to have something that looks like WeatherBoard but just 
> these four extra items on it?  Will you want more after you add these four? 
>  Extra items will mean smaller fonts.  How will this skin be viewed?  I’m 
> assuming you are not looking for the across the room viewing that I 
> targeted with this skin.
>
> Are you looking to write an entirely new skin?
>
> Are you looking to add “update on every loop” capabilities to another skin 
> that you like?
>
> How comfortable are you working with html, css and JavaScript?
>
> Cheers,
> John
>
>
> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2:
>
>> Most of the WeatherBoard will now use the strings in Defaults, so you 
>> should see it in German after you install.  For the custom strings, just 
>> update the strings in the WeatherBoard>Labels>Generic section of weewx.conf.
>>
>> On Jul 7, 2020, at 6:47 AM, John Kline  wrote:
>>
>> 
>>
>> I’ve created a branch of WeatherBoard that substitutes appTemp for 
>> dewpoint.
>>
>> It is here:
>> https://github.com/chaunceygardiner/weewx-weatherboard/tree/appTemp
>>
>> On Jul 7, 2020, at 12:09 AM, John Kline  wrote:
>>
>> 
>> There was a subtle difference in how I was creating the next day 
>> accumulator vs. how WeeWX proper is doing it.  I’ve changed that.  Please 
>> install 1.3.15 and let me know how it goes at midnight.
>>
>> On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com  
>> wrote:
>>
>> Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
>> swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com";] 
>> rsyslogd was HUPed
>> Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
>> Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
>> Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
>> Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db 
>> regeneration.
>> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added 
>> record 2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
>> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added 
>> record 2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'
>>
>>
>> geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:
>>
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   Traceback (most recent call last):
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   self.day_accum.addRecord(pkt)
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   % (record['dateTime'], self.timespan))
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>>> 2020-07-07 00:00:00 CEST (1594072800)])
>>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>>   
>>> Jul  7 00:00:

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 weewx-weatherboard 1.3a the label entries are implemented.
What is the easiest way now
Indoor temperature
barometer
Indoor and outdoor humidity
to show signs on the display? 

jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2:

> Most of the WeatherBoard will now use the strings in Defaults, so you 
> should see it in German after you install.  For the custom strings, just 
> update the strings in the WeatherBoard>Labels>Generic section of weewx.conf.
>
> On Jul 7, 2020, at 6:47 AM, John Kline  wrote:
>
> 
>
> I’ve created a branch of WeatherBoard that substitutes appTemp for 
> dewpoint.
>
> It is here:
> https://github.com/chaunceygardiner/weewx-weatherboard/tree/appTemp
>
> On Jul 7, 2020, at 12:09 AM, John Kline  wrote:
>
> 
> There was a subtle difference in how I was creating the next day 
> accumulator vs. how WeeWX proper is doing it.  I’ve changed that.  Please 
> install 1.3.15 and let me know how it goes at midnight.
>
> On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com  
> wrote:
>
> Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
> swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com";] 
> rsyslogd was HUPed
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db regeneration.
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'
>
>
> geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:
>
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>> 2020-07-07 00:00:00 CEST (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   During handling of the above exception, another exception occurred:
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>> 2020-07-07 00:00:00 CEST (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Rotate log files...
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Daily man-db 
>> regeneration...
>>
>>
>> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 07:09:28 UTC+2:
>>
>>> It looks like loopdata stopped again at midnight (I looked at your 
>>> sight).
>>>
>>> I think it likely that something in the packet at midnight is causing 
>>> this.  Loopdata does print

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

no error in the log file, and weewx-loopdate has mastered midnight.

I will look at weewx-weatherboard in a moment

jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 20:10:24 UTC+2:

> Most of the WeatherBoard will now use the strings in Defaults, so you 
> should see it in German after you install.  For the custom strings, just 
> update the strings in the WeatherBoard>Labels>Generic section of weewx.conf.
>
> On Jul 7, 2020, at 6:47 AM, John Kline  wrote:
>
> 
>
> I’ve created a branch of WeatherBoard that substitutes appTemp for 
> dewpoint.
>
> It is here:
> https://github.com/chaunceygardiner/weewx-weatherboard/tree/appTemp
>
> On Jul 7, 2020, at 12:09 AM, John Kline  wrote:
>
> 
> There was a subtle difference in how I was creating the next day 
> accumulator vs. how WeeWX proper is doing it.  I’ve changed that.  Please 
> install 1.3.15 and let me know how it goes at midnight.
>
> On Jul 6, 2020, at 10:44 PM, geni08...@gmail.com  
> wrote:
>
> Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
> swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com";] 
> rsyslogd was HUPed
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
> Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
> Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db regeneration.
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
> Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
> 2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'
>
>
> geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:
>
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>> 2020-07-07 00:00:00 CEST (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   During handling of the above exception, another exception occurred:
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   self.day_accum.addRecord(pkt)
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   % (record['dateTime'], self.timespan))
>> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
>> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
>> 2020-07-07 00:00:00 CEST (1594072800)])
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Rotate log files...
>> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Daily man-db 
>> regeneration...
>>
>>
>> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 07:09:28 UTC+2:
>>
>>> It looks like loopdata stopped again at midnight (I looked at your 
>>> sight).
>>>
>>> I think it likely that something in the packet at midnight is causing 
>>> this.  Loopdata does print a stack trace on an unexpected exception before 
>>> e

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

Jul  7 00:00:01 Wetter-Raspi rsyslogd:  [origin software="rsyslogd" 
swVersion="8.1901.0" x-pid="295" x-info="https://www.rsyslog.com";] rsyslogd 
was HUPed
Jul  7 00:00:01 Wetter-Raspi systemd[1]: logrotate.service: Succeeded.
Jul  7 00:00:01 Wetter-Raspi systemd[1]: Started Rotate log files.
Jul  7 00:00:02 Wetter-Raspi systemd[1]: man-db.service: Succeeded.
Jul  7 00:00:02 Wetter-Raspi systemd[1]: Started Daily man-db regeneration.
Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
2020-07-07 00:00:00 CEST (1594072800) to database 'weewx'
Jul  7 00:00:15 Wetter-Raspi weewx[18476] INFO weewx.manager: Added record 
2020-07-07 00:00:00 CEST (1594072800) to daily summary in 'weewx'


geni08...@gmail.com schrieb am Dienstag, 7. Juli 2020 um 07:39:52 UTC+2:

> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   self.day_accum.addRecord(pkt)
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   % (record['dateTime'], self.timespan))
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
> 2020-07-07 00:00:00 CEST (1594072800)])
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   During handling of the above exception, another exception occurred:
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   self.day_accum.addRecord(pkt)
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   % (record['dateTime'], self.timespan))
> Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
>   weewx.accum.OutOfSpan: Attempt to add out-of-interval record 
> (1594072801) to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 
> 2020-07-07 00:00:00 CEST (1594072800)])
> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Rotate log files...
> Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Daily man-db 
> regeneration...
>
>
> jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 07:09:28 UTC+2:
>
>> It looks like loopdata stopped again at midnight (I looked at your sight).
>>
>> I think it likely that something in the packet at midnight is causing 
>> this.  Loopdata does print a stack trace on an unexpected exception before 
>> exiting.  Would you have a look in the log and send it?
>>
>> If the stack trace doesn’t give me the info I need, I will send you an 
>> instrumented version of loopdata.py that will, among other things, log loop 
>> packets around midnight.
>>
>> On Jul 6, 2020, at 10:26 AM, John Kline  wrote:
>>
>> 
>>
>> BTW, I should probably make dewpoint position on the weatherboard 
>> configurable between dewpoint and appTemp.  That would save you from having 
>> to hack on the javaascript.
>>
>> Also, I could make the legend configurable for translation.
>>
>> I’ll try to do that today or tomorrow.
>>
>> On Jul 6, 2020, at 10:19 AM, John Kline  wrote:
>>
>> 
>> Yep, you’ll need to make your changes to switch to appTemp.  That’s both 
>> a change in index.html.tmpl and in the realtime_updater.inc file.
>>
>> A new day accumulator gets created at midnight, so I am very interested 
>> in that loopdata crash.  Do you have a stacktrace in the log?  Please send 
>> what you have.  If it’s not descriptive enough, I’ll update loopdata to 
>> provide more info on that crash.
>>
>> On Jul 6, 2020, at 8:20 AM, geni08...@gmail.com  
>> wrote:

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
Traceback (most recent call last):
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
File "/usr/share/weewx/user/loopdata.py", line 365, in process_queue
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
  self.day_accum.addRecord(pkt)
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
  % (record['dateTime'], self.timespan))
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
weewx.accum.OutOfSpan: Attempt to add out-of-interval record (1594072801) 
to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 2020-07-07 00:00:00 
CEST (1594072800)])
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
During handling of the above exception, another exception occurred:
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
Traceback (most recent call last):
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
File "/usr/share/weewx/user/loopdata.py", line 370, in process_queue
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
  self.day_accum.addRecord(pkt)
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
File "/usr/share/weewx/weewx/accum.py", line 423, in addRecord
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata: 
  % (record['dateTime'], self.timespan))
Jul  7 00:00:00 Wetter-Raspi weewx[18476] CRITICAL user.loopdata:   
weewx.accum.OutOfSpan: Attempt to add out-of-interval record (1594072801) 
to timespan ([2020-07-06 00:00:00 CEST (1593986400) -> 2020-07-07 00:00:00 
CEST (1594072800)])
Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Rotate log files...
Jul  7 00:00:00 Wetter-Raspi systemd[1]: Starting Daily man-db 
regeneration...


jo...@johnkline.com schrieb am Dienstag, 7. Juli 2020 um 07:09:28 UTC+2:

> It looks like loopdata stopped again at midnight (I looked at your sight).
>
> I think it likely that something in the packet at midnight is causing 
> this.  Loopdata does print a stack trace on an unexpected exception before 
> exiting.  Would you have a look in the log and send it?
>
> If the stack trace doesn’t give me the info I need, I will send you an 
> instrumented version of loopdata.py that will, among other things, log loop 
> packets around midnight.
>
> On Jul 6, 2020, at 10:26 AM, John Kline  wrote:
>
> 
>
> BTW, I should probably make dewpoint position on the weatherboard 
> configurable between dewpoint and appTemp.  That would save you from having 
> to hack on the javaascript.
>
> Also, I could make the legend configurable for translation.
>
> I’ll try to do that today or tomorrow.
>
> On Jul 6, 2020, at 10:19 AM, John Kline  wrote:
>
> 
> Yep, you’ll need to make your changes to switch to appTemp.  That’s both a 
> change in index.html.tmpl and in the realtime_updater.inc file.
>
> A new day accumulator gets created at midnight, so I am very interested in 
> that loopdata crash.  Do you have a stacktrace in the log?  Please send 
> what you have.  If it’s not descriptive enough, I’ll update loopdata to 
> provide more info on that crash.
>
> On Jul 6, 2020, at 8:20 AM, geni08...@gmail.com  
> wrote:
>
>  
> I have replaced the index.html.tmpl with an old version! However, the 
> appTemp is not yet running. Loopdate also crashed at midnight, so watch 
> that today.
>
> jo...@johnkline.com schrieb am Montag, 6. Juli 2020 um 15:50:11 UTC+2:
>
>> Now that I’m up for the morning, I went to look at your WeatherBoard page 
>> to see what the JavaScript error was, but I see that it is up and runnning!
>>
>> On Jul 6, 2020, at 3:44 AM, John Kline  wrote:
>>
>> 
>>
>> Send realtime_updater.inc and weewx.conf.
>> The JavaScript is broken. I’ll have a look.
>>
>> On Jul 5, 2020, at 10:35 PM, geni08...@gmail.com  
>> wrote:
>>
>> I have weewx-loopdata 1.1.13, only the default km_per_hour definition -> 
>> the loop-data.txt is OK.
>> Why is my WeatherBoard not working? Only time is running.
>>
>> -- 
>> 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.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 I have replaced the index.html.tmpl with an old version! However, the 
appTemp is not yet running. Loopdate also crashed at midnight, so watch 
that today.

jo...@johnkline.com schrieb am Montag, 6. Juli 2020 um 15:50:11 UTC+2:

> Now that I’m up for the morning, I went to look at your WeatherBoard page 
> to see what the JavaScript error was, but I see that it is up and runnning!
>
> On Jul 6, 2020, at 3:44 AM, John Kline  wrote:
>
> 
>
> Send realtime_updater.inc and weewx.conf.
> The JavaScript is broken. I’ll have a look.
>
> On Jul 5, 2020, at 10:35 PM, geni08...@gmail.com  
> wrote:
>
> I have weewx-loopdata 1.1.13, only the default km_per_hour definition -> 
> the loop-data.txt is OK.
> Why is my WeatherBoard not working? Only time is running.
>
> -- 
> 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/b24a6c1c-9b40-4c1b-abde-cf1c40d127e2n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/b24a6c1c-9b40-4c1b-abde-cf1c40d127e2n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 
>
>

-- 
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/441af783-906b-4497-a023-733da7ec6cc3n%40googlegroups.com.

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

I have weewx-loopdata 1.1.13, only the default km_per_hour definition -> 
the loop-data.txt is OK.
Why is my WeatherBoard not working? Only time is running.

-- 
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/b24a6c1c-9b40-4c1b-abde-cf1c40d127e2n%40googlegroups.com.
## Copyright (C)2020 by John A Kline (j...@johnkline.com)
## Distributed under the terms of the GNU Public License (GPLv3)
## See LICENSE for your rights.
#errorCatcher Echo
#encoding UTF-8


  



#if $Extras.has_key('meta_title')
  $Extras.meta_title
#else
  WeatherBoard™—$station.location
#end if


  #centered {
width:100%;
margin: auto;
  }

  
  
#include "analytics.inc"
#include "realtime_updater.inc"

  

  
#if $Extras.has_key('logo') and $Extras.logo != ''
  

  
#else
  
  
#end if

  
#if $Extras.has_key('title')
  $Extras.title
#else
  WeatherBoard™
#end if
  
  
#if $Extras.has_key('subtitle')
  $Extras.subtitle
#else
  Updated continuously.
#end if
  


   

  

  



  

  


  
  

  
$current.outTemp $current.appTemp
  
  
$current.windSpeed
 $current.windDir.ordinal_compass
  
  
 — 

  
  
$day.rain.sum — $current.rainRate
  

  

  

#include "footer.inc"
  

[weewx-user] Re: Belchertown: current weather picture is missing.

[geni08...@gmail.com]

 how is Belchertown updated, what do you have to be careful about between 
release and beta versions? 

Pat schrieb am Freitag, 26. Juni 2020 um 18:32:22 UTC+2:

> Yes you need to use DarkSky or Aeris weather (with the 1.2 beta skin)
>
>
> On Friday, June 26, 2020 at 11:09:46 AM UTC-4, geni08...@gmail.com wrote:
>>
>> I have to configure or install so that this info picture is displayed? 
>> [image: 
>> belch07.jpg]What do 
>>
>> It looks like this to me
>> [image: belch08.jpg]
>>
>

-- 
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/42d2aab3-db56-47b9-a4bc-5980a136b87bn%40googlegroups.com.

[weewx-user] Belchertown: current weather picture is missing.

[geni08...@gmail.com]

 I have to configure or install so that this info picture is displayed? [image: 
belch07.jpg]What do 

It looks like this to me
[image: belch08.jpg]

-- 
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/cc8c6283-fc64-4261-86d6-48716b0cede6n%40googlegroups.com.

[weewx-user] Belchertown: current weather picture is missing

[geni08...@gmail.com]

 What do I have to configure or install so that this info picture is 
displayed?


It looks like this to me:

-- 
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/d7d4102b-95c4-4883-ba83-f3eb28f8c654n%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[geni08...@gmail.com]

@Manfred: Danke, werde dann mal die nächste Woche einen ersten Versuch 
starten :)

Manfred Maier schrieb am Freitag, 26. Juni 2020 um 11:20:48 UTC+2:

> Sorry. Hatte ich vergessen.
>
> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 11:13:44 UTC+2:
>
>> Kannst  du deine extensions.py bitte hier reinstellen?
>>
>>
>> Manfred Maier schrieb am Freitag, 26. Juni 2020 um 10:41:53 UTC+2:
>>
>>> Ich habe meine Datenbank inzwischen schon zweimal erweitert. Einmal nach 
>>> ca. drei Wochen (um appTemp und maxSolarRad in der Datenbank zu haben) und 
>>> dann nochmal letzte Woche, um endlich auch die Anzahl der Sonnenstunden 
>>> schön darstellen zu können.
>>>
>>> Beide Male hat es absolut ohne Probleme funktioniert. 
>>> Schau einfach nur, dass Du ein Backup der Datenbank hast, sollte 
>>> wirklich etwas schief laufen.
>>>
>>> Mit Mariadb10 habe ich leider keinerlei Erfahrung. 
>>> Bei meiner Installation (mit SQLite) wird einfach nur die existierende 
>>> DB erweitert.
>>>
>>> Und bei der Installation der Skin ist es einfach nicht sinnvoll, an der 
>>> Datenbank rumzuspielen. 
>>>
>>> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 10:27:06 UTC+2:
>>>
>>>> @Manfred: Hast du dies schon mal gemacht? Wenn ja ohne Probleme?
>>>> Bleibt dies eine einmalige Sache oder wird dies bei jedem Update von 
>>>> weewx oder Belchertown wieder fällig?
>>>> Wie muss dann die extensions.py aussehen?
>>>> Ich verwende eine externe Mariadb10, wird nun eine neue DB gemacht oder 
>>>> die bestehende modifiziert?
>>>> Dies funktioniert auf meinem Raspberry ja nicht?
>>>> Warum wird dies nicht von der Belchertown installation gemacht?
>>>>
>>>> Bin da für jede Hilfe dankbar.
>>>>
>>>> Manfred Maier schrieb am Freitag, 26. Juni 2020 um 07:59:42 UTC+2:
>>>>
>>>>> Good morning!
>>>>> You can use these instructions to add appTemp to your database:
>>>>>
>>>>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>>>>
>>>>> Just make sure you really have a backup of your database stored.
>>>>>
>>>>> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 07:43:08 
>>>>> UTC+2:
>>>>>
>>>>>> There are errors, a test with $current.appTemp and once with appTemp.
>>>>>> The appTemp field is not in the database, how can I modify my 
>>>>>> database?
>>>>>>
>>>>>>
>>>>>> Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:
>>>>>>
>>>>>>> Good question. If appTemp doesn't exist in the database, then I 
>>>>>>> would have thought the entry would be empty or given an error in the 
>>>>>>> syslog. Any errors?
>>>>>>>
>>>>>>>
>>>>>>> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>>>>>>>
>>>>>>>> Ok. I've just seen that appTemp is not part of the standard 
>>>>>>>> installation of weewx. I've added it later to the database.
>>>>>>>>
>>>>>>>> @Pat: In your index.html.tmpl it looks like your are displaying 
>>>>>>>> $current.appTemp for the "Feels like" temperature. What is used when 
>>>>>>>> appTemp does not exist in the database? Or is appTemp calculated by 
>>>>>>>> weewx 
>>>>>>>> anyway, but if there isn't a field in the database it's just not 
>>>>>>>> stored and 
>>>>>>>> can't be used for the charts?
>>>>>>>>
>>>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>>>>>>> 19:22:55 UTC+2:
>>>>>>>>
>>>>>>>>> if appTemp instead of windchill, graphics no longer work
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>>>>>>>>>
>>>>>>>>>> appTemp is best translated with "Gefühlte Temperatur".
>>>>>>>>>>
>>>>>>>>>> I 

[weewx-user] Re: Belchertown Difference for the same temperature type

[geni08...@gmail.com]

Kannst  du deine extensions.py bitte hier reinstellen?


Manfred Maier schrieb am Freitag, 26. Juni 2020 um 10:41:53 UTC+2:

> Ich habe meine Datenbank inzwischen schon zweimal erweitert. Einmal nach 
> ca. drei Wochen (um appTemp und maxSolarRad in der Datenbank zu haben) und 
> dann nochmal letzte Woche, um endlich auch die Anzahl der Sonnenstunden 
> schön darstellen zu können.
>
> Beide Male hat es absolut ohne Probleme funktioniert. 
> Schau einfach nur, dass Du ein Backup der Datenbank hast, sollte wirklich 
> etwas schief laufen.
>
> Mit Mariadb10 habe ich leider keinerlei Erfahrung. 
> Bei meiner Installation (mit SQLite) wird einfach nur die existierende DB 
> erweitert.
>
> Und bei der Installation der Skin ist es einfach nicht sinnvoll, an der 
> Datenbank rumzuspielen. 
>
> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 10:27:06 UTC+2:
>
>> @Manfred: Hast du dies schon mal gemacht? Wenn ja ohne Probleme?
>> Bleibt dies eine einmalige Sache oder wird dies bei jedem Update von 
>> weewx oder Belchertown wieder fällig?
>> Wie muss dann die extensions.py aussehen?
>> Ich verwende eine externe Mariadb10, wird nun eine neue DB gemacht oder 
>> die bestehende modifiziert?
>> Dies funktioniert auf meinem Raspberry ja nicht?
>> Warum wird dies nicht von der Belchertown installation gemacht?
>>
>> Bin da für jede Hilfe dankbar.
>>
>> Manfred Maier schrieb am Freitag, 26. Juni 2020 um 07:59:42 UTC+2:
>>
>>> Good morning!
>>> You can use these instructions to add appTemp to your database:
>>>
>>> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>>>
>>> Just make sure you really have a backup of your database stored.
>>>
>>> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 07:43:08 UTC+2:
>>>
>>>> There are errors, a test with $current.appTemp and once with appTemp.
>>>> The appTemp field is not in the database, how can I modify my database?
>>>>
>>>>
>>>> Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:
>>>>
>>>>> Good question. If appTemp doesn't exist in the database, then I would 
>>>>> have thought the entry would be empty or given an error in the syslog. 
>>>>> Any 
>>>>> errors?
>>>>>
>>>>>
>>>>> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>>>>>
>>>>>> Ok. I've just seen that appTemp is not part of the standard 
>>>>>> installation of weewx. I've added it later to the database.
>>>>>>
>>>>>> @Pat: In your index.html.tmpl it looks like your are displaying 
>>>>>> $current.appTemp for the "Feels like" temperature. What is used when 
>>>>>> appTemp does not exist in the database? Or is appTemp calculated by 
>>>>>> weewx 
>>>>>> anyway, but if there isn't a field in the database it's just not stored 
>>>>>> and 
>>>>>> can't be used for the charts?
>>>>>>
>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
>>>>>> UTC+2:
>>>>>>
>>>>>>> if appTemp instead of windchill, graphics no longer work
>>>>>>>
>>>>>>>
>>>>>>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>>>>>>>
>>>>>>>> appTemp is best translated with "Gefühlte Temperatur".
>>>>>>>>
>>>>>>>> I would have to look it up in the weewx code, but I think it's 
>>>>>>>> calculated based on temperature, humidity and wind.
>>>>>>>> appTemp can be higher or lower than the temperature.
>>>>>>>>
>>>>>>>> Windchill is normally (always?) lower than the temperature. It's 
>>>>>>>> therefore primarily used in winter. At least in the German news I only 
>>>>>>>> hear 
>>>>>>>> about it in winter.
>>>>>>>>
>>>>>>>> Heat Index is the opposite. It's normally (always?) higher than the 
>>>>>>>> temperature. It useful in the summer.
>>>>>>>>
>>>>>>>> Other people might want to add or correct me here!
>>>>>>>>
>>&g

[weewx-user] Re: Belchertown Difference for the same temperature type

[geni08...@gmail.com]

@Manfred: Hast du dies schon mal gemacht? Wenn ja ohne Probleme?
Bleibt dies eine einmalige Sache oder wird dies bei jedem Update von weewx 
oder Belchertown wieder fällig?
Wie muss dann die extensions.py aussehen?
Ich verwende eine externe Mariadb10, wird nun eine neue DB gemacht oder die 
bestehende modifiziert?
Dies funktioniert auf meinem Raspberry ja nicht?
Warum wird dies nicht von der Belchertown installation gemacht?

Bin da für jede Hilfe dankbar.

Manfred Maier schrieb am Freitag, 26. Juni 2020 um 07:59:42 UTC+2:

> Good morning!
> You can use these instructions to add appTemp to your database:
>
> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>
> Just make sure you really have a backup of your database stored.
>
> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 07:43:08 UTC+2:
>
>> There are errors, a test with $current.appTemp and once with appTemp.
>> The appTemp field is not in the database, how can I modify my database?
>>
>>
>> Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:
>>
>>> Good question. If appTemp doesn't exist in the database, then I would 
>>> have thought the entry would be empty or given an error in the syslog. Any 
>>> errors?
>>>
>>>
>>> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>>>
>>>> Ok. I've just seen that appTemp is not part of the standard 
>>>> installation of weewx. I've added it later to the database.
>>>>
>>>> @Pat: In your index.html.tmpl it looks like your are displaying 
>>>> $current.appTemp for the "Feels like" temperature. What is used when 
>>>> appTemp does not exist in the database? Or is appTemp calculated by weewx 
>>>> anyway, but if there isn't a field in the database it's just not stored 
>>>> and 
>>>> can't be used for the charts?
>>>>
>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
>>>> UTC+2:
>>>>
>>>>> if appTemp instead of windchill, graphics no longer work
>>>>>
>>>>>
>>>>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>>>>>
>>>>>> appTemp is best translated with "Gefühlte Temperatur".
>>>>>>
>>>>>> I would have to look it up in the weewx code, but I think it's 
>>>>>> calculated based on temperature, humidity and wind.
>>>>>> appTemp can be higher or lower than the temperature.
>>>>>>
>>>>>> Windchill is normally (always?) lower than the temperature. It's 
>>>>>> therefore primarily used in winter. At least in the German news I only 
>>>>>> hear 
>>>>>> about it in winter.
>>>>>>
>>>>>> Heat Index is the opposite. It's normally (always?) higher than the 
>>>>>> temperature. It useful in the summer.
>>>>>>
>>>>>> Other people might want to add or correct me here!
>>>>>>
>>>>>> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
>>>>>> Temperature" in Germany (and hopefully also in Switzerland).
>>>>>> Have you tried to put appTemp in your chart? Does the value 
>>>>>> correspond to the other value on your page?
>>>>>>
>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
>>>>>> UTC+2:
>>>>>>
>>>>>>> what is appTemp?
>>>>>>> windchill corresponds to 'feels like'?
>>>>>>>
>>>>>>>
>>>>>>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>>>>>>>
>>>>>>>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>>>>>>>> figure at the top.
>>>>>>>>
>>>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>>>>>>> 17:16:32 UTC+2:
>>>>>>>>
>>>>>>>>> in graphs.inc is  [[[windchill]]]
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>>>>>>>>>
>>>>>>>>>> Next try ... the

[weewx-user] Re: Belchertown Difference for the same temperature type

[geni08...@gmail.com]

 There are errors, a test with $current.appTemp and once with appTemp.
The appTemp field is not in the database, how can I modify my database?


Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:

> Good question. If appTemp doesn't exist in the database, then I would have 
> thought the entry would be empty or given an error in the syslog. Any 
> errors?
>
>
> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:
>>
>> Ok. I've just seen that appTemp is not part of the standard installation 
>> of weewx. I've added it later to the database.
>>
>> @Pat: In your index.html.tmpl it looks like your are displaying 
>> $current.appTemp for the "Feels like" temperature. What is used when 
>> appTemp does not exist in the database? Or is appTemp calculated by weewx 
>> anyway, but if there isn't a field in the database it's just not stored and 
>> can't be used for the charts?
>>
>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 19:22:55 
>> UTC+2:
>>
>>> if appTemp instead of windchill, graphics no longer work
>>>
>>>
>>> Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>>>>
>>>> appTemp is best translated with "Gefühlte Temperatur".
>>>>
>>>> I would have to look it up in the weewx code, but I think it's 
>>>> calculated based on temperature, humidity and wind.
>>>> appTemp can be higher or lower than the temperature.
>>>>
>>>> Windchill is normally (always?) lower than the temperature. It's 
>>>> therefore primarily used in winter. At least in the German news I only 
>>>> hear 
>>>> about it in winter.
>>>>
>>>> Heat Index is the opposite. It's normally (always?) higher than the 
>>>> temperature. It useful in the summer.
>>>>
>>>> Other people might want to add or correct me here!
>>>>
>>>> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
>>>> Temperature" in Germany (and hopefully also in Switzerland).
>>>> Have you tried to put appTemp in your chart? Does the value correspond 
>>>> to the other value on your page?
>>>>
>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
>>>> UTC+2:
>>>>
>>>>> what is appTemp?
>>>>> windchill corresponds to 'feels like'?
>>>>>
>>>>>
>>>>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>>>>>
>>>>>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>>>>>> figure at the top.
>>>>>>
>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
>>>>>> UTC+2:
>>>>>>
>>>>>>> in graphs.inc is  [[[windchill]]]
>>>>>>>
>>>>>>>
>>>>>>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>>>>>>>
>>>>>>>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>>>>>>>> "appTemp"?
>>>>>>>>
>>>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>>>>>>> 16:43:53 UTC+2:
>>>>>>>>
>>>>>>>>> MQTT ist not activ.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>>>>>>>>
>>>>>>>>>> Hi Geni,
>>>>>>>>>> do you have MQTT switched on?
>>>>>>>>>>
>>>>>>>>>> If so, the station observations (top area) display the live data. 
>>>>>>>>>> The charts display the temperature of the last archive loop (= 
>>>>>>>>>> couple of 
>>>>>>>>>> minutes old).
>>>>>>>>>>
>>>>>>>>>> Manfred
>>>>>>>>>>
>>>>>>>>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>>>>>>>>> 15:42:15 UTC+2:
>>>>>>>>>>
>>>>>>>>>>> Why is there