Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Philip Kutzenco]

Hmm. I think galfert is correct. I believe as long as your weewx 
implementation is sending "quality data to pwsweather.com monthly, use of 
the API is free. Sorry for the false alarm.

On Friday, April 24, 2020 at 12:49:03 PM UTC-4, Philip Kutzenco wrote:
>
> I signed up. However, it looks to me that having a PWSweather account lets 
> you get an Aeris Weather account (which is linked), but when I go to the 
> API site with that account, they only offer a 30 day free trial. After that 
> there is a monthly or annual cost.for the API subscription. Am I missing 
> something?
>
> On Thursday, April 23, 2020 at 1:25:18 PM UTC-4, galfert wrote:
>>
>> Aeris Weather seems to be a replacement for Dark Sky that people are 
>> going with. If you upload to PWSweather then you can get a free API key to 
>> Aeris Weather.
>> https://www.aerisweather.com/signup/pws/
>>
>>

-- 
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/91518c36-c95e-4daa-8741-b33ed0a06638%40googlegroups.com.

Re: [weewx-user] Thanks a Lot Darksky (NOT!!)

[Philip Kutzenco]

I signed up. However, it looks to me that having a PWSweather account lets 
you get an Aeris Weather account (which is linked), but when I go to the 
API site with that account, they only offer a 30 day free trial. After that 
there is a monthly or annual cost.for the API subscription. Am I missing 
something?

On Thursday, April 23, 2020 at 1:25:18 PM UTC-4, galfert wrote:
>
> Aeris Weather seems to be a replacement for Dark Sky that people are going 
> with. If you upload to PWSweather then you can get a free API key to Aeris 
> Weather.
> https://www.aerisweather.com/signup/pws/
>
>

-- 
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/ef73fd6a-0d5b-4494-9d88-87274b891274%40googlegroups.com.

[weewx-user] Re: it misses the time display and forecasts

[Philip Kutzenco]

OK. Great that it is working for you!
phil

On Monday, May 13, 2019 at 1:58:58 PM UTC-4, Patrick Tranchant wrote:
>
> sorry, 
>
> I don't know that he did but it works .
>
>
> On Monday, May 13, 2019 at 7:55:30 PM UTC+2, Patrick Tranchant wrote:
>>
>> hello Philip
>>
>> see end pf page of code source  : 
>>
>>   
>>
>> but it is OK now, PAT watched my website the last week, I don't know that I 
>> done but it works .
>> Thanks for you
>> Patrick
>>
>>
>> On Monday, May 13, 2019 at 7:02:14 PM UTC+2, Philip Kutzenco wrote:
>>>
>>> Patrick,
>>>
>>> What version of the Belchertown skin are you using? If you restart WeeWX 
>>> and capture the syslog, it should show the version the first time the skin 
>>> executes. Alternatively, on your web page do a View Page Source and scroll 
>>> to the bottom. You'll see the version there.
>>>
>>> On Monday, May 6, 2019 at 2:03:48 PM UTC-4, Patrick Tranchant wrote:
>>>>
>>>> hi every body,
>>>>
>>>> since yesterday , I had this with skin "Belchertown"; it is ok with 
>>>> skin "Seasons".
>>>>
>>>> it misses the time display and forecasts and graphs on home page !!!
>>>> an idea, the logs are corrects for Belchertown
>>>>
>>>> May  6 20:00:16 raspberrypi weewx[22084]: manager: Added record 
>>>> 2019-05-06 20:00:00 CEST (1557165600) to database 'weewx.sdb'
>>>> May  6 20:00:16 raspberrypi weewx[22084]: manager: Added record 
>>>> 2019-05-06 20:00:00 CEST (1557165600) to daily summary in 'weewx.sdb'
>>>> May  6 20:00:19 raspberrypi weewx[22084]: cheetahgenerator: Generated 8 
>>>> files for report SeasonsReport in 2.81 seconds
>>>> May  6 20:00:26 raspberrypi weewx[22084]: imagegenerator: Generated 28 
>>>> images for SeasonsReport in 6.47 seconds
>>>> May  6 20:00:26 raspberrypi weewx[22084]: copygenerator: copied 0 files 
>>>> to /var/www/html/weewx
>>>> May  6 20:00:26 raspberrypi weewx[22084]: cheetahgenerator: Generated 7 
>>>> files for report SmartphoneReport in 0.23 seconds
>>>> May  6 20:00:29 raspberrypi weewx[22084]: imagegenerator: Generated 14 
>>>> images for SmartphoneReport in 2.88 seconds
>>>> May  6 20:00:29 raspberrypi weewx[22084]: copygenerator: copied 0 files 
>>>> to /var/www/html/weewx/smartphone
>>>> May  6 20:00:29 raspberrypi weewx[22084]: cheetahgenerator: Generated 1 
>>>> files for report MobileReport in 0.08 seconds
>>>> May  6 20:00:30 raspberrypi weewx[22084]: imagegenerator: Generated 4 
>>>> images for MobileReport in 0.53 seconds
>>>> May  6 20:00:30 raspberrypi weewx[22084]: copygenerator: copied 0 files 
>>>> to /var/www/html/weewx/mobile
>>>> May  6 20:00:31 raspberrypi weewx[22084]: Belchertown Extension: New 
>>>> forecast file downloaded to 
>>>> /var/www/html/weewx/belchertown/json/darksky_forecast.json
>>>> May  6 20:00:34 raspberrypi weewx[22084]: cheetahgenerator: Generated 
>>>> 14 files for report Belchertown in 3.73 seconds
>>>> May  6 20:00:34 raspberrypi weewx[22084]: copygenerator: copied 1 files 
>>>> to /var/www/html/weewx/belchertown
>>>> May  6 20:00:50 raspberrypi weewx[22084]: cheetahgenerator: Generated 4 
>>>> files for report Highcharts_Belchertown in 16.39 seconds
>>>> May  6 20:00:50 raspberrypi weewx[22084]: copygenerator: copied 0 files 
>>>> to /var/www/html/weewx/belchertown
>>>>
>>>>
>>>> Patrick
>>>>
>>>

-- 
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/1796024b-b50f-4d40-822b-a62d5bc4bf88%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Re: it misses the time display and forecasts

[Philip Kutzenco]

Patrick,

What version of the Belchertown skin are you using? If you restart WeeWX 
and capture the syslog, it should show the version the first time the skin 
executes. Alternatively, on your web page do a View Page Source and scroll 
to the bottom. You'll see the version there.

On Monday, May 6, 2019 at 2:03:48 PM UTC-4, Patrick Tranchant wrote:
>
> hi every body,
>
> since yesterday , I had this with skin "Belchertown"; it is ok with skin 
> "Seasons".
>
> it misses the time display and forecasts and graphs on home page !!!
> an idea, the logs are corrects for Belchertown
>
> May  6 20:00:16 raspberrypi weewx[22084]: manager: Added record 2019-05-06 
> 20:00:00 CEST (1557165600) to database 'weewx.sdb'
> May  6 20:00:16 raspberrypi weewx[22084]: manager: Added record 2019-05-06 
> 20:00:00 CEST (1557165600) to daily summary in 'weewx.sdb'
> May  6 20:00:19 raspberrypi weewx[22084]: cheetahgenerator: Generated 8 
> files for report SeasonsReport in 2.81 seconds
> May  6 20:00:26 raspberrypi weewx[22084]: imagegenerator: Generated 28 
> images for SeasonsReport in 6.47 seconds
> May  6 20:00:26 raspberrypi weewx[22084]: copygenerator: copied 0 files to 
> /var/www/html/weewx
> May  6 20:00:26 raspberrypi weewx[22084]: cheetahgenerator: Generated 7 
> files for report SmartphoneReport in 0.23 seconds
> May  6 20:00:29 raspberrypi weewx[22084]: imagegenerator: Generated 14 
> images for SmartphoneReport in 2.88 seconds
> May  6 20:00:29 raspberrypi weewx[22084]: copygenerator: copied 0 files to 
> /var/www/html/weewx/smartphone
> May  6 20:00:29 raspberrypi weewx[22084]: cheetahgenerator: Generated 1 
> files for report MobileReport in 0.08 seconds
> May  6 20:00:30 raspberrypi weewx[22084]: imagegenerator: Generated 4 
> images for MobileReport in 0.53 seconds
> May  6 20:00:30 raspberrypi weewx[22084]: copygenerator: copied 0 files to 
> /var/www/html/weewx/mobile
> May  6 20:00:31 raspberrypi weewx[22084]: Belchertown Extension: New 
> forecast file downloaded to 
> /var/www/html/weewx/belchertown/json/darksky_forecast.json
> May  6 20:00:34 raspberrypi weewx[22084]: cheetahgenerator: Generated 14 
> files for report Belchertown in 3.73 seconds
> May  6 20:00:34 raspberrypi weewx[22084]: copygenerator: copied 1 files to 
> /var/www/html/weewx/belchertown
> May  6 20:00:50 raspberrypi weewx[22084]: cheetahgenerator: Generated 4 
> files for report Highcharts_Belchertown in 16.39 seconds
> May  6 20:00:50 raspberrypi weewx[22084]: copygenerator: copied 0 files to 
> /var/www/html/weewx/belchertown
>
>
> Patrick
>

-- 
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/7cc836a1-a8d2-4665-8fb5-9eb89e101eb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[weewx-user] Database not updating - any advice to minimize data loss?

[Philip Kutzenco]

I had a power outage about 30 hours ago and just realized that, since then, 
my weewx.sdb database is not being updated. I first thought that the 
database was damaged when the Raspberry Pi running weewx took the hit. 
However, I can open the database in sqlite3 and it looks ok. I also ran 
wee_database --reconfigure. I renamed the newly built database, but it's 
still not being updated by weewx.

So, I'm assuming my Davis Vantage Vue console (with a USB data module 
connected to the Raspberry Pi) is what got hung. That console, while 
plugged in, does also have batteries, but I'm still guessing it took a hit 
from the power outage. I know that I can reset the memory in the 
console/data module, but I'd lose 30 hours of data (not really the end of 
the world). However, is there anything I can do to avoid losing that data?

Thanks in advance.
phil

-- 
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 0.8.1 released

[Philip Kutzenco]

See my post above in this topic : 
https://groups.google.com/d/msg/weewx-user/ARBHWDXiDpQ/7cz4m-Q7BAAJ. 
<https://groups.google.com/d/msg/weewx-user/ARBHWDXiDpQ/7cz4m-Q7BAAJ>

phil


On Monday, December 10, 2018 at 11:22:58 AM UTC-5, Wes Witt wrote:
>
> following. i'm interested in using apptemp to but would like to know what 
> is necessary to get the archive table configured properly.
>
> On Monday, December 10, 2018 at 7:54:39 AM UTC-8, Philip Kutzenco wrote:
>>
>> This is likely a naive question on my part. But did you extend the schema 
>> on the archive table for your database to include appTemp? Assuming so, did 
>> you rebuild the daily value tables? Are the values in the archive table and 
>> the archive_day_appTemp table being populated? When I look at your website, 
>> your daily.json data shows appTemp with a value of "N/A".phil
>>
>>
>> On Monday, December 10, 2018 at 10:09:52 AM UTC-5, G Hammer wrote:
>>>
>>> Here's the rest of the pertinent log entries that Groups cut off:
>>> Dec 10 09:55:50 ftp weewx[13683]:   raise weedb.
>>> NoColumnError(e)
>>> Dec 10 09:55:50 ftp weewx[13683]:   NoColumnError: no such 
>>> column: appTemp
>>> Dec 10 09:55:50 ftp weewx[13683]:   Generator terminated
>>> Dec 10 09:55:50 ftp weewx[13683]: copygenerator: copied 0 files to /home
>>> /weewx/public_html/weather
>>>
>>>
>>>
>>> On Monday, December 10, 2018 at 10:07:01 AM UTC-5, G Hammer wrote:
>>>>
>>>> Pat,
>>>>
>>>> When I have show_apptemp=1 I do see the Feels like temp as I expect.
>>>> If I set highcharts_show_apptemp = 1 I do not get an apptemp plot, the 
>>>> report generator errors out:
>>>> Dec 10 09:55:50 ftp weewx[13683]: reportengine: Caught unrecoverable 
>>>> exception in generator weewx.cheetahgenerator.CheetahGenerator
>>>> Dec 10 09:55:50 ftp weewx[13683]:   no such column: appTemp
>>>> Dec 10 09:55:50 ftp weewx[13683]:   Traceback (most recent 
>>>> call last):
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
>>>> Dec 10 09:55:50 ftp weewx[13683]:   obj.start()
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
>>>> Dec 10 09:55:50 ftp weewx[13683]:   self.run()
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
>>>> Dec 10 09:55:50 ftp weewx[13683]:   ngen = self.
>>>> generate(gen_dict[section_name], self.gen_ts)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>>>> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.
>>>> generate(section[subsection], gen_ts)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>>>> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.
>>>> generate(section[subsection], gen_ts)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
>>>> Dec 10 09:55:50 ftp weewx[13683]:   default_binding)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in 
>>>> _getSearchList
>>>> Dec 10 09:55:50 ftp weewx[13683]:   searchList += obj.
>>>> get_extension_list(timespan, db_lookup)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/user/belchertown_highchartsSearchX.py", line 85, in 
>>>> get_extension_list
>>>> Dec 10 09:55:50 ftp weewx[13683]:   (time_start_vt, 
>>>> time_stop_vt, appTemp_vt) = db_lookup().getSqlVectors(TimeSpan(
>>>> _start_ts, _end_ts), 'appTemp')
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/manager.py", line 512, in getSqlVectors
>>>> Dec 10 09:55:50 ftp weewx[13683]:   aggregate_type, 
>>>> aggregate_interval)
>>>> Dec 10 09:55:50 ftp weewx[13683]: File 
>>>> "/home/weewx/bin/weewx/manager.py", line 775, in _getSqlVectors
>>>> Dec 10 09:55:50 ftp weewx[13683]:   for _rec in _cursor
>>>> .execute(sql_str, (startstamp, stopstamp)):
>>>> Dec 10 09:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

This is likely a naive question on my part. But did you extend the schema 
on the archive table for your database to include appTemp? Assuming so, did 
you rebuild the daily value tables? Are the values in the archive table and 
the archive_day_appTemp table being populated? When I look at your website, 
your daily.json data shows appTemp with a value of "N/A".phil


On Monday, December 10, 2018 at 10:09:52 AM UTC-5, G Hammer wrote:
>
> Here's the rest of the pertinent log entries that Groups cut off:
> Dec 10 09:55:50 ftp weewx[13683]:   raise weedb.
> NoColumnError(e)
> Dec 10 09:55:50 ftp weewx[13683]:   NoColumnError: no such 
> column: appTemp
> Dec 10 09:55:50 ftp weewx[13683]:   Generator terminated
> Dec 10 09:55:50 ftp weewx[13683]: copygenerator: copied 0 files to /home/
> weewx/public_html/weather
>
>
>
> On Monday, December 10, 2018 at 10:07:01 AM UTC-5, G Hammer wrote:
>>
>> Pat,
>>
>> When I have show_apptemp=1 I do see the Feels like temp as I expect.
>> If I set highcharts_show_apptemp = 1 I do not get an apptemp plot, the 
>> report generator errors out:
>> Dec 10 09:55:50 ftp weewx[13683]: reportengine: Caught unrecoverable 
>> exception in generator weewx.cheetahgenerator.CheetahGenerator
>> Dec 10 09:55:50 ftp weewx[13683]:   no such column: appTemp
>> Dec 10 09:55:50 ftp weewx[13683]:   Traceback (most recent 
>> call last):
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 239, in run
>> Dec 10 09:55:50 ftp weewx[13683]:   obj.start()
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/reportengine.py", line 273, in start
>> Dec 10 09:55:50 ftp weewx[13683]:   self.run()
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 158, in run
>> Dec 10 09:55:50 ftp weewx[13683]:   ngen = self.generate(
>> gen_dict[section_name], self.gen_ts)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.generate
>> (section[subsection], gen_ts)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 232, in generate
>> Dec 10 09:55:50 ftp weewx[13683]:   ngen += self.generate
>> (section[subsection], gen_ts)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 320, in generate
>> Dec 10 09:55:50 ftp weewx[13683]:   default_binding)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/cheetahgenerator.py", line 372, in _getSearchList
>> Dec 10 09:55:50 ftp weewx[13683]:   searchList += obj.
>> get_extension_list(timespan, db_lookup)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/user/belchertown_highchartsSearchX.py", line 85, in 
>> get_extension_list
>> Dec 10 09:55:50 ftp weewx[13683]:   (time_start_vt, 
>> time_stop_vt, appTemp_vt) = db_lookup().getSqlVectors(TimeSpan(_start_ts, 
>> _end_ts), 'appTemp')
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/manager.py", line 512, in getSqlVectors
>> Dec 10 09:55:50 ftp weewx[13683]:   aggregate_type, 
>> aggregate_interval)
>> Dec 10 09:55:50 ftp weewx[13683]: File 
>> "/home/weewx/bin/weewx/manager.py", line 775, in _getSqlVectors
>> Dec 10 09:55:50 ftp weewx[13683]:   for _rec in _cursor.
>> execute(sql_str, (startstamp, stopstamp)):
>> Dec 10 09:55https://groups.google.com/d/optout.

[weewx-user] Re: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

First, let me apologize for hijacking this Belchertown thread to get 
educated on Apparent Temperature.

Second, thanks Gary, your explanation clarifies it for me. It seems I was 
fixed on a simplistic definition of Apparent Temperature sometimes used in 
the US which yields the same value as either Wind Chill, Temperature, or 
Heat Index depending upon the value of "actual temperature". In contrast, 
the weewx calculation relies on the more sophisticated model developed by 
Steadman.

I actually like that the weewx calculated value is different than what I 
thought it should be. The simplistic definition doesn't add any new 
information as you could just look at Wind Chill, Heat Index and 
Temperature to get the same information the simple definition provides. In 
addition, I don't actually know what formula Vantage uses to calculate Wind 
Chill and Heat Index (I'll look it up), which my station hardware 
calculates and provides. 

The Steadman model gives a more nuanced value probably closer to what is 
intended - that is, what the human body perceives the temperature to be.

I'll move any further questions I have on this to a separate topic.
phil

On Sunday, December 9, 2018 at 6:05:08 PM UTC-5, gjr80 wrote:
>
> As you point out weeWX windchill and heatindex values track outTemp below 
> certain minimums and above certain maximums respectively. The weeWX 
> calculated appTemp uses the formulas mentioned in the post you linked and 
> is quite different to a composite heatindex and windchill (by composite I 
> mean windchill below 50F and heatindex above 81F). The key difference 
> (other than the formula) is that appTemp is valid across all temperatures. 
> appTemp is certainly affected by wind speed (just look at the formula), I 
> often notice appTemp moving in time (and quite markedly) with wind speed 
> changes on my realtime gauges.
>
> I like to think of 'feels like' as being a term that means different 
> things to different people and without an agreed understanding can be a 
> source of confusion. It really is just a general term that tries to better 
> approximate the effect of current weather conditions on the body, it could 
> be based on a measure of heatindex, windchill, humidex, wet bulb globe 
> temperature or apparent temperature. For me in Australia I think of 
> apparent temperature, I expect in Canada humidex may be a more accepted 
> measurement.
>
> The use of the term 'apparent temperature' can also be confusing at times; 
> does it refer to the accepted formula for Apparent Temperature (as you 
> linked or as used by weeWX) or is it the more literal meaining. For this 
> reason I prefer to refer to something like the 'weeWX appTemp field' or 
> 'Apparent Temperature' to make it clear I am referring to the calculated 
> value.
>
> 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: Belchertown Skin 0.8.1 released

[Philip Kutzenco]

Dj,

Check out this link for details: 
https://groups.google.com/d/msg/weewx-user/bNz3ymPNHHc/caYi1nqlAgAJ

I must say that I have been a bit confused about the appTemp value weewx 
calculates. My understanding is that the Apparent Temperature is equal to 
the Wind Chill number when the temp is 50 degrees F or below. It is equal 
to the Heat Index with the temp is 81 degrees F or above. My Vantage Vue 
transmits Wind Chill and Heat Index values. But the weewx calculated 
appTemp value doesn't match my understanding of what it should equal (or at 
least closely equal).

