Re: [weewx-user] Re: Forecast Extension and Python 3

[Arne Berglund]

Happy to try it. Works fine, until I take the final step to add the 
ForecastVariables to the CheetahGenerator block. As soon as I do that it 
starts skipping index.html.tmpl with the errors posted above. Still 
complaining about a type error.

FWIW, the server is the latest update of CentOS 8, with Python 3.6.8. I'm 
using MySQL, not SQLite.


On Saturday, July 18, 2020 at 8:40:58 PM UTC-7, John Kline wrote:
>
> I got it working.  There were no changes to forecasting.
>
> exfoliation was not updated for WeeWX4/Py3.
> You are welcome to give it a try:
> https://github.com/chaunceygardiner/weewx-exfoliation
> If you are not up for it, that’s fine too.
>
> On Jul 18, 2020, at 8:16 PM, Arne Berglund  > wrote:
>
> 
> Thanks for checking, John. I'd like to have forecasting, but really don't 
> want to have to find and tweak a new skin.
>
> On Saturday, July 18, 2020 at 7:40:36 PM UTC-7, John Kline wrote:
>>
>> I found it.
>>
>> I get errors without adding ForecastVariables.  I’ll have a quick further 
>> look.
>>
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator:  Ignoring template 
>> /home/weewx/skins/exfoliation/index.html.tmpl 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
>> 'str' and 'int'  
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator:   Traceback (most recent call last):   
>>   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 321, in generate 
>>  
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator:   unicode_string = 
>> compiled_template.respond()   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator: File 
>> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in respond   
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator: File 
>> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in 
>> __errorCatcher43   
>> 
>>   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator: File "", line 1, in
>>   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator: File 
>> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in 
>> get_windspeed_trend 
>> 
>>  
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
>> weewx.cheetahgenerator:   TypeError: '>' not supported between 
>> instances of 'str' and 'int'  
>> Jul 18 19:34:07 judygirldog wee_reports[18730] INFO 
>> weewx.cheetahgenerator: Generated 8 files for report exfoliation in 3.22 
>> seconds  
>> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.imagegenerator: 
>> Generated 68 images for report exfoliation in 11.41 seconds 
>> 
>> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.reportengine: 
>> Copied 92 files to /home/weewx/public_html/exfoliation 
>>
>>
>>
>>
>> On Jul 18, 2020, at 7:26 PM, John Kline  wrote:
>>
>> 
>> Do you see the forecast reports?
>>
>> Where did you get exfoliation 0.45?
>> Is it WeeWX 4 compatible?  If it is, I’ll give it a try.
>>
>> On Jul 18, 2020, at 7:18 PM, Arne Berglund  wrote:
>>
>> 
>> Thanks for that link. Unfortunately, it still gives an error.
>>
>> Everything seems to work fine, until I add the search_list_extensions 
>> into skin.conf (using exfoliation 0.45).
>>
>> When I add the third line here:
>>
>> [CheetahGenerator]
>> encoding = html_entities
>> search_list_extensions = user.forecast.ForecastVariables
>>
>> I get the following error in the log:
>>
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
>> cheetahgenerator: Generate failed with exception ''
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
>> cheetahgenerator:  Ignoring template /etc/weewx/skins/exfoliation/
>> index.html.tmpl
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
>> cheetahgenerator:  Reason: '>' not supported between instances of 
>> 'NoneType' and 'int'
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
>> cheetahgenerator:   Traceback (most recent call 

Re: [weewx-user] Re: Forecast Extension and Python 3

[John Kline]

I got it working.  There were no changes to forecasting.

exfoliation was not updated for WeeWX4/Py3.
You are welcome to give it a try:
https://github.com/chaunceygardiner/weewx-exfoliation
If you are not up for it, that’s fine too.

> On Jul 18, 2020, at 8:16 PM, Arne Berglund  wrote:
> 
> 
> Thanks for checking, John. I'd like to have forecasting, but really don't 
> want to have to find and tweak a new skin.
> 
>> On Saturday, July 18, 2020 at 7:40:36 PM UTC-7, John Kline wrote:
>> I found it.
>> 
>> I get errors without adding ForecastVariables.  I’ll have a quick further 
>> look.
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>>  Ignoring template /home/weewx/skins/exfoliation/index.html.tmpl 
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>>  Reason: '>' not supported between instances of 'str' and 'int'  
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>>   Traceback (most recent call last): 
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>> File "/home/weewx/bin/weewx/cheetahgenerator.py", line 321, in 
>> generate  
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>>   unicode_string = compiled_template.respond()   
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, 
>> in respond   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, 
>> in __errorCatcher43  
>>  
>>   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>> File "", line 1, in  
>> 
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>> File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, 
>> in get_windspeed_trend   
>>  
>>   
>> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
>>   TypeError: '>' not supported between instances of 'str' and 'int'  
>> 
>> Jul 18 19:34:07 judygirldog wee_reports[18730] INFO weewx.cheetahgenerator: 
>> Generated 8 files for report exfoliation in 3.22 seconds 
>>  
>> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.imagegenerator: 
>> Generated 68 images for report exfoliation in 11.41 seconds  
>>
>> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.reportengine: 
>> Copied 92 files to /home/weewx/public_html/exfoliation   
>>  
>> 
>> 
>> 
 On Jul 18, 2020, at 7:26 PM, John Kline  wrote:
 
>>> 
>>> Do you see the forecast reports?
>>> 
>>> Where did you get exfoliation 0.45?
>>> Is it WeeWX 4 compatible?  If it is, I’ll give it a try.
>>> 
> On Jul 18, 2020, at 7:18 PM, Arne Berglund  wrote:
> 
 
 Thanks for that link. Unfortunately, it still gives an error.
 
 Everything seems to work fine, until I add the search_list_extensions into 
 skin.conf (using exfoliation 0.45).
 
 When I add the third line here:
 
 [CheetahGenerator]
 encoding = html_entities
 search_list_extensions = user.forecast.ForecastVariables
 
 I get the following error in the log:
 
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator: Generate failed with exception '>>> 'TypeError'>'
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator:  Ignoring template 
 /etc/weewx/skins/exfoliation/index.html.tmpl
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator:  Reason: '>' not supported between instances 
 of 'NoneType' and 'int'
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator:   Traceback (most recent call last):
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator: File 
 "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
 Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
 weewx.cheetahgenerator:   unicode_string = 
 compiled_template.respond()
 

Re: [weewx-user] Re: Forecast Extension and Python 3

[Arne Berglund]

Thanks for checking, John. I'd like to have forecasting, but really don't 
want to have to find and tweak a new skin.

On Saturday, July 18, 2020 at 7:40:36 PM UTC-7, John Kline wrote:
>
> I found it.
>
> I get errors without adding ForecastVariables.  I’ll have a quick further 
> look.
>
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /home/weewx/skins/exfoliation/index.html.tmpl 
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
> 'str' and 'int'  
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator:   Traceback (most recent call last):   
>   
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator: File 
> "/home/weewx/bin/weewx/cheetahgenerator.py", line 321, in generate 
>  
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator:   unicode_string = 
> compiled_template.respond()   
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in respond   
> 
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in 
> __errorCatcher43   
> 
>   
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator: File "", line 1, in
>   
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator: File 
> "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in 
> get_windspeed_trend 
> 
>  
> Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR 
> weewx.cheetahgenerator:   TypeError: '>' not supported between 
> instances of 'str' and 'int'  
> Jul 18 19:34:07 judygirldog wee_reports[18730] INFO 
> weewx.cheetahgenerator: Generated 8 files for report exfoliation in 3.22 
> seconds  
> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.imagegenerator: 
> Generated 68 images for report exfoliation in 11.41 seconds 
> 
> Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.reportengine: 
> Copied 92 files to /home/weewx/public_html/exfoliation 
>
>
>
>
> On Jul 18, 2020, at 7:26 PM, John Kline > 
> wrote:
>
> 
> Do you see the forecast reports?
>
> Where did you get exfoliation 0.45?
> Is it WeeWX 4 compatible?  If it is, I’ll give it a try.
>
> On Jul 18, 2020, at 7:18 PM, Arne Berglund  > wrote:
>
> 
> Thanks for that link. Unfortunately, it still gives an error.
>
> Everything seems to work fine, until I add the search_list_extensions into 
> skin.conf (using exfoliation 0.45).
>
> When I add the third line here:
>
> [CheetahGenerator]
> encoding = html_entities
> search_list_extensions = user.forecast.ForecastVariables
>
> I get the following error in the log:
>
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator: Generate failed with exception ''
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator:  Ignoring template /etc/weewx/skins/exfoliation/
> index.html.tmpl
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator:  Reason: '>' not supported between instances of 
> 'NoneType' and 'int'
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator:   Traceback (most recent call last):
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator:   unicode_string = compiled_template.respond()
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator: File 
> "_etc_weewx_skins_exfoliation_index_html_tmpl.py", line 1092, in respond
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
> cheetahgenerator:   TypeError: '>' not supported between instances of 
> 'NoneType' and 'int'
>
> Have I done something boneheaded?
>
> -- 
> You received this message because you are subscribed to the Google Groups 
> "weewx-user" 

Re: [weewx-user] Re: Forecast Extension and Python 3

[John Kline]

I found it.

I get errors without adding ForecastVariables.  I’ll have a quick further look.

Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
 Ignoring template /home/weewx/skins/exfoliation/index.html.tmpl
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
 Reason: '>' not supported between instances of 'str' and 'int' 
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
  Traceback (most recent call last):
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
File "/home/weewx/bin/weewx/cheetahgenerator.py", line 321, in generate 
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
  unicode_string = compiled_template.respond()  
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 1292, in 
respond   
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 497, in 
__errorCatcher43

 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
File "", line 1, in 
 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
File "_home_weewx_skins_exfoliation_index_html_tmpl.py", line 187, in 
get_windspeed_trend 

 
Jul 18 19:34:05 judygirldog wee_reports[18730] ERROR weewx.cheetahgenerator: 
  TypeError: '>' not supported between instances of 'str' and 'int' 
 
Jul 18 19:34:07 judygirldog wee_reports[18730] INFO weewx.cheetahgenerator: 
Generated 8 files for report exfoliation in 3.22 seconds
  
Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.imagegenerator: 
Generated 68 images for report exfoliation in 11.41 seconds 

Jul 18 19:34:19 judygirldog wee_reports[18730] INFO weewx.reportengine: Copied 
92 files to /home/weewx/public_html/exfoliation 
   



> On Jul 18, 2020, at 7:26 PM, John Kline  wrote:
> 
> 
> Do you see the forecast reports?
> 
> Where did you get exfoliation 0.45?
> Is it WeeWX 4 compatible?  If it is, I’ll give it a try.
> 
>>> On Jul 18, 2020, at 7:18 PM, Arne Berglund  
>>> wrote:
>>> 
>> 
>> Thanks for that link. Unfortunately, it still gives an error.
>> 
>> Everything seems to work fine, until I add the search_list_extensions into 
>> skin.conf (using exfoliation 0.45).
>> 
>> When I add the third line here:
>> 
>> [CheetahGenerator]
>> encoding = html_entities
>> search_list_extensions = user.forecast.ForecastVariables
>> 
>> I get the following error in the log:
>> 
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator: Generate failed with exception ''
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator:  Ignoring template 
>> /etc/weewx/skins/exfoliation/index.html.tmpl
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
>> 'NoneType' and 'int'
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator:   Traceback (most recent call last):
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator:   unicode_string = 
>> compiled_template.respond()
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator: File 
>> "_etc_weewx_skins_exfoliation_index_html_tmpl.py", line 1092, in respond
>> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
>> weewx.cheetahgenerator:   TypeError: '>' not supported between instances 
>> of 'NoneType' and 'int'
>> 
>> Have I done something boneheaded?
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit 
>> 

Re: [weewx-user] Re: Forecast Extension and Python 3

[John Kline]

Do you see the forecast reports?

Where did you get exfoliation 0.45?
Is it WeeWX 4 compatible?  If it is, I’ll give it a try.

> On Jul 18, 2020, at 7:18 PM, Arne Berglund  wrote:
> 
> 
> Thanks for that link. Unfortunately, it still gives an error.
> 
> Everything seems to work fine, until I add the search_list_extensions into 
> skin.conf (using exfoliation 0.45).
> 
> When I add the third line here:
> 
> [CheetahGenerator]
> encoding = html_entities
> search_list_extensions = user.forecast.ForecastVariables
> 
> I get the following error in the log:
> 
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator: Generate failed with exception ''
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator:  Ignoring template 
> /etc/weewx/skins/exfoliation/index.html.tmpl
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator:  Reason: '>' not supported between instances of 
> 'NoneType' and 'int'
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator:   Traceback (most recent call last):
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 322, in generate
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator:   unicode_string = compiled_template.respond()
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator: File 
> "_etc_weewx_skins_exfoliation_index_html_tmpl.py", line 1092, in respond
> Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR 
> weewx.cheetahgenerator:   TypeError: '>' not supported between instances 
> of 'NoneType' and 'int'
> 
> Have I done something boneheaded?
> -- 
> 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/b484de7a-7d6c-4697-aa06-5be860f51354o%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/65DC0E8A-BEDD-4AC0-8E4B-60BFB1A362DF%40johnkline.com.

Re: [weewx-user] Re: Forecast Extension and Python 3

[Arne Berglund]

Thanks for that link. Unfortunately, it still gives an error.

Everything seems to work fine, until I add the search_list_extensions into 
skin.conf (using exfoliation 0.45).

When I add the third line here:

[CheetahGenerator]
encoding = html_entities
search_list_extensions = user.forecast.ForecastVariables

I get the following error in the log:

Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator: Generate failed with exception ''
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator:  Ignoring template /etc/weewx/skins/exfoliation/index.
html.tmpl
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator:  Reason: '>' not supported between instances of 
'NoneType' and 'int'
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator:   Traceback (most recent call last):
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator: File "/usr/share/weewx/weewx/cheetahgenerator.py", 
line 322, in generate
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator:   unicode_string = compiled_template.respond()
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator: File 
"_etc_weewx_skins_exfoliation_index_html_tmpl.py", line 1092, in respond
Jul 18 19:11:18 localhost journal[14057]: weewx[14057] ERROR weewx.
cheetahgenerator:   TypeError: '>' not supported between instances of 
'NoneType' and 'int'

Have I done something boneheaded?

-- 
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/b484de7a-7d6c-4697-aa06-5be860f51354o%40googlegroups.com.

Re: [weewx-user] upgrade from v1.12.1: stats only generated for past ~week

[Tom Keffer]

Just delete all the plots. WeeWX will regenerate them all at the next
reporting cycle.

Yes, the archive data is used for plots, unless the aggregation interval is
one day, in which case the daily summaries are used.

Yes, inDewpoint is a derived value. Write an xtypes extension
 for it
and StdWXCalculate can calculate it.

-tk



On Sat, Jul 18, 2020 at 6:36 PM Jason Rennie  wrote:

> I know! I guess weewx worked so well that I almost never needed to spend
> any time on it!
>
> I was seeing month and year plots that only had a ~week of data, but now
> that I look at the archive_day_outTemp table, I see data going back at
> least a year. And, now the month plots are fully populated and I realize
> the plots are probably based on the raw data rather than the daily stats.
> The year plots still only have a ~week of data, but I know those are
> regenerated much less often, so I'm guessing I'll see new plots tomorrow.
> So, I suspect this was a false alarm and nothing is wrong. I should have
> investigated a bit more :)
>
> But, while I've got your attention, you might remember that I like to keep
> track of indoor dewpoint. I've got it working for including values in html
> (using "inDewpoint" in the templates). But, plot generation when I try to
> use "inDewpoint" in skin.conf for the daytempin plot. It looks
> like inDewpoint is a generated value. Can plots use inDewpoint?
>
> Thanks,
>
> Jason
>
> On Saturday, July 18, 2020 at 9:00:58 PM UTC-4 tke...@gmail.com wrote:
>
>> Hello, Jason! Have not heard from you in years!
>>
>> The "backfill" process should do the entire database, not just a year.
>> What symptoms are you seeing?
>>
>> On Sat, Jul 18, 2020 at 5:48 PM Jason Rennie  wrote:
>>
>>> I'm amazed that the upgrade mostly worked flawlessly. I installed 4.1.1
>>> via the Deb/Ubuntu package after realizing that Ubuntu 20.04 no longer
>>> supports v2 python libraries. Tom, I'm impressed! Just had to copy
>>> weewx.sdb to /var/lib/weewx and make some minor config tweaks. Plots look
>>> great for day and week, but month/year appear to be missing data. I see
>>> that the stats tables are now part of weewx.sdb. During startup, it spent a
>>> few minutes "generating stats" and I see the new tables in weewx.sdb. Is
>>> there a way to tell it to go back further and generate, say, a year of
>>> stats?
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>> --
>>> 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/CA%2BPf4UBs5k4bkugsewv3_LTc%3Dd74YRhX0ANpmab-4CEBnPp5Ug%40mail.gmail.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/7bf1e090-c097-47c0-a3aa-95e136cen%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/CAPq0zEDncM5RpR8A99e7WQExjJGr7Md5voks2HJKqx6RCg5vtQ%40mail.gmail.com.

