Extra Sensor Files: Difference between revisions

524 bytes added ,  17:57, 4 July 2020
m
Line 29: Line 29:


=== Adding extra sensor values to website pages ===
=== Adding extra sensor values to website pages ===
For Oregon Scientific extra temperature sensors, the value from just one of them can replace the main temperature sensor - see [[Cumulus.ini#Oregon_Scientific_specific:]] and see above.  
 
For Oregon Scientific extra temperature sensors, the value from just one of them can replace the main temperature sensor - see [[Cumulus.ini#Oregon_Scientific_specific:]] and see above.  Otherwise extra sensors cannot be automatically included in the standard uploads to web sites without some actions by you.


On your website, use the [[Webtags#Extra_Sensors|web tags listed here]] to either display current values on your 'latest values'  [[Customised_templates|template page]] (this could be the ''indexT.htm'' page) that is processed by Cumulus, or use those web tags as parameters for feeding your own graphics as on the 'gaugesT.htm' page.
On your website, use the [[Webtags#Extra_Sensors|web tags listed here]] to either display current values on your 'latest values'  [[Customised_templates|template page]] (this could be the ''indexT.htm'' page) that is processed by Cumulus, or use those web tags as parameters for feeding your own graphics as on the 'gaugesT.htm' page.


Any extra sensor monthly log can be uploaded at your usual website update interval by specifying the parameter 'ExtraLocal[0-99]=ExtraLogyyyymm.txt' see [[Cumulus.ini#Section:_FTP_Site]], unfortunately this will need to be updated manually each month to insert the correct replacements for 'yyyymm' if you want the current log. As at August 2013, Cumulus does not calculate extremes for these extra sensors (unless it is the Oregon Scientific extra temperature sensor replacing the main one).  A script written by you can then read the file into an array or database for further processing. If you are skilled enough, it is possible to write code or queries to read that array or database, calculate extremes for yourself, or draw graphs based on these logged extra values.
Any extra sensor monthly log can be uploaded at your usual website update interval, see [[Cumulus.ini#Section:_FTP_Site]].
If you use build 3087 (or later) then MX allows  '''ExtraLocal[0-99]=<currentextralogfile>''' to specify in local (or remote after changing the attribute name but using same value) columns to always insert the latest extra sensor log file in the upload command.
 
However, prior to that version of MX, and if you use Cumulus 1, you will manually have to enter the month and yearfor 'yyyymm' if you want the current log, and you need to do this each month, the whole parameter is therefore in format '''ExtraLocal[0-99]=ExtraLogyyyymm.txt'''.
 
As at August 2013, Cumulus does not calculate extremes for these extra sensors (unless it is the Oregon Scientific extra temperature sensor replacing the main one).  A script written by you can then read the file into an array or database for further processing. If you are skilled enough, it is possible to write code or queries to read that array or database, calculate extremes for yourself, or draw graphs based on these logged extra values. You might take inspiration from some php scripts available at


=== Viewing Extra Sensor Log files ===
=== Viewing Extra Sensor Log files ===
5,838

edits