[weewx-user] Re: NOAA Reports Belchertown Skin

2019-02-02 Thread gjr80
Ok, a few things. You appear to be generating archive records and saving them 
to database. Your log indicates the Standard skin is generating 13 files each 
report cycle, an unmodified Standard skin should be producing at least 15 files 
each report cycle. Have you modified the Standard skin at all?

Secondly, the level of detail in the log extracts indicates that WeeWX is not 
running with debug=1, it may be set in weewx.conf but have you restarted WeeWX 
since making the change? Either way could you confirm that debug=1 is in 
weewx.conf and then restart WeeWX. Could you again let WeeWX run for 2-3 
archive periods and the post the log from the restart onwards. I would like to 
see the startup sequence, it contains a lot of config info.

Finally, whilst WeeWX is saving archive records we don't know what if any data 
is in each archive record. You might want to run weeWX directly 
(http://weewx.com/docs/usersguide.htm#Running_directly), again let it run for a 
few archive periods. This will display loop packets and archive records to the 
console (screen) and is useful for seeing what data is in each. Could you 
please post the output seen on the console. 

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: NOAA Reports Belchertown Skin

2019-02-02 Thread torrin
Here is a full run from journalctl -l:

Feb 02 23:55:31 localhost weewx[482]: manager: Added record 2019-02-02 
23:55:00 CST (1549173300) to database 'weewx.sdb'
Feb 02 23:55:31 localhost weewx[482]: manager: Added record 2019-02-02 
23:55:00 CST (1549173300) to daily summary in 'weewx.sdb'
Feb 02 23:55:32 localhost weewx[482]: reportengine: Running reports for 
latest time in the database.
Feb 02 23:55:32 localhost weewx[482]: reportengine: Running report 
StandardReport
Feb 02 23:55:32 localhost weewx[482]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report StandardReport
Feb 02 23:55:32 localhost weewx[482]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown.getData']
Feb 02 23:55:32 localhost weewx[482]: manager: Daily summary version is 2.0
Feb 02 23:55:32 localhost weewx[482]: Belchertown Extension: New forecast 
file downloaded to /var/www/html/weewx/json/darksky_forecast.json
Feb 02 23:55:35 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:55:35 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report StandardReport in 3.16 seconds
Feb 02 23:55:35 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb 02 23:55:35 localhost weewx[482]: reportengine: Running report 
Highcharts_Belchertown
Feb 02 23:55:35 localhost weewx[482]: reportengine: Found configuration 
file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for report 
Highcharts_Belchertown
Feb 02 23:55:35 localhost weewx[482]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']
Feb 02 23:55:35 localhost weewx[482]: manager: Daily summary version is 2.0
Feb 02 23:55:38 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:55:41 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:55:44 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:55:47 localhost weewx[482]: sdr: MainThread: lines=['{"time" : 
"2019-02-03 05:55:44", "model" : "Fine Offset WH65B", "id" : 41, 
"temperature_C" : 11.500, "humidity" : 58, "wind_dir_deg" : 140, 
"wind_speed_ms" : 0.000, "gust_speed_ms" : 0.000, "rainfall_mm" : 134.112, 
"uv" : 1, "uvi" : 0, "light_lux" : 0.000, "battery" : "OK", "mic" : 
"CRC"}\n']
Feb 02 23:55:47 localhost weewx[482]: sdr: MainThread: 
packet={'outTempBatteryStatus': 0, 'outHumidity': 58.0, 'UV': 0.0, 
'radiation': 0.0, 'dateTime': 1549173344, 'windDir': 140.0, 'outTemp': 
11.5, 'windSpeed': 0.0, 'windGust': 0.0, 'rain_total': 134.112, 'usUnits': 
17}
Feb 02 23:55:49 localhost weewx[482]: cheetahgenerator: Generated 4 files 
for report Highcharts_Belchertown in 14.01 seconds
Feb 02 23:55:49 localhost weewx[482]: copygenerator: copied 0 files to 
/var/www/html/weewx
Feb 02 23:55:49 localhost weewx[482]: reportengine: Running report 
Belchertown
Feb 02 23:55:49 localhost weewx[482]: reportengine: Found configuration 
file /etc/weewx/skins/Belchertown/skin.conf for report Belchertown
Feb 02 23:55:49 localhost weewx[482]: cheetahgenerator: using search list 
['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown.getData']
Feb 02 23:55:49 localhost weewx[482]: manager: Daily summary version is 2.0
Feb 02 23:55:50 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:55:52 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report Belchertown in 2.63 seconds
Feb 02 23:55:52 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb 02 23:55:52 localhost weewx[482]: reportengine: Running report FTP
Feb 02 23:55:52 localhost weewx[482]: reportengine: Found configuration 
file /etc/weewx/skins/Ftp/skin.conf for report FTP
Feb 02 23:55:52 localhost weewx[482]: ftpgenerator: FTP upload not 
requested. Skipped.
Feb 02 23:55:52 localhost weewx[482]: reportengine: Running report RSYNC
Feb 02 23:55:52 localhost weewx[482]: reportengine: Found configuration 
file /etc/weewx/skins/Rsync/skin.conf for report RSYNC
Feb 02 23:55:52 localhost weewx[482]: rsyncgenerator: rsync upload not 
requested. Skipped.
~  


On Saturday, February 2, 2019 at 11:54:52 PM UTC-6, tor...@torrin.org wrote:
>
> I am happy to post the logs:
>
> Feb  2 23:30:27 localhost weewx[482]: 

[weewx-user] Re: NOAA Reports Belchertown Skin

2019-02-02 Thread torrin
I am happy to post the logs:

Feb  2 23:30:27 localhost weewx[482]: manager: Added record 2019-02-02 
23:30:00 CST (1549171800) to database 'weewx.sdb'
Feb  2 23:30:27 localhost weewx[482]: manager: Added record 2019-02-02 
23:30:00 CST (1549171800) to daily summary in 'weewx.sdb'
Feb  2 23:30:30 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report StandardReport in 2.56 seconds
Feb  2 23:30:30 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb  2 23:30:44 localhost weewx[482]: cheetahgenerator: Generated 4 files 
for report Highcharts_Belchertown in 14.08 seconds
Feb  2 23:30:44 localhost weewx[482]: copygenerator: copied 0 files to 
/var/www/html/weewx
Feb  2 23:30:47 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report Belchertown in 2.63 seconds
Feb  2 23:30:47 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb  2 23:35:31 localhost weewx[482]: manager: Added record 2019-02-02 
23:35:00 CST (1549172100) to database 'weewx.sdb'
Feb  2 23:35:31 localhost weewx[482]: manager: Added record 2019-02-02 
23:35:00 CST (1549172100) to daily summary in 'weewx.sdb'
Feb  2 23:35:34 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report StandardReport in 2.56 seconds
Feb  2 23:35:34 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb  2 23:35:48 localhost weewx[482]: cheetahgenerator: Generated 4 files 
for report Highcharts_Belchertown in 14.21 seconds
Feb  2 23:35:48 localhost weewx[482]: copygenerator: copied 0 files to 
/var/www/html/weewx
Feb  2 23:35:51 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report Belchertown in 2.58 seconds
Feb  2 23:35:51 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb  2 23:40:19 localhost weewx[482]: manager: Added record 2019-02-02 
23:40:00 CST (1549172400) to database 'weewx.sdb'
Feb  2 23:40:19 localhost weewx[482]: manager: Added record 2019-02-02 
23:40:00 CST (1549172400) to daily summary in 'weewx.sdb'
Feb  2 23:40:22 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report StandardReport in 2.57 seconds
Feb  2 23:40:22 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx
Feb  2 23:40:36 localhost weewx[482]: cheetahgenerator: Generated 4 files 
for report Highcharts_Belchertown in 14.06 seconds
Feb  2 23:40:36 localhost weewx[482]: copygenerator: copied 0 files to 
/var/www/html/weewx
Feb  2 23:40:39 localhost weewx[482]: cheetahgenerator: Generated 13 files 
for report Belchertown in 2.61 seconds
Feb  2 23:40:39 localhost weewx[482]: copygenerator: copied 1 files to 
/var/www/html/weewx

Here are the log entries for running wee_reports stand alone:
/var/log/messages:
Feb  2 23:45:58 localhost wee_reports[776]: cheetahgenerator: Generated 13 
files for report StandardReport in 18.46 seconds
Feb  2 23:45:58 localhost wee_reports[776]: copygenerator: copied 22 files 
to /var/www/html/weewx
Feb  2 23:45:58 localhost wee_reports[776]: copygenerator: copied 22 files 
to /var/www/html/weewx
Feb  2 23:46:13 localhost wee_reports[776]: copygenerator: copied 0 files 
to /var/www/html/weewx
Feb  2 23:46:13 localhost wee_reports[776]: cheetahgenerator: Generated 4 
files for report Highcharts_Belchertown in 14.96 seconds
Feb  2 23:46:16 localhost wee_reports[776]: cheetahgenerator: Generated 13 
files for report Belchertown in 2.61 seconds
Feb  2 23:46:16 localhost wee_reports[776]: copygenerator: copied 22 files 
to /var/www/html/weewx

journalctl -l:
Feb 02 23:45:58 localhost wee_reports[776]: cheetahgenerator: Generated 13 
files for report StandardReport in 18.46 seconds
Feb 02 23:45:58 localhost wee_reports[776]: copygenerator: copied 22 files 
to /var/www/html/weewx
Feb 02 23:45:58 localhost wee_reports[776]: reportengine: Running report 
Highcharts_Belchertown
Feb 02 23:45:58 localhost wee_reports[776]: reportengine: Found 
configuration file /etc/weewx/skins/Highcharts_Belchertown/skin.conf for 
report Highcharts_Belchertown
Feb 02 23:45:58 localhost wee_reports[776]: cheetahgenerator: using search 
list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 
'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 
'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras', 
'user.belchertown_highchartsSearchX.highchartsDay', 
'user.belchertown_highchartsSearchX.highchartsWeek', 
'user.belchertown_highchartsSearchX.highchartsMonth', 
'user.belchertown_highchartsSearchX.highchartsYear']
Feb 02 23:45:58 localhost wee_reports[776]: manager: Daily summary version 
is 2.0
Feb 02 23:46:01 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:46:04 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:46:07 localhost weewx[482]: sdr: MainThread: lines=[]
Feb 02 23:46:11 localhost weewx[482]: sdr: MainThread: lines=['{"time" : 
"2019-02-03 05:46:08", "model" : "Fine Offset WH65B", "id" : 41, 
"temperature_C" : 12.200, 

[weewx-user] Re: NOAA Reports Belchertown Skin

2019-02-02 Thread gjr80
So it seems you are not prepared to post your logs? As I said in my previous 
post not only do we look for errors in the logs but we look to see what is/is 
not going on. That often gives us a clue to the issue.

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: NOAA Reports Belchertown Skin

2019-02-02 Thread torrin
Hmmm, the only other variable here is I was using interceptor for a bit, 
but it was not stable (stopped capturing packets after 1-4 hours), maybe 
this is SDR vs Interceptor/observer data capture?



On Saturday, February 2, 2019 at 10:17:31 PM UTC-6, tor...@torrin.org wrote:
>
> It is odd, I got weewx running on 1/30/19 and I have entries for 1/30 and 
> 1/31, nothing for 2/1 or 2/2.  I checked the standard skin NOAA reports and 
> they were also missing 2/1 and 2/2.  I checked the NOAA templates in the 
> Belchertown skin and diff'd the weewx standard skin and they are 
> identical.  I am no sqlite wizard and I don't know where this data would be 
> stored to generate the report, but it was storing it as some point.  No 
> errors in the syslog or generated by the service (monitoring with 
> journalctl -l in debug =1 mode)  I don't see any specific entries in the 
> weewx.conf about the NOAA reports.  What's odd is the reports are being 
> generated every time the report engine runs, they just have no data in them.
>
> On the hourly, I was thing like the next 12 hours look forward like Dark 
> Sky does (and supports via API). Saratoga Template did this and it works 
> well.  Not a huge deal, I just love the template and it is something I look 
> at from time to time.
>
> Thanks
>
>
>
> On Saturday, February 2, 2019 at 6:07:05 PM UTC-6, Pat wrote:
>>
>> Hey there. Any errors in syslog when generating the reports? Not sure off 
>> top of my head why NOAA reports would fail. They get the info from within 
>> weewx itself. Do you have any data in the Reports page?
>>
>> What do you mean by the hourly forecasts extended into Belchertown? I'm 
>> using them at https://belchertownweather.com 
>> 
>>  
>> if that helps?
>>
>>
>> On Saturday, February 2, 2019 at 4:29:36 PM UTC-5, tor...@torrin.org 
>> wrote:
>>>
>>> I installed the Belchertown skin last night (It is quite AWESOME!), my 
>>> only issue is my NOAA reports are generating, but have no data in them.  
>>> There are entries from 2 days in January (I just got weewx running 1/30/19) 
>>> but no entries for February.  I am using the Belchertown Skin as the Std 
>>> Report and have no other extensions except RTL_433.  I am not using MQTT 
>>> and I am very Linux fluent and weak on .js stuff.  Any help pointing me in 
>>> a direction to look, I would appreciate it.
>>>
>>> PS. Does anyone have hourly forecasts with Dark Sky extended into 
>>> Belchertown?  That would be the icing on a great cake!
>>>
>>

-- 
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 Reports Belchertown Skin

2019-02-02 Thread torrin
It is odd, I got weewx running on 1/30/19 and I have entries for 1/30 and 
1/31, nothing for 2/1 or 2/2.  I checked the standard skin NOAA reports and 
they were also missing 2/1 and 2/2.  I checked the NOAA templates in the 
Belchertown skin and diff'd the weewx standard skin and they are 
identical.  I am no sqlite wizard and I don't know where this data would be 
stored to generate the report, but it was storing it as some point.  No 
errors in the syslog or generated by the service (monitoring with 
journalctl -l in debug =1 mode)  I don't see any specific entries in the 
weewx.conf about the NOAA reports.  What's odd is the reports are being 
generated every time the report engine runs, they just have no data in them.

On the hourly, I was thing like the next 12 hours look forward like Dark 
Sky does (and supports via API). Saratoga Template did this and it works 
well.  Not a huge deal, I just love the template and it is something I look 
at from time to time.

Thanks



On Saturday, February 2, 2019 at 6:07:05 PM UTC-6, Pat wrote:
>
> Hey there. Any errors in syslog when generating the reports? Not sure off 
> top of my head why NOAA reports would fail. They get the info from within 
> weewx itself. Do you have any data in the Reports page?
>
> What do you mean by the hourly forecasts extended into Belchertown? I'm 
> using them at https://belchertownweather.com 
> 
>  
> if that helps?
>
>
> On Saturday, February 2, 2019 at 4:29:36 PM UTC-5, tor...@torrin.org 
> wrote:
>>
>> I installed the Belchertown skin last night (It is quite AWESOME!), my 
>> only issue is my NOAA reports are generating, but have no data in them.  
>> There are entries from 2 days in January (I just got weewx running 1/30/19) 
>> but no entries for February.  I am using the Belchertown Skin as the Std 
>> Report and have no other extensions except RTL_433.  I am not using MQTT 
>> and I am very Linux fluent and weak on .js stuff.  Any help pointing me in 
>> a direction to look, I would appreciate it.
>>
>> PS. Does anyone have hourly forecasts with Dark Sky extended into 
>> Belchertown?  That would be the icing on a great cake!
>>
>

-- 
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: Second crash after 11 days

2019-02-02 Thread Steve2Q
Tom..thank you for taking the time to help. For now I will reboot the 
system when the % gets up to around 80. It will be interesting if this is a 
problem with Stretch. I wonder if any other Pi users have similar problems 
with Stretch or they are using an older Raspian distro.

-- 
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: Second crash after 11 days

2019-02-02 Thread Thomas Keffer
Well, that's no good.

I've been doing some of my own tests here, and think that the weakrefs are
an artifact of using pympler.

I am running some experiments on my end with stretch. Unfortunately, I
don't have a lot of time at the moment, so it may take a while.

-tk

On Sat, Feb 2, 2019 at 1:18 PM Steve2Q  wrote:

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

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


[weewx-user] Re: NOAA Reports Belchertown Skin

2019-02-02 Thread Pat
Hey there. Any errors in syslog when generating the reports? Not sure off 
top of my head why NOAA reports would fail. They get the info from within 
weewx itself. Do you have any data in the Reports page?

What do you mean by the hourly forecasts extended into Belchertown? I'm 
using them at https://belchertownweather.com if that helps?


On Saturday, February 2, 2019 at 4:29:36 PM UTC-5, tor...@torrin.org wrote:
>
> I installed the Belchertown skin last night (It is quite AWESOME!), my 
> only issue is my NOAA reports are generating, but have no data in them.  
> There are entries from 2 days in January (I just got weewx running 1/30/19) 
> but no entries for February.  I am using the Belchertown Skin as the Std 
> Report and have no other extensions except RTL_433.  I am not using MQTT 
> and I am very Linux fluent and weak on .js stuff.  Any help pointing me in 
> a direction to look, I would appreciate it.
>
> PS. Does anyone have hourly forecasts with Dark Sky extended into 
> Belchertown?  That would be the icing on a great cake!
>

-- 
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: NOAA reports not available

2019-02-02 Thread bgrattan
Glenn,
Thanks! I’ll try the fix tomorrow. Not sure how or when this got messed up. As 
I haven’t used the summary feature for a while then I haven’t missed it.
Much appreciated!  Just curious where you are located?
Will keep you posted.

Bob

-- 
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: NOAA reports not available

2019-02-02 Thread Glenn McKechnie
Hi Bob,

Your page at http://grattans.org/wx/ is missing some vital code, which
interestingly you have correct in your last post.
Is that from your local tmpl version?

The navbar code is missing the 6 lines that start with - in the diff below.

@@ -451,17 +451,11 @@
 
 Monthly summary:
 
-#for $monthYear in $SummaryByMonth
-$monthYear
-#end for
-Select month-
 
 
 Yearly summary:
 
-#for $yr in $SummaryByYear
-$yr
-#end for
-Select year-
 
 

I have your page at http://grattans.org/wx/ correctly generating the
NOAA pages here  if I include that AND also fix the unicode error in
your http://forecast.weather.gov url.

CheetahGenerator complains about invalid code -  I see this "
highlight=on​ "
Remove evrything after the =on and it should generate correctly and
you'll get a fresh copy created and uploaded to your website.
Obviously you'll eventually need to correct the URL and replace
whatever we have rudely taken out.

I suspect half the problem is here, with this broken URL. It breaks
page generation and we/you aren't seeing your changes as the latest
changes aren't being uploaded.






On 03/02/2019, bgrat...@umw.edu  wrote:
> Glenn,
> Here's what I found, so far:
>
> two NOAA directories
> /home/weewx/skins/Standard/NOAA - contains 2 template files for  and MM
>
> summaries
> /home/weewx/pub_html/NOAA - contains all the summary files *.txt from
> 2007-present day
>
> I substituted the original index.html.tmpl and an older weewx.conf file and
>
> got the same results, no pull down  or MM summaries.
>
> The files seem to be being built but not accessible from index.html
> Standard skin.
>
> From my index.html.tmpl:
>
>  
>  onclick="openURL('index.html')" />
>  onclick="openURL('week.html')" />
>  onclick="openURL('month.html')" />
>  onclick="openURL('year.html')" />
> Monthly summary:
> 
> #for $monthYear in $SummaryByMonth
> $monthYear
> #end for
> -Select month-
> 
> 
> Yearly summary:
> 
> #for $yr in $SummaryByYear
> $yr
> #end for
> -Select year-
> 
> 
>   
> 
>
> Thanks for your continued help.  Hope the above tells you something. Sorry
> I'm not much
> of a programmer.
>
> Bob
>
> --
> 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.
>


-- 


Cheers
 Glenn

rorpi - read only raspberry pi & various weewx addons
https://github.com/glennmckechnie

-- 
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: Checking versions, configurations

2019-02-02 Thread mwall
On Saturday, February 2, 2019 at 1:34:44 PM UTC-5, Kevin Tarr wrote:
>
> Sometime in the last six months, my device started to update 
> weatherunderground every 30 minutes instead of 5. Today I started to look.
>

sounds like you have a fine offset station with usb interface.  they will 
occasionally reset to factory defaults.  it seems to be caused by voltage 
changes on the usb, such as dips/surges from a flaky/underpowered power 
supply.

 

> I'm going to ask 2 questions to start:
> The hardware guide has always said this:
>
> wee_device /home/weewx/weewx.conf --help which gives error
> Unable to open configuration file /home/weewx/weewx.conf
>
>
> The program in my version is wee_config_device /home/weewx/weewx.conf 
> --help
>

the utility wee_config_device was replaced by wee_device in weewx release 
3.2.  you can find this information in the 'from 3.1 or earlier' section of 
the upgrade guide:

http://weewx.com/docs/upgrading.htm

 

-- 
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 Reports Belchertown Skin

2019-02-02 Thread torrin
Actually, this looks like a weewx issue, since with the old standard skin 
it was not working past Jan 31.  Any help would be appreciated.  

On Saturday, February 2, 2019 at 3:29:36 PM UTC-6, tor...@torrin.org wrote:
>
> I installed the Belchertown skin last night (It is quite AWESOME!), my 
> only issue is my NOAA reports are generating, but have no data in them.  
> There are entries from 2 days in January (I just got weewx running 1/30/19) 
> but no entries for February.  I am using the Belchertown Skin as the Std 
> Report and have no other extensions except RTL_433.  I am not using MQTT 
> and I am very Linux fluent and weak on .js stuff.  Any help pointing me in 
> a direction to look, I would appreciate it.
>
> PS. Does anyone have hourly forecasts with Dark Sky extended into 
> Belchertown?  That would be the icing on a great cake!
>

-- 
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: Checking versions, configurations

2019-02-02 Thread Kevin Tarr
This is in the hardware guide:
Configuring with wee_device Action --help 

Invoking wee_device  
with the --help option

wee_device */home*/weewx/weewx.conf --help

Anyway, I've upgraded, reset the weewx.conf file.

And this shows the problem:


Feb  2 16:50:21 Dummy-PC weewx[3717]: engine: The archive interval in the 
configuration file (300) does not match the station hardware interval 
(1800).
Feb  2 16:50:21 Dummy-PC weewx[3717]: engine: Using archive interval of 
1800 seconds (specified by hardware)

Trying to change to wee_device /etc/weewx/weewx.conf --set-interval=5

weewx.WeeWxIOError: could not claim interface 0: Operation not permitted

I have weewx stopped.
And this will be upsetting if I cannot reset this. This was the problem I 
had before, I could not change the interval, and eventually the unit 
crapped out. Bought the same thing, a WS-2095, and worked until this summer.

I'm going to post this and restart weewx and think about next steps which 
will include trash compactor.


On Saturday, February 2, 2019 at 4:28:07 PM UTC-5, Kevin Tarr wrote:

>   Installed: 3.1.0-1
>   Candidate: 3.1.0-1
>   Version table:
>  *** 3.1.0-1 0
> 100 /var/lib/dpkg/status
>
> archive_interval = 300
>
> I see it now. Give me an hour.
>
> On Saturday, February 2, 2019 at 2:11:54 PM UTC-5, Pat wrote:
>>
>> I'm a little confused and I think that comes from your confusion. Let's 
>> try to break it down and hopefully that'll help. 
>>
>> It looks like you installed weewx using apt-get. So that would follow the 
>> file location layout for the apt-get installation. Click here and go all 
>> the way to the bottom . (Hint: 
>> weewx.conf is in /etc/weewx not /home/weewx for apt installs). 
>>
>> The latest version is (today) 3.8.2 but 3.9.0 is being beta tested as we 
>> speak. To verify which version you have, run sudo apt policy weewx and 
>> paste the results.
>>
>> Lastly, open /etc/weewx/weewx.conf, then find the [[Wunderground]] 
>> section. This is where you've defined the uploader information. As to why 
>> it's going every 30 minutes - I'm not sure. What is your archive_interval 
>> set to within weewx.conf? I think it may be tied together. Standard 
>> config for archive_interval is 300
>>
>> You could also run:
>>
>> sudo wee_debug /etc/weewx/weewx.conf --info 
>>
>> and paste that here. Be extra careful that it censored all your passwords 
>> within before pasting. 
>>
>>
>>
>> On Saturday, February 2, 2019 at 1:34:44 PM UTC-5, Kevin Tarr wrote:
>>>
>>> Sometime in the last six months, my device started to update 
>>> weatherunderground every 30 minutes instead of 5. Today I started to look.
>>> Problem 1 is that I set this up when I moved houses. I've had to replace 
>>> my home unit sometime (two years ago?) but basically I wanted this to be 
>>> set and forget
>>>
>>> Which is problem 2, I've forgotten everything including how to operate 
>>> this Linux box.
>>>
>>> I'm going to ask 2 questions to start:
>>> The hardware guide has always said this:
>>>
>>> wee_device /home/weewx/weewx.conf --help which gives error
>>> Unable to open configuration file /home/weewx/weewx.conf
>>>
>>>
>>> The program in my version is wee_config_device /home/weewx/weewx.conf 
>>> --help
>>>
>>>
>>>
>>> When I look at wee_config_device the date at the top says 2015-01-19 
>>> 18:41:06 
>>> #!/usr/bin/env python
>>> # $Id: wee_config_device 2867 2015-01-19 18:41:06Z mwall $
>>> # Copyright 2013 Matthew Wall
>>> # See the file LICENSE.txt for your full rights.
>>>
>>> Is this the most current version? I have run the upgrade and it says I 
>>> am running most current version.
>>>
>>>
>>> Reading package lists... Done
>>> Building dependency tree   
>>> Reading state information... Done
>>> weewx is already the newest version.
>>> The following packages were automatically installed and are no longer 
>>> required:
>>>   linux-headers-3.13.0-142 linux-headers-3.13.0-142-generic
>>>   linux-headers-3.13.0-143 linux-headers-3.13.0-143-generic
>>>   linux-image-3.13.0-142-generic linux-image-3.13.0-143-generic
>>>   linux-image-extra-3.13.0-142-generic 
>>> linux-image-extra-3.13.0-143-generic
>>> Use 'apt-get autoremove' to remove them.
>>> 0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
>>>
>>>
>>>
>>>
>>>
>>>

-- 
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: SDR, rtl_433, WH65B, and WH32B

2019-02-02 Thread torrin
Yup, but I am seeing and error and not capturing any data from the WH32B.  
I created an issue, but no one has picked it up yet.  I will post back if I 
get anywhere.

On Saturday, February 2, 2019 at 3:28:34 PM UTC-6, G Hammer wrote:
>
> That may be just the ticket until the 32B is supported.
> So, you've done the steps to get a new device added?
>
> On Saturday, February 2, 2019 at 4:15:49 PM UTC-5, tor...@torrin.org 
> wrote:
>>
>> I have been researching this and I cannot find the WH32B either on 915mhz 
>> (which it is supposed to be on) or 433mhz.  I am working with the rtl_433 
>> folks trying to figure it out.  In the mean time, I picked up a WH25, which 
>> is supported in rtl_433 and is only $16 at AW.
>>
>

-- 
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] NOAA Reports Belchertown Skin