I wonder if it has to do with Loop Values for wind speed (which drives Wind 
Chill) and humidity (which drives Heat Index) vs. archive values for for 
those measures (which are aggregates). I don't know. Maybe someone else  
knows?
phil

On Sunday, December 9, 2018 at 5:04:01 PM UTC-5, Dj Merrill wrote:
>
> That worked beautifully, thank you Philip!
>
> I don't believe the data it is showing is correct, though.  Outside temp 
> is 23.5 F currently, with no wind.  It is showing a "feels like" 
> temperature of 18.1 F.  Other sources  are showing the feels like temp in 
> my area being the same as the outside temp.
>
> How is it calculating the data?
>
> Thanks,
>
> -Dj
>
>

-- 
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 0.8.1 released

[Philip Kutzenco]

One more thing:

extensions.py could be in /home/weewx/bin/user if you installed weewx with 
setup.py rather than with apt-get.
phil


On Sunday, December 9, 2018 at 4:51:15 PM UTC-5, Philip Kutzenco wrote:
>
> Dj,
>
> (I deleted the first version of this post as I left out a trailing "]" in 
> step 1).
>
> This is from instructions Pat gave me in the past to extend the schema:
>
> 1) Extend the database
>
> nano /usr/share/weewx/user/extensions.py
>
> then add the following:
>
>
> *import schemas.wviewschema_apptemp = schemas.wview.schema + 
> [('appTemp',   'REAL')]*
>
>
>
> 2) Stop weewx and edit weewx.conf to tell it to use this new schema 
> extension by adding the *schema = line* below to the [DataBindings] 
> stanza:
>
>
>
>
> *[DataBindings][[wx_binding]]...schema = 
> user.extensions.schema_apptemp*
>
>
>
> 3) Create a new copy of the database with the extended schema
>
> *wee_database weewx.conf --reconfigure*
> and then rename the databases
>
>
>
> 4) Rebuild the database with new daily values
>
> *Sudo wee_database --rebuild-daily*
>
>
>
> 5) restart weewx
>
> phil
>
>

-- 
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 0.8.1 released

[Philip Kutzenco]

Dj,

(I deleted the first version of this post as I left out a trailing "]" in 
step 1).

This is from instructions Pat gave me in the past to extend the schema:

1) Extend the database

nano /usr/share/weewx/user/extensions.py

then add the following:


*import schemas.wviewschema_apptemp = schemas.wview.schema + [('appTemp',   
'REAL')]*



2) Stop weewx and edit weewx.conf to tell it to use this new schema 
extension by adding the *schema = line* below to the [DataBindings] stanza:




*[DataBindings][[wx_binding]]...schema = 
user.extensions.schema_apptemp*



3) Create a new copy of the database with the extended schema

*wee_database weewx.conf --reconfigure*
and then rename the databases



4) Rebuild the database with new daily values

*Sudo wee_database --rebuild-daily*



5) restart weewx

phil

On Sunday, December 9, 2018 at 4:27:23 PM UTC-5, Dj Merrill wrote:
>
> Please forgive my ignorance.  It is not clear after reading the 
> instructions on extending the database precisely what I should do in this 
> case.  Obviously we don't have an "user/electricity.py" file, but we do 
> have a "user/belchertown.py" file.
>
> Should I modify the "belchertown.py" file with something like:
>
> import schemas.wview
> schema_with_apptemp = schemas.wview.schema + [('appTemp', 'REAL')]
>
>
> Then modify weewx.conf to have:
>
> [DataBindings]
> [[wx_binding]]
> database = archive_sqlite
> table_name = archive
> manager = weewx.wxmanager.WXDaySummaryManager
> schema = user.belchertown.schema_with_apptemp
>
>
> I am using SQLlite so I believe I can skip step 3.
>
> Then, "wee_database weewx.conf --reconfigure" and rename the databases?
>
> Thanks,
>
> -Dj
>
>

-- 
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 0.8.1 released

[Philip Kutzenco]

Dj,

This is from instructions Pat gave me in the past to extend the schema:

1) Extend the database

nano /usr/share/weewx/user/extensions.py

then add the following:


*import schemas.wviewschema_apptemp = schemas.wview.schema + [('appTemp',   
'REAL')*



2) Stop weewx and edit weewx.conf to tell it to use this new schema 
extension by adding the *schema = line* below to the [DataBindings] stanza:




*[DataBindings][[wx_binding]]...schema = 
user.extensions.schema_apptemp*



3) Create a new copy of the database with the extended schema

*wee_database weewx.conf --reconfigure*
and then rename the databases



4) Rebuild the database with new daily values

*Sudo wee_database --rebuild-daily*



5) restart weewx

phil

-- 
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 0.8.1 released

[Philip Kutzenco]

Dj,

In addition to extending the schema for your database to include appTemp, 
as Pat notes (this is a requirement), I recommend you add the line 
mentioned by Rich

show apptemp = 1

in the [[[Extras]]] stanza of the [[Belchertown]] stanza in weewx.conf 
(instead of adding it to skin.conf). This will ensure that the change 
"sticks" after installs of new Belchertown skin versions.
phil

On Sunday, December 9, 2018 at 3:49:43 PM UTC-5, Pat wrote:
>
> Thanks Dj! As mentioned in the general options guide 
> , your 
> database will need to be extended for the appTemp 
>  observations. 
>
> On Sunday, December 9, 2018 at 3:44:00 PM UTC-5, rich T wrote:
>>
>> Dj
>>
>> In the skin.conf file located in the Belchertown folder, set 
>> "show_apptemp = 1". Restart weewx.
>>
>> Rich 
>>
>> On Sunday, December 9, 2018 at 3:27:35 PM UTC-5, Dj Merrill wrote:
>>
>>> Pat, what a beautiful piece of work!  Thank you for sharing this with us!
>>>
>>> I notice on your site there is a "Feels like" temperature shown under 
>>> the outside temperature and above the high/low temps on the top of the main 
>>> page.  I don't see that on my site, and am wondering how to enable that?
>>>
>>> Thanks!
>>>
>>> -Dj
>>>
>>>

-- 
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 0.8.1 released

[Philip Kutzenco]

Also upgraded and working great (wx.kutzenco.com).
phil

On Friday, December 7, 2018 at 9:46:05 PM UTC-5, Colin Larsen wrote:
>
> Upgraded 41south.net.nz 
> 
>  
> and working great. In my footer I've added the version and updated date 
> just for reference.
>
> Colin
>
> On Sat, 8 Dec 2018, 12:25 Hector Valenzuela   wrote:
>
>> I installed version 0.1.  I'll have to try another version
>>
>> El viernes, 7 de diciembre de 2018, 15:12:23 (UTC-7), Pat escribió:
>>>
>>> The last thread was getting a bit long. So I've started a new one. 
>>>
>>> Belchertown Skin 0.8.1 has been released which fixes a couple of bugs. 
>>> See the release notes, and install instructions here:
>>>
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>>
>>> -- 
>> 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!

[Philip Kutzenco]

In your weew.conf file (which you attached earlier), HTML_ROOT shoud be the 
same under the [[Belchertown]] stanza and the [Highcharts_Belchertown]] 
stanza. Yours are different. I think they should also be pointing to the 
weewx/belchertown folder (though I'm not sure).

I don't know if that would fix it, but give it a try.
phil

On Thursday, December 6, 2018 at 7:08:26 PM UTC-5, Teva MERVIN wrote:
>
> I use the apt-get.
> my web structure /var/www/html/weewx/belchertown
> All the files and directories are created (about / index.html ), but 
> not the index.html from the beginning
>
> I have this as an error message (message1.txt)
> Le vendredi 7 décembre 2018 10:57:01 UTC+11, Philip Kutzenco a écrit :
>
> I think that normally the Apache server should be serving up the files 
> located in public_html/belchertown. On my weewx system, that is 
> /home/weewx/public_html/belchertown. Did you install weewx with setup.py or 
> apt-get. That will determine where that directory actually is (I used 
> setup.py).
>
> What are the files in that directory? There should be an index.html file 
> (among all of the others) there.
> phil
>
> On Thursday, December 6, 2018 at 5:53:38 PM UTC-5, Teva MERVIN wrote:
>
> The web page is raw, without html, as on the file belchertown01.png
> I did not touch the skin.conf.
> I put it in an attached file.
>
> Le vendredi 7 décembre 2018 09:37:42 UTC+11, Colin Larsen a écrit :
>
> In what way does it not work properly? Do you have no web pages at all or 
> partial page? Have you set
>
> ...

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

[Philip Kutzenco]

I think that normally the Apache server should be serving up the files 
located in public_html/belchertown. On my weewx system, that is 
/home/weewx/public_html/belchertown. Did you install weewx with setup.py or 
apt-get. That will determine where that directory actually is (I used 
setup.py).

What are the files in that directory? There should be an index.html file 
(among all of the others) there.
phil

On Thursday, December 6, 2018 at 5:53:38 PM UTC-5, Teva MERVIN wrote:
>
> The web page is raw, without html, as on the file belchertown01.png
> I did not touch the skin.conf.
> I put it in an attached file.
>
> Le vendredi 7 décembre 2018 09:37:42 UTC+11, Colin Larsen a écrit :
>>
>> In what way does it not work properly? Do you have no web pages at all or 
>> partial page? Have you set up skin.conf Belchertown? Can you post that 
>> please.
>>
>> Colin
>>
>>
>> On Fri, 7 Dec 2018, 10:53 Teva MERVIN >
>>> Hello, and sorry for my approximate english ;)
>>>
>>> I'm trying to install your skin, I have:
>>> - 1 single debian server 4.18.10-2
>>> - Apache2 2.4.37-1
>>> - weewx v3.8.2
>>>
>>> and I have problems installing weewx-belchertown-0.8.tar.gz
>>> I think I have correctly followed your procedure, but the belchertown 
>>> web page does not display correctly
>>> See attach : belchertown01
>>>
>>> I am attaching my file weewx.conf
>>>
>>> What is the problem ?
>>> Thank you for your job's.
>>>
>>> -- 
>>> 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.

[weewx-user] Re: New to WeeWX not sure where to go next

[Philip Kutzenco]

There are lots of terrific skins. The Standard one is a great one to start 
with.Then you can look around and see if there is another you'd prefer. 
Many like SteelSeries Gauges. I am personally fond of the Belchertown skin, 
developed by Pat O'Brien. It is available here: 
https://github.com/poblabs/weewx-belchertown/releases. My website using it 
is https://wx.kutzenco.com. 

I'm sure you'll enjoy weewx!
phil

On Tuesday, December 4, 2018 at 11:24:26 AM UTC-5, Robbie Lister wrote:
>
> Thank's Gary I will give that a go. By the sounds of things the built in 
> default template will be a god starting point.
>
> On Tuesday, 4 December 2018 15:40:39 UTC, Gary Hopkins wrote:
>>
>> sudo apt-get install nginx
>>
>> sudo /etc/init.d/nginx start
>>
>> NGINX defaults its web page location to /var/www/html on Raspbian so if you 
>> want to change that you need to edit
>>
>> /etc/nginx/sites-available/default
>>
>> and edit the line 
>>
>> root /var/www/html/;
>>
>> to
>>
>> root /var/www/html/weewx/;
>>
>>
>> After that you should be able to point a browser at the IP address of the 
>> Pi (hostname -I on the Pi if you want to know its IP address)
>>
>>
>> As for remote website, auto FTP upload is built into weewx. Edit the FTP 
>> section in weewx.conf it's faily self explanatory. There is a basic default 
>> template included - you don't have to do anything it just works.
>>
>> Cheers
>>
>> G
>>
>>

-- 
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: New to WeeWX not sure where to go next

[Philip Kutzenco]

There are lots of terrific skins. The Standard one is a great one to start 
with.Then you can look around and see if there is another you'd prefer. 
Many like SteelSeries Gauges. I am personally fond of the Belchertown skin, 
developed by Pat O'Brien. It is available here: 
https://github.com/poblabs/weewx-belchertown/releases.  My website using it 
is https://wx.kutzenco.com.

I'm sure you'll enjoy weewx!
phil

On Tuesday, December 4, 2018 at 11:24:26 AM UTC-5, Robbie Lister wrote:
>
> Thank's Gary I will give that a go. By the sounds of things the built in 
> default template will be a god starting point.
>
> On Tuesday, 4 December 2018 15:40:39 UTC, Gary Hopkins wrote:
>>
>> sudo apt-get install nginx
>>
>> sudo /etc/init.d/nginx start
>>
>> NGINX defaults its web page location to /var/www/html on Raspbian so if you 
>> want to change that you need to edit
>>
>> /etc/nginx/sites-available/default
>>
>> and edit the line 
>>
>> root /var/www/html/;
>>
>> to
>>
>> root /var/www/html/weewx/;
>>
>>
>> After that you should be able to point a browser at the IP address of the 
>> Pi (hostname -I on the Pi if you want to know its IP address)
>>
>>
>> As for remote website, auto FTP upload is built into weewx. Edit the FTP 
>> section in weewx.conf it's faily self explanatory. There is a basic default 
>> template included - you don't have to do anything it just works.
>>
>> Cheers
>>
>> G
>>
>>

-- 
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: Using a ProData WiFi Logger?

[Philip Kutzenco]

I don't have one of these. But it should work fine with the weeWX Vantage 
driver. It appears to emulate the Davis WeatherLinkIP interface (without 
having a Davis registered "DID", preventing free uploads to Davis own 
weatherlink.com website. FWIW, the Davis DID is the MAC address of the 
device.

In weewx.conf (in the [Vantage] stanza) you would set the "Connection type" 
to ethernet. You also need to set the "host" in that stanza to the IP 
address of the wifi-logger. One thing you need though is to set the 
IPaddress in the wifi-logger device to be the same every time it is 
rebooted. You can do that by specifying a static IP address for the device 
in your router. The device itself, may have a way to set a static IP 
address rather than pick up a new one via DHCP, I'm not sure. 
phil

On Saturday, November 17, 2018 at 11:00:26 PM UTC-5, cfor...@gmail.com 
wrote:
>
> Hello weewx-ers!
>
> Perhaps this is a naive question, but searching isn't turning up any 
> answers. Can I use weewx with this logger:
>
> https://www.weatherstations.co.uk/wifi-logger.htm
>
> It claims that it offers TCP/IP access to LOOP packets, so I presume weewx 
> would work with it, but has anyone tried it yet?
>
>
>
> Charlie
> -- 
> Earth, USA, GA, Atlanta
>

-- 
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] Vantage Vue wind cup size setting with wee_device

[Philip Kutzenco]

Thomas,

Thanks for the reply. I won't worry about it. The reason I asked is that 
the help file for Davis' Weatherlink software shows three options. See the 
attached screen shot I took for setting that in the console with 
Weatherlink. Evidently, you can set a VantagePro to use small cups or 
Vue/Other cups. I'll just leave the value as it is set in the console 
without setting it explicitly.
phil