Re: [weewx-user] Re: Forecast Extension and Python 3

[John Kline]

https://github.com/chaunceygardiner/weewx-forecast

Let me know if you have any issues.

>> On Jul 18, 2020, at 6:15 PM, Arne Berglund  wrote:
> 
> I've run into this with a server rebuild now as well, but I'm not finding a 
> link to the other branch of the forecast extension. I've used this one:
> 
> https://github.com/weewx/weewx/wiki/forecasting
> 
> But it is the one that fails. Can someone point me to the other branch please?
> -- 
> 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/8b32cbed-cf17-4345-9a47-415c9561d563o%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/1CE197BA-A29E-48D2-A075-789378A49431%40johnkline.com.

Re: [weewx-user] upgrade from v1.12.1: stats only generated for past ~week

[Jason Rennie]

I know! I guess weewx worked so well that I almost never needed to spend 
any time on it!

I was seeing month and year plots that only had a ~week of data, but now 
that I look at the archive_day_outTemp table, I see data going back at 
least a year. And, now the month plots are fully populated and I realize 
the plots are probably based on the raw data rather than the daily stats. 
The year plots still only have a ~week of data, but I know those are 
regenerated much less often, so I'm guessing I'll see new plots tomorrow. 
So, I suspect this was a false alarm and nothing is wrong. I should have 
investigated a bit more :)

