Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

[Remy Lavabre]

Yes thank you it works Vince!
I've been racking my brains over these Apache directories for a while and I 
admit I haven't thought about reversing my symbolic links, idiot that I 
am...! :-(

Perhaps an even simpler solution would have been to put the version 4 path 
back in weewx.conf...?

However, I would have liked to understand why I was unable to reach my 
~/weewx-venv/public_html directory with my initial symbolic links... The 
rights seemed to have been assigned correctly to the directories.

But in any case it works with your method! So I'm keeping it :-)))
Thank you Vince and have a good weekend

Le vendredi 26 avril 2024 à 18:44:29 UTC+2, vince a écrit :

> I do it in the opposite direction.   The /var/www/html/weewx path is a 
> directory.  The /home//weewx-data/public_html path is a symlink 'to' 
> the webserver directory.
>
> For a pip installation:
> sudo mkdir /var/www/html/weewx
> sudo chown ${WEEWXUSER}:${WEEWXUSER} /var/www/html/weewx
> ln -s /var/www/html/weewx /home/${WEEWXUSER}/weewx-data/public_html
>
>
> On Friday, April 26, 2024 at 7:53:03 AM UTC-7 Remy Lavabre wrote:
>
>> 1/ if I try xxx.xxx.xxx.xxx/index.html -> Work fine, I've got the Apache2 
>> Debian Default Page (which is in /var/www/html/index.html).
>> 2/ if i try xxx.xxx.xxx.xxx/weewx/index.html -> Forbidden - You don't 
>> have permission to access this resource. (with my symbolic link)
>>
>> I've tried :
>> A/ sudo chown www-data ~/weewx-data/public_html -Rf
>> B/ sudo chmod 775 -R ~/weewx-data/public_html
>> --> Same thing
>>
>> C/ sudo nano /etc/apache2/sites-available/000-default.conf and change 
>> "DocumentRoot /var/www/html" to "DocumentRoot ~/weewx-data/public_html"
>>  xxx.xxx.xxx.xxx/index.html *and* xxx.xxx.xxx.xxx/weewx/index.html does 
>> not work...
>>
>> Any idear ??
>> Le vendredi 26 avril 2024 à 15:46:48 UTC+2, p q a écrit :
>>
>>> Looks like a rights issue with Apache. Find the apache.conf file and you 
>>> probably need to enable access to the right directories.
>>>
>>> On Fri, Apr 26, 2024 at 6:26 AM Remy Lavabre  
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> Good morning,
>>>> I didn't find the answer to my problem in the various discussions on 
>>>> the WeeWX forum...
>>>>
>>>> I installed Weewx 5 in a virtual environment.
>>>> So I have my weewx-data and weewx-venv directories in /home/---/
>>>>
>>>> weewxd seems to "finally" work normally with the 
>>>> ~/weewx-data/public_html directory refreshing.
>>>>
>>>> On version 4, the weewx public_html directory was /var/www/html/weewx 
>>>> ROOT:ROOT and did not pose a problem with the Apache 2 server.
>>>> Since the location of the web server changed in version 5, I put a 
>>>> symbolic link "weewx" in /var/www/html/ pointing to 
>>>> ~/weewx-data/public_html/weewx [sudo ln -s/ ~/ weewx-data/public_htmlweewx 
>>>> /var/www/html/weewx].
>>>>
>>>> The rights of var/www/html remained ROOT:ROOT while the rights of 
>>>> ~/weewx-data/public_html/weewx are those of the creator.
>>>>
>>>> Filezilla navigation works correctly. Clicking on the symbolic link 
>>>> takes you to the new WeeWX 5 public_html directory.
>>>>
>>>> However, when trying to connect through a web browser (
>>>> http://xxx.xxx.xxx.xxx/weewx/index.html), I get the response:
>>>> :
>>>>
>>>>
>>>>
>>>>
>>>> *ForbiddenYou don't have permission to access this 
>>>> resource.Apache/2.4.59 (Debian) Server at xxx.xxx.xxx.xxx Port 80*
>>>>
>>>> I think it must just be a rights issue...?
>>>>
>>>> *What is the recommended solution in Weewx 5 with Apache 2 to redirect 
>>>> Apache from /var/www/html to ~/weewx-data/public_html?*
>>>>
>>>> Thanks a lot for the help! ;-)
>>>>
>>>> -- 
>>>> 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/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>>
>>>
>>> -- 
>>> Peter Quinn
>>> (415)794-2264 <(415)%20794-2264>
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/899b6408-bb57-4117-b8f2-d63703dd4aban%40googlegroups.com.

Re: [weewx-user] Problem for public_html access with Weewx 5 and apache 2

[Remy Lavabre]

1/ if I try xxx.xxx.xxx.xxx/index.html -> Work fine, I've got the Apache2 
Debian Default Page (which is in /var/www/html/index.html).
2/ if i try xxx.xxx.xxx.xxx/weewx/index.html -> Forbidden - You don't have 
permission to access this resource. (with my symbolic link)

I've tried :
A/ sudo chown www-data ~/weewx-data/public_html -Rf
B/ sudo chmod 775 -R ~/weewx-data/public_html
--> Same thing

C/ sudo nano /etc/apache2/sites-available/000-default.conf and change 
"DocumentRoot /var/www/html" to "DocumentRoot ~/weewx-data/public_html"
 xxx.xxx.xxx.xxx/index.html *and* xxx.xxx.xxx.xxx/weewx/index.html does not 
work...

Any idear ??
Le vendredi 26 avril 2024 à 15:46:48 UTC+2, p q a écrit :

> Looks like a rights issue with Apache. Find the apache.conf file and you 
> probably need to enable access to the right directories.
>
> On Fri, Apr 26, 2024 at 6:26 AM Remy Lavabre  wrote:
>
>> Hello,
>>
>> Good morning,
>> I didn't find the answer to my problem in the various discussions on the 
>> WeeWX forum...
>>
>> I installed Weewx 5 in a virtual environment.
>> So I have my weewx-data and weewx-venv directories in /home/---/
>>
>> weewxd seems to "finally" work normally with the ~/weewx-data/public_html 
>> directory refreshing.
>>
>> On version 4, the weewx public_html directory was /var/www/html/weewx 
>> ROOT:ROOT and did not pose a problem with the Apache 2 server.
>> Since the location of the web server changed in version 5, I put a 
>> symbolic link "weewx" in /var/www/html/ pointing to 
>> ~/weewx-data/public_html/weewx [sudo ln -s/ ~/ weewx-data/public_htmlweewx 
>> /var/www/html/weewx].
>>
>> The rights of var/www/html remained ROOT:ROOT while the rights of 
>> ~/weewx-data/public_html/weewx are those of the creator.
>>
>> Filezilla navigation works correctly. Clicking on the symbolic link takes 
>> you to the new WeeWX 5 public_html directory.
>>
>> However, when trying to connect through a web browser (
>> http://xxx.xxx.xxx.xxx/weewx/index.html), I get the response:
>> :
>>
>>
>>
>>
>> *ForbiddenYou don't have permission to access this resource.Apache/2.4.59 
>> (Debian) Server at xxx.xxx.xxx.xxx Port 80*
>>
>> I think it must just be a rights issue...?
>>
>> *What is the recommended solution in Weewx 5 with Apache 2 to redirect 
>> Apache from /var/www/html to ~/weewx-data/public_html?*
>>
>> Thanks a lot for the help! ;-)
>>
>> -- 
>> 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/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Peter Quinn
> (415)794-2264 <(415)%20794-2264>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/5063d8d7-87cf-4fa7-973c-1a36e8f50d3dn%40googlegroups.com.

[weewx-user] Problem for public_html access with Weewx 5 and apache 2

[Remy Lavabre]

Hello,

Good morning,
I didn't find the answer to my problem in the various discussions on the 
WeeWX forum...

I installed Weewx 5 in a virtual environment.
So I have my weewx-data and weewx-venv directories in /home/---/

weewxd seems to "finally" work normally with the ~/weewx-data/public_html 
directory refreshing.

On version 4, the weewx public_html directory was /var/www/html/weewx 
ROOT:ROOT and did not pose a problem with the Apache 2 server.
Since the location of the web server changed in version 5, I put a symbolic 
link "weewx" in /var/www/html/ pointing to ~/weewx-data/public_html/weewx 
[sudo ln -s/ ~/ weewx-data/public_htmlweewx /var/www/html/weewx].

The rights of var/www/html remained ROOT:ROOT while the rights of 
~/weewx-data/public_html/weewx are those of the creator.

Filezilla navigation works correctly. Clicking on the symbolic link takes 
you to the new WeeWX 5 public_html directory.

However, when trying to connect through a web browser 
(http://xxx.xxx.xxx.xxx/weewx/index.html), I get the response:
:




*ForbiddenYou don't have permission to access this resource.Apache/2.4.59 
(Debian) Server at xxx.xxx.xxx.xxx Port 80*

I think it must just be a rights issue...?

*What is the recommended solution in Weewx 5 with Apache 2 to redirect 
Apache from /var/www/html to ~/weewx-data/public_html?*

Thanks a lot for the help! ;-)

-- 
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/1deda7f3-fa1e-4ab8-8ef7-a7b561fa9ffen%40googlegroups.com.

Re: [weewx-user] Problem switching from weewx 4.x -> 5.X

[Remy LAVABRE]

Yes solved !
Thank-you Tom, there was a bin.x forgotten in the [engine] [[service]]
section of weewx.conf... :-((

*Rémy LAVABRE*


Le jeu. 25 avr. 2024 à 17:37, Tom Keffer  a écrit :

> With a pip install, any user modules are normally located in
> ~/weewx-data/bin/user.
>
> You didn't post a copy of the log, but I suspect somewhere in your
> configuration file weewx.conf you have a reference to an extension as
> "bin.user.something" instead of "user.something". Take a look.
>
> If you can't find it, use the tool weectl debug
> <https://www.weewx.com/docs/5.0/utilities/weectl-debug/> to post a copy
> of your configuration file. Be sure to also set debug=1, restart, then post
> a copy of the log. It will have important startup clues.
>
>
> On Thu, Apr 25, 2024 at 8:30 AM Remy Lavabre 
> wrote:
>
>> Good morning,
>>
>> My configuration under weewx 4.10.2 works perfectly with a custom driver.
>>
>> I'm "desperately" trying to upgrade to weewx 5 under virtual environment.
>>
>> -> Configuration with the basic driver simulating the data works ok.
>> -> When I try with my driver, I get the following response:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *(weewx-venv) ---@server:~/weewx-data $ weewxdTraceback (most recent call
>> last):  File "/home//weewx-venv/bin/weewxd", line 8, in 
>> sys.exit(main()) ^^  File
>> "/home//weewx-venv/lib/python3.11/site-packages/weewxd.py", line 160,
>> in mainengine = weewx.engine.StdEngine(config_dict)
>>  ^^^  File
>> "/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line
>> 89, in __init__self.loadServices(config_dict)  File
>> "/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line
>> 157, in loadServicesobj = weeutil.weeutil.get_object(svc)(self,
>> config_dict)  ^^^  File
>> "/home//weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py",
>> line 1404, in get_objectmodule = importlib.import_module(module_name)
>>  File
>> "/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
>> return _bootstrap._gcd_import(name[level:], package, level)
>>    File "> importlib._bootstrap>", line 1206, in _gcd_import  File "> importlib._bootstrap>", line 1178, in _find_and_load  File "> importlib._bootstrap>", line 1128, in _find_and_load_unlocked  File
>> "", line 241, in _call_with_frames_removed
>> File "", line 1206, in _gcd_import  File
>> "", line 1178, in _find_and_load  File
>> "", line 1128, in _find_and_load_unlocked
>> File "", line 241, in
>> _call_with_frames_removed  File "", line 1206,
>> in _gcd_import  File "", line 1178, in
>> _find_and_load  File "", line 1142, in
>> _find_and_load_unlockedModuleNotFoundError: No module named 'bin'*
>>
>> What is the problem ??
>>
>> --
>> 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/909b9a5c-952a-4846-9910-458aaec91616n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/909b9a5c-952a-4846-9910-458aaec91616n%40googlegroups.com?utm_medium=email_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/CAPq0zEAhbUmyp3i0NMWfJ_SUyugOpNT6N83Zp%3D-8U-hYCpna9w%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEAhbUmyp3i0NMWfJ_SUyugOpNT6N83Zp%3D-8U-hYCpna9w%40mail.gmail.com?utm_medium=email_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/CADhm9YfduD1Wwt8cHhufFfQdrtu5QdQqzgXWojr2GZ8DEW107w%40mail.gmail.com.

[weewx-user] Problem switching from weewx 4.x -> 5.X

[Remy Lavabre]

Good morning,

My configuration under weewx 4.10.2 works perfectly with a custom driver.

I'm "desperately" trying to upgrade to weewx 5 under virtual environment.

-> Configuration with the basic driver simulating the data works ok.
-> When I try with my driver, I get the following response:































*(weewx-venv) ---@server:~/weewx-data $ weewxdTraceback (most recent call 
last):  File "/home//weewx-venv/bin/weewxd", line 8, in 
sys.exit(main()) ^^  File 
"/home//weewx-venv/lib/python3.11/site-packages/weewxd.py", line 160, 
in mainengine = weewx.engine.StdEngine(config_dict)
 ^^^  File 
"/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line 
89, in __init__self.loadServices(config_dict)  File 
"/home//weewx-venv/lib/python3.11/site-packages/weewx/engine.py", line 
157, in loadServicesobj = weeutil.weeutil.get_object(svc)(self, 
config_dict)  ^^^  File 
"/home//weewx-venv/lib/python3.11/site-packages/weeutil/weeutil.py", 
line 1404, in get_objectmodule = importlib.import_module(module_name)  
     File 
"/usr/lib/python3.11/importlib/__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)  
   File "", line 1206, in _gcd_import  File "", line 1178, in _find_and_load  File "", line 1128, in _find_and_load_unlocked  File 
"", line 241, in _call_with_frames_removed  
File "", line 1206, in _gcd_import  File 
"", line 1178, in _find_and_load  File 
"", line 1128, in _find_and_load_unlocked  
File "", line 241, in 
_call_with_frames_removed  File "", line 1206, 
in _gcd_import  File "", line 1178, in 
_find_and_load  File "", line 1142, in 
_find_and_load_unlockedModuleNotFoundError: No module named 'bin'*

What is the problem ??

-- 
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/909b9a5c-952a-4846-9910-458aaec91616n%40googlegroups.com.

[weewx-user] Comparison of method of using WeeWX

[Remy Lavabre]

Good morning,

Small question(s) for a PIP installation:

1/ Is there a difference between:
- the use of the weewx daemon
- the weewxd command placed in the contrab at the RPi starting
- the manually typed command "nohup weewxd &"?

2/What is the interest/advantage of one method compared to others?

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/b7d1596e-00e5-4311-b81f-7d0a545fc96dn%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Yes Tom, as I told Matthew in my previous post, I installed V5 in a virtual 
environment then copied the weewx.conf file from my version 4.10.2 which 
works perfectly.
I took the precaution of changing a few variables like SKIN_ROOT = 
skins, HTML_ROOT = public_html, version = 5.0.2
but not WEEWX_ROOT = ~/weewx-data/… :-(

>From the tests I have carried out, it even seems possible to do without 
defining this WEEWX_ROOT variable in weewx.conf of V5... Can you confirm 
Tom?

Many thanks for your software and your much appreciated help! ;-)

Le vendredi 1 mars 2024 à 15:54:48 UTC+1, Tom Keffer a écrit :

> Thank you, Matthew. I had totally forgotten that older weewx.conf files 
> set WEEWX_ROOT=/
>
> Remy: as Matthew asked, do you know how your weewx.conf came to be in its 
> state? Did you copy it from a previous debian install?
>
> On Fri, Mar 1, 2024 at 6:38 AM Remy Lavabre  wrote:
>
>> SOLVED -->> Thank-you MATTHEW ! (and Tom of course...)
>> With *WEEWX_ROOT = ~/weewx-data/*
>>
>> Result -> 
>> Saving installer file to 
>> /home/remy/weewx-data/~/weewx-data/bin/user/installer/awekaswx
>> Saved copy of configuration as 
>> /home/remy/weewx-data/weewx.conf.20240301153706
>> Finished installing extension awekaswx from awekaswx.zip
>>
>> :ooo
>>
>> Le vendredi 1 mars 2024 à 15:34:55 UTC+1, Remy Lavabre a écrit :
>>
>>> Hi Matthew,
>>> Thank you for your help !
>>>
>>> *--->>> /etc/weewx does not exist*
>>> remy@remy-virtual-machine:/etc$ cd weewx
>>> bash: cd: weewx: Aucun fichier ou dossier de ce type
>>>   
>>>
>>> >>> 
>>> *# Root directory of the weewx data file hierarchy for this 
>>> stationWEEWX_ROOT = /*
>>>
>>> >>>> *The weewx.conf file was recovered from version 4.10.2 which 
>>> works perfectly and replaced the weewx.conf file from version 5 after 
>>> installation in a virtual environment and by modifying:*
>>>
>>>
>>> *SKIN_ROOT = skinsHTML_ROOT = public_htmlversion = 5.0.2*
>>>
>>>
>>> Le vendredi 1 mars 2024 à 15:13:04 UTC+1, matthew wall a écrit :
>>>
>>> remy,
>>>
>>> does /etc/weewx exist?
>>>
>>> --->>>>> 
>>>
>>>
>>> does /etc/weewx/bin/user exist?
>>>
>>> in the file ~/weewx-data/weewx.conf, what is WEEWX_ROOT?
>>>
>>> how did the file ~/weewx-data/weewx.conf get to its current state?
>>>
>>> m
>>>
>>> -- 
>>
> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/bf0d11a5-2d3e-4eb8-95b4-43821f035a5bn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/bf0d11a5-2d3e-4eb8-95b4-43821f035a5bn%40googlegroups.com?utm_medium=email_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/a92df256-40f0-4042-bc87-cea709ac92a4n%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

SOLVED -->> Thank-you MATTHEW ! (and Tom of course...)
With *WEEWX_ROOT = ~/weewx-data/*

Result -> 
Saving installer file to 
/home/remy/weewx-data/~/weewx-data/bin/user/installer/awekaswx
Saved copy of configuration as 
/home/remy/weewx-data/weewx.conf.20240301153706
Finished installing extension awekaswx from awekaswx.zip

:ooo

Le vendredi 1 mars 2024 à 15:34:55 UTC+1, Remy Lavabre a écrit :

> Hi Matthew,
> Thank you for your help !
>
> *--->>> /etc/weewx does not exist*
> remy@remy-virtual-machine:/etc$ cd weewx
> bash: cd: weewx: Aucun fichier ou dossier de ce type
>   
>
> >>> 
> *# Root directory of the weewx data file hierarchy for this 
> stationWEEWX_ROOT = /*
>
> >>>> *The weewx.conf file was recovered from version 4.10.2 which 
> works perfectly and replaced the weewx.conf file from version 5 after 
> installation in a virtual environment and by modifying:*
>
>
> *SKIN_ROOT = skinsHTML_ROOT = public_htmlversion = 5.0.2*
>
>
> Le vendredi 1 mars 2024 à 15:13:04 UTC+1, matthew wall a écrit :
>
> remy,
>
> does /etc/weewx exist?
>
> --->>>>> 
>
>
> does /etc/weewx/bin/user exist?
>
> in the file ~/weewx-data/weewx.conf, what is WEEWX_ROOT?
>
> how did the file ~/weewx-data/weewx.conf get to its current state?
>
> m
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/bf0d11a5-2d3e-4eb8-95b4-43821f035a5bn%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Hi Matthew,
Thank you for your help !

*--->>> /etc/weewx does not exist*
remy@remy-virtual-machine:/etc$ cd weewx
bash: cd: weewx: Aucun fichier ou dossier de ce type
  

>>> 
*# Root directory of the weewx data file hierarchy for this 
stationWEEWX_ROOT = /*

 *The weewx.conf file was recovered from version 4.10.2 which works 
perfectly and replaced the weewx.conf file from version 5 after 
installation in a virtual environment and by modifying:*


*SKIN_ROOT = skinsHTML_ROOT = public_htmlversion = 5.0.2*


Le vendredi 1 mars 2024 à 15:13:04 UTC+1, matthew wall a écrit :

remy,

does /etc/weewx exist?

---> 


does /etc/weewx/bin/user exist?

in the file ~/weewx-data/weewx.conf, what is WEEWX_ROOT?

how did the file ~/weewx-data/weewx.conf get to its current state?

m

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/3f100adf-fb5f-4ae1-9891-9ef140e54a9fn%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Hello Tom,

I have also try with the Bresser6in1 driver of Bob Atchley  
-> https://github.com/BobAtchley/weewx-ws6in1

*Same problem *:

Using configuration file /home/remy/weewx-data/weewx.conf
Install extension '6in1.zip' (y/n)? y
Extracting from zip archive 6in1.zip
  Request to install extension found in directory 
/tmp/tmp1rbnn6un/weewx-ws6in1-master/
  Found extension with name 'WS6in1'
  Copying new files...
Copying from '/tmp/tmp1rbnn6un/weewx-ws6in1-master/bin/user/ws6in1.py' 
to '/etc/weewx/bin/user/ws6in1.py'
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 138, in install_extension
extension_name = self._install_from_file(extension_path, filetype)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 168, in _install_from_file
extension_name = self.install_from_dir(extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/weewx/bin/user/ws6in1.py'


Le vendredi 1 mars 2024 à 14:21:47 UTC+1, Remy Lavabre a écrit :

> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$* weectl extension 
> install AWEKAS.zip --verbosity=3*
> Using configuration file /home/remy/weewx-data/weewx.conf
> Install extension 'AWEKAS.zip' (y/n)? y
> Extracting from zip archive AWEKAS.zip
>   Request to install extension found in directory /tmp/tmpmlahffu4/AWEKAS/
>   Found extension with name 'awekaswx'
>   Copying new files...
> Copying from '/tmp/tmpmlahffu4/AWEKAS/bin/user/awekaswx.py' to 
> '/etc/weewx/bin/user/awekaswx.py'
> Traceback (most recent call last):
>   File "/home/remy/weewx-venv/bin/weectl", line 8, in 
> sys.exit(main())
>   File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 
> 66, in main
> namespace.func(namespace)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
> line 121, in dispatch
> namespace.action_func(config_dict, namespace)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>  
> line 116, in install_extension
> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> line 138, in install_extension
> extension_name = self._install_from_file(extension_path, filetype)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> line 168, in _install_from_file
> extension_name = self.install_from_dir(extension_dir)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> line 185, in install_from_dir
> self._install_files(installer['files'], extension_dir)
>   File 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> line 269, in _install_files
> shutil.copy(source_path, destination_path)
>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
> copyfile(src, dst, follow_symlinks=follow_symlinks)
>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/etc/weewx/bin/user/awekaswx.py'
>
>
> Mar  1 14:20:09 remy-virtual-machine weectl[3382]: INFO weectllib: 
> Initializing weectl version 5.0.2
> Mar  1 14:20:09 remy-virtual-machine weectl[3382]: INFO weectllib: Command 
> line: /home/remy/weewx-venv/bin/weectl extension install AWEKAS.zip 
> --verbosity=3
> Mar  1 14:20:

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

(weewx-venv) remy@remy-virtual-machine:~/weewx-data$* weectl extension 
install AWEKAS.zip --verbosity=3*
Using configuration file /home/remy/weewx-data/weewx.conf
Install extension 'AWEKAS.zip' (y/n)? y
Extracting from zip archive AWEKAS.zip
  Request to install extension found in directory /tmp/tmpmlahffu4/AWEKAS/
  Found extension with name 'awekaswx'
  Copying new files...
Copying from '/tmp/tmpmlahffu4/AWEKAS/bin/user/awekaswx.py' to 
'/etc/weewx/bin/user/awekaswx.py'
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 138, in install_extension
extension_name = self._install_from_file(extension_path, filetype)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 168, in _install_from_file
extension_name = self.install_from_dir(extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/weewx/bin/user/awekaswx.py'


Mar  1 14:20:09 remy-virtual-machine weectl[3382]: INFO weectllib: 
Initializing weectl version 5.0.2
Mar  1 14:20:09 remy-virtual-machine weectl[3382]: INFO weectllib: Command 
line: /home/remy/weewx-venv/bin/weectl extension install AWEKAS.zip 
--verbosity=3
Mar  1 14:20:09 remy-virtual-machine weectl[3382]: ERROR weeutil.startup: 
Cannot load user extensions: No module named 'user'

Le vendredi 1 mars 2024 à 14:10:15 UTC+1, Tom Keffer a écrit :

> (Remy sent me a copy of awekas.zip)
>
> It worked for me. Could you try it one more time, this time asking for a 
> more verbose output? It will give us clues where it is trying to copy files 
> to and from.
>
> *weectl extension install awekas.zip --verbosity=3*
>
>
>
> On Thu, Feb 29, 2024 at 2:15 PM Tom Keffer  wrote:
>
>> Yes, I do want it. I am unable to reproduce the problem. It's possible 
>> the problem is with how the extension has been packaged. 
>>
>> On Thu, Feb 29, 2024 at 1:43 PM Remy LAVABRE  wrote:
>>
>>> I do not think that the problem come from awekaswx.py.
>>> The install try to put it in etc/weewx/bin/user/awekaswx.py which does 
>>> not exist as I am under virtuel python environnement !
>>> The problem is independant of what is in awekaswx.py... no ?
>>> You want it anyway ?
>>>
>>>
>>>
>>> Le jeu. 29 févr. 2024, 22:29, Tom Keffer  a écrit :
>>>
>>>> You sent it for the "Unrecognized type" error, not the "No such file" 
>>>> error.
>>>>
>>>> Could you send me the entire file AWEKAS.zip and I will try it on my 
>>>> end?
>>>>
>>>> -tk
>>>>
>>>> On Thu, Feb 29, 2024 at 1:19 PM Remy LAVABRE  
>>>> wrote:
>>>>
>>>>> Sorry Tom but I’ve already send you the return of the terminal :
>>>>>
>>>>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ extension weectl 
>>>>> installer AWEKAS.zip
>>>>> Utilisation du fichier de configuration 
>>>>> /home/remy/weewx-data/weewx.conf
>>>>> Installer l'extension « AWEKAS.zip » (o/n) ? oui
>>>>> Extraction de l'archive zip AWEKAS.zip
>>>>> Traceback (dernier appel le plus récent) :
>>>>> Fichier "/home/remy/weewx-venv/bin/weectl", ligne 8, dans 
>>>>> sys.exit(main())
>>>>> Fichier "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", 
>>>>> ligne 66, dans main
>>>>> espace de noms.func (espace de noms)
>>>>> Fichier 
>>>

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

I do not think that the problem come from awekaswx.py.
The install try to put it in etc/weewx/bin/user/awekaswx.py which does not
exist as I am under virtuel python environnement !
The problem is independant of what is in awekaswx.py... no ?
You want it anyway ?



Le jeu. 29 févr. 2024, 22:29, Tom Keffer  a écrit :

> You sent it for the "Unrecognized type" error, not the "No such file"
> error.
>
> Could you send me the entire file AWEKAS.zip and I will try it on my end?
>
> -tk
>
> On Thu, Feb 29, 2024 at 1:19 PM Remy LAVABRE 
> wrote:
>
>> Sorry Tom but I’ve already send you the return of the terminal :
>>
>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ extension weectl
>> installer AWEKAS.zip
>> Utilisation du fichier de configuration /home/remy/weewx-data/weewx.conf
>> Installer l'extension « AWEKAS.zip » (o/n) ? oui
>> Extraction de l'archive zip AWEKAS.zip
>> Traceback (dernier appel le plus récent) :
>> Fichier "/home/remy/weewx-venv/bin/weectl", ligne 8, dans 
>> sys.exit(main())
>> Fichier "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py",
>> ligne 66, dans main
>> espace de noms.func (espace de noms)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
>> ligne 121, dans dispatch
>> espace de noms.action_func(config_dict, espace de noms)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>> ligne 116, dans install_extension
>> ext.install_extension (namespace.source, no_confirm=namespace.yes)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> ligne 138, dans install_extension
>> extension_name = self._install_from_file (extension_path, type de fichier)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> ligne 168, dans _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> ligne 185, dans install_from_dir
>> self._install_files(installer['files'], extension_dir)
>> Fichier
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> ligne 269, dans _install_files
>> close.copy (chemin_source, chemin_destination)
>> Fichier "/usr/lib/python3.8/shutil.py", ligne 418, en copie
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>> Fichier "/usr/lib/python3.8/shutil.py", ligne 264, dans le copyfile
>> avec open(src, 'rb') comme fsrc, open(dst, 'wb') comme fdst :
>> FileNotFoundError : [Errno 2] Aucun fichier ou répertoire de ce type :
>> '/etc/weewx/bin/user/awekaswx.py'
>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$
>>
>> I have nothing else except syslog already sent...
>> If there there is another information you want, I do not know which one
>> and how to get it... 
>> ???
>>
>>
>>
>> Le jeu. 29 févr. 2024, 19:58, Tom Keffer  a écrit :
>>
>>> When you run "weectl extension install", what shows up on the terminal?
>>> It should tell you which configuration file it is using. That will tell us
>>> what it expects WEEWX_ROOT to be.
>>>
>>> On Thu, Feb 29, 2024 at 10:13 AM Remy LAVABRE 
>>> wrote:
>>>
>>>> Sorry Tom, I don’t understand what you want exactly...
>>>>
>>>> Le jeu. 29 févr. 2024, 17:45, Tom Keffer  a écrit :
>>>>
>>>>> How about the transcript? What did you see when you ran weectl?
>>>>>
>>>>> On Thu, Feb 29, 2024 at 8:05 AM Remy Lavabre 
>>>>> wrote:
>>>>>
>>>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>>>>>> Initializing weectl version 5.0.2
>>>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>>>>>> Command line: /home/remy/weewx-venv/bin/weectl extension install 
>>>>>> AWEKAS.zip
>>>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: ERROR
>>>>>> weeutil.startup: Cannot load user extensions: No module named 'user'
>>>>>>
>>>>>> Le jeudi 29 février 2024 à 16:59:12 UTC+1, Tom Keffer a écrit :
>>>>>>
>>>>>>> It should be trying to install in the WEEWX_ROOT directory, which is
>>>>>>> generally the directory that weewx.conf is in. To diagnose, we

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Sorry.. US version :

(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension 
install AWEKAS.zip
Using configuration file /home/remy/weewx-data/weewx.conf
Install extension 'AWEKAS.zip' (y/n)? y
Extracting from zip archive AWEKAS.zip
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 138, in install_extension
extension_name = self._install_from_file(extension_path, filetype)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 168, in _install_from_file
extension_name = self.install_from_dir(extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/weewx/bin/user/awekaswx.py'
(weewx-venv) remy@remy-virtual-machine:~/weewx-data$

Le jeudi 29 février 2024 à 22:19:57 UTC+1, Remy LAVABRE a écrit :

> Sorry Tom but I’ve already send you the return of the terminal :
>
> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ extension weectl 
> installer AWEKAS.zip
> Utilisation du fichier de configuration /home/remy/weewx-data/weewx.conf
> Installer l'extension « AWEKAS.zip » (o/n) ? oui
> Extraction de l'archive zip AWEKAS.zip
> Traceback (dernier appel le plus récent) :
> Fichier "/home/remy/weewx-venv/bin/weectl", ligne 8, dans 
> sys.exit(main())
> Fichier "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", 
> ligne 66, dans main
> espace de noms.func (espace de noms)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
> ligne 121, dans dispatch
> espace de noms.action_func(config_dict, espace de noms)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>  
> ligne 116, dans install_extension
> ext.install_extension (namespace.source, no_confirm=namespace.yes)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> ligne 138, dans install_extension
> extension_name = self._install_from_file (extension_path, type de fichier)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> ligne 168, dans _install_from_file
> extension_name = self.install_from_dir(extension_dir)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> ligne 185, dans install_from_dir
> self._install_files(installer['files'], extension_dir)
> Fichier 
> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
> ligne 269, dans _install_files
> close.copy (chemin_source, chemin_destination)
> Fichier "/usr/lib/python3.8/shutil.py", ligne 418, en copie
> copyfile(src, dst, follow_symlinks=follow_symlinks)
> Fichier "/usr/lib/python3.8/shutil.py", ligne 264, dans le copyfile
> avec open(src, 'rb') comme fsrc, open(dst, 'wb') comme fdst :
> FileNotFoundError : [Errno 2] Aucun fichier ou répertoire de ce type : 
> '/etc/weewx/bin/user/awekaswx.py'
> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$
>
> I have nothing else except syslog already sent...
> If there there is another information you want, I do not know which one 
> and how to get it... 
> ???
>
>
>
> Le jeu. 29 févr. 2024, 19:58, Tom Keffer  a écrit :
>
>> When you run "weectl extension install", what shows up on the terminal? 
>> It should tell you which configuration file it is using. That will tell us 
>> what it expects WEEWX_ROOT to be. 
>>
>> On Thu, Feb 29, 2024 at 10:13 AM Remy LAVABRE  
>> wrote:
>>
>>> Sorry Tom, I don’t un

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

Sorry Tom but I’ve already send you the return of the terminal :

(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ extension weectl
installer AWEKAS.zip
Utilisation du fichier de configuration /home/remy/weewx-data/weewx.conf
Installer l'extension « AWEKAS.zip » (o/n) ? oui
Extraction de l'archive zip AWEKAS.zip
Traceback (dernier appel le plus récent) :
Fichier "/home/remy/weewx-venv/bin/weectl", ligne 8, dans 
sys.exit(main())
Fichier "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py",
ligne 66, dans main
espace de noms.func (espace de noms)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
ligne 121, dans dispatch
espace de noms.action_func(config_dict, espace de noms)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
ligne 116, dans install_extension
ext.install_extension (namespace.source, no_confirm=namespace.yes)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
ligne 138, dans install_extension
extension_name = self._install_from_file (extension_path, type de fichier)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
ligne 168, dans _install_from_file
extension_name = self.install_from_dir(extension_dir)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
ligne 185, dans install_from_dir
self._install_files(installer['files'], extension_dir)
Fichier
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
ligne 269, dans _install_files
close.copy (chemin_source, chemin_destination)
Fichier "/usr/lib/python3.8/shutil.py", ligne 418, en copie
copyfile(src, dst, follow_symlinks=follow_symlinks)
Fichier "/usr/lib/python3.8/shutil.py", ligne 264, dans le copyfile
avec open(src, 'rb') comme fsrc, open(dst, 'wb') comme fdst :
FileNotFoundError : [Errno 2] Aucun fichier ou répertoire de ce type :
'/etc/weewx/bin/user/awekaswx.py'
(weewx-venv) remy@remy-virtual-machine:~/weewx-data$

I have nothing else except syslog already sent...
If there there is another information you want, I do not know which one and
how to get it... 
???



Le jeu. 29 févr. 2024, 19:58, Tom Keffer  a écrit :

> When you run "weectl extension install", what shows up on the terminal? It
> should tell you which configuration file it is using. That will tell us
> what it expects WEEWX_ROOT to be.
>
> On Thu, Feb 29, 2024 at 10:13 AM Remy LAVABRE 
> wrote:
>
>> Sorry Tom, I don’t understand what you want exactly...
>>
>> Le jeu. 29 févr. 2024, 17:45, Tom Keffer  a écrit :
>>
>>> How about the transcript? What did you see when you ran weectl?
>>>
>>> On Thu, Feb 29, 2024 at 8:05 AM Remy Lavabre 
>>> wrote:
>>>
>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>>>> Initializing weectl version 5.0.2
>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>>>> Command line: /home/remy/weewx-venv/bin/weectl extension install AWEKAS.zip
>>>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: ERROR
>>>> weeutil.startup: Cannot load user extensions: No module named 'user'
>>>>
>>>> Le jeudi 29 février 2024 à 16:59:12 UTC+1, Tom Keffer a écrit :
>>>>
>>>>> It should be trying to install in the WEEWX_ROOT directory, which is
>>>>> generally the directory that weewx.conf is in. To diagnose, we need to see
>>>>> more of the log. It will tell you what WEEWX_ROOT is.
>>>>>
>>>>> Also, it would be useful to see the full transcript when you ran
>>>>> weectl extension install, not just the error.
>>>>>
>>>>> -tk
>>>>>
>>>>> On Thu, Feb 29, 2024 at 7:53 AM Remy Lavabre 
>>>>> wrote:
>>>>>
>>>>>> Ok thanks Tom, thanks Gary.
>>>>>> 1/ Sorry for all these inconveniences, especially since the name in
>>>>>> capital letters was a big stupidity on my part... But by getting so 
>>>>>> angry,
>>>>>> we end up no longer seeing the obvious...
>>>>>>
>>>>>> 2/ These few stupidities having been resolved, there is a new problem
>>>>>> arriving... It will never end! :-(
>>>>>> Obviously the installation is trying to be done in
>>>>>> /etc/weewx/bin/user and not in the virtual environment...Or have I missed
>>>>>> something again???
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
&

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

Sorry Tom, I don’t understand what you want exactly...

Le jeu. 29 févr. 2024, 17:45, Tom Keffer  a écrit :

> How about the transcript? What did you see when you ran weectl?
>
> On Thu, Feb 29, 2024 at 8:05 AM Remy Lavabre 
> wrote:
>
>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>> Initializing weectl version 5.0.2
>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib:
>> Command line: /home/remy/weewx-venv/bin/weectl extension install AWEKAS.zip
>> Feb 29 17:03:12 remy-virtual-machine weectl[3059]: ERROR weeutil.startup:
>> Cannot load user extensions: No module named 'user'
>>
>> Le jeudi 29 février 2024 à 16:59:12 UTC+1, Tom Keffer a écrit :
>>
>>> It should be trying to install in the WEEWX_ROOT directory, which is
>>> generally the directory that weewx.conf is in. To diagnose, we need to see
>>> more of the log. It will tell you what WEEWX_ROOT is.
>>>
>>> Also, it would be useful to see the full transcript when you ran weectl
>>> extension install, not just the error.
>>>
>>> -tk
>>>
>>> On Thu, Feb 29, 2024 at 7:53 AM Remy Lavabre 
>>> wrote:
>>>
>>>> Ok thanks Tom, thanks Gary.
>>>> 1/ Sorry for all these inconveniences, especially since the name in
>>>> capital letters was a big stupidity on my part... But by getting so angry,
>>>> we end up no longer seeing the obvious...
>>>>
>>>> 2/ These few stupidities having been resolved, there is a new problem
>>>> arriving... It will never end! :-(
>>>> Obviously the installation is trying to be done in /etc/weewx/bin/user
>>>> and not in the virtual environment...Or have I missed something again???
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
>>>> install AWEKAS.zipUsing configuration file
>>>> /home/remy/weewx-data/weewx.confInstall extension 'AWEKAS.zip' (y/n)?
>>>> yExtracting from zip archive AWEKAS.zipTraceback (most recent call last):
>>>> File "/home/remy/weewx-venv/bin/weectl", line 8, in 
>>>> sys.exit(main())  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 66, in
>>>> mainnamespace.func(namespace)  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
>>>> line 121, in dispatchnamespace.action_func(config_dict, namespace)
>>>> File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>>>> line 116, in install_extensionext.install_extension(namespace.source,
>>>> no_confirm=namespace.yes)  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>>> line 138, in install_extensionextension_name =
>>>> self._install_from_file(extension_path, filetype)  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>>> line 168, in _install_from_fileextension_name =
>>>> self.install_from_dir(extension_dir)  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>>> line 185, in install_from_dirself._install_files(installer['files'],
>>>> extension_dir)  File
>>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>>> line 269, in _install_filesshutil.copy(source_path, destination_path)
>>>> File "/usr/lib/python3.8/shutil.py", line 418, in copycopyfile(src,
>>>> dst, follow_symlinks=follow_symlinks)  File "/usr/lib/python3.8/shutil.py",
>>>> line 264, in copyfilewith open(src, 'rb') as fsrc, open(dst, 'wb') as
>>>> fdst:FileNotFoundError: [Errno 2] No such file or directory:
>>>> '/etc/weewx/bin/user/awekaswx.py'(weewx-venv)
>>>> remy@remy-virtual-machine:~/weewx-data$ *
>>>>
>>>>
>>>> *Thank you once again! :-(*
>>>>
>>>> Le jeudi 29 février 2024 à 16:40:17 UTC+1, Tom Keffer a écrit :
>&g

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib: 
Initializing weectl version 5.0.2
Feb 29 17:03:12 remy-virtual-machine weectl[3059]: INFO weectllib: Command 
line: /home/remy/weewx-venv/bin/weectl extension install AWEKAS.zip
Feb 29 17:03:12 remy-virtual-machine weectl[3059]: ERROR weeutil.startup: 
Cannot load user extensions: No module named 'user'

Le jeudi 29 février 2024 à 16:59:12 UTC+1, Tom Keffer a écrit :

> It should be trying to install in the WEEWX_ROOT directory, which is 
> generally the directory that weewx.conf is in. To diagnose, we need to see 
> more of the log. It will tell you what WEEWX_ROOT is. 
>
> Also, it would be useful to see the full transcript when you ran weectl 
> extension install, not just the error.
>
> -tk
>
> On Thu, Feb 29, 2024 at 7:53 AM Remy Lavabre  wrote:
>
>> Ok thanks Tom, thanks Gary.
>> 1/ Sorry for all these inconveniences, especially since the name in 
>> capital letters was a big stupidity on my part... But by getting so angry, 
>> we end up no longer seeing the obvious...
>>
>> 2/ These few stupidities having been resolved, there is a new problem 
>> arriving... It will never end! :-(
>> Obviously the installation is trying to be done in /etc/weewx/bin/user 
>> and not in the virtual environment...Or have I missed something again???
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension 
>> install AWEKAS.zipUsing configuration file 
>> /home/remy/weewx-data/weewx.confInstall extension 'AWEKAS.zip' (y/n)? 
>> yExtracting from zip archive AWEKAS.zipTraceback (most recent call last):  
>> File "/home/remy/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 66, in 
>> mainnamespace.func(namespace)  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
>> line 121, in dispatchnamespace.action_func(config_dict, namespace)  
>> File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>>  
>> line 116, in install_extensionext.install_extension(namespace.source, 
>> no_confirm=namespace.yes)  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>> line 138, in install_extensionextension_name = 
>> self._install_from_file(extension_path, filetype)  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>> line 168, in _install_from_fileextension_name = 
>> self.install_from_dir(extension_dir)  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>> line 185, in install_from_dirself._install_files(installer['files'], 
>> extension_dir)  File 
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>> line 269, in _install_filesshutil.copy(source_path, destination_path)  
>> File "/usr/lib/python3.8/shutil.py", line 418, in copycopyfile(src, 
>> dst, follow_symlinks=follow_symlinks)  File "/usr/lib/python3.8/shutil.py", 
>> line 264, in copyfilewith open(src, 'rb') as fsrc, open(dst, 'wb') as 
>> fdst:FileNotFoundError: [Errno 2] No such file or directory: 
>> '/etc/weewx/bin/user/awekaswx.py'(weewx-venv) 
>> remy@remy-virtual-machine:~/weewx-data$ *
>>
>>
>> *Thank you once again! :-(*
>>
>> Le jeudi 29 février 2024 à 16:40:17 UTC+1, Tom Keffer a écrit :
>>
>>> On Thu, Feb 29, 2024 at 12:01 AM Remy Lavabre  
>>> wrote:
>>>
>>>> Hello Tom,
>>>> in your doc (
>>>> https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips), 
>>>> you say :
>>>>
>>>>
>>>>
>>>> *A basic skeleton for your file might look like the one below.from 
>>>> setup import ExtensionInstaller*
>>>>
>>>
>>> Wow. That's the first time I've noticed that page! Fixed.
>>>
>>> In any case, it looks like that was not the problem.
>>>
>> -- 
>>
> 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/c6aa3f12-0903-42a1-a764-70bcfa2f8been%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/c6aa3f12-0903-42a1-a764-70bcfa2f8been%40googlegroups.com?utm_medium=email_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/8d965e23-fd96-43e8-8aba-0a86d39878den%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Ok thanks Tom, thanks Gary.
1/ Sorry for all these inconveniences, especially since the name in capital 
letters was a big stupidity on my part... But by getting so angry, we end 
up no longer seeing the obvious...

2/ These few stupidities having been resolved, there is a new problem 
arriving... It will never end! :-(
Obviously the installation is trying to be done in /etc/weewx/bin/user and 
not in the virtual environment...Or have I missed something again???



























*(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension 
install AWEKAS.zipUsing configuration file 
/home/remy/weewx-data/weewx.confInstall extension 'AWEKAS.zip' (y/n)? 
yExtracting from zip archive AWEKAS.zipTraceback (most recent call last):  
File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 66, in 
mainnamespace.func(namespace)  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
line 121, in dispatchnamespace.action_func(config_dict, namespace)  
File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extensionext.install_extension(namespace.source, 
no_confirm=namespace.yes)  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 138, in install_extensionextension_name = 
self._install_from_file(extension_path, filetype)  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 168, in _install_from_fileextension_name = 
self.install_from_dir(extension_dir)  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 185, in install_from_dirself._install_files(installer['files'], 
extension_dir)  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 269, in _install_filesshutil.copy(source_path, destination_path)  
File "/usr/lib/python3.8/shutil.py", line 418, in copycopyfile(src, 
dst, follow_symlinks=follow_symlinks)  File "/usr/lib/python3.8/shutil.py", 
line 264, in copyfilewith open(src, 'rb') as fsrc, open(dst, 'wb') as 
fdst:FileNotFoundError: [Errno 2] No such file or directory: 
'/etc/weewx/bin/user/awekaswx.py'(weewx-venv) 
remy@remy-virtual-machine:~/weewx-data$ *


*Thank you once again! :-(*

Le jeudi 29 février 2024 à 16:40:17 UTC+1, Tom Keffer a écrit :

> On Thu, Feb 29, 2024 at 12:01 AM Remy Lavabre  wrote:
>
>> Hello Tom,
>> in your doc (
>> https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips), you 
>> say :
>>
>>
>>
>> *A basic skeleton for your file might look like the one below.from setup 
>> import ExtensionInstaller*
>>
>
> Wow. That's the first time I've noticed that page! Fixed.
>
> In any case, it looks like that was not the problem.
>

-- 
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/c6aa3f12-0903-42a1-a764-70bcfa2f8been%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Yesss ! Thank's Gary!!! We progress... :-)))

BUT... :-(((
Now with *from weecfg.extension import ExtensionInstaller or from setup 
import ExtensionInstaller the error* in install.py, the error is :

 (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension 
install awekas.zip
Using configuration file /home/remy/weewx-data/weewx.conf
Install extension 'awekas.zip' (y/n)? y
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line 
66, in main
namespace.func(namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py", 
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File 
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
line 143, in install_extension
raise InstallError(f"Unrecognized type for {extension_path}")
weecfg.extension.InstallError: Unrecognized type for awekas.zip

Le jeudi 29 février 2024 à 09:35:50 UTC+1, gjr80 a écrit :

> On Thursday 29 February 2024 at 17:50:33 UTC+10 remy.l...@gmail.com wrote:
>
> *with* :  unzip -l AWEKAS.zip 
> *we have* :
> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ unzip -l AWEKAS.zip
> Archive:  AWEKAS.zip
>   Length  DateTimeName
> -  -- -   
> 0  2024-02-29 08:42   AWEKAS/
>   565  2024-02-29 08:42   AWEKAS/install.py
> 35149  2024-02-26 10:33   AWEKAS/LICENSE.txt
> 56528  2024-02-26 10:33   AWEKAS*/awekaswx.py*
> - ---
> 92242 4 files
>
>
> And there is your problem, the structure of your extension package/archive 
> does not agree with the instructions you have given to the installer. The 
> line:
>
> files=[('bin/user', ['bin/user/awekaswx.py'])],
>
> in your installer is telling the extension installer to copy the file 
> awekaswx.py from the bin/user directory in your extension package/archive 
> to the WeeWX bin/user directory. The problem is bin/user/awekaswx.py does 
> not exist in your archive, you have awekaswx.py in the main directory (
> AWEKAS) of your archive.
>
> Take for example the Ecowitt gateway driver extension package, its 
> structure is:
>
> gary@cockatoo1:~ $ unzip -l ./gw1000.zip
> Archive:  ./gw1000.zip
>
>   Length  DateTimeName
> -  -- -   
> 0  2024-02-21 19:39   gw1000/bin/
> 0  2024-02-21 19:39   gw1000/bin/user/
>  6148  2024-02-11 20:14   gw1000/bin/user/.DS_Store
>390698  2024-02-21 19:39   gw1000/bin/user/gw1000.py
>  8355  2024-02-21 19:39   gw1000/changelog
> 4  2024-02-21 19:39   gw1000/install.py
> 11346  2024-02-21 19:39   gw1000/readme.txt
> - ---
>
> The extension installer has the same line:
>
> files=[('bin/user', ['bin/user/gw1000.py'])],
>  
> (well the same but of course a different file name). Note 
> bin/user/gw1000.py exists in the extension package/extension. 
>
>  To fix you have two choices, change the files = line in your extension 
> installer or change the structure of your extension package/archive. I 
> favour the latter, it keeps the structure of the extension package more 
> akin to the WeeWX file structure and avoids the 'put everything in one 
> directory' approach. Your choice.
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/c68bfef7-ce42-4ec3-9765-0072e24ce6a2n%40googlegroups.com.

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Hello Tom,
in your doc 
(https://github.com/weewx/weewx/wiki/Weewx-Driver-Development-Tips), you 
say :




*A basic skeleton for your file might look like the one below.from setup 
import ExtensionInstaller...*

Le jeudi 29 février 2024 à 08:50:33 UTC+1, Remy LAVABRE a écrit :

> *with* :  unzip -l AWEKAS.zip 
> *we have* :
> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ unzip -l AWEKAS.zip
> Archive:  AWEKAS.zip
>   Length  DateTimeName
> -  -- -   
> 0  2024-02-29 08:42   AWEKAS/
>   565  2024-02-29 08:42   AWEKAS/install.py
> 35149  2024-02-26 10:33   AWEKAS/LICENSE.txt
> 56528  2024-02-26 10:33   AWEKAS*/awekaswx.py*
> - ---
> 92242 4 files
>
>
> *Rémy LAVABRE*
>
>
> Le mer. 28 févr. 2024 à 09:32, gjr80  a écrit :
>
>> What does unzip -l AWEKAS.zip show? Does bin/user/awekaswx.py actually 
>> exist in the zip file?
>>
>> Gary
>> On Wednesday 28 February 2024 at 17:54:49 UTC+10 remy.l...@gmail.com 
>> wrote:
>>
>>> Hello Tom,
>>> First problem : when trying to install a driver in virtual 
>>> environnement :
>>>
>>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension 
>>> install AWEKAS.zip
>>> Using configuration file /home/remy/weewx-data/weewx.conf
>>> Install extension 'AWEKAS.zip' (y/n)? y
>>> Extracting from zip archive AWEKAS.zip
>>> Traceback (most recent call last):
>>>   File "/home/remy/weewx-venv/bin/weectl", line 8, in 
>>> sys.exit(main())
>>>   File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", 
>>> line 66, in main
>>> namespace.func(namespace)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py", 
>>> line 121, in dispatch
>>> namespace.action_func(config_dict, namespace)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>>>  
>>> line 116, in install_extension
>>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>>> line 138, in install_extension
>>> extension_name = self._install_from_file(extension_path, filetype)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>>> line 168, in _install_from_file
>>> extension_name = self.install_from_dir(extension_dir)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>>> line 185, in install_from_dir
>>> self._install_files(installer['files'], extension_dir)
>>>   File 
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py", 
>>> line 269, in _install_files
>>> shutil.copy(source_path, destination_path)
>>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>>> FileNotFoundError: [Errno 2] No such file or directory: 
>>> '/tmp/tmprpxo6tw5/AWEKAS/bin/user/awekaswx.py'
>>>
>>> *and the install.py :*
>>>
>>> # installer for Awekas Bresser awekaswx driver
>>> # Copyright 2024 Remy LAVABRE
>>>
>>> from setup import ExtensionInstaller
>>>
>>> def loader():
>>> return awekaswxInstaller()
>>>
>>> class awekaswxInstaller(ExtensionInstaller):
>>> def __init__(self):
>>> super(awekaswxInstaller, self).__init__(
>>> version="1.3",
>>> name='awekaswx',
>>> description='Get Bresser 7in1 data on Awekas',
>>> author="Remy LAVABRE",
>>> author_email="remy.l...@gmail.com",
>>> files=[('bin/user', ['bin/user/awekaswx.py'])],
>>> config={
>>> 'awekaswx': {
>>> 'driver' : 'bin.user.awekaswx',
>>>     'poll_interval': '60',
>>> 'awekasapikey' :'My_API_Awekas_Key','
>>> 'openweatherapikey': 'My_API_OpenWeather_Key',
>>> 'send_syslog

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

*with* :  unzip -l AWEKAS.zip
*we have* :
(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ unzip -l AWEKAS.zip
Archive:  AWEKAS.zip
  Length  DateTimeName
-  -- -   
0  2024-02-29 08:42   AWEKAS/
  565  2024-02-29 08:42   AWEKAS/install.py
35149  2024-02-26 10:33   AWEKAS/LICENSE.txt
56528  2024-02-26 10:33   AWEKAS*/awekaswx.py*
- ---
92242 4 files


*Rémy LAVABRE*


Le mer. 28 févr. 2024 à 09:32, gjr80  a écrit :

> What does unzip -l AWEKAS.zip show? Does bin/user/awekaswx.py actually
> exist in the zip file?
>
> Gary
> On Wednesday 28 February 2024 at 17:54:49 UTC+10 remy.l...@gmail.com
> wrote:
>
>> Hello Tom,
>> First problem : when trying to install a driver in virtual environnement :
>>
>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
>> install AWEKAS.zip
>> Using configuration file /home/remy/weewx-data/weewx.conf
>> Install extension 'AWEKAS.zip' (y/n)? y
>> Extracting from zip archive AWEKAS.zip
>> Traceback (most recent call last):
>>   File "/home/remy/weewx-venv/bin/weectl", line 8, in 
>> sys.exit(main())
>>   File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py",
>> line 66, in main
>> namespace.func(namespace)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
>> line 121, in dispatch
>> namespace.action_func(config_dict, namespace)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>> line 116, in install_extension
>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> line 138, in install_extension
>> extension_name = self._install_from_file(extension_path, filetype)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> line 168, in _install_from_file
>> extension_name = self.install_from_dir(extension_dir)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> line 185, in install_from_dir
>> self._install_files(installer['files'], extension_dir)
>>   File
>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>> line 269, in _install_files
>> shutil.copy(source_path, destination_path)
>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>> FileNotFoundError: [Errno 2] No such file or directory:
>> '/tmp/tmprpxo6tw5/AWEKAS/bin/user/awekaswx.py'
>>
>> *and the install.py :*
>>
>> # installer for Awekas Bresser awekaswx driver
>> # Copyright 2024 Remy LAVABRE
>>
>> from setup import ExtensionInstaller
>>
>> def loader():
>> return awekaswxInstaller()
>>
>> class awekaswxInstaller(ExtensionInstaller):
>> def __init__(self):
>> super(awekaswxInstaller, self).__init__(
>> version="1.3",
>> name='awekaswx',
>> description='Get Bresser 7in1 data on Awekas',
>> author="Remy LAVABRE",
>> author_email="remy.l...@gmail.com",
>> files=[('bin/user', ['bin/user/awekaswx.py'])],
>> config={
>> 'awekaswx': {
>> 'driver' : 'bin.user.awekaswx',
>> 'poll_interval': '60',
>> 'awekasapikey' :'My_API_Awekas_Key','
>> 'openweatherapikey': 'My_API_OpenWeather_Key',
>> 'send_syslog': 'True',
>> 'model': 'Bresser 7in1'
>> }
>> }
>> )
>>
>> *Rémy LAVABRE*
>>
>>
>> Le dim. 25 févr. 2024 à 22:45, Tom Keffer  a écrit :
>>
>>> From your description, you're installing it in the correct spot, however
>>> you're not giving us much information. Instead of just showing the single
>>> error line, it would be helpful to see the log from startup. The reason is
>>> that it will log the location of the user directory.
>>>
>>> Set debug=1, then restart weewxd. Post the log *from startup* through
>>> the error.
>>>
>>> 

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

*with :*
*from weecfg.extension import ExtensionInstaller*

def loader():
return awekaswxInstaller()

class awekaswxInstaller(ExtensionInstaller):
def __init__(self):
super(awekaswxInstaller, self).__init__(
version="1.3",
name='awekaswx',
description='Get Bresser 7in1 data on Awekas',
    author="Remy LAVABRE",
author_email="remy.lava...@gmail.com",
files=[('bin/user', ['bin/user/awekaswx.py'])]
)

*We have :*

(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
install awekas.zip
Using configuration file /home/remy/weewx-data/weewx.conf
Install extension 'awekas.zip' (y/n)? y
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line
66, in main
namespace.func(namespace)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
line 143, in install_extension
raise InstallError(f"Unrecognized type for {extension_path}")
weecfg.extension.InstallError: Unrecognized type for awekas.zip

*Rémy LAVABRE*


Le jeu. 29 févr. 2024 à 01:52, Tom Keffer  a écrit :

> I haven't tried it, but I'm thinking the problem is that the awekas
> extension uses
>
> *from setup import ExtensionInstaller*
>
>
> which has been deprecated for a long time and will no longer work with V5.
> It should be
>
> *from weecfg.extension import ExtensionInstaller*
>
>
> Try modifying the extension and see if that helps.
>
> On Wed, Feb 28, 2024 at 12:32 AM gjr80  wrote:
>
>> What does unzip -l AWEKAS.zip show? Does bin/user/awekaswx.py actually
>> exist in the zip file?
>>
>> Gary
>> On Wednesday 28 February 2024 at 17:54:49 UTC+10 remy.l...@gmail.com
>> wrote:
>>
>>> Hello Tom,
>>> First problem : when trying to install a driver in virtual
>>> environnement :
>>>
>>> (weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
>>> install AWEKAS.zip
>>> Using configuration file /home/remy/weewx-data/weewx.conf
>>> Install extension 'AWEKAS.zip' (y/n)? y
>>> Extracting from zip archive AWEKAS.zip
>>> Traceback (most recent call last):
>>>   File "/home/remy/weewx-venv/bin/weectl", line 8, in 
>>> sys.exit(main())
>>>   File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py",
>>> line 66, in main
>>> namespace.func(namespace)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
>>> line 121, in dispatch
>>> namespace.action_func(config_dict, namespace)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
>>> line 116, in install_extension
>>> ext.install_extension(namespace.source, no_confirm=namespace.yes)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>> line 138, in install_extension
>>> extension_name = self._install_from_file(extension_path, filetype)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>> line 168, in _install_from_file
>>> extension_name = self.install_from_dir(extension_dir)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>> line 185, in install_from_dir
>>> self._install_files(installer['files'], extension_dir)
>>>   File
>>> "/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
>>> line 269, in _install_files
>>> shutil.copy(source_path, destination_path)
>>>   File "/usr/lib/python3.8/shutil.py", line 418, in copy
>>> copyfile(src, dst, follow_symlinks=follow_symlinks)
>>>   File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
>>> with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
>>> FileNotFoundError: [Errno 2] No such file or directory:
>>> '/tmp/tmprpxo6tw5/AWEKAS/bin/user/awekaswx.py'
>>>
>>> *and the install.py :*
>>>
>

Re: [weewx-user] Problem with WeeWX5 "driver" directory

[Remy LAVABRE]

Hello Tom,
First problem : when trying to install a driver in virtual environnement :

(weewx-venv) remy@remy-virtual-machine:~/weewx-data$ weectl extension
install AWEKAS.zip
Using configuration file /home/remy/weewx-data/weewx.conf
Install extension 'AWEKAS.zip' (y/n)? y
Extracting from zip archive AWEKAS.zip
Traceback (most recent call last):
  File "/home/remy/weewx-venv/bin/weectl", line 8, in 
sys.exit(main())
  File "/home/remy/weewx-venv/lib/python3.8/site-packages/weectl.py", line
66, in main
namespace.func(namespace)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/__init__.py",
line 121, in dispatch
namespace.action_func(config_dict, namespace)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weectllib/extension_cmd.py",
line 116, in install_extension
ext.install_extension(namespace.source, no_confirm=namespace.yes)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
line 138, in install_extension
extension_name = self._install_from_file(extension_path, filetype)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
line 168, in _install_from_file
extension_name = self.install_from_dir(extension_dir)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
line 185, in install_from_dir
self._install_files(installer['files'], extension_dir)
  File
"/home/remy/weewx-venv/lib/python3.8/site-packages/weecfg/extension.py",
line 269, in _install_files
shutil.copy(source_path, destination_path)
  File "/usr/lib/python3.8/shutil.py", line 418, in copy
copyfile(src, dst, follow_symlinks=follow_symlinks)
  File "/usr/lib/python3.8/shutil.py", line 264, in copyfile
with open(src, 'rb') as fsrc, open(dst, 'wb') as fdst:
FileNotFoundError: [Errno 2] No such file or directory:
'/tmp/tmprpxo6tw5/AWEKAS/bin/user/awekaswx.py'

*and the install.py :*

# installer for Awekas Bresser awekaswx driver
# Copyright 2024 Remy LAVABRE

from setup import ExtensionInstaller

def loader():
return awekaswxInstaller()

class awekaswxInstaller(ExtensionInstaller):
def __init__(self):
super(awekaswxInstaller, self).__init__(
version="1.3",
        name='awekaswx',
description='Get Bresser 7in1 data on Awekas',
author="Remy LAVABRE",
author_email="remy.lava...@gmail.com",
files=[('bin/user', ['bin/user/awekaswx.py'])],
config={
'awekaswx': {
'driver' : 'bin.user.awekaswx',
'poll_interval': '60',
'awekasapikey' :'My_API_Awekas_Key','
'openweatherapikey': 'My_API_OpenWeather_Key',
'send_syslog': 'True',
'model': 'Bresser 7in1'
}
}
)

*Rémy LAVABRE*


Le dim. 25 févr. 2024 à 22:45, Tom Keffer  a écrit :

> From your description, you're installing it in the correct spot, however
> you're not giving us much information. Instead of just showing the single
> error line, it would be helpful to see the log from startup. The reason is
> that it will log the location of the user directory.
>
> Set debug=1, then restart weewxd. Post the log *from startup* through the
> error.
>
> On Sun, Feb 25, 2024 at 10:55 AM Remy Lavabre 
> wrote:
>
>> Hello,
>>
>> weewx is installed in virtual PIP mode -> ~/weewx-data/... and
>> ~/weewx-venv/...
>> I manually added the xxx.py driver for my weather station in the
>> ~/weewx-data/bin/user directory.
>> It is declared in weewx.conf as "driver = usr.xxx", as was done in
>> version 4.x
>>
>> When launching weewxd, I get the message:
>>File
>> "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", line
>> 104, in setupStation
>>  __import__(driver)
>> ModuleNotFoundError: *No module named 'usr'*
>>
>> I tried "driver = xxx.py" without success
>>
>> if I put my driver in
>> ~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put
>> driver = xxx.py in weewx.conf there is no longer the error.
>>
>> Moral: Would it be possible to tell me the exact location where to put my
>> driver in the user directory and how to declare it in weewx.conf ?
>>
>> 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] Re: Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Sorry, small error on my part, it's not "usr" that should be read but "user"

Le dimanche 25 février 2024 à 19:55:27 UTC+1, Remy Lavabre a écrit :

> Hello,
>
> weewx is installed in virtual PIP mode -> ~/weewx-data/... and 
> ~/weewx-venv/...
> I manually added the xxx.py driver for my weather station in the 
> ~/weewx-data/bin/user directory.
> It is declared in weewx.conf as "driver = usr.xxx", as was done in version 
> 4.x
>
> When launching weewxd, I get the message:
>File "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", 
> line 104, in setupStation
>  __import__(driver)
> ModuleNotFoundError: *No module named 'usr'*
>
> I tried "driver = xxx.py" without success
>
> if I put my driver in 
> ~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put 
> driver = xxx.py in weewx.conf there is no longer the error.
>
> Moral: Would it be possible to tell me the exact location where to put my 
> driver in the user directory and how to declare it in weewx.conf ?
>
> 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/6e41bfdc-59cc-454e-b684-3c012745f412n%40googlegroups.com.

[weewx-user] Problem with WeeWX5 "driver" directory

[Remy Lavabre]

Hello,

weewx is installed in virtual PIP mode -> ~/weewx-data/... and 
~/weewx-venv/...
I manually added the xxx.py driver for my weather station in the 
~/weewx-data/bin/user directory.
It is declared in weewx.conf as "driver = usr.xxx", as was done in version 
4.x

When launching weewxd, I get the message:
   File "/home/pi/weewx-venv/lib/python3.8/site-packages/weewx/engine.py", 
line 104, in setupStation
 __import__(driver)
ModuleNotFoundError: *No module named 'usr'*

I tried "driver = xxx.py" without success

if I put my driver in 
~/weewx-venv/lib/python3.8/site-packages/weewx/drivers/xxx.py and I put 
driver = xxx.py in weewx.conf there is no longer the error.

Moral: Would it be possible to tell me the exact location where to put my 
driver in the user directory and how to declare it in weewx.conf ?

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/a6fe6217-0ad7-45b0-8dae-74c94db83fbdn%40googlegroups.com.

Re: [weewx-user] Interceptor + weewx + Bresser

[Remy LAVABRE]

Ok;.. Va pour la version FR.

1/ Dans le paquet généré il y a bien un "soil_most2" mais je ne vois pas de
"soil_moist1". Dans le RAW c'est la même chose : 'soil_moisture_2' mais pas
vu de 'soil_moisture_1'
Avant d'aller plus loin, il y a peut-être déjà là quelque chose à
regarder qui ne marche pas bien... ?

2/ Dans la config de weewx, une fois résolu le point 1/, dans la section
[interceptor], j'aurais tendance à essayer la chose suivante :

[Interceptor]
driver = user.interceptor
device_type = x
...
[[sensor_map_extensions]]
   ...
extraTemp1 = soil_temperature_1
extraTemp2 = soil_temperature_2
extraHumid1 = soil_moisture_1
extraHumid2 = soil_moisture_2

3/ Si vous avez des sondes de température et hygrométrie *de sol*, ok pas
de problème. En revanche si vous avez des sondes de température extérieures
indiquant la température et l'hygrométrie de l'air ambiant, c'est curieux
que le nom récupéré soit "soil_xxx".
Mais comme je vous l'indiquais, sur Awekas, quand je récupère via l'API
les données envoyées par la base Bresser, les températures des sondes
extérieures sont dans les bons champs, en revanche les hygrométries sont
rentrées dans des hygrométries de sonde de sol..
C'est très curieux, et dixit le SAV de Bresser France, je ne suis pas
le seul à avoir signalé la chose !
Côté Bresser "teutons", la chose ne semble pas trop leur poser de
problème métaphysiques... A moins que la modification du firmware de la
base de la station ne soit pas une de leurs priorités !

*Rémy LAVABRE*


Le sam. 24 févr. 2024 à 10:54, sc.lep...@gmail.com 
a écrit :

> Hello Remy (... et bonjour en Français  :)
>  On va le faire en Français  c'est plus simple  :
>  je récupère les data  via  interceptor en Wifi sur Weewx ... Toutes mes
> datas je les récupère correctement.
> la valeur inTemp est celle de la base ca  ok .
> mais  j'ai 2 sondes  en plus  et je voudrais également récupérer ces
> données  (soilTemp1 et soilTemp2) et ma question était comment paramétrer
> le driver interceptor
> Sur le repo  github  ce n'est pas très clair...
>
> Mon site est ici  :  https://meteo-pontscorff.fr/ (il y a mes coordonnées
> mail)
> Merci  !
> Stéphane
>
> Le samedi 24 février 2024 à 05:49:39 UTC+1, Remy LAVABRE a écrit :
>
>> stephane hello,
>> I said something stupid to you previously. interceptor intercepts at the
>> wifi level and not as I thought at the 400 or 800 Mhz radio level... sorry!
>>
>> so normal that you have inTemp and barometer! :-)
>>
>> I too have a Bresser station and retrieve data automatically from Awekas
>> in the absence of a USB output. I have several exterior sensors and there
>> is a somewhat similar problem. the hygrometer values of the probes are
>> retrieved as hygrometer values of the floor probes while the temperatures
>> are retrieved as temperatures of external probes.
>>
>> I reported this anomaly to Bresser in France who already reported it
>> almost a year ago, knowing that I was not the only one to have reported it
>> to them.
>> I also reported the problem to Germany who basically told me it was
>> "normal" operation without explanation
>>
>> As I wrote a driver for weewx which retrieves data directly from Awekas
>> at regular intervals, I reverse the value fields myself...
>>
>> Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com 
>> a écrit :
>>
>>> Hello
>>> I use  weewx  with interceptor :
>>>
>>> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG
>>> user.interceptor: raw packet: {'dateTime': 1708726142, 'usUnits': 1,
>>> 'rain_total': 0.09, 'barometer': 29.99, 'temperature_out': 34.7,
>>> 'humidity_out': 90.0, 'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir':
>>> 138.0, 'dewpoint': 32.0, 'temperature_in': 66.2, 'humidity_in': 57.0, 'uv':
>>> 0.0, 'solar_radiation': 0.0, 'soil_temperature_1': 66.2,
>>> 'soil_temperature_2': 70.8, 'soil_moisture_2': 60.0, 'rain': None}
>>> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG
>>> user.interceptor: mapped packet: {'dateTime': 1708726142, 'usUnits': 1,
>>> 'barometer': 29.99, 'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp':
>>> 34.7, 'inTemp': 66.2, 'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0,
>>> 'radiation': 0.0, 'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1':
>>> 66.2, 'soilTemp2': 70.8, 'soilMoist2': 60.0}
>>>
>>> I dont understand how to use :
>>> soilTemp1': 66.2, '
>>> soilTemp2': 70.8, '
>>> soil_moist1': 60.0,
>>> soil_moist2': 60.0,
>>>
>>> I've 2 temperatures probes
>>>
>

Re: [weewx-user] Interceptor + weewx + Bresser

[Remy LAVABRE]

stephane hello,
I said something stupid to you previously. interceptor intercepts at the
wifi level and not as I thought at the 400 or 800 Mhz radio level... sorry!

so normal that you have inTemp and barometer! :-)

I too have a Bresser station and retrieve data automatically from Awekas in
the absence of a USB output. I have several exterior sensors and there is a
somewhat similar problem. the hygrometer values ​​of the probes are
retrieved as hygrometer values ​​of the floor probes while the temperatures
are retrieved as temperatures of external probes.

I reported this anomaly to Bresser in France who already reported it almost
a year ago, knowing that I was not the only one to have reported it to them.
I also reported the problem to Germany who basically told me it was
"normal" operation without explanation

As I wrote a driver for weewx which retrieves data directly from Awekas at
regular intervals, I reverse the value fields myself...

Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com 
a écrit :

> Hello
> I use  weewx  with interceptor :
>
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> raw packet: {'dateTime': 1708726142, 'usUnits': 1, 'rain_total': 0.09,
> 'barometer': 29.99, 'temperature_out': 34.7, 'humidity_out': 90.0,
> 'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir': 138.0, 'dewpoint': 32.0,
> 'temperature_in': 66.2, 'humidity_in': 57.0, 'uv': 0.0, 'solar_radiation':
> 0.0, 'soil_temperature_1': 66.2, 'soil_temperature_2': 70.8,
> 'soil_moisture_2': 60.0, 'rain': None}
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> mapped packet: {'dateTime': 1708726142, 'usUnits': 1, 'barometer': 29.99,
> 'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp': 34.7, 'inTemp': 66.2,
> 'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0, 'radiation': 0.0,
> 'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1': 66.2, 'soilTemp2':
> 70.8, 'soilMoist2': 60.0}
>
> I dont understand how to use :
> soilTemp1': 66.2, '
> soilTemp2': 70.8, '
> soil_moist1': 60.0,
> soil_moist2': 60.0,
>
> I've 2 temperatures probes
>
> Can someone explain me how to add this in weewx.conf ?
>
> in section  :
>  [[sensor_map_extensions]]
> ???inTemp = temperature_1
>  ???   inHumidity = humidity_1
>  ???   outTemp = temperature_4
>   ???  outHumidity = humidity_4
>
>
> Thanks a lot  ;)
>
> Stephane
>
> --
> 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/c851119a-b274-4ecd-99a3-605d2e393946n%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/CADhm9Yf4z%3DAm12NEJYBFe6vDQbAUWz-H74mNWnenaQGQ5SdQOg%40mail.gmail.com.

Re: [weewx-user] Interceptor + weewx + Bresser

[Remy LAVABRE]

What is the Bresser station you use Stéphane ?
Normaly no inTemp with bresser and interceptor -> inTemp is given with by
the base and so not radio send as the barometer value...


Le ven. 23 févr. 2024, 23:19, sc.lep...@gmail.com 
a écrit :

> Hello
> I use  weewx  with interceptor :
>
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> raw packet: {'dateTime': 1708726142, 'usUnits': 1, 'rain_total': 0.09,
> 'barometer': 29.99, 'temperature_out': 34.7, 'humidity_out': 90.0,
> 'wind_speed': 0.0, 'wind_gust': 0.0, 'wind_dir': 138.0, 'dewpoint': 32.0,
> 'temperature_in': 66.2, 'humidity_in': 57.0, 'uv': 0.0, 'solar_radiation':
> 0.0, 'soil_temperature_1': 66.2, 'soil_temperature_2': 70.8,
> 'soil_moisture_2': 60.0, 'rain': None}
> Feb 23 23:09:01 meteo-Ubuntu weewx-BRESSER[63190] DEBUG user.interceptor:
> mapped packet: {'dateTime': 1708726142, 'usUnits': 1, 'barometer': 29.99,
> 'outHumidity': 90.0, 'inHumidity': 57.0, 'outTemp': 34.7, 'inTemp': 66.2,
> 'windSpeed': 0.0, 'windGust': 0.0, 'windDir': 138.0, 'radiation': 0.0,
> 'dewpoint': 32.0, 'rain': None, 'UV': 0.0, 'soilTemp1': 66.2, 'soilTemp2':
> 70.8, 'soilMoist2': 60.0}
>
> I dont understand how to use :
> soilTemp1': 66.2, '
> soilTemp2': 70.8, '
> soil_moist1': 60.0,
> soil_moist2': 60.0,
>
> I've 2 temperatures probes
>
> Can someone explain me how to add this in weewx.conf ?
>
> in section  :
>  [[sensor_map_extensions]]
> ???inTemp = temperature_1
>  ???   inHumidity = humidity_1
>  ???   outTemp = temperature_4
>   ???  outHumidity = humidity_4
>
>
> Thanks a lot  ;)
>
> Stephane
>
> --
> 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/c851119a-b274-4ecd-99a3-605d2e393946n%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/CADhm9Yd2YgOuSN%3D8E8%2Bdn78BQJYi12%3Dgaqe1uXGiWBvB%2BriOUw%40mail.gmail.com.

[weewx-user] Can we upgrade to WeeWX 5.0x WITHOUT MAJOR RISK?

[Remy Lavabre]

Good morning,

I've been seeing various problems (mainly access rights?) for some time 
with the 5.x update.

For a configuration in 4.10.2 on Pi with Bulleyes 64B, does the transition 
to 5.x present risks of malfunction with the use of a modified base skin 
(Seasons) but above all:

- A personalized driver which retrieves Awekas data from the station via 
the internet as well as various other parameters from the Pi (temperature, 
memory, SSD status etc.) but also data on external counter modules;

- An alarm generator (multialarm.py) allowing you to be notified based on 
precise weather criteria defined in advance

- the excellent alltimeSeasons skin made by Glenn Mckechnie


With experience, are there checks to be made before to avoid surprises 
afterwards...?

Thank you so much... ;-)

-- 
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/e518f4f9-6fcb-4a9f-aeba-810781fd1ef7n%40googlegroups.com.

[weewx-user] Re: New station ? : Bresser 7in1 6 days

[Remy Lavabre]

Good morning,

I have the same outdoor sensor but not the same base.
The exterior sensor works perfectly but does not seem to me to be very 
realistic in terms of wind speed. I think we can easily apply a factor x1.5 
to get closer to reality...

The minimum amount of rain needed to trigger is greater than the 6in1 
station I had previously (0.5mm instead of 0.3mm it seems to me).

The accumulators are recharged by the solar panel and have not (so far...) 
caused me any problems.

The big advantages of Bresser stations are:
1/ The price
2/ Average quality but acceptable given the price
3/ The guarantee (5 years after registration on their site). I took 
advantage of it after 3 years of operation, they changed everything for me 
with a game upgrade and taking the return transport costs at their expense. 
Very correct at Bresser from this point of view

The big drawback: the absence of a USB output unlike on my old 6in1 and the 
need to tinker with a system for data recovery. And so if there is no 
network, total and permanent loss of data!
Le dimanche 4 février 2024 à 16:24:33 UTC+1, sc.lep...@gmail.com a écrit :

> Hello  
> I want to change my  meteo (Froggit WH-6000) and I use it with interceptor 
> plugin (Wifi). 
> Several sensors are HS ( Temp Ext / rain  /)
> I am interested in another station  : Bresser
>
>
> https://www.bresser.de/fr/Temps/Centrale-meteo/Station-meteo-Wi-Fi-Previsions-6-jours-Capteur-7-en-1-solaire.html
>
> I ve read several posts and  I  dont find 
>
> Can someone help in my  choice ? 
> Stephane
>

-- 
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/f7475a38-6df8-4939-88cb-486ff07e47aan%40googlegroups.com.

[weewx-user] Zambretti forecast in StellSeries

[Remy Lavabre]

Good morning,

The SteelSeries skin leaves the possibility of displaying weather forecasts.
The gauge-data.txt.tmpl file contains the following lines:






*## if forecasting is installed, report the Zambretti forecast#if 
$varExists('forecast.zambretti')#set $fc = $forecast.label('Zambretti', 
$forecast.zambretti.code)#else#set $fc = 'Prévisions météo 
indisponibles'#end if*

*Hence my question: how should we activate these “Zambretti” weather 
forecasts?*

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/aed26d5d-cc9c-43a0-a076-626f464843a4n%40googlegroups.com.

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy Lavabre]

Hello Gary,

As promised, news! And good ones!!! :-))
My internet connection having (finally...) returned, the SteelSeasons skin 
works now perfectly. The problem actually came from this deleted 
"rxCheckPercent" field! :-(
Thank you for the troubleshooting because I would have spent a long time on 
the problem...
Thanks again Gary

Le jeudi 25 janvier 2024 à 15:25:38 UTC+1, Remy LAVABRE a écrit :

> hello gary,
> Many thanks for your help and my apologies for the late response as my 
> internet connection is currently cut...
> I would never have thought of looking for this missing field!
> I added this field in percent format and the steelseries skin no longer 
> seems to pose a problem! I say apparently because in the absence of a 
> connection for probably another week, I cannot send or retrieve data on 
> Awekas...
> As soon as the situation returns to normal, I will confirm!
> but in the absence of an error (my driver still gives me the raspberry 
> data in the packetsloop), it seems good! ;-)
>
> thank you very much once again
>
>
> Le mer. 24 janv. 2024, 12:16, gjr80  a écrit :
>
>> Your problem is that you have deleted the column rxCheckPercent from 
>> your database. I'm guessing your driver does not include the field in the 
>> packets/records it emits so when the template attempts to process 
>> rxCheckPercent it fails (rxCheckPercent cannot be found in the current 
>> archive record of the database archive table). You have a few options:
>>
>> 1. put the column back with --add-columns, I suspect this is the easiest 
>> solution
>> 2. have your driver emit the field rxCheckPercent 
>> 3. modify the template 
>>
>> I would suggest you just add the missing column back in. 
>>
>> Gary
>>
>> On Tuesday 23 January 2024 at 18:30:10 UTC+10 remy.l...@gmail.com wrote:
>>
>>> If it helps you, I'll leave you a link to my database. weewx.sdb -> 
>>> https://transfert.free.fr/FgCL7wI
>>>
>>> But once again, I don't think I have deleted any "basic" fields (inTemp, 
>>> Barometer, outTemp etc...) for weewx.
>>>
>>> The SteelSeries skin tells me it hasn't been updated in 178 days, so it 
>>> appears to be from July 29, 2023 (a timestamp >= 1690581600).
>>> And around this date, I didn't notice anything particular in my 
>>> database... :-(
>>>
>>> Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :
>>>
>>>> Hello Gary,
>>>>
>>>> I've put what you asked for below.
>>>>
>>>> The problem is systematic (this is an advantage in some way...)
>>>>
>>>> I think you are right about the problem of a field in the database... 
>>>> But which one?
>>>> SteelSeries was working perfectly BEFORE I added/deleted the data base. 
>>>> I didn't notice the problem immediately since I mainly use the Seasons 
>>>> skin. But there is a good chance that the problem is linked to the 
>>>> modification of the structure of the base.
>>>> Unfortunately, I can't find ! :-(
>>>>
>>>>
>>>> LOOP:   2024-01-22 15:09:07 CET (1705932547) 'altimeter': 'None', 
>>>> 'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5', 
>>>> 'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388', 
>>>> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '0', 
>>>> 'cpu_user': '0', 'dateTime': '1705932547', 'dewpoint': '37.94', 
>>>> 'disk_total': '20425850880', 'disk_used': '10535763968', 
>>>> 'electricityLinky': '0', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
>>>> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': 
>>>> '50.1080004', 'extraTemp2': '52.7', 'extraTemp3': 'None', 
>>>> 'extraTemp4': '66.506', 'extraTemp6': 'None', 'heatindex': '43.228', 
>>>> 'humidex': '45.5', 'inDewpoint': '51.726318793965625', 'inHumidity': '54', 
>>>> 'inTemp': '69.080001', 'inTempDaikin': '68.0', 'kWhPAC': '0.0', 
>>>> 'maxSolarRad': '255.46907895483838', 'mem_total': '8286392320', 
>>>> 'mem_used': 
>>>> '1683726336', 'outHumidity': '74', 'outTemp': '45.5', 'outTempDaikin': 
>>>> '44.6', 'pressure': 'None', 'radiation': '48', 'rain': '0.0', 'rainRate': 
>>>> '0.0', 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 
>>>> 'waterSensus': '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.684', 
>>>> 'windchill': '45.5', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 
>&

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

Sorry Tom, I didn't notice how quick your insight was! ;-)

However *(if I may!*), I think that for a better understanding, there would 
be (*perhaps?*) another correction to make here: 
https://github.com/weewx/weewx/blob/master/ src/weewx/wxxtypes.py#L586

Indeed, you indicate in comments a "rain" field and a "dayRain" field. I 
quote *"for calculating observation type 'rain' from a daily total, such as 
'dayRain'"* -> OK, thank's for the ifo

But below, dayRain "transforms" into "totalRain":

 [StdWXCalculate]
 [[Calculations]]
 ...
 rain = prefer_hardware
 ...
 [[Delta]]
 [[[rain]]]
 input = totalRain

It's certainly not a big problem, but for a neophyte like me, it raises 
unnecessary questions when reading the manual... ;-)

