[weewx-user] Re: NOAA Reports Belchertown Skin

[Pat]

The NOAA files Belchertown skin are using are from the Standard skin. When 
comparing 3.9.1's Standard skin NOAA files, there are no changes to what 
Belchertown has now. It appears as though the Belchertown NOAA files 
already have the same Barometer checks 

 that 
Standard does. 

However, when comparing 3.9.1's Season's NOAA files, there's plenty of 
changes but seem limited to just taking advantage of the newer .format() 
options (e.g. add_label=False). 



On Friday, February 8, 2019 at 12:10:05 AM UTC-5, gjr80 wrote:
>
> Ah yes, should have remembered there is a check in the NOAA templates to 
> see whether data is to be output for that row (day or month) - the check is 
> whether there is barometer data for that row. No barometer data the row is 
> left blank, have barometer data the row is populated. This has come up 
> before and I thought it was addressed, perhaps not. Then again, as the 
> results you posted so far you did not actually run the Standard skin (the 
> Belchertown skin was being called under [[StandardReport]]) it is possible 
> the Standard skin NOAA templates were fixed but perhaps the Belchertown 
> NOAA templates have not been similarly fixed. Needs more investigation, at 
> least we know where to look now.
>
> thanks
>
> Gary  
>
> On Friday, 8 February 2019 14:58:37 UTC+10, tor...@torrin.org wrote:
>>
>> Well, it appears that I solved this.  I picked up a WH25 to get barometer 
>> and inside temp to weewx until I could figure out how to capture the 
>> WH32B.  Once I started capturing a barometer reading again, it started 
>> generating the NOAA reports.  Odd, but that was the only thing IO changed.  
>> I will let it run overnight, then work to upgrade to 3.91.
>>
>>
>>
>> On Monday, February 4, 2019 at 9:02:05 AM UTC-6, tor...@torrin.org wrote:
>>>
>>> Thanks guys, I am travelling and will be away from my pi until Thursday, 
>>> I will try the suggested changes then and report back.
>>>
>>> Thanks!
>>>
>>> On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote:

 I agree with Pat that some changes are needed to [StdReport]. I don't 
 expect the Belchertown extension would be interfering with other skins, 
 but 
 for some reason it appears that a number of settings in [StdReport] 
 have changed from default and would appear to be conflicting (the 
 conflicts 
 may not be the cause of the problem but they certainly limit 
 troubleshooting). We should have been seeing [[StandardReport]] and 
 [[Belchertown]] both producing NOAA format reports. Unfortunately the skin 
 = Belchertown setting under [[StandardReport]] meant that the Standard 
 skin was never called. As it turns out even if [[StandardReport]] had skin 
 = Standard we would not have had any Standard skin NOAA reports to 
 look at as the HTML_ROOT = /var/www/html/weewx appearing under 
 [StdReport] and [[Belchertown]] would mean that all NOAA reports 
 (whether from the Standard skin or Belchertown skin would have gone to 
 /var/www/html/weewx/NOAA and since the Belchertown report was listed 
 after StandardReport the Belchertown NOAA files would have overwritten 
 those generated by StandardReport.

 I suggest a few changes to [StdReport] so we can see if both the 
 Standard skin and Belchertown are having the same problem generating the 
 NOAA reports. Based on the Belchertown and WeeWX defaults I would change 
 [StdReport] to be:

 [StdReport]

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

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

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

 # Each of the following subsections defines a report that will be run.

 [[StandardReport]]
 # See the customizing guide to change the units, plot types and 
 line
 # colors, modify the fonts, display additional sensor data, and 
 other
 # customizations. Many of those changes can be made here by 
 overriding
 # parameters, or by modifying templates within the skin itself.

 # The StandardReport uses the 'Standard' skin, which contains the
 # images, templates and plots for the report.
 skin = Standard
 [[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 = "mydomain.com"
 forecast_enabled = 1
 darksky_secret_key = 

[weewx-user] Re: NOAA Reports Belchertown Skin

[gjr80]

Ah yes, should have remembered there is a check in the NOAA templates to 
see whether data is to be output for that row (day or month) - the check is 
whether there is barometer data for that row. No barometer data the row is 
left blank, have barometer data the row is populated. This has come up 
before and I thought it was addressed, perhaps not. Then again, as the 
results you posted so far you did not actually run the Standard skin (the 
Belchertown skin was being called under [[StandardReport]]) it is possible 
the Standard skin NOAA templates were fixed but perhaps the Belchertown 
NOAA templates have not been similarly fixed. Needs more investigation, at 
least we know where to look now.

thanks

Gary  

On Friday, 8 February 2019 14:58:37 UTC+10, tor...@torrin.org wrote:
>
> Well, it appears that I solved this.  I picked up a WH25 to get barometer 
> and inside temp to weewx until I could figure out how to capture the 
> WH32B.  Once I started capturing a barometer reading again, it started 
> generating the NOAA reports.  Odd, but that was the only thing IO changed.  
> I will let it run overnight, then work to upgrade to 3.91.
>
>
>
> On Monday, February 4, 2019 at 9:02:05 AM UTC-6, tor...@torrin.org wrote:
>>
>> Thanks guys, I am travelling and will be away from my pi until Thursday, 
>> I will try the suggested changes then and report back.
>>
>> Thanks!
>>
>> On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote:
>>>
>>> I agree with Pat that some changes are needed to [StdReport]. I don't 
>>> expect the Belchertown extension would be interfering with other skins, but 
>>> for some reason it appears that a number of settings in [StdReport] 
>>> have changed from default and would appear to be conflicting (the conflicts 
>>> may not be the cause of the problem but they certainly limit 
>>> troubleshooting). We should have been seeing [[StandardReport]] and 
>>> [[Belchertown]] both producing NOAA format reports. Unfortunately the skin 
>>> = Belchertown setting under [[StandardReport]] meant that the Standard 
>>> skin was never called. As it turns out even if [[StandardReport]] had skin 
>>> = Standard we would not have had any Standard skin NOAA reports to look 
>>> at as the HTML_ROOT = /var/www/html/weewx appearing under [StdReport] 
>>> and [[Belchertown]] would mean that all NOAA reports (whether from the 
>>> Standard skin or Belchertown skin would have gone to 
>>> /var/www/html/weewx/NOAA and since the Belchertown report was listed 
>>> after StandardReport the Belchertown NOAA files would have overwritten 
>>> those generated by StandardReport.
>>>
>>> I suggest a few changes to [StdReport] so we can see if both the 
>>> Standard skin and Belchertown are having the same problem generating the 
>>> NOAA reports. Based on the Belchertown and WeeWX defaults I would change 
>>> [StdReport] to be:
>>>
>>> [StdReport]
>>>
>>> # Where the skins reside, relative to WEEWX_ROOT
>>> SKIN_ROOT = /etc/weewx/skins
>>>
>>> # Where the generated reports should go, relative to WEEWX_ROOT
>>> HTML_ROOT = /var/www/html/weewx
>>>
>>> # The database binding indicates which data should be used in reports.
>>> data_binding = wx_binding
>>>
>>> # Each of the following subsections defines a report that will be run.
>>>
>>> [[StandardReport]]
>>> # See the customizing guide to change the units, plot types and line
>>> # colors, modify the fonts, display additional sensor data, and 
>>> other
>>> # customizations. Many of those changes can be made here by 
>>> overriding
>>> # parameters, or by modifying templates within the skin itself.
>>>
>>> # The StandardReport uses the 'Standard' skin, which contains the
>>> # images, templates and plots for the report.
>>> skin = Standard
>>> [[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 = "mydomain.com"
>>> forecast_enabled = 1
>>> darksky_secret_key = "MyGoodKey"
>>> earthquake_enabled = 1
>>>
>>> Looking at the Belchertown extension installer I see that HTML_ROOT is 
>>> normally be set to HTML_ROOT = belchertown, but in that case that would 
>>> put the Belchertown generated files in /usr/share/weewx/belchertown, I 
>>> think it will be easier to keep them close to the rest of the generated 
>>> output in /var/www/html/weewx. 
>>>
>>> Leave debug = 1 in weewx.conf for the time being. I would also delete 
>>> the contents of the /var/www/html/weewx directory so we can be certain 
>>> it is all freshly generated. Once the [StdReport] changes have been 
>>> made and /var/www/html/weewx cleared of content, restart WeeWX and let 
>>> it run for a couple of archive intervals. Check the 

[weewx-user] Re: NOAA Reports Belchertown Skin

[torrin]

Well, it appears that I solved this.  I picked up a WH25 to get barometer 
and inside temp to weewx until I could figure out how to capture the 
WH32B.  Once I started capturing a barometer reading again, it started 
generating the NOAA reports.  Odd, but that was the only thing IO changed.  
I will let it run overnight, then work to upgrade to 3.91.



On Monday, February 4, 2019 at 9:02:05 AM UTC-6, tor...@torrin.org wrote:
>
> Thanks guys, I am travelling and will be away from my pi until Thursday, I 
> will try the suggested changes then and report back.
>
> Thanks!
>
> On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote:
>>
>> I agree with Pat that some changes are needed to [StdReport]. I don't 
>> expect the Belchertown extension would be interfering with other skins, but 
>> for some reason it appears that a number of settings in [StdReport] have 
>> changed from default and would appear to be conflicting (the conflicts may 
>> not be the cause of the problem but they certainly limit troubleshooting). 
>> We should have been seeing [[StandardReport]] and [[Belchertown]] both 
>> producing NOAA format reports. Unfortunately the skin = Belchertown 
>> setting under [[StandardReport]] meant that the Standard skin was never 
>> called. As it turns out even if [[StandardReport]] had skin = Standard 
>> we would not have had any Standard skin NOAA reports to look at as the 
>> HTML_ROOT 
>> = /var/www/html/weewx appearing under [StdReport] and [[Belchertown]] 
>> would mean that all NOAA reports (whether from the Standard skin or 
>> Belchertown skin would have gone to /var/www/html/weewx/NOAA and since 
>> the Belchertown report was listed after StandardReport the Belchertown NOAA 
>> files would have overwritten those generated by StandardReport.
>>
>> I suggest a few changes to [StdReport] so we can see if both the 
>> Standard skin and Belchertown are having the same problem generating the 
>> NOAA reports. Based on the Belchertown and WeeWX defaults I would change 
>> [StdReport] to be:
>>
>> [StdReport]
>>
>> # Where the skins reside, relative to WEEWX_ROOT
>> SKIN_ROOT = /etc/weewx/skins
>>
>> # Where the generated reports should go, relative to WEEWX_ROOT
>> HTML_ROOT = /var/www/html/weewx
>>
>> # The database binding indicates which data should be used in reports.
>> data_binding = wx_binding
>>
>> # Each of the following subsections defines a report that will be run.
>>
>> [[StandardReport]]
>> # See the customizing guide to change the units, plot types and line
>> # colors, modify the fonts, display additional sensor data, and other
>> # customizations. Many of those changes can be made here by 
>> overriding
>> # parameters, or by modifying templates within the skin itself.
>>
>> # The StandardReport uses the 'Standard' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Standard
>> [[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 = "mydomain.com"
>> forecast_enabled = 1
>> darksky_secret_key = "MyGoodKey"
>> earthquake_enabled = 1
>>
>> Looking at the Belchertown extension installer I see that HTML_ROOT is 
>> normally be set to HTML_ROOT = belchertown, but in that case that would 
>> put the Belchertown generated files in /usr/share/weewx/belchertown, I 
>> think it will be easier to keep them close to the rest of the generated 
>> output in /var/www/html/weewx. 
>>
>> Leave debug = 1 in weewx.conf for the time being. I would also delete 
>> the contents of the /var/www/html/weewx directory so we can be certain 
>> it is all freshly generated. Once the [StdReport] changes have been made 
>> and /var/www/html/weewx cleared of content, restart WeeWX and let it run 
>> for a couple of archive intervals. Check the NOAA reports for completeness. 
>> If both the Standard and Belchertown NOAA files are missing data than then 
>> the problem is something wider than either report. In which case please 
>> post a copy of the log from when WeeWX was restarted and we will take it 
>> from there.
>>
>> Gary
>>
>> On Monday, 4 February 2019 08:10:15 UTC+10, Pat wrote:
>>>
>>> The Belchertown skin shouldn't be altering the skin settings of other 
>>> skins. The exception is the Highcharts_Belchertown skin (which I refer to 
>>> as a subskin). However, the Belchertown skin does ship with its own NOAA 
>>> report templates - which are borrowed from the Standard skin. Exact 
>>> copy/paste from Standard. 
>>>
>>> Gary might be onto something Torrin. Maybe reset the entire StdReport 
>>> section back to default, restart weewx and see what happens?
>>>
>>>
>>>
>>> On Sunday, February 3, 2019 at 4:54:37 

[weewx-user] Re: NOAA Reports Belchertown Skin

[torrin]

Thanks guys, I am travelling and will be away from my pi until Thursday, I 
will try the suggested changes then and report back.

Thanks!

On Sunday, February 3, 2019 at 10:47:42 PM UTC-6, gjr80 wrote:
>
> I agree with Pat that some changes are needed to [StdReport]. I don't 
> expect the Belchertown extension would be interfering with other skins, but 
> for some reason it appears that a number of settings in [StdReport] have 
> changed from default and would appear to be conflicting (the conflicts may 
> not be the cause of the problem but they certainly limit troubleshooting). 
> We should have been seeing [[StandardReport]] and [[Belchertown]] both 
> producing NOAA format reports. Unfortunately the skin = Belchertown 
> setting under [[StandardReport]] meant that the Standard skin was never 
> called. As it turns out even if [[StandardReport]] had skin = Standard we 
> would not have had any Standard skin NOAA reports to look at as the HTML_ROOT 
> = /var/www/html/weewx appearing under [StdReport] and [[Belchertown]] 
> would mean that all NOAA reports (whether from the Standard skin or 
> Belchertown skin would have gone to /var/www/html/weewx/NOAA and since 
> the Belchertown report was listed after StandardReport the Belchertown NOAA 
> files would have overwritten those generated by StandardReport.
>
> I suggest a few changes to [StdReport] so we can see if both the Standard 
> skin and Belchertown are having the same problem generating the NOAA 
> reports. Based on the Belchertown and WeeWX defaults I would change 
> [StdReport] to be:
>
> [StdReport]
>
> # Where the skins reside, relative to WEEWX_ROOT
> SKIN_ROOT = /etc/weewx/skins
>
> # Where the generated reports should go, relative to WEEWX_ROOT
> HTML_ROOT = /var/www/html/weewx
>
> # The database binding indicates which data should be used in reports.
> data_binding = wx_binding
>
> # Each of the following subsections defines a report that will be run.
>
> [[StandardReport]]
> # See the customizing guide to change the units, plot types and line
> # colors, modify the fonts, display additional sensor data, and other
> # customizations. Many of those changes can be made here by overriding
> # parameters, or by modifying templates within the skin itself.
>
> # The StandardReport uses the 'Standard' skin, which contains the
> # images, templates and plots for the report.
> skin = Standard
> [[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 = "mydomain.com"
> forecast_enabled = 1
> darksky_secret_key = "MyGoodKey"
> earthquake_enabled = 1
>
> Looking at the Belchertown extension installer I see that HTML_ROOT is 
> normally be set to HTML_ROOT = belchertown, but in that case that would 
> put the Belchertown generated files in /usr/share/weewx/belchertown, I 
> think it will be easier to keep them close to the rest of the generated 
> output in /var/www/html/weewx. 
>
> Leave debug = 1 in weewx.conf for the time being. I would also delete the 
> contents of the /var/www/html/weewx directory so we can be certain it is 
> all freshly generated. Once the [StdReport] changes have been made and 
> /var/www/html/weewx cleared of content, restart WeeWX and let it run for 
> a couple of archive intervals. Check the NOAA reports for completeness. If 
> both the Standard and Belchertown NOAA files are missing data than then the 
> problem is something wider than either report. In which case please post a 
> copy of the log from when WeeWX was restarted and we will take it from 
> there.
>
> Gary
>
> On Monday, 4 February 2019 08:10:15 UTC+10, Pat wrote:
>>
>> The Belchertown skin shouldn't be altering the skin settings of other 
>> skins. The exception is the Highcharts_Belchertown skin (which I refer to 
>> as a subskin). However, the Belchertown skin does ship with its own NOAA 
>> report templates - which are borrowed from the Standard skin. Exact 
>> copy/paste from Standard. 
>>
>> Gary might be onto something Torrin. Maybe reset the entire StdReport 
>> section back to default, restart weewx and see what happens?
>>
>>
>>
>> On Sunday, February 3, 2019 at 4:54:37 PM UTC-5, tor...@torrin.org wrote:
>>>
>>> Yup, I noticed that and just commented out the StdReport, same results 
>>> (no new data in NOAA reports), though it only runs the skin once.
>>>
>>> On Sunday, February 3, 2019 at 3:41:58 PM UTC-6, gjr80 wrote:

 So WeeWX is generating archive records with data and saving them to 
 archive. Looking at weewx.conf I notice you are not running the Standard 
 skin:

 [[StandardReport]]
 # See the customizing guide to change the units, plot types and 
 

[weewx-user] Re: NOAA Reports Belchertown Skin

[gjr80]

I agree with Pat that some changes are needed to [StdReport]. I don't 
expect the Belchertown extension would be interfering with other skins, but 
for some reason it appears that a number of settings in [StdReport] have 
changed from default and would appear to be conflicting (the conflicts may 
not be the cause of the problem but they certainly limit troubleshooting). 
We should have been seeing [[StandardReport]] and [[Belchertown]] both 
producing NOAA format reports. Unfortunately the skin = Belchertown setting 
under [[StandardReport]] meant that the Standard skin was never called. As 
it turns out even if [[StandardReport]] had skin = Standard we would not 
have had any Standard skin NOAA reports to look at as the HTML_ROOT = 
/var/www/html/weewx appearing under [StdReport] and [[Belchertown]] would 
mean that all NOAA reports (whether from the Standard skin or Belchertown 
skin would have gone to /var/www/html/weewx/NOAA and since the Belchertown 
report was listed after StandardReport the Belchertown NOAA files would 
have overwritten those generated by StandardReport.

I suggest a few changes to [StdReport] so we can see if both the Standard 
skin and Belchertown are having the same problem generating the NOAA 
reports. Based on the Belchertown and WeeWX defaults I would change 
[StdReport] to be:

[StdReport]

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

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

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

# Each of the following subsections defines a report that will be run.

[[StandardReport]]
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

# The StandardReport uses the 'Standard' skin, which contains the
# images, templates and plots for the report.
skin = Standard
[[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 = "mydomain.com"
forecast_enabled = 1
darksky_secret_key = "MyGoodKey"
earthquake_enabled = 1

Looking at the Belchertown extension installer I see that HTML_ROOT is 
normally be set to HTML_ROOT = belchertown, but in that case that would put 
the Belchertown generated files in /usr/share/weewx/belchertown, I think it 
will be easier to keep them close to the rest of the generated output in 
/var/www/html/weewx. 

Leave debug = 1 in weewx.conf for the time being. I would also delete the 
contents of the /var/www/html/weewx directory so we can be certain it is 
all freshly generated. Once the [StdReport] changes have been made and 
/var/www/html/weewx cleared of content, restart WeeWX and let it run for a 
couple of archive intervals. Check the NOAA reports for completeness. If 
both the Standard and Belchertown NOAA files are missing data than then the 
problem is something wider than either report. In which case please post a 
copy of the log from when WeeWX was restarted and we will take it from 
there.

Gary

On Monday, 4 February 2019 08:10:15 UTC+10, Pat wrote:
>
> The Belchertown skin shouldn't be altering the skin settings of other 
> skins. The exception is the Highcharts_Belchertown skin (which I refer to 
> as a subskin). However, the Belchertown skin does ship with its own NOAA 
> report templates - which are borrowed from the Standard skin. Exact 
> copy/paste from Standard. 
>
> Gary might be onto something Torrin. Maybe reset the entire StdReport 
> section back to default, restart weewx and see what happens?
>
>
>
> On Sunday, February 3, 2019 at 4:54:37 PM UTC-5, tor...@torrin.org wrote:
>>
>> Yup, I noticed that and just commented out the StdReport, same results 
>> (no new data in NOAA reports), though it only runs the skin once.
>>
>> On Sunday, February 3, 2019 at 3:41:58 PM UTC-6, gjr80 wrote:
>>>
>>> So WeeWX is generating archive records with data and saving them to 
>>> archive. Looking at weewx.conf I notice you are not running the Standard 
>>> skin:
>>>
>>> [[StandardReport]]
>>> # See the customizing guide to change the units, plot types and 
>>> line
>>> # colors, modify the fonts, display additional sensor data, and 
>>> other
>>> # customizations. Many of those changes can be made here by 
>>> overriding
>>> # parameters, or by modifying templates within the skin itself.
>>>
>>> # The StandardReport uses the 'Standard' skin, which contains the
>>> # images, 

[weewx-user] Re: NOAA Reports Belchertown Skin

[Pat]

The Belchertown skin shouldn't be altering the skin settings of other 
skins. The exception is the Highcharts_Belchertown skin (which I refer to 
as a subskin). However, the Belchertown skin does ship with its own NOAA 
report templates - which are borrowed from the Standard skin. Exact 
copy/paste from Standard. 

Gary might be onto something Torrin. Maybe reset the entire StdReport 
section back to default, restart weewx and see what happens?



On Sunday, February 3, 2019 at 4:54:37 PM UTC-5, tor...@torrin.org wrote:
>
> Yup, I noticed that and just commented out the StdReport, same results (no 
> new data in NOAA reports), though it only runs the skin once.
>
> On Sunday, February 3, 2019 at 3:41:58 PM UTC-6, gjr80 wrote:
>>
>> So WeeWX is generating archive records with data and saving them to 
>> archive. Looking at weewx.conf I notice you are not running the Standard 
>> skin:
>>
>> [[StandardReport]]
>> # See the customizing guide to change the units, plot types and 
>> line
>> # colors, modify the fonts, display additional sensor data, and 
>> other
>> # customizations. Many of those changes can be made here by 
>> overriding
>> # parameters, or by modifying templates within the skin itself.
>>
>> # The StandardReport uses the 'Standard' skin, which contains the
>> # images, templates and plots for the report.
>> skin = Belchertown
>>
>> So you are actually running the Belchertown skin twice, once under 
>> [[StandardReport]] and once again under [[Belchertown]]? I know little 
>> detail of how the Belchertown skin works but this does not seem right to 
>> me, one skin should not be altering the settings of another. It will 
>> certainly prevent the Standard skin NOAA reports from being run. I cannot 
>> speak for the Belchertown skin.
>>
>> 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

[torrin]

Yup, I noticed that and just commented out the StdReport, same results (no 
new data in NOAA reports), though it only runs the skin once.

On Sunday, February 3, 2019 at 3:41:58 PM UTC-6, gjr80 wrote:
>
> So WeeWX is generating archive records with data and saving them to 
> archive. Looking at weewx.conf I notice you are not running the Standard 
> skin:
>
> [[StandardReport]]
> # See the customizing guide to change the units, plot types and 
> line
> # colors, modify the fonts, display additional sensor data, and 
> other
> # customizations. Many of those changes can be made here by 
> overriding
> # parameters, or by modifying templates within the skin itself.
>
> # The StandardReport uses the 'Standard' skin, which contains the
> # images, templates and plots for the report.
> skin = Belchertown
>
> So you are actually running the Belchertown skin twice, once under 
> [[StandardReport]] and once again under [[Belchertown]]? I know little 
> detail of how the Belchertown skin works but this does not seem right to 
> me, one skin should not be altering the settings of another. It will 
> certainly prevent the Standard skin NOAA reports from being run. I cannot 
> speak for the Belchertown skin.
>
> 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

[gjr80]

So WeeWX is generating archive records with data and saving them to archive. 
Looking at weewx.conf I notice you are not running the Standard skin:

[[StandardReport]]
# See the customizing guide to change the units, plot types and line
# colors, modify the fonts, display additional sensor data, and other
# customizations. Many of those changes can be made here by overriding
# parameters, or by modifying templates within the skin itself.

# The StandardReport uses the 'Standard' skin, which contains the
# images, templates and plots for the report.
skin = Belchertown

So you are actually running the Belchertown skin twice, once under 
[[StandardReport]] and once again under [[Belchertown]]? I know little detail 
of how the Belchertown skin works but this does not seem right to me, one skin 
should not be altering the settings of another. It will certainly prevent the 
Standard skin NOAA reports from being run. I cannot speak for the Belchertown 
skin.

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

[torrin]

weewx is 3.8.2 and I am using sqlite3 v3.7.17

All other data seems to plot well in the standard skin when I was using it 
and in Belchertown, so the data is being written.  I am not currently 
capture barometric pressure, but I do not even see that in the NOAA reports.
.
On Sunday, February 3, 2019 at 1:30:45 PM UTC-6, Pat wrote:
>
> Yeah, I don't think it's the skin either. You do appear to have some data 
> though but it seems to be spotty. Your LOOPs look good and your RECs do 
> too. I'm a bit at a loss too. 
>
> What version of weewx and what database type are you using (sqlite or 
> mysql)?   
>

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

[Pat]

Yeah, I don't think it's the skin either. You do appear to have some data 
though but it seems to be spotty. Your LOOPs look good and your RECs do 
too. I'm a bit at a loss too. 

What version of weewx and what database type are you using (sqlite or 
mysql)?

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

[torrin]

Oh and I am 100% convinced it is not the Belchertown skin.

On Sunday, February 3, 2019 at 1:09:56 PM UTC-6, tor...@torrin.org wrote:
>
> I am running 0.8.2, here are the files:
>
> cd /var/www/html/weewx/NOAA/
> [root@localhost NOAA]# ls -ltr
> total 12
> -rw-r--r--. 1 root root 1037 Feb  2 22:31 NOAA-2019-01.txt
> -rw-r--r--. 1 root root 1788 Feb  3 13:05 NOAA-2019.txt
> -rw-r--r--. 1 root root  857 Feb  3 13:05 NOAA-2019-02.txt
> [root@localhost NOAA]# cat NOAA-2019.txt
>  CLIMATOLOGICAL SUMMARY for year 2019
>
>
> NAME: Nolensville, Tennessee
> ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W
>
>
>TEMPERATURE (F)
>
>   HEATCOOL  
> MAXMAXMINMIN
>   MEAN   MEAN DEG DEG
> >= <= <= <=
>  YR  MO   MAXMINMEAN  DAYSDAYS  HI  DAY LOW  DAY
>  90 32 32  0
>
> 
> 2019 01   30.6   18.1   28.1  116.70.041.7   3115.8   30  
> 0  2  3  0
> 2019 02
> 2019 03
> 2019 04
> 2019 05
> 2019 06
> 2019 07
> 2019 08
> 2019 09
> 2019 10
> 2019 11
> 2019 12
>
> 
>   45.2   31.2   43.2  157.30.064.6  Feb15.8  Jan  
> 0  2  3  0
>
>
>   PRECIPITATION (in)
>
>   MAX ---DAYS OF RAIN---
>   OBS.   OVER
>  YR  MO  TOTALDAY  DATE   0.01   0.10   1.00
> 
> 2019 01   0.00   0.0029  0  0  0
> 2019 02
> 2019 03
> 2019 04
> 2019 05
> 2019 06
> 2019 07
> 2019 08
> 2019 09
> 2019 10
> 2019 11
> 2019 12
> 
>   0.00   0.00   Jan  0  0  0
>
>
>WIND SPEED (mph)
>
> DOM
>  YR  MOAVG HI   DATEDIR
> ---
> 2019 011.1   11.4 30 89
> 2019 02
> 2019 03
> 2019 04
> 2019 05
> 2019 06
> 2019 07
> 2019 08
> 2019 09
> 2019 10
> 2019 11
> 2019 12
> ---
>1.0   12.5Feb110
>
> [root@localhost NOAA]# cat NOAA-2019-02.txt
>MONTHLY CLIMATOLOGICAL SUMMARY for Feb 2019
>
>
> NAME: Nolensville, Tennessee
> ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W
>
>
>TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND  
>  DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
>  TIMEDIR
>
> ---
>  01
>  02
>  03
>  04
>  05
>  06
>  07
>  08
>  09
>  10
>  11
>  12
>  13
>  14
>  15
>  16
>  17
>  18
>  19
>  20
>  21
>  22
>  23
>  24
>  25
>  26
>  27
>  28
>
> ---
>   51.0   64.6 03   40.5 01   40.60.0   0.000.9   12.5  
>01119
>
>
> cat NOAA-2019-01.txt
>MONTHLY CLIMATOLOGICAL SUMMARY for Jan 2019
>
>
> NAME: Nolensville, Tennessee
> ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W
>
>
>TEMPERATURE (F), RAIN (in), WIND SPEED (mph)
>
>  HEAT   COOL AVG
>   MEAN   DEGDEG  WIND  
>  DOM
> DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
>  TIMEDIR
>
> ---
>  01
>  02
>  03
>  04
>  05
>  06
>  07
>  08
>  09
>  10
>  11
>  12
>  13
>  14
>  15
>  16
>  17
>  18
>  19
>  20
>  21
>  22
>  23
>  24
>  25
>  26
>  27
>  28
>  29
>  30   20.2   24.1  10:34   15.8  21:21   44.80.0   0.001.3   11.4  
> 08:30 39
>  31   34.3   41.7  23:16   15.8  01:18   30.70.0   0.001.16.8  
> 21:06117
>
> ---
>   28.1   41.7 31   15.8 30  116.70.0   0.001.1   11.4  
>30 89
>
>
> On Sunday, February 3, 2019 at 12:21:57 PM UTC-6, Pat wrote:
>>
>> Just curious, what version of Belchertown skin are you running? I don't 
>> see it outputting the version number in your log file which tells me you 
>> may be a few versions old. I'd say upgrade to the latest release 
>>  0.8.2, but I'm 
>> finalizing a 0.9 release which should be out in the next few days. 
>>
>> To back up a bit - I haven't thought 

[weewx-user] Re: NOAA Reports Belchertown Skin

[torrin]

I am running 0.8.2, here are the files:

cd /var/www/html/weewx/NOAA/
[root@localhost NOAA]# ls -ltr
total 12
-rw-r--r--. 1 root root 1037 Feb  2 22:31 NOAA-2019-01.txt
-rw-r--r--. 1 root root 1788 Feb  3 13:05 NOAA-2019.txt
-rw-r--r--. 1 root root  857 Feb  3 13:05 NOAA-2019-02.txt
[root@localhost NOAA]# cat NOAA-2019.txt
 CLIMATOLOGICAL SUMMARY for year 2019


NAME: Nolensville, Tennessee
ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W


   TEMPERATURE (F)

  HEATCOOL  
MAXMAXMINMIN
  MEAN   MEAN DEG DEG
>= <= <= <=
 YR  MO   MAXMINMEAN  DAYSDAYS  HI  DAY LOW  DAY
 90 32 32  0

2019 01   30.6   18.1   28.1  116.70.041.7   3115.8   30  
0  2  3  0
2019 02
2019 03
2019 04
2019 05
2019 06
2019 07
2019 08
2019 09
2019 10
2019 11
2019 12

  45.2   31.2   43.2  157.30.064.6  Feb15.8  Jan  
0  2  3  0


  PRECIPITATION (in)

  MAX ---DAYS OF RAIN---
  OBS.   OVER
 YR  MO  TOTALDAY  DATE   0.01   0.10   1.00

2019 01   0.00   0.0029  0  0  0
2019 02
2019 03
2019 04
2019 05
2019 06
2019 07
2019 08
2019 09
2019 10
2019 11
2019 12

  0.00   0.00   Jan  0  0  0


   WIND SPEED (mph)

DOM
 YR  MOAVG HI   DATEDIR
---
2019 011.1   11.4 30 89
2019 02
2019 03
2019 04
2019 05
2019 06
2019 07
2019 08
2019 09
2019 10
2019 11
2019 12
---
   1.0   12.5Feb110

[root@localhost NOAA]# cat NOAA-2019-02.txt
   MONTHLY CLIMATOLOGICAL SUMMARY for Feb 2019


NAME: Nolensville, Tennessee
ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W


   TEMPERATURE (F), RAIN (in), WIND SPEED (mph)

 HEAT   COOL AVG
  MEAN   DEGDEG  WIND  
 DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
 TIMEDIR
---
 01
 02
 03
 04
 05
 06
 07
 08
 09
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
---
  51.0   64.6 03   40.5 01   40.60.0   0.000.9   12.5  
   01119


cat NOAA-2019-01.txt
   MONTHLY CLIMATOLOGICAL SUMMARY for Jan 2019


NAME: Nolensville, Tennessee
ELEV: 680 feetLAT: 35-55.20 NLONG: 086-41.46 W


   TEMPERATURE (F), RAIN (in), WIND SPEED (mph)

 HEAT   COOL AVG
  MEAN   DEGDEG  WIND  
 DOM
DAY   TEMP   HIGH   TIMELOW   TIME   DAYS   DAYS   RAIN  SPEED   HIGH  
 TIMEDIR
---
 01
 02
 03
 04
 05
 06
 07
 08
 09
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30   20.2   24.1  10:34   15.8  21:21   44.80.0   0.001.3   11.4  
08:30 39
 31   34.3   41.7  23:16   15.8  01:18   30.70.0   0.001.16.8  
21:06117
---
  28.1   41.7 31   15.8 30  116.70.0   0.001.1   11.4  
   30 89


On Sunday, February 3, 2019 at 12:21:57 PM UTC-6, Pat wrote:
>
> Just curious, what version of Belchertown skin are you running? I don't 
> see it outputting the version number in your log file which tells me you 
> may be a few versions old. I'd say upgrade to the latest release 
>  0.8.2, but I'm 
> finalizing a 0.9 release which should be out in the next few days. 
>
> To back up a bit - I haven't thought about an hourly forecast - but you're 
> right, the data's there. Let me think about how to incorporate it that 
> works with the simplicity of the skin. Maybe a sub page. Hmm.
>
> Back to the NOAA file issue. Files are being generated, but nothing within 
> them? Can you attach one of them here?
>
>
> On Sunday, February 3, 2019 at 12:20:46 PM UTC-5, tor...@torrin.org wrote:
>>
>> Here is the output to the screen when running weewxd:
>>
>> weewxd /etc/weewx/weewx.conf -n TRACKER /etc/weewx/weewx.conf
>> 

[weewx-user] Re: NOAA Reports Belchertown Skin

[Pat]

Just curious, what version of Belchertown skin are you running? I don't see 
it outputting the version number in your log file which tells me you may be 
a few versions old. I'd say upgrade to the latest release 
 0.8.2, but I'm 
finalizing a 0.9 release which should be out in the next few days. 

To back up a bit - I haven't thought about an hourly forecast - but you're 
right, the data's there. Let me think about how to incorporate it that 
works with the simplicity of the skin. Maybe a sub page. Hmm.

Back to the NOAA file issue. Files are being generated, but nothing within 
them? Can you attach one of them here?


On Sunday, February 3, 2019 at 12:20:46 PM UTC-5, tor...@torrin.org wrote:
>
> Here is the output to the screen when running weewxd:
>
> weewxd /etc/weewx/weewx.conf -n TRACKER /etc/weewx/weewx.conf
> LOOP:   2019-02-03 11:03:28 CST (1549213408) appTemp: 61.5912522388, 
> cloudbase: 3116.86206104, dateTime: 1549213408, dewpoint: 52.0578069314, 
> heatindex: 62.78, humidex: 66.0646331192, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.78, outTempBatteryStatus: 0, radiation: 341.332785, rain: 
> None, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 2.0, windchill: 
> 62.78, windDir: 112.0, windGust: 3.42252103347, windSpeed: 3.27935675494
> LOOP:   2019-02-03 11:03:44 CST (1549213424) appTemp: 61.1197809308, 
> cloudbase: 3114.97201301, dateTime: 1549213424, dewpoint: 51.8861231428, 
> heatindex: 62.6, humidex: 65.799945974, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.6, outTempBatteryStatus: 0, radiation: 385.131042, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
> 62.6, windDir: 129.0, windGust: 4.56336137796, windSpeed: 3.70884959052
> LOOP:   2019-02-03 11:04:00 CST (1549213440) appTemp: 60.6384609308, 
> cloudbase: 3114.97201301, dateTime: 1549213440, dewpoint: 51.8861231428, 
> heatindex: 62.6, humidex: 65.799945974, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.6, outTempBatteryStatus: 0, radiation: 425.132766, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
> 62.6, windDir: 127.0, windGust: 5.70420172245, windSpeed: 4.56336137796
> LOOP:   2019-02-03 11:04:16 CST (1549213456) appTemp: 61.1440786973, 
> cloudbase: 3111.19406503, dateTime: 1549213456, dewpoint: 51.5427461139, 
> heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 450.21672, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
> 62.24, windDir: 105.0, windGust: 4.56336137796, windSpeed: 2.85210086122
> LOOP:   2019-02-03 11:04:32 CST (1549213472) appTemp: 62.1079786973, 
> cloudbase: 3111.19406503, dateTime: 1549213472, dewpoint: 51.5427461139, 
> heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 459.388386, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
> 62.24, windDir: 135.0, windGust: 2.28168068898, windSpeed: 1.14084034449
> LOOP:   2019-02-03 11:04:48 CST (1549213488) appTemp: 61.2247186973, 
> cloudbase: 3111.19406503, dateTime: 1549213488, dewpoint: 51.5427461139, 
> heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 440.303112, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
> 62.24, windDir: 128.0, windGust: 3.42252103347, windSpeed: 2.7089365827
> LOOP:   2019-02-03 11:05:04 CST (1549213504) appTemp: 60.3414586973, 
> cloudbase: 3111.19406503, dateTime: 1549213504, dewpoint: 51.5427461139, 
> heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 456.823161, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
> 62.24, windDir: 113.0, windGust: 6.84504206693, windSpeed: 4.27703282091
> LOOP:   2019-02-03 11:05:20 CST (1549213520) appTemp: 60.3533852058, 
> cloudbase: 3109.30616512, dateTime: 1549213520, dewpoint: 51.3710528735, 
> heatindex: 62.06, humidex: 65.0087672443, maxSolarRad: None, outHumidity: 
> 68.0, outTemp: 62.06, outTempBatteryStatus: 0, radiation: 463.303314, rain: 
> 0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
> 62.06, windDir: 89.0, windGust: 5.70420172245, windSpeed: 3.84977692719
> REC:2019-02-03 11:05:00 CST (1549213500) appTemp: 61.3043783654, 
> cloudbase: 3113.39804702, dateTime: 1549213500.0, dewpoint: 51.7430485931, 
> ET: 0.000565469569265, heatindex: 62.45, humidex: 65.5800952241, interval: 
> 5, maxSolarRad: None, outHumidity: 68.0, outTemp: 62.45, 
> outTempBatteryStatus: 0.0, radiation: 416.9174685, rain: 0.0, rain_total: 
> 134.112, rainRate: 0.0, usUnits: 1, UV: 3.167, windchill: 62.45, 
> windDir: 121.955999296, windGust: 5.70420172245, 

[weewx-user] Re: NOAA Reports Belchertown Skin

[torrin]

Here is the output to the screen when running weewxd:

weewxd /etc/weewx/weewx.conf -n TRACKER /etc/weewx/weewx.conf
LOOP:   2019-02-03 11:03:28 CST (1549213408) appTemp: 61.5912522388, 
cloudbase: 3116.86206104, dateTime: 1549213408, dewpoint: 52.0578069314, 
heatindex: 62.78, humidex: 66.0646331192, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.78, outTempBatteryStatus: 0, radiation: 341.332785, rain: 
None, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 2.0, windchill: 
62.78, windDir: 112.0, windGust: 3.42252103347, windSpeed: 3.27935675494
LOOP:   2019-02-03 11:03:44 CST (1549213424) appTemp: 61.1197809308, 
cloudbase: 3114.97201301, dateTime: 1549213424, dewpoint: 51.8861231428, 
heatindex: 62.6, humidex: 65.799945974, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.6, outTempBatteryStatus: 0, radiation: 385.131042, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
62.6, windDir: 129.0, windGust: 4.56336137796, windSpeed: 3.70884959052
LOOP:   2019-02-03 11:04:00 CST (1549213440) appTemp: 60.6384609308, 
cloudbase: 3114.97201301, dateTime: 1549213440, dewpoint: 51.8861231428, 
heatindex: 62.6, humidex: 65.799945974, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.6, outTempBatteryStatus: 0, radiation: 425.132766, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
62.6, windDir: 127.0, windGust: 5.70420172245, windSpeed: 4.56336137796
LOOP:   2019-02-03 11:04:16 CST (1549213456) appTemp: 61.1440786973, 
cloudbase: 3111.19406503, dateTime: 1549213456, dewpoint: 51.5427461139, 
heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 450.21672, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.24, windDir: 105.0, windGust: 4.56336137796, windSpeed: 2.85210086122
LOOP:   2019-02-03 11:04:32 CST (1549213472) appTemp: 62.1079786973, 
cloudbase: 3111.19406503, dateTime: 1549213472, dewpoint: 51.5427461139, 
heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 459.388386, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.24, windDir: 135.0, windGust: 2.28168068898, windSpeed: 1.14084034449
LOOP:   2019-02-03 11:04:48 CST (1549213488) appTemp: 61.2247186973, 
cloudbase: 3111.19406503, dateTime: 1549213488, dewpoint: 51.5427461139, 
heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 440.303112, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 3.0, windchill: 
62.24, windDir: 128.0, windGust: 3.42252103347, windSpeed: 2.7089365827
LOOP:   2019-02-03 11:05:04 CST (1549213504) appTemp: 60.3414586973, 
cloudbase: 3111.19406503, dateTime: 1549213504, dewpoint: 51.5427461139, 
heatindex: 62.24, humidex: 65.2720154258, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.24, outTempBatteryStatus: 0, radiation: 456.823161, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.24, windDir: 113.0, windGust: 6.84504206693, windSpeed: 4.27703282091
LOOP:   2019-02-03 11:05:20 CST (1549213520) appTemp: 60.3533852058, 
cloudbase: 3109.30616512, dateTime: 1549213520, dewpoint: 51.3710528735, 
heatindex: 62.06, humidex: 65.0087672443, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.06, outTempBatteryStatus: 0, radiation: 463.303314, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.06, windDir: 89.0, windGust: 5.70420172245, windSpeed: 3.84977692719
REC:2019-02-03 11:05:00 CST (1549213500) appTemp: 61.3043783654, 
cloudbase: 3113.39804702, dateTime: 1549213500.0, dewpoint: 51.7430485931, 
ET: 0.000565469569265, heatindex: 62.45, humidex: 65.5800952241, interval: 
5, maxSolarRad: None, outHumidity: 68.0, outTemp: 62.45, 
outTempBatteryStatus: 0.0, radiation: 416.9174685, rain: 0.0, rain_total: 
134.112, rainRate: 0.0, usUnits: 1, UV: 3.167, windchill: 62.45, 
windDir: 121.955999296, windGust: 5.70420172245, windGustDir: 127.0, 
windrun: 13.2957366953, windSpeed: 3.04224091864
LOOP:   2019-02-03 11:05:36 CST (1549213536) appTemp: 61.1560052058, 
cloudbase: 3109.30616512, dateTime: 1549213536, dewpoint: 51.3710528735, 
heatindex: 62.06, humidex: 65.0087672443, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.06, outTempBatteryStatus: 0, radiation: 465.876432, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.06, windDir: 111.0, windGust: 3.42252103347, windSpeed: 2.4248449675
LOOP:   2019-02-03 11:05:52 CST (1549213552) appTemp: 60.0320852058, 
cloudbase: 3109.30616512, dateTime: 1549213552, dewpoint: 51.3710528735, 
heatindex: 62.06, humidex: 65.0087672443, maxSolarRad: None, outHumidity: 
68.0, outTemp: 62.06, outTempBatteryStatus: 0, radiation: 465.016095, rain: 
0.0, rain_total: 134.112, rainRate: 0, usUnits: 1, UV: 4.0, windchill: 
62.06, 

[weewx-user] Re: NOAA Reports Belchertown Skin

[torrin]

No modification to the standard skin at all, I checked the file stamps and 
all are from August of last year (I installed on a few weeks ago)

I do indeed have debug = 1 set in my weewx config, I have always felt the 
info put in the log is light for debug mode being on.  I tried removing the 
space between the " = " and there was a trailing space on the line entry, 
both did not yield more output on restart. I think deleted the debug line 
and re-added it and it magically worked?  Weird, but better output now.

*I have attached the output running "weewxd /etc/weewx/weewx.conf -n 
TRACKER" and my weewx.conf file.*


On Sunday, February 3, 2019 at 1:11:30 AM UTC-6, gjr80 wrote:
>
> 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.
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Initializing weewx version 
3.8.2
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Using Python 2.7.5 (default, 
Oct 31 2018, 20:11:09)
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Platform 
Linux-4.14.91-v7.1.el7-armv7l-with-centos-7.6.1810-AltArch
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Locale is 'en_US.UTF-8'
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Using configuration file 
/etc/weewx/weewx.conf
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Debug is 1
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Initializing engine
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading station type SDR 
(user.sdr)
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: MainThread: driver version is 0.54
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: MainThread: sensor map is 
{'outTemp': 'temperature.41.FOWH65BPacket', 'outHumidity': 
'humidity.41.FOWH65BPacket', 'windDir': 'wind_dir.41.FOWH65BPacket', 
'windSpeed': 'wind_speed.41.FOWH65BPacket', 'windGust': 
'wind_gust.41.FOWH65BPacket', 'rain_total': 'rain_total.41.FOWH65BPacket', 
'UV': 'uv_index.41.FOWH65BPacket', 'radiation': 'light.41.FOWH65BPacket', 
'outTempBatteryStatus': 'battery.41.FOWH65BPacket', 'cloudBase': 
'cloudbase.41.FOWH65BPacket', 'appTemp': 'appTemp.41.FOWH65BPacket'}
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: MainThread: deltas is {'rain': 
'rain_total'}
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: MainThread: startup process 
'rtl_433 -q -M utc -F json -p 39.741 -R 78 -f 91498'
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: stdout-thread: start async reader 
for stdout-thread
Feb 03 11:03:19 localhost TRACKER[4407]: sdr: stderr-thread: start async reader 
for stderr-thread
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading service 
weewx.engine.StdTimeSynch
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Finished loading service 
weewx.engine.StdTimeSynch
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading service 
weewx.engine.StdConvert
Feb 03 11:03:19 localhost TRACKER[4407]: engine: StdConvert target unit is 0x1
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Finished loading service 
weewx.engine.StdConvert
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading service 
weewx.engine.StdCalibrate
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Finished loading service 
weewx.engine.StdCalibrate
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading service 
weewx.engine.StdQC
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Finished loading service 
weewx.engine.StdQC
Feb 03 11:03:19 localhost TRACKER[4407]: engine: Loading service 
weewx.wxservices.StdWXCalculate
Feb 03 11:03:19 localhost TRACKER[4407]: wxcalculate: The following values will 
be calculated: barometer=prefer_hardware, 

[weewx-user] Re: NOAA Reports Belchertown Skin

[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

[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

[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

[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

[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

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

[weewx-user] Re: NOAA Reports Belchertown Skin

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

[weewx-user] Re: NOAA Reports Belchertown Skin

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