2019-02-02 Thread torrin
I installed the Belchertown skin last night (It is quite AWESOME!), my only 
issue is my NOAA reports are generating, but have no data in them.  There 
are entries from 2 days in January (I just got weewx running 1/30/19) but 
no entries for February.  I am using the Belchertown Skin as the Std Report 
and have no other extensions except RTL_433.  I am not using MQTT and I am 
very Linux fluent and weak on .js stuff.  Any help pointing me in a 
direction to look, I would appreciate it.

PS. Does anyone have hourly forecasts with Dark Sky extended into 
Belchertown?  That would be the icing on a great cake!

-- 
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: SDR, rtl_433, WH65B, and WH32B

2019-02-02 Thread G Hammer
That may be just the ticket until the 32B is supported.
So, you've done the steps to get a new device added?

On Saturday, February 2, 2019 at 4:15:49 PM UTC-5, tor...@torrin.org wrote:
>
> I have been researching this and I cannot find the WH32B either on 915mhz 
> (which it is supposed to be on) or 433mhz.  I am working with the rtl_433 
> folks trying to figure it out.  In the mean time, I picked up a WH25, which 
> is supported in rtl_433 and is only $16 at AW.
>

-- 
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: Checking versions, configurations

2019-02-02 Thread Kevin Tarr
  Installed: 3.1.0-1
  Candidate: 3.1.0-1
  Version table:
 *** 3.1.0-1 0
