CustomLogs beta

[AndyKF650]

Hi Hans

As ever I just cannot help trying to extend the envelope!

Today's issue is trying to get my RPi CPUTemp in a custom log. I have put the webtags <#CPUTemp>and <#temp> into the custom log folder in CMX and then run customlogs and useraskeddata but the info does not appear on my site.

The data file on CMX shows that the webtags produce valid data but the the utilslogs for the customlogs and useraskeddata warn that the CPUTemp webtag is not valid.

Do you have any thoughts on this?

[HansR]

Hi Andy, that's nice: not even released yet and the bugs are already coming in

I maintain a subset of legal webtags to use for the CustomLogs (obviously strings cannot be charted as neither can numbers with strings attached (e.g. a temperature with a unit attached). The CPU temperature had not made it to that list but it should as it is just a number.

BTW: if you are testing anyway, 1) you can add literals in the logs, 2) try webtags resulting in strings and 3) try webtag parameters which modify the value. Best for testing is to create a Test CustomLog on Interval frequency and only modify that one because changing the tags will reset the chart so it won't interfere with your serious CustomLogs and can easily be deleted afterwards.

#CPUtemp has now been added to that list and you find attached a version 6.21.0 RC (qualifier is not displayed) which should solve your issue.

[AndyKF650]

Hi Hans

That worked as expected, I now am now recording CPU temp in the custom logs Just ran website to update everything and the chart popped up with the back data.

I have some other work to do today so extra testing will be later.

[HansR]

OK.

Note that you do not have to run website, CustomLogs as argument is way faster.

[HansR]

I started using custom logs 2 days ago. It went relatively smoothly, but since then I haven't had any charts. I thought maybe there had to be a minimum amount of time for this to happen (for me it was 48 hours), but I was checking the website for the code today and the browser prompted

Code: Select all

Failed to load resource: https://pogodarybnik.pl/customlogsRecentdata.json? the server responded with a status of 404 ()

From this I understand that the module is looking for the customlogsRecentdata.json file in the main directory, but I have all the cutils files in the /CU directory. My path should look like this:

Code: Select all

https://pogodarybnik.pl/CU/customlogsRecentdata.json?

Would adding

Code: Select all

cumulusutils.ini -> CustomLogs -> FTPDirectory=

solve the problem?

Great you use the CustomLogs module

OK, your datafile is in the CU directory (I checked). Apparently you defined that as the uploading directory for the CUtils modules but you run the modules from one level up: your webroot is https://pogodarybnik.pl/ this separation of modules and website directory has never been done before: the CUtils files should be in the webroot. I assume you don't want that but I ask you: would that really be an issue?

What we now have is a 'kind of inverse use' of CumulusRealTimeLocation (which is used if the CMX datafiles are outside the CUtils directory structure). If you wish to stay with the CU directory for the modules, I'll have to think on how to deal with this.

The issue can now only be solved by moving all files to the webroot and run from there (effectively removing CU from the path)

Your suggested solution for adding another directory may work but through another parameter specifically for module use.

[HansR]

This topic has been locked, please start a new thread if any issue.