On Saturday, October 20, 2018 at 8:22:26 PM UTC-4, Thomas Keffer wrote:
>
> A Vantage (whether a Vue or a VantagePro) ships with a value in the EEPROM 
> firmware that matches its cup size. Unless you change the cups, there is no 
> reason to mess with this value. The wee_device utility option is there if, 
> for some reason, you have to change the cups.
>
> To answer your question, the Davis documentation lists only two sizes: 
> small and large. If there's a third "Vue" sized, I haven't heard of it. 
> You'd have to ask Davis.
>
> -tk
>
> On Sat, Oct 20, 2018 at 7:35 AM Philip Kutzenco  > wrote:
>
>> Now that I have my external website operational (https://wx.kutzenco.com) 
>> with a Mosquitto MQTT broker and Belchertown skin, I'm spending a bit more 
>> time reviewing the weeWX documentation to get a deeper understanding of my 
>> system. I'm hoping to do some customization.
>>
>> I have a Davis Vantage Vue weather station and weeWX running on a 
>> Raspberry Pi Zero W. I see that the Davis Weatherlink software gives the 
>> options for wind cup size as Small, Large or Vue/Other. That Davis 
>> documentation says that Vantage Pro systems generally ship with large cups, 
>> and that (obviously) Vantage Vue systems ship with Vue cups.
>>
>> The wee_device --help command mentions only Small and Large options for 
>> wind cup size. Is there an option for Vue/other cups? I don't know what is 
>> adjusted in the readings/calculations by specifying different cup sizes. I 
>> didn't see that called out in the weeWX documention. I suspect the 
>> difference is minimal, but, just to ensure that everything can be set 
>> properly with weeWX does that option need to be added to wee_device for 
>> Vantage systems, if it isn't there?
>>
>> phil
>>
>> -- 
>> 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.

[weewx-user] Vantage Vue wind cup size setting with wee_device

[Philip Kutzenco]

Now that I have my external website operational (https://wx.kutzenco.com) 
with a Mosquitto MQTT broker and Belchertown skin, I'm spending a bit more 
time reviewing the weeWX documentation to get a deeper understanding of my 
system. I'm hoping to do some customization.

I have a Davis Vantage Vue weather station and weeWX running on a Raspberry 
Pi Zero W. I see that the Davis Weatherlink software gives the options for 
wind cup size as Small, Large or Vue/Other. That Davis documentation says 
that Vantage Pro systems generally ship with large cups, and that 
(obviously) Vantage Vue systems ship with Vue cups.

The wee_device --help command mentions only Small and Large options for 
wind cup size. Is there an option for Vue/other cups? I don't know what is 
adjusted in the readings/calculations by specifying different cup sizes. I 
didn't see that called out in the weeWX documention. I suspect the 
difference is minimal, but, just to ensure that everything can be set 
properly with weeWX does that option need to be added to wee_device for 
Vantage systems, if it isn't there?

phil

-- 
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 [[[Extras]]] not working?

[Philip Kutzenco]

I put my [[[Extras]]] stanza under [[Belchertown]] in weewx.conf and it's 
working in my implementation.
phil

On Tuesday, October 16, 2018 at 11:12:42 AM UTC-4, Gabe wrote:
>
> I had to put extras at the same level as Units. The github readme is 
> confusing (or maybe I'm just too dumb)
>
> skin = Belchertown
> [[[Units]]]
> Groups
> group_altitude = meter
> group_speed2 = meter_per_second2
> group_pressure = mbar
> group_rain = mm
> group_rainrate = mm_per_hour
> group_temperature = degree_C
> group_degree_day = degree_C_day
> group_speed = meter_per_second
> [[[Extras]]]
> footer_copyright_text = "Main Copyright"
> [[neowx]]
> HTML_ROOT = /var/www/html/weewx/neowx
> skin = neowx
> [[Highcharts_Belchertown]]
> HTML_ROOT = /var/www/html/weewx/belchertown
> skin = Highcharts_Belchertown
> [[Belchertown]]
> HTML_ROOT = /var/www/html/weewx/belchertown
> skin = Belchertown
>
>
> On Tuesday, October 16, 2018 at 10:59:25 AM UTC-4, Gabe wrote:
>>
>> I noticed that if I modify weewx.conf with [[[Extras]]], nothing happens 
>> in the skin. If I modify skin.conf, then it works (footer_copyright_text 
>> for example). Is this normal?
>>
>> skin = Belchertown
>> [[[Units]]]
>> Groups
>> group_altitude = meter
>> group_speed2 = meter_per_second2
>> group_pressure = mbar
>> group_rain = mm
>> group_rainrate = mm_per_hour
>> group_temperature = degree_C
>> group_degree_day = degree_C_day
>> group_speed = meter_per_second
>> [[neowx]]
>> HTML_ROOT = /var/www/html/weewx/neowx
>> skin = neowx
>> [[Highcharts_Belchertown]]
>> HTML_ROOT = /var/www/html/weewx/belchertown
>> skin = Highcharts_Belchertown
>> [[Belchertown]]
>> HTML_ROOT = /var/www/html/weewx/belchertown
>> skin = Belchertown
>> [[[Extras]]]
>> footer_copyright_text = "Test Copyright"
>>
>>

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

[Philip Kutzenco]

I think that version 0.7 is the most recent complete release. Pat has 
issued commits for updates to some files, mostly to address those using 
Metric units. So, individual files can be downloaded to implement those. I 
don't think he has yet packaged them all into a later version.
phil

On Tuesday, October 16, 2018 at 10:40:12 AM UTC-4, Paul Lacatus wrote:
>
> Is there a procedure to update the running belchertown skin 0.7 to the 
> last version on the github ? 
>
>

-- 
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 and MQTT With Username Not Working

[Philip Kutzenco]

I think I found it.

In weewx.conf, you have:

[[tls]]
tls_version = tlsv1
ca_certs = /etc/ssl/certs/ca-certificates.crt

It should be:

[[[tls]]]
tls_version = tlsv1
ca_certs = /etc/ssl/certs/ca-certificates.crt

Note 3 brackets around tls. Try that.

BTW. I do have the extra lines you note in 
/etc/mosquitto/conf.d/myconfig.conf. I was in a huury when posting last 
night.

phil

On Friday, October 12, 2018 at 6:42:41 AM UTC-4, David Hindley wrote:
>
> Not sure it will help solve this or not, but the Mosquitto log shows the 
> following:
>
>  New connection from 86.27.145.159 on port 8883.
> 1539340809: OpenSSL Error: error:1408F10B:SSL 
> routines:ssl3_get_record:wrong version number
> 1539340809: Socket error on client , disconnecting.
> 1539340811: Client connection from 86.27.145.159 failed: 
> error:1408F10B:SSL routines:ssl3_get_record:wrong version number.
> 1539340814: New connection from 86.27.145.159 on port 8883.
>
> So, it does seem to be SSL related, but I am not sure how to solve this.  
> Any ideas please anyone?
>
> David.
>
> On Fri, 12 Oct 2018 at 10:01, David Hindley  > wrote:
>
>> Phil/Pat
>>
>> Many Thanks for you reply. 
>>
>> I did set up a password for Mosquitto and also the acl file, as per your 
>> email below.
>>
>> However, my myconfig.conf file is different to the one you listed below, 
>> as I am using Let's Encrypt SSL, so followed the format towards the end of 
>> Pat's post ( MQTT "tutorial" 
>>  ), as 
>> follows:
>>
>> persistence false
>>
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>
>> acl_file /etc/mosquitto/acl
>>
>> #Insecure mqtt to localhost only and secure mqtt with ssl
>> listener 1883 localhost
>> listener 8883
>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>> protocol websockets
>>
>> Did you not use SSL on your set up for  https://wx.kutzenco.com? Maybe I 
>> have done something wrong with trying to set this part up.  It is really 
>> frustrating, as the syslog reports that MQTT is sending records, as it 
>> contains several lines like:
>>
>> Oct 12 09:58:27 raspberrypi weewx[1147]: restx: MQTT: Published record 
>> 2018-10-12 09:58:28 BST (1539334708)
>>
>> Pat - if you see this, do you have any ideas what I might be doing wrong 
>> - my hunch is that it is something to do with the settings for SSL for MQTT 
>> in weewx.conf, which are shown below.  Do I need to create the 
>> ca-certificates.crt file?  Or I guess it could be some issue with my web 
>> host for www.ashteadweather.com which is 1&1 (with SSL).
>>
>> Thanks
>>
>> David.
>>
>> *weewx.conf file*
>>
>>   [[MQTT]]
>> server_url = mqtt://x:...@mqttdh.uk:8883/
>> topic = weather
>> unit_system = METRIC
>> aggregation = aggregate
>> binding = archive,loop
>> # log_success = False
>> # log_failure = True
>> [[tls]]
>>tls_version = tlsv1
>>ca_certs = /etc/ssl/certs/ca-certificates.crt
>>
>> The Belchertown skin.conf MQTT content is as follows:
>>
>>  # MQTT Defaults
>> mqtt_enabled = 1
>> mqtt_host = mqttdh.uk
>> mqtt_port = 9001
>> mqtt_ssl = 1
>> mqtt_topic = "weather/loop"
>> disconnect_live_website_visitor = 0
>>
>>

-- 
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 and MQTT With Username Not Working

[Philip Kutzenco]

I may have found it.

in weewx.conf, you have a stanza:

[[tls]]
tls_version = tlsv1
ca_certs = /etc/ssl/certs/ca-certificates.crt

It should be:

[[[tls]]]
tls_version = tlsv1
ca_certs = /etc/ssl/certs/ca-certificates.crt

with 3 brackets.

Try that.

BTW: I do have the added lines in myconfig.conf that you do. I was in 
hurray when I posted last night.

phil


On Friday, October 12, 2018 at 6:42:41 AM UTC-4, David Hindley wrote:
>
> Not sure it will help solve this or not, but the Mosquitto log shows the 
> following:
>
>  New connection from 86.27.145.159 on port 8883.
> 1539340809: OpenSSL Error: error:1408F10B:SSL 
> routines:ssl3_get_record:wrong version number
> 1539340809: Socket error on client , disconnecting.
> 1539340811: Client connection from 86.27.145.159 failed: 
> error:1408F10B:SSL routines:ssl3_get_record:wrong version number.
> 1539340814: New connection from 86.27.145.159 on port 8883.
>
> So, it does seem to be SSL related, but I am not sure how to solve this.  
> Any ideas please anyone?
>
> David.
>
> On Fri, 12 Oct 2018 at 10:01, David Hindley  > wrote:
>
>> Phil/Pat
>>
>> Many Thanks for you reply. 
>>
>> I did set up a password for Mosquitto and also the acl file, as per your 
>> email below.
>>
>> However, my myconfig.conf file is different to the one you listed below, 
>> as I am using Let's Encrypt SSL, so followed the format towards the end of 
>> Pat's post ( MQTT "tutorial" 
>>  ), as 
>> follows:
>>
>> persistence false
>>
>> allow_anonymous true
>> password_file /etc/mosquitto/passwd
>>
>> acl_file /etc/mosquitto/acl
>>
>> #Insecure mqtt to localhost only and secure mqtt with ssl
>> listener 1883 localhost
>> listener 8883
>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>> protocol mqtt
>>
>> # websockets
>> listener 9001
>> certfile /etc/letsencrypt/live/mqttdh.uk/cert.pem
>> cafile /etc/letsencrypt/live/mqttdh.uk/chain.pem
>> keyfile /etc/letsencrypt/live/mqttdh.uk/privkey.pem
>> protocol websockets
>>
>> Did you not use SSL on your set up for  https://wx.kutzenco.com? Maybe I 
>> have done something wrong with trying to set this part up.  It is really 
>> frustrating, as the syslog reports that MQTT is sending records, as it 
>> contains several lines like:
>>
>> Oct 12 09:58:27 raspberrypi weewx[1147]: restx: MQTT: Published record 
>> 2018-10-12 09:58:28 BST (1539334708)
>>
>> Pat - if you see this, do you have any ideas what I might be doing wrong 
>> - my hunch is that it is something to do with the settings for SSL for MQTT 
>> in weewx.conf, which are shown below.  Do I need to create the 
>> ca-certificates.crt file?  Or I guess it could be some issue with my web 
>> host for www.ashteadweather.com which is 1&1 (with SSL).
>>
>> Thanks
>>
>> David.
>>
>> *weewx.conf file*
>>
>>   [[MQTT]]
>> server_url = mqtt://x:...@mqttdh.uk:8883/
>> topic = weather
>> unit_system = METRIC
>> aggregation = aggregate
>> binding = archive,loop
>> # log_success = False
>> # log_failure = True
>> [[tls]]
>>tls_version = tlsv1
>>ca_certs = /etc/ssl/certs/ca-certificates.crt
>>
>> The Belchertown skin.conf MQTT content is as follows:
>>
>>  # MQTT Defaults
>> mqtt_enabled = 1
>> mqtt_host = mqttdh.uk
>> mqtt_port = 9001
>> mqtt_ssl = 1
>> mqtt_topic = "weather/loop"
>> disconnect_live_website_visitor = 0
>>
>>
>>>

-- 
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 and MQTT With Username Not Working

[Philip Kutzenco]

David,

You don't need to specify a username/password to receive data if you have 
sett up your broker as Pat detailed in his post 
<https://obrienlabs.net/how-to-setup-your-own-mqtt-broker/>. The weewx.conf 
stanzas in the file I attached in my earlier post are working fine at 
https://wx.kutzenco.com. One minor change is that I changed the 
subscription to "weather/loop" instead of "weather/#". It works with #, but 
I think best practice is to only subscribe to loop.

Here are some things to look at:

1. Did you set up a password for Mosquitto? It is done as follows:
*sudo mosquitto_passwd -c /etc/mosquitto/passwd *
Note that the username is just for Mosquitto. It doesn't need to be a linux 
account name.

1.  Did you set up an acl file (*/etc/mosquitto/acl)*? It should contain:



*# Allow anonymous access to the systopic read $SYS/# # Allow anonymous to 
read weathertopic read weather/#*


*# weewx readwrite to the loopuser topic 
weather/#*

2. Does your Mosquitto myconfig.conf (*/etc/mosquitto/conf.d/myconfig.conf) 
*file contain the following? It should have:





*persistence falseallow_anonymous truepassword_file 
/etc/mosquitto/passwdacl_file /etc/mosquitto/acllistener 1883protocol mqtt*



*# websocketslistener 9001protocol websocket *

I am far from an expert on this, but if you post copies of those files. I 
will look at them in addition to the weewx.conf stanzas you already 
published, ans see if I can spot a reason for it not working for you. (I 
probably won't get a chance to look until tomorrow).

phil

On Thursday, October 11, 2018 at 5:13:23 PM UTC-4, Colin Larsen wrote:
>
> You'll also need to supply the username and password to "receive" the MQTT 
> data (in skin.conf or Belchertown) but that is not yet supported as far as 
> I know.
>
> Colin
>
>
> On Fri, 12 Oct 2018, 07:59 , > wrote:
>
>> Hi 
>>
>>  
>>
>> I am trying to set up MQTT on the Belchertown skin, and just can't get it 
>> to work, but think I am very nearly there.  Like Philip Kutzenco, I am 
>> using Digital Ocean to host my MQTT broker, with my own domain name, and 
>> have followed Pat's guide to set up the MQTT broker with SSL using Let's 
>> Encrypt.   MQTT all seems to be working, as per Pat's guide.  My weather 
>> website (ashteadweather.com hosted at 1&1 with SSL certificate) says 
>> "Connected.  Waiting for data", which sounds promising, but it just stays 
>> at that message.  I copied the weewx.conf settings format for MQTT and the 
>> skin.conf format for Belchertown skin, as suggested by Philip Kutzenco, as 
>> per below:
>>
>>  
>>
>>  
>>
>>  
>>
>> weewx.conf:
>>
>>  
>>
>>  
>>
>> [[MQTT]]
>>
>> server_url = mqtt://:zz...@mqttdh.uk:8883/
>>
>> topic = weather
>>
>> unit_system = METRIC
>>
>> aggregation = aggregate
>>
>> binding = archive,loop
>>
>> log_success = False
>>
>> log_failure = True
>>
>> [[tls]]
>>
>>tls_version = tlsv1
>>
>>ca_certs = /etc/ssl/certs/ca-certificates.crt
>>
>>  
>>
>>  
>>
>>  
>>
>> Belchertown:
>>
>>  # MQTT Defaults
>>
>> mqtt_enabled = 1
>>
>> mqtt_host = mqttdh.uk
>>
>> mqtt_port = 9001
>>
>> mqtt_ssl = 1
>>
>> mqtt_topic = "weather/#"
>>
>> disconnect_live_website_visitor = 0
>>
>>  
>> Syslog does give any clues as to what is going wrong - no errors 
>> reported, for example.  Any suggestions from those that have got a similar 
>> set up.  I must be doing something basic wrong.  For example, do I need to 
>> put any certificates to follow the line   "ca_certs = 
>> /etc/ssl/certs/ca-certificates.crt" in weewx.conf?  Or is it something to 
>> with needing user names and passwords on publishing/subscribing perhaps?
>>
>> Many Thanks 
>>
>> David.
>>
>> On Tuesday, 9 October 2018 12:53:40 UTC+1, G Hammer wrote:
>>>
>>> I rarely cut & paste when configuring. 
>>>
>>> I too have found that restarting any service doesn’t always produce good 
>>> results.  I just stop then start things. 
>>>
>>> I’ll post my config files later as an example for others. 
>>>
>>> I’m just happy to have it running in house at long last. 
>>>
>>> The public test.mosquitto.org was not real reliable.  
>>>
>>> On Tue, Oct 9, 2018 at 7:45 AM Philip Kutzenco  
>>

Re: [weewx-user] Re: Belchertown Skin and MQTT With Username Not Working

[Philip Kutzenco]

Mosquitto is fussy, especially about its config files. In Pat's guide, he 
mentions that extra spaces at the end of lines messes things up. He says 
Mosquitto sometimes needs to be restarted completely. I found that 
Mosquitto also requires a newline at the end of config files. If you start 
(or restart) Mosquitto and it sees something it doesn't like in a config 
file, it immediately exits. Starting Mosquitto again, even if you first fix 
any errors in the config files, causes it to fail immediately again. 

For me, issuing a stop command first (sudo /etc/init.d/mosquitto stop) and 
then starting it (sudo /etc/init.d/mosquitto start) works. My theory  (with 
no real evidence :-)) is that when Mosquitto exits badly, it leaves its pid 
file, or some other flag, in place. When you try to start Mosquitto again, 
it sees that the pid file is there and won't start. If you first issue the 
stop command, Mosquitto clears the pid (or some other flag) which allows it 
to start when issued a start command.

I wonder if Mosquitto was unhappy about starting or restarting cleanly for 
you because of a leftover artifact, which cleared itself after time? Just 
speculation with no evidence.

Glad you have it running, at least.

phil

On Tuesday, October 9, 2018 at 6:27:24 AM UTC-4, G Hammer wrote:
>
> Well, I have followed Pat's guide and reconfigured my server's mosquitto 
> install.
> Websockets is a mysterious beast.
> This is what I get when I open my weather webpage:
> 1539079347: SNI: Unknown ServerName: ftp.ghammer.net
> 1539079348: Socket error on client , disconnecting.
> 1539079348: SNI: Unknown ServerName: ftp.ghammer.net
> 1539079368: SNI: Unknown ServerName: ftp.ghammer.net
>
> However, that is the server's name and the name in the SSL cert.
> 1539077963: Initial logging level 5
> 1539077963: Libwebsockets version: 2.0.3 unknown-build-hash
> 1539077963: IPV6 not compiled in
> 1539077963: libev support compiled in but disabled
> 1539077963: libuv support compiled in but disabled
> 1539077963:  Threads: 1 each 1024 fds
> 1539077963:  mem: platform fd map:  8192 bytes
> 1539077963:  Compiled with OpenSSL support
> 1539077963: Creating Vhost 'default' port 9001, 3 protocols
> 1539077963:  Using SSL mode
> 1539077963:  SSL ECDH curve 'prime256v1'
> 1539077963:  Listening on port 9001
> 1539077963:  mem: per-conn:  920 bytes + protocol rx buf
> 1539077963:  canonical_hostname = ftp.ghammer.net
> 1539077964: lws_protocol_init
>
> After about 15 minutes, voila!
> All is working with zero changes to any config.
> Quite puzzled, but not touching a thing.
>
> On Monday, October 8, 2018 at 5:52:39 PM UTC-4, Philip Kutzenco wrote:
>>
>> The answer to that question is no. I've attached a file with sanitized 
>> excerpts of my weewx.conf file showing the stanzas related to:
>>
>> 1. MQTT (publishing) - which specifies a username and password but not 
>> websocket (port 8883 - SSL not websocket)
>> 2. Belchertown Highcharts
>> 3. Belchertown (subscribing) - which specifies websockets but no 
>> username/password (port 9001 - SSL and websocket)
>>
>> You'll need to check with Pat, but I expect he saw no reason to lock down 
>> the subscriptions with username/password when programming his skin, only 
>> locking down the publishing (which is done by MWall's MQTT extension). I 
>> think the rationale is you don't care who sees the output (after all, it's 
>> being published on an open web site), but you don't want any unauthorized 
>> uploading of data which you'll be outputting and displaying to others.
>>
>> So, if the MQTT broker requires a username/password for subscribing over 
>> websockets, I don't know if the skin provides for that. I assume you've 
>> tried to prepend :@ to the host name in the Belchertown 
>> Extras stanza without success.
>>
>> Hopefully Pat can weigh in here.
>>
>> phil
>>
>>
>> On Monday, October 8, 2018 at 4:54:41 PM UTC-4, G Hammer wrote:
>>>
>>> Do you connect the client (skin) via websockets or any other way using a 
>>> username and password?
>>>
>>> That is the question.
>>>
>>>  
>>>
>>> *From:* weewx...@googlegroups.com  *On 
>>> Behalf Of *Philip Kutzenco
>>> *Sent:* Monday, October 8, 2018 3:32 PM
>>> *To:* weewx-user 
>>> *Subject:* [weewx-user] Re: Belchertown Skin and MQTT With Username Not 
>>> Working
>>>
>>>  
>>>
>>> I have it working on my own externally hosted Mosquitto server (on 
>>> Digital Ocean). My Mosquiutto MQTT broker is set up requiring a username 
>>> and password for publishing. Additionally it has TLS/SSL implemented (with 

[weewx-user] Re: Belchertown Skin and MQTT With Username Not Working

[Philip Kutzenco]

 I have it working on my own externally hosted Mosquitto server (on Digital 
Ocean). My Mosquitto MQTT broker is set up requiring a username and 
password for publishing. Additionally it has TLS/SSL implemented (with 
Let's Encrypt certificates). It allows subscribing anonymously and also 
runs Websockets so that it can feedthe Belchertown skin. I used Pat's MQTT 
"tutorial"  to 
do this. My website is https://wx.kutzenco.com.

phil

On Monday, October 8, 2018 at 10:21:50 AM UTC-4, G Hammer wrote:
>
>
> Does anyone have the Belchertown skin working with MQTT using a server 
> that requires a username and password such as CloudMQTT?
>
> I have tried several different ways of configuring the skin and it fails 
> to connect or it shows 'Connecting to weather station real time data' 
> forever without connecting.
> The data is being sent to the server fine and I have subscribed to it 
> using client software (see below).
>
> Thanks for any input, I'm at a loss here.
>
> [image: wxmqtt.png]
>
>

-- 
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 and MQTT With Username Not Working

[Philip Kutzenco]

I have it working on my own externally hosted Mosquitto server (on Digital 
Ocean). My Mosquiutto MQTT broker is set up requiring a username and 
password for publishing. Additionally it has TLS/SSL implemented (with 
Let's Encrypt certificates). It allows subscribing anonymously and also 
runs Websockets so that it can feedthe Belchertown skin. I used Pat's MQTT 
"tutorial"  to 
do this. My website is https://wx.kutzenco.com.

phil

On Monday, October 8, 2018 at 10:21:50 AM UTC-4, G Hammer wrote:
>
>
> Does anyone have the Belchertown skin working with MQTT using a server 
> that requires a username and password such as CloudMQTT?
>
> I have tried several different ways of configuring the skin and it fails 
> to connect or it shows 'Connecting to weather station real time data' 
> forever without connecting.
> The data is being sent to the server fine and I have subscribed to it 
> using client software (see below).
>
> Thanks for any input, I'm at a loss here.
>
> [image: wxmqtt.png]
>
>

-- 
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: Rsync vs FTP - which to choose/what are the pros and cons?

[Philip Kutzenco]

Thomas,

Can I make a request that the Rsync block in the initially default 
weewx.conf file be updated (for the next version) to include the following 
lines (which are included in the default weewx.conf FTP block but not the 
default weewx.conf RSYNC block):

# To upload files from something other than what HTML_ROOT is set
# to above, specify a different HTML_ROOT here.
#HTML_ROOT = public_html

It may be obvious to others, but it wasn't to me initially, that you need 
to specify that variable in the block to upload files generated by a 
specific skin. If you don't add an explicit HTML_ROOT definition in that 
block, the default HTML_ROOT definition from the beginning of weewx.conf is 
used.

By the way, I've gotten my external website set up and working great using 
Rsync to feed my weewx output files there. Thanks to everyone for weewx 
help and to you, in particular, for the terrific weewx software!!

phil

On Friday, October 5, 2018 at 5:26:09 PM UTC-4, Philip Kutzenco wrote:
>
> I am moving my weewx web server output to an outside hoster. What 
> considerations should I take into account to decide whether to use Rsync or 
> FTP (both should be available to me). I've looked at the user guide 
> sections for both options and (optimistically) believe I will be able to 
> set up either.
>
> What are the pros & cons of each method?
>
> Apologies if this question has been asked/answered before. If so, please 
> point me to the discussion or wiki topic.
>
> phil
>

-- 
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] Rsync vs FTP - which to choose/what are the pros and cons?

[Philip Kutzenco]

Perfect. Thanks!
phil

On Friday, October 5, 2018 at 5:35:07 PM UTC-4, Thomas Keffer wrote:
>
> rsync is superior in every way. It's secure, faster, and uses less 
> bandwidth. The only reason to use FTP is if your web host does not offer 
> rsync.
>
> -tk
>
> On Fri, Oct 5, 2018 at 2:26 PM Philip Kutzenco  > wrote:
>
>> I am moving my weewx web server output to an outside hoster. What 
>> considerations should I take into account to decide whether to use Rsync or 
>> FTP (both should be available to me). I've looked at the user guide 
>> sections for both options and (optimistically) believe I will be able to 
>> set up either.
>>
>> What are the pros & cons of each method?
>>
>> Apologies if this question has been asked/answered before. If so, please 
>> point me to the discussion or wiki topic.
>>
>> phil
>>
>> -- 
>> 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.

[weewx-user] Rsync vs FTP - which to choose/what are the pros and cons?

[Philip Kutzenco]

I am moving my weewx web server output to an outside hoster. What 
considerations should I take into account to decide whether to use Rsync or 
FTP (both should be available to me). I've looked at the user guide 
sections for both options and (optimistically) believe I will be able to 
set up either.

What are the pros & cons of each method?

Apologies if this question has been asked/answered before. If so, please 
point me to the discussion or wiki topic.

phil

-- 
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] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

Pat's new .py file seems to fix some of the charts. But, I think not all. 
I'm gathering details and will send them to him to check and see if there 
is still an issue to address. I'll post what I find here.
phil

On Saturday, September 29, 2018 at 9:47:24 PM UTC-4, Pat wrote:
>
> Hi everyone, I think this has been resolved in a latest commit. In 0.6 I 
> was using timespan but also highcharts was packaged as 1 skin. The 
> timespans were giving me some problems, so I reverted to time.time and that 
> was causing the problems you see. Thanks Gary for taking the time to check 
> my code! 
>
> I've pushed an updated commit here 
> <https://github.com/poblabs/weewx-belchertown/commit/5ac7b8d7165737c2f3ffd7dcfb22fa6fbcb0801d>and
>  
> you can view the new file in full here 
> <https://github.com/poblabs/weewx-belchertown/blob/5ac7b8d7165737c2f3ffd7dcfb22fa6fbcb0801d/bin/user/belchertown_highchartsSearchX.py>.
>  
> Those here are welcome to try it. If I don't hear back it'll be rolled into 
> my 0.8 update when I release that. 
>
>
> On Tuesday, September 25, 2018 at 9:48:21 PM UTC-4, Philip Kutzenco wrote:
>>
>> Yes, same for me. The week.json datafile has the last point for each 
>> measurement associated with the beginning of the 60 minute period following 
>> the current time. So, it is the same cause. As you say, it's likely related 
>> to the timestamp Pat chose to use.
>>
>> Phil
>>
>> On Tuesday, September 25, 2018 at 7:12:57 PM UTC-4, Colin Larsen wrote:
>>>
>>> I've just noticed that the end of the Week chart is an hour ahead of my 
>>> current time - probably all related
>>>
>>> On Wed, Sep 26, 2018 at 7:40 AM Colin Larsen  
>>> wrote:
>>>
>>>> Thanks Gary and Phil for finding and sorting this :)
>>>>
>>>> On Wed, 26 Sep 2018, 04:19 Philip Kutzenco,  wrote:
>>>>
>>>>> Gary,
>>>>>
>>>>> Excellent. Thanks for sussing this out! I'll look forward to Pat's 
>>>>> next release.
>>>>>
>>>>> Phil
>>>>>
>>>>> On Tuesday, September 25, 2018 at 10:04:07 AM UTC-4, gjr80 wrote:
>>>>>>
>>>>>> OK, I think I have handle on what is happening here. The cause is as 
>>>>>> Phil has noted, the last timestamp in each data series in month.json 
>>>>>> is midnight at the end of the current local day. A commit by Pat on 4 
>>>>>> September changed that timestamp from being the last timestamp in the 
>>>>>> archive to being the midnight timestamp. Looking at the releases that 
>>>>>> Pat 
>>>>>> has made I think 0.7 will exhibit this behaviour but 0.6 does not. I 
>>>>>> will 
>>>>>> drop Pat a line with the details.
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>> On Tuesday, 25 September 2018 22:14:20 UTC+10, Philip Kutzenco wrote:
>>>>>>>
>>>>>>> So, looking at the data in the json file, the last epoch date in the 
>>>>>>> series is 153793440 and translates to September 26 at 4:00 AM UTC. 
>>>>>>> So 
>>>>>>> that is midnight on September 26 EDT (my time zone). So it sounds like 
>>>>>>> the 
>>>>>>> aggregated temperature data displayed is for the period prior to that 
>>>>>>> date/time. But it definitely makes the plot seem inaccurate, especially 
>>>>>>> when you look at past dates. You'd expect that the aggregated data 
>>>>>>> point to 
>>>>>>> correspond to the data gathered from the start of the date to midnight 
>>>>>>> just 
>>>>>>> before the next date starts. I hope that is clear (and that I'm not 
>>>>>>> confused). 
>>>>>>>
>>>>>>> Phil
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco 
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> Gary,
>>>>>>>>
>>>>>>>> I think this is the file you want me to post. It is timestamped 
>>>>>>>> September 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone 
>>>>>>>> currently 
>>>>>>>> observing Daylight Saving Time. So my time zone is EDT. I checked 

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

[Philip Kutzenco]

You need to specify the full url, including http://

Best,

Phil

> On Sep 26, 2018, at 3:49 PM, Juan Antonio Mosquera 
>  wrote:
> 
> yesss
> 
>> On Wed, Sep 26, 2018, 21:43 Thomas Sch  wrote:
>> Thanks for the answer :) How do I do this? in weewx.conf ?
>> 
>> Am Mittwoch, 26. September 2018 21:31:46 UTC+2 schrieb Juan Antonio Mosquera:
>>> 
>>> Set station_url OK for css routes.
>>> 
>>> Hi.
>>> 
>>> El miércoles, 26 de septiembre de 2018, 21:14:18 (UTC+2), Thomas Sch 
>>> escribió:
 
