Re: [weewx-user] weewx and Wunderground - Recent Data Issue

[Andrew Milner]

I think, but cannot prove it, that WU may have changed their algorithms 
recently.  I run wunderfixer at 12 noon and 12 midnight.  Wunderfixer used 
to usuallu upload some missing records each time, but now it is uploading 
100+ missing records each time.  Something at their end has changed, and I 
think they are trying to move towards storing data at fewer intervals.  
Something has changed at their end.



On Tuesday, 13 November 2018 00:34:42 UTC+2, Dave McCreath wrote:
>
> Thomas
>
> Many thanks for getting back to me, no surprize there then!
>
> I'll leave the system on rapid-fire for another couple of weeks and try 
> again, but I do like the way weewx aggregates data over a five minute 
> period before uploading unlike rapid fire.
>
> Kind regards
>
> Dave
>
> On Monday, 12 November 2018 21:54:12 UTC, Thomas Keffer wrote:
>>
>> Dave, unfortunately, the WU is full of many, many bugs. Looks like you 
>> stumbled across another one. There's not much we can do about them from our 
>> end.
>>
>> -tk
>>
>> On Mon, Nov 12, 2018 at 9:15 AM Dave McCreath  
>> wrote:
>>
>>> Eqpt:
>>>
>>> Vantage Vue on USB with datalogger.
>>> Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
>>> weewx v.3.8.2.
>>> Wunderfixer running as a cron task every 60 minutes (at the moment).
>>> WunderGround ID ICAMBSLE2 (which has been running well for over three 
>>> years).
>>>
>>> Issue:  
>>>
>>> weewx uploads data packets to Wundergound every five minutes but less 
>>> than half appear to get through first time.  Those that do get through 
>>> first time do not appear on the Wundergound GUI until 6/7 minutes after 
>>> being uploaded.  Previously, they would appear within 2 minutes of 
>>> uploading.  However, with Wunderfixer (currently) running every hour, data 
>>> records are eventually getting through to the server after about two and a 
>>> half hours (sometimes three).  Local data is being saved to my personal 
>>> weewx website without any issues. 
>>>
>>> Background:  
>>>
>>> The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after 
>>> the clocks changed!).  I initially thought it might be a timing issue post 
>>> the clocks changing, but checking the records for Sunday 28 Oct, all was 
>>> fine.  Checked the epoch time on the RPi and Davis console, both OK.  
>>> Strangely, If I turn on rapid-fire (via .conf), all works as it should do, 
>>> no issues whatsoever.
>>>
>>> Log Extract: (No issues as far as I can see)
>>>
>>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>>> 15:55:00 GMT (1542038100) to database 'weewx.sdb'
>>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>>> 15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
>>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for 
>>> latest time in the database.
>>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
>>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report 
>>> StandardReport
>>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console 
>>> successful
>>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration 
>>> file /etc/weewx/skins/Standard/skin.conf for report StandardReport
>>> Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list 
>>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
>>> Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
>>> Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published 
>>> record 2018-11-12 15:55:00 GMT (1542038100)
>>> Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files 
>>> for report StandardReport in 1.46 seconds
>>> Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
>>> Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images 
>>> for StandardReport in 0.90 seconds
>>> Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to 
>>> /var/www/html/weewx
>>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
>>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration 
>>> file /etc/weewx/skins/Ftp/skin.conf for report FTP
>>> Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not 
>>> requested. Skipped.
>>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
>>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration 
>>> file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
>>> Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not 
>>> requested. Skipped.
>>> Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
>>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx 
>>> configuration file /etc/weewx/weewx.conf.
>>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: 

Re: [weewx-user] Multiple errors in weewx 3.8.2

[gjr80]

Tom is the author/developer, the rest of us just help out where/when we can.

I have  attached a version of tags.py with some extra logging to hopefully 
give us a clue why things are happening. What I would like you to do on 
your problem install is:

1. rename /usr/share/weewx/weewx/tags.py as tags_orig.py

$ sudo mv /usr/share/weewx/weewx/tags.py /usr/share/weewx/weewx/tags_orig.py

2. download/copy the attached tags.py to /usr/share/weewx/weewx

3. restart weeWX.

4. Post the log from weeWX startup through until the error occurs.

5. Start a MySQL/Mariadb shell and run the following commands:

> USE weewx;
> SELECT dateTime,max FROM archive_day_wind ORDER BY dateTime DESC LIMIT 32;

6. Post the output from the above commands.

To revert the tags.py changes just delete tags.py and rename tags_orig.py 
back to tags.py and restart weeWX.

Gary

On Tuesday, 13 November 2018 09:18:48 UTC+10, Jonis Maurin Ceará wrote:
>
> I'm not sure who is the mais author/developer, but I can give you access 
> to my station. It's in use right now, but is not imperative to keep online 
> 24/7, so you can access and check/test. The only thing is that I'm using my 
> old mysql databasebut. like I said before, I've made tests with clean 
> and new database (sqlite and mysql). If you like, you can test and 
> re-create those databases again..just don't delete my old mysql 
> database :)
>
>
> Em seg, 12 de nov de 2018 às 20:43, gjr80  > escreveu:
>
>> Tom, yes knew that was going on as soon as I saw the error message. Just 
>> having a trouble finding out why. Somewhere a timestamp must be missing a 
>> day boundary but I haven't yet worked out which. Particularly confusing 
>> when a clean database exhibits the same problem immediately. Also odd that 
>> week.html.tmpl throws the error but month.html.tmpl and year.html.tmpl do 
>> not which suggests week.wind is the culprit. Really want to see some of the 
>> timestamps being used to try and work out what is being used and why.
>>
>> Gary
>>
>> -- 
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "weewx-user" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/weewx-user/llOh8p8emYY/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> weewx-user+...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.
#
#Copyright (c) 2009-2015 Tom Keffer 
#
#See the file LICENSE.txt for your full rights.
#
"""Classes for implementing the weewx tag 'code' codes."""

import syslog

import weeutil.weeutil
from weeutil.weeutil import to_int
import weewx.units
from weewx.units import ValueTuple

#===
#Class TimeBinder
#===

class TimeBinder(object):
"""Binds to a specific time. Can be queried for time attributes, such as month.

When a time period is given as an attribute to it, such as obj.month,
the next item in the chain is returned, in this case an instance of
TimespanBinder, which binds things to a timespan.
"""

def __init__(self, db_lookup, report_time,
 formatter=weewx.units.Formatter(), converter=weewx.units.Converter(), **option_dict):
"""Initialize an instance of DatabaseBinder.

db_lookup: A function with call signature db_lookup(data_binding), which
returns a database manager and where data_binding is an optional binding
name. If not given, then a default binding will be used.

report_time: The time for which the report should be run.

formatter: An instance of weewx.units.Formatter() holding the formatting
information to be used. [Optional. If not given, the default
Formatter will be used.]

converter: An instance of weewx.units.Converter() holding the target unit
information to be used. [Optional. If not given, the default
Converter will be used.]

option_dict: Other options which can be used to customize calculations.
[Optional.]
"""
self.db_lookup= db_lookup
self.report_time  = report_time
self.formatter= formatter
self.converter= converter
self.option_dict  = option_dict

# What follows is the list of time period attributes:

def trend(self, time_delta=None, time_grace=None, data_binding=None):
"""Returns a TrendObj that is bound to the trend parameters."""
if time_delta is None:
time_delta = 

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Jonis Maurin Ceará]

I'm not sure who is the mais author/developer, but I can give you access to
my station. It's in use right now, but is not imperative to keep online
24/7, so you can access and check/test. The only thing is that I'm using my
old mysql databasebut. like I said before, I've made tests with clean
and new database (sqlite and mysql). If you like, you can test and
re-create those databases again..just don't delete my old mysql
database :)


Em seg, 12 de nov de 2018 às 20:43, gjr80  escreveu:

> Tom, yes knew that was going on as soon as I saw the error message. Just
> having a trouble finding out why. Somewhere a timestamp must be missing a
> day boundary but I haven't yet worked out which. Particularly confusing
> when a clean database exhibits the same problem immediately. Also odd that
> week.html.tmpl throws the error but month.html.tmpl and year.html.tmpl do
> not which suggests week.wind is the culprit. Really want to see some of the
> timestamps being used to try and work out what is being used and why.
>
> Gary
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/llOh8p8emYY/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Multiple errors in weewx 3.8.2

[gjr80]

Tom, yes knew that was going on as soon as I saw the error message. Just having 
a trouble finding out why. Somewhere a timestamp must be missing a day boundary 
but I haven't yet worked out which. Particularly confusing when a clean 
database exhibits the same problem immediately. Also odd that week.html.tmpl 
throws the error but month.html.tmpl and year.html.tmpl do not which suggests 
week.wind is the culprit. Really want to see some of the timestamps being used 
to try and work out what is being used and why.

Gary

-- 
You received this message because you are subscribed to the Google Groups 
"weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to weewx-user+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] weewx and Wunderground - Recent Data Issue

[Dave McCreath]

Thomas

Many thanks for getting back to me, no surprize there then!

I'll leave the system on rapid-fire for another couple of weeks and try 
again, but I do like the way weewx aggregates data over a five minute 
period before uploading unlike rapid fire.

Kind regards

Dave

On Monday, 12 November 2018 21:54:12 UTC, Thomas Keffer wrote:
>
> Dave, unfortunately, the WU is full of many, many bugs. Looks like you 
> stumbled across another one. There's not much we can do about them from our 
> end.
>
> -tk
>
> On Mon, Nov 12, 2018 at 9:15 AM Dave McCreath  > wrote:
>
>> Eqpt:
>>
>> Vantage Vue on USB with datalogger.
>> Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
>> weewx v.3.8.2.
>> Wunderfixer running as a cron task every 60 minutes (at the moment).
>> WunderGround ID ICAMBSLE2 (which has been running well for over three 
>> years).
>>
>> Issue:  
>>
>> weewx uploads data packets to Wundergound every five minutes but less 
>> than half appear to get through first time.  Those that do get through 
>> first time do not appear on the Wundergound GUI until 6/7 minutes after 
>> being uploaded.  Previously, they would appear within 2 minutes of 
>> uploading.  However, with Wunderfixer (currently) running every hour, data 
>> records are eventually getting through to the server after about two and a 
>> half hours (sometimes three).  Local data is being saved to my personal 
>> weewx website without any issues. 
>>
>> Background:  
>>
>> The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after 
>> the clocks changed!).  I initially thought it might be a timing issue post 
>> the clocks changing, but checking the records for Sunday 28 Oct, all was 
>> fine.  Checked the epoch time on the RPi and Davis console, both OK.  
>> Strangely, If I turn on rapid-fire (via .conf), all works as it should do, 
>> no issues whatsoever.
>>
>> Log Extract: (No issues as far as I can see)
>>
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>> 15:55:00 GMT (1542038100) to database 'weewx.sdb'
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
>> 15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for 
>> latest time in the database.
>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report 
>> StandardReport
>> Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console 
>> successful
>> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Standard/skin.conf for report StandardReport
>> Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list 
>> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
>> Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
>> Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published 
>> record 2018-11-12 15:55:00 GMT (1542038100)
>> Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files 
>> for report StandardReport in 1.46 seconds
>> Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
>> Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images 
>> for StandardReport in 0.90 seconds
>> Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to 
>> /var/www/html/weewx
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Ftp/skin.conf for report FTP
>> Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not 
>> requested. Skipped.
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
>> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
>> /etc/weewx/skins/Rsync/skin.conf for report RSYNC
>> Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not 
>> requested. Skipped.
>> Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx configuration 
>> file /etc/weewx/weewx.conf.
>> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using database binding 
>> 'wx_binding', which is bound to database 'archive_sqlite'
>> Nov 12 15:59:02 weewx weewx[9216]: wunderfixer: 25 Weather Underground 
>> records missing.
>> Nov 12 15:59:13 weewx weewx[9216]: wunderfixer: 25 out of 25 missing 
>> records published to 'ICAMBSLE2' for date 2018-11-12. Wunderfixer exiting.
>>
>> WunderGround Web Page:
>>
>> [image: WeeWx Issue.jpg]
>>  Anyone any ideas?
>>
>> Regards
>>
>> Dave
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group 

Re: [weewx-user] weewx and Wunderground - Recent Data Issue

[Thomas Keffer]

Dave, unfortunately, the WU is full of many, many bugs. Looks like you
stumbled across another one. There's not much we can do about them from our
end.

-tk

On Mon, Nov 12, 2018 at 9:15 AM Dave McCreath 
wrote:

> Eqpt:
>
> Vantage Vue on USB with datalogger.
> Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
> weewx v.3.8.2.
> Wunderfixer running as a cron task every 60 minutes (at the moment).
> WunderGround ID ICAMBSLE2 (which has been running well for over three
> years).
>
> Issue:
>
> weewx uploads data packets to Wundergound every five minutes but less than
> half appear to get through first time.  Those that do get through first
> time do not appear on the Wundergound GUI until 6/7 minutes after being
> uploaded.  Previously, they would appear within 2 minutes of uploading.
> However, with Wunderfixer (currently) running every hour, data records are
> eventually getting through to the server after about two and a half hours
> (sometimes three).  Local data is being saved to my personal weewx website
> without any issues.
>
> Background:
>
> The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after
> the clocks changed!).  I initially thought it might be a timing issue post
> the clocks changing, but checking the records for Sunday 28 Oct, all was
> fine.  Checked the epoch time on the RPi and Davis console, both OK.
> Strangely, If I turn on rapid-fire (via .conf), all works as it should do,
> no issues whatsoever.
>
> Log Extract: (No issues as far as I can see)
>
> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12
> 15:55:00 GMT (1542038100) to database 'weewx.sdb'
> Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12
> 15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for
> latest time in the database.
> Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report
> StandardReport
> Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console
> successful
> Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration file
> /etc/weewx/skins/Standard/skin.conf for report StandardReport
> Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list
> ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
> Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
> Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published
> record 2018-11-12 15:55:00 GMT (1542038100)
> Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files
> for report StandardReport in 1.46 seconds
> Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
> Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images for
> StandardReport in 0.90 seconds
> Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to
> /var/www/html/weewx
> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file
> /etc/weewx/skins/Ftp/skin.conf for report FTP
> Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not requested.
> Skipped.
> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
> Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file
> /etc/weewx/skins/Rsync/skin.conf for report RSYNC
> Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not
> requested. Skipped.
> Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx configuration
> file /etc/weewx/weewx.conf.
> Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using database binding
> 'wx_binding', which is bound to database 'archive_sqlite'
> Nov 12 15:59:02 weewx weewx[9216]: wunderfixer: 25 Weather Underground
> records missing.
> Nov 12 15:59:13 weewx weewx[9216]: wunderfixer: 25 out of 25 missing
> records published to 'ICAMBSLE2' for date 2018-11-12. Wunderfixer exiting.
>
> WunderGround Web Page:
>
> [image: WeeWx Issue.jpg]
>  Anyone any ideas?
>
> Regards
>
> Dave
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Thomas Keffer]

Gary: one thing I'm noticing is that the tag
DaySummaryManager.getAggregate() is using its superclass version,
Manager.getAggregate(), presumably because the boundaries of the query are
not falling on midnight.

A clue, perhaps...?

-tk

On Sun, Nov 11, 2018 at 3:03 PM gjr80  wrote:

> I have set up a Stretch VM using the same locale and timezone settings as
> you running a .deb weeWX install and I cannot reproduce the fault you are
> experiencing. This really brings me back to the your database. I will
> instrument one of the weeWX files with some extra logging so we can see
> exactly what is happening when the offending tag(s) is/are called. In the
> meantime can you confirm exactly what version of weeWX you are now running
> on the problem system (3.8.2 I am guessing) so that I can ensure I give you
> a compatible version of the file.
>
> Gary
>
> On Friday, 9 November 2018 20:27:44 UTC+10, Jonis Maurin Ceará wrote:
>>
>> Sure!
>> And one more info: this error (wind) happens on all skins.
>>
>> pi@SkyWeather:~ $ locale
>>> LANG=en_GB.UTF-8
>>> LANGUAGE=
>>> LC_CTYPE="en_GB.UTF-8"
>>> LC_NUMERIC="en_GB.UTF-8"
>>> LC_TIME="en_GB.UTF-8"
>>> LC_COLLATE="en_GB.UTF-8"
>>> LC_MONETARY="en_GB.UTF-8"
>>> LC_MESSAGES="en_GB.UTF-8"
>>> LC_PAPER="en_GB.UTF-8"
>>> LC_NAME="en_GB.UTF-8"
>>> LC_ADDRESS="en_GB.UTF-8"
>>> LC_TELEPHONE="en_GB.UTF-8"
>>> LC_MEASUREMENT="en_GB.UTF-8"
>>> LC_IDENTIFICATION="en_GB.UTF-8"
>>> LC_ALL=
>>> pi@SkyWeather:~ $ timedatectl
>>>   Local time: Fri 2018-11-09 08:26:49 -02
>>>   Universal time: Fri 2018-11-09 10:26:49 UTC
>>> RTC time: n/a
>>>Time zone: America/Sao_Paulo (-02, -0200)
>>>  Network time on: yes
>>> NTP synchronized: yes
>>>  RTC in local TZ: no
>>
>>
>>
>> Em sex, 9 de nov de 2018 às 00:53, gjr80  escreveu:
>>
>>> I have not forgotten this. Definitely starting with a clean database:
>>>
>>> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and
>>> initialized table 'archive' in database 'weewx.sdb'
>>> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily summary
>>> tables
>>>
>>> Interesting that the only template that fails is week.html.tmpl, all of
>>> its friends (index.html.tmpl, month.html.tmpl and year.html.tmpl) also
>>> contain wind tags but only week.html.tmpl fails. Suggests the issue is
>>> confined to week.wind.xxx.
>>>
>>> Can I ask you to run a couple of commands on your weeWX system and post
>>> the output. The commands are:
>>>
>>> locale
>>> timedatectl
>>>
>>>
>>> Gary
>>>
>>>
>>> On Tuesday, 6 November 2018 23:50:02 UTC+10, Jonis Maurin Ceará wrote:

 Yes, logs from fresh install yesterday.


 Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Initializing weewx
>> version 3.8.2
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Platform
>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Locale is
>> 'en_GB.UTF-8'
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: pid file is
>> /var/run/weewx.pid
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using configuration
>> file /etc/weewx/weewx.conf
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Loading station type
>> Simulator (weewx.drivers.simulator)
>
> Nov  5 10:02:31 SkyWeather weewx[30073]: Starting weewx weather
>> system: weewx.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: StdConvert target
>> unit is 0x1
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following
>> values will be calculated: barometer=prefer_hardware,
>> windchill=prefer_hardware, dewpoint=prefer_hardware,
>> appTemp=prefer_hardware, rainRate=prefer_hardware, 
>> windrun=prefer_hardware,
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
>> humidex=prefer_hardware, pressure=prefer_hardware,
>> inDewpoint=prefer_hardware, ET=prefer_hardware, 
>> altimeter=prefer_hardware,
>> cloudbase=prefer_hardware
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following
>> algorithms will be used for calculations: altimeter=aaNOAA, 
>> maxSolarRad=RS
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Archive will use data
>> binding wx_binding
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Record generation
>> will be attempted in 'hardware'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using archive
>> interval of 300 seconds (specified in weewx configuration)
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and
>> initialized table 'archive' in database 'weewx.sdb'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily
>> summary tables
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: 

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Another unintended side affect of adding elements to the top of the front 
page would be the change to the mobile view. It would change the "at a 
glance" view of temperature/wind if there's stuff at the top taking its 
place. 

Of course this would only be a problem to those who use the option

Hmm... 

On Monday, November 12, 2018 at 4:10:12 PM UTC-5, Colin Larsen wrote:
>
> I found your instructions on integrating new items into the same menu line 
> as the existing items easy to follow and it looks good with it all in the 
> same line. Otherwise my vote would be above the temp/radar
>
> On Tue, 13 Nov 2018, 10:06 Pat  wrote:
>
> I could do that. 
>
> Where in index do you think? Above the temperature/radar bar? Or above the 
> forecast bar? or above the graphs? So many options, it'll be hard to make 
> everyone happy...
>
> On Monday, November 12, 2018 at 1:39:36 PM UTC-5, Jonis Maurin Ceará wrote:
>
> One sugestion: create an index.top.inc and index.bottom.inc, so users can 
> include code at top and bottom of index pageuser's choice!
> Edit index.tmpl os easyI'm just avoiding because of updates, that I 
> really don't want to lose. If is the case, I'll wait for at least version 
> 0.8 and then edit I just want to include my WebCam image for now.
>
> Em seg, 12 de nov de 2018 às 11:54, Pat  escreveu:
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Colin Larsen]

I found your instructions on integrating new items into the same menu line
as the existing items easy to follow and it looks good with it all in the
same line. Otherwise my vote would be above the temp/radar

On Tue, 13 Nov 2018, 10:06 Pat  I could do that.
>
> Where in index do you think? Above the temperature/radar bar? Or above the
> forecast bar? or above the graphs? So many options, it'll be hard to make
> everyone happy...
>
> On Monday, November 12, 2018 at 1:39:36 PM UTC-5, Jonis Maurin Ceará wrote:
>>
>> One sugestion: create an index.top.inc and index.bottom.inc, so users can
>> include code at top and bottom of index pageuser's choice!
>> Edit index.tmpl os easyI'm just avoiding because of updates, that I
>> really don't want to lose. If is the case, I'll wait for at least version
>> 0.8 and then edit I just want to include my WebCam image for now.
>>
>> Em seg, 12 de nov de 2018 às 11:54, Pat  escreveu:
>>
>> Hi everyone, I'm planning on releasing a 0.8 version very shortly which
>> should contain a lot of fixes you guys have been looking for. No doubt
>> it'll introduce some more bugs, but we'll work on them as they come up.
>>
>> To answer some questions from the last few weeks:
>>
>> Q: Juan had an error using Xiaomi Mi6 to display a graphic
>> A: This seems like a UTF-8 decoding error maybe? Juan, can you paste what
>> character it's trying to use? Do you know?
>>
>> Q: From Juan: I have configured to use the METRIC target unit, so the
>> rain data is in mm. But I see that in the graphics it appears in cm. Can
>> this be changed without modifying target_unit section?
>> A; I think that this should be fixed in 0.8
>>
>> Q: From Paul: Is there a procedure to update the running belchertown skin
>> 0.7 to the last version on the github ?
>> A: No "offi
>>
>> ...
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

I could do that. 

Where in index do you think? Above the temperature/radar bar? Or above the 
forecast bar? or above the graphs? So many options, it'll be hard to make 
everyone happy...

On Monday, November 12, 2018 at 1:39:36 PM UTC-5, Jonis Maurin Ceará wrote:
>
> One sugestion: create an index.top.inc and index.bottom.inc, so users can 
> include code at top and bottom of index pageuser's choice!
> Edit index.tmpl os easyI'm just avoiding because of updates, that I 
> really don't want to lose. If is the case, I'll wait for at least version 
> 0.8 and then edit I just want to include my WebCam image for now.
>
> Em seg, 12 de nov de 2018 às 11:54, Pat  > escreveu:
>
> Hi everyone, I'm planning on releasing a 0.8 version very shortly which 
> should contain a lot of fixes you guys have been looking for. No doubt 
> it'll introduce some more bugs, but we'll work on them as they come up. 
>
> To answer some questions from the last few weeks: 
>
> Q: Juan had an error using Xiaomi Mi6 to display a graphic
> A: This seems like a UTF-8 decoding error maybe? Juan, can you paste what 
> character it's trying to use? Do you know?
>
> Q: From Juan: I have configured to use the METRIC target unit, so the rain 
> data is in mm. But I see that in the graphics it appears in cm. Can this be 
> changed without modifying target_unit section?
> A; I think that this should be fixed in 0.8
>
> Q: From Paul: Is there a procedure to update the running belchertown skin 
> 0.7 to the last version on the github ? 
> A: No "offi
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Easier way to change barometer => pressure ?

[Thomas Keffer]

WeeWX calculates three different types of pressure: barometer, pressure,
and altimeter. The Wiki

explains the difference. Use which ever one you want in your template files.

-tk

On Sun, Nov 11, 2018 at 3:08 AM Per Edström 
wrote:

> My WMR200 is presenting local airpressure ("pressure") on the display but
> Weewx have default setting to present sea-lever pressure ("barmometer").
>
> I don't find sea-level-pressure useful as it differs from what the WMR200
> is showing. It is also more acurate.
>
> Changing this requires editing "barometer" => "pressure" in a lot of files
> and there in many places (and just replacing "barometer" with "pressure"
> will change too much e.g. pure text on web page):
> - weex.conf
> - skin.conf
> - index.html.tmpl
> - week.html.tmpl
> - month.html.tmpl
> - year.html.tmpl
> - smartphone/index.html.tmpl
> - smartphone/barometer.html.tmpl
>
> Can this be done in one place instead? Like changing just in weewx.conf
>
> *airpressure = barometer/pressure*
>
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[Jonis Maurin Ceará]

One sugestion: create an index.top.inc and index.bottom.inc, so users can
include code at top and bottom of index pageuser's choice!
Edit index.tmpl os easyI'm just avoiding because of updates, that I
really don't want to lose. If is the case, I'll wait for at least version
0.8 and then edit I just want to include my WebCam image for now.

Em seg, 12 de nov de 2018 às 11:54, Pat  escreveu:

> Hi everyone, I'm planning on releasing a 0.8 version very shortly which
> should contain a lot of fixes you guys have been looking for. No doubt
> it'll introduce some more bugs, but we'll work on them as they come up.
>
> To answer some questions from the last few weeks:
>
> Q: Juan had an error using Xiaomi Mi6 to display a graphic
> A: This seems like a UTF-8 decoding error maybe? Juan, can you paste what
> character it's trying to use? Do you know?
>
> Q: From Juan: I have configured to use the METRIC target unit, so the rain
> data is in mm. But I see that in the graphics it appears in cm. Can this be
> changed without modifying target_unit section?
> A; I think that this should be fixed in 0.8
>
> Q: From Paul: Is there a procedure to update the running belchertown skin
> 0.7 to the last version on the github ?
> A: No "official" procedure, but you can just copy the file to their
> desintation. For example, everything in bin/user on GitHub would go into
> bin/user on your weewx system. Same with the skins folder. Just make sure
> you have a backup, and you restart weewx after you copy the files.
>
> Q: Just one question: do you have any plans to include option to add an
> custom html/code on main page and maybe translations?
> A: No plans right now since I've been working on trying to stabilize a lot
> of the bugs. I suppose I could do an index.inc just like I did with the
> about.inc. But I'm not sure where that custom content would go in the page
> since this could be very different for everyone's site. So I would say it
> might be best for you to edit the index.html.tmpl for the time being -
> which isn't ideal.
>
> I think (hope) that covers it!
>
> The GitHub page has updates for 0.8rc2 right now - I'm waiting for a
> little more feedback before I push those changes into a proper 0.8 release.
> Hopefully in the next few days.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/GSrKZEiPqsc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Jonis Maurin Ceará]

Yes Andrew, same problem. Like I said before, I've tried with a fresh-new
install, with all default configs and no mods, including skins, just
default installation and Standard skin/configuration, including default
sqlite database. Problem is alwayd the same.

I'm running new skin now because despiste error in log, page is being
updated fine.but problem (wind on log) still.


1) Remove all packages and files relates to weewx (including all dir and
> subdirs on /etc/weewx, /usr/share/weewx, /var/lib/weewx or /usr/lib/weewx,
> don't rememebr now). Everything
> 2) Install from .deb package and accept default settings (name, location,
> driver=simulation, etc...)
> 3) Just start, done!
> When you access webpage, loads fine.but still the same error in
> logfile, wind column not found (of course, the error is using sqlite, and
> not mysqllite like I posted).
> Second attempt:
> 1) Change archive database to mysql instead of sqlite.
> 2) Re-start weewx. Tables are created and archive page is created
> 3) Still the same problem on log (wind column), but information on log's
> say 'mysql' driver, and not sqlite.
> And then with fileparser driver, with exactly same results



Em seg, 12 de nov de 2018 às 13:02, Andrew Milner <
andrew.s.r.mil...@gmail.com> escreveu:

> The site URL you gave is not running the standard weewx skin, but is
> instead appears to be using the Belchertown skin and using Highcharts to do
> the graphing.  Do you get the same 'problems' if you just use the Standard
> skin which comes with weewx  What else have you loaded on top of the
> standard weewx installation
>
>
>
> Belchertown problems and issues should really be referred to the
> Belchertown author via his GitHub site.
>
>
>
> On Monday, 12 November 2018 16:13:11 UTC+2, Jonis Maurin Ceará wrote:
>>
>> Yes, I'm using this file: weewx_3.8.2-1_all.deb
>>
>> Currently I'm using with MySQLthe problem persist (wind error in
>> logs), but archive is being generated. http://weather.jonis.com.br/
>>
>>
>> Em dom, 11 de nov de 2018 às 21:03, gjr80  escreveu:
>>
>>> I have set up a Stretch VM using the same locale and timezone settings
>>> as you running a .deb weeWX install and I cannot reproduce the fault you
>>> are experiencing. This really brings me back to the your database. I will
>>> instrument one of the weeWX files with some extra logging so we can see
>>> exactly what is happening when the offending tag(s) is/are called. In the
>>> meantime can you confirm exactly what version of weeWX you are now running
>>> on the problem system (3.8.2 I am guessing) so that I can ensure I give you
>>> a compatible version of the file.
>>>
>>> Gary
>>>
>>> On Friday, 9 November 2018 20:27:44 UTC+10, Jonis Maurin Ceará wrote:

 Sure!
 And one more info: this error (wind) happens on all skins.

 pi@SkyWeather:~ $ locale
> LANG=en_GB.UTF-8
> LANGUAGE=
> LC_CTYPE="en_GB.UTF-8"
> LC_NUMERIC="en_GB.UTF-8"
> LC_TIME="en_GB.UTF-8"
> LC_COLLATE="en_GB.UTF-8"
> LC_MONETARY="en_GB.UTF-8"
> LC_MESSAGES="en_GB.UTF-8"
> LC_PAPER="en_GB.UTF-8"
> LC_NAME="en_GB.UTF-8"
> LC_ADDRESS="en_GB.UTF-8"
> LC_TELEPHONE="en_GB.UTF-8"
> LC_MEASUREMENT="en_GB.UTF-8"
> LC_IDENTIFICATION="en_GB.UTF-8"
> LC_ALL=
> pi@SkyWeather:~ $ timedatectl
>   Local time: Fri 2018-11-09 08:26:49 -02
>   Universal time: Fri 2018-11-09 10:26:49 UTC
> RTC time: n/a
>Time zone: America/Sao_Paulo (-02, -0200)
>  Network time on: yes
> NTP synchronized: yes
>  RTC in local TZ: no



 Em sex, 9 de nov de 2018 às 00:53, gjr80  escreveu:

> I have not forgotten this. Definitely starting with a clean database:
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and
> initialized table 'archive' in database 'weewx.sdb'
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily
> summary tables
>
> Interesting that the only template that fails is week.html.tmpl, all
> of its friends (index.html.tmpl, month.html.tmpl and year.html.tmpl)
> also contain wind tags but only week.html.tmpl fails. Suggests the
> issue is confined to week.wind.xxx.
>
> Can I ask you to run a couple of commands on your weeWX system and
> post the output. The commands are:
>
> locale
> timedatectl
>
>
> Gary
>
>
> On Tuesday, 6 November 2018 23:50:02 UTC+10, Jonis Maurin Ceará wrote:
>>
>> Yes, logs from fresh install yesterday.
>>
>>
>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Initializing weewx
 version 3.8.2
>>>
>>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Using Python 2.7.13
 (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>>
>>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Platform
 Linux-4.14.71-v7+-armv7l-with-debian-9.4
>>>
>>> Nov  5 10:02:31 

[weewx-user] weewx and Wunderground - Recent Data Issue

[Dave McCreath]

Eqpt:

Vantage Vue on USB with datalogger.
Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
weewx v.3.8.2.
Wunderfixer running as a cron task every 60 minutes (at the moment).
WunderGround ID ICAMBSLE2 (which has been running well for over three 
years).

Issue:  

weewx uploads data packets to Wundergound every five minutes but less than 
half appear to get through first time.  Those that do get through first 
time do not appear on the Wundergound GUI until 6/7 minutes after being 
uploaded.  Previously, they would appear within 2 minutes of uploading.  
However, with Wunderfixer (currently) running every hour, data records are 
eventually getting through to the server after about two and a half hours 
(sometimes three).  Local data is being saved to my personal weewx website 
without any issues. 

Background:  

The issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day after 
the clocks changed!).  I initially thought it might be a timing issue post 
the clocks changing, but checking the records for Sunday 28 Oct, all was 
fine.  Checked the epoch time on the RPi and Davis console, both OK.  
Strangely, If I turn on rapid-fire (via .conf), all works as it should do, 
no issues whatsoever.

Log Extract: (No issues as far as I can see)

Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
15:55:00 GMT (1542038100) to database 'weewx.sdb'
Nov 12 15:55:15 weewx weewx[4781]: manager: Added record 2018-11-12 
15:55:00 GMT (1542038100) to daily summary in 'weewx.sdb'
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running reports for latest 
time in the database.
Nov 12 15:55:15 weewx weewx[4781]: vantage: Requesting 200 LOOP packets.
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Running report 
StandardReport
Nov 12 15:55:15 weewx weewx[4781]: vantage: Gentle wake up of console 
successful
Nov 12 15:55:15 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Standard/skin.conf for report StandardReport
Nov 12 15:55:15 weewx weewx[4781]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']
Nov 12 15:55:15 weewx weewx[4781]: manager: Daily summary version is 2.0
Nov 12 15:55:16 weewx weewx[4781]: restx: Wunderground-PWS: Published 
record 2018-11-12 15:55:00 GMT (1542038100)
Nov 12 15:55:17 weewx weewx[4781]: cheetahgenerator: Generated 14 files for 
report StandardReport in 1.46 seconds
Nov 12 15:55:17 weewx weewx[4781]: manager: Daily summary version is 2.0
Nov 12 15:55:18 weewx weewx[4781]: imagegenerator: Generated 12 images for 
StandardReport in 0.90 seconds
Nov 12 15:55:18 weewx weewx[4781]: copygenerator: copied 0 files to 
/var/www/html/weewx
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report FTP
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Ftp/skin.conf for report FTP
Nov 12 15:55:18 weewx weewx[4781]: ftpgenerator: FTP upload not requested. 
Skipped.
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Running report RSYNC
Nov 12 15:55:18 weewx weewx[4781]: reportengine: Found configuration file 
/etc/weewx/skins/Rsync/skin.conf for report RSYNC
Nov 12 15:55:18 weewx weewx[4781]: rsyncgenerator: rsync upload not 
requested. Skipped.
Nov 12 15:59:01 weewx CRON[9215]: (pi) CMD (wunderfixer --log weewx)
Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using weewx configuration 
file /etc/weewx/weewx.conf.
Nov 12 15:59:01 weewx weewx[9216]: wunderfixer: Using database binding 
'wx_binding', which is bound to database 'archive_sqlite'
Nov 12 15:59:02 weewx weewx[9216]: wunderfixer: 25 Weather Underground 
records missing.
Nov 12 15:59:13 weewx weewx[9216]: wunderfixer: 25 out of 25 missing 
records published to 'ICAMBSLE2' for date 2018-11-12. Wunderfixer exiting.

WunderGround Web Page:

[image: WeeWx Issue.jpg]
 Anyone any ideas?

Regards

Dave

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] weewx and Wunderground, Recent Issue

[Dave McCreath]

Vantage Vue on USB with datalogger.
Debian 9.4 on a Raspberry Pi (updated and upgraded as of two weeks ago).
weewx v.3.8.2.
Wunderfixer running as a cron task every 60 minutes (at the moment).
WunderGround ID ICAMBSLE2 (which has been running well for over three 
years).

Issue:  weewx uploads data packets to Wundergound every five minutes but 
less than half appear to get through first time.  Those that do get through 
first time do not appear on the Wundergound GUI until 6/7 minutes after 
being uploaded.  Previously, they would appear within 2 minutes of 
uploading.  However, with Wunderfixer (currently) running every hour, data 
records are eventually getting through to the server after about two and a 
half hours (sometimes three).  Local data is being saved to my personal 
weewx website without any issues. 

Background:  Issue first appeared at roughly 1400hrs GMT on Mon 29 Oct (day 
after the clocks changed!).  I initially thought it might be a timing issue 
post the clocks changing, but checking the records for Sunday 28 Oct, all 
was fine.  Checked the time on the RPi and Davis console, both OK.  
Strangely, If I turn on rapid-fire (via .conf file), all works as it should 
do, no issues whatsoever.

Anyone any ideas?

[image: WeeWx Issue.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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Andrew Milner]

The site URL you gave is not running the standard weewx skin, but is 
instead appears to be using the Belchertown skin and using Highcharts to do 
the graphing.  Do you get the same 'problems' if you just use the Standard 
skin which comes with weewx  What else have you loaded on top of the 
standard weewx installation



Belchertown problems and issues should really be referred to the 
Belchertown author via his GitHub site.



On Monday, 12 November 2018 16:13:11 UTC+2, Jonis Maurin Ceará wrote:
>
> Yes, I'm using this file: weewx_3.8.2-1_all.deb
>
> Currently I'm using with MySQLthe problem persist (wind error in 
> logs), but archive is being generated. http://weather.jonis.com.br/
>
>
> Em dom, 11 de nov de 2018 às 21:03, gjr80  > escreveu:
>
>> I have set up a Stretch VM using the same locale and timezone settings as 
>> you running a .deb weeWX install and I cannot reproduce the fault you are 
>> experiencing. This really brings me back to the your database. I will 
>> instrument one of the weeWX files with some extra logging so we can see 
>> exactly what is happening when the offending tag(s) is/are called. In the 
>> meantime can you confirm exactly what version of weeWX you are now running 
>> on the problem system (3.8.2 I am guessing) so that I can ensure I give you 
>> a compatible version of the file.
>>
>> Gary
>>
>> On Friday, 9 November 2018 20:27:44 UTC+10, Jonis Maurin Ceará wrote:
>>>
>>> Sure!
>>> And one more info: this error (wind) happens on all skins.
>>>
>>> pi@SkyWeather:~ $ locale
 LANG=en_GB.UTF-8
 LANGUAGE=
 LC_CTYPE="en_GB.UTF-8"
 LC_NUMERIC="en_GB.UTF-8"
 LC_TIME="en_GB.UTF-8"
 LC_COLLATE="en_GB.UTF-8"
 LC_MONETARY="en_GB.UTF-8"
 LC_MESSAGES="en_GB.UTF-8"
 LC_PAPER="en_GB.UTF-8"
 LC_NAME="en_GB.UTF-8"
 LC_ADDRESS="en_GB.UTF-8"
 LC_TELEPHONE="en_GB.UTF-8"
 LC_MEASUREMENT="en_GB.UTF-8"
 LC_IDENTIFICATION="en_GB.UTF-8"
 LC_ALL=
 pi@SkyWeather:~ $ timedatectl
   Local time: Fri 2018-11-09 08:26:49 -02
   Universal time: Fri 2018-11-09 10:26:49 UTC
 RTC time: n/a
Time zone: America/Sao_Paulo (-02, -0200)
  Network time on: yes
 NTP synchronized: yes
  RTC in local TZ: no
>>>
>>>
>>>
>>> Em sex, 9 de nov de 2018 às 00:53, gjr80  escreveu:
>>>
 I have not forgotten this. Definitely starting with a clean database:

 Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and 
 initialized table 'archive' in database 'weewx.sdb'
 Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily 
 summary tables

 Interesting that the only template that fails is week.html.tmpl, all 
 of its friends (index.html.tmpl, month.html.tmpl and year.html.tmpl) 
 also contain wind tags but only week.html.tmpl fails. Suggests the 
 issue is confined to week.wind.xxx.

 Can I ask you to run a couple of commands on your weeWX system and post 
 the output. The commands are:

 locale
 timedatectl


 Gary


 On Tuesday, 6 November 2018 23:50:02 UTC+10, Jonis Maurin Ceará wrote:
>
> Yes, logs from fresh install yesterday.
>
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Initializing weewx 
>>> version 3.8.2
>>
>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Using Python 2.7.13 
>>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>>
>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Platform 
>>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>>
>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Locale is 
>>> 'en_GB.UTF-8'
>>
>> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: pid file is 
>>> /var/run/weewx.pid
>>
>> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using configuration 
>>> file /etc/weewx/weewx.conf
>>
>> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Loading station type 
>>> Simulator (weewx.drivers.simulator)
>>
>> Nov  5 10:02:31 SkyWeather weewx[30073]: Starting weewx weather 
>>> system: weewx.
>>
>> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: StdConvert target 
>>> unit is 0x1
>>
>> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following 
>>> values will be calculated: barometer=prefer_hardware, 
>>> windchill=prefer_hardware, dewpoint=prefer_hardware, 
>>> appTemp=prefer_hardware, rainRate=prefer_hardware, 
>>> windrun=prefer_hardware, 
>>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware, 
>>> humidex=prefer_hardware, pressure=prefer_hardware, 
>>> inDewpoint=prefer_hardware, ET=prefer_hardware, 
>>> altimeter=prefer_hardware, 
>>> cloudbase=prefer_hardware
>>
>> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following 
>>> algorithms will be used for calculations: altimeter=aaNOAA, 
>>> maxSolarRad=RS
>>
>> Nov  5 10:02:31 

Re: [weewx-user] Multiple errors in weewx 3.8.2

[Jonis Maurin Ceará]

Yes, I'm using this file: weewx_3.8.2-1_all.deb

Currently I'm using with MySQLthe problem persist (wind error in logs),
but archive is being generated. http://weather.jonis.com.br/


Em dom, 11 de nov de 2018 às 21:03, gjr80  escreveu:

> I have set up a Stretch VM using the same locale and timezone settings as
> you running a .deb weeWX install and I cannot reproduce the fault you are
> experiencing. This really brings me back to the your database. I will
> instrument one of the weeWX files with some extra logging so we can see
> exactly what is happening when the offending tag(s) is/are called. In the
> meantime can you confirm exactly what version of weeWX you are now running
> on the problem system (3.8.2 I am guessing) so that I can ensure I give you
> a compatible version of the file.
>
> Gary
>
> On Friday, 9 November 2018 20:27:44 UTC+10, Jonis Maurin Ceará wrote:
>>
>> Sure!
>> And one more info: this error (wind) happens on all skins.
>>
>> pi@SkyWeather:~ $ locale
>>> LANG=en_GB.UTF-8
>>> LANGUAGE=
>>> LC_CTYPE="en_GB.UTF-8"
>>> LC_NUMERIC="en_GB.UTF-8"
>>> LC_TIME="en_GB.UTF-8"
>>> LC_COLLATE="en_GB.UTF-8"
>>> LC_MONETARY="en_GB.UTF-8"
>>> LC_MESSAGES="en_GB.UTF-8"
>>> LC_PAPER="en_GB.UTF-8"
>>> LC_NAME="en_GB.UTF-8"
>>> LC_ADDRESS="en_GB.UTF-8"
>>> LC_TELEPHONE="en_GB.UTF-8"
>>> LC_MEASUREMENT="en_GB.UTF-8"
>>> LC_IDENTIFICATION="en_GB.UTF-8"
>>> LC_ALL=
>>> pi@SkyWeather:~ $ timedatectl
>>>   Local time: Fri 2018-11-09 08:26:49 -02
>>>   Universal time: Fri 2018-11-09 10:26:49 UTC
>>> RTC time: n/a
>>>Time zone: America/Sao_Paulo (-02, -0200)
>>>  Network time on: yes
>>> NTP synchronized: yes
>>>  RTC in local TZ: no
>>
>>
>>
>> Em sex, 9 de nov de 2018 às 00:53, gjr80  escreveu:
>>
>>> I have not forgotten this. Definitely starting with a clean database:
>>>
>>> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and
>>> initialized table 'archive' in database 'weewx.sdb'
>>> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily summary
>>> tables
>>>
>>> Interesting that the only template that fails is week.html.tmpl, all of
>>> its friends (index.html.tmpl, month.html.tmpl and year.html.tmpl) also
>>> contain wind tags but only week.html.tmpl fails. Suggests the issue is
>>> confined to week.wind.xxx.
>>>
>>> Can I ask you to run a couple of commands on your weeWX system and post
>>> the output. The commands are:
>>>
>>> locale
>>> timedatectl
>>>
>>>
>>> Gary
>>>
>>>
>>> On Tuesday, 6 November 2018 23:50:02 UTC+10, Jonis Maurin Ceará wrote:

 Yes, logs from fresh install yesterday.


 Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Initializing weewx
>> version 3.8.2
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Using Python 2.7.13
>> (default, Sep 26 2018, 18:42:22) #012[GCC 6.3.0 20170516]
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Platform
>> Linux-4.14.71-v7+-armv7l-with-debian-9.4
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: Locale is
>> 'en_GB.UTF-8'
>
> Nov  5 10:02:31 SkyWeather weewx[30084]: engine: pid file is
>> /var/run/weewx.pid
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using configuration
>> file /etc/weewx/weewx.conf
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Loading station type
>> Simulator (weewx.drivers.simulator)
>
> Nov  5 10:02:31 SkyWeather weewx[30073]: Starting weewx weather
>> system: weewx.
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: StdConvert target
>> unit is 0x1
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following
>> values will be calculated: barometer=prefer_hardware,
>> windchill=prefer_hardware, dewpoint=prefer_hardware,
>> appTemp=prefer_hardware, rainRate=prefer_hardware, 
>> windrun=prefer_hardware,
>> heatindex=prefer_hardware, maxSolarRad=prefer_hardware,
>> humidex=prefer_hardware, pressure=prefer_hardware,
>> inDewpoint=prefer_hardware, ET=prefer_hardware, 
>> altimeter=prefer_hardware,
>> cloudbase=prefer_hardware
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: wxcalculate: The following
>> algorithms will be used for calculations: altimeter=aaNOAA, 
>> maxSolarRad=RS
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Archive will use data
>> binding wx_binding
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Record generation
>> will be attempted in 'hardware'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using archive
>> interval of 300 seconds (specified in weewx configuration)
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created and
>> initialized table 'archive' in database 'weewx.sdb'
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: manager: Created daily
>> summary tables
>
> Nov  5 10:02:31 SkyWeather weewx[30088]: engine: Using binding
>> 'wx_binding' to 

[weewx-user] Re: Belchertown skin for weewx now available!

[Pat]

Hi everyone, I'm planning on releasing a 0.8 version very shortly which 
should contain a lot of fixes you guys have been looking for. No doubt 
it'll introduce some more bugs, but we'll work on them as they come up. 

To answer some questions from the last few weeks: 

Q: Juan had an error using Xiaomi Mi6 to display a graphic
A: This seems like a UTF-8 decoding error maybe? Juan, can you paste what 
character it's trying to use? Do you know?

Q: From Juan: I have configured to use the METRIC target unit, so the rain 
data is in mm. But I see that in the graphics it appears in cm. Can this be 
changed without modifying target_unit section?
A; I think that this should be fixed in 0.8

Q: From Paul: Is there a procedure to update the running belchertown skin 
0.7 to the last version on the github ? 
A: No "official" procedure, but you can just copy the file to their 
desintation. For example, everything in bin/user on GitHub would go into 
bin/user on your weewx system. Same with the skins folder. Just make sure 
you have a backup, and you restart weewx after you copy the files. 

Q: Just one question: do you have any plans to include option to add an 
custom html/code on main page and maybe translations?
A: No plans right now since I've been working on trying to stabilize a lot 
of the bugs. I suppose I could do an index.inc just like I did with the 
about.inc. But I'm not sure where that custom content would go in the page 
since this could be very different for everyone's site. So I would say it 
might be best for you to edit the index.html.tmpl for the time being - 
which isn't ideal. 

I think (hope) that covers it! 

The GitHub page has updates for 0.8rc2 right now - I'm waiting for a little 
more feedback before I push those changes into a proper 0.8 release. 
Hopefully in the next few days. 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [weewx-user] Re: Belchertown skin for weewx now available!

[hindleydj]

The above change does not fix the records problem, but uploading latest 
belchertown.py, skin.conf and index.html.tmpl (from records folder) does.  
See latest comments 
in https://github.com/poblabs/weewx-belchertown/issues/8 for further 
details.

On Saturday, 10 November 2018 14:03:31 UTC, hind...@gmail.com wrote:
>
> Many thanks for the tip.  I tried it, but so far it hasn't worked; the 
> records have the same errors as before.  Do I have to wait a while to allow 
> the records to be recalculated?  I am a bit puzzled by how a change to code 
> whose name appears to relate to charts can fix a numerical records page, 
> but maybe there is some dependency of the records calculation that means 
> this makes sense.
>
> On Saturday, 10 November 2018 13:30:33 UTC, WILWetter25 wrote:
>
> or download this file in the attachment
>
> Am Donnerstag, 8. November 2018 16:18:23 UTC+1 schrieb hind...@gmail.com:
>
> Yes, but from what I can see, no solution has been suggested for the 
> records problem, except maybe manually adjusting the unit conversion code 
> in the records python code - has anyone done that and if so what changes 
> are needed?
>
> On Thursday, 8 November 2018 11:23:33 UTC, Praveen Chandrasekaran wrote:
>
> Issue already exists for this:
>
> ...

-- 
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.
For more options, visit https://groups.google.com/d/optout.