100 /var/lib/dpkg/status

archive_interval = 300

I see it now. Give me an hour.

On Saturday, February 2, 2019 at 2:11:54 PM UTC-5, Pat wrote:
>
> I'm a little confused and I think that comes from your confusion. Let's 
> try to break it down and hopefully that'll help. 
>
> It looks like you installed weewx using apt-get. So that would follow the 
> file location layout for the apt-get installation. Click here and go all 
> the way to the bottom . (Hint: 
> weewx.conf is in /etc/weewx not /home/weewx for apt installs). 
>
> The latest version is (today) 3.8.2 but 3.9.0 is being beta tested as we 
> speak. To verify which version you have, run sudo apt policy weewx and 
> paste the results.
>
> Lastly, open /etc/weewx/weewx.conf, then find the [[Wunderground]] 
> section. This is where you've defined the uploader information. As to why 
> it's going every 30 minutes - I'm not sure. What is your archive_interval set 
> to within weewx.conf? I think it may be tied together. Standard config for 
> archive_interval is 300
>
> You could also run:
>
> sudo wee_debug /etc/weewx/weewx.conf --info 
>
> and paste that here. Be extra careful that it censored all your passwords 
> within before pasting. 
>
>
>
> On Saturday, February 2, 2019 at 1:34:44 PM UTC-5, Kevin Tarr wrote:
>>
>> Sometime in the last six months, my device started to update 
>> weatherunderground every 30 minutes instead of 5. Today I started to look.
>> Problem 1 is that I set this up when I moved houses. I've had to replace 
>> my home unit sometime (two years ago?) but basically I wanted this to be 
>> set and forget
>>
>> Which is problem 2, I've forgotten everything including how to operate 
>> this Linux box.
>>
>> I'm going to ask 2 questions to start:
>> The hardware guide has always said this:
>>
>> wee_device /home/weewx/weewx.conf --help which gives error
>> Unable to open configuration file /home/weewx/weewx.conf
>>
>>
>> The program in my version is wee_config_device /home/weewx/weewx.conf 
>> --help
>>
>>
>>
>> When I look at wee_config_device the date at the top says 2015-01-19 
>> 18:41:06 
>> #!/usr/bin/env python
>> # $Id: wee_config_device 2867 2015-01-19 18:41:06Z mwall $
>> # Copyright 2013 Matthew Wall
>> # See the file LICENSE.txt for your full rights.
>>
>> Is this the most current version? I have run the upgrade and it says I am 
>> running most current version.
>>
>>
>> Reading package lists... Done
>> Building dependency tree   
>> Reading state information... Done
>> weewx is already the newest version.
>> The following packages were automatically installed and are no longer 
>> required:
>>   linux-headers-3.13.0-142 linux-headers-3.13.0-142-generic
>>   linux-headers-3.13.0-143 linux-headers-3.13.0-143-generic
>>   linux-image-3.13.0-142-generic linux-image-3.13.0-143-generic
>>   linux-image-extra-3.13.0-142-generic 
>> linux-image-extra-3.13.0-143-generic
>> Use 'apt-get autoremove' to remove them.
>> 0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
>>
>>
>>
>>
>>
>>

