Re: [weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

2024-07-29 Thread Marty b
Thank you for all the responses.  I ended up doing another fresh install of 
the Raspberry Pi OS and WeeWx and everything worked like a charm on the 1st 
try - based on the feedback provided.  I do believe there was something 
wrong with my 1st fresh install of the RaspiOS that caused problems not 
being able to initially install the ' sortedcontainers' module.

Thank you again - the assistance was appreciated!

Marty

On Monday, July 29, 2024 at 9:50:04 AM UTC-7 bell...@gmail.com wrote:

>
> Oops, sudo apt install python3-paho-mqtt
> On Monday 29 July 2024 at 12:49:10 UTC-4 bell...@gmail.com wrote:
>
>> Depending on your preference, either of these should work for the paho 
>> mqtt client.
>> sudo apt install python-paho-mqtt
>> pip install paho-mqtt --break-system-packages
>> rich
>>
>> On Monday 29 July 2024 at 11:56:37 UTC-4 Marty b wrote:
>>
>>> Hello everyone,
>>>
>>> Thank you all for the replies!
>>>
>>> I tried installing the module using both methods (apt & pip).  Both gave 
>>> errors. I tried a bunch of other things and couldn't get it to work.  So, I 
>>> started working on some other things on the Pi and noticed that the 
>>> language was set for EN-GB-UTF8.  I change this to EN-US-UTF8 and tried 
>>> install the module again (via apt) and was successful.  This make 
>>> absolutely no sense, but that was the last thing that changed.  
>>>
>>> I did try activating the virtual environment and could not make it 
>>> work.  
>>>
>>> I am new to the virtual environment of python - and very willing to 
>>> learn/understand it.
>>>
>>> I will further try to figure it out since I want to use the mqtt plug-in 
>>> (https://github.com/weewx/weewx/wiki/mqtt) and it requires a package 
>>> that does not appear to be installable via apt (paho-mqtt).
>>>
>>>
>>>
>>> On Monday, July 29, 2024 at 8:04:23 AM UTC-7 John Kline wrote:
>>>
>>>> I looks like he is using an extension of mine (weewx-loopdata) that 
>>>> requires sorted containers since weewx-loopdata v3.0.  The README states 
>>>> that sortedcontainers must be installed and the weewx 5 install 
>>>> instructions, step 1, states:
>>>>
>>>>1. 
>>>>
>>>>
>>>>Activate the virtual environment (actual syntax varies by type of 
>>>>WeeWX install):/home/weewx/weewx-venv/bin/activate
>>>>
>>>>
>>>> I’m asssuming weewx 5.  If it is weewx 4, follow the WeeWX instructions 
>>>> for weewx 4 installs.
>>>>
>>>> On Jul 29, 2024, at 9:51 AM, bell...@gmail.com  
>>>> wrote:
>>>>
>>>> 
>>>>
>>>> This is ‘due’ to pep 668 and a ‘push’ for users to use virtual 
>>>> environments. It is warning the person installing the python module, 
>>>> sortedcontainers, that they  are installing into an ‘global’ 
>>>> (externally-managed-environment) location. There are a few ways to solve 
>>>> this.
>>>> Create a virtual environment, activate it, and install the module. 
>>>> Since WeeWX was a package install, this is not reasonable.
>>>> As the message states, override the warning using the 
>>>> ‘--break-system-packages’ option. It would look something like this, ‘pip3 
>>>> install sortedcontainers --break-system-packages’.
>>>> If it exists, install the OS package. It would be something like this, 
>>>> ‘sudo apt install python3-sortedcontainers’
>>>>
>>>> Additional information:
>>>> http://rptl.io/venv
>>>> https://peps.python.org/pep-0668/
>>>>
>>>> https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments
>>>>
>>>> rich
>>>> On Monday 29 July 2024 at 10:10:36 UTC-4 Tom Keffer wrote:
>>>>
>>>>> The user is doing a package install (the clue is paths such as 
>>>>> '/usr/share/weewx/...'
>>>>>
>>>>> My thinking is that you are using an extension that needs 
>>>>> 'sortedcontainers'.
>>>>>
>>>>> Please post your configuration file, /etc/weewx/weewx.conf. Make sure 
>>>>> you look it over and remove any passwords or other sensitive information 
>>>>> before posting. 
>>>>>
>>>>>
>>>>>
>>>>&g

Re: [weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

2024-07-29 Thread Marty b
Hello everyone,

Thank you all for the replies!

I tried installing the module using both methods (apt & pip).  Both gave 
errors. I tried a bunch of other things and couldn't get it to work.  So, I 
started working on some other things on the Pi and noticed that the 
language was set for EN-GB-UTF8.  I change this to EN-US-UTF8 and tried 
install the module again (via apt) and was successful.  This make 
absolutely no sense, but that was the last thing that changed.  

I did try activating the virtual environment and could not make it work.  

I am new to the virtual environment of python - and very willing to 
learn/understand it.

I will further try to figure it out since I want to use the mqtt plug-in 
(https://github.com/weewx/weewx/wiki/mqtt) and it requires a package that 
does not appear to be installable via apt (paho-mqtt).



On Monday, July 29, 2024 at 8:04:23 AM UTC-7 John Kline wrote:

> I looks like he is using an extension of mine (weewx-loopdata) that 
> requires sorted containers since weewx-loopdata v3.0.  The README states 
> that sortedcontainers must be installed and the weewx 5 install 
> instructions, step 1, states:
>
>1. 
>
>
>Activate the virtual environment (actual syntax varies by type of 
>WeeWX install):/home/weewx/weewx-venv/bin/activate
>
>
> I’m asssuming weewx 5.  If it is weewx 4, follow the WeeWX instructions 
> for weewx 4 installs.
>
> On Jul 29, 2024, at 9:51 AM, bell...@gmail.com  wrote:
>
> 
>
> This is ‘due’ to pep 668 and a ‘push’ for users to use virtual 
> environments. It is warning the person installing the python module, 
> sortedcontainers, that they  are installing into an ‘global’ 
> (externally-managed-environment) location. There are a few ways to solve 
> this.
> Create a virtual environment, activate it, and install the module. Since 
> WeeWX was a package install, this is not reasonable.
> As the message states, override the warning using the 
> ‘--break-system-packages’ option. It would look something like this, ‘pip3 
> install sortedcontainers --break-system-packages’.
> If it exists, install the OS package. It would be something like this, 
> ‘sudo apt install python3-sortedcontainers’
>
> Additional information:
> http://rptl.io/venv
> https://peps.python.org/pep-0668/
>
> https://packaging.python.org/en/latest/specifications/externally-managed-environments/#externally-managed-environments
>
> rich
> On Monday 29 July 2024 at 10:10:36 UTC-4 Tom Keffer wrote:
>
>> The user is doing a package install (the clue is paths such as 
>> '/usr/share/weewx/...'
>>
>> My thinking is that you are using an extension that needs 
>> 'sortedcontainers'.
>>
>> Please post your configuration file, /etc/weewx/weewx.conf. Make sure you 
>> look it over and remove any passwords or other sensitive information before 
>> posting. 
>>
>>
>>
>> On Sun, Jul 28, 2024 at 11:41 PM Marty b  wrote:
>>
>>> Should point out that I did try installing the missing module, but got 
>>> the following error:
>>>
>>>  $ pip3 install sortedcontainers
>>> error: externally-managed-environment
>>>
>>> × This environment is externally managed
>>> ╰─> To install Python packages system-wide, try apt install
>>> python3-xyz, where xyz is the package you are trying to
>>> install.
>>>
>>> If you wish to install a non-Debian-packaged Python package,
>>> create a virtual environment using python3 -m venv path/to/venv.
>>> Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
>>> sure you have python3-full installed.
>>>
>>> For more information visit http://rptl.io/venv
>>>
>>> note: If you believe this is a mistake, please contact your Python 
>>> installation or OS distribution provider. You can override this, at the 
>>> risk of breaking your Python installation or OS, by passing 
>>> --break-system-packages.
>>>
>>> On Sunday, July 28, 2024 at 11:14:11 PM UTC-7 Marty b wrote:
>>>
>>>> Hello,
>>>>
>>>> Just built a new SD card with Raspbian bookworm 64 bit and WeeWx.  When 
>>>> starting weewx I get an error "No module named 'sortedcontainers'.  Please 
>>>> let me know how to resolve this.
>>>>
>>>> Thanks!
>>>>
>>>> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: StdConvert 
>>>> target unit is 0x1
>>>> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.wxservices: 
>>>> StdWXCalculate will use da

[weewx-user] Re: New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

2024-07-28 Thread Marty b
Should point out that I did try installing the missing module, but got the 
following error:

 $ pip3 install sortedcontainers
error: externally-managed-environment

× This environment is externally managed
╰─> To install Python packages system-wide, try apt install
python3-xyz, where xyz is the package you are trying to
install.

If you wish to install a non-Debian-packaged Python package,
create a virtual environment using python3 -m venv path/to/venv.
Then use path/to/venv/bin/python and path/to/venv/bin/pip. Make
sure you have python3-full installed.

For more information visit http://rptl.io/venv

note: If you believe this is a mistake, please contact your Python 
installation or OS distribution provider. You can override this, at the 
risk of breaking your Python installation or OS, by passing 
--break-system-packages.

On Sunday, July 28, 2024 at 11:14:11 PM UTC-7 Marty b wrote:

> Hello,
>
> Just built a new SD card with Raspbian bookworm 64 bit and WeeWx.  When 
> starting weewx I get an error "No module named 'sortedcontainers'.  Please 
> let me know how to resolve this.
>
> Thanks!
>
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: StdConvert 
> target unit is 0x1
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Archive will 
> use data binding wx_binding
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Using archive 
> interval of 300 seconds (specified by hardware)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: StationRegistry: 
> Registration not requested.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: Wunderground: 
> Posting not enabled.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: PWSweather: 
> Posting not enabled.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: CWOP: Posting 
> not enabled.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: WOW: Posting not 
> enabled.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: 'pyephem' 
> detected, extended almanac data is available
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: Caught 
> unrecoverable exception:
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:   No 
> module named 'sortedcontainers'
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  Traceback (most recent call last):
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewxd.py", line 121, in main
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  engine = weewx.engine.StdEngine(config_dict)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
> ^^^
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 89, in __init__
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  self.loadServices(config_dict)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "/usr/share/weewx/weewx/engine.py", line 157, in loadServices
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  obj = weeutil.weeutil.get_object(svc)(self, config_dict)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  ^^^
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "/usr/share/weewx/weeutil/weeutil.py", line 1404, in get_object
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  module = importlib.import_module(module_name)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
> 
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "/usr/lib/python3.11/importlib/__init__.py", line 126, in 
> import_module
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
>  return _bootstrap._gcd_import(name[level:], package, level)
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>   
> Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:    
>  File "", line 1206, in _gcd_import
> Jul 28 23:12:1

[weewx-user] New Install of WeeWx on Raspbian Bookworm - No module named 'sortedcontainers'

2024-07-28 Thread Marty b
Hello,

Just built a new SD card with Raspbian bookworm 64 bit and WeeWx.  When 
starting weewx I get an error "No module named 'sortedcontainers'.  Please 
let me know how to resolve this.

Thanks!

Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: StdConvert 
target unit is 0x1
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Archive will use 
data binding wx_binding
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: Using archive 
interval of 300 seconds (specified by hardware)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: StationRegistry: 
Registration not requested.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: Wunderground: 
Posting not enabled.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: PWSweather: 
Posting not enabled.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: CWOP: Posting not 
enabled.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: WOW: Posting not 
enabled.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.restx: AWEKAS: Posting 
not enabled.
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: Caught 
unrecoverable exception:
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:   No 
module named 'sortedcontainers'
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 Traceback (most recent call last):
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/usr/share/weewx/weewxd.py", line 121, in main
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 engine = weewx.engine.StdEngine(config_dict)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
  ^^^
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 89, in __init__
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 self.loadServices(config_dict)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/usr/share/weewx/weewx/engine.py", line 157, in loadServices
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 obj = weeutil.weeutil.get_object(svc)(self, config_dict)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
   ^^^
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/usr/share/weewx/weeutil/weeutil.py", line 1404, in get_object
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 module = importlib.import_module(module_name)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
  
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  
 return _bootstrap._gcd_import(name[level:], package, level)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__:  

Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 1206, in _gcd_import
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 1178, in _find_and_load
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 1149, in _find_and_load_unlocked
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 690, in _load_unlocked
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: Traceback (most recent call last):
Jul 28 23:12:10 WeeWx2024 weewxd[2632]:   File 
"/usr/share/weewx/weewxd.py", line 226, in 
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 940, in exec_module
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: main()
Jul 28 23:12:10 WeeWx2024 weewxd[2632]:   File 
"/usr/share/weewx/weewxd.py", line 121, in main
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"", line 241, in _call_with_frames_removed
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: engine = 
weewx.engine.StdEngine(config_dict)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: 
 ^^^
Jul 28 23:12:10 WeeWx2024 weewxd[2632]:   File 
"/usr/share/weewx/weewx/engine.py", line 89, in __init__
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: CRITICAL __main__: File 
"/etc/weewx/bin/user/loopdata.py", line 30, in 
Jul 28 23:12:10 WeeWx2024 weewxd[2632]: self.loadServices(config_dict)
Jul 28 23:12:10 WeeWx2024 weewxd[2632]:   File

[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.


[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] Error generating loop-data.txt with 4.6.2

2022-02-21 Thread Marty b
Thank you.  Problem resolved. :-)

On Monday, February 21, 2022 at 9:41:12 PM UTC-8 jo...@johnkline.com wrote:

> Yes, you must be running WeeWX 4.6.x.  Install the latest release of 
> loopdata (which is version 2.10).
>
> On Feb 21, 2022, at 6:49 PM, Marty b  wrote:
>
> 
>
> Hello everyone,
>
> My loop-data generation recently stopped working.  Here is a section from 
> my syslog that shows the error:
>
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
> '/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version 
> is 2.7.2.
> Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
> target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
> option "minute_label"  in interpolation.
> Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx 
> version 4.6.2
> F
>
> Any suggestion on resolving this?
>
> Thanks,
> Marty
>
> -- 
> 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/8228f6ce-270e-400f-a559-5320a59f13c4n%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/8228f6ce-270e-400f-a559-5320a59f13c4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5be67d02-026b-4539-b11a-b28e736526f5n%40googlegroups.com.


[weewx-user] Error generating loop-data.txt with 4.6.2

2022-02-21 Thread Marty b
Hello everyone,

My loop-data generation recently stopped working.  Here is a section from 
my syslog that shows the error:

Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.rtgd: 
'/dev/shm/weewx/gauge-data.txt' wil be generated. min_interval is None
Feb 21 00:35:14 WeeWx2021 weewx[560] INFO user.loopdata: Service version is 
2.7.2.
Feb 21 00:35:14 WeeWx2021 weewx[560] ERROR user.loopdata: Could not find 
target_report: LoopDataReport.  LoopData is exiting. Exception: missing 
option "minute_label"  in interpolation.
Feb 21 00:35:14 WeeWx2021 weewx[560] INFO __main__: Starting up weewx 
version 4.6.2
F

Any suggestion on resolving this?

Thanks,
Marty

-- 
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/8228f6ce-270e-400f-a559-5320a59f13c4n%40googlegroups.com.


Re: [weewx-user] Re: gjr80/weewx-steelseries update interval

2021-09-12 Thread Marty b
Thank you for the responses John and Gary.  I have them both running and 
they seem to be working fine together.

Gary - Thank you again for the assistance getting your extension 
operational!

Marty

On Thursday, September 9, 2021 at 6:21:49 PM UTC-7 jo...@johnkline.com 
wrote:

> Yeah, the two won’t interfere with each other.  I ran both plugins 
> together for a long time.
>
> On Sep 9, 2021, at 5:58 PM, gjr80  wrote:
>
> 
>
> > Is it safe to also install the chaunceygardiner/weewx-loopdata along 
> side your loopdata extension?
>
> I know nothing of what weewx-loopdata does but I can't see why not. Best 
> way to find out is try it and see and monitor your log and the various 
> outputs that WeeWX generates.
>
> Gary
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to weewx-user+...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/f051dd10-cc4d-424a-b124-b2b7b6bb89ccn%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/fddf14bd-4943-4bd9-b053-ecfafb24eef5n%40googlegroups.com.


[weewx-user] Re: gjr80/weewx-steelseries update interval

2021-09-08 Thread Marty b
That worked!  Thank you very much.

Is it safe to also install the chaunceygardiner/weewx-loopdata along side 
your loopdata extension?

Thank you again!
Marty

On Wednesday, September 8, 2021 at 4:30:37 AM UTC-7 gjr80 wrote:

> Thanks. It seems v0.5.0 was a bit of a buggers muddle; I should not have 
> released v0.5.0 and when I did I released some early alpha code that has a 
> bug. Rather then work through another release just now can I get you to 
> replace your existing rtgd.py with the attached, to do this:
>
> 1. delete your existing /usr/share/weewx/user/rtgd.py
> 2. download that attached rtgd.py and save it as 
> /usr/share/weewx/user/rtgd.py
> 3. restart WeeWX
> 4. monitor your log for errors and check that gauge-data.txt is generated 
> and saved where it should be
>
> If you do encounter any errors could you post a log extract showing WeeWX 
> startup through until the error occurs, just as you did here.
>
> There is one shortcoming in this version; I suspect the Beaufort value 
> (field Tbeaufort in gauge-data.txt) will be zero irrespective of wind 
> speed. This shouldn't matter too much just now as as far as I know the 
> SteelSeries Gauges only uses the Tbeaufort field to display on the 
> mouseover panel for the wind speed gauge. I need to work on fixing that, 
> will post here when it is fixed.
>
> Gary
> On Wednesday, 8 September 2021 at 13:56:58 UTC+10 Marty b wrote:
>
>> Here are the logs in a text file - in case that helps.  I do not see the 
>> file real time data file generated...
>>
>>
>>
>> On Tuesday, September 7, 2021 at 8:30:20 PM UTC-7 Marty b wrote:
>>
>>> I was getting an error after installing the gjr80 
>>> <https://github.com/gjr80> / * weewx-realtime_gauge-data 
>>> <https://github.com/gjr80/weewx-realtime_gauge-data> * extension so I 
>>> reinstalled everything from scratch.  After reinstalling from scratch (OS, 
>>> Apache, Weewx, RealtimeGauge-Data extension) I get the same error:
>>>
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO weewx.engine: Starting main 
>>> packet loop.
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
>>> Traceback (most recent call last):
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 1815, in process_packet
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  data = self.calculate(cached_packet)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 2187, in calculate
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  data[field] = self.get_field_value(field, packet)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 1944, in get_field_value
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  _raw_vt = as_value_tuple(packet, source)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/weewx/units.py", line 1740, in as_value_tuple
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  val = record_dict[obs_type]
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
>>> KeyError: 'beaufort'
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
>>> Traceback (most recent call last):
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 1815, in process_packet
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  data = self.calculate(cached_packet)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 2187, in calculate
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  data[field] = self.get_field_value(field, packet)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/usr/share/weewx/user/rtgd.py", line 1944, in get_field_value
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread: 
>>>  _raw_vt = as_value_tuple(packet, source)
>>> Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
>>> File "/us

[weewx-user] Re: gjr80/weewx-steelseries update interval

2021-09-07 Thread Marty b
I was getting an error after installing the gjr80 <https://github.com/gjr80> 
/ * weewx-realtime_gauge-data 
<https://github.com/gjr80/weewx-realtime_gauge-data> * extension so I 
reinstalled everything from scratch.  After reinstalling from scratch (OS, 
Apache, Weewx, RealtimeGauge-Data extension) I get the same error:

Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO weewx.engine: Starting main 
packet loop.
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
Traceback (most recent call last):
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 1815, in process_packet
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
data = self.calculate(cached_packet)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 2187, in calculate
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
data[field] = self.get_field_value(field, packet)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 1944, in get_field_value
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
_raw_vt = as_value_tuple(packet, source)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/weewx/units.py", line 1740, in as_value_tuple
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
val = record_dict[obs_type]
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
KeyError: 'beaufort'
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
Traceback (most recent call last):
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 1815, in process_packet
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
data = self.calculate(cached_packet)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 2187, in calculate
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
data[field] = self.get_field_value(field, packet)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/user/rtgd.py", line 1944, in get_field_value
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
_raw_vt = as_value_tuple(packet, source)
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:    
File "/usr/share/weewx/weewx/units.py", line 1740, in as_value_tuple
Sep  7 20:23:33 WeeWx2021 weewx[3153] INFO user.rtgd: rtgdthread:  
val = record_dict[obs_type]

What am I doing wrong?

Thank you,
Marty

  

On Tuesday, September 7, 2021 at 7:28:05 AM UTC-7 Marty b wrote:

> Thank you.  I will give it a try today...
>
> On Tuesday, September 7, 2021 at 5:49:19 AM UTC-7 gjr80 wrote:
>
>> There are a couple of ways you can disable generation of gauge-data.txt 
>> by the SteelSeries skin, but the simplest is to edit the SteelSeries skin 
>> skin config file (/etc/weewx/skins/ss/skin.conf) and comment out the 
>> highlighted lines under [CheetahGenerator]:
>>
>> [CheetahGenerator]
>> encoding = html_entities
>> [[ToDate]]
>> [[[index]]]
>> template = index.html.tmpl
>> #[[[data]]]
>> #template = gauge-data.txt.tmpl
>>
>> Save the file (no need to restart WeeWX) and the SteelSeries skin will no 
>> longer generate gauge-data.txt. The only downside of this approach is if 
>> you ever re-install or update the SteelSeries skin you will need to revisit 
>> the skin config file and disable the gauge-data.txt generation.
>>
>> Gary
>> On Tuesday, 7 September 2021 at 12:16:41 UTC+10 Marty b wrote:
>>
>>> Thank you.  I will make sure I have the realtime gauge-data extension 
>>> installed and enabled.
>>>
>>> How do I disable the generation of the gauge-data.txt by the SteelSeries 
>>> skin?
>>>
>>> Marty
>>>
>>> On Monday, September 6, 2021 at 6:56:03 PM UTC-7 gjr80 wrote:
>>>
>>>> Thanks. The logs indicate that you have the SteelSeries skin 
>>>> <https://github.com/weewx/weewx/wiki/steelseries> installed and the 
>>>> Realtime 
>>>> gauge-data extension 
>>>> <https://github.com/gjr80/weewx-realtime_gauge-data>, if installed, is 
>>>> not enabled. The SteelSeries skin generates gauge-data.txt during the 
>>>> report cycle at the end of every archive period, in your case every five 
>>>> 

[weewx-user] Re: gjr80/weewx-steelseries update interval

2021-09-07 Thread Marty b
Thank you.  I will give it a try today...

On Tuesday, September 7, 2021 at 5:49:19 AM UTC-7 gjr80 wrote:

> There are a couple of ways you can disable generation of gauge-data.txt 
> by the SteelSeries skin, but the simplest is to edit the SteelSeries skin 
> skin config file (/etc/weewx/skins/ss/skin.conf) and comment out the 
> highlighted lines under [CheetahGenerator]:
>
> [CheetahGenerator]
> encoding = html_entities
> [[ToDate]]
> [[[index]]]
> template = index.html.tmpl
> #[[[data]]]
> #template = gauge-data.txt.tmpl
>
> Save the file (no need to restart WeeWX) and the SteelSeries skin will no 
> longer generate gauge-data.txt. The only downside of this approach is if 
> you ever re-install or update the SteelSeries skin you will need to revisit 
> the skin config file and disable the gauge-data.txt generation.
>
> Gary
> On Tuesday, 7 September 2021 at 12:16:41 UTC+10 Marty b wrote:
>
>> Thank you.  I will make sure I have the realtime gauge-data extension 
>> installed and enabled.
>>
>> How do I disable the generation of the gauge-data.txt by the SteelSeries 
>> skin?
>>
>> Marty
>>
>> On Monday, September 6, 2021 at 6:56:03 PM UTC-7 gjr80 wrote:
>>
>>> Thanks. The logs indicate that you have the SteelSeries skin 
>>> <https://github.com/weewx/weewx/wiki/steelseries> installed and the 
>>> Realtime 
>>> gauge-data extension 
>>> <https://github.com/gjr80/weewx-realtime_gauge-data>, if installed, is 
>>> not enabled. The SteelSeries skin generates gauge-data.txt during the 
>>> report cycle at the end of every archive period, in your case every five 
>>> minutes. The wiki you are referring to is for the Realtime gauge-data 
>>> extension which can generate gauge-data.txt on receipt of each loop packet, 
>>> in your case every 2.5 odd seconds. The setting for the Realtime gauge-data 
>>> extension have no effect on the SteelSeries skin.
>>>
>>> If you want gauge-data.txt to be generated on every loop packet then you 
>>> need to install (or enable if already installed) the Realtime gauge-data 
>>> extension. Note you will then. need to disable generation of gauge-data.txt 
>>> by the SteelSeries skin or you will have the skin and the extension both 
>>> generating gauge-data.txt. This would be bad.
>>>
>>> Gary
>>>
>>> On Tuesday, 7 September 2021 at 10:40:54 UTC+10 Marty b wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for the response.  The logs are attached
>>>>
>>>> Marty
>>>>
>>>> On Monday, September 6, 2021 at 4:22:58 PM UTC-7 gjr80 wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> There are two means of having WeeWX generate gauge-data.txt; one is 
>>>>> via the SteelSeries skin and the other is via the real-time gauge data 
>>>>> extension. The former generates gauge-data.txt no quicker than every 
>>>>> archive interval the latter up to every ‘loop interval’. It sounds like 
>>>>> you 
>>>>> may be using the former. It would help to know what you have installed 
>>>>> and 
>>>>> enabled. Could you please set debug = 1 in weewx.conf and then restart 
>>>>> WeeWX. Let WeeWX run for at least  two archive intervals and then post 
>>>>> the 
>>>>> log showing the full WeeWX startup through until the two archive 
>>>>> intervals 
>>>>> have passed.nThat will tell us exactly what your install is doing.
>>>>>
>>>>> Gary
>>>>> On Tuesday, 7 September 2021 at 08:03:42 UTC+10 Marty b wrote:
>>>>>
>>>>>> Hello everyone,
>>>>>>
>>>>>> I am trying to figure out how to get gauge-data.txt to update each 
>>>>>> time a loop packet is received.  Currently it only updates at the same 
>>>>>> interval as the rest of the weewx files (~every 10 minutes).  I looked 
>>>>>> at 
>>>>>> the wiki page for extension, but the section for ' Changing how 
>>>>>> often *gauge-data.txt* is generated' says ' To be written.'
>>>>>>
>>>>>> Any help would be appreciated.
>>>>>>
>>>>>> 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/0a7658c0-9ef5-475d-bad0-6b29b6406c09n%40googlegroups.com.


[weewx-user] Re: gjr80/weewx-steelseries update interval

2021-09-06 Thread Marty b
Thank you.  I will make sure I have the realtime gauge-data extension 
installed and enabled.

How do I disable the generation of the gauge-data.txt by the SteelSeries 
skin?

Marty

On Monday, September 6, 2021 at 6:56:03 PM UTC-7 gjr80 wrote:

> Thanks. The logs indicate that you have the SteelSeries skin 
> <https://github.com/weewx/weewx/wiki/steelseries> installed and the Realtime 
> gauge-data extension <https://github.com/gjr80/weewx-realtime_gauge-data>, 
> if installed, is not enabled. The SteelSeries skin generates gauge-data.txt 
> during the report cycle at the end of every archive period, in your case 
> every five minutes. The wiki you are referring to is for the Realtime 
> gauge-data extension which can generate gauge-data.txt on receipt of each 
> loop packet, in your case every 2.5 odd seconds. The setting for the 
> Realtime gauge-data extension have no effect on the SteelSeries skin.
>
> If you want gauge-data.txt to be generated on every loop packet then you 
> need to install (or enable if already installed) the Realtime gauge-data 
> extension. Note you will then. need to disable generation of gauge-data.txt 
> by the SteelSeries skin or you will have the skin and the extension both 
> generating gauge-data.txt. This would be bad.
>
> Gary
>
> On Tuesday, 7 September 2021 at 10:40:54 UTC+10 Marty b wrote:
>
>> Hi,
>>
>> Thanks for the response.  The logs are attached
>>
>> Marty
>>
>> On Monday, September 6, 2021 at 4:22:58 PM UTC-7 gjr80 wrote:
>>
>>> Hi,
>>>
>>> There are two means of having WeeWX generate gauge-data.txt; one is via 
>>> the SteelSeries skin and the other is via the real-time gauge data 
>>> extension. The former generates gauge-data.txt no quicker than every 
>>> archive interval the latter up to every ‘loop interval’. It sounds like you 
>>> may be using the former. It would help to know what you have installed and 
>>> enabled. Could you please set debug = 1 in weewx.conf and then restart 
>>> WeeWX. Let WeeWX run for at least  two archive intervals and then post the 
>>> log showing the full WeeWX startup through until the two archive intervals 
>>> have passed.nThat will tell us exactly what your install is doing.
>>>
>>> Gary
>>> On Tuesday, 7 September 2021 at 08:03:42 UTC+10 Marty b wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I am trying to figure out how to get gauge-data.txt to update each time 
>>>> a loop packet is received.  Currently it only updates at the same interval 
>>>> as the rest of the weewx files (~every 10 minutes).  I looked at the wiki 
>>>> page for extension, but the section for ' Changing how often 
>>>> *gauge-data.txt* is generated' says ' To be written.'
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> 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/e8da8f9f-a2a7-4d23-85a4-a0dce06c9a94n%40googlegroups.com.


[weewx-user] gjr80/weewx-steelseries update interval

2021-09-06 Thread Marty b
Hello everyone,

I am trying to figure out how to get gauge-data.txt to update each time a 
loop packet is received.  Currently it only updates at the same interval as 
the rest of the weewx files (~every 10 minutes).  I looked at the wiki page 
for extension, but the section for ' Changing how often *gauge-data.txt* is 
generated' says ' To be written.'

Any help would be appreciated.

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/556307ac-a341-4f7f-868d-32b71a3e8ee2n%40googlegroups.com.


Re: [weewx-user] Re: recommend IP cameras that are easy to grab a single frame from?

2021-08-10 Thread Marty b
I use the Ubiquiti Cameras which are PoE and they work quite well. 
(Snapshot example URL: http://192.168.1.95/snap.jpeg)

I have a process on a Raspberry Pi that will grab an image every minute and 
saves it to /dev/shm (the ram disk - which saves wear and tear on the SD 
card).  The image can be viewed via a php webpage grabbing the image from 
/dev/shm.  See code below for example:




Hope this helps.

On Monday, August 9, 2021 at 2:29:28 PM UTC-7 dvdhns wrote:

> One thing to keep in mind is the microSD cards will start to fail after so 
> many write operations. I had one fail after about six months, after saving 
> an image to it once every minute.
>
> I'm currently a cheap IP camera that seems to loose it's network 
> connection whenever weather gets hot. Looking for a better POE IP cam. 
>
> On Sunday, August 8, 2021 at 5:08:41 PM UTC-6 Eric K wrote:
>
>> I have been working with the ESP32-CAM wifi camera today.
>>
>> In weewx, I'm using the Belchertown webpage skin.
>> In its stock setup, you get a weather RADAR image from Windy.com, that 
>> updates every 5 minutes.  
>> This afternoon, I replaced the Windy.com RADAR plot with the webcam 
>> image. 
>> I don't really want to trade the RADAR for the webcam, but I'm not sure 
>> of a slick way to have both, yet.
>>
>> It takes about 10 seconds to transfer an image frame from the ESP32-CAM 
>> to the Raspberry Pi.
>> To remove this delay from the webpage, I wrote a simple executable bash 
>> script to grab the webcam image and store it on the Raspberry Pi micro-SD 
>> card.
>> Then, I have the weewx webpage fetch the webcam.jpg file from the "hard 
>> drive" so it loads instantly.
>>
>> fetch script:
>> #!/bin/bash
>> wget http://192.168.8.122/snapshot.jpg -O 
>> /home/weewx/public_html/images/webcam.jpg
>>
>> Then I have the Belchertown skin put the webcam.jpg file into the page,
>>
>> from the Belchertown index.html.tmpl file:
>> 
>> 
>> > height="480">
>> 
>> 
>> 
>>
>> I'd like to polish this a bit, but it is working.
>>
>>
>>
>> On Sat, Aug 7, 2021 at 5:32 PM p q  wrote:
>>
>>> Please continue to post your results. Particularly which hardware you 
>>> choose. I'm interested in doing the same with my own skin.
>>>
>>> As a side note, I'm playing around with Grafana to see what 
>>> advantages it has compared to the standard graphs. It was easy to install 
>>> on my raspberry pi and fairly easy to hook up to the SQLite DB.
>>>
>>> On Sat, Aug 7, 2021 at 3:24 PM Eric K  wrote:
>>>
 I also want to check out your perl scripts, @mwall!

 On Saturday, August 7, 2021 at 5:18:33 PM UTC-5 Eric K wrote:

> Thanks for all the responses.
>
> Shortly after posting this I got a couple of the ESP32-CAM modules and 
> loaded Tasmota firmware into them.
> see:  https://cgomesu.com/blog/Esp32cam-tasmota-webcam-server/
> You have to use the specific Tasmota32 webcam firmware:   
> tasmota32-webcam.bin 
> 
> The maximum resolution of these is only 1600x1200.  
> The upside is that you can easily grab a single frame using a simple 
> URL command:  http://192.168.8.122/snapshot.jpg
> The only downsides I see:  with the plastic lens and jpeg compression, 
> the images are not great for fine detail.
>
> Given the low cost, small size, MIPI camera interface, and wifi 
> capability of the RPi Zero W board, I reconsidered an RPi camera.
> I'm currently assembling a RPi Zero camera with a 5mp camera module.
> I am getting single images out of it with the raspistill application:
> raspistill -v -o /home/pi/Pictures/pi-cam-test.jpg
>
> I'd like to grab an image every 5-10 minutes and have the current 
> image show up in the Belchertown weewx page.
> I'd also like to create a daily time lapse movie like others have done.
> I recall seeing some webcam script examples in this weewx-user group 
> to do these 2 things.  
> I need to search for them again.
>
>

-- 
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/0de47090-0674-43f8-869e-41424c624d04n%40googlegroups.com.