[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Stefan Gliessmann]

I wish, I could :(

I needed to do a fresh install of my home station on June 23 from scratch.
And belchertown.py was last changed on Jun 21. (specifically for this issue 
<https://github.com/poblabs/weewx-belchertown/commit/8bbda2de5ba2cd1b3fa484852262194c2b452441>
).

So, I am really puzzled what was the issue ...

On Thursday, September 12, 2024 at 3:06:51 PM UTC+2 Karen K wrote:

> Could you report what was the difference between the belchertown.py that 
> created the error and the belchertown.py that works?
>
> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 15:04:49 
> UTC+2:
>
>> well - I just did another:
>>
>> sudo wget 
>> https://github.com/poblabs/weewx-belchertown/raw/master/bin/user/belchertown.py
>>
>> and now, it works 
>>
>> Thank you, again, Tom!
>> On Thursday, September 12, 2024 at 2:50:36 PM UTC+2 Stefan Gliessmann 
>> wrote:
>>
>>> Actually, the updated belchertown.py (three months ago) is already in 
>>> place on my server.
>>> Please notice that this is Ubuntu 24.04.01
>>>
>>> Before the upgrade, it was running just fine on Ubuntu 24.04.
>>>
>>> I did re-install "locales" already:
>>>
>>> sudo apt-get update
>>> sudo apt-get install --reinstall locales
>>>
>>> A little test script return the correct format, too:
>>>
>>> import locale
>>> locale.setlocale(locale.LC_ALL, '')
>>> print(locale.format_string("%g", 12345.6789, grouping=True))
>>>
>>>  Hmm ...
>>>
>>> On Thursday, September 12, 2024 at 2:43:54 PM UTC+2 Stefan Gliessmann 
>>> wrote:
>>>
>>>> Thank you Tom!
>>>>
>>>> I need to improve my search skills in this group!
>>>>
>>>> Cheers,
>>>> Stefan
>>>>
>>>>
>>>> On Thursday, September 12, 2024 at 2:30:20 PM UTC+2 Karen K wrote:
>>>>
>>>>> I guess you may want to re-install some Python modules. The error 
>>>>> message reports an error regarding the "locale" module. I see no 
>>>>> connection 
>>>>> to the Belchertown skin itself.
>>>>>
>>>>> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 
>>>>> 14:18:37 UTC+2:
>>>>>
>>>>>> Dear All -
>>>>>>
>>>>>> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
>>>>>> Ubuntu 24.04.01 LTS.
>>>>>>
>>>>>> After the reboot, things booted up just fine.
>>>>>> But no new reports were generated.
>>>>>> Going to the logfile, I found:
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
>>>>>> unrecoverable exception in generator 
>>>>>> 'weewx.cheetahgenerator.CheetahGenerator'*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>     module 'locale' has no attribute 'format'*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>     Traceback (most recent call last):*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>   File "/usr/share/weewx/weewx/reportengine.py", line 248, in 
>>>>>> run*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>     obj.start()*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>   File "/usr/share/weewx/weewx/reportengine.py", line 465, in 
>>>>>> start*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>     self.run()*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>   File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, 
>>>>>> in 
>>>>>> run*
>>>>>>
>>>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
>>>>>>     ngen = self.generate(gen_dict[section_name

[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Stefan Gliessmann]

well - I just did another:

sudo wget 
https://github.com/poblabs/weewx-belchertown/raw/master/bin/user/belchertown.py

and now, it works 

Thank you, again, Tom!
On Thursday, September 12, 2024 at 2:50:36 PM UTC+2 Stefan Gliessmann wrote:

> Actually, the updated belchertown.py (three months ago) is already in 
> place on my server.
> Please notice that this is Ubuntu 24.04.01
>
> Before the upgrade, it was running just fine on Ubuntu 24.04.
>
> I did re-install "locales" already:
>
> sudo apt-get update
> sudo apt-get install --reinstall locales
>
> A little test script return the correct format, too:
>
> import locale
> locale.setlocale(locale.LC_ALL, '')
> print(locale.format_string("%g", 12345.6789, grouping=True))
>
>  Hmm ...
>
> On Thursday, September 12, 2024 at 2:43:54 PM UTC+2 Stefan Gliessmann 
> wrote:
>
>> Thank you Tom!
>>
>> I need to improve my search skills in this group!
>>
>> Cheers,
>> Stefan
>>
>>
>> On Thursday, September 12, 2024 at 2:30:20 PM UTC+2 Karen K wrote:
>>
>>> I guess you may want to re-install some Python modules. The error 
>>> message reports an error regarding the "locale" module. I see no connection 
>>> to the Belchertown skin itself.
>>>
>>> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 14:18:37 
>>> UTC+2:
>>>
>>>> Dear All -
>>>>
>>>> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
>>>> Ubuntu 24.04.01 LTS.
>>>>
>>>> After the reboot, things booted up just fine.
>>>> But no new reports were generated.
>>>> Going to the logfile, I found:
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
>>>> unrecoverable exception in generator 
>>>> 'weewx.cheetahgenerator.CheetahGenerator'*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   module 'locale' has no attribute 'format'*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   Traceback (most recent call last):*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>> File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   obj.start()*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>> File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   self.run()*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in 
>>>> run*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   ngen = self.generate(gen_dict[section_name], section_name, 
>>>> self.gen_ts)*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>  
>>>> *
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>>>> generate*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   ^^*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>>>> generate*
>>>>
>>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>>>
&

[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Stefan Gliessmann]

Actually, the updated belchertown.py (three months ago) is already in place 
on my server.
Please notice that this is Ubuntu 24.04.01

Before the upgrade, it was running just fine on Ubuntu 24.04.

I did re-install "locales" already:

sudo apt-get update
sudo apt-get install --reinstall locales

A little test script return the correct format, too:

import locale
locale.setlocale(locale.LC_ALL, '')
print(locale.format_string("%g", 12345.6789, grouping=True))

 Hmm ...

On Thursday, September 12, 2024 at 2:43:54 PM UTC+2 Stefan Gliessmann wrote:

> Thank you Tom!
>
> I need to improve my search skills in this group!
>
> Cheers,
> Stefan
>
>
> On Thursday, September 12, 2024 at 2:30:20 PM UTC+2 Karen K wrote:
>
>> I guess you may want to re-install some Python modules. The error message 
>> reports an error regarding the "locale" module. I see no connection to the 
>> Belchertown skin itself.
>>
>> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 14:18:37 
>> UTC+2:
>>
>>> Dear All -
>>>
>>> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
>>> Ubuntu 24.04.01 LTS.
>>>
>>> After the reboot, things booted up just fine.
>>> But no new reports were generated.
>>> Going to the logfile, I found:
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
>>> unrecoverable exception in generator 
>>> 'weewx.cheetahgenerator.CheetahGenerator'*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   module 'locale' has no attribute 'format'*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   Traceback (most recent call last):*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   obj.start()*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   self.run()*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   ngen = self.generate(gen_dict[section_name], section_name, 
>>> self.gen_ts)*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>  
>>> *
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>>> generate*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   ^^*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>>> generate*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   ^^*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
>>> generate*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>   searchList = self._getSearchList(encoding, timespan,*
>>>
>>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>>    ^^^*
>>>
>>> Se

[weewx-user] Re: Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Stefan Gliessmann]

Thank you Tom!

I need to improve my search skills in this group!

Cheers,
Stefan


On Thursday, September 12, 2024 at 2:30:20 PM UTC+2 Karen K wrote:

> I guess you may want to re-install some Python modules. The error message 
> reports an error regarding the "locale" module. I see no connection to the 
> Belchertown skin itself.
>
> Stefan Gliessmann schrieb am Donnerstag, 12. September 2024 um 14:18:37 
> UTC+2:
>
>> Dear All -
>>
>> I just finished upgrading my weewx server's OS from Ubuntu 24.04. to 
>> Ubuntu 24.04.01 LTS.
>>
>> After the reboot, things booted up just fine.
>> But no new reports were generated.
>> Going to the logfile, I found:
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
>> unrecoverable exception in generator 
>> 'weewx.cheetahgenerator.CheetahGenerator'*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   module 'locale' has no attribute 'format'*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   Traceback (most recent call last):*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   obj.start()*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   self.run()*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   ngen = self.generate(gen_dict[section_name], section_name, 
>> self.gen_ts)*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>  
>> *
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>> generate*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   ^^*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in 
>> generate*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   ngen += self.generate(section[subsection], subsection, gen_ts)*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   ^^*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in 
>> generate*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   searchList = self._getSearchList(encoding, timespan,*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>    ^^^*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/usr/share/weewx/weewx/cheetahgenerator.py", line 401, in 
>> _getSearchList*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   search_list += obj.get_extension_list(timespan, db_lookup)*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>  ^^^*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>> File "/etc/weewx/bin/user/belchertown.py", line 612, in 
>> get_extension_list*
>>
>> Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: 
>>   locale.format("%g", float(year_outTemp_max_range_total)),*
>>
>> Sep 12 13:52:49 WXvm wee

[weewx-user] Upgraded OS to Ubuntu 24.04.1 LTS causes error by Belchertown skin?

[Stefan Gliessmann]

Dear All -

I just finished upgrading my weewx server's OS from Ubuntu 24.04. to Ubuntu 
24.04.01 LTS.

After the reboot, things booted up just fine.
But no new reports were generated.
Going to the logfile, I found:

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine: Caught 
unrecoverable exception in generator 
'weewx.cheetahgenerator.CheetahGenerator'*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
module 'locale' has no attribute 'format'*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
Traceback (most recent call last):*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/reportengine.py", line 248, in run*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
obj.start()*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/reportengine.py", line 465, in start*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
self.run()*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 166, in run*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
ngen = self.generate(gen_dict[section_name], section_name, self.gen_ts)*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:  

*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
ngen += self.generate(section[subsection], subsection, gen_ts)*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
^^*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 226, in generate*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
ngen += self.generate(section[subsection], subsection, gen_ts)*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
^^*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 309, in generate*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
searchList = self._getSearchList(encoding, timespan,*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:  
  ^^^*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/usr/share/weewx/weewx/cheetahgenerator.py", line 401, in 
_getSearchList*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
search_list += obj.get_extension_list(timespan, db_lookup)*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:  
^^^*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
  File "/etc/weewx/bin/user/belchertown.py", line 612, in 
get_extension_list*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
locale.format("%g", float(year_outTemp_max_range_total)),*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
^*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
AttributeError: module 'locale' has no attribute 'format'. Did you mean: 
'_format'?*

Sep 12 13:52:49 WXvm weectl[7581]: *ERROR weewx.reportengine:   
Generator terminated*


I read that the upgrade might have changed the installed modules of python3.

Is this really the root cause of this error message? And if so,  how do I 
fix it? Re-install the belchertown skin?


Anybodyelse did the Ubuntu upgrade recently?

-- 
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/7e3bbda4-addd-4ac4-b48b-f31808e42b7dn%40googlegroups.com.

Re: [weewx-user] MQTT error after upgrading to weewx 5.1 from 4.10

[Stefan Gliessmann]

Thank you for the feedback.

Today, I did perform a new install from scratch and - I think - during the 
initial weewx install, I was to quick in accepting the default values. And 
they include US unit.
In today's fresh install, I changed it to METRIC and, so far, it is running 
smoothly :)

On Saturday, August 31, 2024 at 5:37:12 PM UTC+2 Graham Eddy wrote:

> unless, i guess, the weewx.conf unit system is changed after data had 
> already been stored under previous unit system
> *⊣GE⊢*
>
> On 1 Sep 2024, at 1:33 AM, Karen K  wrote:
>
> The error message says the database one unit system and weewx.conf is the 
> other. One of them is US, the other one is METRIC. That is not possible.
>
>
> -- 
> 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/d3c75978-2367-4b1f-ab28-773bdc3d6598n%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/fdee0a04-35c5-4145-bcd4-c7d8fe786943n%40googlegroups.com.

[weewx-user] Re: MQTT error after upgrading to weewx 5.1 from 4.10

[Stefan Gliessmann]

31 17:20:27 rvwx weewxd[2124]: *CRITICAL __main__:   
self._check_units(accumulator.unit_system)*

Aug 31 17:20:27 rvwx weewxd[2124]: main()

Aug 31 17:20:27 rvwx weewxd[2124]:   File "/usr/share/weewx/weewxd.py", 
line 127, in main

Aug 31 17:20:27 rvwx weewxd[2124]: engine.run()

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 217, in run

Aug 31 17:20:27 rvwx weewxd[2124]: 
self.dispatchEvent(weewx.Event(weewx.POST_LOOP))

Aug 31 17:20:27 rvwx weewxd[2124]: *CRITICAL __main__: File 
"/usr/share/weewx/weewx/accum.py", line 620, in _check_units*

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent

Aug 31 17:20:27 rvwx weewxd[2124]: callback(event)

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 672, in post_loop

Aug 31 17:20:27 rvwx weewxd[2124]: *CRITICAL __main__:   raise 
ValueError("Unit system mismatch %d v. %d" % (self.unit_system,*

Aug 31 17:20:27 rvwx weewxd[2124]: self._software_catchup()

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 743, in _software_catchup

Aug 31 17:20:27 rvwx weewxd[2124]: *CRITICAL __main__:   
ValueError: Unit system mismatch 1 v. 16*

Aug 31 17:20:27 rvwx weewxd[2124]: 
self.engine.dispatchEvent(weewx.Event(weewx.NEW_ARCHIVE_RECORD,

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 241, in dispatchEvent

Aug 31 17:20:27 rvwx weewxd[2124]: callback(event)

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/engine.py", line 703, in new_archive_record

Aug 31 17:20:27 rvwx weewxd[2124]: *CRITICAL __main__:   Exiting.*

Aug 31 17:20:27 rvwx weewxd[2124]: dbmanager.addRecord(event.record,

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/manager.py", line 401, in addRecord

Aug 31 17:20:27 rvwx weewxd[2124]: self._updateHiLo(accumulator, cursor)

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/manager.py", line 1217, in _updateHiLo

Aug 31 17:20:27 rvwx weewxd[2124]: _stats_dict.updateHiLo(accumulator)

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/accum.py", line 446, in updateHiLo

Aug 31 17:20:27 rvwx weewxd[2124]: 
self._check_units(accumulator.unit_system)

Aug 31 17:20:27 rvwx weewxd[2124]:   File 
"/usr/share/weewx/weewx/accum.py", line 620, in _check_units

Aug 31 17:20:27 rvwx weewxd[2124]: raise ValueError("Unit system 
mismatch %d v. %d" % (self.unit_system,

Aug 31 17:20:27 rvwx weewxd[2124]: ValueError: Unit system mismatch 1 v. 16

Aug 31 17:20:27 rvwx systemd[1]: *weewx.service: Main process exited, 
code=exited, status=1/FAILURE*

Aug 31 17:20:27 rvwx systemd[1]: *weewx.service: Failed with result 
'exit-code'.*

Aug 31 17:20:27 rvwx systemd[1]: weewx.service: Consumed 2.427s CPU time.


On Saturday, August 31, 2024 at 5:08:16 PM UTC+2 Stefan Gliessmann wrote:

> I made yesterday a copy of my weewx.sdb. I just pushed the copy on my 
> raspi and now everything is solved!
>
> I am happy - eventhough I do not know what happened ...
>
>
> On Saturday, August 31, 2024 at 4:43:33 PM UTC+2 Stefan Gliessmann wrote:
>
>> Hello -
>>
>> for some moments today, the upgraded weewx system worked just fine.
>>
>> Unfortunately, not for long time ...
>>
>> The MQTT driver from https://github.com/matthewwall/weewx-mqtt exits 
>> with this message
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: DEBUG weewx.manager: Daily summary 
>> version is 4.0
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: MQTT: Unexpected 
>> exception of type *
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** Traceback 
>> (most recent call last):*
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
>> "/usr/share/weewx/weewx/restx.py", line 384, in run_loop*
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** 
>> self.process_record(_record, dbmanager)*
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
>> "/etc/weewx/bin/user/mqtt.py", line 513, in process_record*
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** record = 
>> self.get_record(record, dbm)*
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***  
>> *
>>
>> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
>> "/usr/share/weewx/weewx/restx.py", line 317, in get_record*
>>
>> Aug 31 16:38

[weewx-user] Re: MQTT error after upgrading to weewx 5.1 from 4.10

[Stefan Gliessmann]

I made yesterday a copy of my weewx.sdb. I just pushed the copy on my raspi 
and now everything is solved!

I am happy - eventhough I do not know what happened ...


On Saturday, August 31, 2024 at 4:43:33 PM UTC+2 Stefan Gliessmann wrote:

> Hello -
>
> for some moments today, the upgraded weewx system worked just fine.
>
> Unfortunately, not for long time ...
>
> The MQTT driver from https://github.com/matthewwall/weewx-mqtt exits with 
> this message
>
> Aug 31 16:38:40 rvwx weewxd[2937]: DEBUG weewx.manager: Daily summary 
> version is 4.0
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: MQTT: Unexpected 
> exception of type *
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** Traceback 
> (most recent call last):*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 384, in run_loop*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** 
> self.process_record(_record, dbmanager)*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
> "/etc/weewx/bin/user/mqtt.py", line 513, in process_record*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** record = 
> self.get_record(record, dbm)*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***  
> *
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
> "/usr/share/weewx/weewx/restx.py", line 317, in get_record*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** raise 
> ValueError(*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** ValueError: 
> Inconsistent units (1 vs 1 vs 16) when querying for rain24*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: *CRITICAL weewx.restx: MQTT: Thread 
> terminating. Reason: Inconsistent units (1 vs 1 vs 16) when querying for 
> rain24*
>
> Aug 31 16:38:40 rvwx weewxd[2937]: Exception in thread MQTT:
>
> Aug 31 16:38:40 rvwx weewxd[2937]: Traceback (most recent call last):
>
> Aug 31 16:38:40 rvwx weewxd[2937]:   File 
> "/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner
>
> Aug 31 16:38:40 rvwx weewxd[2937]: self.run()
>
> Aug 31 16:38:40 rvwx weewxd[2937]:   File 
> "/usr/share/weewx/weewx/restx.py", line 357, in run
>
> Aug 31 16:38:40 rvwx weewxd[2937]: self.run_loop(_manager)
>
> Aug 31 16:38:40 rvwx weewxd[2937]:   File 
> "/usr/share/weewx/weewx/restx.py", line 384, in run_loop
>
> Aug 31 16:38:40 rvwx weewxd[2937]: self.process_record(_record, 
> dbmanager)
>
> Aug 31 16:38:40 rvwx weewxd[2937]:   File "/etc/weewx/bin/user/mqtt.py", 
> line 513, in process_record
>
> Aug 31 16:38:40 rvwx weewxd[2937]: record = self.get_record(record, 
> dbm)
>
> Aug 31 16:38:40 rvwx weewxd[2937]:  
> 
>
> Aug 31 16:38:40 rvwx weewxd[2937]:   File 
> "/usr/share/weewx/weewx/restx.py", line 317, in get_record
>
> Aug 31 16:38:40 rvwx weewxd[2937]: raise ValueError(
>
> Aug 31 16:38:40 rvwx weewxd[2937]: ValueError: Inconsistent units (1 vs 1 
> vs 16) when querying for rain24
>
> Any recommendations on how to fix would be highly appreciated!
> Cheers!
>

-- 
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/1bd1e2c0-2d12-4d21-a65c-8f26b3d60848n%40googlegroups.com.

[weewx-user] MQTT error after upgrading to weewx 5.1 from 4.10

[Stefan Gliessmann]

Hello -

for some moments today, the upgraded weewx system worked just fine.

Unfortunately, not for long time ...

The MQTT driver from https://github.com/matthewwall/weewx-mqtt exits with 
this message

Aug 31 16:38:40 rvwx weewxd[2937]: DEBUG weewx.manager: Daily summary 
version is 4.0

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: MQTT: Unexpected 
exception of type *

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** Traceback (most 
recent call last):*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 384, in run_loop*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** 
self.process_record(_record, dbmanager)*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
"/etc/weewx/bin/user/mqtt.py", line 513, in process_record*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** record = 
self.get_record(record, dbm)*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***  
*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 317, in get_record*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** raise 
ValueError(*

Aug 31 16:38:40 rvwx weewxd[2937]: *ERROR weewx.restx: *** ValueError: 
Inconsistent units (1 vs 1 vs 16) when querying for rain24*

Aug 31 16:38:40 rvwx weewxd[2937]: *CRITICAL weewx.restx: MQTT: Thread 
terminating. Reason: Inconsistent units (1 vs 1 vs 16) when querying for 
rain24*

Aug 31 16:38:40 rvwx weewxd[2937]: Exception in thread MQTT:

Aug 31 16:38:40 rvwx weewxd[2937]: Traceback (most recent call last):

Aug 31 16:38:40 rvwx weewxd[2937]:   File 
"/usr/lib/python3.11/threading.py", line 1038, in _bootstrap_inner

Aug 31 16:38:40 rvwx weewxd[2937]: self.run()

Aug 31 16:38:40 rvwx weewxd[2937]:   File 
"/usr/share/weewx/weewx/restx.py", line 357, in run

Aug 31 16:38:40 rvwx weewxd[2937]: self.run_loop(_manager)

Aug 31 16:38:40 rvwx weewxd[2937]:   File 
"/usr/share/weewx/weewx/restx.py", line 384, in run_loop

Aug 31 16:38:40 rvwx weewxd[2937]: self.process_record(_record, 
dbmanager)

Aug 31 16:38:40 rvwx weewxd[2937]:   File "/etc/weewx/bin/user/mqtt.py", 
line 513, in process_record

Aug 31 16:38:40 rvwx weewxd[2937]: record = self.get_record(record, dbm)

Aug 31 16:38:40 rvwx weewxd[2937]:  

Aug 31 16:38:40 rvwx weewxd[2937]:   File 
"/usr/share/weewx/weewx/restx.py", line 317, in get_record

Aug 31 16:38:40 rvwx weewxd[2937]: raise ValueError(

Aug 31 16:38:40 rvwx weewxd[2937]: ValueError: Inconsistent units (1 vs 1 
vs 16) when querying for rain24

Any recommendations on how to fix would be highly appreciated!
Cheers!

-- 
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/62b368f6-ace0-4b50-a8f0-9fa144b201fdn%40googlegroups.com.

[weewx-user] Re: OpenWeather current data support in weewx-DWD

[Stefan Gliessmann]

*There is an additional feature I could not test: If your station is 
mounted on a vehicle and its location is available in WeeWX by observation 
types called latitude and longitude, you can specify "station = mobile", 
and data is always retrieved for the current location of the station as 
defined by the observation types latitude and longitude. I am sure there is 
at least one person who wants to try this feature.*

... and that person is going to test this very soon :)
On Friday, August 23, 2024 at 5:06:34 PM UTC+2 Karen K wrote:

> weewx-DWD  provides an interface to 
> various weather services. It uses their APIs to retrieve weather and 
> forecast data for use in WeeWX.
>
> OpenWeather  is an UK based company that 
> provides weather data based on calculations for every point on earth.
>
> Now weewx-DWD was updated to support retrieving actual weather data from 
> OpenWeather by their API. It includes additional observation types to the 
> archive record. The observation types are named like the standard 
> observation types of core WeeWX, but prepended by a configurable prefix. 
> You can retrieve data for more than one location in parallel.
>
> The configuration is simple. Specify latitude and longitude and the 
> language, the text messages should be provided in. You need an API key 
> which you get from OpenWeather for free. The configuration section in 
> weewx.conf could look like this:
>
> [WeatherServices]
>
> path = '.'
>
> [[current]]
>
> [[[FichtelbergOWM]]]
>
> provider = OpenWeather
>
> station = Fichtelberg
>
> latitude = 50.4283
>
> longitude = 12.9536
>
> lang = 'en'
>
> prefix = 'xyz'
>
> api_key = 'API key that you got from OpenWeather'
>
> This would retrieve current weather data for mount Fichtelberg in Saxony. 
> You can specify any other location around the world.
>
> The prefix is set to 'xyz' here. This means, if you want to display the 
> temperature you would write $current.xyzOutTemp in the skin template. 
> $current.xyzIcon.raw provides an icon file name, and 
> $current.xyzIcontitle.raw a text message describing the current weather.
>
> As OpenWeather does not provide dewpoint, it is calculated within 
> weewx-DWD using the WeeWX formula.
>
> WeeWX uses a constant archive interval, but OpenWeather provides their 
> data with a varying interval. Therefore, weewx-DWD stores the data it got 
> from OpenWeather to a separate database. This database can be made 
> available to WeeWX by configuring an appropriate binding. 
>
> I see no use in putting downloaded data into LOOP packets here, as their 
> data is updated at most once per 5 minutes.
>
> There is an additional feature I could not test: If your station is 
> mounted on a vehicle and its location is available in WeeWX by observation 
> types called latitude and longitude, you can specify "station = mobile", 
> and data is always retrieved for the current location of the station as 
> defined by the observation types latitude and longitude. I am sure there 
> is at least one person who wants to try this feature.
>
>

-- 
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/60696900-82cf-42fe-a71d-0a4b439caecbn%40googlegroups.com.

[weewx-user] MQTT change GPS coordinates' units from None to compass_degrees or " °"

[Stefan Gliessmann]

A GPS device in my RV sends the current coordinates via MQTT to my weewx 
server.
The coordinates are displayed with units = None.
Trying to change them to units = degree_compass or units = " °" results in 
the below error:

Aug 21 15:28:26 rvwx weewx[1590] DEBUG weewx.units: Unable to convert from 
None to  °
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: MQTT: Unexpected 
exception of type 
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** Traceback (most 
recent call last):
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/restx.py", line 382, in run_loop
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** 
self.process_record(_record, dbmanager)
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
"/usr/share/weewx/user/mqtt.py", line 516, in process_record
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** data = 
self.filter_data(record)
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
"/usr/share/weewx/user/mqtt.py", line 496, in filter_data
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** v = 
weewx.units.convert(from_t, to_units)[0]
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: ***   File 
"/usr/share/weewx/weewx/units.py", line 1454, in convert
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** conversion_func 
= conversionDict[val_t[1]][target_unit]
Aug 21 15:28:26 rvwx weewx[1590] ERROR weewx.restx: *** KeyError: None
Aug 21 15:28:26 rvwx weewx[1590] CRITICAL weewx.restx: MQTT: Thread 
terminating. Reason: None

Here is the relevant section from weewx.conf to display coordinates in 
belchertown skin:
 [[MQTT]]
server_url = mqtt://
:yy...@wxvm.bz3gfkrlqtrsc3sv.myfritz.net:1883/ 
<http://:y...@wxvm.bz3gfkrlqtrsc3sv.myfritz.net:1883/>
topic = RV
unit_system = METRIC
binding = loop, archive
log_success = true
   [[[inputs]]]
latitude
# units = " °"
 format = %.3f

and MQTT subscribe to Write the GPS data received via MQTT into the weewx 
db:
[MQTTSubscribeService]
# This section is for the MQTTSubscribe service.

# Turn the service on and off.
# Default is: true
# Only used by the service.
enable = true
log = true

# The MQTT server.
# Default is localhost.
host = "wxvm.bz3gfkrlqtrsc3sv.myfritz.net"

# The port to connect to.
# Default is 1883.
port = 1883

# Maximum period in seconds allowed between communications with the 
broker.
# Default is 60.
keepalive = 60

# username for broker authentication.
# Default is None.
username = 

# password for broker authentication.
# Default is None.
password = 

# The binding, loop or archive.
# Default is: loop
# Only used by the service.
binding = loop

# The message handler to use
[[message_callback]]
# The format of the MQTT payload.
# Currently support: individual, json, keyword
# Must be specified.
type = json

# The topics to subscribe to.
[[topics]]
# Units for MQTT payloads without unit value.
# Valid values: US, METRIC, METRICWX
# Default is: US
unit_system = US
#adjust_start_time = 1
use_server_datetime = True
use_topic_as_fieldname = true

[[[RVGPS/#]]]
# The WeeWX name.
# Default is the name from MQTT.
#name = Latitude

# True if the incoming data should not be processed into WeeWX.
# Valid values: True, False
# Default is False
ignore = False

# True if the incoming data is cumulative.
# Valid values: True, False
# Default is False
#contains_total = False

# The conversion type necessary for WeeWX compatibility
# Valid values: bool, float, int, none
# Default is float
#conversion_type = int

# The units of the incoming data.
# Useful if this field's units differ from the topic's 
unit_system's units.
# Valid values: see, 
http://www.weewx.com/docs/customizing.htm#units
# Default is not set
#units = degree_compass  

[image: Screenshot 2024-08-21 at 15.40.43.png]

This is how it Looks on belchertown skin with units = None, e.g. no change 
of units intented.

TIA,
Stefan

-- 
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/a9592842-2b05-46f6-9959-1e9cf791edcan%40googlegroups.com.

[weewx-user] Re: Weewx Weather iOS App

[Stefan Gliessmann]

Thanks, Gerard!

I look for a way to share data from my weewx pws as a complication on my 
apple watch. I was hoping that this app could help, but it doesn't.

On Sunday, August 4, 2024 at 4:27:38 PM UTC+2 Gerard Cerchio wrote:

> I use the smartphone skin on my site 
> <https://www.oceanbeach.org/weewx/index.html>it covers all smart phones. 
> The incoming screen size is checked in index.html.template. I redirect to 
> the smart phone skin if it's a small screen. I added a row to to the 
> smartphone that allows the user to view the full sized site by creating 
> another template bigphone.html that does not have the screen size check in 
> it. I try to minimize the number of apps in IOS and Android which are both 
> high value malware targets.
> On Saturday, August 3, 2024 at 8:14:45 AM UTC-7 Stefan Gliessmann wrote:
>
>> Is anybody using this iOS app?
>>
>> I was able to Install the extension and the report is running without 
>> errors. I see also content on my hosting server, but when entering the web 
>> address, the app cannot find any data ...
>>
>> https://emkubed.com.au/index.php/weewx-weather-ios-app/
>>
>

-- 
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/923e0dd5-ecf8-49ca-9991-3875c71cbee6n%40googlegroups.com.

[weewx-user] Weewx Weather iOS App

[Stefan Gliessmann]

Is anybody using this iOS app?

I was able to Install the extension and the report is running without 
errors. I see also content on my hosting server, but when entering the web 
address, the app cannot find any data ...

https://emkubed.com.au/index.php/weewx-weather-ios-app/

-- 
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/37975d94-67af-4213-be75-50d5f8dbcc7fn%40googlegroups.com.

[weewx-user] Re: Belchertown skin Index_hook_after_forecast.inc

[Stefan Gliessmann]

I solved it this way (after reading up on bootstrap):

 

   

   



  

   

 https://www.dwd.de/DWD/warnungen/warnstatus/SchilderHA.jpg";>https://www.dwd.de/DWD/warnungen/warnstatus/SchilderHA.jpg"; width="150%" 
height="150%">



   


  

   

 #include raw "dwd/warn-HI.inc"

   

  



 



On Tuesday, July 23, 2024 at 3:26:13 PM UTC+2 Stefan Gliessmann wrote:

> I am trying to display an image next to the weather warn message from the 
> dwd weewx extension.
>
> However, this is what I get (above each other and not next to each other):
> [image: Screenshot 2024-07-23 at 15.23.17.png]
>
> This is the content of the inc file:
>
> 
>
> 
>
>   
>
> 
>
>   https://www.dwd.de/DWD/warnungen/warnstatus/SchilderHA.jpg
> ">https://www.dwd.de/DWD/warnungen/warnstatus/SchilderHA.jpg"; 
> width="40%" height="40%">
>
> 
>
> 
>
>   #include raw "dwd/warn-HI.inc"
>
> 
>
>   
>
> 
>
>
> Any hint would be highly appreciated!
>
>
> TIA,
>
> Stefan
>
>
>

-- 
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/1292fd5d-2daa-4b62-9f17-08ea7fbe90c4n%40googlegroups.com.

Re: [weewx-user] Re: Biowetter and Pollen forecast in weewx-DWD

[Stefan Gliessmann]

Awesome!

Thank you!

I am updating weewx.conf as we are writting ;)

On Saturday, July 13, 2024 at 10:13:02 PM UTC+2 Karen K wrote:

> Some instructions:
>
>- Biowettervorhersage 
>
>- Pollenflugvorhersage 
>
>
>
>

-- 
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/8760e424-80de-4a6f-86d2-b3a8a7bdc35cn%40googlegroups.com.

[weewx-user] Re: DWD warnings

[Stefan Gliessmann]

[WeatherServices]

path = /etc/weewx/skins/Belchertown/dwd

[[current]]

safe = True

[[forecast]]

icons = ../images

orientation = "h,v"

show_obs_symbols = True

show_obs_description = True

show_placemark = True

[[warning]]

# icons = ../images

# icons = replace_me

[[[103254000]]]

provider = BBK

# Die Überschrift ist die Kreiskennung.

file = HIX

[[[Hildesheim]]]

provider = BBK

county = 803254021

file = HI

For whatever reason, if I comment the location of the icons in the warning 
section, it works again!!!

Apologies for the extra spam!

On Tuesday, July 9, 2024 at 4:40:52 PM UTC+2 Stefan Gliessmann wrote:

> After updating to WeeWx 5.0 I got DWD forecasts and warnings working, but 
> since several days DWD warnings are no longer updated.
> I am getting the same error message as one year ago ...
>
> teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=city --verbose
>
> Using test configuration
>
> -- configuration data --
>
> log success:   True
>
> log failure:   True
>
> filter area:   {'Stadt Döbeln': 'DL', 'Stadt Leipzig': 'L', 'Stadt Jena': 
> 'J', 'Stadt Dresden': 'DD'}
>
> target path:   .
>
> icon URL:  ../dwd/warn_icons_50x50
>
> logo URL:  None
>
> -- configuration dict --
>
> {
>
> "log_success": true,
>
> "log_failure": true,
>
> "path": ".",
>
> "dwd_icons": "../dwd/warn_icons_50x50",
>
> "dwd_resolution": "city",
>
> "1": {
>
> "path": ".",
>
> "provider": "MSC",
>
> "office": "CWHX",
>
> "county": "Upper Lake Melville",
>
> "file": "XX"
>
> },
>
> "counties": {
>
> "Kreis Mittelsachsen - Tiefland": "DL",
>
> "Stadt Leipzig": "L",
>
> "Stadt Jena": "J",
>
> "Stadt Dresden": "DD"
>
> },
>
> "cities": {
>
> "Stadt Döbeln": "DL",
>
> "Stadt Leipzig": "L",
>
> "Stadt Jena": "J",
>
> "Stadt Dresden": "DD"
>
> }
>
> }
>
> 
>
> -- get_warnings ---
>
> INFO about to download zip file list from 
> https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT
>
> INFO zip file list from 
> https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/ 
> successfully downloaded
>
> INFO processing file 
> Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip
>
> INFO about to download 
> https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip
>
> INFO successfully downloaded 
> https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip
>
> teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=city --verbose 
> --weewx
>
> Using configuration file /etc/weewx/weewx.conf
>
> Traceback (most recent call last):
>
>   File "/usr/local/bin/dwd-cap-warnings", line 1993, in 
>
> cap = CAPwarnings(config,provider,options.verbose)
>
>   File "/usr/local/bin/dwd-cap-warnings", line 1761, in __init__
>
> sec_dict = 
> accumulateLeaves(config_dict['WeatherServices']['warning'][sec])
>
>   File "/usr/local/bin/dwd-cap-warnings", line 142, in accumulateLeaves
>
> y.update({a:x.parent.parent[a] for a in x.parent.parent.scalars})
>
> AttributeError: 'str' object has no attribute 'parent'
>
> teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=county 
> --verbose --weewx
>
> Using configuration file /etc/weewx/weewx.conf
>
> Traceback (most recent call last):
>
>   File "/usr/local/bin/dwd-cap-warnings", line 1993, in 
>
> cap = CAPwarnings(config,provider,options.verbose)
>
>   File "/usr/local/bin/dwd-cap-warnings", line 1761, in __init__
>
> sec_dict = 
> accumulateLeaves(config_dict['

[weewx-user] Re: DWD warnings

[Stefan Gliessmann]

After updating to WeeWx 5.0 I got DWD forecasts and warnings working, but 
since several days DWD warnings are no longer updated.
I am getting the same error message as one year ago ...

teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=city --verbose

Using test configuration

-- configuration data --

log success:   True

log failure:   True

filter area:   {'Stadt Döbeln': 'DL', 'Stadt Leipzig': 'L', 'Stadt Jena': 
'J', 'Stadt Dresden': 'DD'}

target path:   .

icon URL:  ../dwd/warn_icons_50x50

logo URL:  None

-- configuration dict --

{

"log_success": true,

"log_failure": true,

"path": ".",

"dwd_icons": "../dwd/warn_icons_50x50",

"dwd_resolution": "city",

"1": {

"path": ".",

"provider": "MSC",

"office": "CWHX",

"county": "Upper Lake Melville",

"file": "XX"

},

"counties": {

"Kreis Mittelsachsen - Tiefland": "DL",

"Stadt Leipzig": "L",

"Stadt Jena": "J",

"Stadt Dresden": "DD"

},

"cities": {

"Stadt Döbeln": "DL",

"Stadt Leipzig": "L",

"Stadt Jena": "J",

"Stadt Dresden": "DD"

}

}



-- get_warnings ---

INFO about to download zip file list from 
https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT

INFO zip file list from 
https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/ 
successfully downloaded

INFO processing file 
Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip

INFO about to download 
https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip

INFO successfully downloaded 
https://opendata.dwd.de/weather/alerts/cap/COMMUNEUNION_CELLS_STAT/Z_CAP_C_EDZW_LATEST_PVW_STATUS_PREMIUMCELLS_COMMUNEUNION_DE.zip

teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=city --verbose 
--weewx

Using configuration file /etc/weewx/weewx.conf

Traceback (most recent call last):

  File "/usr/local/bin/dwd-cap-warnings", line 1993, in 

cap = CAPwarnings(config,provider,options.verbose)

  File "/usr/local/bin/dwd-cap-warnings", line 1761, in __init__

sec_dict = 
accumulateLeaves(config_dict['WeatherServices']['warning'][sec])

  File "/usr/local/bin/dwd-cap-warnings", line 142, in accumulateLeaves

y.update({a:x.parent.parent[a] for a in x.parent.parent.scalars})

AttributeError: 'str' object has no attribute 'parent'

teffi@WXvm:/etc/weewx$ sudo dwd-cap-warnings --resolution=county --verbose 
--weewx

Using configuration file /etc/weewx/weewx.conf

Traceback (most recent call last):

  File "/usr/local/bin/dwd-cap-warnings", line 1993, in 

cap = CAPwarnings(config,provider,options.verbose)

  File "/usr/local/bin/dwd-cap-warnings", line 1761, in __init__

sec_dict = 
accumulateLeaves(config_dict['WeatherServices']['warning'][sec])

  File "/usr/local/bin/dwd-cap-warnings", line 142, in accumulateLeaves

y.update({a:x.parent.parent[a] for a in x.parent.parent.scalars})

AttributeError: 'str' object has no attribute 'parent'

and my /etc/weewx/weewx.conf

[DeutscherWetterdienst]

# Konfiguration für dwd-cap-warnings

[[warning]]

icons = ../images

states = Niedersachsen

resolution = county|city

[[[counties]]]

Kreis Hildesheim = HIX

[[[cities]]]

Stadt Hildesheim = HI

[WeatherServices]

path = /etc/weewx/skins/Belchertown/dwd

[[current]]

safe = True

[[forecast]]

icons = ../images

orientation = "h,v"

show_obs_symbols = True

show_obs_description = True

    show_placemark = True

[[warning]]

icons = ../images

# icons = replace_me

[[[103254000]]]

provider = BBK

# Die Überschrift ist die Kreiskennung.

file = HIX

[[[Hildesheim]]]

provider = BBK

county = 803254021

file = HI


[[Belchertown]]

section = Belchertown

warnings = HIX

forecast = K1546

include_advance_warings = 3600

aqi_source = aeris

#compass_lang = replace_me

any hint would b

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefan Gliessmann]

Thanks a lot!
I will try this later ;)


On Tue, Feb 6, 2024 at 1:43 PM Dominic Reich  wrote:

> 'michael.k...@gmx.at' via weewx-user  wrote:
>
> >
> >sudo apt install weewx=4.10.2
>
> and to not upgrade again set it on hold:
>
> sudo apt-mark hold weewx
>
> >Stefan Gliessmann schrieb am Dienstag, 6. Februar 2024 um 13:02:38 UTC+1:
> >
> >I run weewx 4.10.2 on Ubuntu.
> >I did an sudo apt update, too,  and weewx 5.x got installed.
> >Since then, weewx is no longer running.
> >
> >How did you revert back to weewx 4.10.2?
> >
> >TIA,
> >Stefan
> >
> >On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis
> wrote:
> >
> >
> >I had the same error with sdr driver(weewx v5 )  running on
> debian 12 .
> >The problem solved by making udev rules ... maybe you are in the
> same
> >situation as i was.
> >
> >
> >Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk 
> έγραψε:
> >
> >The system was running weewx v5.0.0 with no issue then we did
> the
> >upgrade to v5.0.1 (sudo apt update) and weewx failed to run.
> >we downgraded weewx to v5.0.0 but it did not work this time,
> so we
> >went back to v4.10.2 and it run just fine.
> >did the upgrade again and got the same error.so we are back to
> >v4.10.2
> >we tested the sdr hardware using rtl_433 and it is working
> fine.
> >we are not sure of what to do next!
> >
> >log:
> >weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
> >weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to
> >database 'weewx.sdb'
> >weewxd[2386]: INFO weewx.manager: Starting backfill of daily
> >summaries
> >weewxd[2386]: INFO weewx.manager: Daily summaries up to date
> >weewxd[2386]: INFO weewx.engine: Starting main packet loop.
> >weewxd[2386]: ERROR user.sdr: rtl_433 version
> 23.11-41-g06b03b7a
> >branch master at 202402051043 inputs file rtl_tcp RTL-SDR
> >weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any
> >messages, warnings, and errors in the console.
> >weewxd[2386]: ERROR user.sdr: usb_open error -3
> >weewxd[2386]: ERROR user.sdr: Please fix the device
> permissions,
> >e.g. by installing the udev rules file rtl-sdr.rules
> >weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting
> engine
> >down.
> >weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f
> 433.7M -s
> >1024k -R 40
> >weewxd[2386]: Exception in thread stdout-thread:
> >weewxd[2386]: Traceback (most recent call last):
> >weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line
> 954,
> >in _bootstrap_inner
> >weewxd[2386]: Exception in thread stderr-thread:
> >weewxd[2386]: Traceback (most recent call last):
> >weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line
> 954,
> >in _bootstrap_inner
> >weewxd[2386]: self.run()
> >weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197,
> in run
> >weewxd[2386]: for line in iter(self._fd.readline, ''):
> >weewxd[2386]: ValueError: PyMemoryView_FromBuffer():
> info->buf must
> >not be NULL
> >weewxd[2386]: self.run()
> >weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197,
> in run
> >weewxd[2386]: for line in iter(self._fd.readline, ''):
> >weewxd[2386]: ValueError: PyMemoryView_FromBuffer():
> info->buf must
> >not be NULL
> >weewxd[2386]: INFO user.sdr: shutdown complete
> >weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433
> >process is not running
> >weewxd[2386]: CRITICAL __main__:   Waiting 60.0
> seconds
> >then retrying...
> >
> >--
> >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,
> > 

Re: [weewx-user] weewx v5.0.1 upgrade problem

[Stefan Gliessmann]

I run weewx 4.10.2 on Ubuntu.
I did an sudo apt update, too,  and weewx 5.x got installed.
Since then, weewx is no longer running.

How did you revert back to weewx 4.10.2? 

TIA,
Stefan

On Tuesday, February 6, 2024 at 10:36:52 AM UTC+1 Stefanos Kalaitzis wrote:

> I had the same error with sdr driver(weewx v5 )  running on debian 12 . 
> The problem solved by making udev rules ... maybe you are in the same 
> situation as i was. 
>
> Στις Τρί 6 Φεβ 2024, 11:29 ο χρήστης Mks Mk  έγραψε:
>
>> The system was running weewx v5.0.0 with no issue then we did the upgrade 
>> to v5.0.1 (sudo apt update) and weewx failed to run.
>> we downgraded weewx to v5.0.0 but it did not work this time, so we went 
>> back to v4.10.2 and it run just fine.
>> did the upgrade again and got the same error.so we are back to v4.10.2
>> we tested the sdr hardware using rtl_433 and it is working fine.
>> we are not sure of what to do next!
>>
>> log:
>> weewxd[2386]: INFO __main__: Starting up weewx version 5.0.1
>> weewxd[2386]: INFO weewx.engine: Using binding 'wx_binding' to database 
>> 'weewx.sdb'
>> weewxd[2386]: INFO weewx.manager: Starting backfill of daily summaries
>> weewxd[2386]: INFO weewx.manager: Daily summaries up to date
>> weewxd[2386]: INFO weewx.engine: Starting main packet loop.
>> weewxd[2386]: ERROR user.sdr: rtl_433 version 23.11-41-g06b03b7a branch 
>> master at 202402051043 inputs file rtl_tcp RTL-SDR
>> weewxd[2386]: ERROR user.sdr: Use "-F log" if you want any messages, 
>> warnings, and errors in the console.
>> weewxd[2386]: ERROR user.sdr: usb_open error -3
>> weewxd[2386]: ERROR user.sdr: Please fix the device permissions, e.g. by 
>> installing the udev rules file rtl-sdr.rules
>> weewxd[2386]: INFO weewx.engine: Main loop exiting. Shutting engine down.
>> weewxd[2386]: INFO user.sdr: shutdown process rtl_433 -f 433.7M -s 1024k 
>> -R 40
>> weewxd[2386]: Exception in thread stdout-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: Exception in thread stderr-thread:
>> weewxd[2386]: Traceback (most recent call last):
>> weewxd[2386]:   File "/usr/lib/python3.9/threading.py", line 954, in 
>> _bootstrap_inner
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: self.run()
>> weewxd[2386]:   File "/etc/weewx/bin/user/sdr.py", line 197, in run
>> weewxd[2386]: for line in iter(self._fd.readline, ''):
>> weewxd[2386]: ValueError: PyMemoryView_FromBuffer(): info->buf must not 
>> be NULL
>> weewxd[2386]: INFO user.sdr: shutdown complete
>> weewxd[2386]: CRITICAL __main__: Caught WeeWxIOError: rtl_433 process is 
>> not running
>> weewxd[2386]: CRITICAL __main__:   Waiting 60.0 seconds then 
>> retrying...
>>
>> -- 
>> 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/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/4c62d6c3-d690-49e8-8151-8b9af8dd5b43n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/ab729bc6-195f-498e-b0db-e404297666den%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

I am using the Belchertown skin.

"These settings need to be enabled in order for the skin to work. Within 
weewx.conf, under [Station] make sure you have:

   - latitude - used for forecasting and earthquake data
   - longitude - used for forecasting and earthquake data"

How can I change the use of latitude & longitude from the stanze [Station] to 
current values from the weewx.sdb $latitude and $longitude for weather 
forecasting?

I want to use the most current poisition for forecasting either thru 
Belchertown AerisWeather or weewx-DWD dwd-mosix WeatherService with 
openmeteo.

For both forecasting options, it seems that the location is read from 
[Station] and not from weewx.sdb $latitude and $longitude.

TIA!

On Friday, October 27, 2023 at 3:40:42 PM UTC+2 Stefan Gliessmann wrote:

> Hi Rich et al.,
>
> today, I finally was able to do more trouble shooting ...
>
> I let WeeWX nun from CLI and - surprise, surprise - the archive records 
> included the GPS coordinates.
> I double checked in my weewx.sdb and since Oct 25, 2023 14:55:00 the 
> coordinates are recorded in the db!
>
> YEAH :)
>
> I guess I have not looked at the last page of the db before as I have not 
> changed any configuration since Wednesday ... LOL!
>
> Ok - now I just have to figure out why the forecast is not using the 
> coordinates for the Belchertown skin forecast using dwd-mosmix ... once 
> that is achieved, I am extremely happy.
>
> AGAIN - huge thanks to this group whose members always nudges me in the 
> right direction!
>
> Thank you,
> Stefan
>
> On Thu, Oct 26, 2023 at 2:54 PM bell...@gmail.com  
> wrote:
>
>> Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
>> Archive topic is None
>> This is just saying you are not using an experimental option, 
>> archive_topic (
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-experimental-options#archive_topic
>> ).
>>
>> Oct 25 15:18:08 rvwx weewx[32590] DEBUG user.MQTTSubscribe: (Service) 
>> data-> final packet is 2023-10-25 15:18:08 CEST (1698239888): 'dateTime': 
>> '1698239888.0', 'inHumidity': '74', 'inTemp': '13.2', 'latitude': 
>> '52.152477', 'longitude': '9.929382', 'outHumidity': '86', 'outTemp': 
>> '12.9', 'pressure': '987.0', 'relbarometer': '987.0', 'usUnits': '17', 
>> 'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch8_batt': 'None', 
>> 'wh31_ch8_sig': '0'
>> This is saying that MQTTSubscribe has updated the loop packet. So WeeWX 
>> should be using this to update the archive record and database.
>>
>> Next steps. Run WeeWX from the command line for a couple of archive 
>> periods. This will print the loop packets and archive records to the 
>> console. Post the console and complete log, from startup through the 
>> archive periods. Double check that the log does not have any sensitive 
>> information.
>>
>> - rich
>>
>

-- 
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/4d800788-2578-45da-81cd-0326dadad5ddn%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Hi Rich et al.,

today, I finally was able to do more trouble shooting ...

I let WeeWX nun from CLI and - surprise, surprise - the archive records
included the GPS coordinates.
I double checked in my weewx.sdb and since Oct 25, 2023 14:55:00 the
coordinates are recorded in the db!

YEAH :)

I guess I have not looked at the last page of the db before as I have not
changed any configuration since Wednesday ... LOL!

Ok - now I just have to figure out why the forecast is not using the
coordinates for the Belchertown skin forecast using dwd-mosmix ... once
that is achieved, I am extremely happy.

AGAIN - huge thanks to this group whose members always nudges me in the
right direction!

Thank you,
Stefan

On Thu, Oct 26, 2023 at 2:54 PM bell...@gmail.com 
wrote:

> Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) Archive
> topic is None
> This is just saying you are not using an experimental option,
> archive_topic (
> https://github.com/bellrichm/WeeWX-MQTTSubscribe/wiki/Configuring-experimental-options#archive_topic
> ).
>
> Oct 25 15:18:08 rvwx weewx[32590] DEBUG user.MQTTSubscribe: (Service)
> data-> final packet is 2023-10-25 15:18:08 CEST (1698239888): 'dateTime':
> '1698239888.0', 'inHumidity': '74', 'inTemp': '13.2', 'latitude':
> '52.152477', 'longitude': '9.929382', 'outHumidity': '86', 'outTemp':
> '12.9', 'pressure': '987.0', 'relbarometer': '987.0', 'usUnits': '17',
> 'wh31_ch1_batt': '0', 'wh31_ch1_sig': '4', 'wh31_ch8_batt': 'None',
> 'wh31_ch8_sig': '0'
> This is saying that MQTTSubscribe has updated the loop packet. So WeeWX
> should be using this to update the archive record and database.
>
> Next steps. Run WeeWX from the command line for a couple of archive
> periods. This will print the loop packets and archive records to the
> console. Post the console and complete log, from startup through the
> archive periods. Double check that the log does not have any sensitive
> information.
>
> - rich
>

-- 
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/CACXWM9Q47dpEZRB5uAwWoc8027LXUf3sj0E4PfUu9cA1W1DFJA%40mail.gmail.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

nore': 'False'}}, 'log': 
'true', 'port': '1883', 'binding': 'loop', 'enable': 'true', 'keepalive': 
'60', 'host': 'weewx.bz3gfkrlqtrsc3sv.myfritz.net', 'message_callback': 
{'type': 'json'}}
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
'use_topic_as_fieldname' option is no longer needed and can be removed.
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager self.collect_wind_across_loops is True
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager self.collect_observations is False
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager single_queue is False
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager single_queue is False
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager self.subscribed_topics is {"RVGPS/#": {"ignore": false, 
"subscribe": true, "conversion_func": {"source": "lambda x: to_float(x)", 
"compiled": " at 0xf72d89b8>"}, "unit_system": 1, 
"msg_id_field": null, "qos": 0, "topic_tail_is_fieldname": false, 
"use_server_datetime": true, "datetime_format": null, "offset_format": 
null, "ignore_msg_id_field": [], "fields": {"RVGPS/#": {"name": "RVGPS/#", 
"ignore": false, "contains_total": false, "total_wrap_around": false, 
"conversion_func": {"source": "lambda x: to_float(x)", "compiled": 
" at 0xf72ed970>"}, "conversion_type": "float", 
"conversion_error_to_none": false}}, "queue": {"name": "RVGPS/#", "type": 
"normal", "ignore_start_time": false, "ignore_end_time": false, 
"adjust_start_time": 0.0, "adjust_end_time": 0.0, "max_size": 2147483647, 
"data": "deque([])"}, "filters": {}, "message-1698241329.683747": {}}, 
"1698241329.686176-windGust-windGustDir-windDir-windSpeed": {"subscribe": 
false, "message-1698241329.683747": {}, "unit_system": 1, "qos": 0, 
"topic_tail_is_fieldname": false, "use_server_datetime": true, 
"datetime_format": null, "offset_format": null, "queue": {"name": 
"1698241329.686176-windGust-windGustDir-windDir-windSpeed", "type": 
"collector", "ignore_start_time": false, "ignore_end_time": false, 
"adjust_start_time": 0.0, "adjust_end_time": 0.0, "max_size": 2147483647, 
"data": "deque([])"}}}
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager self.cached_fields is {}
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
message_callback_provider_name is user.MQTTSubscribe.MessageCallbackProvider
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) clientid 
is MQTTSubscribe-3055
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
client_session is True
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) host is 
weewx.bz3gfkrlqtrsc3sv.myfritz.net
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) port is 
1883
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
keepalive is 60
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) username 
is teffi
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
min_delay is 1
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
max_delay is 120
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) password 
is set
Oct 25 15:42:09 rvwx weewx[460] *INFO user.MQTTSubscribe: (Service) Archive 
topic is None*
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MQTTSubscribe MQTT: Sending CONNECT (u1, p1, wr0, wq0, wf0, c1, k60) 
client_id=b'MQTTSubscribe-3055'
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) binding 
is loop
Oct 25 15:42:09 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
Starting loop
Oct 25 15:42:09 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) Waiting 
for MQTT connection.
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MQTTSubscribe MQTT: Received CONNACK (0, 0)
Oct 25 15:42:10 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
Connected with result code 0
Oct 25 15:42:10 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
Connected flags {'session present': 0}
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MQTTSubscribe MQTT: Sending SUBSCRIBE (d0, m1) [(b'RVGPS/#', 0)]
Oct 25 15:42:10 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
Subscribing to RVGPS/# has a mid 1 and rc 0
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MQTTSubscribe MQTT: Received SUBACK
Oct 25 15:42:10 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) 
Subscribed to mid: 1 is size 1 has a QOS of 0
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MQTTSubscribe MQTT: Received PUBLISH (d0, q0, r0, m0), 'RVGPS/loop', ... 
 (76 bytes)
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
MessageCallbackProvider data-> incoming topic: RVGPS/loop, QOS: 0, retain: 
0, payload: b'{"dateTime": "1698241325", "latitude": "52.152546", 
"longitude": "9.929337"}'
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager data-> incoming RVGPS/loop: 'dateTime': '1698241325.0', 
'latitude': '52.152546', 'longitude': '9.929337'
Oct 25 15:42:10 rvwx weewx[460] DEBUG user.MQTTSubscribe: (Service) 
TopicManager Added to queue RVGPS/loop RVGPS/# 2023-10-25 15:42:10 CEST 
(1698241330): 'dateTime': '1698241330.3411937', 'latitude': '52.152546', 
'longitude': '9.929337', 'usUnits': '1'
Oct 25 15:42:10 rvwx weewx[460] INFO user.MQTTSubscribe: (Service) MQTT 
initialization complete.

I just notice that there is no archive topic set. Is that the reason why 
nothing is written to the weewx.sdb?
*user.MQTTSubscribe: (Service) Archive topic is None*

TIA for any hint!
On Sunday, October 22, 2023 at 4:38:49 PM UTC+2 Stefan Gliessmann wrote:

> Thank you, Greg!
>
> That makes so much sense now to me!
> 🙏😇
>
>
> Greg Troxel  schrieb am So. 22. Okt. 2023 um 16:28:
>
>> Stefan Gliessmann  writes:
>>
>> > I thought that having the topic's binding set to archive would populate 
>> the 
>> > weewx db accordingly ...
>>
>> I think you are missing that MQTT is supported in two distinct ways and
>> that these two methods have nothing to do with each other.
>>
>>   The mqtt extension
>> https://github.com/matthewwall/weewx-mqtt
>>   takes data from weewx (archive and loop) and publishes it to
>>   MQTT.  This is used to provide data to be read by skins like
>>   Belchertown and things like Home Assistant.
>>
>>   The mqtt-subscribe service/driver
>> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>>   takes data from MQTT and stores it in the database.  This is used to
>>   add sensors to weewx, from data that appears over MQTT.
>>
>>
>> You should be able to store coordinates with mqtt-subscribe and then
>> also publish those so HA/skin/whatever can see them.  But they are in
>> the db (or as loop packets) in the middle.
>>
>

-- 
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/47df9630-cbe6-4ea7-a8ae-2e68c27e63c3n%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Thank you, Greg!

That makes so much sense now to me!
🙏😇


Greg Troxel  schrieb am So. 22. Okt. 2023 um 16:28:

> Stefan Gliessmann  writes:
>
> > I thought that having the topic's binding set to archive would populate
> the
> > weewx db accordingly ...
>
> I think you are missing that MQTT is supported in two distinct ways and
> that these two methods have nothing to do with each other.
>
>   The mqtt extension
> https://github.com/matthewwall/weewx-mqtt
>   takes data from weewx (archive and loop) and publishes it to
>   MQTT.  This is used to provide data to be read by skins like
>   Belchertown and things like Home Assistant.
>
>   The mqtt-subscribe service/driver
> https://github.com/bellrichm/WeeWX-MQTTSubscribe
>   takes data from MQTT and stores it in the database.  This is used to
>   add sensors to weewx, from data that appears over MQTT.
>
>
> You should be able to store coordinates with mqtt-subscribe and then
> also publish those so HA/skin/whatever can see them.  But they are in
> the db (or as loop packets) in the middle.
>

-- 
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/CACXWM9Qcuk%2Bjtv9_y8iJmvEPD7m%2BKYmgSfisbDxn3mh%3D%2B%3DE59w%40mail.gmail.com.

Re: [weewx-user] Re: MQTT disconnect when MQTT publishes new data since adding soil moisture sensors

[Stefan Gliessmann]

Oh My God!
THANK YOU!

lightning_distance, lightning_strike_count
are published since I added the lightning sensor in August 2023.

However, I added lightning_distance & lightning_strike_count in the
weewx.conf Belchertown stanza the same time as I added graph.conf for the
soil moisture sensors.

#station_observations = inTemp, inHumidity, outHumidity,
barometer, dewpoint, rainWithRainRate, radiation, lightning_distance,
lightning_strike_count

station_observations = inTemp, inHumidity, outHumidity,
barometer, dewpoint, rainWithRainRate, radiation, lightning_distance


Since it showed correctly "0" in the skin, I was not even thinking that
this could be the issue.

I just removed it in weewx.conf and now MQTT just works fine again!


Thank you again for your investigation :)


Now, I just have to figure out what continues to wrong with lightning_distance,
lightning_strike_count

On Wed, Oct 11, 2023 at 1:57 AM bell...@gmail.com 
wrote:

> Disclaimer, I don’t know anything about the Belchertown skin, but since
> your site is public, I thought I would poke around see if I could help.
>
> From, https://www.w3schools.com/jsref/jsref_tolocalestring_number.asp, it
> looks like valid values for minimumFractionDigits is 0 to 20.
> I guessed that the exception was in the onMessageArrived callback.
> If you trace the code from when a MQTT message arrive, at line 1675 is
> ‘html_output =
> parseFloat(parseFloat(data[mqttdata])).toLocaleString("en-US",
> {minimumFractionDigits: unit_rounding_array[thisElementClass],
> maximumFractionDigits: unit_rounding_array[thisElementClass], useGrouping:
> localeStringUseGrouping}) + unit_label_array[thisElementClass]'
>
> When the exception is raised, thisElementClass = lightning_strike_count
> and unit_rounding_array[‘lightning_strike_count’] = %d. Reading the code,
> unit_rounding_array is sourced from weewx_data.json.
>
> Any chance that you also started publishing_lightning_strike_count when
> you started publishing soilMoistN?
>
> Hopefully someone who uses/knows Belchertown can tell you how
> weewx_data.json is created. If not, I’d stop publishing
> lightning_strike_count (and any other observations with non-numeric values
> in weewx_data.json) and see if that helps.
> rich
>
> On Tuesday, 10 October 2023 at 09:12:49 UTC-4 Stefan Gliessmann wrote:
>
>> Thanks again, Greg, for you "moral" support ;)
>>
>> with the appropiate setting in weewx.conf for the MQTT extension, the
>> soil moisture values have no digits after the decimal point.
>>
>> By now, I believe it is a mqtt topic issue.
>> It is a bit odd as I use the same infrastructure for my other weewx
>> station (rv.stegli.de) and, there MQTT just Works fine with the topic RV.
>> For weather.stegli.de the topic is weather ... and that worked well
>> prior adding the WH51s ...
>>
>> Oh well - it keeps me busy 😅
>>
>> Thanks again!
>> Stefan
>>
>> On Tue, Oct 10, 2023 at 2:58 PM Greg Troxel  wrote:
>>
>>> Stefan Gliessmann  writes:
>>>
>>> > My soil moisture sensors are Ecowitt WH51.
>>> > Online I found their specs:
>>> > Moisture Range: 0 - 100 %
>>> > Resolution: 1 %
>>> > (so, it is % and not centibar?!)
>>>
>>> Yes, that is % moisture.  The WH51 is a very normal sensor.  I have one
>>> and read it via rtl_433.   See src/devices/fineoffset.c at
>>> https://github.com/merbanan/rtl_433/ for details.n
>>>
>>> It reads in integer %, but there is also an ADC raw value that one can
>>> use to calculate.
>>>
>>> > I do not understand how my moisture graph displays values after the
>>> decimal
>>> > point.
>>>
>>> I don't either, but to figure that out you will need to trace data flow
>>> through the entire system, examining each step.  That may require you to
>>> read docs on various other things and dig in enough to understand.
>>>
>>> > I use the https://github.com/matthewwall/weewx-mqtt weewx mqtt
>>> extension
>>> > version 0.24 for broadcasting the Ecowitt GW 1100 data thru a local
>>> > mosquitto server into Belchertown skin.
>>>
>>> I would recommend looking at what is in your weewx database, and also
>>> subscribe manually to the mqtt feed and look at that.   It is likely
>>> that somehwere, something is off, but I don't expect anyone here to
>>> guess.
>>>
>>> > Is there another weewx mqtt extension which is recommended to be used
>>> as a
>>> > publisher?
>>>
>>> That's the stan