-- 
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: SDR, rtl_433, WH65B, and WH32B

2019-02-02 Thread torrin
I have been researching this and I cannot find the WH32B either on 915mhz 
(which it is supposed to be on) or 433mhz.  I am working with the rtl_433 
folks trying to figure it out.  In the mean time, I picked up a WH25, which 
is supported in rtl_433 and is only $16 at AW.

On Saturday, February 2, 2019 at 2:24:50 PM UTC-6, G Hammer wrote:
>
> I have an Ambient Weather which has the WH65B outdoor sensor and since I 
> have the WS2000 console, I have a WH32B indoor temp/humidity/barometer.
> I get good data from the outdoor sensor using this: 
> rtl_433 -M utc -F json -p 39.741 -R 78 -f 91498
> {"time" : "2019-02-02 19:21:57", "model" : "Fine Offset WH65B", "id" : 172
> , "temperature_C" : -0.300, "humidity" : 35, "wind_dir_deg" : 105, 
> "wind_speed_ms" : 0.255, "gust_speed_ms" : 0.510, "rainfall_mm" : 1316.228
> , "uv" : 1000, "uvi" : 2, "light_lux" : 35448.000, "battery" : "OK", "mic" 
> : "CRC"}
>
> Does anyone know if the WH32B sensor is supported and if so, how to 
> capture it? It would be required to get the barometer reading.
>
> This would be great for getting away from sniffing data from WiFi if the 
> WH32B data can be captured as well.
>
>

-- 
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: Second crash after 11 days

2019-02-02 Thread Steve2Q
Now up to 15%  :(

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

2019-02-02 Thread John Masters


Yes tk, i have followed the instructions and added FilePile via your manual 
method.
Hey Presto, no more spikes on the graph! Your code has cracked it, many 
thanks:
the RECs are correctly showing extraTemp1:
john@pyzero:/home/weewx $ sudo bin/weewxd weewx.conf 
REC:2019-02-02 19:50:13 GMT (1549137013) altimeter: 30.2555134087, 
appTemp: 26.8722205692, barometer: 30.2692025906, cloudbase: 977.76006791, 
dateTime: 1549137013, delay: 5, dewpoint: 27.1278557012, ET: None, 
extraTemp1: 38.48, heatindex: 31.1, humidex: 31.1, inDewpoint: 
53.4656096097, inHumidity: 59.0, inTemp: 68.36, interval: 5, maxSolarRad: 
0.0, outHumidity: 85.0, outTemp: 31.1, outTempBatteryStatus: 0, pressure: 
30.1826002238, ptr: 20528, radiation: None, rain: None, rainRate: 0, 
rainTotal: 77.73, rxCheckPercent: 100, status: 0, usUnits: 1, UV: None, 
windchill: 31.1, windDir: None, windGust: 0.67108282, windrun: 
23.0591422571, windSpeed: 0.0
REC:2019-02-02 19:55:13 GMT (1549137313) altimeter: 30.2584728857, 
appTemp: 27.0739763543, barometer: 30.2721322622, cloudbase: 978.517865133, 
dateTime: 1549137313, delay: 5, dewpoint: 27.3045213934, ET: None, 
extraTemp1: 38.48, heatindex: 31.28, humidex: 31.28, inDewpoint: 
53.4656096097, inHumidity: 59.0, inTemp: 68.36, interval: 5, maxSolarRad: 
0.0, outHumidity: 85.0, outTemp: 31.28, outTempBatteryStatus: 0, pressure: 
30.1855532225, ptr: 20544, radiation: None, rain: 0.0, rainRate: 0, 
rainTotal: 77.73, rxCheckPercent: 100, status: 0, usUnits: 1, UV: None, 
windchill: 31.28, windDir: None, windGust: 1.56585929636, windrun: 
23.0591422571, windSpeed: 0.0
REC:2019-02-02 20:00:13 GMT (1549137613) altimeter: 30.2673513159, 
appTemp: 27.4779108554, barometer: 30.2809531191, cloudbase: 980.034404442, 
dateTime: 1549137613, delay: 5, dewpoint: 27.6578486205, ET: None, 
extraTemp1: 38.48, heatindex: 31.64, humidex: 31.64, inDewpoint: 
53.4656096097, inHumidity: 59.0, inTemp: 68.36, interval: 5, maxSolarRad: 
0.0, outHumidity: 85.0, outTemp: 31.64, outTempBatteryStatus: 0, pressure: 
30.1944122187, ptr: 20560, radiation: None, rain: 0.0, rainRate: 0, 
rainTotal: 77.73, rxCheckPercent: 100, status: 0, usUnits: 1, UV: None, 
windchill: 31.64, windDir: None, windGust: 1.56585929636, windrun: 
23.0591422571, windSpeed: 0.0
REC:2019-02-02 20:05:13 GMT (1549137913) altimeter: 30.2673513159, 
appTemp: 27.8461508, barometer: 30.2808896633, cloudbase: 1046.90658162, 
dateTime: 1549137913, delay: 5, dewpoint: 27.7236110409, ET: None, 
extraTemp1: 38.48, heatindex: 32.0, humidex: 32.0, inDewpoint: 
53.2969727299, inHumidity: 59.0, inTemp: 68.18, interval: 5, maxSolarRad: 
0.0, outHumidity: 84.0, outTemp: 32.0, outTempBatteryStatus: 0, pressure: 
30.1944122187, ptr: 20576, radiation: None, rain: 0.0, rainRate: 0, 
rainTotal: 77.73, rxCheckPercent: 100, status: 0, usUnits: 1, UV: None, 
windchill: 32.0, windDir: None, windGust: 0.67108282, windrun: 
23.0591422571, windSpeed: 0.0

Daypond.png attached.

Regards
John

-- 
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] SDR, rtl_433, WH65B, and WH32B

2019-02-02 Thread G Hammer
I have an Ambient Weather which has the WH65B outdoor sensor and since I 
have the WS2000 console, I have a WH32B indoor temp/humidity/barometer.
I get good data from the outdoor sensor using this: 
rtl_433 -M utc -F json -p 39.741 -R 78 -f 91498
{"time" : "2019-02-02 19:21:57", "model" : "Fine Offset WH65B", "id" : 172, 
"temperature_C" : -0.300, "humidity" : 35, "wind_dir_deg" : 105, 
"wind_speed_ms" : 0.255, "gust_speed_ms" : 0.510, "rainfall_mm" : 1316.228, 
"uv" : 1000, "uvi" : 2, "light_lux" : 35448.000, "battery" : "OK", "mic" : 
"CRC"}

Does anyone know if the WH32B sensor is supported and if so, how to capture 
it? It would be required to get the barometer reading.

This would be great for getting away from sniffing data from WiFi if the 
WH32B data can be captured as well.

-- 
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: Checking versions, configurations

2019-02-02 Thread Pat
I'm a little confused and I think that comes from your confusion. Let's try 
to break it down and hopefully that'll help. 

It looks like you installed weewx using apt-get. So that would follow the 
file location layout for the apt-get installation. Click here and go all 
the way to the bottom . (Hint: weewx.conf 
is in /etc/weewx not /home/weewx for apt installs). 

The latest version is (today) 3.8.2 but 3.9.0 is being beta tested as we 
speak. To verify which version you have, run sudo apt policy weewx and 
paste the results.

Lastly, open /etc/weewx/weewx.conf, then find the [[Wunderground]] section. 
This is where you've defined the uploader information. As to why it's going 
every 30 minutes - I'm not sure. What is your archive_interval set to 
within weewx.conf? I think it may be tied together. Standard config for 
archive_interval is 300

You could also run:

sudo wee_debug /etc/weewx/weewx.conf --info 

and paste that here. Be extra careful that it censored all your passwords 
within before pasting. 



On Saturday, February 2, 2019 at 1:34:44 PM UTC-5, Kevin Tarr wrote:
>
> Sometime in the last six months, my device started to update 
> weatherunderground every 30 minutes instead of 5. Today I started to look.
> Problem 1 is that I set this up when I moved houses. I've had to replace 
> my home unit sometime (two years ago?) but basically I wanted this to be 
> set and forget
>
> Which is problem 2, I've forgotten everything including how to operate 
> this Linux box.
>
> I'm going to ask 2 questions to start:
> The hardware guide has always said this:
>
> wee_device /home/weewx/weewx.conf --help which gives error
> Unable to open configuration file /home/weewx/weewx.conf
>
>
> The program in my version is wee_config_device /home/weewx/weewx.conf 
> --help
>
>
>
> When I look at wee_config_device the date at the top says 2015-01-19 
> 18:41:06 
> #!/usr/bin/env python
> # $Id: wee_config_device 2867 2015-01-19 18:41:06Z mwall $
> # Copyright 2013 Matthew Wall
> # See the file LICENSE.txt for your full rights.
>
> Is this the most current version? I have run the upgrade and it says I am 
> running most current version.
>
>
> Reading package lists... Done
> Building dependency tree   
> Reading state information... Done
> weewx is already the newest version.
> The following packages were automatically installed and are no longer 
> required:
>   linux-headers-3.13.0-142 linux-headers-3.13.0-142-generic
>   linux-headers-3.13.0-143 linux-headers-3.13.0-143-generic
>   linux-image-3.13.0-142-generic linux-image-3.13.0-143-generic
>   linux-image-extra-3.13.0-142-generic linux-image-extra-3.13.0-143-generic
> Use 'apt-get autoremove' to remove them.
> 0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.
>
>
>
>
>
>

-- 
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: Argent Ads-Ws1 Replacement and other stuff

2019-02-02 Thread Jardi Martínez
Hi!

As a request in another post here, I have been working on a driver for the
Build Your Own Weather Station, as described in this guide:
https://projects.raspberrypi.org/en/projects/build-your-own-weather-station

I don't have the hardware so the debugging is being done by the guy who
requested it, Patrick. I have converted the Python script into a basic but
functional driver, it works well if you follow the guide and use the same
suggested hardware and everything is connected since I have all the
parameters hard coded in the driver right now.

I have the code in a git repository, this is the weeWX driver:
https://github.com/jardiamj/BYOWS_RPi/blob/master/byows_rpi.py

As I said before, this is a basic driver and needs a lot of improvement. I
am tidying up the code at the moment, and will make it so you can pass some
parameters through the weewx.conf file. I also need to add some error
catching.

I would not be that difficult to add support for other hardware once I get
the driver all figured out. My only issue is that I don't have the
hardware, I have a raspberry pi and have been simulating the sensors with
push buttons and other things but I have to rely on Patrick for debugging
at the moment. I might get some of the sensors myself later on but at the
moment I have.

On Fri, Feb 1, 2019, 12:56 PM HoracioDos  No love for this thread?
>
> On Wednesday, January 30, 2019 at 12:23:09 PM UTC-3, HoracioDos wrote:
>>
>> Hello!
>>
>> I've been out of the forum for a long time and I hope to jump into into
>> my hobbies again this year. I would like to build my own weather station.
>>
>> I already own an Argent ads-ws1 and I've been adding external sensors to
>> weewx in recent years to get better measurements , but now I would like to
>> replace the whole thing with a new design. I didn't define yet if I will
>> use some microcontroller or I will attach sensors directly to a raspberry
>> pi. So I would like to hear some advice about the easier way to define a
>> record format. I don't know how hard it could be to write a new driver from
>> the scratch or if I should use a driver that it's already working like
>> peetbros for the ws1.
>>
>> I would like also to have a proper WS and I've found a Welleman WS3080
>> for €106. What's the experience with this model? I'm a little bit worried
>> about fineoffset usb locks. ¿How often it occurs?
>>
>> 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.
>

-- 
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: Ambient Weather WS-2000/WH31B

