[weewx-user] Re: Apt update source for weewx.

[didier....@gmail.com]

Hi again

Problem solved 

We need to re-import keys by this command:
curl -sSf 'https://weewx.com/keys.html' | sudo gpg --dearmor -o 
/etc/apt/trusted.gpg.d/weewx.gpg --yes

Le mercredi 28 février 2024 à 17:16:43 UTC+1, didier@gmail.com a écrit :

> Hi
>
> I have upgrade debian 10 to debian 11 bullseye, and I have 
> changed /etc/apt/sources.list.d/weewx.list  with:
> deb [arch=all] http://weewx.com/apt/python3 *buster InRelease*
> instead of deb [arch=all] http://weewx.com/apt/python3 *bullseye main*
>
> But after apt update I have a warning/error about a control of sign in due 
> to a no available public key (NO_PUBKEY E788768B9CB16E10)
>
> Where is my mistake?
>
> Thanks a lot
>
> Le samedi 2 juillet 2022 à 23:47:41 UTC+2, Peter Fletcher a écrit :
>
>> Thanks!
>>
>> On Saturday, July 2, 2022 at 5:38:23 PM UTC-4 matthew wall wrote:
>>
>>> On Saturday, July 2, 2022 at 4:14:37 PM UTC-4 Peter Fletcher wrote:
>>>
>>>> The installation instructions add 'http://weewx.com/apt/python3 
>>>> *buster* InRelease' to apt's list of sources for Debian installs, and 
>>>> this works.
>>>>
>>>
>>> you can replace 'buster' with whatever you want.
>>>
>>> we do not track specific debian (or ubuntu, or mint, or whatever) 
>>> releases.  basically we target two debian releases: squeeze (for python2) 
>>> and buster (for python3).
>>>
>>> the weewx python2 deb package first worked with debian 6 (squeeze), and 
>>> works with every subsequent debian release until the python2 packages are 
>>> no longer provided.
>>>
>>> the weewx python3 deb package first worked with debian 10 (buster) and 
>>> will continue to work with every subsequent debian release until debian 
>>> breaks the python3 packages.
>>>
>>> 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/f998f0fd-238d-4842-be60-231d325af07an%40googlegroups.com.

[weewx-user] Re: Apt update source for weewx.

[didier....@gmail.com]

Hi

I have upgrade debian 10 to debian 11 bullseye, and I have 
changed /etc/apt/sources.list.d/weewx.list  with:
deb [arch=all] http://weewx.com/apt/python3 *buster InRelease*
instead of deb [arch=all] http://weewx.com/apt/python3 *bullseye main*

But after apt update I have a warning/error about a control of sign in due 
to a no available public key (NO_PUBKEY E788768B9CB16E10)

Where is my mistake?

Thanks a lot

Le samedi 2 juillet 2022 à 23:47:41 UTC+2, Peter Fletcher a écrit :

> Thanks!
>
> On Saturday, July 2, 2022 at 5:38:23 PM UTC-4 matthew wall wrote:
>
>> On Saturday, July 2, 2022 at 4:14:37 PM UTC-4 Peter Fletcher wrote:
>>
>>> The installation instructions add 'http://weewx.com/apt/python3 *buster* 
>>> InRelease' to apt's list of sources for Debian installs, and this works.
>>>
>>
>> you can replace 'buster' with whatever you want.
>>
>> we do not track specific debian (or ubuntu, or mint, or whatever) 
>> releases.  basically we target two debian releases: squeeze (for python2) 
>> and buster (for python3).
>>
>> the weewx python2 deb package first worked with debian 6 (squeeze), and 
>> works with every subsequent debian release until the python2 packages are 
>> no longer provided.
>>
>> the weewx python3 deb package first worked with debian 10 (buster) and 
>> will continue to work with every subsequent debian release until debian 
>> breaks the python3 packages.
>>
>> 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/84f075bc-eb94-4fbb-858c-b731f385411fn%40googlegroups.com.

Re: [weewx-user] Error after ugrade debian 10 to debian 11

[didier....@gmail.com]