Finally, I would like to take this opportunity to ask you if it would not 
be possible to provide a new class for a counter that never resets to zero 
(DELTA2 for example), which would simply calculate the delta between two 
packetsloops (delta2 = measurement2 - measurement1) and if the result is 
negative, then delta2 = measurement2 (obviously the counter has been reset).
That would be very cool... ;-)
A (good) idea for development... no ?
Thank you Tom

Le dimanche 28 janvier 2024 à 18:40:37 UTC+1, Tom Keffer a écrit :

> Oh, it was the first thing I did after realizing my omission! Commit 
> 9455fa1 
> <https://github.com/weewx/weewx/commit/9455fa17169463c3174f3517bdc652c4f2dd5036>
> .
>
> On Sun, Jan 28, 2024 at 7:30 AM Remy Lavabre  wrote:
>
>> thanks Tom,
>>
>> I had thought about putting rain = prefer_software but as this type of 
>> rain configuration is not documented in the Weewx documentation (or at 
>> least I didn't find it!) I didn't take the initiative. .. stupid I am ! :-(
>>
>> little suggestion Tom, perhaps it would be good to document this point in 
>> the [[Delta]] rain class? 
>> Well, not everyone is ignorant like me!! :-))
>> Many thanks to you for your help Tom
>>
>> Le dimanche 28 janvier 2024 à 00:21:43 UTC+1, Tom Keffer a écrit :
>>
>>> My apologies. I forgot one important detail. The "[Delta]" section tells 
>>> WeeWX how to calculate rain, but you also have to include "rain" under 
>>> [StdWXCalculations] / [[Calculations]] in order to get it to do the actual 
>>> calculation. It looks like
>>>
>>> [StdWXCalculate]
>>> [[Calculations]]
>>> ...
>>> rain = prefer_hardware
>>>
>>> ...
>>> [[Delta]]
>>> [[[rain]]]
>>> input = dayRain
>>>
>>> On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre  
>>> wrote:
>>>
>>>> Hello Tom,
>>>>
>>>> I followed your instructions:
>>>>
>>>> 1/“rain” field present in the database
>>>> 2/ “dayRain” field not present in the database
>>>> 3/ My driver returns “dayRain” values and not “rain” values in the 
>>>> packetsloop
>>>> 4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under 
>>>> [StdWXCalculate]).
>>>>
>>>> I did some tests : my driver returns 0.0 for dayRain but unfortunately 
>>>> the "rain" field in my database always remains NULL, even after several 
>>>> recordings in weewx.conf.
>>>> Shouldn't "rain" field go to 0.0?
>>>>
>>>> THANKS
>>>>
>>>> Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :
>>>>
>>>>> If an observation type never gets reset to zero, you have two choices.
>>>>> 1. Save the value. If you want to know daily use, take the difference 
>>>>> of the value.
>>>>> 2. Save the difference. That is, the change in the value over an 
>>>>> archive period. If you want to know daily use, you would sum all the 
>>>>> small 
>>>>> deltas. This is like rain
>>>>>
>>>>> See the discussion *Accumulated vs delta energy 
>>>>> <https://github.com/tkeffer/weewx-brultech?tab=readme-ov-file#accumulated-vs-delta-energy>*
>>>>>  in 
>>>>> the README of the Brultech driver for the pros and cons of the two 
>>>>> approaches.
>>>>>
>>>>> It is not necessary to save "dayRain". WeeWX mostly uses "rain". 
>>>>> Besides, as you note, it can always be calculated.
>>>>>
>>>>>
>>>>&g

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

