[weewx-user] Re: Belchertown Highcharts not updating

Great! I'll update the GitHub readme so it's a little clearer when making the skin the default Thanks for the patience. On Wednesday, November 28, 2018 at 9:16:26 PM UTC-5, rich T wrote: > > Pat > > You are correct, there was had duplicated data. Performed your > recommended steps and

[weewx-user] Re: Belchertown Highcharts not updating

Pat You are correct, there was had duplicated data. Performed your recommended steps and allowed to run over an hour. The site now updates as expected. Just a side note; I did not get any error about belchertown_root_url not being defined. Thanks for your help Rich -- You received

[weewx-user] Re: Belchertown Highcharts not updating

I still think this is a root URL issue and duplicated data since you have effectively two locations for belchertown. Let's try and clean it up, then regenerate from scratch: Validation: 1. Stop weewx. Keep it stopped until you go through the whole process. 2. Delete the

[weewx-user] Re: Belchertown Highcharts not updating

I can view the site @ http://192.168.XXX.XXX/weewx or http://192.168.XXX.XXX/weewx/belchertown

[weewx-user] Re: Belchertown Highcharts not updating

If you view the skin at http://192.168.XXX.XXX/weewx/belchertown, then yes, make the belchertown_root_url the same url - without the trailing slash. On Tuesday, November 27, 2018 at 9:38:46 PM UTC-5, rich T wrote: > > Pat > > The charts contain day old data and for now this site is only on my

[weewx-user] Re: Belchertown Highcharts not updating

Pat The charts contain day old data and for now this site is only on my local LAN. Currently, the site_url option is "belchertown_root_url = http://192.168.XXX.XXX/weewx;. Let me try pointing to the belchertown folder and see what happens. Rich On Tuesday, November 27, 2018 at 9:11:17 PM

[weewx-user] Re: Belchertown Highcharts not updating

Ok so the files are updated correctly. I'm thinking its a JavaScript load error now. Are the graphs blank or old data? Is your site public? In weewx, did you define the site_url option? The site_url option needs to match your website URL exactly. e.g. http://richt/weewx/belchertown or

[weewx-user] Re: Belchertown Highcharts not updating

Pat This is the WEEWX Config: [[Highcharts_Belchertown]] HTML_ROOT = public_html/belchertown skin = Highcharts_Belchertown [[Belchertown]] HTML_ROOT = public_html/belchertown skin = Belchertown #[[[Extras]]] #logo_image = ""

[weewx-user] Re: Belchertown Highcharts not updating

Andrew, you may be right - and that's why I mentioned I was confused earlier - quite a few generators that do different things. :) Still - I'm not sure where the issue lies with this particular issue yet. I don't think it's a CopyGenerator problem as initially reported. That was what my

[weewx-user] Re: Belchertown Highcharts not updating

Pat Will check later this evening, when I get back home. Rich On Tuesday, November 27, 2018 at 9:44:52 AM UTC-5, Pat wrote: > Gary, understood on all counts. My belief is that the copy generator will > copy the newly generated files by the report generator. In this case, it's > the 4 json

[weewx-user] Re: Belchertown Highcharts not updating

Pat If I am understanding correctly it is the report generator which is putting the .json files in the correct place - not the copy generator. On Tuesday, 27 November 2018 16:44:52 UTC+2, Pat wrote: > > Gary, understood on all counts. My belief is that the copy generator will > copy the newly

[weewx-user] Re: Belchertown Highcharts not updating

Gary, understood on all counts. My belief is that the copy generator will copy the newly generated files by the report generator. In this case, it's the 4 json files. This is how it's working in Belchertown 0.7, as well as in 0.8rc1,2,3. I don't think I need to explicitly specify copy_always =

[weewx-user] Re: Belchertown Highcharts not updating

On Tuesday, 27 November 2018 12:09:05 UTC+10, Pat wrote: > > Ok your explanation is my understanding as well. Understood on Rich's > report of 0 files copied - which is why I'm lost as to why it's failing > since it should have 4 files to copy. The Belchertown highcharts skin > should create

[weewx-user] Re: Belchertown Highcharts not updating

Ok your explanation is my understanding as well. Understood on Rich's report of 0 files copied - which is why I'm lost as to why it's failing since it should have 4 files to copy. The Belchertown highcharts skin should create new json files every archive interval, which should be a fresh copy

[weewx-user] Re: Belchertown Highcharts not updating

On Tuesday, 27 November 2018 11:17:49 UTC+10, Pat wrote: > > I think you've lost me a bit on this one. > > Your statement is true but the highcharts skin generates 4 json files on > every archive interval. Which should be copied every time it runs I'd > gather? > No. I think we need to be

[weewx-user] Re: Belchertown Highcharts not updating

I think you've lost me a bit on this one. Your statement is true but the highcharts skin generates 4 json files on every archive interval. Which should be copied every time it runs I'd gather? This is the first I'm hearing of the skin ignoring the generated files? The copy_once, and

Re: [weewx-user] Re: Belchertown Highcharts not updating

Or sooner if you set it to :) On Tue, 27 Nov 2018, 12:56 rich T 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?

[weewx-user] Re: Belchertown Highcharts not updating

Whoops, premature posting... Be careful when interpreting 'how many files are copied'. The line Nov 25 17:35:44 raspberrypi weewx[1619]: copygenerator: copied 0 files to / home/weewx/public_html/belchertown is the result of the copy generator being run. The copy generator is frequently used to

[weewx-user] Re: Belchertown Highcharts not updating

Be careful when interpreting 'how many files are copied'. The line Nov 25 17:35:44 raspberrypi weewx[1619]: copygenerator: copied 0 files to / home/weewx/public_html/belchertown is the result of the copy generator being run. The copy generator is frequently used to copy css, js or other type

[weewx-user] Re: Belchertown Highcharts not updating

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:

[weewx-user] Re: Belchertown Highcharts not updating

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

[weewx-user] Re: Belchertown Highcharts not updating

I do see that it's trying to copy to /home/weewx/public_html/belchertown which tells me you've installed from the tar file (and not from apt-get). Most of the skin should be install agnostic, but maybe there's something getting gummed up with the tar install (I've seen it before). Let me do

[weewx-user] Re: Belchertown Highcharts not updating

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

[weewx-user] Re: Belchertown Highcharts not updating

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

[weewx-user] Re: Belchertown Highcharts not updating

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 , or we can try to figure out what's wrong together. If you choose the latter, I notice your syslog