> 
 
 Hey I installed the beautiful skin. But my generated website is not very 
 looking good. Is there a solution? I hope anyone can help me :D
 
  http://wilwetter.bplaced.net/wetterdaten/screenshot1.png
>> 
>> -- 
>> 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] NOAA data question

[Philip Kutzenco]

What skin are you using? I am using the belchertown skin. It copies the 
NOAA reports and displays them from the new location. I needed to delete 
the copy it made to force it to re-copy it before it would show the updated 
report. Again, my corrected data was from an older monthly NOAA report. I 
would go and check the actual NOAA report that the Standard report creates 
in /home/weewx/public_html/NOAA. If that's wrong, I'm sure Thomas will have 
a better suggestion.


Phil


On Wednesday, September 26, 2018 at 8:43:52 AM UTC-4, Charles Ross wrote:
>
> Yes I did, I followed that web page exactly yesterday.
>
>
> On Wednesday, September 26, 2018 at 8:37:22 AM UTC-4, Thomas Keffer wrote:
>>
>> Did you follow the directions in the Wiki entry, *Cleaning up old 'bad' 
>> data *?
>>
>> -tk
>>
>> On Wed, Sep 26, 2018 at 5:18 AM Charles Ross  wrote:
>>
>>> Hi all,
>>>
>>> Yesterday two pieces of bad temperature and dewpoint data made it's way 
>>> into the weewx.sdb archive database.   I removed the bad data but my NOAA 
>>> September and yearly files are still corrupt this morning.
>>>
>>> Can someone please guide me on how to fix the reports so I can have 
>>> correct NOAA reports?
>>>
>>> Thank you for taking the time to help,
>>>
>>> Chuck Ross 
>>>
>>> -- 
>>> 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.

[weewx-user] Re: NOAA data question

[Philip Kutzenco]

I'll let those with more experience and knowledge weigh in, if this is more 
to this. But have you followed the steps in this link 
https://github.com/weewx/weewx/wiki/Cleaning-up-old-'bad'-data? It worked 
for me. You shouldn't need to delete the existing NOAA reports as the 
latest monthly and yearly files should be re-created automatically (I had 
fixed older data and deleted the relevant monthly report to force 
re-creation). I think that dropping and rebuilding the old daily-summary 
tables is required.
Phil

On Wednesday, September 26, 2018 at 8:17:59 AM UTC-4, Charles Ross wrote:
>
> Hi all,
>
> Yesterday two pieces of bad temperature and dewpoint data made it's way 
> into the weewx.sdb archive database.   I removed the bad data but my NOAA 
> September and yearly files are still corrupt this morning.
>
> Can someone please guide me on how to fix the reports so I can have 
> correct NOAA reports?
>
> Thank you for taking the time to help,
>
> Chuck Ross 
>

-- 
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] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

Yes, same for me. The week.json datafile has the last point for each 
measurement associated with the beginning of the 60 minute period following 
the current time. So, it is the same cause. As you say, it's likely related 
to the timestamp Pat chose to use.

Phil

On Tuesday, September 25, 2018 at 7:12:57 PM UTC-4, Colin Larsen wrote:
>
> I've just noticed that the end of the Week chart is an hour ahead of my 
> current time - probably all related
>
> On Wed, Sep 26, 2018 at 7:40 AM Colin Larsen  > wrote:
>
>> Thanks Gary and Phil for finding and sorting this :)
>>
>> On Wed, 26 Sep 2018, 04:19 Philip Kutzenco, > > wrote:
>>
>>> Gary,
>>>
>>> Excellent. Thanks for sussing this out! I'll look forward to Pat's next 
>>> release.
>>>
>>> Phil
>>>
>>> On Tuesday, September 25, 2018 at 10:04:07 AM UTC-4, gjr80 wrote:
>>>>
>>>> OK, I think I have handle on what is happening here. The cause is as 
>>>> Phil has noted, the last timestamp in each data series in month.json 
>>>> is midnight at the end of the current local day. A commit by Pat on 4 
>>>> September changed that timestamp from being the last timestamp in the 
>>>> archive to being the midnight timestamp. Looking at the releases that Pat 
>>>> has made I think 0.7 will exhibit this behaviour but 0.6 does not. I will 
>>>> drop Pat a line with the details.
>>>>
>>>> Gary
>>>>
>>>> On Tuesday, 25 September 2018 22:14:20 UTC+10, Philip Kutzenco wrote:
>>>>>
>>>>> So, looking at the data in the json file, the last epoch date in the 
>>>>> series is 153793440 and translates to September 26 at 4:00 AM UTC. So 
>>>>> that is midnight on September 26 EDT (my time zone). So it sounds like 
>>>>> the 
>>>>> aggregated temperature data displayed is for the period prior to that 
>>>>> date/time. But it definitely makes the plot seem inaccurate, especially 
>>>>> when you look at past dates. You'd expect that the aggregated data point 
>>>>> to 
>>>>> correspond to the data gathered from the start of the date to midnight 
>>>>> just 
>>>>> before the next date starts. I hope that is clear (and that I'm not 
>>>>> confused). 
>>>>>
>>>>> Phil
>>>>>
>>>>>
>>>>>
>>>>> On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco 
>>>>> wrote:
>>>>>>
>>>>>> Gary,
>>>>>>
>>>>>> I think this is the file you want me to post. It is timestamped 
>>>>>> September 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone 
>>>>>> currently 
>>>>>> observing Daylight Saving Time. So my time zone is EDT. I checked the 
>>>>>> date 
>>>>>> and time with the date command on my Raspberry Pi running running weewx 
>>>>>> and 
>>>>>> it is correct.
>>>>>>
>>>>>> Let me know if you wanted a different file.
>>>>>>
>>>>>> Thanks. I appreciate the help.
>>>>>>
>>>>>> Phil
>>>>>>
>>>>>> On Monday, September 24, 2018 at 11:33:58 PM UTC-4, gjr80 wrote:
>>>>>>>
>>>>>>> I suspect the issue will be related to how highcharts is 
>>>>>>> interpreting timestamps in the plot data rather then the wrong data 
>>>>>>> being 
>>>>>>> in the plot data files. I have seen something like this before but it 
>>>>>>> was 
>>>>>>> related to the timezone of the client computer viewing the plots, would 
>>>>>>> seem that is not the issue here though. I am rather pushed for time at 
>>>>>>> the 
>>>>>>> moment but will have a look when I can, though it's been a while though 
>>>>>>> since I have delved into highcharts.
>>>>>>>
>>>>>>> Phil, can you post one of the generated  highcharts data files that 
>>>>>>> is displaying the issue. Would help to know your timezone and at  what 
>>>>>>> time 
>>>>>>> the file was generated as well.
>>>>>>>
>>>>>>> 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+...@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] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

Gary,

Excellent. Thanks for sussing this out! I'll look forward to Pat's next 
release.

Phil

On Tuesday, September 25, 2018 at 10:04:07 AM UTC-4, gjr80 wrote:
>
> OK, I think I have handle on what is happening here. The cause is as Phil 
> has noted, the last timestamp in each data series in month.json is 
> midnight at the end of the current local day. A commit by Pat on 4 
> September changed that timestamp from being the last timestamp in the 
> archive to being the midnight timestamp. Looking at the releases that Pat 
> has made I think 0.7 will exhibit this behaviour but 0.6 does not. I will 
> drop Pat a line with the details.
>
> Gary
>
> On Tuesday, 25 September 2018 22:14:20 UTC+10, Philip Kutzenco wrote:
>>
>> So, looking at the data in the json file, the last epoch date in the 
>> series is 153793440 and translates to September 26 at 4:00 AM UTC. So 
>> that is midnight on September 26 EDT (my time zone). So it sounds like the 
>> aggregated temperature data displayed is for the period prior to that 
>> date/time. But it definitely makes the plot seem inaccurate, especially 
>> when you look at past dates. You'd expect that the aggregated data point to 
>> correspond to the data gathered from the start of the date to midnight just 
>> before the next date starts. I hope that is clear (and that I'm not 
>> confused). 
>>
>> Phil
>>
>>
>>
>> On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco wrote:
>>>
>>> Gary,
>>>
>>> I think this is the file you want me to post. It is timestamped 
>>> September 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone currently 
>>> observing Daylight Saving Time. So my time zone is EDT. I checked the date 
>>> and time with the date command on my Raspberry Pi running running weewx and 
>>> it is correct.
>>>
>>> Let me know if you wanted a different file.
>>>
>>> Thanks. I appreciate the help.
>>>
>>> Phil
>>>
>>> On Monday, September 24, 2018 at 11:33:58 PM UTC-4, gjr80 wrote:
>>>>
>>>> I suspect the issue will be related to how highcharts is interpreting 
>>>> timestamps in the plot data rather then the wrong data being in the plot 
>>>> data files. I have seen something like this before but it was related to 
>>>> the timezone of the client computer viewing the plots, would seem that is 
>>>> not the issue here though. I am rather pushed for time at the moment but 
>>>> will have a look when I can, though it's been a while though since I have 
>>>> delved into highcharts.
>>>>
>>>> Phil, can you post one of the generated  highcharts data files that is 
>>>> displaying the issue. Would help to know your timezone and at  what time 
>>>> the file was generated as well.
>>>>
>>>> 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] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

So, looking at the data in the json file, the last epoch date in the series 
is 153793440 and translates to September 26 at 4:00 AM UTC. So that is 
midnight on September 26 EDT (my time zone). So it sounds like the 
aggregated temperature data displayed is for the period prior to that 
date/time. But it definitely makes the plot seem inaccurate, especially 
when you look at past dates. You'd expect that the aggregated data point to 
correspond to the data gathered from the start of the date to midnight just 
before the next date starts. I hope that is clear (and that I'm not 
confused). 

Phil



On Tuesday, September 25, 2018 at 7:59:03 AM UTC-4, Philip Kutzenco wrote:
>
> Gary,
>
> I think this is the file you want me to post. It is timestamped September 
> 25, 2108 at 7:46 AM. I am in the US Eastern Time Zone currently observing 
> Daylight Saving Time. So my time zone is EDT. I checked the date and time 
> with the date command on my Raspberry Pi running running weewx and it is 
> correct.
>
> Let me know if you wanted a different file.
>
> Thanks. I appreciate the help.
>
> Phil
>
> On Monday, September 24, 2018 at 11:33:58 PM UTC-4, gjr80 wrote:
>>
>> I suspect the issue will be related to how highcharts is interpreting 
>> timestamps in the plot data rather then the wrong data being in the plot 
>> data files. I have seen something like this before but it was related to 
>> the timezone of the client computer viewing the plots, would seem that is 
>> not the issue here though. I am rather pushed for time at the moment but 
>> will have a look when I can, though it's been a while though since I have 
>> delved into highcharts.
>>
>> Phil, can you post one of the generated  highcharts data files that is 
>> displaying the issue. Would help to know your timezone and at  what time 
>> the file was generated as well.
>>
>> 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] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

OK. More info. I checked Pat O'Brien's website and also  Juan Antonio 
Mosquera's website. Neither shows the date offset that my website shows. 
So, It looks like I've got a problem with my implementation or my database. 
But, since the NOAA reports for monthly min and max seem to be correct, 
that argues, I think, that the database is ok.

Where should I look? I considered time zone offsets, but Pat and I are in 
the same time zone and his website doesn't exhibit the issue. Is it in the 
calculation of daily min and max? Is there a way to clear them and 
recalculate/store them in the database?

Best,
Phil

On Monday, September 24, 2018 at 10:24:30 PM UTC-4, Philip Kutzenco wrote:
>
> Ah, yes. Gary is correct. It appears that only rainfall is aggregated (two 
> hour aggregates for the Monthly plot). The others seem to be Min or Max at 
> a discrete time.
>
> Phil
>
> On Monday, September 24, 2018 at 10:19:34 PM UTC-4, Philip Kutzenco wrote:
>>
>> Thomas,
>>
>> I think you are correct about aggregated data. Unfortunately, my website 
>> isn't externally available (yet). But I attached a couple of screenshots 
>> (monthly temperature and rainfall). On the monthly plots, each point seems 
>> to represent a 2 hour aggregate. You can see how the latest temperature 
>> data is associated with tomorrow's date, while the latest rainfall data is 
>> labeled with today's date.
>>
>> I don't have any other skins with Highcharts. So, I don't know if my 
>> issue is confined to my implementation, or the Belchertown skin, or if it 
>> is caused by the Highcharts code itself.
>>
>> Phil
>>
>> On Monday, September 24, 2018 at 9:19:10 PM UTC-4, Thomas Keffer wrote:
>>>
>>> You're probably right. Plus, I gather that you are working with 
>>> aggregated plots, not the raw data?
>>>
>>> It was just a thought...
>>>
>>> -tk
>>>
>>> On Mon, Sep 24, 2018 at 6:11 PM Philip Kutzenco  
>>> wrote:
>>>
>>>> If that's so, wouldn't rainfall also exhibit the offset?
>>>>
>>>> Even if Thomas is correct (and something about rainfall calculation 
>>>> keeps it from being offset), the call out numbers (showing data values and 
>>>> date) you see when you move the cursor across the graph are wrong because 
>>>> of the date offset. So, it may be a bug, but the graphs are definitely 
>>>> wrong, at least in my implementation of the Belchertown skin. 
>>>>
>>>> Phil
>>>>
>>>> On Monday, September 24, 2018 at 8:14:19 PM UTC-4, Thomas Keffer wrote:
>>>>>
>>>>> In WeeWX, records are timestamped with the *end* of the record. 
>>>>> Perhaps Highcharts uses the beginning?
>>>>>
>>>>> -tk
>>>>>
>>>>> On Mon, Sep 24, 2018 at 10:28 AM Philip Kutzenco  
>>>>> wrote:
>>>>>
>>>>>> I notice that, for me, some of the historic data graphs supplied with 
>>>>>> the Belchertown skin are off by one day. In particular, if you go to the 
>>>>>> "Graphs" page and select either "Month" or "Year", the temperature graph 
>>>>>> data are labeled as being one day beyond what they should be. For 
>>>>>> instance 
>>>>>> at the right end of the plot, today's data is shown, but the date on the 
>>>>>> y-axis is tomorrow's date.
>>>>>>
>>>>>> This is also true for the Wind/Wind Gust graph, the Wind Direction 
>>>>>> graph and also the Barometer graph. The Rainfall graph is fine.
>>>>>>
>>>>>> If you select "Week" all of the graphs are fine; of course the data 
>>>>>> on the "Today" and "Week" are actual recorded data points, while the 
>>>>>> "Month" and "Year" data are max and min data for each date.
>>>>>>
>>>>>> For some more context, the Standard skin shows the correct max and 
>>>>>> min temperature data for the month of September (I didn't check 
>>>>>> further). 
>>>>>> Also, I did need to NULL some anomalous temperature data in the database 
>>>>>> for June 14 (the guy who stained my back deck through a plastic sheet 
>>>>>> over 
>>>>>> my weather station for  hours). I followed the directions in the Wiki 
>>>>>> and 
>>>>>> had weewx recalculate the summaries without inc

Re: [weewx-user] Date error on some historic data graphs using Belchertown skin

[Philip Kutzenco]

Ah, yes. Gary is correct. It appears that only rainfall is aggregated (two 
hour aggregates for the Monthly plot). The others seem to be Min or Max at 
a discrete time.

Phil

On Monday, September 24, 2018 at 10:19:34 PM UTC-4, Philip Kutzenco wrote:
>
> Thomas,
>
> I think you are correct about aggregated data. Unfortunately, my website 
> isn't externally available (yet). But I attached a couple of screenshots 
> (monthly temperature and rainfall). On the monthly plots, each point seems 
> to represent a 2 hour aggregate. You can see how the latest temperature 
> data is associated with tomorrow's date, while the latest rainfall data is 
> labeled with today's date.
>
> I don't have any other skins with Highcharts. So, I don't know if my issue 
> is confined to my implementation, or the Belchertown skin, or if it is 
> caused by the Highcharts code itself.
>
> Phil
>
> On Monday, September 24, 2018 at 9:19:10 PM UTC-4, Thomas Keffer wrote:
>>
>> You're probably right. Plus, I gather that you are working with 
>> aggregated plots, not the raw data?
>>
>> It was just a thought...
>>
>> -tk
>>
>> On Mon, Sep 24, 2018 at 6:11 PM Philip Kutzenco  
>> wrote:
>>
>>> If that's so, wouldn't rainfall also exhibit the offset?
>>>
>>> Even if Thomas is correct (and something about rainfall calculation 
>>> keeps it from being offset), the call out numbers (showing data values and 
>>> date) you see when you move the cursor across the graph are wrong because 
>>> of the date offset. So, it may be a bug, but the graphs are definitely 
>>> wrong, at least in my implementation of the Belchertown skin. 
>>>
>>> Phil
>>>
>>> On Monday, September 24, 2018 at 8:14:19 PM UTC-4, Thomas Keffer wrote:
>>>>
>>>> In WeeWX, records are timestamped with the *end* of the record. 
>>>> Perhaps Highcharts uses the beginning?
>>>>
>>>> -tk
>>>>
>>>> On Mon, Sep 24, 2018 at 10:28 AM Philip Kutzenco  
>>>> wrote:
>>>>
>>>>> I notice that, for me, some of the historic data graphs supplied with 
>>>>> the Belchertown skin are off by one day. In particular, if you go to the 
>>>>> "Graphs" page and select either "Month" or "Year", the temperature graph 
>>>>> data are labeled as being one day beyond what they should be. For 
>>>>> instance 
>>>>> at the right end of the plot, today's data is shown, but the date on the 
>>>>> y-axis is tomorrow's date.
>>>>>
>>>>> This is also true for the Wind/Wind Gust graph, the Wind Direction 
>>>>> graph and also the Barometer graph. The Rainfall graph is fine.
>>>>>
>>>>> If you select "Week" all of the graphs are fine; of course the data on 
>>>>> the "Today" and "Week" are actual recorded data points, while the "Month" 
>>>>> and "Year" data are max and min data for each date.
>>>>>
>>>>> For some more context, the Standard skin shows the correct max and min 
>>>>> temperature data for the month of September (I didn't check further). 
>>>>> Also, 
>>>>> I did need to NULL some anomalous temperature data in the database for 
>>>>> June 
>>>>> 14 (the guy who stained my back deck through a plastic sheet over my 
>>>>> weather station for  hours). I followed the directions in the Wiki and 
>>>>> had 
>>>>> weewx recalculate the summaries without incident. I also deleted the June 
>>>>> NOAA report, which was properly re-created. I did look at that June NOAA 
>>>>> report which shows the correct min and max temperatures for each date, 
>>>>> while the Belchertown "Year" graph is off by one day for the June 
>>>>> temperature data. So none of what I did seems to me to be causal for a 
>>>>> Monthly graph to list today's data with a Y-axis of tomorrow. 
>>>>>
>>>>> I know that Pat is using code from Highcharts for these graphs but I 
>>>>> don't know if this is occurring in all Highcharts, only those in the 
>>>>> Belchertown skin, or only for me.
>>>>>
>>>>> Does anyone else see this? Where should I look to identify the cause? 
>>>>> Is there any other information I should post to help the group guide me?
>>>>>
>>>>> Phil
>>>>>
>>>>> -- 
>>>>> 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+...@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] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

Thomas,

Thanks for improving the fallback moon phase calculation for those who 
haven't installed pyephem. Happily, with the help of Gary, you, and others, 
I've done that.

Reading your post, though, I find it interesting that something as well 
studied and modeled as moon phases doesn't have a well accepted algorithm 
that can be applied. The different values provided by different web sites 
who offer the result of calculating it shows that lack. It makes you wonder 
about the accuracy of other astronomical calculations, often provided with 
many significant digits. It reminds us that precision doesn't guarantee 
accuracy!

Best,
Phil

On Monday, September 17, 2018 at 10:04:00 AM UTC-4, Thomas Keffer wrote:
>
> I've changed the formula used to calculate the moon phase if you have not 
> installed pyephem. For 15-Sept-2018, this version gives 37% illumination 
> (versus 24% for the old version).
>
> Interesting project. I learned a lot about lunations and how to calculate 
> the phases of the moon. The root problem is that the time between new moons 
> is not a constant value. So, as time marches on, the approximations get 
> worse and worse.
>
> This new version starts with the first new moon of 2018 (16-Jan-2018) and 
> calculates forward from that.
>
> Commit 0220656 
> <https://github.com/weewx/weewx/commit/0220656bc86785b51684d7eb20dfd3a991dee8f7>
>
> -tk
>
> On Sun, Sep 16, 2018 at 4:45 AM Philip Kutzenco  > wrote:
>
>> Gary,
>>
>> OK. It's working now! 
>>
>> Interestingly - "sudo pip uninstall ephem" and "sudo pip uninstall 
>> pyephem" gave not-installed errors. However, "pip uninstall ephem" and "pip 
>> uninstall pyephem" both did uninstalls. It appears that installing without 
>> privileges puts the files in /home/pi/.local/lib/python2.7/site-packages/ .
>> After uninstalling both, I installed pyephem with sudo, restarted weewx 
>> and now am showing 46% moon illumination on both the standard skin and the 
>> belchertown skin.
>>
>> Thanks for your (and everyone else's) help.
>>
>> Now if someone can help explain the inconsistency between the DarkSky API 
>> download and the DarkSky.net forecast for my location I'd be grateful. 
>> If I see no answer to that, I can move that question to a new topic. 
>>
>> Best,
>> Phil
>>
>> On Sunday, September 16, 2018 at 1:14:28 AM UTC-4, gjr80 wrote:
>>>
>>> On Sunday, 16 September 2018 12:39:53 UTC+10, Philip Kutzenco wrote:
>>>>
>>>>
>>>> Plus that doesn't explain why weewx is still indicating 24% on Standard 
>>>> and Belchertown skins for me.
>>>>
>>>>
>>> Let's deal with the second problem first. It appears that installing 
>>> ephem and pyephem as an unprivileged causes issues, particularly for 
>>> WeeWX (well it does on my Debian stretch VM). I would also be using 
>>> pyephem and not ephem. First off let's uninstall ephem and pyephem:
>>>
>>> $ sudo pip uninstall ephem
>>> $ sudo pip uninstall pyephem
>>>
>>> answer y to any y/n prompts
>>>
>>> Now install pyephem making sure you have privileges:
>>>
>>> $ sudo pip install pyephem
>>>
>>> and finally restart WeeWX:
>>>
>>> $ sudo systemctl restart weewx
>>>
>>> Wait for a report cycle to complete then check you pages again.
>>>
>>> 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+...@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] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

Gary,

OK. It's working now! 

Interestingly - "sudo pip uninstall ephem" and "sudo pip uninstall pyephem" 
gave not-installed errors. However, "pip uninstall ephem" and "pip 
uninstall pyephem" both did uninstalls. It appears that installing without 
privileges puts the files in /home/pi/.local/lib/python2.7/site-packages/ .
After uninstalling both, I installed pyephem with sudo, restarted weewx and 
now am showing 46% moon illumination on both the standard skin and the 
belchertown skin.

Thanks for your (and everyone else's) help.

Now if someone can help explain the inconsistency between the DarkSky API 
download and the DarkSky.net forecast for my location I'd be grateful. If I 
see no answer to that, I can move that question to a new topic. 

Best,
Phil

On Sunday, September 16, 2018 at 1:14:28 AM UTC-4, gjr80 wrote:
>
> On Sunday, 16 September 2018 12:39:53 UTC+10, Philip Kutzenco wrote:
>>
>>
>> Plus that doesn't explain why weewx is still indicating 24% on Standard 
>> and Belchertown skins for me.
>>
>>
> Let's deal with the second problem first. It appears that installing ephem 
> and pyephem as an unprivileged causes issues, particularly for WeeWX 
> (well it does on my Debian stretch VM). I would also be using pyephem and 
> not ephem. First off let's uninstall ephem and pyephem:
>
> $ sudo pip uninstall ephem
> $ sudo pip uninstall pyephem
>
> answer y to any y/n prompts
>
> Now install pyephem making sure you have privileges:
>
> $ sudo pip install pyephem
>
> and finally restart WeeWX:
>
> $ sudo systemctl restart weewx
>
> Wait for a report cycle to complete then check you pages again.
>
> 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] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

So just now, following your code I entered:

>>> import ephem
>>> moon = ephem.Moon()
>>> moon.compute()
>>> print moon.phase
*and got*
41.6761169434

When I enter:

>>> import datetime
>>> import ephem
>>> print(ephem.Moon(datetime.date.today()).moon_phase)
*now I get*
0.31187416036

That's too large a difference between midnight and the actual time.

I'm clearly confused or doing something wrong (or both).

Plus that doesn't explain why weewx is still indicating 24% on Standard and 
Belchertown skins for me.

Best,
Phil

On Saturday, September 15, 2018 at 7:53:44 PM UTC-4, gjr80 wrote:
>
> Likewise on the first part.
>
> Just now my pyephem enabled page shows 41%, a non-pyephem enabled VM shows 
> 34%, timeanddate.com shows 40.5%, best I could get from USNO is 41% but I 
> am not sure as of what time that is, it is just shown as a 'day' figure. 
> Pyephem gives me 40.5641403198% but that is using:
>
> >>> import ephem
> >>> moon = ephem.Moon()
> >>> moon.compute()
> >>> print moon.phase
> 40.5641403198
>
> Your pyephem code gives me
>
> >>> import ephem
> >>> print(ephem.Moon(datetime.date.today()).moon_phase)
> 0.408785965463
> >>> datetime.date.today()
> datetime.date(2018, 9, 16)
>
> but I suspect the variance there is because datetime.date.today() returns 
> a date with no time so I suspect that will mean pyephem returns the moon 
> phase at midnight today whereas ephem.Moon()  will cause the current time 
> to be used instead. 
>
> Might need to look into the non-pyephem page 34% value but all the others 
> seem completely consistent to me.
>
> Gary
>
> On Sunday, 16 September 2018 09:26:30 UTC+10, Thomas Keffer wrote:
>>
>> Can't help you with the first of your two questions.
>>
>> Regarding the second, when I look at my own skin 
>> <http://www.threefools.org/weewx/>, it shows 41% for today. Are you sure 
>> you're not looking at an old, perhaps cached, version?
>>
>> -tk
>>
>> On Sat, Sep 15, 2018 at 2:45 PM Philip Kutzenco  
>> wrote:
>>
>>> I've noticed that some information from the DarkSky API as well as 
>>> calculated moon phase don't seem to be correct or consistent with other 
>>> sources of data on WeeWX. Here's what I have seen:
>>>
>>> *DarkSky API* - I display a minimal 8 day forecast on the Belchertown 
>>> Skin. When I pull down the values using the SPI directly with my lat and 
>>> long, the values pulled down match what the skin shows. However, If I go to 
>>> DarkSky.net using the same location, the values (like min & max temp, 
>>> weather icon, precip probability etc.) are usually very different. I'm 
>>> pretty tuned into the weather right now as I live in Western North Carolina 
>>> and will be impacted by the remains of Florence over the next several days. 
>>> What's going on with the DarkSky API?
>>>
>>> *Moon phase* - WeeWX shows the moon phase for today to be a waxing 
>>> crescent - 24% (I think that means 24% visible or illuminated). When I do 
>>> the calculation using python's ephem module - 
>>> *print(ephem.Moon(datetime.date.today()).moon_phase)* - the answer I 
>>> get for moon phase is 31.19%. I thought that WeeWX used ephem for that 
>>> calculation. On timeanddate.com today's moon phase is 39.5%. At 
>>> http://aa.usno.navy.mil, 37% of the moon is illuminated today. Why such 
>>> a variation?
>>>
>>> These two items are vexing me. Can someone help explain these anomalies?
>>>
>>> Phil
>>>
>>> -- 
>>> 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] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

I am also using MQTT realtime data - my Belchertown skin continues to show 
24%. The my Standard skin also shows 24% for me. As I'm in the US, I am 
using US for the units. As I mentioned earlier I ran pip install pyephem, 
then stopped and started weewx. 

Also, I'm running weewx on a Raspberry Pi Zero W. It's got the latest 
version of Raspbian and weewx 3.8.2.

For what it's worth I had previously installed ephem (not pyephem) with pip 
install ephem. I was obviously confused about the two (still am, I guess). 
But after Thomas said to install pyephem and you indicated success when 
doing that, I installed that package.

Best,
Phil

On Saturday, September 15, 2018 at 9:22:21 PM UTC-4, Colin Larsen wrote:
>
> Philip, interestingly although at one stage I did see the 34% value I 
> reported it then changed to the 24% that you have (and I did have) - not 
> sure what that's about.
>
> I did nothing other than installing, restarting Weewx and waiting an 
> archive period
>
> In terms of difference between your site and mine (both running 
> Belchertown skins) I have metric set and am using the mqtt real-time update 
> system. I have no idea if either of those is pertinent or if the Moon data 
> is even included in the real-time data.
>
> Cheers
> Colin
>
> On Sun, Sep 16, 2018 at 1:02 PM Philip Kutzenco  > wrote:
>
>> No joy for me. I must be doing something wrong. I installed pyephem (pip 
>> install pyephem). Then I stopped and started weewx. My standard and 
>> belchertown skins still show 24% even after waiting for a couple of archive 
>> intervals. Is there someplace I tell weewx to use pyephem? I did clear the 
>> cache on my browser to be sure it isn't that.
>>
>> Phil
>>
>> On Saturday, September 15, 2018 at 8:14:57 PM UTC-4, Thomas Keffer wrote:
>>>
>>> Yes, like Colin, you must not be using pyephem. As mentioned earlier in 
>>> this thread, I've created issue #342 
>>> <https://github.com/weewx/weewx/issues/342> to track this.
>>>
>>> In the meantime, try installing pyephem.
>>>
>>> -tk
>>>
>>> On Sat, Sep 15, 2018 at 5:11 PM Philip Kutzenco  
>>> wrote:
>>>
>>>> Thomas,
>>>>
>>>> Thanks for replying. My website isn't published externally, but I've 
>>>> attached a screenshot of part of the Standard skin display. I'm pretty 
>>>> sure 
>>>> it isn't cached. Also, take a look at Pat's 
>>>> http://www.belchertownweather.com website. Both my standard skin (as 
>>>> well as my implementation of the belchertown skin) and Pat's skin show 24% 
>>>> today.
>>>>
>>>> Phil
>>>>
>>>> On Saturday, September 15, 2018 at 7:26:30 PM UTC-4, Thomas Keffer 
>>>> wrote:
>>>>>
>>>>> Can't help you with the first of your two questions.
>>>>>
>>>>> Regarding the second, when I look at my own skin 
>>>>> <http://www.threefools.org/weewx/>, it shows 41% for today. Are you 
>>>>> sure you're not looking at an old, perhaps cached, version?
>>>>>
>>>>> -tk
>>>>>
>>>>> On Sat, Sep 15, 2018 at 2:45 PM Philip Kutzenco  
>>>>> wrote:
>>>>>
>>>>>> I've noticed that some information from the DarkSky API as well as 
>>>>>> calculated moon phase don't seem to be correct or consistent with other 
>>>>>> sources of data on WeeWX. Here's what I have seen:
>>>>>>
>>>>>> *DarkSky API* - I display a minimal 8 day forecast on the 
>>>>>> Belchertown Skin. When I pull down the values using the SPI directly 
>>>>>> with 
>>>>>> my lat and long, the values pulled down match what the skin shows. 
>>>>>> However, 
>>>>>> If I go to DarkSky.net using the same location, the values (like min 
>>>>>> & max temp, weather icon, precip probability etc.) are usually very 
>>>>>> different. I'm pretty tuned into the weather right now as I live in 
>>>>>> Western 
>>>>>> North Carolina and will be impacted by the remains of Florence over the 
>>>>>> next several days. What's going on with the DarkSky API?
>>>>>>
>>>>>> *Moon phase* - WeeWX shows the moon phase for today to be a waxing 
>>>>>> crescent - 24% (I think that means 24% visible or illuminated). When I 
>>>>>> do 
>>>>>> the calculation using python's ephem 

Re: [weewx-user] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

No joy for me. I must be doing something wrong. I installed pyephem (pip 
install pyephem). Then I stopped and started weewx. My standard and 
belchertown skins still show 24% even after waiting for a couple of archive 
intervals. Is there someplace I tell weewx to use pyephem? I did clear the 
cache on my browser to be sure it isn't that.

Phil

On Saturday, September 15, 2018 at 8:14:57 PM UTC-4, Thomas Keffer wrote:
>
> Yes, like Colin, you must not be using pyephem. As mentioned earlier in 
> this thread, I've created issue #342 
> <https://github.com/weewx/weewx/issues/342> to track this.
>
> In the meantime, try installing pyephem.
>
> -tk
>
> On Sat, Sep 15, 2018 at 5:11 PM Philip Kutzenco  > wrote:
>
>> Thomas,
>>
>> Thanks for replying. My website isn't published externally, but I've 
>> attached a screenshot of part of the Standard skin display. I'm pretty sure 
>> it isn't cached. Also, take a look at Pat's 
>> http://www.belchertownweather.com website. Both my standard skin (as 
>> well as my implementation of the belchertown skin) and Pat's skin show 24% 
>> today.
>>
>> Phil
>>
>> On Saturday, September 15, 2018 at 7:26:30 PM UTC-4, Thomas Keffer wrote:
>>>
>>> Can't help you with the first of your two questions.
>>>
>>> Regarding the second, when I look at my own skin 
>>> <http://www.threefools.org/weewx/>, it shows 41% for today. Are you 
>>> sure you're not looking at an old, perhaps cached, version?
>>>
>>> -tk
>>>
>>> On Sat, Sep 15, 2018 at 2:45 PM Philip Kutzenco  
>>> wrote:
>>>
>>>> I've noticed that some information from the DarkSky API as well as 
>>>> calculated moon phase don't seem to be correct or consistent with other 
>>>> sources of data on WeeWX. Here's what I have seen:
>>>>
>>>> *DarkSky API* - I display a minimal 8 day forecast on the Belchertown 
>>>> Skin. When I pull down the values using the SPI directly with my lat and 
>>>> long, the values pulled down match what the skin shows. However, If I go 
>>>> to 
>>>> DarkSky.net using the same location, the values (like min & max temp, 
>>>> weather icon, precip probability etc.) are usually very different. I'm 
>>>> pretty tuned into the weather right now as I live in Western North 
>>>> Carolina 
>>>> and will be impacted by the remains of Florence over the next several 
>>>> days. 
>>>> What's going on with the DarkSky API?
>>>>
>>>> *Moon phase* - WeeWX shows the moon phase for today to be a waxing 
>>>> crescent - 24% (I think that means 24% visible or illuminated). When I do 
>>>> the calculation using python's ephem module - 
>>>> *print(ephem.Moon(datetime.date.today()).moon_phase)* - the answer I 
>>>> get for moon phase is 31.19%. I thought that WeeWX used ephem for that 
>>>> calculation. On timeanddate.com today's moon phase is 39.5%. At 
>>>> http://aa.usno.navy.mil, 37% of the moon is illuminated today. Why 
>>>> such a variation?
>>>>
>>>> These two items are vexing me. Can someone help explain these anomalies?
>>>>
>>>> Phil
>>>>
>>>> -- 
>>>> 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+...@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] Values displayed by WeeWX skins from DarkSky API and moon phase calculations don't seem correct - Anyone else notice this?

[Philip Kutzenco]

I've noticed that some information from the DarkSky API as well as 
calculated moon phase don't seem to be correct or consistent with other 
sources of data on WeeWX. Here's what I have seen:

*DarkSky API* - I display a minimal 8 day forecast on the Belchertown Skin. 
When I pull down the values using the SPI directly with my lat and long, 
the values pulled down match what the skin shows. However, If I go to 
DarkSky.net using the same location, the values (like min & max temp, 
weather icon, precip probability etc.) are usually very different. I'm 
pretty tuned into the weather right now as I live in Western North Carolina 
and will be impacted by the remains of Florence over the next several days. 
What's going on with the DarkSky API?

*Moon phase* - WeeWX shows the moon phase for today to be a waxing crescent 
- 24% (I think that means 24% visible or illuminated). When I do the 
calculation using python's ephem module - 
*print(ephem.Moon(datetime.date.today()).moon_phase)* - the answer I get 
for moon phase is 31.19%. I thought that WeeWX used ephem for that 
calculation. On timeanddate.com today's moon phase is 39.5%. At 
http://aa.usno.navy.mil, 37% of the moon is illuminated today. Why such a 
variation?

These two items are vexing me. Can someone help explain these anomalies?

Phil

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

[Philip Kutzenco]

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 with the vantage driver getting data from my 
> Davis Vantage Vue. My setup gets wind data. I looked at your web site and 
> you also seem to be getting wind data. I see a wind gust and wind charted 
> on the main page and wind data in the reports.
>
> What issue are you having with wind?
>
> On Tuesday, September 11, 2018 at 3:48:44 AM UTC-4, Juan Antonio Mosquera 
> wrote:
>
> I installed 0.7 version... all ok... but no data of Wind...
>
>
> http://www.meteomontaos2.ga/
>
> any problem?
>
> Thanks.
>
> El sábado, 8 de septiembre de 2018, 20:48:04 (UTC+2), Pat escribió:
>
> ...

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

[Philip Kutzenco]

I am running version 0.7 with the vantage driver getting data from my Davis 
Vantage Vue. My setup gets wind data. I looked at your web site and you 
also seem to be getting wind data. I see a wind gust and wind charted on 
the main page and wind data in the reports.

What issue are you having with wind?

On Tuesday, September 11, 2018 at 3:48:44 AM UTC-4, Juan Antonio Mosquera 
wrote:
>
> I installed 0.7 version... all ok... but no data of Wind...
>
>
> http://www.meteomontaos2.ga/
>
> any problem?
>
> Thanks.
>
> El sábado, 8 de septiembre de 2018, 20:48:04 (UTC+2), Pat escribió:
>
> 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.
>
> ...

-- 
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] Potential extension for Belchertown skin

[Philip Kutzenco]

Pat,
I am using your Belchertown skin to display data from a Davis Vantage Vue 
weather station. The Vantage Vue does not have a UV sensor, so the Charts 
feature of the Belchertown skin shows an empty chart for solar radiation.

I would like to replace the solar radiation chart and history with a chart 
of humidity and history. I assume that change would require a change to 
belchertown_highchartsSearchX.py. It appears that Gary's original 
highchartsSearchX.py does, in fact, include humidity data.

The most flexible solution would be to add humidity data to the 
belchertown_highcharts and set things up so that choices about which charts 
are included would be options in the [[EXTRAS]] part of weewx.conf for 
Belchertown. Things like calculated cloud base could also be an added 
option. Any chance you would be willing to do that? If not, could you point 
me to the way to what I would need to change in 
belchertown_highchartsSearchX.py (and any other scripts required) to 
replace solar radiation with humidity (I've done programming in the past, 
but never Python coding). I guess I could also try implementing the 
flexible solution of allowing choices in weewx.conf, though that may be 
beyond my abilities at this point.

I'm still working to implement MQTT updating on my Belchertown installation 
and will then publish my website externally.

Phil

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

[Philip Kutzenco]

Pat,

Gotcha. I'm disabling the highcharts portion. Will be glad to test any 
changes you make.

Best,
Phil

On Monday, September 3, 2018 at 8:46:44 PM UTC-4, Pat wrote:
>
> That's what looks like is going on. Your reports are stepping on each 
> other and the database is locked. 
>
> You can either disable the highcharts portion by setting highcharts_enabled 
> = 0 <https://github.com/poblabs/weewx-belchertown#general-options> in 
> options or disable the skin all together. I'm going to be tinkering around 
> with the chart generations this week. I'll keep you updated on anything 
> that needs some testing
>
>
> On Monday, September 3, 2018 at 8:04:07 PM UTC-4, Philip Kutzenco wrote:
>
> Pat
>
> It actually may be running a bit better now, though the Belchertown web 
> page update time is behind my SteelSeries web page. And both are behind my 
> archive period. I'm not using mqtt at this point. Just want to get this 
> running. 
>
> So maybe it's now just that report generation is extremely slow. I hope 
> there is a way to resolve that without buying a new box to run weewx on.
>
> It looks like it's taking about 575 seconds to generate the files for the 
> Belchertown report. I am also still seeing notes about report thread launch 
> being aborted as one is already running. My archive period is 300 seconds.
>
>
> Best,
> Phil
>
> On Monday, September 3, 2018 at 7:46:07 PM UTC-4, Philip Kutzenco wrote:
>
> Pat,
>
> I installed WeeWX with install.py. So everything lives underneath 
> /home/weewx/.
>
> I replaced the file in /Belchertown/records folder with the one you gave 
> me. Then I re-enabled the Belchertown skin in weewx.conf, restarted WeeWX 
> and ran wee_reports. Per the log extract below, after about 8 minutes, 
> weewx hung with the database locked. WeeWX automatically restarted 2 
> minutes later.
>
> In between my efforts to run Belchertown, I've been disabling the 
> Belchertown extension by commenting out the three lines in weewx.conf 
> starting with [[Belchertown]] and then stopping and then starting weewx 
> again. I re-enable it to test the next change.
>
> I wonder if locking the file is also the cause of the complaints that 
> header.html.tmpl doesn't exist in earlier efforts. I noticed that a 
> report thread couldn't be started as one was already running. Maybe that 
> running report thread locked the file as it (or something) locked the 
> archive database?
>
> Also, it seems that typing sudo /etc/init.d/weewx stop doesn't always stop 
> weewx when Belchertown is running. Even though I return to the prompt, when 
> I looked at ps, WeeWX was still running. I ended up rebooting once and 
> Killing the PID the last time.
>
> Will the Belchertown report generation time decrease after the initial run 
> through the database? Or will it take the same time each report generation 
> cycle?
>
> Thoughts? I saw a note on disabling the charts to speed things up, but I'd 
> really hate to do that.
>
> Best,
> Phil
>
> Sep  3 19:02:38 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 14 files for report StandardReport in 19.27 seconds
> Sep  3 19:02:51 Weather-pi systemd[1]: Started Session c7 of user pi.
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: imagegenerator: Generated 24 
> images for StandardReport in 14.84 seconds
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: copygenerator: copied 14 
> files to /home/weewx/public_html
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: copygenerator: copied 6 
> files to /home/weewx/public_html/ss
> Sep  3 19:02:58 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 2 files for report SteelSeries in 4.53 seconds
> Sep  3 19:03:01 Weather-pi wee_reports[3281]: imagegenerator: Generated 11 
> images for SteelSeries in 3.43 seconds
> Sep  3 19:03:16 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 12 files for report forecast in 14.73 seconds
> Sep  3 19:03:16 Weather-pi wee_reports[3281]: copygenerator: copied 87 
> files to /home/weewx/public_html/forecast
> Sep  3 19:03:17 Weather-pi wee_reports[3281]: Belchertown Extension: 
> version 0.6
> Sep  3 19:05:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
> 19:05:00 EDT (1536015900) to database 'weewx.sdb'
> Sep  3 19:05:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
> 19:05:00 EDT (1536015900) to daily summary in 'weewx.sdb'
> Sep  3 19:05:56 Weather-pi weewx[3254]: cheetahgenerator: Generated 14 
> files for report StandardReport in 39.86 seconds
> Sep  3 19:06:03 Weather-pi weewx[3254]: imagegenerator: Generated 12 
> images for StandardReport in 7.67 seconds
> Sep  3 19:06:04 Weather-pi weewx[3254]: copygenerator: copied 14 files to 
> /h

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

[Philip Kutzenco]

Pat

It actually may be running a bit better now, though the Belchertown web 
page update time is behind my SteelSeries web page. And both are behind my 
archive period. I'm not using mqtt at this point. Just want to get this 
running. 

So maybe it's now just that report generation is extremely slow. I hope 
there is a way to resolve that without buying a new box to run weewx on.

It looks like it's taking about 575 seconds to generate the files for the 
Belchertown report. I am also still seeing notes about report thread launch 
being aborted as one is already running. My archive period is 300 seconds.


Best,
Phil

On Monday, September 3, 2018 at 7:46:07 PM UTC-4, Philip Kutzenco wrote:

> Pat,
>
> I installed WeeWX with install.py. So everything lives underneath 
> /home/weewx/.
>
> I replaced the file in /Belchertown/records folder with the one you gave 
> me. Then I re-enabled the Belchertown skin in weewx.conf, restarted WeeWX 
> and ran wee_reports. Per the log extract below, after about 8 minutes, 
> weewx hung with the database locked. WeeWX automatically restarted 2 
> minutes later.
>
> In between my efforts to run Belchertown, I've been disabling the 
> Belchertown extension by commenting out the three lines in weewx.conf 
> starting with [[Belchertown]] and then stopping and then starting weewx 
> again. I re-enable it to test the next change.
>
> I wonder if locking the file is also the cause of the complaints that 
> header.html.tmpl doesn't exist in earlier efforts. I noticed that a 
> report thread couldn't be started as one was already running. Maybe that 
> running report thread locked the file as it (or something) locked the 
> archive database?
>
> Also, it seems that typing sudo /etc/init.d/weewx stop doesn't always stop 
> weewx when Belchertown is running. Even though I return to the prompt, when 
> I looked at ps, WeeWX was still running. I ended up rebooting once and 
> Killing the PID the last time.
>
> Will the Belchertown report generation time decrease after the initial run 
> through the database? Or will it take the same time each report generation 
> cycle?
>
> Thoughts? I saw a note on disabling the charts to speed things up, but I'd 
> really hate to do that.
>
> Best,
> Phil
>
> Sep  3 19:02:38 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 14 files for report StandardReport in 19.27 seconds
> Sep  3 19:02:51 Weather-pi systemd[1]: Started Session c7 of user pi.
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: imagegenerator: Generated 24 
> images for StandardReport in 14.84 seconds
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: copygenerator: copied 14 
> files to /home/weewx/public_html
> Sep  3 19:02:53 Weather-pi wee_reports[3281]: copygenerator: copied 6 
> files to /home/weewx/public_html/ss
> Sep  3 19:02:58 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 2 files for report SteelSeries in 4.53 seconds
> Sep  3 19:03:01 Weather-pi wee_reports[3281]: imagegenerator: Generated 11 
> images for SteelSeries in 3.43 seconds
> Sep  3 19:03:16 Weather-pi wee_reports[3281]: cheetahgenerator: Generated 
> 12 files for report forecast in 14.73 seconds
> Sep  3 19:03:16 Weather-pi wee_reports[3281]: copygenerator: copied 87 
> files to /home/weewx/public_html/forecast
> Sep  3 19:03:17 Weather-pi wee_reports[3281]: Belchertown Extension: 
> version 0.6
> Sep  3 19:05:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
> 19:05:00 EDT (1536015900) to database 'weewx.sdb'
> Sep  3 19:05:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
> 19:05:00 EDT (1536015900) to daily summary in 'weewx.sdb'
> Sep  3 19:05:56 Weather-pi weewx[3254]: cheetahgenerator: Generated 14 
> files for report StandardReport in 39.86 seconds
> Sep  3 19:06:03 Weather-pi weewx[3254]: imagegenerator: Generated 12 
> images for StandardReport in 7.67 seconds
> Sep  3 19:06:04 Weather-pi weewx[3254]: copygenerator: copied 14 files to 
> /home/weewx/public_html
> Sep  3 19:06:04 Weather-pi weewx[3254]: copygenerator: copied 6 files to 
> /home/weewx/public_html/ss
> Sep  3 19:06:12 Weather-pi weewx[3254]: cheetahgenerator: Generated 2 
> files for report SteelSeries in 8.29 seconds
> Sep  3 19:06:19 Weather-pi weewx[3254]: imagegenerator: Generated 11 
> images for SteelSeries in 6.76 seconds
> Sep  3 19:06:49 Weather-pi weewx[3254]: cheetahgenerator: Generated 12 
> files for report forecast in 30.19 seconds
> Sep  3 19:06:50 Weather-pi weewx[3254]: copygenerator: copied 87 files to 
> /home/weewx/public_html/forecast
> Sep  3 19:06:50 Weather-pi weewx[3254]: Belchertown Extension: version 0.6
> Sep  3 19:09:01 Weather-pi CRON[3321]: (root) CMD (  [ -x 
> /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/syst

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

[Philip Kutzenco]

estx: CWOP: Posting not enabled.
Sep  3 19:12:30 Weather-pi weewx[3254]: restx: WOW: Posting not enabled.
Sep  3 19:12:30 Weather-pi weewx[3254]: restx: AWEKAS: Posting not enabled.
Sep  3 19:12:30 Weather-pi weewx[3254]: engine: Starting up weewx version 
3.8.2
Sep  3 19:12:30 Weather-pi weewx[3254]: engine: Clock error is -0.69 
seconds (positive is fast)
Sep  3 19:12:30 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
19:10:00 EDT (1536016200) to database 'weewx.sdb'
Sep  3 19:12:31 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
19:10:00 EDT (1536016200) to daily summary in 'weewx.sdb'
Sep  3 19:12:31 Weather-pi weewx[3254]: engine: Starting main packet loop.
Sep  3 19:12:31 Weather-pi weewx[3254]: forecast: ZambrettiThread: 
Zambretti: generated 1 forecast record
Sep  3 19:12:31 Weather-pi weewx[3254]: forecast: ZambrettiThread: 
Zambretti: saved 1 forecast records
Sep  3 19:12:31 Weather-pi weewx[3254]: forecast: ZambrettiThread: 
Zambretti: deleted forecasts prior to 1535411551
Sep  3 19:15:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
19:15:00 EDT (1536016500) to database 'weewx.sdb'
Sep  3 19:15:15 Weather-pi weewx[3254]: manager: Added record 2018-09-03 
19:15:00 EDT (1536016500) to daily summary in 'weewx.sdb'
Sep  3 19:15:22 Weather-pi weewx[3254]: cheetahgenerator: Generated 14 
files for report StandardReport in 6.59 seconds
Sep  3 19:15:25 Weather-pi weewx[3254]: imagegenerator: Generated 12 images 
for StandardReport in 3.52 seconds
Sep  3 19:15:25 Weather-pi weewx[3254]: copygenerator: copied 14 files to 
/home/weewx/public_html
Sep  3 19:15:26 Weather-pi weewx[3254]: copygenerator: copied 6 files to 
/home/weewx/public_html/ss
Sep  3 19:15:26 Weather-pi weewx[3254]: cheetahgenerator: Generated 2 files 
for report SteelSeries in 0.59 seconds
Sep  3 19:15:29 Weather-pi weewx[3254]: imagegenerator: Generated 11 images 
for SteelSeries in 3.25 seconds
Sep  3 19:15:31 Weather-pi weewx[3254]: cheetahgenerator: Generated 12 
files for report forecast in 1.56 seconds
Sep  3 19:15:31 Weather-pi weewx[3254]: copygenerator: copied 87 files to 
/home/weewx/public_html/forecast
Sep  3 19:17:01 Weather-pi CRON[3382]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
Sep  3 19:18:08 Weather-pi systemd[1]: Started Session c8 of user pi.


On Monday, September 3, 2018 at 6:03:13 PM UTC-4, Pat wrote:
>
> Thanks! It's my day off work, so in between my daughter's naps I've been 
> able to get a few things done :)
>
> The station hardware shouldn't matter since it's weewx that is doing the 
> middle-man work to make them all speak the same language in the skin files. 
>
> My archive is 261,459 records (not on a Pi) but it shouldn't matter either 
> way. The Pi might take a while longer to process those 106,000 records - 
> which is why you see 571.39 seconds. 
>
> I'm not sure why it's said your header.html.tmpl is missing. I wonder if 
> there's something else going on and that's just an effect of it.
>
> How did you install? Using apt or using setup.py? 
>
> There are 4 places .wind is used on the records page. Let's try this out. 
> Take this attached file, and copy it to the skins/Belchertown/records 
> folder overwriting the one there. Then run sudo wee_reports and see if it 
> helps?
>
>
>
> On Monday, September 3, 2018 at 5:51:29 PM UTC-4, Philip Kutzenco wrote:
>
> Pat,
>
> I tried David's fix and get the errors below. Maybe something different 
> for me? I'm using a Davis Vantage Vue.
>
> Regarding your question:
> 2. How did you install the skin? header.html.tmpl should be in 
> skins/Belchertown.  - *I used sudo wee_extension --install. I checked and 
> header.html.tmpl is, indeed in skins/Belchertown*
>
> You should know that my archive database has about 106,000 records. I 
> wouldn't think that's particularly large. Also, I am running weewx on a Pi 
> Zero W. So, it's a pretty weak system processing-wise.
>
> You're really multi-tasking today - I see lots of posts from you. You're 
> supposed to be enjoying Labor Day, not laboring on it :-).
> I owe you coffee. Will do that!
>
> Looking forward to your guidance.
>
> Best,
> Phil
>
> Sep  3 15:46:02 Weather-pi weewx[1669]: Belchertown Extension: version 0.6
> Sep  3 15:50:15 Weather-pi weewx[1669]: manager: Added record 2018-09-03 
> 15:50:00 EDT (1536004200) to database 'weewx.sdb'
> Sep  3 15:50:15 Weather-pi weewx[1669]: manager: Added record 2018-09-03 
> 15:50:00 EDT (1536004200) to daily summary in 'weewx.sdb'
> Sep  3 15:50:15 Weather-pi weewx[1669]: engine: Launch of report thread 
> aborted: existing report thread still running
> Sep  3 15:53:35 Weather-pi weewx[1669]: cheetahgenerator: Generate failed 
> with exception ''
> Sep  3 15:53:35 Weather-pi weewx[1669]: cheetahgenerator:  Ignoring 
> template /home/we

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

[Philip Kutzenco]

qsc/k6ErSz6sAgAJ> The 
> file you want to change is in skins/Belchertown/records/index.html.tmpl
>
> 2. How did you install the skin? header.html.tmpl should be in 
> skins/Belchertown. 
>
> 3. This is a sort-of known issue and no real fix at this time. Has to do 
> with archive interval, database size, and length of time it takes to 
> generate the graphs. Gary is the original author of the highcharts 
> extension, which I've extended and re-packaged with the skin. I've been 
> thinking about ways to optimize it, and I believe he is too.
>
>
>
> On Monday, September 3, 2018 at 12:17:23 PM UTC-4, Philip Kutzenco wrote:
>
> Pat,
>
> OK. I'm making progress. I put in about.inc and records.inc files.
>
> Now I am seeing a number of errors. Syslog output with debug=1 is 
> attached. 
>
> 1. First it says I'm getting errors from the Cheetahgenerator saying that 
> it is ignoring index.html.tmpl in the Belchertown records directory because 
> no column called wind exists.
> 2. Later errors say it is ignoring index.html.tmpl because 
> /home/weewx/skins/Standard/header.html.tmpl doesn't exist.
> 3. Finally report generation is exceeding my 5 minute archive time and I 
> get errors saying report thread not start because of an existing one. 
>
> Regarding 3. I remember reading something about excessive report time in 
> the thread on weewx-user, but couldn't find the particular post just now.
>
> I hope you can point me in the right direction. I did get one web page 
> generated that looked nice, but it didn't get updated.
>
> Phil
>
>
>
> On Monday, September 3, 2018 at 7:30:42 AM UTC-4, Pat wrote:
>
> Hi Phil, 
>
> Your post actually made me update the readme to be a little more clearer 
> :) 
>
> T 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/about.inc>here
>  
> are about.inc 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/about.inc>
>  
> and records.inc 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/records.inc>
>  
> samples in the GitHub. I'll update the readme with those l
>
> ...

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

[Philip Kutzenco]

Pat,

OK. I'm making progress. I put in about.inc and records.inc files.

Now I am seeing a number of errors. Syslog output with debug=1 is attached. 

1. First it says I'm getting errors from the Cheetahgenerator saying that 
it is ignoring index.html.tmpl in the Belchertown records directory because 
no column called wind exists.
2. Later errors say it is ignoring index.html.tmpl because 
/home/weewx/skins/Standard/header.html.tmpl doesn't exist.
3. Finally report generation is exceeding my 5 minute archive time and I 
get errors saying report thread not start because of an existing one. 

Regarding 3. I remember reading something about excessive report time in 
the thread on weewx-user, but couldn't find the particular post just now.

I hope you can point me in the right direction. I did get one web page 
generated that looked nice, but it didn't get updated.

Phil



On Monday, September 3, 2018 at 7:30:42 AM UTC-4, Pat wrote:
>
> Hi Phil, 
>
> Your post actually made me update the readme to be a little more clearer 
> :) 
>
> T 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/about.inc>here
>  
> are about.inc 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/about.inc>
>  
> and records.inc 
> <https://github.com/poblabs/weewx-belchertown/blob/master/skins/Belchertown/records.inc>
>  
> samples in the GitHub. I'll update the readme with those links for future 
> reference. 
>
> Sadly, the installer seems basic at this point in time where it'll 
> overwrite everything you have listed to install. So this was a work-around 
> for the time being. 
>
>
> On Sunday, September 2, 2018 at 9:47:49 PM UTC-4, Philip Kutzenco wrote:
>
> Pat,
> Ah. When I downloaded the skin from GitHub this afternoon (US Eastern 
> time), I also printed out a copy of the README.md. It's listed as being 
> created 3 days ago. That version has a section called "Customizing About 
> Page and Records Page" which says create (or edit) the about.inc and 
> records.inc files.
>
> It looks like I printed that shortly before you updated it :-). The 
> section in the new version is called "Creating About Page and Records Page" 
> and has a line that says in version 0.6+ you need to create these files if 
> you are installing the skin for the first time.
>
> I'll create those files. BTW, I know you suggest looking at 
> www.BelchertownWeather.com for examples of what they can contain. You may 
> want to post starter files on GitHub, though, for those just starting out 
> to download and use.
>
> Thanks.
> Phil
>
> On Sunday, September 2, 2018 at 7:30:21 PM UTC-4, Pat wrote:
>
> Looks like you may have skipped this step 
> <https://github.com/poblabs/weewx-belchertown#customizing-about-page-and-records-page>
> .
>
> On Sunday, September 2, 2018 at 5:05:54 PM UTC-4, Philip Kutzenco wrote:
>
> Pat,
>
> I finally got a chance to install your skin (V 0.6). And I'm seeing 
> errors: What have I done wrong?
>
> Phil
>
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:35:00 EDT (1535920500) to database 'weewx.sdb'
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:35:00 EDT (1535920500) to daily summary in 'weewx.sdb'
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:40:00 EDT (1535920800) to database 'weewx.sdb'
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
> Zambretti: generated 1 forecast record
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
> Zambretti: saved 1 forecast records
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
> Zambretti: deleted forecasts prior to 1535316382
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:40:00 EDT (1535920800) to daily summary in 'weewx.sdb'
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:45:00 EDT (1535921100) to database 'weewx.sdb'
> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
> 16:45:00 EDT
>
> ...

-- 
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.
Sep  3 10:47:18 WeeWX-pi weewx[413]: engine: Using configuration file 
/home/weewx/weewx.conf
Sep  3 10:47:18 WeeWX-pi weewx[413]: engine: Debug is 1
Sep  3 10:47:18 WeeWX-pi weewx[413]: engine: Initializing engine
Sep  3 10:47:18 WeeWX-pi weewx[413]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Sep  3 10:47:18 WeeWX-pi dh

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

[Philip Kutzenco]

Colin and Pat,
I recognize the difficulty. I think leaving the files out of the install 
package is the correct thing to do. I also think that you are correct in 
not having two versions of the installer. I guess I can think of two 
potential options.

1. If the installer is smart enough (I don't know what capabilities it 
actually has), it can check to see if the inc files exist during the 
install. If not, then it's a new install and can drop the files where they 
belong. If they don't exist, then it's an upgrade and copying the files can 
either be skipped, or dropped with a different name about.inc.example and 
records.inc.example perhaps. I'm thinking about people (like me, for 
example :-) ) who aren't competent in writing html code).

2. If the installer can't make those checks, then either publish 
rudimentary sample html text for each file right in the README.md file or 
just put links in the README.md file to external files stored in GitHub but 
not in the archive file.

By the way, I appreciate how much work Pat has put into developing this and 
the responsiveness to folks posting to this thread is just awesome.

Phil



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

[Philip Kutzenco]

Pat,
Ah. When I downloaded the skin from GitHub this afternoon (US Eastern 
time), I also printed out a copy of the README.md. It's listed as being 
created 3 days ago. That version has a section called "Customizing About 
Page and Records Page" which says create (or edit) the about.inc and 
records.inc files.

It looks like I printed that shortly before you updated it :-). The section 
in the new version is called "Creating About Page and Records Page" and has 
a line that says in version 0.6+ you need to create these files if you are 
installing the skin for the first time.

I'll create those files. BTW, I know you suggest looking at 
www.BelchertownWeather.com for examples of what they can contain. You may 
want to post starter files on GitHub, though, for those just starting out 
to download and use.

Thanks.
Phil

On Sunday, September 2, 2018 at 7:30:21 PM UTC-4, Pat wrote:
>
> Looks like you may have skipped this step 
> <https://github.com/poblabs/weewx-belchertown#customizing-about-page-and-records-page>
> .
>
> On Sunday, September 2, 2018 at 5:05:54 PM UTC-4, Philip Kutzenco wrote:
>>
>> Pat,
>>
>> I finally got a chance to install your skin (V 0.6). And I'm seeing 
>> errors: What have I done wrong?
>>
>> Phil
>>
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:35:00 EDT (1535920500) to database 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:35:00 EDT (1535920500) to daily summary in 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:40:00 EDT (1535920800) to database 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
>> Zambretti: generated 1 forecast record
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
>> Zambretti: saved 1 forecast records
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
>> Zambretti: deleted forecasts prior to 1535316382
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:40:00 EDT (1535920800) to daily summary in 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:45:00 EDT (1535921100) to database 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:45:00 EDT (1535921100) to daily summary in 'weewx.sdb'
>> Sep  2 16:46:22 WeeWX-pi weewx[24513]: engine: Starting main packet loop.
>> Sep  2 16:49:31 WeeWX-pi systemd[1]: Started Session c31 of user pi.
>> Sep  2 16:50:14 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:50:00 EDT (1535921400) to database 'weewx.sdb'
>> Sep  2 16:50:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:50:00 EDT (1535921400) to daily summary in 'weewx.sdb'
>> Sep  2 16:50:37 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 14 
>> files for report StandardReport in 22.19 seconds
>> Sep  2 16:50:41 WeeWX-pi weewx[24513]: imagegenerator: Generated 12 
>> images for StandardReport in 4.05 seconds
>> Sep  2 16:50:41 WeeWX-pi weewx[24513]: copygenerator: copied 14 files to 
>> /home/weewx/public_html
>> Sep  2 16:50:42 WeeWX-pi weewx[24513]: copygenerator: copied 6 files to 
>> /home/weewx/public_html/ss
>> Sep  2 16:50:46 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 2 
>> files for report SteelSeries in 4.88 seconds
>> Sep  2 16:50:50 WeeWX-pi weewx[24513]: imagegenerator: Generated 11 
>> images for SteelSeries in 3.94 seconds
>> Sep  2 16:51:07 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 12 
>> files for report forecast in 16.67 seconds
>> Sep  2 16:51:07 WeeWX-pi weewx[24513]: copygenerator: copied 87 files to 
>> /home/weewx/public_html/forecast
>> Sep  2 16:51:08 WeeWX-pi weewx[24513]: Belchertown Extension: version 0.6
>> Sep  2 16:55:16 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:55:00 EDT (1535921700) to database 'weewx.sdb'
>> Sep  2 16:55:16 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
>> 16:55:00 EDT (1535921700) to daily summary in 'weewx.sdb'
>> Sep  2 16:55:16 WeeWX-pi weewx[24513]: engine: Launch of report thread 
>> aborted: existing report thread still running
>> Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator: Generate failed 
>> with exception ''
>> Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator:  Ignoring 
>> template /home/weewx/skins/Belchertown/about/index.html.tmpl
>> Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator:  Reason: 
>> [Errno 2] No such file or directory: 
>> '/home/weewx/skins/Belchertow

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

[Philip Kutzenco]

And here's some further output:

Sep  2 17:00:11 WeeWX-pi weewx[24513]: cheetahgenerator: Generate failed 
with exception ''
Sep  2 17:00:11 WeeWX-pi weewx[24513]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Belchertown/records/index.html.tmpl
Sep  2 17:00:11 WeeWX-pi weewx[24513]: cheetahgenerator:  Reason: 
[Errno 2] No such file or directory: 
'/home/weewx/skins/Belchertown/records.inc'
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   Traceback (most recent call 
last):
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 330, in generate
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   print >> _file, 
compiled_template
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   rc = getattr(self, 
mainMethName)()
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"_home_weewx_skins_Belchertown_records_index_html_tmpl.py", line 863, in 
respond
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1597, in 
_handleCheetahInclude
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   nestedTemplateClass = 
compiler.compile(source=source, file=file)
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 706, in compile
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   fileHash += 
str(os.path.getmtime(file))
Sep  2 17:00:11 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/genericpath.py", line 62, in getmtime
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   return 
os.stat(filename).st_mtime
Sep  2 17:00:11 WeeWX-pi weewx[24513]:   OSError: [Errno 2] No such 
file or directory: '/home/weewx/skins/Belchertown/records.inc'
Sep  2 17:00:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
17:00:00 EDT (1535922000) to database 'weewx.sdb'
Sep  2 17:00:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
17:00:00 EDT (1535922000) to daily summary in 'weewx.sdb'
Sep  2 17:00:15 WeeWX-pi weewx[24513]: engine: Previous report thread has 
been running 600.651339054 seconds.  Launching report thread anyway.
Sep  2 17:00:31 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 14 files 
for report StandardReport in 15.20 seconds
Sep  2 17:01:04 WeeWX-pi weewx[24513]: imagegenerator: Generated 24 images 
for StandardReport in 33.40 seconds
Sep  2 17:01:04 WeeWX-pi weewx[24513]: copygenerator: copied 0 files to 
/home/weewx/public_html
Sep  2 17:01:05 WeeWX-pi weewx[24513]: copygenerator: copied 0 files to 
/home/weewx/public_html/ss
Sep  2 17:01:06 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 2 files 
for report SteelSeries in 1.33 seconds
Sep  2 17:01:14 WeeWX-pi weewx[24513]: imagegenerator: Generated 11 images 
for SteelSeries in 7.65 seconds
Sep  2 17:01:17 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 12 files 
for report forecast in 3.51 seconds
Sep  2 17:01:17 WeeWX-pi weewx[24513]: copygenerator: copied 0 files to 
/home/weewx/public_html/forecast
Sep  2 17:04:40 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 14 files 
for report Belchertown in 812.75 seconds
Sep  2 17:04:41 WeeWX-pi weewx[24513]: copygenerator: copied 22 files to 
/home/weewx/public_html/belchertown
Sep  2 17:05:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
17:05:00 EDT (1535922300) to database 'weewx.sdb'
Sep  2 17:05:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
17:05:00 EDT (1535922300) to daily summary in 'weewx.sdb'
Sep  2 17:05:15 WeeWX-pi weewx[24513]: engine: Launch of report thread 
aborted: existing report thread still running

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

[Philip Kutzenco]

Pat,

I finally got a chance to install your skin (V 0.6). And I'm seeing errors: 
What have I done wrong?

Phil

Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:35:00 EDT (1535920500) to database 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:35:00 EDT (1535920500) to daily summary in 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:40:00 EDT (1535920800) to database 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
Zambretti: generated 1 forecast record
Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
Zambretti: saved 1 forecast records
Sep  2 16:46:22 WeeWX-pi weewx[24513]: forecast: ZambrettiThread: 
Zambretti: deleted forecasts prior to 1535316382
Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:40:00 EDT (1535920800) to daily summary in 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:45:00 EDT (1535921100) to database 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:45:00 EDT (1535921100) to daily summary in 'weewx.sdb'
Sep  2 16:46:22 WeeWX-pi weewx[24513]: engine: Starting main packet loop.
Sep  2 16:49:31 WeeWX-pi systemd[1]: Started Session c31 of user pi.
Sep  2 16:50:14 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:50:00 EDT (1535921400) to database 'weewx.sdb'
Sep  2 16:50:15 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:50:00 EDT (1535921400) to daily summary in 'weewx.sdb'
Sep  2 16:50:37 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 14 files 
for report StandardReport in 22.19 seconds
Sep  2 16:50:41 WeeWX-pi weewx[24513]: imagegenerator: Generated 12 images 
for StandardReport in 4.05 seconds
Sep  2 16:50:41 WeeWX-pi weewx[24513]: copygenerator: copied 14 files to 
/home/weewx/public_html
Sep  2 16:50:42 WeeWX-pi weewx[24513]: copygenerator: copied 6 files to 
/home/weewx/public_html/ss
Sep  2 16:50:46 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 2 files 
for report SteelSeries in 4.88 seconds
Sep  2 16:50:50 WeeWX-pi weewx[24513]: imagegenerator: Generated 11 images 
for SteelSeries in 3.94 seconds
Sep  2 16:51:07 WeeWX-pi weewx[24513]: cheetahgenerator: Generated 12 files 
for report forecast in 16.67 seconds
Sep  2 16:51:07 WeeWX-pi weewx[24513]: copygenerator: copied 87 files to 
/home/weewx/public_html/forecast
Sep  2 16:51:08 WeeWX-pi weewx[24513]: Belchertown Extension: version 0.6
Sep  2 16:55:16 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:55:00 EDT (1535921700) to database 'weewx.sdb'
Sep  2 16:55:16 WeeWX-pi weewx[24513]: manager: Added record 2018-09-02 
16:55:00 EDT (1535921700) to daily summary in 'weewx.sdb'
Sep  2 16:55:16 WeeWX-pi weewx[24513]: engine: Launch of report thread 
aborted: existing report thread still running
Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator: Generate failed 
with exception ''
Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator:  Ignoring 
template /home/weewx/skins/Belchertown/about/index.html.tmpl
Sep  2 16:58:01 WeeWX-pi weewx[24513]: cheetahgenerator:  Reason: 
[Errno 2] No such file or directory: 
'/home/weewx/skins/Belchertown/about.inc'
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   Traceback (most recent call 
last):
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"/home/weewx/bin/weewx/cheetahgenerator.py", line 330, in generate
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   print >> _file, 
compiled_template
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1005, in 
__str__
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   rc = getattr(self, 
mainMethName)()
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"_home_weewx_skins_Belchertown_about_index_html_tmpl.py", line 181, in 
respond
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 1597, in 
_handleCheetahInclude
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   nestedTemplateClass = 
compiler.compile(source=source, file=file)
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/dist-packages/Cheetah/Template.py", line 706, in compile
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   fileHash += 
str(os.path.getmtime(file))
Sep  2 16:58:01 WeeWX-pi weewx[24513]: File 
"/usr/lib/python2.7/genericpath.py", line 62, in getmtime
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   return 
os.stat(filename).st_mtime
Sep  2 16:58:01 WeeWX-pi weewx[24513]:   OSError: [Errno 2] No such 
file or directory: '/home/weewx/skins/Belchertown/about.inc'