But, while I've got your attention, you might remember that I like to keep 
track of indoor dewpoint. I've got it working for including values in html 
(using "inDewpoint" in the templates). But, plot generation when I try to 
use "inDewpoint" in skin.conf for the daytempin plot. It looks 
like inDewpoint is a generated value. Can plots use inDewpoint?

Thanks,

Jason

On Saturday, July 18, 2020 at 9:00:58 PM UTC-4 tke...@gmail.com wrote:

> Hello, Jason! Have not heard from you in years!
>
> The "backfill" process should do the entire database, not just a year. 
> What symptoms are you seeing?
>
> On Sat, Jul 18, 2020 at 5:48 PM Jason Rennie  wrote:
>
>> I'm amazed that the upgrade mostly worked flawlessly. I installed 4.1.1 
>> via the Deb/Ubuntu package after realizing that Ubuntu 20.04 no longer 
>> supports v2 python libraries. Tom, I'm impressed! Just had to copy 
>> weewx.sdb to /var/lib/weewx and make some minor config tweaks. Plots look 
>> great for day and week, but month/year appear to be missing data. I see 
>> that the stats tables are now part of weewx.sdb. During startup, it spent a 
>> few minutes "generating stats" and I see the new tables in weewx.sdb. Is 
>> there a way to tell it to go back further and generate, say, a year of 
>> stats?
>>
>> Thanks,
>>
>> Jason
>>
>> -- 
>> 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/CA%2BPf4UBs5k4bkugsewv3_LTc%3Dd74YRhX0ANpmab-4CEBnPp5Ug%40mail.gmail.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/7bf1e090-c097-47c0-a3aa-95e136cen%40googlegroups.com.

[weewx-user] Re: Forecast Extension and Python 3

[Arne Berglund]

I've run into this with a server rebuild now as well, but I'm not finding a 
link to the other branch of the forecast extension. I've used this one:

https://github.com/weewx/weewx/wiki/forecasting

But it is the one that fails. Can someone point me to the other branch 
please?