Re: [weewx-user] Re: MQTT disconnect when MQTT publishes new data since adding soil moisture sensors

[Stefan Gliessmann]

Thanks again, Greg, for you "moral" support ;)

with the appropiate setting in weewx.conf for the MQTT extension, the soil
moisture values have no digits after the decimal point.

By now, I believe it is a mqtt topic issue.
It is a bit odd as I use the same infrastructure for my other weewx station
(rv.stegli.de) and, there MQTT just Works fine with the topic RV.
For weather.stegli.de the topic is weather ... and that worked well prior
adding the WH51s ...

Oh well - it keeps me busy 😅

Thanks again!
Stefan

On Tue, Oct 10, 2023 at 2:58 PM Greg Troxel  wrote:

> Stefan Gliessmann  writes:
>
> > My soil moisture sensors are Ecowitt WH51.
> > Online I found their specs:
> > Moisture Range: 0 - 100 %
> > Resolution: 1 %
> > (so, it is % and not centibar?!)
>
> Yes, that is % moisture.  The WH51 is a very normal sensor.  I have one
> and read it via rtl_433.   See src/devices/fineoffset.c at
> https://github.com/merbanan/rtl_433/ for details.n
>
> It reads in integer %, but there is also an ADC raw value that one can
> use to calculate.
>
> > I do not understand how my moisture graph displays values after the
> decimal
> > point.
>
> I don't either, but to figure that out you will need to trace data flow
> through the entire system, examining each step.  That may require you to
> read docs on various other things and dig in enough to understand.
>
> > I use the https://github.com/matthewwall/weewx-mqtt weewx mqtt extension
> > version 0.24 for broadcasting the Ecowitt GW 1100 data thru a local
> > mosquitto server into Belchertown skin.
>
> I would recommend looking at what is in your weewx database, and also
> subscribe manually to the mqtt feed and look at that.   It is likely
> that somehwere, something is off, but I don't expect anyone here to guess.
>
> > Is there another weewx mqtt extension which is recommended to be used as
> a
> > publisher?
>
> That's the standard approach.  I have been using it for years with no
> issues.
>

-- 
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/CACXWM9R-Fbu%2B_MJf-Yn6t5p_XsPAjCdcY_eGGMnbbukCgCPw%2Bg%40mail.gmail.com.

Re: [weewx-user] Re: MQTT disconnect when MQTT publishes new data since adding soil moisture sensors

[Stefan Gliessmann]

Hi Greg et al.,

My soil moisture sensors are Ecowitt WH51.
Online I found their specs:
Moisture Range: 0 - 100 %
Resolution: 1 %

(so, it is % and not centibar?!)

I do not understand how my moisture graph displays values after the decimal
point.

I use the https://github.com/matthewwall/weewx-mqtt weewx mqtt extension
version 0.24 for broadcasting the Ecowitt GW 1100 data thru a local
mosquitto server into Belchertown skin.

Is there another weewx mqtt extension which is recommended to be used as a
publisher?

TIA,
Stefan

On Mon, Oct 9, 2023 at 4:37 PM Greg Troxel  wrote:

> Stefan Gliessmann  writes:
>
> > Using the inspect function of google chrome, I see this error message:
> >
> > *MQTT: 2023-10-09T16:01:34+02:00: mqtt Connection Lost: AMQJS0005E
> Internal
> > error. Error Message: minimumFractionDigits value is out of range.,
> Stack
> > trace: No Error Stack Available*
> >
> > I can see that the GW1100 is broadcasting the soil moisture values as
> > integers in the EcoWitt app as well as the gw1000 weewx driver:
> >   *'soilmoist1': 12, 'soilmoist2': 20, 'soilmoist3': 17, 'soilmoist4':
> 26*
>
> mqtt is strings.   It is not integers or floats.
>
> It is  perfectly normal for a receiver to try to parse a number from
> that string, but I would say that "17" is a perfectly reasonable number
> and that objecting to it because it is not "17.0" is a bug.  If that's
> what is going on of course!
>
> > I can also see that user.mqtt sends the values as fractions adding ".0"
> to
> > the values from gw1000 driver:
> >   *'soilMoist1_centibar': '12.0'*, 'wh51_ch1_batt': '1.6',
> 'wh51_ch1_sig':
> > '4.0', *'soilMoist2_centibar': '20.0'*, 'wh51_ch2_batt': '1.6',
> > 'wh51_ch2_sig': '4.0', *'soilMoist3_centibar': '17.0'*, 'wh51_ch3_batt':
> > '1.6', 'wh51_ch3_sig': '4.0', *'soilMoist4_centibar': '26.0'*,
> > 'wh51_ch4_batt': '1.6', 'wh51_ch4_sig': '4.0'
> >
> > In my graph for soil moisture I can see "sometimes" fractions, too,
> which
> > are not ".0" (as it is archive data and not loop data?):
> > [image: Screenshot 2023-10-09 at 16.25.08.png]
> >
> > Any clue what I need to adjust?
>
> First you need to find out what the resolution of the sensor really is.
> (Very cool that is it moisture in pressure instead of the usual %.)
> Then  a publisher might need to adjust.  Separately the subscriber
> should probably be fixed too.
>

-- 
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/CACXWM9TZtZgyLjaMiECvfpj%2BSrb1ALf5JbRKzuDA79cvMQVXCw%40mail.gmail.com.

[weewx-user] Re: MQTT disconnect when MQTT publishes new data since adding soil moisture sensors

[Stefan Gliessmann]

Uncaught Error: AMQJS0011E Invalid state not connecting or connected.
at d.disconnect (paho-mqtt.min.js:35:305)
at Client.disconnect (paho-mqtt.min.js:74:193)
at inactive (belchertown.js?1696860019:1586:12)
d.disconnect @ paho-mqtt.min.js:35
Client.disconnect @ paho-mqtt.min.js:74
inactive @ belchertown.js?1696860019:1586

I just noticed this as well in the inspect frame of google chrome ...
On Monday, October 9, 2023 at 4:29:36 PM UTC+2 Stefan Gliessmann wrote:

> Since ever I have the soil moisture sensors installed, MQTT displays in 
> the Belchertown skin "Lost connection" whenever a new MQTT dataset is 
> broadcasted.
>
> Using the inspect function of google chrome, I see this error message:
>
> *MQTT: 2023-10-09T16:01:34+02:00: mqtt Connection Lost: AMQJS0005E 
> Internal error. Error Message: minimumFractionDigits value is out of 
> range., Stack trace: No Error Stack Available*
>
> I can see that the GW1100 is broadcasting the soil moisture values as 
> integers in the EcoWitt app as well as the gw1000 weewx driver: 
>   *'soilmoist1': 12, 'soilmoist2': 20, 'soilmoist3': 17, 'soilmoist4': 26*
>
> I can also see that user.mqtt sends the values as fractions adding ".0" to 
> the values from gw1000 driver: 
>   *'soilMoist1_centibar': '12.0'*, 'wh51_ch1_batt': '1.6', 
> 'wh51_ch1_sig': '4.0', *'soilMoist2_centibar': '20.0'*, 'wh51_ch2_batt': 
> '1.6', 'wh51_ch2_sig': '4.0', *'soilMoist3_centibar': '17.0'*, 
> 'wh51_ch3_batt': '1.6', 'wh51_ch3_sig': '4.0', *'soilMoist4_centibar': 
> '26.0'*, 'wh51_ch4_batt': '1.6', 'wh51_ch4_sig': '4.0'
>
> In my graph for soil moisture I can see "sometimes" fractions, too, which 
> are not ".0" (as it is archive data and not loop data?):
> [image: Screenshot 2023-10-09 at 16.25.08.png]
>
> Any clue what I need to adjust?
>
> TIA,
> Stefan
>
> On Thursday, October 5, 2023 at 2:17:29 PM UTC+2 Stefan Gliessmann wrote:
>
>> Hello group!
>>
>> Yesterday, I added soil moisture sensors to my EcoWitt GW1100.
>> I added also a graph in my Belchertown skin:
>>
>> [image: Screenshot 2023-10-05 at 14.04.21.png]
>>
>> However, since then I notice this:
>> [image: Screenshot 2023-10-05 at 13.56.38.png]
>>
>> The same MQTT server is used for another weewx instance and, hence, I 
>> knew it is not the MQTT server or broadcasting.
>>
>> Today, I used the inspection function of google chrome and I found this 
>> error message:
>> [image: Screenshot 2023-10-05 at 14.09.33.png]
>> I haven't seen this issue since I have added the soil moisture sensors. 
>> Hence, it should be correlated, shouldn't it?
>>
>> This is the Gateway Driver & MQTT data from the syslog:
>>
>> Oct  5 14:12:55 weewx weewx[140241] INFO weewx.restx: MQTT: Published 
>> record 2023-10-05 14:12:55 CEST (1696507975)
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Sending packet 'FF 
>> FF 27 03 2A' to 192.168.178.45:45000
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Received response 
>> 'FF FF 27 00 54 01 00 DD 06 32 08 27 9D 09 27 FB 02 00 A6 07 46 0A 00 C7 0B 
>> 00 04 0C 00 0A 15 00 02 3A F0 16 00 A5 17 01 2C 0E 2E 16 30 15 32 1E 62 00 
>> 00 00 00 61 65 1C 15 90 60 0A 19 00 3D 0E 00 00 10 00 00 11 00 51 12 00 00 
>> 00 51 13 00 00 08 61 0D 00 00 AF'
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Sending packet 'FF 
>> FF 57 03 5A' to 192.168.178.45:45000
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Received response 
>> 'FF FF 57 00 29 0E 00 00 10 00 00 00 00 11 00 00 00 51 12 00 00 00 51 13 00 
>> 00 08 61 0D 00 00 0F 00 64 88 00 01 00 7A 01 7B 00 DE'
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Unknown field 
>> address '7B' detected. Remaining data '00' ignored.
>>
>> Oct  5 14:13:00 weewx weewx[140241] DEBUG user.gw1000: Parsed data: 
>> {'intemp': 22.1, 'inhumid': 50, 'absbarometer': 1014.1, 'relbarometer': 
>> 1023.5, 'outtemp': 16.6, 'outhumid': 70, 'winddir': 199, 'windspeed': 0.4, 
>> 'gustspeed': 1.0, 'light': 14616.0, 'uv': 16.5, 'uvi': 1, 'soilmoist1': 14, 
>> 'soilmoist2': 22, 'soilmoist3': 21, 'so

[weewx-user] Re: Introducing weewx-svg2png generator for creating thumbnail images and mini-pics in WeeWX

[Stefan Gliessmann]

Awesome!

I will give it a shoot later and let you know :)

Thanks in advance for your contributions

On Tuesday, October 3, 2023 at 4:15:11 PM UTC+2 Karen K wrote:

> If there is a link in a social media post, sites like Twitter (X), 
> Mastodon and others show a preview image or thumbnail of the linked page. 
> For a long time I wondered how to define that image. Then I found out they 
> look for special "meta" statements within the page header. I included such 
> statements in my weather website, and indeed, the respective images were 
> displayed.
>
> I used a screenshot for that purpose. But the screenshot said 3,8°C, and 
> it's summer time and temperatures are much higher. And I wondered how to 
> get actual data into that screenshot. So I thought I could create an SVG 
> file using the CheetahGenerator functionality of WeeWX, and convert it to 
> PNG afterwards. I found the CairoSVG package to do the converting job. 
>
> But how to do the conversion after WeeWX created the SVG file, but before 
> WeeWX sends the data to the web server?
>
> The answer is to write a generator for use in skins. And that's it: 
> weewx-svg2png 
>
> Now I look what is happening, and meanwhile I publish the generator here.
>

-- 
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/d633b50a-4acc-40cf-9483-462471b05e02n%40googlegroups.com.

Re: [weewx-user] mosquitto & SSL

[Stefan Gliessmann]

good catch - I had them actually *copied* ... but nevertheless, I shall
probably *link* them as I copied cert1.pem, etc ... otherwise, in three
months I will wonder why MQTT stopped working suddenly ;)


On Fri, Sep 29, 2023 at 4:35 PM Graham Eddy  wrote:

> i was expecting log file to show either file not found (misnamed) or
> permission denied (user ‘mosquitto’ not able to read). maybe need to add 
> log_type
> debug to config file to get that message. anyway, looks like you fixed
> perms problem
>
> note: if you *moved* (not copied) them from letsencrypt, better put them
> back then copy them, or the cert refresh will get confused
> *⊣GE⊢*
>
> On 30 Sep 2023, at 12:25 am, Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wrote:
>
> Well - I just moved my certs from the lets encrypt dir to the
> mosquitto/cert dir and now mosquitto restarted without problems ... :)
>
>
> On Fri, Sep 29, 2023 at 3:41 PM Graham Eddy  wrote:
>
>> try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo
>> tail -50 /var/log/mosquitto/* if it puts them there instead)
>> *⊣GE⊢*
>>
>> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann <
>> stefan.gliessm...@gmail.com> wrote:
>>
>> I am trying to get my weather station web presence secure with https://
>> Therefore, I also need my MQTT server be secure via SSL.
>>
>> I followed the setup by
>> https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/
>>
>> I received my certificates from Let's encrypt and edited my mosquitto
>> config file accordingly:
>>
>>   GNU nano 6.2 /etc/mosquitto/conf.d/myconfig.conf
>>
>> persistence false
>> allow_anonymous true
>> #allow_zero_length_clientid true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>> # mqtt
>> #listener 1883 localhost
>> listener 8883
>> certfile /etc/letsencrypt/live/
>> weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
>> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
>> keyfile /etc/letsencrypt/live/
>> weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
>> tls_version tlsv1.2
>> protocol mqtt
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/
>> weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
>> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
>> keyfile /etc/letsencrypt/live/
>> weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
>> protocol websockets
>>
>> every time I reboot now mosquitto, I get an error by mosquitto:
>>
>> root@weewx:/# sudo systemctl restart mosquitto.service
>> Job for mosquitto.service failed because the control process exited with
>> error code.
>> See "systemctl status mosquitto.service" and "journalctl -xeu
>> mosquitto.service" for details.
>> root@weewx:/# sudo systemctl status mosquitto.service
>> *×* mosquitto.service - Mosquitto MQTT Broker
>>  Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled;
>> vendor preset: enabled)
>>  Active: *failed* (Result: exit-code) since Fri 2023-09-29 15:32:19
>> CEST; 1s ago
>>Docs: man:mosquitto.conf(5)
>>  man:mosquitto(8)
>> Process: 542132 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto
>> (code=exited, status=0/SUCCESS)
>> Process: 542133 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto
>> (code=exited, status=0/SUCCESS)
>> Process: 542134 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto
>> (code=exited, status=0/SUCCESS)
>> Process: 542135 ExecStartPre=/bin/chown mosquitto /run/mosquitto
>> (code=exited, status=0/SUCCESS)
>> Process: 542136 ExecStart=/usr/sbin/mosquitto -c
>> /etc/mosquitto/mosquitto.conf *(code=exited, status=1/FAILURE)*
>>Main PID: 542136 (code=exited, status=1/FAILURE)
>> CPU: 22ms
>>
>> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart
>> job, restart counter is at 5.
>> Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.
>> Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Start request
>> repeated too quickly.*
>> Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Failed with result
>> 'exit-code'.*
>> Sep 29 15:32:19 weewx systemd[1]: *Failed to start Mosquitto MQTT
>> Broker.*
>> root@weewx:/#
>>
>> Once I command the certificates out, mosquitto starts up fine.
>>
>> I double checked that the certificates can be read by everybody.
>>
>> Any clue what else I check for?
>>
>> TIA,
>

Re: [weewx-user] mosquitto & SSL

[Stefan Gliessmann]

Well - I just moved my certs from the lets encrypt dir to the
mosquitto/cert dir and now mosquitto restarted without problems ... :)


On Fri, Sep 29, 2023 at 3:41 PM Graham Eddy  wrote:

> try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo
> tail -50 /var/log/mosquitto/* if it puts them there instead)
> *⊣GE⊢*
>
> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wrote:
>
> I am trying to get my weather station web presence secure with https://
> Therefore, I also need my MQTT server be secure via SSL.
>
> I followed the setup by
> https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/
>
> I received my certificates from Let's encrypt and edited my mosquitto
> config file accordingly:
>
>   GNU nano 6.2 /etc/mosquitto/conf.d/myconfig.conf
>
> persistence false
> allow_anonymous true
> #allow_zero_length_clientid true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
> # mqtt
> #listener 1883 localhost
> listener 8883
> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
> keyfile /etc/letsencrypt/live/
> weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
> tls_version tlsv1.2
> protocol mqtt
> # websockets
> listener 9001
> certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem
> cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem
> keyfile /etc/letsencrypt/live/
> weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem
> protocol websockets
>
> every time I reboot now mosquitto, I get an error by mosquitto:
>
> root@weewx:/# sudo systemctl restart mosquitto.service
> Job for mosquitto.service failed because the control process exited with
> error code.
> See "systemctl status mosquitto.service" and "journalctl -xeu
> mosquitto.service" for details.
> root@weewx:/# sudo systemctl status mosquitto.service
> *×* mosquitto.service - Mosquitto MQTT Broker
>  Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled;
> vendor preset: enabled)
>  Active: *failed* (Result: exit-code) since Fri 2023-09-29 15:32:19
> CEST; 1s ago
>Docs: man:mosquitto.conf(5)
>  man:mosquitto(8)
> Process: 542132 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto
> (code=exited, status=0/SUCCESS)
> Process: 542133 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto
> (code=exited, status=0/SUCCESS)
> Process: 542134 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto
> (code=exited, status=0/SUCCESS)
> Process: 542135 ExecStartPre=/bin/chown mosquitto /run/mosquitto
> (code=exited, status=0/SUCCESS)
> Process: 542136 ExecStart=/usr/sbin/mosquitto -c
> /etc/mosquitto/mosquitto.conf *(code=exited, status=1/FAILURE)*
>Main PID: 542136 (code=exited, status=1/FAILURE)
> CPU: 22ms
>
> Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart
> job, restart counter is at 5.
> Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.
> Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Start request
> repeated too quickly.*
> Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Failed with result
> 'exit-code'.*
> Sep 29 15:32:19 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*
> root@weewx:/#
>
> Once I command the certificates out, mosquitto starts up fine.
>
> I double checked that the certificates can be read by everybody.
>
> Any clue what else I check for?
>
> TIA,
> Stefan
>
>
> --
> 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/0fb5acdb-156e-489c-a3bb-06acfe4381a8n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/0fb5acdb-156e-489c-a3bb-06acfe4381a8n%40googlegroups.com?utm_medium=email&utm_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/wP9f-eDW6tk/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/049C6B06-B1C3-4335-A1A3-B690452E44B1%40geddy.au
> <https://groups.google.com/d/msgid/weewx-user/049C6B06-B1C3-4335-A1A3-B

Re: [weewx-user] mosquitto & SSL

[Stefan Gliessmann]

root@weewx:/# sudo journalctl -u mosquitto -n 50

Sep 29 15:31:52 weewx mosquitto[542060]: 1695994312: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:31:52 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:31:52 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:31:52 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:31:52 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 5.

Sep 29 15:31:52 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:31:52 weewx systemd[1]: *mosquitto.service: Start request
repeated too quickly.*

Sep 29 15:31:52 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:31:52 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:18 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:32:18 weewx mosquitto[542113]: 1695994338: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:18 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:18 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 1.

Sep 29 15:32:18 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:18 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:32:18 weewx mosquitto[542119]: 1695994338: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:18 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:18 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 2.

Sep 29 15:32:18 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:18 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:32:18 weewx mosquitto[542125]: 1695994338: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:18 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:18 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 3.

Sep 29 15:32:18 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:18 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:32:18 weewx mosquitto[542130]: 1695994338: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:32:18 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:18 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 4.

Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:19 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:32:19 weewx mosquitto[542136]: 1695994339: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Main process exited,
code=exited, status=1/FAILURE*

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:19 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart job,
restart counter is at 5.

Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Start request
repeated too quickly.*

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Failed with result
'exit-code'.*

Sep 29 15:32:19 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

Sep 29 15:36:37 weewx systemd[1]: Starting Mosquitto MQTT Broker...

Sep 29 15:36:37 weewx mosquitto[542525]: 1695994597: Loading config file
/etc/mosquitto/conf.d/myconfig.conf

Sep 29 15:36:37 weewx systemd[1]: Started Mosquitto MQTT Broker.


Mosquitto has issues with reading my mosquitto/conf.d/myconfig.conf when
the certificates are active.

It works fine when certificates are commanded out ...




On Fri, Sep 29, 2023 at 3:41 PM Graham Eddy  wrote:

> try sudo journalctl -u mosquitto -n 50 to see the log messages (or sudo
> tail -50 /var/log/mosquitto/* if it puts them there instead)
> *⊣GE⊢*
>
> On 29 Sep 2023, at 11:35 pm, Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wro

[weewx-user] mosquitto & SSL

[Stefan Gliessmann]

I am trying to get my weather station web presence secure with https://
Therefore, I also need my MQTT server be secure via SSL.

I followed the setup 
by https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/

I received my certificates from Let's encrypt and edited my mosquitto 
config file accordingly:

  GNU nano 6.2 /etc/mosquitto/conf.d/myconfig.conf 
 

persistence false

allow_anonymous true

#allow_zero_length_clientid true

password_file /etc/mosquitto/passwd

acl_file /etc/mosquitto/acl

# mqtt

#listener 1883 localhost

listener 8883

certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem

cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem

keyfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem

tls_version tlsv1.2

protocol mqtt

# websockets

listener 9001

certfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/cert.pem

cafile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/chain.pem

keyfile /etc/letsencrypt/live/weewx.bz3gfkrlqtrsc3sv.myfritz.net/privkey.pem

protocol websockets


every time I reboot now mosquitto, I get an error by mosquitto:


root@weewx:/# sudo systemctl restart mosquitto.service 

Job for mosquitto.service failed because the control process exited with 
error code.

See "systemctl status mosquitto.service" and "journalctl -xeu 
mosquitto.service" for details.

root@weewx:/# sudo systemctl status mosquitto.service 

*×* mosquitto.service - Mosquitto MQTT Broker

 Loaded: loaded (/lib/systemd/system/mosquitto.service; enabled; vendor 
preset: enabled)

 Active: *failed* (Result: exit-code) since Fri 2023-09-29 15:32:19 
CEST; 1s ago

   Docs: man:mosquitto.conf(5)

 man:mosquitto(8)

Process: 542132 ExecStartPre=/bin/mkdir -m 740 -p /var/log/mosquitto 
(code=exited, status=0/SUCCESS)

Process: 542133 ExecStartPre=/bin/chown mosquitto /var/log/mosquitto 
(code=exited, status=0/SUCCESS)

Process: 542134 ExecStartPre=/bin/mkdir -m 740 -p /run/mosquitto 
(code=exited, status=0/SUCCESS)

Process: 542135 ExecStartPre=/bin/chown mosquitto /run/mosquitto 
(code=exited, status=0/SUCCESS)

Process: 542136 ExecStart=/usr/sbin/mosquitto -c 
/etc/mosquitto/mosquitto.conf *(code=exited, status=1/FAILURE)*

   Main PID: 542136 (code=exited, status=1/FAILURE)

CPU: 22ms


Sep 29 15:32:19 weewx systemd[1]: mosquitto.service: Scheduled restart job, 
restart counter is at 5.

Sep 29 15:32:19 weewx systemd[1]: Stopped Mosquitto MQTT Broker.

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Start request 
repeated too quickly.*

Sep 29 15:32:19 weewx systemd[1]: *mosquitto.service: Failed with result 
'exit-code'.*

Sep 29 15:32:19 weewx systemd[1]: *Failed to start Mosquitto MQTT Broker.*

root@weewx:/# 


Once I command the certificates out, mosquitto starts up fine.


I double checked that the certificates can be read by everybody.


Any clue what else I check for?


TIA,

Stefan


-- 
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/0fb5acdb-156e-489c-a3bb-06acfe4381a8n%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Thx!
I added it in skin.conf, but I still see "undefined" ...

On Friday, September 15, 2023 at 8:35:57 AM UTC+2 Karen K wrote:

> You could set
> degree_compass = " °"
> in section "Labels" of section "Units" in lang/en.conf, skin.conf or 
> weewx.conf
>
> Sheldon Herold schrieb am Donnerstag, 14. September 2023 um 12:20:55 UTC+2:
>
>> Bin bald zuhause.
>> -Von meinem Garmin-Gerät gesen 
>>
>> Stefan Gliessmann  schrieb am Do., 14. Sept. 
>> 2023, 12:17:
>>
>>> Thank you for reminding me of Karen's input ...
>>>
>>> Nevertheless, I am unable to have units for the coordinates displayed in 
>>> Belchertown skin.
>>> Furthermore, longitude and latitude are first invalid observation
>>> [image: Screenshot 2023-09-14 at 11.40.15.png]
>>> until a MQTT GPS packet is delivered. Then in turns into
>>> [image: Screenshot 2023-09-14 at 11.40.08.png]
>>>
>>> Any ideas why?
>>>
>>> P.S.: I changed from gpsLat to latitude and gpsLong to longitude ...
>>>
>>> On Saturday, September 9, 2023 at 7:39:50 PM UTC+2 vince wrote:
>>>
>>>> Karen answered your question previously - 
>>>> https://groups.google.com/g/weewx-user/c/Fwd1BvCfCoM/m/NAuZqAfTAAAJ
>>>>
>>>> On Saturday, September 9, 2023 at 10:07:50 AM UTC-7 Stefan Gliessmann 
>>>> wrote:
>>>>
>>>> What is the right unit for longitude and latitude?
>>>> They should be degrees, but other then for temperature or compass I 
>>>> couldn't find any other ...
>>>>
>>>> [image: Screenshot 2023-09-09 at 19.05.18.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+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/75fe0f45-0523-452c-b5cc-325007ca5929n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/weewx-user/75fe0f45-0523-452c-b5cc-325007ca5929n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/209d7898-fdd5-4cb2-84f8-86b30f04d1fdn%40googlegroups.com.

[weewx-user] Cookie consent with Belchertown skin

[Stefan Gliessmann]

Hello weewx-users,

for all the weewx users in Europe, you are probably already aware of GDPR.
In trying to beaf up compliance for my web site http://weather.stegli.de, I 
am using cookiebot (https://www.cookiebot.com). I integrated their scripts 
in the hooks Option of the Belchertown skin.

And it seems to work ok.
After the first cookie selection, it seems, that one has to reload the page 
again for full functionality.

Are there other Solutions for GDPR out there which one uses in Kombination 
with Belchertown?

Cheers,
Stefan

-- 
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/d2440a7e-cc33-4af4-b952-8b9ec1a84a7cn%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

What is the right unit for longitude and latitude?
They should be degrees, but other then for temperature or compass I 
couldn't find any other ...

[image: Screenshot 2023-09-09 at 19.05.18.png]

On Friday, September 8, 2023 at 6:42:24 PM UTC+2 Stefan Gliessmann wrote:

> This is an awesome group!
> Without your help of so many folks, I would not have achieved what I have 
> so far ...
> Still need to do more to pass the coordinates to Belchertown skin 
> forecasts and weather warnings ...
> But I am getting there now (I hope) ...
>
> Thank you all again for your help!
>
> On Friday, September 8, 2023 at 6:40:13 PM UTC+2 Stefan Gliessmann wrote:
>
>> The clock in my about page is actually from 
>> https://github.com/roe-dl/websocket-clock-js/commits?author=roe-dl aka 
>> Karen K in this group!
>> She did a lot of work to use German weather data (DWD) with the 
>> Belchertown skin.
>> Check out her work on her PWS page https://www.woellsdorf-wetter.de/
>>
>>
>> On Friday, September 8, 2023 at 6:35:37 PM UTC+2 Stefan Gliessmann wrote:
>>
>>> Vince, thank you again for the scripts ... once I figured out that my 
>>> MQTT requires  user & password, it works now ...
>>> seems that I still have to do something with the units for the GPS 
>>> coordinates ...
>>>
>>> [image: Screenshot 2023-09-08 at 18.32.17.png]
>>>
>>> On Sunday, September 3, 2023 at 2:24:04 AM UTC+2 vince wrote:
>>>
>>>> Yes.  ipv6 is an adventure.  I tried to turn it on for my home LAN and 
>>>> DNS was a big problem until I figured out that I just needed to always use 
>>>> "hostname.local" for the LAN DNS and it would work.  Unfortunately it also 
>>>> seemed to break my pihole ad-blocking so I turned ipv6 back off here after 
>>>> a few day test.
>>>>
>>>> I like the clock on your About page too!
>>>> On Saturday, September 2, 2023 at 1:02:04 PM UTC-7 Stefan Gliessmann 
>>>> wrote:
>>>>
>>>>> Dear Vince,
>>>>>
>>>>> thank you very much for providing the scripts! I really do appreciate!
>>>>> However, last Tuesday I changed my ISP. Good think - it is 1 Gbps! And 
>>>>> my challenge was that it is IPv6 and I had to learn very quickly that 
>>>>> port 
>>>>> forwarding with IPv6 is completely different to IPv4, and even more 
>>>>> particular DDNS with IPv6.
>>>>> But I am happy to report that my server is back online rv.sgplex.de :)
>>>>> As I will be on vacation in Spain the next few weeks, I will place 
>>>>> your scripts in action!
>>>>>
>>>>> Thanks again for providing them!
>>>>>
>>>>> Cheers
>>>>>
>>>>> On Monday, August 28, 2023 at 10:17:58 PM UTC+2 vince wrote:
>>>>>
>>>>>> (sorry - ignore the earlier truncated post)
>>>>>>
>>>>>> I cooked up a bash script that subscribes, calls a python script to 
>>>>>> reformat, then publishes.   The bash script sleeps a second between 
>>>>>> loops 
>>>>>> to not eat up your cpu.   You 'should' be able to change the variables 
>>>>>> in 
>>>>>> the bash script to match your configuration pretty easily...
>>>>>>
>>>>>> This subscribes to ORIGINAL_TOPIC and publishes to FINAL_TOPIC in the 
>>>>>> bash script.
>>>>>> To test:
>>>>>>
>>>>>>- open a bash window and subscribe to the FINAL_TOPIC
>>>>>>- open a second window and run the bash script which will 
>>>>>>listen/reformat/publish
>>>>>>- if you're not querying your gps currently, open a third window 
>>>>>>and publish to the ORIGINAL_TOPIC ala
>>>>>>
>>>>>> mosquitto_pub -h 192.168.1.171 -t RV/original -m 
>>>>>> '[{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]'
>>>>>>
>>>>>> What you should see in window1 that is subscribing is output ala:
>>>>>> {"dateTime": "1693128700.0", "gpsLat": "52.152435", "gpsLong": 
>>>>>> "9.929356"}
>>>>>>
>>>&

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

This is an awesome group!
Without your help of so many folks, I would not have achieved what I have 
so far ...
Still need to do more to pass the coordinates to Belchertown skin forecasts 
and weather warnings ...
But I am getting there now (I hope) ...

Thank you all again for your help!

On Friday, September 8, 2023 at 6:40:13 PM UTC+2 Stefan Gliessmann wrote:

> The clock in my about page is actually from 
> https://github.com/roe-dl/websocket-clock-js/commits?author=roe-dl aka 
> Karen K in this group!
> She did a lot of work to use German weather data (DWD) with the 
> Belchertown skin.
> Check out her work on her PWS page https://www.woellsdorf-wetter.de/
>
>
> On Friday, September 8, 2023 at 6:35:37 PM UTC+2 Stefan Gliessmann wrote:
>
>> Vince, thank you again for the scripts ... once I figured out that my 
>> MQTT requires  user & password, it works now ...
>> seems that I still have to do something with the units for the GPS 
>> coordinates ...
>>
>> [image: Screenshot 2023-09-08 at 18.32.17.png]
>>
>> On Sunday, September 3, 2023 at 2:24:04 AM UTC+2 vince wrote:
>>
>>> Yes.  ipv6 is an adventure.  I tried to turn it on for my home LAN and 
>>> DNS was a big problem until I figured out that I just needed to always use 
>>> "hostname.local" for the LAN DNS and it would work.  Unfortunately it also 
>>> seemed to break my pihole ad-blocking so I turned ipv6 back off here after 
>>> a few day test.
>>>
>>> I like the clock on your About page too!
>>> On Saturday, September 2, 2023 at 1:02:04 PM UTC-7 Stefan Gliessmann 
>>> wrote:
>>>
>>>> Dear Vince,
>>>>
>>>> thank you very much for providing the scripts! I really do appreciate!
>>>> However, last Tuesday I changed my ISP. Good think - it is 1 Gbps! And 
>>>> my challenge was that it is IPv6 and I had to learn very quickly that port 
>>>> forwarding with IPv6 is completely different to IPv4, and even more 
>>>> particular DDNS with IPv6.
>>>> But I am happy to report that my server is back online rv.sgplex.de :)
>>>> As I will be on vacation in Spain the next few weeks, I will place your 
>>>> scripts in action!
>>>>
>>>> Thanks again for providing them!
>>>>
>>>> Cheers
>>>>
>>>> On Monday, August 28, 2023 at 10:17:58 PM UTC+2 vince wrote:
>>>>
>>>>> (sorry - ignore the earlier truncated post)
>>>>>
>>>>> I cooked up a bash script that subscribes, calls a python script to 
>>>>> reformat, then publishes.   The bash script sleeps a second between loops 
>>>>> to not eat up your cpu.   You 'should' be able to change the variables in 
>>>>> the bash script to match your configuration pretty easily...
>>>>>
>>>>> This subscribes to ORIGINAL_TOPIC and publishes to FINAL_TOPIC in the 
>>>>> bash script.
>>>>> To test:
>>>>>
>>>>>- open a bash window and subscribe to the FINAL_TOPIC
>>>>>- open a second window and run the bash script which will 
>>>>>listen/reformat/publish
>>>>>- if you're not querying your gps currently, open a third window 
>>>>>and publish to the ORIGINAL_TOPIC ala
>>>>>
>>>>> mosquitto_pub -h 192.168.1.171 -t RV/original -m 
>>>>> '[{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]'
>>>>>
>>>>> What you should see in window1 that is subscribing is output ala:
>>>>> {"dateTime": "1693128700.0", "gpsLat": "52.152435", "gpsLong": 
>>>>> "9.929356"}
>>>>>
>>>>> That kind of data should be ok to subscribe to in weewx for your 
>>>>> lat/lon data
>>>>>
>>>>> # reformat_mqtt.bash 
>>>>>
>>>>> #!/bin/bash
>>>>> #
>>>>> # ip address of MQTT broker
>>>>> BROKER="192.168.1.171"
>>>>>
>>>>> ORIGINAL_TOPIC="RV/original"
>>>>> FINAL_TOPIC="RV/final"
>>>>>
>>>>> while true; do
>>>>>
>>>>>   # subscribe to a topic
>>>>>   # run the python script to reformat to stdout
>>

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

The clock in my about page is actually 
from https://github.com/roe-dl/websocket-clock-js/commits?author=roe-dl aka 
Karen K in this group!
She did a lot of work to use German weather data (DWD) with the Belchertown 
skin.
Check out her work on her PWS page https://www.woellsdorf-wetter.de/


On Friday, September 8, 2023 at 6:35:37 PM UTC+2 Stefan Gliessmann wrote:

> Vince, thank you again for the scripts ... once I figured out that my MQTT 
> requires  user & password, it works now ...
> seems that I still have to do something with the units for the GPS 
> coordinates ...
>
> [image: Screenshot 2023-09-08 at 18.32.17.png]
>
> On Sunday, September 3, 2023 at 2:24:04 AM UTC+2 vince wrote:
>
>> Yes.  ipv6 is an adventure.  I tried to turn it on for my home LAN and 
>> DNS was a big problem until I figured out that I just needed to always use 
>> "hostname.local" for the LAN DNS and it would work.  Unfortunately it also 
>> seemed to break my pihole ad-blocking so I turned ipv6 back off here after 
>> a few day test.
>>
>> I like the clock on your About page too!
>> On Saturday, September 2, 2023 at 1:02:04 PM UTC-7 Stefan Gliessmann 
>> wrote:
>>
>>> Dear Vince,
>>>
>>> thank you very much for providing the scripts! I really do appreciate!
>>> However, last Tuesday I changed my ISP. Good think - it is 1 Gbps! And 
>>> my challenge was that it is IPv6 and I had to learn very quickly that port 
>>> forwarding with IPv6 is completely different to IPv4, and even more 
>>> particular DDNS with IPv6.
>>> But I am happy to report that my server is back online rv.sgplex.de :)
>>> As I will be on vacation in Spain the next few weeks, I will place your 
>>> scripts in action!
>>>
>>> Thanks again for providing them!
>>>
>>> Cheers
>>>
>>> On Monday, August 28, 2023 at 10:17:58 PM UTC+2 vince wrote:
>>>
>>>> (sorry - ignore the earlier truncated post)
>>>>
>>>> I cooked up a bash script that subscribes, calls a python script to 
>>>> reformat, then publishes.   The bash script sleeps a second between loops 
>>>> to not eat up your cpu.   You 'should' be able to change the variables in 
>>>> the bash script to match your configuration pretty easily...
>>>>
>>>> This subscribes to ORIGINAL_TOPIC and publishes to FINAL_TOPIC in the 
>>>> bash script.
>>>> To test:
>>>>
>>>>- open a bash window and subscribe to the FINAL_TOPIC
>>>>- open a second window and run the bash script which will 
>>>>listen/reformat/publish
>>>>- if you're not querying your gps currently, open a third window 
>>>>and publish to the ORIGINAL_TOPIC ala
>>>>
>>>> mosquitto_pub -h 192.168.1.171 -t RV/original -m 
>>>> '[{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]'
>>>>
>>>> What you should see in window1 that is subscribing is output ala:
>>>> {"dateTime": "1693128700.0", "gpsLat": "52.152435", "gpsLong": 
>>>> "9.929356"}
>>>>
>>>> That kind of data should be ok to subscribe to in weewx for your 
>>>> lat/lon data
>>>>
>>>> # reformat_mqtt.bash 
>>>>
>>>> #!/bin/bash
>>>> #
>>>> # ip address of MQTT broker
>>>> BROKER="192.168.1.171"
>>>>
>>>> ORIGINAL_TOPIC="RV/original"
>>>> FINAL_TOPIC="RV/final"
>>>>
>>>> while true; do
>>>>
>>>>   # subscribe to a topic
>>>>   # run the python script to reformat to stdout
>>>>   # publish to a final topic
>>>>
>>>>   mosquitto_sub -C 1 -h ${BROKER} -t ${ORIGINAL_TOPIC} \
>>>> | python3 reformat_mqtt.py \
>>>> | mosquitto_pub --stdin-line -h ${BROKER} -t ${FINAL_TOPIC}
>>>>
>>>>   # sleep a bit to not eat up your cpu
>>>>   sleep 1
>>>>
>>>> done
>>>>
>>>>
>>>> # reformat_mqtt.py -
>>>> #
>>>> # this reformats the GPS information
>>>> # to a more normal looking output
>>>> #
>>>>
>>>> # it assumes your input data is always in the same order and alway

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Dear Vince,

thank you very much for providing the scripts! I really do appreciate!
However, last Tuesday I changed my ISP. Good think - it is 1 Gbps! And my 
challenge was that it is IPv6 and I had to learn very quickly that port 
forwarding with IPv6 is completely different to IPv4, and even more 
particular DDNS with IPv6.
But I am happy to report that my server is back online rv.sgplex.de :)
As I will be on vacation in Spain the next few weeks, I will place your 
scripts in action!

Thanks again for providing them!

Cheers

On Monday, August 28, 2023 at 10:17:58 PM UTC+2 vince wrote:

> (sorry - ignore the earlier truncated post)
>
> I cooked up a bash script that subscribes, calls a python script to 
> reformat, then publishes.   The bash script sleeps a second between loops 
> to not eat up your cpu.   You 'should' be able to change the variables in 
> the bash script to match your configuration pretty easily...
>
> This subscribes to ORIGINAL_TOPIC and publishes to FINAL_TOPIC in the bash 
> script.
> To test:
>
>- open a bash window and subscribe to the FINAL_TOPIC
>- open a second window and run the bash script which will 
>listen/reformat/publish
>- if you're not querying your gps currently, open a third window and 
>publish to the ORIGINAL_TOPIC ala
>
> mosquitto_pub -h 192.168.1.171 -t RV/original -m 
> '[{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]'
>
> What you should see in window1 that is subscribing is output ala:
> {"dateTime": "1693128700.0", "gpsLat": "52.152435", "gpsLong": "9.929356"}
>
> That kind of data should be ok to subscribe to in weewx for your lat/lon 
> data
>
> # reformat_mqtt.bash 
>
> #!/bin/bash
> #
> # ip address of MQTT broker
> BROKER="192.168.1.171"
>
> ORIGINAL_TOPIC="RV/original"
> FINAL_TOPIC="RV/final"
>
> while true; do
>
>   # subscribe to a topic
>   # run the python script to reformat to stdout
>   # publish to a final topic
>
>   mosquitto_sub -C 1 -h ${BROKER} -t ${ORIGINAL_TOPIC} \
> | python3 reformat_mqtt.py \
> | mosquitto_pub --stdin-line -h ${BROKER} -t ${FINAL_TOPIC}
>
>   # sleep a bit to not eat up your cpu
>   sleep 1
>
> done
>
>
> # reformat_mqtt.py -
> #
> # this reformats the GPS information
> # to a more normal looking output
> #
>
> # it assumes your input data is always in the same order and always 
> complete
> # ala: 
> [{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]
>
> import json
> import sys
> for line in sys.stdin:
> jsondata = json.loads(line)
> reorganized_data = {}
> reorganized_data['dateTime'] = jsondata[0]['dateTime']
> reorganized_data['gpsLat']   = jsondata[0]['gpsLat']
> reorganized_data['gpsLong']  = jsondata[1]['gpsLong']
> print(json.dumps(reorganized_data))
>
>
> On Monday, August 28, 2023 at 5:19:15 AM UTC-7 Stefan Gliessmann wrote:
>
>> I asked in the community forum for my router and I was told that this is 
>> the only way they can currently forward data via MQTT.
>> A future firmware release shall allow more formatting.
>>
>> I might now play around with this 
>> https://github.com/mrtncls/mqtt-translator to get the MQTT payload from 
>> an array in one single statement ...
>> Anybody used the MQTT Translator for this purpose?
>>
>> On Monday, August 28, 2023 at 11:01:41 AM UTC+2 Stefan Gliessmann wrote:
>>
>>> Which code do you refer to?
>>> [image: Screenshot 2023-08-28 at 11.00.03.png]
>>> This is what I specified in the GPS/Router to push via MQTT to my broker 
>>> ...
>>> On Sunday, August 27, 2023 at 8:39:40 PM UTC+2 vince wrote:
>>>
>>>> We'd have to see your code to see what you are publishing.
>>>>
>>>> Your MQTT log looks very odd and likely needs some tweaking
>>>>
>>>> MQTT: 
>>>> [{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]
>>>>  
>>>>  
>>>>
>>>> I'd expect something like {"dateTime":"1233456", "gpsLat":"52.1234", 
>>>> "gpsLong": "9.987"} for a more typical set of JSON to publish.   You want 
>>>> one element (not in an array) with three items therein - dateTime/lat/lon.
>>>>
>>>>

-- 
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/066c03f8-5bb8-42ff-adbb-3c258676ab91n%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

I asked in the community forum for my router and I was told that this is 
the only way they can currently forward data via MQTT.
A future firmware release shall allow more formatting.

I might now play around with 
this https://github.com/mrtncls/mqtt-translator to get the MQTT payload 
from an array in one single statement ...
Anybody used the MQTT Translator for this purpose?

On Monday, August 28, 2023 at 11:01:41 AM UTC+2 Stefan Gliessmann wrote:

> Which code do you refer to?
> [image: Screenshot 2023-08-28 at 11.00.03.png]
> This is what I specified in the GPS/Router to push via MQTT to my broker 
> ...
> On Sunday, August 27, 2023 at 8:39:40 PM UTC+2 vince wrote:
>
>> We'd have to see your code to see what you are publishing.
>>
>> Your MQTT log looks very odd and likely needs some tweaking
>>
>> MQTT: 
>> [{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]
>>  
>>  
>>
>> I'd expect something like {"dateTime":"1233456", "gpsLat":"52.1234", 
>> "gpsLong": "9.987"} for a more typical set of JSON to publish.   You want 
>> one element (not in an array) with three items therein - dateTime/lat/lon.
>>
>>

-- 
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/245ee62b-70f4-495f-8b43-f9dbf8adc180n%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Which code do you refer to?
[image: Screenshot 2023-08-28 at 11.00.03.png]
This is what I specified in the GPS/Router to push via MQTT to my broker ...
On Sunday, August 27, 2023 at 8:39:40 PM UTC+2 vince wrote:

> We'd have to see your code to see what you are publishing.
>
> Your MQTT log looks very odd and likely needs some tweaking
>
> MQTT: 
> [{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]
>  
>  
>
> I'd expect something like {"dateTime":"1233456", "gpsLat":"52.1234", 
> "gpsLong": "9.987"} for a more typical set of JSON to publish.   You want 
> one element (not in an array) with three items therein - dateTime/lat/lon.
>
>

-- 
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/3128c8e4-fe9e-4b0a-a43e-e40c59c2f0e5n%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Thank you for providing the extensions.py code, Karen K!
You really rock!!!

I placed it @ /usr/share/weewx/
with this I added new observations. 
(Check)

I also added the database columns with 
sudo wee_database --add-column=gpsLat
sudo wee_database --add-column=gpsLong
(Check)

However, they are empty with NULL

and in weewx.conf I added:
[[MQTT]]
 server_url = mqtt://xyz:xyz...@teffi71.spdns.de:1883/
 topic = RV
 unit_system = METRIC
 binding = loop, archive
 log_success = true
  [[[inputs]]]
   gpsLat
 name = gpsLat
#units = mm_per_hour
   gpsLong
 name = gpsLong

(Is adding this to weewx.conf needed?)

Whenever the gps coordinates are sent, the Belchertown MQTT status line 
says:
Connected to weather station live. Data received *Invalid date*

Looking in the Chrome Inspect console I can see:

MQTT: 
[{"dateTime":"1693128694.0","gpsLat":"52.152435"},{"dateTime":"1693128694.0","gpsLong":"9.929356"}]
 
MQTT: 
[{"dateTime":"1693128696.0","gpsLat":"52.152435"},{"dateTime":"1693128696.0","gpsLong":"9.929356"}]
 
 
MQTT: 
[{"dateTime":"1693128698.0","gpsLat":"52.152435"},{"dateTime":"1693128698.0","gpsLong":"9.929356"}]
 
 
MQTT: {"dateTime": "1693128703.0", "inTemp_C": "20.2", "outTemp_C": 
"20.504", "outHumidity": "66.0", "pressure_mbar": "998.3", 
"relbarometer": "998.3", "wh31_ch1_batt": "0.0", "wh31_ch1_sig": "4.0", 
"inHumidity": "60.0", "altimeter_mbar": "1001.9404121257783", 
"barometer_mbar": "1001.7762197264383", "cloudbase_meter": 
"849.858055043151", "dewpoint_C": "13.923820763390072", "heatindex_C": 
"20.3288894", "humidex_C": "23.820824059901074", "inDewpoint_C": 
"12.180722362154029", "rainRate_cm_per_hour": "0.0", "usUnits": "16.0"} 
MQTT: 
[{"dateTime":"1693128700.0","gpsLat":"52.152435"},{"dateTime":"1693128700.0","gpsLong":"9.929356"}]
 
 
MQTT: 
[{"dateTime":"1693128702.0","gpsLat":"52.152435"},{"dateTime":"1693128702.0","gpsLong":"9.929356"}]
 
MQTT: 
[{"dateTime":"1693128704.0","gpsLat":"52.152435"},{"dateTime":"1693128704.0","gpsLong":"9.929356"}]
 
MQTT: {"dateTime": "1693128708.0", "inTemp_C": "20.2", "outTemp_C": 
"20.504", "outHumidity": "66.0", "pressure_mbar": "998.3", 
"relbarometer": "998.3", "wh31_ch1_batt": "0.0", "wh31_ch1_sig": "4.0", 
"inHumidity": "60.0", "altimeter_mbar": "1001.9404121257783", 
"barometer_mbar": "1001.7762197264383", "cloudbase_meter": 
"849.858055043151", "dewpoint_C": "13.923820763390072", "heatindex_C": 
"20.3288894", "humidex_C": "23.820824059901074", "inDewpoint_C": 
"12.180722362154029", "rainRate_cm_per_hour": "0.0", "usUnits": "16.0"}

What do I miss? What may I have done wrongly?


On Thursday, August 24, 2023 at 9:05:49 PM UTC+2 Karen K wrote:

> You can define new observation types in /usr/share/weewx/extensions.py 
> like this:
>
> *import *weewx.units
>
> *for* group *in* weewx.units.std_groups:
>
> weewx.units.std_groups[group].setdefault('group_coordinate',
> 'degree_compass')
>
> weewx.units.obs_group_dict.setdefault('gpsLat','group_coordinate')
>
> weewx.units.obs_group_dict.setdefault('gpsLong','group_coordinate')
>
>
> Stefan Gliessmann schrieb am Donnerstag, 24. August 2023 um 19:23:27 UTC+2:
>
>> This is what I see in MQTT for the GPS data:
>>
>> [{"dateTime":"1692897570", 
>> "gpsLat":"52.152496"},{"dateTime":"1692897570", "gpsLong":"9.929346"}]
>>
>> versus 
>>
>> {"dateTime": "1692897612.0", "inTemp_C": "30.1", "outTemp_C": "27.5", 
>

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

This is what I see in MQTT for the GPS data:

[{"dateTime":"1692897570", "gpsLat":"52.152496"},{"dateTime":"1692897570", 
"gpsLong":"9.929346"}]

versus 

{"dateTime": "1692897612.0", "inTemp_C": "30.1", "outTemp_C": "27.5", 
"outHumidity": "54.0", "pressure_mbar": "1001.30001", 
"relbarometer": "1001.3", "wh31_ch1_batt": "0.0", "wh31_ch1_sig": "4.0", 
"inHumidity": "49.0", "altimeter_mbar": "1004.9493958235101", 
"barometer_mbar": "1004.7053486054396", "cloudbase_meter": 
"1295.8252688165874", "dewpoint_C": "17.347230252723698", "heatindex_C": 
"28.7943194455", "humidex_C": "33.03157722271784", "inDewpoint_C": 
"18.191750223011855", "rainRate_cm_per_hour": "0.0", "usUnits": "16.0"}

I just noticed the [ ... ], but still MQTT in Belchertown needs to be 
explained what these values are. Where would I need to do that?

On Thursday, August 24, 2023 at 7:14:15 PM UTC+2 Stefan Gliessmann wrote:

> [image: Screenshot 2023-08-24 at 19.08.31.png]
> [image: Screenshot 2023-08-24 at 19.08.18.png]
>
> Well - I was successful in forwarding the RV's GPS data per MQTT to the 
> Belchertown skin.
>
> It receives the coordinates, but it does not know what to do with it (e.g. 
> "Data received Invalid date").
> Where would I need to define what values these are and how to store them 
> in the weewx.sdb?
>
> Thank you for any input! :)
>
> Cheers,
> Stefan
>
>
> On Thursday, August 10, 2023 at 6:38:10 PM UTC+2 Stefan Gliessmann wrote:
>
>> Wow - thanks, Tom!
>>
>> That actually sound pretty straight forward and almost too easy ;)
>> Once I have the GPS receiver hooked up to my LTE router; I will try it 
>> out!
>>
>> 😇
>>
>> On Wed, Aug 9, 2023 at 5:54 PM Tom Keffer  wrote:
>>
>>> One way of doing this...
>>>
>>> Station altitude, latitude, and longitude are always obtained from an 
>>> instance of StationInfo 
>>> <https://github.com/weewx/weewx/blob/26bbcc56b5939d3e7e102ba21e9e656074714f67/bin/weewx/station.py#L14>,
>>>  
>>> held in the engine. From this, various views are constructed, including 
>>> what's used as a tag, such as $station.altitude.
>>>
>>> So, with every new archive record you could replace that instance with a 
>>> fresh instance, created in a WeeWX service, using updated values. 
>>> The instance is available as engine.stn_info in the service.
>>>
>>> How does your service get its information? One way would be to add new 
>>> observation types altitude, latitude, and longitude to the archive record. 
>>> Then your new service can get the values from there.
>>>
>>> If you also want values in the database, add altitude,  longitude, and 
>>> latitude to the schema and they will automatically be populated if the 
>>> archive record holds matching types.
>>>
>>> That's off the top of my head. It's a nice approach because it does not 
>>> involve modifying any base weewx code. But, I'm sure I've missed 
>>> something...
>>>
>>> -tk
>>>
>>>
>>> On Wed, Aug 9, 2023 at 8:00 AM Stefan Gliessmann  
>>> wrote:
>>>
>>>> After running into major issues with my LTE router in my RV, weewx and 
>>>> Belchertown w/ MQTT are up and running :)
>>>> Check it out here: https://t.ly/4icFe
>>>>
>>>> My RV router is actually a serious professional LTE router which can 
>>>> provide GPS data, too (once I have a GPs receiver installed).
>>>> Now, I still have to figure out how to push the GPS data into weewx db 
>>>> and have weewx use it for the weather forecasts using aeris within the 
>>>> Belchertown skin.
>>>> Since I have MQTT already working and my router can send the GPS data 
>>>> as MQTT packages, maybe that is a way to do so.
>>>> In weewx.conf the long, latitude and altitude are specified. Is there a 
>>>> way to not update these in the weewx.conf, but have them read from the db 
>>>> and considered accordingly?
>>>>
>>>> Thanks for brainstorming this with me ;)
>>>>
>>>> TIA,
>>>> Stefan
>>>>
>>&

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Wow - thanks, Tom!

That actually sound pretty straight forward and almost too easy ;)
Once I have the GPS receiver hooked up to my LTE router; I will try it out!

😇

On Wed, Aug 9, 2023 at 5:54 PM Tom Keffer  wrote:

> One way of doing this...
>
> Station altitude, latitude, and longitude are always obtained from an
> instance of StationInfo
> <https://github.com/weewx/weewx/blob/26bbcc56b5939d3e7e102ba21e9e656074714f67/bin/weewx/station.py#L14>,
> held in the engine. From this, various views are constructed, including
> what's used as a tag, such as $station.altitude.
>
> So, with every new archive record you could replace that instance with a
> fresh instance, created in a WeeWX service, using updated values.
> The instance is available as engine.stn_info in the service.
>
> How does your service get its information? One way would be to add new
> observation types altitude, latitude, and longitude to the archive record.
> Then your new service can get the values from there.
>
> If you also want values in the database, add altitude,  longitude, and
> latitude to the schema and they will automatically be populated if the
> archive record holds matching types.
>
> That's off the top of my head. It's a nice approach because it does not
> involve modifying any base weewx code. But, I'm sure I've missed
> something...
>
> -tk
>
>
> On Wed, Aug 9, 2023 at 8:00 AM Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wrote:
>
>> After running into major issues with my LTE router in my RV, weewx and
>> Belchertown w/ MQTT are up and running :)
>> Check it out here: https://t.ly/4icFe
>>
>> My RV router is actually a serious professional LTE router which can
>> provide GPS data, too (once I have a GPs receiver installed).
>> Now, I still have to figure out how to push the GPS data into weewx db
>> and have weewx use it for the weather forecasts using aeris within the
>> Belchertown skin.
>> Since I have MQTT already working and my router can send the GPS data as
>> MQTT packages, maybe that is a way to do so.
>> In weewx.conf the long, latitude and altitude are specified. Is there a
>> way to not update these in the weewx.conf, but have them read from the db
>> and considered accordingly?
>>
>> Thanks for brainstorming this with me ;)
>>
>> TIA,
>> Stefan
>>
>> On Monday, July 31, 2023 at 4:25:05 AM UTC+2 Cameron D wrote:
>>
>>> This would be my suggestion as well.  Certainly use a dedicated DB for
>>> the task, then populate it according to the effort you want to put into it.
>>> Options would be:
>>>
>>>- custom GPS unit along the lines Vince suggested
>>>- use a normal in-car GPS unit that records your tracks and
>>>download/export data each day.  I combine my car and walking gps tracks 
>>> for
>>>geotagging photos.
>>>- manually enter data once a day
>>>
>>> When I do long trips, I often take a simple handheld temp/RH logger that
>>> I download occasionally - every few days.
>>> I also have a second table with one row per day, where I manually enter
>>> comments about where the device was located and anything unusual that might
>>> have influenced the results.  Probably less necessary in an RV with fixed
>>> locations, but my logger might end up left inside the tent, outside the
>>> tent, or left inside the car on different days.  This table could also
>>> double as a more general diary.
>>>
>>> On Sunday, 30 July 2023 at 6:39:28 am UTC+10 vince wrote:
>>>
>>>> On Saturday, July 29, 2023 at 1:11:25 PM UTC-7 Stefan Gliessmann wrote:
>>>>
>>>> That would work. But I would miss out on the location and elevation
>>>> data … I would like to include location in a database …
>>>>
>>>>
>>>> Sure. Get a GPS module for your pi and write a little script to seed a
>>>> custom field in the db.   Shouldn't be a big deal.  Just write to a
>>>> secondary sqlite db.
>>>>
>>>>
>>>>
>>> --
>> 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/c0a89ba0-e981-4e58-8a3b-9412bbd0b1c4n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/c0a89ba0-e981-4e58-8a3b-9412

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

After running into major issues with my LTE router in my RV, weewx and 
Belchertown w/ MQTT are up and running :)
Check it out here: https://t.ly/4icFe

My RV router is actually a serious professional LTE router which can 
provide GPS data, too (once I have a GPs receiver installed).
Now, I still have to figure out how to push the GPS data into weewx db and 
have weewx use it for the weather forecasts using aeris within the 
Belchertown skin.
Since I have MQTT already working and my router can send the GPS data as 
MQTT packages, maybe that is a way to do so.
In weewx.conf the long, latitude and altitude are specified. Is there a way 
to not update these in the weewx.conf, but have them read from the db and 
considered accordingly?

Thanks for brainstorming this with me ;)

TIA,
Stefan

On Monday, July 31, 2023 at 4:25:05 AM UTC+2 Cameron D wrote:

> This would be my suggestion as well.  Certainly use a dedicated DB for the 
> task, then populate it according to the effort you want to put into it.
> Options would be:
>
>- custom GPS unit along the lines Vince suggested
>- use a normal in-car GPS unit that records your tracks and 
>download/export data each day.  I combine my car and walking gps tracks 
> for 
>geotagging photos.
>- manually enter data once a day
>
> When I do long trips, I often take a simple handheld temp/RH logger that I 
> download occasionally - every few days.
> I also have a second table with one row per day, where I manually enter 
> comments about where the device was located and anything unusual that might 
> have influenced the results.  Probably less necessary in an RV with fixed 
> locations, but my logger might end up left inside the tent, outside the 
> tent, or left inside the car on different days.  This table could also 
> double as a more general diary.
>
> On Sunday, 30 July 2023 at 6:39:28 am UTC+10 vince wrote:
>
>> On Saturday, July 29, 2023 at 1:11:25 PM UTC-7 Stefan Gliessmann wrote:
>>
>> That would work. But I would miss out on the location and elevation data 
>> … I would like to include location in a database …
>>
>>
>> Sure. Get a GPS module for your pi and write a little script to seed a 
>> custom field in the db.   Shouldn't be a big deal.  Just write to a 
>> secondary sqlite db.
>>
>>  
>>
>

-- 
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/c0a89ba0-e981-4e58-8a3b-9412bbd0b1c4n%40googlegroups.com.

Re: [weewx-user] Re: Lightning Data Stored in weewx.sdb

[Stefan Gliessmann]

Hello everybody ;)

I have a smilier issue with last lightning distance been charted ...
I used the above information to generate my chart which looks like this:

[image: Screenshot 2023-08-09 at 16.43.03.png]

This is with 
[[Corrections]]
lightning_distance = lightning_distance if lightning_strike_count > 
0 else None

I do not have an AcuRite, but an Ecowitt lightning detector ...

Any hint to have the distance been zero when there isn't and lightning 
would be appreciated.

TIA,
Stefan
On Thursday, June 15, 2023 at 6:03:12 AM UTC+2 William Reading wrote:

> I was going to submit a pull request to fix this and realized that the 
> Atlas driver uses "strike_count" and the rest of them use "strikes_total", 
> so fixing the defaults would be a breaking change. I went ahead and just 
> put the delta in my weewx.conf file to work around it.
>
> [[sensor_map]]
> ...
> atlas_lightning_strike_count = strike_count..AcuriteAtlasPacket
> ...
>
> [[deltas]]
> lightning_strike_count = atlas_lightning_strike_count
> On Wednesday, June 14, 2023 at 12:59:13 PM UTC-4 Mark Fraser wrote:
>
>> On 13/06/2023 20:17, Kevin Crivelli wrote: 
>> > mines definitely a little different. This is what I already have. It 
>> > seems to follow the logic you shared above in your configuration but my 
>> > packets are named differently. where you have "Atlas_strike_count = 
>> > strike_count.0011.AcuriteAtlasPacket" I have "strikes_total = 
>> > strikes_total.1255.AcuriteLightningPacket". from looking at my deltas 
>> > section, does it look as though I have this set up correctly or am I 
>> off 
>> > a little bit? 
>> > 
>> > [SDR] 
>> > # This section is for the software-defined radio driver. 
>> > 
>> > # The driver to use 
>> > driver = user.sdr 
>> > 
>> > 
>> > [[sensor_map]] 
>> > outTemp = temperature.030B.AcuriteAtlasPacket 
>> > outHumidity = humidity.030B.AcuriteAtlasPacket 
>> > windSpeed = wind_speed.030B.AcuriteAtlasPacket 
>> > windDir = wind_dir.030B.AcuriteAtlasPacket 
>> > UV = uv.030B.AcuriteAtlasPacket 
>> > rain_total = rain_total.030B.AcuriteAtlasPacket 
>> > radiation = lux.030B.AcuriteAtlasPacket 
>> > lux = lux.030B.AcuriteAtlasPacket 
>> > outTempBatteryStatus = battery.030B.AcuriteAtlasPacket 
>> > lightning_distance = distance.1255.AcuriteLightningPacket 
>> > strikes_total = strikes_total.1255.AcuriteLightningPacket 
>> > inTemp = temperature.3071.AcuriteTowerPacketV2 
>> > inHumidity = humidity.3071.AcuriteTowerPacketV2 
>> > pressure = pressure.171.FOWH32BPacket 
>> > 
>> > 
>> > [[deltas]] 
>> > rain = rain_total 
>> > lightning_strike_count = strikes_total 
>>
>> I think there is a bug in the sdr.py from 
>> https://github.com/matthewwall/weewx-sdr/blob/master/bin/user/sdr.py 
>> where the deltas are listed as: 
>>
>> DEFAULT_DELTAS = { 
>> 'rain': 'rain_total', 
>> 'strikes': 'strikes_total'} 
>>
>> Which I couldn't get to work, so I changed mine to: 
>> DEFAULT_DELTAS = { 
>> 'rain': 'rain_total', 
>> 'lightning_strike_count': 'strikes_total'} 
>> And it works without having to add a deltas section to weewx.conf. 
>>
>>

-- 
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/c31d91eb-24d9-472e-8476-60af931c04e8n%40googlegroups.com.

[weewx-user] Use of systemd-time-wait-sync instead of time-sync.target in weewx.service

[stefan...@gmail.com]

Could it be a good idea to replace the following lines in weewx.service?

Replacing:
Requires=time-sync.target
After=time-sync.target

With:
Requires=systemd-time-wait-sync.service
After=systemd-time-wait-sync.service

in Raspbian Buster it should be able to prevent weewx from running until 
the system time has been synchronized via the internet.
Any advice on using or not using this trick?

-- 
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/f27ef18a-e6ba-459f-b86c-89a794d413edn%40googlegroups.com.

Re: [weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

That would work. But I would miss out on the location and elevation data …
I would like to include location in a database …

p q  schrieb am Sa. 29. Juli 2023 um 20:25:

> Why not use the same one and send the temp/rH via MQTT to your main
> system, since you have connectivity. You can use one of the ExtraTemps and
> there's probably something suitable for rH.
>
> On Sat, Jul 29, 2023 at 10:49 AM Stefan Gliessmann <
> stefan.gliessm...@gmail.com> wrote:
>
>> Dear all -
>>
>> I was googling this topic without any results. So, I came here to see, if
>> anybody did this already.
>>
>> Since ever I have a weewx installation running at home, I would like to
>> built a second one in my RV with probably just temps in/out, humidity
>> in/out and air pressure. The RV has 4G/5G internet connection and plenty of
>> power to run a RPi ...
>>
>> Any experiences with updating the station locations automatically in
>> weewx.conf? Anything else seems to be straight forward ...
>>
>> Cheers,
>> Stefan
>>
>> --
>> 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/97dea70f-9a2e-422d-a25b-924011308c35n%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/97dea70f-9a2e-422d-a25b-924011308c35n%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>
>
>>
>
> --
> Peter Quinn
> (415)794-2264
>
> --
> 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/Fwd1BvCfCoM/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/CAA1SM22tJ81-cEEcFrpK6yD%2BOoqjnLB7CsJbvr8HRnZ%2BPMdo6w%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAA1SM22tJ81-cEEcFrpK6yD%2BOoqjnLB7CsJbvr8HRnZ%2BPMdo6w%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACXWM9Q7vSQ%3DvyPm0Uvpw9t7u0Uz3ajzuvSTNYKC3OimW-0-6w%40mail.gmail.com.

Re: [weewx-user] Re: WeeWX in an RV?

[Stefan Gliessmann]

There is no real reason why other then having historical record of weather
where I was …

I am thinking of the Ecowitt GW-1100 with an external 3-in-1 sensor or this
one
https://www.amazon.de/dp/B06X3YDSVS?psc=1&smid=A29AHYTNE2R6PE&ref_=chk_typ_imgToDp
which should be compatible with the Ecowitt infrastructure.

When updating the location, forecasts should be also updated within skins
like Belchertown.


vince  schrieb am Sa. 29. Juli 2023 um 20:44:

> On Saturday, July 29, 2023 at 10:49:14 AM UTC-7 Stefan Gliessmann wrote:
>
> Any experiences with updating the station locations automatically in
> weewx.conf? Anything else seems to be straight forward ...
>
>
> Why do you need to update the location at all ?   What is your goal for
> displaying the data ?   Do you need to upload somewhere and/or have a db of
> historical data (ie, do you really even need weewx) ?   And of course
> what's your budget ?
>
> Picking a random Ecowitt product it's under a $50 thing if you just want a
> small display and a sensor or two with no internet required...
> (https://shop.ecowitt.com/products/wn2810)
>
>
>
> --
> 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/Fwd1BvCfCoM/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/d033aa60-76a0-44e0-9009-3398ac0d65c4n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/d033aa60-76a0-44e0-9009-3398ac0d65c4n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACXWM9ROvh-bmCSMYctgS8J5%3Db5_yes-_0%2BV7ANgSyJp7YzNrA%40mail.gmail.com.

[weewx-user] WeeWX in an RV?

[Stefan Gliessmann]

Dear all -

I was googling this topic without any results. So, I came here to see, if 
anybody did this already.

Since ever I have a weewx installation running at home, I would like to 
built a second one in my RV with probably just temps in/out, humidity 
in/out and air pressure. The RV has 4G/5G internet connection and plenty of 
power to run a RPi ...

Any experiences with updating the station locations automatically in 
weewx.conf? Anything else seems to be straight forward ...

Cheers,
Stefan

-- 
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/97dea70f-9a2e-422d-a25b-924011308c35n%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

SOLVED!

[image: Screenshot 2023-07-25 at 11.44.40.png]

Thank you, Jacques, for pointing out that I had two (2) weewx to mqtt
extensions installed. 😁
Once I removed both and reinstalled the one from
https://github.com/matthewwall/weewx-mqtt, modified the weewx.conf
accordingly and restarted WeeWX, I had the green dot and data receiving!

I do highly appreciate your patience with me! 🙏

Thank you all again,
Stefan


On Tue, Jul 25, 2023 at 10:35 AM Jacques Terrettaz 
wrote:

> It seems that you have 2 mqtt extensions installed :
>
> *mqtt  0.24  Upload weather data to MQTT server.*
>
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
>
> Which one is active ?
>
> Le 25 juil. 2023 à 10:25, Stefan Gliessmann 
> a écrit :
>
> the current main version 0.24
>
> sudo wee_extension --list
> Extension NameVersion   Description
> *mqtt  0.24  Upload weather data to MQTT server.*
> GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
> LAN/Wi-Fi Gateway API.
> Belchertown   1.3.1 A clean modern skin with real time streaming
> updates and interactive charts. Modeled after BelchertownWeather.com
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
> How did you grep the weather/loop mqtt message on your system?
>
>
>
> On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
> wrote:
>
>> It should look like : weather/loop. The loop topic is a json containing
>> all the data aggregated  and is apparently not generated with your setup.
>>
>> Here is an exemple of the content of a weather/loop mqtt message for my
>> station : {"dateTime": "1690272486.0", "barometer_mbar":
>> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
>> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
>> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
>> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
>> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
>> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
>> "21.668", "leafTemp2_C": "18.332", "outHumidity":
>> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
>> "125.0", "stormRain_cm": "0.3902", "stormStart":
>> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
>> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
>> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
>> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
>> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
>> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
>> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
>> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
>> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
>> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
>> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
>> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
>> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
>> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
>> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
>> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
&

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

OMG - what did I do there?
I will first remove the MQTT 0.2.0 one.
I don't remember that installation :(

Glad, you asked me which version I run ... LOL

On Tue, Jul 25, 2023 at 10:35 AM Jacques Terrettaz 
wrote:

> It seems that you have 2 mqtt extensions installed :
>
> *mqtt  0.24  Upload weather data to MQTT server.*
>
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
>
> Which one is active ?
>
> Le 25 juil. 2023 à 10:25, Stefan Gliessmann 
> a écrit :
>
> the current main version 0.24
>
> sudo wee_extension --list
> Extension NameVersion   Description
> *mqtt  0.24  Upload weather data to MQTT server.*
> GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
> LAN/Wi-Fi Gateway API.
> Belchertown   1.3.1 A clean modern skin with real time streaming
> updates and interactive charts. Modeled after BelchertownWeather.com
> MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
> broker
>
> How did you grep the weather/loop mqtt message on your system?
>
>
>
> On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
> wrote:
>
>> It should look like : weather/loop. The loop topic is a json containing
>> all the data aggregated  and is apparently not generated with your setup.
>>
>> Here is an exemple of the content of a weather/loop mqtt message for my
>> station : {"dateTime": "1690272486.0", "barometer_mbar":
>> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
>> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
>> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
>> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
>> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
>> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
>> "21.668", "leafTemp2_C": "18.332", "outHumidity":
>> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
>> "125.0", "stormRain_cm": "0.3902", "stormStart":
>> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
>> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
>> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
>> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
>> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
>> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
>> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
>> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
>> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
>> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
>> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
>> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
>> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
>> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
>> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
>> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
>> "14.312901895429865", "heatindex_C": "19.1672225", "humidex_C":
>> "22.828243781966584", "inDewpoint_C": "13.129089961868337",
>> "maxSolarRad_Wpm2": "598.7

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

https://github.com/matthewwall/weewx-mqtt

Yes, I use the one from Matthew Wall ...

I am just about to remove and reinstall it ;)

On Tue, Jul 25, 2023 at 10:29 AM Jacques Terrettaz 
wrote:

> Are you using this extension : https://github.com/michael-slx/weewx-mqtt.
> ?
>
> If yes, this extension does not generate a "loop" json topic needed by the
> Belchertown skin. In that case, you have to use the following extension :
> https://github.com/matthewwall/weewx-mqtt/tree/master
>
> Le 25 juil. 2023 à 10:03, Stefan Gliessmann 
> a écrit :
>
> GE - could you expand on your statement: "referenced topic not listed in
> the topics of published messages"?
>
> what should mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>
>> referenced topic not listed in the topics of published messages
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>> wrote:
>>
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
> --
> 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/Scp2wA2qOw4/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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com?utm_medium=email&utm_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/Scp2wA2qOw4/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/89EEBE22-7B54-4AAA-89C6-BF9E60E7B00B%40gmail.com
> <https://groups.google.com/d/msgid/weewx-user/89EEBE22-7B54-4AAA-89C6-BF9E60E7B00B%40gmail.com?utm_medium=email&utm_source=footer>
> .
>

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

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thank you, GE!
I appreciate your help. the topic was configured according the different
guides online.

On Tue, Jul 25, 2023 at 10:11 AM Graham Eddy  wrote:

> i don’t use belchertown or that mqtt driver so i don’t know the details.
> my observation is that the report belchertown seems to be waiting on topic
> ‘’weather/loop’’ (i don’t know the syntax but it’s a reasonable
> presumption), but when you printed all the messages being published, none
> had that topic → belchertown quite rightly is not reporting receiving any
> messages
> *⊣GE⊢*
>
> On 25 Jul 2023, at 6:03 pm, Stefan Gliessmann 
> wrote:
>
> GE - could you expand on your statement: "referenced topic not listed in
> the topics of published messages"?
>
> what should mqtt_websockets_topic look like? e.g. =
> weather/inTemp_degree_C/loop?
>
> TIA,
> Stefan
>
> On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:
>
>> referenced topic not listed in the topics of published messages
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann 
>> wrote:
>>
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
> --
> 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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com?utm_medium=email&utm_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/Scp2wA2qOw4/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/87896D52-4563-457D-A539-A436ACCAEF10%40geddy.au
> <https://groups.google.com/d/msgid/weewx-user/87896D52-4563-457D-A539-A436ACCAEF10%40geddy.au?utm_medium=email&utm_source=footer>
> .
>

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

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

the current main version 0.24

sudo wee_extension --list
Extension NameVersion   Description
*mqtt  0.24  Upload weather data to MQTT server.*
GW10000.5.0b5   WeeWX driver for devices using the Ecowitt
LAN/Wi-Fi Gateway API.
Belchertown   1.3.1 A clean modern skin with real time streaming
updates and interactive charts. Modeled after BelchertownWeather.com
MQTT  0.2.0 Extension for uploading LOOP data to an MQTT
broker

How did you grep the weather/loop mqtt message on your system?



On Tue, Jul 25, 2023 at 10:12 AM Jacques Terrettaz 
wrote:

> It should look like : weather/loop. The loop topic is a json containing
> all the data aggregated  and is apparently not generated with your setup.
>
> Here is an exemple of the content of a weather/loop mqtt message for my
> station : {"dateTime": "1690272486.0", "barometer_mbar":
> "1006.4684246818595", "inTemp_C": "24.218", "inHumidity":
> "50.0", "outTemp_C": "19.28", "windSpeed_kph": "8.04672",
> "windSpeed10_kph": "6.437376", "windDir": "197.0", "extraTemp1_C":
> "26.664", "extraTemp2_C": "27.22", "extraTemp3_C":
> "23.89", "soilTemp1_C": "21.668", "soilTemp2_C":
> "18.332", "soilTemp3_C": "21.668", "leafTemp1_C":
> "21.668", "leafTemp2_C": "18.332", "outHumidity":
> "73.0", "rainRate_cm_per_hour": "0.0", "UV": "1.3", "radiation_Wpm2":
> "125.0", "stormRain_cm": "0.3902", "stormStart":
> "1690149600.0", "dayRain_cm": "0.01999878", "monthRain_cm":
> "3.69977435", "yearRain_cm": "35.67782352006", "dayET_cm":
> "0.03048", "monthET": "4.03", "yearET": "18.16", "soilMoist1_centibar":
> "51.0", "soilMoist3_centibar": "41.0", "leafWet1_count": "0.0",
> "insideAlarm": "0.0", "rainAlarm": "0.0", "outsideAlarm1": "0.0",
> "outsideAlarm2": "0.0", "extraAlarm1": "0.0", "extraAlarm2": "0.0",
> "extraAlarm3": "0.0", "extraAlarm4": "0.0", "extraAlarm5": "0.0",
> "extraAlarm6": "0.0", "extraAlarm7": "0.0", "extraAlarm8": "0.0",
> "soilLeafAlarm1": "0.0", "soilLeafAlarm2": "0.0", "soilLeafAlarm3": "0.0",
> "soilLeafAlarm4": "0.0", "txBatteryStatus": "0.0",
> "consBatteryVoltage_volt": "3.89", "forecastIcon": "3.0", "forecastRule":
> "192.0", "sunrise": "1690258020.0", "sunset": "1690312440.0", "rain_cm":
> "0.0", "windGust_kph": "17.702784", "windGustDir": "190.0",
> "pressure_mbar": "963.8859943175378", "altimeter_mbar":
> "1008.0216245072318", "appTemp_C": "19.08558834080051", "beaufort_count":
> "2.0", "cloudbase_meter": "993.9764167741055", "dewpoint_C":
> "14.312901895429865", "heatindex_C": "19.1672225", "humidex_C":
> "22.828243781966584", "inDewpoint_C": "13.129089961868337",
> "maxSolarRad_Wpm2": "598.7311131756545", "windchill_C":
> "19.28", "outVaporP_mbar": "16.311027360815487", "outSVP_mbar":
> "22.343873097007513", "outMixingRatio_gram_per_kilogram":
> "10.713127603866752", "outEquiTemp_C": "44.3435366864702", "outThetaE_C":
> "47.69725228025629", "outHumAbs_microgram_per_meter_cubed":
> "12085709.924432162", "sunshineThreshold_Wpm2": "413.9737112655241",
> "sunshineDay": "53.43", "radiationISS_Wpm2": "111.0",
> "OutTemp-1h_C": "18.332", "OutTemp-24h_C": "20.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

GE - could you expand on your statement: "referenced topic not listed in 
the topics of published messages"?

what should mqtt_websockets_topic look like? e.g. = 
weather/inTemp_degree_C/loop?

TIA,
Stefan

On Tuesday, July 25, 2023 at 9:45:40 AM UTC+2 Graham Eddy wrote:

> referenced topic not listed in the topics of published messages
> *⊣GE⊢*
>
> On 25 Jul 2023, at 5:34 pm, Stefan Gliessmann  
> wrote:
>
> mqtt_websockets_topic = weather/loop
>
>
>

-- 
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/58a676a8-50db-4f36-8078-f27ddf27d2c3n%40googlegroups.com.

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

This is what I get:

teffi@weewx:~$ *mosquitto_sub -v -t "#" -h 192.168.178.190*
weather/connection_status online
weather/connection_status online
weather/dateTime_unix_epoch 1690270081
weather/inTemp_degree_C 24.2
weather/outTemp_degree_C 15.799
weather/inHumidity_percent 53
weather/outHumidity_percent 75
weather/pressure_mbar 996.7
weather/relbarometer 996.7
weather/luminosity 8013.0
weather/uvradiation 6.4
weather/UV_uv_index 0
weather/rain_cm 0.0
weather/stormRain_cm 0.35003
weather/rainRate_cm_per_hour 0.0
weather/dayRain_cm 0.0
weather/weekRain 3.8
weather/monthRain_cm 1.8103
weather/yearRain_cm 1.8103
weather/windDir_degree_compass 346
weather/windSpeed_km_per_hour 3.9600098425441494
weather/windGust_km_per_hour 5.400013421651113
weather/daymaxwind 4.1
weather/wh65_batt 0
weather/wh65_sig 4
weather/radiation_watt_per_meter_squared 63.24388318863457
weather/altimeter_mbar 1000.3356188974249
weather/appTemp_degree_C 15.463360560056334
weather/barometer_mbar 1000.2272009128795
weather/cloudbase_meter 581.6088849469353
weather/dewpoint_degree_C 11.375139081484333
weather/heatindex_degree_C 15.3938887
weather/humidex_degree_C 17.74032194160783
weather/inDewpoint_degree_C 14.004795683252373
weather/maxSolarRad_watt_per_meter_squared 496.46758917662
weather/windchill_degree_C 15.799
weather/usUnits 16

So, weewx prodcasts the weather thru the mqtt broker mosquitto :)
Yet still, Belchertown skin remains waiting for data

Here is my [StdReport] [[Belchertown]] [[[Extras]]] stanza in weewx.conf:

#--- MQTT Websockets (for Real Time Streaming) Options ---
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.178.190
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/loop
mqtt_websockets_username = teffi
mqtt_websockets_password = 5tefan4U
disconnect_live_website_visitor = 180

On Tue, Jul 25, 2023 at 3:52 AM Graham Eddy  wrote:

> i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus
> authentication if any
> *⊣GE⊢*
>
> On 25 Jul 2023, at 11:47 am, Graham Eddy  wrote:
>
> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is**
> being published
> *⊣GE⊢*
>
> On 25 Jul 2023, at 5:08 am, vince  wrote:
>
> I think you have a mismatch in what you are publishing vs. what you are
> trying to subscribe to.
>
>
>
> --
> 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/686A219D-75B5-431B-9044-215355744BDF%40geddy.au
> 
> .
>
>
> --
> 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/Scp2wA2qOw4/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/749B9857-ACE8-4069-87AF-55F0BDB55EFF%40geddy.au
> 
> .
>

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

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Dear Vince,

you mean something like this?


Jul 24, 2023, 1:51:16 PM (19 hours ago) 
to weewx-user
Thank you all for providing input / sharing your configurations.
I made the suggested changes and more, but still belchertown displays 
Connected. Waiting for data ...
I have attached all configs / logs / checks I could think of below.

Thanks again for your input in advance!
Stefan


These are my current configs:

*mosquitto*:
*/etc/mosquitto/mosquitto.conf *
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /run/mosquitto/mosquitto.pid

