Darksky updates once an hour.

On Monday, November 26, 2018 at 6:45:56 PM UTC-5, Pat wrote:
>
> Interesting. OK.
>
> Also, the 8 day forecast is part of darksky, not highcharts. Does that 
> work when Belchertown is the skin?
>
>
>
> On Monday, November 26, 2018 at 5:50:12 PM UTC-5, rich T wrote:
>>
>> Pat
>>
>> Don't know if this will help, but if I change the skin to point 
>> to Highcharts_Belchertown and include the extras, everything works except 
>> the 8 Day Forecast.
>>
>> Rich
>>
>> On Monday, November 26, 2018 at 4:39:25 PM UTC-5, Pat wrote:
>>>
>>> I noticed it said it moved 0 files too. Don't know why though - there is 
>>> no other information. In my standard report I have this below as an example 
>>> where both skins are copying data to the same html folder. 
>>>
>>> I assume you have both skins outlined in weewx.conf similar to the below?
>>>
>>> I'm still a little lost since there's not much data to go off of quite 
>>> yet. 
>>>
>>>     [[Belchertown]]
>>>         skin = Belchertown
>>>         HTML_ROOT = /var/www/html/belchertown
>>>         [[[Extras]]]
>>>             logo_image = https://
>>> belchertownweather.com/images/content/btownwx-logo-slim.png
>>>             show_apptemp = 0
>>>             show_windrun = 1
>>>             forecast_enabled = 1
>>>             darksky_secret_key = 123
>>>             earthquake_enabled = 1
>>>
>>>     [[Highcharts_Belchertown]]
>>>         HTML_ROOT = /var/www/html/belchertown
>>>         skin = Highcharts_Belchertown
>>>
>>>
>>> On Sunday, November 25, 2018 at 10:02:14 PM UTC-5, rich T wrote:
>>>>
>>>> Pat
>>>>
>>>> I don't mind being a beta tester.  :)  I cleaned up the extra newlines 
>>>> within weewx.conf file and restarted weewx and allowed to run several 
>>>> archive periods, the charts did not updated.  I rebooted the RPI and 
>>>> allowed to run several archive periods, again the charts did not updated. 
>>>> What I do notice in the sys_log after the files for the 
>>>> Highcharts_Belchertown report are generated, zero files are being copied 
>>>> to 
>>>> the  /home/weewx/public_html/belchertown.    
>>>>
>>>> Nov 25 21:40:40 raspberrypi weewx[546]: cheetahgenerator: Generated 4 
>>>> files for report Highcharts_Belchertown in 7.62 seconds
>>>> Nov 25 21:40:40 raspberrypi weewx[546]: copygenerator: copied 0 files 
>>>> to /home/weewx/public_html/belchertown
>>>>
>>>> In the [[StandardReport]] does the skin need to point Belchertown? 
>>>> Could it point to Highcharts_Belchertown?
>>>>
>>>> Thanks
>>>> Rich
>>>>
>>>>
>>>> On Sunday, November 25, 2018 at 8:06:58 PM UTC-5, Pat wrote:
>>>>>
>>>>> 0.8 isn't released yet so I guess you've become a beta tester. :)
>>>>>
>>>>> You have 2 options. You can downgrade to the supported 0.7 release 
>>>>> <https://github.com/poblabs/weewx-belchertown/releases>, or we can 
>>>>> try to figure out what's wrong together.
>>>>>
>>>>> If you choose the latter, I notice your syslog doesn't show any 
>>>>> glaring errors. However, I do see some spacing in your weewx.conf which 
>>>>> may 
>>>>> be the problem?
>>>>>
>>>>> Check out this link for a good config example within weewx.conf 
>>>>> <https://github.com/poblabs/weewx-belchertown#belchertown-skin-options> - 
>>>>> (e.g. removing the newline between skin = Belchertown and [[[Extras]]]
>>>>>
>>>>> Restart weewx when done and see what happens. 
>>>>>
>>>>>
>>>>>
>>>>> On Sunday, November 25, 2018 at 6:14:30 PM UTC-5, rich T wrote:
>>>>>>
>>>>>> First of all, very nice skin design.  Everything thing is working 
>>>>>> correctly except the Highcharts are not updating.  I'm just updated 0.8 
>>>>>> and 
>>>>>> still I have the same issues.  One of my conf files must be incorrect, 
>>>>>> but 
>>>>>> I can't see where. Attached are the current config files with sys_log.
>>>>>>
>>>>>> Thanks
>>>>>> Rich
>>>>>>
>>>>>

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