-- 
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/8b32cbed-cf17-4345-9a47-415c9561d563o%40googlegroups.com.

Re: [weewx-user] upgrade from v1.12.1: stats only generated for past ~week

[Tom Keffer]

Hello, Jason! Have not heard from you in years!

The "backfill" process should do the entire database, not just a year. What
symptoms are you seeing?

On Sat, Jul 18, 2020 at 5:48 PM Jason Rennie  wrote:

> I'm amazed that the upgrade mostly worked flawlessly. I installed 4.1.1
> via the Deb/Ubuntu package after realizing that Ubuntu 20.04 no longer
> supports v2 python libraries. Tom, I'm impressed! Just had to copy
> weewx.sdb to /var/lib/weewx and make some minor config tweaks. Plots look
> great for day and week, but month/year appear to be missing data. I see
> that the stats tables are now part of weewx.sdb. During startup, it spent a
> few minutes "generating stats" and I see the new tables in weewx.sdb. Is
> there a way to tell it to go back further and generate, say, a year of
> stats?
>
> Thanks,
>
> Jason
>
> --
> 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/CA%2BPf4UBs5k4bkugsewv3_LTc%3Dd74YRhX0ANpmab-4CEBnPp5Ug%40mail.gmail.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/CAPq0zEDzwK4NCq0jm9oFNfSkQkO-sKg%3D5KFQU9cB7UoQcn1E0A%40mail.gmail.com.

[weewx-user] upgrade from v1.12.1: stats only generated for past ~week

[Jason Rennie]

I'm amazed that the upgrade mostly worked flawlessly. I installed 4.1.1 via
the Deb/Ubuntu package after realizing that Ubuntu 20.04 no longer supports
v2 python libraries. Tom, I'm impressed! Just had to copy weewx.sdb to
/var/lib/weewx and make some minor config tweaks. Plots look great for day
and week, but month/year appear to be missing data. I see that the stats
tables are now part of weewx.sdb. During startup, it spent a few minutes
"generating stats" and I see the new tables in weewx.sdb. Is there a way to
tell it to go back further and generate, say, a year of stats?

Thanks,

Jason

-- 
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/CA%2BPf4UBs5k4bkugsewv3_LTc%3Dd74YRhX0ANpmab-4CEBnPp5Ug%40mail.gmail.com.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Greg from Oz]

WOW..I MUST be an expert hhaha.
Glad it works.
I don't have raspberry but I took that code from my Ubuntu server, so I 
guess it would work.
I run proxmox and 5 virtual machines on a Dell  r210 ii and it only draws 
35 watts.


On Sunday, 19 July 2020 at 00:38:13 UTC+10 Michael Grossie wrote:

> Greg - works like a charm - thanks for the advice and for explaining -
>
>  
>  
> Michael H Grossie
> mhgr...@sbcglobal.net
>
>
> On Sat, Jul 18, 2020 at 5:55 AM Greg from Oz  wrote:
>
>> Maybe if you create a weewx.conf file in /etc/apache2/sites-available and 
>> call it weewx.conf
>>
>> Put this in the file:
>>
>> Alias /weewx "/home/weewx/public_html"
>> 
>> Options Indexes MultiViews
>> AllowOverride None
>> Order allow,deny
>> Allow from all
>> Require all granted
>> 
>>
>> Save the file.
>>
>>  Then run sudo a2ensite weewx.conf   (this enables the site)
>>
>> Then reload apache
>>
>> Then go to http://localhost/weewx
>>
>> I am not an expert either and don't have a raspbaerry pi running apache.
>>
>> Good luck. I don't guarantee this will work but hey! you never know. 
>>
>>
>> On Saturday, 18 July 2020 at 12:33:05 UTC+10 Michael Grossie wrote:
>>
>>> I have found the index.html file in /home/weewx/public_html. I still 
>>> cannot access it with http://localhost/weewx - I need to use the full 
>>> path - but I can get to it and it does show data.
>>>  
>>> Michael H Grossie
>>> mhgr...@sbcglobal.net
>>>
>>>
>>> On Mon, Jul 13, 2020 at 12:49 PM Michael Grossie  
>>> wrote:
>>>
 Installed sqlitebrowser. Opened weewx.sdb and did see records had been 
 created. So, why does it not write to "weewx/public_html?"
  
  
 Michael H Grossie
 mhgr...@sbcglobal.net


 On Mon, Jul 13, 2020 at 12:30 PM Michael Grossie  
 wrote:

> After reloading cheetah, I rebooted, started weewx and apache2. I 
> opened a browser and went to http://localhost/weewx (as directed in 
> the User Guide) and received the 404 page not found error.
>
> I then ran "sudo /etc/init.d/weewx status -l"  and received -
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *pi@raspberrypi:/home/weewx $ sudo /etc/init.d/weewx status -l● 
> weewx.service - LSB: weewx weather system   Loaded: loaded 
> (/etc/init.d/weewx; generated; vendor preset: enabled)   Active: active 
> (running) since Mon 2020-07-13 12:03:01 CDT; 18min ago Docs: 
> man:systemd-sysv-generator(8)  Process: 281 ExecStart=/etc/init.d/weewx 
> start (code=exited, status=0/SUCCESS)Tasks: 2 (limit: 4915)   CGroup: 
> /system.slice/weewx.service   └─497 /usr/bin/python2 
> /home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid 
> /home/weewx/weewx.confJul 13 12:15:16 raspberrypi weewxd[497]: weewx[497] 
> INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to 
> database 'weewx.sdb'Jul 13 12:15:16 raspberrypi weewxd[497]: weewx[497] 
> INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to 
> daily summary …weewx.sdb'Jul 13 12:15:21 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report 
> SeasonsReport in 3.39 secondsJul 13 12:15:25 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.imagegenerator: Generated 15 images for report 
> SeasonsReport in 3.65 secondsJul 13 12:15:25 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.reportengine: Copied 0 files to 
> /home/weewx/public_htmlJul 13 12:20:16 raspberrypi weewxd[497]: 
> weewx[497] 
> INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to 
> database 'weewx.sdb'Jul 13 12:20:16 raspberrypi weewxd[497]: weewx[497] 
> INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to 
> daily summary …weewx.sdb'Jul 13 12:20:21 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report 
> SeasonsReport in 3.79 secondsJul 13 12:20:34 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.imagegenerator: Generated 30 images for report 
> SeasonsReport in 12.33 secondsJul 13 12:20:34 raspberrypi weewxd[497]: 
> weewx[497] INFO weewx.reportengine: Copied 0 files to 
> /home/weewx/public_htmlHint: Some lines were ellipsized, use -l to show 
> in 
> full.*
>  
> Now I see that records were added and reports generated, but nothing 
> transferred to /home/weewx/public_html
> I am still missing something - I don't know if I have a program 
> installed to view the contents of weewx.sdb
> Michael H Grossie
> mhgr...@sbcglobal.net
>
>
> On Mon, Jul 13, 2020 at 11:53 AM Michael Grossie <
> mhgr...@sbcglobal.net> wrote:
>
>> In trying to find folders and files are at, they are all in the 
>> proper places (based on the list in the User 

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[John Kline]

Give 2.0.b7 a spin.

trend has now been generalized (as opposed to only working with barometer).  It 
will also honor the time_span configured for the target report.

If the numbers don’t look right to you, the last 36 records in the archive 
table would be more helpful than sending screenshots of the value differing 
from what report generation produces.

trend.barometer.desc (i.e, the .desc suffix) is still an oddball.  It shouldn’t 
be part of LoopData.  I’m going to remove it, but I need to move the code (to 
produce the description) to JavasSript (for one of my personal reports, not as 
part of LoopData).

> On Jul 18, 2020, at 6:05 AM, John Kline  wrote:
> 
> 
> I’ve already well on my way to replacing this.  Trend will work for all 
> scalar values, not just barometer.  The code is done, but I need to add it to 
> the tests.
> 
>>> On Jul 17, 2020, at 11:17 PM, geni08...@gmail.com  
>>> wrote:
>>> 
>>  I don't think there are any errors in the database, the barometer trend is 
>> displayed in my season with a credible value that also matches the value in 
>> the index.html from the weatherboard (as documented in the older answer).
>> I also attached the file loop-data-xxx.txt, in the upper part you can see 
>> the values generated by loop-data in the lower part my entry in weewx.conf. 
>> It is striking that the values "trend.barometerRate.desc" and 
>> "trend.barometerRate" are missing.
>> Yesterday at noon I noticed that the value of the 
>> "trend.barometer.formatted", which is now> 300 is exactly at 12h (GTM + 2) 
>> on the expected value. Will watch this today). 
>> 
>> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 16:23:27 UTC+2:
>>> 
>>> As the documentation states, trend.barometer and 10m.windGust are special 
>>> cases.
>>> 
>>> In this case, where we are talking about trend.barometer, it is alway the 
>>> delta from three hours ago and uses archive records to compute the starting 
>>> reading.  Also, it is expressed as a per hour rate.  Thus, it would be 1/3 
>>> of the three hour delta.  I did it this way because my sole purpose was to 
>>> compute the text description (e.g., rising slowly).
>>> 
>>> Perhaps you have some bad data in your database?  Have you checked that to 
>>> see what the actual delta and per hour delta should be?
>>> 
>>> In any event, I need to make trend less special.  I think I’ll do that this 
>>> weekend.  It should honor the $delta.time_delta for the skin and report the 
>>> actual delta, not on a per hour basis.  While I’m doing that, I’ll make 
>>> sure my tests around trend.barometer are good enough.  If there is a bug, I 
>>> should find it then.
>>> 
>>> 
> On Jul 16, 2020, at 11:07 PM, geni08...@gmail.com  
> wrote:
> 
 Thank you very much, the script is a good idea.
>>> 
 
 
 There was another question regarding "trend.barometerRate.formatted". At 
 the beginning this gave plausible values, from yesterday evening it 
 delivers impossible values.
 Is it possible that 2 sources supply data and interfere?
 I tried to keep a momentary status.
 
 Display liveboard
>>> 
 
 
 
 index.html
 
 
 
 loop-data.txt
>>> 
 
 
 
 index.html.tmpl
 
 
 $current.barometer(>>> id="trend.barometer.formatted">$trend.barometer.formatted)->>>  id="current.outHumidity">$current.outHumidity 
 
 
 
 
 jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 00:02:36 UTC+2:
> I’m not sure which parts of Bechlertown rely on MQTT and which parts rely 
> on auto refreshing the page.  For the former, if the info is available in 
> LoopData, you would need to add an id to the HTML element and then set 
> the contents via javascript in the same way as WeatherBoard does it.
> 
> Bechlertown appears to be a well supported skin with frequent updates.  
> You do need to worry about taking updates of the skin since you’ll be 
> making modifications.  Ideally, you would write a script to add the ids 
> in the right place and add a line to include the javascript.
> 
>>> On Jul 16, 2020, at 8:18 AM, geni08...@gmail.com  
>>> wrote:
>>> 
>> 
> 
>> Hi John, Thank you for your help so far, my next goal is to update the 
>> Belchertown template with weewx-loopdata.
>> MQTT needs an infrastructure there ... I find your solution really 
>> elegant. Do you have a tip for me where to start?
>> 
>> 
>> jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um 15:46:28 
>> UTC+2:
>>> It looks like you are on a roll!
>>> 
>>> I think you are asking why I don’t have the actual values filled in for 
>>> windGust in the template.
>>> 
>>> The answer for $10m.windGust.max is that the $10m period is only 
>>> understood by LoopData.  If you put $10m.windGust.max in the template, 
>>> it would cause an error.  There is probably a way to 

Re: [weewx-user] NOAA yearly reports doesnt populate

[Praveen Chandrasekaran]

V4.0.0.

Time for an upgrade then! Thanks. I wasnt aware of the bug!

On Sat, 18 Jul 2020 at 20:57, Tom Keffer  wrote:

> What version? This was a known bug in V4.0.0 and v4.1.0, fixed in v4.1.1.
>
> On Sat, Jul 18, 2020 at 7:56 AM Praveen Chandrasekaran <
> praveen.c...@gmail.com> wrote:
>
>> Hi,
>>
>> I am having an issue where when weewx generates reports in its usual 5
>> min cycle, it doesnt populate the years for NOAA "Select by Year" drop down
>> box. However when I run wee_reports manually it populates it.
>>
>> Log doesnt have any error related to this.
>>
>> Regards,
>> Praveen
>>
>> --
>> 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/3d94a154-6024-446a-84a7-2b6af359c48eo%40googlegroups.com
>> 
>> .
>>
> --
> 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/I7uPCD4s_BM/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/CAPq0zEAeHApxk11ueuCzrHF0kHCGKfheLYkp3xQV4HPry5Ap2Q%40mail.gmail.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/CA%2BW%3DTmUdb%3DpodORBhOge9DxaPJb7kT%2Bk4rFA-EcfHtpsaWdy1w%40mail.gmail.com.

Re: [weewx-user] NOAA yearly reports doesnt populate

[Tom Keffer]

What version? This was a known bug in V4.0.0 and v4.1.0, fixed in v4.1.1.

On Sat, Jul 18, 2020 at 7:56 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:

> Hi,
>
> I am having an issue where when weewx generates reports in its usual 5 min
> cycle, it doesnt populate the years for NOAA "Select by Year" drop down
> box. However when I run wee_reports manually it populates it.
>
> Log doesnt have any error related to this.
>
> Regards,
> Praveen
>
> --
> 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/3d94a154-6024-446a-84a7-2b6af359c48eo%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/CAPq0zEAeHApxk11ueuCzrHF0kHCGKfheLYkp3xQV4HPry5Ap2Q%40mail.gmail.com.

[weewx-user] Belchertown 1.0.1 question on wind direction in graphs

