[weewx-user] Re: Who is using what Weather Station

[David Hathaway]

"the vast majority of the users here are running everything with a Pi"

That's interesting.  Is it true?  Not in my case; I'm in the 
inconsequential minority.

To OP: I am running a Davis Vantage Pro 2.  I originally used an Oregon 
Scientific WMR-200A but I had too many problems with it performing 
reliably.  I am in favor of cost-effectiveness, but when the effectiveness 
of the solution is questionable... I upgraded.

On Wednesday, March 21, 2018 at 11:44:55 AM UTC-5, WindnFog wrote:
>
> I'm using a Davis Vantage Vue.  It's been going since 2012 (6 years 
> non-stop except for battery changes ~ 1 time a year.)  I've only been using 
> weewx for ~2.5 years with it.  This combo is rock solid . . . but I'm not 
> exactly using a Pi to do everything.  My Pi just takes pictures every 5 
> minutes and sends them to my main CentOS system, which is running weewx.  A 
> bit more complicated than I want, but it evolved over time and it's hard to 
> get the energy to put everything on the Pi.  I'd recommend Davis any day, 
> and I suspect the vast majority of the users here are running everything 
> with a Pi.  As Andrew suggested, take a look at the various combinations 
> that over 1000 users have picked on the station map.
>
> - Paul VE1DX
>
>
> On Tuesday, March 20, 2018 at 1:49:04 AM UTC-3, Kevin Hedgepeth wrote:
>>
>> I am looking to attach a weather station to a Pi.  I am curious to know 
>> what weather stations you are using.  Please include the manufacturer and 
>> model.  If you had issues getting it to work with WeeWx or the Pi I would 
>> like to hear that too.
>>
>> Kevin Hedgepeth, Hermiston, Oregon
>>
>

-- 
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] Re: Belchertown skin for weewx now available!

[David Hathaway]

I'm having a different error, I believe.  Any ideas on how to sort it out?

My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.

I downloaded the version the day you posted it first, so it is v0.1?  Would 
the later revisions solve the issue?  I think not, since this appears to be 
a SQL issue.


13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published record 
2018-08-26 13:56:00 CDT (1535309760)
Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated 14 
files for report StandardReport in 0.78 seconds
Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16 images 
for StandardReport in 0.76 seconds
Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Aug 26 13:56:16 localhost weewx[23412]:*   (1055, "Expression 
#2 of SELECT list is not in GROUP BY clause and contains nonaggregated 
column 'weewx.archive_day_rain.dateTime' which is not functionally 
dependent on columns in GROUP BY clause; this is incompatible with 
sql_mode=only_full_group_by")*
Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most 
recent call last):
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Aug 26 13:56:16 localhost weewx[23412]:   self.run()
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
Aug 26 13:56:16 localhost weewx[23412]:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
Aug 26 13:56:16 localhost weewx[23412]:   default_binding)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
Aug 26 13:56:16 localhost weewx[23412]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/user/belchertown.py", line 82, in get_extension_list
Aug 26 13:56:16 localhost weewx[23412]:   at_rainiest_month 
= wx_manager.getSql( at_rainiest_month_sql )
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weewx/manager.py", line 394, in getSql
Aug 26 13:56:16 localhost weewx[23412]:   
_cursor.execute(sql, sqlargs)
Aug 26 13:56:16 localhost weewx[23412]: File 
"/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
Aug 26 13:56:16 localhost weewx[23412]:   raise klass(e)
Aug 26 13:56:16 localhost weewx[23412]:   *DatabaseError: 
(1055, "Expression #2 of SELECT list is not in GROUP BY clause and contains 
nonaggregated column 'weewx.archive_day_rain.dateTime' which is not 
functionally dependent on columns in GROUP BY clause; this is incompatible 
with sql_mode=only_full_group_by")*
Aug 26 13:56:16 localhost weewx[23412]:   Generator terminated
Aug 26 13:56:16 localhost weewx[23412]: copygenerator: copied 1 files to 
/var/www/html/weewx/belchertown

-- 
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] Re: Belchertown skin for weewx now available!

[David Hathaway]

Well, I saw I was running 3.8.0 but it the latest is 3.8.2, so I am 
upgrading now.  For some reason, it replaced my weewx.conf even though I 
asked to keep the existing one, so that is slowing things a bit.

On Sunday, August 26, 2018 at 2:48:43 PM UTC-5, Pat wrote:
>
> I haven't come across this error before. How old is your weewx? 
>
> On Sunday, August 26, 2018 at 3:01:10 PM UTC-4, David Hathaway wrote:
>>
>> I'm having a different error, I believe.  Any ideas on how to sort it out?
>>
>> My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.
>>
>> I downloaded the version the day you posted it first, so it is v0.1?  
>> Would the later revisions solve the issue?  I think not, since this appears 
>> to be a SQL issue.
>>
>>
>> 13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published 
>> record 2018-08-26 13:56:00 CDT (1535309760)
>> Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated 14 
>> files for report StandardReport in 0.78 seconds
>> Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16 
>> images for StandardReport in 0.76 seconds
>> Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught 
>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Aug 26 13:56:16 localhost weewx[23412]:*   (1055, 
>> "Expression #2 of SELECT list is not in GROUP BY clause and contains 
>> nonaggregated column 'weewx.archive_day_rain.dateTime' which is not 
>> functionally dependent on columns in GROUP BY clause; this is incompatible 
>> with sql_mode=only_full_group_by")*
>> Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most 
>> recent call last):
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Aug 26 13:56:16 localhost weewx[23412]:   self.run()
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>> Aug 26 13:56:16 localhost weewx[23412]:   ngen = 
>> self.generate(gen_dict[section_name], self.gen_ts)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>> self.generate(section[subsection], gen_ts)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>> self.generate(section[subsection], gen_ts)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>> Aug 26 13:56:16 localhost weewx[23412]:   default_binding)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Aug 26 13:56:16 localhost weewx[23412]:   searchList += 
>> obj.get_extension_list(timespan, db_lookup)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/user/belchertown.py", line 82, in get_extension_list
>> Aug 26 13:56:16 localhost weewx[23412]:   
>> at_rainiest_month = wx_manager.getSql( at_rainiest_month_sql )
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weewx/manager.py", line 394, in getSql
>> Aug 26 13:56:16 localhost weewx[23412]:   
>> _cursor.execute(sql, sqlargs)
>> Aug 26 13:56:16 localhost weewx[23412]: File 
>> "/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
>> Aug 26 13:56:16 localhost weewx[23412]:   raise klass(e)
>> Aug 26 13:56:16 localhost weewx[23412]:   *DatabaseError: 
>> (1055, "Expression #2 of SELECT list is not in GROUP BY clause and contains 
>> nonaggregated column 'weewx.archive_day_rain.dateTime' which is not 
>> functionally dependent on columns in GROUP BY clause; this is incompatible 
>> with sql_mode=only_full_group_by")*
>> Aug 26 13:56:16 localhost weewx[23412]:   Generator terminated
>> Aug 26 13:56:16 localhost weewx[23412]: copygenerator: copied 1 files to 
>> /var/www/html/weewx/belchertown
>>
>

-- 
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] Re: Belchertown skin for weewx now available!

[David Hathaway]

Thanks for this Andrew.  It shows great promise.

Unfortunately, I think there are trickle down issues.  I don't know.  Now I 
am getting exceptions in weewx.cheetahgenerator.CheetahGenerator in 
sqlite.py... but I am running MySQL?  This not a Belchertown error, so I'll 
move further conversation about it outside this conversation.

On Sunday, August 26, 2018 at 8:45:04 PM UTC-5, Andrew Milner wrote:
>
> It looks like this may be an issue with MySQL versions with updates from 
> 5.5 to later:
>
>
> https://www.sitepoint.com/quick-tip-how-to-permanently-change-sql-mode-in-mysql/
>
>
>
> On Sunday, 26 August 2018 22:48:43 UTC+3, Pat wrote:
>>
>> I haven't come across this error before. How old is your weewx? 
>>
>> On Sunday, August 26, 2018 at 3:01:10 PM UTC-4, David Hathaway wrote:
>>>
>>> I'm having a different error, I believe.  Any ideas on how to sort it 
>>> out?
>>>
>>> My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.
>>>
>>> I downloaded the version the day you posted it first, so it is v0.1?  
>>> Would the later revisions solve the issue?  I think not, since this appears 
>>> to be a SQL issue.
>>>
>>>
>>> 13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published 
>>> record 2018-08-26 13:56:00 CDT (1535309760)
>>> Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated 14 
>>> files for report StandardReport in 0.78 seconds
>>> Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16 
>>> images for StandardReport in 0.76 seconds
>>> Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught 
>>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>>> Aug 26 13:56:16 localhost weewx[23412]:*   (1055, 
>>> "Expression #2 of SELECT list is not in GROUP BY clause and contains 
>>> nonaggregated column 'weewx.archive_day_rain.dateTime' which is not 
>>> functionally dependent on columns in GROUP BY clause; this is incompatible 
>>> with sql_mode=only_full_group_by")*
>>> Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most 
>>> recent call last):
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>> Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>> Aug 26 13:56:16 localhost weewx[23412]:   self.run()
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen = 
>>> self.generate(gen_dict[section_name], self.gen_ts)
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>>> self.generate(section[subsection], gen_ts)
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>>> self.generate(section[subsection], gen_ts)
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>>> Aug 26 13:56:16 localhost weewx[23412]:   
>>> default_binding)
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>>> Aug 26 13:56:16 localhost weewx[23412]:   searchList += 
>>> obj.get_extension_list(timespan, db_lookup)
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/user/belchertown.py", line 82, in get_extension_list
>>> Aug 26 13:56:16 localhost weewx[23412]:   
>>> at_rainiest_month = wx_manager.getSql( at_rainiest_month_sql )
>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>> "/usr/share/weewx/weewx/manager.py", line 394, in getSql
>>> Aug 26 13:56:16 localhost weewx[23412]:   
>>> _cursor.execute(sql, sqlargs)
>>> Au

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

[David Hathaway]

FWIW, the CheetahGenerator issue was caused by the borked upgrade to 3.8.2, 
which set DataBindings.wx_binding.database to archive_sqlite when I have 
been using mysql.  I really ought to get a better text compare program for 
times like this.  UltraCompare is awesome, but Windows.

I'm ready to get back to trying Belchertown.  Yay!

Pat, are there known issues moving from v 0.1 to whatever is on github 
now?  (0.4?)  If I am going to try moving forward, it ought to be on the 
latest codebase, eh?

On Monday, August 27, 2018 at 6:26:40 AM UTC-5, David Hathaway wrote:
>
> Thanks for this Andrew.  It shows great promise.
>
> Unfortunately, I think there are trickle down issues.  I don't know.  Now 
> I am getting exceptions in weewx.cheetahgenerator.CheetahGenerator in 
> sqlite.py... but I am running MySQL?  This not a Belchertown error, so I'll 
> move further conversation about it outside this conversation.
>
> On Sunday, August 26, 2018 at 8:45:04 PM UTC-5, Andrew Milner wrote:
>>
>> It looks like this may be an issue with MySQL versions with updates from 
>> 5.5 to later:
>>
>>
>> https://www.sitepoint.com/quick-tip-how-to-permanently-change-sql-mode-in-mysql/
>>
>>
>>
>> On Sunday, 26 August 2018 22:48:43 UTC+3, Pat wrote:
>>>
>>> I haven't come across this error before. How old is your weewx? 
>>>
>>> On Sunday, August 26, 2018 at 3:01:10 PM UTC-4, David Hathaway wrote:
>>>>
>>>> I'm having a different error, I believe.  Any ideas on how to sort it 
>>>> out?
>>>>
>>>> My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.
>>>>
>>>> I downloaded the version the day you posted it first, so it is v0.1?  
>>>> Would the later revisions solve the issue?  I think not, since this 
>>>> appears 
>>>> to be a SQL issue.
>>>>
>>>>
>>>> 13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published 
>>>> record 2018-08-26 13:56:00 CDT (1535309760)
>>>> Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated 14 
>>>> files for report StandardReport in 0.78 seconds
>>>> Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16 
>>>> images for StandardReport in 0.76 seconds
>>>> Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught 
>>>> unrecoverable exception in generator 
>>>> weewx.cheetahgenerator.CheetahGenerator
>>>> Aug 26 13:56:16 localhost weewx[23412]:*   (1055, 
>>>> "Expression #2 of SELECT list is not in GROUP BY clause and contains 
>>>> nonaggregated column 'weewx.archive_day_rain.dateTime' which is not 
>>>> functionally dependent on columns in GROUP BY clause; this is incompatible 
>>>> with sql_mode=only_full_group_by")*
>>>> Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most 
>>>> recent call last):
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>>> Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>>> Aug 26 13:56:16 localhost weewx[23412]:   self.run()
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen = 
>>>> self.generate(gen_dict[section_name], self.gen_ts)
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>>>> self.generate(section[subsection], gen_ts)
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>>> Aug 26 13:56:16 localhost weewx[23412]:   ngen += 
>>>> self.generate(section[subsection], gen_ts)
>>>> Aug 26 13:56:16 localhost weewx[23412]: File 
>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>>>> Aug 26 13:56:16 localhost weewx[23412]:   
>>>> default_binding)
>>>&

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

[David Hathaway]

Thanks Pat.  I moved the options into weewx.conf after reading that
suggestion.

On Mon, Aug 27, 2018 at 8:03 AM Pat  wrote:

> I'd suggest using the latest release
> <https://github.com/poblabs/weewx-belchertown/releases>. No issues with
> upgrading if all your Belchertown options are within weewx.conf. See the 
> GitHub
> readme <https://github.com/poblabs/weewx-belchertown> for those options.
>
>
> On Monday, August 27, 2018 at 8:50:29 AM UTC-4, David Hathaway wrote:
>>
>> FWIW, the CheetahGenerator issue was caused by the borked upgrade to
>> 3.8.2, which set DataBindings.wx_binding.database to archive_sqlite when I
>> have been using mysql.  I really ought to get a better text compare program
>> for times like this.  UltraCompare is awesome, but Windows.
>>
>> I'm ready to get back to trying Belchertown.  Yay!
>>
>> Pat, are there known issues moving from v 0.1 to whatever is on github
>> now?  (0.4?)  If I am going to try moving forward, it ought to be on the
>> latest codebase, eh?
>>
>> On Monday, August 27, 2018 at 6:26:40 AM UTC-5, David Hathaway wrote:
>>>
>>> Thanks for this Andrew.  It shows great promise.
>>>
>>> Unfortunately, I think there are trickle down issues.  I don't know.
>>> Now I am getting exceptions in weewx.cheetahgenerator.CheetahGenerator in
>>> sqlite.py... but I am running MySQL?  This not a Belchertown error, so I'll
>>> move further conversation about it outside this conversation.
>>>
>>> On Sunday, August 26, 2018 at 8:45:04 PM UTC-5, Andrew Milner wrote:
>>>>
>>>> It looks like this may be an issue with MySQL versions with updates
>>>> from 5.5 to later:
>>>>
>>>>
>>>> https://www.sitepoint.com/quick-tip-how-to-permanently-change-sql-mode-in-mysql/
>>>>
>>>>
>>>>
>>>> On Sunday, 26 August 2018 22:48:43 UTC+3, Pat wrote:
>>>>>
>>>>> I haven't come across this error before. How old is your weewx?
>>>>>
>>>>> On Sunday, August 26, 2018 at 3:01:10 PM UTC-4, David Hathaway wrote:
>>>>>>
>>>>>> I'm having a different error, I believe.  Any ideas on how to sort it
>>>>>> out?
>>>>>>
>>>>>> My weewx is quite old indeed.  Ubuntu 18.04LTS and MySQL.
>>>>>>
>>>>>> I downloaded the version the day you posted it first, so it is v0.1?
>>>>>> Would the later revisions solve the issue?  I think not, since this 
>>>>>> appears
>>>>>> to be a SQL issue.
>>>>>>
>>>>>>
>>>>>> 13:56:15 localhost weewx[23412]: restx: Wunderground-PWS: Published
>>>>>> record 2018-08-26 13:56:00 CDT (1535309760)
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: cheetahgenerator: Generated
>>>>>> 14 files for report StandardReport in 0.78 seconds
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: imagegenerator: Generated 16
>>>>>> images for StandardReport in 0.76 seconds
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: reportengine: Caught
>>>>>> unrecoverable exception in generator 
>>>>>> weewx.cheetahgenerator.CheetahGenerator
>>>>>> Aug 26 13:56:16 localhost weewx[23412]:*   (1055,
>>>>>> "Expression #2 of SELECT list is not in GROUP BY clause and contains
>>>>>> nonaggregated column 'weewx.archive_day_rain.dateTime' which is not
>>>>>> functionally dependent on columns in GROUP BY clause; this is 
>>>>>> incompatible
>>>>>> with sql_mode=only_full_group_by")*
>>>>>> Aug 26 13:56:16 localhost weewx[23412]:   Traceback (most
>>>>>> recent call last):
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: File
>>>>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>>>>> Aug 26 13:56:16 localhost weewx[23412]:   obj.start()
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: File
>>>>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>>>>> Aug 26 13:56:16 localhost weewx[23412]:   self.run()
>>>>>> Aug 26 13:56:16 localhost weewx[23412]: File
>>>>>> "/usr/share/weewx/weewx/cheet

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

[David Hathaway]

I updated MySQL to stop throwing that error, updated to weewx v 3.8.2, and 
installed Belchertown 0.4. Now I get this error:

Aug 27 09:17:16 localhost weewx[4131]: imagegenerator: Generated 16 images 
for StandardReport in 0.75 seconds
Aug 27 09:17:47 localhost weewx[4131]: reportengine: Caught unrecoverable 
exception in generator weewx.cheetahgenerator.CheetahGenerator
Aug 27 09:17:47 localhost weewx[4131]:   start time 
(1535346000) is greater than stop time (1420092000)
Aug 27 09:17:47 localhost weewx[4131]:   Traceback (most recent 
call last):
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Aug 27 09:17:47 localhost weewx[4131]:   obj.start()
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Aug 27 09:17:47 localhost weewx[4131]:   self.run()
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
Aug 27 09:17:47 localhost weewx[4131]:   ngen = 
self.generate(gen_dict[section_name], self.gen_ts)
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 27 09:17:47 localhost weewx[4131]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 27 09:17:47 localhost weewx[4131]:   ngen += 
self.generate(section[subsection], gen_ts)
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
Aug 27 09:17:47 localhost weewx[4131]:   default_binding)
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
Aug 27 09:17:47 localhost weewx[4131]:   searchList += 
obj.get_extension_list(timespan, db_lookup)
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 88, in 
get_extension_list
Aug 27 09:17:47 localhost weewx[4131]:   (time_start_vt, 
time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, 
timespan.stop), 'outTemp')
Aug 27 09:17:47 localhost weewx[4131]: File 
"/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
Aug 27 09:17:47 localhost weewx[4131]:   raise 
ValueError("start time (%d) is greater than stop time (%d)" % (args[0], 
args[1]))
Aug 27 09:17:47 localhost weewx[4131]:   ValueError: start time 
(1535346000) is greater than stop time (1420092000)
Aug 27 09:17:47 localhost weewx[4131]:   Generator terminated
Aug 27 09:17:47 localhost weewx[4131]: copygenerator: copied 1 files to 
/var/www/html/weewx/belchertown


On Monday, August 27, 2018 at 8:35:00 AM UTC-5, David Hathaway wrote:
>
> Thanks Pat.  I moved the options into weewx.conf after reading that 
> suggestion.
>
> On Mon, Aug 27, 2018 at 8:03 AM Pat <> wrote:
>
>> I'd suggest using the latest release 
>> <https://github.com/poblabs/weewx-belchertown/releases>. No issues with 
>> upgrading if all your Belchertown options are within weewx.conf. See the 
>> GitHub 
>> readme <https://github.com/poblabs/weewx-belchertown> for those options. 
>>
>>

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

[David Hathaway]

OK, I will try that and see if that gets the rest going.

On Mon, Aug 27, 2018 at 9:37 AM Pat  wrote:

> Thanks. I'm aware of this error but haven't resolved it yet. It's a
> problem with NOAA reports being generated.
>
> My thought is to move the NOAA reports to another skin, but I'm afraid
> that'll be too much extra work for everyone who installs the skin.
>
> If you want to stop it from happening, open skin.conf and remove the 
> NOAA_month
> and NOAA_year sections - which will get the skin working but will not
> produce the NOAA reports.
>
>
> On Monday, August 27, 2018 at 10:22:23 AM UTC-4, David Hathaway wrote:
>>
>> I updated MySQL to stop throwing that error, updated to weewx v 3.8.2,
>> and installed Belchertown 0.4. Now I get this error:
>>
>> Aug 27 09:17:16 localhost weewx[4131]: imagegenerator: Generated 16
>> images for StandardReport in 0.75 seconds
>> Aug 27 09:17:47 localhost weewx[4131]: reportengine: Caught unrecoverable
>> exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Aug 27 09:17:47 localhost weewx[4131]:   start time
>> (1535346000) is greater than stop time (1420092000)
>> Aug 27 09:17:47 localhost weewx[4131]:   Traceback (most
>> recent call last):
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Aug 27 09:17:47 localhost weewx[4131]:   obj.start()
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Aug 27 09:17:47 localhost weewx[4131]:   self.run()
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>> Aug 27 09:17:47 localhost weewx[4131]:   ngen =
>> self.generate(gen_dict[section_name], self.gen_ts)
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 27 09:17:47 localhost weewx[4131]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 27 09:17:47 localhost weewx[4131]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>> Aug 27 09:17:47 localhost weewx[4131]:   default_binding)
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Aug 27 09:17:47 localhost weewx[4131]:   searchList +=
>> obj.get_extension_list(timespan, db_lookup)
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 88, in
>> get_extension_list
>> Aug 27 09:17:47 localhost weewx[4131]:   (time_start_vt,
>> time_stop_vt, outTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts,
>> timespan.stop), 'outTemp')
>> Aug 27 09:17:47 localhost weewx[4131]: File
>> "/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
>> Aug 27 09:17:47 localhost weewx[4131]:   raise
>> ValueError("start time (%d) is greater than stop time (%d)" % (args[0],
>> args[1]))
>> Aug 27 09:17:47 localhost weewx[4131]:   ValueError: start
>> time (1535346000) is greater than stop time (1420092000)
>> Aug 27 09:17:47 localhost weewx[4131]:   Generator terminated
>> Aug 27 09:17:47 localhost weewx[4131]: copygenerator: copied 1 files to
>> /var/www/html/weewx/belchertown
>>
>>
>> On Monday, August 27, 2018 at 8:35:00 AM UTC-5, David Hathaway wrote:
>>>
>>> Thanks Pat.  I moved the options into weewx.conf after reading that
>>> suggestion.
>>>
>>> On Mon, Aug 27, 2018 at 8:03 AM Pat <> wrote:
>>>
>>>> I'd suggest using the latest release
>>>> <https://github.com/poblabs/weewx-belchertown/releases>. No issues
>>>> with upgrading if all your Belchertown options are within weewx.conf. See
>>>> the GitHub readme <https://github.com/poblabs/weewx-belchertown> for
>>>> those options.
>>>>
>>>> --
>

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

[David Hathaway]

I feel like a problem child at this point.  Maybe I should email you 
directly rather than via this group?  No worries if you want to continue 
this way though.

Commenting out the NOAA reports got it to run...ish.


   - I got a "NoColumnError" in the wind section.  See log below.  I 
   commented out the Wind Records section of the records\index.html.tmpl to 
   continue on.
   - The skin is taking 2 minutes to be generated.  Is this expected?  In 
   contrast, StandardReport takes 0.75 seconds.
   - The resulting page is broken as if it is missing all content.  See it 
   here:  http://dave77459.mynetgear.com/weewx/belchertown/


Aug 27 09:53:16 localhost weewx[22819]: cheetahgenerator: Generated 14 
files for report StandardReport in 1.18 seconds
Aug 27 09:53:17 localhost weewx[22819]: imagegenerator: Generated 16 images 
for StandardReport in 1.54 seconds
Aug 27 09:54:14 localhost weewx[22819]: manager: Added record 2018-08-27 
09:54:00 CDT (1535381640) to database 'weewx'
Aug 27 09:54:14 localhost weewx[22819]: manager: Added record 2018-08-27 
09:54:00 CDT (1535381640) to daily summary in 'weewx'
Aug 27 09:54:14 localhost weewx[22819]: engine: Launch of report thread 
aborted: existing report thread still running
Aug 27 09:54:15 localhost weewx[22819]: restx: Wunderground-PWS: Published 
record 2018-08-27 09:54:00 CDT (1535381640)
Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator: Generate failed 
with exception ''
Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/records/index.html.tmpl
Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator:  Reason: 
(1054, "Unknown column 'wind' in 'where clause'")
Aug 27 09:54:35 localhost weewx[22819]:   Traceback (most recent call 
last):
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Aug 27 09:54:35 localhost weewx[22819]:   print >> _file, 
compiled_template
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Aug 27 09:54:35 localhost weewx[22819]:   rc = getattr(self, 
mainMethName)()
Aug 27 09:54:35 localhost weewx[22819]: File 
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1109, in 
respond
Aug 27 09:54:35 localhost weewx[22819]: File 
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in 
__errorCatcher46
Aug 27 09:54:35 localhost weewx[22819]: File "", line 1, in 

Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
Aug 27 09:54:35 localhost weewx[22819]:   return 
self._do_query(aggregate_type)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/tags.py", line 343, in _do_query
Aug 27 09:54:35 localhost weewx[22819]:   val=val, 
**self.option_dict)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
Aug 27 09:54:35 localhost weewx[22819]:   return 
weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type, 
aggregateType, **option_dict)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/manager.py", line 1249, in getAggregate
Aug 27 09:54:35 localhost weewx[22819]:   **option_dict)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/manager.py", line 458, in getAggregate
Aug 27 09:54:35 localhost weewx[22819]:   _row = 
self.getSql(select_stmt % interpolate_dict)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weewx/manager.py", line 394, in getSql
Aug 27 09:54:35 localhost weewx[22819]:   _cursor.execute(sql, 
sqlargs)
Aug 27 09:54:35 localhost weewx[22819]: File 
"/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
Aug 27 09:54:35 localhost weewx[22819]:   raise klass(e)
Aug 27 09:54:35 localhost weewx[22819]:   NoColumnError: (1054, 
"Unknown column 'wind' in 'where clause'")
Aug 27 09:54:54 localhost weewx[22819]: cheetahgenerator: Generated 13 
files for report Belchertown in 96.59 seconds
Aug 27 09:54:54 localhost weewx[22819]: copygenerator: copied 22 files to 
/var/www/html/weewx/belchertown


On Monday, August 27, 2018 at 9:44:55 AM UTC-5, David Hathaway wrote:
>
> OK, I will try that and see if that gets the rest going.
>
> On Mon, Aug 27, 2018 at 9:37 AM Pat <> wrote:
>
>> Thanks. I'm aware of this error but haven't resolved it yet. It's a 
>> problem with NOAA reports being generated. 
>>
>> My thought is to move the NOAA reports to another

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

[David Hathaway]

Do you mean this section of weewx.conf?

# If you have a website, you may specify an URL
station_url = http://dave77459.mynetgear.com/weewx/

Will that mess up StandardReport?  Heck, I'll try it and see.  Easy to
change back.

I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main drive.
Hardly anything takes time on this system.

I'll give --rebuild-daily a try.  I have a backup from yesterday, but I'll
make another first.


On Mon, Aug 27, 2018 at 10:31 AM Pat  wrote:

> This way is fine. Problems and resolutions can help everyone if it's in
> the public forum.
>
> I think I just resolved the error. In my highcharts Day function I'm
> defining an end point, yet still using the timespan (which causes the
> problem). Moving to my defined end point may have fixed it. Doing some
> testing with it now across a few lab systems to make sure. Then I'll issue
> 0.5 and we can give that a test.
>
> To answer some of your questions:
>
> The link to styles.css file is wrong. To fix this, change your
> weewx.conf's URL to "http://dave77459.mynetgear.com/weewx/belchertown";
> and re-run the report.
>
> The 2 minute generation is for the highcharts section and it does seem
> high. Are you on a Pi? I have 3 years of data in my database and it takes
> 15 seconds to generate on a PC. A pi would be a bit slower.
>
> No column error with wind? Hmm. Not too sure on this. Could be database
> related. You can try to run sudo wee_database --rebuild-daily to rebuild
> the daily values and see if that helps.  Make sure you have a *working backup
> of your database* just in case you need to revert back to it.
>
>
> On Monday, August 27, 2018 at 11:25:07 AM UTC-4, David Hathaway wrote:
>>
>> I feel like a problem child at this point.  Maybe I should email you
>> directly rather than via this group?  No worries if you want to continue
>> this way though.
>>
>> Commenting out the NOAA reports got it to run...ish.
>>
>>
>>- I got a "NoColumnError" in the wind section.  See log below.  I
>>commented out the Wind Records section of the records\index.html.tmpl to
>>continue on.
>>- The skin is taking 2 minutes to be generated.  Is this expected?
>>In contrast, StandardReport takes 0.75 seconds.
>>- The resulting page is broken as if it is missing all content.  See
>>it here:  http://dave77459.mynetgear.com/weewx/belchertown/
>>
>>
>> Aug 27 09:53:16 localhost weewx[22819]: cheetahgenerator: Generated 14
>> files for report StandardReport in 1.18 seconds
>> Aug 27 09:53:17 localhost weewx[22819]: imagegenerator: Generated 16
>> images for StandardReport in 1.54 seconds
>> Aug 27 09:54:14 localhost weewx[22819]: manager: Added record 2018-08-27
>> 09:54:00 CDT (1535381640) to database 'weewx'
>> Aug 27 09:54:14 localhost weewx[22819]: manager: Added record 2018-08-27
>> 09:54:00 CDT (1535381640) to daily summary in 'weewx'
>> Aug 27 09:54:14 localhost weewx[22819]: engine: Launch of report thread
>> aborted: existing report thread still running
>> Aug 27 09:54:15 localhost weewx[22819]: restx: Wunderground-PWS:
>> Published record 2018-08-27 09:54:00 CDT (1535381640)
>> Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator: Generate failed
>> with exception ''
>> Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator:  Ignoring
>> template /etc/weewx/skins/Belchertown/records/index.html.tmpl
>> Aug 27 09:54:35 localhost weewx[22819]: cheetahgenerator:  Reason:
>> (1054, "Unknown column 'wind' in 'where clause'")
>> Aug 27 09:54:35 localhost weewx[22819]:   Traceback (most recent call
>> last):
>> Aug 27 09:54:35 localhost weewx[22819]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>> Aug 27 09:54:35 localhost weewx[22819]:   print >> _file,
>> compiled_template
>> Aug 27 09:54:35 localhost weewx[22819]: File
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
>> __str__
>> Aug 27 09:54:35 localhost weewx[22819]:   rc = getattr(self,
>> mainMethName)()
>> Aug 27 09:54:35 localhost weewx[22819]: File
>> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1109, in
>> respond
>> Aug 27 09:54:35 localhost weewx[22819]: File
>> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in
>> __errorCatcher46
>> Aug 27 09:54:35 localhost weewx[22819]: File "", line 1,
>> in 
>

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

[David Hathaway]

The .tar.gz backup of the database is 71MB.  That is to say, it is big.  It
is possible that it needs tuning, but running a query to create a
cumulative rain table for the past year takes less than a second.  When I
get home, I can investigate further.  Maybe there is a deadlock or
something.

Meanwhile, yay!  It runs and looks nice.
http://dave77459.mynetgear.com/weewx/belchertown/

TO-DO:

   - Figure out the wind records
   - Figure out the server load issue
   - NOAA data when 0.5 comes out
   - Personalize the headings, etc
   - Figure out how to get my smokeping graph to show
   - Figure out how to get pwrstat, which indirectly tracks server loads
   - Update my URL

Thanks for the help!  Many hours of fun ahead. :-)



On Mon, Aug 27, 2018 at 11:06 AM Pat  wrote:

> > Do you mean this section of weewx.conf?
>
> Yep
>
> > Will that mess up StandardReport?
>
> Don't believe so. It will change your URL that is displayed on weewx.com
> if you have register_this_station = true
>
> >  I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
> drive.
>
> So basically a server. Hmm the highcharts do a lot of queries so an
> extended generation time is expected but not sure why it's 2 minutes. Maybe
> your tables needs to be optimized?
>
> There are ways to tune MySQL which may be something to check out too?
>
>
>
> On Monday, August 27, 2018 at 11:58:28 AM UTC-4, David Hathaway wrote:
>>
>> Do you mean this section of weewx.conf?
>>
>> # If you have a website, you may specify an URL
>> station_url = http://dave77459.mynetgear.com/weewx/
>>
>> Will that mess up StandardReport?  Heck, I'll try it and see.  Easy to
>> change back.
>>
>> I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>> drive.  Hardly anything takes time on this system.
>>
>> I'll give --rebuild-daily a try.  I have a backup from yesterday, but
>> I'll make another first.
>>
>>
>> On Mon, Aug 27, 2018 at 10:31 AM Pat  wrote:
>>
>>> This way is fine. Problems and resolutions can help everyone if it's in
>>> the public forum.
>>>
>>> I think I just resolved the error. In my highcharts Day function I'm
>>> defining an end point, yet still using the timespan (which causes the
>>> problem). Moving to my defined end point may have fixed it. Doing some
>>> testing with it now across a few lab systems to make sure. Then I'll issue
>>> 0.5 and we can give that a test.
>>>
>>> To answer some of your questions:
>>>
>>> The link to styles.css file is wrong. To fix this, change your
>>> weewx.conf's URL to "http://dave77459.mynetgear.com/weewx/belchertown";
>>> and re-run the report.
>>>
>>> The 2 minute generation is for the highcharts section and it does seem
>>> high. Are you on a Pi? I have 3 years of data in my database and it takes
>>> 15 seconds to generate on a PC. A pi would be a bit slower.
>>>
>>> No column error with wind? Hmm. Not too sure on this. Could be database
>>> related. You can try to run sudo wee_database --rebuild-daily to
>>> rebuild the daily values and see if that helps.  Make sure you have a 
>>> *working backup
>>> of your database* just in case you need to revert back to it.
>>>
>>>
>>> On Monday, August 27, 2018 at 11:25:07 AM UTC-4, David Hathaway wrote:
>>>>
>>>> I feel like a problem child at this point.  Maybe I should email you
>>>> directly rather than via this group?  No worries if you want to continue
>>>> this way though.
>>>>
>>>> Commenting out the NOAA reports got it to run...ish.
>>>>
>>>>
>>>>- I got a "NoColumnError" in the wind section.  See log below.  I
>>>>commented out the Wind Records section of the records\index.html.tmpl to
>>>>continue on.
>>>>- The skin is taking 2 minutes to be generated.  Is this expected?
>>>>In contrast, StandardReport takes 0.75 seconds.
>>>>- The resulting page is broken as if it is missing all content.
>>>>See it here:  http://dave77459.mynetgear.com/weewx/belchertown/
>>>>
>>>>
>>>> Aug 27 09:53:16 localhost weewx[22819]: cheetahgenerator: Generated 14
>>>> files for report StandardReport in 1.18 seconds
>>>> Aug 27 09:53:17 localhost weewx[22819]: imagegenerator: Generated 16
>>>> images for StandardReport in 1.54 seconds
>>>> Aug 27 09:54:14 localhost weewx[22819]: ma

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

[David Hathaway]

Pat,

If you look at my site and graphs, the year rain is very odd.

http://dave77459.mynetgear.com/weewx/belchertown/graphs/

On the yearly graph, rain is far less than 0.02.  Switch to month, and you
can see it exceeds 1/2" a few days.  I also miss the total rainfall line on
the year graph.

Dave


On Mon, Aug 27, 2018 at 11:24 AM David Hathaway 
wrote:

> The .tar.gz backup of the database is 71MB.  That is to say, it is big.
> It is possible that it needs tuning, but running a query to create a
> cumulative rain table for the past year takes less than a second.  When I
> get home, I can investigate further.  Maybe there is a deadlock or
> something.
>
> Meanwhile, yay!  It runs and looks nice.
> http://dave77459.mynetgear.com/weewx/belchertown/
>
> TO-DO:
>
>- Figure out the wind records
>- Figure out the server load issue
>- NOAA data when 0.5 comes out
>- Personalize the headings, etc
>- Figure out how to get my smokeping graph to show
>- Figure out how to get pwrstat, which indirectly tracks server loads
>- Update my URL
>
> Thanks for the help!  Many hours of fun ahead. :-)
>
>
>
> On Mon, Aug 27, 2018 at 11:06 AM Pat  wrote:
>
>> > Do you mean this section of weewx.conf?
>>
>> Yep
>>
>> > Will that mess up StandardReport?
>>
>> Don't believe so. It will change your URL that is displayed on weewx.com
>> if you have register_this_station = true
>>
>> >  I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>> drive.
>>
>> So basically a server. Hmm the highcharts do a lot of queries so an
>> extended generation time is expected but not sure why it's 2 minutes. Maybe
>> your tables needs to be optimized?
>>
>> There are ways to tune MySQL which may be something to check out too?
>>
>>
>>
>> On Monday, August 27, 2018 at 11:58:28 AM UTC-4, David Hathaway wrote:
>>>
>>> Do you mean this section of weewx.conf?
>>>
>>> # If you have a website, you may specify an URL
>>> station_url = http://dave77459.mynetgear.com/weewx/
>>>
>>> Will that mess up StandardReport?  Heck, I'll try it and see.  Easy to
>>> change back.
>>>
>>> I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>> drive.  Hardly anything takes time on this system.
>>>
>>> I'll give --rebuild-daily a try.  I have a backup from yesterday, but
>>> I'll make another first.
>>>
>>>
>>> On Mon, Aug 27, 2018 at 10:31 AM Pat  wrote:
>>>
>>>> This way is fine. Problems and resolutions can help everyone if it's in
>>>> the public forum.
>>>>
>>>> I think I just resolved the error. In my highcharts Day function I'm
>>>> defining an end point, yet still using the timespan (which causes the
>>>> problem). Moving to my defined end point may have fixed it. Doing some
>>>> testing with it now across a few lab systems to make sure. Then I'll issue
>>>> 0.5 and we can give that a test.
>>>>
>>>> To answer some of your questions:
>>>>
>>>> The link to styles.css file is wrong. To fix this, change your
>>>> weewx.conf's URL to "http://dave77459.mynetgear.com/weewx/belchertown";
>>>> and re-run the report.
>>>>
>>>> The 2 minute generation is for the highcharts section and it does seem
>>>> high. Are you on a Pi? I have 3 years of data in my database and it takes
>>>> 15 seconds to generate on a PC. A pi would be a bit slower.
>>>>
>>>> No column error with wind? Hmm. Not too sure on this. Could be database
>>>> related. You can try to run sudo wee_database --rebuild-daily to
>>>> rebuild the daily values and see if that helps.  Make sure you have a 
>>>> *working backup
>>>> of your database* just in case you need to revert back to it.
>>>>
>>>>
>>>> On Monday, August 27, 2018 at 11:25:07 AM UTC-4, David Hathaway wrote:
>>>>>
>>>>> I feel like a problem child at this point.  Maybe I should email you
>>>>> directly rather than via this group?  No worries if you want to continue
>>>>> this way though.
>>>>>
>>>>> Commenting out the NOAA reports got it to run...ish.
>>>>>
>>>>>
>>>>>- I got a "NoColumnError" in the wind section.  See log below.  I
>>>>>commented out the Wind Records se

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

[David Hathaway]

[StdArchive]

# If the station hardware supports data logging then the archive
interval
# will be downloaded from the station. Otherwise, specify it (in
seconds).
archive_interval = 60

On Mon, Aug 27, 2018 at 11:36 AM Pat  wrote:

> The year graph don't total like the others, just shows you which days had
> rain. That being said your year.json is HUGE at 8mb (by contrast my
> year.json is 231kb). I wonder why yours is so big? This is why your report
> generation is so slow. Month and Year look rather large.
>
> How often are you doing archive? weewx.conf StdArchive.archive_interval
>
> On Monday, August 27, 2018 at 12:29:26 PM UTC-4, David Hathaway wrote:
>>
>> Pat,
>>
>> If you look at my site and graphs, the year rain is very odd.
>>
>> http://dave77459.mynetgear.com/weewx/belchertown/graphs/
>>
>> On the yearly graph, rain is far less than 0.02.  Switch to month, and
>> you can see it exceeds 1/2" a few days.  I also miss the total rainfall
>> line on the year graph.
>>
>> Dave
>>
>>
>> On Mon, Aug 27, 2018 at 11:24 AM David Hathaway 
>> wrote:
>>
>>> The .tar.gz backup of the database is 71MB.  That is to say, it is big.
>>> It is possible that it needs tuning, but running a query to create a
>>> cumulative rain table for the past year takes less than a second.  When I
>>> get home, I can investigate further.  Maybe there is a deadlock or
>>> something.
>>>
>>> Meanwhile, yay!  It runs and looks nice.
>>> http://dave77459.mynetgear.com/weewx/belchertown/
>>>
>>> TO-DO:
>>>
>>>- Figure out the wind records
>>>- Figure out the server load issue
>>>- NOAA data when 0.5 comes out
>>>- Personalize the headings, etc
>>>- Figure out how to get my smokeping graph to show
>>>- Figure out how to get pwrstat, which indirectly tracks server loads
>>>- Update my URL
>>>
>>> Thanks for the help!  Many hours of fun ahead. :-)
>>>
>>>
>>>
>>> On Mon, Aug 27, 2018 at 11:06 AM Pat  wrote:
>>>
>>>> > Do you mean this section of weewx.conf?
>>>>
>>>> Yep
>>>>
>>>> > Will that mess up StandardReport?
>>>>
>>>> Don't believe so. It will change your URL that is displayed on
>>>> weewx.com if you have register_this_station = true
>>>>
>>>> >  I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>>> drive.
>>>>
>>>> So basically a server. Hmm the highcharts do a lot of queries so an
>>>> extended generation time is expected but not sure why it's 2 minutes. Maybe
>>>> your tables needs to be optimized?
>>>>
>>>> There are ways to tune MySQL which may be something to check out too?
>>>>
>>>>
>>>>
>>>> On Monday, August 27, 2018 at 11:58:28 AM UTC-4, David Hathaway wrote:
>>>>>
>>>>> Do you mean this section of weewx.conf?
>>>>>
>>>>> # If you have a website, you may specify an URL
>>>>> station_url = http://dave77459.mynetgear.com/weewx/
>>>>>
>>>>> Will that mess up StandardReport?  Heck, I'll try it and see.  Easy to
>>>>> change back.
>>>>>
>>>>> I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>>>> drive.  Hardly anything takes time on this system.
>>>>>
>>>>> I'll give --rebuild-daily a try.  I have a backup from yesterday, but
>>>>> I'll make another first.
>>>>>
>>>>>
>>>>> On Mon, Aug 27, 2018 at 10:31 AM Pat  wrote:
>>>>>
>>>>>> This way is fine. Problems and resolutions can help everyone if it's
>>>>>> in the public forum.
>>>>>>
>>>>>> I think I just resolved the error. In my highcharts Day function I'm
>>>>>> defining an end point, yet still using the timespan (which causes the
>>>>>> problem). Moving to my defined end point may have fixed it. Doing some
>>>>>> testing with it now across a few lab systems to make sure. Then I'll 
>>>>>> issue
>>>>>> 0.5 and we can give that a test.
>>>>>>
>>>>>> To answer some of your questions:
>>>>>>
>>>>>> The link to styles.css file is wrong. To f

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

[David Hathaway]

I guess your month and year data doesn't use the daily records instead of
the interval ones?

At least I know why it is so slow then.

On Mon, Aug 27, 2018 at 11:47 AM Pat  wrote:

> Ah, that'll do it. Explains why your database is so large and why it takes
> a while to generate the graph json files. That's a lot of records to
> process when generating the graphs.
>
> You may want to consider going to 300 seconds for archive which is the 
> aggregation
> of the loops during those 300 seconds
> <http://www.weewx.com/docs/customizing.htm#_LOOP_packets_vs._archive_records___>.
> Up to you though, it's your data.
>
> Changing it now won't cure the size and slowness issues though. Suppose
> you could run a database query to drop any dateTime from archive that isn't
> on a 5 minute interval (0, 5, 10, 15, etc).
>
> Don't know if Tom or Matthew have another way.
>
>
>
> On Monday, August 27, 2018 at 12:40:15 PM UTC-4, David Hathaway wrote:
>>
>> [StdArchive]
>>
>> # If the station hardware supports data logging then the archive
>> interval
>> # will be downloaded from the station. Otherwise, specify it (in
>> seconds).
>> archive_interval = 60
>>
>> On Mon, Aug 27, 2018 at 11:36 AM Pat  wrote:
>>
>>> The year graph don't total like the others, just shows you which days
>>> had rain. That being said your year.json is HUGE at 8mb (by contrast my
>>> year.json is 231kb). I wonder why yours is so big? This is why your report
>>> generation is so slow. Month and Year look rather large.
>>>
>>> How often are you doing archive? weewx.conf StdArchive.archive_interval
>>>
>>> On Monday, August 27, 2018 at 12:29:26 PM UTC-4, David Hathaway wrote:
>>>>
>>>> Pat,
>>>>
>>>> If you look at my site and graphs, the year rain is very odd.
>>>>
>>>> http://dave77459.mynetgear.com/weewx/belchertown/graphs/
>>>>
>>>> On the yearly graph, rain is far less than 0.02.  Switch to month, and
>>>> you can see it exceeds 1/2" a few days.  I also miss the total rainfall
>>>> line on the year graph.
>>>>
>>>> Dave
>>>>
>>>>
>>>> On Mon, Aug 27, 2018 at 11:24 AM David Hathaway 
>>>> wrote:
>>>>
>>>>> The .tar.gz backup of the database is 71MB.  That is to say, it is
>>>>> big.  It is possible that it needs tuning, but running a query to create a
>>>>> cumulative rain table for the past year takes less than a second.  When I
>>>>> get home, I can investigate further.  Maybe there is a deadlock or
>>>>> something.
>>>>>
>>>>> Meanwhile, yay!  It runs and looks nice.
>>>>> http://dave77459.mynetgear.com/weewx/belchertown/
>>>>>
>>>>> TO-DO:
>>>>>
>>>>>- Figure out the wind records
>>>>>- Figure out the server load issue
>>>>>- NOAA data when 0.5 comes out
>>>>>- Personalize the headings, etc
>>>>>- Figure out how to get my smokeping graph to show
>>>>>- Figure out how to get pwrstat, which indirectly tracks server
>>>>>loads
>>>>>- Update my URL
>>>>>
>>>>> Thanks for the help!  Many hours of fun ahead. :-)
>>>>>
>>>>>
>>>>>
>>>>> On Mon, Aug 27, 2018 at 11:06 AM Pat  wrote:
>>>>>
>>>>>> > Do you mean this section of weewx.conf?
>>>>>>
>>>>>> Yep
>>>>>>
>>>>>> > Will that mess up StandardReport?
>>>>>>
>>>>>> Don't believe so. It will change your URL that is displayed on
>>>>>> weewx.com if you have register_this_station = true
>>>>>>
>>>>>> >  I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>>>>> drive.
>>>>>>
>>>>>> So basically a server. Hmm the highcharts do a lot of queries so
>>>>>> an extended generation time is expected but not sure why it's 2 minutes.
>>>>>> Maybe your tables needs to be optimized?
>>>>>>
>>>>>> There are ways to tune MySQL which may be something to check out too?
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Monday, August 

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

[David Hathaway]

Phillip,

That would explain why I see Dallas on the map... I use a private VPN at
work that connects to the net from Dallas.  I thought that was maybe where
the regional radar emanated.  Thanks for pointing this out.

I'm attaching the "Day sensors" plot which I repurposed to show my
electrical power load; you can see the influence of having this skin
active.  My fault for the short archive window, but it does show.

Dave




On Mon, Aug 27, 2018 at 4:42 PM Philip Kutzenco  wrote:

> David and Pat,
>
> When I go to David's site, his Windy.Com display is centered on my
> location, not his. See the png file I attached. I first thought David was
> my close neighbor, but I think Sugar Land, TX is pretty far away from
> Western North Carolina :-).
>
> I think I saw an earlier post by someone else who noted a similar
> issue.Windy.com is updating in realtime using info from the site running
> the browser. Is there a way that can be resolved?
>
> I hope to work on getting Pat's awesome skin set up for me in the near
> future.
>
> On Monday, August 27, 2018 at 12:24:39 PM UTC-4, David Hathaway wrote:
>>
>> The .tar.gz backup of the database is 71MB.  That is to say, it is big.
>> It is possible that it needs tuning, but running a query to create a
>> cumulative rain table for the past year takes less than a second.  When I
>> get home, I can investigate further.  Maybe there is a deadlock or
>> something.
>> Meanwhile, yay!  It runs and looks nice.
>> http://dave77459.mynetgear.com/weewx/belchertown/
>>
>> TO-DO:
>>
>>- Figure out the wind records
>>- Figure out the server load issue
>>- NOAA data when 0.5 comes out
>>- Personalize the headings, etc
>>- Figure out how to get my smokeping graph to show
>>- Figure out how to get pwrstat, which indirectly tracks server loads
>>- Update my URL
>>
>> Thanks for the help!  Many hours of fun ahead. :-)
>>
>>
>>
>> On Mon, Aug 27, 2018 at 11:06 AM Pat  wrote:
>>
>>> > Do you mean this section of weewx.conf?
>>>
>>> Yep
>>>
>>> > Will that mess up StandardReport?
>>>
>>> Don't believe so. It will change your URL that is displayed on weewx.com
>>> if you have register_this_station = true
>>>
>>> >  I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>> drive.
>>>
>>> So basically a server. Hmm the highcharts do a lot of queries so an
>>> extended generation time is expected but not sure why it's 2 minutes. Maybe
>>> your tables needs to be optimized?
>>>
>>> There are ways to tune MySQL which may be something to check out too?
>>>
>>>
>>>
>>> On Monday, August 27, 2018 at 11:58:28 AM UTC-4, David Hathaway wrote:
>>>>
>>>> Do you mean this section of weewx.conf?
>>>>
>>>> # If you have a website, you may specify an URL
>>>> station_url = http://dave77459.mynetgear.com/weewx/
>>>>
>>>> Will that mess up StandardReport?  Heck, I'll try it and see.  Easy to
>>>> change back.
>>>>
>>>> I am on a quad core Xeon CPU at 3.30Ghz, 16GB RAM, and an SSD main
>>>> drive.  Hardly anything takes time on this system.
>>>>
>>>> I'll give --rebuild-daily a try.  I have a backup from yesterday, but
>>>> I'll make another first.
>>>>
>>>>
>>>> On Mon, Aug 27, 2018 at 10:31 AM Pat  wrote:
>>>>
>>>>> This way is fine. Problems and resolutions can help everyone if it's
>>>>> in the public forum.
>>>>>
>>>>> I think I just resolved the error. In my highcharts Day function I'm
>>>>> defining an end point, yet still using the timespan (which causes the
>>>>> problem). Moving to my defined end point may have fixed it. Doing some
>>>>> testing with it now across a few lab systems to make sure. Then I'll issue
>>>>> 0.5 and we can give that a test.
>>>>>
>>>>> To answer some of your questions:
>>>>>
>>>>> The link to styles.css file is wrong. To fix this, change your
>>>>> weewx.conf's URL to "http://dave77459.mynetgear.com/weewx/belchertown";
>>>>> and re-run the report.
>>>>>
>>>>> The 2 minute generation is for the highcharts section and it does seem
>>>>> high. Are you on a Pi? I have 3 years of data in my database 

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

[David Hathaway]

Was about to report this very issue.  So "me too"

Aug 28 06:03:18 localhost weewx[4973]: imagegenerator: Generated 16 images
for StandardReport in 0.78 seconds
Aug 28 06:03:50 localhost weewx[4973]: reportengine: Caught unrecoverable
exception in generator weewx.cheetahgenerator.CheetahGenerator
Aug 28 06:03:50 localhost weewx[4973]:   a float is required
Aug 28 06:03:50 localhost weewx[4973]:   Traceback (most recent
call last):
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/reportengine.py", line 239, in run
Aug 28 06:03:50 localhost weewx[4973]:   obj.start()
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/reportengine.py", line 273, in start
Aug 28 06:03:50 localhost weewx[4973]:   self.run()
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
Aug 28 06:03:50 localhost weewx[4973]:   ngen =
self.generate(gen_dict[section_name], self.gen_ts)
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
self.generate(section[subsection], gen_ts)
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
Aug 28 06:03:50 localhost weewx[4973]:   default_binding)
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
Aug 28 06:03:50 localhost weewx[4973]:   searchList +=
obj.get_extension_list(timespan, db_lookup)
Aug 28 06:03:50 localhost weewx[4973]: File
"/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 440, in
get_extension_list
Aug 28 06:03:50 localhost weewx[4973]:   rain_round.append(
round( rainsql[1], 2) )
Aug 28 06:03:50 localhost weewx[4973]:   TypeError: a float is
required
Aug 28 06:03:50 localhost weewx[4973]:   Generator terminated
Aug 28 06:03:50 localhost weewx[4973]: copygenerator: copied 1 files to
/var/www/html/weewx/belchertown


On Tue, Aug 28, 2018 at 12:47 AM Juan Antonio Mosquera <
juanantoniomosqu...@juanantoniomosquera.com> wrote:

> Hi.
>
> New problem now.
>
>
> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Running report
> Belchertown
> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Found
> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
> Belchertown
> Aug 28 07:42:34 meteomontaos weewx[17746]: cheetahgenerator: using search
> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
> 'user.belchertown.getAllStats', 'user.belchertown.getForecast',
> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata',
> 'user.belchertown.getSocialShare',
> 'user.belchertown_highchartsSearchX.highchartsDay',
> 'user.belchertown_highchartsSearchX.highchartsWeek',
> 'user.belchertown_highchartsSearchX.highchartsMonth',
> 'user.belchertown_highchartsSearchX.highchartsYear']
> Aug 28 07:42:35 meteomontaos weewx[17746]: manager: Daily summary version
> is 2.0
> Aug 28 07:42:46 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:43:08 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:43:15 meteomontaos sudo[19974]: pam_unix(sudo:session): session
> closed for user root
> Aug 28 07:44:31 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:44:52 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:45:12 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:45:32 meteomontaos weewx[17746]: wmr300: dump history is disabled
> Aug 28 07:45:39 meteomontaos weewx[17746]: reportengine: Caught
> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 28 07:45:39 meteomontaos weewx[17746]:   a float is required
> Aug 28 07:45:39 meteomontaos weewx[17746]:   Traceback (most recent
> call last):
> Aug 28 07:45:39 meteomontaos weewx[17746]: File
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Aug 28 07:45:39 meteomontaos weewx[17746]:   obj.start()
> Aug 28 07:45:39 meteomontaos weewx[17746]: File
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Aug 28 07:45:39 meteomontaos weewx[17746]:   self.run()
> Aug 28 07:45:39 meteomontaos weewx[17746]: File
> "/usr/share/weewx/weewx/cheetahgenerato

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

[David Hathaway]

Pat,

What config settings to comment out now to get past this issue for the
moment?

Dave

On Tue, Aug 28, 2018 at 6:06 AM David Hathaway 
wrote:

> Was about to report this very issue.  So "me too"
>
> Aug 28 06:03:18 localhost weewx[4973]: imagegenerator: Generated 16 images
> for StandardReport in 0.78 seconds
> Aug 28 06:03:50 localhost weewx[4973]: reportengine: Caught unrecoverable
> exception in generator weewx.cheetahgenerator.CheetahGenerator
> Aug 28 06:03:50 localhost weewx[4973]:   a float is required
> Aug 28 06:03:50 localhost weewx[4973]:   Traceback (most
> recent call last):
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
> Aug 28 06:03:50 localhost weewx[4973]:   obj.start()
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
> Aug 28 06:03:50 localhost weewx[4973]:   self.run()
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
> Aug 28 06:03:50 localhost weewx[4973]:   ngen =
> self.generate(gen_dict[section_name], self.gen_ts)
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
> self.generate(section[subsection], gen_ts)
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
> Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
> self.generate(section[subsection], gen_ts)
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
> Aug 28 06:03:50 localhost weewx[4973]:   default_binding)
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
> Aug 28 06:03:50 localhost weewx[4973]:   searchList +=
> obj.get_extension_list(timespan, db_lookup)
> Aug 28 06:03:50 localhost weewx[4973]: File
> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 440, in
> get_extension_list
> Aug 28 06:03:50 localhost weewx[4973]: 
> rain_round.append( round( rainsql[1], 2) )
> Aug 28 06:03:50 localhost weewx[4973]:   TypeError: a float is
> required
> Aug 28 06:03:50 localhost weewx[4973]:   Generator terminated
> Aug 28 06:03:50 localhost weewx[4973]: copygenerator: copied 1 files to
> /var/www/html/weewx/belchertown
>
>
> On Tue, Aug 28, 2018 at 12:47 AM Juan Antonio Mosquera <
> juanantoniomosqu...@juanantoniomosquera.com> wrote:
>
>> Hi.
>>
>> New problem now.
>>
>>
>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Running report
>> Belchertown
>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Found
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
>> Belchertown
>> Aug 28 07:42:34 meteomontaos weewx[17746]: cheetahgenerator: using search
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
>> 'user.belchertown.getAllStats', 'user.belchertown.getForecast',
>> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata',
>> 'user.belchertown.getSocialShare',
>> 'user.belchertown_highchartsSearchX.highchartsDay',
>> 'user.belchertown_highchartsSearchX.highchartsWeek',
>> 'user.belchertown_highchartsSearchX.highchartsMonth',
>> 'user.belchertown_highchartsSearchX.highchartsYear']
>> Aug 28 07:42:35 meteomontaos weewx[17746]: manager: Daily summary version
>> is 2.0
>> Aug 28 07:42:46 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:43:08 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:43:15 meteomontaos sudo[19974]: pam_unix(sudo:session): session
>> closed for user root
>> Aug 28 07:44:31 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:44:52 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:45:12 meteomontaos weewx[17

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

[David Hathaway]

Hi Pat,

Which archive is this an issue?  I just set all rain to 0 in archive where
they were null (23000 rows).  Still crashing.

Dave


On Tue, Aug 28, 2018 at 5:55 AM Pat  wrote:

> Hi Juan, I think I've seen this before when rain values are NULL in the
> archive. Let me see if I can update the query to work around that
>
> On Tuesday, August 28, 2018 at 1:47:06 AM UTC-4, Juan Antonio Mosquera
> wrote:
>>
>> Hi.
>>
>> New problem now.
>>
>>
>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Running report
>> Belchertown
>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Found
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
>> Belchertown
>> Aug 28 07:42:34 meteomontaos weewx[17746]: cheetahgenerator: using search
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
>> 'user.belchertown.getAllStats', 'user.belchertown.getForecast',
>> 'user.belchertown.getEarthquake', 'user.belchertown.getNOAAdata',
>> 'user.belchertown.getSocialShare',
>> 'user.belchertown_highchartsSearchX.highchartsDay',
>> 'user.belchertown_highchartsSearchX.highchartsWeek',
>> 'user.belchertown_highchartsSearchX.highchartsMonth',
>> 'user.belchertown_highchartsSearchX.highchartsYear']
>> Aug 28 07:42:35 meteomontaos weewx[17746]: manager: Daily summary version
>> is 2.0
>> Aug 28 07:42:46 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:43:08 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:43:15 meteomontaos sudo[19974]: pam_unix(sudo:session): session
>> closed for user root
>> Aug 28 07:44:31 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:44:52 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:45:12 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:45:32 meteomontaos weewx[17746]: wmr300: dump history is
>> disabled
>> Aug 28 07:45:39 meteomontaos weewx[17746]: reportengine: Caught
>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   a float is required
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   Traceback (most recent
>> call last):
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   obj.start()
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   self.run()
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   ngen =
>> self.generate(gen_dict[section_name], self.gen_ts)
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   ngen +=
>> self.generate(section[subsection], gen_ts)
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   default_binding)
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   searchList +=
>> obj.get_extension_list(timespan, db_lookup)
>> Aug 28 07:45:39 meteomontaos weewx[17746]: File
>> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 440, in
>> get_extension_list
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   rain_round.append(
>> round( rainsql[1], 2) )
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   TypeError: a float is
>> required
>> Aug 28 07:45:39 meteomontaos weewx[17746]:   Generator terminated
>> Aug 28 07:45:39 meteomontaos weewx[17746]: copygenerator: copied 22 files
>> to /var/www/html/weewx/belchertown
>>
>>
>>
>> Greetings and thanks.
>>
>> El martes, 28 de agosto de 2018, 3:16:41 (UTC+2), Pat escribió:
>>>
>>> Belchertown skin 0.5 is released
>>> .
>>>
>>> This should fix the NOAA reports and day charts. Tested it against
>>> sqlite and mysql, and in a couple different timezones. Please let me know
>>> if it persists.
>>>
>>> Few other fixes and updates listed in the release notes.
>>>
>> --
> You received this message because you are subscribed to a topic in the
> Google Gro

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

[David Hathaway]

Excellent, thanks!

On Tue, Aug 28, 2018 at 6:14 AM Pat  wrote:

> You could set highcharts_enabled = 0 for the time being. I should have a
> test soon then can send you guys the file to try it yourself before I
> publish a release.
>
>
> On Tuesday, August 28, 2018 at 7:08:32 AM UTC-4, David Hathaway wrote:
>>
>> Pat,
>>
>> What config settings to comment out now to get past this issue for the
>> moment?
>>
>> Dave
>>
>> On Tue, Aug 28, 2018 at 6:06 AM David Hathaway 
>> wrote:
>>
>>> Was about to report this very issue.  So "me too"
>>>
>>> Aug 28 06:03:18 localhost weewx[4973]: imagegenerator: Generated 16
>>> images for StandardReport in 0.78 seconds
>>> Aug 28 06:03:50 localhost weewx[4973]: reportengine: Caught
>>> unrecoverable exception in generator weewx.cheetahgenerator.CheetahGenerator
>>> Aug 28 06:03:50 localhost weewx[4973]:   a float is required
>>> Aug 28 06:03:50 localhost weewx[4973]:   Traceback (most
>>> recent call last):
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/reportengine.py", line 239, in run
>>> Aug 28 06:03:50 localhost weewx[4973]:   obj.start()
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/reportengine.py", line 273, in start
>>> Aug 28 06:03:50 localhost weewx[4973]:   self.run()
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>>> Aug 28 06:03:50 localhost weewx[4973]:   ngen =
>>> self.generate(gen_dict[section_name], self.gen_ts)
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>> Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
>>> self.generate(section[subsection], gen_ts)
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>> Aug 28 06:03:50 localhost weewx[4973]:   ngen +=
>>> self.generate(section[subsection], gen_ts)
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>>> Aug 28 06:03:50 localhost weewx[4973]:   default_binding)
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in _getSearchList
>>> Aug 28 06:03:50 localhost weewx[4973]:   searchList +=
>>> obj.get_extension_list(timespan, db_lookup)
>>> Aug 28 06:03:50 localhost weewx[4973]: File
>>> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 440, in
>>> get_extension_list
>>> Aug 28 06:03:50 localhost weewx[4973]: 
>>> rain_round.append( round( rainsql[1], 2) )
>>> Aug 28 06:03:50 localhost weewx[4973]:   TypeError: a float
>>> is required
>>> Aug 28 06:03:50 localhost weewx[4973]:   Generator terminated
>>> Aug 28 06:03:50 localhost weewx[4973]: copygenerator: copied 1 files to
>>> /var/www/html/weewx/belchertown
>>>
>>>
>>> On Tue, Aug 28, 2018 at 12:47 AM Juan Antonio Mosquera <
>>> juananton...@juanantoniomosquera.com> wrote:
>>>
>>>> Hi.
>>>>
>>>> New problem now.
>>>>
>>>>
>>>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Running report
>>>> Belchertown
>>>> Aug 28 07:42:34 meteomontaos weewx[17746]: reportengine: Found
>>>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
>>>> Belchertown
>>>> Aug 28 07:42:34 meteomontaos weewx[17746]: cheetahgenerator: using
>>>> search list ['weewx.cheetahgenerator.Almanac',
>>>> 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current',
>>>> 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo',
>>>> 'weewx.cheetahgenerator.Extras', 'user.belchertown.getAllStats',
>>>> 'user.belchertown.getForecast', 'user.belchertown.getEarthquake',
>>>> 'user.belchertown.getNOAAdata', 'user.belchertown.getSocialShare&#

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

[David Hathaway]

Hi Pat,

I updated.  If anyone is following along, belchertown_highchartsSearchX.py
went into /usr/share/weewx/user .

I have the following error, but I am not sure where I would see a hole?

Aug 28 08:53:46 localhost weewx[10317]: cheetahgenerator: Generate failed
with exception ''
Aug 28 08:53:46 localhost weewx[10317]: cheetahgenerator:  Ignoring
template /etc/weewx/skins/Belchertown/records/index.html.tmpl
Aug 28 08:53:46 localhost weewx[10317]: cheetahgenerator:  Reason:
(1054, "Unknown column 'wind' in 'where clause'")
Aug 28 08:53:46 localhost weewx[10317]:   Traceback (most recent call
last):
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Aug 28 08:53:46 localhost weewx[10317]:   print >> _file,
compiled_template
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
__str__
Aug 28 08:53:46 localhost weewx[10317]:   rc = getattr(self,
mainMethName)()
Aug 28 08:53:46 localhost weewx[10317]: File
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1109, in
respond
Aug 28 08:53:46 localhost weewx[10317]: File
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in
__errorCatcher46
Aug 28 08:53:46 localhost weewx[10317]: File "", line 1, in

Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
Aug 28 08:53:46 localhost weewx[10317]:   return
self._do_query(aggregate_type)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/tags.py", line 343, in _do_query
Aug 28 08:53:46 localhost weewx[10317]:   val=val,
**self.option_dict)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
Aug 28 08:53:46 localhost weewx[10317]:   return
weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type,
aggregateType, **option_dict)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/manager.py", line 1249, in getAggregate
Aug 28 08:53:46 localhost weewx[10317]:   **option_dict)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/manager.py", line 458, in getAggregate
Aug 28 08:53:46 localhost weewx[10317]:   _row =
self.getSql(select_stmt % interpolate_dict)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weewx/manager.py", line 394, in getSql
Aug 28 08:53:46 localhost weewx[10317]:   _cursor.execute(sql,
sqlargs)
Aug 28 08:53:46 localhost weewx[10317]: File
"/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
Aug 28 08:53:46 localhost weewx[10317]:   raise klass(e)
Aug 28 08:53:46 localhost weewx[10317]:   NoColumnError: (1054,
"Unknown column 'wind' in 'where clause'")
Aug 28 08:54:05 localhost weewx[10317]: cheetahgenerator: Generated 15
files for report Belchertown in 108.92 seconds
Aug 28 08:54:05 localhost weewx[10317]: copygenerator: copied 1 files to
/var/www/html/weewx/belchertown

On Tue, Aug 28, 2018 at 7:43 AM Pat  wrote:

> Juan, David, give this attached file a try.
>
> I set a rain value in the archive table to NULL and saw it fail on MySQL
> and sqlite.
>
> Updated file skips NULL values
>
> Place it into your bin/user folder replacing the old one. Restart weewx,
> then either wait for an archive to happen, or run sudo wee_reports and
> let me know the results.
>
> Make sure you turn highcharts_enabled back to 1 to enable it.
>
>
>
> On Tuesday, August 28, 2018 at 7:16:32 AM UTC-4, David Hathaway wrote:
>>
>> Excellent, thanks!
>>
>> On Tue, Aug 28, 2018 at 6:14 AM Pat  wrote:
>>
>>> You could set highcharts_enabled = 0 for the time being. I should have
>>> a test soon then can send you guys the file to try it yourself before I
>>> publish a release.
>>>
>>>
>>> On Tuesday, August 28, 2018 at 7:08:32 AM UTC-4, David Hathaway wrote:
>>>>
>>>> Pat,
>>>>
>>>> What config settings to comment out now to get past this issue for the
>>>> moment?
>>>>
>>>> Dave
>>>>
>>>> On Tue, Aug 28, 2018 at 6:06 AM David Hathaway 
>>>> wrote:
>>>>
>>>>> Was about to report this very issue.  So "me too"
>>>>>
>>>>> Aug 28 06:03:18 localhost weewx[4973]: imagegenerator: Generated 16
>>>>> images for StandardReport in 0.78 seconds
>>>>> Aug 28 06:03:50 localhost weewx[4973]:

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

[David Hathaway]

The radar works for you?

On Tue, Aug 28, 2018 at 5:57 PM Colin Larsen  wrote:

> Actually, just clicked on your link and it works fine for me :)
>
> On Wed, Aug 29, 2018 at 10:58 AM Colin Larsen 
> wrote:
>
>> Could be the  size, try width=650 height=360? That was the
>> original size in the template I think and that's also what I specified in
>> the widget generator on the Windy website
>>
>>
>>
>>
>> On Wed, Aug 29, 2018 at 10:47 AM David Hathaway 
>> wrote:
>>
>>> Am I the only one whose windy radar graph doesn't show?  It said
>>> something about being logged off briefly, then went away.  However, if I
>>> look at the source and clock the link, it appears.  Inspection image
>>> follows.
>>>
>>>
>>> https://embed.windy.com/embed2.html?lat=29.690&lon=-95.625&zoom=9&level=surface&overlay=radar&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&detailLat=29.625&detailLon=-95.627&metricWind=default&metricTemp=default&radarRange=-1
>>>
>>> Oh, BTW, today I did a long-delayed task and got a custom domain,
>>> houston.house (didn't know that .house was a thing until recently).  So if
>>> you want to visit the page, soon only the following will work:
>>>
>>> http://www.hathaway.house/weewx/belchertown/
>>>
>>> Other things I have noticed...
>>>
>>> Month Rain Highest Rate shows as 0.07 in
>>>
>>> However, the standard skin reports 4.97 in, and the rainRate field in
>>> the archive table shows,
>>>
>>> '2018-08-11 18:56:00', '0.674193548387097'
>>> '2018-08-11 18:57:00', '2.85193548387097'
>>> '2018-08-11 18:58:00', '2.17645161290323'
>>> '2018-08-11 18:59:00', '0.759677419354838'
>>> '2018-08-11 19:00:00', '0.686129032258064'
>>> '2018-08-11 19:01:00', '3.26612903225806'
>>> '2018-08-11 19:02:00', '4.52290322580645'
>>> '2018-08-11 19:03:00', '0.998709677419355'
>>> '2018-08-11 19:04:00', '3.04032258064516'
>>> '2018-08-11 19:05:00', '1.28258064516129'
>>>
>>> Looks like more than 0.07 in.
>>>
>>> The records page probably reflects bad data.  However, I'm not sure the
>>> barometer never was -18.6F.  This looks like it is using the lowest
>>> dewpoint field instead, units included,
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Aug 28, 2018 at 5:06 PM Colin Larsen 
>>> wrote:
>>>
>>>> I hate to add more .. this may be just a question
>>>>
>>>> Currently the rain graph says there has been 0.51 mm rain today as does
>>>> the data just to the right of the current temp on the main page.
>>>>
>>>> However this info box says 5.1mm
>>>>
>>>> Today, Wednesday, August 29, 2018
>>>> High: 21.1 °C Low: -0.7 °C
>>>> Highest Wind: 8 km/h Highest UV: 10.2
>>>> Today's Rain: 5.1 mm Highest Rate: 0.3 mm
>>>>
>>>> Is that just hourly versus accumulated for the day?? It's a bit hard
>>>> only running the simulator as I have no hard data to error check
>>>>
>>>> On Wed, Aug 29, 2018 at 9:52 AM Pat O'Brien 
>>>> wrote:
>>>>
>>>>> Good catch! I wonder if there's a way around that on upgrades.
>>>>>
>>>>> On Tue, Aug 28, 2018, 5:42 PM Colin Larsen 
>>>>> wrote:
>>>>>
>>>>>> Something to watch - the 'about.inc' is also overwritten, so if you
>>>>>> have lots of goodies modified in that it will go back to the vanilla
>>>>>> install page when you do an update :) Might pay to backup all the skins
>>>>>> directory not just conf files
>>>>>>
>>>>>> On Wed, Aug 29, 2018 at 7:31 AM Colin Larsen 
>>>>>> wrote:
>>>>>>
>>>>>>> Yes quite probably. I might just shorten the update time and monitor
>>>>>>> it - I don't think I'll crash over the allowance at this stage.
>>>>>>>
>>>>>>> Cheers
>>>>>>>
>>>>>>> 

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

[David Hathaway]

Huh, works on my phone too.  Aha!  Privacy Badger from EFF is blocking it.
Thanks Colin for the confirmation. :)

On Tue, Aug 28, 2018 at 6:11 PM David Hathaway 
wrote:

> The radar works for you?
>
> On Tue, Aug 28, 2018 at 5:57 PM Colin Larsen 
> wrote:
>
>> Actually, just clicked on your link and it works fine for me :)
>>
>> On Wed, Aug 29, 2018 at 10:58 AM Colin Larsen 
>> wrote:
>>
>>> Could be the  size, try width=650 height=360? That was the
>>> original size in the template I think and that's also what I specified in
>>> the widget generator on the Windy website
>>>
>>>
>>>
>>>
>>> On Wed, Aug 29, 2018 at 10:47 AM David Hathaway 
>>> wrote:
>>>
>>>> Am I the only one whose windy radar graph doesn't show?  It said
>>>> something about being logged off briefly, then went away.  However, if I
>>>> look at the source and clock the link, it appears.  Inspection image
>>>> follows.
>>>>
>>>>
>>>> https://embed.windy.com/embed2.html?lat=29.690&lon=-95.625&zoom=9&level=surface&overlay=radar&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&detailLat=29.625&detailLon=-95.627&metricWind=default&metricTemp=default&radarRange=-1
>>>>
>>>> Oh, BTW, today I did a long-delayed task and got a custom domain,
>>>> houston.house (didn't know that .house was a thing until recently).  So if
>>>> you want to visit the page, soon only the following will work:
>>>>
>>>> http://www.hathaway.house/weewx/belchertown/
>>>>
>>>> Other things I have noticed...
>>>>
>>>> Month Rain Highest Rate shows as 0.07 in
>>>>
>>>> However, the standard skin reports 4.97 in, and the rainRate field in
>>>> the archive table shows,
>>>>
>>>> '2018-08-11 18:56:00', '0.674193548387097'
>>>> '2018-08-11 18:57:00', '2.85193548387097'
>>>> '2018-08-11 18:58:00', '2.17645161290323'
>>>> '2018-08-11 18:59:00', '0.759677419354838'
>>>> '2018-08-11 19:00:00', '0.686129032258064'
>>>> '2018-08-11 19:01:00', '3.26612903225806'
>>>> '2018-08-11 19:02:00', '4.52290322580645'
>>>> '2018-08-11 19:03:00', '0.998709677419355'
>>>> '2018-08-11 19:04:00', '3.04032258064516'
>>>> '2018-08-11 19:05:00', '1.28258064516129'
>>>>
>>>> Looks like more than 0.07 in.
>>>>
>>>> The records page probably reflects bad data.  However, I'm not sure the
>>>> barometer never was -18.6F.  This looks like it is using the lowest
>>>> dewpoint field instead, units included,
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Tue, Aug 28, 2018 at 5:06 PM Colin Larsen 
>>>> wrote:
>>>>
>>>>> I hate to add more .. this may be just a question
>>>>>
>>>>> Currently the rain graph says there has been 0.51 mm rain today as
>>>>> does the data just to the right of the current temp on the main page.
>>>>>
>>>>> However this info box says 5.1mm
>>>>>
>>>>> Today, Wednesday, August 29, 2018
>>>>> High: 21.1 °C Low: -0.7 °C
>>>>> Highest Wind: 8 km/h Highest UV: 10.2
>>>>> Today's Rain: 5.1 mm Highest Rate: 0.3 mm
>>>>>
>>>>> Is that just hourly versus accumulated for the day?? It's a bit hard
>>>>> only running the simulator as I have no hard data to error check
>>>>>
>>>>> On Wed, Aug 29, 2018 at 9:52 AM Pat O'Brien 
>>>>> wrote:
>>>>>
>>>>>> Good catch! I wonder if there's a way around that on upgrades.
>>>>>>
>>>>>> On Tue, Aug 28, 2018, 5:42 PM Colin Larsen 
>>>>>> wrote:
>>>>>>
>>>>>>> Something to watch - the 'about.inc' is also overwritten, so if you
>>>>>>> have lots of goodies modified in that it will go back to the vanilla
>>>>>>> install page when you do an update :) Might pay to backup a

Re: [weewx-user] Avoid bad data with StdQC

[David Hathaway]

I have found that I have many variables outside the StdQC values.  For 
example, my range for dewpoint is 5 to 95, but there are 897 rows outside 
this range.  The minimum is -18!

So, I have a couple questions:


   - Does case count in the StdQC fields?  I have dewpoint but the variable 
   is dewPoint.

[[MinMax]]
barometer = 26, 32.5, inHg
outTemp = 0, 120, degree_F
inTemp = 10, 120, degree_F
outHumidity = 0, 100
inHumidity = 0, 100
windSpeed = 0, 120, mile_per_hour
rain = 0, 120, inch
dewpoint = 5, 95, degree_F
windDir = 0, 360
pressure = 24, 34.5, inHg


   - What can I do to fix it?  I can obviously do a table UPDATE, (archive 
   and archive_day_dewpoint), but is there a utility I have been ignoring?

Dave


On Thursday, August 16, 2018 at 3:54:42 PM UTC-5, Thomas Keffer wrote:
>
> Because the WMR300 supplies rainRate in hardware, you will need to supply 
> limits for both rain and rainRate. It's up to you to pick sensible values, 
> but something like this should work. 
>
> [StdQC]
>   rain = 0, 10, mm
>   rainRate = 0, 100.0, mm_per_hour
>
> -tk
>
> On Thu, Aug 16, 2018 at 1:10 PM Alberto Sánchez  > wrote:
>
>> Sometimes, in my Oregon WMR300, there are more than 8000mm rains.It is a 
>> mistake of the station, because the error also appears in the console.
>>
>> I have cleaned those records from the database but I would like to avoid 
>> them by software. I read that by using 
>> http://weewx.com/docs/usersguide.htm#StdQC I could do it, but I do not 
>> know what parameters I would have to put, rain_rate?
>>
>> An example in wunderground (
>> https://www.wunderground.com/personal-weather-station/dashboard?ID=IVILLAVA2.June
>>  
>> 13, 2018 ) because from the database I have deleted the errors.
>>
>> Thanks
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "weewx-user" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to weewx-user+...@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!

[David Hathaway]

Gary,
I appreciate your response, although much of it is lost on me.  However,
the idea of a dramatic difference between first pass and subsequent passes
isn't happening here.  You can tell by the pid that there was a restart,
but the times are about the same.

Aug 28 17:58:35 hathaway weewx[1319]: cheetahgenerator: Generated 16 files
for report Belchertown in 137.68 seconds
Aug 28 18:01:35 hathaway weewx[1319]: cheetahgenerator: Generated 16 files
for report Belchertown in 137.63 seconds
Aug 28 18:04:38 hathaway weewx[1319]: cheetahgenerator: Generated 16 files
for report Belchertown in 137.25 seconds
Aug 28 18:08:35 hathaway weewx[25730]: cheetahgenerator: Generated 16 files
for report Belchertown in 136.85 seconds
Aug 28 18:11:34 hathaway weewx[25730]: cheetahgenerator: Generated 16 files
for report Belchertown in 137.22 seconds
Aug 28 18:14:35 hathaway weewx[25730]: cheetahgenerator: Generated 16 files
for report Belchertown in 138.26 seconds

Dave



On Tue, Aug 28, 2018 at 7:05 PM gjr80  wrote:

> On Tuesday, 28 August 2018 04:11:36 UTC+10, Pat wrote:
>>
>> Most of the highcharts code is from @gjr80 so he may be able to speak
>> better to it, but looking at how it gets its data, it's using getSqlVectors
>> which looks like it gets its data from the archive table and not a day
>> summary table.
>>
>>
> I realise this is a bit dated in terms of this thread but I missed this
> post.
>
> The original 'highcharts' extension I shared with Pat used getSQLVectors
> throughout which queries the archive and not the daily summaries. From
> memory (and my current highcharts extension has morphed substantially from
> what I first shared with Pat) the day and week SLEs pulled data directly
> from the archive, month and year used an aggregate (hour and day
> respectively I think). This was done for much the same reason as the
> default WeeWX plots plot an aggregate for month and year plots - there is
> just too many data points otherwise.
>
> Also, on the topic of execution times. My original highcharts extension
> used 4 SLEs to produce 4 json format data files using 1 skin with 4 WeeWX
> reports; one report each for day, week, month and year. Each of the SLE
> made a number of calls to getSQLVectors to gather the data vectors for
> the period concerned, These were not done lazily rather they were executed
> in full each time the SLE was called. The way that SLEs work within WeeWX
> is that all SLEs listed in skin.conf are executed for each report in the
> skin. So even with my 4 reports and 4 SLEs there was quite a lot of
> unnecessary SLE execution (16 SLE calls in all when only 4 were actually
> required) going on each with numerous complex SQL queries of the archive.
> If you now magnify that with Pat's extension where there are quite a few
> more reports in the skin that use the highcharts SLEs, the underlying
> queries in the SLEs are being run many times each report cycle. When
> coupled with a database that has a very short archive interval (say sub-5
> minutes) you magnify the time taken to execute these queries due to the
> extra data points in a given period.
>
> I guess the bottom line is that the highcharts SLEs do not scale well in a
> WeeWX report context, judicious placements of reports/SLEs in skins can
> help. The highcharts SLEs really need to rewritten to be more efficient (eg
> lazy evaluation) but that is a biggish task and has follow on consequences
> for the supported reports.
>
> One quick comment on report times, take note of the time taken for the
> second and subsequent report passes after a restart. If the total time
> taken for the reports is approaching your archive interval you will
> possibly have stability issues. The first report pass after a restart
> always takes longer, in my experience up to twice as long as second and
> subsequent passes.
>
> 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/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] Avoid bad data with StdQC

[David Hathaway]

Hi Gary,

I don't know where I saw dewPoint as a variable, but looking at my archive
table, but it is dewpoint.

If I use an update query to modify the out-of-bounds dewpoint values,
should I set it to the limit or NULL? I see 897 values outside the range,
but 22454 that are NULL.

Dave





On Tue, Aug 28, 2018 at 7:35 PM gjr80  wrote:

> Hi,
>
> Yes case counts when using variable/field names (that is what the names on
> the left hand side of the equal sign are). The WeeWX dewpoint field name is
> dewpoint, no spaces all lower case. What do you mean the 'variable is
> dewPoint', if something has added dewPoint then that will at the very least
> cause confusion and quite possibly errors. That being said, if you have a
> field ABCDEFG in your loop packet/archive record you can use StdQC to
> quality control it, just add an entry for ABCDEFG. A couple of caveats
> though. The field must be in the loop packet or archive record as that is
> all that StdQC works on, if it is just a variable somewhere in your code
> then you are out of luck. Secondly, if the service that creates/adds your
> field to the loop packet or archive record appears after StdQC in the
> services list in weewx.conf then StdQC will not correct it as StdQC has
> already done its job. That is why it is best to put services that add data
> to the loop packet/archive record in the data_services line under [Engine]
> [[Services]] in weewx.conf.
>
> Gary
>
> On Wednesday, 29 August 2018 10:19:40 UTC+10, David Hathaway wrote:
>>
>> I have found that I have many variables outside the StdQC values.  For
>> example, my range for dewpoint is 5 to 95, but there are 897 rows outside
>> this range.  The minimum is -18!
>>
>> So, I have a couple questions:
>>
>>
>>- Does case count in the StdQC fields?  I have dewpoint but the
>>variable is dewPoint.
>>
>> [[MinMax]]
>> barometer = 26, 32.5, inHg
>> outTemp = 0, 120, degree_F
>> inTemp = 10, 120, degree_F
>> outHumidity = 0, 100
>> inHumidity = 0, 100
>> windSpeed = 0, 120, mile_per_hour
>> rain = 0, 120, inch
>> dewpoint = 5, 95, degree_F
>> windDir = 0, 360
>> pressure = 24, 34.5, inHg
>>
>>
>>- What can I do to fix it?  I can obviously do a table UPDATE,
>>(archive and archive_day_dewpoint), but is there a utility I have been
>>ignoring?
>>
>> Dave
>>
>>
>> On Thursday, August 16, 2018 at 3:54:42 PM UTC-5, Thomas Keffer wrote:
>>>
>>> Because the WMR300 supplies rainRate in hardware, you will need to
>>> supply limits for both rain and rainRate. It's up to you to pick sensible
>>> values, but something like this should work.
>>>
>>> [StdQC]
>>>   rain = 0, 10, mm
>>>   rainRate = 0, 100.0, mm_per_hour
>>>
>>> -tk
>>>
>>> On Thu, Aug 16, 2018 at 1:10 PM Alberto Sánchez 
>>> wrote:
>>>
>>>> Sometimes, in my Oregon WMR300, there are more than 8000mm rains.It is
>>>> a mistake of the station, because the error also appears in the console.
>>>>
>>>> I have cleaned those records from the database but I would like to
>>>> avoid them by software. I read that by using
>>>> http://weewx.com/docs/usersguide.htm#StdQC I could do it, but I do not
>>>> know what parameters I would have to put, rain_rate?
>>>>
>>>> An example in wunderground (
>>>> https://www.wunderground.com/personal-weather-station/dashboard?ID=IVILLAVA2.June
>>>> 13, 2018 ) because from the database I have deleted the errors.
>>>>
>>>> Thanks
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google
>>>> Groups "weewx-user" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send
>>>> an email to weewx-user+...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>> --
> 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/JaHGiL2mYMQ/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] Re: Belchertown skin for weewx now available!

[David Hathaway]

Hi Gary,

It doesn't look like the processing time is running away.  After starting
at 137 seconds, it eventually went up to 145 seconds before settling back
down to 133 seconds and staying there.  This machine has lots of oomph to
give.  A Pi might struggle.

Dave

On Tue, Aug 28, 2018 at 7:46 PM gjr80  wrote:

> Hmm, that is odd. Using WeeWX for 6 odd years on a number of machines I
> have always noticed a drop in times. I guess there is an exception to the
> rule. I guess I need to refactor the SLEs from my highcharts extension but
> that will not be a quick process. If Pat decides to adopt the revised code
> he will need to modify his code as he has made a number of changes to mine.
>
> If you are running a 1 minute archive interval (I think you mentioned that
> earlier?) and have those sorts of execution time you will eventually grind
> to a halt. When a report cycle comes around WeeWX kicks off a new thread to
> run the report engine, if that takes longer than the archive interval that
> thread is still running when the next report thread is launched and the
> extra load slows things down. The process repeats and eventually it will
> grind to a halt with too many report threads open.
>
> Gary
>
> On Wednesday, 29 August 2018 10:37:18 UTC+10, David Hathaway wrote:
>>
>> Gary,
>> I appreciate your response, although much of it is lost on me.  However,
>> the idea of a dramatic difference between first pass and subsequent passes
>> isn't happening here.  You can tell by the pid that there was a restart,
>> but the times are about the same.
>>
>> Aug 28 17:58:35 hathaway weewx[1319]: cheetahgenerator: Generated 16
>> files for report Belchertown in 137.68 seconds
>> Aug 28 18:01:35 hathaway weewx[1319]: cheetahgenerator: Generated 16
>> files for report Belchertown in 137.63 seconds
>> Aug 28 18:04:38 hathaway weewx[1319]: cheetahgenerator: Generated 16
>> files for report Belchertown in 137.25 seconds
>> Aug 28 18:08:35 hathaway weewx[25730]: cheetahgenerator: Generated 16
>> files for report Belchertown in 136.85 seconds
>> Aug 28 18:11:34 hathaway weewx[25730]: cheetahgenerator: Generated 16
>> files for report Belchertown in 137.22 seconds
>> Aug 28 18:14:35 hathaway weewx[25730]: cheetahgenerator: Generated 16
>> files for report Belchertown in 138.26 seconds
>>
>> Dave
>>
>>
>>
>> On Tue, Aug 28, 2018 at 7:05 PM gjr80  wrote:
>>
>>> On Tuesday, 28 August 2018 04:11:36 UTC+10, Pat wrote:
>>>>
>>>> Most of the highcharts code is from @gjr80 so he may be able to speak
>>>> better to it, but looking at how it gets its data, it's using getSqlVectors
>>>> which looks like it gets its data from the archive table and not a day
>>>> summary table.
>>>>
>>>>
>>> I realise this is a bit dated in terms of this thread but I missed this
>>> post.
>>>
>>> The original 'highcharts' extension I shared with Pat used getSQLVectors
>>> throughout which queries the archive and not the daily summaries. From
>>> memory (and my current highcharts extension has morphed substantially from
>>> what I first shared with Pat) the day and week SLEs pulled data directly
>>> from the archive, month and year used an aggregate (hour and day
>>> respectively I think). This was done for much the same reason as the
>>> default WeeWX plots plot an aggregate for month and year plots - there is
>>> just too many data points otherwise.
>>>
>>> Also, on the topic of execution times. My original highcharts extension
>>> used 4 SLEs to produce 4 json format data files using 1 skin with 4 WeeWX
>>> reports; one report each for day, week, month and year. Each of the SLE
>>> made a number of calls to getSQLVectors to gather the data vectors for
>>> the period concerned, These were not done lazily rather they were executed
>>> in full each time the SLE was called. The way that SLEs work within WeeWX
>>> is that all SLEs listed in skin.conf are executed for each report in
>>> the skin. So even with my 4 reports and 4 SLEs there was quite a lot of
>>> unnecessary SLE execution (16 SLE calls in all when only 4 were actually
>>> required) going on each with numerous complex SQL queries of the archive.
>>> If you now magnify that with Pat's extension where there are quite a few
>>> more reports in the skin that use the highcharts SLEs, the underlying
>>> queries in the SLEs are being run many times each report cycle. When
>>> coupled with a database that has a very short archive interval (say s

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

[David Hathaway]

Pat.

A couple things I have found:

   - How do I get the Rainfall Total line on the Yearly Rainfall graph?
   - The Yearly Rainfall graph has been factored.  Where monthly scales to
   2 inches and the max is about .75 inch, the yearly scales to 0.06 inches
   and the maximum is maybe 0.002 inch?
   - The graphs are not consistent.  Monthly starts at 31 Jul 0:00 except
   rain, which starts at Monday, July 30 0:00 (different callout format only
   for rain).  Yearly starts at  at Jan 1, except for rain that starts at Dec
   31.  Also, wind direction is missing a callout.

Dave

On Wed, Aug 29, 2018 at 6:13 AM David Hathaway 
wrote:

> Hi Gary,
>
> It doesn't look like the processing time is running away.  After starting
> at 137 seconds, it eventually went up to 145 seconds before settling back
> down to 133 seconds and staying there.  This machine has lots of oomph to
> give.  A Pi might struggle.
>
> Dave
>
> On Tue, Aug 28, 2018 at 7:46 PM gjr80  wrote:
>
>> Hmm, that is odd. Using WeeWX for 6 odd years on a number of machines I
>> have always noticed a drop in times. I guess there is an exception to the
>> rule. I guess I need to refactor the SLEs from my highcharts extension but
>> that will not be a quick process. If Pat decides to adopt the revised code
>> he will need to modify his code as he has made a number of changes to mine.
>>
>> If you are running a 1 minute archive interval (I think you mentioned
>> that earlier?) and have those sorts of execution time you will eventually
>> grind to a halt. When a report cycle comes around WeeWX kicks off a new
>> thread to run the report engine, if that takes longer than the archive
>> interval that thread is still running when the next report thread is
>> launched and the extra load slows things down. The process repeats and
>> eventually it will grind to a halt with too many report threads open.
>>
>> Gary
>>
>> On Wednesday, 29 August 2018 10:37:18 UTC+10, David Hathaway wrote:
>>>
>>> Gary,
>>> I appreciate your response, although much of it is lost on me.  However,
>>> the idea of a dramatic difference between first pass and subsequent passes
>>> isn't happening here.  You can tell by the pid that there was a restart,
>>> but the times are about the same.
>>>
>>> Aug 28 17:58:35 hathaway weewx[1319]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 137.68 seconds
>>> Aug 28 18:01:35 hathaway weewx[1319]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 137.63 seconds
>>> Aug 28 18:04:38 hathaway weewx[1319]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 137.25 seconds
>>> Aug 28 18:08:35 hathaway weewx[25730]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 136.85 seconds
>>> Aug 28 18:11:34 hathaway weewx[25730]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 137.22 seconds
>>> Aug 28 18:14:35 hathaway weewx[25730]: cheetahgenerator: Generated 16
>>> files for report Belchertown in 138.26 seconds
>>>
>>> Dave
>>>
>>>
>>>
>>> On Tue, Aug 28, 2018 at 7:05 PM gjr80  wrote:
>>>
>>>> On Tuesday, 28 August 2018 04:11:36 UTC+10, Pat wrote:
>>>>>
>>>>> Most of the highcharts code is from @gjr80 so he may be able to speak
>>>>> better to it, but looking at how it gets its data, it's using 
>>>>> getSqlVectors
>>>>> which looks like it gets its data from the archive table and not a day
>>>>> summary table.
>>>>>
>>>>>
>>>> I realise this is a bit dated in terms of this thread but I missed this
>>>> post.
>>>>
>>>> The original 'highcharts' extension I shared with Pat used
>>>> getSQLVectors throughout which queries the archive and not the daily
>>>> summaries. From memory (and my current highcharts extension has morphed
>>>> substantially from what I first shared with Pat) the day and week SLEs
>>>> pulled data directly from the archive, month and year used an aggregate
>>>> (hour and day respectively I think). This was done for much the same reason
>>>> as the default WeeWX plots plot an aggregate for month and year plots -
>>>> there is just too many data points otherwise.
>>>>
>>>> Also, on the topic of execution times. My original highcharts extension
>>>> used 4 SLEs to produce 4 json format data files using 1 skin with 4 WeeWX
>>>> reports; one report each for 

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

[David Hathaway]

Gary, yes.

On Wed, Aug 29, 2018 at 6:19 AM gjr80  wrote:

> And still on a 1 minute archive period?
>
> 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/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] Avoid bad data with StdQC

[David Hathaway]

Gary,

Thanks for your reply and guidance to use NULL for out-of-limit values.

The latest occurrence of out-of-limit dewpoint is 2016-04-08.  The span of
time with out-of-limit dewpoints was 2015-01-18 to 2016-04-08, in case
there is some versioning question.

Dave

On Wed, Aug 29, 2018 at 8:11 AM gjr80  wrote:

> Dave,
>
> Within WeeWX a SQL NULL or python None value is used to represent an
> observation where there is no data or data is otherwise non-existent for
> that observation. So seeing NULLs in your archive is not necessarily a bad
> thing, just means that valid data was not available for that observation at
> that time. The way that StdQC works is that if it detects a value outside
> of its limits for the observation concerned, the value for that observation
> is set to None. This translates to a NULL in the database. So the correct
> operation for your update query would be to replace the high/low values
> with NULL.
>
> Interesting you have values outside the range, they really should be
> cleaned up by StdQC, is this an ongoing occurrence or is it behaving
> itself now?
>
> Gary
>
> On Wednesday, 29 August 2018 20:56:47 UTC+10, David Hathaway wrote:
>>
>> Hi Gary,
>>
>> I don't know where I saw dewPoint as a variable, but looking at my
>> archive table, but it is dewpoint.
>>
>> If I use an update query to modify the out-of-bounds dewpoint values,
>> should I set it to the limit or NULL? I see 897 values outside the range,
>> but 22454 that are NULL.
>>
>> Dave
>>
>>
>>
>>
>>
>> On Tue, Aug 28, 2018 at 7:35 PM gjr80  wrote:
>>
>>> Hi,
>>>
>>> Yes case counts when using variable/field names (that is what the names
>>> on the left hand side of the equal sign are). The WeeWX dewpoint field name
>>> is dewpoint, no spaces all lower case. What do you mean the 'variable
>>> is dewPoint', if something has added dewPoint then that will at the very
>>> least cause confusion and quite possibly errors. That being said, if you
>>> have a field ABCDEFG in your loop packet/archive record you can use
>>> StdQC to quality control it, just add an entry for ABCDEFG. A couple of
>>> caveats though. The field must be in the loop packet or archive record as
>>> that is all that StdQC works on, if it is just a variable somewhere in
>>> your code then you are out of luck. Secondly, if the service that
>>> creates/adds your field to the loop packet or archive record appears after
>>> StdQC in the services list in weewx.conf then StdQC will not correct it
>>> as StdQC has already done its job. That is why it is best to put
>>> services that add data to the loop packet/archive record in the
>>> data_services line under [Engine] [[Services]] in weewx.conf.
>>>
>>> Gary
>>>
>>> On Wednesday, 29 August 2018 10:19:40 UTC+10, David Hathaway wrote:
>>>>
>>>> I have found that I have many variables outside the StdQC values.  For
>>>> example, my range for dewpoint is 5 to 95, but there are 897 rows outside
>>>> this range.  The minimum is -18!
>>>>
>>>> So, I have a couple questions:
>>>>
>>>>
>>>>- Does case count in the StdQC fields?  I have dewpoint but the
>>>>variable is dewPoint.
>>>>
>>>> [[MinMax]]
>>>> barometer = 26, 32.5, inHg
>>>> outTemp = 0, 120, degree_F
>>>> inTemp = 10, 120, degree_F
>>>> outHumidity = 0, 100
>>>> inHumidity = 0, 100
>>>> windSpeed = 0, 120, mile_per_hour
>>>> rain = 0, 120, inch
>>>> dewpoint = 5, 95, degree_F
>>>> windDir = 0, 360
>>>> pressure = 24, 34.5, inHg
>>>>
>>>>
>>>>- What can I do to fix it?  I can obviously do a table UPDATE,
>>>>(archive and archive_day_dewpoint), but is there a utility I have been
>>>>ignoring?
>>>>
>>>> Dave
>>>>
>>>>
>>>> On Thursday, August 16, 2018 at 3:54:42 PM UTC-5, Thomas Keffer wrote:
>>>>>
>>>>> Because the WMR300 supplies rainRate in hardware, you will need to
>>>>> supply limits for both rain and rainRate. It's up to you to pick sensible
>>>>> values, but something like this should work.
>>>>>
>>>>> [StdQC]
>>>>>   rain = 0, 10, mm
>>>>>   rainRate = 0, 100.0, mm_per_hour
&g

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

[David Hathaway]

Pat,

I am installing now to https://hathaway.house/weewx/belchertown/

Is there a way to determine the running version?

Dave


On Thu, Aug 30, 2018 at 1:15 PM Pat  wrote:

> Version 0.6 is out which fixes a lot of items.
>
> https://github.com/poblabs/weewx-belchertown/releases
>
> --
> 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] Re: Belchertown skin for weewx now available!

[David Hathaway]

7:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 158, in run
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   ngen =
>>>>>>> self.generate(gen_dict[section_name], self.gen_ts)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   ngen +=
>>>>>>> self.generate(section[subsection], gen_ts)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 232, in generate
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   ngen +=
>>>>>>> self.generate(section[subsection], gen_ts)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 320, in generate
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: 
>>>>>>> default_binding)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 372, in 
>>>>>>> _getSearchList
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   searchList
>>>>>>> += obj.get_extension_list(timespan, db_lookup)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/user/belchertown_highchartsSearchX.py", line 1350, in
>>>>>>> get_extension_list
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: 
>>>>>>> (time_start_vt, time_stop_vt, outTemp_vt) =
>>>>>>> db_lookup().getSqlVectors(TimeSpan(_start_ts, timespan.stop), 'outTemp',
>>>>>>> 'max', 86400)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]: File
>>>>>>> "/usr/share/weewx/weeutil/weeutil.py", line 315, in __new__
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   raise
>>>>>>> ValueError("start time (%d) is greater than stop time (%d)" % (args[0],
>>>>>>> args[1]))
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   ValueError:
>>>>>>> start time (1514674800) is greater than stop time (1420066800)
>>>>>>> Aug 29 17:16:28 meteomontaos wee_reports[4760]:   Generator
>>>>>>> terminated
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Greetings.
>>>>>>>
>>>>>>> El martes, 28 de agosto de 2018, 14:43:42 (UTC+2), Pat escribió:
>>>>>>>>
>>>>>>>> Juan, David, give this attached file a try.
>>>>>>>>
>>>>>>>> I set a rain value in the archive table to NULL and saw it fail on
>>>>>>>> MySQL and sqlite.
>>>>>>>>
>>>>>>>> Updated file skips NULL values
>>>>>>>>
>>>>>>>> Place it into your bin/user folder replacing the old one. Restart
>>>>>>>> weewx, then either wait for an archive to happen, or run sudo
>>>>>>>> wee_reports and let me know the results.
>>>>>>>>
>>>>>>>> Make sure you turn highcharts_enabled back to 1 to enable it.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Tuesday, August 28, 2018 at 7:16:32 AM UTC-4, David Hathaway
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Excellent, thanks!
>>>>>>>>>
>>>>>>>>> On Tue, Aug 28, 2018 at 6:14 AM Pat  wrote:
>>>>>>>>>
>>>>>>>>>> You could set highcharts_enabled = 0 for the time being. I
>>>>>>>>>> should have a test soon then can send you guys the file to try it 
>>>>>>>>>> yourself
>>>>>>>>>> before I publish a release.
>>

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

[David Hathaway]

Well, this is interesting.  Here is a statement that fails:

SELECT dateTime FROM archive WHERE dateTime > 1389475998 AND dateTime <=
1535720400 AND wind = (SELECT MAX(wind) FROM archive WHERE dateTime >
1389475998 and dateTime <= 1535720400) AND wind IS NOT NULL

My schema has windSpeed, windDir, windGust, and windGustDir.  Should it
have plain old 'wind'?

Dave



On Fri, Aug 31, 2018 at 7:50 AM David Hathaway 
wrote:

> I'd like to solve my "wind" issue, since I have to modify the template on
> each revision.  What table is lacking "wind"?
>
> Aug 31 07:40:53 hathaway weewx[32401]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Belchertown/records/index.html.tmpl
> Aug 31 07:40:53 hathaway weewx[32401]: cheetahgenerator:  Reason:
> (1054, "Unknown column 'wind' in 'where clause'")
> Aug 31 07:40:53 hathaway weewx[32401]:   Traceback (most recent call
> last):
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
> Aug 31 07:40:53 hathaway weewx[32401]:   print >> _file,
> compiled_template
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Aug 31 07:40:53 hathaway weewx[32401]:   rc = getattr(self,
> mainMethName)()
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "cheetah__etc_weewx_skins_Belchertown_records_index_html_tmpl_1535719243_19_63343.py",
> line 1124, in respond
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "cheetah__etc_weewx_skins_Belchertown_records_index_html_tmpl_1535719243_19_63343.py",
> line 385, in __errorCatcher46
> Aug 31 07:40:53 hathaway weewx[32401]: File "", line 1, in
> 
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
> Aug 31 07:40:53 hathaway weewx[32401]:   return
> self._do_query(aggregate_type)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/tags.py", line 343, in _do_query
> Aug 31 07:40:53 hathaway weewx[32401]:   val=val,
> **self.option_dict)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
> Aug 31 07:40:53 hathaway weewx[32401]:   return
> weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type,
> aggregateType, **option_dict)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/manager.py", line 1249, in getAggregate
> Aug 31 07:40:53 hathaway weewx[32401]:   **option_dict)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/manager.py", line 458, in getAggregate
> Aug 31 07:40:53 hathaway weewx[32401]:   _row =
> self.getSql(select_stmt % interpolate_dict)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weewx/manager.py", line 394, in getSql
> Aug 31 07:40:53 hathaway weewx[32401]:   _cursor.execute(sql,
> sqlargs)
> Aug 31 07:40:53 hathaway weewx[32401]: File
> "/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
> Aug 31 07:40:53 hathaway weewx[32401]:   raise klass(e)
> Aug 31 07:40:53 hathaway weewx[32401]:   NoColumnError: (1054,
> "Unknown column 'wind' in 'where clause'")
> Aug 31 07:41:11 hathaway weewx[32401]: cheetahgenerator: Generated 15
> files for report Belchertown in 113.97 seconds
>
> On Fri, Aug 31, 2018 at 1:27 AM Juan Antonio Mosquera <
> juanantoniomosqu...@juanantoniomosquera.com> wrote:
>
>> Intall 0.6 version now... and same problem. My installation is wit APT
>>
>>
>>
>> Aug 31 08:25:17 meteomontaos weewx[14817]: reportengine: Found
>> configuration file /etc/weewx/skins/Belchertown/skin.conf for report
>> Belchertown
>> Aug 31 08:25:18 meteomontaos weewx[14817]: cheetahgenerator: using search
>> list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station',
>> 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats',
>> 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras',
>> 'user.belchertown.getData', 'user.belchertown.getForecast',
>> 'user.belchertown.getEarthquake',
>> 'user.belchertown_highchartsSearchX.highchartsDay',
>> 'user.belchertown_highchartsSearchX.highchartsWeek',
>> 'user.belchertown_highchartsSearchX.highchartsMonth&

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

[David Hathaway]

This was the query right before the exception:


Aug 31 08:06:51 hathaway weewx[22213]: manager: getSQL: SELECT dateTime 
FROM archive WHERE dateTime > 1389475998 AND dateTime <= 1535720760 AND 
wind = (SELECT MAX(wind) FROM archive WHERE dateTime > 1389475998 and 
dateTime <= 1535720760) AND wind IS NOT NULL
Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator: Generate failed 
with exception ''
Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator:  Ignoring 
template /etc/weewx/skins/Belchertown/records/index.html.tmpl
Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator:  Reason: 
(1054, "Unknown column 'wind' in 'where clause'")
Aug 31 08:06:51 hathaway weewx[22213]:   Traceback (most recent call 
last):
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
Aug 31 08:06:51 hathaway weewx[22213]:   print >> _file, 
compiled_template
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Aug 31 08:06:51 hathaway weewx[22213]:   rc = getattr(self, 
mainMethName)()
Aug 31 08:06:51 hathaway weewx[22213]: File 
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1123, in 
respond
Aug 31 08:06:51 hathaway weewx[22213]: File 
"_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in 
__errorCatcher46
Aug 31 08:06:51 hathaway weewx[22213]: File "", line 1, in 

Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
Aug 31 08:06:51 hathaway weewx[22213]:   return 
self._do_query(aggregate_type)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/tags.py", line 343, in _do_query
Aug 31 08:06:51 hathaway weewx[22213]:   val=val, 
**self.option_dict)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
Aug 31 08:06:51 hathaway weewx[22213]:   return 
weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type, 
aggregateType, **option_dict)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/manager.py", line 1252, in getAggregate
Aug 31 08:06:51 hathaway weewx[22213]:   **option_dict)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/manager.py", line 461, in getAggregate
Aug 31 08:06:51 hathaway weewx[22213]:   _row = 
self.getSql(select_stmt % interpolate_dict)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weewx/manager.py", line 397, in getSql
Aug 31 08:06:51 hathaway weewx[22213]:   _cursor.execute(sql, 
sqlargs)
Aug 31 08:06:51 hathaway weewx[22213]: File 
"/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
Aug 31 08:06:51 hathaway weewx[22213]:   raise klass(e)
Aug 31 08:06:51 hathaway weewx[22213]:   NoColumnError: (1054, "Unknown 
column 'wind' in 'where clause'")
Aug 31 08:06:51 hathaway weewx[22213]: manager: getSQL: SELECT 
MIN(dateTime) FROM archive

If I comment out this part, I don't get the exception:

#if $Extras.has_key('show_windrun') and 
$Extras.show_windrun == '1'

Wind Records


 
$current.dateTime.format("%Y")
All Time


Strongest Wind Gust
$year.wind.max
$year.wind.maxtime.format("%B 
%-d, %Y at %-I:%M %p")
$alltime.wind.maxtime.format("%B %-d, %Y at %-I:%M 
%p")
$alltime.wind.max  
  

#end if

Perhaps instead of $year.wind.maxtime it should be $year.windGust.maxtime ?




On Friday, August 31, 2018 at 8:13:59 AM UTC-5, Pat wrote:
>
> As far as I know, my skin isn’t specifying a query for wind. A search on 
> the repo in GitHub shows that the columns I query are “windSpeed, 
> windGust”, etc. 
>
>  
>
> Anything for “wind” is done through a built in weewx call for $day.wind, 
> $week.wind, etc. 
>
>  
>
> Where do you see this query? 
>

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

[David Hathaway]

Andrew,

Thanks for the pointer.  I'll have to read this several times to let what 
it says sink in.

Dave

On Friday, August 31, 2018 at 9:10:30 AM UTC-5, Andrew Milner wrote:
>
> Gary gave a description of the wind tag in this thread:
>
> https://groups.google.com/forum/?fromgroups=#!topic/weewx-user/siTLWVi_fLM
>
>
> On Friday, 31 August 2018 16:13:59 UTC+3, Pat wrote:
>>
>> As far as I know, my skin isn’t specifying a query for wind. A search on 
>> the repo in GitHub shows that the columns I query are “windSpeed, 
>> windGust”, etc. 
>>
>>  
>>
>> Anything for “wind” is done through a built in weewx call for $day.wind, 
>> $week.wind, etc. 
>>
>>  
>>
>> Where do you see this query? 
>>
>>  
>>
>>  
>>
>> *From:* weewx...@googlegroups.com [mailto:weewx...@googlegroups.com] *On 
>> Behalf Of *David Hathaway
>> *Sent:* Friday, August 31, 2018 9:07 AM
>> *To:* weewx-user 
>> *Subject:* Re: [weewx-user] Re: Belchertown skin for weewx now available!
>>
>>  
>>
>> Well, this is interesting.  Here is a statement that fails:
>>
>>  
>>
>> SELECT dateTime FROM archive WHERE dateTime > 1389475998 AND dateTime <= 
>> 1535720400 AND wind = (SELECT MAX(wind) FROM archive WHERE dateTime > 
>> 1389475998 and dateTime <= 1535720400) AND wind IS NOT NULL
>>
>>  
>>
>> My schema has windSpeed, windDir, windGust, and windGustDir.  Should it 
>> have plain old 'wind'?
>>
>>  
>>
>> Dave
>>
>>  
>>
>>  
>>
>>  
>>
>> On Fri, Aug 31, 2018 at 7:50 AM David Hathaway  
>> wrote:
>>
>> I'd like to solve my "wind" issue, since I have to modify the template on 
>> each revision.  What table is lacking "wind"?
>>
>>  
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: cheetahgenerator:  Ignoring 
>> template /etc/weewx/skins/Belchertown/records/index.html.tmpl
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: cheetahgenerator:  Reason: 
>> (1054, "Unknown column 'wind' in 'where clause'")
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   Traceback (most recent call 
>> last):
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   print >> _file, 
>> compiled_template
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
>> __str__
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   rc = getattr(self, 
>> mainMethName)()
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "cheetah__etc_weewx_skins_Belchertown_records_index_html_tmpl_1535719243_19_63343.py",
>>  
>> line 1124, in respond
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "cheetah__etc_weewx_skins_Belchertown_records_index_html_tmpl_1535719243_19_63343.py",
>>  
>> line 385, in __errorCatcher46
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File "", line 1, 
>> in 
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   return 
>> self._do_query(aggregate_type)
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/tags.py", line 343, in _do_query
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   val=val, 
>> **self.option_dict)
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   return 
>> weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type, 
>> aggregateType, **option_dict)
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/manager.py", line 1249, in getAggregate
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   **option_dict)
>>
>> Aug 31 07:40:53 hathaway weewx[32401]: File 
>> "/usr/share/weewx/weewx/manager.py", line 458, in getAggregate
>>
>> Aug 31 07:40:53 hathaway weewx[32401]:   _row = 
>> self.getSql(select_stmt % interpolate_dict)
>>
>> A

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

[David Hathaway]

Reckoned it was easy enough to try, so I changed the records code to


Strongest Wind Gust
$year.windGust.max
$year.windGust.maxtime.format("%B %-d, %Y at %-I:%M %p")
$alltime.windGust.maxtime.format("%B %-d, %Y at 
%-I:%M %p")
$alltime.windGust.max


(using windGust instead of wind)

It does work in my installation.


On Friday, August 31, 2018 at 9:32:23 AM UTC-5, David Hathaway wrote:
>
> This was the query right before the exception:
>
>
> Aug 31 08:06:51 hathaway weewx[22213]: manager: getSQL: SELECT dateTime 
> FROM archive WHERE dateTime > 1389475998 AND dateTime <= 1535720760 AND 
> wind = (SELECT MAX(wind) FROM archive WHERE dateTime > 1389475998 and 
> dateTime <= 1535720760) AND wind IS NOT NULL
> Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator: Generate failed 
> with exception ''
> Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator:  Ignoring 
> template /etc/weewx/skins/Belchertown/records/index.html.tmpl
> Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator:  Reason: 
> (1054, "Unknown column 'wind' in 'where clause'")
> Aug 31 08:06:51 hathaway weewx[22213]:   Traceback (most recent call 
> last):
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
> Aug 31 08:06:51 hathaway weewx[22213]:   print >> _file, 
> compiled_template
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
> __str__
> Aug 31 08:06:51 hathaway weewx[22213]:   rc = getattr(self, 
> mainMethName)()
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1123, in 
> respond
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in 
> __errorCatcher46
> Aug 31 08:06:51 hathaway weewx[22213]: File "", line 1, in 
> 
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
> Aug 31 08:06:51 hathaway weewx[22213]:   return 
> self._do_query(aggregate_type)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/tags.py", line 343, in _do_query
> Aug 31 08:06:51 hathaway weewx[22213]:   val=val, 
> **self.option_dict)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
> Aug 31 08:06:51 hathaway weewx[22213]:   return 
> weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type, 
> aggregateType, **option_dict)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/manager.py", line 1252, in getAggregate
> Aug 31 08:06:51 hathaway weewx[22213]:   **option_dict)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/manager.py", line 461, in getAggregate
> Aug 31 08:06:51 hathaway weewx[22213]:   _row = 
> self.getSql(select_stmt % interpolate_dict)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weewx/manager.py", line 397, in getSql
> Aug 31 08:06:51 hathaway weewx[22213]:   _cursor.execute(sql, 
> sqlargs)
> Aug 31 08:06:51 hathaway weewx[22213]: File 
> "/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
> Aug 31 08:06:51 hathaway weewx[22213]:   raise klass(e)
> Aug 31 08:06:51 hathaway weewx[22213]:   NoColumnError: (1054, 
> "Unknown column 'wind' in 'where clause'")
> Aug 31 08:06:51 hathaway weewx[22213]: manager: getSQL: SELECT 
> MIN(dateTime) FROM archive
>
> If I comment out this part, I don't get the exception:
>
> #if $Extras.has_key('show_windrun') 
> and $Extras.show_windrun == '1'
> 
>  colspan=5>Wind Records
> 
> 
>  colspan=1> 
>  colspan=2>$current.dateTime.format("%Y")
>  colspan=2>All Time
> 
> 
> Strongest Wind Gust
>  

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

[David Hathaway]

The confusing thing is that this is the part that throws an exception:


  Strongest Wind Gust
  $year.wind.max
  $year.wind.maxtime.format("%B %-d, %Y at %-I:%M %p")
  $alltime.wind.maxtime.format("%B %-d, %Y at %-I:%M
%p")
  $alltime.wind.max
  

Should this work?

The exception is  NoColumnError: (1054, "Unknown column 'wind' in 'where
clause'")

On Fri, Aug 31, 2018 at 2:05 PM Thomas Keffer  wrote:

> It all depends on what you want.
>
> In what follows, I am assuming that option loop_hilo
> <http://weewx.com/docs/usersguide.htm#StdArchive> is set to true (the
> normal state of affairs). Much of this information is also in the section 
> *Wind
> <http://www.weewx.com/docs/customizing.htm#Wind>*.
>
> $day.wind.max is the maximum wind speed seen during the day (including
> LOOP packets). It's obtained from the daily summaries.
> $day.windGust.max is the same. However, because windGust does not appear
> in the daily summaries, it is calculated from the archive data.
> $day.windSpeed.max is the max average wind speed. This is calculated from
> the archive data. The wind is averaged over each of the archive intervals,
> then the maximum of these values is taken. This is different from the above
> two tags.
>
> Generally, you work with $day.wind.*something. *This is because, for the
> average user, it's easier to just tell him/her to work with 'wind' and not
> worry about how it got flattened. $day.wind.max is natural,
> $day.windGust.max is not.
>
> Also, it's much more efficient to calculate things from the daily archives.
>
> On Fri, Aug 31, 2018 at 11:15 AM Pat  wrote:
>
>> You're right, this is confusing. I do have one tmpl with
>> day/week/month/year.wind. Are you suggesting that I change the week/month
>> to the proper windGust, windSpeed, etc? or change all 4 types since
>> day/year can be used in aggregation?
>>
>> On Friday, August 31, 2018 at 12:43:26 PM UTC-4, Thomas Keffer wrote:
>>>
>>> The tag "wind" can only be used in aggregations, such as day and year.
>>> The tags windSpeed, windDir, windGust, and windGustDir can be used for
>>> current observations, as well as aggregations. This is all explained in the
>>> Customizing Guide, section *Wind
>>> <http://www.weewx.com/docs/customizing.htm#Wind>*.
>>>
>>> Confusing, I know. It's the product of a legacy schema from wview, and
>>> the need to flatten vector-like quantities into a two dimensional SQL
>>> table. A more general solution would have been a separate table for each
>>> type (much like the daily summaries), but that would break compatibility
>>> with wview, as well as be slower.
>>>
>>> -tk
>>>
>>> On Fri, Aug 31, 2018 at 9:16 AM Pat O'Brien 
>>> wrote:
>>>
>>> I'm on mobile, so I read this again. Maybe the difference is year.wind
>>> as opposed to day?
>>>
>>> On Fri, Aug 31, 2018, 12:12 PM Pat O'Brien  wrote:
>>>
>>> Interesting... Check this link as it is the official document.
>>>
>>> http://www.weewx.com/docs/customizing.htm
>>>
>>> Then search for "day.wind". You'll see the differences.
>>>
>>>
>>> On Fri, Aug 31, 2018, 11:57 AM David Hathaway 
>>> wrote:
>>>
>>> Reckoned it was easy enough to try, so I changed the records code to
>>>
>>> 
>>> Strongest Wind Gust
>>> $year.windGust.max
>>> $year.windGust.maxtime.format("%B %-d, %Y at %-I:%M %p")
>>> $alltime.windGust.maxtime.format("%B %-d, %Y
>>> at %-I:%M %p")
>>> $alltime.windGust.max
>>> 
>>>
>>> (using windGust instead of wind)
>>>
>>> It does work in my installation.
>>>
>>>
>>> On Friday, August 31, 2018 at 9:32:23 AM UTC-5, David Hathaway wrote:
>>>
>>> This was the query right before the exception:
>>>
>>>
>>> Aug 31 08:06:51 hathaway weewx[22213]: manager: getSQL: SELECT dateTime
>>> FROM archive WHERE dateTime > 1389475998 AND dateTime <= 1535720760 AND
>>> wind = (SELECT MAX(wind) FROM archive WHERE dateTime > 1389475998 and
>>> dateTime <= 1535720760) AND wind IS NOT NULL
>>> Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator: Generate failed
>>> with exception ''
>>> Aug 31 08:06:51 hathaway weewx[22213]: cheetahgenerator:  Ignoring
>>> template /etc/weewx/skins/Belchertown/records/index.html.tm

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

[David Hathaway]

Sylvain,

You are impacted by the very issue we are discussing.  It looks like you
can avoid the error by modifying *records/index.html.tmpl *around line 132

FROM:
$alltime.*wind*.maxtime.format("%B %-d, %Y at %-I:%M
%p")
$alltime.*wind*.max

TO:
$alltime.*windGust*.maxtime.format("%B %-d, %Y at
%-I:%M %p")
$alltime.*windGust*.max

The issue as described above is limited to the $alltime.wind variable.

With this change, you will get a log entry like

cheetahgenerator: Generated 16 files for report Belchertown in 134.22
seconds

but in your case it looks to be 14 minutes instead of 2.

If you can live without the graphs (I can't), turning them off makes the
generation quick.  I went from 134.22 seconds to 0.99 seconds.  To do that,
that set highcharts_enabled = 0 in Extras.  I moved my Belchertown settings
to weewx.conf, and I suggest you do the same so they aren't overwritten in
updates:

[StdReport]

# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = /etc/weewx/skins

# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx

# The database binding indicates which data should be used in reports.
data_binding = wx_binding

# Each of the following subsections defines a report that will be run.
[[Belchertown]]
HTML_ROOT = /var/www/html/weewx/belchertown
skin = Belchertown
[[[Extras]]]
forecast_enabled = 1
*highcharts_enabled = 0*
darksky_secret_key = thisisheretotakeupspace
earthquake_enabled = 1
site_title = The Hill
footer_copyright_text = The Hill
radar_html = https://embed.windy.com/embed2.html?yoururl"; frameborder="0">


[[StandardReport]]

etc





On Sat, Sep 1, 2018 at 7:01 AM Sylvain Martel  wrote:

>
>
> On Saturday, 1 September 2018 07:39:32 UTC-4, Sylvain Martel wrote:
>>
>> With the skin installed, the reports thread never finish.  Usually it
>> takes 15-50 seconds to generate them(Raspberry Pi 2) but it never finish
>> now.  Any clue?
>>
>
>
> Update:  Finally got this error after waiting 14 mins:
> ep  1 07:59:03 Pi2 weewx-sto2[11171]: cheetahgenerator: Generate failed
> with exception ''
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: cheetahgenerator:  Ignoring
> template /etc/weewx/skins/Belchertown/records/index.html.tmpl
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: cheetahgenerator:  Reason:
> (1054, "Unknown column 'wind' in 'where clause'")
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   Traceback (most recent call
> last):
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/cheetahgenerator.py", line 330, in generate
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   print >> _file,
> compiled_template
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in
> __str__
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   rc = getattr(self,
> mainMethName)()
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 1124, in
> respond
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "_etc_weewx_skins_Belchertown_records_index_html_tmpl.py", line 385, in
> __errorCatcher46
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File "", line 1, in
> 
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/tags.py", line 329, in __getattr__
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   return
> self._do_query(aggregate_type)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/tags.py", line 343, in _do_query
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   val=val,
> **self.option_dict)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/wxmanager.py", line 60, in getAggregate
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   return
> weewx.manager.DaySummaryManager.getAggregate(self, timespan, obs_type,
> aggregateType, **option_dict)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/manager.py", line 1249, in getAggregate
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   **option_dict)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/manager.py", line 458, in getAggregate
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   _row =
> self.getSql(select_stmt % interpolate_dict)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weewx/manager.py", line 394, in getSql
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   _cursor.execute(sql,
> sqlargs)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]: File
> "/usr/share/weewx/weedb/mysql.py", line 48, in guarded_fn
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   raise klass(e)
> Sep  1 07:59:03 Pi2 weewx-sto2[11171]:   NoColumnError: (1054,
> "Unknown column 'wind' in 'where clause'")
>
> --
> You received this message because you 

[weewx-user] Custom Charts Question; colors, labels at bottom

[David Hathaway]

I love the Belchertown skin, but I am uncomfortable with the very long 
processing time to create the highcharts.  I am pondering the ability to 
run the JSON charts for day charts, and to switch to the weewx standard 
charts for week, month, and year.  So what I am doing now is trying to 
recreate the JSON chart look with the imagegenerator.

My current status is attached.  The top is the imagegenerator version and 
the bottom is the highcharts / JSON version.  The biggest difference I am 
ignoring, where highcharts uses "today" versus imagegenerator using "last 
24 hours".  That won't be important for weekly+ periods.

The first hurdle was fonts.  The highcharts use Lucida, which is 
proprietary to Macs.  Otherwise, the skin uses Lato, which is opensource 
and available.  Installing that font and using it in the charts resolves 
that issue completely (at least on my screen!).  I might continue to seek 
an on-demand online font (Google font?) that allows everyone to see the 
same thing; I doubt visitors will want to install a font,

But now I am puzzled as to how to solve the other obvious issues:

   - How do I get rid of the vertical grid lines?
   - How do I move the labels from the top to the bottom; I am supposing 
   sample lines are impossible.
   - I am being driven nuts by the colors.  They should be blue, black, 
   green, orange from left to right.  No matter what I do, they are shown 
   orange, black, green, and blue.


Here is what I tried first (excerpted):

[ImageGenerator]

# Default colors for the plot lines. These can be overridden for
# individual lines using option 'color'
chart_line_colors = 0x7cb5ec, 0x434348, 0x90ed7d, 0xf7a35c, 0x8085e9, 
0xf15c80, 0xe4d354, 0x2b908f, 0xf45b5b, 0x91e8e1

# Default fill colors for bar charts. These can be overridden for
# individual bar plots using option 'fill_color'
chart_fill_colors = 0x7cb5ec, 0x434348, 0x90ed7d, 0xf7a35c, 0x8085e9, 
0xf15c80, 0xe4d354, 0x2b908f, 0xf45b5b, 0x91e8e1

However, it does not use the colors in that order.  Is it alphabetical?

No matter, I tried,

[[[daytempdew]]]
outTemp
   color = 0x7cb5ec
dewpoint
   color = 0x434348
windchill
   color = 0x90ed7d
heatindex
   color = 0xf7a35c

[[[daywind]]]
windSpeed
   color = 0x7cb5ec
windGust
   color = 0x434348

The comments and the guide suggests using color = should overwrite whatever 
is the default but they are not using the specified colors.  You can see it 
most easily on the wind graph.

I am generally happy so far, in that generating the 22 charts using 
imagegenerator takes .53 seconds compared to 134 seconds using the 
highcharts.  I just would like to tweak the look and I am confounded by the 
colors.

BTW, the url is https://hathaway.house/weewx/belchertown/

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] Re: Custom Charts Question; colors, labels at bottom

[David Hathaway]

Oh, I don't disagree.  I'm just trying to match.

On Saturday, September 1, 2018 at 12:37:26 PM UTC-5, vince wrote:
>
> On Saturday, September 1, 2018 at 9:09:26 AM UTC-7, David Hathaway wrote:
>>
>> But now I am puzzled as to how to solve the other obvious issues:
>>
>>- How do I get rid of the vertical grid lines?
>>
>>
> FWIW - I think the vertical grid lines 'help' a lot
>  
>

-- 
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] Re: Custom Charts Question; colors, labels at bottom

[David Hathaway]

Gary,

Thanks for the insight.  Swapping around the bytes to BBGGRR worked.  
However, using #RRGGBB left me with this exception:

Sep  2 05:43:57 hathaway weewx[2554]:   ValueError: Unknown 
color specifier: ''.  Colors must be specified as 0xBBGGRR, #RRGGBB, or 
standard color names.

I was doing as it said, so this appears to be a bug.  Both lowercase and 
upper case didn't work.

Oh... # starts a comment, so not sure how #RRGGBB works?



On Saturday, September 1, 2018 at 6:16:30 PM UTC-5, gjr80 wrote:
>
>
> On Sunday, 2 September 2018 02:09:26 UTC+10, David Hathaway wrote:
>>
>>
>> But now I am puzzled as to how to solve the other obvious issues:
>>
>>- How do I get rid of the vertical grid lines?
>>
>> The WeeWX image generator is pretty sophisticated for what it is, a 
> utility written from scratch in python to generate plots; however, its 
> capabilities are limited in a number of areas and unfortunately it is not 
> possible to disable the vertical grid lines. The only thing you can do 
> short of changing the image generator code is set the grid line colour to 
> be the same as your background but that will hide all grid line not just 
> the vertical - not really much practical use.
>
>>
>>- How do I move the labels from the top to the bottom; I am supposing 
>>sample lines are impossible.
>>
>> Again, unfortunately, it is not possible to move the top labels (eg 
> outTemp dewpoint etc) to the bottom. I assume when you say 'sample' you 
> mean a sample line in the colour/format to be used for the obs being 
> plotted, if so then again no this can't be done with the present image 
> generator.
>
>>
>>- I am being driven nuts by the colors.  They should be blue, black, 
>>green, orange from left to right.  No matter what I do, they are shown 
>>orange, black, green, and blue.
>>
>> This one we can help with! I think the issue you are having is that when 
> specified with the 0x prefix the colour format is BBGGRR not RRGGBB as we 
> commonly use. So 0x7cb5ec will in fact result in an orange line, if you 
> swap the first and last colour pair (ie 0xecb57c) you will get the blue 
> that you seek. You should be able to use #RRGGBB but I seem to recall I 
> struck a few quirks with this a few years back, could be mistaken though. 
> Looking at the section Customizing images 
> <http://weewx.com/docs/customizing.htm#Customizing_images> in the 
> Customization Guide and then again at the [ImageGenerator] Overall options 
> <http://weewx.com/docs/customizing.htm#Overall_options> section this 
> details is not explicitly stated, it is covered though in notes under 
> [ImageGenerator] in the Standard skin.conf 
> <https://github.com/weewx/weewx/blob/master/skins/Standard/skin.conf#L285>. 
> I guess most folks would see these when they customize the Standard skin 
> but in your case you may not as perhaps you are working with another skin. 
> Probably need to make a few changes to the Customization Guide. 
>
> 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] Re: Belchertown skin for weewx now available!

[David Hathaway]

I use Chrome on Android Pie (Pixel XL) and my test looks surprisingly good
in mobile:
https://hathaway.house/weewx/belchertown/

On Sun, Sep 2, 2018 at 10:59 AM Praveen Chandrasekaran <
praveen.c...@gmail.com> wrote:

> The formatting in many place goes haywire on mobile. I was using 3 seasons
> because it's formatting on mobile was awesome better than Standard skin. I
> think this is something that can improve in this skin.
>
> Attached a sample screenshot of belchertown page. I assume the skin will
> be exactly same. Have not got the time to install try yet
>
> On Sun, 2 Sep 2018, 20:13 Praveen Chandrasekaran, 
> wrote:
>
>> How do I setup username password with free broker (test.mosquito)?
>>
>> --
>> 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 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] Re: Belchertown skin for weewx now available!

[David Hathaway]

Hi Pat,

Got the new skin installed, and I really like how the "home" page is 
available quite quickly.  I'll keep an eye on the cpu usage.  In fact, I 
replaced the radiation graph with a cpu activity chart.  You can pretty 
easily detect when I changed skins.

https://hathaway.house/weewx/belchertown/

I have a question about the 8-Day forecast.  With both Chromium and 
Firefox, 7 of the forecasts line up, and the 8th is centered below.  I 
fixed it before I reinstalled by reducing padding or something.  Is there 
some reason why I am getting wrapping?

Dave

On Saturday, September 8, 2018 at 1:48:04 PM UTC-5, Pat wrote:
>
> To all who are subscribed, Belchertown skin 0.7 is out!
>
> *There are a lot of changes and an uninstall and re-install of the skin is 
> advised.* 
>
> This is due to the charts generator being split into it's own skin to 
> speed up generation time. The 2 skins are linked together and released as 1 
> skin. 
>
> *Be sure to have a backup of all your custom skin settings! *
>
> Read more details here: 
> https://github.com/poblabs/weewx-belchertown/releases/tag/weewx-belchertown-0.7
>
>
>
> On Saturday, September 8, 2018 at 1:58:23 PM UTC-4, Andrew Milner wrote:
>
> Why not create a skin to transfer only Belchertown yearly via FTP, and 
> remove yearly from other skins and then run wee_reports with just the 
> Belchertown ftp skin via cron once per day.
>
> Something like that anyway should give you what you need.
>
>
>
> On Saturday, 8 September 2018 18:08:08 UTC+3, Pat wrote:
>
> How are you transferring it? The skin doesn't ftp.  Are you Using the ftp 
> extension? Not sure on the options of that. 
>
> On Sat, Sep 8, 2018, 10:59 AM Praveen Chandrasekaran  
> wrote:
>
> Another suggestion
>
> I was looking at the size of belchertown skin output. Sign
>
> ...

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

[David Hathaway]

On Sunday, September 9, 2018 at 11:24:19 AM UTC-5, Pat wrote:
>
> Ah, I forgot I set a CSS padding of 15px around each day... That could be 
> the problem (although your site still looks fine to me) 
>
> You can play with either the width of .wuforecast or with the padding to 
> see if that fixes it for you. 
>
> On Sunday, September 9, 2018 at 12:20:39 PM UTC-4, Pat wrote:
>>
>> Strange, your looks good to me. It could mean the difference of a pixel 
>> or two pushing the 8th day out of the container and wrapping. I tried to 
>> make the forecasts as wide as possible to fill the container. 
>>
>> Is your zoom 100%?
>>
>> The container is 1210 pixels wide, divided by 8 days would be 151 pixels 
>> to play with. I set them at 140px to be safe.
>>
>> If you open your public_html/Belchertown/style.css, and on line 1960 
>> you'll see width: 140px. Try changing that down to 138px or so and see if 
>> that fixes it?
>>
>>
>> On Sunday, September 9, 2018 at 11:03:51 AM UTC-4, David Hathaway wrote:
>>
>> Hi Pat,
>>
>> Got the new skin installed, and I really like how the "home" page is 
>> available quite quickly.  I'll keep an eye on the cpu usage.  In fact, I 
>> replaced the radiation graph with a cpu activity chart.  You can pretty 
>> easily detect when I changed skins.
>>
>> https://hathaway.house/weewx/b 
>> <https://hathaway.house/weewx/belchertown/>
>>
>> ...
>
>

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

[David Hathaway]

Well, that was dumb, hitting post when I meant to type.  Sorry!

I was gonna say Chrome has a handy inspect feature where I can modify 
settings "live".  I'll see what works.


On Sunday, September 9, 2018 at 4:27:06 PM UTC-5, David Hathaway wrote:
>
>
>
> On Sunday, September 9, 2018 at 11:24:19 AM UTC-5, Pat wrote:
>
> Ah, I forgot I set a CSS padding of 15px around each day... That could be 
> the problem (although your site still looks fine to me) 
>
> You can play with either the width of .wuforecast or with the padding to 
> see if that fixes it for you. 
>
> On Sunday, September 9, 2018 at 12:20:39 PM UTC-4, Pat wrote:
>
> Strange, your looks good to me. It could mean the difference of a pixel or 
> two pushing the 8th day out of the container and wrapping. I tried to make 
> the forecasts as wide as possible to fill the container. 
>
> Is your zoom 100%?
>
> The container is 1210 pixels wide, divided by 8 days would be 151 pixels 
> to play with. I set them at 140px to be safe.
>
> If you open your public_html/Belchertown/style.css, and on line 1960 
> you'll see width: 140px. Try changing that down to 138px or so and see if 
> that fixes it?
>
>
> On Sunday, September 9, 2018 at 11:03:51 AM UTC-4, David Hathaway wrote:
>
> Hi Pat,
>
> Got the new skin installed, and I really like how the "home" page is 
> available quite quickly.  I'll keep an eye on the cpu usage.  In fact, I 
> replaced the radiation graph with a cpu activity chart.  You can pretty 
> easily detect when I changed skins.
>
> ...

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

[David Hathaway]

I think your site looks nice.  Couple tweaks, though... I see Houston radar
in your windy because you haven't set the location in the url, and I see
that Galacia is in Massachusetts (i.e., you are using the stock logo :)
Otherwise, I think it looks great.

One odd thing (for me) though.  I see your charts span across days, but
mine are from today at midnight to present.  I think they look better with
a longer span; I wonder how you got that and I didn't?

Dave

On Tue, Sep 11, 2018 at 9:30 AM Juan Antonio Mosquera <
juanantoniomosqu...@juanantoniomosquera.com> wrote:

> Now, reinstalled extension and works fine... i dont understand...
>
> http://www.meteomontaos2.ga/
>
> Thanks.
>
> El martes, 11 de septiembre de 2018, 14:43:23 (UTC+2), Philip Kutzenco
> escribió:
>>
>> Strange. I now see your old skin on your website. When I last looked, I
>> saw the Belchertown skin with wind data apparently shown properly.
>>
>> I see you are using a WMR300 station. I know that Pat made some changes
>> for the charts, at least where he was gathering windgust data instead of
>> wind data to fix errors that others (including me) saw. I wonder if that is
>> causing issues when you use the WMR300 driver to gather data. As I said
>> earlier, I use the vantage driver to gather data from my Vantage Vue
>> station.
>>
>> On Tuesday, September 11, 2018 at 8:08:14 AM UTC-4, Juan Antonio Mosquera
>> wrote:
>>
>> Now i have wind data because uninstall extension:
>>
>> http://www.meteomontaos.es/
>>
>>
>> http://www.meteomontaos2.ga/ is for try... not updated.
>>
>> With belchertown extension enabled, not recieved Wind data... but... i
>> wil try again  for confirm.
>>
>> Greetings.
>>
>> El martes, 11 de septiembre de 2018, 14:03:40 (UTC+2), Philip Kutzenco
>> escribió:
>>
>> I am running version 0.7 wit
>>
>> ...
>
> --
> 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] Re: Belchertown skin for weewx now available!

[David Hathaway]

Pat,

How do I get a reasonable "Rainfall" value on the chart.  The Rainfall 
Total graph looks fine, but the amount looks factored down.  I have changed 
my interval to 5 minutes last week, so I am not sure that is the issue.  
Meanwhile, the text reports highest rainfall rate was 2.45 in/hr.  Not sure 
what to tweak.

See attached.  You can also visit

https://hathaway.house/weewx/belchertown/

and Wunderground to compare:

https://www.wunderground.com/personal-weather-station/dashboard?ID=KTXSUGAR19

Dave


On Tuesday, September 11, 2018 at 9:52:14 AM UTC-5, David Hathaway wrote:
>
> I think your site looks nice.  Couple tweaks, though... I see Houston 
> radar in your windy because you haven't set the location in the url, and I 
> see that Galacia is in Massachusetts (i.e., you are using the stock logo 
> :)  Otherwise, I think it looks great.
>
> One odd thing (for me) though.  I see your charts span across days, but 
> mine are from today at midnight to present.  I think they look better with 
> a longer span; I wonder how you got that and I didn't?
>
> Dave
>
> On Tue, Sep 11, 2018 at 9:30 AM Juan Antonio Mosquera <
> juanantoniomosqu...@juanantoniomosquera.com> wrote:
>
> Now, reinstalled extension and works fine... i dont understand...
>
> http://www.meteomontaos2.ga/
>
> Thanks.
>
> El martes, 11 de septiembre de 2018, 14:43:23 (UTC+2), Philip Kutzenco 
> escribió:
>
> Strange. I now see your old skin on your website. When I last looked, I 
> saw the Belchertown skin with wind data apparently shown properly.
>
> I see you are using a WMR300 station. I know that Pat made some changes 
> for the charts, at least where he was gathering windgust data instead of 
> wind data to fix errors that others (including me) saw. I wonder if that is 
> causing issues when you use the WMR300 driver to gather data. As I said 
> earlier, I use the vantage driver to gather data from my Vantage Vue 
> station.
>
> On Tuesday, September 11, 2018 at 8:08:14 AM UTC-4, Juan Antonio Mosquera 
> wrote:
>
> ...

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

[David Hathaway]

Regarding Windy, early in this thread (August 21), it was discovered that 
windy will by default show the location of where your ISP connects from. So 
for you, it would show your home.  When I look at your windy, I get MY 
home.  The solution is, (quoting):

Change the lat/lon for your area, but the bit I changed (and got lucky 
with) was overlay=wind

https://embed.windy.com/embed2.html?*lat=-26.195&lon=138.560*
&zoom=5&level=surface&overlay=wind&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&
*detailLat=-26.195&detailLon=138.560*
&metricWind=default&metricTemp=default&radarRange=-1 
<https://embed.windy.com/embed2.html?lat=-26.195&lon=138.560&zoom=5&level=surface&overlay=wind&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&detailLat=-26.195&detailLon=138.560&metricWind=default&metricTemp=default&radarRange=-1>


This will tell windy to use the defined location rather than where you 
connect to the internet.  My conf has this,

radar_html = https://embed.windy.com/embed2.html?lat=29.690&lon=-95.625&zoom=9&level=surface&overlay=radar&menu=&message=&marker=&calendar=&pressure=&type=map&location=coordinates&detail=&detailLat=29.625&detailLon=-95.627&metricWind=default&metricTemp=default&radarRange=-1";
 
frameborder="0">


Dave


On Tuesday, September 11, 2018 at 10:59:50 AM UTC-5, Juan Antonio Mosquera 
wrote:
>
> I have only translated the text. I get the perfect location (Galicia - 
> Spain) in Windy.
> I have not made any modifications to the graphics, it's the default as Pat 
> did.
> I have already changed the logo (the website is for testing).
> Greetings and thanks.
>
> El martes, 11 de septiembre de 2018, 16:52:14 (UTC+2), David Hathaway 
> escribió:
>
> I think your site looks nice.  Couple tweaks, though... I see Houston 
> radar in your windy because you haven't set the location in the url, and I 
> see that Galacia is in Massachusetts (i.e., you are using the stock logo 
> :)  Otherwise, I think it looks great.
>
> One odd thing (for me) though.  I see your charts span across days, but 
> mine are from today at midnight to present.  I think they look better with 
> a longer span; I wonder how you got that and I didn't?
>
> Dave
>
> On Tue, Sep 11, 2018 at 9:30 AM Juan Antonio Mosquera <
> juananton...@juanantoniomosquera.com> wrote:
>
> Now, reinstalled extension and works fine... i dont understand...
>
> ...

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

[David Hathaway]

Pat,

Why would my Davis Vantage Pro2 be any different than any one elses? 

Here is the latest non-0 rain data, which supports your idea to use 
rainRate rather than rain.

dateTime rain rainRate
1536705240 0.01 0.0270967741935484
1536704340 0.01 0
1536703200 0.01 0
1536701220 0.01 0
1536692220 0.02 1.41193548387097
1536692160 0.03 2.21870967741936
1536692100 0.02 0.904193548387097

On Wednesday, September 12, 2018 at 12:52:02 PM UTC-5, Pat wrote:
>
> Dave, 
>
> The "Rainfall" in your graph is a really a bucket tip as I understand it. 
> So if it's only showing 0.01 or 0.02 then that's how many tips per archive 
> interval. The code that generates that graph is here 
> <https://github.com/poblabs/weewx-belchertown/blob/master/bin/user/belchertown_highchartsSearchX.py#L140>
> . 
>
> The wunderground page shows the precip rate. 
>
> So I think you're looking for the weewx observation rainRate and not rain 
> (which 
> shows the 'bucket tips')...?
>
> For giggles, and since today is a rainy day for me it's easy to test this, 
> I changed the SQL to rainRate instead of rain and it gave me the graph 
> attached - which is slightly different than wunderground. Not sure why to 
> be honest...
>
>
>
> On Tuesday, September 11, 2018 at 11:00:54 AM UTC-4, David Hathaway wrote:
>>
>> Pat,
>>
>> How do I get a reasonable "Rainfall" value on the chart.  The Rainfall 
>> Total graph looks fine, but the amount looks factored down.  I have changed 
>> my interval to 5 minutes last week, so I am not sure that is the issue.  
>> Meanwhile, the text reports highest rainfall rate was 2.45 in/hr.  Not sure 
>> what to tweak.
>>
>> See attached.  You can also visit
>>
>> https://hathaway.house/weewx/belchertown/
>>
>> and Wunderground to compare:
>>
>>
>> https://www.wunderground.com/personal-weather-station/dashboard?ID=KTXSUGAR19
>>
>> 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.

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

[David Hathaway]

Thanks for the explanation.  That is pretty clear.

I guess my confusion lies in that the graph says "hourly rainfall" but is
showing interval rainfall.  I'm not sure what it should show, to be
honest.  With a archive interval of 180 seconds, should it multiply by 20
to what the hourly rain would be if that rate lasted for an hour?  An
aggregation?

What I see now with the scale set to inches while the values are in the
hundredths... just looks weird.

Dave


On Wed, Sep 12, 2018 at 1:31 PM Thomas Keffer  wrote:

> "rain" is the amount of rain that fell in the archive interval.
>
> "rainRate" is a derived quantity, calculated by StdWXCalculate. It's the
> amount of rain in a fixed period, divided by the length of that period. The
> period is set by option rain_period, with a default of 900 seconds (15
> minutes).
>
> Posts to the WU use something completely different: the amount of rain
> that fell during the preceding 60 minutes. Presumably, the WU then takes
> deltas on this number to calculate whatever it is that they are showing.
>
> -tk
>
>
> On Wed, Sep 12, 2018 at 10:52 AM Pat  wrote:
>
>> Dave,
>>
>> The "Rainfall" in your graph is a really a bucket tip as I understand it.
>> So if it's only showing 0.01 or 0.02 then that's how many tips per archive
>> interval. The code that generates that graph is here
>> <https://github.com/poblabs/weewx-belchertown/blob/master/bin/user/belchertown_highchartsSearchX.py#L140>
>> .
>>
>> The wunderground page shows the precip rate.
>>
>> So I think you're looking for the weewx observation rainRate and not rain
>> (which shows the 'bucket tips')...?
>>
>> For giggles, and since today is a rainy day for me it's easy to test
>> this, I changed the SQL to rainRate instead of rain and it gave me the
>> graph attached - which is slightly different than wunderground. Not sure
>> why to be honest...
>>
>>
>>
>> On Tuesday, September 11, 2018 at 11:00:54 AM UTC-4, David Hathaway wrote:
>>>
>>> Pat,
>>>
>>> How do I get a reasonable "Rainfall" value on the chart.  The Rainfall
>>> Total graph looks fine, but the amount looks factored down.  I have changed
>>> my interval to 5 minutes last week, so I am not sure that is the issue.
>>> Meanwhile, the text reports highest rainfall rate was 2.45 in/hr.  Not sure
>>> what to tweak.
>>>
>>> See attached.  You can also visit
>>>
>>> https://hathaway.house/weewx/belchertown/
>>>
>>> and Wunderground to compare:
>>>
>>>
>>> https://www.wunderground.com/personal-weather-station/dashboard?ID=KTXSUGAR19
>>>
>>> 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 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.

[weewx-user] Re: MySQL Question

[David Hathaway]

I see you have some good responses so far, but that won't stop me from 
throwing in mine as well. :-)

I am quite goal oriented, so I would appreciate some moderately hard things 
to accomplish.  From there, the sky's the limit.  Here are some you can try.

1)  Attempt to enter the MySQL application from the command line.  That is 
open a terminal and run MySQL.  Sound easy?  Ha.  Hint: you will need to 
figure out how to enter user names and passwords

2) Once you succeed in getting a mysql> prompt, enter a command (like, 
"select dateTime, outTemp from archive limit 1;").

3) Now try to do this from the command line, like you would from a script.  
After that, do the same thing but placing your credentials in a config file 
so it isn't shown on the command line.

4) Now for something a little different, install MySQL Workbench, a GUI 
interface.  Once you can connect to that, you can run interactive queries 
to learn the SQL language.

5) Once you have some queries, create a script that you can run to give you 
useful information.  Like, the high temperatures for the past week, or the 
rainfall for the past week.  You know, apply what you have learned to 
something "practical".

MySQL really has two things to learn.  You need to learn how to access it 
and you need to learn the language.  Access can be really frustrating when 
all you want to do is learn the language, but it is vital.  Then, once you 
start learning the language you will go from brute force queries to 
increasingly elegant solutions.  You won't be happy seeing dates as 
numbers, you will want to see actual dates.  You might want to do a 
cumulative rain by day query for a year, and find there is an elegant way 
to do that.

Good luck!

Dave

On Saturday, September 15, 2018 at 9:09:10 AM UTC-5, John Clark wrote:
>
> I realize that this is a bit off topic, but having never even worried 
> about MySQL or SQL Lite before I encountered Weewx, I never felt the need 
> for learning it. However,  having recently
>
> 1. Retired, so I have time, and
>
> 2. realized it probably would be a good thing to learn because it might 
> help in some projects I am working on
>
> What and where is a good starting point for an absolute MySQL noob?
> -- 
> *John Clark *
>

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

[David Hathaway]

Paul,

I haven't tried this here, but I have used the meta tag in the header to 
auto-refresh pages.  I think this would be a trivial change to your index 
template if it does what you want.


  


https://www.w3schools.com/TAGS/att_meta_http_equiv.asp

Dave


On Tuesday, September 18, 2018 at 10:01:01 AM UTC-5, Paul Lacatus wrote:
>
> I have tried to change it in 
> /etc/weewx/skins/Highcharts_Belchertown/skin.conf and 
> /etc/weewx/skins/Belchertown/skin.conf to [Units]   [[Groups]]
>
> group_temperature  = degree_C
>
> but still the Today temperature  trend is in imperial units and all others 
> are in metric . Even on the Y axis  the unit is written degree Celsius but 
> the values are in Fahrenheit 
>
> you can check :
> http://www.paul-lacatus.ro:8881/weewx/belchertown/
>
> Other question : is possible to generate a Html code to force the Browser 
> to update on the page update ? I am using an android tablet with Chrome 
> browser to show the weews/belchertown page and for Android chrome is not 
> trivial to force an autoupdate 
>
> Thank you  all
> Paul 
>  
>
> On 15-Sep-18 00:04, Colin Larsen wrote:
>
> Better to do it in the weewx.conf then it isn't overwritten by updates
>
> On Sat, 15 Sep 2018, 08:58 Juan Antonio Mosquera, <
> juananton...@juanantoniomosquera.com > wrote:
>
> You have  to modify skin.conf of highcharts template. 
>
> Greetings.
>
> El viernes, 14 de septiembre de 2018, 18:10:09 (UTC+2), Paul Lacatus 
> escribió: 
>
> Maybe I just missed the explanation on HighCharts.  Still some strange 
> things on temperature charts . Maybe I have to wait more for graphs 
> updates.  In home page the indication on the graph are in Celsius but the 
> values are in Fahrenheit .  The same in Today graphs 
>
> On 14-Sep-18 18:50, Pat wrote:
>
> Don't forget to restart weewx once done
>
> On Friday, September 14, 2018 at 11:46:56 AM UTC-4, Pat wrote: 
>
> I thought I had updated the docs - guess I forgot.  
>
> Please add the metric updates to the Highcharts_Belchertown skin section 
> in weewx.conf too. 
>
> On Friday, September 14, 2018 at 11:39:09 AM UTC-4, Paul Lacatus wrote: 
>
> Dear Pat, 
>
> ...

-- 
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: Current Windspeed in Beaufort ? Bft?

[David Hathaway]

Thank you.  Worked perfectly for me.  Since we are likely to be hit by a 
tropical storm in the next day or two (I live in Houston, Texas), this will 
be pretty interesting.

On Tuesday, August 22, 2017 at 3:14:20 PM UTC-5, WindnFog wrote:
>
> If you want to avoid Java, I cobbled together some code based on gjr80's 
> template and added it to /etc/weewx/skins/Standard/index.html.tmpl as 
> follows:
>
> ##Calculate today's highest Beaufort based on wind speed in knots
>   
>   #if $varExists('day.windSpeed') and $day.windSpeed.max.raw is 
> not None
>   #if $unit.unit_type.windSpeed == 'mile_per_hour'
>   #set $kts = $day.windSpeed.max.raw * 0.8689762
>   #elif $unit.unit_type.windSpeed == 'km_per_hour'
> #set $kts = $day.windSpeed.max.raw * 0.539956
>   #elif $unit.unit_type.windSpeed == 'meter_per_second'
> #set $kts = $day.windSpeed.max.raw * 1.943844
>   #elif $unit.unit_type.windSpeed == 'knot'
> #set $kts = $day.windSpeed.max.raw
>   #else
> #set $kts = 0
>   #end if
>   #if $kts < 1
> #set $beaufort = 0
> #set $word_beaufort = 'Calm'
>   #elif $kts < 4
> #set $beaufort = 1
> #set $word_beaufort = 'Light air'
>   #elif $kts < 7
> #set $beaufort = 2
> #set $word_beaufort = 'Light breeze'
>   #elif $kts < 11
> #set $beaufort = 3
> #set $word_beaufort = 'Gentle breeze'
>   #elif $kts < 17
> #set $beaufort = 4
> #set $word_beaufort = 'Moderate breeze'
>   #elif $kts < 22
> #set $beaufort = 5
> #set $word_beaufort = 'Fresh breeze'
>   #elif $kts < 28
> #set $beaufort = 6
> #set $word_beaufort = 'Strong breeze'
>   #elif $kts < 34
> #set $beaufort = 7
> #set $word_beaufort = 'High wind'
>   #elif $kts < 41
> #set $beaufort = 8
> #set $word_beaufort = 'Gale'
>   #elif $kts < 48
> #set $beaufort = 9
> #set $word_beaufort = 'Strong gale'
>   #elif $kts < 56
> #set $beaufort = 10
> #set $word_beaufort = 'Storm'
>   #elif $kts < 64
> #set $beaufort = 11
> #set $word_beaufort = 'Violent storm'
>   #else
> #set $beaufort = 12
> #set $word_beaufort = 'Hurricane'
>   #end if
>   #else
> #set $beaufort = 'N/A'
>   #end if
>
>  Put the above somewhere near the top, and then modify the Since Midnight 
> table by adding a couple of lines in the High Wind row:
>
> 
>   High Wind
>   High Beaufort Scale
> 
> 
>   $day.wind.max from $day.wind.gustdir at $day.wind.maxtime
> 
>   $beaufort or $word_beaufort at $day.wind.maxtime
> 
>
> - Paul VE1DX
>
> https://www.ve1dx.net/
>
>
>
>
> On Sunday, March 16, 2014 at 12:50:02 PM UTC-3, Ronald Wildner wrote:
>>
>> Thanks !
>>  With $current.windSpeed.raw and some Javascript  it was easy and fits 
>> perfectly for me ! .raw was what I was looking for ;-)
>>
>>
>> Am Sonntag, 16. März 2014 12:53:38 UTC+1 schrieb Andrew Milner:
>>>
>>> the simplest way would be to replace $current.windSpeed with something 
>>> like (($current.windSpeed.raw + 5) * 5) in the templates wherever needed I 
>>> would have thought.  More comolex to actually add the unit type to be 
>>> generally available, but possible - read the user manual for more details 
>>> on unit types  - under extensions I think, but could be ustomisation - not 
>>> sure which it comes under!!
>>>
>>>
>>> On 16 March 2014 11:12, Ronald Wildner  wrote:
>>>
 Thanks for the quick anwer ...
 I am pretty new to weewx ...
  how can I now  add the calculated bft to my template ... (something 
 like $current.windSpeed.bft) ?
 Am Sonntag, 16. März 2014 09:08:27 UTC+1 schrieb Ronald Wildner:
>
> I am wondering if there is any hint to display current WindSpeed in 
> Beaufort !
> I used google and the search -function, but could not find anything 
> adequate ;-)
>
 -- 
 You received this message because you are subscribed to a topic in the 
 Google Groups "Weewx user's group" group.
 To unsubscribe from this topic, visit 
 https://groups.google.com/d/topic/weewx-user/b7TqpYD9sxY/unsubscribe - 
 private 
 
  - private 
 .
 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

[weewx-user] Re: UPS monitoring service

[David Hathaway]

+watching.

I recently got an APC and am doing the exact same thing, but I am using 
pwrstat since I have a Cyberpower APC.

On Wednesday, September 27, 2017 at 5:43:46 PM UTC-5, Joe Percival wrote:
>
> Back in the day, about 7 years ago, when I first built my weewx based 
> weather information server, one of the things I did was to build a custom 
> service that captured status from my UPS using apcupsd.  The line voltage 
> was stored in the database using an existing but unused parameter like leaf 
> temperature.  A graph of line voltage was then generated as part of the 
> report process and uploaded to my web server.
> For the new system I've just completed, I'm using NUT rather than apcupsd. 
> Has anyone built a service as described above using NUT?

-- 
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] Re: weewx.com bad Station Registry database?

[David Hathaway]

I'm glad this group exists and that search works. :-)  I was surprised it 
auto-suggested 'malformed' when I started typing. lol

Issue still exists, but at least I won't worry about it.

-- 
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] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

Xfinity crapped again, cutting my station off from the net.  I decided to 
try wunderfixer.

When run as

>> sudo wunderfixer -t

I get a lot of pseudo-published records, such as.

Using configuration file /etc/weewx/weewx.conf.
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
2016-11-02 00:00:00 CDT (1478062800); 30.014";  75.2F;  86%; 0.8 mph;  97 
deg; 2.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain  ... skipped.
2016-11-02 00:01:00 CDT (1478062860); 30.013";  75.2F;  86%; 0.2 mph;  97 
deg; 1.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain  ... skipped.

etc

However, run as 

>> sudo wunderfixer

I get:

Using configuration file /etc/weewx/weewx.conf.
Using database binding 'wx_binding', which is bound to database 
'archive_mysql'
2016-11-02 00:00:00 CDT (1478062800); 30.014";  75.2F;  86%; 0.8 mph;  97 
deg; 2.0 mph gust;  70.7F; 0.00" rain; 0.00" daily rain
Traceback (most recent call last):
  File "/usr/bin/wunderfixer", line 558, in 
main()
  File "/usr/bin/wunderfixer", line 276, in main
wunder.postData(record)
  File "/usr/bin/wunderfixer", line 387, in postData
for _key in weewx.restx.AmbientThread._formats:
AttributeError: type object 'AmbientThread' has no attribute '_formats'

What am I doing wrong?

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.

Re: [weewx-user] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

mwall and Gary,

Yes, it is 3.6.0.  I'll go ahead and update.  I didn't realize there was a
3.6.1 already. :-/

I'll report back on success or failure.

Dave

On Wed, Nov 2, 2016 at 8:57 PM, gjr80  wrote:

> Hi,
>
> What version of weewx are you running, 3.6.0? I am pretty sure this issue
> was fixed in 3.6.1. If you are on 3.6.0 you might want to try pulling down
> the current wunderfixer.py.
>
> 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/W2sBVQJmAQw/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] wunderfixer: OK with --test, fails when doing it for real

[David Hathaway]

Worked great!  Thanks ever so much!

Dave

On Wednesday, November 2, 2016 at 9:02:49 PM UTC-5, David Hathaway wrote:
>
> mwall and Gary,
>
> Yes, it is 3.6.0.  I'll go ahead and update.  I didn't realize there was a 
> 3.6.1 already. :-/
>
> I'll report back on success or failure.
>
> Dave
>
> On Wed, Nov 2, 2016 at 8:57 PM, gjr80  wrote:
>
>> Hi,
>>
>> What version of weewx are you running, 3.6.0? I am pretty sure this issue 
>> was fixed in 3.6.1. If you are on 3.6.0 you might want to try pulling down 
>> the current wunderfixer.py.
>>
>> 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/W2sBVQJmAQw/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.

[weewx-user] Re: Off topic - sql issue

[David Hathaway]

Based on the initial post, it seems you want all the columns for the latest 
datetime?  If so, I think y'all are working too hard:

Try,

SELECT *
FROM 'table_name'
ORDER BY datetime DESC
LIMIT 1

I put the various parts on separate lines for emphasis.  I'd have it all on 
one line, separated by spaces.

   - The *LIMIT 1* part says give me only one row
   - The *ORDER BY datetime DESC* part says to sort by datetime, biggest 
   values first
   - Together, these give the 1 row that has the highest datetime.


This should be a very efficient statement since it use core functions and 
the last record is probably still in MySQL's memory.

Dave


On Wednesday, November 9, 2016 at 12:59:17 AM UTC-6, Andrew Milner wrote:
>
> Thanks Gary - done my homework, created a subquery for today's readings 
> (since MySQL can't have a subquery in a view) and selected from that.  
> Still do not fully understand the where datetime is null part though - but 
> it works (down to a second now)
>
> On Wednesday, 9 November 2016 07:32:46 UTC+2, gjr80 wrote:
>>
>> The WHERE clause must be satisfied or surely there would be no results at 
>> all? 
>>
>> As for optimising, that is left as homework... Seriously, you might find 
>> some info by googling 'SQL optimise left join', quite a few results but a 
>> bit heavy for me. Sorry but it was a stretch coming up with the query.
>>
>> 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.

[weewx-user] Re: Wunderground postings

[David Hathaway]

Based on this idea, this weekend I finally remembered to create a cron task 
for wunderfixer.  The timing looks like 5 */11 * * *... which I intended to 
mean run at hours divisible by 11: 11:05 and 22:05.  I was surprised to see 
it also run at 12:05 AM.  I was writing and ask if anyone knew why I was 
getting this bonus run, when it struck me that midnight is 0:00.  And 0 is 
also evenly divisible by 11!  LOL, there is always some gotcha.

Thanks for the idea!  It is very helpful especially now that my cablemodem 
is dying daily and I have hours of time off-network.  My new modem is 
coming today, but I highly doubt I will ever see a day go by without 
wunderfixer filling in the gaps.

Dave

On Saturday, November 19, 2016 at 1:06:14 AM UTC-6, Andrew Milner wrote:
>
> I have been using weewx for a few years now, and have always thought that 
> although I have been uploading at 5 minute intervals WU was 'doing its own 
> thing'  when I viewed the station tables and saw intervals of 10 minutes 
> usually with the occasional 5 minute posting.  I had thought nothing of it 
> for ages!!
> Anyway, after having had success with wee_import I then decided to give 
> wunderfixer a go - so set it up to run via cron twice per day and have been 
> surprised to see 50-60 records being uploaded every time.  However, when I 
> now go back and check previous days' data I see table entries every 5 
> minutes.
> Does anyone have any idea what is happening??  weewx *appears* to upload 
> every 5 minutes, wu shows records for every 10 minutes (approx.).  
> wunderfixer runs and fills in the gaps and then wu seems to be happy and 
> retains the uploads.  I am baffled to put it mildly!!!
>
>   
>

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

[David Hathaway]

Checking the log, it looks like in the past 3 days the largest number of
records published is 143, which took 43 seconds.  I do believe I will
change to your timing.

Thanks,

Dave

On Tue, Nov 29, 2016 at 8:14 AM, Andrew Milner 
wrote:

> Yes, I specify 58 11,23 * * * * as my run times - but have had the
> midnight one sometimes not finish until after midnight (and thus appear to
> exit at the start of the next days' log)
>
>
> On Tuesday, 29 November 2016 15:39:30 UTC+2, David Hathaway wrote:
>>
>> Based on this idea, this weekend I finally remembered to create a cron
>> task for wunderfixer.  The timing looks like 5 */11 * * *... which I
>> intended to mean run at hours divisible by 11: 11:05 and 22:05.  I was
>> surprised to see it also run at 12:05 AM.  I was writing and ask if anyone
>> knew why I was getting this bonus run, when it struck me that midnight is
>> 0:00.  And 0 is also evenly divisible by 11!  LOL, there is always some
>> gotcha.
>>
>> Thanks for the idea!  It is very helpful especially now that my
>> cablemodem is dying daily and I have hours of time off-network.  My new
>> modem is coming today, but I highly doubt I will ever see a day go by
>> without wunderfixer filling in the gaps.
>>
>> Dave
>>
>> On Saturday, November 19, 2016 at 1:06:14 AM UTC-6, Andrew Milner wrote:
>>>
>>> I have been using weewx for a few years now, and have always thought
>>> that although I have been uploading at 5 minute intervals WU was 'doing its
>>> own thing'  when I viewed the station tables and saw intervals of 10
>>> minutes usually with the occasional 5 minute posting.  I had thought
>>> nothing of it for ages!!
>>> Anyway, after having had success with wee_import I then decided to give
>>> wunderfixer a go - so set it up to run via cron twice per day and have been
>>> surprised to see 50-60 records being uploaded every time.  However, when I
>>> now go back and check previous days' data I see table entries every 5
>>> minutes.
>>> Does anyone have any idea what is happening??  weewx *appears* to
>>> upload every 5 minutes, wu shows records for every 10 minutes (approx.).
>>> wunderfixer runs and fills in the gaps and then wu seems to be happy and
>>> retains the uploads.  I am baffled to put it mildly!!!
>>>
>>>
>>>
>> --
> 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/oh-nl8GhdOg/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.

[weewx-user] Re: Is it worth swapping from fine offset to Davis Vantage?

[David Hathaway]

Here's my input. I had a banana trees near my Vantage Pro, and pollen would 
clog the hole in the rain guage that fed the teeter-totter. We'd get rain, I'd 
see nothing recorded, and I would find the hole plugged and the bucket full. I 
now check whenever I expect rain. I also cut down the banana trees. 

In short, there is nothing superior about the Vantage to prevent clogging. It 
is way better than my WMR200 that it replaced in all regards (except 
price), but it is not spider proof.

-- 
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] How to detect/recover restx thread exiting?

[David Hathaway]

Every once in a while, I get an exception posting to Wunderground :

Dec  8 01:48:52 hathaway weewx[1353]: restx: Wunderground-PWS: Unexpected 
exception of type 
Dec  8 01:48:52 hathaway weewx[1353]: restx: Wunderground-PWS: Thread 
exiting. Reason: hostname 'weatherstation.wunderground.com' doesn't match 
either of '*.wpengine.com', 'wpengine.com'

Further, Wunderground has stopped sending me alerts that my station isn't 
reporting, so I may go many days without posting to WU.  And as of now, 
wunderfixer doesn't work to populate the history.

Is there a way to automatically detect that restx isn't running and to 
restart it?  Or to email me an alert?

-- 
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/760b4fe6-1a66-47dd-b08c-d11d5fdbbac3%40googlegroups.com.

Re: [weewx-user] How to detect/recover restx thread exiting?

[David Hathaway]

Thanks for this.  I'll give logwatch a try.  I appreciate the suggestion.


On Tue, Dec 10, 2019 at 8:36 AM Thomas Keffer  wrote:

> Wunderground has a habit of fiddling with their SSL certificates, and/or
> letting them expire, which can cause this error. See issue #413
> <https://github.com/weewx/weewx/issues/413>. There's a fix for this,
> appearing in V4. Instead of exiting, the thread will wait 60 minutes, then
> retry.
>
> In the meantime, you can try using logwatch
> <https://github.com/weewx/weewx/wiki/logwatch> to send you an email if
> the thread exits.
>
> -tk
>
> On Tue, Dec 10, 2019 at 6:15 AM David Hathaway 
> wrote:
>
>> Every once in a while, I get an exception posting to Wunderground :
>>
>> Dec  8 01:48:52 hathaway weewx[1353]: restx: Wunderground-PWS: Unexpected
>> exception of type 
>> Dec  8 01:48:52 hathaway weewx[1353]: restx: Wunderground-PWS: Thread
>> exiting. Reason: hostname 'weatherstation.wunderground.com' doesn't
>> match either of '*.wpengine.com', 'wpengine.com'
>>
>> Further, Wunderground has stopped sending me alerts that my station isn't
>> reporting, so I may go many days without posting to WU.  And as of now,
>> wunderfixer doesn't work to populate the history.
>>
>> Is there a way to automatically detect that restx isn't running and to
>> restart it?  Or to email me an alert?
>>
>> --
>> 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/760b4fe6-1a66-47dd-b08c-d11d5fdbbac3%40googlegroups.com
>> <https://groups.google.com/d/msgid/weewx-user/760b4fe6-1a66-47dd-b08c-d11d5fdbbac3%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "weewx-user" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/weewx-user/-IF4QjC82-w/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> weewx-user+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/weewx-user/CAPq0zEC4S16kLUb%2BzDP1MFdcL0raAFjmOoumqmzwRVDuccRhZQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/weewx-user/CAPq0zEC4S16kLUb%2BzDP1MFdcL0raAFjmOoumqmzwRVDuccRhZQ%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>

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

[weewx-user] Unable to wake up Vantage console

[David Hathaway]

I am unsure how to start with this issue.  I had to move out of my house 
for a month during renovations, and left the Davis Vantage console plugged 
into the garage to collect data.  I took the computer to the hotel to use 
for work, and I think WeeWX updated during that time.

Now that I am back in the house, I have connected the device back into the 
computer.  I got half a day of records, but then I started getting this 
*CRITICAL 
__main__: Unable to load driver: Unable to wake up Vantage console* error.

Maybe this is a quick fix?

Log to follow.

Dave

Mar 15 11:28:32 HP-Iron weewx[78695]:  * Starting weewx weather system weewx
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Initializing weewx 
version 4.7.0
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Using Python 3.8.10 
(default, Nov 26 2021, 20:14:08) #012[GCC 9.3.0]
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Platform 
Linux-5.13.0-35-generic-x86_64-with-glibc2.29
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Locale is 'en_US.UTF-8'
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: Debug is 0
Mar 15 11:28:32 HP-Iron weewx[78706] INFO __main__: PID file is 
/var/run/weewx.pid
Mar 15 11:28:32 HP-Iron weewx[78720] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar 15 11:28:32 HP-Iron weewx[78695]:...done.
Mar 15 11:28:53 HP-Iron weewx[78720] ERROR weewx.drivers.vantage: Unable to 
wake up console
Mar 15 11:28:53 HP-Iron weewx[78720] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 40, in loader
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 return VantageService(engine, config_dict)
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1916, in __init__
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 517, in __init__
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 self._setup()
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1335, in _setup
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 self.port.wakeup_console(max_tries=self.max_tries)
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 120, in 
wakeup_console
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 raise weewx.WakeupError("Unable to wake up Vantage console")
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL weewx.engine:  
 weewx.WakeupError: Unable to wake up Vantage console
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL __main__: Unable to load 
driver: Unable to wake up Vantage console
Mar 15 11:28:53 HP-Iron weewx[78720] CRITICAL __main__:   Exiting...

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

Re: [weewx-user] Unable to wake up Vantage console

[David Hathaway]

Thanks Greg.  It appears my computer has a bad USB port; I used the 
USB-serial connection.  I switched to a different port and wee_device 
--info returned device status.

However, now I get the following logs.

Dave

Mar 16 07:11:20 HP-Iron weewx[2377499]:  * Starting weewx weather system 
weewx
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Initializing weewx 
version 4.7.0
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Using Python 3.8.10 
(default, Nov 26 2021, 20:14:08) #012[GCC 9.3.0]
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Platform 
Linux-5.13.0-35-generic-x86_64-with-glibc2.29
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Locale is 
'en_US.UTF-8'
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Using configuration 
file /etc/weewx/weewx.conf
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Debug is 0
Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: PID file is 
/var/run/weewx.pid
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar 16 07:11:20 HP-Iron weewx[2377499]:...done.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: StdConvert target 
unit is 0x1
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.wxservices: 
StdWXCalculate will use data binding wx_binding
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Archive will use 
data binding wx_binding
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Record generation 
will be attempted in 'hardware'
Mar 16 07:11:20 HP-Iron weewx[2377529] ERROR weewx.engine: The archive 
interval in the configuration file (180) does not match the station 
hardware interval (60).
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Using archive 
interval of 60 seconds (specified by hardware)
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: StationRegistry: 
Station will be registered.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: Wunderground-PWS: 
Data for station KTXSUGAR19 will be posted
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: PWSweather: 
Posting not enabled.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: CWOP: Posting not 
enabled.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: WOW: Posting not 
enabled.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: AWEKAS: Posting 
not enabled.
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: 'pyephem' not 
detected, extended almanac data is not available
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO __main__: Starting up weewx 
version 4.7.0
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Clock error is 
-1556.87 seconds (positive is fast)
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.drivers.vantage: Clock 
set to 2022-03-16 07:11:21 CDT (1647432681)
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Using binding 
'wx_binding' to database 'weewx'
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.manager: Starting 
backfill of daily summaries
Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.manager: Daily summaries 
up to date
Mar 16 07:11:41 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: Unable 
to wake up console
Mar 16 07:11:41 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: DMPAFT 
try #1; error: Unable to wake up Vantage console
Mar 16 07:12:02 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: Unable 
to wake up console
Mar 16 07:12:02 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: DMPAFT 
try #2; error: Unable to wake up Vantage console
Mar 16 07:12:23 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: Unable 
to wake up console
Mar 16 07:12:23 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: DMPAFT 
try #3; error: Unable to wake up Vantage console
Mar 16 07:12:44 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: Unable 
to wake up console
Mar 16 07:12:44 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: DMPAFT 
try #4; error: Unable to wake up Vantage console
Mar 16 07:12:44 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: DMPAFT 
max tries (4) exceeded.
Mar 16 07:12:44 HP-Iron weewx[2377529] INFO weewx.engine: Main loop 
exiting. Shutting engine down.
Mar 16 07:12:44 HP-Iron weewx[2377529] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting archive data.
Mar 16 07:12:44 HP-Iron weewx[2377529] CRITICAL __main__:   Waiting 
60 seconds then retrying...
Mar 16 07:13:44 HP-Iron weewx[2377529] INFO __main__: retrying...
Mar 16 07:13:44 HP-Iron weewx[2377529] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
Mar 16 07:14:05 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: Unable 
to wake up console
Mar 16 07:14:05 HP-Iron weewx[2377529] ERROR weewx.engine: Import of driver 
failed: Unable to wake up Vantage console ()
Mar 16 07:14:05 HP-Iron weewx[2377529] CRITICAL weewx.engine:  
 Traceback (most recent call last):
Mar 16 07:14:05 HP-Iron weewx[2377529] CRITICAL weewx.engine:    
 Fil

Re: [weewx-user] Unable to wake up Vantage console

[David Hathaway]

Yes, this does feel like a bad cable or something.  Even cables wear out 
occasionally.

On Wednesday, March 16, 2022 at 8:11:55 AM UTC-5 tke...@gmail.com wrote:

> (You might get a little more information by setting debug=1 in the 
> configuration file, weewx.conf.)
>
> Things to try:
>
>- This still feels a lot like either a bad port, or a bad 
>serial-to-usb connector.
>- Another possibility is that another instance of weewxd is competing 
>for the port, although that would presumably be reflected in the log. 
>- Try rebooting the PC. 
>- Check the baudrate.
>
>
> On Wed, Mar 16, 2022 at 5:16 AM David Hathaway  
> wrote:
>
>> Thanks Greg.  It appears my computer has a bad USB port; I used the 
>> USB-serial connection.  I switched to a different port and wee_device 
>> --info returned device status.
>>
>> However, now I get the following logs.
>>
>> Dave
>>
>> Mar 16 07:11:20 HP-Iron weewx[2377499]:  * Starting weewx weather system 
>> weewx
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Initializing weewx 
>> version 4.7.0
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Using Python 3.8.10 
>> (default, Nov 26 2021, 20:14:08) #012[GCC 9.3.0]
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Platform 
>> Linux-5.13.0-35-generic-x86_64-with-glibc2.29
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Locale is 
>> 'en_US.UTF-8'
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Using configuration 
>> file /etc/weewx/weewx.conf
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: Debug is 0
>> Mar 16 07:11:20 HP-Iron weewx[2377510] INFO __main__: PID file is 
>> /var/run/weewx.pid
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Mar 16 07:11:20 HP-Iron weewx[2377499]:...done.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: StdConvert 
>> target unit is 0x1
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.wxservices: 
>> StdWXCalculate will use data binding wx_binding
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Archive will 
>> use data binding wx_binding
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Record 
>> generation will be attempted in 'hardware'
>> Mar 16 07:11:20 HP-Iron weewx[2377529] ERROR weewx.engine: The archive 
>> interval in the configuration file (180) does not match the station 
>> hardware interval (60).
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Using archive 
>> interval of 60 seconds (specified by hardware)
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: StationRegistry: 
>> Station will be registered.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: 
>> Wunderground-PWS: Data for station KTXSUGAR19 will be posted
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: PWSweather: 
>> Posting not enabled.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: CWOP: Posting 
>> not enabled.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: WOW: Posting not 
>> enabled.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.restx: AWEKAS: Posting 
>> not enabled.
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: 'pyephem' not 
>> detected, extended almanac data is not available
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO __main__: Starting up weewx 
>> version 4.7.0
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Clock error is 
>> -1556.87 seconds (positive is fast)
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.drivers.vantage: Clock 
>> set to 2022-03-16 07:11:21 CDT (1647432681)
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.engine: Using binding 
>> 'wx_binding' to database 'weewx'
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.manager: Starting 
>> backfill of daily summaries
>> Mar 16 07:11:20 HP-Iron weewx[2377529] INFO weewx.manager: Daily 
>> summaries up to date
>> Mar 16 07:11:41 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Mar 16 07:11:41 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: 
>> DMPAFT try #1; error: Unable to wake up Vantage console
>> Mar 16 07:12:02 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: 
>> Unable to wake up console
>> Mar 16 07:12:02 HP-Iron weewx[2377529] ERROR weewx.drivers.vantage: 
>> DMPAFT try #2; error: Unable to wake up Vantage console
>> Mar 16 07:12:23 HP-Iron weewx[2

Re: [weewx-user] Unable to wake up Vantage console

[David Hathaway]

This is a Davis serial-USB adapter, inside the console.  It has worked 
flawlessly for 3 years.  Maybe it just had one unplugging too many.

On Wednesday, March 16, 2022 at 9:39:50 AM UTC-5 tom.h...@gmail.com wrote:

> Just a thought to add, but where did the FTDI serial-USB adapter come 
> from? From my work in ham radio I've found that most of them are Chinese 
> fakes, not actually licensed and compatible, just a quick reverse-engineer 
> and ship it. Took me three tries ordering "real" FTDI adapters before I got 
> one that was actually "real". The current one I use was almost $40 if I 
> recall and is 100% rock solid, while the others were $10-20 and "flaky" - 
> drop connections, random timeouts, etc., sometimes immediately and 
> sometimes after a day or three. If you have one from Davis then I'd trust 
> it as "real".
>
>
> On Wednesday, March 16, 2022 at 5:11:55 AM UTC-8 tke...@gmail.com wrote:
>
>> (You might get a little more information by setting debug=1 in the 
>> configuration file, weewx.conf.)
>>
>> Things to try:
>>
>>- This still feels a lot like either a bad port, or a bad 
>>serial-to-usb connector.
>>- Another possibility is that another instance of weewxd is competing 
>>for the port, although that would presumably be reflected in the log. 
>>- Try rebooting the PC. 
>>- Check the baudrate.
>>
>>
>> On Wed, Mar 16, 2022 at 5:16 AM David Hathaway  
>> wrote:
>>
>>> Thanks Greg.  It appears my computer has a bad USB port; I used the 
>>> USB-serial connection.  I switched to a different port and wee_device 
>>> --info returned device status.
>>
>>
>>>

-- 
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/7ba19899-db6b-4ebe-b74f-5c1a61c364d6n%40googlegroups.com.

Re: [weewx-user] Re: Davis Data Logger - Issue

[David Hathaway]

Also, I bought a new USB data logger as I thought that could be the issue.  
It was not.

Dave

On Monday, May 9, 2022 at 8:32:18 AM UTC-5 David Hathaway wrote:

> If you need another system to test on, mine reliably has this issue.  I 
> talked about it in Unable to wake up Vantage console 
> <https://groups.google.com/g/weewx-user/c/tzEYLxJBVy8/m/691INrMDAAAJ> a 
> couple months ago.  This is so persistent that I have jobs that starts 
> WeeWX every five minutes and then turn it off a minute later.  Any longer 
> and WeeWX will abend. (Another job starts wee_reports to generate graphs, 
> etc)
>
> The log looks like this,
>
> May  9 08:20:00 HP-Iron weewx[2476847]:  * Starting weewx weather system 
> weewx
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Initializing weewx 
> version 4.8.0
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Using Python 3.8.10 
> (default, Mar 15 2022, 12:22:08) #012[GCC 9.4.0]
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Platform 
> Linux-5.13.0-37-generic-x86_64-with-glibc2.29
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Locale is 
> 'en_US.UTF-8'
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Using configuration 
> file /etc/weewx/weewx.conf
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: Debug is 0
> May  9 08:20:00 HP-Iron weewx[2476858] INFO __main__: PID file is 
> /var/run/weewx.pid
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Loading station 
> type Vantage (weewx.drivers.vantage)
> May  9 08:20:00 HP-Iron weewx[2476847]:...done.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: StdConvert 
> target unit is 0x1
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.wxservices: 
> StdWXCalculate will use data binding wx_binding
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Archive will use 
> data binding wx_binding
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Record 
> generation will be attempted in 'hardware'
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Using archive 
> interval of 300 seconds (specified by hardware)
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: StationRegistry: 
> Station will be registered.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: Wunderground-PWS: 
> Data for station KTXSUGAR19 will be posted
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: PWSweather: 
> Posting not enabled.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: CWOP: Posting not 
> enabled.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: WOW: Posting not 
> enabled.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.restx: AWEKAS: Posting 
> not enabled.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: 'pyephem' not 
> detected, extended almanac data is not available
> May  9 08:20:00 HP-Iron weewx[2476872] INFO __main__: Starting up weewx 
> version 4.8.0
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Clock error is 
> -0.49 seconds (positive is fast)
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Using binding 
> 'wx_binding' to database 'weewx'
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.manager: Starting 
> backfill of daily summaries
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.manager: Daily summaries 
> up to date
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.wxxtypes: Type beaufort 
> has been deprecated. Use unit beaufort instead.
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.manager: Added record 
> 2022-05-09 08:20:00 CDT (1652102400) to database 'weewx'
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.manager: Added record 
> 2022-05-09 08:20:00 CDT (1652102400) to daily summary in 'weewx'
> May  9 08:20:00 HP-Iron weewx[2476872] INFO weewx.engine: Starting main 
> packet loop.
> May  9 08:20:01 HP-Iron weewx[2476872] INFO weewx.restx: Wunderground-PWS: 
> Published record 2022-05-09 08:20:00 CDT (1652102400)
> May  9 08:20:01 HP-Iron weewx[2476872] INFO weewx.restx: StationRegistry: 
> Published record 2022-05-09 08:20:00 CDT (1652102400)
> May  9 08:20:05 HP-Iron weewx[2476872] ERROR weewx.drivers.vantage: LOOP 
> try #1; error: Expected to read 99 chars; got 0 instead
> May  9 08:20:09 HP-Iron weewx[2476872] ERROR weewx.drivers.vantage: LOOP 
> try #2; error: Expected to read 99 chars; got 0 instead
> May  9 08:20:13 HP-Iron weewx[2476872] ERROR weewx.drivers.vantage: LOOP 
> try #3; error: Expected to read 99 chars; got 20 instead
> May  9 08:20:17 HP-Iron weewx[2476872] ERROR weewx.drivers.vantage: LOOP 
> try #4; error: Expected to read 99 chars; got 19 instead
> May  9 08:20:17 HP-Iron weewx[24

[weewx-user] Re: Davis Data Logger - Issue

[David Hathaway]

I wish mine would settle down.  I do the stop/start jobs because mine 
eventually exits the engine.

Dave

May  9 12:56:30 HP-Iron weewx[3016530] INFO weewx.restx: Wunderground-PWS: 
Published record 2022-05-09 12:55:00 CDT (1652118900)
May  9 12:56:55 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: LOOP 
try #1; error: Expected to read 99 chars; got 0 instead
May  9 12:56:59 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: LOOP 
try #2; error: Expected to read 99 chars; got 10 instead
May  9 12:57:03 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: LOOP 
try #3; error: Expected to read 99 chars; got 20 instead
May  9 12:57:07 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: LOOP 
try #4; error: Expected to read 99 chars; got 20 instead
May  9 12:57:07 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: LOOP 
max tries (4) exceeded.
May  9 12:57:07 HP-Iron weewx[3016530] INFO weewx.engine: Main loop 
exiting. Shutting engine down.
May  9 12:57:07 HP-Iron weewx[3016530] CRITICAL __main__: Caught 
WeeWxIOError: Max tries exceeded while getting LOOP data.
May  9 12:57:07 HP-Iron weewx[3016530] CRITICAL __main__:   Waiting 
60 seconds then retrying...
May  9 12:58:07 HP-Iron weewx[3016530] INFO __main__: retrying...
May  9 12:58:07 HP-Iron weewx[3016530] INFO weewx.engine: Loading station 
type Vantage (weewx.drivers.vantage)
May  9 12:58:07 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
SerialException on read.
May  9 12:58:07 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
 read failed: device reports readiness to read but returned no data (device 
disconnected or multiple access on port?)
May  9 12:58:07 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
 Is there a competing process running??
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: No 
 received from console
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #0: 'No  received from Vantage console'
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: No 
 received from console
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #1: 'No  received from Vantage console'
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: No 
 received from console
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #2: 'No  received from Vantage console'
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: No 
 received from console
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: 
_determine_hardware; retry #3: 'No  received from Vantage console'
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.drivers.vantage: Unable 
to read hardware type; raise WeeWxIOError
May  9 12:58:08 HP-Iron weewx[3016530] ERROR weewx.engine: Import of driver 
failed: Unable to read hardware type ()
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 Traceback (most recent call last):
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 self.console = loader_function(config_dict, self)
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 40, in loader
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 return VantageService(engine, config_dict)
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1916, in __init__
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 Vantage.__init__(self, **config_dict[DRIVER_NAME])
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 517, in __init__
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 self._setup()
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1339, in _setup
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 self.hardware_type = self._determine_hardware()
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:    
 File "/usr/share/weewx/weewx/drivers/vantage.py", line 1330, in 
_determine_hardware
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 raise weewx.WeeWxIOError("Unable to read hardware type")
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL weewx.engine:  
 weewx.WeeWxIOError: Unable to read hardware type
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL __main__: Unable to load 
driver: Unable to read hardware type
May  9 12:58:08 HP-Iron weewx[3016530] CRITICAL __main__:  
 Exiting...

On Monday, May 9, 2022 at 9:08:28 

Re: [weewx-user] Weewx doesn't start anymore after update from 5.0.0 to 5.0.1-3

[David Hathaway]

I had this same issue immediately after updating from 5.0.0 to 5.0.1, the 
exact same error.

*sudo lsof /dev/ttyUSB0*


threw an error.

I rebooted the machine and now weewx is running normally again.


On Monday, February 5, 2024 at 7:03:18 AM UTC-6 Tom Keffer wrote:

> Make sure there isn't another process claiming /dev/ttyUSB0. The process 
> "modemmanager" is a common one.
>
> To see what processes are using /dev/ttyUSB0 try
>
> *sudo lsof /dev/ttyUSB0*
>
>
> -tk
>
> On Sun, Feb 4, 2024 at 11:40 PM hb9...@gmail.com  wrote:
>
>> I get a permission error for /dev/ttyUSB0
>> However, there should be no problem accessing ttyUSB0 (Vantage driver)
>> weectl device --info runs just fine:
>> ---
>> # weectl device --info
>> Using configuration file /etc/weewx/weewx.conf
>> Using driver weewx.drivers.vantage.
>> Using Vantage driver version 3.6.2 (weewx.drivers.vantage)
>> Querying...
>> Davis Vantage EEPROM settings:
>> 
>> CONSOLE TYPE:   Vantage Vue
>> (etc.)
>> ---
>>
>>
>> × weewx.service - WeeWX
>>  Loaded: loaded (/lib/systemd/system/weewx.service; enabled; preset: 
>> enabled)
>>  Active: failed (Result: exit-code) since Mon 2024-02-05 08:31:01 
>> CET; 2s ago
>>Duration: 100ms
>>Docs: https://weewx.com/docs
>> Process: 2627140 ExecStart=weewxd /etc/weewx/weewx.conf (code=exited, 
>> status=4)
>>Main PID: 2627140 (code=exited, status=4)
>> CPU: 89ms
>>
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine:  
>> 
>> ^
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/serial/serialutil.py", line 244, in __init__
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine:  
>>  self.open()
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine: File 
>> "/usr/lib/python3/dist-packages/serial/serialposix.py", line 325, in open
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine:  
>>  raise SerialException(msg.errno, "could not open port {}: 
>> {}".format(self._port, msg))
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL weewx.engine:  
>>  serial.serialutil.SerialException: [Errno 16] could not open port 
>> /dev/ttyUSB0: [Errno 16] Device or resource busy: '/dev/ttyUSB0'
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL __main__: Unable to load 
>> driver: [Errno 16] could not open port /dev/ttyUSB0: [Errno 16] Device or 
>> resource busy: '/dev/ttyUSB0'
>> Feb 05 08:31:01 weewxd[2627140]: CRITICAL __main__:   Exiting...
>> Feb 05 08:31:01 systemd[1]: weewx.service: Main process exited, 
>> code=exited, status=4/NOPERMISSION
>> Feb 05 08:31:01 systemd[1]: weewx.service: Failed with result 'exit-code'.
>>
>> -- 
>> 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/8fc2aaad-705d-45ff-9e1b-f2a80b84d48dn%40googlegroups.com
>>  
>> 
>> .
>>
>

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

Re: [weewx-user] 4.9.1 issue

[David Hathaway]

I've had a version of this issue since upgrading to 4.8.0.  In addition to 
the "Caught WeeWxIOError: Max tries exceeded while getting LOOP data" 
error, I have "Expected X chars, got Y " errors too.

Oct 28 11:10:15 HP-Iron weewx[3203645] ERROR weewx.drivers.vantage: LOOP 
try #1; error: Expected to read 99 chars; got 0 instead
Oct 28 11:10:19 HP-Iron weewx[3203645] ERROR weewx.drivers.vantage: LOOP 
try #2; error: Expected to read 99 chars; got 11 instead
Oct 28 11:10:23 HP-Iron weewx[3203645] ERROR weewx.drivers.vantage: LOOP 
try #3; error: Expected to read 99 chars; got 20 instead

It will run for a little bit, then eventually fail.  I have cron jobs that 
kill WeeWX and starts it again 15 minutes later.  It will catch up and then 
will start having errors and either die, or it is killed because it will 
fail anyways.

I'm on 4.8.0.  I'll see if 4.9.1 improves things.

Dave

On Friday, October 28, 2022 at 10:23:31 AM UTC-5 tke...@gmail.com wrote:

> Marius, that is a much older problem with several solutions. See the 
> *Troubleshooting 
> Davis stations guide 
> *
>  
> in the wiki.
>
> On Fri, Oct 28, 2022 at 8:18 AM Marius Schamschula  
> wrote:
>
>> I ran into the same issue yesterday when upgrading my RaspberryPI.
>>
>> The device had changed from /dev/ttyUSB0 to /dev/ttyUSB1
>>
>> I updated the weewx.conf file and all is well.
>>
>> On Oct 28, 2022, at 9:12 AM, wfs...@gmail.com  wrote:
>>
>> I just updated to 4.9.1 and am having similar problems..."unable to wake 
>> up Vantage console".  I have a VP1 and I've rebooted the Pi and unplugged 
>> and replugged the serial-to-USB interface.
>>
>> At reboot when Weewx first tries to start, it gets the unable to wakeup 
>> error.  If I do a sudo /etc/init.d/weewx stop and then sudo 
>> /etc/init.d/weewx start, it starts OK.  But I have yet to see it process an 
>> archive interval correctly.  It's getting an unable to wakeup error every 
>> time. 
>>
>> FWIW, I was watching the syslog with tail -f and the try errors all 
>> spilled out at once, like it wasn't pausing between retries. 
>>
>> My setup up until now has been very stable.  I'll go for months without 
>> any errors.
>>
>> At update, I chose to keep my current weewx.conf, and I haven't made any 
>> changes.  The only somewhat unexpected difference between my weewx.conf and 
>> weewx.conf-4.9.1 is that the socket timeout parameter is not in 4.9.1.  
>> But that seems unrelated, and it's still in my weewx.conf anyway.
>>
>> Walt
>>
>> At initial startup:
>>
>> Oct 28 08:20:56 raspberrypi weewx[907] INFO weewx.engine: Loading station 
>> type Vantage (weewx.drivers.vantage)
>> Oct 28 08:20:56 raspberrypi weewx[894]: Starting weewx weather system: 
>> weewx.
>> Oct 28 08:20:56 raspberrypi systemd[1]: Started LSB: weewx weather system.
>> Oct 28 08:20:56 raspberrypi weewx[907] ERROR weewx.drivers.vantage: 
>> Unable to wake up Vantage console
>> Oct 28 08:20:56 raspberrypi weewx[907] ERROR weewx.engine: Import of 
>> driver failed: Unable to wake up Vantage console (> 'weewx.WakeupError'>)
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:  
>>  Traceback (most recent call last):
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/engine.py", line 119, in setupStation
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>self.console = loader_function(config_dict, self)
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 40, in loader
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>return VantageService(engine, config_dict)
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1939, in __init__
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>Vantage.__init__(self, **config_dict[DRIVER_NAME])
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 521, in __init__
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>self._setup()
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 1340, in _setup
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>self.port.wakeup_console(max_tries=self.max_tries)
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>  File "/usr/share/weewx/weewx/drivers/vantage.py", line 118, in 
>> wakeup_console
>> Oct 28 08:20:56 raspberrypi weewx[907] CRITICAL weewx.engine:    
>>raise weewx.WakeupError("Unable to wake up Vantage console")
>> Oct 28 08:20:56 raspberrypi w

[weewx-user] Re: Access OGC Servers to Download Weather Maps, Warn Maps, Satellite Pictures etc.

[David Hathaway]

This is really interesting. Can you get underlaying geo features, like 
roads or topology?

Dave

On Saturday, August 17, 2024 at 10:25:44 AM UTC-5 Karen K wrote:

>
>- I added an English description, containing an example for querying 
>the NOAA server: Query Open Geospatial Consortium (OGC) Servers 
>(English) 
>
> 
>.
>- The german description as at: Open Geospatial Consortium (OGC) 
>Server abfragen 
>
> 
>.
>
>
> A lot of weather services (like NOAA, DWD etc.) operate an OGC server to 
> provide weather maps, warnings maps, satellite pictures etc. What data to 
> download is defined by a special set of URL parameters. weewx-DWD 
>  provides a configuration interface 
> to access such servers. You can easily set up the download parameters in 
> weewx.conf as described in the Wiki pages mentioned above.
>
> Besides querying OGC servers the module can also download arbitrary files 
> from every server specified in weewx.conf by the url key.
>
>

-- 
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/4db0e05a-742c-4a46-b4d6-6ee1493bb711n%40googlegroups.com.