#persistence true
#persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d

*/etc/mosquitto/conf.d/myconfig.conf *
persistence false

allow_anonymous true
password_file /etc/mosquitto/passwd

acl_file /etc/mosquitto/acl

# mqtt
listener 1883
protocol mqtt

# websockets
listener 9001
protocol websockets

*/etc/mosquitto/acl*
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user teffi
topic weather/#

*MQTT in WeeWX:*
[StdRESTful]
[[MQTT]]

# Enable/disable this service
enable = true

# Hostname/IP of MQTT broker
host = 192.168.178.190
server_url = mqtt://teffi:@localhost:1883/


# Credentials
user = teffi
password = 

# Prefix for topics

topic = weather
unit_system = METRIC
binding = archive,loop
aggregation = aggregate

*checking if WeeWX serves mosquitto with info:*
*mosquitto_sub -h 192.168.178.190 -t weather/#*
online
online
1690198935
24.6
23.9
53
54
993.7
993.7
11377.0
8.9
0
0.0
0.0
0.0
0.0
0.3
1.46
1.46
294
6.480016105981334
9.360023264195261
7.1
0
4
89.7947908445146
997.3266279778212
23.910163208269463
997.1205287280834
1262.3292207924262
14.015863559854884
23.75
27.2746765106266
14.37423758808152
859.4544718145543
23.9
16

*Belchertown skin receiving MQTT topic /weather/#*
[StdReport]
[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true

[[[Extras]]]
#--- MQTT Websockets (for Real Time Streaming) Options ---
#log_failure = True 
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.178.190
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/loop
mqtt_websockets_username = teffi
mqtt_websockets_password = 
disconnect_live_website_visitor = 180

*Checking if it works in webpage:*
*http://localhost/weewx/belchertown/ <http://localhost/weewx/belchertown/>*
 or weewxhi.de

Connected. Waiting for data. Last Updated July 24, 2023, 1:20:00 PM

The webpage never receives data.


*mosquitto.log shows connections:*
*sudo more /var/log/mosquitto/mosquitto.log *

1690197817: mosquitto version 2.0.11 starting
1690197817: Config loaded from /etc/mosquitto/mosquitto.conf.
1690197817: Opening ipv4 listen socket on port 1883.
1690197817: Opening ipv6 listen socket on port 1883.
1690197817: Opening websockets listen socket on port 9001.
1690197817: mosquitto version 2.0.11 running
1690197822: New connection from 192.168.178.190:36367 on port 1883.
1690197822: New client connected from 192.168.178.190:36367 as 
weewx_e353ae0d (p2, c1, k60, u'teffi').
1690197840: New client connected from :::192.168.178.190:59900 as 
website819759641 (p2, c1, k60, u'teffi').
1690197884: Client website819759641 closed its connection.
1690197884: Client  closed its connection.
1690197886: New client connected from :::192.168.178.190:52896 as 
website398593267 (p2, c1, k60, u'teffi').
1690198918: New connection from 192.168.178.190:36078 on port 1883.
1690198918: New client connected from 192.168.178.190:36078 as 
auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA (p2, c1, k60).
1690198939: Client auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA disconnected.
1690199057: New client connected from :::192.168.178.64:57281 as 
website924402803 (p2, c1, k60, u'teffi').
On Tuesday, July 25, 2023 at 5:15:54 AM UTC+2 vince wrote:

> If Stefan would just post his MQTT and Belchertown stanzas from weewx.conf 
> we could cut to the chase here and just tell him where things aren't 
> configured correctly
>
> On Monday, July 24, 2023 at 6:52:05 PM UTC-7 Graham Eddy wrote:
>
>> i meant ‘mosquito_sub -v -t “#" -h brokerhost’ on weewx host, plus 
>> authentication if any
>> *⊣GE⊢*
>>
>> On 25 Jul 2023, at 11:47 am, Graham Eddy  wrote:
>>
>> try ‘mosquito_sub -v -t topic_pattern -h brokerhost’ to see what **is** 
>> being published
>&

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

user "teffi" has readwrite permission

in Firefox inspect error console there are no errors wrt websocket or
javascript errors ... (only errors with geolocation & uncaught type error
in context with windy.com)



On Mon, Jul 24, 2023 at 5:04 PM Jacques Terrettaz 
wrote:

> Another point to check :
>
> Please verify in your mosquitto acl file (/etc/mosquitto/acl) that the
> user "teffi" has read permission for the topic "weather"
>
> Le 24 juil. 2023 à 16:40, Stefan Gliessmann 
> a écrit :
>
> Thanks, Jaques!
>
> wrt
> *1)  when opening your website from local network :  your mqtt broker is
> using port 9001 for websockets. If it doesn't works , you may have to
> verify that this port 9001 is not blocked by a firewall.  *
> 9001 is not blocked by the firewall on 192.168.178.190
> I can receive the via 9001 on my iPhone with an Matt client the values
>
> *2)  when opening your website from internet (http://weewxhi.de
> <http://weewxhi.de/>) .i.e outside your local network
> :  mqtt_websockets_host = 192.168.178.190  is a local network IP address
> that cannot be accessed from outside. You should use  a dynamic dns service
> (no-ip, dyndns or other) to create a redirection from internet to your mqtt
> broker, and configure your router and firewall accordingly.*
> Yeah - I have dyndns enabled and just opened 9001 on my router, too.
>
> Unfortunately, it continues to say "Connected. Waiting for data."
>
> Does a Belchertown config file override weewx.conf settings somewhere?
>
>
> On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz 
> wrote:
>
>> Two things to consider :
>>
>>
>> 1)  when opening your website from local network :  your mqtt broker is
>> using port 9001 for websockets. If it doesn't works , you may have to
>> verify that this port 9001 is not blocked by a firewall.
>> 2)  when opening your website from internet (http://weewxhi.de) .i.e
>> outside your local network :  mqtt_websockets_host = 192.168.178.190  is
>> a local network IP address that cannot be accessed from outside. You should
>> use  a dynamic dns service (no-ip, dyndns or other) to create a redirection
>> from internet to your mqtt broker, and configure your router and firewall
>> accordingly.
>>
>>
>>
>>
>> Le 24 juil. 2023 à 15:06, Stefan Gliessmann 
>> a écrit :
>>
>> Thank you for the feedback.
>> I changed "localhost" to the IP of the MQTT broker as suggested.
>> It did not fix it ...
>>
>> As far as I understand that section is for uploading weewx data to the
>> mqtt broker.
>> That part works well as I can read the weather with an mqtt client.
>>
>> It is the Belchertown skin part which connects to the MQTT Brocker with
>> websocket, but it cannot receive data for updates ...
>>
>> I am really puzzled ...
>>
>> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
>> wrote:
>>
>>> Hi,
>>>
>>> it doesnt work with localhost. Think, you start your Browser localy so
>>> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>>>
>>> From My weewx config (the MQTT part). Think i configured my mqtt and
>>> Webssite with https.
>>>
>>> ##weewx.conf#
>>> [[MQTT]]
>>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
>>> topic = weather
>>> unit_system = METRIC
>>> binding = archive, loop
>>> aggregation = aggregate
>>> log_success = False
>>> log_failure = True
>>> [[[tls]]]
>>> tls_version = tlsv12
>>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>>> [[[inputs]]]
>>> dayRain
>>> name = dayRain_mm
>>> units = mm
>>> rainRate
>>> name = rainRate_mm_per_hour
>>> units = mm_per_hour
>>>
>>> [[Belchertown]]
>>>
>>> [[[Extras]]]
>>>
>>>
>>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>>> mqtt_websockets_enabled = 1
>>> mqtt_websockets_host = gw.martenhinrichs.de
>>> mqtt_websockets_port = 9001
>>> mqtt_websockets_ssl = 1
>>> mqtt_websockets_topic = weather/loop
>>>
>>>
>>>
>>>
>>>
>>> #mosquitto.conf

Re: [weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thanks, Jaques!

wrt
*1)  when opening your website from local network :  your mqtt broker is
using port 9001 for websockets. If it doesn't works , you may have to
verify that this port 9001 is not blocked by a firewall.  *
9001 is not blocked by the firewall on 192.168.178.190
I can receive the via 9001 on my iPhone with an Matt client the values

*2)  when opening your website from internet (http://weewxhi.de
<http://weewxhi.de>) .i.e outside your local network
:  mqtt_websockets_host = 192.168.178.190  is a local network IP address
that cannot be accessed from outside. You should use  a dynamic dns service
(no-ip, dyndns or other) to create a redirection from internet to your mqtt
broker, and configure your router and firewall accordingly.*
Yeah - I have dyndns enabled and just opened 9001 on my router, too.

Unfortunately, it continues to say "Connected. Waiting for data."

Does a Belchertown config file override weewx.conf settings somewhere?


On Mon, Jul 24, 2023 at 3:24 PM Jacques Terrettaz 
wrote:

> Two things to consider :
>
>
> 1)  when opening your website from local network :  your mqtt broker is
> using port 9001 for websockets. If it doesn't works , you may have to
> verify that this port 9001 is not blocked by a firewall.
> 2)  when opening your website from internet (http://weewxhi.de) .i.e
> outside your local network :  mqtt_websockets_host = 192.168.178.190  is
> a local network IP address that cannot be accessed from outside. You should
> use  a dynamic dns service (no-ip, dyndns or other) to create a redirection
> from internet to your mqtt broker, and configure your router and firewall
> accordingly.
>
>
>
>
> Le 24 juil. 2023 à 15:06, Stefan Gliessmann 
> a écrit :
>
> Thank you for the feedback.
> I changed "localhost" to the IP of the MQTT broker as suggested.
> It did not fix it ...
>
> As far as I understand that section is for uploading weewx data to the
> mqtt broker.
> That part works well as I can read the weather with an mqtt client.
>
> It is the Belchertown skin part which connects to the MQTT Brocker with
> websocket, but it cannot receive data for updates ...
>
> I am really puzzled ...
>
> On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
> wrote:
>
>> Hi,
>>
>> it doesnt work with localhost. Think, you start your Browser localy so
>> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>>
>> From My weewx config (the MQTT part). Think i configured my mqtt and
>> Webssite with https.
>>
>> ##weewx.conf#
>> [[MQTT]]
>> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
>> topic = weather
>> unit_system = METRIC
>> binding = archive, loop
>> aggregation = aggregate
>> log_success = False
>> log_failure = True
>> [[[tls]]]
>> tls_version = tlsv12
>> ca_certs = /etc/ssl/certs/ca-certificates.crt
>> [[[inputs]]]
>> dayRain
>> name = dayRain_mm
>> units = mm
>> rainRate
>> name = rainRate_mm_per_hour
>> units = mm_per_hour
>>
>> [[Belchertown]]
>>
>> [[[Extras]]]
>>
>>
>> #--- MQTT Websockets (for Real Time Streaming) Options ---
>> mqtt_websockets_enabled = 1
>> mqtt_websockets_host = gw.martenhinrichs.de
>> mqtt_websockets_port = 9001
>> mqtt_websockets_ssl = 1
>> mqtt_websockets_topic = weather/loop
>>
>>
>>
>>
>>
>> #mosquitto.conf
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>> acl_file /etc/mosquitto/acl
>> persistence false
>>
>> # mqtt
>> listener 1883
>> listener 8883
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
>> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
>> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
>> protocol websockets
>>
>>
>>
>>
>>
>>
>> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>>
>>> Thank you all for providing input / sharing your configurations.
>>> I made the suggeste

Re: [weewx-user] Re: MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thank you for the feedback.
I changed "localhost" to the IP of the MQTT broker as suggested.
It did not fix it ...

As far as I understand that section is for uploading weewx data to the mqtt
broker.
That part works well as I can read the weather with an mqtt client.

It is the Belchertown skin part which connects to the MQTT Brocker with
websocket, but it cannot receive data for updates ...

I am really puzzled ...

On Mon, Jul 24, 2023 at 2:56 PM mh081...@gmail.com 
wrote:

> Hi,
>
> it doesnt work with localhost. Think, you start your Browser localy so
> your Loca Browser try to mqqt to localhost. And there is no mwtt server.
>
> From My weewx config (the MQTT part). Think i configured my mqtt and
> Webssite with https.
>
> ##weewx.conf#
> [[MQTT]]
> server_url = mqtt://pi:passw...@gw.martenhinrichs.de:8883/
> topic = weather
> unit_system = METRIC
> binding = archive, loop
> aggregation = aggregate
> log_success = False
> log_failure = True
> [[[tls]]]
> tls_version = tlsv12
> ca_certs = /etc/ssl/certs/ca-certificates.crt
> [[[inputs]]]
> dayRain
> name = dayRain_mm
> units = mm
> rainRate
> name = rainRate_mm_per_hour
> units = mm_per_hour
>
> [[Belchertown]]
>
> [[[Extras]]]
>
>
> #--- MQTT Websockets (for Real Time Streaming) Options ---
> mqtt_websockets_enabled = 1
> mqtt_websockets_host = gw.martenhinrichs.de
> mqtt_websockets_port = 9001
> mqtt_websockets_ssl = 1
> mqtt_websockets_topic = weather/loop
>
>
>
>
>
> #mosquitto.conf
> allow_anonymous true
> password_file /etc/mosquitto/passwd
> acl_file /etc/mosquitto/acl
> persistence false
>
> # mqtt
> listener 1883
> listener 8883
> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
> protocol mqtt
>
> # websockets
> listener 9001
> certfile /etc/letsencrypt/live/gw.martenhinrichs.de/cert.pem
> cafile /etc/letsencrypt/live/gw.martenhinrichs.de/chain.pem
> keyfile /etc/letsencrypt/live/gw.martenhinrichs.de/privkey.pem
> protocol websockets
>
>
>
>
>
>
> Stefan Gliessmann schrieb am Montag, 24. Juli 2023 um 13:51:16 UTC+2:
>
>> Thank you all for providing input / sharing your configurations.
>> I made the suggested changes and more, but still belchertown displays
>> Connected. Waiting for data ...
>> I have attached all configs / logs / checks I could think of below.
>>
>> Thanks again for your input in advance!
>> Stefan
>>
>>
>> These are my current configs:
>>
>> *mosquitto*:
>> */etc/mosquitto/acl:*
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>>
>> # Allow anonymous to read weather
>> topic read weather/#
>>
>> # weewx readwrite to the loop
>> user teffi
>>
>> */etc/mosquitto/mosquitto.conf *
>> # Place your local configuration in /etc/mosquitto/conf.d/
>> #
>> # A full description of the configuration file is at
>> # /usr/share/doc/mosquitto/examples/mosquitto.conf.example
>>
>> pid_file /run/mosquitto/mosquitto.pid
>>
>> #persistence true
>> #persistence_location /var/lib/mosquitto/
>>
>> log_dest file /var/log/mosquitto/mosquitto.log
>>
>> include_dir /etc/mosquitto/conf.d
>>
>> */etc/mosquitto/conf.d/myconfig.conf *
>> persistence false
>>
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>
>> acl_file /etc/mosquitto/acl
>>
>> # mqtt
>> listener 1883
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> protocol websockets
>>
>> */etc/mosquitto/acl*
>> # Allow anonymous access to the sys
>> topic read $SYS/#
>>
>> # Allow anonymous to read weather
>> topic read weather/#
>>
>> # weewx readwrite to the loop
>> user teffi
>> topic weather/#
>>
>> *MQTT in WeeWX:*
>> [StdRESTful]
>> [[MQTT]]
>>
>> # Enable/disable this service
>> enable = true
>>
>> # Hostname/IP of MQTT broker
>> host = 192.168.178.190
>> server_url = mqtt://teffi:@localhost:1883/
>>
>>
>> # Credentials
>> user = t

[weewx-user] Re: MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

Thank you all for providing input / sharing your configurations.
I made the suggested changes and more, but still belchertown displays 
Connected. Waiting for data ...
I have attached all configs / logs / checks I could think of below.

Thanks again for your input in advance!
Stefan


These are my current configs:

*mosquitto*:
*/etc/mosquitto/acl:*
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user teffi

*/etc/mosquitto/mosquitto.conf *
# Place your local configuration in /etc/mosquitto/conf.d/
#
# A full description of the configuration file is at
# /usr/share/doc/mosquitto/examples/mosquitto.conf.example

pid_file /run/mosquitto/mosquitto.pid

#persistence true
#persistence_location /var/lib/mosquitto/

log_dest file /var/log/mosquitto/mosquitto.log

include_dir /etc/mosquitto/conf.d

*/etc/mosquitto/conf.d/myconfig.conf *
persistence false

allow_anonymous true
password_file /etc/mosquitto/passwd

acl_file /etc/mosquitto/acl

# mqtt
listener 1883
protocol mqtt

# websockets
listener 9001
protocol websockets

*/etc/mosquitto/acl*
# Allow anonymous access to the sys
topic read $SYS/#

# Allow anonymous to read weather
topic read weather/#

# weewx readwrite to the loop
user teffi
topic weather/#

*MQTT in WeeWX:*
[StdRESTful]
[[MQTT]]

# Enable/disable this service
enable = true

# Hostname/IP of MQTT broker
host = 192.168.178.190
server_url = mqtt://teffi:@localhost:1883/

# Credentials
user = teffi
password = 

# Prefix for topics
topic = weather
unit_system = METRIC
binding = archive,loop
aggregation = aggregate

*checking if WeeWX serves mosquitto with info:*
*mosquitto_sub -h 192.168.178.190 -t weather/#*
online
online
1690198935
24.6
23.9
53
54
993.7
993.7
11377.0
8.9
0
0.0
0.0
0.0
0.0
0.3
1.46
1.46
294
6.480016105981334
9.360023264195261
7.1
0
4
89.7947908445146
997.3266279778212
23.910163208269463
997.1205287280834
1262.3292207924262
14.015863559854884
23.75
27.2746765106266
14.37423758808152
859.4544718145543
23.9
16

*Belchertown skin receiving MQTT topic /weather/#*
[StdReport]
[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true

[[[Extras]]]
#--- MQTT Websockets (for Real Time Streaming) Options ---
#log_failure = True 
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.178.190
mqtt_websockets_port = 9001
mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/loop
mqtt_websockets_username = teffi
mqtt_websockets_password = 
disconnect_live_website_visitor = 180

*Checking if it works in webpage:*
*http://localhost/weewx/belchertown/* or weewxhi.de

Connected. Waiting for data. Last Updated July 24, 2023, 1:20:00 PM

The webpage never receives data.


*mosquitto.log shows connections:*
*sudo more /var/log/mosquitto/mosquitto.log *

1690197817: mosquitto version 2.0.11 starting
1690197817: Config loaded from /etc/mosquitto/mosquitto.conf.
1690197817: Opening ipv4 listen socket on port 1883.
1690197817: Opening ipv6 listen socket on port 1883.
1690197817: Opening websockets listen socket on port 9001.
1690197817: mosquitto version 2.0.11 running
1690197822: New connection from 192.168.178.190:36367 on port 1883.
1690197822: New client connected from 192.168.178.190:36367 as 
weewx_e353ae0d (p2, c1, k60, u'teffi').
1690197840: New client connected from :::192.168.178.190:59900 as 
website819759641 (p2, c1, k60, u'teffi').
1690197884: Client website819759641 closed its connection.
1690197884: Client  closed its connection.
1690197886: New client connected from :::192.168.178.190:52896 as 
website398593267 (p2, c1, k60, u'teffi').
1690198918: New connection from 192.168.178.190:36078 on port 1883.
1690198918: New client connected from 192.168.178.190:36078 as 
auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA (p2, c1, k60).
1690198939: Client auto-C1ABF6AD-7B82-CBED-2BB0-5DECA756C1BA disconnected.
1690199057: New client connected from :::192.168.178.64:57281 as 
website924402803 (p2, c1, k60, u'teffi').
On Sunday, July 23, 2023 at 4:01:07 PM UTC+2 Claudio wrote:

> this is my config, 
> no ssl / read user = all
>
> Belchertown skin.conf
>
>
>  # MQTT Websockets defaults
>
> mqtt_websockets_enabled = 1
>
> mqtt_websockets_host = public IP (no local IP)
>
> mqtt_websockets_port = 9001
>
> mqtt_websockets_ssl = 0
>
> mqtt_websockets_topic = weather/loop
>
> mqtt_websockets_username = ""
>
> mqtt_websockets_password = ""
>
> disconnect_live_website_visitor = 180
>
> weewx weewx.conf
&g

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

Thank you! It works for me, too :)

Cheers,
Stefan

On Sat, Jul 22, 2023 at 4:18 PM Karen K  wrote:

> I applied a little fix. Please try.
>
> Stefan Gliessmann schrieb am Samstag, 22. Juli 2023 um 10:42:45 UTC+2:
>
>> Thank you for looking into it 🙏
>>
>> On Fri, Jul 21, 2023 at 5:44 PM Karen K  wrote:
>>
>>> I see.
>>>
>>> I tried it myself and I got the same result. This will take some time to
>>> check.
>>>
>>> Stefan Gliessmann schrieb am Freitag, 21. Juli 2023 um 15:22:37 UTC+2:
>>>
>>>> You wrote:
>>>> "For including messages originating from DWD you need to add
>>>> --include-dwd. Otherwise message from other sources are included only."
>>>>
>>>> How does this relate to *bbk-warnings mowas --weewx?*
>>>> Despite there are warnings, bbk-mowas.inc shows that there aren't any
>>>> ...
>>>>
>>>> *more /etc/weewx/skins/Belchertown/dwd/bbk-mowas.inc zur Zeit keine
>>>> WarnungenZuletzt beim BBK abgerufen am
>>>> 21.07.2023 15:16*
>>>>
>>>>
>>>> teffi@weewx:~/Downloads$ *sudo bbk-warnings mowas --weewx*
>>>>
>>>> Using configuration file /etc/weewx/weewx.conf
>>>> INFO successfully downloaded
>>>> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
>>>> INFO successfully downloaded
>>>> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
>>>> -- get_warnings ---
>>>> ++ dashboard data ++
>>>> INFO successfully downloaded
>>>> https://warnung.bund.de/api31/mowas/mapData.json
>>>> INFO Regionalschlüssel ARS mowas, 12 Einträge
>>>>
>>>> INFO Warn ID: mow.DE-NW-EU-SE091-20210823-109-000
>>>> INFO {'id': 'mow.DE-NW-EU-SE091-20210823-109-000', 'version': 1,
>>>> 'startDate': '2021-11-09T15:17:17+01:00', 'severity': 'Minor', 'type':
>>>> 'Update', 'i18nTitle': {'de': '+++ Betretungsverbot Bergschadensgebiet
>>>> Stadt Mechernich +++'}, 'transKeys': {'event': 'BBK-EVC-059'}}
>>>> INFO Warn ID: mow.DE-BY-ED-W186-20230717-000
>>>> INFO {'id': 'mow.DE-BY-ED-W186-20230717-000', 'version': 5,
>>>> 'startDate': '2023-07-17T15:22:30+02:00', 'severity': 'Minor', 'type':
>>>> 'Alert', 'i18nTitle': {'de': 'Verunreinigung des Trinkwassers mit Keimen in
>>>> der Stadt Moosburg a.d. Isar - Stadt Moosburg; Thonstetten;
>>>> Grünseiboldsdorf; Ober-Niederhummel'}, 'transKeys': {'event':
>>>> 'BBK-EVC-069'}}
>>>> INFO Warn ID: mow.DE-SH-KI-SE099-20230719-99-000
>>>> INFO {'id': 'mow.DE-SH-KI-SE099-20230719-99-000', 'version': 5,
>>>> 'startDate': '2023-07-19T13:23:13+02:00', 'severity': 'Minor', 'type':
>>>> 'Alert', 'i18nTitle': {'de': 'Kampfmittelentschärfung im Kieler Stadtgebiet
>>>> - Kiel-Ellerbek und Kiel-Gaarden-Ost'}, 'transKeys': {'event':
>>>> 'BBK-EVC-009'}}
>>>> INFO Warn ID: mow.DE-BB-BRB-SE081-20230720-81-000
>>>> INFO {'id': 'mow.DE-BB-BRB-SE081-20230720-81-000', 'version': 5,
>>>> 'startDate': '2023-07-20T04:26:44+02:00', 'severity': 'Minor', 'type':
>>>> 'Update', 'i18nTitle': {'de': 'Warnung vor freilaufender Raubkatze -
>>>> Kleinmachnow,Stahnsdorf, Teltow'}, 'transKeys': {'event': 'BBK-EVC-078'}}
>>>> INFO Warn ID: mow.DE-BB-BRB-SE081-20230721-81-000
>>>> INFO {'id': 'mow.DE-BB-BRB-SE081-20230721-81-000', 'version': 5,
>>>> 'startDate': '2023-07-21T04:14:57+02:00', 'severity': 'Minor', 'type':
>>>> 'Alert', 'i18nTitle': {'de': 'Brand Reifenstapel mit starker schwarzer
>>>> Rauchentwicklung - Gem. Großbeeren, Blankenfelde-Mahlow, Rangsdorf,
>>>> Ludwigsfelde, Berlin Süden'}, 'transKeys': {'event': 'BBK-EVC-030'}}
>>>&g

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

Thank you for looking into it 🙏

On Fri, Jul 21, 2023 at 5:44 PM Karen K  wrote:

> I see.
>
> I tried it myself and I got the same result. This will take some time to
> check.
>
> Stefan Gliessmann schrieb am Freitag, 21. Juli 2023 um 15:22:37 UTC+2:
>
>> You wrote:
>> "For including messages originating from DWD you need to add
>> --include-dwd. Otherwise message from other sources are included only."
>>
>> How does this relate to *bbk-warnings mowas --weewx?*
>> Despite there are warnings, bbk-mowas.inc shows that there aren't any ...
>>
>> *more /etc/weewx/skins/Belchertown/dwd/bbk-mowas.inc zur Zeit keine
>> WarnungenZuletzt beim BBK abgerufen am
>> 21.07.2023 15:16*
>>
>>
>> teffi@weewx:~/Downloads$ *sudo bbk-warnings mowas --weewx*
>>
>> Using configuration file /etc/weewx/weewx.conf
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
>> -- get_warnings ---
>> ++ dashboard data ++
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/mowas/mapData.json
>> INFO Regionalschlüssel ARS mowas, 12 Einträge
>>
>> INFO Warn ID: mow.DE-NW-EU-SE091-20210823-109-000
>> INFO {'id': 'mow.DE-NW-EU-SE091-20210823-109-000', 'version': 1,
>> 'startDate': '2021-11-09T15:17:17+01:00', 'severity': 'Minor', 'type':
>> 'Update', 'i18nTitle': {'de': '+++ Betretungsverbot Bergschadensgebiet
>> Stadt Mechernich +++'}, 'transKeys': {'event': 'BBK-EVC-059'}}
>> INFO Warn ID: mow.DE-BY-ED-W186-20230717-000
>> INFO {'id': 'mow.DE-BY-ED-W186-20230717-000', 'version': 5, 'startDate':
>> '2023-07-17T15:22:30+02:00', 'severity': 'Minor', 'type': 'Alert',
>> 'i18nTitle': {'de': 'Verunreinigung des Trinkwassers mit Keimen in der
>> Stadt Moosburg a.d. Isar - Stadt Moosburg; Thonstetten; Grünseiboldsdorf;
>> Ober-Niederhummel'}, 'transKeys': {'event': 'BBK-EVC-069'}}
>> INFO Warn ID: mow.DE-SH-KI-SE099-20230719-99-000
>> INFO {'id': 'mow.DE-SH-KI-SE099-20230719-99-000', 'version': 5,
>> 'startDate': '2023-07-19T13:23:13+02:00', 'severity': 'Minor', 'type':
>> 'Alert', 'i18nTitle': {'de': 'Kampfmittelentschärfung im Kieler Stadtgebiet
>> - Kiel-Ellerbek und Kiel-Gaarden-Ost'}, 'transKeys': {'event':
>> 'BBK-EVC-009'}}
>> INFO Warn ID: mow.DE-BB-BRB-SE081-20230720-81-000
>> INFO {'id': 'mow.DE-BB-BRB-SE081-20230720-81-000', 'version': 5,
>> 'startDate': '2023-07-20T04:26:44+02:00', 'severity': 'Minor', 'type':
>> 'Update', 'i18nTitle': {'de': 'Warnung vor freilaufender Raubkatze -
>> Kleinmachnow,Stahnsdorf, Teltow'}, 'transKeys': {'event': 'BBK-EVC-078'}}
>> INFO Warn ID: mow.DE-BB-BRB-SE081-20230721-81-000
>> INFO {'id': 'mow.DE-BB-BRB-SE081-20230721-81-000', 'version': 5,
>> 'startDate': '2023-07-21T04:14:57+02:00', 'severity': 'Minor', 'type':
>> 'Alert', 'i18nTitle': {'de': 'Brand Reifenstapel mit starker schwarzer
>> Rauchentwicklung - Gem. Großbeeren, Blankenfelde-Mahlow, Rangsdorf,
>> Ludwigsfelde, Berlin Süden'}, 'transKeys': {'event': 'BBK-EVC-030'}}
>> INFO Warn ID: mow.DE-BW-LB-W026-20230721-000
>> INFO {'id': 'mow.DE-BW-LB-W026-20230721-000', 'version': 5, 'startDate':
>> '2023-07-21T11:22:36+02:00', 'severity': 'Minor', 'type': 'Update',
>> 'i18nTitle': {'de': 'Abkochgebot Trinkwasser in Mundelsheim -
>> Mundelsheim'}, 'transKeys': {'event': 'BBK-EVC-069'}}
>> INFO Warn ID: mow.DE-SL-SB-SE035-20230721-35-000
>> INFO {'id': 'mow.DE-SL-SB-SE035-20230721-35-000', 'version': 5,
>> 'startDate': '2023-07-21T11:39:19+02:00', 'severity': 'Minor', 'type'

[weewx-user] MQTT / Belchertown / Connected. Waiting for data.

[Stefan Gliessmann]

I am struggling to understand why the Belchertown skin is not receiving 
weather data even though it is connected to the MQTT broker and user.mqtt 
is publishing weather data.

TIA,
Stefan

Here is what I have configured in /etc/weewx/weewx.conf:

[StdRESTful]

[[MQTT]]

# Enable/disable this service
enable = true

# Hostname/IP of MQTT broker
host = 192.168.178.190
server_url = mqtt://teffi:@192.168.178.190:1883/

# Credentials
user = teffi
password = 

# Prefix for topics
topic = weather/weewx
unit_system = METRIC
binding = archive,loop
aggregation = aggregate
[[[inputs]]]
rainRate
units = mm_per_hour
rain
units = mm
hourRain
units = mm
rain24
units = mm
dayRain
units = mm
ET
units = mm
dayET
units = mm
ET24
units = mm

[StdReport]
[[Belchertown]]
skin = Belchertown
HTML_ROOT = /var/www/html/weewx/belchertown
enable = true

[[[Extras]]]
#--- MQTT Websockets (for Real Time Streaming) Options ---
log_failure = True
mqtt_websockets_enabled = 1
mqtt_websockets_host = 192.168.178.190
mqtt_websockets_port = 9001
#mqtt_websockets_ssl = 0
mqtt_websockets_topic = weather/weewx
# disconnect_live_website_visitor = 180

and in /var/log/syslog I can see:
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/dateTime_unix_epoch": 1689946202 (unix_epoch)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/inTemp_degree_C": 23.297 (degree_C)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/outTemp_degree_C": 19.098 (degree_C)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/inHumidity_percent": 51 (percent)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/outHumidity_percent": 61 (percent)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/pressure_mbar": 1001.4 (mbar)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/relbarometer": 1001.4 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/luminosity": 29620.0 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/uvradiation": 67.8 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/UV_uv_index": 2 (uv_index)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/rain_cm": 0.0 (cm)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/stormRain_cm": 0.0 (cm)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/rainRate_cm_per_hour": 0.0 (cm_per_hour)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/dayRain_cm": 0.0 (cm)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/weekRain": 11.7 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/monthRain_cm": 1.4304 (cm)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/yearRain_cm": 1.4304 (cm)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/windDir_degree_compass": 186 (degree_compass)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/windSpeed_km_per_hour": 0.0 (km_per_hour)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/windGust_km_per_hour": 0.0 (km_per_hour)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/daymaxwind": 8.7 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/wh65_batt": 0 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/wh65_sig": 4 (None)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/radiation_watt_per_meter_squared": 233.78058405682714 
(watt_per_meter_squared)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/altimeter_mbar": 1005.049695199262 (mbar)
Jul 21 15:30:02 weewx weewx[37286] DEBUG user.mqtt: Publishing 
"weather/weewx/appTemp_degree_C": 19.53993189168407 (degree_C)
Jul 21 15:30:02 weewx weewx[37286] 

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

5, 'startDate': 
'2023-07-21T12:39:32+02:00', 'severity': 'Minor', 'type': 'Update', 
'i18nTitle': {'de': 'Trinkwasserverunreinigung in Niederstetten - 
Niederstetten (nur Kernstadt)'}, 'transKeys': {'event': 'BBK-EVC-069'}}
INFO Warn ID: mow.DE-NI-GF-W216-20230721-000
INFO {'id': 'mow.DE-NI-GF-W216-20230721-000', 'version': 5, 'startDate': 
'2023-07-21T12:41:23+02:00', 'severity': 'Minor', 'type': 'Update', 
'i18nTitle': {'de': 'Verunreinigung des Trinkwassers in Teilen des 
Landkreises Gifhorn mit E. Coli Keim - Landkreis Gifhorn'}, 'transKeys': 
{'event': 'BBK-EVC-069'}}
INFO Warn ID: mow.DE-SH-OD-SE105-20230721-105-000
INFO {'id': 'mow.DE-SH-OD-SE105-20230721-105-000', 'version': 5, 
'startDate': '2023-07-21T14:15:36+02:00', 'severity': 'Severe', 'type': 
'Alert', 'i18nTitle': {'de': 'Feuerwehreinsatz - Bargteheide'}, 
'transKeys': {'event': 'BBK-EVC-027'}}
INFO Warn ID: mow.DE-BR-B-SE017-20230721-17-000
INFO {'id': 'mow.DE-BR-B-SE017-20230721-17-000', 'version': 5, 'startDate': 
'2023-07-21T14:32:27+02:00', 'expiresDate': '2023-07-21T20:32:27+02:00', 
'severity': 'Minor', 'type': 'Cancel', 'i18nTitle': {'de': 'Entwarnung: 
Warnung vor einem freilaufenden gefährlichen Wildtier. - Bereich der 
südliche Landesgrenze Berlins'}, 'transKeys': {'event': 'BBK-EVC-078'}}
BBK.warnings() areas ['mow.DE-NW-EU-SE091-20210823-109-000', 
'mow.DE-BY-ED-W186-20230717-000', 'mow.DE-SH-KI-SE099-20230719-99-000', 
'mow.DE-BB-BRB-SE081-20230720-81-000', 
'mow.DE-BB-BRB-SE081-20230721-81-000', 'mow.DE-BW-LB-W026-20230721-000', 
'mow.DE-SL-SB-SE035-20230721-35-000', 'mow.DE-MV-SN-SE049-20230721-49-000', 
'mow.DE-BW-TBB-W028-20230721-001', 'mow.DE-NI-GF-W216-20230721-000', 
'mow.DE-SH-OD-SE105-20230721-105-000', 'mow.DE-BR-B-SE017-20230721-17-000']
BBK.warnings() areas[] mow.DE-NW-EU-SE091-20210823-109-000 
['mow.DE-NW-EU-SE091-20210823-109-000']
BBK.warnings() areas[] mow.DE-BY-ED-W186-20230717-000 
['mow.DE-BY-ED-W186-20230717-000']
BBK.warnings() areas[] mow.DE-SH-KI-SE099-20230719-99-000 
['mow.DE-SH-KI-SE099-20230719-99-000']
BBK.warnings() areas[] mow.DE-BB-BRB-SE081-20230720-81-000 
['mow.DE-BB-BRB-SE081-20230720-81-000']
BBK.warnings() areas[] mow.DE-BB-BRB-SE081-20230721-81-000 
['mow.DE-BB-BRB-SE081-20230721-81-000']
BBK.warnings() areas[] mow.DE-BW-LB-W026-20230721-000 
['mow.DE-BW-LB-W026-20230721-000']
BBK.warnings() areas[] mow.DE-SL-SB-SE035-20230721-35-000 
['mow.DE-SL-SB-SE035-20230721-35-000']
BBK.warnings() areas[] mow.DE-MV-SN-SE049-20230721-49-000 
['mow.DE-MV-SN-SE049-20230721-49-000']
BBK.warnings() areas[] mow.DE-BW-TBB-W028-20230721-001 
['mow.DE-BW-TBB-W028-20230721-001']
BBK.warnings() areas[] mow.DE-NI-GF-W216-20230721-000 
['mow.DE-NI-GF-W216-20230721-000']
BBK.warnings() areas[] mow.DE-SH-OD-SE105-20230721-105-000 
['mow.DE-SH-OD-SE105-20230721-105-000']
BBK.warnings() areas[] mow.DE-BR-B-SE017-20230721-17-000 
['mow.DE-BR-B-SE017-20230721-17-000']
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-NW-EU-SE091-20210823-109-000.json
BBK.warnings() get_warning( mow.DE-NW-EU-SE091-20210823-109-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BY-ED-W186-20230717-000.json
BBK.warnings() get_warning( mow.DE-BY-ED-W186-20230717-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-SH-KI-SE099-20230719-99-000.json
BBK.warnings() get_warning( mow.DE-SH-KI-SE099-20230719-99-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BB-BRB-SE081-20230720-81-000.json
BBK.warnings() get_warning( mow.DE-BB-BRB-SE081-20230720-81-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BB-BRB-SE081-20230721-81-000.json
BBK.warnings() get_warning( mow.DE-BB-BRB-SE081-20230721-81-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BW-LB-W026-20230721-000.json
BBK.warnings() get_warning( mow.DE-BW-LB-W026-20230721-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-SL-SB-SE035-20230721-35-000.json
BBK.warnings() get_warning( mow.DE-SL-SB-SE035-20230721-35-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-MV-SN-SE049-20230721-49-000.json
BBK.warnings() get_warning( mow.DE-MV-SN-SE049-20230721-49-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BW-TBB-W028-20230721-001.json
BBK.warnings() get_warning( mow.DE-BW-TBB-W028-20230721-001 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-NI-GF-W216-20230721-000.json
BBK.warnings() get_warning( mow.DE-NI-GF-W216-20230721-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-SH-OD-SE105-20230721-105-000.json
BBK.warnings() get_warning( mow.DE-SH-OD-SE105-20230721-105-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BR-B-SE017-20230721-17-000.json
BBK.warnings() get_warning( mow.DE-BR-B-SE017-20230721-17-000 )
teffi@weewx:~/Downloads$ 
*more /etc/weewx/skins/Belchertown/dwd/bbk-mowas.inc zur Zeit keine 
WarnungenZuletzt beim BBK abgerufen am 
21.07.2023 15:16*
On Thursday, July 20, 2023 at 8:35:11 AM UTC+2 Karen K wrote:

> Stefan Gliessmann schrieb am Mittwoch, 19. Juli 2023 um 17:52:24 UTC+2:
>
> Maybe this explains my confusion a bit better.
>
> I run the bbk-warning comand for mowas as shown below.
> Messages are getting loaded from warnung.bund.de.
> However the related file bbk-mowas.inc states that there aren't any 
> warnings.
> I expected that if the option "mowas" is used instead of an ARS, all 
> warnings would be included in the bbk-mowas.inc file.
>
> Is this expectation correct?
>
> Do I need to configure something additionally?
>
>
> For including messages originating from DWD you need to add --include-dwd. 
> Otherwise message from other sources are included only. 
>  
>

-- 
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/25e40927-17e4-47d4-9cea-33d5293a2cd0n%40googlegroups.com.

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

Maybe this explains my confusion a bit better.

I run the bbk-warning comand for mowas as shown below.
Messages are getting loaded from warnung.bund.de.
However the related file bbk-mowas.inc states that there aren't any 
warnings.
I expected that if the option "mowas" is used instead of an ARS, all 
warnings would be included in the bbk-mowas.inc file.

Is this expectation correct?

Do I need to configure something additionally?

I do really appreciate your help on this topic! 
Thank you in advance,
Stefan


teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ *sudo bbk-warnings mowas 
--weewx*
Using configuration file /etc/weewx/weewx.conf
INFO successfully downloaded 
https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
INFO successfully downloaded 
https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
-- get_warnings ---
++ dashboard data ++
INFO successfully downloaded 
https://warnung.bund.de/api31/mowas/mapData.json
INFO Regionalschlüssel ARS mowas, 9 Einträge
INFO Warn ID: mow.DE-NW-EU-SE091-20210823-109-000
INFO {'id': 'mow.DE-NW-EU-SE091-20210823-109-000', 'version': 1, 
'startDate': '2021-11-09T15:17:17+01:00', 'severity': 'Minor', 'type': 
'Update', 'i18nTitle': {'de': '+++ Betretungsverbot Bergschadensgebiet 
Stadt Mechernich +++'}, 'transKeys': {'event': 'BBK-EVC-059'}}
INFO Warn ID: mow.DE-HE-FB-W193-20230714-002
INFO {'id': 'mow.DE-HE-FB-W193-20230714-002', 'version': 5, 'startDate': 
'2023-07-14T15:08:50+02:00', 'severity': 'Minor', 'type': 'Update', 
'i18nTitle': {'de': 'Explosionsgefahr Stadtwald Butzbach - Stadtwald 
Butzbach'}, 'transKeys': {'event': 'BBK-EVC-077'}}
INFO Warn ID: mow.DE-BW-LB-W026-20230714-000
INFO {'id': 'mow.DE-BW-LB-W026-20230714-000', 'version': 5, 'startDate': 
'2023-07-14T16:59:18+02:00', 'severity': 'Minor', 'type': 'Alert', 
'i18nTitle': {'de': 'Abkochgebot Trinkwasser in Mundelsheim - Mundelsheim 
gesamtes Ortsgebiet'}, 'transKeys': {'event': 'BBK-EVC-069'}}
INFO Warn ID: mow.DE-BY-ED-W186-20230717-000
INFO {'id': 'mow.DE-BY-ED-W186-20230717-000', 'version': 5, 'startDate': 
'2023-07-17T15:22:30+02:00', 'severity': 'Minor', 'type': 'Alert', 
'i18nTitle': {'de': 'Verunreinigung des Trinkwassers mit Keimen in der 
Stadt Moosburg a.d. Isar - Stadt Moosburg; Thonstetten; Grünseiboldsdorf; 
Ober-Niederhummel'}, 'transKeys': {'event': 'BBK-EVC-069'}}
INFO Warn ID: mow.DE-SH-KI-SE099-20230719-99-000
INFO {'id': 'mow.DE-SH-KI-SE099-20230719-99-000', 'version': 5, 
'startDate': '2023-07-19T13:23:13+02:00', 'severity': 'Minor', 'type': 
'Alert', 'i18nTitle': {'de': 'Kampfmittelentschärfung im Kieler Stadtgebiet 
- Kiel-Ellerbek und Kiel-Gaarden-Ost'}, 'transKeys': {'event': 
'BBK-EVC-009'}}
INFO Warn ID: mow.DE-BY-LA-W144-20230719-000
INFO {'id': 'mow.DE-BY-LA-W144-20230719-000', 'version': 5, 'startDate': 
'2023-07-19T14:36:29+02:00', 'expiresDate': '2023-07-19T20:36:29+02:00', 
'severity': 'Minor', 'type': 'Cancel', 'i18nTitle': {'de': 'Entwarnung: 
Bakterielle Verkeimung im Trinkwasser in einzelnen Ortsteilen von Neus - 
Neustadt a.d. Donau - Ortsteile Arresting, Hienheim, Irnsing und 
Marching'}, 'transKeys': {'event': 'BBK-EVC-069'}}
INFO Warn ID: mow.DE-BW-HD-W086-20230719-001
INFO {'id': 'mow.DE-BW-HD-W086-20230719-001', 'version': 5, 'startDate': 
'2023-07-19T15:46:23+02:00', 'expiresDate': '2023-07-19T21:46:23+02:00', 
'severity': 'Minor', 'type': 'Cancel', 'i18nTitle': {'de': 'Entwarnung: 
Stromausfall in Eberbach (Stadtmitte + Nord) - Eberbach 
(Rhein-Neckar-Kreis)'}, 'transKeys': {'event': 'BBK-EVC-063'}}
INFO Warn ID: mow.DE-BW-RT-SE050-20230719-50-000
INFO {'id': 'mow.DE-BW-RT-SE050-20230719-50-000', 'version': 5, 
'startDate': '2023-07-19T17:16:13+02:00', 'severity': 'Minor', 'type': 
'Alert', 'i18

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

7;Official WARNING of HEAVY THUNDERSTORMS', 'es': 'AVISO oficial de TORMENTA 
FUERTE', 'fr': 'ALERTE officielle INTEMPÉRIES PRONONCÉES pour FORTS 
ORAGES'}}
BBK.warnings() areas 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168976782.3464be94-05f9-4c04-a628-ea9d41c9ed6a.MUL',
 
'dwdmap.2.49.0.0.276.0.DWD.PVW.168976938.5290e8e2-bd40-47fd-85f1-e33429a9636e.MUL',
 
'dwdmap.2.49.0.0.276.0.DWD.PVW.168977046.86b27fa8-155b-4003-839d-33d2bf2caa63.MUL',
 
'dwdmap.2.49.0.0.276.0.DWD.PVW.168977088.5319aa3e-f134-42c5-90f9-6cf98fb52ae7.MUL',
 
'dwdmap.2.49.0.0.276.0.DWD.PVW.168977112.540c5865-d4f3-460d-a63d-1dd9a4058900.MUL']
BBK.warnings() areas[] 
dwdmap.2.49.0.0.276.0.DWD.PVW.168976782.3464be94-05f9-4c04-a628-ea9d41c9ed6a.MUL
 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168976782.3464be94-05f9-4c04-a628-ea9d41c9ed6a.MUL']
BBK.warnings() areas[] 
dwdmap.2.49.0.0.276.0.DWD.PVW.168976938.5290e8e2-bd40-47fd-85f1-e33429a9636e.MUL
 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168976938.5290e8e2-bd40-47fd-85f1-e33429a9636e.MUL']
BBK.warnings() areas[] 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977046.86b27fa8-155b-4003-839d-33d2bf2caa63.MUL
 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168977046.86b27fa8-155b-4003-839d-33d2bf2caa63.MUL']
BBK.warnings() areas[] 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977088.5319aa3e-f134-42c5-90f9-6cf98fb52ae7.MUL
 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168977088.5319aa3e-f134-42c5-90f9-6cf98fb52ae7.MUL']
BBK.warnings() areas[] 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977112.540c5865-d4f3-460d-a63d-1dd9a4058900.MUL
 
['dwdmap.2.49.0.0.276.0.DWD.PVW.168977112.540c5865-d4f3-460d-a63d-1dd9a4058900.MUL']
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168976782.3464be94-05f9-4c04-a628-ea9d41c9ed6a.MUL.json
BBK.warnings() get_warning( 
dwdmap.2.49.0.0.276.0.DWD.PVW.168976782.3464be94-05f9-4c04-a628-ea9d41c9ed6a.MUL
 
)
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168976938.5290e8e2-bd40-47fd-85f1-e33429a9636e.MUL.json
BBK.warnings() get_warning( 
dwdmap.2.49.0.0.276.0.DWD.PVW.168976938.5290e8e2-bd40-47fd-85f1-e33429a9636e.MUL
 
)
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168977046.86b27fa8-155b-4003-839d-33d2bf2caa63.MUL.json
BBK.warnings() get_warning( 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977046.86b27fa8-155b-4003-839d-33d2bf2caa63.MUL
 
)
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168977088.5319aa3e-f134-42c5-90f9-6cf98fb52ae7.MUL.json
BBK.warnings() get_warning( 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977088.5319aa3e-f134-42c5-90f9-6cf98fb52ae7.MUL
 
)
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168977112.540c5865-d4f3-460d-a63d-1dd9a4058900.MUL.json
BBK.warnings() get_warning( 
dwdmap.2.49.0.0.276.0.DWD.PVW.168977112.540c5865-d4f3-460d-a63d-1dd9a4058900.MUL
 
)

-- HTML -- bbk-dwd.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 19.07.2023 14:54

-- JSON -- bbk-dwd.json -
[]

On Wednesday, July 19, 2023 at 2:41:08 PM UTC+2 Stefan Gliessmann wrote:

> Thank you for your reply and the hint for --include-dwd. :)
>
> Do you have an explanation why 
>
> sudo bbk-warnings mowas --weewx --dry-run
>
>
> downloads MoWas messages, but the bbl-mowas.inc file says:
>
> -- HTML -- bbk-mowas.inc --
>
> zur Zeit keine WarnungenZuletzt beim BBK 
> abgerufen am 18.07.2023 18:03
>
> This is actually the issue. the command downloads current warnings, but it 
> does not generate the content of the *.inc files correctly.
>
>
> On Wed, Jul 19, 2023 at 2:25 PM Karen K  wrote:
>
>> To prevent weather warnings from being downloaded twice if you use both 
>> dwd-cap-warnings and bbk-warnings, you need an additional parameter for 
>> bbk-warnings to get weather warnings: --include-dwd. See README 
>> <https://github.com/roe-dl/weewx-DWD#bbk-warnings>. I hope this answers 
>> your question.
>>
>> Um zu vermeiden, daß man dieselbe Meldung doppelt erhält, wenn man sowohl 
>> dwd-cap-warnings als auch bbk-warnings benutzt, werden Wettermeldungen bei 
>> bbk-warnings nur dann einbezogen, wenn man zusätzlich den Parameter 
>> --include-dwd angibt. Das ist in der README 
>> <https://github.com/roe-dl/weewx-DWD#bbk-warnings> beschrieben. Ich 
>> hoffe, daß das der Punkt war.
>>
>>
>> Stefan Gliessmann schrieb am Dienstag, 18. Juli 2023 um 18:17:59 UTC+2:
>>
>>> for BiWapp it works ...
&g

Re: [weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

Thank you for your reply and the hint for --include-dwd. :)

Do you have an explanation why

sudo bbk-warnings mowas --weewx --dry-run


downloads MoWas messages, but the bbl-mowas.inc file says:

-- HTML -- bbk-mowas.inc --

zur Zeit keine WarnungenZuletzt beim BBK
abgerufen am 18.07.2023 18:03

This is actually the issue. the command downloads current warnings, but it
does not generate the content of the *.inc files correctly.


On Wed, Jul 19, 2023 at 2:25 PM Karen K  wrote:

> To prevent weather warnings from being downloaded twice if you use both
> dwd-cap-warnings and bbk-warnings, you need an additional parameter for
> bbk-warnings to get weather warnings: --include-dwd. See README
> <https://github.com/roe-dl/weewx-DWD#bbk-warnings>. I hope this answers
> your question.
>
> Um zu vermeiden, daß man dieselbe Meldung doppelt erhält, wenn man sowohl
> dwd-cap-warnings als auch bbk-warnings benutzt, werden Wettermeldungen bei
> bbk-warnings nur dann einbezogen, wenn man zusätzlich den Parameter
> --include-dwd angibt. Das ist in der README
> <https://github.com/roe-dl/weewx-DWD#bbk-warnings> beschrieben. Ich
> hoffe, daß das der Punkt war.
>
>
> Stefan Gliessmann schrieb am Dienstag, 18. Juli 2023 um 18:17:59 UTC+2:
>
>> for BiWapp it works ...
>>
>> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ sudo bbk-warnings biwapp
>> --weewx --dry-run
>>
>> Using configuration file /etc/weewx/weewx.conf
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
>> -- get_warnings ---
>> ++ dashboard data ++
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/biwapp/mapData.json
>> INFO Regionalschlüssel ARS biwapp, 1 Einträge
>> INFO Warn ID: biw.BIWAPP-76845
>> INFO {'id': 'biw.BIWAPP-76845', 'version': 5, 'startDate':
>> '2023-07-12T17:46:26+02:00', 'expiresDate': '2023-07-31T17:34:00+02:00',
>> 'severity': 'Minor', 'type': 'Update', 'i18nTitle': {'de': 'Gefahren durch
>> Gewitterschäden in den Wäldern um Sulz a.N., besonders Glatt und
>> Dürrenmettstetten'}}
>> BBK.warnings() areas ['biw.BIWAPP-76845']
>> BBK.warnings() areas[] biw.BIWAPP-76845 ['biw.BIWAPP-76845']
>> INFO successfully downloaded
>> https://warnung.bund.de/api31/warnings/biw.BIWAPP-76845.json
>> BBK.warnings() get_warning( biw.BIWAPP-76845 )
>> 
>> -- HTML -- bbk-biwapp.inc --
>> Sulz am Neckar
>> 
>> https://warnung.bund.de/assets/icons/report_mowas.svg"; alt="8"/>
>> Gefahren durch
>> Gewitterschäden in den Wäldern um Sulz a.N., besonders Glatt und
>> Dürrenmettstetten
>> gültig vom 12.07. 17:46 bis 31.07. 17:34
>> 
>> In der Nacht auf Mittwoch 12.07.2023 sind teils schwere Gewitter über
>> Baden-Württemberg hinweggezogen. In den Wäldern rund um Sulz am Neckar
>> wurden viele Bäume entwurzelt und abgerissen, v.a. die Waldbereiche um
>> Dürrenmettstetten und Glatt sind besonders betroffen. Teilweise wurden
>> Bäume nur angeschoben und stehen nun sehr unsicher schräg im Wald. Diese
>> können unvermittelt und ohne erkennbare Vorwarnung zu Boden fallen.
>> Außerdem hängen in vielen Bäumen noch lose, vom Sturm abgerissene Äste.
>> Auch diese können bei weiteren Windbewegungen unkontrolliert zu Boden
>> fallen.Das Forstamt warnt ausdrücklich vor diesen Waldgefahren nach
>> Gewitterstürmen.Das Forstamt bittet die Waldbesucher daher, den
>> Wald rund um Sulz am Neckar vorerst zu meiden. Sperrungen von Waldstraßen
>> müssen unbedingt beachtet werden!Die Forstpartie hat bereits mit den
>> Aufräumarbeiten begonnen. Da die betroffenen Waldflächen sehr groß sind und
>> die Aufräumarbeiten mit großer Vorsicht durchgeführt werden müssen, werden
>> die Arbeiten voraussichtlich zwei Wochen andauern. Wir bitten die
>> Waldbesucher hierfür um Verständnis.Rottweil, 12.07.2023gez.
>> Strasdeit, Gebietsleitung Schwarzwald-Neckar
>> Quelle: https://warnung.bund.de/api31/appdata/gsb/logos/CAP_at_biwapp.de.png";
>> style="max-height:16px" alt="c...@biwapp.de" /> BIWAPP (c...@biwapp.de)> style="font-size:40%">None – 8  –   2 – leicht
>>  –  ['Safety'] – ['allgemeine Gefahren und
>> öffentliche Sicherheit']  –  biw.BIWAPP-768

[weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

die Aufräumarbeiten mit großer Vorsicht durchgeführt werden müssen, werden 
die Arbeiten voraussichtlich zwei Wochen andauern. Wir bitten die 
Waldbesucher hierfür um Verständnis.Rottweil, 12.07.2023gez. 
Strasdeit, Gebietsleitung Schwarzwald-Neckar",
"event": "8",
"headline": "Gefahren durch Gewitterschäden in den Wäldern um Sulz 
a.N., besonders Glatt und Dürrenmettstetten",
"instruction": "",
"category": [
"Safety"
],
"categoryName": [
"allgemeine Gefahren und öffentliche Sicherheit"
],
"responseType": null,
"urgency": "Unknown",
"severity": "Minor",
"released": 1689176786000,
"start": 1689176786000,
"end": 169081764,
"parameter": {},
"level": 2,
"level_text": "leicht",
"type": null,
"icon": "https://warnung.bund.de/assets/icons/report_mowas.svg";,
"sender_logo": 
"https://warnung.bund.de/api31/appdata/gsb/logos/CAP_at_biwapp.de.png";,
"sender_name": "BIWAPP",
"capwarnings_downloaded": 1689696989.723921
}
]
teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ 



On Tuesday, July 18, 2023 at 6:05:12 PM UTC+2 Stefan Gliessmann wrote:

> Ok - thank you for the hint :)
>
> here is another try with --weewx dwd whole of Germany
>
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ sudo bbk-warnings dwd 
> --weewx --dry-run
> [sudo] password for teffi: 
> Using configuration file /etc/weewx/weewx.conf
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
> -- get_warnings ---
> ++ dashboard data ++
> INFO successfully downloaded 
> https://warnung.bund.de/api31/dwd/mapData.json
> INFO Regionalschlüssel ARS dwd, 1 Einträge
> INFO Warn ID: 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
> INFO {'id': 
> 'dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL',
>  
> 'version': 5, 'startDate': '2023-07-18T10:46:00+02:00', 'expiresDate': 
> '2023-07-19T06:00:00+02:00', 'severity': 'Moderate', 'type': 'Alert', 
> 'i18nTitle': {'de': 'Amtliche WARNUNG vor STURMBÖEN', 'en': 'Official 
> WARNING of GALE-FORCE GUSTS', 'es': 'AVISO oficial de TURBONADA', 'fr': 
> 'ALERTE officielle INTEMPÉRIES PRONONCÉES pour RAFALES DE FORCE FORT COUP 
> DE VENT'}}
> BBK.warnings() areas 
> ['dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL']
> BBK.warnings() areas[] 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
>  
> ['dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL']
> INFO successfully downloaded 
> https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL.json
> BBK.warnings() get_warning( 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
>  
> )
>
> 
> -- HTML -- bbk-dwd.inc --
> zur Zeit keine WarnungenZuletzt beim BBK 
> abgerufen am 18.07.2023 17:59
>
>
> -- JSON -- bbk-dwd.json -
> []
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ 
>
>
> oder auch mit MoWas:
>
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ sudo bbk-warnings mowas 
> --weewx --dry-run
> Using configuration file /etc/weewx/weewx.conf
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
> -- get_warnings ---
> ++ dashboard data ++
> INFO successfully downloaded 
> https://warnung.bund.de/api31/mowas/mapData.json
> INFO Regionalschlüssel ARS mowas, 11 Einträge
> INFO Warn ID: mow.DE-NW-EU-SE091-20210823-109-000
> INFO {'id': 'mow.DE-NW-EU-SE091-20210823-109-000', 'version': 1, 
> 'startDate': '2021-11-09T15:17:17+01:00', 'severity':

[weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

which part of the weewx.conf might be of interest to you?

TIA,
Stefan

P.S.: ich mag Deine/Eure Wetter Homepage sehr ;)


On Tuesday, July 18, 2023 at 6:05:12 PM UTC+2 Stefan Gliessmann wrote:

> Ok - thank you for the hint :)
>
> here is another try with --weewx dwd whole of Germany
>
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ sudo bbk-warnings dwd 
> --weewx --dry-run
> [sudo] password for teffi: 
> Using configuration file /etc/weewx/weewx.conf
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
> -- get_warnings ---
> ++ dashboard data ++
> INFO successfully downloaded 
> https://warnung.bund.de/api31/dwd/mapData.json
> INFO Regionalschlüssel ARS dwd, 1 Einträge
> INFO Warn ID: 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
> INFO {'id': 
> 'dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL',
>  
> 'version': 5, 'startDate': '2023-07-18T10:46:00+02:00', 'expiresDate': 
> '2023-07-19T06:00:00+02:00', 'severity': 'Moderate', 'type': 'Alert', 
> 'i18nTitle': {'de': 'Amtliche WARNUNG vor STURMBÖEN', 'en': 'Official 
> WARNING of GALE-FORCE GUSTS', 'es': 'AVISO oficial de TURBONADA', 'fr': 
> 'ALERTE officielle INTEMPÉRIES PRONONCÉES pour RAFALES DE FORCE FORT COUP 
> DE VENT'}}
> BBK.warnings() areas 
> ['dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL']
> BBK.warnings() areas[] 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
>  
> ['dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL']
> INFO successfully downloaded 
> https://warnung.bund.de/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL.json
> BBK.warnings() get_warning( 
> dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL
>  
> )
>
> 
> -- HTML -- bbk-dwd.inc --
> zur Zeit keine WarnungenZuletzt beim BBK 
> abgerufen am 18.07.2023 17:59
>
>
> -- JSON -- bbk-dwd.json -
> []
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ 
>
>
> oder auch mit MoWas:
>
> teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ sudo bbk-warnings mowas 
> --weewx --dry-run
> Using configuration file /etc/weewx/weewx.conf
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/eventCodes/eventCodes.json
> INFO successfully downloaded 
> https://warnung.bund.de/api31/appdata/gsb/logos/logos.json
> -- get_warnings ---
> ++ dashboard data ++
> INFO successfully downloaded 
> https://warnung.bund.de/api31/mowas/mapData.json
> INFO Regionalschlüssel ARS mowas, 11 Einträge
> INFO Warn ID: mow.DE-NW-EU-SE091-20210823-109-000
> INFO {'id': 'mow.DE-NW-EU-SE091-20210823-109-000', 'version': 1, 
> 'startDate': '2021-11-09T15:17:17+01:00', 'severity': 'Minor', 'type': 
> 'Update', 'i18nTitle': {'de': '+++ Betretungsverbot Bergschadensgebiet 
> Stadt Mechernich +++'}, 'transKeys': {'event': 'BBK-EVC-059'}}
> INFO Warn ID: mow.DE-BY-LA-W144-20230713-000
> INFO {'id': 'mow.DE-BY-LA-W144-20230713-000', 'version': 5, 'startDate': 
> '2023-07-13T12:41:33+02:00', 'severity': 'Minor', 'type': 'Alert', 
> 'i18nTitle': {'de': 'Bakterielle Verkeimung im Trinkwasser in einzelnen 
> Ortsteilen von Neustadt a.d. Do - Neustadt a.d. Donau - Ortsteile 
> Arresting, Hienheim, Irnsing und Marching'}, 'transKeys': {'event': 
> 'BBK-EVC-069'}}
> INFO Warn ID: mow.DE-HE-FB-W193-20230714-002
> INFO {'id': 'mow.DE-HE-FB-W193-20230714-002', 'version': 5, 'startDate': 
> '2023-07-14T15:08:50+02:00', 'severity': 'Minor', 'type': 'Update', 
> 'i18nTitle': {'de': 'Explosionsgefahr Stadtwald Butzbach - Stadtwald 
> Butzbach'}, 'transKeys': {'event': 'BBK-EVC-077'}}
>

[weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

001 
['mow.DE-BB-BRB-SE081-20230718-81-001']
BBK.warnings() areas[] mow.DE-TH-HIG-W111-20230718-002 
['mow.DE-TH-HIG-W111-20230718-002']
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-NW-EU-SE091-20210823-109-000.json
BBK.warnings() get_warning( mow.DE-NW-EU-SE091-20210823-109-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BY-LA-W144-20230713-000.json
BBK.warnings() get_warning( mow.DE-BY-LA-W144-20230713-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-HE-FB-W193-20230714-002.json
BBK.warnings() get_warning( mow.DE-HE-FB-W193-20230714-002 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BW-LB-W026-20230714-000.json
BBK.warnings() get_warning( mow.DE-BW-LB-W026-20230714-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BY-ED-W186-20230717-000.json
BBK.warnings() get_warning( mow.DE-BY-ED-W186-20230717-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BW-HD-W086-20230718-001.json
BBK.warnings() get_warning( mow.DE-BW-HD-W086-20230718-001 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-SN-HY-SE048-20230718-122-001.json
BBK.warnings() get_warning( mow.DE-SN-HY-SE048-20230718-122-001 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-SL-SB-SE035-20230718-35-000.json
BBK.warnings() get_warning( mow.DE-SL-SB-SE035-20230718-35-000 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-NW-HER-SE083-20230718-83-001.json
BBK.warnings() get_warning( mow.DE-NW-HER-SE083-20230718-83-001 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-BB-BRB-SE081-20230718-81-001.json
BBK.warnings() get_warning( mow.DE-BB-BRB-SE081-20230718-81-001 )
INFO successfully downloaded 
https://warnung.bund.de/api31/warnings/mow.DE-TH-HIG-W111-20230718-002.json
BBK.warnings() get_warning( mow.DE-TH-HIG-W111-20230718-002 )

-- HTML -- bbk-mowas.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 18:03

-- JSON -- bbk-mowas.json -
[]
teffi@weewx:/etc/weewx/skins/Belchertown/dwd$ 
On Tuesday, July 18, 2023 at 4:50:08 PM UTC+2 Karen K wrote:

> "Using test configuration" is the important notice within the output. This 
> is for testing only. You need to specify either --weewx or 
> --config=your_config_file at the command line.
>
> Stefan Gliessmann schrieb am Dienstag, 18. Juli 2023 um 11:08:24 UTC+2:
>
>> similar with bbk-warnings dwd --dry-run
>>
>> there is a gale wind warning, but bbk-dwd.inc says no warnings ...
>>
>> teffi@weewx:~/bkk-warnings$ sudo bbk-warnings dwd --dry-run
>>
>> Using test configuration
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/appdata/gsb/eventCodes/eventCodes.json
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/appdata/gsb/logos/logos.json
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/dwd/mapData.json
>>
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/dashboard/14522000.json
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/dashboard/14713000.json
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/dashboard/14521000.json
>> INFO successfully downloaded 
>> https://nina.api.proxy.bund.dev/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL.json
>> 
>> -- HTML -- bbk-dwd.inc --
>> zur Zeit keine WarnungenZuletzt beim BBK 
>> abgerufen am 18.07.2023 11:04
>>
>> -- JSON -- bbk-dwd.json -
>>
>> []
>> 
>> -- HTML -- bbk-DL.inc --
>> zur Zeit keine WarnungenZuletzt beim BBK 
>> abgerufen am 18.07.2023 11:04
>>
>>
>> -- JSON -- bbk-DL.json -
>> []
>> 
>> -- HTML -- bbk-L.inc --
>> zur Zeit keine WarnungenZuletzt beim BBK 
>> abgerufen am 18.07.2023 11:04
>>
>>
>> -- JSON -- bbk-L.json -
>> []
>> 
>> -- HTML -- bbk-Oberwiesenthal.inc --
>> zur Zeit keine WarnungenZuletzt beim BBK 
>> abgerufen am 18.07.2023 11:04
>>
>>
>> -- JSON -- bbk-Oberwiesenthal.json -
>> []
>&

[weewx-user] Re: bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

similar with bbk-warnings dwd --dry-run

there is a gale wind warning, but bbk-dwd.inc says no warnings ...

teffi@weewx:~/bkk-warnings$ sudo bbk-warnings dwd --dry-run
Using test configuration
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/appdata/gsb/eventCodes/eventCodes.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/appdata/gsb/logos/logos.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dwd/mapData.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14522000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14713000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14521000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL.json

-- HTML -- bbk-dwd.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 11:04

-- JSON -- bbk-dwd.json -
[]

-- HTML -- bbk-DL.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 11:04

-- JSON -- bbk-DL.json -
[]

-- HTML -- bbk-L.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 11:04

-- JSON -- bbk-L.json -
[]

-- HTML -- bbk-Oberwiesenthal.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 11:04

-- JSON -- bbk-Oberwiesenthal.json -
[]
teffi@weewx:~/bkk-warnings$ sudo curl -X 'GET' 
'https://nina.api.proxy.bund.dev/api31/dwd/mapData.json' -H 'accept: 
application/json'
[{"id":"dwdmap.2.49.0.0.276.0.DWD.PVW.168966996.e59c3f1a-6812-4a12-a755-9d83ea7e2deb.MUL","version":5,"startDate":"2023-07-18T10:46:00+02:00","expiresDate":"2023-07-19T06:00:00+02:00","severity":"Moderate","type":"Alert","i18nTitle":{"de":"Amtliche
 
WARNUNG vor STURMBÖEN","en":"Official WARNING of GALE-FORCE 
GUSTS","es":"AVISO oficial de TURBONADA","fr":"ALERTE officielle 
INTEMPÉRIES PRONONCÉES pour RAFALES DE FORCE FORT COUP DE 
VENT"}}]teffi@weewx:~/bkk-warnings$ 
teffi@weewx:~/bkk-warnings$ 

On Tuesday, July 18, 2023 at 10:47:44 AM UTC+2 Stefan Gliessmann wrote:

> I am struggling with the use of bbk-warnings.
>
> I would like to use "bundesweit" instead of a specific ARS. Hence, I use 
> biwapp, mowas, lhp, police, etc.
> Checking using the NINA or BiWapp Apps, it seems that I do not receive all 
> infos/warnings in the generated e.g. bbk-mowas.inc files.
>
> please take a look at the following example:
>
> teffi@weewx:~/bkk-warnings$ sudo bbk-warnings mowas --dry-run
> Using test configuration
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/appdata/gsb/eventCodes/eventCodes.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/appdata/gsb/logos/logos.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/mowas/mapData.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/dashboard/14522000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/dashboard/14713000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/dashboard/14521000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-NW-EU-SE091-20210823-109-000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BY-LA-W144-20230713-000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-HE-FB-W193-20230714-002.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BW-LB-W026-20230714-000.json
> INFO successfully downloaded 
> https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BY-ED-W186-20230717-000.json
> 
> -- HTML -- bbk-mowas.inc --
> zur Zeit keine WarnungenZuletzt beim BBK 
> abgerufen am 18.07.2023 10:37
>
> -- JSON -- bbk-mowas.json -
> []
> 
> -- HTML -- bbk-DL.inc --
> zur Zeit keine WarnungenZuletzt beim BBK 
> abgerufen am 18.07.2023 10:37
&g

[weewx-user] bbk-warnings does not display warnings eventhough there are some

[Stefan Gliessmann]

I am struggling with the use of bbk-warnings.

I would like to use "bundesweit" instead of a specific ARS. Hence, I use 
biwapp, mowas, lhp, police, etc.
Checking using the NINA or BiWapp Apps, it seems that I do not receive all 
infos/warnings in the generated e.g. bbk-mowas.inc files.

please take a look at the following example:

teffi@weewx:~/bkk-warnings$ sudo bbk-warnings mowas --dry-run
Using test configuration
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/appdata/gsb/eventCodes/eventCodes.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/appdata/gsb/logos/logos.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/mowas/mapData.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14522000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14713000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/dashboard/14521000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-NW-EU-SE091-20210823-109-000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BY-LA-W144-20230713-000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-HE-FB-W193-20230714-002.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BW-LB-W026-20230714-000.json
INFO successfully downloaded 
https://nina.api.proxy.bund.dev/api31/warnings/mow.DE-BY-ED-W186-20230717-000.json

-- HTML -- bbk-mowas.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 10:37

-- JSON -- bbk-mowas.json -
[]

-- HTML -- bbk-DL.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 10:37

-- JSON -- bbk-DL.json -
[]

-- HTML -- bbk-L.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 10:37

-- JSON -- bbk-L.json -
[]

-- HTML -- bbk-Oberwiesenthal.inc --
zur Zeit keine WarnungenZuletzt beim BBK 
abgerufen am 18.07.2023 10:37

-- JSON -- bbk-Oberwiesenthal.json -
[]
teffi@weewx:~/bkk-warnings$ sudo curl -X 'GET' 
'https://nina.api.proxy.bund.dev/api31/mowas/mapData.json' -H 'accept: 
application/json'
[{"id":"mow.DE-NW-EU-SE091-20210823-109-000","version":1,"startDate":"2021-11-09T15:17:17+01:00","severity":"Minor","type":"Update","i18nTitle":{"de":"+++
 
Betretungsverbot Bergschadensgebiet Stadt Mechernich 
+++"},"transKeys":{"event":"BBK-EVC-059"}},{"id":"mow.DE-BY-LA-W144-20230713-000","version":5,"startDate":"2023-07-13T12:41:33+02:00","severity":"Minor","type":"Alert","i18nTitle":{"de":"Bakterielle
 
Verkeimung im Trinkwasser in einzelnen Ortsteilen von Neustadt a.d. Do - 
Neustadt a.d. Donau - Ortsteile Arresting, Hienheim, Irnsing und 
Marching"},"transKeys":{"event":"BBK-EVC-069"}},{"id":"mow.DE-HE-FB-W193-20230714-002","version":5,"startDate":"2023-07-14T15:08:50+02:00","severity":"Minor","type":"Update","i18nTitle":{"de":"Explosionsgefahr
 
Stadtwald Butzbach - Stadtwald 
Butzbach"},"transKeys":{"event":"BBK-EVC-077"}},{"id":"mow.DE-BW-LB-W026-20230714-000","version":5,"startDate":"2023-07-14T16:59:18+02:00","severity":"Minor","type":"Alert","i18nTitle":{"de":"Abkochgebot
 
Trinkwasser in Mundelsheim - Mundelsheim gesamtes 
Ortsgebiet"},"transKeys":{"event":"BBK-EVC-069"}},{"id":"mow.DE-BY-ED-W186-20230717-000","version":5,"startDate":"2023-07-17T15:22:30+02:00","severity":"Minor","type":"Alert","i18nTitle":{"de":"Verunreinigung
 
des Trinkwassers mit Keimen in der Stadt Moosburg a.d. Isar - Stadt 
Moosburg; Thonstetten; Grünseiboldsdorf; 
Ober-Niederhummel"},"transKeys":{"event":"BBK-EVC-069"}}]teffi@weewx:~/bkk-warnings$
 

teffi@weewx:~/bkk-warnings$ 

-- 
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/fb5624f9-939b-4ead-9b28-15091292fab0n%40googlegroups.com.

Re: [weewx-user] weewx can't update data from netatmo no more

[Stefan Gliessmann]

Awesome!

Glad I was of help :)

On Tue, Jul 18, 2023 at 10:20 AM 'neu...@bnjpro.dk' via weewx-user <
weewx-user@googlegroups.com> wrote:

> It works.
>
> Thank you Stefan, it made my day. :-)
>
> mandag den 17. juli 2023 kl. 21.17.17 UTC+2 skrev neu...@bnjpro.dk:
>
>> Thank you Stefan, this looks like a good solution. I will try it out
>> tomorrow. :-)
>>
>>
>> mandag den 17. juli 2023 kl. 15.34.08 UTC+2 skrev Stefan Gliessmann:
>>
>>> a friend is using netatmo, too.
>>>
>>> take a look here:
>>>
>>> https://oe7drt.com/posts/2023-07-15-update-weewx-netatmo-extension/
>>>
>>> On Monday, July 17, 2023 at 11:38:47 AM UTC+2 Rainer Lang wrote:
>>>
>>>> Maybe you send us a complete excerpt from your syslog covering the
>>>> weewx startup and at least one archiving period
>>>> That would be more helpful than just a few snippets.
>>>>
>>>> Thanks
>>>> On 17.07.2023 11:02, 'neu...@bnjpro.dk' via weewx-user wrote:
>>>>
>>>> I have been the happy user of weeWX for a very long time now. And I'm
>>>> still amazed that someone is able to write such a large and well
>>>> functioning piece of software. I think when you are not able to program in
>>>> python it is amazing when someone else can. :-)
>>>>
>>>> Friday last week (monday today) I made an upgrade on my server (Ubuntu
>>>> 22.04 LTS) to also be able to get updates from Ubuntu pro.
>>>>
>>>> But after doing that, my WeeWX installation doesn't work. Well that is
>>>> not entirely true, because WeeWx works, but the driver for my netatmo
>>>> weather-station does not get data.
>>>>
>>>> I use driver version 0.14 which I think is the latest, and the one that
>>>> gets data the way netatmo API wants it to. I have user, password, client-id
>>>> and client-secret running as expected.
>>>>
>>>> But looking at the logfile (syslog) I get the hint that there is a HTTP
>>>> error 400. This hint is a little week for me to figure out what is the real
>>>> course of fail, to be able to do something about it.
>>>>
>>>> Additionally I get this output from the log: url:
>>>> https://api.netatmo.com/oauth2/token data:
>>>> b'grant_type=password&client_id=64b0ea9f090b11190f07b867&client_secret=Haf1qozNFvLMjpjp64cSpgiuPY3IYm4BlPb8zp7EmjlL&username=neumann%
>>>> 40bnjpro.dk&password=SECRET&scope=read_station' hdr: {'Content-Type':
>>>> 'application/x-www-form-urlencoded;charset=utf-8'}
>>>>
>>>> I have masked out my password.
>>>>
>>>> Is there any obvious reason for the driver to not being able to connect
>>>> to the API?
>>>>
>>>> --
>>>> 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/b75a72cd-6c53-49ed-98a8-03e52a7634a2n%40googlegroups.com
>>>> <https://groups.google.com/d/msgid/weewx-user/b75a72cd-6c53-49ed-98a8-03e52a7634a2n%40googlegroups.com?utm_medium=email&utm_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/XpT98FO3i5w/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/07c41b85-19ef-4e79-9b69-609a4428ad6an%40googlegroups.com
> <https://groups.google.com/d/msgid/weewx-user/07c41b85-19ef-4e79-9b69-609a4428ad6an%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/CACXWM9QyGPMSZONokASruv8UGHbP8%3DoxyXhLVhfug2jp0Qe%2BGQ%40mail.gmail.com.

Re: [weewx-user] weewx can't update data from netatmo no more

[Stefan Gliessmann]

a friend is using netatmo, too.

take a look here:

https://oe7drt.com/posts/2023-07-15-update-weewx-netatmo-extension/

On Monday, July 17, 2023 at 11:38:47 AM UTC+2 Rainer Lang wrote:

> Maybe you send us a complete excerpt from your syslog covering the weewx 
> startup and at least one archiving period
> That would be more helpful than just a few snippets.
>
> Thanks
> On 17.07.2023 11:02, 'neu...@bnjpro.dk' via weewx-user wrote:
>
> I have been the happy user of weeWX for a very long time now. And I'm 
> still amazed that someone is able to write such a large and well 
> functioning piece of software. I think when you are not able to program in 
> python it is amazing when someone else can. :-) 
>
> Friday last week (monday today) I made an upgrade on my server (Ubuntu 
> 22.04 LTS) to also be able to get updates from Ubuntu pro.
>
> But after doing that, my WeeWX installation doesn't work. Well that is not 
> entirely true, because WeeWx works, but the driver for my netatmo 
> weather-station does not get data.
>
> I use driver version 0.14 which I think is the latest, and the one that 
> gets data the way netatmo API wants it to. I have user, password, client-id 
> and client-secret running as expected.
>
> But looking at the logfile (syslog) I get the hint that there is a HTTP 
> error 400. This hint is a little week for me to figure out what is the real 
> course of fail, to be able to do something about it.
>
> Additionally I get this output from the log: url: 
> https://api.netatmo.com/oauth2/token data: 
> b'grant_type=password&client_id=64b0ea9f090b11190f07b867&client_secret=Haf1qozNFvLMjpjp64cSpgiuPY3IYm4BlPb8zp7EmjlL&username=neumann%
> 40bnjpro.dk&password=SECRET&scope=read_station' hdr: {'Content-Type': 
> 'application/x-www-form-urlencoded;charset=utf-8'}
>
> I have masked out my password.
>
> Is there any obvious reason for the driver to not being able to connect to 
> the API?
>
> -- 
> 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/b75a72cd-6c53-49ed-98a8-03e52a7634a2n%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/fa1b5737-3d04-4a55-894e-3ea6c2e229d9n%40googlegroups.com.

Re: [weewx-user] Re: Belchertown Charts Color

[Schnidrig Stefan]

HelloThank you very much. It works. The standart is 30 ms, when the intervall is 5minutes. I have 10minutes, also 60ms. ThxHolen Sie sich Outlook für Android



-- 
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/A0445B7E-E7E8-524E-AEF0-1470058F35A3%40hxcore.ol.

Re: [weewx-user] Re: Belchertown Charts Color

[Schnidrig Stefan]

Hello.Thx for the reponse. The database is correct. When i go with the Mouse over the Grafik, i can see the datapoint. Holen Sie sich Outlook für Android



-- 
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/97B5F2FA-8673-9D4B-905B-9CDABE7268E3%40hxcore.ol.

Re: [weewx-user] Re: Merge database failed

[Schnidrig Stefan]

Hello Vince Many thanks for your response. I moved my old weewx.sdb to the new weewx version and then created it in the new format with "wee_database weewx.conf --reconfigure". Unfortunately, the "sunshine_hours" was deleted in the process. Can I somehow transfer these to the new scheme? Greeting



-- 
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/98443152-C44D-644F-A2E3-497322D3C5B7%40hxcore.ol.

Re: [weewx-user] Sunshine Duration

[Schnidrig Stefan]

Hey.Yes. Is in the weewx.sdb. The current sunshine time works. The day sunshine time not. Holen Sie sich Outlook für Android



-- 
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/AE606AC9-915E-6B4E-871F-47CFB3D9317A%40hxcore.ol.

[weewx-user] Re: weewx-mqtt configuration wrong?

['Stefan Ferber' via weewx-user]

Thx for your great hints. The weewx-mqtt configuration was correct. I was 
listening to the topic weewx but if you read (AND really understand AND 
follow  ;-) the documentation, it is published on /loop and /observation_.  
Here is the output of weewx/loop payload arriving every 5 minutes:

{ "dateTime": "1609226100.0", "windLinkStatus": "1.0", "windBatteryStatus": 
"0.0", "rainLinkStatus": "0.0", "rainBatteryStatus": "0.0", "uvLinkStatus": 
"1.0", "uvBatteryStatus": "0.0", "inTemp_C": "23.970689655172414", 
"inHumidity": "38.0", "outTemp_C": "2.603448275862065", "outHumidity": 
"84.0", "outTempBatteryStatus": "0.0", "outLinkStatus": "0.0", 
"extraTemp1_C": "23.025", "extraHumid1": "39.0", 
"extraBatteryStatus1": "0.0", "extraLinkStatus1": "0.0", "extraTemp2_C": 
"21.286", "extraHumid2": "43.0", "extraBatteryStatus2": "0.0", 
"extraLinkStatus2": "0.0", "extraTemp3_C": "25.165517241379295", 
"extraHumid3": "65.62068965517241", "extraBatteryStatus3": "0.0", 
"extraLinkStatus3": "0.0", "extraTemp4_C": "21.62068965517242", 
"extraHumid4": "43.0", "extraBatteryStatus4": "0.0", "extraLinkStatus4": 
"0.0", "rainTotal": "218.018040001", "rain_cm": "0.0", 
"barometer_mbar": "948.5258620689654", "forecast": "4.0", "storm": "0.0", 
"pressure_mbar": "916.376047509162", "altimeter_mbar": "947.8952290346878", 
"cloudbase_meter": "582.7279829856743", "dewpoint_C": "0.1756150230575394", 
"heatindex_C": "2.603448275862065", "humidex_C": "2.603448275862065", 
"inDewpoint_C": "8.76924066086359", "rainRate_cm_per_hour": "0.0", 
"interval_minute": "5.0", "hourRain_cm": "0.0", "rain24_cm": 
"0.211667935", "dayRain_cm": "0.141112000185", "usUnits": 
"16.0" }

... the floating point number with 22 digits are little bit overkill.

Thx so much - issue closed ;-)
bell...@gmail.com schrieb am Montag, 28. Dezember 2020 um 20:47:19 UTC+1:

> A couple more things to check out.
> 1. If my memory is correct the mqtt extension publishes ‘aggregate’ (json 
> format) to /loop and individual to  name>/observation_. So after the simple pub/sub test, try 
> subscribing to weewx/# and see what you get.
> 2. From your log snippet you are publishing on archive record generation. 
> Which from your log is 300 seconds.  So, will need to wait for this to 
> happen before anything will be published.
> rich
>
> On Monday, 28 December 2020 at 14:07:50 UTC-5 vince wrote:
>
>> I'd start in weewx.conf by setting debug=1 at the top, and in your MQTT 
>> section set log_success=true and log_failure=true.   Then restart weewx and 
>> check your logs.
>>
>> A better test of your MQTT is to publish in one shell and subscribe in 
>> another.   Just open two windows.
>>
>> In one shell:   mosquito_pub -h homeassistant.local -t weewx -u 
>> mqtt-local -P  -m "hello world" 
>> In the other:mosquito_sub -h homeassistant.local -t weewx -u 
>> mqtt-local -P 
>>
>> You should see 'hello world' appear in the shell that is subscribing.
>>
>>

-- 
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/130691f9-ce1d-41c4-891c-d0ae22848826n%40googlegroups.com.

[weewx-user] weewx-mqtt configuration wrong?

['Stefan Ferber' via weewx-user]

Just installed the mqtt extension https://github.com/weewx/weewx/wiki/mqtt and 
configured the /etc/weewx/weewx.conf file

[[MQTT]]
server_url = 
"mqtt://mqtt-local:@homeassistant.local:1883"
topic = weewx
unit_system = METRIC

*But the broker does not receive any message on this topic.*

Checking the log files everything looks fine:

Dec 28 18:34:49 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Dec 28 18:34:52 raspberrypi weewx[31732] INFO __main__: Initializing weewx 
version 4.2.0
Dec 28 18:34:52 raspberrypi weewx[31732] INFO __main__: Using Python 3.7.3 
(default, Dec 20 2019, 18:57:59) #012[GCC 8.3.0]
Dec 28 18:34:52 raspberrypi weewx[31732] INFO __main__: Platform 
Linux-4.19.97+-armv6l-with-debian-10.3
Dec 28 18:34:52 raspberrypi weewx[31732] INFO __main__: Locale is 
'de_DE.UTF-8'
Dec 28 18:34:52 raspberrypi weewx[31732] INFO __main__: PID file is 
/var/run/weewx.pid
Dec 28 18:34:52 raspberrypi weewx[31720]: Starting weewx weather system: 
weewx.
Dec 28 18:34:52 raspberrypi systemd[1]: Started LSB: weewx weather system.
Dec 28 18:34:52 raspberrypi weewx[31736] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Dec 28 18:34:53 raspberrypi weewx[31736] INFO __main__: Debug is 0
Dec 28 18:34:53 raspberrypi weewx[31736] INFO weewx.engine: Loading station 
type TE923 (weewx.drivers.te923)
Dec 28 18:34:53 raspberrypi weewx[31736] INFO weewx.drivers.te923: driver 
version is 0.41.1
Dec 28 18:34:53 raspberrypi weewx[31736] INFO weewx.drivers.te923: polling 
interval is 10
Dec 28 18:34:53 raspberrypi weewx[31736] INFO weewx.drivers.te923: sensor 
map is {'windLinkStatus': 'link_wind', 'windBatteryStatus': 'bat_wind', 
'rainLinkStatus': 'link_rain', 'rainBatteryStatus': 'bat_rain', 
'uvLinkStatus': 'link_uv', 'uvBatteryStatus': 'bat_uv', 'inTemp': 't_in', 
'inHumidity': 'h_in', 'outTemp': 't_1', 'outHumidity': 'h_1', 
'outTempBatteryStatus': 'bat_1', 'outLinkStatus': 'link_1', 'extraTemp1': 
't_2', 'extraHumid1': 'h_2', 'extraBatteryStatus1': 'bat_2', 
'extraLinkStatus1': 'link_2', 'extraTemp2': 't_3', 'extraHumid2': 'h_3', 
'extraBatteryStatus2': 'bat_3', 'extraLinkStatus2': 'link_3', 'extraTemp3': 
't_4', 'extraHumid3': 'h_4', 'extraBatteryStatus3': 'bat_4', 
'extraLinkStatus3': 'link_4', 'extraTemp4': 't_5', 'extraHumid4': 'h_5', 
'extraBatteryStatus4': 'bat_5', 'extraLinkStatus4': 'link_5'}
Dec 28 18:34:53 raspberrypi weewx[31736] INFO weewx.drivers.te923: Found 
device on USB bus= device=
Dec 28 18:34:55 raspberrypi weewx[31736] ERROR weewx.drivers.te923: Failed 
attempt 1 of 5 to read data: [Errno 110] Operation timed out
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.drivers.te923: logger 
capacity 208 records
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.drivers.te923: station 
time is 1582844400.0, computer time is 1609176898
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.engine: StdConvert 
target unit is 0x1
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.engine: Archive will 
use data binding wx_binding
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.engine: Record 
generation will be attempted in 'hardware'
Dec 28 18:34:58 raspberrypi weewx[31736] INFO weewx.engine: Using archive 
interval of 300 seconds (specified in weewx configuration)
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: StationRegistry: 
Registration not requested.
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: 
Wunderground-PWS: Data for station IBADENWR90 will be posted
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: PWSweather: 
Posting not enabled.
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: CWOP: Posting 
not enabled.
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: WOW: Posting not 
enabled.
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.restx: AWEKAS: Posting 
not enabled.
Dec 28 18:34:59 raspberrypi weewx[31736] INFO user.mqtt: service version is 
0.23
Dec 28 18:34:59 raspberrypi weewx[31736] INFO user.mqtt: binding to archive
Dec 28 18:34:59 raspberrypi weewx[31736] INFO user.mqtt: topic is weewx
Dec 28 18:34:59 raspberrypi weewx[31736] INFO user.mqtt: desired unit 
system is METRIC
Dec 28 18:34:59 raspberrypi weewx[31736] INFO user.mqtt: data will be 
uploaded to mqtt://mqtt-local:xxx@homeassistant.local:1883
Dec 28 18:34:59 raspberrypi weewx[31736] INFO __main__: Starting up weewx 
version 4.2.0
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx.sdb'
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.manager: Starting 
backfill of daily summaries
Dec 28 18:34:59 raspberrypi weewx[31736] INFO weewx.drivers.te923: reading 
records from logger since 1609176600
Dec 28 18:35:00 raspberrypi weewx[31736] INFO weewx.drivers.te923: read 0 
records from logger
Dec 28 18:35:00 raspberrypi weewx[31736] INFO weewx.engine: Starting main 
packet loop.
 
the "loop" also reports success

Dec 28 18:34:59 raspberrypi weewx[31736] INFO user

[weewx-user] Re: Missing channel 5 for TE923 in html-report

['Stefan Ferber' via weewx-user]

issue closed

Stefan Ferber schrieb am Montag, 28. Dezember 2020 um 16:03:23 UTC+1:

> Found the solution myself. In /etc/weewx/skins/Seasons/skin.conf I had to 
> add a line for the missing channel 4:
>
> [[[daytemp]]]
> yscale = None, None, 0.5 
> extraTemp1 
> extraTemp2 
> extraTemp3 
> *extraTemp4*
>
> and for all other seasons week, month, and year, too
> Stefan Ferber schrieb am Sonntag, 27. Dezember 2020 um 22:05:41 UTC+1:
>
>> Thx for providing WeeWx - really impressed by the ease of installation 
>> and configuration options. Running for two weeks now ;-)
>>
>> I have 5 external sensors (temp, humidity, battery status) connected to 
>> my TE923. WeeWx is fetching the data correctly 
>> $ sudo wee_device --current
>> Using configuration file /etc/weewx/weewx.conf
>> Using TE923 driver version 0.41.1 (weewx.drivers.te923)
>> Querying the station for current weather data...
>> dateTime: 1609093626
>> forecast: 0
>>  h_1: 64
>>h_1_state: ok
>>  h_2: 38
>>h_2_state: ok
>>  h_3: 41
>>h_3_state: ok
>>  h_4: 47
>>h_4_state: ok
>>  h_5: 37
>>h_5_state: ok
>> h_in: 36
>>   h_in_state: ok
>> rain: 3087
>>   rain_state: ok
>>  slp: 948.625
>>slp_state: ok
>>storm: 0
>>  t_1: 2.7
>>t_1_state: ok
>>  t_2: 22.1
>>t_2_state: ok
>>  t_3: 20.8
>>t_3_state: ok
>>  t_4: 21.6
>>t_4_state: ok
>>  t_5: 20.8
>>t_5_state: ok
>> t_in: 22.85
>>   t_in_state: ok
>>   uv: None
>> uv_state: no_link
>>windchill: 1.9
>>  windchill_state: ok
>>  winddir: 2
>>winddir_state: ok
>> windgust: 0.0
>>   windgust_state: ok
>>windspeed: 0.0
>>  windspeed_state: ok
>>
>> but the last channel 5 is not shown in the temperature graphs.  The 
>> mapping is a little bit confusing but this graph should show 4 channels but 
>> is providing only 3 channels. 
>> [image: daytemp.png]
>>
>> Therefore, I added a new line for the missing channel "extraTemp4" in 
>> the weewx.conf and change the names to my rooms:
>>
>> # The labels to be used for each observation type
>> [[[Labels]]]
>>
>> # Set to hemisphere abbreviations suitable for your location:
>> hemispheres = N, S, E, W
>>
>> # Formats to be used for latitude whole degrees, longitude 
>> whole
>> # degrees, and minutes:
>> latlon_formats = %02d, %03d, %05.2f
>>
>> # Generic labels, keyed by an observation type.
>> Generic
>> barometer = Barometer
>> <...>
>> windvec = Wind Vector
>> extraTemp1 = Living Room
>> extraTemp2 = Kitchen
>> extraTemp3 = Bath
>> extraTemp4 = Kids Room
>>
>> But the report still contains only 3 channels. 
>> [image: daytemp (1).png]
>>
>>
>> What do I have to do now?
>>
>>
>>

-- 
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/e7472908-9c6f-4e63-9447-7d8fd1424c32n%40googlegroups.com.

[weewx-user] Re: Missing channel 5 for TE923 in html-report

['Stefan Ferber' via weewx-user]

Found the solution myself. In /etc/weewx/skins/Seasons/skin.conf I had to 
add a line for the missing channel 4:

[[[daytemp]]]
yscale = None, None, 0.5 
extraTemp1 
extraTemp2 
extraTemp3 
*extraTemp4*

and for all other seasons week, month, and year, too
Stefan Ferber schrieb am Sonntag, 27. Dezember 2020 um 22:05:41 UTC+1:

> Thx for providing WeeWx - really impressed by the ease of installation and 
> configuration options. Running for two weeks now ;-)
>
> I have 5 external sensors (temp, humidity, battery status) connected to my 
> TE923. WeeWx is fetching the data correctly 
> $ sudo wee_device --current
> Using configuration file /etc/weewx/weewx.conf
> Using TE923 driver version 0.41.1 (weewx.drivers.te923)
> Querying the station for current weather data...
> dateTime: 1609093626
> forecast: 0
>  h_1: 64
>h_1_state: ok
>  h_2: 38
>h_2_state: ok
>  h_3: 41
>h_3_state: ok
>  h_4: 47
>h_4_state: ok
>  h_5: 37
>h_5_state: ok
> h_in: 36
>   h_in_state: ok
> rain: 3087
>   rain_state: ok
>  slp: 948.625
>slp_state: ok
>storm: 0
>  t_1: 2.7
>t_1_state: ok
>  t_2: 22.1
>t_2_state: ok
>  t_3: 20.8
>t_3_state: ok
>  t_4: 21.6
>t_4_state: ok
>  t_5: 20.8
>t_5_state: ok
> t_in: 22.85
>   t_in_state: ok
>   uv: None
> uv_state: no_link
>windchill: 1.9
>  windchill_state: ok
>  winddir: 2
>winddir_state: ok
> windgust: 0.0
>   windgust_state: ok
>windspeed: 0.0
>  windspeed_state: ok
>
> but the last channel 5 is not shown in the temperature graphs.  The 
> mapping is a little bit confusing but this graph should show 4 channels but 
> is providing only 3 channels. 
> [image: daytemp.png]
>
> Therefore, I added a new line for the missing channel "extraTemp4" in the 
> weewx.conf 
> and change the names to my rooms:
>
> # The labels to be used for each observation type
> [[[Labels]]]
>
> # Set to hemisphere abbreviations suitable for your location:
> hemispheres = N, S, E, W
>
> # Formats to be used for latitude whole degrees, longitude 
> whole
> # degrees, and minutes:
> latlon_formats = %02d, %03d, %05.2f
>
> # Generic labels, keyed by an observation type.
> Generic
> barometer = Barometer
> <...>
> windvec = Wind Vector
> extraTemp1 = Living Room
> extraTemp2 = Kitchen
> extraTemp3 = Bath
> extraTemp4 = Kids Room
>
> But the report still contains only 3 channels. 
> [image: daytemp (1).png]
>
>
> What do I have to do now?
>
>
>

-- 
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/22c34cf5-2254-4673-8ccd-e1927ee679d5n%40googlegroups.com.

Re: [weewx-user] SFTP upload error ftplib.py

['Stefan Ferber' via weewx-user]

issue is closed.

Stefan Ferber schrieb am Montag, 28. Dezember 2020 um 12:23:06 UTC+1:

> Just installed this weewx extension 
> https://github.com/matthewwall/weewx-sftp  
> <https://github.com/matthewwall/weewx-sftp>
> works great ;-)
> Stefan Ferber schrieb am Montag, 28. Dezember 2020 um 11:47:01 UTC+1:
>
>> Thx for your quick answer - 100% correct: although my provider IONOS 
>> supports SFTP and FTPS, looks like my account supports only SFTP.
>>
>> tke...@gmail.com schrieb am Montag, 28. Dezember 2020 um 01:45:46 UTC+1:
>>
>>> WeeWX supports FTPS, which is FTP over TLS. It does *not* support SFTP, 
>>> which uses a Secure Socket Shell protocol. I'm guessing your FTP server 
>>> simply does not support FTPS.
>>>
>>> Can you use rsync? It's better in almost every way.
>>>
>>> On Sun, Dec 27, 2020 at 1:47 PM 'Stefan Ferber' via weewx-user <
>>> weewx...@googlegroups.com> wrote:
>>>
>>>> Cannot find the defect in my sftp configuration. Could you please check?
>>>>
>>>> [[SmartphoneReport]]
>>>> # The SmartphoneReport uses the 'Smartphone' skin, and the 
>>>> images and
>>>> # files are placed in a dedicated subdirectory.
>>>> skin = Smartphone
>>>> enable = true 
>>>> HTML_ROOT = /var/www/html/weewx/smartphone
>>>>
>>>> [[MobileReport]]
>>>> # The MobileReport uses the 'Mobile' skin, and the images and 
>>>> files
>>>> # are placed in a dedicated subdirectory.
>>>> skin = Mobile
>>>> enable = true 
>>>> HTML_ROOT = /var/www/html/weewx/mobile
>>>>
>>>> [[StandardReport]]
>>>> # This is the old "Standard" skin. By default, it is not 
>>>> enabled.
>>>> skin = Standard
>>>> enable = false
>>>>
>>>> [[FTP]]
>>>> # FTP'ing the results to a webserver is treated as just another 
>>>> report,
>>>> # albeit one with an unusual report generator!
>>>> skin = Ftp
>>>>
>>>> # If you wish to use FTP, set "enable" to "true", then
>>>> # fill out the next four lines.
>>>> # Use quotes around passwords to guard against parsing errors.
>>>> enable = true 
>>>> user =   
>>>> password = ""
>>>> server = home15604585.1and1-data.host# The ftp server name, 
>>>> e.g, www.myserver.org
>>>> path = /SmartFerber/weewx# The destination directory, e.g., 
>>>> /weather
>>>>
>>>> # Set to True for an FTP over TLS (FTPS) connection. Not all 
>>>> servers
>>>> # support this.
>>>> secure_ftp = 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 = 22
>>>>
>>>> # Set to 1 to use passive mode, zero for active mode
>>>> passive = 1
>>>>
>>>> getting multiple errors:
>>>>
>>>> Dec 27 22:35:51 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>>> Generated 8 files for report SeasonsReport in 28.09 seconds
>>>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>>>> Generated 15 images for report SeasonsReport in 6.71 seconds
>>>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.reportengine: 
>>>> Copied 5 files to /var/www/html/weewx
>>>> Dec 27 22:36:01 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>>> Generated 6 files for report SmartphoneReport in 2.09 seconds
>>>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>>>> Generated 6 images for report SmartphoneReport in 2.40 seconds
>>>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.reportengine: 
>>>> Copied 6 files to /var/www/html/weewx/smartphone
>>>> Dec 27 22:36:04 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>>> Generated 1 files for report MobileRep

Re: [weewx-user] SFTP upload error ftplib.py

['Stefan Ferber' via weewx-user]

Just installed this weewx extension 
https://github.com/matthewwall/weewx-sftp  
<https://github.com/matthewwall/weewx-sftp>
works great ;-)
Stefan Ferber schrieb am Montag, 28. Dezember 2020 um 11:47:01 UTC+1:

> Thx for your quick answer - 100% correct: although my provider IONOS 
> supports SFTP and FTPS, looks like my account supports only SFTP.
>
> tke...@gmail.com schrieb am Montag, 28. Dezember 2020 um 01:45:46 UTC+1:
>
>> WeeWX supports FTPS, which is FTP over TLS. It does *not* support SFTP, 
>> which uses a Secure Socket Shell protocol. I'm guessing your FTP server 
>> simply does not support FTPS.
>>
>> Can you use rsync? It's better in almost every way.
>>
>> On Sun, Dec 27, 2020 at 1:47 PM 'Stefan Ferber' via weewx-user <
>> weewx...@googlegroups.com> wrote:
>>
>>> Cannot find the defect in my sftp configuration. Could you please check?
>>>
>>> [[SmartphoneReport]]
>>> # The SmartphoneReport uses the 'Smartphone' skin, and the 
>>> images and
>>> # files are placed in a dedicated subdirectory.
>>> skin = Smartphone
>>> enable = true 
>>> HTML_ROOT = /var/www/html/weewx/smartphone
>>>
>>> [[MobileReport]]
>>> # The MobileReport uses the 'Mobile' skin, and the images and 
>>> files
>>> # are placed in a dedicated subdirectory.
>>> skin = Mobile
>>> enable = true 
>>> HTML_ROOT = /var/www/html/weewx/mobile
>>>
>>> [[StandardReport]]
>>> # This is the old "Standard" skin. By default, it is not enabled.
>>> skin = Standard
>>> enable = false
>>>
>>> [[FTP]]
>>> # FTP'ing the results to a webserver is treated as just another 
>>> report,
>>> # albeit one with an unusual report generator!
>>> skin = Ftp
>>>
>>> # If you wish to use FTP, set "enable" to "true", then
>>> # fill out the next four lines.
>>> # Use quotes around passwords to guard against parsing errors.
>>> enable = true 
>>> user =   
>>> password = ""
>>> server = home15604585.1and1-data.host# The ftp server name, 
>>> e.g, www.myserver.org
>>> path = /SmartFerber/weewx# The destination directory, e.g., 
>>> /weather
>>>
>>> # Set to True for an FTP over TLS (FTPS) connection. Not all 
>>> servers
>>> # support this.
>>> secure_ftp = 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 = 22
>>>
>>> # Set to 1 to use passive mode, zero for active mode
>>> passive = 1
>>>
>>> getting multiple errors:
>>>
>>> Dec 27 22:35:51 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>> Generated 8 files for report SeasonsReport in 28.09 seconds
>>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>>> Generated 15 images for report SeasonsReport in 6.71 seconds
>>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>>> 5 files to /var/www/html/weewx
>>> Dec 27 22:36:01 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>> Generated 6 files for report SmartphoneReport in 2.09 seconds
>>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>>> Generated 6 images for report SmartphoneReport in 2.40 seconds
>>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>>> 6 files to /var/www/html/weewx/smartphone
>>> Dec 27 22:36:04 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>>> Generated 1 files for report MobileReport in 0.78 seconds
>>> Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>>> Generated 4 images for report MobileReport in 1.65 seconds
>>> Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>>> 2 files to /var/www/html/weewx/mobile
>>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine: 
>>> ftpgenerator: (0): caught exception '': timed out
>>> Dec 27 22:36:26 raspber

Re: [weewx-user] SFTP upload error ftplib.py

['Stefan Ferber' via weewx-user]

Thx for your quick answer - 100% correct: although my provider IONOS 
supports SFTP and FTPS, looks like my account supports only SFTP.

tke...@gmail.com schrieb am Montag, 28. Dezember 2020 um 01:45:46 UTC+1:

> WeeWX supports FTPS, which is FTP over TLS. It does *not* support SFTP, 
> which uses a Secure Socket Shell protocol. I'm guessing your FTP server 
> simply does not support FTPS.
>
> Can you use rsync? It's better in almost every way.
>
> On Sun, Dec 27, 2020 at 1:47 PM 'Stefan Ferber' via weewx-user <
> weewx...@googlegroups.com> wrote:
>
>> Cannot find the defect in my sftp configuration. Could you please check?
>>
>> [[SmartphoneReport]]
>> # The SmartphoneReport uses the 'Smartphone' skin, and the images 
>> and
>> # files are placed in a dedicated subdirectory.
>> skin = Smartphone
>> enable = true 
>> HTML_ROOT = /var/www/html/weewx/smartphone
>>
>> [[MobileReport]]
>> # The MobileReport uses the 'Mobile' skin, and the images and 
>> files
>> # are placed in a dedicated subdirectory.
>> skin = Mobile
>> enable = true 
>> HTML_ROOT = /var/www/html/weewx/mobile
>>
>> [[StandardReport]]
>> # This is the old "Standard" skin. By default, it is not enabled.
>> skin = Standard
>> enable = false
>>
>> [[FTP]]
>> # FTP'ing the results to a webserver is treated as just another 
>> report,
>> # albeit one with an unusual report generator!
>> skin = Ftp
>>
>> # If you wish to use FTP, set "enable" to "true", then
>> # fill out the next four lines.
>> # Use quotes around passwords to guard against parsing errors.
>> enable = true 
>> user =   
>> password = ""
>> server = home15604585.1and1-data.host# The ftp server name, 
>> e.g, www.myserver.org
>> path = /SmartFerber/weewx# The destination directory, e.g., 
>> /weather
>>
>> # Set to True for an FTP over TLS (FTPS) connection. Not all 
>> servers
>> # support this.
>> secure_ftp = 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 = 22
>>
>> # Set to 1 to use passive mode, zero for active mode
>> passive = 1
>>
>> getting multiple errors:
>>
>> Dec 27 22:35:51 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report SeasonsReport in 28.09 seconds
>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>> Generated 15 images for report SeasonsReport in 6.71 seconds
>> Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>> 5 files to /var/www/html/weewx
>> Dec 27 22:36:01 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>> Generated 6 files for report SmartphoneReport in 2.09 seconds
>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>> Generated 6 images for report SmartphoneReport in 2.40 seconds
>> Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>> 6 files to /var/www/html/weewx/smartphone
>> Dec 27 22:36:04 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
>> Generated 1 files for report MobileReport in 0.78 seconds
>> Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
>> Generated 4 images for report MobileReport in 1.65 seconds
>> Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 
>> 2 files to /var/www/html/weewx/mobile
>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine: 
>> ftpgenerator: (0): caught exception '': timed out
>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
>>    Traceback (most recent call last):
>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
>>    n = ftp_data.run()
>> Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
>>  File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run
>> De

[weewx-user] SFTP upload error ftplib.py

['Stefan Ferber' via weewx-user]

Cannot find the defect in my sftp configuration. Could you please check?

[[SmartphoneReport]]
# The SmartphoneReport uses the 'Smartphone' skin, and the images 
and
# files are placed in a dedicated subdirectory.
skin = Smartphone
enable = true 
HTML_ROOT = /var/www/html/weewx/smartphone

[[MobileReport]]
# The MobileReport uses the 'Mobile' skin, and the images and files
# are placed in a dedicated subdirectory.
skin = Mobile
enable = true 
HTML_ROOT = /var/www/html/weewx/mobile

[[StandardReport]]
# This is the old "Standard" skin. By default, it is not enabled.
skin = Standard
enable = false

[[FTP]]
# FTP'ing the results to a webserver is treated as just another 
report,
# albeit one with an unusual report generator!
skin = Ftp

# If you wish to use FTP, set "enable" to "true", then
# fill out the next four lines.
# Use quotes around passwords to guard against parsing errors.
enable = true 
user =   
password = ""
server = home15604585.1and1-data.host# The ftp server name, 
e.g, www.myserver.org
path = /SmartFerber/weewx# The destination directory, e.g., 
/weather

# Set to True for an FTP over TLS (FTPS) connection. Not all servers
# support this.
secure_ftp = 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 = 22

# Set to 1 to use passive mode, zero for active mode
passive = 1

getting multiple errors:

Dec 27 22:35:51 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
Generated 8 files for report SeasonsReport in 28.09 seconds
Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
Generated 15 images for report SeasonsReport in 6.71 seconds
Dec 27 22:35:58 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 5 
files to /var/www/html/weewx
Dec 27 22:36:01 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
Generated 6 files for report SmartphoneReport in 2.09 seconds
Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
Generated 6 images for report SmartphoneReport in 2.40 seconds
Dec 27 22:36:03 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 6 
files to /var/www/html/weewx/smartphone
Dec 27 22:36:04 raspberrypi weewx[24064] INFO weewx.cheetahgenerator: 
Generated 1 files for report MobileReport in 0.78 seconds
Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.imagegenerator: 
Generated 4 images for report MobileReport in 1.65 seconds
Dec 27 22:36:06 raspberrypi weewx[24064] INFO weewx.reportengine: Copied 2 
files to /var/www/html/weewx/mobile
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine: 
ftpgenerator: (0): caught exception '': timed out
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
   Traceback (most recent call last):
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/share/weewx/weewx/reportengine.py", line 331, in run
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
   n = ftp_data.run()
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/share/weewx/weeutil/ftpupload.py", line 127, in run
Dec 27 22:36:26 raspberrypi weewx[24064] ERROR weewx.reportengine:
   ftp_server.connect(self.server, self.port)
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 155, in connect
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
   self.welcome = self.getresp()
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 236, in getresp
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
   resp = self.getmultiline()
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 226, in getmultiline
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
   nextline = self.getline()
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/ftplib.py", line 204, in getline
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
   line = self.file.readline(self.maxline + 1)
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
 File "/usr/lib/python3.7/socket.py", line 589, in readinto
Dec 27 22:36:27 raspberrypi weewx[24064] ERROR weewx.reportengine:
   return self._sock.recv_into(b)
Dec 27 22:36:27 raspberrypi weewx[24064] 

[weewx-user] Missing channel 5 for TE923 in html-report

['Stefan Ferber' via weewx-user]

Thx for providing WeeWx - really impressed by the ease of installation and 
configuration options. Running for two weeks now ;-)

I have 5 external sensors (temp, humidity, battery status) connected to my 
TE923. WeeWx is fetching the data correctly 
$ sudo wee_device --current
Using configuration file /etc/weewx/weewx.conf
Using TE923 driver version 0.41.1 (weewx.drivers.te923)
Querying the station for current weather data...
dateTime: 1609093626
forecast: 0
 h_1: 64
   h_1_state: ok
 h_2: 38
   h_2_state: ok
 h_3: 41
   h_3_state: ok
 h_4: 47
   h_4_state: ok
 h_5: 37
   h_5_state: ok
h_in: 36
  h_in_state: ok
rain: 3087
  rain_state: ok
 slp: 948.625
   slp_state: ok
   storm: 0
 t_1: 2.7
   t_1_state: ok
 t_2: 22.1
   t_2_state: ok
 t_3: 20.8
   t_3_state: ok
 t_4: 21.6
   t_4_state: ok
 t_5: 20.8
   t_5_state: ok
t_in: 22.85
  t_in_state: ok
  uv: None
uv_state: no_link
   windchill: 1.9
 windchill_state: ok
 winddir: 2
   winddir_state: ok
windgust: 0.0
  windgust_state: ok
   windspeed: 0.0
 windspeed_state: ok

but the last channel 5 is not shown in the temperature graphs.  The mapping 
is a little bit confusing but this graph should show 4 channels but is 
providing only 3 channels. 
[image: daytemp.png]

Therefore, I added a new line for the missing channel "extraTemp4" in the 
weewx.conf 
and change the names to my rooms:

# The labels to be used for each observation type
[[[Labels]]]

# Set to hemisphere abbreviations suitable for your location:
hemispheres = N, S, E, W

# Formats to be used for latitude whole degrees, longitude whole
# degrees, and minutes:
latlon_formats = %02d, %03d, %05.2f

# Generic labels, keyed by an observation type.
Generic
barometer = Barometer
<...>
windvec = Wind Vector
extraTemp1 = Living Room
extraTemp2 = Kitchen
extraTemp3 = Bath
extraTemp4 = Kids Room

But the report still contains only 3 channels. 
[image: daytemp (1).png]


What do I have to do now?


-- 
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/8cd66287-dc9a-45be-9f6d-47848d2c10b3n%40googlegroups.com.

[weewx-user] Re: Error parsing wu-client data

[Stefan Guddat]

Last try, anyone able to help!? Thanks a lot.

Stefan Guddat schrieb am Freitag, 25. September 2020 um 14:50:10 UTC+2:

> Anyone with python knowledge able to help? Thanks
>
> Stefan Guddat schrieb am Dienstag, 22. September 2020 um 23:42:16 UTC+2:
>
>> The last step to have my setup running is fixing the following issue.
>> Anyone any idea?
>>
>> Sep 22 23:04:44 nas weewx[2042] ERROR user.interceptor: parse failed for 
>> ID=IALSDO10&PASSWORD=PASSWORD&indoortempf=80.2&indoorhumidity=40&tempf=59.6&humidity=68&temp8f=80.4&humidity8=46&dewptf=49.0&windchillf=59.6&absbaromin=29.22&baromin=29.84&windspeedmph=0.0&windgustmph=0.0&winddir=256&windspdmph_avg2m=0.0&winddir_avg2m=306&windgustmph_10m=0.4&windgustdir_10m=294&dailyrainin=0.0&weeklyrainin=0.0&monthlyrainin=2.16&solarradiation=0.0&UV=0&dateutc=2020-9-22%2023:4:42&action=updateraw&realtime=1&rtfreq=5&:
>>  
>> dictionary update sequence element #28 has length 1; 2 is required
>>
>> 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/1343eca6-7f31-4077-ad03-a1f242132f8bn%40googlegroups.com.

[weewx-user] Re: Error parsing wu-client data

[Stefan Guddat]

Anyone with python knowledge able to help? Thanks

Stefan Guddat schrieb am Dienstag, 22. September 2020 um 23:42:16 UTC+2:

> The last step to have my setup running is fixing the following issue.
> Anyone any idea?
>
> Sep 22 23:04:44 nas weewx[2042] ERROR user.interceptor: parse failed for 
> ID=IALSDO10&PASSWORD=PASSWORD&indoortempf=80.2&indoorhumidity=40&tempf=59.6&humidity=68&temp8f=80.4&humidity8=46&dewptf=49.0&windchillf=59.6&absbaromin=29.22&baromin=29.84&windspeedmph=0.0&windgustmph=0.0&winddir=256&windspdmph_avg2m=0.0&winddir_avg2m=306&windgustmph_10m=0.4&windgustdir_10m=294&dailyrainin=0.0&weeklyrainin=0.0&monthlyrainin=2.16&solarradiation=0.0&UV=0&dateutc=2020-9-22%2023:4:42&action=updateraw&realtime=1&rtfreq=5&:
>  
> dictionary update sequence element #28 has length 1; 2 is required
>
> 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/cf0fb565-69ff-4755-b131-e39bea8a02b9n%40googlegroups.com.

[weewx-user] Error parsing wu-client data

[Stefan Guddat]

The last step to have my setup running is fixing the following issue.
Anyone any idea?

Sep 22 23:04:44 nas weewx[2042] ERROR user.interceptor: parse failed for 
ID=IALSDO10&PASSWORD=PASSWORD&indoortempf=80.2&indoorhumidity=40&tempf=59.6&humidity=68&temp8f=80.4&humidity8=46&dewptf=49.0&windchillf=59.6&absbaromin=29.22&baromin=29.84&windspeedmph=0.0&windgustmph=0.0&winddir=256&windspdmph_avg2m=0.0&winddir_avg2m=306&windgustmph_10m=0.4&windgustdir_10m=294&dailyrainin=0.0&weeklyrainin=0.0&monthlyrainin=2.16&solarradiation=0.0&UV=0&dateutc=2020-9-22%2023:4:42&action=updateraw&realtime=1&rtfreq=5&:
 
dictionary update sequence element #28 has length 1; 2 is required

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/8101b01a-2d65-48bf-a1d5-5ae1a69a8857n%40googlegroups.com.

[weewx-user] Re: Import of driver failed [Interceptor]

[Stefan Guddat]

What did work for me was using pypcap instead of libpcap. So uninstall the 
recommended "python-libcacp" and install "python-pypcap" instead.

lop...@gmail.com schrieb am Donnerstag, 2. Juli 2020 um 01:26:55 UTC+2:

> Solved by uninstalling python3 and installing 2.7.
>
>
> On Wednesday, July 1, 2020 at 12:06:44 PM UTC+12, Zsolt Máté wrote:
>>
>> Did anyone find a fix for this?
>> I'm in the same boat. Fresh raspberry pi image, clean install.
>>
>> sudo PYTHONPATH=/usr/share/weewx python 
>> /usr/share/weewx/user/interceptor.py --device=observer --mode=sniff 
>> --iface=wlan0 --filter="src 10.3.141.115 and dst port 80"
>> mapped packet: {'barometer': 29.986, 'windchill': 45.5, 'dewpoint': 39.7, 
>> 'pressure': 30.024, 'outHumidity': 77.0, 'UV': 1.0, 'radiation': 105.33, 
>> 'rain': None, 'dateTime': 1593561263, 'windDir': 244.0, 'outTemp': 46.6, 
>> 'windSpeed': 3.4, 'inHumidity': 44.0, 'inTemp': 69.6, 'windGust': 4.5, 
>> 'usUnits': 1}
>>
>>
>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
 Observer.Parser(), handler=Observer.Handler, **stn_dict)
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
   File "/usr/share/weewx/user/interceptor.py", line 427, in __init__
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
 iface, pcap_filter, promiscuous)
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
   File "/usr/share/weewx/user/interceptor.py", line 469, in __init__
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
 self.sniffer.open_live(iface, snaplen, pval, timeout_ms)
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
   File "/usr/lib/python2.7/dist-packages/pcap.py", line 108, in open_live
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
 def open_live(self, *args): return _pcap.pcapObject_open_live(self, 
 *args)
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL weewx.engine:   
 TypeError: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__: Unable to 
 load driver: in method 'pcapObject_open_live', argument 2 of type 'char *'
>>>
>>> Jul  1 12:05:51 raspberrypi weewx[4198] CRITICAL __main__:   
 Exiting...
>>>
>>>
>>>

-- 
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/66fe009d-3b14-4c5e-9123-7bcd5ad090b6n%40googlegroups.com.

Re: [weewx-user] Re: Datenbank zusammen legen.

[Schnidrig Stefan]

Hallo Günther
In welchem Ordner hast du das gelöscht? 




On Sat, Apr 18, 2020 at 5:34 PM +0200, "Günther Wrana"  
wrote:










HelloI deleted the file NOAA-2019-05.txt, NOAA-2019.txt and it worked 
perfectly. For me is now the 01.05.2015 that I imported. The fact that there is 
nothing inside has happened to me even though I have only deleted the NOAA.txt. 
Maybe you have to restart or reload weewx.
Günther
Am Samstag, 18. April 2020 14:56:21 UTC+2 schrieb Meteo Oberwallis:Hello.
I have now deleted the data in the folder "/var/www/html/weewx/NOAA/". These 
came again after the next interval. Unfortunately without data. Do I have to 
delete it anywhere else?
Thank you for your top help

Am Freitag, 17. April 2020 23:42:39 UTC+2 schrieb gjr80:Hallo Günther,



Good to hear you have imported your data and WeeWX is running without error. 
You need WeeWX to recreate all of your NOAA format reports, to do this just 
delete the reports on your WeeWX machine and they will be recreated (including 
your earlier ones) on the next report cycle.



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/8fc609f0-224a-4205-98d4-410a7acc759f%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/2898FBC8D83E6725.70be2414-6650-4943-b430-8ca60e16cb95%40mail.outlook.com.

[weewx-user] Re: wind speed wrong (kph/miles)

[Stefan Pachlina]

Hello,

hmm, i will do following.
1) i will buy a hand-held-windmeter to check windspeed at the current 
position of my weather-sensors ... maybe you are right and the position of 
the windsensor is not perfect.
2) I will move my weatherstation-outsensors to the top of the roof. 
(currently its not at the top, 3m lower, but no slipstream from west, north 
and south)

You should know that I see many kilometers to the mountains.
There is nothing higher in sight (from the west) than my house. So the wind 
loves my roof :D

i am just wondering why all other stations i checked have the same 
"problem".

lets see :)

thx for you help  

Am Sonntag, 8. März 2020 02:50:12 UTC+1 schrieb Cameron D:
>
> Hello Stephan,
> I am still not sure why you think your station was reading 100km/h. I 
> wonder if the following could explain the discrepancy...
>
> If that speed came from official weather reports, then their standard (in 
> many countries) requires that they are measured in open flat areas with the 
> anemometer 10m above ground level.  Wind speed decreases as you get closer 
> to the ground.
>
> Also, the presence of buildings, trees and so on, creates a much more 
> turbulent flow. The wind can have as much energy but lower measured speeds 
> are recorded since vertical components are not normally measured by home 
> instruments.
>
>
> Cameron.
>
>
> On Thursday, 5 March 2020 03:32:24 UTC+10, Stefan Pachlina wrote:
>>
>> Hello,
>>
>> feb 24 2020, it was a stormy day in austria ... but most weatherstations 
>> (weewx-map, wunderground-map) show windspeed like 64kph.
>> but on this day wind speed was ~103kph
>> i have the same problem with my weather-site. 
>> http://wetter.pachlina.net/
>>
>> *i configured weewx.config to see kph:*
>> Groups
>>   
>>   group_speed = km_per_hour
>>   group_speed2 = km_per_hour2
>>   
>>
>> but what i see are miles and not kph.
>> cause if i multiplicate the wind-speed with 1,61 i get the right 
>> wind-speed of 103 kph
>>
>> so what is to do to get the right values?
>> is there something more to do?
>> i read the manual again and again, but i cant find the solution to see 
>> right wind speed.
>> all other values are ok .. like temperature in celsius.
>>
>> and this is what i see on many many weatherstation around austria, 
>> germany  with weewx-map, wunderground, ...
>>
>> h any idea?
>> thx
>>
>> Stefan
>>
>>

-- 
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/f6ee460c-bd4a-42b3-9adb-af70cc51c413%40googlegroups.com.

Re: [weewx-user] wind speed wrong (kph/miles)

[Stefan Pachlina]

Hello,

in austria was a stormwarning of storm "Sabine" by weather-service 
https://warnungen.zamg.at    but yes, we are talking about wind-gust 
~100kph
Heavy roof tiles were dropped from the roof and crashed on the street, etc 
 it was a terrible night.
Cause of that ... wind-gust was greater then 63.7 kph ;)

*so what i see in dB is frustrating:*
2020-02-23 22:01:00|1|13.6453452968298|20.5798650378416
2020-02-23 22:31:00|1|22.8168068897809|39.5938707793257  <-- parts of my 
roof flew away :D
2020-02-23 23:01:00|1|17.4481464451266|27.2906905936595
2020-02-23 23:31:00|1|9.17146159295115|14.5401220376055
2020-02-24 00:01:00|1|14.5401220376055|25.0537487417202
2020-02-24 00:31:00|1|21.2509475934234|34.8962928902531
2020-02-24 01:01:00|1|19.0140057414841|31.0934917419563

are these values the one directly from my weatherstation? unformatted by 
weewx?

i found a very interesting section in weewx.conf an in customers guide.
[[Corrections]]

i think i can do something like that in that section:
windSpeed = windSpeed * 1.61

but i dont undestand what my weatherstation is doing with the windspeed 
hmmmmm

regards
Stefan

Am Mittwoch, 4. März 2020 23:56:55 UTC+1 schrieb Thomas Keffer:
>
> Hello,
>
> Looking through your website, it looks like the max wind you saw was 63.7 
> kph. How do you know it was really 103 kph?
>
> It would also be worth looking in your database. Try this:
>
> *sqlite3 weewx.sdb*
> sqlite> *select datetime(dateTime,'unixepoch','localtime'), usUnits, 
> windSpeed, windGust from archive where dateTime>=1582491600 and 
> dateTime<=1582502400;*
>
> Hopefully, if I got the time zone right, this will print out wind values 
> in your database from 23-feb-2020 2200 to 24-feb-2020 0100 local time.
>
> -tk
>
>
>
> On Wed, Mar 4, 2020 at 9:32 AM Stefan Pachlina  > wrote:
>
>> Hello,
>>
>> feb 24 2020, it was a stormy day in austria ... but most weatherstations 
>> (weewx-map, wunderground-map) show windspeed like 64kph.
>> but on this day wind speed was ~103kph
>> i have the same problem with my weather-site. 
>> http://wetter.pachlina.net/
>>
>> *i configured weewx.config to see kph:*
>> Groups
>>   
>>   group_speed = km_per_hour
>>   group_speed2 = km_per_hour2
>>   
>>
>> but what i see are miles and not kph.
>> cause if i multiplicate the wind-speed with 1,61 i get the right 
>> wind-speed of 103 kph
>>
>> so what is to do to get the right values?
>> is there something more to do?
>> i read the manual again and again, but i cant find the solution to see 
>> right wind speed.
>> all other values are ok .. like temperature in celsius.
>>
>> and this is what i see on many many weatherstation around austria, 
>> germany  with weewx-map, wunderground, ...
>>
>> h any idea?
>> thx
>>
>> Stefan
>>
>> -- 
>> 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...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/298dc427-566d-481b-ba62-94b571cb8ea9%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/weewx-user/298dc427-566d-481b-ba62-94b571cb8ea9%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/614b154e-d937-4d10-b0e0-96f0d1764aef%40googlegroups.com.

[weewx-user] wind speed wrong (kph/miles)

[Stefan Pachlina]

Hello,

feb 24 2020, it was a stormy day in austria ... but most weatherstations 
(weewx-map, wunderground-map) show windspeed like 64kph.
but on this day wind speed was ~103kph
i have the same problem with my weather-site. 
http://wetter.pachlina.net/

*i configured weewx.config to see kph:*
Groups
  
  group_speed = km_per_hour
  group_speed2 = km_per_hour2
  

but what i see are miles and not kph.
cause if i multiplicate the wind-speed with 1,61 i get the right wind-speed 
of 103 kph

so what is to do to get the right values?
is there something more to do?
i read the manual again and again, but i cant find the solution to see 
right wind speed.
all other values are ok .. like temperature in celsius.

and this is what i see on many many weatherstation around austria, germany 
 with weewx-map, wunderground, ...

h any idea?
thx

Stefan

-- 
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/298dc427-566d-481b-ba62-94b571cb8ea9%40googlegroups.com.

Re: [weewx-user] Re: **** Expected to read 99 chars; got 0 instead

[Stefan]

Hello.

I have this Problem

Feb 24 07:45:19 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Initializing weewx version 
3.9.2
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Using Python 2.7.16 
(default, Oct 10 2019, 22:02:15) #012[GCC 8.3.0]
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Platform 
Linux-4.19.97-v7+-armv7l-with-debian-10.3
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Locale is 'de_CH.UTF-8'
Feb 24 07:45:20 raspberrypi weewx[669]: engine: pid file is 
/var/run/weewx.pid
Feb 24 07:45:20 raspberrypi weewx[658]: Starting weewx weather system: 
weewx.
Feb 24 07:45:20 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using configuration file 
/etc/weewx/weewx.conf
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Debug is 1
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Initializing engine
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Driver version is 3.1.1
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Gentle wake up of console 
successful
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware type is 16
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: ISS ID is 1
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware name: Vantage Pro2
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdTimeSynch
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdConvert
Feb 24 07:45:20 raspberrypi weewx[673]: engine: StdConvert target unit is 
0x1
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdConvert
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdCalibrate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdCalibrate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdQC
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdQC
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
user.radiationhours.RadiationHours
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
user.radiationhours.RadiationHours
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdArchive
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Archive will use data 
binding wx_binding
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Record generation will be 
attempted in 'hardware'
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using archive interval of 
300 seconds (specified by hardware)
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Use LOOP data in hi/low 
calculations: 1
Feb 24 07:45:20 raspberrypi weewx[673]: manager: Daily summary version is 
2.0
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb_new'
Feb 24 07:45:20 raspberrypi weewx[673]: manager: Starting backfill of daily 
summaries
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdArchive
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdStationRegistry
Feb 24 07:45:20 raspberrypi weewx[673]: restx: StationRegistry: 
Registration not requested.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdWunderground
Feb 24 07:45:20 raspberrypi weewx[673]: restx: Wunderground: Posting not 
enabled.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.restx.StdWunderground
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdPWSweather
Feb 24 07:45:20 raspberrypi weewx[673]: restx: PWSweather: Posting not 
enabled.
Feb 24 07:45:20 raspberrypi weewx[673]: engine:

Re: [weewx-user] Re: **** Expected to read 99 chars; got 0 instead

[Stefan]

Hello.

I have this Problem

Feb 24 07:45:19 raspberrypi systemd[1]: Starting LSB: weewx weather 
system...
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Initializing weewx version 
3.9.2
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Using Python 2.7.16 
(default, Oct 10 2019, 22:02:15) #012[GCC 8.3.0]
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Platform 
Linux-4.19.97-v7+-armv7l-with-debian-10.3
Feb 24 07:45:20 raspberrypi weewx[669]: engine: Locale is 'de_CH.UTF-8'
Feb 24 07:45:20 raspberrypi weewx[669]: engine: pid file is 
/var/run/weewx.pid
Feb 24 07:45:20 raspberrypi weewx[658]: Starting weewx weather system: 
weewx.
Feb 24 07:45:20 raspberrypi systemd[1]: Started LSB: weewx weather system.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using configuration file 
/etc/weewx/weewx.conf
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Debug is 1
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Initializing engine
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading station type 
Vantage (weewx.drivers.vantage)
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Driver version is 3.1.1
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Gentle wake up of console 
successful
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware type is 16
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: ISS ID is 1
Feb 24 07:45:20 raspberrypi weewx[673]: vantage: Hardware name: Vantage Pro2
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdTimeSynch
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdConvert
Feb 24 07:45:20 raspberrypi weewx[673]: engine: StdConvert target unit is 
0x1
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdConvert
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdCalibrate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdCalibrate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdQC
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdQC
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following values 
will be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, 
rainRate=prefer_hardware, windrun=prefer_hardware, 
heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Feb 24 07:45:20 raspberrypi weewx[673]: wxcalculate: The following 
algorithms will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
user.radiationhours.RadiationHours
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
user.radiationhours.RadiationHours
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.engine.StdArchive
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Archive will use data 
binding wx_binding
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Record generation will be 
attempted in 'hardware'
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using archive interval of 
300 seconds (specified by hardware)
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Use LOOP data in hi/low 
calculations: 1
Feb 24 07:45:20 raspberrypi weewx[673]: manager: Daily summary version is 
2.0
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Using binding 'wx_binding' 
to database 'weewx.sdb_new'
Feb 24 07:45:20 raspberrypi weewx[673]: manager: Starting backfill of daily 
summaries
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.engine.StdArchive
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdStationRegistry
Feb 24 07:45:20 raspberrypi weewx[673]: restx: StationRegistry: 
Registration not requested.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.restx.StdStationRegistry
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdWunderground
Feb 24 07:45:20 raspberrypi weewx[673]: restx: Wunderground: Posting not 
enabled.
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Finished loading service 
weewx.restx.StdWunderground
Feb 24 07:45:20 raspberrypi weewx[673]: engine: Loading service 
weewx.restx.StdPWSweather
Feb 24 07:45:20 raspberrypi weewx[673]: restx: PWSweather: Posting not 
enabled.
Feb 24 07:45:20 raspberrypi weewx[673]: engine:

[weewx-user] Re: Display rainrate in mm/h not mm/hr

[Stefan]

Hallo Geni.

Ich habe deine Mailadresse gesucht und leider nicht gefunden. Kannst du mir 
diese bitte mal zukommen lassen?

Danke und Gruss aus der Schweiz. Meteo Oberwallis Stefan 
(i...@meteo-oberwallis.ch)

Am Sonntag, 29. Dezember 2019 16:05:12 UTC+1 schrieb Geni:
>
> Hello, 
>
> i use weewx 3.9.2 on a raspberry 3+ with a mysql database, the template is 
> season.
> unfortunately since switching to a new raspberry the rainrate is displayed 
> with xx mm/hr but i want mm/h.
> What do I have to change so that the rain rate is displayed in mm/h?
>
> Thanks, Geni
>
> Livesite is https://affolter.familyds.net/wetter/index.html
>

-- 
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/189922cc-3963-45d9-9b00-63ffb91723a9%40googlegroups.com.

[weewx-user] Re: Sunshine Time

[Stefan]

Hello everybody
I have a question about graphic design. I would like to include the sunshine 
time in the graphics. Currently the value of 0.08 in sunshine always appears 
there. This is my current code in use.
[[chart6]]
title = Sonnenschein
# Make sure the y-axis increment is at least 0.02 for the sun plot
yscale = 0.0, 1.0, 0.1
type = column
[[[sunshine_hours]]]
aggregate_type = sum
aggregate_interval = 300
color = "#e4d354"
name = Sonnenschein in Minuten

[image: Unbenannt.PNG]



I would like to do this now, because the interval 300s is 5min as sunshine. Can 
one make it like this?

Many thanks for your help




Am Montag, 22. Juli 2019 11:50:28 UTC+2 schrieb Stefan:
>
> Hello everybody.
>
> I have found this link (
> https://github.com/brewster76/util-archer/blob/master/user/radiationhours.py) 
> where is described how to display the sunshine time. Now I would like to 
> show this value in numbers (eg 4:15 h). Is that possible?
>
> 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/38847624-7a27-4899-a03d-f1b6f92652d3%40googlegroups.com.