thanks Tom,

I had thought about putting rain = prefer_software but as this type of rain 
configuration is not documented in the Weewx documentation (or at least I 
didn't find it!) I didn't take the initiative. .. stupid I am ! :-(

little suggestion Tom, perhaps it would be good to document this point in 
the [[Delta]] rain class? 
Well, not everyone is ignorant like me!! :-))
Many thanks to you for your help Tom

Le dimanche 28 janvier 2024 à 00:21:43 UTC+1, Tom Keffer a écrit :

> My apologies. I forgot one important detail. The "[Delta]" section tells 
> WeeWX how to calculate rain, but you also have to include "rain" under 
> [StdWXCalculations] / [[Calculations]] in order to get it to do the actual 
> calculation. It looks like
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> rain = prefer_hardware
>
> ...
> [[Delta]]
> [[[rain]]]
>     input = dayRain
>
> On Sat, Jan 27, 2024 at 9:17 AM Remy Lavabre  wrote:
>
>> Hello Tom,
>>
>> I followed your instructions:
>>
>> 1/“rain” field present in the database
>> 2/ “dayRain” field not present in the database
>> 3/ My driver returns “dayRain” values and not “rain” values in the 
>> packetsloop
>> 4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under 
>> [StdWXCalculate]).
>>
>> I did some tests : my driver returns 0.0 for dayRain but unfortunately 
>> the "rain" field in my database always remains NULL, even after several 
>> recordings in weewx.conf.
>> Shouldn't "rain" field go to 0.0?
>>
>> THANKS
>>
>> Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :
>>
>>> If an observation type never gets reset to zero, you have two choices.
>>> 1. Save the value. If you want to know daily use, take the difference of 
>>> the value.
>>> 2. Save the difference. That is, the change in the value over an archive 
>>> period. If you want to know daily use, you would sum all the small deltas. 
>>> This is like rain
>>>
>>> See the discussion *Accumulated vs delta energy 
>>> <https://github.com/tkeffer/weewx-brultech?tab=readme-ov-file#accumulated-vs-delta-energy>*
>>>  in 
>>> the README of the Brultech driver for the pros and cons of the two 
>>> approaches.
>>>
>>> It is not necessary to save "dayRain". WeeWX mostly uses "rain". 
>>> Besides, as you note, it can always be calculated.
>>>
>>>
>>>
>>> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre  
>>> wrote:
>>>
>>>> And one more question
>>>> Is it absolutely necessary to create a "dayRain" field in addition to 
>>>> the "rain" field in the weewx.sdb database?
>>>> If the database only contains the [rain] field but the Weewx driver 
>>>> returns a "dayRain" field (cumulative rain over 24 hours since midnight) 
>>>> with a real value in each packetloop, the class [[Delta]] [[ [rain]]] 
>>>> input 
>>>> = dayRain will it work??
>>>> (the accumulation of rain since midnight is useless to me in a database 
>>>> field since it is easily calculated)
>>>> Sorry for all the questions...and thanks again! ;-)
>>>>
>>>> Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
>>>>
>>>>> Hello Tom and thank you for your response.
>>>>>
>>>>>  [StdWXCalculate]
>>>>>  [[Calculations]]
>>>>>  ...
>>>>>  [[Delta]]
>>>>>  [[[rain]]]
>>>>>  input = dayRain
>>>>>
>>>>> This will calculate the rain difference between two records in weewx 
>>>>> sql based on the principle that the counter is reset to zero at midnight 
>>>>> -> 
>>>>> PERFECT FOR THE RAIN 24H !
>>>>>
>>>>> Small additional question: if we wish to constantly calculate the 
>>>>> difference between two records values of a meter which *never* resets 
>>>>> to zero (such as an electricity or water meter), how should we proceed?
>>>>>
>>>>> THANKS
>>>>>
>>>>> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>>>>>
>>>>>> Unfortunately (for you), WeeWX mostly uses observation type "rain", 
>>>>>> the amount of rain that fell s

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

Hello Tom,

I followed your instructions:

1/“rain” field present in the database
2/ “dayRain” field not present in the database
3/ My driver returns “dayRain” values and not “rain” values in the 
packetsloop
4/ [[Delta]] [[ [rain]]] input = dayRain added in weewx.conf (under 
[StdWXCalculate]).

I did some tests : my driver returns 0.0 for dayRain but unfortunately the 
"rain" field in my database always remains NULL, even after several 
recordings in weewx.conf.
Shouldn't "rain" field go to 0.0?

THANKS

Le vendredi 26 janvier 2024 à 22:48:03 UTC+1, Tom Keffer a écrit :

> If an observation type never gets reset to zero, you have two choices.
> 1. Save the value. If you want to know daily use, take the difference of 
> the value.
> 2. Save the difference. That is, the change in the value over an archive 
> period. If you want to know daily use, you would sum all the small deltas. 
> This is like rain
>
> See the discussion *Accumulated vs delta energy 
> <https://github.com/tkeffer/weewx-brultech?tab=readme-ov-file#accumulated-vs-delta-energy>*
>  in 
> the README of the Brultech driver for the pros and cons of the two 
> approaches.
>
> It is not necessary to save "dayRain". WeeWX mostly uses "rain". Besides, 
> as you note, it can always be calculated.
>
>
>
> On Fri, Jan 26, 2024 at 7:06 AM Remy Lavabre  wrote:
>
>> And one more question
>> Is it absolutely necessary to create a "dayRain" field in addition to the 
>> "rain" field in the weewx.sdb database?
>> If the database only contains the [rain] field but the Weewx driver 
>> returns a "dayRain" field (cumulative rain over 24 hours since midnight) 
>> with a real value in each packetloop, the class [[Delta]] [[ [rain]]] input 
>> = dayRain will it work??
>> (the accumulation of rain since midnight is useless to me in a database 
>> field since it is easily calculated)
>> Sorry for all the questions...and thanks again! ;-)
>>
>> Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :
>>
>>> Hello Tom and thank you for your response.
>>>
>>>  [StdWXCalculate]
>>>  [[Calculations]]
>>>  ...
>>>  [[Delta]]
>>>  [[[rain]]]
>>>  input = dayRain
>>>
>>> This will calculate the rain difference between two records in weewx sql 
>>> based on the principle that the counter is reset to zero at midnight -> 
>>> PERFECT FOR THE RAIN 24H !
>>>
>>> Small additional question: if we wish to constantly calculate the 
>>> difference between two records values of a meter which *never* resets 
>>> to zero (such as an electricity or water meter), how should we proceed?
>>>
>>> THANKS
>>>
>>> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>>>
>>>> Unfortunately (for you), WeeWX mostly uses observation type "rain", the 
>>>> amount of rain that fell since the last loop packet (what you are calling 
>>>> "instantaneous rain").
>>>>
>>>> You should assign the rain since midnight to type "dayRain".
>>>>
>>>> Then calculate "rain" as the difference between successive 
>>>> "dayRain" values. While this is a pretty simple calculation, there is an 
>>>> xtype that can do it for you.  See class Delta in weewx.wxxtypes 
>>>> <https://github.com/weewx/weewx/blob/master/src/weewx/wxxtypes.py#L586>. 
>>>> To use it, add this to weewx.conf:
>>>>
>>>> [StdWXCalculate]
>>>> [[Calculations]]
>>>> ...
>>>> [[Delta]]
>>>> [[[rain]]]
>>>> input = dayRain
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre  
>>>> wrote:
>>>>
>>>>> Good morning,
>>>>>
>>>>> I created a [driver] for weewx to retrieve data from the Awekas API 
>>>>> (my Bresser weather station does not have a USB port).
>>>>>
>>>>> This works but regarding the rain, it is not the instantaneous rain 
>>>>> (from a packetloop) that we recover but the rain over 24 hours since 
>>>>> midnight.
>>>>> Is there a "simple" way to tell WeeWX that the packetsloop rain data 
>>>>> corresponds to the cumulative rain since midnight and not the rain that 
>>

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

And one more question
Is it absolutely necessary to create a "dayRain" field in addition to the 
"rain" field in the weewx.sdb database?
If the database only contains the [rain] field but the Weewx driver returns 
a "dayRain" field (cumulative rain over 24 hours since midnight) with a 
real value in each packetloop, the class [[Delta]] [[ [rain]]] input = 
dayRain will it work??
(the accumulation of rain since midnight is useless to me in a database 
field since it is easily calculated)
Sorry for all the questions...and thanks again! ;-)

Le vendredi 26 janvier 2024 à 15:46:04 UTC+1, Remy Lavabre a écrit :

> Hello Tom and thank you for your response.
>
>  [StdWXCalculate]
>  [[Calculations]]
>  ...
>  [[Delta]]
>  [[[rain]]]
>  input = dayRain
>
> This will calculate the rain difference between two records in weewx sql 
> based on the principle that the counter is reset to zero at midnight -> 
> PERFECT FOR THE RAIN 24H !
>
> Small additional question: if we wish to constantly calculate the 
> difference between two records values of a meter which *never* resets to 
> zero (such as an electricity or water meter), how should we proceed?
>
> THANKS
>
> Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :
>
>> Unfortunately (for you), WeeWX mostly uses observation type "rain", the 
>> amount of rain that fell since the last loop packet (what you are calling 
>> "instantaneous rain").
>>
>> You should assign the rain since midnight to type "dayRain".
>>
>> Then calculate "rain" as the difference between successive 
>> "dayRain" values. While this is a pretty simple calculation, there is an 
>> xtype that can do it for you.  See class Delta in weewx.wxxtypes 
>> <https://github.com/weewx/weewx/blob/master/src/weewx/wxxtypes.py#L586>. 
>> To use it, add this to weewx.conf:
>>
>> [StdWXCalculate]
>> [[Calculations]]
>> ...
>> [[Delta]]
>> [[[rain]]]
>> input = dayRain
>>
>>
>>
>>
>> On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre  
>> wrote:
>>
>>> Good morning,
>>>
>>> I created a [driver] for weewx to retrieve data from the Awekas API (my 
>>> Bresser weather station does not have a USB port).
>>>
>>> This works but regarding the rain, it is not the instantaneous rain 
>>> (from a packetloop) that we recover but the rain over 24 hours since 
>>> midnight.
>>> Is there a "simple" way to tell WeeWX that the packetsloop rain data 
>>> corresponds to the cumulative rain since midnight and not the rain that 
>>> fell during the data retrieval interval (the time gap between two 
>>> packetsloops) ?
>>>
>>> Thank you so much...
>>>
>>> -- 
>>> 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/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com?utm_medium=email_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/796eb84f-ad09-41bf-ad90-202ad6f05773n%40googlegroups.com.

Re: [weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

Hello Tom and thank you for your response.

 [StdWXCalculate]
 [[Calculations]]
 ...
 [[Delta]]
 [[[rain]]]
 input = dayRain

This will calculate the rain difference between two records in weewx sql 
based on the principle that the counter is reset to zero at midnight -> 
PERFECT FOR THE RAIN 24H !

Small additional question: if we wish to constantly calculate the 
difference between two records values of a meter which *never* resets to 
zero (such as an electricity or water meter), how should we proceed?

THANKS

Le jeudi 18 janvier 2024 à 14:05:10 UTC+1, Tom Keffer a écrit :

> Unfortunately (for you), WeeWX mostly uses observation type "rain", the 
> amount of rain that fell since the last loop packet (what you are calling 
> "instantaneous rain").
>
> You should assign the rain since midnight to type "dayRain".
>
> Then calculate "rain" as the difference between successive 
> "dayRain" values. While this is a pretty simple calculation, there is an 
> xtype that can do it for you.  See class Delta in weewx.wxxtypes 
> <https://github.com/weewx/weewx/blob/master/src/weewx/wxxtypes.py#L586>. 
> To use it, add this to weewx.conf:
>
> [StdWXCalculate]
> [[Calculations]]
> ...
> [[Delta]]
>     [[[rain]]]
> input = dayRain
>
>
>
>
> On Wed, Jan 17, 2024 at 11:47 PM Remy Lavabre  wrote:
>
>> Good morning,
>>
>> I created a [driver] for weewx to retrieve data from the Awekas API (my 
>> Bresser weather station does not have a USB port).
>>
>> This works but regarding the rain, it is not the instantaneous rain (from 
>> a packetloop) that we recover but the rain over 24 hours since midnight.
>> Is there a "simple" way to tell WeeWX that the packetsloop rain data 
>> corresponds to the cumulative rain since midnight and not the rain that 
>> fell during the data retrieval interval (the time gap between two 
>> packetsloops) ?
>>
>> Thank you so much...
>>
>> -- 
>> 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/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com?utm_medium=email_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/502b5332-d7a0-4585-ad1a-98bc8167ab7cn%40googlegroups.com.

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy LAVABRE]

hello gary,
Many thanks for your help and my apologies for the late response as my
internet connection is currently cut...
I would never have thought of looking for this missing field!
I added this field in percent format and the steelseries skin no longer
seems to pose a problem! I say apparently because in the absence of a
connection for probably another week, I cannot send or retrieve data on
Awekas...
As soon as the situation returns to normal, I will confirm!
but in the absence of an error (my driver still gives me the raspberry data
in the packetsloop), it seems good! ;-)

thank you very much once again


Le mer. 24 janv. 2024, 12:16, gjr80  a écrit :

> Your problem is that you have deleted the column rxCheckPercent from your
> database. I'm guessing your driver does not include the field in the
> packets/records it emits so when the template attempts to process
> rxCheckPercent it fails (rxCheckPercent cannot be found in the current
> archive record of the database archive table). You have a few options:
>
> 1. put the column back with --add-columns, I suspect this is the easiest
> solution
> 2. have your driver emit the field rxCheckPercent
> 3. modify the template
>
> I would suggest you just add the missing column back in.
>
> Gary
>
> On Tuesday 23 January 2024 at 18:30:10 UTC+10 remy.l...@gmail.com wrote:
>
>> If it helps you, I'll leave you a link to my database. weewx.sdb ->
>> https://transfert.free.fr/FgCL7wI
>>
>> But once again, I don't think I have deleted any "basic" fields (inTemp,
>> Barometer, outTemp etc...) for weewx.
>>
>> The SteelSeries skin tells me it hasn't been updated in 178 days, so it
>> appears to be from July 29, 2023 (a timestamp >= 1690581600).
>> And around this date, I didn't notice anything particular in my
>> database... :-(
>>
>> Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :
>>
>>> Hello Gary,
>>>
>>> I've put what you asked for below.
>>>
>>> The problem is systematic (this is an advantage in some way...)
>>>
>>> I think you are right about the problem of a field in the database...
>>> But which one?
>>> SteelSeries was working perfectly BEFORE I added/deleted the data base.
>>> I didn't notice the problem immediately since I mainly use the Seasons
>>> skin. But there is a good chance that the problem is linked to the
>>> modification of the structure of the base.
>>> Unfortunately, I can't find ! :-(
>>>
>>>
>>> LOOP:   2024-01-22 15:09:07 CET (1705932547) 'altimeter': 'None',
>>> 'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5',
>>> 'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388',
>>> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '0',
>>> 'cpu_user': '0', 'dateTime': '1705932547', 'dewpoint': '37.94',
>>> 'disk_total': '20425850880', 'disk_used': '10535763968',
>>> 'electricityLinky': '0', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2':
>>> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1':
>>> '50.1080004', 'extraTemp2': '52.7', 'extraTemp3': 'None',
>>> 'extraTemp4': '66.506', 'extraTemp6': 'None', 'heatindex': '43.228',
>>> 'humidex': '45.5', 'inDewpoint': '51.726318793965625', 'inHumidity': '54',
>>> 'inTemp': '69.080001', 'inTempDaikin': '68.0', 'kWhPAC': '0.0',
>>> 'maxSolarRad': '255.46907895483838', 'mem_total': '8286392320', 'mem_used':
>>> '1683726336', 'outHumidity': '74', 'outTemp': '45.5', 'outTempDaikin':
>>> '44.6', 'pressure': 'None', 'radiation': '48', 'rain': '0.0', 'rainRate':
>>> '0.0', 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0',
>>> 'waterSensus': '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.684',
>>> 'windchill': '45.5', 'windDir': 'None', 'windGust': '0.0', 'windGustDir':
>>> 'None', 'windrun': 'None', 'windSpeed': '0.0'
>>>
>>> LOOP:   2024-01-22 15:10:07 CET (1705932607) 'altimeter': 'None',
>>> 'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '42.0',
>>> 'charge5': '27.5', 'charge15': '14.0', 'cloudbase': '3342.900026403866',
>>> 'cpu_io': '1', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '27',
>>> 'cpu_user': '28', 'dateTime': '1705932607', 'dewpoint': '38.3',
>>> 'disk_total': '20425850880', 'disk_used': '10592305152',
>>> 'electricityLinky': '12', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2':
>>> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0',
>>> 'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy Lavabre]

If it helps you, I'll leave you a link to my database. weewx.sdb 
-> https://transfert.free.fr/FgCL7wI

But once again, I don't think I have deleted any "basic" fields (inTemp, 
Barometer, outTemp etc...) for weewx.

