Cumulus Support

1. The logfiles now should be read irrespective of differences because of locales
2. Daily Custom JSON are now only constructed and uploaded once per day (i.e. the first opportunity after midnight)
3. CustomLogs data are now split in two: customlogsRecentdata.json and customlogsDailydata.json
4. A link to the Wiki Webtag list is now displayed above the table(s) on the left pane

1. You do not need to zip txt files unless they are really very big. I prefer not zipped because that makes viewing easier.
2. Running only utils/bin/cumulusutils.exe CustomLogs is much faster
3. Remember once you created the module with the previous command, if nothing changed in your configuration there is no need to run it again (unless there is a new release). So to see a data result just run UserAskedData.
4. Could you repost your ExtraTempLog-202310.txt?

10/10/23,17:00,16.2,59,16.0,20.2,72,15.0

NOTE: The formatting of the datafiles is important as the Custom Logs are basically free format: you can put into the file any text and numbers with any separator you wish. CUtils will NOT handle that Free Format in general. The user has to take care the information in the resulting datafiles is as follows:

1) There MUST be at least one space between the numbers;
2) There cannot be any plain text in the logfile
The date/time will be untouched i.e. the format is: dd-mm-yy;hh:mm;

1. The menu still holds an item ExtraCharts under which you defined an item Custom Charts. That only loads the charts and not the realtime table on the left of it. Please make an empty top item Extra in your menu and remove the items under your ExtraCharts item. When running website, that should generate automatically the CustomLogs module (including the table, not only the charts)
2. The customlogsRecentdata.json (e.g. for your ExtraTempLog) has the data twice for each variable. This produces a line running back from the end to the graph start. I don't understand yet but it does not happen (so far) on my site.
3. I notice you changed the frequency for the ExtraTempLog quite often

1. The CO2 sensor webtags as described above => I asked Mark
2. Changing a table name requires a rerun of CustomLogs (and the implicit recompilation) if you forget to run CustomLogs, the compilation will fail and JSON's will no longer be created and sent in subsequent UserAskedData runs. This will show the system failing (charts not updated). The dependencies on user interaction must be avoided or minimized.
3. Adding a log (Recent) leads to a 500 error when uploading with PHP. I asked Mark a question.
4. Adding a log (Daily) and running CustomLogs (as one should), will create a new log/data only at rollover. That means that between the moment of running CustomLog and the needed data in the new log, the UserAskedData will fail because of missing data file. The workaround here is wait for data or run CustomLogs only after some data is available. Again, user action / reflection is required.
5. The user must be aware that webtag values are always instantaneous values which after some thought I think is correct (see here)