[Ernest Jillson]

I know I'm not at the latest version of Belchertown. In fact, I'm still
using the older version (3.9.2). I've tried copying
/etc/weewx/skins/Belchertown/graphs.conf.example to graphs.conf, but I
can't find where to change wind direction from ordinal direction to degrees.

My wind direction is only plotted to the nearest value of NNE, or NE, or
E.  You get the idea. I'd like to have it plot to the whole degree. Any
ideas?

My site can be seen here: http://greylords.us

Thanks in advance.

Ernie

-- 
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/CAC5oUmPxg57vwENc5bm%2Bhwt5_MteyD%2BC4xfFWsDq8j_YXjy_sQ%40mail.gmail.com.

[weewx-user] NOAA yearly reports doesnt populate

[Praveen Chandrasekaran]

Hi,

I am having an issue where when weewx generates reports in its usual 5 min 
cycle, it doesnt populate the years for NOAA "Select by Year" drop down 
box. However when I run wee_reports manually it populates it.

Log doesnt have any error related to this.

Regards,
Praveen

-- 
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/3d94a154-6024-446a-84a7-2b6af359c48eo%40googlegroups.com.

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Michael Grossie]

Greg - works like a charm - thanks for the advice and for explaining -



Michael H Grossie
mhgros...@sbcglobal.net


On Sat, Jul 18, 2020 at 5:55 AM Greg from Oz  wrote:

> Maybe if you create a weewx.conf file in /etc/apache2/sites-available and
> call it weewx.conf
>
> Put this in the file:
>
> Alias /weewx "/home/weewx/public_html"
> 
> Options Indexes MultiViews
> AllowOverride None
> Order allow,deny
> Allow from all
> Require all granted
> 
>
> Save the file.
>
>  Then run sudo a2ensite weewx.conf   (this enables the site)
>
> Then reload apache
>
> Then go to http://localhost/weewx
>
> I am not an expert either and don't have a raspbaerry pi running apache.
>
> Good luck. I don't guarantee this will work but hey! you never know.
>
>
> On Saturday, 18 July 2020 at 12:33:05 UTC+10 Michael Grossie wrote:
>
>> I have found the index.html file in /home/weewx/public_html. I still
>> cannot access it with http://localhost/weewx - I need to use the full
>> path - but I can get to it and it does show data.
>>
>> Michael H Grossie
>> mhgr...@sbcglobal.net
>>
>>
>> On Mon, Jul 13, 2020 at 12:49 PM Michael Grossie 
>> wrote:
>>
>>> Installed sqlitebrowser. Opened weewx.sdb and did see records had been
>>> created. So, why does it not write to "weewx/public_html?"
>>>
>>>
>>> Michael H Grossie
>>> mhgr...@sbcglobal.net
>>>
>>>
>>> On Mon, Jul 13, 2020 at 12:30 PM Michael Grossie 
>>> wrote:
>>>
 After reloading cheetah, I rebooted, started weewx and apache2. I
 opened a browser and went to http://localhost/weewx (as directed in
 the User Guide) and received the 404 page not found error.

 I then ran "sudo /etc/init.d/weewx status -l"  and received -




















 *pi@raspberrypi:/home/weewx $ sudo /etc/init.d/weewx status -l●
 weewx.service - LSB: weewx weather system   Loaded: loaded
 (/etc/init.d/weewx; generated; vendor preset: enabled)   Active: active
 (running) since Mon 2020-07-13 12:03:01 CDT; 18min ago Docs:
 man:systemd-sysv-generator(8)  Process: 281 ExecStart=/etc/init.d/weewx
 start (code=exited, status=0/SUCCESS)Tasks: 2 (limit: 4915)   CGroup:
 /system.slice/weewx.service   └─497 /usr/bin/python2
 /home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid
 /home/weewx/weewx.confJul 13 12:15:16 raspberrypi weewxd[497]: weewx[497]
 INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to
 database 'weewx.sdb'Jul 13 12:15:16 raspberrypi weewxd[497]: weewx[497]
 INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to
 daily summary …weewx.sdb'Jul 13 12:15:21 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report
 SeasonsReport in 3.39 secondsJul 13 12:15:25 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.imagegenerator: Generated 15 images for report
 SeasonsReport in 3.65 secondsJul 13 12:15:25 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.reportengine: Copied 0 files to
 /home/weewx/public_htmlJul 13 12:20:16 raspberrypi weewxd[497]: weewx[497]
 INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to
 database 'weewx.sdb'Jul 13 12:20:16 raspberrypi weewxd[497]: weewx[497]
 INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to
 daily summary …weewx.sdb'Jul 13 12:20:21 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report
 SeasonsReport in 3.79 secondsJul 13 12:20:34 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.imagegenerator: Generated 30 images for report
 SeasonsReport in 12.33 secondsJul 13 12:20:34 raspberrypi weewxd[497]:
 weewx[497] INFO weewx.reportengine: Copied 0 files to
 /home/weewx/public_htmlHint: Some lines were ellipsized, use -l to show in
 full.*

 Now I see that records were added and reports generated, but nothing
 transferred to /home/weewx/public_html
 I am still missing something - I don't know if I have a program
 installed to view the contents of weewx.sdb
 Michael H Grossie
 mhgr...@sbcglobal.net


 On Mon, Jul 13, 2020 at 11:53 AM Michael Grossie 
 wrote:

> In trying to find folders and files are at, they are all in the proper
> places (based on the list in the User Guide) - I ran
> "sudo /etc/init.d/weewx status -l" from the /home/weewx directory.  I
> received the following -
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> *pi@raspberrypi:/home/weewx $ sudo /etc/init.d/weewx status -ls●
> weewx.service - LSB: weewx weather system   Loaded: loaded
> (/etc/init.d/weewx; generated; vendor preset: enabled)   Active: active
> (running) since Mon 2020-07-13 11:10:24 CDT; 28min ago 

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[John Kline]

I’ve already well on my way to replacing this.  Trend will work for all scalar 
values, not just barometer.  The code is done, but I need to add it to the 
tests.

> On Jul 17, 2020, at 11:17 PM, geni08...@gmail.com  
> wrote:
> 
>  I don't think there are any errors in the database, the barometer trend is 
> displayed in my season with a credible value that also matches the value in 
> the index.html from the weatherboard (as documented in the older answer).
> I also attached the file loop-data-xxx.txt, in the upper part you can see the 
> values generated by loop-data in the lower part my entry in weewx.conf. It is 
> striking that the values "trend.barometerRate.desc" and "trend.barometerRate" 
> are missing.
> Yesterday at noon I noticed that the value of the 
> "trend.barometer.formatted", which is now> 300 is exactly at 12h (GTM + 2) on 
> the expected value. Will watch this today). 
> 
> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 16:23:27 UTC+2:
>> 
>> As the documentation states, trend.barometer and 10m.windGust are special 
>> cases.
>> 
>> In this case, where we are talking about trend.barometer, it is alway the 
>> delta from three hours ago and uses archive records to compute the starting 
>> reading.  Also, it is expressed as a per hour rate.  Thus, it would be 1/3 
>> of the three hour delta.  I did it this way because my sole purpose was to 
>> compute the text description (e.g., rising slowly).
>> 
>> Perhaps you have some bad data in your database?  Have you checked that to 
>> see what the actual delta and per hour delta should be?
>> 
>> In any event, I need to make trend less special.  I think I’ll do that this 
>> weekend.  It should honor the $delta.time_delta for the skin and report the 
>> actual delta, not on a per hour basis.  While I’m doing that, I’ll make sure 
>> my tests around trend.barometer are good enough.  If there is a bug, I 
>> should find it then.
>> 
>> 
 On Jul 16, 2020, at 11:07 PM, geni08...@gmail.com  
 wrote:
 