The SteelSeries skin tells me it hasn't been updated in 178 days, so it 
appears to be from July 29, 2023 (a timestamp >= 1690581600).
And around this date, I didn't notice anything particular in my database... 
:-(

Le lundi 22 janvier 2024 à 15:23:25 UTC+1, Remy Lavabre a écrit :

> Hello Gary,
>
> I've put what you asked for below.
>
> The problem is systematic (this is an advantage in some way...)
>
> I think you are right about the problem of a field in the database... But 
> which one?
> SteelSeries was working perfectly BEFORE I added/deleted the data base. I 
> didn't notice the problem immediately since I mainly use the Seasons skin. 
> But there is a good chance that the problem is linked to the modification 
> of the structure of the base.
> Unfortunately, I can't find ! :-(
>
>
> LOOP:   2024-01-22 15:09:07 CET (1705932547) 'altimeter': 'None', 
> 'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5', 
> 'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388', 
> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '0', 
> 'cpu_user': '0', 'dateTime': '1705932547', 'dewpoint': '37.94', 
> 'disk_total': '20425850880', 'disk_used': '10535763968', 
> 'electricityLinky': '0', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': 
> '50.1080004', 'extraTemp2': '52.7', 'extraTemp3': 'None', 
> 'extraTemp4': '66.506', 'extraTemp6': 'None', 'heatindex': '43.228', 
> 'humidex': '45.5', 'inDewpoint': '51.726318793965625', 'inHumidity': '54', 
> 'inTemp': '69.080001', 'inTempDaikin': '68.0', 'kWhPAC': '0.0', 
> 'maxSolarRad': '255.46907895483838', 'mem_total': '8286392320', 'mem_used': 
> '1683726336', 'outHumidity': '74', 'outTemp': '45.5', 'outTempDaikin': 
> '44.6', 'pressure': 'None', 'radiation': '48', 'rain': '0.0', 'rainRate': 
> '0.0', 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 
> 'waterSensus': '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.684', 
> 'windchill': '45.5', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 
> 'None', 'windrun': 'None', 'windSpeed': '0.0'
>
> LOOP:   2024-01-22 15:10:07 CET (1705932607) 'altimeter': 'None', 
> 'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '42.0', 
> 'charge5': '27.5', 'charge15': '14.0', 'cloudbase': '3342.900026403866', 
> 'cpu_io': '1', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '27', 
> 'cpu_user': '28', 'dateTime': '1705932607', 'dewpoint': '38.3', 
> 'disk_total': '20425850880', 'disk_used': '10592305152', 
> 'electricityLinky': '12', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0', 
> 'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4': '66.506', 
> 'extraTemp6': 'None', 'heatindex': '43.4730006', 'humidex': 
> '45.68', 'inDewpoint': '51.55950246316422', 'inHumidity': '54', 'inTemp': 
> '68.9', 'inTempDaikin': '68.0', 'kWhPAC': '0.827', 'maxSolarRad': 
> '253.53718615434911', 'mem_total': '8286392320', 'mem_used': '1643642880', 
> 'outHumidity': '75', 'outTemp': '45.68', 'outTempDaikin': '44.6', 
> 'pressure': 'None', 'radiation': '50', 'rain': '0.0', 'rainRate': '0.0', 
> 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 'waterSensus': 
> '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.99', 'windchill': 
> '45.68', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 'None', 
> 'windrun': 'None', 'windSpeed': '0.0'
>
> LOOP:   2024-01-22 15:11:06 CET (1705932666) 'altimeter': 'None', 
> 'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '39.5', 
> 'charge5': '30.0', 'charge15': '15.5', 'cloudbase': '3342.900026403866', 
> 'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '2', 
> 'cpu_user': '4', 'dateTime': '1705932666', 'dewpoint': '38.3', 
> 'disk_total': '20425850880', 'disk_used': '10592309248', 
> 'electricityLinky': '13', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
> '92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0', 
> 'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4': '66.506', 
> 'extraTemp6': 'None', 'heatindex': '43.4730006', 'humidex': 
> '45.68', 'inDewpoint': '51.55950246316422', 'inHumidity': '54', 'inTemp': 
> '68.9', 'inTempDaikin': '68.0', 'kWhPAC': '0.807', 'maxSolarRad': 
> '251.62699567181605', 'mem_total': '8286392320', 'mem_used': '1660600320', 
> 'outHumidity': '75', 'outTemp': '45.68', 'outTempDaikin': '44.6', 
> 'pressure': 'None', 'r

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy Lavabre]

Hello Gary,

I've put what you asked for below.

The problem is systematic (this is an advantage in some way...)

I think you are right about the problem of a field in the database... But 
which one?
SteelSeries was working perfectly BEFORE I added/deleted the data base. I 
didn't notice the problem immediately since I mainly use the Seasons skin. 
But there is a good chance that the problem is linked to the modification 
of the structure of the base.
Unfortunately, I can't find ! :-(


LOOP:   2024-01-22 15:09:07 CET (1705932547) 'altimeter': 'None', 
'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5', 
'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388', 
'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '0', 
'cpu_user': '0', 'dateTime': '1705932547', 'dewpoint': '37.94', 
'disk_total': '20425850880', 'disk_used': '10535763968', 
'electricityLinky': '0', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
'92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': 
'50.1080004', 'extraTemp2': '52.7', 'extraTemp3': 'None', 
'extraTemp4': '66.506', 'extraTemp6': 'None', 'heatindex': '43.228', 
'humidex': '45.5', 'inDewpoint': '51.726318793965625', 'inHumidity': '54', 
'inTemp': '69.080001', 'inTempDaikin': '68.0', 'kWhPAC': '0.0', 
'maxSolarRad': '255.46907895483838', 'mem_total': '8286392320', 'mem_used': 
'1683726336', 'outHumidity': '74', 'outTemp': '45.5', 'outTempDaikin': 
'44.6', 'pressure': 'None', 'radiation': '48', 'rain': '0.0', 'rainRate': 
'0.0', 'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 
'waterSensus': '0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.684', 
'windchill': '45.5', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 
'None', 'windrun': 'None', 'windSpeed': '0.0'

LOOP:   2024-01-22 15:10:07 CET (1705932607) 'altimeter': 'None', 
'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '42.0', 
'charge5': '27.5', 'charge15': '14.0', 'cloudbase': '3342.900026403866', 
'cpu_io': '1', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '27', 
'cpu_user': '28', 'dateTime': '1705932607', 'dewpoint': '38.3', 
'disk_total': '20425850880', 'disk_used': '10592305152', 
'electricityLinky': '12', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
'92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0', 
'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4': '66.506', 
'extraTemp6': 'None', 'heatindex': '43.4730006', 'humidex': 
'45.68', 'inDewpoint': '51.55950246316422', 'inHumidity': '54', 'inTemp': 
'68.9', 'inTempDaikin': '68.0', 'kWhPAC': '0.827', 'maxSolarRad': 
'253.53718615434911', 'mem_total': '8286392320', 'mem_used': '1643642880', 
'outHumidity': '75', 'outTemp': '45.68', 'outTempDaikin': '44.6', 
'pressure': 'None', 'radiation': '50', 'rain': '0.0', 'rainRate': '0.0', 
'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 'waterSensus': 
'0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.99', 'windchill': 
'45.68', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 'None', 
'windrun': 'None', 'windSpeed': '0.0'

LOOP:   2024-01-22 15:11:06 CET (1705932666) 'altimeter': 'None', 
'appTemp': '41.99', 'barometer': '30.359780148749998', 'charge1': '39.5', 
'charge5': '30.0', 'charge15': '15.5', 'cloudbase': '3342.900026403866', 
'cpu_io': '0', 'cpu_irq': '0', 'cpu_softirq': '0', 'cpu_system': '2', 
'cpu_user': '4', 'dateTime': '1705932666', 'dewpoint': '38.3', 
'disk_total': '20425850880', 'disk_used': '10592309248', 
'electricityLinky': '13', 'ET': 'None', 'extraHumid1': '66', 'extraHumid2': 
'92', 'extraHumid3': 'None', 'extraHumid4': '61', 'extraTemp1': '50.0', 
'extraTemp2': '52.7', 'extraTemp3': 'None', 'extraTemp4': '66.506', 
'extraTemp6': 'None', 'heatindex': '43.4730006', 'humidex': 
'45.68', 'inDewpoint': '51.55950246316422', 'inHumidity': '54', 'inTemp': 
'68.9', 'inTempDaikin': '68.0', 'kWhPAC': '0.807', 'maxSolarRad': 
'251.62699567181605', 'mem_total': '8286392320', 'mem_used': '1660600320', 
'outHumidity': '75', 'outTemp': '45.68', 'outTempDaikin': '44.6', 
'pressure': 'None', 'radiation': '56', 'rain': '0.0', 'rainRate': '0.0', 
'thermostatDaikin': '68.0', 'usUnits': '1', 'UV': '0', 'waterSensus': 
'0.0', 'waterTempDaikin': '80.6', 'wetbulbTemp': '41.99', 'windchill': 
'45.68', 'windDir': 'None', 'windGust': '0.0', 'windGustDir': 'None', 
'windrun': 'None', 'windSpeed': '0.0'


*REC:*2024-01-22 15:10:00 CET (1705932600) 'altimeter': 'None', 
'appTemp': '41.684', 'barometer': '30.359780148749998', 'charge1': '25.5', 
'charge5': '19.5', 'charge15': '10.5', 'cloudbase': '3419.1984298366388', 
'cpu_io': '0.0', 'cpu_irq': '0.0', 'cpu_softirq': '0.0', 'cpu_system': 
'0.0', 'cpu_user': '0.0', 'dateTime': '1705932600', 'dewpoint': '37.94', 
'disk_total': '20425850880.0', 'disk_used': '10535763968.0', 
'electricityLinky': '0.0', 'ET': 'None', 'extraHumid1': '66.0', 
'extraHumid2': '92.0', 'extraHumid3': 'None', 'extraHumid4': '61.0', 

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy Lavabre]

Hello Gary and thank you for your response.

I have put all the fields in my database below :

[image: WX1.png]

[image: WX2.png]

[image: WX3.png]

[image: WX4.png]

Indeed the error perhaps comes from this side because I deleted fields 
which were useless to me and added others...*However I do not think I 
deleted "basic" fields such as those which are used in the skin...?*

As for the WeeWX driver, this is also a driver that I created myself since 
it directly retrieves the data from AWEKAS after my Bresser 7in1 weather 
station sent it to their site (no USB output unfortunately) .
But I don't think this driver is to blame since all the data entered into 
the database is consistent!
For information: -> https://meteomillau.go.yo.fr/index.html

Concerning the configuration of Weewx, nothing more classic it seems to 
me...:

 [[SteelSeries]]
 skin = ss
 enable = False
 HTML_ROOT = /var/www/html/weewx/ss
 [[[Units]]]
 Groups
 group_altitude = meter
 group_pressure = hPa
 group_rain = mm
 group_rainRate = mm_per_hour
 group_speed = km_per_hour
 group_temperature = degree_C
 StringFormats
 degree_C = %.1f
 degree_F = %.1f
 degree_compass = %.0f
 foot = %.0f
 hPa = %.1f
 inHg = %.3f
 inch = %.2f
 inch_per_hour = %.2f
 km = %.1f
 km_per_hour = %.0f
 knot = %.0f
 mbar = %.1f
 meter = %.0f
 meter_per_second = %.1f
 mile = %.1f
 mile_per_hour = %.0f
 mm = %.1f
 mmHg = %.1f
 mm_per_hour = %.1f
 percent = %.0f
 uv_index = %.1f
 watt_per_meter_squared = %.0f

Le dimanche 21 janvier 2024 à 05:52:36 UTC+1, gjr80 a écrit :

