Re: [weewx-user] Update interval less than 300 seconds?

[gjr80]

I think the error trace says it all:

configobj.ConfigObjError: Parsing failed with several errors.
First error at line 532.

Someone or something has introduced an error in your weewx.conf, line 532 would 
be a good place to look. The error trace says there are multiple errors, so 
expect to find others. I suggest that if you cannot identify the error yourself 
you post a copy of weewx.conf making sure you obliterate any user names, 
passwords, api keys or other sensitive info in the file first.

Gary

As the config file is used by WeeWX and most of the utilities this is likely 
why you cannot run WeeWX and the utilities. 

-- 
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/044a524e-2fae-479a-ac9b-614225c2e440o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I don’t know what issue you are having.  It doesn’t seem like to could be 
caused by this extension, but it is best to eliminate that possibility right 
away.

Let’s manually remove loopdata and weatherboard.  Substitute weewx’s home 
directory for  In these instructions.

1. sudo rm /bin/user/loopdata.py
2. sudo rm -rf /skins/WeatherBoard
3. With your favorite editor:
  Remove user.loopdata.LoopData from the report_services line.
   Remove the [LoopData] section in its entirety.
   Remove the [[WeatherBoard]] report section in its entirety.
4. Restart weewx.

>> On Jul 4, 2020, at 8:53 AM, Geni 0815  wrote:
> 
> even a simple wee_extension --list has not worked since loopdata 1.3.5 was 
> installed
> 
>> pi@Wetter-Raspi:~ $ wee_extension --list
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_extension", line 88, in 
>> main()
>>   File "/usr/share/weewx/wee_extension", line 67, in main
>> config_path, config_dict = weecfg.read_config(options.config, _args)
>>   File "/usr/share/weewx/weecfg/__init__.py", line 179, in read_config
>> default_encoding='utf-8')
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 1229, in __init__
>> self._load(infile, configspec)
>>   File "/usr/lib/python3/dist-packages/configobj.py", line 1318, in _load
>> raise error
>> configobj.ConfigObjError: Parsing failed with several errors.
>> First error at line 532.
>> 
> How can I get my weewx up and running again?
> 
> 
> 
> Am Samstag, 4. Juli 2020 14:35:37 UTC+2 schrieb John Kline:
>> 
>> wee_extension --uninstall loopdata
>> will remove loopdata.  You’ll need to restart weewx
>> 
 On Jul 3, 2020, at 10:41 PM, Geni 0815  wrote:
>>> 
>>> How can I stop loop data?
>>> -- 
>>> 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/6fe8b84f-8c69-4293-b848-b5c8f87034aao%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/c8f18743-9b50-4547-b275-383b9491b218o%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/920F0985-5E31-4679-905C-674461BC91D5%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

even a simple wee_extension --list has not worked since loopdata 1.3.5 was 
installed

pi@Wetter-Raspi:~ $ wee_extension --list
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_extension", line 88, in 
> main()
>   File "/usr/share/weewx/wee_extension", line 67, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 179, in read_config
> default_encoding='utf-8')
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 532.
>
> How can I get my weewx up and running again?



Am Samstag, 4. Juli 2020 14:35:37 UTC+2 schrieb John Kline:
>
> wee_extension --uninstall loopdata
> will remove loopdata.  You’ll need to restart weewx
>
> On Jul 3, 2020, at 10:41 PM, Geni 0815 > 
> wrote:
>
> 
> How can I stop loop data? 
>
> -- 
> 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/6fe8b84f-8c69-4293-b848-b5c8f87034aao%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/c8f18743-9b50-4547-b275-383b9491b218o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

doesn’t work either, I don’t want to run weewx anymore!

pi@Wetter-Raspi:~ $ wee_extension --uninstall loopdata
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_extension", line 88, in 
> main()
>   File "/usr/share/weewx/wee_extension", line 67, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 179, in read_config
> default_encoding='utf-8')
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 532.
>
>
Am Samstag, 4. Juli 2020 14:35:37 UTC+2 schrieb John Kline:
>
> wee_extension --uninstall loopdata
> will remove loopdata.  You’ll need to restart weewx
>
> On Jul 3, 2020, at 10:41 PM, Geni 0815 > 
> wrote:
>
> 
> How can I stop loop data? 
>
> -- 
> 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/6fe8b84f-8c69-4293-b848-b5c8f87034aao%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/8180ac18-cc02-47b7-bdc0-0c40df0b46c1o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

wee_extension --uninstall loopdata
will remove loopdata.  You’ll need to restart weewx

> On Jul 3, 2020, at 10:41 PM, Geni 0815  wrote:
> 
> 
> How can I stop loop data?
> -- 
> 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/6fe8b84f-8c69-4293-b848-b5c8f87034aao%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/FE38820D-4FAA-4501-AC4B-F8375EA36519%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

How can I stop loop data? 

-- 
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/6fe8b84f-8c69-4293-b848-b5c8f87034aao%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

weewx debug = 1
does not issue errors

Am Freitag, 3. Juli 2020 23:17:17 UTC+2 schrieb John Kline:
>
> OK, ignore my last email.  The accumulators were correct and conversions 
> of observations were being done correctly.  But not highs, lows, sums, ...
>
> This is fixed in loopdata 1.3.5.  Please pull it, install it and restart 
> weewx.  It should all work with this change.
>
> It’s fortunate (for me) that WeeWX stores rain in cm and defaults to 
> reporting it in mm.  Because of that, FMT_SUM_rain revealed the issue (in 
> Metric) and that let me fix it.
>
> Thank you for reporting this.
> John
>
> On Jul 3, 2020, at 12:28 PM, John Kline > 
> wrote:
>
> 
> I found the problem.  The database is storing rain as cm and, as you might 
> expect, the day accumulators were correct.  I however, when I copied the 
> accumulators at startup, was treating them as if they were in the report 
> target units (in this case mm).
>
> I’ll push a fix today.
>
> On Jul 3, 2020, at 11:14 AM, John Kline > 
> wrote:
>
> 
> I’ve duplicated the daily rainfall discrepancy.
>
> I am asking WeeWX for the day summary and initializing my day accumulators 
> with the day summary.
> day_summary = dbm._get_day_summary(time.time())
>
> But the day summary accumulator for rain is reporting 1/10 of the actual 
> rain.  Before I can fix this, I need to take the time to understand why I 
> am seeing what I am seeing in WeeWX’s day summary.
>
> On Jul 3, 2020, at 10:10 AM, Geni 0815 > 
> wrote:
>
> 
> I'm using the latest driver
> wget -P / var / tmp 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
>
> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>>
>>
>>
>> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
>>
>> 
>> All fields are displayed again, we have absolute calm at the moment so I 
>> can not see how it works.
>> The error kph is desired km / h
>>
>> You can ask others how to change a label on a report.  Once you do that, 
>> LoopData will use it.
>>
>> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>>
>> Indeed, when i curl your page, I see the .6 being generated at reporting 
>>> time and I can look at your loop-data.txt and see 0.1.  I am actually 
>>> copying the day summary accumulators, so this is perplexing.  I will 
>>> investigate this.  I have not run into it since I have been using 
>>> day_rain_total, which isn’t available in your driver.
>>>
>>
>> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>>>
>>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>>> trying to get a document element by the name of FMT_dewpoint, but that 
>>> element no longer exists in index.html.
>>>
>>> Make the following changes and let me know how it goes.
>>>
>>> In index.html.tmpl:
>>> Change:
>>>  $current.outTemp>> id="appTemp">$current.appTemp
>>> to:
>>> $current.outTemp>> id="FMT_appTemp">$current.appTemp
>>>
>>> In weewx.conf>LoopData>Include>fields:
>>> Change:
>>> appTemp
>>> to:
>>> FMT_appTemp
>>>
>>> In realtime_updater.inc:
>>> Change:
>>>  // dew point  
>>>   var dew = result["FMT_dewpoint"];
>>>   if (dew.length == 5) {
>>> dew = "" + dew;
>>>   } else if (dew.length == 6) {
>>> dew = "" + dew;
>>>   } 
>>> 
>>>   
>>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>>> to:
>>>  // apparent temp  
>>>   var appTemp = result["FMT_appTemp"];
>>>   if (appTemp.length == 5) {
>>> appTemp = "" + appTemp;
>>>   } else if (appTemp.length == 6) {
>>> appTemp = "" + appTemp;
>>>   } 
>>> 
>>>   
>>>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>>>
>>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
>>>
>>> 
>>>
>>>
>>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:



 Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>
> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
> could be the problem
>
> # Options for extension 'loopdata'
>> [LoopData]
>> [[FileSpec]]
>> loop_data_dir = /home/pi/wetter/loop-data
>> filename = loop-data.txt
>> [[Formatting]]
>> target_report = WeatherBoardReport
>> [[RsyncSpec]]
>> enable = false
>> remote_server = 192.168
>> remote_port = 2022
>> remote_user = 
>> remote_dir = /web/wetter/loop-data
>> compress = false
>> log_success = false

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

After installing 1.3.5, sudo extension --list reports errors and weewx no 
longer works

pi@Wetter-Raspi:~/NAS/weewx-loopdata $ sudo wee_extension --list
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
> pi@Wetter-Raspi:~/NAS/weewx-loopdata $ sudo wee_extension --install 
> weewx-loopdata-master.zip
> Request to install 'weewx-loopdata-master.zip'
> Extracting from zip archive weewx-loopdata-master.zip
> Saving installer file to /usr/share/weewx/user/installer/loopdata
> Saved configuration dictionary. Backup copy at 
> /etc/weewx/weewx.conf.20200704064717
> Finished installing extension 'weewx-loopdata-master.zip'
> pi@Wetter-Raspi:~/NAS/weewx-loopdata $ sudo nano /etc/weewx/weewx.conf
> pi@Wetter-Raspi:~/NAS/weewx-loopdata $ sudo /etc/init.d/weewx restart
> [ ok ] Restarting weewx (via systemctl): weewx.service.
> pi@Wetter-Raspi:~/NAS/weewx-loopdata $ sudo wee_extension --list
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_extension", line 88, in 
> main()
>   File "/usr/share/weewx/wee_extension", line 67, in main
> config_path, config_dict = weecfg.read_config(options.config, _args)
>   File "/usr/share/weewx/weecfg/__init__.py", line 179, in read_config
> default_encoding='utf-8')
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1229, in 
> __init__
> self._load(infile, configspec)
>   File "/usr/lib/python3/dist-packages/configobj.py", line 1318, in _load
> raise error
> configobj.ConfigObjError: Parsing failed with several errors.
> First error at line 532.
> pi@Wetter-Raspi:~/NAS/weewx-loopdata $ 
>
 

Am Samstag, 4. Juli 2020 00:50:00 UTC+2 schrieb John Kline:
>
> OK, as far as changing to km/h.  It’s done the same way you would change a 
> label
> for any report in WeeWX.  In this case, just add the last two lines below 
> to WeatherBoardReport in weewx.conf.  This is assuming the target_report
> LoopData section is WeatherBoardReport (which it should be).
>
> [[WeatherBoardReport]]
> HTML_ROOT = public_html/weatherboard
> enable = true
> .
> .
> .
> [[[Units]]]
> StringFormats
> mile_per_hour = %.1f
> degree_C = %.1f
> km_per_hour = %.1f
> degree_F = %.1f
> Labels]]]
> km_per_hour = km/h
>
> This change looks weird to me because there is a slash separating the two 
> wind numbers:
> 3.5 km/h/ 7.7 km/h
>
> You might want to change line 83 to:
>   id="FMT_HI_windGust">
>
> That will look better:
> 3.5 km/h - 7.7 km/h
>  
>
>
> On Jul 3, 2020, at 2:17 PM, John Kline > 
> wrote:
>
> 
> OK, ignore my last email.  The accumulators were correct and conversions 
> of observations were being done correctly.  But not highs, lows, sums, ...
>
> This is fixed in loopdata 1.3.5.  Please pull it, install it and restart 
> weewx.  It should all work with this change.
>
> It’s fortunate (for me) that WeeWX stores rain in cm and defaults to 
> reporting it in mm.  Because of that, FMT_SUM_rain revealed the issue (in 
> Metric) and that let me fix it.
>
> Thank you for reporting this.
> John
>
> On Jul 3, 2020, at 12:28 PM, John Kline > 
> wrote:
>
> 
> I found the problem.  The database is storing rain as cm and, as you might 
> expect, the day accumulators were correct.  I however, when I copied the 
> accumulators at startup, was treating them as if they were in the report 
> target units (in this case mm).
>
> I’ll push a fix today.
>
> On Jul 3, 2020, at 11:14 AM, John Kline > 
> wrote:
>
> 
> I’ve duplicated the daily rainfall discrepancy.
>
> I am asking WeeWX for the day summary and initializing my day accumulators 
> with the day summary.
> day_summary = dbm._get_day_summary(time.time())
>
> But the day summary accumulator for rain is reporting 1/10 of the actual 
> rain.  Before I can fix this, I need to take the time to understand why I 
> am seeing what I am seeing in WeeWX’s day summary.
>
> On Jul 3, 2020, at 10:10 AM, Geni 0815 > 
> wrote:
>
> 
> I'm using the latest driver
> wget -P / var / tmp 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
>
> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>>
>>
>>
>> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
>>
>> 
>> All fields are displayed again, we have absolute calm at the moment so I 
>> can not see how it works.
>> The error kph is desired km / h
>>
>> You can ask others how to change a label on a report.  Once you do that, 
>> LoopData will use it.
>>
>> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>>
>> Indeed, when i curl your page, I see the .6 being generated at reporting 
>>> time and I 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

Actually, you need a space before the km/h.

So add:

Labels
km_per_hour = " km/h"

This will result in:
  3.5 / 7.7 km/h

You can ignore the change to index.html line 83.

> On Jul 3, 2020, at 3:49 PM, John Kline  wrote:
> 
> 
> OK, as far as changing to km/h.  It’s done the same way you would change a 
> label
> for any report in WeeWX.  In this case, just add the last two lines below to 
> WeatherBoardReport in weewx.conf.  This is assuming the target_report
> LoopData section is WeatherBoardReport (which it should be).
> 
> [[WeatherBoardReport]]
> HTML_ROOT = public_html/weatherboard
> enable = true
> .
> .
> .
> [[[Units]]]
> StringFormats
> mile_per_hour = %.1f
> degree_C = %.1f
> km_per_hour = %.1f
> degree_F = %.1f
> Labels]]]
> km_per_hour = km/h
> 
> This change looks weird to me because there is a slash separating the two 
> wind numbers:
> 3.5 km/h/ 7.7 km/h
> 
> You might want to change line 83 to:
>   id="FMT_HI_windGust">
> 
> That will look better:
> 3.5 km/h - 7.7 km/h
>  
> 
> 
>> On Jul 3, 2020, at 2:17 PM, John Kline  wrote:
>> 
>> 
>> OK, ignore my last email.  The accumulators were correct and conversions of 
>> observations were being done correctly.  But not highs, lows, sums, ...
>> 
>> This is fixed in loopdata 1.3.5.  Please pull it, install it and restart 
>> weewx.  It should all work with this change.
>> 
>> It’s fortunate (for me) that WeeWX stores rain in cm and defaults to 
>> reporting it in mm.  Because of that, FMT_SUM_rain revealed the issue (in 
>> Metric) and that let me fix it.
>> 
>> Thank you for reporting this.
>> John
>> 
>>> On Jul 3, 2020, at 12:28 PM, John Kline  wrote:
>>> 
>>> 
>>> I found the problem.  The database is storing rain as cm and, as you might 
>>> expect, the day accumulators were correct.  I however, when I copied the 
>>> accumulators at startup, was treating them as if they were in the report 
>>> target units (in this case mm).
>>> 
>>> I’ll push a fix today.
>>> 
 On Jul 3, 2020, at 11:14 AM, John Kline  wrote:
 
 
 I’ve duplicated the daily rainfall discrepancy.
 
 I am asking WeeWX for the day summary and initializing my day accumulators 
 with the day summary.
 day_summary = dbm._get_day_summary(time.time())
 
 But the day summary accumulator for rain is reporting 1/10 of the actual 
 rain.  Before I can fix this, I need to take the time to understand why I 
 am seeing what I am seeing in WeeWX’s day summary.
 
