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

Reply via email to