> The error message is very non-specific (as Cheetah errors often are), 
> though the error is likely caused by a required field being None or 
> non-existent. When asking for log extract I was not looking for errors in 
> the log, but rather looking for details of your setup including station 
> type, driver and WeeWX configuration that would hopefully give a clue as to 
> the field causing the problem. Without any further information there is 
> little else I can add.
>
> Gary
> On Saturday 20 January 2024 at 20:30:04 UTC+10 remy.l...@gmail.com wrote:
>
>> Thank-you...
>> Sorry but in the syslog, there is only that...
>> And systematically same error at each packetsloop !
>> if the option is disabled in weewx.conf obviously no problem. :-(
>>
>> Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm 
>> set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
>> Jan 16 13:56:19 localhost wee_reports[62658] INFO user.healthchecks: 
>> healthchecks: Using url 
>> https://hc-ping.com/---Spw/weewx-record
>> Jan 16 13:56:20 localhost wee_reports[62658] INFO user.historygenerator: 
>> historygenerator.py: Generated 6 tables in 0.42 seconds
>> Jan 16 13:56:32 localhost wee_reports[62658] INFO weewx.cheetahgenerator: 
>> Generated 13 files for report SeasonsReport2 in 12.56 seconds
>> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.imagegenerator: 
>> Generated 28 images for report SeasonsReport2 in 2.95 seconds
>> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine: 
>> Copied 5 files to /var/www/html/weewx
>> Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine: 
>> Copied 6 files to /var/www/html/weewx/ss
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator: Evaluation of template 
>> /etc/weewx/skins/ss/gauge-data.txt.tmpl failed with exception '> 'TypeError'>'
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator:  Ignoring template 
>> /etc/weewx/skins/ss/gauge-data.txt.tmpl
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator:  Reason: 'UnknownType' object is not 
>> subscriptable
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator:   unicode_string = 
>> compiled_template.respond()
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator: File 
>> "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
>> Jan 16 13:56:36 localhost wee_reports[62658] ERROR 
>> weewx.cheetahgenerator: File 
>> 

Re: [weewx-user] Re: Error with weewx-SteelSeries skin

[Remy LAVABRE]

Thank-you...
Sorry but in the syslog, there is only that...
And systematically same error at each packetsloop !
if the option is disabled in weewx.conf obviously no problem. :-(

Jan 16 13:56:19 localhost wee_reports[62658] INFO user.alarm_multi: Alarm
set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
Jan 16 13:56:19 localhost wee_reports[62658] INFO user.healthchecks:
healthchecks: Using url
https://hc-ping.com/---Spw/weewx-record
Jan 16 13:56:20 localhost wee_reports[62658] INFO user.historygenerator:
historygenerator.py: Generated 6 tables in 0.42 seconds
Jan 16 13:56:32 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 13 files for report SeasonsReport2 in 12.56 seconds
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.imagegenerator:
Generated 28 images for report SeasonsReport2 in 2.95 seconds
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 5 files to /var/www/html/weewx
Jan 16 13:56:35 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 6 files to /var/www/html/weewx/ss
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
Evaluation of template /etc/weewx/skins/ss/gauge-data.txt.tmpl failed with
exception ''
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
 Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
 Reason: 'UnknownType' object is not subscriptable
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  Traceback (most recent call last):
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in
generate
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  unicode_string = compiled_template.respond()
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in
respond
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line
1446, in getVar
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  return valueFromSearchList(
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
File "/usr/share/weewx/weewx/units.py", line 1094, in raw
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  return self.value_t[0]
Jan 16 13:56:36 localhost wee_reports[62658] ERROR weewx.cheetahgenerator:
  TypeError: 'UnknownType' object is not subscriptable
Jan 16 13:56:36 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 1 files for report SteelSeries in 0.76 seconds
Jan 16 13:56:37 localhost wee_reports[62658] INFO weewx.imagegenerator:
Generated 11 images for report SteelSeries in 0.91 seconds
Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.cheetahgenerator:
Generated 2 files for report wxobs in 3.66 seconds
Jan 16 13:56:40 localhost wee_reports[62658] INFO weewx.reportengine:
Copied 6 files to /var/www/html/weewx/wxobs
Jan 16 13:56:54 localhost wee_reports[62658] INFO weewx.reportengine:
ftpgenerator: Ftp'd 54 files in 13.22 seconds

*Rémy LAVABRE*


Le sam. 20 janv. 2024 à 10:51, gjr80  a écrit :

> Impossible to say with such a small log extract. Please refer to the
> section How to get a good, useful log
> 
> on the Help! Posting to weewx user wiki page
> 
> .
>
> Gary
> On Saturday 20 January 2024 at 19:40:47 UTC+10 remy.l...@gmail.com wrote:
>
>> -> https://github.com/gjr80/weewx-steelseries
>> Good morning,
>>
>> I don't understand the reason and why of the error that occurs with my
>> version 4.10.2 of weewx and the 'SteelSeries' Skin.
>>
>> Can anyone help me and tell me what's going on?
>> THANKS
>>
>>
>>
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>> Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>> Reason: 'UnknownType' object is not subscriptable
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>  Traceback (most recent call last):
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>  unicode_string = compiled_template.respond()
>> Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator: 
>>File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
>> Jan 20 10:31:21 localhost 

[weewx-user] Error with weewx-SteelSeries skin

[Remy Lavabre]

-> https://github.com/gjr80/weewx-steelseries
Good morning,

I don't understand the reason and why of the error that occurs with my 
version 4.10.2 of weewx and the 'SteelSeries' Skin.

Can anyone help me and tell me what's going on?
THANKS



Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/ss/gauge-data.txt.tmpl
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
Reason: 'UnknownType' object is not subscriptable
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 348, in generate
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   unicode_string = compiled_template.respond()
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_ss_gauge_data_txt_tmpl.py", line 142, in respond
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1446, in 
getVar
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   return valueFromSearchList(
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 1094, in raw
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:    
   return self.value_t[0]
Jan 20 10:31:21 localhost weewx[16495] ERROR weewx.cheetahgenerator:  
 TypeError: 'UnknownType' object is not subscriptable

-- 
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/16f5a162-11f1-4b5c-b12b-a4539aa7833en%40googlegroups.com.

[weewx-user] Integrate rain24 with Packetsloop

[Remy Lavabre]

Good morning,

I created a [driver] for weewx to retrieve data from the Awekas API (my 
Bresser weather station does not have a USB port).

This works but regarding the rain, it is not the instantaneous rain (from a 
packetloop) that we recover but the rain over 24 hours since midnight.
Is there a "simple" way to tell WeeWX that the packetsloop rain data 
corresponds to the cumulative rain since midnight and not the rain that 
fell during the data retrieval interval (the time gap between two 
packetsloops) ?

Thank you so much...

-- 
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/9887101f-fcc1-45ce-948e-e03429bf7baan%40googlegroups.com.

[weewx-user] Re: Packetsloop aggregation weewx

[Remy Lavabre]

Thank you for the answer ! Perfect...

Only two questions still bothers me:

- 1/ I added an “XField” field to my weewx.sdb database. This XField 
corresponds to a simple parameter such as temperature or pressure. It is 
incorporated into the "PacketsLoop".

Do we absolutely have to declare [Accumulator] in weewx.sdb as follows:







*[Accumulator] ... [[XField]] accumulator = scalar
 adder = add merger = minmax extractor = last*

or are there default parameters in weewx in a (new) field of unknown type 
in a database?


- 2/ Concerning "PacketsLoop": the weewx documentation stipulates that they 
can be complete (all fields in the database) or partial.

But are the two PacketsLoops below interpreted in the same way?

data1 = {'dateTime': mydatetime, 'usUnits': 'METRIC', 'outTemp': '31',* 
'outHumidity': None*, 'dewpoint': '28'}
data2 = {'dateTime': mydatetime, 'usUnits': 'METRIC', 'outTemp': '31',  
'dewpoint': '28'}

Thank you for your help - Kind regards

Le samedi 6 janvier 2024 à 22:34:41 UTC+1, bell...@gmail.com a écrit :

> check out, https://github.com/weewx/weewx/wiki/Accumulators
>
> On Saturday 6 January 2024 at 10:27:48 UTC-5 Remy Lavabre wrote:
>
>> Good morning,
>>
>> Wishing to write a driver for WeeWX in order to automatically retrieve 
>> and integrate AWEKAS data into the weewx.sbd database, I have a question 
>> regarding the management of "PacketsLoop" data:
>>
>> The Weewx documentation states that for temperatures, it is an average of 
>> the "packetsloop" received during the time period set in weewx.conf (300 
>> seconds for example), that for rain it is the maximum of packetsloop. -> OK
>>
>> But for the other data? What about it?
>>
>> If we add personal fields to the database, such as electricity 
>> consumption. What will be the value of this field in the database -> An 
>> average of packets received, the maximum value, the last?
>>
>> And is it possible to specify to wewx (and if so where and how...), what 
>> type of result we want to have with the aggregation of a field from several 
>> loop packets?
>>
>> 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/f70a3a6c-e1c2-4860-ba31-c4d247aff561n%40googlegroups.com.

[weewx-user] Packetsloop aggregation weewx

[Remy Lavabre]

Good morning,

Wishing to write a driver for WeeWX in order to automatically retrieve and 
integrate AWEKAS data into the weewx.sbd database, I have a question 
regarding the management of "PacketsLoop" data:

The Weewx documentation states that for temperatures, it is an average of 
the "packetsloop" received during the time period set in weewx.conf (300 
seconds for example), that for rain it is the maximum of packetsloop. -> OK

But for the other data? What about it?

If we add personal fields to the database, such as electricity consumption. 
What will be the value of this field in the database -> An average of 
packets received, the maximum value, the last?

And is it possible to specify to wewx (and if so where and how...), what 
type of result we want to have with the aggregation of a field from several 
loop packets?

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/93b93f0d-f7bb-4bda-8e34-39c7e73e26a4n%40googlegroups.com.

Re: [weewx-user] Problem registering my weather station in the WeeWX global station map

[Remy LAVABRE]

Thanks for your response Tom.

just a clarification on the use of fileparse:

if the fileparse setting for the loop packet recovery timeout in weewx.conf
is 10 seconds and the file containing the loop packet is only updated after
60 seconds (this is an example), what happens during the 50 seconds where
weewx will retrieve the same packet loop 5 times?

Does Weewx know how to manage the recovery of a same packet loop recovered
several times ?

THANKS

Le lun. 20 nov. 2023, 13:54, Tom Keffer  a écrit :

> The simplest would be to go back to using WeeWX, but this time using a
> driver that reads from your file.
>
> The WeeWX distribution includes an example, fileparse
> <https://github.com/weewx/weewx/tree/master/examples/fileparse>, that
> reads from a file using key=value pairs. Either change your file format to
> match, or modify fileparse to use a CSV input.
>
> On Mon, Nov 20, 2023 at 12:31 AM Remy Lavabre 
> wrote:
>
>> Good morning,
>> I previously used weeWX connected to the USB output of my weather
>> station. No problem, the station was well referenced on the world map of
>> WeeWX weather stations.
>>
>> Unfortunately my station broke down and an exchange was carried out under
>> warranty with a new station without a USB port. This station sends data to
>> AWEKAS.
>>
>> I was therefore forced to modify everything, to stop the WeeWX daemon
>> permanently, to automatically retrieve the data from the AWEKAS site every
>> 5 minutes, save it in CSV format and run wee_import at the same frequency
>> to update my weewx.sdb database and generate all the graphics, html pages
>> etc...
>>
>> It works perfectly EXCEPT that my weather station is no longer referenced
>> on the WeeWX map! :-(
>> Is there a way to reference it again although only using wee_import
>> (which nevertheless uses the weewx.conf configuration file)?
>>
>> 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/1b7247b6-4b94-4ff4-8160-006f54faff2fn%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/1b7247b6-4b94-4ff4-8160-006f54faff2fn%40googlegroups.com?utm_medium=email_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/CAPq0zEDrGDyL3f3nROcRq2X0qQQZFNZ_gR6fevGGPqzjxCWPzQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDrGDyL3f3nROcRq2X0qQQZFNZ_gR6fevGGPqzjxCWPzQ%40mail.gmail.com?utm_medium=email_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/CADhm9Yen3ra4wpHx3FkpPkaX4gqj3P8r5yLHNEpC40_0RfASXA%40mail.gmail.com.

[weewx-user] Problem registering my weather station in the WeeWX global station map

[Remy Lavabre]

Good morning,
I previously used weeWX connected to the USB output of my weather station. 
No problem, the station was well referenced on the world map of WeeWX 
weather stations.

Unfortunately my station broke down and an exchange was carried out under 
warranty with a new station without a USB port. This station sends data to 
AWEKAS.

I was therefore forced to modify everything, to stop the WeeWX daemon 
permanently, to automatically retrieve the data from the AWEKAS site every 
5 minutes, save it in CSV format and run wee_import at the same frequency 
to update my weewx.sdb database and generate all the graphics, html pages 
etc...

It works perfectly EXCEPT that my weather station is no longer referenced 
on the WeeWX map! :-(
Is there a way to reference it again although only using wee_import (which 
nevertheless uses the weewx.conf configuration file)?

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/1b7247b6-4b94-4ff4-8160-006f54faff2fn%40googlegroups.com.

Re: [weewx-user] Managing a boolean variable with weewx

[Remy Lavabre]

Thank you Tom for this suggestion which I will follow...

*One last quick question*:

- My boolean variable in the weewx.sdb database is heater -*> OK*
- For example, I add a "heater_value" variable in the [[Corrections]] 
section of the weewx.conf file -*> OK*

*My question:* Should I declare the "heater_value" variable elsewhere to be 
able to use it in the graphics or is that enough?

Thanks Tom for your idea! ;-)
Le dimanche 5 novembre 2023 à 15:46:15 UTC+1, Tom Keffer a écrit :

> You could create such a variable. Say your boolean value is "heater". Then 
> put in [[Corrections]]
>
> heater_value = 1 if heater else 0
>
>
> Then plot "heater_value".
>
> If you really want it in the same plot as inside temperature, but you 
> don't care what the actual value is, you could do something like
>
> heater_value = 69 if heater else 68
>
> This is assuming US Units. Then you could plot inTemp and heater_value 
> together.
>
> On Sun, Nov 5, 2023 at 5:12 AM Remy LAVABRE  wrote:
>
>> OK thanks. but would you have an idea about visualizing the on/off state 
>> on a graph? Is it better to record the values ​​0 and 1 instead of true 
>> false to ultimately visualize this data in a graph?
>> Thank you Tom
>>
>>
>> Le dim. 5 nov. 2023, 12:46, Tom Keffer  a écrit :
>>
>>> Unfortunately, the plotting library in WeeWX is capable of using only 
>>> one y-axis scale. A limitation, to be sure.
>>>
>>> On Sun, Nov 5, 2023 at 1:44 AM Remy Lavabre  wrote:
>>>
>>>> Good morning,
>>>> A "simple" question (apparently): I have a boolean type variable in my 
>>>> WeeWX database (ON/Off state).
>>>> Is it possible to show this state in a diagram? For example, draw the 
>>>> curve of an indoor temperature and at the same time on the graph the "ON" 
>>>> or "OFF" state of the Boolean variable?
>>>> If yes, how... ?? ;-)
>>>> Thank you so much...
>>>>
>>>> -- 
>>>> 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/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>>> You received this message because you are subscribed to the Google 
>>> Groups "weewx-user" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to weewx-user+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/CAPq0zEBJ0LWahM1WGZhMcg9%3DsPtphm0d5qGpJdYf7MCkNpHXKw%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBJ0LWahM1WGZhMcg9%3DsPtphm0d5qGpJdYf7MCkNpHXKw%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/CADhm9Yea%2B3JRXhxSk-0%2Bi9TCD-VF03GL_cfnHQdGwO0PV%3DFwCg%40mail.gmail.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/CADhm9Yea%2B3JRXhxSk-0%2Bi9TCD-VF03GL_cfnHQdGwO0PV%3DFwCg%40mail.gmail.com?utm_medium=email_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/3bed3e35-635e-4328-beeb-2b35431d7e08n%40googlegroups.com.

Re: [weewx-user] Managing a boolean variable with weewx

[Remy Lavabre]

OK thanks. but would you have an idea about visualizing the on/off state on 
a graph? Is it better to record the values ​​0 and 1 instead of true false 
to ultimately visualize this data in a graph?

Le dimanche 5 novembre 2023 à 12:46:38 UTC+1, Tom Keffer a écrit :

> Unfortunately, the plotting library in WeeWX is capable of using only one 
> y-axis scale. A limitation, to be sure.
>
> On Sun, Nov 5, 2023 at 1:44 AM Remy Lavabre  wrote:
>
>> Good morning,
>> A "simple" question (apparently): I have a boolean type variable in my 
>> WeeWX database (ON/Off state).
>> Is it possible to show this state in a diagram? For example, draw the 
>> curve of an indoor temperature and at the same time on the graph the "ON" 
>> or "OFF" state of the Boolean variable?
>> If yes, how... ?? ;-)
>> Thank you so much...
>>
>> -- 
>> 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/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com?utm_medium=email_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/67ae6a50-b1a7-46e2-88ec-1dd91d63b90an%40googlegroups.com.

Re: [weewx-user] Managing a boolean variable with weewx

[Remy LAVABRE]

OK thanks. but would you have an idea about visualizing the on/off state on
a graph? Is it better to record the values ​​0 and 1 instead of true false
to ultimately visualize this data in a graph?
Thank you Tom


Le dim. 5 nov. 2023, 12:46, Tom Keffer  a écrit :

> Unfortunately, the plotting library in WeeWX is capable of using only one
> y-axis scale. A limitation, to be sure.
>
> On Sun, Nov 5, 2023 at 1:44 AM Remy Lavabre 
> wrote:
>
>> Good morning,
>> A "simple" question (apparently): I have a boolean type variable in my
>> WeeWX database (ON/Off state).
>> Is it possible to show this state in a diagram? For example, draw the
>> curve of an indoor temperature and at the same time on the graph the "ON"
>> or "OFF" state of the Boolean variable?
>> If yes, how... ?? ;-)
>> Thank you so much...
>>
>> --
>> 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/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com?utm_medium=email_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/CAPq0zEBJ0LWahM1WGZhMcg9%3DsPtphm0d5qGpJdYf7MCkNpHXKw%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEBJ0LWahM1WGZhMcg9%3DsPtphm0d5qGpJdYf7MCkNpHXKw%40mail.gmail.com?utm_medium=email_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/CADhm9Yea%2B3JRXhxSk-0%2Bi9TCD-VF03GL_cfnHQdGwO0PV%3DFwCg%40mail.gmail.com.

[weewx-user] Managing a boolean variable with weewx

[Remy Lavabre]

Good morning,
A "simple" question (apparently): I have a boolean type variable in my 
WeeWX database (ON/Off state).
Is it possible to show this state in a diagram? For example, draw the curve 
of an indoor temperature and at the same time on the graph the "ON" or 
"OFF" state of the Boolean variable?
If yes, how... ?? ;-)
Thank you so much...

-- 
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/d04ae7c5-7f56--b60c-7cadffda172cn%40googlegroups.com.

Re: [weewx-user] List of conf parameters for skin.conf

[Remy LAVABRE]

Hello,
Weewx documentation, customisation guide
The Image generator

Le mer. 1 nov. 2023, 00:08, jmltech  a écrit :

> Hi,
> I’m using the Season skin 4.9.1, under Weewx 4.10.2
>
> In reading through the group messgaes, and looking at the skin.conf, I see
> a lot of configuration and override settings that can be made.   Parameters
> such as:
>
> yscale =
> x_label_format =
> bottom_label_format =
> color =
> fill_color =
> chart_line_color =
>
> Are these config and override parameters documented somewhere?  I have
> looked on the weewx wiki, as well as the group messages, and don’t see
> where all of the opions are listed and explained?
>
> 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/f0eb5301-96e2-44d0-ba17-760495586985n%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/CADhm9YdL-Jwd-ygktT%3DFQu791bc53FVUEdxmqPqMx%3D6x%2B7znDQ%40mail.gmail.com.

Re: [weewx-user] Problem with Weewx since 2023-10-31 00H00

[Remy Lavabre]

Yes well seen Tom (as usual...) and thank you!
I would NEVER have thought of that on my own! :-(

On the other hand, I put what is below to have the maximum wind speed over 
the past month and the total rain for the month.

What should I put instead to avoid this 31 day problem?
  Thanks again Tom!

 $current($timestamp=$span($month_delta=1).windGust.maxtime.raw).windDir.ordinal_compass
 
($current($span($month_delta=1).windGust.maxtime.raw).windDir) - $span($mon>
and $month.rain.sum
Le mardi 31 octobre 2023 à 17:55:17 UTC+1, Tom Keffer a écrit :

> This happens with unwary skins that try to calculate something from "a 
> month ago", when a month has 31 days and the previous month had 30. What is 
> "a month ago" from 31 October? Not 31 September --- it doesn't exist.
>
> See Issue #436 <https://github.com/weewx/weewx/issues/436>.
>
> On Tue, Oct 31, 2023 at 9:43 AM Remy Lavabre  wrote:
>
>> Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00
>>
>> Since this date, the Seasons2 skin no longer updates the index.html file. 
>> The Raspberry is not crashed, the database continues to fill normally and 
>> all graphs are generated normally.
>> The log trace gives the error below.
>> Does anyone have an idea of what happened at 00:00 on 10/31 and why there 
>> has been this error since then?
>> thank you
>>
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 
>> StdConvert target unit is 0x1
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive 
>> will use data binding wx_binding
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using 
>> archive interval of 300 seconds (specified by hardware)
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> StationRegistry: Station will be registered.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> Wunderground-PWS: Data for station IMILLA3 will be posted
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
>> PWSweather: Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS: 
>> Posting not enabled.
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service 
>> version is 0.13
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will 
>> be uploaded for id=ad400d4705decc9d
>> Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 'pyephem' 
>> detected, extended almanac data is available
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 0: "inTemp is not None and inTemp <= 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 1: "inTemp is not None and inTemp <= 64.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 2: "outTemp is not None and outTemp <= 34.0 and outTemp 
>> > 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 3: "outTemp is not None and outTemp <= 23.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 4: "outTemp is not None and outTemp <= 14.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 5: "outTemp is not None and outTemp >= 100.0"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 6: "rainRate is not None and rainRate > 0 and rainRate < 
>> 0.59"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 7: "rainRate is not None and rainRate >= 0.59 and 
>> rainRate < 0.98"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 8: "rainRate is not None and rainRate >= 0.98"
>> Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
>> set for expression 9: "windGust is not None and windGust >= 15.5 and 
>> wind

[weewx-user] Problem with Weewx since 2023-10-31 00H00

[Remy Lavabre]

Hello, Weewx 4.5.2 worked perfectly until 2023-10-30 23:55:00

Since this date, the Seasons2 skin no longer updates the index.html file. 
The Raspberry is not crashed, the database continues to fill normally and 
all graphs are generated normally.
The log trace gives the error below.
Does anyone have an idea of what happened at 00:00 on 10/31 and why there 
has been this error since then?
thank you

Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: StdConvert 
target unit is 0x1
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Archive 
will use data binding wx_binding
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: Using 
archive interval of 300 seconds (specified by hardware)
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
StationRegistry: Station will be registered.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: 
Wunderground-PWS: Data for station IMILLA3 will be posted
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: PWSweather: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: CWOP: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: WOW: Posting 
not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.restx: AWEKAS: 
Posting not enabled.
Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: service 
version is 0.13
Oct 31 17:30:27 localhost wee_reports[59221] INFO user.wcloud: Data will be 
uploaded for id=ad400d4705decc9d
Oct 31 17:30:27 localhost wee_reports[59221] INFO weewx.engine: 'pyephem' 
detected, extended almanac data is available
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 0: "inTemp is not None and inTemp <= 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 1: "inTemp is not None and inTemp <= 64.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 2: "outTemp is not None and outTemp <= 34.0 and outTemp 
> 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 3: "outTemp is not None and outTemp <= 23.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 4: "outTemp is not None and outTemp <= 14.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 5: "outTemp is not None and outTemp >= 100.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 6: "rainRate is not None and rainRate > 0 and rainRate < 
0.59"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 7: "rainRate is not None and rainRate >= 0.59 and 
rainRate < 0.98"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 8: "rainRate is not None and rainRate >= 0.98"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 9: "windGust is not None and windGust >= 15.5 and 
windGust < 27.7"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 10: "windGust is not None and windGust >= 27.7 and 
windGust < 31.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 11: "windGust is not None and windGust >= 31.0 and 
windGust < 37.28"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 12: "windGust is not None and windGust >= 37.28"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 13: "extraTemp6 is not None and extraTemp6 >= 133.0 and 
extraTemp6 < 140.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 14: "extraTemp6 is not None and extraTemp6 >= 140.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 15: "barometer is not None and barometer < 29.53"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 16: "extraTemp3 is not None and extraTemp3 <= 37.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 17: "extraTemp3 is not None and extraTemp3 <= 30.0"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.alarm_multi: Alarm 
set for expression 18: "extraTemp3 is not None and extraTemp3 >= 80.6"
Oct 31 17:30:34 localhost wee_reports[59221] INFO user.healthchecks: 
healthchecks: Using url 
https://hc-ping.com/UKc6fHh3r6GrAGmST3bSpw/weewx-record
Oct 31 17:30:35 localhost wee_reports[59221] INFO user.historygenerator: 
historygenerator.py: Generated 6 tables in 

[weewx-user] Re: Cloud base calculation formula in Weewx

[Remy Lavabre]

Thank you all for all this information which really helped me!
Sincerely

Le mardi 24 octobre 2023 à 11:01:49 UTC+2, Karen K a écrit :

> Remy Lavabre schrieb am Montag, 23. Oktober 2023 um 18:07:30 UTC+2:
>
> Would it be possible to know the WeeWX calculation formula used to obtain 
> the height of the cloud base in weewx from the outside temperature and the 
> dew point?
>
>
> It is Henning's formula, that is used.
>  
>

-- 
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/9038ae9c-0b63-4a01-a4d2-b972c08eb3e6n%40googlegroups.com.

[weewx-user] Cloud base calculation formula in Weewx

[Remy Lavabre]

Good morning,
Would it be possible to know the WeeWX calculation formula used to obtain 
the height of the cloud base in weewx from the outside temperature and the 
dew point?
Thank you - Kind regards

-- 
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/f8ce0a4a-b99f-4d4a-aece-f79a238790b1n%40googlegroups.com.

[weewx-user] Re: Changing the color of bars in a histogram chart

[Remy Lavabre]

Hello Gary,

No sorry, it doesn't work anymore.
See below :

#Histogrammes horaires électricité LINKY
[[[daylinky1]]]
yscale = None, None, 1
plot_type = bar
unit = watt_hour
electricityLinky
color = Red
fill_color = Red
*chart_line_colors = Black,Blue*
aggregate_type = sum
aggregate_interval = hour
label = Linky (total horaire)

[image: daylinky1.png]
and idem with "chartl_line_colors = Black,"

Le samedi 23 septembre 2023 à 04:41:35 UTC+2, gjr80 a écrit :

> There is a bug in WeeWX that may cause chart_fill_colours to fail in some 
> circumstances if only a single colour name is specified. The bug will be 
> fixed in due course, but in the interim if you either specify a second 
> colour (eg chart_fill_colors = Red, Blue) or terminate the a single entry 
> with a comma (eg chart_fill_colors = Red,) it should generate the plot as 
> expected.
>
> Same thing applies to chart_line_colors.
>
> Gary
> On Saturday, 23 September 2023 at 01:33:53 UTC+10 remy.l...@gmail.com 
> wrote:
>
>> Hello Gary and thank you again for your response.
>>
>> 1/If I put the option chart_fill_colors = Red in [[[daylinky1]]] as you 
>> suggest, it curiously blocks everything. My histogram is not generated but 
>> also the following ones from skin.conf.
>> If I replace chart_fill_colors = Red in the electricityLinky 
>> section EVERYTHING works normally again.
>>
>> 2/ Well seen for the fill_color = Red option placed in the 
>> electricityLinky section. This now generates red histograms for me.
>> If I set color = Red the title changes to red but also the edges of the 
>> histograms ! :-(
>>
>> The weewx documentation states:
>> "chart_line_colors: Each chart line is drawn in a different color. This 
>> option is a list of those colors. If the number of lines exceeds the length 
>> of the list, then the colors wrap around to the beginning of the list. 
>> Optional. In the case of bar charts, this is the color of the outline of 
>> the bar. Default is #ff, #00ff00, #ff.
>> Individual line color can be overridden by using option color."
>>
>> Oddly enough, the "chart_line_colors = Black" option placed in the 
>> electricityLinky section produces no effect...
>>
>> On the other hand, if I do not stipulate color = Red, I have the borders 
>> of the histograms which are a different color from red (blue).
>>
>> I do not understand why !
>>
>> Without option color = Red :
>> [image: daylinky1.png]
>>
>>
>> with options color = Red *and* chart_line_color = Black :
>>
>> [image: daylinky2.png]
>>
>>
>>
>> Le vendredi 22 septembre 2023 à 11:19:41 UTC+2, gjr80 a écrit :
>>
>>> chart_fill_colors is a config option that applies to all lines/bars not 
>>> individual lines/bars. Try moving chart_fill_colors to be under the 
>>> main plot config rather than under an individual line/bar config, eg:
>>>
>>> #Histogrammes horaires électricité LINKY
>>> [[[daylinky1]]]
>>> yscale = None, None, 1
>>> plot_type = bar
>>> unit = watt_hour
>>> chart_fill_colors = Red
>>> electricityLinky
>>>
>>> color = Red
>>> aggregate_type = sum
>>> aggregate_interval = hour
>>> label = Linky (total horaire)
>>>
>>>
>>> If you want to specify the colour for an individual bar use fill_color 
>>> instead, eg:
>>>
>>> #Histogrammes horaires électricité LINKY
>>> [[[daylinky1]]]
>>> yscale = None, None, 1
>>> plot_type = bar
>>> unit = watt_hour
>>> electricityLinky
>>> color = Red
>>> fill_color = Red
>>>
>>> aggregate_type = sum
>>> aggregate_interval = hour
>>> label = Linky (total horaire)
>>>
>>>
>>> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/997a8c9a-5d1a-4911-99b0-987f8d23010cn%40googlegroups.com.

[weewx-user] Re: Changing the color of bars in a histogram chart

[Remy Lavabre]

Hello Gary and thank you again for your response.

1/If I put the option chart_fill_colors = Red in [[[daylinky1]]] as you 
suggest, it curiously blocks everything. My histogram is not generated but 
also the following ones from skin.conf.
If I replace chart_fill_colors = Red in the electricityLinky 
section EVERYTHING works normally again.

2/ Well seen for the fill_color = Red option placed in the 
electricityLinky section. This now generates red histograms for me.
If I set color = Red the title changes to red but also the edges of the 
histograms ! :-(

The weewx documentation states:
"chart_line_colors: Each chart line is drawn in a different color. This 
option is a list of those colors. If the number of lines exceeds the length 
of the list, then the colors wrap around to the beginning of the list. 
Optional. In the case of bar charts, this is the color of the outline of 
the bar. Default is #ff, #00ff00, #ff.
Individual line color can be overridden by using option color."

Oddly enough, the "chart_line_colors = Black" option placed in the 
electricityLinky section produces no effect...

On the other hand, if I do not stipulate color = Red, I have the borders of 
the histograms which are a different color from red (blue).

I do not understand why !

Without option color = Red :
[image: daylinky1.png]


with options color = Red *and* chart_line_color = Black :

[image: daylinky2.png]



Le vendredi 22 septembre 2023 à 11:19:41 UTC+2, gjr80 a écrit :

> chart_fill_colors is a config option that applies to all lines/bars not 
> individual lines/bars. Try moving chart_fill_colors to be under the main 
> plot config rather than under an individual line/bar config, eg:
>
> #Histogrammes horaires électricité LINKY
> [[[daylinky1]]]
> yscale = None, None, 1
> plot_type = bar
> unit = watt_hour
> chart_fill_colors = Red
> electricityLinky
>
> color = Red
> aggregate_type = sum
> aggregate_interval = hour
> label = Linky (total horaire)
>
>
> If you want to specify the colour for an individual bar use fill_color 
> instead, eg:
>
> #Histogrammes horaires électricité LINKY
> [[[daylinky1]]]
> yscale = None, None, 1
> plot_type = bar
> unit = watt_hour
> electricityLinky
> color = Red
> fill_color = Red
>
> aggregate_type = sum
> aggregate_interval = hour
> label = Linky (total horaire)
>
>
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/21d030f4-a0c5-494b-bf9a-fa2b6e8fffd7n%40googlegroups.com.

[weewx-user] Re: Changing the color of bars in a histogram chart

[Remy Lavabre]

Hi.
Skin.conf :

#Histogrammes horaires électricité LINKY
[[[daylinky1]]]
yscale = None, None, 1
plot_type = bar
unit = watt_hour
electricityLinky
chart_fill_colors = Red
color = Red
aggregate_type = sum
aggregate_interval = hour
label = Linky (total horaire)

#Histogrammes cumul horaires électricité LINKY
[[[daylinky2]]]
yscale = None, None, 1
plot_type = bar
unit = kilowatt_hour
electricityLinky
chart_fill_colors = Red
color = Red
aggregate_type = cumulative
aggregate_interval = hour
label = Linky (cumul sur les 24 dernières heures)

Le mercredi 20 septembre 2023 à 12:03:17 UTC+2, gjr80 a écrit :

> On the face of it that looks OK, but it would help to see the entire 
> [ImageGenerator] stanza in skin.conf.
>
> Gary
>
> On Wednesday, 20 September 2023 at 17:19:50 UTC+10 remy.l...@gmail.com 
> wrote:
>
>> Good morning,
>>
>> the option *chart_fill_colors = *is supposed to change the fill color of 
>> the bar charts *(chart_fill_colors: A list of the color to be used as 
>> the fill of the bar charts. Optional. The default is to use the same color 
>> as the outline color ( option chart_line_colors).*
>>
>> But when in skin.conf I put
>> color = Red
>> chart_fill_colors = Red
>>
>> I get blue histograms with a red border...
>> How to obtain red histograms?
>> THANKS...
>>
>> [image: daylinky1.png]
>>
>

-- 
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/14e0d4f1-85f4-4050-a16f-1597dade44cdn%40googlegroups.com.

[weewx-user] Changing the color of bars in a histogram chart

[Remy Lavabre]

Good morning,

the option *chart_fill_colors = *is supposed to change the fill color of 
the bar charts *(chart_fill_colors: A list of the color to be used as the 
fill of the bar charts. Optional. The default is to use the same color as 
the outline color ( option chart_line_colors).*

But when in skin.conf I put
color = Red
chart_fill_colors = Red

I get blue histograms with a red border...
How to obtain red histograms?
THANKS...

[image: daylinky1.png]

-- 
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/761cc274-ede1-4740-bf45-4a6e1f9f7d28n%40googlegroups.com.

Re: [weewx-user] Re: Problem with weewx SQL database

[Remy Lavabre]

Thank you Gary for all these detailed explanations! Thank you also for your 
patience...
Thanks to you I was finally able to finish integrating the data into the 
weewx database as I wanted!
Without your precious help, I would* NEVER* have gotten there!

Just one last quick question, if weewx is updated, do you know if the 
/usr/share/weewx/user/extensions.py file is modified or if it is kept as is?

Thanks a lot again Gary!

Le lundi 18 septembre 2023 à 14:05:53 UTC+2, gjr80 a écrit :

> Some answers/guidance below.
>
> Gary
>
> On Monday, 18 September 2023 at 00:55:03 UTC+10 remy.l...@gmail.com wrote:
>
> However, I have a new question as I haven't been able to understand 
> exactly the weewx documentation on this subject. I clearly saw that the 
> case of adding electricity consumption to the database had been processed 
> but I did not understand the entire explanation given.
>
> To put it simply, I retrieve data in CSV format which I integrate at 
> regular intervals into the weewx database using wee_import.py (my weather 
> station does not have a USB output and the data is retrieved from AWEKAS).
> To the weather data, I would have liked to add for the period considered:
> - CPU load data (unitless)
> - The total and used memory of the Raspberry (kB unit)
> - The total and used capacity of the SSD (Gb unit)
> - Power consumption (Watt unit)
> - Water consumption (unit per liter)
>
> I created the fields I needed in the existing WeeWX database without 
> problem with wee_database
>
> What I couldn't do:
> - Create a new base group (for example group_memory with the new Kb and Gb 
> units). What file exactly should be modified or created and where is it 
> located?
>
> Compared to the documentation, I would tend to make a file 
> "/usr/share/weewx/user/memory.py" with in it:
>
>
>
>
>
>
>
>
>
> *import weewx.unitsweewx.units.obs_group_dict['rocketForce'] = 
> 'group_memory'weewx.units.USUnits['group_memory'] = 
> 'byte'weewx.units.MetricUnits['group_memory'] = 
> 'byte'weewx.units.MetricWXUnits['group_memory'] = 
> 'byte'weewx.units.default_unit_format_dict['byte'] = 
> '%.1f'weewx.units.default_unit_label_dict['byte'] = ' byte'*
>
> Is my approach correct? How to create the units kB and gB?
>
>
> Not quite. First up, no need for memory.py, just use 
> /usr/share/weewx/user/extensions.py, that is what is is meant for. Next, 
> WeeWX already has a unit named byte which is used with unit group 
> group_data. You can certainly define your own unit group group_memory but 
> why, it just adds the possibility for confusion. The one thing WeeWX does 
> not have is unit names representing kilobyte and gigabyte (and megabyte), 
> these you will need to define or otherwise handle yourself. To add units 
> kilobyte, megabyte and gigabyte you need to define the unit conversion 
> functions for each unit as well as specifying a number format and unit 
> label for each unit. We generally specify unit conversion functions using 
> lambda functions, in the case unit kilobyte we need to specify how to 
> convert from kilobyte to each of the other units that may be used within 
> unit group group_data; ie kilobyte to bit, kilobyte to byte, kilobyte to 
> megabyte and kilobyte to gigabyte. We might do this as follows:
>
> weewx.units.conversionDict['kilobyte'] = {'bit': lambda x: x * 8192.0,
>   'byte': lambda x: x * 1024.0,
>   'megabyte': lambda x: x / 1024.0,
>   'gigabyte': lambda x: x / 
> 1048576.0}
>
> Likewise for each of the other group_data units. To define a unit label 
> and number format for the kilobyte unit you would use something like:
>
> weewx.units.default_unit_label_dict['kilobyte'] = ' kB'
> weewx.units.default_unit_format_dict['kilobyte'] = '%.1f'
>
> Again, likewise for the other units.
>
> Overall you would end up with something like:
>
> weewx.units.conversionDict['bit'] = {'byte': lambda x: x / 8.0,
>  'kilobyte': lambda x: x / 8192.0,
>  'megabyte': lambda x: x / 8388608.0,
>  'gigabyte': lambda x: x / 8589934592 
> <(858)%20993-4592>.0}
> weewx.units.conversionDict['byte'] = {'bit': lambda x: x * 8.0,
>   'kilobyte': lambda x: x / 1024.0,
>   'megabyte': lambda x: x / 1048576.0,
>   'gigabyte': lambda x: x / 
> 1073741824.0}
> weewx.units.conversionDict['kilobyte'] = {'bit': lambda x: x * 8192.0,
>   'byte': lambda x: x * 1024.0,
>   'megabyte': lambda x: x / 1024.0,
>   'gigabyte': lambda x: x / 
> 1048576.0}
> weewx.units.conversionDict['megabyte'] = {'bit': lambda x: x * 8388608.0,
>   'byte': lambda 

Re: [weewx-user] Re: Problem with weewx SQL database

[Remy LAVABRE]

Hello and thank you for your answer.
By adding the line weewx.units.obs_group_dict['wetbulbTemp'] =
'group_temperature' to the /usr/share/weewx/user/extensions.py file, the
wetbulbTemp field is now imported correctly.
Thank you for your help !

However, I have a new question as I haven't been able to understand exactly
the weewx documentation on this subject. I clearly saw that the case of
adding electricity consumption to the database had been processed but I did
not understand the entire explanation given.

To put it simply, I retrieve data in CSV format which I integrate at
regular intervals into the weewx database using wee_import.py (my weather
station does not have a USB output and the data is retrieved from AWEKAS).
To the weather data, I would have liked to add for the period considered:
- CPU load data (unitless)
- The total and used memory of the Raspberry (kB unit)
- The total and used capacity of the SSD (Gb unit)
- Power consumption (Watt unit)
- Water consumption (unit per liter)

I created the fields I needed in the existing WeeWX database without
problem with wee_database

What I couldn't do:
- Create a new base group (for example group_memory with the new Kb and Gb
units). What file exactly should be modified or created and where is it
located?

Compared to the documentation, I would tend to make a file
"/usr/share/weewx/user/memory.py" with in it:









*import weewx.unitsweewx.units.obs_group_dict['rocketForce'] =
'group_memory'weewx.units.USUnits['group_memory'] =
'byte'weewx.units.MetricUnits['group_memory'] =
'byte'weewx.units.MetricWXUnits['group_memory'] =
'byte'weewx.units.default_unit_format_dict['byte'] =
'%.1f'weewx.units.default_unit_label_dict['byte'] = ' byte'*

Is my approach correct? How to create the units kB and gB?


- For data that is unitless such as charge1, charge5 and charge15 (assuming
that the field names of the weewx.sdb database are charge1,charge5,charge15
and that the names of the header fields of the CSV file to import are
charge1, charge5 and charge15), will the import be done by putting in the
CSV import configuration file for wee_import.py:
source = CSV

[CSV]

[[FieldMap]]
dateTime= dateTime, unix_epoch

charge1= charge1
charge5= charge5
charge15   = charge15

Thank you for your help because I have my data in a CSV file but am a
little lost importing it into the weewx database...

*Rémy LAVABRE*


Le sam. 29 juil. 2023 à 13:33, gjr80  a écrit :

> Should have spelt out the full path/file:
>
> /usr/share/weewx/user/extensions.py
>
> Didn’t say the WeeWX daemon has anything to do with your issue, was
> pointing out that for WeeWX to pickup the new settings (eg for reports,
> services etc) you need to restart the daemon. This is SOP for changes to
> .py files. For wee_import you do not need to restart.
>
> Gary
> On Saturday, 29 July 2023 at 09:47:31 UTC+1 remy.l...@gmail.com wrote:
>
>> Thanks Gary for your response.
>> I added :
>>
>>
>> import weewx.units
>> weewx.units.obs_group_dict['wetbulbTemp'] = 'group_temperature'
>>
>> in file /usr/share/weewx/weecfg/extension.py
>>
>> It didn't change anything about the problem when using wee_import.py, I
>> still get the same error.
>> I specify that I did not create a field ['wetbulbTemp'] in the WeeWX
>> database but simply renamed ['heatindex1'] to ['wetbulbTemp'].
>>
>> The WeeWX daemon does not enter (in my opinion) into the problem since to
>> use the wee_import.py utility it is strongly advised to stop it... What I
>> do.
>>
>> I saw in the documentation what you are talking about where it is a
>> question of creating a user/electricity.py service, but unfortunately did
>> not quite understand where this electricity.py file went... :-(
>>
>> *Rémy LAVABRE*
>>
>>
>> Le sam. 29 juil. 2023 à 10:04, gjr80  a écrit :
>>
>>> Your problem is that wee_database --add_column/--rename_column makes
>>> all necessary changes to the database, but it does not make any change to
>>> the WeeWX unit system; in other words WeeWX knows there is a field
>>> wetbulbTemp in the database but does not know if it is a temperature,
>>> wind speed or rainfall. To fix this you need to add wetbulbTemp to the
>>> WeeWX unit system, the usual approach for this is to add a couple of lines
>>> of code to user/extensions.py (refer to Assigning a unit group
>>> 
>>> in the Customization Guide
>>> ), in your case
>>> something like the following should work (untested):
>>>
>>> import weewx.units
>>> weewx.units.obs_group_dict['wetbulbTemp'] = 'group_temperature'
>>>
>>> For the WeeWX daemon this will take effect when WeeWX is restarted, but
>>> for the purposes of wee_import it should work straight away.
>>>
>>> Gary
>>> On Saturday, 29 July 2023 at 08:36:33 UTC+1 remy.l...@gmail.com wrote:
>>>
 *Good morning,*

Re: [weewx-user] Re: Problem with wee_import utility (rain field)

[Remy Lavabre]

Thanks Gary,

My fields, including for rain, incremented automatically yesterday for the 
first time!
Your solution was the right one and I still don't understand why the 
previous time the rain was not taken into account in my weewx database

However, thank you for your explanations which helped me progress and 
allowed me to resolve my problem!

[image: Capture d’écran du 2023-09-03 14-27-35.png]



Le mercredi 30 août 2023 à 22:27:29 UTC+2, gjr80 a écrit :

> Some comments below.
>
> Gary
>
> On Wednesday, 30 August 2023 at 20:02:01 UTC+10 remy.l...@gmail.com wrote:
>
> Actually, to make it simple for you, I have a weather station that doesn't 
> have a USB output. The data is sent to AWEKAS. So in python, for 5 minutes 
> I retrieve this data regularly, make an average for certain fields 
> (temperatures, hygrometry etc.) and for others take the maximum (rain rate) 
> during these 5 minutes. For rain, the station gives me the total since 
> 00:00 which I calculate into rain over the 5 minute time slot.
> After 5 minutes, I generate a CSV which will be integrated into the weewx 
> database with Wee_import.
> Weewx recalculates all the data, generates the html page and the csv file 
> is deleted.
> We start again every 5 minutes.
>
>  
> You have a complex, automated system for using wee_import. I would be 
> looking very carefully at what data wee_import is actually being fed, it 
> might not be what you think it is.
>  
>
> Do you think that a rainRate at 0 with a rain value in the rain field 
> could cause a problem during the integration and set both fields to 0?
>
>
> I don't think this is likely. wee_import will import data if the field 
> map is valid and consistent, the field map fields are found in the source 
> data and the field value is (in this case) numeric. 0 is nothing special, 
> just another number. The import processing of one imported field has no 
> impact on any other imported field.
>
>

-- 
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/4a8e03a6-e0f0-44b9-832b-572c339d04bdn%40googlegroups.com.

Re: [weewx-user] Re: Problem with wee_import utility (rain field)

[Remy LAVABRE]

Thank you very much for your patience Gary,

Indeed I did not provide you with all the data from the CSV file in order
to simplify.
However, the fields were in the correct order with the correct wording.

Regarding the --dry-run command, I actually remove it for integration. This
is why all my fields are saved in the database with the timestamp (except
for rain).

Actually, to make it simple for you, I have a weather station that doesn't
have a USB output. The data is sent to AWEKAS. So in python, for 5 minutes
I retrieve this data regularly, make an average for certain fields
(temperatures, hygrometry etc.) and for others take the maximum (rain rate)
during these 5 minutes. For rain, the station gives me the total since
00:00 which I calculate into rain over the 5 minute time slot.
After 5 minutes, I generate a CSV which will be integrated into the weewx
database with Wee_import.
Weewx recalculates all the data, generates the html page and the csv file
is deleted.
We start again every 5 minutes.

The other day after the changes you told me about there was a very light
rain.
I had this rain over two 5-minute time periods with a correct rain rate in
the CSV file.
However in the weewx database nothing...

This morning, I did another test manually and put a value of 2mm in the
rain field and 4mm/h in the rainRate. I manually tried the wee_import
command (exactly the same one that is in the crontab) and I had a correct
import this time!
So the problem really comes from me and not from weewx...

Do you think that a rainRate at 0 with a rain value in the rain field could
cause a problem during the integration and set both fields to 0?

I will first try to artificially simulate a rain in python in the CSV file
and see if this value now integrates correctly or not automatically with
the crontab.
Secondly, I will monitor the actual conditions (rain is normally forecast
this weekend...) and keep you informed.
*Thank you Gary for helping me out and giving me the solution! ;-)*

*Rémy LAVABRE*


Le mar. 29 août 2023 à 22:42, gjr80  a écrit :

> I just setup a WeeWX instance with your import config file in your first
> post but using rain = discrete and a csv data file using the two records
> in your last post. I ran wee_import using these files and --dry-run and
> --verbose and received somewhat different output to what you posted, in
> my case there were warnings of missing fields in the csv data file:
>
> $ sudo /home/weewx/bin/wee_import --import-config=/var/tmp/csv.conf
> --verbose
> /home/weewx/bin/wee_import:719: DeprecationWarning: The distutils package
> is deprecated and slated for removal in Python 3.12. Use setuptools or
> check PEP 632 for potential alternatives
>   from distutils.version import StrictVersion
> Using WeeWX configuration file /home/weewx/weewx.conf
> Starting wee_import...
> A CSV import from source file '/var/tmp/remy.csv' has been requested.
> The following options will be used:
>  config=/home/weewx/weewx.conf, import-config=/var/tmp/csv.conf
>  source=/var/tmp/remy.csv, from=None, to=None
>  dry-run=None, calc_missing=True, ignore_invalid_data=True
>  tranche=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
>  delimiter=',', rain=discrete, wind_direction=[-360.0, 360.0]
>  UV=True, radiation=True
> Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
> Destination table 'archive' unit system is '0x01' (US).
> Missing derived observations will be calculated.
> Starting import ...
> Obtaining raw import data for period 1 ...
> The following imported field-to-WeeWX field map will be used:
>  source field 'dateTime' in units 'unix_epoch' --> WeeWX field
> 'dateTime'
>  source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
>  source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
>  source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
>  source field 'inHumidity' in units 'percent' --> WeeWX field
> 'inHumidity'
>  source field 'outHumidity' in units 'percent' --> WeeWX field
> 'outHumidity'
>  source field 'windSpeed' in units 'km_per_hour' --> WeeWX field
> 'windSpeed'
>  source field 'windDir' in units 'degree_compass' --> WeeWX field
> 'windDir'
>  source field 'windGust' in units 'km_per_hour' --> WeeWX field
> 'windGust'
>  source field 'rainRate' in units 'mm_per_hour' --> WeeWX field
> 'rainRate'
>  source field 'rain' in units 'mm' --> WeeWX field 'rain'
>  source field 'dewpoint' in units 'degree_C' --> WeeWX field 'dewpoint'
>  source field 'windchill' in units 'degree_C' --> WeeWX field
> 'windchill'
>  source field 'radiation' in units 'watt_per_meter_squared' --> WeeWX
> field 'radiation'
>  source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
>  source field 'extraTemp1' in units 'degree_C' --> WeeWX field
> 'extraTemp1'
> Raw import data read successfully for period 1.
> Mapping raw import data for period 

Re: [weewx-user] Re: Problem with wee_import utility (rain field)

[Remy LAVABRE]

Hi Gary,
I followed your advice:

1/ I now have in the rain field of my csv file the amount of rain that fell
over the previous 5 minutes.
2/ I changed the config file so that rain=discrete is now the config value

Unfortunately, the integration of the csv file in the weewx database with
this new configuration did not solve the problem, the rain and rainRate
fields systematically remain at zero while the integration of all the other
fields works wonderfully!
Do you think there is something wrong or is it a weewx bug?


*My new configuration file :*
*rain = discrete*
wind_direction = 0,360

[[FieldMap]]
dateTime= dateTime, unix_epoch
barometer   = barometer, hPa
inTemp  = inTemp, degree_C
outTemp = outTemp, degree_C
inHumidity  = inHumidity, percent
outHumidity = outHumidity, percent
windSpeed   = windSpeed, km_per_hour
windDir = windDir, degree_compass
windGust= windGust, km_per_hour

*rainRate= rainRate, mm_per_hourrain= rain, mm*
dewpoint= dewpoint, degree_C
windchill   = windchill, degree_C
radiation   = radiation, watt_per_meter_squared
UV  = UV, uv_index
extraTemp1  = extraTemp1, degree_C

*Example of CSV file with rain & rainRate *:
dateTime,outTemp,outHumidity,dewpoint,appTemp,barometer,windchill,windSpeed,windDir,windGust
*,rain,rainRate*
2023-08-28 18:30:00,17.6,66.0,11.3,13.8,1009.5,17.6,3.8,0,6.1,*0.3,3.6*
2023-08-28 18:35:00,16.0,80.0,12.6,13.7,1009.4,16.0,3.8,1,7.1,*0.2,6.0*


*Result of the test :*
sudo wee_import --config=/etc/weewx/weewx.conf
--import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf --dry-run
--verbose
Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file '/home/pi/Documents/Bresser7in1/data5.csv'
has been requested.
The following options will be used:
 config=/etc/weewx/weewx.conf,
import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf
 source=/home/pi/Documents/Bresser7in1/data5.csv, from=None, to=None
 dry-run=True, calc_missing=True, ignore_invalid_data=True
 tranche=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
 delimiter=',', *rain=discrete,* wind_direction=[0.0, 360.0]
 UV=True, radiation=True
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Obtaining raw import data for period 1 ...
The following imported field-to-WeeWX field map will be used:
 source field 'dateTime' in units 'unix_epoch' --> WeeWX field
'dateTime'
 source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
 source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
 source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
 source field 'inHumidity' in units 'percent' --> WeeWX field
'inHumidity'
 source field 'outHumidity' in units 'percent' --> WeeWX field
'outHumidity'
 source field 'windSpeed' in units 'km_per_hour' --> WeeWX field
'windSpeed'
 source field 'windDir' in units 'degree_compass' --> WeeWX field
'windDir'
 source field 'windGust' in units 'km_per_hour' --> WeeWX field
'windGust'


* source field 'rainRate' in units 'mm_per_hour' --> WeeWX field
'rainRate' source field 'rain' in units 'mm' --> WeeWX field 'rain'*
 source field 'dewpoint' in units 'degree_C' --> WeeWX field 'dewpoint'
 source field 'windchill' in units 'degree_C' --> WeeWX field
'windchill'
 source field 'radiation' in units 'watt_per_meter_squared' --> WeeWX
field 'radiation'
 source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
 source field 'extraTemp1' in units 'degree_C' --> WeeWX field
'extraTemp1'
 source field 'extraTemp2' in units 'degree_C' --> WeeWX field
'extraTemp2'
 source field 'extraTemp3' in units 'degree_C' --> WeeWX field
'extraTemp3'
 source field 'extraTemp4' in units 'degree_C' --> WeeWX field
'extraTemp4'
 source field 'extraTemp6' in units 'degree_C' --> WeeWX field
'extraTemp6'
 source field 'extraHumid1' in units 'percent' --> WeeWX field
'extraHumid1'
 source field 'extraHumid2' in units 'percent' --> WeeWX field
'extraHumid2'
 source field 'extraHumid3' in units 'percent' --> WeeWX field
'extraHumid3'
 source field 'extraHumid4' in units 'percent' --> WeeWX field
'extraHumid4'
*Raw import data read successfully for period 1.*
Mapping raw import data for period 1 ...
Mapped 1 records.
*Raw import data mapped successfully for period 1.*
1 records identified for import.
Unique records processed: 1; Last timestamp: 2023-08-29 14:30:00 CEST
(1693312200)
Finished dry run import
1 records were processed and 1 unique records would have been imported.

*Rémy LAVABRE*

[weewx-user] Re: Problem with wee_import utility (rain field)

[Remy Lavabre]

Thank you Gary for your very quick and detailed response. Nice of you!
I had read the documentation on the Weewx utilities guide but had not 
understood it in the sense you indicate...
So I modified my Python program to calculate in the csv file the amount of 
water that fell over the 5 minute period and modified the configuration 
file with rain=discrete instead of rain=cumulative.

Thanks again Gary. I'm waiting for the next rain and confirming the 
resolution of the problem.
Unfortunately no precipitation is expected locally for the next few days... 
We'll have to be patient! ;-)
Thanks a lot again Gary

Le dimanche 27 août 2023 à 05:02:05 UTC+2, gjr80 a écrit :

> If you are importing a single record and using rain = cumulative the 
> imported rain and rainRate values will always be zero, this is expected 
> behaviour. The reason being that WeeWX records rainfall data on a per 
> archive interval basis; in other words each archive record contains the 
> rainfall that was recorded in that archive period, for example in the last 
> five minutes if using a five minute archive interval. When the import 
> source rainfall data is cumulative or a running total wee_import 
> calculates the rain field value as the difference in this cumulative or 
> running total value between successive records. The If there is only one 
> record then this difference cannot be calculated and hence rain is 
> recorded as zero. Likewise for rainRate; if there is no rain data then 
> there can be no rainRate.
>
> The use of the rain config option in a CSV import config file is covered 
> here  in the 
> Utilities 
> Guide .
>
> If you must import a single record at a time you must convert your source 
> rain data to be a per-record value and import using rain = discrete. 
> wee_import was not designed with the regular import of single records in 
> mind, rather it was designed for the bulk import of days/months/years of 
> data. 
>
> Gary
> On Sunday, 27 August 2023 at 04:34:16 UTC+10 remy.l...@gmail.com wrote:
>
>>
>>
>>
>> *Good morning,I am using the wee_import.py utility to integrate AWEKAS 
>> data into my weewx database.command executed: *sudo wee_import 
>> --config=/etc/weewx/weewx.conf 
>> --import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf --dry-run 
>> --verbose
>>
>> *My CSVFile :*
>>
>>
>> dateTime,outTemp,outHumidity,dewpoint,appTemp,barometer,windchill,windSpeed,windDir,windGust,
>> *rain,rainRate*,UV,radiation,inTemp,inHumidity,extraTemp1
>> 2023-08-26 16:35:00,23.6,61.0,15.7,18.4,1010.6,23.6,3.2,214,3.9,*6.9,0,*
>> 1.1,101.0,26.1,53.0,24.9,22.0
>>
>>
>>
>> *My wee_import configuration file:*
>>
>> source = CSV
>>
>>
>> ##
>>
>> [CSV]
>> file = /home/pi/Documents/Bresser7in1/data5.csv
>> delimiter = ','
>> decimal = '.'
>> interval = conf
>> qc = True
>> calc_missing = True
>> ignore_invalid_data = True
>> tranche = 250
>> UV_sensor = True
>> solar_sensor = True
>> raw_datetime_format = %Y-%m-%d %H:%M:%S
>>
>> rain = cumulative
>> wind_direction = 0,360
>>
>>
>> [[FieldMap]]
>> dateTime= dateTime, unix_epoch
>> barometer   = barometer, hPa
>> inTemp  = inTemp, degree_C
>> outTemp = outTemp, degree_C
>> inHumidity  = inHumidity, percent
>> outHumidity = outHumidity, percent
>> windSpeed   = windSpeed, km_per_hour
>> windDir = windDir, degree_compass
>> windGust= windGust, km_per_hour
>> 
>> *rainRate= rainRate, mm_per_hourrain= rain, mm*
>> dewpoint= dewpoint, degree_C
>> windchill   = windchill, degree_C
>> radiation   = radiation, watt_per_meter_squared
>> UV  = UV, uv_index
>> extraTemp1  = extraTemp1, degree_C
>> extraTemp2  = extraTemp2, degree_C
>> extraTemp3  = extraTemp3, degree_C
>> extraTemp4  = extraTemp4, degree_C
>> extraTemp6  = extraTemp6, degree_C
>> extraHumid1 = extraHumid1, percent
>> extraHumid2 = extraHumid2, percent
>> extraHumid3 = extraHumid3, percent
>> extraHumid4 = extraHumid4, percent
>>
>>
>>
>> *Response from WeeWX :*
>>
>> Using WeeWX configuration file /etc/weewx/weewx.conf
>> Starting wee_import...
>> A CSV import from source file '/home/pi/Documents/Bresser7in1/data5.csv' 
>> has been requested.
>> The following options will be used:
>>  config=/etc/weewx/weewx.conf, 
>> import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf
>>  source=/home/pi/Documents/Bresser7in1/data5.csv, from=None, to=None
>>  dry-run=True, calc_missing=True, ignore_invalid_data=True
>>  tranche=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
>>  delimiter=',', rain=cumulative, 

[weewx-user] Problem with wee_import utility (rain field)

[Remy Lavabre]

*Good morning,I am using the wee_import.py utility to integrate AWEKAS data 
into my weewx database.command executed: *sudo wee_import 
--config=/etc/weewx/weewx.conf 
--import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf --dry-run 
--verbose

*My CSVFile :*

dateTime,outTemp,outHumidity,dewpoint,appTemp,barometer,windchill,windSpeed,windDir,windGust,
*rain,rainRate*,UV,radiation,inTemp,inHumidity,extraTemp1
2023-08-26 16:35:00,23.6,61.0,15.7,18.4,1010.6,23.6,3.2,214,3.9,*6.9,0,*
1.1,101.0,26.1,53.0,24.9,22.0



*My wee_import configuration file:*

source = CSV

##

[CSV]
file = /home/pi/Documents/Bresser7in1/data5.csv
delimiter = ','
decimal = '.'
interval = conf
qc = True
calc_missing = True
ignore_invalid_data = True
tranche = 250
UV_sensor = True
solar_sensor = True
raw_datetime_format = %Y-%m-%d %H:%M:%S

rain = cumulative
wind_direction = 0,360


[[FieldMap]]
dateTime= dateTime, unix_epoch
barometer   = barometer, hPa
inTemp  = inTemp, degree_C
outTemp = outTemp, degree_C
inHumidity  = inHumidity, percent
outHumidity = outHumidity, percent
windSpeed   = windSpeed, km_per_hour
windDir = windDir, degree_compass
windGust= windGust, km_per_hour

*rainRate= rainRate, mm_per_hourrain= rain, mm*
dewpoint= dewpoint, degree_C
windchill   = windchill, degree_C
radiation   = radiation, watt_per_meter_squared
UV  = UV, uv_index
extraTemp1  = extraTemp1, degree_C
extraTemp2  = extraTemp2, degree_C
extraTemp3  = extraTemp3, degree_C
extraTemp4  = extraTemp4, degree_C
extraTemp6  = extraTemp6, degree_C
extraHumid1 = extraHumid1, percent
extraHumid2 = extraHumid2, percent
extraHumid3 = extraHumid3, percent
extraHumid4 = extraHumid4, percent



*Response from WeeWX :*

Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file '/home/pi/Documents/Bresser7in1/data5.csv' 
has been requested.
The following options will be used:
 config=/etc/weewx/weewx.conf, 
import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf
 source=/home/pi/Documents/Bresser7in1/data5.csv, from=None, to=None
 dry-run=True, calc_missing=True, ignore_invalid_data=True
 tranche=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
 delimiter=',', rain=cumulative, wind_direction=[0.0, 360.0]
 UV=True, radiation=True
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Obtaining raw import data for period 1 ...
The following imported field-to-WeeWX field map will be used:
 source field 'dateTime' in units 'unix_epoch' --> WeeWX field 
'dateTime'
 source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
 source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
 source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
 source field 'inHumidity' in units 'percent' --> WeeWX field 
'inHumidity'
 source field 'outHumidity' in units 'percent' --> WeeWX field 
'outHumidity'
 source field 'windSpeed' in units 'km_per_hour' --> WeeWX field 
'windSpeed'
 source field 'windDir' in units 'degree_compass' --> WeeWX field 
'windDir'
 source field 'windGust' in units 'km_per_hour' --> WeeWX field 
'windGust'

* source field 'rainRate' in units 'mm_per_hour' --> WeeWX field 
'rainRate' source field 'rain' in units 'mm' --> WeeWX field 'rain'*
 source field 'dewpoint' in units 'degree_C' --> WeeWX field 'dewpoint'
 source field 'windchill' in units 'degree_C' --> WeeWX field 
'windchill'
 source field 'radiation' in units 'watt_per_meter_squared' --> WeeWX 
field 'radiation'
 source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
 source field 'extraTemp1' in units 'degree_C' --> WeeWX field 
'extraTemp1'
 source field 'extraTemp2' in units 'degree_C' --> WeeWX field 
'extraTemp2'
 source field 'extraTemp3' in units 'degree_C' --> WeeWX field 
'extraTemp3'
 source field 'extraTemp4' in units 'degree_C' --> WeeWX field 
'extraTemp4'
 source field 'extraTemp6' in units 'degree_C' --> WeeWX field 
'extraTemp6'
 source field 'extraHumid1' in units 'percent' --> WeeWX field 
'extraHumid1'
 source field 'extraHumid2' in units 'percent' --> WeeWX field 
'extraHumid2'
 source field 'extraHumid3' in units 'percent' --> WeeWX field 
'extraHumid3'
 source field 'extraHumid4' in units 'percent' --> WeeWX field 
'extraHumid4'
Raw import data read successfully for period 1.

Re: [weewx-user] Re: Problem with weewx SQL database

[Remy LAVABRE]

Thanks Gary for your response.
I added :

import weewx.units
weewx.units.obs_group_dict['wetbulbTemp'] = 'group_temperature'

in file /usr/share/weewx/weecfg/extension.py

It didn't change anything about the problem when using wee_import.py, I
still get the same error.
I specify that I did not create a field ['wetbulbTemp'] in the WeeWX
database but simply renamed ['heatindex1'] to ['wetbulbTemp'].

The WeeWX daemon does not enter (in my opinion) into the problem since to
use the wee_import.py utility it is strongly advised to stop it... What I
do.

I saw in the documentation what you are talking about where it is a
question of creating a user/electricity.py service, but unfortunately did
not quite understand where this electricity.py file went... :-(

*Rémy LAVABRE*


Le sam. 29 juil. 2023 à 10:04, gjr80  a écrit :

> Your problem is that wee_database --add_column/--rename_column makes all
> necessary changes to the database, but it does not make any change to the
> WeeWX unit system; in other words WeeWX knows there is a field wetbulbTemp
> in the database but does not know if it is a temperature, wind speed or
> rainfall. To fix this you need to add wetbulbTemp to the WeeWX unit
> system, the usual approach for this is to add a couple of lines of code to
> user/extensions.py (refer to Assigning a unit group
> 
> in the Customization Guide
> ), in your case
> something like the following should work (untested):
>
> import weewx.units
> weewx.units.obs_group_dict['wetbulbTemp'] = 'group_temperature'
>
> For the WeeWX daemon this will take effect when WeeWX is restarted, but
> for the purposes of wee_import it should work straight away.
>
> Gary
> On Saturday, 29 July 2023 at 08:36:33 UTC+1 remy.l...@gmail.com wrote:
>
>> *Good morning,*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *My WeeWX.sdb database works perfectly. I removed all unnecessary fields
>> with sudo wee_database --drop-columns=XXX,YYY,ZZZ which worked perfectly.I
>> renamed the field "heatindex1", from the base to "wetbulbTemp" with the
>> command: sudo wee_database --rename-column=heatindex1
>> --to-name=wetbulbTemp. Flawless.The problem is when I try to insert CSV
>> data into the database using the wee_import.py utility.All fields work on
>> import except the one renamed to "wetbulbTemp"...If I remove the
>> wetbulbTemp field from the import configuration file (*.conf), the import
>> is done without any problem.With the field renamed "wetbulbTemp", I get the
>> following message:*
>>
>> Using WeeWX configuration file /etc/weewx/weewx.conf
>> Starting wee_import...
>> A CSV import from source file '/home/pi/Documents/Bresser7in1/data5.csv'
>> has been requested.
>> The following options will be used:
>>   config=/etc/weewx/weewx.conf,
>> import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf
>>   source=/home/pi/Documents/Bresser7in1/data5.csv, from=None, to=None
>>   dry-run=True, calc_missing=True, ignore_invalid_data=True
>>   slice=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
>>   delimiter=',', rain=cumulative, wind_direction=[0.0, 360.0]
>>   UV=True, radiation=True
>> Using database binding 'wx_binding', which is bound to database
>> 'weewx.sdb'
>> Destination table 'archive' unit system is '0x01' (US).
>> Missing derived observations will be calculated.
>> This is a dry run, imported data will not be saved to archive.
>> Starting dry run import ...
>> Obtaining raw import data for period 1 ...
>> The following imported field-to-WeeWX field map will be used:
>>   source field 'dateTime' in units 'unix_epoch' --> WeeWX field
>> 'dateTime'
>>   source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
>>   source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
>>   source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
>>   source field 'inHumidity' in units 'percent' --> WeeWX field
>> 'inHumidity'
>>   source field 'outHumidity' in units 'percent' --> WeeWX field
>> 'outHumidity'
>>   source field 'windSpeed' in units 'km_per_hour' --> WeeWX field
>> 'windSpeed'
>>   source field 'windDir' in units 'degree_compass' --> WeeWX field
>> 'windDir'
>>   source field 'windGust' in units 'km_per_hour' --> WeeWX field
>> 'windGust'
>>   source field 'rainRate' in units 'mm_per_hour' --> WeeWX field
>> 'rainRate'
>>   source field 'rain' in units 'mm' --> WeeWX field 'rain'
>>   source field 'dewpoint' in units 'degree_C' --> WeeWX field
>> 'dewpoint'
>>   source field 'windchill' in units 'degree_C' --> WeeWX field
>> 'windchill'
>>   source field 'radiation' in units 'watt_per_meter_squared' -->
>> WeeWX field 'radiation'
>>   source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
>>   source field 'extraTemp1' in units 'degree_C' --> WeeWX field
>> 'extraTemp1'
>>   

[weewx-user] Problem with weewx SQL database

[Remy Lavabre]

*Good morning,*










*My WeeWX.sdb database works perfectly. I removed all unnecessary fields 
with sudo wee_database --drop-columns=XXX,YYY,ZZZ which worked perfectly.I 
renamed the field "heatindex1", from the base to "wetbulbTemp" with the 
command: sudo wee_database --rename-column=heatindex1 
--to-name=wetbulbTemp. Flawless.The problem is when I try to insert CSV 
data into the database using the wee_import.py utility.All fields work on 
import except the one renamed to "wetbulbTemp"...If I remove the 
wetbulbTemp field from the import configuration file (*.conf), the import 
is done without any problem.With the field renamed "wetbulbTemp", I get the 
following message:*

Using WeeWX configuration file /etc/weewx/weewx.conf
Starting wee_import...
A CSV import from source file '/home/pi/Documents/Bresser7in1/data5.csv' 
has been requested.
The following options will be used:
  config=/etc/weewx/weewx.conf, 
import-config=/home/pi/Documents/Bresser7in1/csv-Bresser.conf
  source=/home/pi/Documents/Bresser7in1/data5.csv, from=None, to=None
  dry-run=True, calc_missing=True, ignore_invalid_data=True
  slice=250, interval=conf, date/time_string_format=%Y-%m-%d %H:%M:%S
  delimiter=',', rain=cumulative, wind_direction=[0.0, 360.0]
  UV=True, radiation=True
Using database binding 'wx_binding', which is bound to database 'weewx.sdb'
Destination table 'archive' unit system is '0x01' (US).
Missing derived observations will be calculated.
This is a dry run, imported data will not be saved to archive.
Starting dry run import ...
Obtaining raw import data for period 1 ...
The following imported field-to-WeeWX field map will be used:
  source field 'dateTime' in units 'unix_epoch' --> WeeWX field 
'dateTime'
  source field 'barometer' in units 'hPa' --> WeeWX field 'barometer'
  source field 'inTemp' in units 'degree_C' --> WeeWX field 'inTemp'
  source field 'outTemp' in units 'degree_C' --> WeeWX field 'outTemp'
  source field 'inHumidity' in units 'percent' --> WeeWX field 
'inHumidity'
  source field 'outHumidity' in units 'percent' --> WeeWX field 
'outHumidity'
  source field 'windSpeed' in units 'km_per_hour' --> WeeWX field 
'windSpeed'
  source field 'windDir' in units 'degree_compass' --> WeeWX field 
'windDir'
  source field 'windGust' in units 'km_per_hour' --> WeeWX field 
'windGust'
  source field 'rainRate' in units 'mm_per_hour' --> WeeWX field 
'rainRate'
  source field 'rain' in units 'mm' --> WeeWX field 'rain'
  source field 'dewpoint' in units 'degree_C' --> WeeWX field 'dewpoint'
  source field 'windchill' in units 'degree_C' --> WeeWX field 
'windchill'
  source field 'radiation' in units 'watt_per_meter_squared' --> WeeWX 
field 'radiation'
  source field 'UV' in units 'uv_index' --> WeeWX field 'UV'
  source field 'extraTemp1' in units 'degree_C' --> WeeWX field 
'extraTemp1'
  source field 'extraTemp2' in units 'degree_C' --> WeeWX field 
'extraTemp2'
  source field 'extraTemp3' in units 'degree_C' --> WeeWX field 
'extraTemp3'
  source field 'extraTemp4' in units 'degree_C' --> WeeWX field 
'extraTemp4'
  source field 'extraHumid1' in units 'percent' --> WeeWX field 
'extraHumid1'
  source field 'extraHumid2' in units 'percent' --> WeeWX field 
'extraHumid2'
  source field 'extraHumid3' in units 'percent' --> WeeWX field 
'extraHumid3'
  source field 'extraHumid4' in units 'percent' --> WeeWX field 
'extraHumid4'
  source field 'wetbulbTemp' in units 'degree_C' --> WeeWX field 
'wetbulbTemp'
Raw import data read successfully for period 1.
Mapping raw import data for period 1 ...
Traceback (most recent call last):
   File "/usr/share/weewx/wee_import", line 900, in 
 hand()
   File "/usr/share/weewx/wee_import", line 830, in main
 source_obj.run()
   File "/usr/share/weewx/weeimport/weeimport.py", line 421, in run
 _mapped_data = self.mapRawData(_raw_data, self.archive_unit_sys)
   File "/usr/share/weewx/weeimport/weeimport.py", line 981, in mapRawData
 weewx.units.obs_group_dict[_field])
   File "/usr/lib/python3.9/collections/__init__.py", line 941, in 
__getitem__
 return self.__missing__(key) # support subclasses that define 
__missing__
   File "/usr/lib/python3.9/collections/__init__.py", line 933, in 
__missing__
 raiseKeyError(key)
*KeyError: 'wetbulbTemp'*



*I couldn't find any help in the WeeWX documentation on this.What is 
happening with this renamed field and what is the solution to integrate the 
CSV data of this field into my modified weewx.sdb database?*

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 

Re: [weewx-user] FTP Skin weewx - not synchronize a particular file

[Remy LAVABRE]

Thanks for your reply Tom.
Yes the FTP skin transfers all files from the Apache WEEWX server to an
external server such as a site host for example.
The problem is for example when there is a HTML page view counter text
file. That of the main server if it changes overwrites that of the mirror
server... To avoid this, would it be possible to provide in the skin.conf
configuration file of the FTP skin a list of files not to be copied in FTP?
Thanks Tom

*Rémy LAVABRE*


Le ven. 19 mai 2023 à 20:29, Tom Keffer  a écrit :

> Not understanding the question. Page view files normally live on the
> webserver. WeeWX FTP only moves files from the weewx host to the webserver,
> not the other way around.
>
> On Wed, May 17, 2023 at 5:07 AM Remy Lavabre 
> wrote:
>
>> Good morning,
>> Is there a way with the FTP skin not to synchronize a particular file
>> between the appache weewx server and a copy at a host, such as a page view
>> counter file?
>> 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/2d7e0a3b-8fa6-41b2-a836-8921be08ac7en%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/2d7e0a3b-8fa6-41b2-a836-8921be08ac7en%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
> --
> 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/05b0DmvRyoY/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/CAPq0zEDWL99gmfU_CP1sucV3ZD96qEZJHmXYz00rDUh3AbJD%2BQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEDWL99gmfU_CP1sucV3ZD96qEZJHmXYz00rDUh3AbJD%2BQ%40mail.gmail.com?utm_medium=email_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/CADhm9Yf2u9XvvkgOrWa_QiBfEM18e5_AH%2BNQdcrd%3DNtpiUcTMg%40mail.gmail.com.

[weewx-user] FTP Skin weewx - not synchronize a particular file

[Remy Lavabre]

Good morning,
Is there a way with the FTP skin not to synchronize a particular file 
between the appache weewx server and a copy at a host, such as a page view 
counter file?
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/2d7e0a3b-8fa6-41b2-a836-8921be08ac7en%40googlegroups.com.

Re: [weewx-user] Uptime in seconds with v4.10.1?

[Remy Lavabre]

>$time_since_last_frost.long_form and $time_since_last_rain.long_form work 
fine for me with weewx 4.10

[image: Capture d’écran du 2023-02-04 09-31-41.png]

Le samedi 4 février 2023 à 07:23:41 UTC+1, blaise@gmail.com a écrit :

> 02/04/23 07:15:00
> No rain today and
> Since 01/31/23 15:05:00
> *(10 minutes, 0 seconds)*
> Le 03-02-23 à 18:07, PC a écrit :
>
> Sorry, it doesn't work completely. With all my respect, go see the result 
> yourself 
>
> Le vendredi 3 février 2023 à 17:20:01 UTC+1, tke...@gmail.com a écrit :
>
>> It should be 
>>
>> *  $time_since('rain>0').long_form*
>>
>>  
>>
>> On Fri, Feb 3, 2023 at 8:14 AM PC  wrote:
>>
>>> Ok, cela  fonctionne.  Et pour  $time_since('rain>0')  ?
>>>
>>

-- 
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/5e12f52a-0dc3-42ce-b025-bf4b8efccb95n%40googlegroups.com.

[weewx-user] GSM Notifications for weewx

[Remy Lavabre]

Hello everyone...

Like you, I use the superb WeeWX software (thanks again for its designers!) 
and perhaps the alarm.py extension (or even better, alarm_multi.py).

By slightly modifying alarm.py or alarm_multi.py, it is very easily 
possible to receive notifications on your GSM mobile phone (The application 
is available for Android or iPhone on the store).

For example, when it rains, when the temperature drops or rises above a 
certain value, when there is wind with a pre-defined speed, etc. etc you 
receive an alert on your mobile phone

The original extension allows you to send an email, but with ntfy, you can 
very easily send notifications directly to your phones. Several settings 
are possible, such as adding an icon, defining a degree of urgency, etc. etc

It is also possible to self-host the notification server directly on your 
computer, which avoids going through the third-party server (more secure).

The documentation is available here: https://ntfy.sh/

I leave you a working example in python. Good fun to those who are 
interested ;-)


#!/usr/bin/env python3
# -*- coding: utf-8 -*-

import locale
from pip._vendor import requests


locale.setlocale(locale.LC_ALL, 'fr_FR.UTF-8')


URL_NOTIFY = "https://ntfy.sh/;
ABONNEMENT_NOTIFY = "MYNOTIF_PARAMETER"
URL_SERVEUR = "https://meteomillau.pagesperso-orange.fr/;
WEBCAM_FILE = "webcam.png"
ICON_ALERT = "warning,skull"


# Fonction de notification sur téléphone Android ou Iphone via 
l'application ntfy
# titre correspond au titre du message, message au texte du message, icone 
aux icones de notication rajoutés (voir plus bas), urgence de 1 à 5,
# click_ok si vrai renvoie sur une addresse http si click sur la 
notification et image_ok si vrai renvoie l'image png réduite de la WebCam
# En réponse à la procédure notify, le code de retour de la requête put.
# Icones : cloud_with_snow, cloud_with_rain, fog, thermometer, sunny, 
cold_face, hot_face, tornado, warning
# En fin d'operation, renvoie "True" et code erreur 0 si tout s'est bien 
passé, sinon False avec le libellé de l'erreur.

def notify (titre,message,icone,urgence,clic_ok,image_ok) :

if clic_ok :
ADDRESSE_CLIC = URL_SERVEUR
else :
ADDRESSE_CLIC = None

if image_ok :
ADDRESSE_IMAGE = URL_SERVEUR + WEBCAM_FILE
else :
ADDRESSE_IMAGE = None

PRIORITY_VALUE = {
1: "min",
2: "low",
3: "default",
4: "high",
5: "urgent"
}


priorite = PRIORITY_VALUE.get (urgence)

headers = {
'Click' : ADDRESSE_CLIC,
'Title' : titre.encode(encoding='utf-8'),
'Attach' : ADDRESSE_IMAGE,
'Priority': priorite,
'Tags': icone,
}
if priorite != None :
try :
reponse = requests.put(URL_NOTIFY + ABONNEMENT_NOTIFY, 
headers=headers, data=message.encode(encoding='utf-8'))
status_envoie = (reponse.reason=="OK")
erreur = "Notification GSM correctement envoyée"
except Exception as e:
status_envoie = False
erreur = e
else :
status_envoie = False
erreur = "Erreur de notification GSM : niveau d'urgence erroné 
(0...-> 5)"
return (status_envoie,erreur)





# -> Début du Programme 
<-



subj = "Alerte météo : TEMPERATURE EXTERIEURE TRES BASSE ( < -5°C ) -  
! DANGER GEL SEVERE ! "
status,code_erreur= notify ("Message d'alerte 
météo",subj,"warning",None,True,True)
print (status)
print (code_erreur)
exit ()

-- 
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/02bb87e4-7662-44db-ac01-3f8bceaf37a1n%40googlegroups.com.

Re: [weewx-user] Re: Bug with Pi OS 64 and Raspberry Zero 2w

[Remy Lavabre]

Yes the Pi Zero 2W ONLY runs WeeWX.
I added some Python software for WEEWX skin complement and backup (USB SSD 
and cloud).

I am well aware that these crashes are not related to WEEWX which is 
written in Python.
Besides, I have already had problems with crashes when launching sudo apt 
update, for example. The Pi suddenly shut down with a fresh install, PiOS 
lite 64B and no software other than WeeWX and the Python libraries!
The purpose of my message was to know if others had tried WeeWX 24/24 7/7 
in 64B on a Pi Zero 2W...
Thank-you...


Le dimanche 2 octobre 2022 à 10:35:27 UTC+2, Remy Lavabre a écrit :

> Thank you for all the answers.
> For information, the Pi Zero 2W is 64N with 512K of memory.
> I used it in 64B version in lite version without screen.
> I installed a cooler and its temperature is around 42°C on average. So 
> there is no overheating.
> Diagrams over several days show no overhead and no memory overflow. As a 
> precaution, I modified the swap to 1024 instead of the original 256 but 
> without any change!
> Syslog and usersylog don't show anything special. Pi seems to completely 
> crash and stop. No more SSH or HTTP connection and Weewx no longer records 
> anything on the shutdown period.
>
> [image: Capture d’écran du 2022-10-02 10-22-48.png]
> User LOG :
>
> Oct  2 01:10:54 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 2 files for report wxobs in 0.32 seconds
> Oct  2 01:10:54 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx/wxobs
> Oct  2 01:11:14 RPi-Meteo weewx[601] INFO weewx.reportengine: 
> ftpgenerator: Ftp'd 78 files in 19.97 seconds
> Oct  2 01:15:18 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
> 2022-10-02 01:15:19 CEST (1664666119) to database 'cmon.sdb'
> Oct  2 01:15:18 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
> 2022-10-02 01:15:19 CEST (1664666119) to daily summary in 'cmon.sdb'
> Oct  2 01:15:26 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
> 2022-10-02 01:15:00 CEST (1664666100) to database 'weewx.sdb'
> Oct  2 01:15:26 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
> 2022-10-02 01:15:00 CEST (1664666100) to daily summary in 'weewx.sdb'
> Oct  2 01:15:27 RPi-Meteo weewx[601] INFO weewx.restx: WeatherCloud: 
> Published record 2022-10-02 01:15:00 CEST (1664666100)
> Oct  2 01:15:27 RPi-Meteo weewx[601] INFO user.historygenerator: 
> historygenerator.py: Generated 6 tables in 0.29 seconds
> Oct  2 01:15:30 RPi-Meteo weewx[601] INFO weewx.restx: Wunderground-PWS: 
> Published record 2022-10-02 01:15:00 CEST (1664666100)
> Oct  2 01:15:32 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 10 files for report SeasonsReport2 in 4.78 seconds
> Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
> 20 images for report SeasonsReport2 in 2.16 seconds
> Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx
> Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 1 files for report Inigo in 0.38 seconds
> Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx/ss
> Oct  2 01:15:35 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 2 files for report SteelSeries in 0.19 seconds
> Oct  2 01:15:35 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
> 11 images for report SteelSeries in 0.92 seconds
> Oct  2 01:15:36 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 1 files for report cmon in 0.04 seconds
> Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
> 32 images for report cmon in 25.31 seconds
> Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: 
> Generated 2 files for report wxobs in 0.32 seconds
> Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
> files to /var/www/html/weewx/wxobs
> Oct  2 01:16:28 RPi-Meteo weewx[601] INFO weewx.reportengine: 
> ftpgenerator: Ftp'd 82 files in 26.84 seconds
> - CRASHES
> Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 3: 
> "/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.1"
> Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 3 was not an MTP 
> device
> Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 5: 
> "/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.4"
> Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 4: 
> "/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.3"
> Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 5 was not an MTP 
> device
> Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 4 was not an MTP 
> device
> Oct  2 07:17:11 RPi-Meteo udisksd[393]:

Re: [weewx-user] Re: Bug with Pi OS 64 and Raspberry Zero 2w

[Remy Lavabre]

Thank you for all the answers.
For information, the Pi Zero 2W is 64N with 512K of memory.
I used it in 64B version in lite version without screen.
I installed a cooler and its temperature is around 42°C on average. So 
there is no overheating.
Diagrams over several days show no overhead and no memory overflow. As a 
precaution, I modified the swap to 1024 instead of the original 256 but 
without any change!
Syslog and usersylog don't show anything special. Pi seems to completely 
crash and stop. No more SSH or HTTP connection and Weewx no longer records 
anything on the shutdown period.

[image: Capture d’écran du 2022-10-02 10-22-48.png]
User LOG :

Oct  2 01:10:54 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
2 files for report wxobs in 0.32 seconds
Oct  2 01:10:54 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/wxobs
Oct  2 01:11:14 RPi-Meteo weewx[601] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 78 files in 19.97 seconds
Oct  2 01:15:18 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
2022-10-02 01:15:19 CEST (1664666119) to database 'cmon.sdb'
Oct  2 01:15:18 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
2022-10-02 01:15:19 CEST (1664666119) to daily summary in 'cmon.sdb'
Oct  2 01:15:26 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
2022-10-02 01:15:00 CEST (1664666100) to database 'weewx.sdb'
Oct  2 01:15:26 RPi-Meteo weewx[601] INFO weewx.manager: Added record 
2022-10-02 01:15:00 CEST (1664666100) to daily summary in 'weewx.sdb'
Oct  2 01:15:27 RPi-Meteo weewx[601] INFO weewx.restx: WeatherCloud: 
Published record 2022-10-02 01:15:00 CEST (1664666100)
Oct  2 01:15:27 RPi-Meteo weewx[601] INFO user.historygenerator: 
historygenerator.py: Generated 6 tables in 0.29 seconds
Oct  2 01:15:30 RPi-Meteo weewx[601] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-10-02 01:15:00 CEST (1664666100)
Oct  2 01:15:32 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
10 files for report SeasonsReport2 in 4.78 seconds
Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
20 images for report SeasonsReport2 in 2.16 seconds
Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx
Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
1 files for report Inigo in 0.38 seconds
Oct  2 01:15:34 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/ss
Oct  2 01:15:35 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
2 files for report SteelSeries in 0.19 seconds
Oct  2 01:15:35 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
11 images for report SteelSeries in 0.92 seconds
Oct  2 01:15:36 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
1 files for report cmon in 0.04 seconds
Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.imagegenerator: Generated 
32 images for report cmon in 25.31 seconds
Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.cheetahgenerator: Generated 
2 files for report wxobs in 0.32 seconds
Oct  2 01:16:01 RPi-Meteo weewx[601] INFO weewx.reportengine: Copied 0 
files to /var/www/html/weewx/wxobs
Oct  2 01:16:28 RPi-Meteo weewx[601] INFO weewx.reportengine: ftpgenerator: 
Ftp'd 82 files in 26.84 seconds
- CRASHES
Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 3: 
"/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.1"
Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 3 was not an MTP device
Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 5: 
"/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.4"
Oct  2 07:17:11 RPi-Meteo mtp-probe: checking bus 1, device 4: 
"/sys/devices/platform/soc/3f98.usb/usb1/1-1/1-1.3"
Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 5 was not an MTP device
Oct  2 07:17:11 RPi-Meteo mtp-probe: bus: 1, device: 4 was not an MTP device
Oct  2 07:17:11 RPi-Meteo udisksd[393]: udisks daemon version 2.9.2 starting
Oct  2 07:17:12 RPi-Meteo udisksd[393]: failed to load module mdraid: 
libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Oct  2 07:17:12 RPi-Meteo udisksd[393]: Failed to load the 'mdraid' 
libblockdev plugin



Le samedi 1 octobre 2022 à 22:57:41 UTC+2, vince a écrit :

> In the absence of the original poster sharing any logs, we're unlikely to 
> be able to help.
>
>

-- 
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/498bd0ec-aae0-4360-8b4c-24d24b7716afn%40googlegroups.com.

[weewx-user] Bug with Pi OS 64 and Raspberry Zero 2w

[Remy Lavabre]

Good morning all.
I have been using weewx for 3 years with pi os 32B without any problem with 
a pi zero w then 2w.
Since I switched to version 64B, I have had lots of incomprehensible 
crashes with the pi not responding and having to reset. weewx is not in 
question.
I tried to increase the swap, to switch to a 3A power supply, to go back to 
the non-gl drivers, nothing helped! 

Have you noticed this kind of thing in 64 bits? is there a way to fix the 
problem? 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/cc1a4c04-e428-4121-bc83-7a8fde1843d4n%40googlegroups.com.

Re: [weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

No Tom, for me it is not necessary. But maybe one day for someone else? Who 
knows...
Thank's again Tom
Le lundi 27 juin 2022 à 16:11:38 UTC+2, tke...@gmail.com a écrit :

> Yes, I will include the fix in the code base.
>
> Wouldn't it be good to provide a second parameter for the value 
>> "MinProtocol = TLSv1.2"?
>
>
> Are you saying that we should implement ssl.set_alpn_protocols() as well? 
> Do you have a case where that was necessary?
>
> -tk
>
> On Mon, Jun 27, 2022 at 5:48 AM Remy Lavabre  wrote:
>
>> Hello again Tom,
>> This time it seems to be working fine! :-))) THANK YOU !
>>
>> Jun 27 14:41:18 localhost weewx[32382] INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 48 files in 13.59 seconds
>> Jun 27 14:46:28 localhost weewx[32382] INFO weewx.reportengine: 
>> ftpgenerator: Ftp'd 85 files in 27.68 seconds
>>
>> Could you confirm that this optional parameter will be added in the next 
>> WeeWX updates?
>> Wouldn't it be good to provide a second parameter for the value 
>> "MinProtocol = TLSv1.2"?
>>
>> thank you very much
>>
>> Le lundi 27 juin 2022 à 14:24:47 UTC+2, tke...@gmail.com a écrit :
>>
>>> Forgot another step. In addition to replacing weeutil/ftpupload.py, 
>>> replace weewx/reportengine.py with this copy.
>>>
>>> -tk
>>>
>>> On Mon, Jun 27, 2022 at 12:56 AM Remy Lavabre  
>>> wrote:
>>>
>>>> Hello Tom and thank you.
>>>>
>>>> Unfortunately it does not work (see attached syslog)
>>>> 1/ I replaced ftpupload.py in /usr/sare/weewx/weeutil
>>>> 2/ added ciphers = 'DEFAULT@SECLEVEL=1' in the [[FTP]] section of 
>>>> weewx.conf
>>>> 3/ put back in the file /etc/ssl/openssl.cnf the last line 
>>>> "CipherString = DEFAULT@SECLEVEL=2" (as originally by default).
>>>> 4/ Stopped WeeWX and restarted
>>>>
>>>> --> If I put DEFAULT@SECLEVEL=1 in the openssl.cnf file, same thing in 
>>>> the syslog.
>>>> --> If I stop WeeWX and restart it (with the new FTP.py), it works 
>>>> again as before... But with DEFAULT@SECLEVEL=1 in openssl.cnf! :-(
>>>>
>>>> If you have an idear... ?
>>>>
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>>> ftpgenerator: (0): caught exception '': [SSL: 
>>>> DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     Traceback (most recent call last):
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/share/weewx/weewx/reportengine.py", line 436, in run
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     n = ftp_data.run()
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/share/weewx/weeutil/ftpupload.py", line 175, in run
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     ftp_server.login(self.user, self.password)
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/lib/python3.9/ftplib.py", line 738, in login
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     self.auth()
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/lib/python3.9/ftplib.py", line 749, in auth
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     self.sock = self.context.wrap_socket(self.sock, 
>>>> server_hostname=self.host)
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     return self.sslsocket_class._create(
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>   File "/usr/lib/python3.9/ssl.py", line 1040, in _create
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
>>>>     self.do_handshake()
>>>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine:   
&

Re: [weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

Hello again Tom,
This time it seems to be working fine! :-))) THANK YOU !

Jun 27 14:41:18 localhost weewx[32382] INFO weewx.reportengine: 
ftpgenerator: Ftp'd 48 files in 13.59 seconds
Jun 27 14:46:28 localhost weewx[32382] INFO weewx.reportengine: 
ftpgenerator: Ftp'd 85 files in 27.68 seconds

Could you confirm that this optional parameter will be added in the next 
WeeWX updates?
Wouldn't it be good to provide a second parameter for the value 
"MinProtocol = TLSv1.2"?

thank you very much

Le lundi 27 juin 2022 à 14:24:47 UTC+2, tke...@gmail.com a écrit :

> Forgot another step. In addition to replacing weeutil/ftpupload.py, 
> replace weewx/reportengine.py with this copy.
>
> -tk
>
> On Mon, Jun 27, 2022 at 12:56 AM Remy Lavabre  wrote:
>
>> Hello Tom and thank you.
>>
>> Unfortunately it does not work (see attached syslog)
>> 1/ I replaced ftpupload.py in /usr/sare/weewx/weeutil
>> 2/ added ciphers = 'DEFAULT@SECLEVEL=1' in the [[FTP]] section of 
>> weewx.conf
>> 3/ put back in the file /etc/ssl/openssl.cnf the last line "CipherString 
>> = DEFAULT@SECLEVEL=2" (as originally by default).
>> 4/ Stopped WeeWX and restarted
>>
>> --> If I put DEFAULT@SECLEVEL=1 in the openssl.cnf file, same thing in 
>> the syslog.
>> --> If I stop WeeWX and restart it (with the new FTP.py), it works again 
>> as before... But with DEFAULT@SECLEVEL=1 in openssl.cnf! :-(
>>
>> If you have an idear... ?
>>
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> ftpgenerator: (0): caught exception '': [SSL: 
>> DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   Traceback (most recent call last):
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 436, in run
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   n = ftp_data.run()
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weeutil/ftpupload.py", line 175, in run
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   ftp_server.login(self.user, self.password)
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/lib/python3.9/ftplib.py", line 738, in login
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   self.auth()
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/lib/python3.9/ftplib.py", line 749, in auth
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   self.sock = self.context.wrap_socket(self.sock, 
>> server_hostname=self.host)
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   return self.sslsocket_class._create(
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/lib/python3.9/ssl.py", line 1040, in _create
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   self.do_handshake()
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   self._sslobj.do_handshake()
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> ftpgenerator: (1): caught exception '': [SSL: 
>> DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   Traceback (most recent call last):
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 436, in run
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>>   n = ftp_data.run()
>> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weeutil/ftpupload.py", line 175, in run
>> Jun 

Re: [weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

For iformation Tom, my [[FTP]] weewx.conf :

 [[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
# If you wish to use FTP, set "enable" to "true", then
# fill out the next four lines.
skin = Ftp

# Pour Orange, modifier le paramètre ciphers du fichier 
/etc/ssl/openssl.cnf
ciphers = 'DEFAULT@SECLEVEL=1'

# Use quotes around passwords to guard against parsing errors.
enable = True
user = A
password = B
server = C# The ftp server name, e.g, www.myserver.org
path = /# The destination directory, e.g., /weather

# Set to True for an FTP over TLS (FTPS) connection. Not all servers
# support this.
secure_ftp = True
secure_data = True

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
HTML_ROOT = /var/www/html/weewx

# Most FTP servers use port 21
port = 21

# Set to 1 to use passive mode, zero for active mode
passive = 1
max_trie = 3
ftp_encoding = UTF-8

#bug in the Python libraries that happens when use a Pure-FTP server
reuse_ssl = True

Le lundi 27 juin 2022 à 09:56:07 UTC+2, Remy Lavabre a écrit :

> Hello Tom and thank you.
>
> Unfortunately it does not work (see attached syslog)
> 1/ I replaced ftpupload.py in /usr/sare/weewx/weeutil
> 2/ added ciphers = 'DEFAULT@SECLEVEL=1' in the [[FTP]] section of 
> weewx.conf
> 3/ put back in the file /etc/ssl/openssl.cnf the last line "CipherString = 
> DEFAULT@SECLEVEL=2" (as originally by default).
> 4/ Stopped WeeWX and restarted
>
> --> If I put DEFAULT@SECLEVEL=1 in the openssl.cnf file, same thing in the 
> syslog.
> --> If I stop WeeWX and restart it (with the new FTP.py), it works again 
> as before... But with DEFAULT@SECLEVEL=1 in openssl.cnf! :-(
>
> If you have an idear... ?
>
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> ftpgenerator: (0): caught exception '': [SSL: 
> DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weewx/reportengine.py", line 436, in run
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   n = ftp_data.run()
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/share/weewx/weeutil/ftpupload.py", line 175, in run
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   ftp_server.login(self.user, self.password)
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/ftplib.py", line 738, in login
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   self.auth()
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/ftplib.py", line 749, in auth
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   self.sock = self.context.wrap_socket(self.sock, 
> server_hostname=self.host)
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   return self.sslsocket_class._create(
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/ssl.py", line 1040, in _create
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   self.do_handshake()
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   self._sslobj.do_handshake()
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> ftpgenerator: (1): caught exception '': [SSL: 
> DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
>   Traceback (most recent call last):
> Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
> F

Re: [weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
  self._sslobj.do_handshake()
Jun 27 09:41:11 localhost weewx[30338] ERROR weewx.reportengine: 
  ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
ftpgenerator: (2): caught exception '': [SSL: 
DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  Traceback (most recent call last):
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/share/weewx/weewx/reportengine.py", line 436, in run
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  n = ftp_data.run()
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/share/weewx/weeutil/ftpupload.py", line 175, in run
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  ftp_server.login(self.user, self.password)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/lib/python3.9/ftplib.py", line 738, in login
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  self.auth()
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/lib/python3.9/ftplib.py", line 749, in auth
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  self.sock = self.context.wrap_socket(self.sock, 
server_hostname=self.host)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/lib/python3.9/ssl.py", line 500, in wrap_socket
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  return self.sslsocket_class._create(
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/lib/python3.9/ssl.py", line 1040, in _create
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  self.do_handshake()
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
File "/usr/lib/python3.9/ssl.py", line 1309, in do_handshake
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  self._sslobj.do_handshake()
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
  ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1123)
Jun 27 09:41:12 localhost weewx[30338] ERROR weewx.reportengine: 
ftpgenerator: Upload failed

Le dimanche 26 juin 2022 à 21:44:40 UTC+2, tke...@gmail.com a écrit :

> Try this version of weeutil/ftpupload.py. It will allow you to set a 
> customized cipher:
>
> [StdReport]
> ...
> [[FTP]]
> ...
> ciphers = 'DEFAULT@SECLEVEL=1'
>
> If it works, I'll put it in the code base.
>
> -tk
>
>
> On Sun, Jun 26, 2022 at 10:21 AM Remy Lavabre  wrote:
>
>> Thanks for your reply Tom. Unfortunately, the ftp to ftps modification of 
>> the host is not new... May 2019! so no need to explain to you that it will 
>> not change overnight...
>> I thought of trying to modify your Ftp.py, but in the event of an update 
>> of weewx, everything will have to be redone...
>> I opted for the option to modify the ssl.cnf file in /usr/ssl but it is 
>> far from ideal!
>> is it possible to provide this kind of option at the level of weewx.conf 
>> during a future evolution?
>> thanks tom
>>
>> Le dimanche 26 juin 2022 à 13:01:11 UTC+2, tke...@gmail.com a écrit :
>>
>>> A little Googling reveals that this problem is caused by outdated 
>>> libraries on the FTP server. The "set_ciphers" option requests than an 
>>> older, less secure, protocol be used on the client side in order to match 
>>> what the server has.
>>>
>>> We could add support for setting cipher levels, but, before doing that, 
>>> is there any way you can talk your service provider into updating their 
>>> libraries? It's the better approach.
>>>
>>> On Sun, Jun 26, 2022 at 12:45 AM Remy Lavabre  
>>> wrote:
>>>
>>>> Hello,
>>>> I would like to use WeeWX's FTP option.
>>>> In Python, this works perfectly (WITH THE OPTION IN BOLD) :
>>>>
>>>>
>>>> from ftplib import FTP_TLS
>>>> import ssl
>>>> import requests
>>>>
>>>> HOST='A'
>>>> ID = 'B'
>>>> MDP = 'C'
>>>>
>>>> def connect():
>>>> ftp = FTP_TLS()
>>>> ftp.debugging = 2
>>>> *ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')*
>>>&g

Re: [weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

Thanks for your reply Tom. Unfortunately, the ftp to ftps modification of 
the host is not new... May 2019! so no need to explain to you that it will 
not change overnight...
I thought of trying to modify your Ftp.py, but in the event of an update of 
weewx, everything will have to be redone...
I opted for the option to modify the ssl.cnf file in /usr/ssl but it is far 
from ideal!
is it possible to provide this kind of option at the level of weewx.conf 
during a future evolution?
thanks tom

Le dimanche 26 juin 2022 à 13:01:11 UTC+2, tke...@gmail.com a écrit :

> A little Googling reveals that this problem is caused by outdated 
> libraries on the FTP server. The "set_ciphers" option requests than an 
> older, less secure, protocol be used on the client side in order to match 
> what the server has.
>
> We could add support for setting cipher levels, but, before doing that, is 
> there any way you can talk your service provider into updating their 
> libraries? It's the better approach.
>
> On Sun, Jun 26, 2022 at 12:45 AM Remy Lavabre  wrote:
>
>> Hello,
>> I would like to use WeeWX's FTP option.
>> In Python, this works perfectly (WITH THE OPTION IN BOLD) :
>>
>>
>> from ftplib import FTP_TLS
>> import ssl
>> import requests
>>
>> HOST='A'
>> ID = 'B'
>> MDP = 'C'
>>
>> def connect():
>> ftp = FTP_TLS()
>> ftp.debugging = 2
>> *ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')*
>> ftp.connect(HOST)
>> ftp.login(ID, MDP)
>> return ftp
>>
>> ftp = connect()
>> ftp.retrlines('LIST')
>>
>> Without this option ' * ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')'*, 
>> I always get the error: ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too 
>> small (_ssl.c:997)
>>
>> *My question*: How to configure the FTPS option in weewx.conf to force 
>> the same configuration?
>> Thanks a lot
>>
>> -- 
>> 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/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com?utm_medium=email_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/6dfd9849-4b82-461f-a51e-a10cf594e42dn%40googlegroups.com.

[weewx-user] Problem FTPS WeeWX

[Remy Lavabre]

Hello,
I would like to use WeeWX's FTP option.
In Python, this works perfectly (WITH THE OPTION IN BOLD) :


from ftplib import FTP_TLS
import ssl
import requests

HOST='A'
ID = 'B'
MDP = 'C'

def connect():
ftp = FTP_TLS()
ftp.debugging = 2
*ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')*
ftp.connect(HOST)
ftp.login(ID, MDP)
return ftp

ftp = connect()
ftp.retrlines('LIST')

Without this option ' * ftp.context.set_ciphers('DEFAULT@SECLEVEL=1')'*, I 
always get the error: ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too 
small (_ssl.c:997)

*My question*: How to configure the FTPS option in weewx.conf to force the 
same configuration?
Thanks a lot

-- 
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/74de0d09-fe98-4dc4-956a-0dd359f37bd4n%40googlegroups.com.

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

>>>>>>
>>>>>>>> I was able to replicate the problem. Pre V4.6, if windGustDir was 
>>>>>>>> missing, windDir was substituted. That behavior went away with v4.6. 
>>>>>>>> This 
>>>>>>>> patch restores it.
>>>>>>>>
>>>>>>>> Index: bin/weewx/wxxtypes.py
>>>>>>>> ===
>>>>>>>> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
>>>>>>>> --- a/bin/weewx/wxxtypes.py (revision 
>>>>>>>> 279bb450ab801c80a12b8ceadd0144e16c473bea)
>>>>>>>> +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
>>>>>>>> @@ -98,11 +98,18 @@
>>>>>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>>>>>  
>>>>>>>>  def calc_windGustDir(self, key, data, db_manager):
>>>>>>>> -# Return the current gust direction if windGust is 
>>>>>>>> non-zero, otherwise, None
>>>>>>>> -if 'windGust' not in data or 'windGustDir' not in data:
>>>>>>>> +"""If windGustDir is missing, substitute windDir.
>>>>>>>> +Set windGustDir to None if windGust is zero."""
>>>>>>>> +if 'windGust' not in data:
>>>>>>>>  raise weewx.CannotCalculate
>>>>>>>>  if self.force_null and data['windGust'] == 0:
>>>>>>>> +# windGust is zero. Force windGustDir to None
>>>>>>>>  val = None
>>>>>>>> +elif 'windGustDir' not in data:
>>>>>>>> +# windGustDir is missing. If available, substitute 
>>>>>>>> windDir.
>>>>>>>> +if 'windDir' not in data:
>>>>>>>> +raise weewx.CannotCalculate
>>>>>>>> +val = data['windDir']
>>>>>>>>  else:
>>>>>>>>  val = data['windGustDir']
>>>>>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>>>>>
>>>>>>>> Commit 9dc4da8 
>>>>>>>> <https://github.com/weewx/weewx/commit/9dc4da86a260f01d8792ac93d12871a05bff572d>
>>>>>>>> . 
>>>>>>>>
>>>>>>>> If you want this right away, you can replace weewx/wxxtypes.py with 
>>>>>>>> this 
>>>>>>>> version 
>>>>>>>> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxxtypes.py>
>>>>>>>> .
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Sun, Feb 13, 2022 at 1:38 AM Remy Lavabre  
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>>
>>>>>>>>> [image: Capture d’écran de 2022-02-13 10-14-16.png]
>>>>>>>>>
>>>>>>>>> Same problem for me !
>>>>>>>>> Since weewx 4.6.x windGustDir is always N/A but the value is 
>>>>>>>>> correct.
>>>>>>>>> I never had this problem before with 4.5.x or before... Only since 
>>>>>>>>> 4.6.x
>>>>>>>>>
>>>>>>>>> WindGustDir is always None in loop package values :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> LOOP:   2022-02-13 10:32:17 CET (1644744737) 'altimeter': 
>>>>>>>>> '30.122934097139712', 'appTemp': '45.455613403122314', 'barometer': 
>>>>>>>>> '30.14900779712183', 'beaufort': '1', 'cloudbase': 
>>>>>>>>> '3288.4136917377255', 
>>>>>>>>> 'dateTime': '1644744737', 'dayRain': '0.0', 'dewpoint': '41.36', 
>>>>>>>>> 'ET': 
>>>>>>>>> 'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 
>>>>>>>>> 'None', 
>>>>>>>>> 'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
>>>>>>>>> 'extraHum

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

Yes, it’s the good python file, same as me  (if standard installation...)
The Tom’s update/patch solves perfectly the problem and also min/max 
windGustDir data base.
Try stop and start weewx (logicaly same thing as restart... !?)
Try to look for all wxxtype.py on your system to see if there is another 
file ? Logicaly no...


Le dimanche 13 février 2022 à 20:23:07 UTC+1, paul...@gmail.com a écrit :

> Hi Remy
> Yes I did sudo /etc/init.d/weewx restart. Just in case I've done it again 
> but no change.
> Can I just check I swapped the correct wxxtypes.py file. I swapped the one 
> in /usr/share/weewx/weewx
> Paul
>
> On Sunday, 13 February 2022 at 18:08:44 UTC remy.l...@gmail.com wrote:
>
>> Hi Paul.
>> Have you triedto stop weewx and restart it ?
>> You must do that if you modify python file.
>> Cordialy 
>>
>>
>> Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a écrit :
>>
>>> I don't report wind gust values/direction in the Current Conditions 
>>> section of my Seasons skin (version 4.6.2) but in the Statistics 
>>> (previously High/Low) section I've always had a Max Wind entry with both 
>>> speed and direction reported. Since 4.6.2 the direction is reported as N/A 
>>> so I've followed this thread and replaced the wxxtypes.py file with the new 
>>> one from Tom but it doesn't seem to have made any difference to my Max Wind 
>>> entry. If you look at the Statistics report below it still shows N/A for 
>>> Max Wind degrees for Day and Week but for Month and Year (presumably data 
>>> from 4.5.1) a degree value is reported.
>>>
>>> [image: Max Wind.jpg]
>>> Any suggestions?
>>>
>>> Paul
>>> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>>>
>>>> Brilliant, now it work just fine.
>>>> Thanks a lot.
>>>>
>>>> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com 
>>>> wrote:
>>>>
>>>>> Yes !! Thank-you Tom it works great now :
>>>>>
>>>>> [image: Capture d’écran de 2022-02-13 15-26-27.png]
>>>>> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a 
>>>>> écrit :
>>>>>
>>>>>> I was able to replicate the problem. Pre V4.6, if windGustDir was 
>>>>>> missing, windDir was substituted. That behavior went away with v4.6. 
>>>>>> This 
>>>>>> patch restores it.
>>>>>>
>>>>>> Index: bin/weewx/wxxtypes.py
>>>>>> ===
>>>>>> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
>>>>>> --- a/bin/weewx/wxxtypes.py (revision 
>>>>>> 279bb450ab801c80a12b8ceadd0144e16c473bea)
>>>>>> +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
>>>>>> @@ -98,11 +98,18 @@
>>>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>>>  
>>>>>>  def calc_windGustDir(self, key, data, db_manager):
>>>>>> -# Return the current gust direction if windGust is non-zero, 
>>>>>> otherwise, None
>>>>>> -if 'windGust' not in data or 'windGustDir' not in data:
>>>>>> +"""If windGustDir is missing, substitute windDir.
>>>>>> +Set windGustDir to None if windGust is zero."""
>>>>>> +if 'windGust' not in data:
>>>>>>  raise weewx.CannotCalculate
>>>>>>  if self.force_null and data['windGust'] == 0:
>>>>>> +# windGust is zero. Force windGustDir to None
>>>>>>  val = None
>>>>>> +elif 'windGustDir' not in data:
>>>>>> +# windGustDir is missing. If available, substitute 
>>>>>> windDir.
>>>>>> +if 'windDir' not in data:
>>>>>> +raise weewx.CannotCalculate
>>>>>> +val = data['windDir']
>>>>>>  else:
>>>>>>  val = data['windGustDir']
>>>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>>>
>>>>>> Commit 9dc4da8 
>>>>>> <https://github.com/weewx/weewx/commit/9dc4da86a260f01d8792ac93d12871a05bff572d>
>>>>>> . 
>>>>>&g

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

Hi Paul.
Have you triedto stop weewx and restart it ?
You must do that if you modify python file.
Cordialy 


Le dimanche 13 février 2022 à 18:32:38 UTC+1, paul...@gmail.com a écrit :

> I don't report wind gust values/direction in the Current Conditions 
> section of my Seasons skin (version 4.6.2) but in the Statistics 
> (previously High/Low) section I've always had a Max Wind entry with both 
> speed and direction reported. Since 4.6.2 the direction is reported as N/A 
> so I've followed this thread and replaced the wxxtypes.py file with the new 
> one from Tom but it doesn't seem to have made any difference to my Max Wind 
> entry. If you look at the Statistics report below it still shows N/A for 
> Max Wind degrees for Day and Week but for Month and Year (presumably data 
> from 4.5.1) a degree value is reported.
>
> [image: Max Wind.jpg]
> Any suggestions?
>
> Paul
> On Sunday, 13 February 2022 at 15:04:26 UTC asla...@gmail.com wrote:
>
>> Brilliant, now it work just fine.
>> Thanks a lot.
>>
>> On Sunday, February 13, 2022 at 3:28:45 PM UTC+1 remy.l...@gmail.com 
>> wrote:
>>
>>> Yes !! Thank-you Tom it works great now :
>>>
>>> [image: Capture d’écran de 2022-02-13 15-26-27.png]
>>> Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a écrit :
>>>
>>>> I was able to replicate the problem. Pre V4.6, if windGustDir was 
>>>> missing, windDir was substituted. That behavior went away with v4.6. This 
>>>> patch restores it.
>>>>
>>>> Index: bin/weewx/wxxtypes.py
>>>> ===
>>>> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
>>>> --- a/bin/weewx/wxxtypes.py (revision 
>>>> 279bb450ab801c80a12b8ceadd0144e16c473bea)
>>>> +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
>>>> @@ -98,11 +98,18 @@
>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>  
>>>>  def calc_windGustDir(self, key, data, db_manager):
>>>> -# Return the current gust direction if windGust is non-zero, 
>>>> otherwise, None
>>>> -if 'windGust' not in data or 'windGustDir' not in data:
>>>> +"""If windGustDir is missing, substitute windDir.
>>>> +Set windGustDir to None if windGust is zero."""
>>>> +if 'windGust' not in data:
>>>>  raise weewx.CannotCalculate
>>>>  if self.force_null and data['windGust'] == 0:
>>>> +# windGust is zero. Force windGustDir to None
>>>>  val = None
>>>> +elif 'windGustDir' not in data:
>>>> +# windGustDir is missing. If available, substitute windDir.
>>>> +if 'windDir' not in data:
>>>> +raise weewx.CannotCalculate
>>>> +val = data['windDir']
>>>>  else:
>>>>  val = data['windGustDir']
>>>>  return ValueTuple(val, 'degree_compass', 'group_direction')
>>>>
>>>> Commit 9dc4da8 
>>>> <https://github.com/weewx/weewx/commit/9dc4da86a260f01d8792ac93d12871a05bff572d>
>>>> . 
>>>>
>>>> If you want this right away, you can replace weewx/wxxtypes.py with this 
>>>> version 
>>>> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxxtypes.py>
>>>> .
>>>>
>>>>
>>>>
>>>> On Sun, Feb 13, 2022 at 1:38 AM Remy Lavabre  
>>>> wrote:
>>>>
>>>>>
>>>>> [image: Capture d’écran de 2022-02-13 10-14-16.png]
>>>>>
>>>>> Same problem for me !
>>>>> Since weewx 4.6.x windGustDir is always N/A but the value is correct.
>>>>> I never had this problem before with 4.5.x or before... Only since 
>>>>> 4.6.x
>>>>>
>>>>> WindGustDir is always None in loop package values :
>>>>>
>>>>>
>>>>> LOOP:   2022-02-13 10:32:17 CET (1644744737) 'altimeter': 
>>>>> '30.122934097139712', 'appTemp': '45.455613403122314', 'barometer': 
>>>>> '30.14900779712183', 'beaufort': '1', 'cloudbase': '3288.4136917377255', 
>>>>> 'dateTime': '1644744737', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
>>>>> 'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
>>>>> 'extraHumid4':

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

Yes !! Thank-you Tom it works great now :

[image: Capture d’écran de 2022-02-13 15-26-27.png]
Le dimanche 13 février 2022 à 14:33:57 UTC+1, tke...@gmail.com a écrit :

> I was able to replicate the problem. Pre V4.6, if windGustDir was missing, 
> windDir was substituted. That behavior went away with v4.6. This patch 
> restores it.
>
> Index: bin/weewx/wxxtypes.py
> ===
> diff --git a/bin/weewx/wxxtypes.py b/bin/weewx/wxxtypes.py
> --- a/bin/weewx/wxxtypes.py (revision 
> 279bb450ab801c80a12b8ceadd0144e16c473bea)
> +++ b/bin/weewx/wxxtypes.py (date 1644758479921)
> @@ -98,11 +98,18 @@
>  return ValueTuple(val, 'degree_compass', 'group_direction')
>  
>  def calc_windGustDir(self, key, data, db_manager):
> -# Return the current gust direction if windGust is non-zero, 
> otherwise, None
> -if 'windGust' not in data or 'windGustDir' not in data:
> +"""If windGustDir is missing, substitute windDir.
> +Set windGustDir to None if windGust is zero."""
> +if 'windGust' not in data:
>  raise weewx.CannotCalculate
>  if self.force_null and data['windGust'] == 0:
> +# windGust is zero. Force windGustDir to None
>  val = None
> +elif 'windGustDir' not in data:
> +# windGustDir is missing. If available, substitute windDir.
> +if 'windDir' not in data:
> +raise weewx.CannotCalculate
> +val = data['windDir']
>  else:
>  val = data['windGustDir']
>  return ValueTuple(val, 'degree_compass', 'group_direction')
>
> Commit 9dc4da8 
> <https://github.com/weewx/weewx/commit/9dc4da86a260f01d8792ac93d12871a05bff572d>
> . 
>
> If you want this right away, you can replace weewx/wxxtypes.py with this 
> version 
> <https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/wxxtypes.py>
> .
>
>
>
> On Sun, Feb 13, 2022 at 1:38 AM Remy Lavabre  wrote:
>
>>
>> [image: Capture d’écran de 2022-02-13 10-14-16.png]
>>
>> Same problem for me !
>> Since weewx 4.6.x windGustDir is always N/A but the value is correct.
>> I never had this problem before with 4.5.x or before... Only since 4.6.x
>>
>> WindGustDir is always None in loop package values :
>>
>>
>> LOOP:   2022-02-13 10:32:17 CET (1644744737) 'altimeter': 
>> '30.122934097139712', 'appTemp': '45.455613403122314', 'barometer': 
>> '30.14900779712183', 'beaufort': '1', 'cloudbase': '3288.4136917377255', 
>> 'dateTime': '1644744737', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
>> 'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
>> 'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
>> 'extraHumid7': 'None', 'extraTemp1': '51.984', 'extraTemp2': 
>> '51.984', 'extraTemp3': 'None', 'extraTemp4': 'None', 
>> 'extraTemp5': 'None', 'extraTemp6': 'None', 'extraTemp7': 'None', 
>> 'heatindex': '46.886001', 'humidex': '48.74', 'inDewpoint': 
>> '52.863712008361716', 'inHumidity': '52', 'inTemp': '71.42', 'maxSolarRad': 
>> '326.89345093846424', 'outHumidity': '76', 'outTemp': '48.74', 'pressure': 
>> '28.3723877', 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 
>> 'UV': '0', 'windchill': '48.74', *'windDir': '123*', '*windGust': 
>> '2.4233536729342466', 'windGustDir': 'None',* 'windrun': 'None', 
>> *'windSpeed': 
>> '2.4233536729342466'*
>> LOOP:   2022-02-13 10:32:29 CET (1644744749) 'altimeter': 
>> '30.122934097139712', 'appTemp': '44.055613403122315', 'barometer': 
>> '30.14900779712183', 'beaufort': '2', 'cloudbase': '3288.4136917377255', 
>> 'dateTime': '1644744749', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
>> 'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
>> 'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
>> 'extraHumid7': 'None', 'extraTemp1': '51.984', 'extraTemp2': 
>> '51.984', 'extraTemp3': 'None', 'extraTemp4': 'None', 
>> 'extraTemp5': 'None', 'extraTemp6': 'None', 'extraTemp7': 'None', 
>> 'heatindex': '46.886001', 'humidex': '48.74', 'inDewpoint': 
>> '52.863712008361716', 'inHumidity': '52', 'inTemp': '71.42', 'maxSolarRad': 
>> '327.35927830102435', 'outHumidity': '76', 'outTemp': '48.74', 'pressure': 
>> '28.3723877', 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 
>> 'UV': '0', 'windchill': '46.79476438640812', '*windDir': '151',* 
>> *'windGust': 
>> '7.33219829246772', 'windGustDir': 'None',* 'windr

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

[image: Capture d’écran de 2022-02-13 10-14-16.png]

Same problem for me !
Since weewx 4.6.x windGustDir is always N/A but the value is correct.
I never had this problem before with 4.5.x or before... Only since 4.6.x

WindGustDir is always None in loop package values :


LOOP:   2022-02-13 10:32:17 CET (1644744737) 'altimeter': 
'30.122934097139712', 'appTemp': '45.455613403122314', 'barometer': 
'30.14900779712183', 'beaufort': '1', 'cloudbase': '3288.4136917377255', 
'dateTime': '1644744737', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
'extraHumid7': 'None', 'extraTemp1': '51.984', 'extraTemp2': 
'51.984', 'extraTemp3': 'None', 'extraTemp4': 'None', 
'extraTemp5': 'None', 'extraTemp6': 'None', 'extraTemp7': 'None', 
'heatindex': '46.886001', 'humidex': '48.74', 'inDewpoint': 
'52.863712008361716', 'inHumidity': '52', 'inTemp': '71.42', 'maxSolarRad': 
'326.89345093846424', 'outHumidity': '76', 'outTemp': '48.74', 'pressure': 
'28.3723877', 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 
'UV': '0', 'windchill': '48.74', *'windDir': '123*', '*windGust': 
'2.4233536729342466', 'windGustDir': 'None',* 'windrun': 'None', *'windSpeed': 
'2.4233536729342466'*
LOOP:   2022-02-13 10:32:29 CET (1644744749) 'altimeter': 
'30.122934097139712', 'appTemp': '44.055613403122315', 'barometer': 
'30.14900779712183', 'beaufort': '2', 'cloudbase': '3288.4136917377255', 
'dateTime': '1644744749', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
'extraHumid7': 'None', 'extraTemp1': '51.984', 'extraTemp2': 
'51.984', 'extraTemp3': 'None', 'extraTemp4': 'None', 
'extraTemp5': 'None', 'extraTemp6': 'None', 'extraTemp7': 'None', 
'heatindex': '46.886001', 'humidex': '48.74', 'inDewpoint': 
'52.863712008361716', 'inHumidity': '52', 'inTemp': '71.42', 'maxSolarRad': 
'327.35927830102435', 'outHumidity': '76', 'outTemp': '48.74', 'pressure': 
'28.3723877', 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 
'UV': '0', 'windchill': '46.79476438640812', '*windDir': '151',* *'windGust': 
'7.33219829246772', 'windGustDir': 'None',* 'windrun': 'None', *'windSpeed': 
'4.908844619533474'*
LOOP:   2022-02-13 10:32:41 CET (1644744761) 'altimeter': 
'30.122934097139712', 'appTemp': '44.055613403122315', 'barometer': 
'30.14900779712183', 'beaufort': '2', 'cloudbase': '3288.4136917377255', 
'dateTime': '1644744761', 'dayRain': '0.0', 'dewpoint': '41.36', 'ET': 
'None', 'extraHumid1': '65', 'extraHumid2': '91', 'extraHumid3': 'None', 
'extraHumid4': 'None', 'extraHumid5': 'None', 'extraHumid6': 'None', 
'extraHumid7': 'None', 'extraTemp1': '51.984', 'extraTemp2': 
'51.984', 'extraTemp3': 'None', 'extraTemp4': 'None', 
'extraTemp5': 'None', 'extraTemp6': 'None', 'extraTemp7': 'None', 
'heatindex': '46.886001', 'humidex': '48.74', 'inDewpoint': 
'52.863712008361716', 'inHumidity': '52', 'inTemp': '71.42', 'maxSolarRad': 
'327.8246605889759', 'outHumidity': '76', 'outTemp': '48.74', 'pressure': 
'28.3723877', 'rain': '0.0', 'rainRate': '0.0', 'usUnits': '1', 
'UV': '0', 'windchill': '46.79476438640812', '*windDir': '109'*, *'windGust': 
'7.829296481787566', 'windGustDir': 'None'*, 'windrun': 'None', '*windSpeed': 
'4.908844619533474'*


Le samedi 12 février 2022 à 19:23:27 UTC+1, asla...@gmail.com a écrit :

> The result with a couple of LOOP records.
> Both windGust and windGustDir occur in both REC and Loop records.
>
> REC:2022-02-12 19:15:49 CET (1644689749) 'altimeter': 
> '29.447857403881475', 'appTemp': '20.60149362123522', 'barometer': 
> '29.56391226224894', 'cloudbase': '3549.153942263896', 'dateTime': 
> '1644689749', 'delay': '10', 'dewpoint': '28.364486445406747', 'ET': 
> 'None', 'heatindex': '32.36', 'humidex': '32.36', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'interval': '10', 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': 
> '32.36', 'outTempBatteryStatus': '0', 'pressure': '26.733497683750002', 
> 'ptr': '38208', 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 
> 'rainTotal': '104.33', 'rxCheckPercent': '100', 'status': '0', 
> 'usUnits': '1', 'UV': 'None', 'windchill': '22.558136878652178', 'windDir': 
> '202.5', 'windGust': '15.882287148769064', 'windGustDir': 'None', 
> 'windrun': '2.274224216138293', 'windSpeed': '13.645345296829756'
> LOOP:   2022-02-12 19:19:05 CET (1644689945) 'altimeter': 
> '29.444663747054953', 'appTemp': '18.256881727966974', 'barometer': 
> '29.56173534294736', 'cloudbase': '3548.394255363211', 'dateTime': 
> '1644689945', 'delay': '3', 'dewpoint': '28.187829067769762', 'ET': 'None', 
> 'heatindex': '32.18', 

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

[image: Capture d’écran de 2022-02-13 10-14-16.png]
Same problem for me !
Since weewx 4.6.x windGustDir is always N/A but the value is correct.
I never had this problem before with 4.5.x or before... Only since 4.6.x

Would it be possible to tell me how to get the loop packages so that I can 
post them as well? -> I don't know how to get their raw values...
thank you



Le samedi 12 février 2022 à 19:23:27 UTC+1, asla...@gmail.com a écrit :

> The result with a couple of LOOP records.
> Both windGust and windGustDir occur in both REC and Loop records.
>
> REC:2022-02-12 19:15:49 CET (1644689749) 'altimeter': 
> '29.447857403881475', 'appTemp': '20.60149362123522', 'barometer': 
> '29.56391226224894', 'cloudbase': '3549.153942263896', 'dateTime': 
> '1644689749', 'delay': '10', 'dewpoint': '28.364486445406747', 'ET': 
> 'None', 'heatindex': '32.36', 'humidex': '32.36', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'interval': '10', 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': 
> '32.36', 'outTempBatteryStatus': '0', 'pressure': '26.733497683750002', 
> 'ptr': '38208', 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 
> 'rainTotal': '104.33', 'rxCheckPercent': '100', 'status': '0', 
> 'usUnits': '1', 'UV': 'None', 'windchill': '22.558136878652178', 'windDir': 
> '202.5', 'windGust': '15.882287148769064', 'windGustDir': 'None', 
> 'windrun': '2.274224216138293', 'windSpeed': '13.645345296829756'
> LOOP:   2022-02-12 19:19:05 CET (1644689945) 'altimeter': 
> '29.444663747054953', 'appTemp': '18.256881727966974', 'barometer': 
> '29.56173534294736', 'cloudbase': '3548.394255363211', 'dateTime': 
> '1644689945', 'delay': '3', 'dewpoint': '28.187829067769762', 'ET': 'None', 
> 'heatindex': '32.18', 'humidex': '32.18', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': '32.18', 
> 'outTempBatteryStatus': '0', 'pressure': '26.730544685', 'ptr': '38224', 
> 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
> '104.33', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
> '1', 'UV': 'None', 'windchill': '20.989026611354667', 'windDir': '202.5', 
> 'windGust': '19.68508829706588', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '17.448146445126575'
> LOOP:   2022-02-12 19:20:06 CET (1644690006) 'altimeter': 
> '29.441470085033213', 'appTemp': '22.918881727966976', 'barometer': 
> '29.558469574570985', 'cloudbase': '3548.394255363211', 'dateTime': 
> '1644690006', 'delay': '3', 'dewpoint': '28.187829067769762', 'ET': 'None', 
> 'heatindex': '32.18', 'humidex': '32.18', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': '32.18', 
> 'outTempBatteryStatus': '0', 'pressure': '26.72759168625', 'ptr': '38224', 
> 'radiation': 'None', 'rain': '0.0', 'rainRate': '0.0', 'rainTotal': 
> '104.33', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
> '1', 'UV': 'None', 'windchill': '24.387120697115183', 'windDir': '180.0', 
> 'windGust': '11.408403444890455', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '9.171461592951148'
>
> On Saturday, February 12, 2022 at 5:25:08 PM UTC+1 tke...@gmail.com wrote:
>
>> Could you do the same again, except this time show the LOOP data as well? 
>>
>> I'm not exactly sure what's happening, but my operating theory is that 
>> windGust and windDir never appear in the same LOOP packet. When the 
>> software sees windGust, but no windGustDir, it looks to substitute windDir, 
>> but it's not available. We can tell if this theory is correct by looking at 
>> the LOOP packets.
>>
>> On Sat, Feb 12, 2022 at 6:05 AM Tom Keffer  wrote:
>>
>>> Sorry, yes, that's what I meant. If windGustDir is missing, it should 
>>> substitute windDir in its place.
>>>
>>> Let me think about this for a bit.
>>>
>>> On Sat, Feb 12, 2022 at 5:59 AM Aslak Vaa  wrote:
>>>
 Here is the result from running  weewxd  from the command line:

 REC:2022-02-12 14:45:49 CET (1644673549) 'altimeter': 
 '29.559632125170864', 'appTemp': '21.79815080002', 'barometer': 
 '29.68039690383254', 'cloudbase': '3612.989261474405', 'dateTime': 
 '1644673549', 'delay': '10', 'dewpoint': '27.72361104088051', 'ET': 
 'None', 
 'heatindex': '32.0', 'humidex': '32.0', 'inDewpoint': 
 '20.331537695862405', 
 'inHumidity': '40.0', 'inTemp': '42.984', 'interval': '10', 
 'maxSolarRad': '123.63840457180561', 'outHumidity': '84.0', 'outTemp': 
 '32.0', 'outTempBatteryStatus': '0', 'pressure': '26.83685264004', 
 'ptr': '37776', 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 
 'rainTotal': '104.33', 'rxCheckPercent': '100', 'status': '0', 
 'usUnits': '1', 'UV': 'None', 'windchill': '23.36195892493', 

Re: [weewx-user] windGustDir is always set to NULL in database after upgrating to weewx version 4.6.0/4.6.2

[Remy Lavabre]

Same problem for me !
Since weewx 4.6.x windGustDir is always N/A.
Nevers add this problem before with 4.5.x or later...

Le samedi 12 février 2022 à 19:23:27 UTC+1, asla...@gmail.com a écrit :

> The result with a couple of LOOP records.
> Both windGust and windGustDir occur in both REC and Loop records.
>
> REC:2022-02-12 19:15:49 CET (1644689749) 'altimeter': 
> '29.447857403881475', 'appTemp': '20.60149362123522', 'barometer': 
> '29.56391226224894', 'cloudbase': '3549.153942263896', 'dateTime': 
> '1644689749', 'delay': '10', 'dewpoint': '28.364486445406747', 'ET': 
> 'None', 'heatindex': '32.36', 'humidex': '32.36', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'interval': '10', 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': 
> '32.36', 'outTempBatteryStatus': '0', 'pressure': '26.733497683750002', 
> 'ptr': '38208', 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 
> 'rainTotal': '104.33', 'rxCheckPercent': '100', 'status': '0', 
> 'usUnits': '1', 'UV': 'None', 'windchill': '22.558136878652178', 'windDir': 
> '202.5', 'windGust': '15.882287148769064', 'windGustDir': 'None', 
> 'windrun': '2.274224216138293', 'windSpeed': '13.645345296829756'
> LOOP:   2022-02-12 19:19:05 CET (1644689945) 'altimeter': 
> '29.444663747054953', 'appTemp': '18.256881727966974', 'barometer': 
> '29.56173534294736', 'cloudbase': '3548.394255363211', 'dateTime': 
> '1644689945', 'delay': '3', 'dewpoint': '28.187829067769762', 'ET': 'None', 
> 'heatindex': '32.18', 'humidex': '32.18', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': '32.18', 
> 'outTempBatteryStatus': '0', 'pressure': '26.730544685', 'ptr': '38224', 
> 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 'rainTotal': 
> '104.33', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
> '1', 'UV': 'None', 'windchill': '20.989026611354667', 'windDir': '202.5', 
> 'windGust': '19.68508829706588', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '17.448146445126575'
> LOOP:   2022-02-12 19:20:06 CET (1644690006) 'altimeter': 
> '29.441470085033213', 'appTemp': '22.918881727966976', 'barometer': 
> '29.558469574570985', 'cloudbase': '3548.394255363211', 'dateTime': 
> '1644690006', 'delay': '3', 'dewpoint': '28.187829067769762', 'ET': 'None', 
> 'heatindex': '32.18', 'humidex': '32.18', 'inDewpoint': 
> '20.586469406020147', 'inHumidity': '41.0', 'inTemp': '42.625', 
> 'maxSolarRad': '0.0', 'outHumidity': '85.0', 'outTemp': '32.18', 
> 'outTempBatteryStatus': '0', 'pressure': '26.72759168625', 'ptr': '38224', 
> 'radiation': 'None', 'rain': '0.0', 'rainRate': '0.0', 'rainTotal': 
> '104.33', 'rxCheckPercent': '100', 'status': '0', 'usUnits': 
> '1', 'UV': 'None', 'windchill': '24.387120697115183', 'windDir': '180.0', 
> 'windGust': '11.408403444890455', 'windGustDir': 'None', 'windrun': 'None', 
> 'windSpeed': '9.171461592951148'
>
> On Saturday, February 12, 2022 at 5:25:08 PM UTC+1 tke...@gmail.com wrote:
>
>> Could you do the same again, except this time show the LOOP data as well? 
>>
>> I'm not exactly sure what's happening, but my operating theory is that 
>> windGust and windDir never appear in the same LOOP packet. When the 
>> software sees windGust, but no windGustDir, it looks to substitute windDir, 
>> but it's not available. We can tell if this theory is correct by looking at 
>> the LOOP packets.
>>
>> On Sat, Feb 12, 2022 at 6:05 AM Tom Keffer  wrote:
>>
>>> Sorry, yes, that's what I meant. If windGustDir is missing, it should 
>>> substitute windDir in its place.
>>>
>>> Let me think about this for a bit.
>>>
>>> On Sat, Feb 12, 2022 at 5:59 AM Aslak Vaa  wrote:
>>>
 Here is the result from running  weewxd  from the command line:

 REC:2022-02-12 14:45:49 CET (1644673549) 'altimeter': 
 '29.559632125170864', 'appTemp': '21.79815080002', 'barometer': 
 '29.68039690383254', 'cloudbase': '3612.989261474405', 'dateTime': 
 '1644673549', 'delay': '10', 'dewpoint': '27.72361104088051', 'ET': 
 'None', 
 'heatindex': '32.0', 'humidex': '32.0', 'inDewpoint': 
 '20.331537695862405', 
 'inHumidity': '40.0', 'inTemp': '42.984', 'interval': '10', 
 'maxSolarRad': '123.63840457180561', 'outHumidity': '84.0', 'outTemp': 
 '32.0', 'outTempBatteryStatus': '0', 'pressure': '26.83685264004', 
 'ptr': '37776', 'radiation': 'None', 'rain': 'None', 'rainRate': '0.0', 
 'rainTotal': '104.33', 'rxCheckPercent': '100', 'status': '0', 
 'usUnits': '1', 'UV': 'None', 'windchill': '23.36195892493', 
 'windDir': 
 '225.0', 'windGust': '12.079486000472244', 'windGustDir': 'None', 
 'windrun': '1.7895534815514438', 'windSpeed': '10.737320889308663'

 Until version 4.6.0 the windGustDir was recorded in the database with a 
 

[weewx-user] Re: Problem since Weewx 4.6

[Remy Lavabre]

I've found my problem Thank you Vince !
The problems were in 2 extension file : lastrain.py and lastfrost.py (date 
of the last rain and frost and duration without rain and frost).


*Before :*
# Wrap our ts in a ValueHelper
last_rain_vt = (last_rain_ts, 'unix_epoch', 'group_time')
last_rain_vh = ValueHelper(last_rain_vt, 
formatter=self.generator.formatter, converter=self.generator.converter)

# next idea stolen with thanks from weewx station.py
# note this is delta time from 'now' not the last weewx db time
#  - weewx used time.time() but weewx-wd suggests timespan.stop()
delta_time = time.time() - last_rain_ts if last_rain_ts else None

# Wrap our ts in a ValueHelper
delta_time_vt = (delta_time, 'second', 'group_deltatime')
delta_time_vh = ValueHelper(delta_time_vt, 
formatter=self.generator.formatter, converter=self.generator.converter)

*AFTER :*
   # Wrap our ts in a ValueHelper
last_rain_vt = (last_rain_ts, 'unix_epoch', 'group_time')
last_rain_vh = ValueHelper(last_rain_vt, 
formatter=self.generator.formatter, converter=self.generator.converter)

# next idea stolen with thanks from weewx station.py
# note this is delta time from 'now' not the last weewx db time
#  - weewx used time.time() but weewx-wd suggests timespan.stop()
delta_time = time.time() - last_rain_ts if last_rain_ts else None

# Wrap our ts in a ValueHelper
delta_time_vt = (delta_time, 'second', 'group_deltatime')
delta_time_vh = ValueHelper(delta_time_vt, *context='long_delta',* 
formatter=self.generator.formatter, 
converter=self.generator.converter)

And now... ALL IS OK !!  THANK-YOU VERY MUCH VINCE ! ::-))
Le lundi 7 février 2022 à 20:30:39 UTC+1, Remy Lavabre a écrit :

> Thank you for your answer Vincent.
> Could you indicate me which python file exactly to add the New value 
> context='long_delta ? And where I must add this New value in the py file ?
> I have seen the article you indicate me but i did not understand what to 
> do...
> Than you . Cordialy vincent
> Le lundi 7 février 2022 à 18:36:06 UTC+1, vince a écrit :
>
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>> Ignoring template /etc/weewx/skins/Seasons2/index.html.tmpl
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>> Reason: %x format: an integer is required, not dict
>>
>> I saw this when I upgraded my system yesterday.
>>
>> The problem was my ancient custom extension broke due to group_deltatime 
>> API change in 4.6.0 - the fix is documented in 
>> https://weewx.com/docs/upgrading.htm#API_changes - all I did was add 
>> context='long_delta' to my python extension and restarted weewx and all was 
>> good again.
>>
>> On Monday, February 7, 2022 at 9:22:21 AM UTC-8 remy.l...@gmail.com 
>> wrote:
>>
>>> With the previous version 4.51, no problem since 1 year.
>>> Since 4.6.0 the records are good on the database, but I have errors in 
>>> the log file and the value in the "current conditions" of the skin Seasons 
>>> don't move.
>>> They remain frozen at the last known value with Weewx 4.5.1. In fact, 
>>> the Season skin no longer works but the data is correctly saved in the 
>>> database.
>>> Attached is the log file. I can't get my skin season to start again! :-((
>>> HELP !
>>>
>>> Feb  7 17:55:16 RPiMeteo weewx[29371] INFO weewx.restx: 
>>> Wunderground-PWS: Published record 2022-02-07 17:55:00 CET (1644252900)
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator: 
>>> Evaluation of template /etc/weewx/skins/Seasons2/index.html.tmpl failed 
>>> with exception ''
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>> Ignoring template /etc/weewx/skins/Seasons2/index.html.tmpl
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>> Reason: %x format: an integer is required, not dict
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>>  Traceback (most recent call last):
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generate
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>>  unicode_string = compiled_template.respond()
>>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>>File "_etc_weewx_skins_Seasons2_index_html_tmpl.py", line 259, in respond
>>> Feb  7 17:55:

[weewx-user] Re: Problem since Weewx 4.6

[Remy Lavabre]

Thank you for your answer Vincent.
Could you indicate me which python file exactly to add the New value 
context='long_delta ? And where I must add this New value in the py file ?
I have seen the article you indicate me but i did not understand what to 
do...
Than you . Cordialy vincent
Le lundi 7 février 2022 à 18:36:06 UTC+1, vince a écrit :

> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
> Ignoring template /etc/weewx/skins/Seasons2/index.html.tmpl
> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
> Reason: %x format: an integer is required, not dict
>
> I saw this when I upgraded my system yesterday.
>
> The problem was my ancient custom extension broke due to group_deltatime 
> API change in 4.6.0 - the fix is documented in 
> https://weewx.com/docs/upgrading.htm#API_changes - all I did was add 
> context='long_delta' to my python extension and restarted weewx and all was 
> good again.
>
> On Monday, February 7, 2022 at 9:22:21 AM UTC-8 remy.l...@gmail.com wrote:
>
>> With the previous version 4.51, no problem since 1 year.
>> Since 4.6.0 the records are good on the database, but I have errors in 
>> the log file and the value in the "current conditions" of the skin Seasons 
>> don't move.
>> They remain frozen at the last known value with Weewx 4.5.1. In fact, the 
>> Season skin no longer works but the data is correctly saved in the database.
>> Attached is the log file. I can't get my skin season to start again! :-((
>> HELP !
>>
>> Feb  7 17:55:16 RPiMeteo weewx[29371] INFO weewx.restx: Wunderground-PWS: 
>> Published record 2022-02-07 17:55:00 CET (1644252900)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator: 
>> Evaluation of template /etc/weewx/skins/Seasons2/index.html.tmpl failed 
>> with exception ''
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>> Ignoring template /etc/weewx/skins/Seasons2/index.html.tmpl
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>> Reason: %x format: an integer is required, not dict
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  Traceback (most recent call last):
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generate
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  unicode_string = compiled_template.respond()
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "_etc_weewx_skins_Seasons2_index_html_tmpl.py", line 259, in respond
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
>> _handleCheetahInclude
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "_etc_weewx_skins_Seasons2_current_inc.py", line 714, in respond
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/cheetahgenerator.py", line 816, in filter
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  filtered = six.text_type(val)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/units.py", line 1005, in __str__
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  s = self.toString()
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/units.py", line 998, in toString
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  s = self.formatter.toString(self.value_t, self.context, 
>> addLabel=addLabel,
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/units.py", line 688, in toString
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  s = self._to_string(val_t, context, addLabel, useThisFormat, 
>> None_string, localize)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/units.py", line 748, in _to_string
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  val_str = self.delta_secs_to_string(val_t[0], format_string)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/share/weewx/weewx/units.py", line 796, in delta_secs_to_string
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>  ans = locale.format_string(label_format, etime_dict)
>> Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
>>File "/usr/lib/python3.9/locale.py", line 223, in 

[weewx-user] Problem since Weewx 4.6

[Remy Lavabre]

With the previous version 4.51, no problem since 1 year.
Since 4.6.0 the records are good on the database, but I have errors in the 
log file and the value in the "current conditions" of the skin Seasons 
don't move.
They remain frozen at the last known value with Weewx 4.5.1. In fact, the 
Season skin no longer works but the data is correctly saved in the database.
Attached is the log file. I can't get my skin season to start again! :-((
HELP !

Feb  7 17:55:16 RPiMeteo weewx[29371] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-02-07 17:55:00 CET (1644252900)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator: 
Evaluation of template /etc/weewx/skins/Seasons2/index.html.tmpl failed 
with exception ''
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
Ignoring template /etc/weewx/skins/Seasons2/index.html.tmpl
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
Reason: %x format: an integer is required, not dict
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
 Traceback (most recent call last):
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 344, in generate
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   unicode_string = compiled_template.respond()
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons2_index_html_tmpl.py", line 259, in respond
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
_handleCheetahInclude
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "_etc_weewx_skins_Seasons2_current_inc.py", line 714, in respond
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/cheetahgenerator.py", line 816, in filter
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   filtered = six.text_type(val)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 1005, in __str__
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   s = self.toString()
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 998, in toString
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   s = self.formatter.toString(self.value_t, self.context, 
addLabel=addLabel,
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 688, in toString
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   s = self._to_string(val_t, context, addLabel, useThisFormat, 
None_string, localize)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 748, in _to_string
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   val_str = self.delta_secs_to_string(val_t[0], format_string)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/share/weewx/weewx/units.py", line 796, in delta_secs_to_string
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   ans = locale.format_string(label_format, etime_dict)
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3.9/locale.py", line 223, in format_string
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   new_val.append(_format(perc.group(), val, grouping, monetary))
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
 File "/usr/lib/python3.9/locale.py", line 187, in _format
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:    
   formatted = percent % value
Feb  7 17:55:17 RPiMeteo weewx[29371] ERROR weewx.cheetahgenerator:  
 TypeError: %x format: an integer is required, not dict
Feb  7 17:55:17 RPiMeteo weewx[29371] INFO weewx.restx: WeatherCloud: 
Published record 2022-02-07 17:55:00 CET (1644252900)

-- 
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/bdf83c0f-6204-49c9-bd8c-8b5a64b0200cn%40googlegroups.com.

Re: [weewx-user] Run a script - with parameter? - via WeeWX?

[Remy LAVABRE]

Multi_alarm.py is a super python program for different test alarm on each
loop pack et {ex outTemp<0, rainRate>0, inTemp<17 etc. etc}.
If you want only battery power test, perhaps this is more for you... :

https://github.com/weewx/weewx/blob/master/examples/lowBattery.py

If you want I can send you multi alarm.py but i made little change in the
code to have a different delay between 2 alarms for each type of alert {ex
36000 seconds for inTemp<17 but 3600 seconds for rainRate>1 etc. Etc}
In the original you specify a delay in weewx.conf and the delay is the same
for each alarm you program




Le mar. 8 juin 2021 à 18:13, Rob Cranfill  a écrit :

> Remy, I am sorry if I am missing the obvious - where do I find
> Multi_alarm.py?
>
> On Monday, June 7, 2021 at 10:31:28 AM UTC-7 remy.l...@gmail.com wrote:
>
>> Hello Rob.
>> Multi_alarm.py is perfect for the job !
>> And the battery will be checked at each loop packet record !
>> After, you can sens à mail or SMS or... all what you want !
>> ;-)
>>
>>
>> Le lun. 7 juin 2021 à 18:27, Rob Cranfill  a écrit :
>>
>>> Apologies if this has been asked - I searched without luck - let me know
>>> where to look.
>>>
>>> I would like to have WeeWX tell me when my weather station's battery is
>>> low - perhaps running a script once a day that can check the battery status
>>> and send me mail if it's low. (All kinds of weirdness happens when it gets
>>> that way, which I always forget about and freak out thinking the whole
>>> system is boofed, when it's really only a low battery.)
>>>
>>> Currently I have a cron job that "screen scrapes" the main page, where
>>> the Sensor Status / Battery Status / Transmitter Battery field has the info
>>> I want  ("OK", or "LOW", I think). But that's kinda clunky.
>>>
>>> The best I can come up with so far is to configure the system to also
>>> output a simple HTML page - or maybe just a text file? - with that one
>>> value in it, that will simplify the parsing/scraping, but that's still not
>>> very elegant.
>>>
>>> Or is this just beyond the scope of WeeWX?
>>>
>>> Thanks for any suggestions,
>>>  Rob in Seattle
>>>
>>> --
>>> 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/633505d8-0882-40c0-9bc9-7e8f7118cac7n%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/08a11db7-2cf9-4029-94b3-f8d13eb656f5n%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/CADhm9YeeStdVYHcNDvLzOtNegVc6CRsZW0Yu0qYyPnd0XC-Z%2Bw%40mail.gmail.com.

Re: [weewx-user] Run a script - with parameter? - via WeeWX?

[Remy LAVABRE]

Hello Rob.
Multi_alarm.py is perfect for the job !
And the battery will be checked at each loop packet record !
After, you can sens à mail or SMS or... all what you want !
;-)


Le lun. 7 juin 2021 à 18:27, Rob Cranfill  a écrit :

> Apologies if this has been asked - I searched without luck - let me know
> where to look.
>
> I would like to have WeeWX tell me when my weather station's battery is
> low - perhaps running a script once a day that can check the battery status
> and send me mail if it's low. (All kinds of weirdness happens when it gets
> that way, which I always forget about and freak out thinking the whole
> system is boofed, when it's really only a low battery.)
>
> Currently I have a cron job that "screen scrapes" the main page, where the
> Sensor Status / Battery Status / Transmitter Battery field has the info I
> want  ("OK", or "LOW", I think). But that's kinda clunky.
>
> The best I can come up with so far is to configure the system to also
> output a simple HTML page - or maybe just a text file? - with that one
> value in it, that will simplify the parsing/scraping, but that's still not
> very elegant.
>
> Or is this just beyond the scope of WeeWX?
>
> Thanks for any suggestions,
>  Rob in Seattle
>
> --
> 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/633505d8-0882-40c0-9bc9-7e8f7118cac7n%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/CADhm9YfhP9MpukMumBp6FAMz4Tht%3D67bpH7LqeZSugjqMY2%3DhA%40mail.gmail.com.

Re: [weewx-user] Direction of the maximum wind value

[Remy Lavabre]

gt; On Friday, June 4, 2021 at 5:07:09 AM UTC-3 remy.l...@gmail.com wrote:
>>>>
>>>>> Thanks for the quick response! And it actually works :-)))
>>>>>
>>>>> Two slight corrections are however to be made to work fine :
>>>>>
>>>>> -1 / You forgot the "$" at timestamp. We must read 
>>>>> $current(*$*timestamp=$t).windDir 
>>>>> instead of $current(timestamp=$t).windDir
>>>>> -2 / The time format must be in raw to work. We must read #set t = 
>>>>> $month.windSpeed.maxtime*.raw* instead of #set t = 
>>>>> $month.windSpeed.maxtime
>>>>>
>>>>> Aside from that it was a perfect solution !! Thanks again Tom
>>>>>
>>>>> Le jeudi 3 juin 2021 à 22:41:54 UTC+2, tke...@gmail.com a écrit :
>>>>>
>>>>>> You could do something like (NOT TESTED):
>>>>>>
>>>>>> #set t = $month.windSpeed.maxtime
>>>>>> The max wind speed this month is $month.windSpeed.max from 
>>>>>> direction $current(timestamp=$t).windDir at time $t.
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, Jun 3, 2021 at 8:38 AM Remy Lavabre  
>>>>>> wrote:
>>>>>>
>>>>>>> Good morning all,
>>>>>>>
>>>>>>> To have the maximum wind gust over a period this works very well and 
>>>>>>> also gives the time and date of this wind gust:
>>>>>>>
>>>>>>> Win Gust Max
>>>>>>> #for $archive in $archive_data
>>>>>>> >>>>>> "DarkRed">
>>>>>>>   
>>>>>>> $archive[1].wind.gustdir.ordinal_compass 
>>>>>>> ($archive[1].wind.gustdir.format(add_label=False)$unit.label.windDir)
>>>>>>> - $archive[1].wind.max.format(add_label=False)
>>>>>>> $archive[1].wind.maxtime
>>>>>>> 
>>>>>>>
>>>>>>>
>>>>>>> Over the same period, I get the maximum wind value (not the gust) 
>>>>>>> with the following formula:
>>>>>>>
>>>>>>>   
>>>>>>> 
>>>>>>> $archive[1].windSpeed.max.format(add_label=False)
>>>>>>> >>>>>> class="timestamp">$archive[1].windSpeed.maxtime
>>>>>>>
>>>>>>> My problem is that I cannot recover the direction of the wind during 
>>>>>>> this maximum :
>>>>>>>
>>>>>>> $archive[1].windDir.ordinal_compass ( $archive[1].windSpeed.max  ) 
>>>>>>> does not work ! :-(
>>>>>>>
>>>>>>> How should I do it?
>>>>>>> Thank you
>>>>>>>
>>>>>>>
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "weewx-user" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>> send an email to weewx-user+...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/weewx-user/85fa1519-24ba-45a0-bc45-20bf18a9b9ben%40googlegroups.com
>>>>>>>  
>>>>>>> <https://groups.google.com/d/msgid/weewx-user/85fa1519-24ba-45a0-bc45-20bf18a9b9ben%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>> .
>>>>>>>
>>>>>> -- 
>>>> You received this message because you are subscribed to the Google 
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>> an email to weewx-user+...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/weewx-user/e2555ed6-93cb-4081-9ad1-9c56a0379b6dn%40googlegroups.com
>>>>  
>>>> <https://groups.google.com/d/msgid/weewx-user/e2555ed6-93cb-4081-9ad1-9c56a0379b6dn%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>>
>>> -- 
>>>
>>> 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/w8QBuJtV6Tc/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/CAPq0zEB2b1DJ%2BOPZkURqjoyuRUSnkG4OLRNqM6iKSH%2BOm2xGQA%40mail.gmail.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEB2b1DJ%2BOPZkURqjoyuRUSnkG4OLRNqM6iKSH%2BOm2xGQA%40mail.gmail.com?utm_medium=email_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/ee1d9e28-62ff-4de6-9abe-431a0911aa95n%40googlegroups.com.

Re: [weewx-user] Direction of the maximum wind value

[Remy Lavabre]

*In the same genre but for the rain (not rain rate) ... Is it possible to 
recover in Seasons on a period, the day of the maximum rain (the 
$day.rain.sum maximum) ?*

  $archive[1].rain.maxtime
  $archive[1].rain.max.format(add_label=False)
  $archive[1].rain.maxtime

*Gives the day and time of the maximum value of rain in the loop packets 
... OK no problem, but it does not give me the day with the maximum rain... 
:-( *


  $archive[1].rain.sum.format(add_label=False)

*Gives the total rainfall over the period ... OK not always the maximum 
rain day... :-(*

*How to get the maxi day rainfall over the period considered ??*

*Thank-you...*

Le samedi 5 juin 2021 à 21:46:35 UTC+2, WindnFog a écrit :

> Thanks, Tom.  I always take the longest path between two point!
>
> - Paul VE1DX
>
>
> On 2021-06-05 4:32 p.m., Tom Keffer wrote:
>
> You're making this a lot more complicated than it needs to be. Try this:
>
> #set $mnth=$month.dateTime.format("%B")
> Minimum temp for $mnth was $month.outTemp.min on 
> $month.outTemp.mintime.format("%d %b at %H:%M")
> 
> Maximum temp for $mnth was $month.outTemp.max on 
> $month.outTemp.maxtime.format("%d %b at %H:%M")
> 
> Maximum 10-min avg. wind speed for $mnth was $month.windSpeed.max
> 
> #set t = $month.windSpeed.maxtime
> (From the $current($timestamp=$t.raw).windDir.ordinal_compass on 
> $t.format("%d %b at %H:%M"))
>
>
> Take a look through all the formatting options in the Customizing Guide. 
> There's no need to do strftime manipulations.
>
> On Sat, Jun 5, 2021 at 12:13 PM WindnFog  wrote:
>
>> I embellished this a bit by adding the temperature ranges:
>>
>> #set t = $month.outTemp.mintime.raw
>> #import time
>> #set mnth=time.strftime("%B", time.localtime(t))
>> #set str_t=time.strftime("%d %b at %H:%M", time.localtime(t))
>> Minimum temp for $mnth was $month.outTemp.min on $str_t
>> 
>> #set t = $month.outTemp.maxtime.raw
>> #set str_t=time.strftime("%d %b at %H:%M", time.localtime(t))
>> Maximum temp for $mnth was $month.outTemp.max on $str_t
>> 
>> #set t = $month.windSpeed.maxtime.raw
>> #set str_t=time.strftime("%d %b at %H:%M", time.localtime(t))
>> Maximum 10-min avg. wind speed for $mnth was $month.windSpeed.max 
>> 
>>(From the $current($timestamp=$t).windDir.ordinal_compass on 
>> $str_t)
>>
>> - Paul VE1DX
>>
>> On Friday, June 4, 2021 at 5:07:09 AM UTC-3 remy.l...@gmail.com wrote:
>>
>>> Thanks for the quick response! And it actually works :-)))
>>>
>>> Two slight corrections are however to be made to work fine :
>>>
>>> -1 / You forgot the "$" at timestamp. We must read 
>>> $current(*$*timestamp=$t).windDir 
>>> instead of $current(timestamp=$t).windDir
>>> -2 / The time format must be in raw to work. We must read #set t = 
>>> $month.windSpeed.maxtime*.raw* instead of #set t = 
>>> $month.windSpeed.maxtime
>>>
>>> Aside from that it was a perfect solution !! Thanks again Tom
>>>
>>> Le jeudi 3 juin 2021 à 22:41:54 UTC+2, tke...@gmail.com a écrit :
>>>
>>>> You could do something like (NOT TESTED):
>>>>
>>>> #set t = $month.windSpeed.maxtime
>>>> The max wind speed this month is $month.windSpeed.max from direction 
>>>> $current(timestamp=$t).windDir at time $t.
>>>>
>>>>
>>>>
>>>> On Thu, Jun 3, 2021 at 8:38 AM Remy Lavabre  
>>>> wrote:
>>>>
>>>>> Good morning all,
>>>>>
>>>>> To have the maximum wind gust over a period this works very well and 
>>>>> also gives the time and date of this wind gust:
>>>>>
>>>>> Win Gust Max
>>>>> #for $archive in $archive_data
>>>>> >>>> "DarkRed">
>>>>>   
>>>>> $archive[1].wind.gustdir.ordinal_compass 
>>>>> ($archive[1].wind.gustdir.format(add_label=False)$unit.label.windDir)
>>>>> - $archive[1].wind.max.format(add_label=False)
>>>>> $archive[1].wind.maxtime
>>>>> 
>>>>>
>>>>>
>>>>> Over the same period, I get the maximum wind value (not the gust) with 
>>>>> the following formula:
>>>>>
>>>>&g

Re: [weewx-user] Direction of the maximum wind value

[Remy Lavabre]

Thanks for the quick response! And it actually works :-)))

Two slight corrections are however to be made to work fine :

-1 / You forgot the "$" at timestamp. We must read 
$current(*$*timestamp=$t).windDir 
instead of $current(timestamp=$t).windDir
-2 / The time format must be in raw to work. We must read #set t = 
$month.windSpeed.maxtime*.raw* instead of #set t = $month.windSpeed.maxtime

Aside from that it was a perfect solution !! Thanks again Tom

Le jeudi 3 juin 2021 à 22:41:54 UTC+2, tke...@gmail.com a écrit :

> You could do something like (NOT TESTED):
>
> #set t = $month.windSpeed.maxtime
> The max wind speed this month is $month.windSpeed.max from direction 
> $current(timestamp=$t).windDir at time $t.
>
>
>
> On Thu, Jun 3, 2021 at 8:38 AM Remy Lavabre  wrote:
>
>> Good morning all,
>>
>> To have the maximum wind gust over a period this works very well and also 
>> gives the time and date of this wind gust:
>>
>> Win Gust Max
>> #for $archive in $archive_data
>> 
>>   
>> $archive[1].wind.gustdir.ordinal_compass 
>> ($archive[1].wind.gustdir.format(add_label=False)$unit.label.windDir)
>> - $archive[1].wind.max.format(add_label=False)
>> $archive[1].wind.maxtime
>> 
>>
>>
>> Over the same period, I get the maximum wind value (not the gust) with 
>> the following formula:
>>
>>   
>> $archive[1].windSpeed.max.format(add_label=False)
>> > class="timestamp">$archive[1].windSpeed.maxtime
>>
>> My problem is that I cannot recover the direction of the wind during this 
>> maximum :
>>
>> $archive[1].windDir.ordinal_compass ( $archive[1].windSpeed.max  ) does 
>> not work ! :-(
>>
>> How should I do it?
>> Thank you
>>
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/85fa1519-24ba-45a0-bc45-20bf18a9b9ben%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/85fa1519-24ba-45a0-bc45-20bf18a9b9ben%40googlegroups.com?utm_medium=email_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/0474055b-d3d9-4ac2-82f6-a19043dfef47n%40googlegroups.com.

[weewx-user] Direction of the maximum wind value

[Remy Lavabre]

Good morning all,

To have the maximum wind gust over a period this works very well and also 
gives the time and date of this wind gust:

Win Gust Max
#for $archive in $archive_data

  
$archive[1].wind.gustdir.ordinal_compass 
($archive[1].wind.gustdir.format(add_label=False)$unit.label.windDir)
- $archive[1].wind.max.format(add_label=False)
$archive[1].wind.maxtime



Over the same period, I get the maximum wind value (not the gust) with the 
following formula:

  
$archive[1].windSpeed.max.format(add_label=False)
$archive[1].windSpeed.maxtime

My problem is that I cannot recover the direction of the wind during this 
maximum :

$archive[1].windDir.ordinal_compass ( $archive[1].windSpeed.max  ) does not 
work ! :-(

How should I do it?
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/85fa1519-24ba-45a0-bc45-20bf18a9b9ben%40googlegroups.com.

[weewx-user] Problem with barometerRate WeeWX

[Remy Lavabre]

Hello,

I have a problem with using the barometerRate variable.

In skin :
$obs.label.barometerRate
$current.barometerRate

And the result in HTML is :
Barometer Change Rate ?'barometerRate'?

I don't understand why the "$current.barometerRate" variable is not 
reconize

Where is the problem ? (Weewx 4.5.1)
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/ce8d7b09-3916-47b6-8b33-c784b557c6f9n%40googlegroups.com.

Re: [weewx-user] FTP

[Remy LAVABRE]

Hi,
I have a problem to with the FTP option :

Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine:
ftpgenerator: (0): caught exception '': [SSL:
DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 Traceback (most recent call last):
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 n = ftp_data.run()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weeutil/ftpupload.py", line 128, in run
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 ftp_server.login(self.user, self.password)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ftplib.py", line 749, in login
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self.auth()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ftplib.py", line 761, in auth
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 server_hostname=self.host)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 session=session
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 853, in _create
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self.do_handshake()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self._sslobj.do_handshake()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine:
ftpgenerator: (1): caught exception '': [SSL:
DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 Traceback (most recent call last):
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 n = ftp_data.run()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weeutil/ftpupload.py", line 128, in run
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 ftp_server.login(self.user, self.password)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ftplib.py", line 749, in login
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self.auth()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ftplib.py", line 761, in auth
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 server_hostname=self.host)
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 412, in wrap_socket
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 session=session
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 853, in _create
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self.do_handshake()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/lib/python3.7/ssl.py", line 1117, in do_handshake
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 self._sslobj.do_handshake()
Jan 29 14:17:42 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 ssl.SSLError: [SSL: DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine:
ftpgenerator: (2): caught exception '': [SSL:
DH_KEY_TOO_SMALL] dh key too small (_ssl.c:1056)
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 Traceback (most recent call last):
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
 n = ftp_data.run()
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine: 
   File "/usr/share/weewx/weeutil/ftpupload.py", line 128, in run
Jan 29 14:17:43 RPiMeteo weewx[1429] ERROR weewx.reportengine: