Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[Geni 0815]

Thanks for the help, it worked like this.

Am Mittwoch, 12. August 2020 17:01:07 UTC+2 schrieb Tom Keffer:
>
> As noted in the install page for Debian 
> <http://www.weewx.com/docs/debian.htm>, for stretch (Debian 9), you need 
> to use Python 2. So, you want
>
>
> *wget -qO - http://weewx.com/apt/weewx- 
> <http://weewx.com/apt/weewx->python2.list | sudo tee 
> /etc/apt/sources.list.d/weewx.list*
> *sudo apt-get update*
> *sudo apt-get install weewx*
>
> The reason is that not all packages are available for Python 3 on stretch. 
>
> -tk
>
>
>
> On Tue, Aug 11, 2020 at 10:07 PM Geni 0815  > wrote:
>
>> pi@raspberrypi:~ $ PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"
>>
>> pi@raspberrypi:~ $ NAME="Raspbian GNU/Linux"
>>
>> pi@raspberrypi:~ $ VERSION_ID="9"
>>
>> pi@raspberrypi:~ $ VERSION="9 (stretch)"
>>
>> pi@raspberrypi:~ $ VERSION_CODENAME=stretch
>>
>> pi@raspberrypi:~ $ ID=raspbian
>>
>> pi@raspberrypi:~ $ ID_LIKE=debian
>>
>> pi@raspberrypi:~ $ HOME_URL="http://www.raspbian.org/";
>>
>> pi@raspberrypi:~ $ SUPPORT_URL="http://www.raspbian.org/RaspbianForums";
>>
>> pi@raspberrypi:~ $ BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";
>>
>>
>> Am Dienstag, 11. August 2020 16:45:24 UTC+2 schrieb Tom Keffer:
>>>
>>> What version of Rasbian are you running? 
>>>
>>> *cat /etc/os-release*
>>>
>>> -tk
>>>
>>> On Tue, Aug 11, 2020 at 7:25 AM geni08...@gmail.com  
>>> wrote:
>>>
>>>> pi@raspberrypi:~ $ sudo apt install weewx
>>>> Paketlisten werden gelesen... Fertig
>>>> Abhängigkeitsbaum wird aufgebaut.
>>>> Statusinformationen werden eingelesen Fertig
>>>> Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
>>>> Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
>>>> Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
>>>> nicht erstellt wurden oder Incoming noch nicht verlassen haben.
>>>> Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu 
>>>> lösen:
>>>>
>>>> Die folgenden Pakete haben unerfüllte Abhängigkeiten:
>>>>  weewx : Hängt ab von: python3-cheetah ist aber nicht installierbar
>>>> E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene 
>>>> defekte Pakete.
>>>> pi@raspberrypi:~ $
>>>>
>>>> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 14:30:02 
>>>> UTC+2:
>>>>
>>>>> I'm sorry: I just realized that your post is unrelated to the original 
>>>>> post. We need some context to understand what you are trying to do. The 
>>>>> screenshot you sent does not match your description of what you did. Are 
>>>>> you truly upgrading? If so, from what version?
>>>>>
>>>>> What happens when you do a simple install:
>>>>>
>>>>>
>>>>> *wget -qO - http://weewx.com/apt/weewx-python3.list 
>>>>> <http://weewx.com/apt/weewx-python3.list> | sudo tee 
>>>>> /etc/apt/sources.list.d/weewx.list*
>>>>> *sudo apt update*
>>>>> *sudo apt install weewx*
>>>>>
>>>>> -tk
>>>>>
>>>>> On Mon, Aug 10, 2020 at 10:44 PM geni08...@gmail.com <
>>>>> geni08...@gmail.com> wrote:
>>>>>
>>>>>> I did this:
>>>>>> wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee 
>>>>>> /etc/apt/sources.list.d/weewx.list
>>>>>> sudo apt-get update
>>>>>> sudo apt-get upgrade
>>>>>> sudo apt install python3-mysqldb 
>>>>>> sudo apt install python3-ephem
>>>>>> sudo apt-get update
>>>>>> sudo apt-get upgrade
>>>>>>
>>>>>>
>>>>>> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 02:56:50 
>>>>>> UTC+2:
>>>>>>
>>>>>>> (Please do not send a screen shot. They are hard to read, include 
>>>>>>> only a few lines, and cannot be translated. Cut and paste instead.)
>>>>>>>
>>>>>>> Did you do
>>>>>>>
>>>>>>> *sudo apt-get update*
>>>>>>>
&g

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

[Geni 0815]

Thanks for the explanation.

I had target_report = SeasonsReport, and there are 2 unit definitions for 
some.
 km_per_hour =% .0f
 km_per_hour2 =% .1f
 knot =% .0f
 knot2 =% .1f
meter_per_second = %.1f
meter_per_second2 = %.1f
mile_per_hour = %.0f
mile_per_hour2 = %.1f

  I have now redefined target_report = LoopDataReport, now it works as 
desired

Am Mittwoch, 12. August 2020 14:56:16 UTC+2 schrieb John Kline:
>
> > Where can I find a description of what a “Rain Year” is?
>
> By default, rainyear is the same as year.  It’s the 12-month period for 
> which the cumulative rain amount is measured.
> See: https://en.wikipedia.org/wiki/Water_year
> To set the rain year, see:  
> http://weewx.com/docs/usersguide.htm#rain_year_start
>
> > Where and how can I set that $wind.rms.formatted and 
> $windGust.max.formatted have a decimal place at km / h?
>
> I’m assuming you mean .rms.formatted and 
> .windGust.max.formatted (where  is 10m, day, week, month, 
> year or rainyear).
>
> Also assuming you want to see one decimal position in these values.
>
> In the LoopDataReport section of weewx.conf, there is already 1 decimal 
> place specified for km_per_hour (“%.1f”), unless you have changed it:
>[[[Units]]]
> StringFormats
> mile_per_hour = %.1f
> degree_C = %.1f
> km_per_hour = %.1f
> degree_F = %.1f 
>
> I suspect you have a different target report specified:
> Let’s imagine your [LoopData] section looks like this where the 
> target_report is WeatherBoardReport:
>
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/weewx/gauge-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = WeatherBoardReport
>
> In this case, you would to specify the decimal for km_per_hour under 
> WeatherBoardReport, since that is the report you have specified for 
> conversion and formattting.  You would want that report to specify the 
> decimal place for km_per_hour.
>
> [[WeatherBoardReport]]
>[[[Units]]]
> StringFormats
> km_per_hour = %.1f
>
>
> On Aug 11, 2020, at 11:01 PM, Geni 0815 > 
> wrote:
>
> 
> Hi John, Thanks for the new version.
> I still have the following questions:
> Where can I find a description of what a "Rain Year" is?
> Where and how can I set that $wind.rms.formatted and 
> $windGust.max.formatted also have a decimal place at km / h?
> Current Livelink <https://affolter.familyds.net/wetter/loopdata/>
>
> Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
>>
>> OK, I found the issue.  My tests simulate running weewx and processing 
>> packets.  The issue was at startup where I use daily summaries to create 
>> accumulators for day, week, year and rainyear.  That code was missing the 
>> first daily summary of each of these periods.
>>
>> I’ve fixed this issue in v2.7.  Please give it a try.
>>
>> On Aug 11, 2020, at 9:41 AM, John Kline  wrote:
>>
>> 
>> It does not look like you have installed from head on github.
>>
>> Go to this page:
>>
>> https://github.com/chaunceygardiner/weewx-loopdata
>>
>> Click “Code” and then click download zip.  Install that zip file.
>>
>> When you do that, after time_delta in the log, you should see week_start 
>> and rainyear_start.
>>
>> On Aug 11, 2020, at 9:37 AM, Geni 0815  wrote:
>>
>> 
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> tmpname: /tmp/LoopDataz7h4ntn0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> enable : 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_server  : www.foobar.com
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_port: None
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> remote_user: root
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_dir   
>>   Af: /home/weewx/loop-data
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> compress   : 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> log_success: 0
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> ssh_options: -o ConnectTimeout=1
>> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
>> timeout: 1
>> Aug 11 18:05:41 Wetter

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

[Geni 0815]

Hi John, Thanks for the new version.
I still have the following questions:
Where can I find a description of what a "Rain Year" is?
Where and how can I set that $wind.rms.formatted and $windGust.max.formatted 
also have a decimal place at km / h?
Current Livelink <https://affolter.familyds.net/wetter/loopdata/>

Am Mittwoch, 12. August 2020 03:20:18 UTC+2 schrieb John Kline:
>
> OK, I found the issue.  My tests simulate running weewx and processing 
> packets.  The issue was at startup where I use daily summaries to create 
> accumulators for day, week, year and rainyear.  That code was missing the 
> first daily summary of each of these periods.
>
> I’ve fixed this issue in v2.7.  Please give it a try.
>
> On Aug 11, 2020, at 9:41 AM, John Kline > 
> wrote:
>
> 
> It does not look like you have installed from head on github.
>
> Go to this page:
>
> https://github.com/chaunceygardiner/weewx-loopdata
>
> Click “Code” and then click download zip.  Install that zip file.
>
> When you do that, after time_delta in the log, you should see week_start 
> and rainyear_start.
>
> On Aug 11, 2020, at 9:37 AM, Geni 0815 > 
> wrote:
>
> 
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> tmpname: /tmp/LoopDataz7h4ntn0
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> enable : 0
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> remote_server  : www.foobar.com
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> remote_port: None
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> remote_user: root
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: remote_dir   
>   Af: /home/weewx/loop-data
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> compress   : 0
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> log_success: 0
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> ssh_options: -o ConnectTimeout=1
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> timeout: 1
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> skip_if_older_than : 3
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> time_delta : 10800
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> trend_obstypes : ['barometer', 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> rainyear_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
> 'windGust', 'windGustDir', 'rain']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> year_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
> 'windGust', 'windGustDir', 'rain']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> month_obstypes : ['wind', 'windSpeed', 'windDir', 'windGust', 
> 'windGustDir', 'rain', 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> week_obstypes  : ['wind', 'windSpeed', 'windDir', 'windGust', 
> 'windGustDir', 'rain', 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> day_obstypes   : ['windGust', 'wind', 'windSpeed', 'windDir', 
> 'windGustDir', 'rain', 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> ten_min_obstypes   : ['windGust', 'wind', 'windSpeed', 'windDir', 
> 'windGustDir', 'rain', 'outTemp']
> Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
> baro_trend_descs   : {: 'Rising Very 
> Rapidly', : 'Rising 
>
> Am Dienstag, 11. August 2020 18:12:01 UTC+2 schrieb John Kline:
>>
>> OK, before we look at the daily summaries in your database, please 
>> install loopdata at head.  I’ve added logging for week_start and 
>> rainyear_start at startup.  Let’s make sure that the extension thinks 
>> week_start is 0.  Install the the extension. Restart weewx and then paste 
>> in the lines from the log.  They should look something like this:
>> Aug 11 09:09:14 ella weewx[5404] INFO user.loopdata: week_start : 
>> 0
>> Aug 11 09:09:14 ella weewx[5404] INFO user.loopdata: rainyear_start : 
>> 1
>>
>> On Aug 11, 2020, at 8:49 AM, geni08...@gmail.com  
>> wr

Re: [weewx-user] Re: upgrade from weewx 3.9.2 to 4.1.1 doesn't work ...

[Geni 0815]

pi@raspberrypi:~ $ PRETTY_NAME="Raspbian GNU/Linux 9 (stretch)"

pi@raspberrypi:~ $ NAME="Raspbian GNU/Linux"

pi@raspberrypi:~ $ VERSION_ID="9"

pi@raspberrypi:~ $ VERSION="9 (stretch)"

pi@raspberrypi:~ $ VERSION_CODENAME=stretch

pi@raspberrypi:~ $ ID=raspbian

pi@raspberrypi:~ $ ID_LIKE=debian

pi@raspberrypi:~ $ HOME_URL="http://www.raspbian.org/";

pi@raspberrypi:~ $ SUPPORT_URL="http://www.raspbian.org/RaspbianForums";

pi@raspberrypi:~ $ BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs";


Am Dienstag, 11. August 2020 16:45:24 UTC+2 schrieb Tom Keffer:
>
> What version of Rasbian are you running? 
>
> *cat /etc/os-release*
>
> -tk
>
> On Tue, Aug 11, 2020 at 7:25 AM geni08...@gmail.com  > wrote:
>
>> pi@raspberrypi:~ $ sudo apt install weewx
>> Paketlisten werden gelesen... Fertig
>> Abhängigkeitsbaum wird aufgebaut.
>> Statusinformationen werden eingelesen Fertig
>> Einige Pakete konnten nicht installiert werden. Das kann bedeuten, dass
>> Sie eine unmögliche Situation angefordert haben oder, wenn Sie die
>> Unstable-Distribution verwenden, dass einige erforderliche Pakete noch
>> nicht erstellt wurden oder Incoming noch nicht verlassen haben.
>> Die folgenden Informationen helfen Ihnen vielleicht, die Situation zu 
>> lösen:
>>
>> Die folgenden Pakete haben unerfüllte Abhängigkeiten:
>>  weewx : Hängt ab von: python3-cheetah ist aber nicht installierbar
>> E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene 
>> defekte Pakete.
>> pi@raspberrypi:~ $
>>
>> tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 14:30:02 UTC+2:
>>
>>> I'm sorry: I just realized that your post is unrelated to the original 
>>> post. We need some context to understand what you are trying to do. The 
>>> screenshot you sent does not match your description of what you did. Are 
>>> you truly upgrading? If so, from what version?
>>>
>>> What happens when you do a simple install:
>>>
>>>
>>> *wget -qO - http://weewx.com/apt/weewx-python3.list 
>>>  | sudo tee 
>>> /etc/apt/sources.list.d/weewx.list*
>>> *sudo apt update*
>>> *sudo apt install weewx*
>>>
>>> -tk
>>>
>>> On Mon, Aug 10, 2020 at 10:44 PM geni08...@gmail.com <
>>> geni08...@gmail.com> wrote:
>>>
 I did this:
 wget -qO - http://weewx.com/apt/weewx-python3.list | sudo tee 
 /etc/apt/sources.list.d/weewx.list
 sudo apt-get update
 sudo apt-get upgrade
 sudo apt install python3-mysqldb 
 sudo apt install python3-ephem
 sudo apt-get update
 sudo apt-get upgrade


 tke...@gmail.com schrieb am Dienstag, 11. August 2020 um 02:56:50 
 UTC+2:

> (Please do not send a screen shot. They are hard to read, include only 
> a few lines, and cannot be translated. Cut and paste instead.)
>
> Did you do
>
> *sudo apt-get update*
>
> first?
>
> On Mon, Aug 10, 2020 at 10:02 AM geni08...@gmail.com <
> geni08...@gmail.com> wrote:
>
>> Update gets stuck with errors from missing packages
>> [image: weewx1.jpg]
>>
>> Jlou 43 schrieb am Dienstag, 4. August 2020 um 23:13:53 UTC+2:
>>
>>>  Thanks for your reply, but I solved my problem by reinstalling 
>>> this way:
>>>
>>>
>>> 3. Install WeeWX 
>>>
>>> After installing the prerequisites, you can install WeeWX itself.
>>>
>>>1. 
>>>
>>>Expand the source archive:
>>>
>>>tar xvfz weewx-X.Y.Z.tar.gz
>>>
>>>2. 
>>>
>>>Change directory into the expanded archive:
>>>
>>>cd weewx-X.Y.Z
>>>
>>>3. 
>>>
>>>To specify an install location different from the default 
>>>/home/weewx, modify the parameter home in the setup.cfg file. 
>>>Mac users will want to change it to /Users/Shared/weewx. 
>>>4. 
>>>
>>>Then build and install. Python 2 users: substitute python2 for 
>>>python3. 
>>>
>>>python3 ./setup.py build
>>>sudo python3 ./setup.py install
>>>
>>>
>>> I replace python3 by python2 and now everything works perfectly, but 
>>> if i have to switch to python3 your advice will be helpful.
>>> Thank you.
>>>
>>>
>>> -- 
>> You received this message because you are subscribed to the Google 
>> Groups "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, 
>> send an email to weewx-user+...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/weewx-user/2f8b8c32-509d-4cac-9ce7-36e3354418den%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
 You received this message because you are subscribed to the Google 
 Groups "weewx-user" group.
>>>

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

[Geni 0815]

Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
tmpname: /tmp/LoopDataz7h4ntn0
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
enable : 0
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
remote_server  : www.foobar.com
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
remote_port: None
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
remote_user: root
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
remote_dir : /home/weewx/loop-data
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
compress   : 0
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
log_success: 0
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
ssh_options: -o ConnectTimeout=1
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
timeout: 1
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
skip_if_older_than : 3
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
time_delta : 10800
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
trend_obstypes : ['barometer', 'outTemp']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
rainyear_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
'windGust', 'windGustDir', 'rain']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
year_obstypes  : ['outTemp', 'wind', 'windSpeed', 'windDir', 
'windGust', 'windGustDir', 'rain']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
month_obstypes : ['wind', 'windSpeed', 'windDir', 'windGust', 
'windGustDir', 'rain', 'outTemp']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
week_obstypes  : ['wind', 'windSpeed', 'windDir', 'windGust', 
'windGustDir', 'rain', 'outTemp']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
day_obstypes   : ['windGust', 'wind', 'windSpeed', 'windDir', 
'windGustDir', 'rain', 'outTemp']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
ten_min_obstypes   : ['windGust', 'wind', 'windSpeed', 'windDir', 
'windGustDir', 'rain', 'outTemp']
Aug 11 18:05:41 Wetter-Raspi weewx[1211] INFO user.loopdata: 
baro_trend_descs   : {: 'Rising Very 
Rapidly', : 'Rising 

Am Dienstag, 11. August 2020 18:12:01 UTC+2 schrieb John Kline:
>
> OK, before we look at the daily summaries in your database, please install 
> loopdata at head.  I’ve added logging for week_start and rainyear_start at 
> startup.  Let’s make sure that the extension thinks week_start is 0. 
>  Install the the extension. Restart weewx and then paste in the lines from 
> the log.  They should look something like this:
> Aug 11 09:09:14 ella weewx[5404] INFO user.loopdata: week_start : 0
> Aug 11 09:09:14 ella weewx[5404] INFO user.loopdata: rainyear_start : 1
>
> On Aug 11, 2020, at 8:49 AM, geni08...@gmail.com  > wrote:
>
>  week_start = 0
>
> jo...@johnkline.com schrieb am Dienstag, 11. August 2020 um 16:08:18 
> UTC+2:
>
>> When does your week start?
>>
>> You should see something like this is weewx.conf:
>> # Start of week (0=Monday, 6=Sunday)
>> week_start = 6
>>
>> What value do you have for week_start?
>>
>> On Aug 11, 2020, at 3:20 AM, geni08...@gmail.com  
>> wrote:
>>
>> I found a syntax.
>>
>>
>> Question: for example "Hi Out Temp, week", shouldn't it be the highest 
>> temp since Monday? But this is not true for me! Why?
>>
>> geni08...@gmail.com schrieb am Dienstag, 11. August 2020 um 10:57:03 
>> UTC+2:
>>
>>> @John: I installed version 2.6.
>>> how do i get the values:
>>> >> style='white-space:pre;'>
>>> >> style='white-space:pre;'>
>>> >> style='white-space:pre;'>
>>> >> style='white-space:pre;'>
>>> >> style='white-space:pre;'>
>>
>> -- 
>> You received this message because you are subscribed 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/282de9d8-ff84-4c29-b302-2893aded408fn%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...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/weewx-user/40bdd07b-16f1-4413-b532-05222b4a8b5en%40googlegroups.com
>  
> 
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe f

[weewx-user] Belchertown Question about "yAxis_tickinterval"

[Geni 0815]

I have Belchertown Skin Version: 1.2rc2
"YAxis_tickinterval" doesn't work for me.

 [[chart4]]
 title = air pressure
 type = spline
 [[[barometer]]]
 yAxis_tickinterval = 2
 color = "# BECC00"

  still produces the following graphic:

[image: belch06.jpg] 

I expect this

[image: belch07.jpg]



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

[weewx-user] Re: Belchertown, graphics are faulty

[Geni 0815]

Why is the value correct here?

[image: belch2.jpg]

https://affolter.familyds.net/wetter/graphs/?graph=monthnow


Am Mittwoch, 15. Juli 2020 14:19:19 UTC+2 schrieb Pat:
>
> Sounds like you may have some problems with your database. I suggest you 
> take a backup and follow the database drop-daily 
> <http://www.weewx.com/docs/utilities.htm#Action_--drop-daily>and 
> rebuild-daily 
> <http://www.weewx.com/docs/utilities.htm#Action_--rebuild-daily>and see 
> if that helps
>
> The graphs uses your archive table
>
> The reports uses your daily tables. 
>
> Seems like those aren't in sync for you.
>
> On Wednesday, July 15, 2020 at 6:16:48 AM UTC-4, Geni 0815 wrote:
>>
>> Hi Pat, I just noticed the following:
>> As an example in the graphic "last 30 days", "rain per day". These values 
>> sometimes change every hour!
>> For my understanding, the amount of rain per day is to be understood on a 
>> calendar day within the last 30 days.
>> In the graphics, however, the day begins fluently.
>> I want a day to be a calendar day and not flowing 24h.
>> This is how it is handled in the Templete Season.
>> How do I have to make the graphic settings so that a day is a calendar 
>> day?
>> I hope I have clearly described my wish.
>>
>> Am Sonntag, 12. Juli 2020 10:47:51 UTC+2 schrieb Geni 0815:
>>>
>>> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 
>>> 0mm, 15mm and 3.2mm on the corresponding days. The sum is correct but 
>>> wrongly divided. Where is the mistake?
>>> [image: belch10.jpg]
>>> [image: belch11.jpg]
>>> [month]
>>> # Chart Timespan Defaults
>>> title = "Letzte 30 Tage"
>>> show_button = true
>>> button_text = "Letzte 30 Tage"
>>> type = spline
>>> time_length = 2592000 # Last 30 days
>>> tooltip_date_format = " LL"
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640 # 1 day in milliseconds
>>> 
>>> [[chart3]]
>>> title = Regenx
>>> type = line
>>> aggregate_type=sum
>>> [[[rainTotal]]]
>>> name = Regen Total
>>> [[[rain]]]
>>> yAxis = 1
>>> type = column
>>> 
>>> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>>>
>>

-- 
You received this message because you are subscribed 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/01689e5f-19f1-48f4-b434-0967d9fa95b0o%40googlegroups.com.

[weewx-user] Re: Belchertown, graphics are faulty

[Geni 0815]

Hi Pat, I just noticed the following:
As an example in the graphic "last 30 days", "rain per day". These values 
sometimes change every hour!
For my understanding, the amount of rain per day is to be understood on a 
calendar day within the last 30 days.
In the graphics, however, the day begins fluently.
I want a day to be a calendar day and not flowing 24h.
This is how it is handled in the Templete Season.
How do I have to make the graphic settings so that a day is a calendar day?
I hope I have clearly described my wish.

Am Sonntag, 12. Juli 2020 10:47:51 UTC+2 schrieb Geni 0815:
>
> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 0mm, 
> 15mm and 3.2mm on the corresponding days. The sum is correct but wrongly 
> divided. Where is the mistake?
> [image: belch10.jpg]
> [image: belch11.jpg]
> [month]
> # Chart Timespan Defaults
> title = "Letzte 30 Tage"
> show_button = true
> button_text = "Letzte 30 Tage"
> type = spline
> time_length = 2592000 # Last 30 days
> tooltip_date_format = " LL"
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640 # 1 day in milliseconds
> 
> [[chart3]]
> title = Regenx
> type = line
> aggregate_type=sum
> [[[rainTotal]]]
> name = Regen Total
> [[[rain]]]
> yAxis = 1
> type = column
> 
> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>

-- 
You received this message because you are subscribed 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/e7ad98e7-cf53-44b5-a604-9b7d281c5855o%40googlegroups.com.

[weewx-user] Re: Belchertown, graphics are faulty

[Geni 0815]

Hi Pat, for me the mistake is more than just a rounding.

Day in the report  in graphics
2620.023.4
27 3.4  0.0
28 8.633.2
29   24.8  0.2

0113.418.6
02 5.4 0.8
03 0.6 0.0
10 9.015.0
11 8.6 3.2
12 1.0 0.4


Am Dienstag, 14. Juli 2020 19:44:15 UTC+2 schrieb Pat:
>
> Edit your bin/user/belchertown.py file. 
>
> Look for this line:
>
> if time_length == "today" or time_length == "timespan_specific" or 
> isinstance(time_length, int):
>
>
> Change it to
>
> if time_length == "today" or time_length == "timespan_specific":
>
>
>
> Update your graphs.conf with this
>
> [month]
> # Chart Timespan Defaults
> title = "Letzte 30 Tage"
> show_button = true
> button_text = "Letzte 30 Tage"
> type = spline
> time_length = 2592000 # Last 30 days
> tooltip_date_format = " LL"
> aggregate_type = max
> aggregate_interval = 86400 # 1 day
> gapsize = 8640 # 1 day in milliseconds
>
> [[chart3]]
> title = Regenx
> [[[rainTotal]]]
> type = line
> name = Rain Total
> [[[rain]]]   
> aggregate_type = sum
> yAxis = 1
> type = column
>
>
> Restart weewx and let me know if this works for you.
>
> Highcharts looks to be doing a little bit of rounding. I'm seeing my 2.42
>
>
> On Tuesday, July 14, 2020 at 12:59:42 PM UTC-4, Pat wrote:
>>
>> The rainTotal is the accumulation over the time span, so that will be 
>> your line graph. 
>>
>> The rain will show you rain over the aggregate_interval - so for this 
>> chart it's 1 day. 
>>
>> So your graph looks right, but I'm seeing the data a little wrong too. 
>> For example on June 28 I had 2.41 inches rain, but the graph shows it on 
>> June 29. 
>>
>> I'll look at why it's showing the wrong day. I think it's a setting with 
>> the way the json generator is running
>>
>>
>> On Tuesday, July 14, 2020 at 12:15:48 PM UTC-4, Geni 0815 wrote:
>>>
>>> I would like to have a graph of the last 30 days with a column with the 
>>> amount of rain per day and a curve that accumulates these daily amounts.
>>> What should the definition in fer Graphic.conf look like?
>>> Do these daily values have to match the NOAA reports?
>>>
>>> Am Dienstag, 14. Juli 2020 16:52:45 UTC+2 schrieb Pat:
>>>>
>>>> Which one is the error? rainTotal does not use the aggregate_type since 
>>>> it is already aggregating these totals. 
>>>>
>>>> On Monday, July 13, 2020 at 1:54:36 AM UTC-4, geni08...@gmail.com 
>>>> wrote:
>>>>>
>>>>> @Pat: The error is not only with me, also with @Andre. I see the 
>>>>> error when the graphic "last 30 days" has been selected and the rain is 
>>>>> selected as the daily total bar. The graphics are one day late. No 
>>>>> daily value is correct, the sum of 3-4 days is correct again. In my 
>>>>> opinion the graphic has problems to calculate the correct local start and 
>>>>> end of the day. 
>>>>>
>>>>> geni08...@gmail.com schrieb am Sonntag, 12. Juli 2020 um 10:47:51 
>>>>> UTC+2:
>>>>>
>>>>>> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 
>>>>>> 0mm, 15mm and 3.2mm on the corresponding days. The sum is correct but 
>>>>>> wrongly divided. Where is the mistake?
>>>>>> [image: belch10.jpg]
>>>>>> [image: belch11.jpg]
>>>>>> [month]
>>>>>> # Chart Timespan Defaults
>>>>>> title = "Letzte 30 Tage"
>>>>>> show_button = true
>>>>>> button_text = "Letzte 30 Tage"
>>>>>> type = spline
>>>>>> time_length = 2592000 # Last 30 days
>>>>>> tooltip_date_format = " LL"
>>>>>> aggregate_type = max
>>>>>> aggregate_interval = 86400 # 1 day
>>>>>> gapsize = 8640 # 1 day in milliseconds
>>>>>> 
>>>>>> [[chart3]]
>>>>>> title = Regenx
>>>>>> type = line
>>>>>> aggregate_type=sum
>>>>>> [[[rainTotal]]]
>>>>>> name = Regen Total
>>>>>> [[[rain]]]
>>>>>> yAxis = 1
>>>>>> type = column
>>>>>> 
>>>>>> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>>>>>>
>>>>>

-- 
You received this message because you are subscribed 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/34034a73-3e96-49eb-a73b-f3add3487577o%40googlegroups.com.

[weewx-user] Re: Belchertown, graphics are faulty

[Geni 0815]

I would like to have a graph of the last 30 days with a column with the 
amount of rain per day and a curve that accumulates these daily amounts.
What should the definition in fer Graphic.conf look like?
Do these daily values have to match the NOAA reports?

Am Dienstag, 14. Juli 2020 16:52:45 UTC+2 schrieb Pat:
>
> Which one is the error? rainTotal does not use the aggregate_type since it 
> is already aggregating these totals. 
>
> On Monday, July 13, 2020 at 1:54:36 AM UTC-4, geni08...@gmail.com wrote:
>>
>> @Pat: The error is not only with me, also with @Andre. I see the error 
>> when the graphic "last 30 days" has been selected and the rain is selected 
>> as the daily total bar. The graphics are one day late. No daily value is 
>> correct, the sum of 3-4 days is correct again. In my opinion the graphic 
>> has problems to calculate the correct local start and end of the day. 
>>
>> geni08...@gmail.com schrieb am Sonntag, 12. Juli 2020 um 10:47:51 UTC+2:
>>
>>> On 3 days we had rain of 9mm, 8.6mm and 0.6mm. The graphic now shows 
>>> 0mm, 15mm and 3.2mm on the corresponding days. The sum is correct but 
>>> wrongly divided. Where is the mistake?
>>> [image: belch10.jpg]
>>> [image: belch11.jpg]
>>> [month]
>>> # Chart Timespan Defaults
>>> title = "Letzte 30 Tage"
>>> show_button = true
>>> button_text = "Letzte 30 Tage"
>>> type = spline
>>> time_length = 2592000 # Last 30 days
>>> tooltip_date_format = " LL"
>>> aggregate_type = max
>>> aggregate_interval = 86400 # 1 day
>>> gapsize = 8640 # 1 day in milliseconds
>>> 
>>> [[chart3]]
>>> title = Regenx
>>> type = line
>>> aggregate_type=sum
>>> [[[rainTotal]]]
>>> name = Regen Total
>>> [[[rain]]]
>>> yAxis = 1
>>> type = column
>>> 
>>> Live: https://affolter.familyds.net/wetter/graphs/?graph=month
>>>
>>

-- 
You received this message because you are subscribed 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/54315ccd-8336-4210-becb-4687e322543bo%40googlegroups.com.

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

[Geni 0815]

@John: WeaterBoard 2.0b3 causes problems. everything worked until the time 
with the old version.
With version 2 I get the error: Uncaught ReferenceError: inHumidity is not 
defined, and refreshing doesn't seem to work properly.
The syntax also seems different?

I'll test that with current.dateTime.raw in a moment

Am Dienstag, 14. Juli 2020 15:52:13 UTC+2 schrieb John Kline:
>
> It looks like you are missing the following in the fields line:
>
> current.dateTime.raw
>
> That is, to upgrade, dateTime needs to be changed to current.dateTime.raw
>
> I’ll update the How to Upgrade section to reflect that.
>
> On Jul 14, 2020, at 6:01 AM, Geni 0815 > 
> wrote:
>
> 
> @John: I installed version 2.0.b6, almost everything worked right away, 
> congratulations.
> What is not yet running is the label: Live and the clock at the bottom 
> right.
>
>
> Am Freitag, 10. Juli 2020 20:09:30 UTC+2 schrieb John Kline:
>>
>> I had a look.  You never actually write FMT_windDir in the JavaScript. 
>>  Just add:
>> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
>> on the appropriate line in realtime_updater.inc.
>>
>> As for barometerRate.  I do see it.  I just spills over to the next line. 
>>  It looks like I am not properly formatting barometerRate.  I will fix that 
>> as part of the 2.0 release which I am working on and hope to have out this 
>> weekend.
>>
>> On Jul 10, 2020, at 9:03 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>> Hi John, I'm on the mountain, there was more. Can you please keep an eye 
>> on the two files?
>>
>>
>> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:
>>
>>> You need to add the fields:
>>> barometerRate
>>> FMT_windDir
>>> to the fields line in the LoopData section of weewx.conf.
>>>
>>> After you do that and restart WeeWX, verify that you see these readings 
>>> in loop-data.txt.
>>>
>>> Finally, you need to set these values in the JavaScript.
>>>
>>> If you have already done all of the above, perhaps you have a JavaScript 
>>> error.  Have a look in the JavaScript console in your browser (note: it may 
>>> be called something else, search for how to see JavaScript errors).
>>>
>>> BTW, this weekend, I should have a version of LoopData out that uses the 
>>> same naming scheme as cheetah.  As such, you will then specify 
>>> $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
>>> (for example) in the fields line in weewx.conf and those keys will show up 
>>> in loop-data.txt.  There was no good reason to invent a new language for 
>>> this. 
>>>
>>> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>>  
>>>
>>> what do I have to change so that the two values (in the yellow circle) 
>>> are always displayed? Now they only flash briefly during a manual 
>>> refresh.
>>>
>>> 
>>>
>>> in index.html.templ:
>>>  >> style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>>>  
>>> $current.windDir.ordinal_compass ($current.windDir)
>>> $current.barometer 
>>> ($trend.barometer.formatted) - >> id="FMT_outHumidity">$current.outHumidity
>>>
>>> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 
>>> UTC+2:
>>>
>>>>
>>>>
>>>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>>>> wrote:
>>>>
>>>> Question for my understanding:
>>>>
>>>>
>>>> If or why is the id = string supplemented with $current, $day or not at 
>>>> all?
>>>>
>>>> 
>>>>
>>>>
>>>> In the examples, no IDs is supplemented with current, day or none at 
>>>> all.  Some values say $current, which means the current observation.  Some 
>>>> say day, which would be for the day and have an aggregator 
>>>> ($day.rain.sum). 
>>>>  In any event, all of these values are overwritten every couple of seconds 
>>>> by the javascript.  As such, they could be removed.
>>>>
>>>> As for the ids.  They could be anything you wish.  They just are used 
>>>> by the JavaScript to look up the element.  As a naming scheme for ids, I 
>>>> chose to to name them for the corresponding key in loop-data.txt.
>>>>
>>>> For example, FMT_HI_windGust.  Th

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

[Geni 0815]

@John: I installed version 2.0.b6, almost everything worked right away, 
congratulations.
What is not yet running is the label: Live and the clock at the bottom 
right.


Am Freitag, 10. Juli 2020 20:09:30 UTC+2 schrieb John Kline:
>
> I had a look.  You never actually write FMT_windDir in the JavaScript. 
>  Just add:
> + ‘ (‘ + result[‘FMT_windDir’] + ‘)’
> on the appropriate line in realtime_updater.inc.
>
> As for barometerRate.  I do see it.  I just spills over to the next line. 
>  It looks like I am not properly formatting barometerRate.  I will fix that 
> as part of the 2.0 release which I am working on and hope to have out this 
> weekend.
>
> On Jul 10, 2020, at 9:03 AM, geni08...@gmail.com  > wrote:
>
>  
> Hi John, I'm on the mountain, there was more. Can you please keep an eye 
> on the two files?
>
>
> jo...@johnkline.com schrieb am Freitag, 10. Juli 2020 um 16:05:18 UTC+2:
>
>> You need to add the fields:
>> barometerRate
>> FMT_windDir
>> to the fields line in the LoopData section of weewx.conf.
>>
>> After you do that and restart WeeWX, verify that you see these readings 
>> in loop-data.txt.
>>
>> Finally, you need to set these values in the JavaScript.
>>
>> If you have already done all of the above, perhaps you have a JavaScript 
>> error.  Have a look in the JavaScript console in your browser (note: it may 
>> be called something else, search for how to see JavaScript errors).
>>
>> BTW, this weekend, I should have a version of LoopData out that uses the 
>> same naming scheme as cheetah.  As such, you will then specify 
>> $current.windSpeed, $current.windDir.ordinal_compass and $current.windDir 
>> (for example) in the fields line in weewx.conf and those keys will show up 
>> in loop-data.txt.  There was no good reason to invent a new language for 
>> this. 
>>
>> On Jul 10, 2020, at 1:54 AM, geni08...@gmail.com  
>> wrote:
>>
>>  
>>
>> what do I have to change so that the two values (in the yellow circle) 
>> are always displayed? Now they only flash briefly during a manual 
>> refresh.
>>
>> 
>>
>> in index.html.templ:
>>  > style="font-family:monospace;font-size:85px;text-align:center;">$current.windSpeed
>>  
>> $current.windDir.ordinal_compass ($current.windDir)
>> $current.barometer 
>> ($trend.barometer.formatted) - > id="FMT_outHumidity">$current.outHumidity
>>
>> jo...@johnkline.com schrieb am Donnerstag, 9. Juli 2020 um 15:40:48 
>> UTC+2:
>>
>>>
>>>
>>> On Jul 9, 2020, at 1:52 AM, geni08...@gmail.com  
>>> wrote:
>>>
>>> Question for my understanding:
>>>
>>>
>>> If or why is the id = string supplemented with $current, $day or not at 
>>> all?
>>>
>>> 
>>>
>>>
>>> In the examples, no IDs is supplemented with current, day or none at 
>>> all.  Some values say $current, which means the current observation.  Some 
>>> say day, which would be for the day and have an aggregator ($day.rain.sum). 
>>>  In any event, all of these values are overwritten every couple of seconds 
>>> by the javascript.  As such, they could be removed.
>>>
>>> As for the ids.  They could be anything you wish.  They just are used by 
>>> the JavaScript to look up the element.  As a naming scheme for ids, I chose 
>>> to to name them for the corresponding key in loop-data.txt.
>>>
>>> For example, FMT_HI_windGust.  The JavaScript will get lookup the 
>>> element with the id FMT_HI_windGust.  It will then lookup the value in 
>>> loop-data.txt for the key FMT_HI_windGust and set the contents of the HTML 
>>> tag (innerHTML property) to that value.
>>>
>>> If the id was foo on this element, the JavaScript would have to find the 
>>> foo element in the DOM.  Of course, it will still need to use the key 
>>> FMT_HI_windGust for looking up the loop-data value.
>>>
>>> As for the naming scheme in loop-data.txt:
>>> FMT_HI_windGust
>>> The FMT_ means include the label.
>>> The HI_ means give me today’s high.
>>>
>>> FMT_windGust would be for the current observation and would include the 
>>> label.
>>>
>>> windGust would be for the current observation. It would NOT include a 
>>> label, but it would still be formatted.  That is, if wind should have 1 
>>> decimal place, it be formatted as such (e.g., 4.0).
>>>
>>> The README has this info, but to summarize:
>>>
>>> If the key is missing an aggregator (HI, LO, AVG, WAVG, SUM, RMS, 
>>> VEC_AVG, VEC_DIR), it is the current observation.  If it has an aggregator 
>>> prefix, it is for the day.  Exceptions are the items I made up 10mMaxGust 
>>> (which is 10 minutes) and barometerRate (which is a delta from 3 hours ago) 
>>> and windRose.
>>>
>>> FMT_ includes the label.
>>>
>>> UNITS_ is the unit for the observation.
>>>
>>> LABEL_ is the label for the observation.
>>>
>>> COMPASS_ for windDIr and windGustDir gives compass (text) direction.
>>>
>>> DESC_ for barometer rate gives a text description of the rate (and 
>>> probably needs to be internationalized).
>>>
>>> T_ is the time of the observation.  For example, T_HI_ would be the 
>>> time today that the 

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

[Geni 0815]

Now it gets interesting, where do you see kph on my season page?

Am Sonntag, 5. Juli 2020 14:18:00 UTC+2 schrieb John Kline:
>
> That’s great that you are up and running.  I had a look at your 
> WeatherBoard report and indeed I see kph.
>
> I just tried this myself.  I targeted SeasonsReport (since that is what 
> you did) and added the km/h and it’s working for me.  Let’s compare our 
> SeasonsReport entries.
>
> I have the following.  Note the Labels entry with km/h in quotes with a 
> leading space.
> Please send what you have for this section.
>
> [[SeasonsReport]]
> # The SeasonsReport uses the 'Seasons' skin, which contains the
> # images, templates and plots for the report.
> skin = Seasons
> enable = true
> [[[Units]]]
> StringFormats
> mile_per_hour = %.1f
> degree_C = %.1f
> km_per_hour = %.1f
> degree_F = %.1f
> Labels
> km_per_hour = " km/h"
>
> On Jul 5, 2020, at 4:58 AM, Geni 0815 > 
> wrote:
>
> 
> @John: I have new installed the weewx-loopdata here my settings in 
> weewx.conf. In my SeasonsReport 
> <https://affolter.familyds.net/wetter/Seasons/index.html>the field 
> *km_per_hour 
> *is correctly displayed with km/h.
> appended a loop_data.txt and kph is still in it.
>
> How does your built-in tests for conversions and formatting work?
>
> [LoopData]
> [[FileSpec]]
> loop_data_dir = /home/pi/wetter/loop-data
> filename = loop-data.txt
> [[Formatting]]
> target_report = SeasonsReport
> [[RsyncSpec]]
> enable = false
> remote_server = www.foobar.com
> remote_user = root
> remote_dir = /home/weewx/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, FMT_appTemp
> [[Rename]]
>
> -- 
> You received this message because you are 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/34cc8d8a-4be6-48d6-9503-505d399d10ceo%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/34cc8d8a-4be6-48d6-9503-505d399d10ceo%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/9d702cab-41cf-4e8b-9e8f-f3f6464f9f50o%40googlegroups.com.
# WEEWX CONFIGURATION FILE
# modify ea 26.12.2019 MariaDB 10 aktivieren mit DB weewx
# 27.12.2019 Wechsel Raspi-HW zu 3+
# 29.12.2019 
# Copyright (c) 2009-2019 Tom Keffer 
# See the file LICENSE.txt for your rights.
# 17.06.2020 Belchertown Skin
# 05.07.2020 HTML_ROOT = /home/pi/wetter als default dadurch ist kein FTP mehr 
notwendig
# 05.06.2020 loop-data, weatherboard
##

# This section is for general configuration information.

# Set to 1 for extra debug info, otherwise comment it out or set to zero
debug = 0

# Root directory of the weewx data file hierarchy for this station
WEEWX_ROOT = /

# Whether to log successful operations
log_success = False

# Whether to log unsuccessful operations
log_failure = True

# How long to wait before timing out a socket (FTP, HTTP) connection
socket_timeout = 20

# Do not modify this. It is used when installing and updating weewx.
version = 4.1.1

##

#   This section is for information about the station.

[Station]

# Description of the station location
location = "Wetterstation Buttwil, Schweiz"

# Latitude and longitude in decimal degrees
latitude = 47.2667
longitude = 8.3078

# Altitude of the station, with unit it is in. This is downloaded from
# from the station if the hardware supports it.
altitude = 668, meter

# Set to type of station hardware. There must be a corresponding stanza

Re: [weewx-user] weewx has been dead since an extension installation

[Geni 0815]

Am Sonntag, 5. Juli 2020 13:29:49 UTC+2 schrieb John Kline:
>
> I don’t believe that would cause the problem.  Do you have the bad copy of 
> weewx.conf that you could send?
>
> On Jul 5, 2020, at 1:39 AM, Geni 0815  wrote:
>
> 
> @John: comment on your impression, I was helpless and didn't know what to 
> do next!
>
> The difference in weewx.conf from the still good to the dead version is 
> the entry
>
> Labels]]]
> km_per_hour = km / h
>
> under [[WeatherBoardReport]]
>
> And the Loop-Data version 1.3.4 and after 1.3.5
>
> Question: can this label entry have this effect?
>
> Am Sonntag, 5. Juli 2020 02:18:52 UTC+2 schrieb John Kline:
>>
>> HI Tom,
>>
>> I’m not sure which of the two errors we have discussed you have in mind?
>>
>> The most likely case for this error is that it was caused by a hand 
>> modification to weewx.conf that I asked him to make.  I asked him to look 
>> at his weewx.conf backups to restore the file to a working state.  He has 
>> done that.  Since the user was quite upset at weewx breaking, out of an 
>> abundance of caution (and mostly because I don’t want to deal with it), I 
>> won’t proceed until we understand how weewx.conf got into a bad state.
>>
>> The configobj error I am getting is at head.  It has NEVER been observed 
>> in 4.1.1.  It has also NEVER been observed without the LiveSeasonsSkin 
>> which this user has not installed and cannot install, as it is private.
>>
>> Perhaps you mean the non-existent database error, but that is not in the 
>> stack trace and has never been observed in 4.1.1.
>>
>> On Jul 4, 2020, at 4:59 PM, Tom Keffer  wrote:
>>
>> 
>> Oh dear. John, this error is looking familiar...
>>
>> On Sat, Jul 4, 2020 at 11:02 AM John Kline  wrote:
>>
>>> Before we do anything else, we need to figure out why your installation 
>>> broke.
>>>
>>> Did you make any manual changes to weewx.conf?  For example, did you 
>>> edit weewx.conf to change the label form “ kph” to “ km/h”?
>>>
>>> On Jul 4, 2020, at 10:51 AM, Geni 0815  wrote:
>>>
>>> 
>>> OK again, thank you
>>> But would like loop data, goal: instead of MQTT in Belchertown.
>>> Is this possible?
>>>
>>>
>>> Am Samstag, 4. Juli 2020 18:44:23 UTC+2 schrieb John Kline:
>>>>
>>>> Did you follow the steps I sent to manually remove loopdata?
>>>>
>>>> Also, I forgot one file:
>>>> sudo rm /bin/user/installer/loopdata
>>>>
>>>> One you have followed these steps, you will have a weewx untouched by 
>>>> loopdata and weatherboard.
>>>>
>>>> It looks like you have messed up your weewx.conf file.   If you look in 
>>>> your weewx home directory, you will see lots of backups.  You should 
>>>> probably compare those to get to a working weewx.conf file.
>>>>
>>>> On Jul 4, 2020, at 9:39 AM, Geni 0815  wrote:
>>>>
>>>> 
>>>> Weewx v 4.1.1
>>>> nothing has happened since loop-data 1.3.5 was installed
>>>>
>>>>
>>>> what went wrong, how can I correct this?
>>>>
>>>> wee_extension --list
>>>>
>>>>> 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.
>>>>>
>>>>>
>>>> or wee_debug --info
>>>>
>>>>> pi@Wetter-Raspi:~ $ wee_debug --info
>>>>> Traceback (most recent call last):
>>>>>   File "/usr/share/weewx/wee_debug", line 435, in 
>>>>>

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

[Geni 0815]

@John: I have new installed the weewx-loopdata here my settings in 
weewx.conf. In my SeasonsReport 
the field *km_per_hour 
*is correctly displayed with km/h.
appended a loop_data.txt and kph is still in it.

How does your built-in tests for conversions and formatting work?

[LoopData]
[[FileSpec]]
loop_data_dir = /home/pi/wetter/loop-data
filename = loop-data.txt
[[Formatting]]
target_report = SeasonsReport
[[RsyncSpec]]
enable = false
remote_server = www.foobar.com
remote_user = root
remote_dir = /home/weewx/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, FMT_appTemp
[[Rename]]

-- 
You received this message because you are subscribed 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/34cc8d8a-4be6-48d6-9503-505d399d10ceo%40googlegroups.com.
{"dateTime": 1593949782, "windSpeed": "5", "COMPASS_windDir": "N", 
"DESC_barometerRate": "Falling Slowly", "FMT_barometer": "1017.4 hPa", 
"FMT_SUM_rain": "0.0 mm", "FMT_dewpoint": "16.7\u00b0C", "FMT_heatindex": 
"25.3\u00b0C", "FMT_outHumidity": "59%", "FMT_outTemp": "25.3\u00b0C", 
"FMT_rain": "0.0 mm", "FMT_rainRate": "0.0 mm/h", "FMT_windchill": 
"25.3\u00b0C", "FMT_windSpeed": "5 kph", "FMT_HI_windGust": "23 kph", 
"FMT_10mMaxGust": "13 kph", "FMT_appTemp": "26.6\u00b0C"}

Re: [weewx-user] weewx has been dead since an extension installation

[Geni 0815]

@John: comment on your impression, I was helpless and didn't know what to 
do next!

The difference in weewx.conf from the still good to the dead version is the 
entry

Labels]]]
km_per_hour = km / h

under [[WeatherBoardReport]]

And the Loop-Data version 1.3.4 and after 1.3.5

Question: can this label entry have this effect?

Am Sonntag, 5. Juli 2020 02:18:52 UTC+2 schrieb John Kline:
>
> HI Tom,
>
> I’m not sure which of the two errors we have discussed you have in mind?
>
> The most likely case for this error is that it was caused by a hand 
> modification to weewx.conf that I asked him to make.  I asked him to look 
> at his weewx.conf backups to restore the file to a working state.  He has 
> done that.  Since the user was quite upset at weewx breaking, out of an 
> abundance of caution (and mostly because I don’t want to deal with it), I 
> won’t proceed until we understand how weewx.conf got into a bad state.
>
> The configobj error I am getting is at head.  It has NEVER been observed 
> in 4.1.1.  It has also NEVER been observed without the LiveSeasonsSkin 
> which this user has not installed and cannot install, as it is private.
>
> Perhaps you mean the non-existent database error, but that is not in the 
> stack trace and has never been observed in 4.1.1.
>
> On Jul 4, 2020, at 4:59 PM, Tom Keffer > 
> wrote:
>
> 
> Oh dear. John, this error is looking familiar...
>
> On Sat, Jul 4, 2020 at 11:02 AM John Kline  > wrote:
>
>> Before we do anything else, we need to figure out why your installation 
>> broke.
>>
>> Did you make any manual changes to weewx.conf?  For example, did you edit 
>> weewx.conf to change the label form “ kph” to “ km/h”?
>>
>> On Jul 4, 2020, at 10:51 AM, Geni 0815 > 
>> wrote:
>>
>> 
>> OK again, thank you
>> But would like loop data, goal: instead of MQTT in Belchertown.
>> Is this possible?
>>
>>
>> Am Samstag, 4. Juli 2020 18:44:23 UTC+2 schrieb John Kline:
>>>
>>> Did you follow the steps I sent to manually remove loopdata?
>>>
>>> Also, I forgot one file:
>>> sudo rm /bin/user/installer/loopdata
>>>
>>> One you have followed these steps, you will have a weewx untouched by 
>>> loopdata and weatherboard.
>>>
>>> It looks like you have messed up your weewx.conf file.   If you look in 
>>> your weewx home directory, you will see lots of backups.  You should 
>>> probably compare those to get to a working weewx.conf file.
>>>
>>> On Jul 4, 2020, at 9:39 AM, Geni 0815  wrote:
>>>
>>> 
>>> Weewx v 4.1.1
>>> nothing has happened since loop-data 1.3.5 was installed
>>>
>>>
>>> what went wrong, how can I correct this?
>>>
>>> wee_extension --list
>>>
>>>> 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.
>>>>
>>>>
>>> or wee_debug --info
>>>
>>>> pi@Wetter-Raspi:~ $ wee_debug --info
>>>> Traceback (most recent call last):
>>>>   File "/usr/share/weewx/wee_debug", line 435, in 
>>>> main()
>>>>   File "/usr/share/weewx/wee_debug", line 118, in main
>>>> config_path, config_dict = weecfg.read_config(options.config_path, 
>>>> 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
>>>>

Re: [weewx-user] weewx has been dead since an extension installation

[Geni 0815]

OK again, thank you
But would like loop data, goal: instead of MQTT in Belchertown.
Is this possible?


Am Samstag, 4. Juli 2020 18:44:23 UTC+2 schrieb John Kline:
>
> Did you follow the steps I sent to manually remove loopdata?
>
> Also, I forgot one file:
> sudo rm /bin/user/installer/loopdata
>
> One you have followed these steps, you will have a weewx untouched by 
> loopdata and weatherboard.
>
> It looks like you have messed up your weewx.conf file.   If you look in 
> your weewx home directory, you will see lots of backups.  You should 
> probably compare those to get to a working weewx.conf file.
>
> On Jul 4, 2020, at 9:39 AM, Geni 0815 > 
> wrote:
>
> 
> Weewx v 4.1.1
> nothing has happened since loop-data 1.3.5 was installed
>
>
> what went wrong, how can I correct this?
>
> wee_extension --list
>
>> 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.
>>
>>
> or wee_debug --info
>
>> pi@Wetter-Raspi:~ $ wee_debug --info
>> Traceback (most recent call last):
>>   File "/usr/share/weewx/wee_debug", line 435, in 
>> main()
>>   File "/usr/share/weewx/wee_debug", line 118, in main
>> config_path, config_dict = weecfg.read_config(options.config_path, 
>> 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.
>>
>> -- 
> You received this message because you are 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/fd8cd91a-dc9c-412d-9cc5-4c5126f113f2o%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/weewx-user/fd8cd91a-dc9c-412d-9cc5-4c5126f113f2o%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

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

[weewx-user] weewx has been dead since an extension installation

[Geni 0815]

Weewx v 4.1.1
nothing has happened since loop-data 1.3.5 was installed


what went wrong, how can I correct this?

wee_extension --list

> 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.
>
>
or wee_debug --info

> pi@Wetter-Raspi:~ $ wee_debug --info
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_debug", line 435, in 
> main()
>   File "/usr/share/weewx/wee_debug", line 118, in main
> config_path, config_dict = weecfg.read_config(options.config_path, 
> 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.
>
>

-- 
You received this message because you are subscribed 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/fd8cd91a-dc9c-412d-9cc5-4c5126f113f2o%40googlegroups.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
>  
> <https://groups.google.com/d/msgid/weewx-user/6fe8b84f-8c69-4293-b848-b5c8f87034aao%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/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
>  
> <https://groups.google.com/d/msgid/weewx-user/6fe8b84f-8c69-4293-b848-b5c8f87034aao%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/weewx-user/8180ac18-cc02-47b7-bdc0-0c40df0b46c1o%40googlegroups.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:
>>>
>>> 
>>>
>

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:
>>
>>

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:
>>>>>
>

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:
>>>>>
>>>>> You

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 t

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.
>>>>>

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.  Renam

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.
>>>
>>>

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?

[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 
>>

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:
>
>

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-R

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:

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 fi

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
  
 

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

The problem was that the user did not have enough rights. Furthermore, the 
import of the database did not work with phpmyAdmin because the database 
was too large, it worked with putty directly on the Synology with mysql.
Now this is as requested, thanks for the help.

Am Sonntag, 28. Juni 2020 19:13:38 UTC+2 schrieb Pat:
>
> This error says you have a bad username for your database. Nothing to do 
> with the skin. Check your database settings in weewx.conf.
>
> On Sunday, June 28, 2020 at 12:02:47 PM UTC-4, Geni 0815 wrote:
>>
>> @pat:
>> @Manfred:
>> This results in my attempt!
>>
>> pi@Wetter-Raspi:~ $ sudo wee_database /etc/weewx/weewx.conf --reconfigure
>>> Using configuration file /etc/weewx/weewx.conf
>>> Using database binding 'wx_binding', which is bound to database 
>>> 'archive_mysql'
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/weedb/mysql.py", line 52, in guarded_fn
>>> return fn(*args, **kwargs)
>>>   File "/usr/share/weewx/weedb/mysql.py", line 262, in execute
>>> self.cursor.execute(mysql_string, tuple(sql_tuple))
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 250, in 
>>> execute
>>> self.errorhandler(self, exc, value)
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 50, 
>>> in defaulterrorhandler
>>> raise errorvalue
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 247, in 
>>> execute
>>> res = self._query(query)
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 411, in 
>>> _query
>>> rowcount = self._do_query(q)
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 374, in 
>>> _do_query
>>> db.query(q)
>>>   File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 
>>> 292, in query
>>> _mysql.connection.query(self, query)
>>> _mysql_exceptions.OperationalError: (1044, "Access denied for user 
>>> 'raspberry'@'%' to database 'weewx_new'")
>>>
>>> During handling of the above exception, another exception occurred:
>>>
>>> Traceback (most recent call last):
>>>   File "/usr/share/weewx/wee_database", line 974, in 
>>> main()
>>>   File "/usr/share/weewx/wee_database", line 145, in main
>>> reconfigMainDatabase(config_dict, db_binding)
>>>   File "/usr/share/weewx/wee_database", line 312, in reconfigMainDatabase
>>> weedb.create(new_database_dict)
>>>   File "/usr/share/weewx/weedb/__init__.py", line 80, in create
>>> return driver_mod.create(**db_dict)
>>>   File "/usr/share/weewx/weedb/mysql.py", line 87, in create
>>> cursor.execute("CREATE DATABASE %s" % (database_name,))
>>>   File "/usr/share/weewx/weedb/mysql.py", line 61, in guarded_fn
>>> raise klass(e)
>>> weedb.PermissionError: (1044, "Access denied for user 'raspberry'@'%' to 
>>> database 'weewx_new'")
>>> pi@Wetter-Raspi:~ $
>>>
>>>
>> Am Freitag, 26. Juni 2020 11:20:48 UTC+2 schrieb Manfred Maier:
>>>
>>> Sorry. Hatte ich vergessen.
>>>
>>> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 11:13:44 UTC+2:
>>>
>>>> Kannst  du deine extensions.py bitte hier reinstellen?
>>>>
>>>>
>>>> Manfred Maier schrieb am Freitag, 26. Juni 2020 um 10:41:53 UTC+2:
>>>>
>>>>> Ich habe meine Datenbank inzwischen schon zweimal erweitert. Einmal 
>>>>> nach ca. drei Wochen (um appTemp und maxSolarRad in der Datenbank zu 
>>>>> haben) 
>>>>> und dann nochmal letzte Woche, um endlich auch die Anzahl der 
>>>>> Sonnenstunden 
>>>>> schön darstellen zu können.
>>>>>
>>>>> Beide Male hat es absolut ohne Probleme funktioniert. 
>>>>> Schau einfach nur, dass Du ein Backup der Datenbank hast, sollte 
>>>>> wirklich etwas schief laufen.
>>>>>
>>>>> Mit Mariadb10 habe ich leider keinerlei Erfahrung. 
>>>>> Bei meiner Installation (mit SQLite) wird einfach nur die existierende 
>>>>> DB erweitert.
>>>>>
>>>>> Und bei der Installation der Skin ist es einfach nicht sinnvoll, an 
>>&

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

@pat:
@Manfred:
This results in my attempt!

pi@Wetter-Raspi:~ $ sudo wee_database /etc/weewx/weewx.conf --reconfigure
> Using configuration file /etc/weewx/weewx.conf
> Using database binding 'wx_binding', which is bound to database 
> 'archive_mysql'
> Traceback (most recent call last):
>   File "/usr/share/weewx/weedb/mysql.py", line 52, in guarded_fn
> return fn(*args, **kwargs)
>   File "/usr/share/weewx/weedb/mysql.py", line 262, in execute
> self.cursor.execute(mysql_string, tuple(sql_tuple))
>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 250, in 
> execute
> self.errorhandler(self, exc, value)
>   File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 50, 
> in defaulterrorhandler
> raise errorvalue
>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 247, in 
> execute
> res = self._query(query)
>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 411, in 
> _query
> rowcount = self._do_query(q)
>   File "/usr/lib/python3/dist-packages/MySQLdb/cursors.py", line 374, in 
> _do_query
> db.query(q)
>   File "/usr/lib/python3/dist-packages/MySQLdb/connections.py", line 292, 
> in query
> _mysql.connection.query(self, query)
> _mysql_exceptions.OperationalError: (1044, "Access denied for user 
> 'raspberry'@'%' to database 'weewx_new'")
>
> During handling of the above exception, another exception occurred:
>
> Traceback (most recent call last):
>   File "/usr/share/weewx/wee_database", line 974, in 
> main()
>   File "/usr/share/weewx/wee_database", line 145, in main
> reconfigMainDatabase(config_dict, db_binding)
>   File "/usr/share/weewx/wee_database", line 312, in reconfigMainDatabase
> weedb.create(new_database_dict)
>   File "/usr/share/weewx/weedb/__init__.py", line 80, in create
> return driver_mod.create(**db_dict)
>   File "/usr/share/weewx/weedb/mysql.py", line 87, in create
> cursor.execute("CREATE DATABASE %s" % (database_name,))
>   File "/usr/share/weewx/weedb/mysql.py", line 61, in guarded_fn
> raise klass(e)
> weedb.PermissionError: (1044, "Access denied for user 'raspberry'@'%' to 
> database 'weewx_new'")
> pi@Wetter-Raspi:~ $
>
>
Am Freitag, 26. Juni 2020 11:20:48 UTC+2 schrieb Manfred Maier:
>
> Sorry. Hatte ich vergessen.
>
> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 11:13:44 UTC+2:
>
>> Kannst  du deine extensions.py bitte hier reinstellen?
>>
>>
>> Manfred Maier schrieb am Freitag, 26. Juni 2020 um 10:41:53 UTC+2:
>>
>>> Ich habe meine Datenbank inzwischen schon zweimal erweitert. Einmal nach 
>>> ca. drei Wochen (um appTemp und maxSolarRad in der Datenbank zu haben) und 
>>> dann nochmal letzte Woche, um endlich auch die Anzahl der Sonnenstunden 
>>> schön darstellen zu können.
>>>
>>> Beide Male hat es absolut ohne Probleme funktioniert. 
>>> Schau einfach nur, dass Du ein Backup der Datenbank hast, sollte 
>>> wirklich etwas schief laufen.
>>>
>>> Mit Mariadb10 habe ich leider keinerlei Erfahrung. 
>>> Bei meiner Installation (mit SQLite) wird einfach nur die existierende 
>>> DB erweitert.
>>>
>>> Und bei der Installation der Skin ist es einfach nicht sinnvoll, an der 
>>> Datenbank rumzuspielen. 
>>>
>>> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 10:27:06 UTC+2:
>>>
 @Manfred: Hast du dies schon mal gemacht? Wenn ja ohne Probleme?
 Bleibt dies eine einmalige Sache oder wird dies bei jedem Update von 
 weewx oder Belchertown wieder fällig?
 Wie muss dann die extensions.py aussehen?
 Ich verwende eine externe Mariadb10, wird nun eine neue DB gemacht oder 
 die bestehende modifiziert?
 Dies funktioniert auf meinem Raspberry ja nicht?
 Warum wird dies nicht von der Belchertown installation gemacht?

 Bin da für jede Hilfe dankbar.

 Manfred Maier schrieb am Freitag, 26. Juni 2020 um 07:59:42 UTC+2:

> Good morning!
> You can use these instructions to add appTemp to your database:
>
> https://github.com/poblabs/weewx-belchertown/wiki/Adding-a-new-observation-type-to-the-WeeWX-database
>
> Just make sure you really have a backup of your database stored.
>
> geni08...@gmail.com schrieb am Freitag, 26. Juni 2020 um 07:43:08 
> UTC+2:
>
>> There are errors, a test with $current.appTemp and once with appTemp.
>> The appTemp field is not in the database, how can I modify my 
>> database?
>>
>>
>> Pat schrieb am Donnerstag, 25. Juni 2020 um 21:32:55 UTC+2:
>>
>>> Good question. If appTemp doesn't exist in the database, then I 
>>> would have thought the entry would be empty or given an error in the 
>>> syslog. Any errors?
>>>
>>>
>>> On Thursday, June 25, 2020 at 1:36:54 PM UTC-4, Manfred Maier wrote:

 Ok. I've just seen that appTemp is not part of the standard 
 installation of weewx. I've added it later to the database.

 @Pat: In your index.html.tmpl it loo

[weewx-user] Re: Belchertown: current weather picture is missing.

[Geni 0815]

@pat: Will the update also be done with "wee_extension --install 
weewx-belchertown-development.zip"? 
Above or first a "wee_extension --uninstall 
weewx-belchertown-release-1.1.tar.gz"?

Am Samstag, 27. Juni 2020 19:23:12 UTC+2 schrieb Pat:
>
> Please read the skin's README. Almost all of this is covered there.  
> 
>
> On Saturday, June 27, 2020 at 10:09:19 AM UTC-4, geni08...@gmail.com 
> wrote:
>>
>> how is Belchertown updated, what do you have to be careful about between 
>> release and beta versions? 
>>
>> Pat schrieb am Freitag, 26. Juni 2020 um 18:32:22 UTC+2:
>>
>>> Yes you need to use DarkSky or Aeris weather (with the 1.2 beta skin)
>>>
>>>
>>> On Friday, June 26, 2020 at 11:09:46 AM UTC-4, geni08...@gmail.com 
>>> wrote:

 I have to configure or install so that this info picture is displayed? 
 [image: 
 belch07.jpg]What do 

 It looks like this to me
 [image: belch08.jpg]

>>>

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

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

if appTemp instead of windchill, graphics no longer work

Am Donnerstag, 25. Juni 2020 17:46:56 UTC+2 schrieb Manfred Maier:
>
> appTemp is best translated with "Gefühlte Temperatur".
>
> I would have to look it up in the weewx code, but I think it's calculated 
> based on temperature, humidity and wind.
> appTemp can be higher or lower than the temperature.
>
> Windchill is normally (always?) lower than the temperature. It's therefore 
> primarily used in winter. At least in the German news I only hear about it 
> in winter.
>
> Heat Index is the opposite. It's normally (always?) higher than the 
> temperature. It useful in the summer.
>
> Other people might want to add or correct me here!
>
> As mentioned: appTemp get's closest to what we refer to as "Gefühlte 
> Temperature" in Germany (and hopefully also in Switzerland).
> Have you tried to put appTemp in your chart? Does the value correspond to 
> the other value on your page?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:34:22 
> UTC+2:
>
>> what is appTemp?
>> windchill corresponds to 'feels like'?
>>
>>
>> Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>>>
>>> Try to change it to [[[appTemp]]]. It then should correspond to the 
>>> figure at the top.
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
>>> UTC+2:
>>>
 in graphs.inc is  [[[windchill]]]


 Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>
> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
> "appTemp"?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
> UTC+2:
>
>> MQTT ist not activ.
>>
>>
>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>
>>> Hi Geni,
>>> do you have MQTT switched on?
>>>
>>> If so, the station observations (top area) display the live data. 
>>> The charts display the temperature of the last archive loop (= couple 
>>> of 
>>> minutes old).
>>>
>>> Manfred
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 
>>> 15:42:15 UTC+2:
>>>
 Why is there a different temperature displayed?

>>>

-- 
You received this message because you are subscribed 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/2df4e6f4-95fe-4849-b74c-f09d308808f0o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

what is appTemp?
windchill corresponds to 'feels like'?


Am Donnerstag, 25. Juni 2020 17:18:38 UTC+2 schrieb Manfred Maier:
>
> Try to change it to [[[appTemp]]]. It then should correspond to the figure 
> at the top.
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 17:16:32 
> UTC+2:
>
>> in graphs.inc is  [[[windchill]]]
>>
>>
>> Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>>>
>>> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
>>> "appTemp"?
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
>>> UTC+2:
>>>
 MQTT ist not activ.


 Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>
> Hi Geni,
> do you have MQTT switched on?
>
> If so, the station observations (top area) display the live data. The 
> charts display the temperature of the last archive loop (= couple of 
> minutes old).
>
> Manfred
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
> UTC+2:
>
>> Why is there a different temperature displayed?
>>
>

-- 
You received this message because you are subscribed 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/399fe36b-7987-4d1c-b7ed-8ace3fb07c31o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

in graphs.inc is  [[[windchill]]]

Am Donnerstag, 25. Juni 2020 16:51:00 UTC+2 schrieb Manfred Maier:
>
> Next try ... the "Gefühlte Temp" in your graphs.conf is displaying 
> "appTemp"?
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 16:43:53 
> UTC+2:
>
>> MQTT ist not activ.
>>
>>
>> Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>>>
>>> Hi Geni,
>>> do you have MQTT switched on?
>>>
>>> If so, the station observations (top area) display the live data. The 
>>> charts display the temperature of the last archive loop (= couple of 
>>> minutes old).
>>>
>>> Manfred
>>>
>>> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
>>> UTC+2:
>>>
 Why is there a different temperature displayed?

>>>

-- 
You received this message because you are subscribed 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/0d62de32-015f-4014-8067-70b1b739b351o%40googlegroups.com.

[weewx-user] Re: Belchertown Difference for the same temperature type

[Geni 0815]

MQTT ist not activ.

Am Donnerstag, 25. Juni 2020 15:51:16 UTC+2 schrieb Manfred Maier:
>
> Hi Geni,
> do you have MQTT switched on?
>
> If so, the station observations (top area) display the live data. The 
> charts display the temperature of the last archive loop (= couple of 
> minutes old).
>
> Manfred
>
> geni08...@gmail.com schrieb am Donnerstag, 25. Juni 2020 um 15:42:15 
> UTC+2:
>
>> Why is there a different temperature displayed?
>>
>

-- 
You received this message because you are subscribed 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/f9382978-ad3b-4b79-b06a-d749926ee6d4o%40googlegroups.com.

[weewx-user] Belchertown Difference for the same temperature type

[Geni 0815]

Why is there a different temperature displayed?

-- 
You received this message because you are subscribed 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/d13ff833-c555-42ec-af4a-06907cef5f00o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Ich habe jetzt einen eigenen Iframe code gemacht damit gibt es keine 
Fehlermeldungen mehr!
Vielen Dank für die Hilfen, werden nun vorerst mal ein wenig mit den 
verschiedenen Möglichkeiten für Diagramme spielen.
Gruss Geni

Am Samstag, 20. Juni 2020 20:54:59 UTC+2 schrieb Manfred Maier:
>
> Am Widget habe ich nichts geändert.
>
> In der .htaccess Datei auf dem Webserver habe ich folgenden Code eingefügt:
> # Extra Security Headers
> 
> Header set Feature-Policy "geolocation 'none'"
> 
>
> Bei manchen Browsers (leider nicht bei allen) unterdrückt dieser Code die 
> Standort-Abfrage der Windy-Widgets.
>
> Ich kann mir aber nicht vorstellen, dass dies der Grund dafür ist, dass 
> bei Dir eine Fehlermeldung kommt und bei mir nicht.
> Bekommst Du die gleiche Fehlermeldung, wenn Du auf andere Seiten mit dem 
> Belchertown-Skin gehst?
>
> Hast Du schon mal im Forum von Windy nachgelesen, ob das Problem bekannt 
> ist?
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 17:04:32 UTC+2:
>
>> Ich verwende Firefox 77.0.1 (64-Bit), die Fehlermeldung kommt aber nur 
>> von meiner Seite, bei Deiner gibt es keine!
>> Was ist bei Windy bei dir anders?
>>
>> Am Samstag, 20. Juni 2020 13:08:25 UTC+2 schrieb Manfred Maier:
>>>
>>> Das Widget von Meteoblue ist leider nach unten hin nicht responsive. 
>>> Bisher ist Meteoblue aber die beste und schönste Vorhersage, die ich 
>>> gefunden habe.
>>> Sowohl DarkSky als auch Aeris liegen hier bei mir von den Vorhersagen 
>>> her leider deutlich daneben.
>>>
>>> Die Fehlermeldung von Windy bekomme ich nicht. Welchen Browser (mit 
>>> Version) verwendest Du?
>>>  
>>>
>>> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 13:04:10 UTC+2:
>>>
 Auf dem Handy wird aber abgeschnitten!

 warum kommt die Fehlermeldung von Windy

 Am Samstag, 20. Juni 2020 11:29:05 UTC+2 schrieb Manfred Maier:
>
> Responsive ist es bei mir auch nur in Grenzen.
> Es gibt eine minimale Breite, ab der das Widget dann abgeschnitten 
> wird. Nur nach oben hin skaliert es schön.
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 10:21:01 
> UTC+2:
>
>> @Manfred
>> Der Eintrag gemäss deinen Angaben funktioniert aber nicht Responsiv, 
>> irgendwie bekommt das iframe die benutzte breite nicht mit.
>> Hast du eine Idee?
>>
>> Am Freitag, 19. Juni 2020 13:14:23 UTC+2 schrieb Manfred Maier:
>>>
>>> Ist bei mir in der index_hook_after_charts.inc drin.
>>>
>>>
>>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis 
>>> anlegen
>>> 2) den folgenden Code reinkopieren
>>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
>>> Code gibt's auf Meteoblue unter Website-Widgets).
>>>
>>> 
>>> 
>>> 
>>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed&nocurrent=1&noforecast=0&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&layout=image";
>>>  
>>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>>> sandbox="allow-same-origin allow-scripts allow-popups 
>>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>>> padding-left: 16px; padding-right: 16px">
>>> 
>>> 
>>>
>>>

-- 
You received this message because you are subscribed 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/1a9f933a-052d-4d9e-9320-bdeb976bb35do%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Ich verwende Firefox 77.0.1 (64-Bit), die Fehlermeldung kommt aber nur von 
meiner Seite, bei Deiner gibt es keine!
Was ist bei Windy bei dir anders?

Am Samstag, 20. Juni 2020 13:08:25 UTC+2 schrieb Manfred Maier:
>
> Das Widget von Meteoblue ist leider nach unten hin nicht responsive. 
> Bisher ist Meteoblue aber die beste und schönste Vorhersage, die ich 
> gefunden habe.
> Sowohl DarkSky als auch Aeris liegen hier bei mir von den Vorhersagen her 
> leider deutlich daneben.
>
> Die Fehlermeldung von Windy bekomme ich nicht. Welchen Browser (mit 
> Version) verwendest Du?
>  
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 13:04:10 UTC+2:
>
>> Auf dem Handy wird aber abgeschnitten!
>>
>> warum kommt die Fehlermeldung von Windy
>>
>> Am Samstag, 20. Juni 2020 11:29:05 UTC+2 schrieb Manfred Maier:
>>>
>>> Responsive ist es bei mir auch nur in Grenzen.
>>> Es gibt eine minimale Breite, ab der das Widget dann abgeschnitten wird. 
>>> Nur nach oben hin skaliert es schön.
>>>
>>> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 10:21:01 UTC+2:
>>>
 @Manfred
 Der Eintrag gemäss deinen Angaben funktioniert aber nicht Responsiv, 
 irgendwie bekommt das iframe die benutzte breite nicht mit.
 Hast du eine Idee?

 Am Freitag, 19. Juni 2020 13:14:23 UTC+2 schrieb Manfred Maier:
>
> Ist bei mir in der index_hook_after_charts.inc drin.
>
>
> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis 
> anlegen
> 2) den folgenden Code reinkopieren
> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
> Code gibt's auf Meteoblue unter Website-Widgets).
>
> 
> 
> 
> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed&nocurrent=1&noforecast=0&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&layout=image";
>  
>  frameborder="0" scrolling="YES" allowtransparency="true" 
> sandbox="allow-same-origin allow-scripts allow-popups 
> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
> padding-left: 16px; padding-right: 16px">
> 
> 
>
>

-- 
You received this message because you are subscribed 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/d71d68da-2937-4243-be51-6d38cba4558bo%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Auf dem Handy wird aber abgeschnitten!

warum kommt die Fehlermeldung von Windy

Am Samstag, 20. Juni 2020 11:29:05 UTC+2 schrieb Manfred Maier:
>
> Responsive ist es bei mir auch nur in Grenzen.
> Es gibt eine minimale Breite, ab der das Widget dann abgeschnitten wird. 
> Nur nach oben hin skaliert es schön.
>
> geni08...@gmail.com schrieb am Samstag, 20. Juni 2020 um 10:21:01 UTC+2:
>
>> @Manfred
>> Der Eintrag gemäss deinen Angaben funktioniert aber nicht Responsiv, 
>> irgendwie bekommt das iframe die benutzte breite nicht mit.
>> Hast du eine Idee?
>>
>> Am Freitag, 19. Juni 2020 13:14:23 UTC+2 schrieb Manfred Maier:
>>>
>>> Ist bei mir in der index_hook_after_charts.inc drin.
>>>
>>>
>>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
>>> 2) den folgenden Code reinkopieren
>>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
>>> Code gibt's auf Meteoblue unter Website-Widgets).
>>>
>>> 
>>> 
>>> 
>>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed&nocurrent=1&noforecast=0&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&layout=image";
>>>  
>>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>>> sandbox="allow-same-origin allow-scripts allow-popups 
>>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>>> padding-left: 16px; padding-right: 16px">
>>> 
>>> 
>>>
>>>

-- 
You received this message because you are subscribed 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/9d46f376-fd3f-421f-8d5a-92efcfe278c6o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

@Manfred
Der Eintrag gemäss deinen Angaben funktioniert aber nicht Responsiv, 
irgendwie bekommt das iframe die benutzte breite nicht mit.
Hast du eine Idee?

Am Freitag, 19. Juni 2020 13:14:23 UTC+2 schrieb Manfred Maier:
>
> Ist bei mir in der index_hook_after_charts.inc drin.
>
>
> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
> 2) den folgenden Code reinkopieren
> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den Code 
> gibt's auf Meteoblue unter Website-Widgets).
>
> 
> 
> 
> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed&nocurrent=1&noforecast=0&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&layout=image";
>  
>  frameborder="0" scrolling="YES" allowtransparency="true" 
> sandbox="allow-same-origin allow-scripts allow-popups 
> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
> padding-left: 16px; padding-right: 16px">
> 
> 
>
>

-- 
You received this message because you are subscribed 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/5d0d77db-4464-4102-91aa-432da7c53d12o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

I changed the 2 lines and now it also works with de_CH local setting.
I also adjusted the gapSize because my interval is 10min.
So far it goes now, but I would have the time window of the last 24 hours 
in the day view and not a start at midnight.
Could I get the example of the rain?

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
You received this message because you are subscribed 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/2df82e90-759d-4ca0-b4fb-4f86df89abedo%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Gratuliere, der Schuss ging ins schwarze!
Im skin.conf habe ich auto
Der Raspberry lief natürlich für mich lokal auf de_CH.UTF-8
ich habe diesen nun auf de_DE.UTF-8 geändert und schon hatte ich das 
Zuletzt aktualisiert und Charts.
Die Charts sind leider teilweise leer?


Am Freitag, 19. Juni 2020 15:25:44 UTC+2 schrieb Manfred Maier:
>
> Das ist jetzt ein Schuss ins Blaue (vielleicht treffe ich aber):
> Welche "belchertown_locale" hast Du angegeben? Bzw. in welcher 
> "Locale"Einstellung läuft Dein Rechner?
>
> In der besagten Belchertown.js auf Deinem Webserver steht in Zeile 507:
>thousandsSep: '''
>
> Es sieht so aus, als würde ein Hochkomma als Tausender-Punkt verwendet. 
> Der Browser fällt hier wohl drüber (3 Hochkommas nacheinander).
>
> Der Tausender-Seperator ist eigentlich automatisch von der Locale 
> gesteuert.
>  
>
> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 15:01:48 UTC+2:
>
>> Ich hab mir Deine Website jetzt mal angesehen.
>> Es sieht so aus, als hättest Du ein Problem mit Deiner Belchertown.js.tmpl
>>
>> Hast Du da mal etwas geändert?
>>
>> Wenn ich die Fehlermeldung richtig interpretiere, gibt es ein Problem bei 
>> Zeile 506. Das EOF bedeutet meiner Meinung nach, dass das File hier endet?
>> Wie viele Zeilen hat Deine Belchertown.js.tmpl?
>>
>>
>>
>> Manfred Maier schrieb am Freitag, 19. Juni 2020 um 13:14:23 UTC+2:
>>
>>> Ist bei mir in der index_hook_after_charts.inc drin.
>>>
>>>
>>> 1) Datei (index_hook_after_charts.inc) im Belchertown-Verzeichnis anlegen
>>> 2) den folgenden Code reinkopieren
>>> 3) In der weewx.conf (Belchertown -Section) einschalten, dass der 
>>> Index-Hook alle 300 Sekunden (oder auch weniger oft) neu geladen wird.
>>> 4) Noch den iframe aus meinem Code für Deinen Standort anpassen (den 
>>> Code gibt's auf Meteoblue unter Website-Widgets).
>>>
>>> 
>>> 
>>> 
>>> https://www.meteoblue.com/de/wetter/widget/three/zorneding_deutschland_2803884?geoloc=fixed&nocurrent=1&noforecast=0&days=7&tempunit=CELSIUS&windunit=KILOMETER_PER_HOUR&layout=image";
>>>  
>>>  frameborder="0" scrolling="YES" allowtransparency="true" 
>>> sandbox="allow-same-origin allow-scripts allow-popups 
>>> allow-popups-to-escape-sandbox" style="width: 100%; height: 525px; 
>>> padding-left: 16px; padding-right: 16px">
>>> 
>>> 
>>>
>>>

-- 
You received this message because you are subscribed 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/810af773-6f20-4783-816d-184f49f447c9o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

@Manfred, wie und wo hast die meteoblue vorhersage eingebaut?

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
You received this message because you are subscribed 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/0cb4795c-4c60-47b2-a2b2-c3e534208970o%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Die charts liefen noch nie.
Der Eintrag highcharts_enabled = 1 ist nur in der skin.conf.
Es gibt keine Fehlermeldungen, ich habe das belchertown_debug = 1 gesetzt, 
wo sieht man diese Meldungen?

Am Freitag, 19. Juni 2020 11:49:03 UTC+2 schrieb Manfred Maier:
>
> Liefen die Charts bei Dir schon mal?
>
> Der generelle Switch für die Highcharts ist in der skin.conf (bzw. 
> weewx.conf):
> # Highcharts settings
> highcharts_enabled = 1
>
> Kommen auf Deiner Website irgendwelche Fehlermeldungen? 
>
> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 11:42:06 UTC+2:
>
>> Es ist die Original graphs.conf.example, da sollte doch nichts falsch 
>> sein?
>>
>>
>> Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>>>
>>> And if still no charts are produced, you probably have an error in 
>>> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
>>> at all are produced.
>>>
>>> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>>>

 What do I have to set where and how to get diagrams

 Regards
 Geni

>>>

-- 
You received this message because you are subscribed 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/c266b139-87ee-4639-9064-ece981b6136co%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

und warum bekomme ich keine Letzte Update Information

Am Freitag, 19. Juni 2020 10:48:16 UTC+2 schrieb Geni 0815:
>
>
> What do I have to set where and how to get diagrams
>
> Regards
> Geni
>

-- 
You received this message because you are subscribed 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/fa242998-aa80-4150-9a0d-880516b4467co%40googlegroups.com.

[weewx-user] Re: Belchertown no charts

[Geni 0815]

Es ist die Original graphs.conf.example, da sollte doch nichts falsch sein?


Am Freitag, 19. Juni 2020 10:59:49 UTC+2 schrieb Manfred Maier:
>
> And if still no charts are produced, you probably have an error in 
> somewhere in your graphs.conf. If one chart in there is invalid, no charts 
> at all are produced.
>
> geni08...@gmail.com schrieb am Freitag, 19. Juni 2020 um 10:48:16 UTC+2:
>
>>
>> What do I have to set where and how to get diagrams
>>
>> Regards
>> Geni
>>
>

-- 
You received this message because you are subscribed 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/90d9440e-1916-47f5-a97b-3dcd6e80b66co%40googlegroups.com.

[weewx-user] Belchertown no charts

[Geni 0815]

What do I have to set where and how to get diagrams

Regards
Geni

-- 
You received this message because you are subscribed 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/6ae74ae1-c020-4d8c-8f68-8ed82afeda0co%40googlegroups.com.

[weewx-user] Re: Belchertown github_version.json. Reason: [Errno 2]

[Geni 0815]

Hello Pat
thank you so no more errors.
Regards
Geni

Am Mittwoch, 17. Juni 2020 19:26:52 UTC+2 schrieb Pat:
>
> I'll be removing this feature in skin 1.2. It's not working as I had 
> planned and I've invested too much time trying to resolve it. The reward 
> isn't there any longer. 
>
> In your skin.conf, set check_for_updates = 0 and restart weewx and this 
> will go away
>
> On Wednesday, June 17, 2020 at 1:19:54 PM UTC-4, Geni 0815 wrote:
>>
>> I have reinstalled the skin Belchertown
>> I have weewx 4.1.1 on a Raspberry 3+ with Buster lite.
>> Minimally no Darksky and no MQTT.
>> Only the weather data is generated with the Windy picture but no graphics. 
>> Many 
>> lines are displayed in the console with the following:
>>
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] INFO user.belchertown: version 
>> 1.1
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>> Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Error downloading GitHub Version data. The error is: HTTP Error 
>> 403: rate limit exceeded
>> Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
>> Checker: Unable to open 
>> /home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
>> Datei oder Verzeichnis nicht gefunden: 
>> '/home/pi/NAS/www/belchertown/json/github_version.json'
>>
>>
>> What's missing?
>>
>> Regards 
>> Geni
>>
>

-- 
You received this message because you are subscribed 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/84b8a353-7341-4a5a-a837-a7ce1e75e276o%40googlegroups.com.

[weewx-user] Re: Belchertown - German Translation

[Geni 0815]

Hallo Manfred, ich finde hier nichts übersetztes.
Gruss Geni

Am Donnerstag, 11. Juni 2020 11:19:14 UTC+2 schrieb Manfred Maier:
>
> Here you go!
>
> Attached please find my skin.conf (with - I guess - no relevant 
> information in it), plus the relevant part of my weewx.conf that holds all 
> the German translations. It's important to put the translations into the 
> weewx.conf. Otherwise the translations might get lost when updating the 
> skin.
>
> Would be great if you could post the URL of your site. I'm always looking 
> for ideas of how to improve my site ;)
>
> Best regards!
> Manfred 
>
> Am Donnerstag, 11. Juni 2020 11:02:22 UTC+2 schrieb Manfred Maier:
>>
>> Sure. 
>> I'll upload my translations for you. Give me 15 mins.
>>
>> Manfred
>>
>> PS: On my site you can see my German translation in action (
>> wetter-zorneding.de) 
>>
>> Am Donnerstag, 11. Juni 2020 10:53:22 UTC+2 schrieb NanoG5Kite:
>>>
>>> Hello everybody
>>>
>>> Would someone support me with his German skin-conf...?
>>>
>>> Regards,
>>>
>>> Matthias
>>>
>>

-- 
You received this message because you are subscribed 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/64bb03ff-0bf4-47ea-b9b1-be478580b43do%40googlegroups.com.

[weewx-user] Belchertown github_version.json. Reason: [Errno 2]

[Geni 0815]

I have reinstalled the skin Belchertown
I have weewx 4.1.1 on a Raspberry 3+ with Buster lite.
Minimally no Darksky and no MQTT.
Only the weather data is generated with the Windy picture but no graphics. Many 
lines are displayed in the console with the following:

Jun 17 18:30:32 Wetter-Raspi weewx[22848] INFO user.belchertown: version 1.1
Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:32 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'
Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:33 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'
Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:35 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'
Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:36 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'
Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:37 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'
Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Error downloading GitHub Version data. The error is: HTTP Error 
403: rate limit exceeded
Jun 17 18:30:38 Wetter-Raspi weewx[22848] ERROR user.belchertown: Update 
Checker: Unable to open 
/home/pi/NAS/www/belchertown/json/github_version.json. Reason: [Errno 2] 
Datei oder Verzeichnis nicht gefunden: 
'/home/pi/NAS/www/belchertown/json/github_version.json'


What's missing?

Regards 
Geni

-- 
You received this message because you are subscribed 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/350932cf-9818-43c4-bf6a-87b621880e34o%40googlegroups.com.