> On Jul 3, 2020, at 10:10 AM, Geni 0815  wrote:
> 
> 
> I'm using the latest driver
> wget -P / var / tmp 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
> 
> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>> 
>> 
>> 
>>> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
>>> 
>>> 
>>> All fields are displayed again, we have absolute calm at the moment so 
>>> I can not see how it works.
>>> The error kph is desired km / h
>> You can ask others how to change a label on a report.  Once you do that, 
>> LoopData will use it.
>>> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>>> Indeed, when i curl your page, I see the .6 being generated at 
>>> reporting time and I can look at your loop-data.txt and see 0.1.  I am 
>>> actually copying the day summary accumulators, so this is perplexing.  
>>> I will investigate this.  I have not run into it since I have been 
>>> using day_rain_total, which isn’t available in your driver.
>>> 
>>> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
 
 You didn’t quite get the change to appTemp correct.  The JavaScript 
 was trying to get a document element by the name of FMT_dewpoint, but 
 that element no longer exists in index.html.
 
 Make the following changes and let me know how it goes.
 
 In index.html.tmpl:
 Change:
  >>> id="FMT_outTemp">$current.outTemp>>> id="appTemp">$current.appTemp
 to:
 $current.outTemp>>> id="FMT_appTemp">$current.appTemp
 
 In weewx.conf>LoopData>Include>fields:
 Change:
 appTemp
 to:
 FMT_appTemp
 
 In realtime_updater.inc:
 Change:
  // dew point  
   var dew = result["FMT_dewpoint"];
   if (dew.length == 5) {
 dew = "" + dew;
   } else if (dew.length == 6) {
 dew = "" + dew;
   }
  

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

OK, as far as changing to km/h.  It’s done the same way you would change a label
for any report in WeeWX.  In this case, just add the last two lines below to 
WeatherBoardReport in weewx.conf.  This is assuming the target_report
LoopData section is WeatherBoardReport (which it should be).

[[WeatherBoardReport]]
HTML_ROOT = public_html/weatherboard
enable = true
.
.
.
[[[Units]]]
StringFormats
mile_per_hour = %.1f
degree_C = %.1f
km_per_hour = %.1f
degree_F = %.1f
Labels]]]
km_per_hour = km/h

This change looks weird to me because there is a slash separating the two wind 
numbers:
3.5 km/h/ 7.7 km/h

You might want to change line 83 to:
 

That will look better:
3.5 km/h - 7.7 km/h
 


> On Jul 3, 2020, at 2:17 PM, John Kline  wrote:
> 
> 
> OK, ignore my last email.  The accumulators were correct and conversions of 
> observations were being done correctly.  But not highs, lows, sums, ...
> 
> This is fixed in loopdata 1.3.5.  Please pull it, install it and restart 
> weewx.  It should all work with this change.
> 
> It’s fortunate (for me) that WeeWX stores rain in cm and defaults to 
> reporting it in mm.  Because of that, FMT_SUM_rain revealed the issue (in 
> Metric) and that let me fix it.
> 
> Thank you for reporting this.
> John
> 
>>> On Jul 3, 2020, at 12:28 PM, John Kline  wrote:
>>> 
>> 
>> I found the problem.  The database is storing rain as cm and, as you might 
>> expect, the day accumulators were correct.  I however, when I copied the 
>> accumulators at startup, was treating them as if they were in the report 
>> target units (in this case mm).
>> 
>> I’ll push a fix today.
>> 
 On Jul 3, 2020, at 11:14 AM, John Kline  wrote:
 
>>> 
>>> I’ve duplicated the daily rainfall discrepancy.
>>> 
>>> I am asking WeeWX for the day summary and initializing my day accumulators 
>>> with the day summary.
>>> day_summary = dbm._get_day_summary(time.time())
>>> 
>>> But the day summary accumulator for rain is reporting 1/10 of the actual 
>>> rain.  Before I can fix this, I need to take the time to understand why I 
>>> am seeing what I am seeing in WeeWX’s day summary.
>>> 
> On Jul 3, 2020, at 10:10 AM, Geni 0815  wrote:
> 
 
 I'm using the latest driver
 wget -P / var / tmp 
 https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
 
 Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
> 
> 
> 
>> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
>> 
>> 
>> All fields are displayed again, we have absolute calm at the moment so I 
>> can not see how it works.
>> The error kph is desired km / h
> You can ask others how to change a label on a report.  Once you do that, 
> LoopData will use it.
>> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>> Indeed, when i curl your page, I see the .6 being generated at reporting 
>> time and I can look at your loop-data.txt and see 0.1.  I am actually 
>> copying the day summary accumulators, so this is perplexing.  I will 
>> investigate this.  I have not run into it since I have been using 
>> day_rain_total, which isn’t available in your driver.
>> 
>> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>>> 
>>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>>> trying to get a document element by the name of FMT_dewpoint, but that 
>>> element no longer exists in index.html.
>>> 
>>> Make the following changes and let me know how it goes.
>>> 
>>> In index.html.tmpl:
>>> Change:
>>>  $current.outTemp>> id="appTemp">$current.appTemp
>>> to:
>>> $current.outTemp>> id="FMT_appTemp">$current.appTemp
>>> 
>>> In weewx.conf>LoopData>Include>fields:
>>> Change:
>>> appTemp
>>> to:
>>> FMT_appTemp
>>> 
>>> In realtime_updater.inc:
>>> Change:
>>>  // dew point  
>>>   var dew = result["FMT_dewpoint"];
>>>   if (dew.length == 5) {
>>> dew = "" + dew;
>>>   } else if (dew.length == 6) {
>>> dew = "" + dew;
>>>   } 
>>> 
>>>   
>>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>>> to:
>>>  // apparent temp  
>>>   var appTemp = result["FMT_appTemp"];
>>>   if (appTemp.length == 5) {
>>> appTemp = "" + appTemp;
>>>   } else if (appTemp.length == 6) {
>>> appTemp = "" + appTemp;
>>>   }

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

OK, ignore my last email.  The accumulators were correct and conversions of 
observations were being done correctly.  But not highs, lows, sums, ...

This is fixed in loopdata 1.3.5.  Please pull it, install it and restart weewx. 
 It should all work with this change.

It’s fortunate (for me) that WeeWX stores rain in cm and defaults to reporting 
it in mm.  Because of that, FMT_SUM_rain revealed the issue (in Metric) and 
that let me fix it.

Thank you for reporting this.
John

> On Jul 3, 2020, at 12:28 PM, John Kline  wrote:
> 
> 
> I found the problem.  The database is storing rain as cm and, as you might 
> expect, the day accumulators were correct.  I however, when I copied the 
> accumulators at startup, was treating them as if they were in the report 
> target units (in this case mm).
> 
> I’ll push a fix today.
> 
>>> On Jul 3, 2020, at 11:14 AM, John Kline  wrote:
>>> 
>> 
>> I’ve duplicated the daily rainfall discrepancy.
>> 
>> I am asking WeeWX for the day summary and initializing my day accumulators 
>> with the day summary.
>> day_summary = dbm._get_day_summary(time.time())
>> 
>> But the day summary accumulator for rain is reporting 1/10 of the actual 
>> rain.  Before I can fix this, I need to take the time to understand why I am 
>> seeing what I am seeing in WeeWX’s day summary.
>> 
 On Jul 3, 2020, at 10:10 AM, Geni 0815  wrote:
 
>>> 
>>> I'm using the latest driver
>>> wget -P / var / tmp 
>>> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
>>> 
>>> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
 
 
 
> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
> 
> 
> All fields are displayed again, we have absolute calm at the moment so I 
> can not see how it works.
> The error kph is desired km / h
 You can ask others how to change a label on a report.  Once you do that, 
 LoopData will use it.
> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
> Indeed, when i curl your page, I see the .6 being generated at reporting 
> time and I can look at your loop-data.txt and see 0.1.  I am actually 
> copying the day summary accumulators, so this is perplexing.  I will 
> investigate this.  I have not run into it since I have been using 
> day_rain_total, which isn’t available in your driver.
> 
> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>> 
>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>> trying to get a document element by the name of FMT_dewpoint, but that 
>> element no longer exists in index.html.
>> 
>> Make the following changes and let me know how it goes.
>> 
>> In index.html.tmpl:
>> Change:
>>  $current.outTemp> id="appTemp">$current.appTemp
>> to:
>> $current.outTemp> id="FMT_appTemp">$current.appTemp
>> 
>> In weewx.conf>LoopData>Include>fields:
>> Change:
>> appTemp
>> to:
>> FMT_appTemp
>> 
>> In realtime_updater.inc:
>> Change:
>>  // dew point  
>>   var dew = result["FMT_dewpoint"];
>>   if (dew.length == 5) {
>> dew = "" + dew;
>>   } else if (dew.length == 6) {
>> dew = "" + dew;
>>   }  
>>  
>> 
>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>> to:
>>  // apparent temp  
>>   var appTemp = result["FMT_appTemp"];
>>   if (appTemp.length == 5) {
>> appTemp = "" + appTemp;
>>   } else if (appTemp.length == 6) {
>> appTemp = "" + appTemp;
>>   }  
>>  
>> 
>>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>> 
 On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
 
>>> 
>>> 
>>> 
>>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
 
 
 
 Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
> 
> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, 
> this could be the problem
> 
>> # Options for extension 'loopdata'
>> [LoopData]
>> [[FileSpec]]
>> loop_data_dir = /home/pi/wetter/loop-data
>> filename = loop-data.txt
>> [[Formatting]]
>> target_report = WeatherBoardReport
>> [[RsyncSpec]]
>> enable = false
>> 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I found the problem.  The database is storing rain as cm and, as you might 
expect, the day accumulators were correct.  I however, when I copied the 
accumulators at startup, was treating them as if they were in the report target 
units (in this case mm).

I’ll push a fix today.

> On Jul 3, 2020, at 11:14 AM, John Kline  wrote:
> 
> 
> I’ve duplicated the daily rainfall discrepancy.
> 
> I am asking WeeWX for the day summary and initializing my day accumulators 
> with the day summary.
> day_summary = dbm._get_day_summary(time.time())
> 
> But the day summary accumulator for rain is reporting 1/10 of the actual 
> rain.  Before I can fix this, I need to take the time to understand why I am 
> seeing what I am seeing in WeeWX’s day summary.
> 
>>> On Jul 3, 2020, at 10:10 AM, Geni 0815  wrote:
>>> 
>> 
>> I'm using the latest driver
>> wget -P / var / tmp 
>> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
>> 
>> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>>> 
>>> 
>>> 
 On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
 
 
 All fields are displayed again, we have absolute calm at the moment so I 
 can not see how it works.
 The error kph is desired km / h
>>> You can ask others how to change a label on a report.  Once you do that, 
>>> LoopData will use it.
 Rain display is wrong where the 0.1mm would come from correctly 0.6mm
 Indeed, when i curl your page, I see the .6 being generated at reporting 
 time and I can look at your loop-data.txt and see 0.1.  I am actually 
 copying the day summary accumulators, so this is perplexing.  I will 
 investigate this.  I have not run into it since I have been using 
 day_rain_total, which isn’t available in your driver.
 
 Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
> 
> You didn’t quite get the change to appTemp correct.  The JavaScript was 
> trying to get a document element by the name of FMT_dewpoint, but that 
> element no longer exists in index.html.
> 
> Make the following changes and let me know how it goes.
> 
> In index.html.tmpl:
> Change:
>  $current.outTemp id="appTemp">$current.appTemp
> to:
> $current.outTemp id="FMT_appTemp">$current.appTemp
> 
> In weewx.conf>LoopData>Include>fields:
> Change:
> appTemp
> to:
> FMT_appTemp
> 
> In realtime_updater.inc:
> Change:
>  // dew point  
>   var dew = result["FMT_dewpoint"];
>   if (dew.length == 5) {
> dew = "" + dew;
>   } else if (dew.length == 6) {
> dew = "" + dew;
>   }   
>   
>   
>   document.getElementById("FMT_dewpoint").innerHTML = dew;
> to:
>  // apparent temp  
>   var appTemp = result["FMT_appTemp"];
>   if (appTemp.length == 5) {
> appTemp = "" + appTemp;
>   } else if (appTemp.length == 6) {
> appTemp = "" + appTemp;
>   }   
>   
>   
>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
> 
>>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
>>> 
>> 
>> 
>> 
>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>>> 
>>> 
>>> 
>>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
 
 The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
 "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, 
 this could be the problem
 
> # Options for extension 'loopdata'
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/pi/wetter/loop-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
> [[RsyncSpec]]
> enable = false
> remote_server = 192.168
> remote_port = 2022
> remote_user = 
> remote_dir = /web/wetter/loop-data
> compress = false
> log_success = false
> ssh_options = -o ConnectTimeout=1
> timeout = 1
> skip_if_older_than = 3
> [[Include]]
> fields = dateTime, windSpeed, COMPASS_windDir, 
> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I’ve duplicated the daily rainfall discrepancy.

I am asking WeeWX for the day summary and initializing my day accumulators with 
the day summary.
day_summary = dbm._get_day_summary(time.time())

But the day summary accumulator for rain is reporting 1/10 of the actual rain.  
Before I can fix this, I need to take the time to understand why I am seeing 
what I am seeing in WeeWX’s day summary.

> On Jul 3, 2020, at 10:10 AM, Geni 0815  wrote:
> 
> 
> I'm using the latest driver
> wget -P / var / tmp 
> https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py
> 
> Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>> 
>> 
>> 
 On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
 
>>> 
>>> All fields are displayed again, we have absolute calm at the moment so I 
>>> can not see how it works.
>>> The error kph is desired km / h
>> You can ask others how to change a label on a report.  Once you do that, 
>> LoopData will use it.
>>> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>>> Indeed, when i curl your page, I see the .6 being generated at reporting 
>>> time and I can look at your loop-data.txt and see 0.1.  I am actually 
>>> copying the day summary accumulators, so this is perplexing.  I will 
>>> investigate this.  I have not run into it since I have been using 
>>> day_rain_total, which isn’t available in your driver.
>>> 
>>> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
 
 You didn’t quite get the change to appTemp correct.  The JavaScript was 
 trying to get a document element by the name of FMT_dewpoint, but that 
 element no longer exists in index.html.
 
 Make the following changes and let me know how it goes.
 
 In index.html.tmpl:
 Change:
  $current.outTemp>>> id="appTemp">$current.appTemp
 to:
 $current.outTemp>>> id="FMT_appTemp">$current.appTemp
 
 In weewx.conf>LoopData>Include>fields:
 Change:
 appTemp
 to:
 FMT_appTemp
 
 In realtime_updater.inc:
 Change:
  // dew point  
   var dew = result["FMT_dewpoint"];
   if (dew.length == 5) {
 dew = "" + dew;
   } else if (dew.length == 6) {
 dew = "" + dew;
   }

   document.getElementById("FMT_dewpoint").innerHTML = dew;
 to:
  // apparent temp  
   var appTemp = result["FMT_appTemp"];
   if (appTemp.length == 5) {
 appTemp = "" + appTemp;
   } else if (appTemp.length == 6) {
 appTemp = "" + appTemp;
   }

   document.getElementById("FMT_appTemp").innerHTML = appTemp;
 
>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
>> 
> 
> 
> 
> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>> 
>> 
>> 
>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>>> 
>>> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
>>> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, 
>>> this could be the problem
>>> 
 # Options for extension 'loopdata'
 [LoopData]
 [[FileSpec]]
 loop_data_dir = /home/pi/wetter/loop-data
 filename = loop-data.txt
 [[Formatting]]
 target_report = WeatherBoardReport
 [[RsyncSpec]]
 enable = false
 remote_server = 192.168
 remote_port = 2022
 remote_user = 
 remote_dir = /web/wetter/loop-data
 compress = false
 log_success = false
 ssh_options = -o ConnectTimeout=1
 timeout = 1
 skip_if_older_than = 3
 [[Include]]
 fields = dateTime, windSpeed, COMPASS_windDir, 
 DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
 FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
 FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
 [[Rename]]
>>> 
>>> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
 
 Your JavaScript has an error. Nothing is updated after it hits that 
 error.  Since the 10m and day high wind is only updated in the 
 JavaScript, they are blank.
 
 Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
 and realtime_updater.inc files.
 
 
 
>> On Jul 3, 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