On Thursday, August 30, 2018 at 2:15:10 PM UTC-4, 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 the Google Groups 

[weewx-user] Re: Need help with forecasts in SteelSeries extension - apologies in advance

[Philip Kutzenco]

Gary,
Thanks so much! Bitten by a typo - sloppy on my part. It's all better now!

If I might ask one more question: Right now, I only want forecast info in 
the SteelSeries generated webpage. That will likely change, but if I have 
no need for the forecast output in public_html/forecast (or, for that 
matter output from any specific other skin or extension) how do I stop 
that? If it's a skin, I should be able to uninstall it with the 
wee_extension utility. If it is an extension like forecast, I imagine that 
uninstalling it would stop the Zambretti forecast and prevent me using it 
in SteelSeries. Do I just let WeeWX keep copying files to 
public_html/forecast? If there is something on this in the User Guide or 
Wiki, just point me there.
Thanks once again.
Phil

On Sunday, September 2, 2018 at 8:02:47 AM UTC-4, gjr80 wrote:...
>
> Phil,
>
> In skin.conf change 'search_list_extension =' to 'search_list_extensions 
> ='. Save skin.conf and on the next report cycle it should work fine.
>
> 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: Need help with forecasts in SteelSeries extension - apologies in advance

[Philip Kutzenco]

Gary,
I've attached my skin.conf for the SteelSeries skin.

I notice that there is a file called Zambretti.html in public_html/ss that 
has a message in it that "The forecast search list extension is not 
installed". However, the timestamp on that is hours earlier than the all of 
the other files which are currently being populated there. I think that 
Zambretti.html file was left over from earlier, when I first installed the 
forecast extension, but prior to my adding the search list extension line 
to skin.conf for ss. So, I probably can just delete it.
Phil


On Sunday, September 2, 2018 at 2:11:44 AM UTC-4, gjr80 wrote:
>
> Phil,
>
> Thanks, it appears all is fine but the forecast extension extension does 
> not appear to be being called by the SteelSeries skin (we should be 
> user.forecast.ForecastVariables appearing in the search list log entry for 
> the SteelSeries skin). Could you post a copy of your SteelSeries skin.conf 
> please.
>
> 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.
# $Id: skin.conf 1210 2015-01-01 17:01:08Z mwall $
# configuration file for the steel series gauges skin for weewx
#   created by Matthew Wall
#   based on work by Mark Crossley and others
#
# This skin can be copied, modified, and distributed as long as this notice
# is included in any derivative work.

[CopyGenerator]
copy_once = css/*.css, scripts/*.js

[CheetahGenerator]
search_list_extension = user.forecast.ForecastVariables
encoding = html_entities
[[ToDate]]
[[[index]]]
template = index.html.tmpl
[[[data]]]
template = gauge-data.txt.tmpl

[ImageGenerator]
image_width = 720
image_height = 196
image_background_color = 0xff
chart_background_color = 0xff
chart_gridline_color = 0xeaeaea

top_label_font_path = 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-Bold.ttf
top_label_font_size = 10

unit_label_font_path = 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
unit_label_font_size = 10
unit_label_font_color = 0xaa

bottom_label_font_path = 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
bottom_label_font_size = 10
bottom_label_font_color = 0xaa

axis_label_font_path = 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
axis_label_font_size = 10
axis_label_font_color = 0xaa

rose_label = N
rose_label_font_path = 
/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
rose_label_font_size  = 8
rose_label_font_color = 0x88
rose_color = 0xaa

chart_line_colors = 0x1e69d2, 0x8b008b, 0xa09e5f, 0x8080f0
chart_fill_colors = 0x7ec9f2, 0xeb00eb, 0xf0febf, 0xe0e0f0

line_type = 'solid'
marker_size = 2
marker_type ='none'
plot_type = line
aggregate_type = none
width = 1
yscale = None, None, None
vector_rotate = 90
line_gap_fraction = 0.01
bar_gap_fraction = 0.2
daynight_day_color = 0xff
daynight_night_color = 0xf8f0f0
daynight_edge_color = 0xafefef
bottom_label_format = %x %X
time_length = 9

[[images]]
x_label_format = %H:%M
show_daynight = true
[[[daybarometer]]]
barometer
[[[dayrain]]]
yscale = None, None, 0.02
plot_type = bar
rain
aggregate_type = sum
aggregate_interval = 3600
label = Rain (hourly total)
[[[dayrainrate]]]
rainrate
[[[daywind]]]
windSpeed
windGust
[[[daywinddir]]]
line_type = None
marker_type = 'box'
marker_size = 2
yscale = 0.0, 360.0, 45.0
windDir
[[[daywindvec]]]
windvec
plot_type = vector
windgustvec
plot_type = vector
aggregate_type = max
aggregate_interval = 3600
[[[dayouttemphum]]]
windchill
heatindex
dewpoint
outTemp
[[[dayinouttemp]]]
outTemp
inTemp
[[[dayinouthum]]]
yscale = 0, 100, 10
outHumidity
inHumidity
[[[dayradiation]]]
radiation
[[[dayuv]]]
UV

[Generators]
generator_list = weewx.reportengine.CopyGenerator, 
weewx.cheetahgenerator.CheetahGenerator, weewx.imagegenerator.ImageGenerator

[weewx-user] Re: Need help with forecasts in SteelSeries extension - apologies in advance

[Philip Kutzenco]

Gary,

Here's the log file. FWIW, in gauges.js, I set the pageUpdateLimit to 0 (so 
the web page wouldn't time out) and the realtimeInterval to 300 - matching 
the archive interval of 5 minutes (so the viewer will get an indication of 
when the web page will update). I've waiting more than long enough for 
several web page updates, though.

Thanks for the quick reply and offer to help.

Best,
Phil

On Saturday, September 1, 2018 at 8:50:40 PM UTC-4, gjr80 wrote:
>
>
> On Sunday, 2 September 2018 10:12:02 UTC+10, Philip Kutzenco wrote:
>>
>>
>> The most pertinent info I found was to add the line:
>> search_list_extensions = user.forecast.ForecastVariables
>> to the  [Cheetah Generator] section of skin.conf for SteelSeries.
>>
>>
> Hi, that should do the trick. Just to be sure can you set debug=1 in 
> weewx.conf, restart WeeWX and then post a log extract from startup 
> covering a couple of report cycles.
>
> 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.
Sep  1 21:23:00 WeeWX-pi systemd[1]: Starting LSB: weewx weather system...
Sep  1 21:23:01 WeeWX-pi weewx[17821]: engine: Initializing weewx version 3.8.2
Sep  1 21:23:01 WeeWX-pi weewx[17821]: engine: Using Python 2.7.13 (default, 
Nov 24 2017, 17:33:09) #012[GCC 6.3.0 20170516]
Sep  1 21:23:01 WeeWX-pi weewx[17821]: engine: Platform 
Linux-4.14.62+-armv6l-with-debian-9.4
Sep  1 21:23:01 WeeWX-pi weewx[17821]: engine: Locale is 'en_US.UTF-8'
Sep  1 21:23:01 WeeWX-pi weewx[17821]: engine: pid file is /var/run/weewx.pid
Sep  1 21:23:01 WeeWX-pi weewx[17810]: Starting weewx weather system: weewx.
Sep  1 21:23:01 WeeWX-pi systemd[1]: Started LSB: weewx weather system.
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Using configuration file 
/home/weewx/weewx.conf
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Debug is 1
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Initializing engine
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading station type Vantage 
(weewx.drivers.vantage)
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: Driver version is 3.0.11
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: Opened up serial port 
/dev/ttyUSB0; baud 19200; timeout 4.00
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: Gentle wake up of console 
successful
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: Hardware type is 17
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: ISS ID is 1
Sep  1 21:23:02 WeeWX-pi weewx[17825]: vantage: Hardware name: Vantage Vue
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.engine.StdTimeSynch
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.engine.StdConvert
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: StdConvert target unit is 0x1
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Finished loading service 
weewx.engine.StdConvert
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.engine.StdCalibrate
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Finished loading service 
weewx.engine.StdCalibrate
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.engine.StdQC
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Finished loading service 
weewx.engine.StdQC
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Sep  1 21:23:02 WeeWX-pi weewx[17825]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, windchill=prefer_hardware, 
dewpoint=prefer_hardware, appTemp=prefer_hardware, rainRate=prefer_hardware, 
windrun=prefer_hardware, heatindex=prefer_hardware, 
maxSolarRad=prefer_hardware, humidex=prefer_hardware, pressure=prefer_hardware, 
inDewpoint=prefer_hardware, ET=prefer_hardware, altimeter=prefer_hardware, 
cloudbase=prefer_hardware
Sep  1 21:23:02 WeeWX-pi weewx[17825]: wxcalculate: The following algorithms 
will be used for calculations: altimeter=aaNOAA, maxSolarRad=RS
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Finished loading service 
weewx.wxservices.StdWXCalculate
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Loading service 
weewx.engine.StdArchive
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Archive will use data binding 
wx_binding
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Record generation will be 
attempted in 'hardware'
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Using archive interval of 300 
seconds (specified by hardware)
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Use LOOP data in hi/low 
calculations: 1
Sep  1 21:23:02 WeeWX-pi weewx[17825]: manager: Daily summary version is 2.0
Sep  1 21:23:02 WeeWX-pi weewx[17825]: engine: Using bin

[weewx-user] Need help with forecasts in SteelSeries extension - apologies in advance

[Philip Kutzenco]

I am a pretty new WeeWX user (installed with setup.py and running on a 
Raspberry Pi for a month or so). I've been mostly successful - up to now.

WeeWX is running well (V3.8.2) on my Pi Zero W with a Real Time Clock and 
nginx as a web server. I'm collecting data from a Davis Vantage Vue 
station. I installed the SteelSeries extension and that is working well. I 
then installed the forecast extension with an expectation to get the 
Zambretti forecast to use in the scrolling area of the SS. The forecast 
extension successfully outputs "sample" forecast html files in the 
public_html/forecast directory including the Zambretti forecast. I see no 
errors in the log - Zambretti forecasts are generated.

However, even after spending a significant amount of time reviewing Wiki 
and WeeWX-user group info, I can't get the forecast to work with SS. No 
matter what I do, the scrolling area still says "forecast is unavailable".

The most pertinent info I found was to add the line:
search_list_extensions = user.forecast.ForecastVariables
to the  [Cheetah Generator] section of skin.conf for SteelSeries.

That didn't fix it for me. Am I supposed to add a [[[forecast]]] template 
under [[ToDate]]? If so, what should that be?

Anyway, I apologize. I'm sure I should have quickly found out how to do 
this, but I haven't been successful. So, please excuse this question - What 
do I need to do to get this working?

FWIW, after this, I plan to install the Realtime extension. Next I will 
work on MQTT and plan to move over to the Belchertown extension that Pat 
has developed and which he is actively augmenting. Hosted publication of my 
page will follow!

Apologies and thanks in advance.

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

[Philip Kutzenco]

Like Colin, I registered my DarkSky account and am reading up on MQTT. I 
notice though, that on your https:/belchertownweather.com site, the icons 
you have for sunrise and for sundown show next to readouts for the same 
time (8:02 PM). AccuWeather.com lists sunrise as 6:06 AM and sunset as 7:37 
PM for Belchertown, MA. Am I misreading the meaning of those icons?

On Tuesday, August 21, 2018 at 2:45:13 PM UTC-4, Pat wrote:
>
> The Belchertown skin for weewx is now available. This skin is modeled 
> after https://belchertownweather.com 
>
> The skin features
>
>- Real time streaming updates on the front page without needing to 
>reload the site (weewx-mqtt extension required)
>- Forecast data updated every hour without needing to reload (a free 
>DarkSky API key required)
>- Information on your closest Earthquake updated automatically every 3 
>hours
>- Weather station observation graphs which update without needing to 
>reload
>- Weather records for the current year, and for all time
>- A mobile and iPad ready display. You could use an iPad as a "2nd 
>console". 
>
> There are dozens of options to configure within the skin. Please view the 
> readme on GitHub  for a 
> detailed explanation. 
>
> The GitHub page: https://github.com/poblabs/weewx-belchertown
>
> Direct download of v0.1: 
> https://github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> Quick install:
>
> wget https://
> github.com/poblabs/weewx-belchertown/archive/weewx-belchertown-0.1.tar.gz
>
> sudo wee_extension --install weewx-belchertown-0.1.tar.gz
>
> Configure weewx.conf with your options
>
> Restart weewx
>
> Out of the box, it is a very basic theme. Make sure to check out the readme 
> for all options available !
>
>
> This is my first skin, and I've done all I could to test it out in various 
> environments to iron out any initial bugs. If you do find something that's 
> a little off, or room for improvement, please let me know!
>
>

-- 
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: Want to update Raspian on my WeeWX Pi - advice?

[Philip Kutzenco]

Vince,

Thanks for your reply. I posted here as I recall a number of posts that 
discuss problems with certain versions of Python. My purpose was to ensure 
that WeeWX  wouldn't break after upgrading Raspbian. Also, I read that 
operating system upgrades undid some RTC setups (I know changes were made 
to the latest version of WeeWX to make a RTC less critical, but accurate 
time is important to WeeWX). Additionally, of course, I want to be sure 
that my system would continue without loss of my existing WeeWX history. 
Those goals make my original post legitimate for a WeeWX users group.

Thanks for letting me know what to back up and drop onto a new install to 
make my existing WeeWX configuration and historic data is preserved. 

Thanks again for your helpful reply.

On Sunday, August 19, 2018 at 12:59:38 PM UTC-4, vince wrote:
>
> On Sunday, August 19, 2018 at 5:50:43 AM UTC-7, Philip Kutzenco wrote:
>>
>> I have been successfully running WeeWX (currently V3.8.2) on a Raspberry 
>> Pi Zero W with an RTC for some time. The Pi is running Raspian Stretch (and 
>> using NGINX as a web server). I would like to update Raspian by running 
>> sudo apt-get update and either sudo apt-get upgrade or sudo apt-get 
>> dist-upgrade. I have a couple of questions:
>>
>>
> This really isn't the forum for questions like "how do I upgrade operating 
> system XYZ without losing my previous changes and data".
>
> That said, since there are so many pi users here, let me take a quick 
> crack at it
>
>- don't do a dist-upgrade.  It takes for-ev-er and beats the heck out 
>of your SD card
>- instead, do a clean install to a new card (if you have one) and 
>reinstall cleanly, restoring any data or changes you want to keep
>- if you don't have a backup SD card, it's ok to reimage the same one 
>if you've saved any data and changes you want to restore elsewhere
>- personally, I like "Etcher" for software to image the SD card.  100% 
>reliable for me on a Macbook Air
>
> Re: what and how to back up:
>
>- I don't back up my SD cards, I back up the stuff 'on' those cards 
>that I care about
>- for a wifi pi - remember to back up your wpa_supplicant.conf file so 
>you can get back on the air for wifi
>
> Typically for a weewx system with RTC you'd want to back up:
>
>- the archive database (to keep your old data)
>- probably the public_html tree (so weewx doesn't have to recreate the 
>NOAA archives)
>- almost certainly weewx.conf (either to copy back, or as a reference 
>for hand-editing a new one)
>- whatever you edit so the RTC works
>- whatever else you changed that you didn't mention
>
> Short answer is:
>
>- image a SD card
>- mount the /boot it creates, touch a 'ssh' file and copy your 
>wpa_supplicant.conf there
>- boot it up, install nginx and weewx
>- restore your data and any other stuff you need to save
>- always do that one last reboot at the end so you know it will come 
>up ok
>
> Should be 15 minutes max to do.
>
>

-- 
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] Want to update Raspian on my WeeWX Pi - advice?

[Philip Kutzenco]

I have been successfully running WeeWX (currently V3.8.2) on a Raspberry Pi 
Zero W with an RTC for some time. The Pi is running Raspian Stretch (and 
using NGINX as a web server). I would like to update Raspian by running 
sudo apt-get update and either sudo apt-get upgrade or sudo apt-get 
dist-upgrade. I have a couple of questions:

I assume I should:
1.Shut down the Pi
2. Back up my SD card on another PC (in case I really mess things up)
3. Restart the PI
4. Stop WeeWX
5. Run the commands for Raspian update/upgrade
6. Start WeeWX

Does this make sense?
Does anyone have guidance for apt-get upgrade vs apt-get dist-upgrade for 
my case?
Will either upgrade or dist-upgrade put back the fake-hwclock, which I 
purged when adding my RTC?
Will either upgrade or dist-upgrade mess up the udev rule I added to 
/etc/udev (KERNEL=="rtc0", RUN+="/sbin/hwclock --rtc=$root/$name --hctosys")to 
have the RTC update the time on boot? 
Anything else I should do or be aware of - any other advice or suggestions?

Thanks in advance.

Phil

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

[Philip Kutzenco]

Pat,

Sign me up for the beta of your skin! Your site is terrific.

Phil

On Friday, August 10, 2018 at 8:42:55 PM UTC-4, Pat wrote:
>
> What kind of skin are you looking for? 
>
> For what it's worth, I'm working on porting my site 
>  to a skin. It has a couple years of 
> custom code I've created that I need to port over to weewx skins. Hope to 
> have it in a beta form soon. 
>
> On Wednesday, August 8, 2018 at 3:04:27 AM UTC-4, Bengt Carlsson wrote:
>>
>> Yes, but cant find any similar.
>>
>> Bengt C
>>
>>  
>>
>> *Från:* weewx...@googlegroups.com  *För *Andrew 
>> Milner
>> *Skickat:* den 8 augusti 2018 08:44
>> *Till:* weewx-user 
>> *Ämne:* [weewx-user] Re: Skins
>>
>>  
>>
>> Have you looked in the wiki??
>>
>>  
>>
>>  
>>
>>
>> On Wednesday, 8 August 2018 09:05:19 UTC+3, John Clark wrote:
>>
>> Is there a "repository" of various "Standard" skins that may be 
>> downloaded? Or a "how-to" manual? So far, understanding "skin theory" has 
>> been problematic. I have seen a few I love, but have no idea on how to 
>> reproduce them. Need to "get my foot in the door" so to speak.
>>
>> -- 
>> *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+...@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: Davis driver: weewx & sending data to Davis weatherlink.com

[Philip Kutzenco]

This has been true for me. AFAIK it is an issue with pretty much every 
program that gets data from the Davis IP Data Logger other than Davis' own 
Weatherlink software. Cumulus, for instance, has a setting that releases 
the driver periodically to allow the IP Data Logger to upload. In the 
Cumulus MX version, though, using that setting doesn't work reliably in my 
experience - usually crashing Cumulus MX periodically.

There is a WeeWX extension (wlink) that connects to weatherlink.com and 
downloads data from the website, rather than from your onsite data logger. 
My experience with it is that it only provides "archive" updates (every 30 
minutes) rather than LOOP data (which is every minute for me). I ended up 
purchasing a second console and a USB data logger which I connected to a 
Raspberry Pi Zero W running WeeWX. My first console has a Davis IP Data 
Logger and updates weatherlink.com.

On Friday, August 10, 2018 at 7:33:31 AM UTC-4, Premle wrote:
>
> Hi,
>
>  I noticed weewx keeps the IP data logger from sending data to 
> weatherllink.com
>
> On 
> https://www.davisinstruments.com/resource/how-do-i-communicate-directly-with-my-weatherlinkip-data-logger/
>  
> I found the following info:
>
> Please note that in order to allow the IP logger to send to 
>> WeatherLink.com, you must release the TCP socket for about 5 seconds once 
>> per minute for the current conditions (loop packet) to be sent and about 60 
>> seconds once per hour for the archive records to be sent up.
>>
>
> Could it be the current davis driver does not take this suggestion into 
> account? At least there is no configuration option to trigger such 
> behaviour.
> The alternative would probably be weewx forwarding the data to 
> weatherlink.com
>
> Did anyone else run into this issue?
>
>
>
>
>
>
>

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