Thank's, 
after re-install paho-mqtt, I have updated information on my screen (I 
don't understand why this package has disappeared...)

But, on the Belchertown skin, celestial frame is not correct, bad data and 
detailed almanac link is missed

before upgrade
[image: before upgarde.jpg]

after upgrade
[image: after upgrade.jpg]
After upgrade, hours and % visible are the data of yesterday (date of my 
vmware snapshot )
Le lundi 28 février 2022 à 14:49:50 UTC+1, tke...@gmail.com a écrit :

> You need to install paho-mqtt. See the README 
> <https://github.com/matthewwall/weewx-mqtt> file for the MQTT extension.
>
> On Mon, Feb 28, 2022 at 2:56 AM didier@gmail.com  
> wrote:
>
>> Hi everybody
>>
>> I have upgraded my debian 10 (buster) to debian 11 (bullseye) following 
>> this procedure: 
>> https://ostechnix.com/upgrade-to-debian-11-bullseye-from-debian-10-buster/
>>
>>
>>1. During first step (10.4 to 10.11) it's ok but I have to replace 
>>weewx.conf by the copy (before upgrade)
>>2. During second step (10.11 to 11) the upgrade seems to be OK but I 
>>have this error:
>>
>>
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_reports", line 102, in 
>> main()
>>   File "/usr/share/weewx/wee_reports", line 66, in main
>> engine = weewx.engine.DummyEngine(config_dict)
>>   File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
>> self.loadServices(config_dict)
>>   File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
>> obj = weeutil.weeutil.get_object(svc)(self, config_dict)
>>   File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
>> mod = __import__(module)
>>   File "/usr/share/weewx/user/mqtt.py", line 100, in 
>> import paho.mqtt.client as mqtt
>> ModuleNotFoundError: No module named 'paho'
>>
>> Could you help me
>> Thank's
>>
>> -- 
>> 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/fc6e209e-90df-4626-9163-0ff2689b4932n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/fc6e209e-90df-4626-9163-0ff2689b4932n%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/f15eca23-8aff-4014-95ff-bb91c4567a05n%40googlegroups.com.

Re: [weewx-user] Re: Upgrade debian 11 bullseye

[didier....@gmail.com]

I have disabled brotli (command a2dismod brotli) 
No more errors about brotli during upgrade

Thank's

Le vendredi 25 février 2022 à 10:57:44 UTC+1, didier@gmail.com a écrit :

> I agree with you, I will try to disable brotli, it's a good idea
> I have also opened a discussion on brotli google group, but no news...
>
> Le ven. 25 févr. 2022 à 10:53, vhel...@gmail.com  a 
> écrit :
>
>> That error does not have anythink to do with Weewx, you should google 
>> with error or try to disable that brotli compression and then upgrade.
>>
>> torstai 24. helmikuuta 2022 klo 12.21.07 UTC+2 didier@gmail.com 
>> kirjoitti:
>>
>>> Hi
>>>
>>> During the first upgrade (10.4 to 10.10), I have an error:
>>>
>>> invoke-rc.d: initscript apache2, action "restart" failed.
>>> ● apache2.service - The Apache HTTP Server
>>>Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor 
>>> preset: enabled)
>>>Active: failed (Result: exit-code) since Wed 2022-02-23 18:55:55 CET; 
>>> 12ms ago
>>>  Docs: https://httpd.apache.org/docs/2.4/
>>>   Process: 17929 ExecStart=/usr/sbin/apachectl start (code=exited, 
>>> status=1/FAILURE)
>>>
>>> févr. 23 18:55:55 meteo systemd[1]: Starting The Apache HTTP Server...
>>> févr. 23 18:55:55 meteo apachectl[17929]: AH00526: Syntax error on line 
>>> 4 of /etc/apache2/mods-enabled/brotli.conf:
>>> févr. 23 18:55:55 meteo apachectl[17929]: Invalid command 
>>> 'BrotliCompressionLevel', perhaps misspelled or defined by a module not 
>>> included in the server configuration
>>> févr. 23 18:55:55 meteo apachectl[17929]: Action 'start' failed.
>>> févr. 23 18:55:55 meteo apachectl[17929]: The Apache error log may have 
>>> more information.
>>> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Control process 
>>> exited, code=exited, status=1/FAILURE
>>> févr. 23 18:55:55 meteo systemd[1]: apache2.service: Failed with result 
>>> 'exit-code'.
>>> févr. 23 18:55:55 meteo systemd[1]: Failed to start The Apache HTTP 
>>> Server.
>>>
>>> May be due to brotli, I check brotli.conf (but I think it's correct...)
>>>
>>> 
>>>   # Compression
>>>   ## BrotliCompressionLevel: 0-11 (default: 11)
>>>   BrotliCompressionLevel 10
>>>   ## BrotliWindowSize: 10-24 (default: 22)
>>>   BrotliWindowSize 22
>>>   # Logging
>>>   # Filter note
>>>   BrotliFilterNote Input  brotli_in
>>>   BrotliFilterNote Output brotli_out
>>>   BrotliFilterNote Ratio  brotli_ratio
>>>   #LogFormat '"%r" %{brotli_out}n/%{brotli_in}n (%{brotli_ratio}n)' 
>>> brotli
>>>   #CustomLog ${APACHE_LOG_DIR}/brotli_access.log brotli
>>>   # Output filter
>>>   AddOutputFilterByType BROTLI text/html text/plain text/css text/xml
>>>   AddOutputFilterByType BROTLI text/css
>>>   AddOutputFilterByType BROTLI application/x-javascript 
>>> application/javascript
>>>   AddOutputFilterByType BROTLI application/rss+xml
>>>   AddOutputFilterByType BROTLI application/xml
>>>   AddOutputFilterByType BROTLI application/json
>>>   # Global output filer if necessary.
>>>   # SetOutputFilter BROTLI
>>>   # SetEnvIfNoCase Request_URI \.txt$ no-br
>>> 
>>>
>>> Le jeu. 24 févr. 2022 à 10:29, vhel...@gmail.com  a 
>>> écrit :
>>>
>>>> Hi,
>>>>
>>>> You can upgrade to Debian 11. Here's one howto: 
>>>> https://www.linuxtechi.com/how-to-upgrade-debian-10-to-debian-11/
>>>> Since you are using VMware, take a snapshot before upgrade, and maybe 
>>>> also copy important weewx files to somewhere safe too.
>>>> It should be flawless, but you newer know... :) 
>>>>
>>>>
>>>>
>>>> keskiviikko 23. helmikuuta 2022 klo 18.21.14 UTC+2 didier@gmail.com 
>>>> kirjoitti:
>>>>
>>>>> Thanks for your answer
>>>>> I have not a raspberry, this is a virtual machine 64bits on a 
>>>>> vmware server, but I think that the upgrade is similar.
>>>>>
>>>>> Le mer. 23 févr. 2022 à 16:21, Aslak Vaa  a écrit :
>>>>>
>>>>>> It is possible to make an upgrade from Raspbian OS Buster to Bullseye 
>>>>>> as long as you do not change from 32 bits to 64 bits version or vice 
>>>>>> versa.
>>>>>> You will find instructions on how to m

[weewx-user] Error after ugrade debian 10 to debian 11

[didier....@gmail.com]

Hi everybody

I have upgraded my debian 10 (buster) to debian 11 (bullseye) following 
this procedure: 
https://ostechnix.com/upgrade-to-debian-11-bullseye-from-debian-10-buster/


   1. During first step (10.4 to 10.11) it's ok but I have to replace 
   weewx.conf by the copy (before upgrade)
   2. During second step (10.11 to 11) the upgrade seems to be OK but I 
   have this error:


Traceback (most recent call last):
  File "/usr/share/weewx/wee_reports", line 102, in 
main()
  File "/usr/share/weewx/wee_reports", line 66, in main
