I would like to spend a few words on some recent changes in CumulusMX which have some consequences for the use of CumulusUtils, specifically the bandwidth used.
The standard Cumulus Charts (Recent Charts as they are named in the Menu) are also used in CumulusUtils and can be found under the Home button in the menu. Recently in CumulusMX there have been additions for Historic Charts, AQ charts and the most recent Select-a-chart (which uses the JSON's for the Recent Charts).
All these charts have their own set of JSON data files: eg. the Recent Charts need tempdata.json, solardata.json [etc...], the Historic Charts need the alldailyxxxxdata.json and the AQ data require airquality.json (from the point of view of CumulusMX).
The presence of the datafiles on your website is governed by the parameter IncludeGraphDataFiles=1 [section: FTP Site] of the Cumulus.ini file. This parameter is an all or nothing option.
I asked for a break down in parameters to govern which JSON files to actually send but @mcrossley does not want to do that and it is suggested that if you don't want all datafiles you just switch off the IncludeGraphDataFiles parameter and regulate the required presence of specific JSON files by the Extra Web Files feature of CumulusMX. This process has recently been described in this thread.
So, if you don't mind to waste some bandwidth every 10 or 30 minutes or so, you can stop reading here and leave everything as is.
If you do mind about bandwidth, read on.
CumulusUtils assumed setting of CumulusMX as choices of the user which were reflected in CumulusUtils. With the expansion of CMX and the whole JSON dataset transferred to the website that assumption is no longer correct.
So I will advise to:
- Set IncludeGraphDataFiles=0 in Cumulus.ini
- Put the datafiles for the Recent Charts in the Extra Web Files section, do not tick Process, do not tick Realtime
- Historic charts are not used in CumulusUtils and will probably not be added to CumulusUtils. Not on a short term, maybe never. If you use them for your other websites, remember that the FTP send is done in the UpdateInterval (Cumulus.ini, [section: FTP site]) and cannot be changed. Those files refresh only at rollover time so would only require a once per 24 hr refresh, no optimisation is possible (afaik) see reaction of @mcrossley below.
- The AirQuality.json as output by CMX is not used by CumulusUtils, so don't send it unless you have use of it soemwhere else (if you have an AirLink device). The AirQuality JSON's required for CumulusUtils are only sent when configured properly and and only carry the data you wish to see.
- The new Select-a-Graph does not require additional JSON files. I had already been thinking of a graph (as a HOME page starter) with multiple parameters in it (compile time selectable) and I may still do that. Maybe I will borrow the dynamic Select-a-Graph feature by Mark, I have not decided yet. Whatever choice, this seems not to require additional advise wrt the JSON datafiles.
Setting the JSON transfer as indicated above you will definitely save a lot of bandwidth, together with the Thrifty qualifier option (with especially a long period for the Wind and Solar graphs - I use 21 days) CumulusUtils has a very optimised performance both in CPU as in bandwidth.
Sorry for the inconvenience and awkward configuration change.
Please NOTE: The CumulusMX version of the AirQuality data only contains the current concentrations of pm2p5 and pm10 and nothing more. As in CumulusUtils you can chart every AirLink data you wish, it requires its own datafiles which are generated at the same frequency as the CumulusMX JSON files and contain only those data you ask for. As the parameters in the JSON are different from the CumulusMX JSON, the files are not interchangeable. So for CumulusUtils you do NOT need the CMX AirQualiy.json
Please NOTE: the AirQuality data (and other 'Extra' sensor data produced by the Ecowitt GW1000 and similar devices) are not supported by CumulusUtils and I doubt they ever will be.