date:20240117

Good morning,
I followed the steps in the guide and I get this error

python3 -m pip install weewx
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Collecting weewx
  Downloading 
https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl (1.4 MB)
 || 1.4 MB 531 kB/s
Collecting pyserial<4.0,>=3.4
  Downloading 
https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl 
(90 kB)
 || 90 kB 450 kB/s
Collecting ephem<5.0,>=4.1
  Downloading 
https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl 
(1.7 MB)
 || 1.7 MB 851 kB/s
Collecting pyusb<2.0.0,>=1.0.2
  Downloading 
https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl (58 kB)
 || 58 kB 602 kB/s
Collecting configobj<6.0,>=5.0
  Downloading 
https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl 
(35 kB)
Collecting Pillow>=5.2
  Downloading 
https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl 
(1.2 MB)
 || 1.2 MB 988 kB/s
Collecting CT3<4.0,>=3.1
  Downloading 
https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
(196 kB)
 || 196 kB 569 kB/s
Collecting PyMySQL<2.0,>=1.0
  Downloading 
https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl (44 
kB)
 || 44 kB 271 kB/s
Collecting six
  Downloading 
https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl (11 kB)
Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
ephem, CT3, configobj, weewx
Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 weewx-5.0.0
(weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
--config=/home/weewx/weewx.conf
Using configuration file /home/weewx/weewx.conf

Upgrade examples, utility files in /home/weewx (Y/n)? Y
Removing example directory /home/weewx/examples
Copying examples into /home/weewx/examples
Traceback (most recent call last):
  File "/home/pi/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
line 339, in upgrade_station
weectllib.station_actions.station_upgrade(config_dict=config_dict,
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", 
line 800, in station_upgrade
examples_dir = copy_examples(config_dict, examples_root=examples_root,
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py", 
line 616, in copy_examples
shutil.copytree(examples_resources, examples_dir)
  File "/usr/lib/python3.9/shutil.py", line 557, in copytree
return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
  File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
os.makedirs(dst, exist_ok=dirs_exist_ok)
  File "/usr/lib/python3.9/os.py", line 225, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/home/weewx/examples'





Il giorno martedì 16 gennaio 2024 alle 18:49:59 UTC+1 vince ha scritto:

> Francesco this error came up during beta testing if you search the group 
> archives. My recollection is you might need to install the pip module 
> ‘wheel’ in your step 2 after activating the virtual environment.

-- 
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/f4cbc406-74de-4f58-8bd3-5304c2acc477n%40googlegroups.com.

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

2024-01-17 Thread Ξ

Hi Tom,

Yes, that's exactly the ws6in1 driver I'm using, ever since July 2022.
target_unit is set to METRICWX and that's how I've always had it since I 
started running weewx 5 years ago on this R-Pi initially with an Acurite 
station.

Thanks a bunch!

On Monday, January 15, 2024 at 1:03:41 AM UTC+2 Tom Keffer wrote:

> I think I'm getting close to figuring this out. Can you confirm the 
> following:
>
> - You are using the "ws6in1" driver, right? This one 
> .
> - What unit system are you using in your database? This is the setting for 
> option "*target_unit*".
>
> -tk
>
> On Sun, Jan 14, 2024 at 10:56 AM Ξ  wrote:
>
>> and the NOAA reports show it too:
>>
>>MONTHLY CLIMATOLOGICAL SUMMARY for Sep 2023
>>
>> NAME: Dolni Okol  
>> ELEV: 1010 metersLAT: 42-29.40 NLONG: 023-29.70 E
>>
>>
>>TEMPERATURE (C), RAIN (mm), WIND SPEED (m/s)
>>
>>  HEAT   COOL AVG
>>   MEAN   DEGDEG  WIND 
>>   DOM   INSIDE  INS
>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH 
>>   TIMEDIR   HIGHLOW
>>
>> -
>>  01   16.7   28.7  15:308.5  07:301.30.00.00.12.7 
>>  14:30165   22.8   20.3
>>  02   18.6   33.0  16:15   10.7  07:300.00.60.00.02.1 
>>  16:30186   23.1   20.7
>>  03   18.8   32.7  16:15   10.0  07:300.00.80.00.12.2 
>>  10:45168   23.2   20.6
>>  04   12.3   16.5  00:15   11.1  20:155.70.0   25.60.14.2 
>>  07:30 95   22.5   19.0
>>  05   13.3   20.0  15:45   11.5  07:304.70.0   11.60.02.0 
>>  02:00282   19.0   18.3
>>  06   15.7   25.1  16:07   10.5  04:402.30.00.00.02.1 
>>  14:02161   18.8   17.6
>>  07   17.2   25.7  16:02   14.0  07:190.80.00.80.02.6 
>>  12:09152   19.4   18.3
>>  08   17.3   30.3  15:36   10.3  07:180.70.00.80.02.5 
>>  10:30161   20.4   18.4
>>  09   16.9   32.8  16:199.2  07:331.10.00.00.12.2 
>>  15:13188   21.0   18.7
>>  10   14.9   29.4  16:246.1  06:523.10.00.00.12.2 
>>  14:40184   21.1   17.9
>>  11   15.2   32.1  15:306.5  06:012.80.00.00.01.9 
>>  15:10163   21.2   18.0
>>  12   15.5   34.3  17:105.3  07:072.50.00.00.02.0 
>>  12:38155   20.9   17.7
>>  13   16.0   36.0  17:177.0  07:082.00.00.00.02.1 
>>  15:20168   21.5   18.1
>>  14   18.0   32.7  15:41   10.1  03:420.00.00.00.12.2 
>>  14:23 86   21.9   19.3
>>  15   18.0   29.2  16:13   11.1  07:040.00.00.00.02.0 
>>  11:07185   22.6   20.0
>>  16   17.5   28.7  17:15   13.9  23:450.50.0   59.20.01.7 
>>  15:02188   22.0   20.7
>>  17   16.0   29.0  16:20   11.2  23:542.00.00.80.01.1 
>>  16:16172   20.9   19.6
>>  18   16.4   29.9  15:559.8  23:531.60.00.00.02.0 
>>  15:16182   20.4   19.0
>>  19   14.6   29.6  16:437.1  06:423.40.00.40.01.8 
>>  23:47146   20.0   17.8
>>  20   16.6   31.8  17:339.3  07:271.40.09.60.12.5 
>>  00:04164   21.2   18.3
>>  21   16.8   33.2  17:23   10.6  02:411.20.00.40.02.0 
>>  20:39295   20.6   19.1
>>  22   19.7   33.1  16:33   11.2  07:130.01.70.00.14.2 
>>  15:00290   22.3   19.2
>>  23   21.2   36.6  15:47   11.7  07:300.03.20.00.02.2 
>>  12:23289   23.6   20.5
>>  24   17.8   24.7  15:31   12.8  04:530.20.00.00.01.8 
>>  10:08243   23.4   21.5
>>  25   17.9   28.8  16:26   14.7  05:330.10.00.00.12.3 
>>  10:52168   22.3   21.2
>>  26   16.2   27.2  16:209.9  07:321.80.00.00.13.6 
>>  14:22168   21.6   19.6
>>  27   15.5   26.6  15:149.4  06:002.50.00.00.13.0 
>>  11:47169   21.5   19.1
>>  28   14.7   26.1  15:537.8  05:533.30.00.00.02.1 
>>  13:01216   20.1   18.6
>>  29   15.2   26.7  15:299.8  23:512.80.00.00.12.8 
>>  13:59205   20.1   18.3
>>  30   14.5   26.9  17:138.7  07:553.50.00.00.12.3 
>>  12:57201   20.5   17.8
>>
>> -
>>   16.5   36.6 235.3 12   51.26.3  109.20.04.2 
>> 04176   23.6   17.6
>>
>>
>>
>> =
>>
>> For December
>>
>>   MONT

Re: [weewx-user] Re: Weewx version 5 installation

also on this command

weewxd --config=/home/weewx/weewx.conf
Traceback (most recent call last):
  File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
sys.exit(main())
  File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 
160, in main
engine = weewx.engine.StdEngine(config_dict)
  File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
line 89, in __init__
self.loadServices(config_dict)
  File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
line 157, in loadServices
obj = weeutil.weeutil.get_object(svc)(self, config_dict)
  File 
"/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", line 
1404, in get_object
module = importlib.import_module(module_name)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1030, in _gcd_import
  File "", line 1007, in _find_and_load
  File "", line 986, in _find_and_load_unlocked
  File "", line 680, in _load_unlocked
  File "", line 790, in exec_module
  File "", line 228, in 
_call_with_frames_removed
  File "/home/weewx/bin/user/mqtt.py", line 100, in 
import paho.mqtt.client as mqtt
ModuleNotFoundError: No module named 'paho'

Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco Fasano ha 
scritto:

> Good morning,
> I followed the steps in the guide and I get this error
>
> python3 -m pip install weewx
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting weewx
>   Downloading 
> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl (1.4 
> MB)
>  || 1.4 MB 531 kB/s
> Collecting pyserial<4.0,>=3.4
>   Downloading 
> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl 
> (90 kB)
>  || 90 kB 450 kB/s
> Collecting ephem<5.0,>=4.1
>   Downloading 
> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl 
> (1.7 MB)
>  || 1.7 MB 851 kB/s
> Collecting pyusb<2.0.0,>=1.0.2
>   Downloading 
> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl (58 kB)
>  || 58 kB 602 kB/s
> Collecting configobj<6.0,>=5.0
>   Downloading 
> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>  
> (35 kB)
> Collecting Pillow>=5.2
>   Downloading 
> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>  
> (1.2 MB)
>  || 1.2 MB 988 kB/s
> Collecting CT3<4.0,>=3.1
>   Downloading 
> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
> (196 kB)
>  || 196 kB 569 kB/s
> Collecting PyMySQL<2.0,>=1.0
>   Downloading 
> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
> (44 kB)
>  || 44 kB 271 kB/s
> Collecting six
>   Downloading 
> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl (11 
> kB)
> Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
> ephem, CT3, configobj, weewx
> Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
> configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 weewx-5.0.0
> (weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
> --config=/home/weewx/weewx.conf
> Using configuration file /home/weewx/weewx.conf
>
> Upgrade examples, utility files in /home/weewx (Y/n)? Y
> Removing example directory /home/weewx/examples
> Copying examples into /home/weewx/examples
>
> Traceback (most recent call last):
>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
> sys.exit(main())
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
> 66, in main
> namespace.func(namespace)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
> line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
> line 339, in upgrade_station
> weectllib.station_actions.station_upgrade(config_dict=config_dict,
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>  
> line 800, in station_upgrade
> examples_dir = copy_examples(config_dict, examples_root=examples_root,
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>  
> line 616, in copy_examples
> shutil.copytree(examples_resources, examples_dir)
>   File "/usr/lib/python3.9/shutil.py", line 557, in copytree
> return _copytree(entries=entries, src=src, dst=dst, symlinks=symlinks,
>   File "/usr/lib/python3.9/shutil.py", line 458, in _copytree
> os.makedirs(dst, exist_ok=dirs_exist_ok)
>   File "/usr/lib/python3.9/os.py", line 225, in makedirs
> mkdir(name, mode)

Re: [weewx-user] Re: Weewx version 5 installation

2024-01-17 Thread 'michael.k...@gmx.at' via weewx-user

This is not a weewx issue, it is related to the extension, but  a user 
error: read the friendly manual for the 
extension: https://github.com/matthewwall/weewx-mqtt

Use pip to install paho-mqtt, as this is a prerequisite.

Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 UTC+1:

> also on this command
>
> weewxd --config=/home/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
> sys.exit(main())
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 
> 160, in main
> engine = weewx.engine.StdEngine(config_dict)
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
> line 89, in __init__
> self.loadServices(config_dict)
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
> line 157, in loadServices
> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", line 
> 1404, in get_object
> module = importlib.import_module(module_name)
>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1030, in _gcd_import
>   File "", line 1007, in _find_and_load
>   File "", line 986, in 
> _find_and_load_unlocked
>   File "", line 680, in _load_unlocked
>   File "", line 790, in exec_module
>   File "", line 228, in 
> _call_with_frames_removed
>   File "/home/weewx/bin/user/mqtt.py", line 100, in 
> import paho.mqtt.client as mqtt
> ModuleNotFoundError: No module named 'paho'
>
> Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco Fasano 
> ha scritto:
>
>> Good morning,
>> I followed the steps in the guide and I get this error
>>
>> python3 -m pip install weewx
>> Looking in indexes: https://pypi.org/simple, 
>> https://www.piwheels.org/simple
>> Collecting weewx
>>   Downloading 
>> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl (1.4 
>> MB)
>>  || 1.4 MB 531 kB/s
>> Collecting pyserial<4.0,>=3.4
>>   Downloading 
>> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl 
>> (90 kB)
>>  || 90 kB 450 kB/s
>> Collecting ephem<5.0,>=4.1
>>   Downloading 
>> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl 
>> (1.7 MB)
>>  || 1.7 MB 851 kB/s
>> Collecting pyusb<2.0.0,>=1.0.2
>>   Downloading 
>> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl (58 
>> kB)
>>  || 58 kB 602 kB/s
>> Collecting configobj<6.0,>=5.0
>>   Downloading 
>> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>>  
>> (35 kB)
>> Collecting Pillow>=5.2
>>   Downloading 
>> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>>  
>> (1.2 MB)
>>  || 1.2 MB 988 kB/s
>> Collecting CT3<4.0,>=3.1
>>   Downloading 
>> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
>> (196 kB)
>>  || 196 kB 569 kB/s
>> Collecting PyMySQL<2.0,>=1.0
>>   Downloading 
>> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
>> (44 kB)
>>  || 44 kB 271 kB/s
>> Collecting six
>>   Downloading 
>> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl (11 
>> kB)
>> Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
>> ephem, CT3, configobj, weewx
>> Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
>> configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 weewx-5.0.0
>> (weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
>> --config=/home/weewx/weewx.conf
>> Using configuration file /home/weewx/weewx.conf
>>
>> Upgrade examples, utility files in /home/weewx (Y/n)? Y
>> Removing example directory /home/weewx/examples
>> Copying examples into /home/weewx/examples
>>
>> Traceback (most recent call last):
>>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
>> 66, in main
>> namespace.func(namespace)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
>> line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_cmd.py", 
>> line 339, in upgrade_station
>> weectllib.station_actions.station_upgrade(config_dict=config_dict,
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/station_actions.py",
>>  
>> line 800, in station_upgrade
>> examples_dir = copy_examples(config_dict, examples_root=examples_root,
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packa

Re: [weewx-user] Re: Weewx version 5 installation

 sudo pip3 install paho-mqtt
Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple
Requirement already satisfied: paho-mqtt in /usr/lib/python3/dist-packages 
(1.5.1)

Il giorno mercoledì 17 gennaio 2024 alle 13:03:05 UTC+1 michael.k...@gmx.at 
ha scritto:

> This is not a weewx issue, it is related to the extension, but  a user 
> error: read the friendly manual for the extension: 
> https://github.com/matthewwall/weewx-mqtt
>
> Use pip to install paho-mqtt, as this is a prerequisite.
>
> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 UTC+1:
>
>> also on this command
>>
>> weewxd --config=/home/weewx/weewx.conf
>> Traceback (most recent call last):
>>   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
>> sys.exit(main())
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 
>> 160, in main
>> engine = weewx.engine.StdEngine(config_dict)
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
>> line 89, in __init__
>> self.loadServices(config_dict)
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", 
>> line 157, in loadServices
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", line 
>> 1404, in get_object
>> module = importlib.import_module(module_name)
>>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
>> import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>>   File "", line 1030, in _gcd_import
>>   File "", line 1007, in _find_and_load
>>   File "", line 986, in 
>> _find_and_load_unlocked
>>   File "", line 680, in _load_unlocked
>>   File "", line 790, in exec_module
>>   File "", line 228, in 
>> _call_with_frames_removed
>>   File "/home/weewx/bin/user/mqtt.py", line 100, in 
>> import paho.mqtt.client as mqtt
>> ModuleNotFoundError: No module named 'paho'
>>
>> Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco Fasano 
>> ha scritto:
>>
>>> Good morning,
>>> I followed the steps in the guide and I get this error
>>>
>>> python3 -m pip install weewx
>>> Looking in indexes: https://pypi.org/simple, 
>>> https://www.piwheels.org/simple
>>> Collecting weewx
>>>   Downloading 
>>> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl (1.4 
>>> MB)
>>>  || 1.4 MB 531 kB/s
>>> Collecting pyserial<4.0,>=3.4
>>>   Downloading 
>>> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl 
>>> (90 kB)
>>>  || 90 kB 450 kB/s
>>> Collecting ephem<5.0,>=4.1
>>>   Downloading 
>>> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl
>>>  
>>> (1.7 MB)
>>>  || 1.7 MB 851 kB/s
>>> Collecting pyusb<2.0.0,>=1.0.2
>>>   Downloading 
>>> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl (58 
>>> kB)
>>>  || 58 kB 602 kB/s
>>> Collecting configobj<6.0,>=5.0
>>>   Downloading 
>>> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>>>  
>>> (35 kB)
>>> Collecting Pillow>=5.2
>>>   Downloading 
>>> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>>>  
>>> (1.2 MB)
>>>  || 1.2 MB 988 kB/s
>>> Collecting CT3<4.0,>=3.1
>>>   Downloading 
>>> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
>>> (196 kB)
>>>  || 196 kB 569 kB/s
>>> Collecting PyMySQL<2.0,>=1.0
>>>   Downloading 
>>> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
>>> (44 kB)
>>>  || 44 kB 271 kB/s
>>> Collecting six
>>>   Downloading 
>>> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl (11 
>>> kB)
>>> Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
>>> ephem, CT3, configobj, weewx
>>> Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
>>> configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 weewx-5.0.0
>>> (weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
>>> --config=/home/weewx/weewx.conf
>>> Using configuration file /home/weewx/weewx.conf
>>>
>>> Upgrade examples, utility files in /home/weewx (Y/n)? Y
>>> Removing example directory /home/weewx/examples
>>> Copying examples into /home/weewx/examples
>>>
>>> Traceback (most recent call last):
>>>   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
>>> sys.exit(main())
>>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", line 
>>> 66, in main
>>> namespace.func(namespace)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weectllib/__init__.py", 
>>> line 121, in dispatch
>>> namespace.action_func(config_dict, namespace)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-

Re: [weewx-user] Re: Weewx version 5 installation

is already installed


Il giorno mercoledì 17 gennaio 2024 alle 13:09:25 UTC+1 Francesco Fasano ha 
scritto:

>  sudo pip3 install paho-mqtt
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Requirement already satisfied: paho-mqtt in /usr/lib/python3/dist-packages 
> (1.5.1)
>
> Il giorno mercoledì 17 gennaio 2024 alle 13:03:05 UTC+1 
> michael.k...@gmx.at ha scritto:
>
>> This is not a weewx issue, it is related to the extension, but  a user 
>> error: read the friendly manual for the extension: 
>> https://github.com/matthewwall/weewx-mqtt
>>
>> Use pip to install paho-mqtt, as this is a prerequisite.
>>
>> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 UTC+1:
>>
>>> also on this command
>>>
>>> weewxd --config=/home/weewx/weewx.conf
>>> Traceback (most recent call last):
>>>   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
>>> sys.exit(main())
>>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", line 
>>> 160, in main
>>> engine = weewx.engine.StdEngine(config_dict)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 89, 
>>> in __init__
>>> self.loadServices(config_dict)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>>> 157, in loadServices
>>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>>   File 
>>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", line 
>>> 1404, in get_object
>>> module = importlib.import_module(module_name)
>>>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
>>> import_module
>>> return _bootstrap._gcd_import(name[level:], package, level)
>>>   File "", line 1030, in _gcd_import
>>>   File "", line 1007, in _find_and_load
>>>   File "", line 986, in 
>>> _find_and_load_unlocked
>>>   File "", line 680, in _load_unlocked
>>>   File "", line 790, in exec_module
>>>   File "", line 228, in 
>>> _call_with_frames_removed
>>>   File "/home/weewx/bin/user/mqtt.py", line 100, in 
>>> import paho.mqtt.client as mqtt
>>> ModuleNotFoundError: No module named 'paho'
>>>
>>> Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco Fasano 
>>> ha scritto:
>>>
 Good morning,
 I followed the steps in the guide and I get this error

 python3 -m pip install weewx
 Looking in indexes: https://pypi.org/simple, 
 https://www.piwheels.org/simple
 Collecting weewx
   Downloading 
 https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl 
 (1.4 MB)
  || 1.4 MB 531 kB/s
 Collecting pyserial<4.0,>=3.4
   Downloading 
 https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl 
 (90 kB)
  || 90 kB 450 kB/s
 Collecting ephem<5.0,>=4.1
   Downloading 
 https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl
  
 (1.7 MB)
  || 1.7 MB 851 kB/s
 Collecting pyusb<2.0.0,>=1.0.2
   Downloading 
 https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl (58 
 kB)
  || 58 kB 602 kB/s
 Collecting configobj<6.0,>=5.0
   Downloading 
 https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
  
 (35 kB)
 Collecting Pillow>=5.2
   Downloading 
 https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
  
 (1.2 MB)
  || 1.2 MB 988 kB/s
 Collecting CT3<4.0,>=3.1
   Downloading 
 https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
 (196 kB)
  || 196 kB 569 kB/s
 Collecting PyMySQL<2.0,>=1.0
   Downloading 
 https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
 (44 kB)
  || 44 kB 271 kB/s
 Collecting six
   Downloading 
 https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl 
 (11 kB)
 Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
 ephem, CT3, configobj, weewx
 Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
 configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 weewx-5.0.0
 (weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
 --config=/home/weewx/weewx.conf
 Using configuration file /home/weewx/weewx.conf

 Upgrade examples, utility files in /home/weewx (Y/n)? Y
 Removing example directory /home/weewx/examples
 Copying examples into /home/weewx/examples

 Traceback (most recent call last):
   File "/home/pi/weewx-venv/bin/weectl", line 8, in 
 sys.exit(main())
   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weectl.py", 
 line 66, in main

Re: [weewx-user] Re: Weewx version 5 installation

2024-01-17 Thread 'michael.k...@gmx.at' via weewx-user

Did you activate the venv before doing so?

Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 13:11:07 UTC+1:

> is already installed
>
>
> Il giorno mercoledì 17 gennaio 2024 alle 13:09:25 UTC+1 Francesco Fasano 
> ha scritto:
>
>>  sudo pip3 install paho-mqtt
>> Looking in indexes: https://pypi.org/simple, 
>> https://www.piwheels.org/simple
>> Requirement already satisfied: paho-mqtt in 
>> /usr/lib/python3/dist-packages (1.5.1)
>>
>> Il giorno mercoledì 17 gennaio 2024 alle 13:03:05 UTC+1 
>> michael.k...@gmx.at ha scritto:
>>
>>> This is not a weewx issue, it is related to the extension, but  a user 
>>> error: read the friendly manual for the extension: 
>>> https://github.com/matthewwall/weewx-mqtt
>>>
>>> Use pip to install paho-mqtt, as this is a prerequisite.
>>>
>>> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 UTC+1:
>>>
 also on this command

 weewxd --config=/home/weewx/weewx.conf
 Traceback (most recent call last):
   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
 sys.exit(main())
   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", 
 line 160, in main
 engine = weewx.engine.StdEngine(config_dict)
   File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
 89, 
 in __init__
 self.loadServices(config_dict)
   File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
 157, in loadServices
 obj = weeutil.weeutil.get_object(svc)(self, config_dict)
   File 
 "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", line 
 1404, in get_object
 module = importlib.import_module(module_name)
   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
 import_module
 return _bootstrap._gcd_import(name[level:], package, level)
   File "", line 1030, in _gcd_import
   File "", line 1007, in _find_and_load
   File "", line 986, in 
 _find_and_load_unlocked
   File "", line 680, in _load_unlocked
   File "", line 790, in 
 exec_module
   File "", line 228, in 
 _call_with_frames_removed
   File "/home/weewx/bin/user/mqtt.py", line 100, in 
 import paho.mqtt.client as mqtt
 ModuleNotFoundError: No module named 'paho'

 Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco 
 Fasano ha scritto:

> Good morning,
> I followed the steps in the guide and I get this error
>
> python3 -m pip install weewx
> Looking in indexes: https://pypi.org/simple, 
> https://www.piwheels.org/simple
> Collecting weewx
>   Downloading 
> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl 
> (1.4 MB)
>  || 1.4 MB 531 kB/s
> Collecting pyserial<4.0,>=3.4
>   Downloading 
> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl
>  
> (90 kB)
>  || 90 kB 450 kB/s
> Collecting ephem<5.0,>=4.1
>   Downloading 
> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl
>  
> (1.7 MB)
>  || 1.7 MB 851 kB/s
> Collecting pyusb<2.0.0,>=1.0.2
>   Downloading 
> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl 
> (58 kB)
>  || 58 kB 602 kB/s
> Collecting configobj<6.0,>=5.0
>   Downloading 
> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>  
> (35 kB)
> Collecting Pillow>=5.2
>   Downloading 
> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>  
> (1.2 MB)
>  || 1.2 MB 988 kB/s
> Collecting CT3<4.0,>=3.1
>   Downloading 
> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
> (196 kB)
>  || 196 kB 569 kB/s
> Collecting PyMySQL<2.0,>=1.0
>   Downloading 
> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
> (44 kB)
>  || 44 kB 271 kB/s
> Collecting six
>   Downloading 
> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl 
> (11 kB)
> Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
> ephem, CT3, configobj, weewx
> Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
> configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 
> weewx-5.0.0
> (weewx-venv) pi@raspberrypi:/home $ weectl station upgrade 
> --config=/home/weewx/weewx.conf
> Using configuration file /home/weewx/weewx.conf
>
> Upgrade examples, utility files in /home/weewx (Y/n)? Y
> Removing example directory /home/weewx/examples
> Copyi

Re: [weewx-user] Re: Weewx version 5 installation

yes


Il giorno mercoledì 17 gennaio 2024 alle 13:25:09 UTC+1 michael.k...@gmx.at 
ha scritto:

> Did you activate the venv before doing so?
>
> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 13:11:07 UTC+1:
>
>> is already installed
>>
>>
>> Il giorno mercoledì 17 gennaio 2024 alle 13:09:25 UTC+1 Francesco Fasano 
>> ha scritto:
>>
>>>  sudo pip3 install paho-mqtt
>>> Looking in indexes: https://pypi.org/simple, 
>>> https://www.piwheels.org/simple
>>> Requirement already satisfied: paho-mqtt in 
>>> /usr/lib/python3/dist-packages (1.5.1)
>>>
>>> Il giorno mercoledì 17 gennaio 2024 alle 13:03:05 UTC+1 
>>> michael.k...@gmx.at ha scritto:
>>>
 This is not a weewx issue, it is related to the extension, but  a user 
 error: read the friendly manual for the extension: 
 https://github.com/matthewwall/weewx-mqtt

 Use pip to install paho-mqtt, as this is a prerequisite.

 Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 UTC+1:

> also on this command
>
> weewxd --config=/home/weewx/weewx.conf
> Traceback (most recent call last):
>   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
> sys.exit(main())
>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", 
> line 160, in main
> engine = weewx.engine.StdEngine(config_dict)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
> 89, 
> in __init__
> self.loadServices(config_dict)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
> 157, in loadServices
> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>   File 
> "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", 
> line 
> 1404, in get_object
> module = importlib.import_module(module_name)
>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1030, in _gcd_import
>   File "", line 1007, in _find_and_load
>   File "", line 986, in 
> _find_and_load_unlocked
>   File "", line 680, in _load_unlocked
>   File "", line 790, in 
> exec_module
>   File "", line 228, in 
> _call_with_frames_removed
>   File "/home/weewx/bin/user/mqtt.py", line 100, in 
> import paho.mqtt.client as mqtt
> ModuleNotFoundError: No module named 'paho'
>
> Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco 
> Fasano ha scritto:
>
>> Good morning,
>> I followed the steps in the guide and I get this error
>>
>> python3 -m pip install weewx
>> Looking in indexes: https://pypi.org/simple, 
>> https://www.piwheels.org/simple
>> Collecting weewx
>>   Downloading 
>> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl 
>> (1.4 MB)
>>  || 1.4 MB 531 kB/s
>> Collecting pyserial<4.0,>=3.4
>>   Downloading 
>> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl
>>  
>> (90 kB)
>>  || 90 kB 450 kB/s
>> Collecting ephem<5.0,>=4.1
>>   Downloading 
>> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl
>>  
>> (1.7 MB)
>>  || 1.7 MB 851 kB/s
>> Collecting pyusb<2.0.0,>=1.0.2
>>   Downloading 
>> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl 
>> (58 kB)
>>  || 58 kB 602 kB/s
>> Collecting configobj<6.0,>=5.0
>>   Downloading 
>> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>>  
>> (35 kB)
>> Collecting Pillow>=5.2
>>   Downloading 
>> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>>  
>> (1.2 MB)
>>  || 1.2 MB 988 kB/s
>> Collecting CT3<4.0,>=3.1
>>   Downloading 
>> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl 
>> (196 kB)
>>  || 196 kB 569 kB/s
>> Collecting PyMySQL<2.0,>=1.0
>>   Downloading 
>> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
>> (44 kB)
>>  || 44 kB 271 kB/s
>> Collecting six
>>   Downloading 
>> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3-none-any.whl 
>> (11 kB)
>> Installing collected packages: six, pyusb, pyserial, PyMySQL, Pillow, 
>> ephem, CT3, configobj, weewx
>> Successfully installed CT3-3.3.3 Pillow-10.2.0 PyMySQL-1.1.0 
>> configobj-5.0.8 ephem-4.1.5 pyserial-3.5 pyusb-1.2.1 six-1.16.0 
>> weewx-5.0.0
>> (weewx-venv) pi@raspberrypi:/home $ weectl station up

Re: [weewx-user] Re: Database Error Message

FWIW I went back to 4.10.2 and no more database errors and the CPU spikes 
are gone. Might be time to upgrade to a PI4 or PI5. 

On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:

> The difference is that V5 could be doing more. We don't know for sure, 
> yet, but it is probably reporting on synthetic types, which V4 was unable 
> to do.
>
> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo  wrote:
>
>> Yes I'm on a PI3 with ADSB tracking running as well. I changed the 
>> archive to 300 so we'll see how it goes. Never had the issue before 
>> upgrading to 5.0 so it must be somewhat related to that.  I've noticed that 
>> CPU usage and temps are slightly higher than average since I upgraded last 
>> night. Thanks for the suggestions. 
>>
>>
>>
>> Sent from my Verizon, Samsung Galaxy smartphone
>>
>>
>>  Original message 
>> From: vince  
>> Date: 1/16/24 4:12 PM (GMT-05:00) 
>> To: weewx-user  
>> Subject: Re: [weewx-user] Re: Database Error Message 
>>
>> The log excerpt is a little short but perhaps.   I see in your log you 
>> have a 120 second archive period yet Belchertown took 125 seconds to run 
>> (which is 'very' slow), so it's possible your archive period is too fast 
>> for your hardware.  What kind of pi are you on ?  Something slower than a 
>> pi4 perhaps ?
>>
>> If you are on slow hardware try disabling Belchertown temporarily and see 
>> if the problem goes away.  Or alternately set your archive period to 
>> perhaps 180 seconds and try that.  Or as always you might throw hardware at 
>> it and use a faster pibut it looks like you're asking your hardware to 
>> do too much too often.
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com
>>  
>> 
>> .
>>
>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>>
> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.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/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%40googlegroups.com.

[weewx-user] Re: Error: invalid read_period in get_records

2024-01-17 Thread Μάριος

Problem solved after weewx uninstall and install again.

Thanks for your help!

Στις Δευτέρα 15 Ιανουαρίου 2024 στις 9:25:37 μ.μ. UTC+2, ο χρήστης Μάριος 
έγραψε:

> And my wee_device --info
>
> Using configuration file /etc/weewx/weewx.conf
> Using FineOffsetUSB driver version 1.20 (weewx.drivers.fousb)
> Querying the station...
> Fine Offset station settings:
> local time: 2024.01.15 21:23:07 EET
>   polling mode: PERIODIC
>
>   abs_pressure: 948.2
>current_pos: 1072
>   data_changed: 0
> data_count: 52
>  date_time: 2024-01-12 04:33
>  hum_in_offset: 13060
> hum_out_offset: 4609
> id: 19986
>  lux_wm2_coeff: None
>magic_1: 0x55
>magic_2: 0xaa
>  model: 4224
>  rain_coef: 24580
>read_period: 5
>   rel_pressure: 1014.1
> temp_in_offset: 9471
>temp_out_offset: None
>   timezone: None
> unknown_01: 0
> unknown_18: 96
>version: 32
>  wind_coef: 2785
>  wind_mult: None
>  max.abs_pressure.date: 2165-165-165 165:165
>   max.abs_pressure.val: None
>  max.dewpoint.date: 2023-11-25 21:15
>   max.dewpoint.val: 13.5
>max.hum_in.date: 2024-01-01 00:13
> max.hum_in.val: 70
>   max.hum_out.date: 2023-11-26 16:16
>max.hum_out.val: 98
>max.illuminance.val: 32767.9
>  max.rain.day.date: 2165-165-165 165:165
>   max.rain.day.val: None
> max.rain.hour.date: 2165-165-165 165:165
>  max.rain.hour.val: None
>max.rain.month.date: 2165-165-165 165:165
> max.rain.month.val: None
>max.rain.total.date: 2165-165-165 165:165
> max.rain.total.val: None
> max.rain.week.date: 2165-165-165 165:165
>  max.rain.week.val: None
>  max.rel_pressure.date: 2165-165-165 165:165
>   max.rel_pressure.val: None
>   max.temp_in.date: 2015-01-01 12:01
>max.temp_in.val: 22.1
>  max.temp_out.date: 2023-11-26 00:35
>   max.temp_out.val: 20.0
> max.uv.val: None
>  max.wind_ave.date: 2165-165-165 165:165
>   max.wind_ave.val: None
> max.wind_gust.date: 2165-165-165 165:165
>  max.wind_gust.val: None
> max.windchill.date: 2023-11-26 00:35
>  max.windchill.val: 20.0
>  min.abs_pressure.date: 2015-01-02 00:54
>   min.abs_pressure.val: 938.8
>  min.dewpoint.date: 2024-01-11 01:03
>   min.dewpoint.val: -8.2
>min.hum_in.date: 2165-165-165 165:165
> min.hum_in.val: None
>   min.hum_out.date: 2015-01-07 11:09
>min.hum_out.val: 23
>  min.rel_pressure.date: 2024-01-03 03:42
>   min.rel_pressure.val: 1000.4
>   min.temp_in.date: 2165-165-165 165:165
>min.temp_in.val: None
>  min.temp_out.date: 2024-01-10 18:14
>   min.temp_out.val: -1.8
> min.windchill.date: 2024-01-10 18:14
>  min.windchill.val: -1.8
>
>   settings_1.pressure_inHg: True
>settings_1.pressure_hPa: True
>  settings_1.temp_out_F: False
>   settings_1.pressure_mmHg: True
> settings_1.rain_in: True
>   settings_1.temp_in_F: False
>settings_1.bit4: True
>settings_1.bit3: True
>settings_2.wind_bft: True
>settings_2.wind_mps: True
>   settings_2.wind_knot: True
>settings_2.bit7: True
>settings_2.bit6: True
>settings_2.bit5: True
>   settings_2.wind_kmph: True
>settings_2.wind_mph: True
>
>display_1.wind_gust: True
>display_1.show_day_name: True
>display_1.show_year: True
>display_1.time_scale_24: True
> display_1.pressure_rel: True
>   display_1.alarm_time: True
> display_1.date_mdy: True
>   display_1.clock_12hr: True
>display_2.temp_out_temp: True
>display_2.rain_hour: True
>   display_2.rain_month: True
>display_2.rain_week: True
>   display_2.temp_out_chill: False
> display_2.rain_day: True
> display_2.temp_out_dew: False
>   display_2.rain_total: True
>   display_3.illuminance_fc: True
> display_3.bit7: True
> display_3.bit6: True
> display_3.bit5: True
> display_3.

[weewx-user] Error upgrading to v5.0

2024-01-17 Thread Marty b

Hello,

I tried upgrading to v5.0 and am getting errors:
pi@WeeWx2021:/var/log/apache2 $ sudo apt-get update
Hit:1 https://weewx.com/apt/python3 buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Reading package lists... Done
pi@WeeWx2021:/var/log/apache2 $ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up weewx (5.0.0-1) ...
Using root:root as user:group
Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 58, in main
module = importlib.import_module(f'weectllib.{subcommand}_cmd')
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1006, in _gcd_import
  File "", line 983, in _find_and_load
  File "", line 953, in _find_and_load_unlocked
  File "", line 219, in 
_call_with_frames_removed
  File "", line 1006, in _gcd_import
  File "", line 983, in _find_and_load
  File "", line 967, in _find_and_load_unlocked
  File "", line 677, in _load_unlocked
  File "", line 728, in exec_module
  File "", line 219, in 
_call_with_frames_removed
  File "/usr/share/weewx/weectllib/__init__.py", line 12, in 
import configobj
  File "/usr/lib/python3/dist-packages/configobj.py", line 22, in 
import six
ImportError: bad magic number in 'six': b'\x03\xf3\r\n'
dpkg: error: --compare-versions takes three arguments:   


Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 
'more' !
Using debconf configuration values from previous install
Traceback (most recent call last):
  File "/usr/share/weewx/weectl.py", line 74, in 
main()
  File "/usr/share/weewx/weectl.py", line 58, in main
module = importlib.import_module(f'weectllib.{subcommand}_cmd')
  File "/usr/lib/python3.7/importlib/__init__.py", line 127, in 
import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File "", line 1006, in _gcd_import
  File "", line 983, in _find_and_load
  File "", line 953, in _find_and_load_unlocked
  File "", line 219, in 
_call_with_frames_removed
  File "", line 1006, in _gcd_import
  File "", line 983, in _find_and_load
  File "", line 967, in _find_and_load_unlocked
  File "", line 677, in _load_unlocked
  File "", line 728, in exec_module
  File "", line 219, in 
_call_with_frames_removed
  File "/usr/share/weewx/weectllib/__init__.py", line 12, in 
import configobj
  File "/usr/lib/python3/dist-packages/configobj.py", line 22, in 
import six
ImportError: bad magic number in 'six': b'\x03\xf3\r\n'
dpkg: error processing package weewx (--configure):
 installed weewx package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 weewx
E: Sub-process /usr/bin/dpkg returned an error code (1)

Please let me know what I need to do to resolve this.

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/68394f8e-5845-46d6-a78e-53f992b97575n%40googlegroups.com.

Re: [weewx-user] Re: Weewx version 5 installation

You have to install the paho-mqtt module into the venv after activating it. 

source /home/pi/weewx-venv/bin/activate
pip3 install paho-mqtt

On Wednesday, January 17, 2024 at 4:28:37 AM UTC-8 Francesco Fasano wrote:

> yes
>
>
> Il giorno mercoledì 17 gennaio 2024 alle 13:25:09 UTC+1 
> michael.k...@gmx.at ha scritto:
>
>> Did you activate the venv before doing so?
>>
>> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 13:11:07 UTC+1:
>>
>>> is already installed
>>>
>>>
>>> Il giorno mercoledì 17 gennaio 2024 alle 13:09:25 UTC+1 Francesco Fasano 
>>> ha scritto:
>>>
  sudo pip3 install paho-mqtt
 Looking in indexes: https://pypi.org/simple, 
 https://www.piwheels.org/simple
 Requirement already satisfied: paho-mqtt in 
 /usr/lib/python3/dist-packages (1.5.1)

 Il giorno mercoledì 17 gennaio 2024 alle 13:03:05 UTC+1 
 michael.k...@gmx.at ha scritto:

> This is not a weewx issue, it is related to the extension, but  a user 
> error: read the friendly manual for the extension: 
> https://github.com/matthewwall/weewx-mqtt
>
> Use pip to install paho-mqtt, as this is a prerequisite.
>
> Francesco Fasano schrieb am Mittwoch, 17. Januar 2024 um 10:32:04 
> UTC+1:
>
>> also on this command
>>
>> weewxd --config=/home/weewx/weewx.conf
>> Traceback (most recent call last):
>>   File "/home/pi/weewx-venv/bin/weewxd", line 8, in 
>> sys.exit(main())
>>   File "/home/pi/weewx-venv/lib/python3.9/site-packages/weewxd.py", 
>> line 160, in main
>> engine = weewx.engine.StdEngine(config_dict)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>> 89, 
>> in __init__
>> self.loadServices(config_dict)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weewx/engine.py", line 
>> 157, in loadServices
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>   File 
>> "/home/pi/weewx-venv/lib/python3.9/site-packages/weeutil/weeutil.py", 
>> line 
>> 1404, in get_object
>> module = importlib.import_module(module_name)
>>   File "/usr/lib/python3.9/importlib/__init__.py", line 127, in 
>> import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>>   File "", line 1030, in _gcd_import
>>   File "", line 1007, in _find_and_load
>>   File "", line 986, in 
>> _find_and_load_unlocked
>>   File "", line 680, in _load_unlocked
>>   File "", line 790, in 
>> exec_module
>>   File "", line 228, in 
>> _call_with_frames_removed
>>   File "/home/weewx/bin/user/mqtt.py", line 100, in 
>> import paho.mqtt.client as mqtt
>> ModuleNotFoundError: No module named 'paho'
>>
>> Il giorno mercoledì 17 gennaio 2024 alle 09:54:46 UTC+1 Francesco 
>> Fasano ha scritto:
>>
>>> Good morning,
>>> I followed the steps in the guide and I get this error
>>>
>>> python3 -m pip install weewx
>>> Looking in indexes: https://pypi.org/simple, 
>>> https://www.piwheels.org/simple
>>> Collecting weewx
>>>   Downloading 
>>> https://www.piwheels.org/simple/weewx/weewx-5.0.0-py3-none-any.whl 
>>> (1.4 MB)
>>>  || 1.4 MB 531 kB/s
>>> Collecting pyserial<4.0,>=3.4
>>>   Downloading 
>>> https://www.piwheels.org/simple/pyserial/pyserial-3.5-py2.py3-none-any.whl
>>>  
>>> (90 kB)
>>>  || 90 kB 450 kB/s
>>> Collecting ephem<5.0,>=4.1
>>>   Downloading 
>>> https://www.piwheels.org/simple/ephem/ephem-4.1.5-cp39-cp39-linux_armv7l.whl
>>>  
>>> (1.7 MB)
>>>  || 1.7 MB 851 kB/s
>>> Collecting pyusb<2.0.0,>=1.0.2
>>>   Downloading 
>>> https://www.piwheels.org/simple/pyusb/pyusb-1.2.1-py3-none-any.whl 
>>> (58 kB)
>>>  || 58 kB 602 kB/s
>>> Collecting configobj<6.0,>=5.0
>>>   Downloading 
>>> https://www.piwheels.org/simple/configobj/configobj-5.0.8-py2.py3-none-any.whl
>>>  
>>> (35 kB)
>>> Collecting Pillow>=5.2
>>>   Downloading 
>>> https://www.piwheels.org/simple/pillow/pillow-10.2.0-cp39-cp39-linux_armv7l.whl
>>>  
>>> (1.2 MB)
>>>  || 1.2 MB 988 kB/s
>>> Collecting CT3<4.0,>=3.1
>>>   Downloading 
>>> https://www.piwheels.org/simple/ct3/CT3-3.3.3-cp39-cp39-linux_armv7l.whl
>>>  
>>> (196 kB)
>>>  || 196 kB 569 kB/s
>>> Collecting PyMySQL<2.0,>=1.0
>>>   Downloading 
>>> https://www.piwheels.org/simple/pymysql/PyMySQL-1.1.0-py3-none-any.whl 
>>> (44 kB)
>>>  || 44 kB 271 kB/s
>>> Collecting six
>>>   Downloading 
>>> https://www.piwheels.org/simple/six/six-1.16.0-py2.py3

[weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

2024-01-17 Thread Blaine

Way back in 2020 my NOAA reports stopped populating their daily values. The 
average values for the month continue to be populated at the bottom of the 
table. Since 2020 every year or so I have spent hours banging my head 
against the wall following any and all instructions on the wiki, github, 
google and this user group to attempt to repair this issue. None of the 
published instructions seem to help. I have never been successful.

If this is a problem that can be solved I would be more than happy to pay 
someone to help fix this issue knowing full well there are no guarantees 
recovery is possible. This data is important to me and having essentially 
lost years worth with no chance of recovery is a real bummer.

-- 
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/6be270a2-961f-4952-85b0-6074332671een%40googlegroups.com.

[weewx-user] READ THIS!

We have discovered a potentially serious bug. The specific situation is as
follows:

   - A V4.x configuration file;
   - Package installer;
   - Install an extension;
   - Uninstall the extension.

Under these circumstances, the extension uninstaller could remove system
files!

If you are using a V4.x configuration file, please do not install any
extensions until we get a fix out.

Apologies.

-tk

-- 
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/CAPq0zEC0hzPJ6ViEustFzdLW84%2BnTCGLzfb35pB%3DA3B_UfSuOQ%40mail.gmail.com.

[weewx-user] Re: I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

2024-01-17 Thread 'michael.k...@gmx.at' via weewx-user

Can you share your database? Maybe I can take a look at it the next weekend.

Blaine schrieb am Mittwoch, 17. Januar 2024 um 18:32:19 UTC+1:

> Way back in 2020 my NOAA reports stopped populating their daily values. 
> The average values for the month continue to be populated at the bottom of 
> the table. Since 2020 every year or so I have spent hours banging my head 
> against the wall following any and all instructions on the wiki, github, 
> google and this user group to attempt to repair this issue. None of the 
> published instructions seem to help. I have never been successful.
>
> If this is a problem that can be solved I would be more than happy to pay 
> someone to help fix this issue knowing full well there are no guarantees 
> recovery is possible. This data is important to me and having essentially 
> lost years worth with no chance of recovery is a real bummer.
>

-- 
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/381dece6-3a66-434f-aa76-646d015ebfe4n%40googlegroups.com.

Re: [weewx-user] Re: Database Error Message

Maybe, although I've run V5 without any problems on a RPi Zero! There's
something in your Belchertown skins that is triggering the long runtimes.

On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo 
wrote:

> FWIW I went back to 4.10.2 and no more database errors and the CPU spikes
> are gone. Might be time to upgrade to a PI4 or PI5.
>
> On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:
>
>> The difference is that V5 could be doing more. We don't know for sure,
>> yet, but it is probably reporting on synthetic types, which V4 was unable
>> to do.
>>
>> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo  wrote:
>>
>>> Yes I'm on a PI3 with ADSB tracking running as well. I changed the
>>> archive to 300 so we'll see how it goes. Never had the issue before
>>> upgrading to 5.0 so it must be somewhat related to that.  I've noticed that
>>> CPU usage and temps are slightly higher than average since I upgraded last
>>> night. Thanks for the suggestions.
>>>
>>>
>>>
>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>
>>>
>>>  Original message 
>>> From: vince 
>>> Date: 1/16/24 4:12 PM (GMT-05:00)
>>> To: weewx-user 
>>> Subject: Re: [weewx-user] Re: Database Error Message
>>>
>>> The log excerpt is a little short but perhaps.   I see in your log you
>>> have a 120 second archive period yet Belchertown took 125 seconds to run
>>> (which is 'very' slow), so it's possible your archive period is too fast
>>> for your hardware.  What kind of pi are you on ?  Something slower than a
>>> pi4 perhaps ?
>>>
>>> If you are on slow hardware try disabling Belchertown temporarily and
>>> see if the problem goes away.  Or alternately set your archive period to
>>> perhaps 180 seconds and try that.  Or as always you might throw hardware at
>>> it and use a faster pibut it looks like you're asking your hardware to
>>> do too much too often.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com
>>> 
>>> .
>>>
>>> --
>>>
>> You received this message because you are subscribed to the Google Groups
>>> "weewx-user" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.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/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%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/CAPq0zEAsW87u9EJ27WaXysfzS0M2VfeuzLQg%3DHgMNyHs%2Bvf_2A%40mail.gmail.com.

Re: [weewx-user] Re: Database Error Message

Michael -  guessing you have something customized under the hood causing 
this.  Again you have a few choices

   - disable Belchertown (temporarily) and see if it goes away
   - switch to the Simulator (temporarily) after saving your weewx setup 
   and see if it's related to the Acurite stuff you're using
   - disable everything 'except' weewx (temporarily) and see if it goes away
   - throw hardware at it and get a faster computer.  You might even be 
   paging on a pi3 and a 4GB pi4 or pi5 might be enough

Kinda impossible to know with skeletal data to look at, but these things 
can be difficult to dig into.

I did cause something similar yesterday trying to run on a pi5 where the 
StdReport never finished in even 5 minutes but didn't figure out why.  I 
'think' it was something related to having ancient simulated data in the db 
from timesync issues (2014 dates in the NOAA files is definitely wrong) and 
switching to a different driver.  Moving the old db aside seemed to help, 
but again I didn't dig much into it yesterday on a test system.

On Wednesday, January 17, 2024 at 12:37:35 PM UTC-8 Tom Keffer wrote:

> Maybe, although I've run V5 without any problems on a RPi Zero! There's 
> something in your Belchertown skins that is triggering the long runtimes.
>
> On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo  
> wrote:
>
>> FWIW I went back to 4.10.2 and no more database errors and the CPU spikes 
>> are gone. Might be time to upgrade to a PI4 or PI5. 
>>
>> On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:
>>
>>> The difference is that V5 could be doing more. We don't know for sure, 
>>> yet, but it is probably reporting on synthetic types, which V4 was unable 
>>> to do.
>>>
>>> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo  wrote:
>>>
 Yes I'm on a PI3 with ADSB tracking running as well. I changed the 
 archive to 300 so we'll see how it goes. Never had the issue before 
 upgrading to 5.0 so it must be somewhat related to that.  I've noticed 
 that 
 CPU usage and temps are slightly higher than average since I upgraded last 
 night. Thanks for the suggestions. 

 Sent from my Verizon, Samsung Galaxy smartphone

  Original message 
 From: vince  
 Date: 1/16/24 4:12 PM (GMT-05:00) 
 To: weewx-user  
 Subject: Re: [weewx-user] Re: Database Error Message 

 The log excerpt is a little short but perhaps.   I see in your log you 
 have a 120 second archive period yet Belchertown took 125 seconds to run 
 (which is 'very' slow), so it's possible your archive period is too fast 
 for your hardware.  What kind of pi are you on ?  Something slower than a 
 pi4 perhaps ?

 If you are on slow hardware try disabling Belchertown temporarily and 
 see if the problem goes away.  Or alternately set your archive period to 
 perhaps 180 seconds and try that.  Or as always you might throw hardware 
 at 
 it and use a faster pibut it looks like you're asking your hardware to 
 do too much too often.

 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "weewx-user" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
 To unsubscribe from this group and all its topics, send an email to 
 weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com

 .

 -- 

>>> You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.

>>> To unsubscribe from this group and stop receiving emails from it, send 
 an email to weewx-user+...@googlegroups.com.
 To view this discussion on the web visit 
 https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.com

 .

>>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this grou

Re: [weewx-user] Re: Database Error Message

2024-01-17 Thread p q

You might also swap out your database with an empty one to see if the
volume of data in the database is causing the slowness. I really doubt it,
though.

On Wed, Jan 17, 2024 at 2:32 PM vince  wrote:

> Michael -  guessing you have something customized under the hood causing
> this.  Again you have a few choices
>
>- disable Belchertown (temporarily) and see if it goes away
>- switch to the Simulator (temporarily) after saving your weewx setup
>and see if it's related to the Acurite stuff you're using
>- disable everything 'except' weewx (temporarily) and see if it goes
>away
>- throw hardware at it and get a faster computer.  You might even be
>paging on a pi3 and a 4GB pi4 or pi5 might be enough
>
> Kinda impossible to know with skeletal data to look at, but these things
> can be difficult to dig into.
>
> I did cause something similar yesterday trying to run on a pi5 where the
> StdReport never finished in even 5 minutes but didn't figure out why.  I
> 'think' it was something related to having ancient simulated data in the db
> from timesync issues (2014 dates in the NOAA files is definitely wrong) and
> switching to a different driver.  Moving the old db aside seemed to help,
> but again I didn't dig much into it yesterday on a test system.
>
> On Wednesday, January 17, 2024 at 12:37:35 PM UTC-8 Tom Keffer wrote:
>
>> Maybe, although I've run V5 without any problems on a RPi Zero! There's
>> something in your Belchertown skins that is triggering the long runtimes.
>>
>> On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo 
>> wrote:
>>
>>> FWIW I went back to 4.10.2 and no more database errors and the CPU
>>> spikes are gone. Might be time to upgrade to a PI4 or PI5.
>>>
>>> On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:
>>>
 The difference is that V5 could be doing more. We don't know for sure,
 yet, but it is probably reporting on synthetic types, which V4 was unable
 to do.

 On Tue, Jan 16, 2024 at 2:36 PM sanphillipo  wrote:

> Yes I'm on a PI3 with ADSB tracking running as well. I changed the
> archive to 300 so we'll see how it goes. Never had the issue before
> upgrading to 5.0 so it must be somewhat related to that.  I've noticed 
> that
> CPU usage and temps are slightly higher than average since I upgraded last
> night. Thanks for the suggestions.
>
>
>
> Sent from my Verizon, Samsung Galaxy smartphone
>
>
>  Original message 
> From: vince 
> Date: 1/16/24 4:12 PM (GMT-05:00)
> To: weewx-user 
> Subject: Re: [weewx-user] Re: Database Error Message
>
> The log excerpt is a little short but perhaps.   I see in your log you
> have a 120 second archive period yet Belchertown took 125 seconds to run
> (which is 'very' slow), so it's possible your archive period is too fast
> for your hardware.  What kind of pi are you on ?  Something slower than a
> pi4 perhaps ?
>
> If you are on slow hardware try disabling Belchertown temporarily and
> see if the problem goes away.  Or alternately set your archive period to
> perhaps 180 seconds and try that.  Or as always you might throw hardware 
> at
> it and use a faster pibut it looks like you're asking your hardware to
> do too much too often.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com
> 
> .
>
> --
>
 You received this message because you are subscribed to the Google
> Groups "weewx-user" group.
>
 To unsubscribe from this group and stop receiving emails from it, send
> an email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.com
> 
> .
>
 --
>>> You received this message because you are subscribed to the Google
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to weewx-user+...@googlegroups.com.
>>>
>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/11b0239b-0bd7-4d2f-a5ee-12cc99e402aan%40googlegroups.com
>>>

Re: [weewx-user] Re: Database Error Message

My current database goes back to 2018 so I guess it could be an issue. I
really don't know if that is considered old or not. The fact that it runs
fine on version 4 leads me to think that might not be it.

On Wed, Jan 17, 2024 at 6:14 PM p q  wrote:

> You might also swap out your database with an empty one to see if the
> volume of data in the database is causing the slowness. I really doubt it,
> though.
>
> On Wed, Jan 17, 2024 at 2:32 PM vince  wrote:
>
>> Michael -  guessing you have something customized under the hood causing
>> this.  Again you have a few choices
>>
>>- disable Belchertown (temporarily) and see if it goes away
>>- switch to the Simulator (temporarily) after saving your weewx setup
>>and see if it's related to the Acurite stuff you're using
>>- disable everything 'except' weewx (temporarily) and see if it goes
>>away
>>- throw hardware at it and get a faster computer.  You might even be
>>paging on a pi3 and a 4GB pi4 or pi5 might be enough
>>
>> Kinda impossible to know with skeletal data to look at, but these things
>> can be difficult to dig into.
>>
>> I did cause something similar yesterday trying to run on a pi5 where the
>> StdReport never finished in even 5 minutes but didn't figure out why.  I
>> 'think' it was something related to having ancient simulated data in the db
>> from timesync issues (2014 dates in the NOAA files is definitely wrong) and
>> switching to a different driver.  Moving the old db aside seemed to help,
>> but again I didn't dig much into it yesterday on a test system.
>>
>> On Wednesday, January 17, 2024 at 12:37:35 PM UTC-8 Tom Keffer wrote:
>>
>>> Maybe, although I've run V5 without any problems on a RPi Zero! There's
>>> something in your Belchertown skins that is triggering the long runtimes.
>>>
>>> On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo 
>>> wrote:
>>>
 FWIW I went back to 4.10.2 and no more database errors and the CPU
 spikes are gone. Might be time to upgrade to a PI4 or PI5.

 On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:

> The difference is that V5 could be doing more. We don't know for sure,
> yet, but it is probably reporting on synthetic types, which V4 was unable
> to do.
>
> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo 
> wrote:
>
>> Yes I'm on a PI3 with ADSB tracking running as well. I changed the
>> archive to 300 so we'll see how it goes. Never had the issue before
>> upgrading to 5.0 so it must be somewhat related to that.  I've noticed 
>> that
>> CPU usage and temps are slightly higher than average since I upgraded 
>> last
>> night. Thanks for the suggestions.
>>
>>
>>
>> Sent from my Verizon, Samsung Galaxy smartphone
>>
>>
>>  Original message 
>> From: vince 
>> Date: 1/16/24 4:12 PM (GMT-05:00)
>> To: weewx-user 
>> Subject: Re: [weewx-user] Re: Database Error Message
>>
>> The log excerpt is a little short but perhaps.   I see in your log
>> you have a 120 second archive period yet Belchertown took 125 seconds to
>> run (which is 'very' slow), so it's possible your archive period is too
>> fast for your hardware.  What kind of pi are you on ?  Something slower
>> than a pi4 perhaps ?
>>
>> If you are on slow hardware try disabling Belchertown temporarily and
>> see if the problem goes away.  Or alternately set your archive period to
>> perhaps 180 seconds and try that.  Or as always you might throw hardware 
>> at
>> it and use a faster pibut it looks like you're asking your hardware 
>> to
>> do too much too often.
>>
>> --
>> You received this message because you are subscribed to a topic in
>> the Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%40googlegroups.com
>> 
>> .
>>
>> --
>>
> You received this message because you are subscribed to the Google
>> Groups "weewx-user" group.
>>
> To unsubscribe from this group and stop receiving emails from it, send
>> an email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/65a704ff.050a0220.9fe86.27f4%40mx.google.com
>> 
>> .
>>
> --
 You received thi

Re: [weewx-user] Re: Database Error Message

2024-01-17 Thread p q

It's not "old" that I'm thinking, but it might be big. Though, it didn't
suddenly get bigger with 5.0, so it would be in combination with something
else. I'm betting on something going on in Belchertown.

On Wed, Jan 17, 2024 at 3:19 PM Michael Sanphillipo 
wrote:

> My current database goes back to 2018 so I guess it could be an issue. I
> really don't know if that is considered old or not. The fact that it runs
> fine on version 4 leads me to think that might not be it.
>
> On Wed, Jan 17, 2024 at 6:14 PM p q  wrote:
>
>> You might also swap out your database with an empty one to see if the
>> volume of data in the database is causing the slowness. I really doubt it,
>> though.
>>
>> On Wed, Jan 17, 2024 at 2:32 PM vince  wrote:
>>
>>> Michael -  guessing you have something customized under the hood causing
>>> this.  Again you have a few choices
>>>
>>>- disable Belchertown (temporarily) and see if it goes away
>>>- switch to the Simulator (temporarily) after saving your weewx
>>>setup and see if it's related to the Acurite stuff you're using
>>>- disable everything 'except' weewx (temporarily) and see if it goes
>>>away
>>>- throw hardware at it and get a faster computer.  You might even be
>>>paging on a pi3 and a 4GB pi4 or pi5 might be enough
>>>
>>> Kinda impossible to know with skeletal data to look at, but these things
>>> can be difficult to dig into.
>>>
>>> I did cause something similar yesterday trying to run on a pi5 where the
>>> StdReport never finished in even 5 minutes but didn't figure out why.  I
>>> 'think' it was something related to having ancient simulated data in the db
>>> from timesync issues (2014 dates in the NOAA files is definitely wrong) and
>>> switching to a different driver.  Moving the old db aside seemed to help,
>>> but again I didn't dig much into it yesterday on a test system.
>>>
>>> On Wednesday, January 17, 2024 at 12:37:35 PM UTC-8 Tom Keffer wrote:
>>>
 Maybe, although I've run V5 without any problems on a RPi Zero! There's
 something in your Belchertown skins that is triggering the long runtimes.

 On Wed, Jan 17, 2024 at 6:42 AM Michael Sanphillipo 
 wrote:

> FWIW I went back to 4.10.2 and no more database errors and the CPU
> spikes are gone. Might be time to upgrade to a PI4 or PI5.
>
> On Tuesday, January 16, 2024 at 5:41:39 PM UTC-5 Tom Keffer wrote:
>
>> The difference is that V5 could be doing more. We don't know for
>> sure, yet, but it is probably reporting on synthetic types, which V4 was
>> unable to do.
>>
>> On Tue, Jan 16, 2024 at 2:36 PM sanphillipo 
>> wrote:
>>
>>> Yes I'm on a PI3 with ADSB tracking running as well. I changed the
>>> archive to 300 so we'll see how it goes. Never had the issue before
>>> upgrading to 5.0 so it must be somewhat related to that.  I've noticed 
>>> that
>>> CPU usage and temps are slightly higher than average since I upgraded 
>>> last
>>> night. Thanks for the suggestions.
>>>
>>>
>>>
>>> Sent from my Verizon, Samsung Galaxy smartphone
>>>
>>>
>>>  Original message 
>>> From: vince 
>>> Date: 1/16/24 4:12 PM (GMT-05:00)
>>> To: weewx-user 
>>> Subject: Re: [weewx-user] Re: Database Error Message
>>>
>>> The log excerpt is a little short but perhaps.   I see in your log
>>> you have a 120 second archive period yet Belchertown took 125 seconds to
>>> run (which is 'very' slow), so it's possible your archive period is too
>>> fast for your hardware.  What kind of pi are you on ?  Something slower
>>> than a pi4 perhaps ?
>>>
>>> If you are on slow hardware try disabling Belchertown temporarily
>>> and see if the problem goes away.  Or alternately set your archive 
>>> period
>>> to perhaps 180 seconds and try that.  Or as always you might throw 
>>> hardware
>>> at it and use a faster pibut it looks like you're asking your 
>>> hardware
>>> to do too much too often.
>>>
>>> --
>>> You received this message because you are subscribed to a topic in
>>> the Google Groups "weewx-user" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to
>>> weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/23f37da3-0240-473d-85c1-8102ac757590n%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

Re: [weewx-user] Re: Database Error Message

It's not Belchertown. It's not db size. I ran many tests.

v5 and Belchertown can easily coexist on a pi3 or so system. If every time
through you're exceeding the default archive period you're doing something
custom to make that happen. I keep coming back to the known issue/slowness
with synthetic measurements that Tom mentioned a few times recently.

Here's the test I just did with a newly flashed 32-bit pi3+ running a fully
patched latest raspios...

On a clean pi3+ with weewx v5 via pip and Belchertown installed, using the
Simulator driver and no old pre-existing db present:

Generated 8 files for report SeasonsReport in 3.45 seconds
Generated 56 images for report SeasonsReport in 3.43 seconds
Generated 12 files for report Belchertown in 6.93 seconds
(elapsed time from writing to the db to Belchertown done was 14 seconds)

I then stopped weewx, overwrote my weewx.sdb with my production system data
with 17+ years of data, pre-seeded the Seasons NOAA tree so I didn't need
to wait for them to be regenerated once for this test, then restarted
weewx. So it's running the same skins with 17+ years of data, with the
Seasons NOAA files having been pregenerated and dropped into place

Generated 8 files for report SeasonsReport in 4.28 seconds
Generated 44 images for report SeasonsReport in 6.75 seconds
*Generated 236 files for report Belchertown in 266.59 seconds. <=*
(elapsed time from writing to db to Belchertown done was 4:37 so pretty
close to a 5-minute default archive period)

Why ? Because the 'first' Belchertown run generates its 'own' copy of the
NOAA files down under the Belchertown public_html tree. It had to do that
(for me) with 17+ years of month and year files which takes some time to
complete. Running htop I saw two virtual cpus pegged at 100% throughout
until it completed.

After that Belchertown NOAA files are also pre-seeded there too so it's
just doing normal incremental updates for future report runs. Each skin
that generates NOAA files has to work hard once to do so vs. a pre-existing
db if you start with a legacy db. You only have to bleed through that
once. Subsequent runs should be quick. Lets see...

So I let it run another cycle.looks fine

Generated 8 files for report SeasonsReport in 3.05 seconds
Generated 18 images for report SeasonsReport in 1.22 seconds
Generated 12 files for report Belchertown in 8.26 seconds
(elapsed time this cycle was 14 seconds)

And one more cycle.looks fine

Generated 8 files for report SeasonsReport in 2.94 seconds
Generated 18 images for report SeasonsReport in 1.68 seconds
Generated 12 files for report Belchertown in 7.80 seconds
(elapsed time for this cycle was 14 seconds)

Again - if you are continually exceeding perhaps 15 seconds for Belchertown
to run on a pi3 or better you are doing something custom to make that
happen. I just keep coming beck mentally to Tom's previous responses re:
synthetic measurements.

The original poster uses an Acurite which I don't know enough about to know
for certain, but are you using that feature and not even knowing it ?
Would providing your (sanitized) weewx.conf perhaps be of use in helping
figure it out ?

--
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/9815dc0c-c883-43a3-b9e4-87f4e3a3986fn%40googlegroups.com.

Re: [weewx-user] Re: Database Error Message

I'm also using my Pi3 as a MQTT server feeding Belchertown I'm not sure if
that makes a difference or not. With all of that being said everything runs
smoothly on WeeWxVersion 4. I know Tom said that version 5 does a lot more.
I also use my PI3 for ADSB sending data to a few ADSB sites.

On Wed, Jan 17, 2024 at 7:25 PM vince  wrote:

> It's not Belchertown.  It's not db size.  I ran many tests.
>
> v5 and Belchertown can easily coexist on a pi3 or so system.  If every
> time through you're exceeding the default archive period you're doing
> something custom to make that happen.  I keep coming back to the known
> issue/slowness with synthetic measurements that Tom mentioned a few times
> recently.
>
> Here's the test I just did with a newly flashed 32-bit pi3+ running a
> fully patched latest raspios...
>
> On a clean pi3+ with weewx v5 via pip and Belchertown installed, using the
> Simulator driver and no old pre-existing db present:
>
> Generated 8 files for report SeasonsReport in 3.45 seconds
> Generated 56 images for report SeasonsReport in 3.43 seconds
> Generated 12 files for report Belchertown in 6.93 seconds
> (elapsed time from writing to the db to Belchertown done was 14 seconds)
>
> I then stopped weewx, overwrote my weewx.sdb with my production system
> data with 17+ years of data, pre-seeded the Seasons NOAA tree so I didn't
> need to wait for them to be regenerated once for this test, then restarted
> weewx.  So it's running the same skins with 17+ years of data, with the
> Seasons NOAA files having been pregenerated and dropped into place
>
> Generated 8 files for report SeasonsReport in 4.28 seconds
> Generated 44 images for report SeasonsReport in 6.75 seconds
> *Generated 236 files for report Belchertown in 266.59 seconds.  <=*
> (elapsed time from writing to db to Belchertown done was 4:37 so pretty
> close to a 5-minute default archive period)
>
> Why ?  Because the 'first' Belchertown run generates its 'own' copy of
> the NOAA files down under the Belchertown public_html tree.  It had to do
> that (for me) with 17+ years of month and year files which takes some time
> to complete.   Running htop I saw two virtual cpus pegged at 100%
> throughout until it completed.
>
> After that Belchertown NOAA files are also pre-seeded there too so it's
> just doing normal incremental updates for future report runs.  Each skin
> that generates NOAA files has to work hard once to do so vs. a pre-existing
> db if you start with a legacy db.   You only have to bleed through that
> once.  Subsequent runs should be quick.  Lets see...
>
> So I let it run another cycle.looks fine
>
> Generated 8 files for report SeasonsReport in 3.05 seconds
> Generated 18 images for report SeasonsReport in 1.22 seconds
> Generated 12 files for report Belchertown in 8.26 seconds
> (elapsed time this cycle was 14 seconds)
>
> And one more cycle.looks fine
>
> Generated 8 files for report SeasonsReport in 2.94 seconds
> Generated 18 images for report SeasonsReport in 1.68 seconds
> Generated 12 files for report Belchertown in 7.80 seconds
> (elapsed time for this cycle was 14 seconds)
>
> Again - if you are continually exceeding perhaps 15 seconds for
> Belchertown to run on a pi3 or better you are doing something custom to
> make that happen.  I just keep coming beck mentally to Tom's previous
> responses re: synthetic measurements.
>
> The original poster uses an Acurite which I don't know enough about to
> know for certain, but are you using that feature and not even knowing it ?
> Would providing your (sanitized) weewx.conf perhaps be of use in helping
> figure it out ?
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/9815dc0c-c883-43a3-b9e4-87f4e3a3986fn%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/CAAsGudpq8kEiq7rP5J%3DhhULuyZfhzG0yJoKh0fyyvCPFogGHAQ%40mail.gmail.com.

Re: [weewx-user] Re: Database Error Message

Here is a sanitized copy of my Weewx.conf. I do have all of my Belchertown
settings in the weewx conf , so it adds a bunch of lines. I'm really not
sure about the synthetic measurements.


# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.10.2

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Riverside Belcamp, MD"

# Latitude in decimal degrees. Negative for southern hemisphere
latitude = 39.478306
# Longitude in decimal degrees. Negative for western hemisphere.
longitude = -76.252562

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 100, foot

# Set to type of station hardware. There must be a corresponding stanza
# in this file with a 'driver' parameter indicating the driver to be
used.
station_type = AcuRite

# If you have a website, you may specify an URL
station_url = https://belcampmdweather.tech/weewx/belchertown/

# The start of the rain year (1=January; 10=October, etc.). This is
# downloaded from the station if the hardware supports it.
rain_year_start = 1

# Start of week (0=Monday, 6=Sunday)
week_start = 6

##

[AcuRite]
# This section is for AcuRite weather stations.

# The station model, e.g., 'AcuRite 01025' or 'AcuRite 02032C'
model = AcuRite 02032C

# The driver to use:
driver = weewx.drivers.acurite
use_constants = False
##

#   This section is for uploading data to Internet sites

[StdRESTful]

[[StationRegistry]]
# To register this weather station with weewx, set this to true
register_this_station = true

[[AWEKAS]]
# This section is for configuring posts to AWEKAS.

# If you wish to do this, set the option 'enable' to true,
# and specify a username and password.
# To guard against parsing errors, put the password in quotes.
enable = true
username = ##
password = #

[[CWOP]]
# This section is for configuring posts to CWOP.

# If you wish to do this, set the option 'enable' to true,
# and specify the station ID (e.g., CW1234).
enable = true
station = FW5836

# If this is an APRS (radio amateur) station, uncomment
# the following and replace with a passcode (e.g., 12345).
#passcode = replace_me (APRS stations only)

[[PWSweather]]
# This section is for configuring posts to PWSweather.com.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = true
station = KMDBELCA3
password = #

[[WOW]]
# This section is for configuring posts to WOW.

# If you wish to do this, set the option 'enable' to true,
# and specify a station and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = replace_me
password = replace_me

[[Wunderground]]
# This section is for configuring posts to the Weather Underground.

# If you wish to do this, set the option 'enable' to true,
# and specify a station (e.g., 'KORHOODR3') and password.
# To guard against parsing errors, put the password in quotes.
enable = false
station = KMDBELCA3
password = 

# If you plan on using wunderfixer, set the following
# to your API key:
api_key = ###

# Set the following to True to have weewx use the WU "Rapidfire"
# protocol. Not all hardware can support it. See the User's Guide.
rapidfire = True

post_indoor_observations = true

[[WeatherCloud]]
id = f
key = ##

[[MQTT]]
server_url = mqtt://:#@localhost:1883/
topic = weather
#server_url = mqtt://broker.hivemq.com:1883/
#topic = weather/belcamp

[weewx-user] Re: Weewx and Meteobridge - website update

When you say to add the meta refresh to the "top of the template", which 
configuration file are you referring to please?

Thanks..

On Tuesday, January 9, 2024 at 9:22:27 AM UTC-5 gary@gmail.com wrote:

> What skin are you using?
>
> On Sunday, January 7, 2024 at 1:36:16 PM UTC-5 bhouseski wrote:
>
>> Recently I was able to get Weewx running on a Raspberry Pi 4B, pulling 
>> data from a Vantage Pro2 connected to a D-Link DIR-505 loaded with 
>> Meteobridge (vantage is connected to the Meteobridge via USB).  All is well 
>> except I cannot get the website to autoload new data (I have to keep 
>> hitting refresh on my web browser).  I have played around with the archive 
>> interval, but have had no success.
>>
>> any idea's how to make this work?
>>
>

-- 
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/b73d8ddc-0118-4b68-bf60-802838802898n%40googlegroups.com.

[weewx-user] Web page will not refresh after update to 5.0

After an update of Weewx 4.10.2  to 5.0, the data on the web page 

http:///weewx/index.html

no longer refreshes.

Summary data:

uname -a
Linux linux-3wjh 5.14.21-150500.55.39-default #1 SMP PREEMPT_DYNAMIC Tue 
Dec 5 10:06:35 UTC 2023 (2e4092e) x86_64 x86_64 x86_64 GNU/Linux

openSUSE Leap  15.5

~> weewxd --version
5.0.0

~> python3 --version
Python 3.6.15

systemctl status weewx
● weewx.service - WeeWX
 Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: disabled)
 Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min ago
   Docs: https://weewx.com/docs
   Main PID: 9772 (python3)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/weewx.service
 └─ 9772 python3 /usr/share/weewx/weewxd.py 
/etc/weewx/weewx.conf

Weewx shows to be running OK as seen in the attached logs file.

If I roll back to 4.10.2, the web page refreshes as normal.


-- 
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/12cd9a08-a116-4b47-bb41-0609df53585en%40googlegroups.com.

~> weewxd --version
5.0.0

~> python3 --version
Python 3.6.15

systemctl status weewx
● weewx.service - WeeWX
 Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: disabled)
 Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min ago
   Docs: https://weewx.com/docs
   Main PID: 9772 (python3)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/weewx.service
 └─ 9772 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf

Jan 17 19:21:23 linux-3wjh weewxd[9772]: INFO weewx.restx: AWEKAS: Posting not 
enabled.
Jan 17 19:21:23 linux-3wjh weewxd[9772]: INFO weewx.engine: 'pyephem' detected, 
extended almanac data is available
Jan 17 19:21:23 linux-3wjh weewxd[9772]: INFO __main__: Starting up weewx 
version 5.0.0
Jan 17 19:21:25 linux-3wjh weewxd[9772]: INFO weewx.engine: Clock error is 2.30 
seconds (positive is fast)
Jan 17 19:21:25 linux-3wjh weewxd[9772]: INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan 17 19:21:25 linux-3wjh weewxd[9772]: INFO weewx.manager: Starting backfill 
of daily summaries
Jan 17 19:21:25 linux-3wjh weewxd[9772]: INFO weewx.manager: Daily summaries up 
to date
Jan 17 19:21:28 linux-3wjh weewxd[9772]: INFO weewx.engine: Starting main 
packet loop.
Jan 17 19:30:19 linux-3wjh weewxd[9772]: INFO weewx.manager: Added record 
2024-01-17 19:30:00 EST (1705537800) to datab>
Jan 17 19:30:19 linux-3wjh weewxd[9772]: INFO weewx.manager: Added record 
2024-01-17 19:30:00 EST (1705537800) to daily>
lines 1-19/19 (END)


Messages

2024-01-17T19:20:47.415927-05:00 linux-3wjh weewxd[6205]: INFO __main__: 
Received signal TERM (15).
2024-01-17T19:20:47.416116-05:00 linux-3wjh weewxd[6205]: INFO weewx.engine: 
Main loop exiting. Shutting engine down.
2024-01-17T19:20:47.917580-05:00 linux-3wjh weewxd[6205]: INFO __main__: 
Terminating weewx version 5.0.0
2024-01-17T19:21:19.114820-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Initializing weewxd version 5.0.0
2024-01-17T19:21:19.115071-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Command line: /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf
2024-01-17T19:21:19.115168-05:00 linux-3wjh weewxd[9772]: INFO __main__: Using 
Python 3.6.15 (default, Sep 23 2021, 15:41:43) [GCC]
2024-01-17T19:21:19.115255-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Located at /usr/bin/python3
2024-01-17T19:21:19.125725-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Platform Linux-5.14.21-150500.55.39-default-x86_64-with-glibc2.3.4
2024-01-17T19:21:19.125891-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Locale: 'en_US.UTF-8'
2024-01-17T19:21:19.126000-05:00 linux-3wjh weewxd[9772]: INFO __main__: Entry 
path: /usr/share/weewx/weewxd.py
2024-01-17T19:21:19.126088-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
WEEWX_ROOT: /
2024-01-17T19:21:19.126174-05:00 linux-3wjh weewxd[9772]: INFO __main__: 
Configuration file: /etc/weewx/weewx.conf
2024-01-17T19:21:19.126260-05:00 linux-3wjh weewxd[9772]: INFO __main__: User 
module: /etc/weewx/bin/user
2024-01-17T19:21:19.126826-05:00 linux-3wjh weewxd[9772]: INFO __main__: Debug: 0
2024-01-17T19:21:19.127260-05:00 linux-3wjh weewxd[9772]: INFO weewx.engine: 
Loading station type Vantage (weewx.drivers.vantage)
2024-01-17T19:21:23.647428-05:00 linux-3wjh weewxd[9772]: INFO weewx.engine: 
StdConvert target unit is 0x1
2024-01-17T19:21:23.648398-05:00 linux-3wjh weewxd[9772]: INFO 
weewx.wxservices: StdWXCalculate will use data binding wx_binding
2024-01-17T19:21:23.664377-05:00 linux-3wjh weewxd[9772]: INFO weewx.engine: 
Archive will use data binding wx_binding
2024-01-17T19:21:23.664567-05:00 linux-3wjh weewxd[9772]: INFO weewx.engine: 
Record generation will be attempt

[weewx-user] Re: Web page will not refresh after update to 5.0

Adding logs after roll back to 4.10.2.

On Wednesday, January 17, 2024 at 8:20:05 PM UTC-5 Jim Wilkerson wrote:

> After an update of Weewx 4.10.2  to 5.0, the data on the web page 
>
> http:///weewx/index.html
>
> no longer refreshes.
>
> Summary data:
>
> uname -a
> Linux linux-3wjh 5.14.21-150500.55.39-default #1 SMP PREEMPT_DYNAMIC Tue 
> Dec 5 10:06:35 UTC 2023 (2e4092e) x86_64 x86_64 x86_64 GNU/Linux
>
> openSUSE Leap  15.5
>
> ~> weewxd --version
> 5.0.0
>
> ~> python3 --version
> Python 3.6.15
>
> systemctl status weewx
> ● weewx.service - WeeWX
>  Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
> vendor preset: disabled)
>  Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min ago
>Docs: https://weewx.com/docs
>Main PID: 9772 (python3)
>   Tasks: 1 (limit: 4915)
>  CGroup: /system.slice/weewx.service
>  └─ 9772 python3 /usr/share/weewx/weewxd.py 
> /etc/weewx/weewx.conf
>
> Weewx shows to be running OK as seen in the attached logs file.
>
> If I roll back to 4.10.2, the web page refreshes as normal.
>
>
>

-- 
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/6ec1fcdd-0af6-40a5-a7ae-677ac0cc0a17n%40googlegroups.com.

sudo journalctl -r -u weewx

Jan 17 20:30:20 linux-3wjh python3[20476]: weewx[20476] INFO 
weewx.reportengine: Copied 5 files to /var/www/html/weewx
Jan 17 20:30:20 linux-3wjh python3[20476]: weewx[20476] INFO 
weewx.imagegenerator: Generated 30 images for report SeasonsReport in 0.55 
seconds
Jan 17 20:30:19 linux-3wjh python3[20476]: weewx[20476] INFO 
weewx.cheetahgenerator: Generated 8 files for report SeasonsReport in 0.51 
seconds
Jan 17 20:30:19 linux-3wjh python3[20476]: weewx[20476] INFO weewx.manager: 
Added record 2024-01-17 20:30:00 EST (1705541400) to daily summary in 
'weewx.sdb'
Jan 17 20:30:19 linux-3wjh python3[20476]: weewx[20476] INFO weewx.manager: 
Added record 2024-01-17 20:30:00 EST (1705541400) to database 'weewx.sdb'
Jan 17 20:20:36 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Starting main packet loop.
Jan 17 20:20:33 linux-3wjh python3[20476]: weewx[20476] INFO weewx.manager: 
Daily summaries up to date
Jan 17 20:20:33 linux-3wjh python3[20476]: weewx[20476] INFO weewx.manager: 
Starting backfill of daily summaries
Jan 17 20:20:33 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Using binding 'wx_binding' to database 'weew>
Jan 17 20:20:33 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Clock error is 2.44 seconds (positive is fas>
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Starting 
up weewx version 4.10.2
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
'pyephem' detected, extended almanac data is>
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: 
AWEKAS: Posting not enabled.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: WOW: 
Posting not enabled.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: CWOP: 
Posting not enabled.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: 
PWSweather: Posting not enabled.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: 
Wunderground: Posting not enabled.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.restx: 
StationRegistry: Registration not requested.
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Using archive interval of 1800 seconds (spec>
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Record generation will be attempted in 'hard>
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Archive will use data binding wx_binding
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_>
Jan 17 20:20:31 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
StdConvert target unit is 0x1
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO weewx.engine: 
Loading station type Vantage (weewx.drivers.>
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Debug is 0
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Using 
configuration file /etc/weewx/weewx.conf
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Locale 
is 'en_US.UTF-8'
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Platform 
Linux-5.14.21-150500.55.39-default-x86_>
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Located 
at /usr/bin/python3
Jan 17 20:20:26 linux-3wjh python3[20476]: weewx[20476] INFO __main__: Using 
Python 3.6.15 (default, Sep 23 2

[weewx-user] Re: Web page will not refresh after update to 5.0

2024-01-17 Thread gjr80

Unfortunately the log extracts you have provided lack detail and are 
truncated and consequently of not much help. Please try again noting the 
advice in the *How to get a good, useful log* section 

 
of the *Help! Posting to weewx user* wiki page 
. Make 
sure your log extract covers the full WeeWX startup and at least two 
archive intervals of activity. 

Gary
On Thursday 18 January 2024 at 11:20:05 UTC+10 wil...@gmail.com wrote:

> After an update of Weewx 4.10.2  to 5.0, the data on the web page 
>
> http:///weewx/index.html
>
> no longer refreshes.
>
> Summary data:
>
> uname -a
> Linux linux-3wjh 5.14.21-150500.55.39-default #1 SMP PREEMPT_DYNAMIC Tue 
> Dec 5 10:06:35 UTC 2023 (2e4092e) x86_64 x86_64 x86_64 GNU/Linux
>
> openSUSE Leap  15.5
>
> ~> weewxd --version
> 5.0.0
>
> ~> python3 --version
> Python 3.6.15
>
> systemctl status weewx
> ● weewx.service - WeeWX
>  Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
> vendor preset: disabled)
>  Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min ago
>Docs: https://weewx.com/docs
>Main PID: 9772 (python3)
>   Tasks: 1 (limit: 4915)
>  CGroup: /system.slice/weewx.service
>  └─ 9772 python3 /usr/share/weewx/weewxd.py 
> /etc/weewx/weewx.conf
>
> Weewx shows to be running OK as seen in the attached logs file.
>
> If I roll back to 4.10.2, the web page refreshes as normal.
>
>
>

-- 
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/04137fca-b071-4cc8-a12c-42952a23033cn%40googlegroups.com.

Re: [weewx-user] Database Error Message

2024-01-17 Thread Graham Eddy

maybe a bit short?
⊣GE⊢

> On 18 Jan 2024, at 11:55 am, Michael Sanphillipo  
> wrote:
> 
> archive_interval = 120

-- 
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/5DAE5F07-0D79-4BC7-A67D-09FA84035018%40geddy.au.

[weewx-user] Re: Web page will not refresh after update to 5.0

Jim please set debug=1 and restart weewx. For logs you might try to do 
‘sudo journalctl -u weewx -n 200’ so we see the last 200 lines and not a 
truncated log,. We need to see your reports actually run and where they are 
being written to. My wild guess is your v5 is writing to a different place 
than your v4 does.

On Wednesday, January 17, 2024 at 5:49:58 PM UTC-8 gjr80 wrote:

> Unfortunately the log extracts you have provided lack detail and are 
> truncated and consequently of not much help. Please try again noting the 
> advice in the *How to get a good, useful log* section 
> 
>  
> of the *Help! Posting to weewx user* wiki page 
> . Make 
> sure your log extract covers the full WeeWX startup and at least two 
> archive intervals of activity. 
>
> Gary
> On Thursday 18 January 2024 at 11:20:05 UTC+10 wil...@gmail.com wrote:
>
>> After an update of Weewx 4.10.2  to 5.0, the data on the web page 
>>
>> http:///weewx/index.html
>>
>> no longer refreshes.
>>
>> Summary data:
>>
>> uname -a
>> Linux linux-3wjh 5.14.21-150500.55.39-default #1 SMP PREEMPT_DYNAMIC Tue 
>> Dec 5 10:06:35 UTC 2023 (2e4092e) x86_64 x86_64 x86_64 GNU/Linux
>>
>> openSUSE Leap  15.5
>>
>> ~> weewxd --version
>> 5.0.0
>>
>> ~> python3 --version
>> Python 3.6.15
>>
>> systemctl status weewx
>> ● weewx.service - WeeWX
>>  Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
>> vendor preset: disabled)
>>  Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min ago
>>Docs: https://weewx.com/docs
>>Main PID: 9772 (python3)
>>   Tasks: 1 (limit: 4915)
>>  CGroup: /system.slice/weewx.service
>>  └─ 9772 python3 /usr/share/weewx/weewxd.py 
>> /etc/weewx/weewx.conf
>>
>> Weewx shows to be running OK as seen in the attached logs file.
>>
>> If I roll back to 4.10.2, the web page refreshes as normal.
>>
>>
>>

-- 
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/7ef111b5-8427-450e-bfbe-a6bb342e42a4n%40googlegroups.com.

[weewx-user] Re: Error upgrading to v5.0

2024-01-17 Thread Marty b

I was able to figure out how to fix this.  I had to delete the 'six.pyc' 
file in /usr/share/weewx/ .  After doing that, the install was able to 
complete.  Having some other issues now, but will create a new thread for 
them if I can't figure it out...

On Wednesday, January 17, 2024 at 8:58:12 AM UTC-8 Marty b wrote:

> Hello,
>
> I tried upgrading to v5.0 and am getting errors:
> pi@WeeWx2021:/var/log/apache2 $ sudo apt-get update
> Hit:1 https://weewx.com/apt/python3 buster InRelease
> Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
> Hit:3 http://archive.raspberrypi.org/debian buster InRelease
> Reading package lists... Done
> pi@WeeWx2021:/var/log/apache2 $ sudo apt-get upgrade
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Calculating upgrade... Done
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> 1 not fully installed or removed.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Setting up weewx (5.0.0-1) ...
> Using root:root as user:group
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 58, in main
> module = importlib.import_module(f'weectllib.{subcommand}_cmd')
>   File "/usr/lib/python3.7/importlib/__init__.py", line 127, in 
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1006, in _gcd_import
>   File "", line 983, in _find_and_load
>   File "", line 953, in 
> _find_and_load_unlocked
>   File "", line 219, in 
> _call_with_frames_removed
>   File "", line 1006, in _gcd_import
>   File "", line 983, in _find_and_load
>   File "", line 967, in 
> _find_and_load_unlocked
>   File "", line 677, in _load_unlocked
>   File "", line 728, in exec_module
>   File "", line 219, in 
> _call_with_frames_removed
>   File "/usr/share/weewx/weectllib/__init__.py", line 12, in 
> import configobj
>   File "/usr/lib/python3/dist-packages/configobj.py", line 22, in 
> import six
> ImportError: bad magic number in 'six': b'\x03\xf3\r\n'
> dpkg: error: --compare-versions takes three arguments:  
>  
>
> Type dpkg --help for help about installing and deinstalling packages [*];
> Use 'apt' or 'aptitude' for user-friendly package management;
> Type dpkg -Dhelp for a list of dpkg debug flag values;
> Type dpkg --force-help for a list of forcing options;
> Type dpkg-deb --help for help about manipulating *.deb files;
>
> Options marked [*] produce a lot of output - pipe it through 'less' or 
> 'more' !
> Using debconf configuration values from previous install
> Traceback (most recent call last):
>   File "/usr/share/weewx/weectl.py", line 74, in 
> main()
>   File "/usr/share/weewx/weectl.py", line 58, in main
> module = importlib.import_module(f'weectllib.{subcommand}_cmd')
>   File "/usr/lib/python3.7/importlib/__init__.py", line 127, in 
> import_module
> return _bootstrap._gcd_import(name[level:], package, level)
>   File "", line 1006, in _gcd_import
>   File "", line 983, in _find_and_load
>   File "", line 953, in 
> _find_and_load_unlocked
>   File "", line 219, in 
> _call_with_frames_removed
>   File "", line 1006, in _gcd_import
>   File "", line 983, in _find_and_load
>   File "", line 967, in 
> _find_and_load_unlocked
>   File "", line 677, in _load_unlocked
>   File "", line 728, in exec_module
>   File "", line 219, in 
> _call_with_frames_removed
>   File "/usr/share/weewx/weectllib/__init__.py", line 12, in 
> import configobj
>   File "/usr/lib/python3/dist-packages/configobj.py", line 22, in 
> import six
> ImportError: bad magic number in 'six': b'\x03\xf3\r\n'
> dpkg: error processing package weewx (--configure):
>  installed weewx package post-installation script subprocess returned 
> error exit status 1
> Errors were encountered while processing:
>  weewx
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> Please let me know what I need to do to resolve this.
>
> 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/23047402-519e-40e8-be6c-ba051a4f8dd4n%40googlegroups.com.

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

I would guess that the driver is not calculating "rain" correctly.

WeeWX uses "rain" for the values in the archive table and daily summaries.
The WU uses some mysterious combination of "dayRain" and "hourRain" (they
don't say) for rain totals.

The driver calculates "rain" as the difference in some rain total (I think
differences in "dayRain", but it's hard to tell from the code). This is as
it should be.

You say that the "spikes" occur after power outages. I'm thinking the value
for "dayRain" also changes.

I hate to "pass the buck," but I've taken this as far as I can. I don't
think there's a problem in the WeeWX code --- after all, it works correctly
for thousands of users and many different drivers. The only unusual
circumstances in your case is the use of metric units in the database, and
the use of the ws6in1 driver.

Please ask the author of the driver to double check the calculations for
rain. Ask him to try a power failure and see what happens to "dayRain".

-tk





On Wed, Jan 17, 2024 at 1:22 AM Ξ  wrote:

> Hi Tom,
>
> Yes, that's exactly the ws6in1 driver I'm using, ever since July 2022.
> target_unit is set to METRICWX and that's how I've always had it since I
> started running weewx 5 years ago on this R-Pi initially with an Acurite
> station.
>
> Thanks a bunch!
>
> On Monday, January 15, 2024 at 1:03:41 AM UTC+2 Tom Keffer wrote:
>
>> I think I'm getting close to figuring this out. Can you confirm the
>> following:
>>
>> - You are using the "ws6in1" driver, right? This one
>> .
>> - What unit system are you using in your database? This is the setting
>> for option "*target_unit*".
>>
>> -tk
>>
>> On Sun, Jan 14, 2024 at 10:56 AM Ξ  wrote:
>>
>>> and the NOAA reports show it too:
>>>
>>>MONTHLY CLIMATOLOGICAL SUMMARY for Sep 2023
>>>
>>> NAME: Dolni Okol
>>> ELEV: 1010 metersLAT: 42-29.40 NLONG: 023-29.70 E
>>>
>>>
>>>TEMPERATURE (C), RAIN (mm), WIND SPEED (m/s)
>>>
>>>  HEAT   COOL AVG
>>>   MEAN   DEGDEG  WIND
>>> DOM   INSIDE  INS
>>> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED
>>> HIGH   TIMEDIR   HIGHLOW
>>>
>>> -
>>>  01   16.7   28.7  15:308.5  07:301.30.00.00.1
>>>  2.7  14:30165   22.8   20.3
>>>  02   18.6   33.0  16:15   10.7  07:300.00.60.00.0
>>>  2.1  16:30186   23.1   20.7
>>>  03   18.8   32.7  16:15   10.0  07:300.00.80.00.1
>>>  2.2  10:45168   23.2   20.6
>>>  04   12.3   16.5  00:15   11.1  20:155.70.0   25.60.1
>>>  4.2  07:30 95   22.5   19.0
>>>  05   13.3   20.0  15:45   11.5  07:304.70.0   11.60.0
>>>  2.0  02:00282   19.0   18.3
>>>  06   15.7   25.1  16:07   10.5  04:402.30.00.00.0
>>>  2.1  14:02161   18.8   17.6
>>>  07   17.2   25.7  16:02   14.0  07:190.80.00.80.0
>>>  2.6  12:09152   19.4   18.3
>>>  08   17.3   30.3  15:36   10.3  07:180.70.00.80.0
>>>  2.5  10:30161   20.4   18.4
>>>  09   16.9   32.8  16:199.2  07:331.10.00.00.1
>>>  2.2  15:13188   21.0   18.7
>>>  10   14.9   29.4  16:246.1  06:523.10.00.00.1
>>>  2.2  14:40184   21.1   17.9
>>>  11   15.2   32.1  15:306.5  06:012.80.00.00.0
>>>  1.9  15:10163   21.2   18.0
>>>  12   15.5   34.3  17:105.3  07:072.50.00.00.0
>>>  2.0  12:38155   20.9   17.7
>>>  13   16.0   36.0  17:177.0  07:082.00.00.00.0
>>>  2.1  15:20168   21.5   18.1
>>>  14   18.0   32.7  15:41   10.1  03:420.00.00.00.1
>>>  2.2  14:23 86   21.9   19.3
>>>  15   18.0   29.2  16:13   11.1  07:040.00.00.00.0
>>>  2.0  11:07185   22.6   20.0
>>>  16   17.5   28.7  17:15   13.9  23:450.50.0   59.20.0
>>>  1.7  15:02188   22.0   20.7
>>>  17   16.0   29.0  16:20   11.2  23:542.00.00.80.0
>>>  1.1  16:16172   20.9   19.6
>>>  18   16.4   29.9  15:559.8  23:531.60.00.00.0
>>>  2.0  15:16182   20.4   19.0
>>>  19   14.6   29.6  16:437.1  06:423.40.00.40.0
>>>  1.8  23:47146   20.0   17.8
>>>  20   16.6   31.8  17:339.3  07:271.40.09.60.1
>>>  2.5  00:04164   21.2   18.3
>>>  21   16.8   33.2  17:23   10.6  02:411.20.00.40.0
>>>  2.0  20:39295   20.6   19.1
>>>  22   19.7   33.1  16:33   11.2  07:130.01.70.00.1
>>>  4.2  15:00290   22.3   19.2
>>>  23   21.2   36.6  15:47   11.7  07:300.03.20.00.0
>>>  2.2  12:23289   23.6   20.5
>>>  24   17.8   24.7  15:31   12.8  04:530.20.00.00.0
>>>  1.8  10:08243   23.4   21.5
>>>  2

Re: [weewx-user] I'm desperate to fix my NOAA reports. Can I please pay someone to help fix my database and recover this data?

Have you tried completely deleting all NOAA reports and letting weewx
regenerate them?

On Wed, Jan 17, 2024 at 9:32 AM Blaine  wrote:

> Way back in 2020 my NOAA reports stopped populating their daily values.
> The average values for the month continue to be populated at the bottom of
> the table. Since 2020 every year or so I have spent hours banging my head
> against the wall following any and all instructions on the wiki, github,
> google and this user group to attempt to repair this issue. None of the
> published instructions seem to help. I have never been successful.
>
> If this is a problem that can be solved I would be more than happy to pay
> someone to help fix this issue knowing full well there are no guarantees
> recovery is possible. This data is important to me and having essentially
> lost years worth with no chance of recovery is a real bummer.
>
> --
> 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/6be270a2-961f-4952-85b0-6074332671een%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/CAPq0zEDiu5ykPGVe7_6Kh2thW916%3Dt6MxaxeGkXYQcZg6G6JhQ%40mail.gmail.com.

Re: [weewx-user] Re: Weewx version 5 installation

2024-01-17 Thread Kruse Ludington

An issue that someone here can help with - upgrade problem that made me 
revert back - ? 

I have a custom version of weewx that I attempoted to upgrade from 4.10.2 
to 5.0.0.

I simply used
sudo apt update
sudo apt upgrade

then answered "no" to all the questions about keeping using the new 
configuration files.

It works perfectly except I have one problem. I need all logging to be in 
weewx.log (instead of syslog) and in a different directory instead of 
var/log. In previous updates I had searched my entire system for every 
instance of weewx.conf and updated all of them wherever they have var/log 
and var/log/syslog to the other directory and the name weewx.log. None of 
those changes to every weewx.conf file made any difference - and my config 
file still said 4.10.2 (why)?

Since I could not figure out how to keep my logging in the same weewx.log 
in a different directory that var/log, I just did a full restopre to my 
system so I now have the old systrem Working perfectly but not upgraded.

I want to get to 1.5 - but need the logging in weewx.log onlyand that file 
should be in a diffrerent directory - and to keep my same configuration but 
show and be actually 5.0.0 in stationregistry. How do I do that properly?

On Tuesday, January 16, 2024 at 9:49:59 AM UTC-5 Tom Keffer wrote:

> They look ok.
>
> I don't wish to sound cranky, but we put a lot of time into making the 
> install instructions bulletproof. Just follow the pip install instructions 
> . If you have a failure, 
> then come back and show us what happened.
>
> On Tue, Jan 16, 2024 at 5:44 AM Francesco Fasano  
> wrote:
>
>> Point 5 refers to running weewx as a daemon.
>> Apart from point 5, can you confirm that the points from number 1 to 
>> number 4 are fine?
>>
>> Il giorno martedì 16 gennaio 2024 alle 14:38:12 UTC+1 Tom Keffer ha 
>> scritto:
>>
>>> On Tue, Jan 16, 2024 at 5:19 AM Francesco Fasano  
>>> wrote:
>>>
 Thanks Tom,
 for the answer to tell the truth I'm carrying out tests on a virtual 
 machine with Raspberry operating system with virtual box it could probably 
 be as you say that there is some unusual hardware.
 I have a Raspberry Model 3 B+ and I performed my first installation 
 with setup.py. Over time I updated Python to 3.9 and always updated Weewx.
 the weewx installation in my case is located in /home
 so if I didn't misunderstand I should do the following steps
 1 - sudo apt update
 sudo apt install python3-pip -y
 sudo apt install python3-venv -y
 (do I have to do them from the home folder?)
>>>
>>>
>>> No, these are system installs, so they can be done anywhere.
>>>
>>> 2 - # Create the virtual environment
 python3 -m venv ~/weewx-venv
 # Activate the WeeWX virtual environment
 source ~/weewx-venv/bin/activate
 # Install WeeWX into the virtual environment
 python3 -m pip install weewx

 3 - weewxd --config=/home/weewx/weewx.conf

 4 - # systems with systemd
 # This will run weekx as you, not root. If you prefer to run as
 # the root user, modify the weewx.service file.
 sudo cp /home/weewx/util/systemd/weewx.service /etc/systemd/system
 sudo systemctl daemon-reload
 sudo systemctl enable weewx
 sudo systemctl start weewx

 5 - How do I start weewx version 5 when starting raspberry? with this? 
 sudo sh ~/weewx-data/scripts/setup-daemon.sh

>>>
>>> I'm not sure what instructions you are following there, but the service 
>>> file /etc/systemd/system/weewx.service will cause weewx to start when the 
>>> system starts.
>>>
>> -- 
>>
> 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/27cd8773-394f-4225-97c5-72146cc18d6bn%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/3013432f-6a0e-4a6a-88ff-5ea3e9e1d18dn%40googlegroups.com.

Re: [weewx-user] Re: Weewx version 5 installation

Under weewx-data/rsyslog there is a weewx.conf for rsyslog so just edit 
that as desired for where you want it to go before putting it into place 
and restarting rsyslog.

On Wednesday, January 17, 2024 at 6:39:45 PM UTC-8 Kruse Ludington wrote: 

Since I could not figure out how to keep my logging in the same weewx.log 
in a different directory that var/log, I just did a full restopre to my 
system so I now have the old systrem Working perfectly but not upgraded.

I want to get to 1.5 - but need the logging in weewx.log onlyand that file 
should be in a diffrerent directory - and to keep my same configuration but 
show and be actually 5.0.0 in stationregistry. How do I do that properly?

 

-- 
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/419f2615-40f4-4a06-b4c8-df1dcd3b3d17n%40googlegroups.com.

Re: [weewx-user] Database Error Message

2024-01-17 Thread sanphillipo

I changed it yesterday to 300 and it made no difference. Sent from my Verizon, 
Samsung Galaxy smartphone
 Original message From: Graham Eddy  Date: 
1/17/24  8:51 PM  (GMT-05:00) To: WeeWX User  
Subject: Re: [weewx-user] Database Error Message maybe a bit short?
⊣GE⊢

On 18 Jan 2024, at 11:55 am, Michael Sanphillipo  wrote: 
   archive_interval = 120



-- 
You received this message because you are subscribed to a topic in the Google 
Groups "weewx-user" group.
To unsubscribe from this topic, visit 
https://groups.google.com/d/topic/weewx-user/7tMPKNiRpZg/unsubscribe.
To unsubscribe from this group and all its topics, send an email to 
weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5DAE5F07-0D79-4BC7-A67D-09FA84035018%40geddy.au.

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/65a89190.050a0220.17f9d.c7b2%40mx.google.com.

Re: [weewx-user] Re: Weewx version 5 installation

oops - weewx-data/util/rsyslog of course there.

On Wednesday, January 17, 2024 at 6:47:43 PM UTC-8 vince wrote:

> Under weewx-data/rsyslog there is a weewx.conf for rsyslog so just edit 
> that as desired for where you want it to go before putting it into place 
> and restarting rsyslog.
>
> On Wednesday, January 17, 2024 at 6:39:45 PM UTC-8 Kruse Ludington wrote: 
>
> Since I could not figure out how to keep my logging in the same weewx.log 
> in a different directory that var/log, I just did a full restopre to my 
> system so I now have the old systrem Working perfectly but not upgraded.
>
> I want to get to 1.5 - but need the logging in weewx.log onlyand that file 
> should be in a diffrerent directory - and to keep my same configuration but 
> show and be actually 5.0.0 in stationregistry. How do I do that properly?
>
>  
>

-- 
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/e05bada7-983c-49d5-a971-2c65c8f76c81n%40googlegroups.com.

[weewx-user] ftpupload suddenly stopped working, but....

2024-01-17 Thread Steve2Q

Last evening, my system stopped uploading to Dreamhost.

I get the following message in syslog: " ftpupload: Unable to connect or 
log into server : timed out"

I have checked my config file and my credentials are correct, and using the 
identical credentials I can use my terminal program (Putty) to successfully 
log into Dreamhost. I also have SteelGauges installed, and that is running 
OK.

My ISP did "maintenance" last night, and my IP address has changed, so I 
checked with support on Dreamhost, and they said my new IP has NOT been 
blocked. What further information can I supply so someone can give me some 
guidance? I am running Weewx v 3.8.2

Thanks

-- 
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/ea1a9c8c-7520-47e5-8d0e-e4e395bde924n%40googlegroups.com.

[weewx-user] Re: Web page will not refresh after update to 5.0

Set debug=1   in /etc/weewx/weewx.conf

(2) reports, 21:30 and 22:00 EST

Attached are the requested outputs.

The database appears to have been updated in the same place:

/var/lib/weewx # ls  -l
total 22452
-rw-r--r-- 1 root root 22990848 Jan 17 22:00 weewx.sdb


On Wednesday, January 17, 2024 at 9:01:43 PM UTC-5 vince wrote:

> Jim please set debug=1 and restart weewx. For logs you might try to do 
> ‘sudo journalctl -u weewx -n 200’ so we see the last 200 lines and not a 
> truncated log,. We need to see your reports actually run and where they are 
> being written to. My wild guess is your v5 is writing to a different place 
> than your v4 does.
>
> On Wednesday, January 17, 2024 at 5:49:58 PM UTC-8 gjr80 wrote:
>
>> Unfortunately the log extracts you have provided lack detail and are 
>> truncated and consequently of not much help. Please try again noting the 
>> advice in the *How to get a good, useful log* section 
>> 
>>  
>> of the *Help! Posting to weewx user* wiki page 
>> . Make 
>> sure your log extract covers the full WeeWX startup and at least two 
>> archive intervals of activity. 
>>
>> Gary
>>
> On Thursday 18 January 2024 at 11:20:05 UTC+10 wil...@gmail.com wrote:
>>
>>> After an update of Weewx 4.10.2  to 5.0, the data on the web page 
>>>
>>> http:///weewx/index.html
>>>
>>> no longer refreshes.
>>>
>>> Summary data:
>>>
>>> uname -a
>>> Linux linux-3wjh 5.14.21-150500.55.39-default #1 SMP PREEMPT_DYNAMIC Tue 
>>> Dec 5 10:06:35 UTC 2023 (2e4092e) x86_64 x86_64 x86_64 GNU/Linux
>>>
>>> openSUSE Leap  15.5
>>>
>>> ~> weewxd --version
>>> 5.0.0
>>>
>>> ~> python3 --version
>>> Python 3.6.15
>>>
>>> systemctl status weewx
>>> ● weewx.service - WeeWX
>>>  Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; 
>>> vendor preset: disabled)
>>>  Active: active (running) since Wed 2024-01-17 19:21:18 EST; 16min 
>>> ago
>>>Docs: https://weewx.com/docs
>>>Main PID: 9772 (python3)
>>>   Tasks: 1 (limit: 4915)
>>>  CGroup: /system.slice/weewx.service
>>>  └─ 9772 python3 /usr/share/weewx/weewxd.py 
>>> /etc/weewx/weewx.conf
>>>
>>> Weewx shows to be running OK as seen in the attached logs file.
>>>
>>> If I roll back to 4.10.2, the web page refreshes as normal.
>>>
>>>
>>>

-- 
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/633d193b-0709-446e-af28-14ff3c5c5637n%40googlegroups.com.

~> weewxd --version
5.0.0

# WEEWX CONFIGURATION FILE
#
# Copyright (c) 2009-2020 Tom Keffer 
# See the file LICENSE.txt for your rights.

##

# This section is for general configuration information.

loop_on_init = True

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 1

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = True

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.10.2

##

NOTE:  interesting that this config file still shows version 4.10.2 



~> python3 --version
Python 3.6.15

# systemctl status weewx
● weewx.service - WeeWX
 Loaded: loaded (/usr/lib/systemd/system/weewx.service; enabled; vendor 
preset: disabled)
 Active: active (running) since Wed 2024-01-17 21:18:28 EST; 42min ago
   Docs: https://weewx.com/docs
   Main PID: 31248 (python3)
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/weewx.service
 └─ 31248 python3 /usr/share/weewx/weewxd.py /etc/weewx/weewx.conf

Jan 17 21:45:07 linux-3wjh weewxd[31248]: INFO weewx.restx: AWEKAS: Posting not 
enabled.
Jan 17 21:45:07 linux-3wjh weewxd[31248]: INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Jan 17 21:45:07 linux-3wjh weewxd[31248]: INFO __main__: Starting up weewx 
version 5.0.0
Jan 17 21:45:09 linux-3wjh weewxd[31248]: INFO weewx.engine: Clock error is 
1.62 seconds (positive is fast)
Jan 17 21:45:09 linux-3wjh weewxd[31248]: INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Jan 17 21:45:09 linux-3wjh weewxd[31248]: INFO weewx.manager: Starting backfill 
of daily summaries
Jan 17 21:45:09 linux-3wjh weewxd[31248]: INFO weewx.manager: Daily summaries 
up to date
Jan 17 21:45:11 linux-3wjh weewxd[31248]: INFO weewx.engine: Starting main 
packet loop.
Jan 17 22:

[weewx-user] Re: Web page will not refresh after update to 5.0