engine = weewx.engine.DummyEngine(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 93, in __init__
self.loadServices(config_dict)
  File "/usr/share/weewx/weewx/engine.py", line 161, in loadServices
obj = weeutil.weeutil.get_object(svc)(self, config_dict)
  File "/usr/share/weewx/weeutil/weeutil.py", line 1150, in get_object
mod = __import__(module)
  File "/usr/share/weewx/user/mqtt.py", line 100, in 
import paho.mqtt.client as mqtt
ModuleNotFoundError: No module named 'paho'

Could you help me
Thank's

-- 
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/fc6e209e-90df-4626-9163-0ff2689b4932n%40googlegroups.com.

[weewx-user] Upgrade debian 11 bullseye

[didier....@gmail.com]

Hi

Today I have a debian 10, weewx 4.6.2 and Belchertown skin 1.3b1 (working 
perfectly)
Is it possible to upgarde debian to next release 11 bullseye ?

If yes, what is the procedure?

Many 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/9c79948c-6888-45ae-ada5-6628981a40f5n%40googlegroups.com.

[weewx-user] Re: Problem since Weewx 4.6

[didier....@gmail.com]

I have found my error:
To avoid posting my own weewx.conf (with account and password), I have 
removed this file in the git process
Also version in weewx remained in 4.3.0.
I change in 4.6.1rc and it's OK now

Sorry for my previous message

Le mardi 8 février 2022 à 11:30:48 UTC+1, didier@gmail.com a écrit :

> I have updates weewx to 4.6 and lastrain-extension (compatible weewx 4.6)
> But I have exactly the same error of Remy after reboot
> I've checked lastrain.py and I have the correct §:
> try:
> # 4.6.0 breaking change - must specify either 
> context='short_delta' or context='long_delta'
>
> delta_time_vh = ValueHelper(delta_time_vt, 
> context='long_delta', formatter=self.generator.formatter, 
> converter=self.generator.converter)
> except:
> # this works for prior to 4.6.0
>
>delta_time_vh = ValueHelper(delta_time_vt, 
> formatter=self.generator.formatter, converter=self.generator.converter)
>
> Do you have an idea?
> Le mardi 8 février 2022 à 00:13:07 UTC+1, vince a écrit :
>
>> Yes - I updated my lastrain extension on github yesterday...
>>
>

-- 
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/c80ee268-3dd7-4e17-b6a0-7cf9a2bdf3f5n%40googlegroups.com.

[weewx-user] Re: Problem since Weewx 4.6

[didier....@gmail.com]

I have updates weewx to 4.6 and lastrain-extension (compatible weewx 4.6)
But I have exactly the same error of Remy after reboot
I've checked lastrain.py and I have the correct §:
try:
# 4.6.0 breaking change - must specify either 
context='short_delta' or context='long_delta'
delta_time_vh = ValueHelper(delta_time_vt, 
context='long_delta', formatter=self.generator.formatter, 
converter=self.generator.converter)
except:
# this works for prior to 4.6.0
   delta_time_vh = ValueHelper(delta_time_vt, 
formatter=self.generator.formatter, converter=self.generator.converter)

Do you have an idea?
Le mardi 8 février 2022 à 00:13:07 UTC+1, vince a écrit :

> Yes - I updated my lastrain extension on github yesterday...
>

-- 
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/c1eb57d4-ee50-4924-a80e-5b5a0032996dn%40googlegroups.com.

[weewx-user] Re: Master or development?

[didier....@gmail.com]

Many thanks Gary, it's clear for me now!
Didier

Le mardi 16 novembre 2021 à 13:12:00 UTC+1, gjr80 a écrit :

> Hi,
>
> It depends how daring you are. In general, master is the current release 
> (presently v4.5.1) and development is where the next release (currently 
> v4.6.0) is being developed. Once the development code is ready for release 
> master is updated from development and the release is made from master. 
> Sometimes you will find changes are made to master after a release, these 
> are typically minor changes or perhaps because an urgent minor release is 
> required to fix a specific bug/issue. Alpha and beta releases are taken 
> from development whenever development is at a stage where we want some user 
> input. Issues/bugs identified by alpha/beta users are fixed in development 
> and another alpha/beta release made if required. The process repeats until 
> release.
>
> In summary, master is typically stable and is generally the last release 
> (or very similar). Development is more bleeding edge and likely to contain 
> bugs, or is more subject to change; the number of bugs typically reduces as 
> the code matures. If you want to try some of the new features of the next 
> release, or need a particular new feature of the next release, use the 
> latest alpha/beta or the current development branch but be prepared for 
> bugs and changes. If you want stable use the current release. I would only 
> use master if you need a specific fix that you know has been applied to 
> master since the last release.
>
> Gary
> On Tuesday, 16 November 2021 at 21:07:14 UTC+10 didier@gmail.com 
> wrote:
>
>> Hi,
>> I see that you are solving several bugs, but solutions are included in 
>> the development branch of github.
>>
>> For the moment I use master branch.
>> Is it necessary to change or wait that development becomes master?
>>
>> 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/8c761290-44dc-42a4-906b-b2bcf7f405a3n%40googlegroups.com.

[weewx-user] Master or development?

[didier....@gmail.com]

Hi,
I see that you are solving several bugs, but solutions are included in the 
development branch of github.

For the moment I use master branch.
Is it necessary to change or wait that development becomes master?

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/c73c8e05-0ff3-45d1-8b51-770453d2a304n%40googlegroups.com.

[weewx-user] MQTT username and password in new Belchertown skin

[didier....@gmail.com]

Hi all

My question is about Belchertown skin last update with new 
parameters; mqtt_websockets_username and mqtt_websockets_password

In weewx.conf I have a paragraph (from mqtt github):
[StdRESTful]
[[MQTT]]
server_url = mqtt://xxx:@localhost:1883/
topic = weather

and 2 new lines (from skin.conf):
mqtt_websockets_username = ""
mqtt_websockets_password = "y"

Why I am obliged to duplicate username and password in the same file?

Many thanks

Have a good week-end


-- 
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/dfd510c2-5b38-4801-b97b-26cafc2d4caen%40googlegroups.com.

[weewx-user] Re: Display earthquakes using RENASS network

[didier....@gmail.com]

I have made modifications in Belchertown skin
see Issue https://github.com/poblabs/weewx-belchertown/issues/561
Le mardi 2 février 2021 à 10:38:25 UTC+1, didier@gmail.com a écrit :

> Hi
>
> Today in Belchertown skin, we can display USGS and GEONET earthquakes.
> I would like to add RENASS network.
>
> Renass can be reached by a url and gives a json answer, exemple:
>
> https://renass.unistra.fr/fdsnws/event/1/query?latitude=46.6=1.9=9=1=time=2021-01-18=json
>
> and result is :
> { "bbox": [ -3.621, 41.399, 9.87, 49.682 ], "features": [ { "geometry": { 
> "coordinates": [ 6.953, 44.888, -10 ], "type": "Point" }, "id": 
> "6018e3eb6dc5b1490661b451", "properties": { "description": "S\u00e9isme de 
> magnitude 1.3 \u00e0 31km de Pinerolo", "evaluationMode": "manual", "mag": 
> 1.3, "magType": "MLv", "place": "FRANCE", "time": 
> "2021-02-02T05:30:08.834000Z", "type": "earthquake", "url": "
> https://renass.unistra.fr/evenements/6018e3eb6dc5b1490661b451; }, "type": 
> "Feature" }, { "geometry": { "coordinates": [ 4.436, 47.195, 0 ], "type": 
> "Point" }, "id": "6018079d2d270784e6057f05",
> ...
>
>
>   As I am not a strong programmer, is somebody can add this option?
>
> Many thanks for your help
> Didier
>

-- 
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/68ec2279-3036-473a-8593-2b90f4b7745bn%40googlegroups.com.

[weewx-user] Display earthquakes using RENASS network

[didier....@gmail.com]

Hi

Today in Belchertown skin, we can display USGS and GEONET earthquakes.
I would like to add RENASS network.

Renass can be reached by a url and gives a json answer, exemple:
https://renass.unistra.fr/fdsnws/event/1/query?latitude=46.6=1.9=9=1=time=2021-01-18=json

and result is :
{ "bbox": [ -3.621, 41.399, 9.87, 49.682 ], "features": [ { "geometry": { 
"coordinates": [ 6.953, 44.888, -10 ], "type": "Point" }, "id": 
"6018e3eb6dc5b1490661b451", "properties": { "description": "S\u00e9isme de 
magnitude 1.3 \u00e0 31km de Pinerolo", "evaluationMode": "manual", "mag": 
1.3, "magType": "MLv", "place": "FRANCE", "time": 
"2021-02-02T05:30:08.834000Z", "type": "earthquake", "url": 
"https://renass.unistra.fr/evenements/6018e3eb6dc5b1490661b451; }, "type": 
"Feature" }, { "geometry": { "coordinates": [ 4.436, 47.195, 0 ], "type": 
"Point" }, "id": "6018079d2d270784e6057f05",
...


  As I am not a strong programmer, is somebody can add this option?

Many thanks for your help
Didier

-- 
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/8df4c98b-8053-4887-8342-43c44e29567an%40googlegroups.com.

[weewx-user] Minor and Moderate alert masking

[didier....@gmail.com]

hi

In Belchertown skin, I would like to display Severe and Extrem Aeris alerts 
only
Minor and Moderate will be masked.

Is it possible? in which file I have to test it?

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/bab45737-681a-49d4-a0ac-9097a6209e86n%40googlegroups.com.

[weewx-user] Re: Missing image when forecast_aeris_use_metar = 0

[didier....@gmail.com]

I think it's not a bug, I have found in belchertown.py
___
   if (
len(data["current"][0]["response"]) > 0
and self.generator.skin_dict["Extras"]
*["forecast_aeris_use_metar"]*
*== "0"*
):
# Non-metar responses do not contain these values. Set them 
to empty.
current_obs_summary = ""
*current_obs_icon = ""*
visibility = "N/A"
visibility_unit = ""
elif (
len(data["current"][0]["response"]) > 0
and 
self.generator.skin_dict["Extras"]["forecast_aeris_use_metar"]
== "1"
):
current_obs_summary = aeris_coded_weather(

data["current"][0]["response"]["ob"]["weatherPrimaryCoded"]
)
current_obs_icon = (

aeris_icon(data["current"][0]["response"]["ob"]["icon"]) + ".png"
)
___

If aeris_use_metar =0 then no icon displayed, right, but my question is:
What does mean "metar" and why we cannot display an icon without metar?
It is for a best understanding of this information

many thanks
Le mardi 26 janvier 2021 à 00:39:16 UTC+1, vince a écrit :

> We would have to see your entire [[Belchertown]] stanza without 
> usernames/passwords/keys to debug this.
>
> On Monday, January 25, 2021 at 2:30:05 PM UTC-8 didier@gmail.com 
> wrote:
>
>> Hi
>> Just a question:
>> Why the weather condition image is not displayed 
>> when forecast_aeris_use_metar = 0 ?
>> (I use Belchertown skin)
>>
>> Many thanks
>>
>> [image: missing.jpg]
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8c3c8a38-868c-436a-9d44-793ace24e78en%40googlegroups.com.

[weewx-user] Missing image when forecast_aeris_use_metar = 0

[didier....@gmail.com]

Hi
Just a question:
Why the weather condition image is not displayed 
when forecast_aeris_use_metar = 0 ?
(I use Belchertown skin)

Many thanks

[image: missing.jpg]

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/2572d2e8-ba6a-454b-ace3-49b55e23972bn%40googlegroups.com.

[weewx-user] AQI graph

[didier....@gmail.com]

Hi

I have now the Air Quality Indice in Belchertown skin, and I would like if 
it is possible to add this information into mysqlite database in order to 
create a graph.

Is it difficult? Have you a procedure to add an additional data and which 
files I have to modify?

Many thanks

Didier
https://meteo-auffargis.decoodt.eu

-- 
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/3720516f-0b16-4786-835a-f5e16e2514e7n%40googlegroups.com.

[weewx-user] Re: Version 4.3.0 released

[didier....@gmail.com]

Working fine !!!

Thank's Tom

Le jeudi 7 janvier 2021 à 12:22:18 UTC+1, n0...@n0nb.us a écrit :

> After being away from this group for a long time and having my manually 
> installed version left at 3.1.0 
> for the past several years, I'm back and just upgraded from 4.2.0 to 
> 4.3.0.  Why the upgrade?  I must have
> bumped the power plug and somehow corrupted the database on my Olimex 
> MICRO last week and while
> I managed some repairs to the DB, after a time it would stop reporting the 
> barometric pressure.  The OS
> was still Debian 9 (Stretch,) so I updated that to 10 (Buster) and opted 
> to install WeeWX from the Debian
> archive hosted here.
>
> The database schema upgrade went smoothly and soon 4.2.0 was up and 
> running.  Over the course of the
> next couple of days I integrated my customizations into the Standard skin 
> as well as integrated Wunderground
> radar and satellite images to replace those from NWS, and everything was 
> off and running.  I found the Xstats
> extension to be exactly what I needed to place some bit of Python code 
> that provides a 24 hour time frame for
> looking at the archive data over the past 24 hours regardless of the time 
> of day.
>
> I prefer the Standard report but also generate Seasons and Smartphone in 
> their own directories.  I may get 
> around to customizing Seasons a bit more as time goes on.
>
> This morning I did an apt update and saw 4.3.0 was available.  I read the 
> upgrade notes and went for it.  The
> database fix took a few minutes on this Olimex MICRO board which I have 
> because it supports a SATA drive
> and a 60 GB SSD fit nicely in the metal case.
>
> Once that was complete, I added the 'force_null = False' line and now 
> Wunderground shows the wind direction
> at all times rather than N/A.  Thanks much!  My anemometer is partially 
> shielded and has a sticky bearing so
> it mostly shows 0 MPH at low wind speeds.  Now my station page appears to 
> be continuously active.
>
> I am pleased to see that I had the option to see the differences in the 
> configuration files and keep my modified
> versions while checking for anything important I would need to add later.  
> This is not easy, I suspect and works
> as well as official Debian packages.  Well done!
>
> I am pleased to be running the latest WeeWX and will try to pop in here 
> from time to time again.
>
> - Nate
>
>

-- 
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/bea646df-4bee-4327-a6f8-0dbe8f8d8429n%40googlegroups.com.

[weewx-user] Re: AQI: 0 (unknown) in Belchertown skin

[didier....@gmail.com]

IncredibleI am living in France, near Paris, and when I put 
this URL:

https://api.aerisapi.com/airquality/closest?p=48.700751,1.881646=json=500mi=1_id=V06zdgRVX..
with a radius of 500 miles, I receive data from the nearest place at 
eastbourne in England !

{"success":true,"error":null,"response":[{"id":"AQO_gb6d38797","loc":{"long":0.271611,"lat":50.805778},"place":{"name":"eastbourne","state":"eng","country":"gb"},"periods":[{"dateTimeISO":"2020-12-29T13:00:00+00:00","timestamp":1609246800,"aqi":4,"category":"good","color":"00E400","method":"airnow","dominant":"no2","pollutants":[{"type":"no2","name":"nitrogen
 
dioxide","valuePPB":4,"valueUGM3":8,"aqi":4,"category":"good","color":"00E400"}]}],"profile":{"tz":"Europe\/London","sources":[{"name":"Department
 
for Environmental Food & Rural 
Affairs"},{"name":"OpenAQ"}],"stations":["AQO_gb6d38797"]},"relativeTo":{"lat":48.700751,"long":1.881646,"bearing":333,"bearingENG":"NNW","distanceKM":261.072,"distanceMI":162.223}}]}
  

Does Aeris Air Quality information available in France ?
Le mardi 29 décembre 2020 à 14:10:37 UTC+1, didier@gmail.com a écrit :

> Hi
>
> I have updated my site with the last master repository and I have always 
> AQI: 0 (unknown) for Air Quality
> My aeris account is OK (already used for forecasts)
> aqi_enabled and aqi_location_enabled are set to 1 in my conf file
> aqi_good, aqi_moderate ... labels are translated in conf file
>
> Do you have an idea?
> Where and how I can debug this problem?
>
> Many thanks
> Didier
>
>

-- 
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/71c1c9ac-880a-46e3-811e-b10c2c5562afn%40googlegroups.com.

[weewx-user] AQI: 0 (unknown) in Belchertown skin

[didier....@gmail.com]

Hi

I have updated my site with the last master repository and I have always 
AQI: 0 (unknown) for Air Quality
My aeris account is OK (already used for forecasts)
aqi_enabled and aqi_location_enabled are set to 1 in my conf file
aqi_good, aqi_moderate ... labels are translated in conf file

Do you have an idea?
Where and how I can debug this problem?

Many thanks
Didier

-- 
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/6c08aefc-4cdb-488a-8602-a1f87153fde5n%40googlegroups.com.

Re: [weewx-user] Davis WeatherLink Live: Which driver is best?

[didier....@gmail.com]

The right value is "altimeter"
See 
specs 
https://www.davisinstruments.com/product_documents/weather/spec_sheets/6100_WL-Live_Spec_Sheet.pdf
Le mercredi 2 décembre 2020 à 14:24:37 UTC+1, kk44...@gmail.com a écrit :

> To my support question to the Davis support I finally received a reply. I 
> asked them why there are differences between console value and 
> WeatherLinkLive value and whether that is an accuracy issue. The first 
> answer was not helpful. So I confronted them with the statement about 
> different calculation. They took a long time to answer. 
>
> And from what I understand what they wrote the Davis support does not know 
> for sure. Who then?
>
> This was their answer:
> *Hello, *
> *That looks like it is the case. They are calculated different. *
> *To tell you the truth I was not aware of this. *
> ** * * *
> *Tom Raymond *
> *Technical Support Davis Instruments*
>
>
>
> didier@gmail.com schrieb am Sonntag, 22. November 2020 um 14:29:48 
> UTC+1:
>
>> thank's Florentin, I've just opened a ticket on Davis support, I will 
>> give you the result next week I hope.
>>
>> Le dim. 22 nov. 2020 à 14:24, flor...@pre-vost.fr  
>> a écrit :
>>
>>> Hi,
>>>
>>> I'm the author of WLLDriver on Github.
>>> Yes, I think that *altimeter *is the good value. But I suggest to 
>>> confirm that by directly ask Davis.
>>>
>>> Regards,
>>>
>>> Le samedi 21 novembre 2020 à 22:31:04 UTC+1, kk44...@gmail.com a écrit :
>>>
>>>> I found that additional information at 
>>>> https://www.manula.com/manuals/pws/davis-kb/1/en/topic/barometric-pressure-issues
>>>> .
>>>>
>>>> There they say, that Davis uses different calculations in different 
>>>> devices:
>>>>
>>>>- VP2 and envoy consoles: sea-level pressure ("barometer", QFF)
>>>>- WeatherLinkLive: altimeter pressure ("altimeter", QNH)
>>>>- Vue consoles: user can choose between the two
>>>>
>>>> So it seems, the author of the "weatherlinkliveudp" driver read the 
>>>> documentation most carefully. 
>>>>
>>>> And to confuse the user or something, in the LOOP data record, Davis 
>>>> calls the value, what we learnt is altimeter, "bar_sea_level". 
>>>>
>>>> The archive record contains all the three values barometer, altimeter, 
>>>> and pressure (I checked). Since the "weatherlinkliveudp" driver does not 
>>>> provide a value for barometer, may be, WeeWX calculates it by itself.
>>>>
>>>> didier@gmail.com schrieb am Samstag, 21. November 2020 um 20:54:45 
>>>> UTC+1:
>>>>
>>>>> Thank's a lot
>>>>> I'm learning a lot of things with you
>>>>>
>>>>> Le sam. 21 nov. 2020 à 18:59, vince  a écrit :
>>>>>
>>>>>> On Saturday, November 21, 2020 at 9:31:11 AM UTC-8 kk44...@gmail.com 
>>>>>> wrote:
>>>>>>
>>>>>>> didier@gmail.com schrieb am Samstag, 21. November 2020 um 
>>>>>>> 16:09:22 UTC+1:
>>>>>>>
>>>>>>>> Ooops, after 10 mn the 2 values have diverged (only 1 mbar)
>>>>>>>> The explanation is that weatherlinkliveudp driver uses "altimeter" 
>>>>>>>> and WLLDriver uses "barometer" for the station info
>>>>>>>>
>>>>>>>
>>>>>>> That I do not understand. Does the driver only retrieves the 
>>>>>>> readings from the hardware, doesn't it? So, which way the driver can 
>>>>>>> influence which values is displayed?
>>>>>>>  
>>>>>>>
>>>>>>
>>>>>> There are two pressure-related elements provided by the Davis 
>>>>>> hardware.One is the pressure as reported by the sensor, the other is 
>>>>>> the pressure corrected to sea-level pressure based on your altitude.
>>>>>> The 
>>>>>> driver code defines which sensor values it uses for what generic weewx 
>>>>>> database element
>>>>>>
>>>>>> Both drivers map 'bar_absolute' from the hardware to weewx 'pressure' 
>>>>>> in the database.
>>>>>>
>>>>>> But...the two drivers map 'bar_sea_level' from 

[weewx-user] Re: Version 4.2.0 ready

[didier....@gmail.com]

Hi Tom

Update from 4.1.1 to 4.2.0 : no problem

Perfect!!

Thank's a lot

Le mardi 27 octobre 2020 à 13:14:04 UTC+1, tke...@gmail.com a écrit :

> Some new features, fixes some bugs.
>
> See the *Upgrade Guide * for 
> instructions on how to upgrade.
>
> CHANGE LOG
>
> CHANGES COMING! This is the last release that will support the LaCrosse 
> WS23xx,
> Oregon WMR200 and WMR300 stations. In the future, they will be published as
> unsupported extensions.
>
> Made it easier to add new, derived types via StdWXCalculate. Fixes issue #491.
>
> Changed the tag system slightly in order to make it possible for the XTypes
> system to add new aggregations that take an argument.
>
> Added the new data types in the extended_wview schema to the WeeWX types
> system. Fixes issue #613.
>
> Added ability to label left, right or both y-axes of graphs.  PR#610.
> Fixes issue #609. Thanks to user Brent Fraser!
>
> Added units and labels for the lightning data types.
>
> Fixed problem where threads attempt to access non-existent database. Fixes
> issue #579.
>
> Fixed problem that caused reporting units to revert to US if they were in a
> mixed unit system. Fixes issue #576.
>
> Fixed problem that could cause the station registry to fail if given a 
> location
> with a non-ASCII location name.
>
> Changed TE923 bucket size from 0.02589 inches to 1/36 of an inch
> (0.0278 in). PR #575. Fixes issue #574. Thanks to user Timothy!
>
> Undocumented option retry_certificate has been renamed to retry_ssl, and now
> covers all SSL errors (not just certificate errors). Fixes issue #569. Thanks
> to user Eric!
>
> Fixed problem caused by specifying a [Logging]/[[formatters]] section in
> weewx.conf that uses interpolated variables.
>
> Fixed problem in the Vantage driver that resulted in incorrect sunrise/sunset
> being included in loop packets when run under Python 3. Thanks to users 
> Constantine and Jacques!
>
> Improved auto-scaling of plot axes.
>
> Fixed problem where aggregates of windvec and windgustvec returned the 
> aggregate
> since start of day, not the start of the aggregation period. Fixes issue #590.
>
> New unit "beaufort", included in "group_speed". Treating beaufort as a 
> separate
> type has been deprecated. Fixes issue #591.
>
> New unit "kPa", included in "group_pressure". Fixes issue #596.
>
> Fixed bug in the simulator. Made it easier to subclass class Simulator.
>
> Expressions in StdCalibration are now ordered. Later corrections can depend on
> earlier corrections.
>
> Fixed problem under Python 2, where option 'none' could cause exception.
> PR #597. Thanks to user Clément!
>
> Fixed problem with ws23xx driver under Python 3 that caused it to crash.
>
> Use a more modern formula for heat index. Fixes issue #601. Thanks to
> user Peter Q!
>
> Allow overriding the data binding when using iterators. Fixes issue #580.
>
> Fixed problem where old daily summaries may not have a version number.
>
> Fixed problem in WMR200 driver where missing UV reports as index 255.
>
> Added option 'force_direction' for working around a WU bug. Fixes issue #614.
>
>

-- 
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/d6ef03f2-61af-4947-aed9-2ce249966dc2n%40googlegroups.com.

[weewx-user] Weewx stop with WeatherLinkLiveJSON driver

[didier....@gmail.com]

Hi everyone

In weewx.conf I have the driver WeatherLinkLiveJSON: 
(https://github.com/Drealine/weewx-weatherlinklive-json/tree/patch-1)

##

[WeatherLinkLiveJSON]
driver = user.WeatherLinkLiveJSON
max_tries = 10
retry_wait = 5
poll_interval = 2.5
url = http://192.168.1.201:80/v1/current_conditions 


##


Yesterday I have a brief link interruption between my server and the 
WeatherLinkLive box, then weewx service has stopped.


/var/log/syslog.1:Oct 21 22:47:15 meteo weewx[26403] INFO 
user.WeatherLinkLiveJSON: failure to get data 
http://192.168.1.201:80/v1/current_conditions 
 - try 1 - 
(HTTPConnectionPool(host='192.168.1.201', port=80): Max retries exceeded 
with url: /v1/current_conditions (Caused by 
NewConnectionError(": Failed to establish a new connection: [Errno 110] 
Connexion terminée par expiration du délai d'attente")))
/var/log/syslog.1:Oct 21 22:47:17 meteo weewx[26403] CRITICAL weewx.engine: 
Internal error. Packet loop has exited.
/var/log/syslog.1:Oct 21 22:47:18 meteo weewx[26403] INFO weewx.engine: 
Main loop exiting. Shutting engine down.

In syslog I can see that weewx stops with try = 1, but in weewx.conf I have 
max_tries = 10

Is it normal?

Thank's 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/e19d1cfd-3cde-4350-9068-9d8e52ab50c0n%40googlegroups.com.

[weewx-user] How to backup mysql database

[didier....@gmail.com]

Hi

I would like to backup (each week for exemple) my weewx mysql database from 
debian to a NAS

Thank you for your help

ddperso

-- 
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/48e0c616-da8d-43ef-b925-f147c1fd5e48n%40googlegroups.com.

Re: [weewx-user] CheetahGenerator in weewx.conf?

[didier....@gmail.com]

Thank's 
it's work

Didier

Le vendredi 14 août 2020 à 16:49:17 UTC+2, tke...@gmail.com a écrit :

> I've never tried it, but I don't see why search_list_extensions cannot be 
> overridden 
> in weewx.conf <http://www.weewx.com/docs/customizing.htm#How_options_work> 
> like any other option. So, using Belchertown as an example, you would want
>
> [StdReport]
>   ...
>   [[Belchertown]]
> [[[CheetahGenerator]]]
>   search_list_extensions = user.belchertown.getData
>
> -tk
>
> On Fri, Aug 14, 2020 at 6:39 AM didier@gmail.com  
> wrote:
>
>> Hi
>>
>> Just a question:
>> In order to have all configurable information in weewx.conf, is it 
>> possible to copy the CheetahGenerator paragraph from skin.conf to 
>> weewx.conf?
>>
>> [CheetahGenerator]
>> # This section is used by the generator CheetahGenerator, and 
>> specifies
>> # which files are to be generated from which template.
>>
>> search_list_extensions = user.belchertown.getData
>>
>> Thank's
>>
>> -- 
>> 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/9eeec4ba-4f29-4806-940b-47dd34c85d54n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/9eeec4ba-4f29-4806-940b-47dd34c85d54n%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/8207925b-4ef1-4cbe-9f6e-6fb2b6c53b30n%40googlegroups.com.

[weewx-user] CheetahGenerator in weewx.conf?

[didier....@gmail.com]

Hi

Just a question:
In order to have all configurable information in weewx.conf, is it possible 
to copy the CheetahGenerator paragraph from skin.conf to weewx.conf?

[CheetahGenerator]
# This section is used by the generator CheetahGenerator, and specifies
# which files are to be generated from which template.

search_list_extensions = user.belchertown.getData

Thank's

-- 
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/9eeec4ba-4f29-4806-940b-47dd34c85d54n%40googlegroups.com.

[weewx-user] Format of return values from Last-Rain-extension

[didier....@gmail.com]

Hi
I have installed the last-rain extension which give me 2 return values 
"last_rain" and "time_since_last_rain"

In the Github documentation, I can see:
Result is returned as a ValueHelper so standard Weewx formatting is 
available eg $last_rain.format("%d %m %Y")

Could you say me where I can defined this fomat? Is it in weewx.conf? or 
elsewhere?

Many thanks for your help

Didier

-- 
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/7eda05b5-ab0a-4a6d-8e2b-957b7ca4dd9bn%40googlegroups.com.

[weewx-user] Re: [Belchertown] How to add observation working with mqtt (beaufort)

[didier....@gmail.com]

In MQTT request, we have beaufort_count in real time
Is it possible to add this value in "wind" window ?

MQTT: {"dateTime": "1594981362.0", "outTemp_C": "21.057", 
"outHumidity": "66.3", "dewpoint_C": "14.5", "heatindex_C": 
"20.832", "windchill_C": "21.057", "windSpeed_kph": 
"0.692017920001", "windDir": "72.0", "windGust_kph": 
"4.21648128001", "windGustDir": "308.0", "barometer_mbar": 
"1022.6892239625905", "pressure_mbar": "1005.2493249446854", "rain_mm": 
"0.0", "rainRate_mm_per_hour": "0.0", "inTemp_C": "23.5", "inHumidity": 
"54.4", "inDewpoint_C": "13.777", "usUnits": "16.0", 
"altimeter_mbar": "1023.3754178652133", "appTemp_C": "22.366369245300767", 
"beaufort_count": 
"0.0", "cloudbase_meter": "946.6094010934512", "humidex_C": 
"24.731416236039106", "maxSolarRad_Wpm2": "847.4085991138148", 
"hourRain_mm": "0.0", "rain24_mm": "0.0", "dayRain_mm": "0.0"}

Le vendredi 17 juillet 2020 à 09:54:23 UTC+2, eric9...@gmail.com a écrit :

> I've used the last script described in this topic : 
> https://groups.google.com/forum/m/#!topic/weewx-user/b7TqpYD9sxY

-- 
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/e5083f98-e40d-47aa-8ff9-0dd1cff80719n%40googlegroups.com.

[weewx-user] Re: [Belchertown] How to add observation working with mqtt (beaufort)

[didier....@gmail.com]

Hi Eric
How do you include "Force 3 Beaufort:" in the wind window ? Is it the 
MQTT parameter : beaufort_count ?
Have you find the solution for realtime ?

Merci
Didier
Le dimanche 12 juillet 2020 à 13:53:44 UTC+2, t...@tom.org a écrit :

> Great timing. I have been working to publish energy production and 
> consumption to mqtt and would love basic guidance on how to consume it in 
> Belchertown.
>
> On Sunday, July 12, 2020 at 3:35:58 AM UTC-4 eric9...@gmail.com wrote:
>
>> Hi all !
>>
>> I've managed to add current Beaufort in the wind container. 
>> Unfortunately, the value doesn't change in real time and I don't understand 
>> how it works to turn it working in realtime too.
>>
>> Could you explain me how it works ?
>>
>> [image: beaufort.jpg]
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/d5d7731a-9084-487c-8f3e-39d26b35abb9n%40googlegroups.com.

[weewx-user] Missing Ordinates on windrose graph [Belchertown]

[didier....@gmail.com]

Hi

I have a small problem on windrose graph: some ordinates are not displayed!

Here is a part of my conf file:
Ordinates

# Ordinal directions. The last one is for no wind direction
directions = N, NNE, NE, ENE, E, ESE, SE, SSE, S, SSO, SO, 
OSO, O, ONO, NO, NNO, N/A

Here is a part of my graphs.conf file:
[[chart4]]
title = Rose des vents
[[[windRose]]]


Do you have an idea of this problem?

Many thanks
Didier

-- 
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/46ef2884-2efd-4c3d-a207-a5461a0ab2c5n%40googlegroups.com.

[weewx-user] Air quality in Belchertown skin

[didier....@gmail.com]

Hi

My site is based on Belchertown skin 1.2b6, thank's Pat

I would like to have air quality datas.
Is it possible to have Air Quality information on Belchertown skin, and 
which sensor is available and reliable (with a raisonnable price of course)?

Many thanks
Didier
meteo-auffargis.decoodt.eu 

-- 
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/ad649e26-1c28-4732-b57e-9c2738a7c88dn%40googlegroups.com.

[weewx-user] Re: Weewx tag to show last time it rained

[didier....@gmail.com]

Hi
I have installed the extension and modify the conf file, but I have not the 
file index-hook-after-station-info.inc, and I don't know how to write it. 
Is it possible to have a copy of this file with the 2 parameters last_rain 
and time_since_last_rain?

Many thanks
Didier
Le lundi 8 juin 2020 à 08:57:14 UTC+2, hoev...@gmail.com a écrit :

> Well, speaking for me, I would like to show this information (last time it 
> rained) using a tag, and put it in index_hook_after_station_info.inc The 
> tag is $time_since_last_rain.
>
> Having done that (putting the tag in that inc-file), it throws an error 
> NameMapper.NotFound while the generator is doing its thing. Looking at the 
> html the skin lastrain produces, it shows the correct last datetime it 
> rained. I guess (in my own words) it's the case that calculated variables 
> in one skin can not be used in another skin? Is this true?
>
> Jun  8 08:53:18 weewx weewx[99172] INFO weewx.cheetahgenerator: Generated 
> 8 files for report SeasonsReport in 1.24 seconds
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.imagegenerator: Generated 15 
> images for report SeasonsReport in 0.41 seconds
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.reportengine: Copied 5 files 
> to /var/www/html/weewx
> Jun  8 08:53:19 weewx weewx[99172] INFO weewx.restx: MQTT: Published 
> record 2020-06-08 08:53:19 CEST (1591599199)
> Jun  8 08:53:19 weewx weewx[99172] message repeated 2 times: [ INFO 
> weewx.restx: MQTT: Published record 2020-06-08 08:53:19 CEST (1591599199)]
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: Generate 
> failed with exception ''
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:  
> Ignoring template /etc/weewx/skins/Belchertown/index.html.tmpl
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:  
> Reason: cannot find 'time_since_last_rain'
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> Traceback (most recent call last):
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> unicode_string = compiled_template.respond()
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "_etc_weewx_skins_Belchertown_index_html_tmpl.py", line 1261, in 
> respond
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File "/usr/lib/python3/dist-packages/Cheetah/Template.py", line 1708, in 
> _handleCheetahInclude
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> self._CHEETAH__cheetahIncludes[_includeID].respond(trans)
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator: 
> File 
> "cheetah__etc_weewx_skins_Belchertown_index_hook_after_station_info_inc_1591599200_376662_26334.py",
>  
> line 90, in respond
> Jun  8 08:53:20 weewx weewx[99172] ERROR weewx.cheetahgenerator:   
> NameMapper.NotFound: cannot find 'time_since_last_rain'
> Jun  8 08:53:20 weewx weewx[99172] INFO weewx.restx: MQTT: Published 
> record 2020-06-08 08:53:21 CEST (1591599201)
> Jun  8 08:53:21 weewx weewx[99172] INFO weewx.cheetahgenerator: Generated 
> 10 files for report Belchertown in 1.86 seconds
>
>
> Op woensdag 3 juni 2020 14:11:27 UTC+2 schreef Pat:
>
>> Where on the skin would you display this info? Just curious
>>
>> On Wednesday, June 3, 2020 at 6:59:13 AM UTC-4, NanoG5Kite wrote:
>>>
>>> Got this installed and working too - many thanks for the hint.
>>>
>>>
>>> As Weewx beginner - is there any way to get the two Last Rain Values 
>>> displayed in the Belchertown Homeskin?
>>>
>>> last rain N/A 
>>> time since last rain: N/A 
>>>
>>> Thanks,
>>>
>>> Matthias
>>>
>>> Am Mittwoch, 3. Juni 2020 12:38:05 UTC+2 schrieb Remy Lavabre:

 Yes !
 And it is working perfectly !
>>>
>>>

-- 
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/297fb48e-857d-43ca-843e-b7a6c5f17377n%40googlegroups.com.

[weewx-user] Re: Weewx tag to show last time it rained

[didier....@gmail.com]

Hi
Could you write a small recap tuto to explain the different actions and 
modifications, I would like install this interesting functionnality and I 
am not an expert in Linux and weewx...
Is it possible to include this in the Belchertown development git?
Many thanks

Le lundi 22 juin 2020 à 19:17:44 UTC+2, pligg...@gmail.com a écrit :

> Hi! Just installed this extension. Works perfectly. Just want to change 
> the language in "days", "hours", and "minutes" in $time_since_last_rain 
> tag. Where do I make this change? 
>
> regards Mikael
>

-- 
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/cb2a3ecc-0736-4996-b860-0354b8d9b1f1n%40googlegroups.com.

[weewx-user] Re: Belchertown - Translations

[didier....@gmail.com]

All parameters (Extras, Labels) in skin.conf should be copied into 
weewx.conf (it is recommended)
When you have a Belchertown update, weewx.conf file is not updated.
In this case you have german parameters in weewx.conf and the same english 
defaults parameters in skin.conf, but the priority is for weewx.conf (in 
german)
If you modify other files, it is recommended to save them.
Yesterday I have made an update of Belchertown skin (from 1.1 to 1.2b5) 
with this method and it's work!

Le mardi 16 juin 2020 à 11:17:43 UTC+2, moth...@gmail.com a écrit :

> Is it possible to place all the necessary files needed for a translation, 
> such as German, Spanish, French and Dutch, in a separate folder so that a 
> translated skin becomes more convenient and is not replaced during an 
> update?
> I want to translate the skin into Dutch.
>

-- 
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/3d3214b5-a9b1-414a-b6a5-288bb594f566n%40googlegroups.com.

Re: [weewx-user] Re: Full day highcharts question

[didier....@gmail.com]

Thanks it's work 


Le lundi 15 juin 2020 à 11:12:27 UTC+2, Manfred Maier a écrit :

> Thanks, Gary, for this comprehensive explanation.
>
> Based on what you wrote I was now able to plot an entire day.
>
> [image: Bildschirmfoto 2020-06-15 um 11.07.53.png]
>
> The trick is quite simple: I just had to define an aggregation for the 
> daily charts. I.e. adding the following two lines to the graphs.conf:
>
> aggregate_type = max
>
> aggregate_interval = 300
>
>
>
>

-- 
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/e6f55596-fb95-4621-8599-dac0c18e7540n%40googlegroups.com.