>>> Thank you very much, the script is a good idea.
>> 
>>> 
>>> 
>>> There was another question regarding "trend.barometerRate.formatted". At 
>>> the beginning this gave plausible values, from yesterday evening it 
>>> delivers impossible values.
>>> Is it possible that 2 sources supply data and interfere?
>>> I tried to keep a momentary status.
>>> 
>>> Display liveboard
>> 
>>> 
>>> 
>>> 
>>> index.html
>>> 
>>> 
>>> 
>>> loop-data.txt
>> 
>>> 
>>> 
>>> 
>>> index.html.tmpl
>>> 
>>> 
>>> $current.barometer(>> id="trend.barometer.formatted">$trend.barometer.formatted)->>  id="current.outHumidity">$current.outHumidity 
>>> 
>>> 
>>> 
>>> 
>>> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 00:02:36 UTC+2:
 I’m not sure which parts of Bechlertown rely on MQTT and which parts rely 
 on auto refreshing the page.  For the former, if the info is available in 
 LoopData, you would need to add an id to the HTML element and then set the 
 contents via javascript in the same way as WeatherBoard does it.
 
 Bechlertown appears to be a well supported skin with frequent updates.  
 You do need to worry about taking updates of the skin since you’ll be 
 making modifications.  Ideally, you would write a script to add the ids in 
 the right place and add a line to include the javascript.
 
>> On Jul 16, 2020, at 8:18 AM, geni08...@gmail.com  
>> wrote:
>> 
> 
 
> Hi John, Thank you for your help so far, my next goal is to update the 
> Belchertown template with weewx-loopdata.
> MQTT needs an infrastructure there ... I find your solution really 
> elegant. Do you have a tip for me where to start?
> 
> 
> jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um 15:46:28 
> UTC+2:
>> It looks like you are on a roll!
>> 
>> I think you are asking why I don’t have the actual values filled in for 
>> windGust in the template.
>> 
>> The answer for $10m.windGust.max is that the $10m period is only 
>> understood by LoopData.  If you put $10m.windGust.max in the template, 
>> it would cause an error.  There is probably a way to compute the 10 
>> minute high gust, but I didn’t bother to figure that out since the value 
>> will appear anyway on the next loop.
>> 
>> For $day.windGust.max, adding it to the template should work just fine.  
>> It’s not needed.  In fact, none of the values are needed since they are 
>> overwritten by the JavaScript.
>> 
>> 
>> 
 On Jul 16, 2020, at 5:26 AM, geni08...@gmail.com  
 wrote:
 
>>>  Hi John, it could even add winDir and barometer and humidity!
>> 
>>> What I would like to know why is enough for the two windGust values 
>>> only the id in index.html.tmpl 
>>> https://affolter.familyds.net/wetter/live/
>>> 
>> 
>>> 
>>> 
>>> 
>>> jo...@johnkline.com schrieb am 

Re: [weewx-user] Re: Apache is not showing /weewx on Ubuntu 16.04.1

[Greg from Oz]

Maybe if you create a weewx.conf file in /etc/apache2/sites-available and 
call it weewx.conf

Put this in the file:

Alias /weewx "/home/weewx/public_html"

Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
Require all granted


Save the file.

 Then run sudo a2ensite weewx.conf   (this enables the site)

Then reload apache

Then go to http://localhost/weewx

I am not an expert either and don't have a raspbaerry pi running apache.

Good luck. I don't guarantee this will work but hey! you never know. 


On Saturday, 18 July 2020 at 12:33:05 UTC+10 Michael Grossie wrote:

> I have found the index.html file in /home/weewx/public_html. I still 
> cannot access it with http://localhost/weewx - I need to use the full 
> path - but I can get to it and it does show data.
>  
> Michael H Grossie
> mhgr...@sbcglobal.net
>
>
> On Mon, Jul 13, 2020 at 12:49 PM Michael Grossie  
> wrote:
>
>> Installed sqlitebrowser. Opened weewx.sdb and did see records had been 
>> created. So, why does it not write to "weewx/public_html?"
>>  
>>  
>> Michael H Grossie
>> mhgr...@sbcglobal.net
>>
>>
>> On Mon, Jul 13, 2020 at 12:30 PM Michael Grossie  
>> wrote:
>>
>>> After reloading cheetah, I rebooted, started weewx and apache2. I opened 
>>> a browser and went to http://localhost/weewx (as directed in the User 
>>> Guide) and received the 404 page not found error.
>>>
>>> I then ran "sudo /etc/init.d/weewx status -l"  and received -
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *pi@raspberrypi:/home/weewx $ sudo /etc/init.d/weewx status -l● 
>>> weewx.service - LSB: weewx weather system   Loaded: loaded 
>>> (/etc/init.d/weewx; generated; vendor preset: enabled)   Active: active 
>>> (running) since Mon 2020-07-13 12:03:01 CDT; 18min ago Docs: 
>>> man:systemd-sysv-generator(8)  Process: 281 ExecStart=/etc/init.d/weewx 
>>> start (code=exited, status=0/SUCCESS)Tasks: 2 (limit: 4915)   CGroup: 
>>> /system.slice/weewx.service   └─497 /usr/bin/python2 
>>> /home/weewx/bin/weewxd --daemon --pidfile=/var/run/weewx.pid 
>>> /home/weewx/weewx.confJul 13 12:15:16 raspberrypi weewxd[497]: weewx[497] 
>>> INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to 
>>> database 'weewx.sdb'Jul 13 12:15:16 raspberrypi weewxd[497]: weewx[497] 
>>> INFO weewx.manager: Added record 2020-07-13 12:15:00 CDT (1594660500) to 
>>> daily summary …weewx.sdb'Jul 13 12:15:21 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report 
>>> SeasonsReport in 3.39 secondsJul 13 12:15:25 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.imagegenerator: Generated 15 images for report 
>>> SeasonsReport in 3.65 secondsJul 13 12:15:25 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.reportengine: Copied 0 files to 
>>> /home/weewx/public_htmlJul 13 12:20:16 raspberrypi weewxd[497]: weewx[497] 
>>> INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to 
>>> database 'weewx.sdb'Jul 13 12:20:16 raspberrypi weewxd[497]: weewx[497] 
>>> INFO weewx.manager: Added record 2020-07-13 12:20:00 CDT (1594660800) to 
>>> daily summary …weewx.sdb'Jul 13 12:20:21 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.cheetahgenerator: Generated 8 files for report 
>>> SeasonsReport in 3.79 secondsJul 13 12:20:34 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.imagegenerator: Generated 30 images for report 
>>> SeasonsReport in 12.33 secondsJul 13 12:20:34 raspberrypi weewxd[497]: 
>>> weewx[497] INFO weewx.reportengine: Copied 0 files to 
>>> /home/weewx/public_htmlHint: Some lines were ellipsized, use -l to show in 
>>> full.*
>>>  
>>> Now I see that records were added and reports generated, but nothing 
>>> transferred to /home/weewx/public_html
>>> I am still missing something - I don't know if I have a program 
>>> installed to view the contents of weewx.sdb
>>> Michael H Grossie
>>> mhgr...@sbcglobal.net
>>>
>>>
>>> On Mon, Jul 13, 2020 at 11:53 AM Michael Grossie  
>>> wrote:
>>>
 In trying to find folders and files are at, they are all in the proper 
 places (based on the list in the User Guide) - I ran 
 "sudo /etc/init.d/weewx status -l" from the /home/weewx directory.  I 
 received the following -




















 *pi@raspberrypi:/home/weewx $ sudo /etc/init.d/weewx status -ls● 
 weewx.service - LSB: weewx weather system   Loaded: loaded 
 (/etc/init.d/weewx; generated; vendor preset: enabled)   Active: active 
 (running) since Mon 2020-07-13 11:10:24 CDT; 28min ago Docs: 
 man:systemd-sysv-generator(8)  Process: 281 ExecStart=/etc/init.d/weewx 
 start (code=exited, status=0/SUCCESS)Tasks: 2 (limit: 4915)   CGroup: 
 /system.slice/weewx.service   └─558 /usr/bin/python2 
 /home/weewx/bin/weewxd --daemon 