2019-02-02 Thread G Hammer
I can see my WH31B
Tuned to 433.920MHz.
Allocating 15 zero-copy buffers
{"time" : "2019-02-02 18:52:41", "brand" : "OS", "model" : "THGR122N", "id" 
: 206, "channel" : 1, "battery" : "OK", "temperature_C" : -2.000, 
"humidity" : 12}
{"time" : "2019-02-02 18:52:42", "brand" : "OS", "model" : "THGR122N", "id" 
: 206, "channel" : 1, "battery" : "OK", "temperature_C" : -2.000, 
"humidity" : 12}
{"time" : "2019-02-02 18:53:20", "brand" : "OS", "model" : "THGR122N", "id" 
: 206, "channel" : 1, "battery" : "OK", "temperature_C" : -1.900, 
"humidity" : 12}

On Wednesday, January 30, 2019 at 3:23:54 PM UTC-5, tor...@torrin.org wrote:
>
> Ya, it transmits over some radio frequency, I just can't find it.  I went 
> to inspector to capture all data and it seems like it is working for now.  
> I am still chasing weewx just randomly stopping without erroring out.  
>
> On Wednesday, January 30, 2019 at 9:14:27 AM UTC-6, Andrew Milner wrote:
>>
>> I presume the WH31B is the indoor console.  Are you sure it transmits the 
>> data over the radio??  I thought most of the stations just use the radio to 
>> receive the external sensor data, process/combine the external data with 
>> the internal data and push it back out over usb or tcp/ip on a network.  
>> Who/what would actually receive the data if the console were to push 
>> broadcast it back out again (apart from your sdr receiver of course!!)?? 
>>
>>
>>
>> On Wednesday, 30 January 2019 16:45:39 UTC+2, tor...@torrin.org wrote:
>>>
>>> I have just gotten my Ambient Weather WS-2000 system working on weewx 
>>> with SDR.  The only issue I have remaining is I only see traffic from the 
>>> WH65B Sensor Array, but not the indoor and barometer reading (as they come 
>>> from the WH31B.  Has anyone gotten a WH31B working with the SDR 
>>> configuration?  When I checked for data on the 915mhz band, I only saw the 
>>> WH65B sending info.
>>>
>>>

-- 
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] Checking versions, configurations

2019-02-02 Thread Kevin Tarr
Sometime in the last six months, my device started to update 
weatherunderground every 30 minutes instead of 5. Today I started to look.
Problem 1 is that I set this up when I moved houses. I've had to replace my 
home unit sometime (two years ago?) but basically I wanted this to be set 
and forget

Which is problem 2, I've forgotten everything including how to operate this 
Linux box.

I'm going to ask 2 questions to start:
The hardware guide has always said this:

wee_device /home/weewx/weewx.conf --help which gives error
Unable to open configuration file /home/weewx/weewx.conf


The program in my version is wee_config_device /home/weewx/weewx.conf --help



When I look at wee_config_device the date at the top says 2015-01-19 
18:41:06 
#!/usr/bin/env python
# $Id: wee_config_device 2867 2015-01-19 18:41:06Z mwall $
# Copyright 2013 Matthew Wall
# See the file LICENSE.txt for your full rights.

Is this the most current version? I have run the upgrade and it says I am 
running most current version.


Reading package lists... Done
Building dependency tree   
Reading state information... Done
weewx is already the newest version.
The following packages were automatically installed and are no longer 
required:
  linux-headers-3.13.0-142 linux-headers-3.13.0-142-generic
  linux-headers-3.13.0-143 linux-headers-3.13.0-143-generic
  linux-image-3.13.0-142-generic linux-image-3.13.0-143-generic
  linux-image-extra-3.13.0-142-generic linux-image-extra-3.13.0-143-generic
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 98 not upgraded.





-- 
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: NOAA reports not available

2019-02-02 Thread bgrattan
Glenn,
Here's what I found, so far:

two NOAA directories 
/home/weewx/skins/Standard/NOAA - contains 2 template files for  and MM 
summaries
/home/weewx/pub_html/NOAA - contains all the summary files *.txt from 
2007-present day

I substituted the original index.html.tmpl and an older weewx.conf file and 
got the same results, no pull down  or MM summaries.

The files seem to be being built but not accessible from index.html 
Standard skin.

>From my index.html.tmpl:

 




Monthly summary:

#for $monthYear in $SummaryByMonth
$monthYear
#end for
-Select month-


Yearly summary:

#for $yr in $SummaryByYear
$yr
#end for
-Select year-


  


Thanks for your continued help.  Hope the above tells you something. Sorry 
I'm not much
of a programmer.

Bob

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

2019-02-02 Thread Juan Antonio Mosquera
The internationalization would be very interesting. That way we would not 
have to change the code with each update. Thank you for your work.

El sábado, 2 de febrero de 2019, 13:57:13 (UTC+1), Pat escribió:
>
> Thanks. I'm working on skin version 0.9 now which I'm hoping to release 
> soon. Many bug fixes.
>
> To change the chart names, check the files within 
> skins/Highcharts_Belchertown/json
>
> I haven't had a chance to look into internationalization yet. Hopefully 
> soon.
>
>
>
> On Saturday, February 2, 2019 at 7:35:31 AM UTC-5, opc...@gmail.com wrote:
>>
>> Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
>> everything into German. I am currently stuck at renaming the graphs. Where 
>> do I need to change the titles of the diagrams and also the names of the 
>> single lines?
>>
>>
>> Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>>>
>>> The skin is showing the alerts that are downloaded from DarkSky. I have 
>>> no more developer notes than that. If there's too many alerts, you can 
>>> reach out to DarkSky themselves to ask about it. 
>>>
>>> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm wrote:

 I just implemented this skin and its fantastic

 I do however seem to be getting to many weather warnings..

 Currently showing 4 weather warnings for my area.. but there is 
 currently only one active on darksky

 https://stormy.ie/weather/live/
 https://darksky.net/forecast/53.3272,-9.1737/ca12/en
 https://www.met.ie/warnings

 Each time the MET seems to update it.. I get another weather warning on 
 my site.. any ideas?

 On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:
>
> I've just released version 0.8.2 of the Belchertown skin which fixes 
> the New Year bug some of you are seeing. It also adds some other 
> features. 
>
>
> Download and install instructions here: 
> https://github.com/poblabs/weewx-belchertown/releases
>
>
> * Fixed an error where the skin would fail when the date rolls to the 
> New Year due to no data being in certain tables in the database yet. 
> * Added the ability to show any weather alerts provided by the DarkSky 
> API. Weather alerts are off by default, use forecast_alert_enabled in 
> weewx.conf skin options to enable it.
> * New option to show cloudbase. You must have your database schema 
> extended for the cloudbase observation to be calculated by weewx. Check 
> the 
> Belchertown skin wiki for details.
> * Fixes an issue where the MQTT updates showed altimeter instead of 
> barometer.
> * Updated Google Analytics page to be in header based on Google 
> recommendations. 
> * Updated Google Analytics to a more recent script block. 
> * Added a Google Analytics page view per MQTT update as per Google 
> Recommendations on background updates. 
>
>

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

2019-02-02 Thread Thomas Keffer
I have created an extension, FilePile ,
that automates a lot of this. You specify what unit system your incoming
data is in, and it will automatically convert it to the unit system used by
the incoming record.

Take a look at  the README and see if everything is clear.

-tk

On Sat, Feb 2, 2019 at 4:33 AM John Masters  wrote:

>
> Yes Folks,
>
> @Gary, that's explained a likely cause, thanks for taking the time to
> investigate. Something like the Mars Climate Orbiter, but a lot less
> critical!
>
> @tk, Yes, but i want to put to bed the idea that my temperature sensor is
> randomly switching from degrees_F to degrees_C by itself.
> The sensor is a  DS18B20 1wire connected to a remote RPi. It outputs a
> number which can be interpreted by humans to be a temperature reading. It
> is just a number, with no units attached.
> A script reads this number and inserts it into a MySQL database, which is
> read by php into a graph (see attached pondgraph.jpg). As you can see, the
> temperature is natively and continuously in degrees_C.
>
> The script also writes the number to a plain file, pond.txt, which is
> scp'd every 5 mins to /var/tmp/pond.txt on the Rpi that hosts weewx. It is
> only a number, with no formatting.
> pondservice.py then does it's thing with the number in pond.txt.
>
> When i initially saw that something was going wrong with the resulting
> extraTemp1, and that degrees_C was being interpreted as degrees_F, i wrote
> a conversion into my script so that the number inserted into pond.txt could
> be sent as degrees_F. All that means is that pond.txt contains e.g. instead
> of the number 10 (degrees_C), the number 50 (its Fahrenheit equivalent).
> It is only I who makes that change, by commenting out the conversion in my
> script. See the attached daypond.jpg
>
> Daypond shows pond temperature being sent as a degrees_F number (just a
> plain text number) up until point 1, when i restarted weewx a few times to
> capture the logs that i attached to my post last night, as @Andrew
> suggested.
> Point 2 shows where i commented out the conversion part of my script and
> sent pond temperature as a degrees_C number (again, just a plain text
> number, no units attached), and restarted weewx a couple of times to
> capture more logs, and then let it run like that for a while.
> Point 3 shows where i uncommented the conversion part of my script, and
> continued sending as a degrees_F value, with no restart.
> At no time did i change any other values or settings.
> Every time the file is scp'd there is an entry in the syslog on the remote
> RPi, and the values sent do not change from Degree_C to degrees_F unless i
> comment or uncomment the conversion line in my script,
>
> If i send pond.txt as degrees_F, there is an initial high reading where
> the Fahrenheit number is interpreted as degrees_C, but subsequent readings
> are converted and shown as degrees_C. (e.g. the number 50 in pond.txt is
> initially interpreted as 50 degrees_C in the REC packet, but subsequently
> converted to 10 degrees_C)
> If i send pond.txt as degrees_C, the number is interpreted as its
> Fahrenheit equivalent. (so if pond.txt contains the number 10, it is
> interpreted as 10 degrees_F)
>
> If you follow the Wiki https://github.com/weewx/weewx/wiki/add-sensor and
> install pondservice.py, and create /var/tmp/pond.txt and put any number in
> it, you should see the problem
>
> Phew, you'll all be sick of all this by now, but i hope i have made it
> more clear.
>
> Regards
> John
>
> --
> You received this message because you are subscribed to the Google Groups
> "weewx-user" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to weewx-user+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

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


[weewx-user] Re: Belchertown Skin 0.8.2 Released

2019-02-02 Thread Pat
Thanks. I'm working on skin version 0.9 now which I'm hoping to release 
soon. Many bug fixes.

To change the chart names, check the files within 
skins/Highcharts_Belchertown/json

I haven't had a chance to look into internationalization yet. Hopefully 
soon.



On Saturday, February 2, 2019 at 7:35:31 AM UTC-5, opc...@gmail.com wrote:
>
> Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
> everything into German. I am currently stuck at renaming the graphs. Where 
> do I need to change the titles of the diagrams and also the names of the 
> single lines?
>
>
> Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>>
>> The skin is showing the alerts that are downloaded from DarkSky. I have 
>> no more developer notes than that. If there's too many alerts, you can 
>> reach out to DarkSky themselves to ask about it. 
>>
>> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm wrote:
>>>
>>> I just implemented this skin and its fantastic
>>>
>>> I do however seem to be getting to many weather warnings..
>>>
>>> Currently showing 4 weather warnings for my area.. but there is 
>>> currently only one active on darksky
>>>
>>> https://stormy.ie/weather/live/
>>> https://darksky.net/forecast/53.3272,-9.1737/ca12/en
>>> https://www.met.ie/warnings
>>>
>>> Each time the MET seems to update it.. I get another weather warning on 
>>> my site.. any ideas?
>>>
>>> On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:

 I've just released version 0.8.2 of the Belchertown skin which fixes 
 the New Year bug some of you are seeing. It also adds some other features. 


 Download and install instructions here: 
 https://github.com/poblabs/weewx-belchertown/releases


 * Fixed an error where the skin would fail when the date rolls to the 
 New Year due to no data being in certain tables in the database yet. 
 * Added the ability to show any weather alerts provided by the DarkSky 
 API. Weather alerts are off by default, use forecast_alert_enabled in 
 weewx.conf skin options to enable it.
 * New option to show cloudbase. You must have your database schema 
 extended for the cloudbase observation to be calculated by weewx. Check 
 the 
 Belchertown skin wiki for details.
 * Fixes an issue where the MQTT updates showed altimeter instead of 
 barometer.
 * Updated Google Analytics page to be in header based on Google 
 recommendations. 
 * Updated Google Analytics to a more recent script block. 
 * Added a Google Analytics page view per MQTT update as per Google 
 Recommendations on background updates. 



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

2019-02-02 Thread opchris
Hi Guys!Thank you, Pat, for the great skin! I am about to translate 
everything into German. I am currently stuck at renaming the graphs. Where 
do I need to change the titles of the diagrams and also the names of the 
single lines?


Am Donnerstag, 31. Januar 2019 23:07:46 UTC+1 schrieb Pat:
>
> The skin is showing the alerts that are downloaded from DarkSky. I have no 
> more developer notes than that. If there's too many alerts, you can reach 
> out to DarkSky themselves to ask about it. 
>
> On Thursday, January 31, 2019 at 3:32:05 PM UTC-5, mercurystorm wrote:
>>
>> I just implemented this skin and its fantastic
>>
>> I do however seem to be getting to many weather warnings..
>>
>> Currently showing 4 weather warnings for my area.. but there is currently 
>> only one active on darksky
>>
>> https://stormy.ie/weather/live/
>> https://darksky.net/forecast/53.3272,-9.1737/ca12/en
>> https://www.met.ie/warnings
>>
>> Each time the MET seems to update it.. I get another weather warning on 
>> my site.. any ideas?
>>
>> On Tuesday, 1 January 2019 12:50:49 UTC, Pat wrote:
>>>
>>> I've just released version 0.8.2 of the Belchertown skin which fixes the 
>>> New Year bug some of you are seeing. It also adds some other features. 
>>>
>>>
>>> Download and install instructions here: 
>>> https://github.com/poblabs/weewx-belchertown/releases
>>>
>>>
>>> * Fixed an error where the skin would fail when the date rolls to the 
>>> New Year due to no data being in certain tables in the database yet. 
>>> * Added the ability to show any weather alerts provided by the DarkSky 
>>> API. Weather alerts are off by default, use forecast_alert_enabled in 
>>> weewx.conf skin options to enable it.
>>> * New option to show cloudbase. You must have your database schema 
>>> extended for the cloudbase observation to be calculated by weewx. Check the 
>>> Belchertown skin wiki for details.
>>> * Fixes an issue where the MQTT updates showed altimeter instead of 
>>> barometer.
>>> * Updated Google Analytics page to be in header based on Google 
>>> recommendations. 
>>> * Updated Google Analytics to a more recent script block. 
>>> * Added a Google Analytics page view per MQTT update as per Google 
>>> Recommendations on background updates. 
>>>
>>>

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