I'm using the latest driver
wget -P / var / tmp 
https://raw.githubusercontent.com/weewx/weewx/master/bin/weewx/drivers/vantage.py

Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>
>
>
> On Jul 3, 2020, at 9:27 AM, Geni 0815 > 
> wrote:
>
> 
> All fields are displayed again, we have absolute calm at the moment so I 
> can not see how it works.
> The error kph is desired km / h
>
> You can ask others how to change a label on a report.  Once you do that, 
> LoopData will use it.
>
> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>
> Indeed, when i curl your page, I see the .6 being generated at reporting 
>> time and I can look at your loop-data.txt and see 0.1.  I am actually 
>> copying the day summary accumulators, so this is perplexing.  I will 
>> investigate this.  I have not run into it since I have been using 
>> day_rain_total, which isn’t available in your driver.
>>
>
> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>>
>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>> trying to get a document element by the name of FMT_dewpoint, but that 
>> element no longer exists in index.html.
>>
>> Make the following changes and let me know how it goes.
>>
>> In index.html.tmpl:
>> Change:
>>  $current.outTemp> id="appTemp">$current.appTemp
>> to:
>> $current.outTemp> id="FMT_appTemp">$current.appTemp
>>
>> In weewx.conf>LoopData>Include>fields:
>> Change:
>> appTemp
>> to:
>> FMT_appTemp
>>
>> In realtime_updater.inc:
>> Change:
>>  // dew point  
>>   var dew = result["FMT_dewpoint"];
>>   if (dew.length == 5) {
>> dew = "" + dew;
>>   } else if (dew.length == 6) {
>> dew = "" + dew;
>>   }   
>> 
>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>> to:
>>  // apparent temp  
>>   var appTemp = result["FMT_appTemp"];
>>   if (appTemp.length == 5) {
>> appTemp = "" + appTemp;
>>   } else if (appTemp.length == 6) {
>> appTemp = "" + appTemp;
>>   }   
>> 
>>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>>
>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
>>
>> 
>>
>>
>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>>>
>>>
>>>
>>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:

 The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
 "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
 could be the problem

 # Options for extension 'loopdata'
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/pi/wetter/loop-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
> [[RsyncSpec]]
> enable = false
> remote_server = 192.168
> remote_port = 2022
> remote_user = 
> remote_dir = /web/wetter/loop-data
> compress = false
> log_success = false
> ssh_options = -o ConnectTimeout=1
> timeout = 1
> skip_if_older_than = 3
> [[Include]]
> fields = dateTime, windSpeed, COMPASS_windDir, 
> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
> [[Rename]]
>

 Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>
> Your JavaScript has an error. Nothing is updated after it hits that 
> error.  Since the 10m and day high wind is only updated in the 
> JavaScript, 
> they are blank.
>
> Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
> and realtime_updater.inc files.
>
>
>
> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
>
> 
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time 
> streaming updates and interactive charts. Modeled after 
> BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
>
>
> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>>
>> No errors in the syslog
>> appTemp works in loop-data.txt and in the display of weatherboard
>> all wind displays are not displayed correctly and there is no refresh
>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but 
>> the display 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

Except in LoopDate, windspeed is displayed correctly at "km / h" everywhere. In 
all graphics and reports.


Am Freitag, 3. Juli 2020 18:47:16 UTC+2 schrieb John Kline:
>
>
>
> On Jul 3, 2020, at 9:27 AM, Geni 0815 > 
> wrote:
>
> 
> All fields are displayed again, we have absolute calm at the moment so I 
> can not see how it works.
> The error kph is desired km / h
>
> You can ask others how to change a label on a report.  Once you do that, 
>> LoopData will use it.
>>
> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
>
> Indeed, when i curl your page, I see the .6 being generated at reporting 
> time and I can look at your loop-data.txt and see 0.1.  I am actually 
> copying the day summary accumulators, so this is perplexing.  I will 
> investigate this.  I have not run into it since I have been using 
> day_rain_total, which isn’t available in your driver.
>
>
> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>>
>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>> trying to get a document element by the name of FMT_dewpoint, but that 
>> element no longer exists in index.html.
>>
>> Make the following changes and let me know how it goes.
>>
>> In index.html.tmpl:
>> Change:
>>  $current.outTemp> id="appTemp">$current.appTemp
>> to:
>> $current.outTemp> id="FMT_appTemp">$current.appTemp
>>
>> In weewx.conf>LoopData>Include>fields:
>> Change:
>> appTemp
>> to:
>> FMT_appTemp
>>
>> In realtime_updater.inc:
>> Change:
>>  // dew point  
>>   var dew = result["FMT_dewpoint"];
>>   if (dew.length == 5) {
>> dew = "" + dew;
>>   } else if (dew.length == 6) {
>> dew = "" + dew;
>>   }   
>> 
>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>> to:
>>  // apparent temp  
>>   var appTemp = result["FMT_appTemp"];
>>   if (appTemp.length == 5) {
>> appTemp = "" + appTemp;
>>   } else if (appTemp.length == 6) {
>> appTemp = "" + appTemp;
>>   }   
>> 
>>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>>
>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
>>
>> 
>>
>>
>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>>>
>>>
>>>
>>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:

 The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
 "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
 could be the problem

 # Options for extension 'loopdata'
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/pi/wetter/loop-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
> [[RsyncSpec]]
> enable = false
> remote_server = 192.168
> remote_port = 2022
> remote_user = 
> remote_dir = /web/wetter/loop-data
> compress = false
> log_success = false
> ssh_options = -o ConnectTimeout=1
> timeout = 1
> skip_if_older_than = 3
> [[Include]]
> fields = dateTime, windSpeed, COMPASS_windDir, 
> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
> [[Rename]]
>

 Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>
> Your JavaScript has an error. Nothing is updated after it hits that 
> error.  Since the 10m and day high wind is only updated in the 
> JavaScript, 
> they are blank.
>
> Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
> and realtime_updater.inc files.
>
>
>
> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
>
> 
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time 
> streaming updates and interactive charts. Modeled after 
> BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
>
>
> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>>
>> No errors in the syslog
>> appTemp works in loop-data.txt and in the display of weatherboard
>> all wind displays are not displayed correctly and there is no refresh
>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but 
>> the display is 0.6mm
>>
>> Am 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

> On Jul 3, 2020, at 9:27 AM, Geni 0815  wrote:
> 
> 
> All fields are displayed again, we have absolute calm at the moment so I can 
> not see how it works.
> The error kph is desired km / h
You can ask others how to change a label on a report.  Once you do that, 
LoopData will use it.
> Rain display is wrong where the 0.1mm would come from correctly 0.6mm
Indeed, when i curl your page, I see the .6 being generated at reporting time 
and I can look at your loop-data.txt and see 0.1.  I am actually copying the 
day summary accumulators, so this is perplexing.  I will investigate this.  I 
have not run into it since I have been using day_rain_total, which isn’t 
available in your driver.
> 
> Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>> 
>> You didn’t quite get the change to appTemp correct.  The JavaScript was 
>> trying to get a document element by the name of FMT_dewpoint, but that 
>> element no longer exists in index.html.
>> 
>> Make the following changes and let me know how it goes.
>> 
>> In index.html.tmpl:
>> Change:
>>  $current.outTemp> id="appTemp">$current.appTemp
>> to:
>> $current.outTemp> id="FMT_appTemp">$current.appTemp
>> 
>> In weewx.conf>LoopData>Include>fields:
>> Change:
>> appTemp
>> to:
>> FMT_appTemp
>> 
>> In realtime_updater.inc:
>> Change:
>>  // dew point  
>>   var dew = result["FMT_dewpoint"];
>>   if (dew.length == 5) {
>> dew = "" + dew;
>>   } else if (dew.length == 6) {
>> dew = "" + dew;
>>   }  
>>  
>>   document.getElementById("FMT_dewpoint").innerHTML = dew;
>> to:
>>  // apparent temp  
>>   var appTemp = result["FMT_appTemp"];
>>   if (appTemp.length == 5) {
>> appTemp = "" + appTemp;
>>   } else if (appTemp.length == 6) {
>> appTemp = "" + appTemp;
>>   }  
>>  
>>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>> 
 On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
 
>>> 
>>> 
>>> 
>>> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
 
 
 
 Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
> 
> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
> could be the problem
> 
>> # Options for extension 'loopdata'
>> [LoopData]
>> [[FileSpec]]
>> loop_data_dir = /home/pi/wetter/loop-data
>> filename = loop-data.txt
>> [[Formatting]]
>> target_report = WeatherBoardReport
>> [[RsyncSpec]]
>> enable = false
>> remote_server = 192.168
>> remote_port = 2022
>> remote_user = 
>> remote_dir = /web/wetter/loop-data
>> compress = false
>> log_success = false
>> ssh_options = -o ConnectTimeout=1
>> timeout = 1
>> skip_if_older_than = 3
>> [[Include]]
>> fields = dateTime, windSpeed, COMPASS_windDir, 
>> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
>> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
>> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
>> [[Rename]]
> 
> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>> 
>> Your JavaScript has an error. Nothing is updated after it hits that 
>> error.  Since the 10m and day high wind is only updated in the 
>> JavaScript, they are blank.
>> 
>> Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
>> and realtime_updater.inc files.
>> 
>> 
>> 
 On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
 
>>> 
>>> Extension NameVersion   Description
>>> weatherboard  1.1   WeatherBoard skin.
>>> Belchertown   1.2b6 A clean modern skin with real time 
>>> streaming updates and interactive charts. Modeled after 
>>> BelchertownWeather.com
>>> loopdata  1.3.4 Loop statistics for real time reporting.
>>> 
>>> 
>>> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
 
 No errors in the syslog
 appTemp works in loop-data.txt and in the display of weatherboard
 all wind displays are not displayed correctly and there is no refresh
 In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
 display is 0.6mm
 
 Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
> 
> OK, I’ve 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

All fields are displayed again, we have absolute calm at the moment so I 
can not see how it works.
The error kph is desired km / h
Rain display is wrong where the 0.1mm would come from correctly 0.6mm

Am Freitag, 3. Juli 2020 15:44:29 UTC+2 schrieb John Kline:
>
> You didn’t quite get the change to appTemp correct.  The JavaScript was 
> trying to get a document element by the name of FMT_dewpoint, but that 
> element no longer exists in index.html.
>
> Make the following changes and let me know how it goes.
>
> In index.html.tmpl:
> Change:
>  $current.outTemp id="appTemp">$current.appTemp
> to:
> $current.outTemp id="FMT_appTemp">$current.appTemp
>
> In weewx.conf>LoopData>Include>fields:
> Change:
> appTemp
> to:
> FMT_appTemp
>
> In realtime_updater.inc:
> Change:
>  // dew point  
>   var dew = result["FMT_dewpoint"];
>   if (dew.length == 5) {
> dew = "" + dew;
>   } else if (dew.length == 6) {
> dew = "" + dew;
>   }   
> 
>   document.getElementById("FMT_dewpoint").innerHTML = dew;
> to:
>  // apparent temp  
>   var appTemp = result["FMT_appTemp"];
>   if (appTemp.length == 5) {
> appTemp = "" + appTemp;
>   } else if (appTemp.length == 6) {
> appTemp = "" + appTemp;
>   }   
> 
>   document.getElementById("FMT_appTemp").innerHTML = appTemp;
>
> On Jul 3, 2020, at 4:41 AM, Geni 0815 > 
> wrote:
>
> 
>
>
> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>>
>>
>>
>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>>>
>>> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
>>> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
>>> could be the problem
>>>
>>> # Options for extension 'loopdata'
 [LoopData]
 [[FileSpec]]
 loop_data_dir = /home/pi/wetter/loop-data
 filename = loop-data.txt
 [[Formatting]]
 target_report = WeatherBoardReport
 [[RsyncSpec]]
 enable = false
 remote_server = 192.168
 remote_port = 2022
 remote_user = 
 remote_dir = /web/wetter/loop-data
 compress = false
 log_success = false
 ssh_options = -o ConnectTimeout=1
 timeout = 1
 skip_if_older_than = 3
 [[Include]]
 fields = dateTime, windSpeed, COMPASS_windDir, 
 DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
 FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
 FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
 [[Rename]]

>>>
>>> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:

 Your JavaScript has an error. Nothing is updated after it hits that 
 error.  Since the 10m and day high wind is only updated in the JavaScript, 
 they are blank.

 Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
 and realtime_updater.inc files.



 On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:

 
 Extension NameVersion   Description
 weatherboard  1.1   WeatherBoard skin.
 Belchertown   1.2b6 A clean modern skin with real time 
 streaming updates and interactive charts. Modeled after 
 BelchertownWeather.com
 loopdata  1.3.4 Loop statistics for real time reporting.


 Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>
> No errors in the syslog
> appTemp works in loop-data.txt and in the display of weatherboard
> all wind displays are not displayed correctly and there is no refresh
> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
> display is 0.6mm
>
> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>>
>> OK, I’ve pushed new versions of loopdata and weatherboard to user 
>> FMT_SUM_rain rather than FMT_rain_day_total.
>>
>> You asked if appTemp could be displayed.  Yes, it can be included in 
>> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section 
>> of 
>> LoopData in weewx.conf.
>>
>> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
>> copied it to translate the index.  Just change FMT_dewPoint to 
>> FMT_appTemp 
>> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
>> great deal of customization in the browser for the WeatherBoard skin; 
>> but I 
>> don’t see that happening anytime soon.
>>
>> On Jul 2, 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

You didn’t quite get the change to appTemp correct.  The JavaScript was trying 
to get a document element by the name of FMT_dewpoint, but that element no 
longer exists in index.html.

Make the following changes and let me know how it goes.

In index.html.tmpl:
Change:
 $current.outTemp$current.appTemp
to:
$current.outTemp$current.appTemp

In weewx.conf>LoopData>Include>fields:
Change:
appTemp
to:
FMT_appTemp

In realtime_updater.inc:
Change:
 // dew point  
  var dew = result["FMT_dewpoint"];
  if (dew.length == 5) {
dew = "" + dew;
  } else if (dew.length == 6) {
dew = "" + dew;
  } 
  
  document.getElementById("FMT_dewpoint").innerHTML = dew;
to:
 // apparent temp  
  var appTemp = result["FMT_appTemp"];
  if (appTemp.length == 5) {
appTemp = "" + appTemp;
  } else if (appTemp.length == 6) {
appTemp = "" + appTemp;
  } 
  
  document.getElementById("FMT_appTemp").innerHTML = appTemp;

>> On Jul 3, 2020, at 4:41 AM, Geni 0815  wrote:
> 
> 
> 
> Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>> 
>> 
>> 
>> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>>> 
>>> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
>>> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
>>> could be the problem
>>> 
 # Options for extension 'loopdata'
 [LoopData]
 [[FileSpec]]
 loop_data_dir = /home/pi/wetter/loop-data
 filename = loop-data.txt
 [[Formatting]]
 target_report = WeatherBoardReport
 [[RsyncSpec]]
 enable = false
 remote_server = 192.168
 remote_port = 2022
 remote_user = 
 remote_dir = /web/wetter/loop-data
 compress = false
 log_success = false
 ssh_options = -o ConnectTimeout=1
 timeout = 1
 skip_if_older_than = 3
 [[Include]]
 fields = dateTime, windSpeed, COMPASS_windDir, DESC_barometerRate, 
 FMT_barometer, FMT_SUM_rain, FMT_dewpoint, FMT_heatindex, FMT_outHumidity, 
 FMT_outTemp, FMT_rain, FMT_rainRate, FMT_windchill, FMT_windSpeed, 
 FMT_HI_windGust, FMT_10mMaxGust, appTemp
 [[Rename]]
>>> 
>>> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
 
 Your JavaScript has an error. Nothing is updated after it hits that error. 
  Since the 10m and day high wind is only updated in the JavaScript, they 
 are blank.
 
 Please send the LoopData section of WeeWX.conf and the index.html.tmpl and 
 realtime_updater.inc files.
 
 
 
>> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
> 
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
> 
> 
> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>> 
>> No errors in the syslog
>> appTemp works in loop-data.txt and in the display of weatherboard
>> all wind displays are not displayed correctly and there is no refresh
>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
>> display is 0.6mm
>> 
>> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>>> 
>>> OK, I’ve pushed new versions of loopdata and weatherboard to user 
>>> FMT_SUM_rain rather than FMT_rain_day_total.
>>> 
>>> You asked if appTemp could be displayed.  Yes, it can be included in 
>>> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section 
>>> of LoopData in weewx.conf.
>>> 
>>> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
>>> copied it to translate the index.  Just change FMT_dewPoint to 
>>> FMT_appTemp in index.html and realtime_updater.txt.  Someday, I hope to 
>>> allow for a great deal of customization in the browser for the 
>>> WeatherBoard skin; but I don’t see that happening anytime soon.
>>> 
> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
 
 One more place to change.
 Change the LoopData>Include section in weewx.conf.  That should 
 include FMT_SUM_rain rather than FMT_day_rain_total.
 
 In addition to changing WeatherBoard, I’ll change the doc in LoopData 
 as day_rain_total is likely to be a source 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

Am Freitag, 3. Juli 2020 13:31:49 UTC+2 schrieb Geni 0815:
>
>
>
> Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>>
>> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
>> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
>> could be the problem
>>
>> # Options for extension 'loopdata'
>>> [LoopData]
>>> [[FileSpec]]
>>> loop_data_dir = /home/pi/wetter/loop-data
>>> filename = loop-data.txt
>>> [[Formatting]]
>>> target_report = WeatherBoardReport
>>> [[RsyncSpec]]
>>> enable = false
>>> remote_server = 192.168
>>> remote_port = 2022
>>> remote_user = 
>>> remote_dir = /web/wetter/loop-data
>>> compress = false
>>> log_success = false
>>> ssh_options = -o ConnectTimeout=1
>>> timeout = 1
>>> skip_if_older_than = 3
>>> [[Include]]
>>> fields = dateTime, windSpeed, COMPASS_windDir, 
>>> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
>>> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
>>> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
>>> [[Rename]]
>>>
>>
>> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>>>
>>> Your JavaScript has an error. Nothing is updated after it hits that 
>>> error.  Since the 10m and day high wind is only updated in the JavaScript, 
>>> they are blank.
>>>
>>> Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
>>> and realtime_updater.inc files.
>>>
>>>
>>>
>>> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
>>>
>>> 
>>> Extension NameVersion   Description
>>> weatherboard  1.1   WeatherBoard skin.
>>> Belchertown   1.2b6 A clean modern skin with real time streaming 
>>> updates and interactive charts. Modeled after BelchertownWeather.com
>>> loopdata  1.3.4 Loop statistics for real time reporting.
>>>
>>>
>>> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:

 No errors in the syslog
 appTemp works in loop-data.txt and in the display of weatherboard
 all wind displays are not displayed correctly and there is no refresh
 In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
 display is 0.6mm

 Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>
> OK, I’ve pushed new versions of loopdata and weatherboard to user 
> FMT_SUM_rain rather than FMT_rain_day_total.
>
> You asked if appTemp could be displayed.  Yes, it can be included in 
> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section 
> of 
> LoopData in weewx.conf.
>
> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
> copied it to translate the index.  Just change FMT_dewPoint to 
> FMT_appTemp 
> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
> great deal of customization in the browser for the WeatherBoard skin; but 
> I 
> don’t see that happening anytime soon.
>
> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
>
> 
> One more place to change.
> Change the LoopData>Include section in weewx.conf.  That should 
> include FMT_SUM_rain rather than FMT_day_rain_total.
>
> In addition to changing WeatherBoard, I’ll change the doc in LoopData 
> as day_rain_total is likely to be a source of confusion for many.
>
>
>
> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
>
> 
>
>
> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
>
> 
> Errors are no longer logged
>
> That’s good.
>
> The translation doesn't work anymore:
> [[Rename]]
> kph = kmh
>
> The README says:
>
>- Rename : Used to specify which fields to include and which names 
>should be used as keys (i.e., what these fields should be renamed. If 
>neither Rename nor fields is specified, all fields are included.
>
> Perhaps I need to explain it better.  Rename is used to change the 
> name of the keys in the json (loop-data.txt) file.  It would be used if 
> you 
> have existing JavaScript expecting a different key for an observation.
>
> The good news is that all formatting, conversion, labels, etc. is 
> controlled by the skin you have targeted.  Just change the unit_label for 
> in the skin and the loop-data.txt file will automagically reflect your 
> change.
>
> Rain amount is not in the loop-data.txt
>
> WeatherBoard is using day_rain_total, which is in the loop packet for 
> my weather station, but not yours.  It’s likely you have a rain 
> observation 
> in the loop packet — simply called rain.  SUM_rain would yield the same 
> thing as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
> index.html.tmpl and realtime_updater.inc 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

Am Freitag, 3. Juli 2020 13:29:40 UTC+2 schrieb Geni 0815:
>
> The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
> "FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
> could be the problem
>
> # Options for extension 'loopdata'
>> [LoopData]
>> [[FileSpec]]
>> loop_data_dir = /home/pi/wetter/loop-data
>> filename = loop-data.txt
>> [[Formatting]]
>> target_report = WeatherBoardReport
>> [[RsyncSpec]]
>> enable = false
>> remote_server = 192.168
>> remote_port = 2022
>> remote_user = 
>> remote_dir = /web/wetter/loop-data
>> compress = false
>> log_success = false
>> ssh_options = -o ConnectTimeout=1
>> timeout = 1
>> skip_if_older_than = 3
>> [[Include]]
>> fields = dateTime, windSpeed, COMPASS_windDir, 
>> DESC_barometerRate, FMT_barometer, FMT_SUM_rain, FMT_dewpoint, 
>> FMT_heatindex, FMT_outHumidity, FMT_outTemp, FMT_rain, FMT_rainRate, 
>> FMT_windchill, FMT_windSpeed, FMT_HI_windGust, FMT_10mMaxGust, appTemp
>> [[Rename]]
>>
>
> Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>>
>> Your JavaScript has an error. Nothing is updated after it hits that 
>> error.  Since the 10m and day high wind is only updated in the JavaScript, 
>> they are blank.
>>
>> Please send the LoopData section of WeeWX.conf and the index.html.tmpl 
>> and realtime_updater.inc files.
>>
>>
>>
>> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
>>
>> 
>> Extension NameVersion   Description
>> weatherboard  1.1   WeatherBoard skin.
>> Belchertown   1.2b6 A clean modern skin with real time streaming 
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> loopdata  1.3.4 Loop statistics for real time reporting.
>>
>>
>> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>>>
>>> No errors in the syslog
>>> appTemp works in loop-data.txt and in the display of weatherboard
>>> all wind displays are not displayed correctly and there is no refresh
>>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
>>> display is 0.6mm
>>>
>>> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:

 OK, I’ve pushed new versions of loopdata and weatherboard to user 
 FMT_SUM_rain rather than FMT_rain_day_total.

 You asked if appTemp could be displayed.  Yes, it can be included in 
 loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
 LoopData in weewx.conf.

 Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
 copied it to translate the index.  Just change FMT_dewPoint to FMT_appTemp 
 in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
 great deal of customization in the browser for the WeatherBoard skin; but 
 I 
 don’t see that happening anytime soon.

 On Jul 2, 2020, at 10:59 PM, John Kline  wrote:

 
 One more place to change.
 Change the LoopData>Include section in weewx.conf.  That should include 
 FMT_SUM_rain rather than FMT_day_rain_total.

 In addition to changing WeatherBoard, I’ll change the doc in LoopData 
 as day_rain_total is likely to be a source of confusion for many.



 On Jul 2, 2020, at 10:51 PM, John Kline  wrote:

 


 On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:

 
 Errors are no longer logged

 That’s good.

 The translation doesn't work anymore:
 [[Rename]]
 kph = kmh

 The README says:

- Rename : Used to specify which fields to include and which names 
should be used as keys (i.e., what these fields should be renamed. If 
neither Rename nor fields is specified, all fields are included.

 Perhaps I need to explain it better.  Rename is used to change the name 
 of the keys in the json (loop-data.txt) file.  It would be used if you 
 have 
 existing JavaScript expecting a different key for an observation.

 The good news is that all formatting, conversion, labels, etc. is 
 controlled by the skin you have targeted.  Just change the unit_label for 
 in the skin and the loop-data.txt file will automagically reflect your 
 change.

 Rain amount is not in the loop-data.txt

 WeatherBoard is using day_rain_total, which is in the loop packet for 
 my weather station, but not yours.  It’s likely you have a rain 
 observation 
 in the loop packet — simply called rain.  SUM_rain would yield the same 
 thing as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
 index.html.tmpl and realtime_updater.inc files and change 
 FMT_day_rain_total to FMT_SUM_rain and you should be good to go.  I will 
 update WeatherBoard with this change shortly.

 Cheers,
 John


 Currently live 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

The values "FMT_windSpeed": "0.0 kph", "FMT_HI_windGust": "14.5 kph", 
"FMT_10mMaxGust": "4.8 kph", have the label kph directly with them, this 
could be the problem

# Options for extension 'loopdata'
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/pi/wetter/loop-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
> [[RsyncSpec]]
> enable = false
> remote_server = 192.168
> remote_port = 2022
> remote_user = 
> remote_dir = /web/wetter/loop-data
> compress = false
> log_success = false
> ssh_options = -o ConnectTimeout=1
> timeout = 1
> skip_if_older_than = 3
> [[Include]]
> fields = dateTime, windSpeed, COMPASS_windDir, DESC_barometerRate, 
> FMT_barometer, FMT_SUM_rain, FMT_dewpoint, FMT_heatindex, FMT_outHumidity, 
> FMT_outTemp, FMT_rain, FMT_rainRate, FMT_windchill, FMT_windSpeed, 
> FMT_HI_windGust, FMT_10mMaxGust, appTemp
> [[Rename]]
>

Am Freitag, 3. Juli 2020 13:21:48 UTC+2 schrieb John Kline:
>
> Your JavaScript has an error. Nothing is updated after it hits that error. 
>  Since the 10m and day high wind is only updated in the JavaScript, they 
> are blank.
>
> Please send the LoopData section of WeeWX.conf and the index.html.tmpl and 
> realtime_updater.inc files.
>
>
>
> On Jul 3, 2020, at 3:56 AM, Geni 0815 > 
> wrote:
>
> 
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
>
>
> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>>
>> No errors in the syslog
>> appTemp works in loop-data.txt and in the display of weatherboard
>> all wind displays are not displayed correctly and there is no refresh
>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
>> display is 0.6mm
>>
>> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>>>
>>> OK, I’ve pushed new versions of loopdata and weatherboard to user 
>>> FMT_SUM_rain rather than FMT_rain_day_total.
>>>
>>> You asked if appTemp could be displayed.  Yes, it can be included in 
>>> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
>>> LoopData in weewx.conf.
>>>
>>> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
>>> copied it to translate the index.  Just change FMT_dewPoint to FMT_appTemp 
>>> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
>>> great deal of customization in the browser for the WeatherBoard skin; but I 
>>> don’t see that happening anytime soon.
>>>
>>> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
>>>
>>> 
>>> One more place to change.
>>> Change the LoopData>Include section in weewx.conf.  That should include 
>>> FMT_SUM_rain rather than FMT_day_rain_total.
>>>
>>> In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
>>> day_rain_total is likely to be a source of confusion for many.
>>>
>>>
>>>
>>> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
>>>
>>> 
>>>
>>>
>>> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
>>>
>>> 
>>> Errors are no longer logged
>>>
>>> That’s good.
>>>
>>> The translation doesn't work anymore:
>>> [[Rename]]
>>> kph = kmh
>>>
>>> The README says:
>>>
>>>- Rename : Used to specify which fields to include and which names 
>>>should be used as keys (i.e., what these fields should be renamed. If 
>>>neither Rename nor fields is specified, all fields are included.
>>>
>>> Perhaps I need to explain it better.  Rename is used to change the name 
>>> of the keys in the json (loop-data.txt) file.  It would be used if you have 
>>> existing JavaScript expecting a different key for an observation.
>>>
>>> The good news is that all formatting, conversion, labels, etc. is 
>>> controlled by the skin you have targeted.  Just change the unit_label for 
>>> in the skin and the loop-data.txt file will automagically reflect your 
>>> change.
>>>
>>> Rain amount is not in the loop-data.txt
>>>
>>> WeatherBoard is using day_rain_total, which is in the loop packet for my 
>>> weather station, but not yours.  It’s likely you have a rain observation in 
>>> the loop packet — simply called rain.  SUM_rain would yield the same thing 
>>> as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
>>> index.html.tmpl and realtime_updater.inc files and change 
>>> FMT_day_rain_total to FMT_SUM_rain and you should be good to go.  I will 
>>> update WeatherBoard with this change shortly.
>>>
>>> Cheers,
>>> John
>>>
>>>
>>> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>>>
>>> Is it possible to get the appTemp displayed?
>>>
>>> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:


 -- 
> You received 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

Your JavaScript has an error. Nothing is updated after it hits that error.  
Since the 10m and day high wind is only updated in the JavaScript, they are 
blank.

Please send the LoopData section of WeeWX.conf and the index.html.tmpl and 
realtime_updater.inc files.



> On Jul 3, 2020, at 3:56 AM, Geni 0815  wrote:
> 
> 
> Extension NameVersion   Description
> weatherboard  1.1   WeatherBoard skin.
> Belchertown   1.2b6 A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.4 Loop statistics for real time reporting.
> 
> 
> Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>> 
>> No errors in the syslog
>> appTemp works in loop-data.txt and in the display of weatherboard
>> all wind displays are not displayed correctly and there is no refresh
>> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
>> display is 0.6mm
>> 
>> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>>> 
>>> OK, I’ve pushed new versions of loopdata and weatherboard to user 
>>> FMT_SUM_rain rather than FMT_rain_day_total.
>>> 
>>> You asked if appTemp could be displayed.  Yes, it can be included in 
>>> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
>>> LoopData in weewx.conf.
>>> 
>>> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
>>> copied it to translate the index.  Just change FMT_dewPoint to FMT_appTemp 
>>> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
>>> great deal of customization in the browser for the WeatherBoard skin; but I 
>>> don’t see that happening anytime soon.
>>> 
> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
> 
 
 One more place to change.
 Change the LoopData>Include section in weewx.conf.  That should include 
 FMT_SUM_rain rather than FMT_day_rain_total.
 
 In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
 day_rain_total is likely to be a source of confusion for many.
 
 
 
>> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
>> 
> 
> 
> 
>>> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
>>> 
>> 
>> Errors are no longer logged
> That’s good.
> 
>> The translation doesn't work anymore:
>> [[Rename]]
>> kph = kmh
> The README says:
> Rename : Used to specify which fields to include and which names should 
> be used as keys (i.e., what these fields should be renamed. If neither 
> Rename nor fields is specified, all fields are included.
> Perhaps I need to explain it better.  Rename is used to change the name 
> of the keys in the json (loop-data.txt) file.  It would be used if you 
> have existing JavaScript expecting a different key for an observation.
> 
> The good news is that all formatting, conversion, labels, etc. is 
> controlled by the skin you have targeted.  Just change the unit_label for 
> in the skin and the loop-data.txt file will automagically reflect your 
> change.
> 
>> Rain amount is not in the loop-data.txt
> WeatherBoard is using day_rain_total, which is in the loop packet for my 
> weather station, but not yours.  It’s likely you have a rain observation 
> in the loop packet — simply called rain.  SUM_rain would yield the same 
> thing as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
> index.html.tmpl and realtime_updater.inc files and change 
> FMT_day_rain_total to FMT_SUM_rain and you should be good to go.  I will 
> update WeatherBoard with this change shortly.
> 
> Cheers,
> John
> 
>> 
>> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>> 
>> Is it possible to get the appTemp displayed?
>> 
>> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
>>> 
>>> 
> 
> -- 
> 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/230623f3-cd31-41f1-a7bd-b7238d5fd822o%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/DEFAFFBA-4B64-4865-89AC-0EB5A307D92E%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

Extension NameVersion   Description
weatherboard  1.1   WeatherBoard skin.
Belchertown   1.2b6 A clean modern skin with real time streaming 
updates and interactive charts. Modeled after BelchertownWeather.com
loopdata  1.3.4 Loop statistics for real time reporting.


Am Freitag, 3. Juli 2020 12:55:00 UTC+2 schrieb Geni 0815:
>
> No errors in the syslog
> appTemp works in loop-data.txt and in the display of weatherboard
> all wind displays are not displayed correctly and there is no refresh
> In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
> display is 0.6mm
>
> Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>>
>> OK, I’ve pushed new versions of loopdata and weatherboard to user 
>> FMT_SUM_rain rather than FMT_rain_day_total.
>>
>> You asked if appTemp could be displayed.  Yes, it can be included in 
>> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
>> LoopData in weewx.conf.
>>
>> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
>> copied it to translate the index.  Just change FMT_dewPoint to FMT_appTemp 
>> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
>> great deal of customization in the browser for the WeatherBoard skin; but I 
>> don’t see that happening anytime soon.
>>
>> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
>>
>> 
>> One more place to change.
>> Change the LoopData>Include section in weewx.conf.  That should include 
>> FMT_SUM_rain rather than FMT_day_rain_total.
>>
>> In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
>> day_rain_total is likely to be a source of confusion for many.
>>
>>
>>
>> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
>>
>> 
>>
>>
>> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
>>
>> 
>> Errors are no longer logged
>>
>> That’s good.
>>
>> The translation doesn't work anymore:
>> [[Rename]]
>> kph = kmh
>>
>> The README says:
>>
>>- Rename : Used to specify which fields to include and which names 
>>should be used as keys (i.e., what these fields should be renamed. If 
>>neither Rename nor fields is specified, all fields are included.
>>
>> Perhaps I need to explain it better.  Rename is used to change the name 
>> of the keys in the json (loop-data.txt) file.  It would be used if you have 
>> existing JavaScript expecting a different key for an observation.
>>
>> The good news is that all formatting, conversion, labels, etc. is 
>> controlled by the skin you have targeted.  Just change the unit_label for 
>> in the skin and the loop-data.txt file will automagically reflect your 
>> change.
>>
>> Rain amount is not in the loop-data.txt
>>
>> WeatherBoard is using day_rain_total, which is in the loop packet for my 
>> weather station, but not yours.  It’s likely you have a rain observation in 
>> the loop packet — simply called rain.  SUM_rain would yield the same thing 
>> as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
>> index.html.tmpl and realtime_updater.inc files and change 
>> FMT_day_rain_total to FMT_SUM_rain and you should be good to go.  I will 
>> update WeatherBoard with this change shortly.
>>
>> Cheers,
>> John
>>
>>
>> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>>
>> Is it possible to get the appTemp displayed?
>>
>> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
>>>
>>>
>>>

-- 
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/230623f3-cd31-41f1-a7bd-b7238d5fd822o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

No errors in the syslog
appTemp works in loop-data.txt and in the display of weatherboard
all wind displays are not displayed correctly and there is no refresh
In the loop-date.txt there is always "FMT_SUM_rain": "0.1 mm", but the 
display is 0.6mm

Am Freitag, 3. Juli 2020 08:32:56 UTC+2 schrieb John Kline:
>
> OK, I’ve pushed new versions of loopdata and weatherboard to user 
> FMT_SUM_rain rather than FMT_rain_day_total.
>
> You asked if appTemp could be displayed.  Yes, it can be included in 
> loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
> LoopData in weewx.conf.
>
> Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve 
> copied it to translate the index.  Just change FMT_dewPoint to FMT_appTemp 
> in index.html and realtime_updater.txt.  Someday, I hope to allow for a 
> great deal of customization in the browser for the WeatherBoard skin; but I 
> don’t see that happening anytime soon.
>
> On Jul 2, 2020, at 10:59 PM, John Kline > 
> wrote:
>
> 
> One more place to change.
> Change the LoopData>Include section in weewx.conf.  That should include 
> FMT_SUM_rain rather than FMT_day_rain_total.
>
> In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
> day_rain_total is likely to be a source of confusion for many.
>
>
>
> On Jul 2, 2020, at 10:51 PM, John Kline > 
> wrote:
>
> 
>
>
> On Jul 2, 2020, at 10:28 PM, Geni 0815 > 
> wrote:
>
> 
> Errors are no longer logged
>
> That’s good.
>
> The translation doesn't work anymore:
> [[Rename]]
> kph = kmh
>
> The README says:
>
>- Rename : Used to specify which fields to include and which names 
>should be used as keys (i.e., what these fields should be renamed. If 
>neither Rename nor fields is specified, all fields are included.
>
> Perhaps I need to explain it better.  Rename is used to change the name of 
> the keys in the json (loop-data.txt) file.  It would be used if you have 
> existing JavaScript expecting a different key for an observation.
>
> The good news is that all formatting, conversion, labels, etc. is 
> controlled by the skin you have targeted.  Just change the unit_label for 
> in the skin and the loop-data.txt file will automagically reflect your 
> change.
>
> Rain amount is not in the loop-data.txt
>
> WeatherBoard is using day_rain_total, which is in the loop packet for my 
> weather station, but not yours.  It’s likely you have a rain observation in 
> the loop packet — simply called rain.  SUM_rain would yield the same thing 
> as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
> index.html.tmpl and realtime_updater.inc files and change 
> FMT_day_rain_total to FMT_SUM_rain and you should be good to go.  I will 
> update WeatherBoard with this change shortly.
>
> Cheers,
> John
>
>
> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>
> Is it possible to get the appTemp displayed?
>
> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
>>
>>
>>

-- 
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/05093f02-f4ea-415f-aed0-b404e9e54c0eo%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

OK, I’ve pushed new versions of loopdata and weatherboard to user FMT_SUM_rain 
rather than FMT_rain_day_total.

You asked if appTemp could be displayed.  Yes, it can be included in 
loop-data.txt by adding appTemp (or FMT_appTemp) to the Include section of 
LoopData in weewx.conf.

Perhaps you are asking if I can add it to WeatherBoard.  I see you’ve copied it 
to translate the index.  Just change FMT_dewPoint to FMT_appTemp in index.html 
and realtime_updater.txt.  Someday, I hope to allow for a great deal of 
customization in the browser for the WeatherBoard skin; but I don’t see that 
happening anytime soon.

> On Jul 2, 2020, at 10:59 PM, John Kline  wrote:
> 
> 
> One more place to change.
> Change the LoopData>Include section in weewx.conf.  That should include 
> FMT_SUM_rain rather than FMT_day_rain_total.
> 
> In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
> day_rain_total is likely to be a source of confusion for many.
> 
> 
> 
>>> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
>>> 
>> 
>> 
>> 
 On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
 
>>> 
>>> Errors are no longer logged
>> That’s good.
>> 
>>> The translation doesn't work anymore:
>>> [[Rename]]
>>> kph = kmh
>> The README says:
>> Rename : Used to specify which fields to include and which names should be 
>> used as keys (i.e., what these fields should be renamed. If neither Rename 
>> nor fields is specified, all fields are included.
>> Perhaps I need to explain it better.  Rename is used to change the name of 
>> the keys in the json (loop-data.txt) file.  It would be used if you have 
>> existing JavaScript expecting a different key for an observation.
>> 
>> The good news is that all formatting, conversion, labels, etc. is controlled 
>> by the skin you have targeted.  Just change the unit_label for in the skin 
>> and the loop-data.txt file will automagically reflect your change.
>> 
>>> Rain amount is not in the loop-data.txt
>> WeatherBoard is using day_rain_total, which is in the loop packet for my 
>> weather station, but not yours.  It’s likely you have a rain observation in 
>> the loop packet — simply called rain.  SUM_rain would yield the same thing 
>> as day_rain_total.  So, to fix this issue, edit WeatherBoard’s 
>> index.html.tmpl and realtime_updater.inc files and change FMT_day_rain_total 
>> to FMT_SUM_rain and you should be good to go.  I will update WeatherBoard 
>> with this change shortly.
>> 
>> Cheers,
>> John
>> 
>>> 
>>> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>>> 
>>> Is it possible to get the appTemp displayed?
>>> 
>>> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
 
 

-- 
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/C398BB5F-D5E3-4C33-BA6E-E895A60F1BE5%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

One more place to change.
Change the LoopData>Include section in weewx.conf.  That should include 
FMT_SUM_rain rather than FMT_day_rain_total.

In addition to changing WeatherBoard, I’ll change the doc in LoopData as 
day_rain_total is likely to be a source of confusion for many.



> On Jul 2, 2020, at 10:51 PM, John Kline  wrote:
> 
> 
> 
> 
>>> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
>>> 
>> 
>> Errors are no longer logged
> That’s good.
> 
>> The translation doesn't work anymore:
>> [[Rename]]
>> kph = kmh
> The README says:
> Rename : Used to specify which fields to include and which names should be 
> used as keys (i.e., what these fields should be renamed. If neither Rename 
> nor fields is specified, all fields are included.
> Perhaps I need to explain it better.  Rename is used to change the name of 
> the keys in the json (loop-data.txt) file.  It would be used if you have 
> existing JavaScript expecting a different key for an observation.
> 
> The good news is that all formatting, conversion, labels, etc. is controlled 
> by the skin you have targeted.  Just change the unit_label for in the skin 
> and the loop-data.txt file will automagically reflect your change.
> 
>> Rain amount is not in the loop-data.txt
> WeatherBoard is using day_rain_total, which is in the loop packet for my 
> weather station, but not yours.  It’s likely you have a rain observation in 
> the loop packet — simply called rain.  SUM_rain would yield the same thing as 
> day_rain_total.  So, to fix this issue, edit WeatherBoard’s index.html.tmpl 
> and realtime_updater.inc files and change FMT_day_rain_total to FMT_SUM_rain 
> and you should be good to go.  I will update WeatherBoard with this change 
> shortly.
> 
> Cheers,
> John
> 
>> 
>> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
>> 
>> Is it possible to get the appTemp displayed?
>> 
>> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
>>> 
>>> 

-- 
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/476D4157-35CB-4AA0-950D-0CC329C5FD5B%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

>> On Jul 2, 2020, at 10:28 PM, Geni 0815  wrote:
> 
> Errors are no longer logged
That’s good.

> The translation doesn't work anymore:
> [[Rename]]
> kph = kmh
The README says:
Rename : Used to specify which fields to include and which names should be used 
as keys (i.e., what these fields should be renamed. If neither Rename nor 
fields is specified, all fields are included.
Perhaps I need to explain it better.  Rename is used to change the name of the 
keys in the json (loop-data.txt) file.  It would be used if you have existing 
JavaScript expecting a different key for an observation.

The good news is that all formatting, conversion, labels, etc. is controlled by 
the skin you have targeted.  Just change the unit_label for in the skin and the 
loop-data.txt file will automagically reflect your change.

> Rain amount is not in the loop-data.txt
WeatherBoard is using day_rain_total, which is in the loop packet for my 
weather station, but not yours.  It’s likely you have a rain observation in the 
loop packet — simply called rain.  SUM_rain would yield the same thing as 
day_rain_total.  So, to fix this issue, edit WeatherBoard’s index.html.tmpl and 
realtime_updater.inc files and change FMT_day_rain_total to FMT_SUM_rain and 
you should be good to go.  I will update WeatherBoard with this change shortly.

Cheers,
John

> 
> Currently live here: https://affolter.familyds.net/wetter/weatherboard/
> 
> Is it possible to get the appTemp displayed?
> 
> Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:

-- 
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/AB74E45E-5F74-4164-8A88-ED6F34DFE0A4%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

Errors are no longer logged
The translation doesn't work anymore:
[[Rename]]
kph = kmh
Rain amount is not in the loop-data.txt

Currently live here: https://affolter.familyds.net/wetter/weatherboard/

Is it possible to get the appTemp displayed?

Am Donnerstag, 2. Juli 2020 20:33:09 UTC+2 schrieb John Kline:
>
> 1.3.3 is pushed.  I won’t try to format the sums of unix_epoch observation 
> types.
>
> Please let me know how this works for you.
>
> Cheers,
> John
>
> On Jul 2, 2020, at 11:22 AM, John Kline > 
> wrote:
>
> 
> On second thought, I can think of reasons to have times in the packet. 
>  So, I take back
> being very interested in the log info from version 1.3.2.
>
> I’ll push a 1.3.3 shortly that skips formatting the sum of unix_epoch 
> observations.
>
> On Jul 2, 2020, at 10:44 AM, John Kline > 
> wrote:
>
> 
> OK, I pushed 1.3.2.  It will catch and skip the FMT_SUM_ when 
> something goes wrong.
> It will also log the incident and include the obstype, the unit_type and 
> the unit_group.  I am VERY
> interested in seeing this information.  Please send it.
>
> Cheers,
> John
>
> On Jul 2, 2020, at 10:21 AM, John Kline > 
> wrote:
>
> 
> It’s formatting a sum for a unix_epoch type.  Sum doesn’t make sense for 
> this type; but the observation,
> which I unfortunately don’t log, seems to have a scalar accumulator.
>
> This doesn’t seem right to me.  I could skip summing, etc. for this type; 
> but this is strange.
>
> I’ll put out an update today that works around this, and logs it, please 
> get back to me with the actual
> observation you see in the log with hew new version.
>
> On Jul 2, 2020, at 9:45 AM, Geni 0815 > 
> wrote:
>
> 
> At the moment I have the following errors
> Since no loop-data.txt is generated, rsync is diabled
>
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>> Traceback (most recent call last):
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>   self.convert_units(pkt, obstype)
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>   self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 685, in 
>> convert_hi_lo_etc_units
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>   pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
>> unit_type, unit_group))
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/units.py", line 758, in toString
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>   time.localtime(val_t[0]))
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>> OverflowError: timestamp out of range for platform time_t
>>
>> pi@Wetter-Raspi:~/wetter/loop-data $ ^C
>> pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
>> Extension NameVersion   Description
>> weatherboard  1.0   WeatherBoard skin.
>> Belchertown   1.1   A clean modern skin with real time streaming 
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> loopdata  1.3.1 Loop statistics for real time reporting.
>>
>>
> Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
>>
>> I added this section to the README:
>>
>> Rsync "errors" in the log:
>>
>> If one is using rsync, especially if the loop interval is short (e.g., 
>> 2s), it is expected that
>>
>> there will be log entries for connection timeouts, data timeouts and 
>> skipped packets.
>>
>> By default only one second is allowed to connect or transmit the data. 
>> Also, by default,
>>
>> if the loop data is older than 3s, it is skipped. With these settings, 
>> the remote server
>>
>> may miss receiving some loop-data packets, but it won't get caught behind 
>> trying to
>>
>> send a backlog of old loop data.
>>
>>
>> Following are examples of a connection timeout, a data transmission 
>> timeout and a
>>
>> skipped packet. These errors are fine in moderation. If too many packets 
>> are timing out,
>>
>> one might try changing the connection timeout or timeout values 
>> (depending on whether
>>
>> the timeouts are in the connection or the transmission).
>>
>> Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
>> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
>> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
>> reported errors: ssh: connect to host 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

1.3.3 is pushed.  I won’t try to format the sums of unix_epoch observation 
types.

Please let me know how this works for you.

Cheers,
John

> On Jul 2, 2020, at 11:22 AM, John Kline  wrote:
> 
> 
> On second thought, I can think of reasons to have times in the packet.  So, I 
> take back
> being very interested in the log info from version 1.3.2.
> 
> I’ll push a 1.3.3 shortly that skips formatting the sum of unix_epoch 
> observations.
> 
>>> On Jul 2, 2020, at 10:44 AM, John Kline  wrote:
>>> 
>> 
>> OK, I pushed 1.3.2.  It will catch and skip the FMT_SUM_ when something 
>> goes wrong.
>> It will also log the incident and include the obstype, the unit_type and the 
>> unit_group.  I am VERY
>> interested in seeing this information.  Please send it.
>> 
>> Cheers,
>> John
>> 
 On Jul 2, 2020, at 10:21 AM, John Kline  wrote:
 
>>> 
>>> It’s formatting a sum for a unix_epoch type.  Sum doesn’t make sense for 
>>> this type; but the observation,
>>> which I unfortunately don’t log, seems to have a scalar accumulator.
>>> 
>>> This doesn’t seem right to me.  I could skip summing, etc. for this type; 
>>> but this is strange.
>>> 
>>> I’ll put out an update today that works around this, and logs it, please 
>>> get back to me with the actual
>>> observation you see in the log with hew new version.
>>> 
> On Jul 2, 2020, at 9:45 AM, Geni 0815  wrote:
> 
 
 At the moment I have the following errors
 Since no loop-data.txt is generated, rsync is diabled
 
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> Traceback (most recent call last):
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>   File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> self.convert_units(pkt, obstype)
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>   File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>   File "/usr/share/weewx/user/loopdata.py", line 685, in 
> convert_hi_lo_etc_units
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
> unit_type, unit_group))
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>   File "/usr/share/weewx/weewx/units.py", line 758, in toString
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> time.localtime(val_t[0]))
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> OverflowError: timestamp out of range for platform time_t
> 
> pi@Wetter-Raspi:~/wetter/loop-data $ ^C
> pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
> Extension NameVersion   Description
> weatherboard  1.0   WeatherBoard skin.
> Belchertown   1.1   A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.1 Loop statistics for real time reporting.
> 
 
 Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
> 
> I added this section to the README:
> 
> Rsync "errors" in the log:
> 
> If one is using rsync, especially if the loop interval is short (e.g., 
> 2s), it is expected that
> 
> there will be log entries for connection timeouts, data timeouts and 
> skipped packets.
> 
> By default only one second is allowed to connect or transmit the data. 
> Also, by default,
> 
> if the loop data is older than 3s, it is skipped. With these settings, 
> the remote server
> 
> may miss receiving some loop-data packets, but it won't get caught behind 
> trying to
> 
> send a backlog of old loop data.
> 
> 
> 
> Following are examples of a connection timeout, a data transmission 
> timeout and a
> 
> skipped packet. These errors are fine in moderation. If too many packets 
> are timing out,
> 
> one might try changing the connection timeout or timeout values 
> (depending on whether
> 
> the timeouts are in the connection or the transmission).
> 
> Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
> reported errors: ssh: connect to host www.paloaltoweather.com port 22: 
> 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

On second thought, I can think of reasons to have times in the packet.  So, I 
take back
being very interested in the log info from version 1.3.2.

I’ll push a 1.3.3 shortly that skips formatting the sum of unix_epoch 
observations.

> On Jul 2, 2020, at 10:44 AM, John Kline  wrote:
> 
> 
> OK, I pushed 1.3.2.  It will catch and skip the FMT_SUM_ when something 
> goes wrong.
> It will also log the incident and include the obstype, the unit_type and the 
> unit_group.  I am VERY
> interested in seeing this information.  Please send it.
> 
> Cheers,
> John
> 
>>> On Jul 2, 2020, at 10:21 AM, John Kline  wrote:
>>> 
>> 
>> It’s formatting a sum for a unix_epoch type.  Sum doesn’t make sense for 
>> this type; but the observation,
>> which I unfortunately don’t log, seems to have a scalar accumulator.
>> 
>> This doesn’t seem right to me.  I could skip summing, etc. for this type; 
>> but this is strange.
>> 
>> I’ll put out an update today that works around this, and logs it, please get 
>> back to me with the actual
>> observation you see in the log with hew new version.
>> 
 On Jul 2, 2020, at 9:45 AM, Geni 0815  wrote:
 
>>> 
>>> At the moment I have the following errors
>>> Since no loop-data.txt is generated, rsync is diabled
>>> 
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
 Traceback (most recent call last):
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
  File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
self.convert_units(pkt, obstype)
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
  File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
  File "/usr/share/weewx/user/loopdata.py", line 685, in 
 convert_hi_lo_etc_units
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
 unit_type, unit_group))
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
  File "/usr/share/weewx/weewx/units.py", line 758, in toString
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:    
time.localtime(val_t[0]))
 Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
 OverflowError: timestamp out of range for platform time_t
 
 pi@Wetter-Raspi:~/wetter/loop-data $ ^C
 pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
 Extension NameVersion   Description
 weatherboard  1.0   WeatherBoard skin.
 Belchertown   1.1   A clean modern skin with real time streaming 
 updates and interactive charts. Modeled after BelchertownWeather.com
 loopdata  1.3.1 Loop statistics for real time reporting.
 
>>> 
>>> Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
 
 I added this section to the README:
 
 Rsync "errors" in the log:
 
 If one is using rsync, especially if the loop interval is short (e.g., 
 2s), it is expected that
 
 there will be log entries for connection timeouts, data timeouts and 
 skipped packets.
 
 By default only one second is allowed to connect or transmit the data. 
 Also, by default,
 
 if the loop data is older than 3s, it is skipped. With these settings, the 
 remote server
 
 may miss receiving some loop-data packets, but it won't get caught behind 
 trying to
 
 send a backlog of old loop data.
 
 
 
 Following are examples of a connection timeout, a data transmission 
 timeout and a
 
 skipped packet. These errors are fine in moderation. If too many packets 
 are timing out,
 
 one might try changing the connection timeout or timeout values (depending 
 on whether
 
 the timeouts are in the connection or the transmission).
 
 Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
 [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
 ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
 reported errors: ssh: connect to host www.paloaltoweather.com port 22: 
 Connection timed out. rsync: connection unexpectedly closed (0 bytes 
 received so far) [sender]. rsync error: unexplained error (code 255) at 
 io.c(235) [sender=3.1.3]
 Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
 [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

OK, I pushed 1.3.2.  It will catch and skip the FMT_SUM_ when something 
goes wrong.
It will also log the incident and include the obstype, the unit_type and the 
unit_group.  I am VERY
interested in seeing this information.  Please send it.

Cheers,
John

> On Jul 2, 2020, at 10:21 AM, John Kline  wrote:
> 
> 
> It’s formatting a sum for a unix_epoch type.  Sum doesn’t make sense for this 
> type; but the observation,
> which I unfortunately don’t log, seems to have a scalar accumulator.
> 
> This doesn’t seem right to me.  I could skip summing, etc. for this type; but 
> this is strange.
> 
> I’ll put out an update today that works around this, and logs it, please get 
> back to me with the actual
> observation you see in the log with hew new version.
> 
>>> On Jul 2, 2020, at 9:45 AM, Geni 0815  wrote:
>>> 
>> 
>> At the moment I have the following errors
>> Since no loop-data.txt is generated, rsync is diabled
>> 
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>>> Traceback (most recent call last):
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>>   self.convert_units(pkt, obstype)
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>>   self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 685, in 
>>> convert_hi_lo_etc_units
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>>   pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
>>> unit_type, unit_group))
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/weewx/units.py", line 758, in toString
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>>>   time.localtime(val_t[0]))
>>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>>> OverflowError: timestamp out of range for platform time_t
>>> 
>>> pi@Wetter-Raspi:~/wetter/loop-data $ ^C
>>> pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
>>> Extension NameVersion   Description
>>> weatherboard  1.0   WeatherBoard skin.
>>> Belchertown   1.1   A clean modern skin with real time streaming 
>>> updates and interactive charts. Modeled after BelchertownWeather.com
>>> loopdata  1.3.1 Loop statistics for real time reporting.
>>> 
>> 
>> Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
>>> 
>>> I added this section to the README:
>>> 
>>> Rsync "errors" in the log:
>>> 
>>> If one is using rsync, especially if the loop interval is short (e.g., 2s), 
>>> it is expected that
>>> 
>>> there will be log entries for connection timeouts, data timeouts and 
>>> skipped packets.
>>> 
>>> By default only one second is allowed to connect or transmit the data. 
>>> Also, by default,
>>> 
>>> if the loop data is older than 3s, it is skipped. With these settings, the 
>>> remote server
>>> 
>>> may miss receiving some loop-data packets, but it won't get caught behind 
>>> trying to
>>> 
>>> send a backlog of old loop data.
>>> 
>>> 
>>> 
>>> Following are examples of a connection timeout, a data transmission timeout 
>>> and a
>>> 
>>> skipped packet. These errors are fine in moderation. If too many packets 
>>> are timing out,
>>> 
>>> one might try changing the connection timeout or timeout values (depending 
>>> on whether
>>> 
>>> the timeouts are in the connection or the transmission).
>>> 
>>> Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
>>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
>>> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
>>> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
>>> reported errors: ssh: connect to host www.paloaltoweather.com port 22: 
>>> Connection timed out. rsync: connection unexpectedly closed (0 bytes 
>>> received so far) [sender]. rsync error: unexplained error (code 255) at 
>>> io.c(235) [sender=3.1.3]
>>> Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
>>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
>>> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
>>> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
>>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>> Jun 21 19:16:23 charlemagne weewx[8170] INFO user.rtgd: rsync_data: 
>>> skipping packet (2020-06
>>> 
> On Jul 1, 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

It’s formatting a sum for a unix_epoch type.  Sum doesn’t make sense for this 
type; but the observation,
which I unfortunately don’t log, seems to have a scalar accumulator.

This doesn’t seem right to me.  I could skip summing, etc. for this type; but 
this is strange.

I’ll put out an update today that works around this, and logs it, please get 
back to me with the actual
observation you see in the log with hew new version.

> On Jul 2, 2020, at 9:45 AM, Geni 0815  wrote:
> 
> 
> At the moment I have the following errors
> Since no loop-data.txt is generated, rsync is diabled
> 
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>> Traceback (most recent call last):
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:  
>>  self.convert_units(pkt, obstype)
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:  
>>  self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 685, in 
>> convert_hi_lo_etc_units
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:  
>>  pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, unit_type, 
>> unit_group))
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weewx/units.py", line 758, in toString
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:  
>>  time.localtime(val_t[0]))
>> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
>> OverflowError: timestamp out of range for platform time_t
>> 
>> pi@Wetter-Raspi:~/wetter/loop-data $ ^C
>> pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
>> Extension NameVersion   Description
>> weatherboard  1.0   WeatherBoard skin.
>> Belchertown   1.1   A clean modern skin with real time streaming 
>> updates and interactive charts. Modeled after BelchertownWeather.com
>> loopdata  1.3.1 Loop statistics for real time reporting.
>> 
> 
> Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
>> 
>> I added this section to the README:
>> 
>> Rsync "errors" in the log:
>> 
>> If one is using rsync, especially if the loop interval is short (e.g., 2s), 
>> it is expected that
>> 
>> there will be log entries for connection timeouts, data timeouts and skipped 
>> packets.
>> 
>> By default only one second is allowed to connect or transmit the data. Also, 
>> by default,
>> 
>> if the loop data is older than 3s, it is skipped. With these settings, the 
>> remote server
>> 
>> may miss receiving some loop-data packets, but it won't get caught behind 
>> trying to
>> 
>> send a backlog of old loop data.
>> 
>> 
>> 
>> Following are examples of a connection timeout, a data transmission timeout 
>> and a
>> 
>> skipped packet. These errors are fine in moderation. If too many packets are 
>> timing out,
>> 
>> one might try changing the connection timeout or timeout values (depending 
>> on whether
>> 
>> the timeouts are in the connection or the transmission).
>> 
>> Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
>> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
>> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
>> reported errors: ssh: connect to host www.paloaltoweather.com port 22: 
>> Connection timed out. rsync: connection unexpectedly closed (0 bytes 
>> received so far) [sender]. rsync error: unexplained error (code 255) at 
>> io.c(235) [sender=3.1.3]
>> Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: 
>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -o 
>> ConnectTimeout=1', '/home/weewx/gauge-data/loop-data.txt', 
>> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>> Jun 21 19:16:23 charlemagne weewx[8170] INFO user.rtgd: rsync_data: skipping 
>> packet (2020-06
>> 
>>> On Jul 1, 2020, at 10:20 AM, John Kline  wrote:
>>> 
>>> 
>>> It is normal to have some timeouts as the timeout is set to 1s.
>>> 
>>> For example, today so far I’ve had 5 connection timeouts on loop-data.  
>>> I’ve also had 3 gauge-data timeouts (I contributed the rsync code for rtgd).
>>> 
>>>rsync: gauge-data: connection timeouts 3
>>>rsync: loop-data: connection timeouts5
>>> 
>>> How many of these 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

At the moment I have the following errors
Since no loop-data.txt is generated, rsync is diabled

Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> Traceback (most recent call last):
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 515, in process_queue
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>   self.convert_units(pkt, obstype)
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 757, in convert_units
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>   self.convert_hi_lo_etc_units(pkt, obstype, unit_type, unit_group)
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 685, in 
> convert_hi_lo_etc_units
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>   pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
> unit_type, unit_group))
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weewx/units.py", line 758, in toString
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata: 
>   time.localtime(val_t[0]))
> Jul  2 17:55:23 Wetter-Raspi weewx[947] CRITICAL user.loopdata:   
> OverflowError: timestamp out of range for platform time_t
>
> pi@Wetter-Raspi:~/wetter/loop-data $ ^C
> pi@Wetter-Raspi:~/wetter/loop-data $ sudo wee_extension --list
> Extension NameVersion   Description
> weatherboard  1.0   WeatherBoard skin.
> Belchertown   1.1   A clean modern skin with real time streaming 
> updates and interactive charts. Modeled after BelchertownWeather.com
> loopdata  1.3.1 Loop statistics for real time reporting.
>
>
Am Mittwoch, 1. Juli 2020 19:51:05 UTC+2 schrieb John Kline:
>
> I added this section to the README:
>
> Rsync "errors" in the log:
>
> If one is using rsync, especially if the loop interval is short (e.g., 
> 2s), it is expected that
>
> there will be log entries for connection timeouts, data timeouts and 
> skipped packets.
>
> By default only one second is allowed to connect or transmit the data. 
> Also, by default,
>
> if the loop data is older than 3s, it is skipped. With these settings, the 
> remote server
>
> may miss receiving some loop-data packets, but it won't get caught behind 
> trying to
>
> send a backlog of old loop data.
>
>
> Following are examples of a connection timeout, a data transmission 
> timeout and a
>
> skipped packet. These errors are fine in moderation. If too many packets 
> are timing out,
>
> one might try changing the connection timeout or timeout values (depending 
> on whether
>
> the timeouts are in the connection or the transmission).
>
> Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
> '--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
> '/home/weewx/gauge-data/loop-data.txt', 
> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
> reported errors: ssh: connect to host www.paloaltoweather.com port 22: 
> Connection timed out. rsync: connection unexpectedly closed (0 bytes received 
> so far) [sender]. rsync error: unexplained error (code 255) at io.c(235) 
> [sender=3.1.3]
> Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
> '--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
> '/home/weewx/gauge-data/loop-data.txt', 
> 'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] 
> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync error: 
> timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
> Jun 21 19:16:23 charlemagne weewx[8170] INFO user.rtgd: rsync_data: skipping 
> packet (2020-06
>
>
> On Jul 1, 2020, at 10:20 AM, John Kline > 
> wrote:
>
> 
> It is normal to have some timeouts as the timeout is set to 1s.
>
> For example, today so far I’ve had 5 connection timeouts on loop-data. 
>  I’ve also had 3 gauge-data timeouts (I contributed the rsync code for 
> rtgd).
>
>rsync: gauge-data: connection timeouts 3
>rsync: loop-data: connection timeouts5
>
> How many of these error messages are you seeing?
>
> John
>
> On Jul 1, 2020, at 10:03 AM, Geni 0815 > 
> wrote:
>
> 
>
> @John: This is the error message, where do I have to search?
>
> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>>
>
> complete line:
> Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
> ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
> 'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I added this section to the README:

Rsync "errors" in the log:

If one is using rsync, especially if the loop interval is short (e.g., 2s), it 
is expected that

there will be log entries for connection timeouts, data timeouts and skipped 
packets.

By default only one second is allowed to connect or transmit the data. Also, by 
default,

if the loop data is older than 3s, it is skipped. With these settings, the 
remote server

may miss receiving some loop-data packets, but it won't get caught behind 
trying to

send a backlog of old loop data.



Following are examples of a connection timeout, a data transmission timeout and 
a

skipped packet. These errors are fine in moderation. If too many packets are 
timing out,

one might try changing the connection timeout or timeout values (depending on 
whether

the timeouts are in the connection or the transmission).

Jul  1 04:12:03 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
'--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
'/home/weewx/gauge-data/loop-data.txt', 
'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] reported 
errors: ssh: connect to host www.paloaltoweather.com port 22: Connection timed 
out. rsync: connection unexpectedly closed (0 bytes received so far) [sender]. 
rsync error: unexplained error (code 255) at io.c(235) [sender=3.1.3]
Jun 30 20:51:48 charlemagne weewx[1126] ERROR weeutil.rsyncupload: [['rsync', 
'--archive', '--stats', '--timeout=1', '-e ssh -o ConnectTimeout=1', 
'/home/weewx/gauge-data/loop-data.txt', 
'r...@www.paloaltoweather.com:/home/weewx/gauge-data/loop-data.txt']] reported 
errors: [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in 
data send/receive (code 30) at io.c(204) [sender=3.1.3]
Jun 21 19:16:23 charlemagne weewx[8170] INFO user.rtgd: rsync_data: skipping 
packet (2020-06

> On Jul 1, 2020, at 10:20 AM, John Kline  wrote:
> 
> 
> It is normal to have some timeouts as the timeout is set to 1s.
> 
> For example, today so far I’ve had 5 connection timeouts on loop-data.  I’ve 
> also had 3 gauge-data timeouts (I contributed the rsync code for rtgd).
> 
>rsync: gauge-data: connection timeouts 3
>rsync: loop-data: connection timeouts5
> 
> How many of these error messages are you seeing?
> 
> John
> 
>>> On Jul 1, 2020, at 10:03 AM, Geni 0815  wrote:
>>> 
>> 
>> 
>> @John: This is the error message, where do I have to search?
>> 
>>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>> 
>> complete line:
>> Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
>> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
>> ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
>> 'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
>> [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in data 
>> send/receive (code 30) at io.c(204) [sender=3.1.3]
>> 
>> 
>> Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>>> 
>>> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
>>> int.
>>> 
>>> I didn’t catch this as I was not specifying a port.  This should now be 
>>> fixed in 1.3.1.  Would you please give it a try?
>>> 
> On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
> 
 
> 
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in 
> process_queue
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in 
> write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   if 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

It is normal to have some timeouts as the timeout is set to 1s.

For example, today so far I’ve had 5 connection timeouts on loop-data.  I’ve 
also had 3 gauge-data timeouts (I contributed the rsync code for rtgd).

   rsync: gauge-data: connection timeouts 3
   rsync: loop-data: connection timeouts5

How many of these error messages are you seeing?

John

> On Jul 1, 2020, at 10:03 AM, Geni 0815  wrote:
> 
> 
> 
> @John: This is the error message, where do I have to search?
> 
>> reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
>> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
> 
> complete line:
> Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
> [['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
> ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
> 'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
> [sender] io timeout after 1 seconds -- exiting. rsync error: timeout in data 
> send/receive (code 30) at io.c(204) [sender=3.1.3]
> 
> 
> Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>> 
>> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
>> int.
>> 
>> I didn’t catch this as I was not specifying a port.  This should now be 
>> fixed in 1.3.1.  Would you please give it a try?
>> 
 On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
 
>>> 
 
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  Traceback (most recent call last):
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.compose_and_write_packet(pkt)
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 541, in 
 compose_and_write_packet
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.write_packet(selective_pkt)
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  self.rsync_data(pkt['dateTime'])
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  rsync_upload.run()
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  if self.port is not None and len(self.port.strip()) > 0:
 Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:  
  AttributeError: 'int' object has no attribute 'strip'
 
 
>>> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
 
 @John: I have the following entry in the syslog, what is not suitable?
 
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> barometer_rate_secs: 10800
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_secs : 86400
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_points   : 16
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in 
> process_queue
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in 
> write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

@John: This is the error message, where do I have to search?

reported errors: [sender] io timeout after 1 seconds -- exiting. rsync 
> error: timeout in data send/receive (code 30) at io.c(204) [sender=3.1.3]
>

complete line:
Jul  1 18:47:12 Wetter-Raspi weewx[22015] ERROR weeutil.rsyncupload: 
[['rsync', '--archive', '--stats', '--timeout=1', '-e ssh -p 2022 -o 
ConnectTimeout=1', '/home/pi/NAS/www/loop-data/loop-data.txt', 
'xx@192.999.999.9:/xxx//loop-data/loop-data.txt']] reported errors: 
[sender] io timeout after 1 seconds -- exiting. rsync error: timeout in 
data send/receive (code 30) at io.c(204) [sender=3.1.3]


Am Dienstag, 30. Juni 2020 16:01:30 UTC+2 schrieb John Kline:
>
> weeutil.RsyncUpload was expecting a string for port.  I was passing it an 
> int.
>
> I didn’t catch this as I was not specifying a port.  This should now be 
> fixed in 1.3.1.  Would you please give it a try?
>
> On Jun 30, 2020, at 1:32 AM, Geni 0815 > 
> wrote:
>
> 
>>
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>>
>> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>>
>> @John: I have the following entry in the syslog, what is not suitable?
>>
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> barometer_rate_secs: 10800
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_secs : 86400
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_points   : 16
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   Traceback (most recent call last):
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.compose_and_write_packet(pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>>> compose_and_write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.write_packet(selective_pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   self.rsync_data(pkt['dateTime'])
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   rsync_upload.run()
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   if self.port is not None and len(self.port.strip()) > 0:
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>>   AttributeError: 'int' object has no attribute 'strip'
>>>
>>> [image: belch09.jpg]
>>  
>>
>> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>>
>>> I just now updated this extension to 1.1.  I would try it before 
>>> resorting to a clean install.
>>>
>>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

weeutil.RsyncUpload was expecting a string for port.  I was passing it an int.

I didn’t catch this as I was not specifying a port.  This should now be fixed 
in 1.3.1.  Would you please give it a try?

> On Jun 30, 2020, at 1:32 AM, Geni 0815  wrote:
> 
> 
>> 
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:   
>> Traceback (most recent call last):
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.compose_and_write_packet(pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.write_packet(selective_pkt)
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>self.rsync_data(pkt['dateTime'])
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>rsync_upload.run()
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>  File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:    
>>if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata:   
>> AttributeError: 'int' object has no attribute 'strip'
>> 
>> 
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>> 
>> @John: I have the following entry in the syslog, what is not suitable?
>> 
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> barometer_rate_secs: 10800
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_secs : 86400
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>>> wind_rose_points   : 16
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> Traceback (most recent call last):
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.compose_and_write_packet(pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 541, in 
>>> compose_and_write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.write_packet(selective_pkt)
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> self.rsync_data(pkt['dateTime'])
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> rsync_upload.run()
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>>   File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> if self.port is not None and len(self.port.strip()) > 0:
>>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata:   
>>> AttributeError: 'int' object has no attribute 'strip'
>>> 
>> 
>>  
>> 
>> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>> 
>>> I just now updated this extension to 1.1.  I would try it before resorting 
>>> to a clean install.
>>> 
 On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
 
 
 Hello John, I did grep and get some results. Next time I used grep again 
 no results. I uninstalled weewx because I did the first installation with 
 Debian. I did installation weewx with setup py. Again no loop_data.txt 
 created. I will do a fresh Buster light image next. After that I will do 
 also a complete new weewx installation. I will let you know if 
 successfully. Thx for your help!
 Michael
 
 John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
> Well, I see loopdata in the log snippet you just sent.
> 
> Would you try the grep again?
> grep loopdata /var/log/syslog
> 
> And look for the loopdata file again?
> 
>> On Jun 26, 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

>
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   if self.port is not None and len(self.port.strip()) > 0:
> Jun 30 10:27:05 Wetter-Raspi weewx[10952] CRITICAL user.loopdata: 
>   AttributeError: 'int' object has no attribute 'strip'
>
>
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>
> @John: I have the following entry in the syslog, what is not suitable?
>
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> barometer_rate_secs: 10800
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_secs : 86400
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_points   : 16
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>> [image: belch09.jpg]
>  
>
> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>
>> I just now updated this extension to 1.1.  I would try it before 
>> resorting to a clean install.
>>
>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
>>
>> 
>> Hello John, I did grep and get some results. Next time I used grep again 
>> no results. I uninstalled weewx because I did the first installation with 
>> Debian. I did installation weewx with setup py. Again no loop_data.txt 
>> created. I will do a fresh Buster light image next. After that I will do 
>> also a complete new weewx installation. I will let you know if 
>> successfully. Thx for your help!
>> Michael
>>
>> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>>
>>> Well, I see loopdata in the log snippet you just sent.
>>>
>>> Would you try the grep again?
>>> grep loopdata /var/log/syslog
>>>
>>> And look for the loopdata file again?
>>>
>>> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>>>
>>> 
>>> Yes I stopped, start and restart. 
>>> I will try to find out how to send files.
>>> 
>>>
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>>
 Not sure how to post files; but since you are running WeeWX 4 and 
 Python 3.  Did you restart WeeWX after you installed 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

>
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 507, in process_queue
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   self.convert_units(pkt, obstype)
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 735, in convert_units
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   self.convert_hi_lo_sum_units(pkt, obstype, unit_type, unit_group)
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 677, in 
> convert_hi_lo_sum_units
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   pkt['FMT_SUM_%s' % obstype] = self.cfg.formatter.toString((sum, 
> unit_type, unit_group))
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weewx/units.py", line 758, in toString
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   time.localtime(val_t[0]))
> Jun 30 09:53:09 Wetter-Raspi weewx[10609] CRITICAL user.loopdata: 
>   OverflowError: timestamp out of range for platform time_t
>
>
> Am Dienstag, 30. Juni 2020 09:47:44 UTC+2 schrieb Geni 0815:
>
> @John: I have the following entry in the syslog, what is not suitable?
>
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> barometer_rate_secs: 10800
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_secs : 86400
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
>> wind_rose_points   : 16
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   Traceback (most recent call last):
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.compose_and_write_packet(pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 541, in 
>> compose_and_write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.write_packet(selective_pkt)
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   self.rsync_data(pkt['dateTime'])
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   rsync_upload.run()
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   if self.port is not None and len(self.port.strip()) > 0:
>> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>>   AttributeError: 'int' object has no attribute 'strip'
>>
>> [image: belch09.jpg]
>  
>
> Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>>
>> I just now updated this extension to 1.1.  I would try it before 
>> resorting to a clean install.
>>
>> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
>>
>> 
>> Hello John, I did grep and get some results. Next time I used grep again 
>> no results. I uninstalled weewx because I did the first installation with 
>> Debian. I did installation weewx with setup py. Again no loop_data.txt 
>> created. I will do a fresh Buster light image next. After that I will do 
>> also a complete new weewx installation. I will let you know if 
>> successfully. Thx for your help!
>> Michael
>>
>> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>>
>>> Well, I see loopdata in the log snippet you just sent.
>>>
>>> Would you try the grep again?
>>> grep loopdata /var/log/syslog
>>>
>>> And look for the loopdata file again?
>>>
>>> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>>>
>>> 
>>> Yes I stopped, start and restart. 
>>> I will try to find out how to send files.
>>> 
>>>
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>>
 Not sure how to post files; but since you are running WeeWX 4 and 
 Python 3.  Did you restart WeeWX after you installed loopdata?

 It’s to imagine why you don’t see any occurrence of loopdata in the 
 log?  Do you see other weewx messages in the log?

 On Jun 26, 2020, at 10:40 AM, Michael 

Re: [weewx-user] Update interval less than 300 seconds?

[Geni 0815]

@John: I have the following entry in the syslog, what is not suitable?

Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> barometer_rate_secs: 10800
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_secs : 86400
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] INFO user.loopdata: 
> wind_rose_points   : 16
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   Traceback (most recent call last):
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 521, in process_queue
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.compose_and_write_packet(pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 541, in 
> compose_and_write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.write_packet(selective_pkt)
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 555, in write_packet
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   self.rsync_data(pkt['dateTime'])
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/user/loopdata.py", line 645, in rsync_data
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   rsync_upload.run()
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
> File "/usr/share/weewx/weeutil/rsyncupload.py", line 72, in run
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   if self.port is not None and len(self.port.strip()) > 0:
> Jun 30 09:24:21 Wetter-Raspi weewx[10361] CRITICAL user.loopdata: 
>   AttributeError: 'int' object has no attribute 'strip'
>
> [image: belch09.jpg]
 

Am Samstag, 27. Juni 2020 21:18:06 UTC+2 schrieb John Kline:
>
> I just now updated this extension to 1.1.  I would try it before resorting 
> to a clean install.
>
> On Jun 27, 2020, at 12:16 PM, Michael Meyer  > wrote:
>
> 
> Hello John, I did grep and get some results. Next time I used grep again 
> no results. I uninstalled weewx because I did the first installation with 
> Debian. I did installation weewx with setup py. Again no loop_data.txt 
> created. I will do a fresh Buster light image next. After that I will do 
> also a complete new weewx installation. I will let you know if 
> successfully. Thx for your help!
> Michael
>
> John Kline > schrieb am Fr., 26. Juni 
> 2020, 20:54:
>
>> Well, I see loopdata in the log snippet you just sent.
>>
>> Would you try the grep again?
>> grep loopdata /var/log/syslog
>>
>> And look for the loopdata file again?
>>
>> On Jun 26, 2020, at 11:48 AM, Michael Meyer > > wrote:
>>
>> 
>> Yes I stopped, start and restart. 
>> I will try to find out how to send files.
>> 
>>
>>
>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>
>>> Not sure how to post files; but since you are running WeeWX 4 and Python 
>>> 3.  Did you restart WeeWX after you installed loopdata?
>>>
>>> It’s to imagine why you don’t see any occurrence of loopdata in the 
>>> log?  Do you see other weewx messages in the log?
>>>
>>> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
>>>
>>> 
>>>
>>> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
>>> Any idea why I can't post the created myfile here? I just can post 
>>> pictures but no files! I can create an attachment but couldn't send?
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>>>
 It appears that loopdata isn’t running.

 Let’s start with the obvious.  As stated in the README:

 This extension requires Python 3 and WeeWX 4.

 Are you running WeeWX 4.x?  Are you running Python 3?

 If are on WeeWX 4.x and Python 3, use the following guide to post the 
 log and I’ll have a look.

 https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

 Cheers,
 John

 On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:

 

 Hi John,
 thx for your help! grep loopdata /var/log/syslog doesn't deliver 
 anything. With "where is" I get zero result in var/log/syslog. 

 


 
 
 Cheers,
 Michael

 -- 
 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%40googlegroups.com
  
 

Re: [weewx-user] Update interval less than 300 seconds?

[Michael Meyer]

Just installed 1.2.1! Get loop-data.txt! Thx for your help!

John Kline  schrieb am Sa., 27. Juni 2020, 21:18:

> I just now updated this extension to 1.1.  I would try it before resorting
> to a clean install.
>
> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
>
> 
> Hello John, I did grep and get some results. Next time I used grep again
> no results. I uninstalled weewx because I did the first installation with
> Debian. I did installation weewx with setup py. Again no loop_data.txt
> created. I will do a fresh Buster light image next. After that I will do
> also a complete new weewx installation. I will let you know if
> successfully. Thx for your help!
> Michael
>
> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>
>> Well, I see loopdata in the log snippet you just sent.
>>
>> Would you try the grep again?
>> grep loopdata /var/log/syslog
>>
>> And look for the loopdata file again?
>>
>> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>>
>> 
>> Yes I stopped, start and restart.
>> I will try to find out how to send files.
>> 
>>
>>
>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>>
>>> Not sure how to post files; but since you are running WeeWX 4 and Python
>>> 3.  Did you restart WeeWX after you installed loopdata?
>>>
>>> It’s to imagine why you don’t see any occurrence of loopdata in the
>>> log?  Do you see other weewx messages in the log?
>>>
>>> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
>>>
>>> 
>>>
>>> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
>>> Any idea why I can't post the created myfile here? I just can post
>>> pictures but no files! I can create an attachment but couldn't send?
>>>
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>>>
 It appears that loopdata isn’t running.

 Let’s start with the obvious.  As stated in the README:

 This extension requires Python 3 and WeeWX 4.

 Are you running WeeWX 4.x?  Are you running Python 3?

 If are on WeeWX 4.x and Python 3, use the following guide to post the
 log and I’ll have a look.

 https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

 Cheers,
 John

 On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:

 

 Hi John,
 thx for your help! grep loopdata /var/log/syslog doesn't deliver
 anything. With "where is" I get zero result in var/log/syslog.

 


 
 
 Cheers,
 Michael

 --
 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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+...@googlegroups.com.
>>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/weewx-user/cf03c41c-a0fc-41f0-bee1-51e921e55122n%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/2b47dad8-63fb-4310-b7e6-befef8b22a0bn%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/99150DD3-6998-4BAC-9E06-E461789335F9%40johnkline.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
> 

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I just now updated this extension to 1.1.  I would try it before resorting to a 
clean install.

> On Jun 27, 2020, at 12:16 PM, Michael Meyer  wrote:
> 
> 
> Hello John, I did grep and get some results. Next time I used grep again no 
> results. I uninstalled weewx because I did the first installation with 
> Debian. I did installation weewx with setup py. Again no loop_data.txt 
> created. I will do a fresh Buster light image next. After that I will do also 
> a complete new weewx installation. I will let you know if successfully. Thx 
> for your help!
> Michael
> 
> John Kline  schrieb am Fr., 26. Juni 2020, 20:54:
>> Well, I see loopdata in the log snippet you just sent.
>> 
>> Would you try the grep again?
>> grep loopdata /var/log/syslog
>> 
>> And look for the loopdata file again?
>> 
 On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
 
>>> 
>>> Yes I stopped, start and restart. 
>>> I will try to find out how to send files.
>>> 
>>> 
>>> 
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
 Not sure how to post files; but since you are running WeeWX 4 and Python 
 3.  Did you restart WeeWX after you installed loopdata?
 
 It’s to imagine why you don’t see any occurrence of loopdata in the log?  
 Do you see other weewx messages in the log?
 
>> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
>> 
> 
 
> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
> Any idea why I can't post the created myfile here? I just can post 
> pictures but no files! I can create an attachment but couldn't send?
> 
> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>> It appears that loopdata isn’t running.
>> 
>> Let’s start with the obvious.  As stated in the README:
>> 
>> This extension requires Python 3 and WeeWX 4.
>> 
>> Are you running WeeWX 4.x?  Are you running Python 3?
>> 
>> If are on WeeWX 4.x and Python 3, use the following guide to post the 
>> log and I’ll have a look.
>> 
>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>> 
>> Cheers,
>> John
>> 
 On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
 
>>> 
>> 
>>> Hi John,
>>> thx for your help! grep loopdata /var/log/syslog doesn't deliver 
>>> anything. With "where is" I get zero result in var/log/syslog. 
>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Cheers,
>>> Michael
>> 
>>> -- 
>>> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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+...@googlegroups.com.
 
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/cf03c41c-a0fc-41f0-bee1-51e921e55122n%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/2b47dad8-63fb-4310-b7e6-befef8b22a0bn%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/99150DD3-6998-4BAC-9E06-E461789335F9%40johnkline.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/CAK0Zn%2BRxuLBBnPZMdruaALU-%3Dx8b0V_Xa87VTJYNMsEHNuAgXg%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/3742CF7F-5453-451E-A82B-499069518B7B%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Michael Meyer]

Hello John, I did grep and get some results. Next time I used grep again no
results. I uninstalled weewx because I did the first installation with
Debian. I did installation weewx with setup py. Again no loop_data.txt
created. I will do a fresh Buster light image next. After that I will do
also a complete new weewx installation. I will let you know if
successfully. Thx for your help!
Michael

John Kline  schrieb am Fr., 26. Juni 2020, 20:54:

> Well, I see loopdata in the log snippet you just sent.
>
> Would you try the grep again?
> grep loopdata /var/log/syslog
>
> And look for the loopdata file again?
>
> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
>
> 
> Yes I stopped, start and restart.
> I will try to find out how to send files.
> 
>
>
> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>
>> Not sure how to post files; but since you are running WeeWX 4 and Python
>> 3.  Did you restart WeeWX after you installed loopdata?
>>
>> It’s to imagine why you don’t see any occurrence of loopdata in the log?
>> Do you see other weewx messages in the log?
>>
>> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
>>
>> 
>>
>> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
>> Any idea why I can't post the created myfile here? I just can post
>> pictures but no files! I can create an attachment but couldn't send?
>>
>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>>
>>> It appears that loopdata isn’t running.
>>>
>>> Let’s start with the obvious.  As stated in the README:
>>>
>>> This extension requires Python 3 and WeeWX 4.
>>>
>>> Are you running WeeWX 4.x?  Are you running Python 3?
>>>
>>> If are on WeeWX 4.x and Python 3, use the following guide to post the
>>> log and I’ll have a look.
>>>
>>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>>>
>>> Cheers,
>>> John
>>>
>>> On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
>>>
>>> 
>>>
>>> Hi John,
>>> thx for your help! grep loopdata /var/log/syslog doesn't deliver
>>> anything. With "where is" I get zero result in var/log/syslog.
>>>
>>> 
>>>
>>>
>>> 
>>> 
>>> Cheers,
>>> Michael
>>>
>>> --
>>> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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+...@googlegroups.com.
>>
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/weewx-user/cf03c41c-a0fc-41f0-bee1-51e921e55122n%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/2b47dad8-63fb-4310-b7e6-befef8b22a0bn%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/99150DD3-6998-4BAC-9E06-E461789335F9%40johnkline.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/CAK0Zn%2BRxuLBBnPZMdruaALU-%3Dx8b0V_Xa87VTJYNMsEHNuAgXg%40mail.gmail.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

Well, I see loopdata in the log snippet you just sent.

Would you try the grep again?
grep loopdata /var/log/syslog

And look for the loopdata file again?

> On Jun 26, 2020, at 11:48 AM, Michael Meyer  wrote:
> 
> 
> Yes I stopped, start and restart. 
> I will try to find out how to send files.
> 
> 
> 
> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 20:28:49 UTC+2:
>> Not sure how to post files; but since you are running WeeWX 4 and Python 3.  
>> Did you restart WeeWX after you installed loopdata?
>> 
>> It’s to imagine why you don’t see any occurrence of loopdata in the log?  Do 
>> you see other weewx messages in the log?
>> 
 On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
 
>>> 
>> 
>>> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
>>> Any idea why I can't post the created myfile here? I just can post pictures 
>>> but no files! I can create an attachment but couldn't send?
>>> 
>>> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
 It appears that loopdata isn’t running.
 
 Let’s start with the obvious.  As stated in the README:
 
 This extension requires Python 3 and WeeWX 4.
 
 Are you running WeeWX 4.x?  Are you running Python 3?
 
 If are on WeeWX 4.x and Python 3, use the following guide to post the log 
 and I’ll have a look.
 
 https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
 
 Cheers,
 John
 
>> On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
>> 
> 
 
> Hi John,
> thx for your help! grep loopdata /var/log/syslog doesn't deliver 
> anything. With "where is" I get zero result in var/log/syslog. 
 
> 
> 
> 
> 
> 
> Cheers,
> Michael
 
> -- 
> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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+...@googlegroups.com.
>> 
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/weewx-user/cf03c41c-a0fc-41f0-bee1-51e921e55122n%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/2b47dad8-63fb-4310-b7e6-befef8b22a0bn%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/99150DD3-6998-4BAC-9E06-E461789335F9%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

Not sure how to post files; but since you are running WeeWX 4 and Python 3.  
Did you restart WeeWX after you installed loopdata?

It’s to imagine why you don’t see any occurrence of loopdata in the log?  Do 
you see other weewx messages in the log?

> On Jun 26, 2020, at 10:40 AM, Michael Meyer  wrote:
> 
> 
> Weewx 4.1.1 is running I have Python 3.7 on my rpi.
> Any idea why I can't post the created myfile here? I just can post pictures 
> but no files! I can create an attachment but couldn't send?
> 
> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:
>> It appears that loopdata isn’t running.
>> 
>> Let’s start with the obvious.  As stated in the README:
>> 
>> This extension requires Python 3 and WeeWX 4.
>> 
>> Are you running WeeWX 4.x?  Are you running Python 3?
>> 
>> If are on WeeWX 4.x and Python 3, use the following guide to post the log 
>> and I’ll have a look.
>> 
>> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>> 
>> Cheers,
>> John
>> 
 On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
 
>>> 
>> 
>>> Hi John,
>>> thx for your help! grep loopdata /var/log/syslog doesn't deliver anything. 
>>> With "where is" I get zero result in var/log/syslog. 
>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> Cheers,
>>> Michael
>> 
>>> -- 
>>> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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/cf03c41c-a0fc-41f0-bee1-51e921e55122n%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/A07A8D8B-8075-48A8-80E8-73D4EC995E25%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Michael Meyer]

Weewx 4.1.1 is running I have Python 3.7 on my rpi.
Any idea why I can't post the created myfile here? I just can post pictures 
but no files! I can create an attachment but couldn't send?

jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 18:19:36 UTC+2:

> It appears that loopdata isn’t running.
>
> Let’s start with the obvious.  As stated in the README:
>
> This extension requires Python 3 and WeeWX 4.
>
> Are you running WeeWX 4.x?  Are you running Python 3?
>
> If are on WeeWX 4.x and Python 3, use the following guide to post the log 
> and I’ll have a look.
>
> https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user
>
> Cheers,
> John
>
> On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
>
> 
>
> Hi John,
> thx for your help! grep loopdata /var/log/syslog doesn't deliver anything. 
> With "where is" I get zero result in var/log/syslog. 
>
> 
>
>
> 
> 
> Cheers,
> Michael
>
> -- 
> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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/cf03c41c-a0fc-41f0-bee1-51e921e55122n%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

It appears that loopdata isn’t running.

Let’s start with the obvious.  As stated in the README:

This extension requires Python 3 and WeeWX 4.

Are you running WeeWX 4.x?  Are you running Python 3?

If are on WeeWX 4.x and Python 3, use the following guide to post the log and 
I’ll have a look.

https://github.com/weewx/weewx/wiki/Help!-Posting-to-weewx-user

Cheers,
John

>> On Jun 26, 2020, at 8:27 AM, Michael Meyer  wrote:
> 
> Hi John,
> thx for your help! grep loopdata /var/log/syslog doesn't deliver anything. 
> With "where is" I get zero result in var/log/syslog. 
> 
> 
> 
> 
> 
> Cheers,
> Michael
> -- 
> 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/d261b8ee-957e-4158-9b80-dcbe21fcc3f5n%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/1658AE8E-45BC-4355-99C3-ADE54A5734B8%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

Hi Michael,

Would you send the output of (which assumes WeeWX is writing to 
/var/log/syslog)?
grep loopdata /var/log/syslog

Also, please cut and paste the loopdata section of weewx.conf.

Lastly, please send a directory listing of /var/www/html/weewx

Cheers,
John

> On Jun 26, 2020, at 3:07 AM, Michael Meyer  wrote:
> 
> 
> Hello, I installed your extension but the file loop-data.txt will not create. 
> I changed weewx.conf to  loop_data_dir = /var/www/html/weewx. 
> Thx for any help
> 
> jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 02:19:42 UTC+2:
>> I have an extension you could try:
>> https://github.com/chaunceygardiner/weewx-loopdata
>> 
>> I use it to update many pages on my site (https://www.paloaltoweather.com/), 
>> including current conditions at.
>> 
>> It’s relatively simple to install.  You specify the report to target (e.g., 
>> SeasonsReport), and it will do the proper conversions to match the report 
>> and write a file of items you pick on every loop cycle.
>> 
>> Cheers,
>> John
>> 
 On Jun 25, 2020, at 5:12 PM, Richard Zimmerman  wrote:
 
>>> 
>> 
>>> I hate to post this here as it's likely a simple question, but I've been 
>>> unable to find an answer from searching.  I'm brand new to weewx having 
>>> used wview for over a decade.  So I have the generic setup and a Davis 
>>> Vantage Pro2.  My archive interval is 300s.  Is there a way to have certain 
>>> data on the web page update more frequently than every 5 minutes?  I'm 
>>> especially interested in the "Current Conditions" section as I'll 
>>> frequently bring up the page after feeling a strong gust to see what the 
>>> speed was, but I have to wait 5 minutes before the page updates.
>>> 
>>> I figure I could change the archive interval in the main config file, but I 
>>> don't really know what changing it to something different than on the 
>>> console would do.  Furthermore, the graphs don't really have to update more 
>>> frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
>>> way to have those data update on LOOP packets rather than ARCHIVE?
>>> 
>>> 
>> 
>>> -- 
>>> 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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%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/f39930ca-159f-4820-96e7-062f6f4d2b64n%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/143D6024-6BCF-422C-8E06-92B9B8F20189%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Michael Meyer]

Hello, I installed your extension but the file loop-data.txt will not 
create. I changed weewx.conf to  loop_data_dir = /var/www/html/weewx. 
Thx for any help

jo...@johnkline.com schrieb am Freitag, 26. Juni 2020 um 02:19:42 UTC+2:

> I have an extension you could try:
> https://github.com/chaunceygardiner/weewx-loopdata
>
> I use it to update many pages on my site (https://www.paloaltoweather.com/), 
> including current conditions at.
>
> It’s relatively simple to install.  You specify the report to target 
> (e.g., SeasonsReport), and it will do the proper conversions to match the 
> report and write a file of items you pick on every loop cycle.
>
> Cheers,
> John
>
> On Jun 25, 2020, at 5:12 PM, Richard Zimmerman  wrote:
>
> 
>
> I hate to post this here as it's likely a simple question, but I've been 
> unable to find an answer from searching.  I'm brand new to weewx having 
> used wview for over a decade.  So I have the generic setup and a Davis 
> Vantage Pro2.  My archive interval is 300s.  Is there a way to have certain 
> data on the web page update more frequently than every 5 minutes?  I'm 
> especially interested in the "Current Conditions" section as I'll 
> frequently bring up the page after feeling a strong gust to see what the 
> speed was, but I have to wait 5 minutes before the page updates.
>
> I figure I could change the archive interval in the main config file, but 
> I don't really know what changing it to something different than on the 
> console would do.  Furthermore, the graphs don't really have to update more 
> frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
> way to have those data update on LOOP packets rather than ARCHIVE?
>
>
> -- 
> 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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%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/f39930ca-159f-4820-96e7-062f6f4d2b64n%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[rich T]

Take a look @ https://github.com/poblabs/weewx-belchertown

https://belchertownweather.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/7b8864dc-f56f-40df-9ea7-e3f6d3049bb9o%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I should add, the gauges at https://www.paloaltoweather.com/LiveSeasonsGauges 
do not use my extension.  They use Gary Roderick’s:
https://github.com/gjr80/weewx-realtime_gauge-data

Gary’s extension was the inspiration behind the loopdata extension.  loopdata 
simply lets one pick and choose the observations and target any report.

> On Jun 25, 2020, at 5:51 PM, John Kline  wrote:
> 
> 
> BTW, I have the following screen up on two tablets in my house.  It’s great 
> for checking how fast the wind is currently blowing or how hard it’s 
> currently raining.
> 
> https://www.paloaltoweather.com/weatherboard/
> 
>>> On Jun 25, 2020, at 5:32 PM, Richard Zimmerman  wrote:
>>> 
>> 
>> Thanks John.  I see how your web site updates every couple seconds.  That's 
>> fantastic!  I'll dig into the extension
>> -- 
>> 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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%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/D9D3C425-3790-41F3-9012-1C87BEFA1529%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

BTW, I have the following screen up on two tablets in my house.  It’s great for 
checking how fast the wind is currently blowing or how hard it’s currently 
raining.

https://www.paloaltoweather.com/weatherboard/

> On Jun 25, 2020, at 5:32 PM, Richard Zimmerman  wrote:
> 
> 
> Thanks John.  I see how your web site updates every couple seconds.  That's 
> fantastic!  I'll dig into the extension
> -- 
> 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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%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/FD7807F2-94ED-4F04-8B40-7780093BD7D4%40johnkline.com.

Re: [weewx-user] Update interval less than 300 seconds?

[Richard Zimmerman]

Thanks John.  I see how your web site updates every couple seconds.  That's 
fantastic!  I'll dig into the extension

-- 
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/a2cf6c14-92ee-4655-83ec-e8c46f32739fo%40googlegroups.com.

Re: [weewx-user] Update interval less than 300 seconds?

[John Kline]

I have an extension you could try:
https://github.com/chaunceygardiner/weewx-loopdata

I use it to update many pages on my site (https://www.paloaltoweather.com/), 
including current conditions at.

It’s relatively simple to install.  You specify the report to target (e.g., 
SeasonsReport), and it will do the proper conversions to match the report and 
write a file of items you pick on every loop cycle.

Cheers,
John

> On Jun 25, 2020, at 5:12 PM, Richard Zimmerman  wrote:
> 
> 
> I hate to post this here as it's likely a simple question, but I've been 
> unable to find an answer from searching.  I'm brand new to weewx having used 
> wview for over a decade.  So I have the generic setup and a Davis Vantage 
> Pro2.  My archive interval is 300s.  Is there a way to have certain data on 
> the web page update more frequently than every 5 minutes?  I'm especially 
> interested in the "Current Conditions" section as I'll frequently bring up 
> the page after feeling a strong gust to see what the speed was, but I have to 
> wait 5 minutes before the page updates.
> 
> I figure I could change the archive interval in the main config file, but I 
> don't really know what changing it to something different than on the console 
> would do.  Furthermore, the graphs don't really have to update more 
> frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
> way to have those data update on LOOP packets rather than ARCHIVE?
> 
> 
> -- 
> 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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%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/8E859B9C-86D4-4429-B08B-2B6D6FF74E6D%40johnkline.com.

[weewx-user] Update interval less than 300 seconds?

[Richard Zimmerman]

I hate to post this here as it's likely a simple question, but I've been 
unable to find an answer from searching.  I'm brand new to weewx having 
used wview for over a decade.  So I have the generic setup and a Davis 
Vantage Pro2.  My archive interval is 300s.  Is there a way to have certain 
data on the web page update more frequently than every 5 minutes?  I'm 
especially interested in the "Current Conditions" section as I'll 
frequently bring up the page after feeling a strong gust to see what the 
speed was, but I have to wait 5 minutes before the page updates.

I figure I could change the archive interval in the main config file, but I 
don't really know what changing it to something different than on the 
console would do.  Furthermore, the graphs don't really have to update more 
frequently than 5 minutes.  Just the actual raw data displays.  Is there a 
way to have those data update on LOOP packets rather than ARCHIVE?


-- 
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/c1909dcf-1e5a-44ec-a44f-661c4c5364f4o%40googlegroups.com.