Re: [weewx-user] Questions about weewx-loopdata 1.3.x

[geni08...@gmail.com]

 I don't think there are any errors in the database, the barometer trend is 
displayed in my season with 
a credible value that also matches the value in the index.html from the 
weatherboard (as documented in the older answer).
I also attached the file loop-data-xxx.txt, in the upper part you can see 
the values generated by loop-data in the lower part my entry in weewx.conf. It 
is striking that the values "trend.barometerRate.desc" and 
"trend.barometerRate" are missing.
Yesterday at noon I noticed that the value of the 
"trend.barometer.formatted", which is now> 300 is exactly at 12h (GTM + 2) 
on the expected value. Will watch this today). 

jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 16:23:27 UTC+2:

> 
> As the documentation states, trend.barometer and 10m.windGust are special 
> cases.
>
> In this case, where we are talking about trend.barometer, it is alway the 
> delta from three hours ago and uses archive records to compute the starting 
> reading.  Also, it is expressed as a per hour rate.  Thus, it would be 1/3 
> of the three hour delta.  I did it this way because my sole purpose was to 
> compute the text description (e.g., rising slowly).
>
> Perhaps you have some bad data in your database?  Have you checked that to 
> see what the actual delta and per hour delta should be?
>
> In any event, I need to make trend less special.  I think I’ll do that 
> this weekend.  It should honor the $delta.time_delta for the skin and 
> report the actual delta, not on a per hour basis.  While I’m doing that, 
> I’ll make sure my tests around trend.barometer are good enough.  If there 
> is a bug, I should find it then.
>
>
> On Jul 16, 2020, at 11:07 PM, geni08...@gmail.com  
> wrote:
>
> Thank you very much, the script is a good idea.
>
>
>
> There was another question regarding "trend.barometerRate.formatted". At 
> the beginning this gave plausible values, from yesterday evening it 
> delivers impossible values.
> Is it possible that 2 sources supply data and interfere?
> I tried to keep a momentary status.
>
> Display liveboard
>
> 
>
>
> index.html
> 
>
>
> loop-data.txt
>
> 
>
>
> index.html.tmpl
> 
> 
> $current.barometer( id="trend.barometer.formatted">$trend.barometer.formatted)-  
> id="current.outHumidity">$current.outHumidity 
> 
> 
>
>
> jo...@johnkline.com schrieb am Freitag, 17. Juli 2020 um 00:02:36 UTC+2:
>
>> I’m not sure which parts of Bechlertown rely on MQTT and which parts rely 
>> on auto refreshing the page.  For the former, if the info is available in 
>> LoopData, you would need to add an id to the HTML element and then set the 
>> contents via javascript in the same way as WeatherBoard does it.
>>
>> Bechlertown appears to be a well supported skin with frequent updates. 
>>  You do need to worry about taking updates of the skin since you’ll be 
>> making modifications.  Ideally, you would write a script to add the ids in 
>> the right place and add a line to include the javascript.
>>
>> On Jul 16, 2020, at 8:18 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>>
>> Hi John, Thank you for your help so far, my next goal is to update the 
>> Belchertown template with weewx-loopdata.
>> MQTT needs an infrastructure there ... I find your solution really 
>> elegant. Do you have a tip for me where to start?
>>
>>
>> jo...@johnkline.com schrieb am Donnerstag, 16. Juli 2020 um 15:46:28 
>> UTC+2:
>>
>>> It looks like you are on a roll!
>>>
>>> I think you are asking why I don’t have the actual values filled in for 
>>> windGust in the template.
>>>
>>> The answer for $10m.windGust.max is that the $10m period is only 
>>> understood by LoopData.  If you put $10m.windGust.max in the template, it 
>>> would cause an error.  There is probably a way to compute the 10 minute 
>>> high gust, but I didn’t bother to figure that out since the value will 
>>> appear anyway on the next loop.
>>>
>>> For $day.windGust.max, adding it to the template should work just fine. 
>>>  It’s not needed.  In fact, none of the values are needed since they are 
>>> overwritten by the JavaScript.
>>>
>>>
>>>
>>> On Jul 16, 2020, at 5:26 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>>  Hi John, it could even add winDir and barometer and humidity!
>>>
>>> What I would like to know why is enough for the two windGust values only 
>>> the id in index.html.tmpl 
>>> https://affolter.familyds.net/wetter/live/
>>>
>>> 
>>>
>>>
>>> jo...@johnkline.com schrieb am Mittwoch, 15. Juli 2020 um 22:32:15 
>>> UTC+2:
>>>
 Thanks for sending those links.

 Again, I don’t think it’s necessary to move the file to ram disk.  With 
 modern SSDs and wear leveling, and especially with a file this size.  You 
 might want to do some web searches before deciding if its worth the effort.

 On Jul 15, 2020, at 1:14 PM, 'hctp...@googlemail.com' via weewx-user <
 weewx...@googlegroups.com> wrote:

 John,

 so maybe a project for the next