Webtags (preserving history)

Some content has been removed from this page

Please be aware some content originally on this page has been moved to other pages. Old posts on the support forum that used to link directly to the specific material, will instead bring you to this start of the page.

Where the old content was cut, new links have been substituted within three sections on this page: #Input Modification Parameters and Output Modification Parameters, #The tag name, and #Recent History.

Essential Background Reading

If you have not used this Wiki page before, or are unsure about using "web tags", there are some concepts that you do need to understand in the sub-sections that follow.

The tag names

All the "tag_names" that are available for legacy 1.9.4, and for MX up to first beta build release 3.12.0

are in #Full List of Tag Names later on this page.

If you edit this page, to add tag names for later builds, please amend the previous sentence.

If you are using a Oregon Scientific weather station, then you should read #Web tags mentioning (outside) temperature in the optional reading section.

Do not assume that Cumulus always works according to normal meteorological practice in your nation. For examples, the hours used by Cumulus to report derivatives involving rainfall, or minimum temperature, may vary from figures reported by local meteorological stations.

Cumulus MX versus original Legacy Cumulus 1

The full information that used to appear on this page for differences between MX and the legacy Cumulus has been moved to a new Web tag Applicability page. The next subsection just gives a basic summary.

This page has been updated to include web tags up to version 3.12.0 beta build 3134. Announcements for new builds of MX generally provide too little information for it to be easy to update this page, that is why it is often out of date.

• Since version 3.10.x, MX has not used web page templates, please see WebsitedataT.json page, instead of this Wiki page.
  1. That page explains the ID names used on the default web site introduced from release 3.10.0
  2. That page documents each data pair in the file
  3. That page gives the source web tag for each ID name on the web pages
  4. That page explains what data is represented by the ID name, JSON attribute, web tag name
• Past MX releases 3.0.0 to 3.9.7 used web template files, similar to (but not same as) the legacy software
  • This Wiki page remains organised according to the content of those old template files.

This page was created for Cumulus 1. Steve/Beth Loft provided some example web template files, but expected Cumulus users to develop their own Cumulus template files making use of the web tags, listed below, that the software provided.

For tag names available in the release you are using, see the next sub-sections.

What web tags can I use?

Basically, it depends on which web tags are in whatever files are used to transfer weather derivatives to your web server.

As Cumulus has developed, more tag names have been introduced, the tables showing tag names available, attempt to give an indication of which release introduced them. You can, see below, ask Cumulus (both MX and legacy) to list all the tag names it recognises, when it is started at whatever build you are running.

Using release after 3.9.7?

If you are using the default web site, its standard web pages show data as follows:

• Pages with tabular presentation, see WebsitedataT.json.
• Pages with graphs, see Graph File Settings.
• Page with steel series dials, see Display Options.

If you are using your own web templates, or other own Cumulus template files such as XML or PHP data files, then you make the decision on which tag names are used for the data to your web server.

Getting release 3.12.0 or later to list tag names when it starts

Please use the admin interface.

Go to Program settings → General options

Tick List web tags.

The next time that MX is restarted, it will create a file called WebTags.txt in the same folder as where the executable is found. That file will list all the tags your build of Cumulus can currently generate. This list only contains the tag_names, it does not indicate what parameters they can take, nor does it include the brackets the tag name is surrounded by when you quote it in a template file for Cumulus to process.

Go to Program settings → General options, untick List web tags to stop Cumulus continuing to produce new versions of that file next time it is restarted.

Getting legacy Cumulus, or MX releases up to 3.11.4, to list tag names when starting

The tag names available in the release/version/build you are using, can be listed (in Cumulus 1 or Cumulus MX) by adding the following line to Cumulus.ini in the [station] section... ListWebTags=1

Then start Cumulus and it will create a file called WebTags.txt in the same folder as where the executable is found. That file will list all the tags your build of Cumulus can currently generate. This list only contains the tag_names, it does not indicate what parameters they can take, nor does it include the brackets the tag name is surrounded by when you quote it in a template file for Cumulus to process.

To stop Cumulus continuing to produce new versions of that file change the line to say ... ListWebTags=0

If you are using Cumulus 1, each build of that contains a build specific version of Cumulus Help, and within that help is a list of web tags with basic information on what each tag_name returns.

MX bug: The inclusion of a web tag in the list produced by this instruction, does not mean that web tag is actually populated with valid information. See https://cumulus.hosiene.co.uk/viewtopic.php?p=153096#p153096 for an example.

What is a web tag?

Weather values are always changing, so Cumulus needs a way for you to tell Cumulus to enter the current value for a particular derivative, when it is processing templates.

General Format for Web Tags

In the position, in any (HTML, JSON, PHP, XML) template file, SQL, or Custom HTTP, where Cumulus is to insert the relevant data, place a web tag in the general format specified here: <#tag_name [optional input selection parameters] [optional output modification parameters]>

The optional parameters

The terminology "optional" is used because some tag names do not accept any parameters, but there are some tag names where a parameter is mandatory. Therefore, check the web tag parameters page to learn whether a web tag name you find here requires a mandatory parameter, or to find out which parameters are optionally available.

The tables of tag names that appear later on this page will seldom give any information about which parameters are mandatory or optional. There are tables on the other page referenced above that help you to understand what parameters the various tag names accept, explain each of the parameters available, and give examples.

There is a basic guide to what these parameters can do, and another link to the new page at #Input Modification Parameters and Output Modification Parameters later on this page.

Inconsistency of tag names

For both the legacy Cumulus and for MX, it is vital that you use tag names exactly as they are listed. That would be easy had Steve Loft created a naming standard and stuck to it.

To be fair to Steve, he created the legacy Cumulus for his own use, working in his spare time, alongside a full time job.

Remember, the original design did not anticipate use by others, nor how much extra functionality would be added later.

Early versions of Cumulus could only report current values and the summary for the day so far. Different web tags for today-so-far were added at different times, hence the names are inconsistent. New web tags for today-so-far added before yesterday tags were considered lack the T suffix (or prefix) later today-so-far tags use.

All-time tags were introduced before yesterday, this month and this year; hence all-time tag names assume they are only extreme monitoring.

The legacy tag names for this month and this year were all introduced in a single release and they remain consistent apart from what MX added later! However, they are not consistent with the naming of the all-time extremes introduced much earlier.

This great inconsistency in the naming, gives rise to a problem as it very easy to spell a tag_name incorrectly (and from time to time such mistakes creep into the tables on this Wiki page) as you naturally expect there to be a standard pattern. Some tags are all lower-case, some are camel-case, and some start with a capital letter. Have a look yourself at just how much inconsistency is present in the names in the tables below.

Inconsistency in use of "Y"

The character "Y" has been selected to denote yesterday in tag names. The inconsistency is where it appears.

• Steve used Y as a suffix for most, not all, Cumulus 1 yesterday tags (e.g. <#rfallY>, <#windrunY>, <#YSunshineHours>, <#avgtempY>)
• Mark uses Y as a prefix, in most, not all, the extra Cumulus MX tags (e.g. <#Ybeaufort>, <#Ychillhours>, <#windAvgY>)

Consistency in Cumulus 1, becomes inconsistency in MX, for this month and this year

The legacy tag names for this year and this month were all introduced together by Steve in one release, with consistency in how they were named then, "Month" or "Year" was used as a prefix (this was after he had started using "Y" as a prefix for his new yesterday tag names) e.g. <#YearLongestDryPeriod>.

The development of MX however, broke this consistency, as Mark adds "Year" as a suffix, e.g. <#SunshineHoursYear>, instead of following Steve by using a prefix.

Inconsistency in use of "T"

I said above, that early versions of Cumulus only had tag names for current spot values and for today-so-far daily means/extremes/totals. Therefore it could be assumed that <#beaufort>, <#temp> and <#press> all represented current spot values while <#avgtemp> and <#rfall> represented today-so-far values just by looking at their names.

The current value tag names formed the basic part of tag names, extended for daily extremes with "TH" and "TL" added as suffixes (to represent daily highs and daily lows), (e.g. <#tempTH>, <#tempTL> and <#pressTH>, <#pressTL>), which made a lot of sense. Adding a "T" for related times, made some sense, except that use of "T" was not done in a consistent manner (e.g. <#TpressTH>, <#Tbeaufort>, <#TtempTH>, <#YearTempHT>).

The functionality that can use web tags

In the legacy Cumulus software, the only functionality that could use this was the Cumulus template file used to provide data to a web server. That is why Steve Loft, the author of that software named them web tags.

MX has extended the use of these web tags, they can now be inserted into a SQL commands, Custom HTTP, application programming interface, as well as template files.

The output file can be:

• a web page,
• a JavaScript Object Notation (.json) file
• a JavaScript file,
• a PHP script file, or
• a eXtensible Mark-up Language (XML) file.

Optional Background Reading

Web tags mentioning (outside) temperature

For Oregon Scientific weather stations using, either USB connections (e.g. WMR-200), or serial connections (e.g. WMR-928), that can have multiple temperature sensors, it is possible to configure which sensor the outdoor temperature (for which daily and longer period extreme records are maintained) is read from, by following this set of instructions originally supplied by Steve Loft:

1. Stop Cumulus in the normal way
2. Use a text editor to edit the file called Cumulus.ini
3. Scroll down to the line that contains [Station]
4. Create a blank line below it by pressing Return
5. In that new line, type the command shown in the relevant code box below, type the attribute and equals sign exactly as shown without spaces (regardless of your exact model),
   • USB connections → WMR200TempChannel=N
   • Serial connections → WMR928TempChannel=N
6. Now edit the value shown after the equals sign, replace N with the relevant number from the following list:
   • To use the main sensor, replace N with 0 (or don't bother with this procedure, as that is default)
   • To use Extra Temp 1 sensor, replace N with 1
   • To use Extra Temp 2 sensor, replace N with 2
   • and so on, up to a possible maximum (check with your weather station, but Cumulus can accept up to 12)
7. Save the file, and exit
8. Restart Cumulus in the normal way

For other weather stations, the main outdoor temperature sensor is used for what is reported for current value, daily extremes, and longer period extreme records. This temperature is also used for calculation of derived values such as Australian Apparent Temperature, Canadian Humidity Index, and USA Heat Index.

Please check release announcements, it is planned that swaping of main Temperature sensor will become available for Ecowitt.

Input Modification Parameters and Output Modification Parameters

In #Scary_statistics section of this page, it is explained how less than a thousand tag names (the first part of the #General Format for Web Tags) become billions of web tags, simply by adding modifiers.

The modifiers available used to be listed on this page (so if you select the history tab for this page, you will find references to their introduction and growth), but are now on a new web tag parameters page. Here are some of the advantages achieved by moving them to the new page:

• This page is very long, so it is not easy to navigate this page, even without the parameters
• There would be a lot of repetition if you attempted to say beside each tag name which modification parameters were available.
• Having them on separate pages means you can have two tabs (or two separate browsers) open so you can see both the tag name and the modifier parameter by flicking between tabs, instead of lots of scrolling between different parts of same page.
• The introduction of WebsitedataT.json, which controls what data is available to tables in the web pages provided by MX, means that page, rather than this page is the entry point for MX, and it is easier for that page to reference a separate parameters page
• MX has introduced many more input and output modification parameters, it is easier to maintain a separate page (and easier for reference if you just want to refresh your mind on new modification parameters).

For just a taste, there you can discover:

• A score of input modification parameters
  • For example, find which attribute is used with a value between 1 and 12, so the same tag name can give values for 12 different months)
• If your locale normally (in real numbers) uses an integer part, then a comma, and then the decimal part, you should be aware that some computer scripts, and some external servers where you might want to send data, insist on a decimal point, instead of a decimal comma:
  • If you have installed a recent MX release, then change decimal comma to decimal point with a simple "y" value to another attribute
  • If you have the legacy Cumulus 1 installed, stay on this page and look at #No_Commas, as you have to use the restricted alternative set of tag names.
• How to control number of decimal places in any real number output
• All about the complex subject of modifying the way a duration, a date, or a clock time is output by looking at Multiple_Output_Format_Modifier_parameters_for_times_and_dates

Why does MX talk about tokens?

MX uses a token parser to read the web tags and replace them with the correct value, so if diagnostic output refers to tokens, it is saying the attempt to actually work out what content to return to replace the web tag with its tag name and parameters has encountered a problem.

Scary statistics

1. The 3.5.0 release of MX defines 9½ million values that can be represented using web tags!
2. At 3.5.0, there are only 717 options for the tag_name in the general format given above.
3. How come this discrepancy?
4. That discrepancy is purely because some of those 717 tag names can be associated with input parameters, (and for Oregon Scientific stations,you can select which sensor is used for outside temperature), these modifications affect what value is selected to be output by the web tag leading to the large number
5. These millions of web tags can actually produce billions of different outputs!
6. How come this second discrepancy?
7. Well adding all possible different output parameters generates the billions of different ways to output the millions of values!

The statistics quoted above keep increasing as MX is developed, the last time I checked, there were another forty or so tag names, and lots more parameters, so the alternatives are probably well over ten billion now.

Brief history of this page

This page was created in August 2009, to list the tags for the (legacy) Cumulus 1 software. Initially, there were going to be further pages to explain individual web tags, e.g. Forecast_webtag; but that idea was never completed.

When MX came out of beta (3.0.0), it has been developing rapidly, as the statistics above suggest, the number of web tag names and input/output modification parameters, to document became too much for one Wiki page, hence the moving of all documentation about modification parameters to a sub-page. There are still a lot of web tag names to document on this page, and separation into a number of pages was considered, but it is easier to have just one page to refer in answers to questions raised in the forum.

Still got questions?

Full support is available via the support forum at https://cumulus.hosiene.co.uk/viewforum.php?f=40 for the latest MX release. Given that some users may still be running an older MX release, where possible any web tag listed below for MX indicates at which release it first became available.

There is limited support available for Cumulus 1.9.4, but on this page every attempt is made to indicate which version of the legacy software introduced any web tag listed below.

The web tag application programming interface

Available from version 3.7.0 (build 3089) released 28 July 2020. It was proposed in January 2015, see Steve Loft plan to add a call where you supply a list of items (probably web tag names), and you get back the equivalent data.

Where to use

This is meant for services either on the same computer as Cumulus or on your local network. It is not secure, and should not be available, nor requested, via any external network or the internet.

The MX Administrative Interface uses some application programming interface (api) calls to obtain the data each web page in that interface needs, and if you are making an edit, another api to return the results of any edit made.

If you wanted your CumulusMX/interface/todayyest.html web page to include something else (e.g. snow falling/lying/depth) you could edit that HTML page to have the extra sub-table you want (you cannot edit the existing rainfall table as that is dynamically created by existing api). Then you could edit the associated JavaScript file CumulusMX/interface/js/todayyest.js to add a new api call seeking snowdepth, snowfalling, snowlying tags for today (unfortunately there are no tags for yesterday's snow) and to place the returned values into your new sub-table (probably using jQuery to make it easy). In a similar way, you could add anything where today and yesterday tags are available such as UV Index.

In earlier versions of Cumulus if you wanted to make use of values processed by Cumulus, you wrote a script file referencing the web tags you wanted to use, and let Cumulus process that file at an interval set in the settings, then you had to write something to process the results at the relevant interval. Now if you are running other software on your device that runs MX (or a computer or other device linked directly on your personal network), you can request web tags values on demand via an application programming interface (api hereafter) and don't need to worry about any timing issues.

Obviously each api request creates a processing overhead on Cumulus so use this feature wisely (minimise the information you request and minimise the frequency of requesting it). You can use it for extra current information, but in that usage you might need to repeat the call. Consequently, maybe it is more likely that the api will be used to request information that does not keep changing, such as what units are being used for temperature, rainfall, and wind speed; or perhaps daily, monthly, or yearly, summary figures.

Each admin interface web page uses api techniques for all the information it needs. Some api calls are repeated with AJAX requesting updates for the weather information on a frequent basis, but each page has another api request that is issued just once for the version and build being used. To my mind, the design of CumulusMX/interface/todayyest.html is crazy. The HTML appears to have a table structure, but that table structure is overwritten by each repeating api. So every time AJAX repeats that api call it returns in json format the whole table definition as well as table cell contents, despite that much of that json (all that HTML defining table header, table rows, table cells, etc.; and the units for each value) does not change and it is only some values and times buried within the json in the api that actually might change (and of those half of them, the yesterday values and times only change once a day). In some code I wrote (but later abandoned) I made use of the api calls that support the CumulusMX/interface/todayyest.html web page to get the units I wanted on another interface page, but I only called it once as it returned a lot of other information (as just mentioned) that I did not need. I later found a better way, as in example below, which gives me just what I need and no more.

"GET" approach

You may have used GET as an attribute when defining the action of a HTML form. Equally you might in a script language access the query-string part of a Universal Resource Locator to get parameters for what the script is to supply to the web page. Even if you don't understand the meaning of those technical terms, you probably have seen when using a browser (in the box where a URL is entered) that sometimes the URL seen there has a query-string. You will have seen a question mark (?) followed by one or [separated by ampersand (&)] more name=value parameters. Full List of Tag Names The GET approach to using the Cumulus general api works in this way indicating the start of a query-string with a question mark and using ampersands to separate names. The difference is that a tag name (or list of tag names) is used instead of a name=value parameter (or list of name=value parameters). However, when the Cumulus api returns the values they will be in attribute=value format. Therefore if (like example below) you are coding in JavaScript, what is returned is a JavaScript Object and you extract the values by specifying the Object name and the Attribute name. If that technical terminology confuses you, look at the example.

Selecting values using GET

Suppose you want to get the values for the following three web tags:

1. <#RCtemp>
2. <#RChum>
3. <#RCdew>

Then the URL with query-string to use is http: //localhost:8998/api/tags/process.json?rc&temp&hum&dew

Obviously, if you have started MX with a port parameter like this:

sudo mono CumulusMX.exe -port 9999

then you change the 8998 port shown in the URL for the api to use the port you have selected e.g. http: //localhost:9999/api/tags/process.json?rc&temp&hum&dew

The first parameter is rc to indicate that the tags that follow are to use decimal points not decimal commas, which is how many script languages expect to see values. Remember that in current version (and some earlier versions) of MX, the above three web tags are exactly same as:

1. <#temp rc=y>
2. <#hum rc=y>
3. <#dew rc=y>

Since rc=y can be applied to several web tags that don't appear in Webtags#No_Commas table, this shows how the api can access values without commas for all those web tags that report in real numbers and allow that output modifier.

If you are using the api in a context where it does not matter if decimal commas or decimal points are in the api or for any tags that don't report in real numbers, simply omit the rc as first item, and just include tag names separated by ampersands.

JavaScript example

Some people might feel the admin interface could be improved on some of its pages by showing additional information. It is possible from MX 3.7.0 to obtain extra information.

I wanted to improve the log file editing pages, and that was partly by adding validation, and partly by changing the way the editing is done. For the standard log file editor I wanted to achieve even more, I added a script to calculate (and recalculate after any edit) the derived fields from the source fields. To make these calculations work for anyone, I needed to find out what units the Cumulus MX user is using. Before 3.7.0 release the snippet of script that obtained the units via various api calls was quite complex (I described above how the api returned lots of unwanted content), but with 3.7.0 my new api call was greatly simplified to what I show below. Please note my revised log file editing scripts did not make it into a public release, and it is only the units obtaining api that I am making available to public here.

Here is the code (with the api call written using jQuery):

/*    Some new variables connected with new api call (MX 3.7.0)  */
		var tempLetter;  // C or F
		var rainUnit; // mm or in
		var windUnit; // any units in style allowed by Cumulus
/*  The one extra api request included to obtain the units used for temperature, rainfall, and wind speed */
		$.get('./api/tags/process.json?tempunitnodeg&rainunit&windunit', "limit=1", callUnits);
		function callUnits(unitsObject)
		{
			tempLetter = unitsObject.tempunitnodeg;
			rainUnit = unitsObject.rainunit;
			windUnit = unitsObject.windunit;
			console.log("new api", tempLetter, rainUnit,windUnit);
		}

A little bit of explanation might help:

• JavaScript variables generally need to be declared first, I have used 3 separate line each starting with var, but you can list several variables on one line using a comma to separate them
• In my script it is important to define these variables outside the function as I will explain later
• The jQuery get request takes the api URL as first parameter and the function to deal with the returned result as third parameter
• The middle parameter is irrelevant in this context as only one object instance is returned, but if the qet was returning multiple results, "limit=1" would only return the first result
• The function takes as its sole parameter an Object (a JavaScript Object is a collection of properties), this is what is returned by the api, an object can be given any variable name
• In JavaScript if a variable is defined outside the function, then given a value inside the function, that value can be accessed by later code outside the function (in my case by code within the other functions for calculating each derived value)
• We are only interested in 3 of the property_name = property_value items in the Object.
• The JavaScript refinement syntax (starts with a dot) can be used to find the value for any parameter we name. We assign the variable already defined to the object and its refinement (that specifies the attribute we want).
• The console.log command simply outputs all the items in the list within the brackets into the browser console that in many browsers is displayed by selecting F12 on the keyboard. I included this instead of the lengthy rest of my code that uses the units to do the various calculations correctly.

"POST" approach

The word "Post" in a computer environment means that the Hypertext Transfer Protocol (HTTP) used by the internet is being asked to transfer information enclosed in the body of the request message. Put slightly less technically in this approach you produce a text file with the details of what tags you want and send it to the api server. I suppose it is a bit like sending an email, its header (subject, author, date sent) is easy to view, but you need to open it to see what text is in the body.

You may have used POST as an attribute when defining the action of a HTML form. In that context the form is sent as the contents of a message to whatever web page is going to process the contents of that form.

The post approach has a few advantages over get:

• The parameters are not shown in any query-string, so are not obvious to the person looking over your shoulder, nor do they appear in a history list of sites that the browser has visited.
• If you fill out a form online, the post approach will be used as the content needs to be kept secure.
  • The get approach may be seen when you are navigating through a web site, and a selection is being remembered.
• The POST approach can handle very long requests and return a lot of information.
  • In contrast, a URL with query-string is restricted in total length (the restriction is dependent on a number of other factors, but might be at something like 1000 characters in total), so GET comes with a restriction on how many parameters can be specified.

See https://cumulus.hosiene.co.uk/viewtopic.php?p=145050#p145050 for post example

Full List of Tag Names

This document is 'Work In Progress' so content may not be complete.

Request for help from Wiki Readers

• Do you understand how MX works?
• Do you use hardware, or MX functionality, that is not yet documented? Can you begin that documenting?
• Can you contribute simple text for novice users, examples of what you have done, correction of typing or factual errors, or supply missing details?
• Will you make this page more useful by bringing content up-to-date as new releases change some information written for older releases?
• Does any page need a section for novices, so they don't need to read more technical information further down that page?
• Is there some information on this page, that should be on a separate page? Can you create the new page and move the less relevant information off this page, don't forget this page needs a link to the new page so people who expect to find it here know where it has moved to?

If you plan on contributing to the Wiki, then you will need an account.

• Please use the Request Account form to apply for an account. Note that the Wiki is currently undergoing restructuring and is largely locked for editing, but please apply for an account if you wish to contribute in the future.
• You will find help on how to contribute to this wiki at How to Edit.
• If you need to consult others, please use the Cumulus Wiki suggestions forum.

Please be aware that information on this page may be incorrect.

This list only contains the tag_names, don't forget tag_names are only part of the #General Format for Web Tags, for example in a template file you precede the tag name with <, you may need input parameters, you may need output parameters, and you end the full web tag with >.

it does not indicate what parameters they can take, nor does it include the brackets the tag name is surrounded by when you quote it in a template file for Cumulus to process.

Here follow tables that group the tag names by the basic purpose of the tags listed. There has been confusion in the past of tags appearing in more than one group, can contributors remove any remaining duplication, so future maintenance is easier.

There is a table of contents near the top of the page that you might find useful if you are interested in a particular tag group.

Current Conditions

We start with tags that relate to the latest values, as these are the ones that people most often choose to use. The current condition data is also available, for processes external to Cumulus, by using the inbuilt facility to generate a file with such data.

Cumulus software makes current values available for a standard range of sensors where the same web tags apply across a range of weather station models.

Both Cumulus 1 and MX offer current values from some extra temperature and relative humidity sensors (see Extra temperatures) from particular weather station models.

Recently, MX has been developed to support further extra sensors (see Extra Sensor Files page for full list of fields) and web tags have been added to support equivalent current values only.

Feels Like

Feels like temperature was first made available, just for current conditions at MX version 3.5.4. In version 3.6.0. it was extended to add max/min for each day, each month, each year, and all time. In version 3.6.11 it was added to recent history.

The figures quoted for this derivative vary between versions:

• The first formula was used from MX version 3.5.4 (25 Apr 2020) build 3075 until version 3.6.7 (4 June 2020) build 3083
• The second formula, which was coded incorrectly, and so gave strange results, applied in versions 3.6.8 to 3.6.9 (build 3084, 3085)
• The third, and hopefully final, formula applies from version 3.6.10 (build 3086).

A php script for adding feels like as calculated in version 3.6.10 to any standard log line created either without feels like, or with an older (now incorrect) calculation, can be downloaded from Create Missing topic on support forum. Obviously, this calculates from the small sub-set of current conditions that have been logged, and is not as accurate at deriving maximum and minimum as derivation made as each reading is processed by MX (so including all current conditions).

The Create Missing utility will not correct the older (incorrectly calculated) figures, but will add Feels Like temperature values to any standard log line created by Cumulus 1, by MX prior to release 3.5.4, or if you have imported lines into the log from an external source.

Standard sensors

The web tags shown here are mainly determined by which appeared on the original "Now" legacy web page (index.htm).

Consequently, the totals for Rainfall this month, and this year, are included here for consistency with supplied web templates (indexT.htm, thismonthT.htm, and thisyearT.htm) and with the dashboard 'Now' part of the Cumulus MX user; although you might expect to find them listed in tables for this month and this year, those web pages do not show these derivatives.

Those listed here cover both measurements obtained from a weather station (like air temperature, wind speed and direction, humidity and barometric pressure); and all the derived values (like humidex, feels like, apparent temperature, wind chill, and heat index).

Note however, that the derived values calculated for Cumulus 1 and for MX may not agree because of differences in the calculation formulae, see derived value section within Recent History tags section for examples.

Web tag_name	Function
Temperature
<#temp>	The outside (air) temperature For Oregon Scientific models like WMR-200 with USB connection or models like WMR-928 with serial connections, please refer to #Web tags mentioning (outside) temperature because any of the extra sensors can be reported in <#temp>, and consequently also have web tags reporting daily extremes and longer period extreme records.
<#intemp>	The inside temperature
<#TempChangeLastHour>	The change in outside temperature over the last hour (not available in early versions of Cumulus 1, when this was announced, a temperature change over 24 hours was also proposed, but never implemented)
<#temptrend>	The average rate of change in temperature over the last three hours. Trend = (temp_now - temp_3hrs_ago) / 3 (available in all releases, the calculation selected for this trend matches the standard-based calculation for <#presstrendval> despite the naming inconsistency)
<#temptrendtext>	Temperature change over the last three hours - Rising/Falling/Steady (values can be set in strings.ini)
<#temptrendenglish>	Temperature change over the last three hours - Rising/Falling/Steady (for use by HTML, javascript etc, values can't be changed). From version 1.8.8 1st December 2009
<#heatindex>	Current heat index. The referenced page in weather terminology section of this Wiki explains it.
<#humidex>	Current Humidex
<#apptemp>	The apparent temperature. The referenced page in weather terminology section of this Wiki explains it. The formula used is that defined by BOM. Although at temperatures above 20°C (68°F) Feels like reports an "apparent temperature" it uses a different formula.
<#wchill>	The current wind chill temperature. The referenced page in weather terminology section of this Wiki explains it. For temperatures below 10°C (50°F) Feels like reports the same value.
<#feelslike>	Not available in Cumulus 1. Not available in all MX versions. Please see sub-section before this table regarding availability by MX versions if you are using a MX version earlier than 3.6.10. The current Feels Like temperature. The referenced page in weather terminology section of this Wiki explains it.
<#IsFreezing>	If outside temperature is at or below 0°C/32°F. 0=Above freezing, 1=Below freezing
<#chillhours>	The number of 'chill hours' so far this season (threshold temperature and start date are configurable).
Humidity
<#hum>	The outside humidity
<#inhum>	The inside humidity
<#dew>	The current dew point
<#wetbulb>	Estimated wet bulb temperature, can be seen if hover over 'Dew point' on Cumulus 1 main screen
Rainfall
<#rfall>	The total rainfall so far today (reports rain counter now minus rain counter at start of day), start of day counter can be edited using "edit rain today".
<#rrate>	The current rainfall rate
<#rhour>	The rainfall in the last hour
<#rmidnight>	The total rainfall since midnight. Useful if you don't use midnight as your start of day
<#r24hour>	Reading recent history records, takes rain counter for latest minute, and substracts rain counter from as close as possible to same time yesterday (if Cumulus was not running at that time yesterday, but historical catch-up has been enabled, then it is from nearest time available yesterday, so for a logging interval of every 30 minutes might be 24 hours and 16 minutes ago)
<#LastRainTipISO>	Fixed ISO format output giving date and time of last rain gauge tip (e.g 2010-09-06 06:09) The format is always as shown (cannot use output format modifiers)
<#LastRainTip>	(available from release 3.6.1) Date/time of last rain gauge tip (default format is as set in locale) PLEASE NOTE: this web tag WILL accept any date and time output format modifiers
<#MinutesSinceLastRainTip>	The number of minutes since the last rain gauge tip, in whole numbers, rounded down
<#IsRaining>	For Hydreon RG-11 devices, shows the current rain state. 0=No rain, 1=It's raining
<#rmonth>	The total rainfall so far this month
<#ryear>	Annual rainfall total for rainfall season year (i.e. starting month as set on Configuration menu, station screen, Annual rainfall frame)
<#ConsecutiveRainDays>	The number of days up to (but not including) today where it has rained every day. The threshold amount of rain required to determine a rain day is configurable via the RainDayThreshold setting in cumulus.ini, the units for the threshold are the same as your rain units, meteorologists exclude dew (and other times when single tip of recorder).
<#ConsecutiveDryDays>	The number of days up to (but not including) today since it last rained. The threshold amount of rain required to determine a rain day is configurable via the RainDayThreshold setting in cumulus.ini the units for the threshold are the same as your rain units
Pressure
<#press>	The sea level pressure
<#presstrendval>	The average rate of pressure change over the last three hours. Trend = (pressure_now - pressure_3hrs_ago) / 3 (Fixed from version 1.7.7 5th March 2008)
<#presstrend>	The pressure trend in words - values can be set in the 'strings.ini' file
<#presstrendenglish>	a singe word description for the pressure trend - Rising/Falling/Steady (for use by HTML, javascript etc, values can't be changed). From version 1.8.8 1st December 2009
<#PressChangeLast3Hours>	Available from version 3.11.1 Total Pressure Change since 3 hours ago
<#altimeterpressure>	Altimeter pressure. Pressure corrected to sea level using the station's altitude only. Same as sea-level pressure for non-Davis stations.
Wind
<#wlatest>	Current wind speed reading from console. Corresponds to 'latest' on the Cumulus main screen.
<#bearing>	Current wind bearing in degrees
<#currentwdir>	Current wind bearing as a compass point - e.g. ESE
<#wspeed>	The 10-minute average, if you have Cumulus set to calculate a 10-minute average. Otherwise, it's the latest 'wind' value from the console (i.e. the current speed as determined by the station). Corresponds to 'average' on the Cumulus main screen.
<#avgbearing>	Average wind bearing in degrees over last configured interval minutes. Range 1-360, 0=Calm This is calculated by taking the wind direction and speed for the last 10 minutes (or other interval as configured), calculates the sums of the North/South and East/West vector components, divides the E/W component sum by the N/S component sum, and takes the arctan.
<#wdir>	Average wind bearing over last 10 minutes as a compass point - e.g. ESE
<#wgust>	The highest wind reading in the last 10 minutes. Corresponds to 'gust' on the Cumulus main screen.
<#WindSampleCount>	The number of wind samples making up the wind rose (etc) data (up to 3600)
<#wdirdata>	Comma separated list of recent wind bearing readings (every x seconds, up to 3600 entries). This is a circular buffer; to find the most recent value use <#nextwindindex>. Reading interval x varies by station type: Oregon: x=12 seconds (see https://cumulus.hosiene.co.uk/viewtopic.php?p=37#p37) so 12 hours worth in full array Davis: x=2 or 3 seconds (see https://cumulus.hosiene.co.uk/viewtopic.php?p=37#p37) so 2.5 hours worth in full array Fine Offset: Cumulus 1 reads the wind data every minute (although station transmits wind data every 40 seconds), so 60 hours worth in full array Davis WLL: x=2.5 seconds (see https://cumulus.hosiene.co.uk/viewtopic.php?p=160900#p160900) so 2.5 hours worth in full array
<#wspddata>	Comma separated list of recent individual (non-averaged) wind speed (correspond to 'latest' on the Cumulus main screen) readings (every x seconds, up to 3600 entries). This is a circular buffer; to find the most recent value use nextwindindex tag. Reading interval x varies by station type (see above).
<#nextwindindex>	The index of the entries in <#wdirdata> and <#wspddata> that Cumulus is going to use next - i.e. the latest entry used is one less than this; but don't forget to allow for the wrap around!
<#WindRoseData>	A comma-separated list of the wind 'totals' used to draw the wind rose (8 or 16 values)
<#WindRosePoints>	The number of items in <#WindRoseData> (i.e. 8 or 16), as configured on display settings screen
<#beaufort>	The current wind speed on the Beaufort scale (e.g. F8)
<#beaufortnumber>	The current wind speed on the Beaufort scale, without a leading "F", e.g. "6"
<#beaudesc>	The current wind speed Beaufort description (e.g. "Gale")
<#BearingRangeFrom>	The 'lowest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini)
<#BearingRangeTo>	The 'highest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini)
<#BearingRangeFrom10>	The 'lowest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini), rounded down to nearest 10 degrees
<#BearingRangeTo10>	The 'highest' clockwise bearing in the last 10 minutes (or as configured using AvgBearingMinutes in cumulus.ini), rounded down to nearest 10 degrees
Miscellaneous
<#cloudbase>	Calculated cloud base
<#cloudbasevalue>	Current calculated cloud base without units
<#UV>	Current UV index. Requires your station to have a UV sensor.
<#SolarRad>	Current solar radiation. Requires your station to have a solar sensor.
<#Light>	Current Current light level in Lux. Requires your station to have a solar sensor. Only applies to Fine Offset stations.
<#forecast>	The current forecast
<#forecastenc>	The same as <#forecast> but with all reserved HTML characters, and those above character code 159, encoded as HTML entities
<#forecastJsEnc>	Available from version 3.11.0 The current forecast encoded for JavaScript
<#forecastnumber>	The number relating to the current forecast entry in the strings.ini file. If your station is not providing it's own forecast and Cumulus is not calculating one then 0 (zero) is returned. Note: two negative numbers can be returned by Cumulus: -1 (neg 1) = Exceptional Fine, -26 (neg 26) = Exceptional Bad
<#cumulusforecast>	Always gives Cumulus (Zambretti) forecast, even if the <#forecast> tag provides a station forecast
<#cumulusforecastenc>	The same as <#cumulusforecast> but with all reserved HTML characters, and those above character code 159, encoded as HTML entities
<#cumulusforecastJsEnc>	Available from version 3.11.0 The current Cumulus (Zambretti) forecast encoded for JavaScript
<#wsforecast>	Always gives station forecast (if available)
<#wsforecastenc>	The same as <#wsforecast> but with all reserved HTML characters, and those above character code 159, encoded as HTML entities
<#wsforecastJsEnc>	Available from version 3.11.0 The current station forecast encoded for JavaScript
<#currcond>	Represents the value entered on the screen within Cumulus for the Current Weather condition, or the value as held in the currentconditions.txt file. Any reserved HTML characters are encoded as HTML entities
<#currcondenc>	The same as <#currcond> but also has all characters above (decimal base) code 159 encoded as HTML entities for example this would encode any use of symbol for degree.

Extra Sensors

Some tags are only available for certain builds, if the tables below do not say which releases they apply to, see general tip at top of page to check for the build you are using. In particular Cumulus 1 has fewer channels available in its earlier versions, and the final legacy software version 1.9.4 offers just 42 of the 62 extra sensor web tags available in MX.

The extra sensors functionality in Cumulus only supports processing for current spot values as read from the sensors, the only processing is to convert the units ready for output, so only current conditions can be reported in web tags.

Periodically spot extra sensor values are logged, see the Extra_Sensor_Files page for information about log files from where you can extract the past spot values.

Extra Sensors: Davis models and Oregon Scientific WMR928, WR100/200

These web tags hold current values for additional sensors supported by Cumulus 1 and MX.

For Oregon Scientific model like WMR-200 with USB connection, please refer to #Web tags mentioning (outside) temperature because any of the extra temperature tags below can be redirected to <#temp>, and consequently also have web tags reporting daily extremes and longer period extreme records.

Web tag_name	The related description can be changed in 'strings.ini', but below are default descriptions that will be shown in viewer/editor
<#ExtraTemp1 - 10>	Extra temperature channel 1 to channel 10
<#ExtraDP1 - 10>	Extra dew point channel 1 to channel 10
<#ExtraHum1 - 10>	Extra humidity channel 1 to channel 10
<#SoilTemp1 - 16>	Soil temperature channel 1 to channel 16
<#SoilMoisture1 - 16>	Soil moisture channel 1 to channel 16
<#LeafTemp1 - 4>	Leaf temperature channel 1 to channel 4
<#LeafWetness1 - 4>	Leaf wetness channel 1 to channel 4

Extra Sensors: Davis AirLink

New from version 3.9.0. Not available for earlier MX, not available for Cumulus 1.

Note, that you can configure an Indoor or Outdoor (or both) AirLink, most people will use an outdoor. There are a similar set of tags for each device.

Web tag_name	Function
Particulate Matter
<#AirLinkPm1[InǀOut]>	Current particulate matter of 1 μm, or less count
<#AirLinkPm2p5[InǀOut]>	Currentparticulate matter of 2.5 μm, or less, count
<#AirLinkPm2p5_1hr[InǀOut]>	Last hour average particulate matter of 2.5 μm, or less, count
<#AirLinkPm2p5_3hr[InǀOut]>	Last 3 hours average particulate matter of 2.5 μm, or less, count
<#AirLinkPm2p5_24hr[InǀOut]>	Last 24 hours average particulate matter of 2.5 μm, or less, count
<#AirLinkPm2p5_Nowcast[InǀOut]>	The 24 hour "nowcast" weighted average particulate matter of 2.5 μm, or less, count
<#AirLinkPm10[InǀOut]>	Current particulate matter of 10 μm, or less, count
<#AirLinkPm10_1hr[InǀOut]>	Last hour average particulate matter of 10 μm, or less, count
<#AirLinkPm10_3hr[InǀOut]>	Last 3 hours average particulate matter of 10 μm, or less, count
<#AirLinkPm10_24hr[InǀOut]>	Last 24 hours average particulate matter of 10 μm, or less, count
<#AirLinkPm10_Nowcast[InǀOut]>	The 24 hour "nowcast" weighted average particulate matter of 10 μm, or less, count
Air Quality Index Values
<#AirLinkAqiPm2p5[InǀOut]>	Current particulate matter of 2.5 μm, or less AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm2p5_1hr[InǀOut]>	Last hour average particulate matter of 2.5 μm, or less, AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm2p5_3hr[InǀOut]>	Last 3 hour average particulate matter of 2.5 μm, or less, AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm2p5_24hr[InǀOut]>	Last 24 hour average particulate matter of 2.5 μm, or less, AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm2p5_Nowcast[InǀOut]>	Last 24 hour "nowcast" weighted average particulate matter of 2.5 μm, or less, AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm210[InǀOut]>	Current particulate matter of 10 μm, or less value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm10_1hr[InǀOut]>	Last hour average particulate matter of 10 μm, or less, AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm10_3hr[InǀOut]>	Last 3 hour average particulate matter of 10 μm, or less AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm10_24hr[InǀOut]>	Last 24 hour average particulate matter of 10 μm, or less AQI value - allows use of the "dp=n" and "tc=y" parameters
<#AirLinkAqiPm10_Nowcast[InǀOut]>	Last 24 hour "nowcast" weighted average particulate matter of 10 μm, or less AQI value - allows use of the "dp=n" and "tc=y" parameters
Stats Values
<#AirLinkPct_1hr[InǀOut]>	Percentage of possible values that were included in the 1 hour averages
<#AirLinkPct_3hr[InǀOut]>	Percentage of possible values that were included in the 3 hour averages
<#AirLinkPct_24hr[InǀOut]>	Percentage of possible values that were included in the 24 hour averages
<#AirLinkPct_1hr[InǀOut]>	Percentage of possible values that were included in the 24 hour weighted averages
Sensor Info
<#AirLinkFirmwareVersion[InǀOut]>	Shows the AirLink firmware version as a date string. NOTE: This web tag requires a WeatherLink Pro subscription to work
<#AirLinkTemp[InǀOut]>	The sensors internal temperatue value
<#AirLinkHum[InǀOut]>	The sensors internal humidity value
<#AirLinkWifiRssi[InǀOut]>	The sensors WiFi signal strength in dB - anything below -90 is considered very poor. NOTE: This web tag requires a WeatherLink Pro subscription to work

Extra Sensors: Ecowitt

Ecowitt stations are sold under other names depending on nation, e.g. Ambient in USA, Froggit in central Europe, so Ecowitt is used as a generic name in same way as Fine Offset is used as a generic name for stations sold under a variety of branding, in this Wiki.

Not available in Cumulus 1.

Extra Sensors: Ecowitt WH45 CO₂ sensor

Unless otherwise indicated these web tags become available from release 3.9.5.

Web tag_name	Function
<#CO2>	The actual CO2concentration in ppm
<#CO2-pm2p5>	Air Quality expressed in terms of particulate matter of 2.5 μm/m3 or less
<#CO2-pm2p5-24h>	Air Quality expressed in terms of particulate matter of 2.5 μm/m3, or less, 24 hours moving average
<#CO2-pm10>	Air Quality expressed in terms of particulate matter of 10 μm/m3, or less (yes, this includes the 2.5 figure)
<#CO2-pm10-24h>	Air Quality expressed in terms of particulate matter of 10 μm/m3, or less, 24 hours moving average
<#CO2-temp>	Temperature as reported by Air Quality monitor. Note that this temperature has nothing to do with the temperature as reported by the main weather station. It reflects the temperature of the sensor and would be used in combination with the sensors measured humidity (see next) for correction of the measured PM (particulate matter) value. Determination of how to correct the PM value is highly dependent on the conditions and placement of the sensor. See the specification sheet for the sensor or create some multivariate regression line based on calibration measurements. This is also valid for PM sensors like the AirLink. The normal amateur usage of PM sensors is that the uncorrected values are published.
<#CO2-hum>	Relative Humidity as reported by Air Quality monitor

Extra Sensors: Ecowitt WH34 soil and water sensor

Cumulus MX can support the Ecowitt WH34 (other model types exist and are reported here as if WH34) soil and water temperature sensors.

They are reported as "User Temperture 1" to "User Temperature 8", as listed in the table within next sub-section.

Extra Sensors: Ecowitt Air quality, leak sensors, lighting detector, and extra temperature sensors

Not available in Cumulus 1.

Please see release announcements for when individual web tags became available

This sub-section applies only to those using Ecowitt GW1000 (also Froggit DS1500, and other equivalents, see Supported Devices) an interface unit that picks up various external sensors and sends the data via an application programming interface to MX which then generates the following web tags:

Web tag_name	Function
<#GW1000FirmwareVersion>	GW1000 firmware version string

Web tag_name	The related description can be changed in 'strings.ini', but below are default descriptions that will be shown in the viewer/editor
<#AirQuality1>	Air quality in μm/m3 or less
<#AirQuality2>	Air quality in μm/m3 or less
... and so on up to <#AirQuality4>
<#AirQualityAvg1>	24 hr running average Air quality in μm/m3 or less
<#AirQualityAvg2>	24 hr running average Air quality in μm/m3 or less
... and so on up to <#AirQualityAvg4>
<#LeakSensor1>	Leak sensor 1 - returns false/true as 0 or 1
<#LeakSensor2>	Leak sensor 2 - returns false/true as 0 or 1
... and so on up to <#LeakSensor4>
<#LightningDistance>	Distance to last strike (same units as wind run - miles/km/nm) (Returns 0.0 if you don't have a sensor, GW1000 api returns max value you can put in a byte - 0xFF which translates to 158.4 miles = 255 km if have sensor but no strike detected yet, so MX translates that to '----')
<#LightningTime>	Date and Time of last strike (default without output parameters is locale's short time format e.g. 18:02 or 6:02 pm, without date, but tag accepts both date and time output parameters). Returns '----' if you don't have sensor or there has not been a strike since the sensor was installed. (GW1000 api returns FFFF FFFF seconds after midnight on 01 Jan 1970, which translates to 07/02/2106 06:28:15, so MX translates that to '----')
<#LightningSrikesToday>	Number of lighting strikes today
<#UserTemp1>	User Temperature 1
... and so on up to <#UserTemp8> = User temperature 8

Recent History

Please refer to the Recent history page for full information about using the tags in the following two tables, as material once on this page has been moved there.

Using input/output modification parameters with recent history tag names

All tag names listed below, require the mandatory input modification parameters specified in this table.

The optional output modification parameters available are as specified in this table, depending on tag name:

Tag names	Mandatory Input Modification Parameters	Optional Output Modification Parameters
<#RecentTS> (see #Table of Recent History tag names available)	Mandatory parameters as table at Webtags/Parameters#Input_modification_Parameters	Optional parameters to modify the time format described in tables starting at Webtags/Parameters#Multiple_Output_Format_Modifier_parameters_for_times_and_dates
All other tag names in #Available in 1.9.3, 1.9.4, and all MX releases and #Available in MX only	Mandatory parameters as table at Webtags/Parameters#Input_modification_Parameters	Whether you can modify the way these values are output depends on release you are using: From release 3.10.5: Please see tables at Webtags/Parameters#Output_Modification_Parameter_for_changing_any_decimal_comma_into_a_decimal_point and Webtags/Parameters#Controlling_the_number_of_decimal_places For legacy Cumulus, and earlier MX releases, no output format modification parameters are available, instead see #No_Commas section on this page.

Table of Recent History tag names available

One tag name is available since 1.9.3 to report the time associated with values you request.

Although as Recent history page explains, the history is intended to cover every minute in last 7 days, some entries may be at less frequent intervals, and when clocks change some entries will be missing altogether.

Web tag_name	Function	Parameters example
Time-stamp tag
<#RecentTS>	Gives the timestamp of the data that will be returned for any other recent history tag that uses same d, h, and m parameters	<#RecentTS h=3 m=1 format="HH:nn"> for cumulus 1; <#RecentTS h=3 m=1 format="HH:mm"> for cumulus MX

Available in 1.9.3, 1.9.4, and all MX releases

Tag_name	Function	Input Modification Parameters example
Temperature & Humidity tags
<#RecentOutsideTemp>	Outside Temperature	<#RecentOutsideTemp h=3 m=1> <#tempunit> will display the temperature at the start of the period for which <#temptrend> is calculated
<#RecentWindChill>	Wind Chill	<#RecentWindChill d=48 m=1> reports the wind chill temperature 2 days ago
<#RecentDewPoint>	Dew Point	<#RecentDewPoint h=25> reports the dew point temperature just over a day ago
<#RecentHeatIndex>	Heat Index	<#RecentHeatIndex m=121> reports the heat index about 2 hours ago
<#RecentHumidity>	Relative Humidity	d=n (where n runs 0 to 6) days ago; h=n (where n is any number of hours ago); m=n (where n is any number of minutes ago)
Wind (Note: Wind 'Speed', 'Gust' and 'Latest' have the usual Cumulus meanings see Wind measurement)
<#RecentWindSpeed>	Wind Speed	<#RecentWindSpeed m=10> will display the average wind speed 10 minutes ago
<#RecentWindGust>	Wind Gust (reports maximum gust from build 1088 of version 1.9.4)	<#RecentWindGust d=1 m=1> will report the wind gust at approximately the same time yesterday
<#RecentWindLatest>	Wind Latest.	d=n (where n runs 0 to 6) days ago; h=n (where n is any number of hours ago); m=n (where n is any number of minutes ago)
<#RecentWindDir>	Wind Direction (instantaneous)	<#RecentWindDir m=10> will tell you which direction the wind was blowing from 10 minutes ago
<#RecentWindAvgDir>	Wind Direction (average)	<#RecentWindAvgDir d=6> will say what the calculated average wind direction was at this time at the start of the week
Pressure
<#RecentPressure>	Sea-level Pressure	<#RecentPressure h=3 m=1> gives the sea level pressure when <#presstrendval> started tracking the pressure
Rainfall
<#RecentRainToday>	Daily rain total from last roll-over to specified time	d=n (where n runs 0 to 6) days ago; h=n (where n is any number of hours ago); m=n (where n is any number of minutes ago)
Solar & UV
<#RecentSolarRad>	Solar Radiation	d=n (where n runs 0 to 6) days ago; h=n (where n is any number of hours ago); m=n (where n is any number of minutes ago)
<#RecentUV>	UV Index	d=n (where n runs 0 to 6) days ago; h=n (where n is any number of hours ago); m=n (where n is any number of minutes ago)

Available in MX only

Please note this section has NOT yet been updated for recent MX releases, it appears from RecentData table in cumulusmx.db that the list here is not complete for MX. However, no release announcement has been found listing tag names not shown here (i.e. apparent temperature, indoor temperature and humidity, air quality)

tag_name	Introduced	Function	Input Modification Parameters example
Indoor Temperature & Humidity tags
(to do)
Outdoor Temperature & Humidity tags
<#RecentWindChill>	Legacy Cumulus version 1.8.5	Wind Chill (if temperature is below 10°C or 50 °F, then the new Feels Like now available in MX (next item) will report this same value).	<#RecentWindChill d=48 m=1> reports the wind chill temperature 2 days ago
<#RecentFeelsLike>	Available from version 3.6.11 (build 3087) onwards.	Feels Like Temperature	<#RecentFeelsLike h=12 m=1> reports the feel like temperature 12 hours ago
<#RecentHumidex>	Available from version 3.7.0 (build 3089) onwards.	Canadian Humidity Index (humidex) Dimensionless - no units	<#RecentHumidex h=3> reports humidex 3 hours ago
Air Quality tags

System

Special tags returning information about the Windows device hosting Cumulus 1.

If you are running MX, then most tags do not work.

Web tag_name	Applicability	Function
<#OsVersion>	up to 1.9.4, and MX	OS version, e.g. "Windows 7 x64 build 7600" Please note this may not return the information you expect!
<#OsLanguage>	Both leagacy and MX	OS language, e.g. "English"
<#SystemUpTime>	(not available on MX) only in legacy Cumulus	How long the system has been up, e.g. "8 hours 21 minutes"
<#ProgramUpTime>	all releases	How long Cumulus has been running, e.g. "7 hours 55 minutes"
<#CpuName>	(not available on MX) only in legacy Cumulus	CPU type, e.g. "Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz"
<#CpuCount>	(not available on MX) only in legacy Cumulus	Number of processors, e.g. "4"
<#MemoryStatus>	(not available on MX) only in legacy Cumulus	Free and total system RAM, e.g. "4619/8191 MB (free/total)"
<#DisplayMode>	(not available on MX) only in legacy Cumulus	Screen display mode, e.g. "1680x1050, 32 bit"
<#AllocatedMemory>	(not available on MX) only in legacy Cumulus	Amount of memory allocated to Cumulus, e.g. "18.76 MB"
<#DiskSize>	(not available on MX) only in legacy Cumulus	Size of disk on which Cumulus is running, e.g. "931.51 GB"
<#DiskFree>	(not available on MX) only in legacy Cumulus	Free space on disk on which Cumulus is running, e.g. "515.36 GB"

Miscellaneous

All tags are available in all flavours, as far as I know, although their output might vary, and which input/output parameters they permit might vary between Cumulus 1 and MX.

Web tag_name	Function
<#LatestError>	Displays the last error from the Cumulus 1 error log. (The value is cleared when you click the error light in Cumulus 1). Note: This tag displays all errors, even if they do not cause the error light to flash in Cumulus 1. Although this tag and the next 3 are in MX, none of them are actually used (as at April 2020).
<#LatestErrorDate>	The date of the latest error logged to the error log window, using the system short date format. Gives dashes when latest error is reset
<#LatestErrorTime>	The time of the latest error logged to the error log window, using the system short time format. Gives dashes when latest error is reset
<#ErrorLight>	1 if the 'error' light is flashing, 0 if not
<#version>	The version of Cumulus in use e.g. '1.9.4' or '3.4.1'
<#build>	The build of Cumulus in use e.g. '10992' for latest Cumulus 1 patch (Cumulus MX is under development so new builds are released frequently)
<#NewBuildAvailable>	Only available from release 3.7.0 onwards, it is checked on start-up and once a day thereafter at a random time Returns a boolean value 0 - MX running the latest build available 1 - MX is running an earlier build that the latest public release
<#NewBuildNumber>	Only available from release 3.7.0 onwards, it is checked on start-up and once a day thereafter at a random time Displays the latest public release build number - eg. b3089
<#realtimeinterval>	The real time update interval in seconds (integer)
<#interval>	The web site update interval in minutes (integer)
<#rollovertime>	The time that the logs rollover to the next day: will always return one of these: 'Midnight', '9 am' or '10 am' This is the end of the meteorological day, so if during Daylight Saving Time rolover is at "10 am", then on the day DST ends it will return to "9 am" ensuring every meteorological day is exactly 24 hours long. If the time is "Midnight" (or during DST it is "9 am"), then days will be 23 or 25 hours long just on day clocks change, 24 hours otherwise.
<#update>	The date and time of the last web site update. The default format of the output depends on your locale settings.
<#LastDataReadT>	The date/time data was last read from the station. The default format of the output depends on your locale settings.
<#stationtype>	The weather station model description (you choose what text appears for this on 'Display' settings screen within Configuration menu - the field is at the bottom left of that screen).
<#latitude>	The station latitude (as you entered during setup). Supports an optional 'dp' parameter, if supplied, instead of the usual web-encoded text format with degrees/minutes/seconds, the result is in decimal degrees to the specified number of decimal places. E.g <#latitude> gives "N 59& deg;&nbsp;14&#39;&nbsp;33&quot;" for N 59 14 33 <#latitude dp=5> gives "59.24250" If the "dp" parameter is supplied, then supplying "rc=y" in addition will cause any decimal comma to be converted to a decimal point.
<#latitudeJsEnc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is HTML encoded
<#longitude>	The station longitude (as you entered during setup). Supports an optional 'dp' and 'rc' parameters as per the latitude tag.
<#longitudeJsEnc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is HTML encoded
<#altitude>	The station altitude value (web tag outputs web encoded format containing figure, '&nbsp;' and units) in either feet or metres just as you entered during setup (so it is more complex to extract number for script arithmetic); e.g. '123&nbsp;m'
<#altitudenoenc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is HTML encoded
<#location>	The station location (as you entered during setup)
<#locationJsEnc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is plain text
<#locationenc>	Available from version 3.10.3 HTML encoded version of previous web tag that is JavaScript encoded
<#longlocation>	Longer description of the station location (as you entered during setup)
<#longlocationJsEnc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is plain text
<#longlocationenc>	Available from version 3.10.3 HTML encoded version of previous web tag that is JavaScript encoded
<#forum>	URL of the forum (as you entered during setup) encoded into a web page menu item by adding colons For Cumulus 1, this defaults to a Sandaysoft URL that is no longer available, for MX this defaults to the current support forum (web server site hosted by "Freddie")
<#forumurl>	Available from version 3.10.0 Same as previous, but just URL, without any additional colons
<#webcam>	URL of the webcam (as you entered during setup) encoded into a web page menu item by adding colons. Default is blank. Can be used to link to any other web page that you host (Cumulus does not verify that it is a web can, that is just a label, and the label can be changed on each standard web page individually)
<#webcamurl>	Available from version 3.10.0 Same as previous, but just URL, without any additional colons
<#graphperiod>	The number of hours displayed by the graphs, as set using Configuration menu, Display settings screen 'Detailed Chart Period'
<#dailygraphperiod>	The number of days displayed by the graphs, as set using Configuration menu, Display settings screen 'Daily Chart Period' (available from build 1098)
<#LatestNOAAMonthlyReport>	Gives file name of latest auto-saved NOAA monthly report
<#LatestNOAAYearlyReport>	Gives file name of latest auto-saved NOAA yearly report
Options Available from version 3.10.0
<#Option_useApparent>	Whether user prefers to see Apparent Temperature or Feels Like Temperature
<#Option_showSolar>	Whether user wants to show Solar data or does not not have a solar sensor
<#Option_showUV>	Whether user wants to show Ultra Violet data or does not not have a UV sensor

Units

Apply to Cumulus 1 and MX, no optional input nor output parameters.

Web tag_name	Function
<#tempunit>	Unit of temperature being used (Set in Cumulus as Celsius or Fahrenheit) values "&deg;C" or "&deg;F"
<#tempunitnoenc>	Available from version 3.11.0 JavaScript encoded of previous web tag that is HTML encoded (i.e. without & and without °)
<#tempunitnodeg>	The temperature units being used, without a degree symbol, i.e. "F" or "C"
<#pressunit>	Unit of measure for pressure. Possible values: "mb", "hPa", "in"
<#rainunit>	Unit of measure for rain fall. Possible values: "mm" or "inches"
<#windunit>	Unit of measure for wind speed. Possible values: "m/s", "mph", "km/h", "kts"
<#windrununit>	Unit of measure for wind run (distance). Possible values: "km", "miles", "km", "nm" (for wind speeds in m/s, mph, km/h, kts)
<#cloudbaseunit>	The units used for cloudbase value. Possible values: "ft" or "m"

Date & Time

Both Cumulus 1 and MX support all of these, except where marked as MX only, most of these web tags can be used with output parameters.

Web tag_name	Function
<#date>	The current date - format depends on locale you use to run Cumulus
<#metdate>	The current meteorological date. The default format depends on the locale you use to run Cumulus If you use midnight rollover, this returns same date as <#date> (above), but with a different default format. If using a 9am/10am rollover: After rollover time on current calendar date, this is same as <#date>, but with a different default format. Between midnight and 9am/10am the <#metdate> will return the date associated with previous calendar day, but will still return current time Legacy website: Can be used with relevant format parameters to customise todayT.htm template page to display current meteorological day, to customise thismonthT.htm template page to display meteorological month, and to customise thisyearT.htm template page to display correct meteorological year. This will be particularly useful on first and last day of month/year when rollover happens at 9 (or 10) a.m. and the month (and maybe year) is different before and after rollover. Earlier MX releases provide a similar web template set, so these can be customised in same way as for legacy Cumulus above (but note capital "M" must be used for any month formatting). From release 3.10.1 the supplied web pages are web server based, there are no web templates to customise, and the supplied .json files do not include any meteorological date functionality.
<#timeUTC>	The current UTC date/time rather than local date/time. Example result (actual format depends on locale settings): 18:30 on 30 December 2009. If you want the local date and time, use next tag (below).
<#time>	The current time and date. Example result (actual format depends on locale settings): 18:30 on 30 December 2009. If you simply wish the time, use next tag (below).
<#timehhmmss>	The current time (without date). Example format: 18:30:27. You can use output format specifiers to change the way the time is output, but any date specifiers are ignored.
<#minute>	The current time, just the minutes. Fixed format: 07 (cannot use output format modifiers)
<#hour>	The current time, just the hour. Fixed format: 07 (cannot use output format modifiers)
<#day>	The current day as a 2-digit number. Fixed format: 07 (cannot use output format modifiers)
<#dayname>	The current day as a word. For example, Monday (actual format depends on locale settings)
<#shortdayname>	The current day as a shortened word. Example format: Mon
<#month>	The current month as a 2-digit number. Fixed format: 07 (cannot use output format modifiers)
<#monthname>	The current month as a word. Example format: July
<#shortmonthname>	The current month as a shortened word. Example format: Jul
<#year>	The current year as a 4-digit number. Example format: 2009 (cannot use output format modifiers)
<#shortyear>	The current year as a 2-digit number. Example format: 09 (cannot use output format modifiers)
<#rollovertime>	The time that the logs rollover to the next day: 'Midnight', '9 am' or '10 am' PHP code example for testing whether before or after rollover given in next entry.
<#metdateyesterday>	The previous meteorological date. The default format depends on the locale you use to run Cumulus If you use midnight rollover, this returns same date as <#date>, but with a different default format. If using a 9am/10am rollover: After rollover time on current calendar date, this is same as <#yesterday> (below), but with a different default format. Between midnight and 9am/10am the date output by <#metdateyesterday> will be the calendar day before that returned by <#yesterday>, but the time returned is actual local time. Can be used with relevant format parameters to indicate correct day on yesterdayT.htm template page, and can be used to return latest day stored on dayfile.txt and NOAA report for latest month. if you use PHP Hypertext preprocessor, you can output different text for before and after rollover, e.g. <?php if('<#yesterday format=dddd>' == '<#metdateyesterday format=dddd>') echo '(calendar date and meteorological date same)'; else echo 'rollover still to happen, these results will be treated as belonging to <#metdate format=dddd>';?>
<#yesterday>	Yesterday's date. The default format depends on the locale you use to run Cumulus
<#update>	The date and time of the last web site update. The default format depends on the locale you use to run Cumulus
<#timeJavaScript>	Available from version 3.5.2, so not available in legacy software The JavaScript Date object contains the number of miliseconds since 00:00:00.000 UTC on 1st January 1970, that date and time is known as the UNIX Epoch. In JavaScript, you can use Math.floor(new Date().getTime()/1000.0) This getTime method returns the time in milliseconds. The web tag returns an integer (currently with 13 digits) representing the number of milliseconds since the UNIX epoch when the web tag was processed. It can be used in a script where you wish to re-express other times output by Cumulus MX into UTC (Coordinated Universal Time). Mac OS X uses 00:00:00.000 UTC on 1st January 2001 as the starting time and date for its millisecond count, so that is considerably lower. Note that UTC is calculated using 9192631770 times a particular transition time for Caesium 133 as a basis for 1 second. GMT (Greenwich Mean Time) is calculated on the basis that 1 second is 1/86400 of the time taken for a whole (day) rotation of the Earth. UT1 (or solar time) is calculated from various space measurements. Periodically, leap seconds are added to UTC to realign it with UT1, but these leap seconds are not added to the count of milliseconds represented by this web tag. Do be aware that some devices will use a 32 bit signed integer to represent this number, and that will stop working on 19 January 2038, the year 2038 problem for computing world.
<#timeUnix>	Available from version 3.7.0, so not available in legacy software Unix tracks the number of seconds since the UNIX epoch. So this web tag can be used when you do not want the millisecond accuracy of the previous web tag. Like previous web tag this relates to UTC, so see details for that tag to find out more. This is equivalent in PHP 5 and PHP 7 to time(); (in PHP 8, a parameter is mandatory for time function, so the call changes).
<#LastDataReadT>	The date/time data was last read from the station. Default format for this tag is like this example 18:30 on 30 December 2009, but output parameters for both date and time can modify this to include seconds in 1.9.x builds and most MX builds such as per this example '<#LastDataReadT format="yyyy-MM-dd HH:mm:ss">'.
<#DaysSince30Dec1899>	Day count (gives whole and fractional part) Example: 41250.6523310301
<#recordsbegandate>	Date when records began (appears twice on "recordT.htm" provided in standard web page, and used to calculate next tag, but ignored for all other Cumulus processing). Any output parameters valid for a date can be used here, don't forget differences in modifiers for Cumulus 1 and MX. There is no time associated with this web tag. The default format is like 30 December 2009, please note although this web tag reports the value associated with [b]StartDate=dd/MM/yyyy[/b] (see Cumulus.ini#Section:_Station), the format there is short-date format and different to default format for this web tag.
<#DaysSinceRecordsBegan>	Day count since Cumulus records started

Today

Cumulus allows some control over the time that "Today" begins:

• For the weather diary feature (originally called "The Log" if you have a very old release or look at old posts on the support forum), Cumulus classifies what you enter by a date. The hour of the day, when that date is first applied, is set in the configuration by the SnowDepthHour (called that as the only tag name available in the legacy Cumulus was for Snow Depth.
  • The default snow depth hour is 9 for the legacy Cumulus and 0 for MX.
• Readings from your weather station are assigned to the "Today" based on 3 options for Meteorological day
  1. starting at 9:00 am, based on winter time, so switching to 10:00 during Daylight Saving (summer) time, or
  2. starting at 9:00 am, all year round, or
  3. aligned with calendar days, so today starts at midnight

The practice for professional meteorologists varies between nations, some of the traditional practices listed below have been abandoned now most weather reading is by machines:

• Generally, Meteorologists report snowfall, and snow days, on a calendar day basis (i.e. midnight to midnight).
• Most frequently, the Lowest temperature for a day is that recorded prior to the start time for Highest temperature.
  • This is because Meteorologists in the past took manual observations at one, or more, fixed times during each day (9 a.m. was the most common, and the closest lowest temperature was generally earlier that morning, while the closest highest temperature was generally the following afternoon)
• Sunshine hours were recorded from sunrise to sunset, so assigned to "Today" aligned with calendar day
• The way that total rainfall was reported varied:
  • Some nations assigned used days that ended at 9 a.m. so rainfall was recorded against the end date
  • Sometimes totals were recorded separately for 9 a.m to 3 p.m, with 3 p.m. to 9 a.m being assigned to next day (again these were manual observation times)
  • In other cases, the total for 9 p.m to 9 a.m was recorded separately, and possibly assigned to the day after the total for 9 a.m. to 9 p.m.

Cumulus does not support most of these practices. The independence of the start time for weather diary and weather station related web tags means needs to be remembered when labelling web tags from the two tables below. Steve Loft assumed that you would use 9 a.m. as start time for both, but not care when snow fell, as it often has in the UK, after Summer Time has begun, so weather station tags were by default reporting from 10 a.m. local time and snow as at 9 a.m.

In MX, if you choose 9 a.m. (optionally 10 a.m. in summer) for rollover, so all the standard derivative are assigned to the date the meteorological day starts as Today, but the sunshine hours recorded against today will be from midnight on the said date.

Weather Diary

This first table lists all the web tags available for reporting what is recorded in the weather diary. Just to be clear, the web tags shown below, will report data for previous day if the current time is before the snow depth hour setting, and report data for the current day if the current time matches the snow depth hour or is later.

Web tag_name	Function
<#snowdepth>	Meteorologists report snow depth in cm, so this is default unit for Cumulus. If there is no entry in Weather Diary for the day explained above, reports zero. Input is to 2 decimal places. Available from version 3.1.1 - build 3054 when weather diary editor was added to MX. MX allows output in centimetres with decimal places without any script. You can't change the units shown in admin interface, but your value can be input as inches to 2 decimal places if you ignore "cm" that is displayed in that interface. Input and output is always as integer. Available from very early builds, weather diary input amended from version 1.8.6 14th April 2009 to allow units to be specified on diary edit screen. If you choose to enter as whole millimetres, you can use JavaScript (or another script language) on your web page to divide the web tag by 10 and get centimetres to 1 decimal place on output.
MX only
<#snowlying>	Available from version 3.1.1 - build 3054. If there is no entry in Weather Diary for the day explained above, , this web tag returns Null. Otherwise reports 1 if tick in diary, 0 is unticked. Although this tag is not available in Cumulus 1, your web page can use a script to check if <#snowdepth> is non zero, as that means snow is lying
<#snowfalling>	Available from version 3.1.1 - build 3054. If there is no entry in Weather Diary for the day explained above, , this web tag returns Null. Otherwise reports 1 if tick in diary, 0 is unticked. Not available in Cumulus 1. There is no web page workaround, unless you write a script that reads Weather Diary and makes relevant information available on your web server.

Today.ini

As explained earlier, these tag names relate to latest Meteorological day and they are populated from information held in today.ini, as the sub-section title suggests; except for Sunshine Hours which relate to latest Calendar day and can be taken from either yesterday.ini or "today.ini" depending on (respectively) whether before or after rollover time if that is not midnight.

Where a tag name reports a value specific to a past time in today-so-far, there will also be a tag name that can give the time of day, shown in same row of table below. For those that cover whole day so far, the final column contains "n/a". Please note none of the time tags can be modified by output parameters to give a date, but they can be changed from the default time format that is 'H:mm' (24 hour clock notation without leading zero for hour) for Cumulus 1 and MX.

Also as explained earlier, there is some inconsistency in naming with "T" not included in all tag names, "T" is used in conjunction with "H" or "L" as a suffix for extreme values/time-stamps, but a prefix "T" can identify today's value, or prefix "T" can signify a time-stamp.

In the legacy todayT.htm template, in the legacy "/web" folder, use was made of a selection of the tag names listed here.

If you are using MX, the today and yesterday page in the MX_Administrative_Interface shows similar information by using the local application programming interface.

Web tag_name	Function	Time tag_name
Temperature & Humidity
<#tempTH>	Today's highest temperature	<#TtempTH>
<#tempTL>	Today's lowest temperature	<#TtempTL>
<#avgtemp>	The average temperature so far today (calculated from all temperature readings processed by Cumulus, today.ini stores a cumulative aggregate and counts the number of values processed, so a division gives this output)	n/a
<#temprange>	The temperature range (<#tempTH> - <#tempTL>) so far today (Cumulus calculates all these tags using Celsius values, but outputs them in your chosen units)	n/a
<#apptempTH>	Today's high apparent temperature	<#TapptempTH>
<#apptempTL>	Today's low apparent temperature	<#TapptempTL>
MX only
<#feelslikeTH>	Available from version 3.6.10 (NOT AVAILABLE IN CUMULUS 1) Today's high feels like temperature Please see sub-section below current conditions if you are using an earlier 3.6.x version of MX.	<#TfeelslikeTH>
<#feelslikeTL>	Available from version 3.6.10 (NOT AVAILABLE IN CUMULUS 1) Today's low feels like temperature	<#TfeelslikeTL>
<#humidexTH>	Available from version 3.7.0 (NOT AVAILABLE IN CUMULUS 1) Today's high Canadian Humidity Index Please see sub-section below current conditions if you are using Cumulus 1 or an earlier version of MX.	<#ThumidexTH>
Both legacy and MX
<#heatindexTH>	Today's high heat index	<#TheatindexTH>
<#wchillTL>	Today's greatest wind chill (i.e. lowest temperature, highest wind speed)	<#TwchillTL>
<#dewpointTH>	Today's highest dew point	<#TdewpointTH>
<#dewpointTL>	Today's lowest dew point	<#TdewpointTL>
<#humTH>	Today's highest humidity	<#ThumTH>
<#humTL>	Today's lowest humidity	<#ThumTL>
Precipitation
<#rrateTM>	Today's maximum rain rate	<#TrrateTM>
<#hourlyrainTH>	Today's highest hourly rain	<#ThourlyrainTH>
<#RG11RainToday>	If you have an RG-11 rain sensor configured in "Tipping Bucket" mode, this gives today's rain total so far according to the sensor	n/a
Pressure
<#pressTH>	Today's highest pressure reading	<#TpressTH>
<#pressTL>	Today's lowest pressure reading	<#TpressTL>
Wind
<#windTM>	Today's maximum (average) wind speed	<#TwindTM>
<#wgustTM>	Today's maximum wind gust	<#TwgustTM>
<#bearingTM>	The wind bearing at the time of today's high gust (<#wgustTM>) in degrees	<#TwgustTM>
<#Tbeaufort>	Today's highest wind speed, expressed in the Beaufort scale	<#TwindTM>
<#Tbeaufortnumber>	Today's high wind speed on the Beaufort scale, without a leading "F", e.g. "6"	<#TwindTM>
<#windrun>	The total wind run so far today	N/A
<#windAvg>	(Available from release 3.12.0 onwards) The wind run divided by time passed since rollover to express it as an average wind speed	n/a
<#domwindbearing>	Today's dominant wind direction in degrees	n/a
<#domwinddir>	Today's dominant wind direction as compass point	n/a
<#Tbeaudesc>	Beaufort 'description' for today's high wind speed	n/a
Miscellaneous
<#ET>	Today's evapotranspiration. Applies only to Davis stations, equipped with a solar sensor. "The ET value provided to Cumulus by the console and/or DLL is buggy and unreliable. It often shows a negative value. See this FAQ."	N/A
<#heatdegdays>	Today's heating degree days	n/a
<#cooldegdays>	Today's cooling degree days	n/a
<#solarTH>	Today's high solar radiation value (Solar sensor needed)	<#TsolarTH>
<#UVTH>	Today's high UV Index (UV sensor needed)	<#TUVTH>
<#SunshineHours>	Today's hours of sunshine so far. Added in Cumulus 2, then to 1.9.1 build 957, also available in MX. From version 3.7.0 takes a parameter "dp=n" so the number of decimal places required can be specified	n/a
MX only
<#LightningStrikesToday>	Number of strikes since midnight, default 0 - Added at 3.2.0 - b3056, but see subsequent release announcements as the handling of lightning was improved gradually over several subsequent releases. (other lightning tags can be found in Current Conditions table)
<#chillhoursToday>	The incremental chill hours figure since start of today (tag name available from version 3.12.0 beta build 3134, but the coding to process this web tag has a bug at time of adding this note to this Wiki page, as it may incorrectly report 99.99; hopefully a calculation using <#Ychillhours> and <#chillhours> will work better) (Compare with Cumulative seasonal Chill Hours at end of today <#chillhours> found in Current Conditions table)

No Commas

This section is for those locales where a comma is used instead of a full stop to separate the integer and decimal parts of a number. This section on this Wiki page was written for the legacy Cumulus (1.9.4) software. Although tag names in this section can be used in Cumulus MX, for backwards compatibility, there is now a better way to ensure that the value output by web tags can be understood by script languages which expect a full stop between the integer and decimal parts of a number.

Note that Cumulus does not use thousand separators, so the only places a comma can be used are as a field separator, or as a decimal separator. Obviously it cannot be used for both. Some computer languages like JavaScript will not accept a comma being used for this purpose.

MX

Cumulus MX uses JavaScript Object Notation files for many of its data transfers.

From release 3.5.4 build 3075, most web tags (one notable exception is indoor temperature <#intemp> where rc parameter not available until release 3.6.8 build 3084), that produce decimal number output now support the "rc=y" option. e.g. <#tempYH rc=y> will report yesterday's highest temperature using a full stop to separate decimal part where the locale would normally use a comma.

Legacy Cumulus

Cumulus 1.9.4 uses JavaScript for various tasks, as do various third party web pages.

From version 1.9.3 build 1045, Cumulus 1 (and MX) has provided some current conditions web tags, some today web tags, and some recent history web tags in an alternative format where (regardless of locale) the number is always output in a format that uses a decimal point. They are listed in the sub-sections that follow and all correspond to the same tag name with the letters 'RC' removed that has been listed in respective sections of this Wiki page.

RC CURRENT CONDITIONS:

<#RCtemp>, <#RCdew>, <#RCheatindex>, <#RChum>, <#RCinhum>, <#RCintemp>, <#RCpress>, <#RCrfall>, <#RCrrate>, <#RCwchill>, <#RCwgust>, <#RCwspeed>, <#RCwlatest>

RC TODAY:

<#RCpressTH>, <#RCpressTL>, <#RCrrateTM>, <#RCtempTH>, <#RCtempTL>, <#RCwgustTM>, <#RCdewpointTH>, <#RCdewpointTL>, <#RCwchillTL>, <#RCheatindexTH>, <#RCapptempTH>, <#RCapptempTL>

RC RECENT HISTORY:

<#RCRecentOutsideTemp>, <#RCRecentWindSpeed>, <#RCRecentWindGust>, <#RCRecentWindLatest>, <#RCRecentWindChill>, <#RCRecentDewPoint>, <#RCRecentHeatIndex>, <#RCRecentPressure>, <#RCRecentRainToday>, <#RCRecentUV>

Although 'Apparent Temperature' is not included as a tag, it can be calculated in a script from the RC tags for 'outside temperature', 'wind speed', and 'relative humidity' values. In php language this is $RCapptempCALC = round(<#temp> + (0.33 * (<#hum> / 100 * 6.105 * exp (17.27 * <#temp> / (237.7 + <#temp>) ))) - (0.7 * $wspeed) - 4.0, 2);.

There are other derivatives that can be calculated similarly from a set of simultaneous values, as described below the recent history section.

Yesterday

Note that the Y indicating yesterday is sometimes a prefix, sometimes a suffix (with H for High, L for Low), web tags are not named consistently!

Many of these web tags are used on the supplied yesterdayT.htm template.

If you are using MX, the today and yesterday page in the MX_Administrative_Interface shows similar information by using the local application programming interface.

For web tags that refer to a particular time of day, there is a corresponding web tag that can give the time of day. Please note none of the time web tags can be modified by output parameters to give a date, but they can be changed from the default time format that is 'h:mm'.

Web tag_name	Function	Time
Legacy and MX
Temperature & Humidity
<#tempYH>	Yesterday's highest temperature	<#TtempYH>
<#tempYL>	Yesterday's lowest temperature	<#TtempYL>
<#avgtempY>	Yesterday's average temperature	n/a
<#temprangeY>	The temperature range (max - min) yesterday	n/a
<#apptempYH>	Yesterday's high apparent temperature	<#TapptempYH>
<#apptempYL>	Yesterday's low apparent temperature	<#TapptempYL>
MX only
<#Ychillhours>	The Cumulative Chill Hours as recorded at rollover (the end of meteorological yesterday) (Available from release 3.12.0 onwards)	n/a
<#chillhoursYest>	The incremental Chill Hours change yesterday (Available from release 3.12.0 onwards) (compare with <#chillhoursToday> described in #Today.ini table)	n/a
<#feelslikeYH>	Available from version 3.6.10 Yesterday's high feels like temperature	<#TfeelslikeYH>
<#feelslikeYL>	Available from version 3.6.10 Yesterday's low feels like temperature	<#TfeelslikeYL>
<#humidexYH	Available from version 3.7.0 Yesterday's high Canadian Humidity Index	<#ThumidexYH>
Legacy and MX
<#heatindexYH>	Yesterday's high heat index	<#TheatindexYH>
<#wchillYL>	Yesterday's greatest wind chill (i.e. lowest temperature)	<#TwchillYL>
<#dewpointYL>	Yesterday's lowest dew point	<#TdewpointYL>
<#dewpointYH>	Yesterday's highest dew point	<#TdewpointYH>
<#humYH>	High humidity yesterday	<#ThumYH>
<#humYL>	Low humidity yesterday	<#ThumYL>
Rainfall
<#rfallY>	The total rainfall for yesterday according to the connected weather station	n/a
<#RG11RainYest>	The total rainfall for yesterday according to an RG-11 rain sensor configured in "Tipping Bucket" mode	n/a
<#rrateYM>	Yesterday's maximum rain rate	<#TrrateYM>
<#hourlyrainYH>	Yesterday's highest hourly rain	<#ThourlyrainYH>
Pressure
<#pressYH>	Yesterday's highest pressure reading	<#TpressYH>
<#pressYL>	Yesterday's lowest pressure reading	<#TpressYL>
Wind
<#windYM>	Yesterday's maximum (average) wind speed	<#TwindYM>
<#wgustYM>	Yesterday's maximum wind gust	<#TwgustYM>
<#bearingYM>	The wind bearing at the time of yesterday's high gust	<#TwgustYM>
<#Ybeaufort>	Yesterday's highest wind speed, expressed in the Beaufort scale	<#TwindYM>
<#Ybeaufortnumber>	Yesterday's high wind speed on the Beaufort scale, without a leading "F", e.g. "6"	<#TwindYM>
<#Ybeaudesc>	Beaufort 'description' for yesterday's high wind speed	n/a
<#domwindbearingY>	Yesterday's dominant wind direction in degrees	n/a
<#domwinddirY>	Yesterday's dominant wind direction as compass point	n/a
<#windrunY>	The total wind run for yesterday	n/a
MX only
<#windAvgY>	(Available from release 3.12.0 onwards) The wind run yesterday divided by 24 hours to express it as an average wind speed	n/a
Legacy and MX
Miscellaneous
<#heatdegdaysY>	Yesterday's heating degree days	n/a
<#cooldegdaysY>	Yesterday's cooling degree days	n/a
<#YSunshineHours>	Yesterday's hours of sunshine so far. Added in Cumulus 2, then to 1.9.1 build 957, also in MX. From version 3.7.0 takes a parameter "dp=n" so the number of decimal places required can be specified	n/a
<#solarYH>	Yesterday's high solar radiation value (Solar sensor needed)	<#TsolarYH>
<#UVYH>	Yesterday's high UV Index (UV sensor needed)	<#TUVYH>

Yearly

This table shows most of the web tags used on the "thisyearT.htm" web template.

The web tags in the date column output dates in the format "dd MMMM" (for once this is same for Cumulus 1 and Cumulus MX). Should you require a different output format, this can be changed using the format parameters described above. For web tags that represent daily values, there are (obviously) no corresponding time web tags, but for high and low spot values the default 'h:mm' format of the time output can be changed using output parameters. Do make sure that you get the web tag names right and the output form at parameters right.

As another example of inconsistency in how web tags added in different versions are coded, there are two web tags (highest minimum/lowest maximum temperatures) where a standard web tag is not provided by Cumulus (1 or MX) for the associated time-stamp. Consequently, for these 2 (and their corresponding tags in the this month group), there are mandatory output parameters required as shown in the table. Obviously Cumulus 1 lets you use "NN", "nn", "MM", or "mm" for the minutes, but minutes can only be represented in one way in Cumulus MX.

Remember that the Year-to-date runs from roll-over time on 1 January for all web tags listed here.

The list below does NOT include any web tags that represent seasonal derivatives, i.e. where you define the month from which they start counting. (Cumulative seasonal Chill Hours <#chillhours> and Total seasonal rainfall <#ryear> can both be found in Current Conditions). Note, that does not imply both are included in indexT.htm.

Web tag_name	Function	Time	Date
Temperature & Humidity
<#YearTempH>	This year's highest temperature	<#YearTempHT>	<#YearTempHD>
<#YearTempL>	This year's lowest temperature	<#YearTempLT>	<#YearTempLD>
<#YearHighDailyTempRange>	This year's highest Daily Temp Range	n/a	<#YearHighDailyTempRangeD>
<#YearLowDailyTempRange>	This year's lowest Daily Temp Range	n/a	<#YearLowDailyTempRangeD>
<#YearHeatIndexH>	This year's highest USA heat index	<#YearHeatIndexHT>	<#YearHeatIndexHD>
<#YearWChillL>	This year's greatest wind chill (i.e. lowest temperature)	<#YearWChillLT>	<#YearWChillLD>
<#YearAppTempH>	This year's highest apparent temperature	<#YearAppTempHT>	<#YearAppTempHD>
<#YearAppTempL>	This year's lowest apparent temperature	<#YearAppTempLT>	<#YearAppTempLD>
<#YearFeelsLikeH>	This year's highest feels like temperature (available from 3.6.0) (NOT AVAILABLE IN CUMULUS 1)	<#YearFeelsLikeHT>	<#YearFeelsLikeHD>
<#YearFeelsLikeL>	This year's lowest feels like temperature (available from 3.6.0) (NOT AVAILABLE IN CUMULUS 1)	<#YearFeelsLikeLT>	<#YearFeelsLikeLD>
<#YearHumidexH>	(Available from version 3.7.0) (NOT AVAILABLE IN CUMULUS 1) This year's highest Canadian Humidity Index	<#YearHumidexHT>	<#YearHumidexHD>
<#YearDewPointH>	This year's highest dew point	<#YearDewPointHT>	<#YearDewPointHD>
<#YearDewPointL>	This year's lowest dew point	<#YearDewPointLT>	<#YearDewPointLD>
<#YearMinTempH>	This year's highest daily minimum temperature	Flavour specific mandatory output parameters: <#YearMinTempHD format=HH:nn> for Cumulus 1, <#YearMinTempHD format=HH:mm> for Cumulus MX	<#YearMinTempHD>
<#YearMaxTempL>	This year's lowest daily maximum temperature	Flavour specific mandatory output parameters: <#YearMaxTempHD format=HH:nn> for Cumulus 1, <#YearMaxTempHD format=HH:mm> for Cumulus MX	<#YearMaxTempLD>
<#YearHumH>	This year's high humidity	<#YearHumHT>	<#YearHumHD>
<#YearHumL>	This year's low humidity	<#YearHumLT>	<#YearHumLD>
Pressure
<#YearPressH>	This year's high pressure	<#YearPressHT>	<#YearPressHD>
<#YearPressL>	This year's low pressure	<#YearPressLT>	<#YearPressLD>
Wind
<#YearGustH>	This year's high wind gust	<#YearGustHT>	<#YearGustHD>
<#YearWindH>	This year's high wind speed	<#YearWindHT>	<#YearWindHD>
<#YearWindRunH>	This year's highest Daily Wind Run	n/a	<#YearWindRunHD>
Rainfall
<#YearRainRateH>	This year's highest rainfall rate	<#YearRainRateHT>	<#YearRainRateHD>
<#YearHourlyRainH>	This year's highest hourly rain	<#YearHourlyRainHT>	<#YearHourlyRainHD>
<#YearDailyRainH>	This year's high daily rain	n/a	<#YearDailyRainHD>
<#YearMonthlyRainH>	This year's high monthly rain	n/a	<#YearMonthlyRainHD>
<#YearLongestDryPeriod>	Longest period without rain ending this year (days)	n/a	<#YearLongestDryPeriodD>
<#YearLongestWetPeriod>	Longest period of rain every day ending this year (days)	n/a	<#YearLongestWetPeriodD>
Solar (Available from release 3.12.0 onwards)
<#SunshineHoursYear>	the total sunshine hours in year-to-date, or with input modification parameters using either y or r for a past year	n/a	n/a

All Time

This table lists the web tags that appear in the recordsT.htm example template that is included in each release since version 1.5.1 10th January 2006. Additional tags correctly populated from 3.6.10 (build 3086) or 3.7.0 (build 3089) are marked with a "MX" icon as they are not available in Cumulus 1. Please note the 3.6.10 release was available from 24 June 2020, if the date shown for those MX only tags is before when you installed that (or a later release), the output may show incorrect values.

The output from the web tags shown in the date/time column have the default format that is seen on "records.htm" in the standard web pages:

• The default format for an extreme month is to show the month name in full i.e. format 'MMMM' followed by the year in full.
• For an extreme day it shows the day of the month and the month name in full i.e. format "dd MMMM" (same for Cumulus 1 and Cumulus MX), prefixed with the word 'on' again ending with the year.
• For the highest/lowest within a day in the year it shows both time and date adding the word "at" before the time, and the word 'on' before the date (i.e. on the standard web page the time comes first, not as seen in admin interface).

You can change the default output on either the standard web template, or in your own file, by using the formats features described above, but this can involve complicated use of single and double quotes and there are differences between Cumulus 1 and Cumulus MX. Please see examples section above for advice.

Note that unlike the this month and this year web tags, the time and the date are both included in the default format of the standard time-stamp web tags for the 'highest minimum' and 'lowest maximum' temperatures, yet another inconsistency!

Web tag_name	Function	Date/Time
Temperature & Humidity
<#tempH>	All time high temperature	<#TtempH>
<#tempL>	All time low temperature	<#TtempL>
<#mintempH>	All time high minimum temperature	<#TmintempH>
<#maxtempL>	All time low maximum temperature	<#TmaxtempL>
<#LowDailyTempRange>	All time low daily temperature range	<#TLowDailyTempRange>
<#HighDailyTempRange>	All time high daily temperature range	<#THighDailyTempRange>
<#apptempH>	All time high apparent temperature	<#TapptempH>
<#apptempL>	All time low apparent temperature	<#TapptempL>
<#feelslikeH>	All time high feels like temperature (available from 3.6.0)	<#TfeelslikeH>
<#feelslikeL>	All time low feels like temperature (available from 3.6.0)	<#TfeelslikeL>
<#humidexH>	All time high Canadian Humidity Index (available from 3.7.0)	<#ThumidexH>
<#heatindexH>	All time high USA heat index	<#TheatindexH>
<#dewpointH>	All time high dew point	<#TdewpointH>
<#dewpointL>	All time low dew point	<#TdewpointL>
<#humH>	All time high humidity	<#ThumH>
<#humL>	All time low humidity	<#ThumL>
<#wchillH>	All time greatest wind chill (i.e. lowest temperature, but highest wind speed)	<#TwchillH>
Rainfall
<#rrateM>	All time high rain rate	<#TrrateM>
<#rfallH>	All time high daily rain	<#TrfallH>
<#rfallhH>	All time high hourly rain	<#TrfallhH>
<#rfallmH>	All time high monthly rain	<#TrfallmH>
<#LongestDryPeriod>	All time longest dry period (days)	<#TLongestDryPeriod>
<#LongestWetPeriod>	All time longest wet period (days)	<#TLongestWetPeriod>
Pressure
<#pressH>	All time high pressure	<#TpressH>
<#pressL>	All time low pressure	<#TpressL>
Wind
<#gustM>	All time high wind gust	<#TgustM>
<#wspeedH>	All time high average wind speed	<#TwspeedH>
<#windrunH>	All time high daily wind run	<#TwindrunH>

Monthly

This table shows the web tags used on the thismonthT.htm web template.

Because the rainfall this month does not appear on thismonthT.htm web page, it is shown in indexT.htm table earlier in this article which is for the web page where it does appear.

The web tags in the date column output dates in the format "dd MMMM" (for once this is same for Cumulus 1 and Cumulus MX). Should you require a different output format, this can be changed using the format parameters described above. For web tags that represent daily values, there are (obviously) no corresponding time web tags, but for high and low spot values the default 'h:mm' format of the time output can be changed using output parameters. Do make sure that you get the web tag names right and the output form at parameters right.

As another example of inconsistency in how web tags added in different versions are coded, there are two web tags (highest minimum/lowest maximum temperatures) where a standard web tag is not provided by Cumulus (1 or MX) for the associated time-stamp. Consequently, for these 2 (and their corresponding tags in the this year group), there are mandatory output parameters required as shown in the table. Obviously Cumulus 1 lets you use "NN", "nn", "MM", or "mm" for the minutes, but minutes can only be represented in one way in Cumulus MX.

Web tag_name	Function	Time	Date
Temperature & Humidity
<#MonthTempH>	This months high temperature	<#MonthTempHT>	<#MonthTempHD>
<#MonthTempL>	This months low temperature	<#MonthTempLT>	<#MonthTempLD>
<#MonthMinTempH>	This months highest daily minimum temperature	<#MonthMinTempHD format=hh:nn> or <#MonthMinTempHD format=HH:mm> for Cumulus 1, <#MonthMinTempHD format=HH:mm> for Cumulus MX	<#MonthMinTempHD>
<#MonthMaxTempL>	This months lowest daily maximum temperature	<#MonthMaxTempLD format=HH:mm> or <#MonthMaxTempLD format=hh:nn> for Cumulus 1, <#MonthMaxTempLD format=HH:mm> for Cumulus MX	<#MonthMaxTempLD>
<#MonthHighDailyTempRange>	High Daily Temp Range	n/a	<#MonthHighDailyTempRangeD>
<#MonthLowDailyTempRange>	Low Daily Temp Range	n/a	<#MonthLowDailyTempRangeD>
<#MonthHeatIndexH>	This months high USA heat index	<#MonthHeatIndexHT>	<#MonthHeatIndexHD>
<#MonthWChillL>	This months greatest wind chill (i.e. lowest temperature)	<#MonthWChillLT>	<#MonthWChillLD>
<#MonthAppTempH>	This month's high apparent temperature	<#MonthAppTempHT>	<#MonthAppTempHD>
<#MonthAppTempL>	This month's low apparent temperature	<#MonthAppTempLT>	<#MonthAppTempLD>
<#MonthFeelsLikeH>	This month's highest feels like temperature (available from 3.6.0) (NOT AVAILABLE IN CUMULUS 1)	<#MonthFeelsLikeHT>	<#MonthFeelsLikeHD>
<#MonthFeelsLikeL>	This months lowest feels like temperature (available from 3.6.0) (NOT AVAILABLE IN CUMULUS 1)	<#MonthFeelsLikeLT>	<#MonthFeelsLikeLD>
<#MonthHumidexH>	(Available from version 3.7.0) (NOT AVAILABLE IN CUMULUS 1) This month's highest Canadian Humidity Index	<#MonthHumidexHT>	<#MonthHumidexHD>
<#MonthDewPointH>	This month's high dew point	<#MonthDewPointHT>	<#MonthDewPointHD>
<#MonthDewPointL>	This month's low dew point	<#MonthDewPointLT>	<#MonthDewPointLD>
<#MonthHumH>	This month's highest humidity	<#MonthHumHT>	<#MonthHumHD>
<#MonthHumL>	This month's lowest humidity	<#MonthHumLT>	<#MonthHumLD>
Pressure
<#MonthPressH>	This month's highest pressure	<#MonthPressHT>	<#MonthPressHD>
<#MonthPressL>	This month's lowest pressure	<#MonthPressLT>	<#MonthPressLD>
Wind
<#MonthGustH>	This month's highest wind gust	<#MonthGustHT>	<#MonthGustHD>
<#MonthWindH>	This month's highest wind speed	<#MonthWindHT>	<#MonthWindHD>
<#MonthWindRunH>	This month's high Daily Wind Run	n/a	<#MonthWindRunHD>
Rainfall
<#MonthRainRateH>	This month's highest rainfall rate	<#MonthRainRateHT>	<#MonthRainRateHD>
<#MonthHourlyRainH>	This month's highest hourly rain	<#MonthHourlyRainHT>	<#MonthHourlyRainHD>
<#MonthDailyRainH>	This month's wettest day (greatest daily rain)	n/a	<#MonthDailyRainHD>
<#MonthLongestDryPeriod>	Longest dry period ending this month (days)	n/a	<#MonthLongestDryPeriodD>
<#MonthLongestWetPeriod>	Longest period of rain every day, ending this month (days)	n/a	<#MonthLongestWetPeriodD>
Solar (Available from release 3.12.0 onwards)
<#SunshineHoursMonth>	the total sunshine hours in month-to-date, or with input modification parameters using either y and m or r for a past month	n/a	n/a

Monthly All Time Records

This table includes web tags that show the values in Monthlyalltime.ini log file, which was introduced in version 1.9.3 (build 1033, 10 Apr 2012).

These are a set of tags for monthly all-time highs and lows, in other words the highest and lowest values for a particular month of the year.

1. The tag names listed here require a input modification parameter.
2. The tag names here can optionally take any output modification parameters.
3. To supply both optional input modification, and optional output modification parameters, separate them with spaces, e.g. <#ByMonthTempHT mon=7 format=hh:nn>. In that example, the time (not date) of highest ever temperature in July is returned after processing by Cumulus.

At release 3.6.10 (build 3086), and at release 3.7.0 (build 3089); additional tag names were introduced:

• They are marked with a "MX" icon as they are not available in legacy Cumulus 1.
• If you have any "feels like temperatures" that appear with a date/time parameter with a date before 24 June 2020, or before you installed the 3.6.10 release (or a later release), then the value web tag may show incorrect values.

Web tag_name	Function	Date/Time
Temperature & Humidity
<#ByMonthTempH>	High Temperature	<#ByMonthTempHT>
<#ByMonthTempL>	Low Temperature	<#ByMonthTempLT>
<#ByMonthHeatIndexH>	High Heat Index	<#ByMonthHeatIndexHT>
<#ByMonthWChillL>	Greatest wind chill (i.e. lowest temperature and highest wind speed)	<#ByMonthWChillLT>
<#ByMonthAppTempH>	High Apparent Temperature	<#ByMonthAppTempHT>
<#ByMonthAppTempL>	Low Apparent Temperature	<#ByMonthAppTempLT>
<#ByMonthFeelsLikeH>	High Feels Like Temperature (available from 3.6.10)	<#ByMonthFeelsLikeHT>
<#ByMonthFeelsLikeL>	Low Feels Like Temperature (available from 3.6.10)	<#ByMonthFeelsLikeLT>
<#ByMonthHumidexH>	High Canadian Humidity Index (Humidex) - available from version 3.7.0	<#ByMonthHumidexHT>
<#ByMonthHumidexL>	Low Canadian Humidity Index (Humidex) - available from version 3.7.0	<#ByMonthHumidexLT>
<#ByMonthDewPointH>	High Dew Point	<#ByMonthDewPointHT>
<#ByMonthDewPointL>	Low Dew Point	<#ByMonthDewPointLT>
<#ByMonthMinTempH>	Highest Daily Minimum Temperature	<#ByMonthMinTempHT>
<#ByMonthMaxTempL>	Lowest Daily Maximum Temperature	<#ByMonthMaxTempLT>
<#ByMonthHighDailyTempRange>	High Daily Temp Range	<#ByMonthHighDailyTempRangeT>
<#ByMonthLowDailyTempRange>	Low Daily Temp Range	<#ByMonthLowDailyTempRangeT>
<#ByMonthHumH>	High Humidity	<#ByMonthHumHT>
<#ByMonthHumL>	Low Humidity	<#ByMonthHumLT>
Pressure
<#ByMonthPressH>	High Pressure	<#ByMonthPressHT>
<#ByMonthPressL>	Low Pressure	<#ByMonthPressLT>
Wind
<#ByMonthGustH>	High Wind Gust	<#ByMonthGustHT>
<#ByMonthWindH>	High Wind Speed	<#ByMonthWindHT>
<#ByMonthWindRunH>	High Daily Wind Run	<#ByMonthWindRunHT>
Rainfall
<#ByMonthRainRateH>	High Rain Rate	<#ByMonthRainRateHT>
<#ByMonthMonthlyRainH>	High Monthly Rainfall	<#ByMonthMonthlyRainHT>
<#ByMonthHourlyRainH>	High Hourly Rain	<#ByMonthHourlyRainHT>
<#ByMonthDailyRainH>	High Daily Rain	<#ByMonthDailyRainHT>
<#ByMonthLongestDryPeriod>	Longest Dry Period	<#ByMonthLongestDryPeriodT>
<#ByMonthLongestWetPeriod>	Longest Wet Period	<#ByMonthLongestWetPeriodT>

Day/Night/Sun/Moon

In Cumulus 1 most of these are only calculated at UTC zero hours, but are updated each hour to refer to current time-zone.

MX is more complicated, but most of these are calculated hourly.

Web tag_name	Function
<#sunrise>	Last sunrise time at the station - This sunrise time is calculated by a third party library each midnight UTC (in legacy cumulus), and each hour Cumulus converts it to local time to ensure shown correctly before and after any clock change.
<#sunset>	Next sunset time at the station - The sunset/sunrise times are calculated each midnight UTC (in legacy cumulus), and each hour Cumulus converts them to local time to ensure it shows them correctly before and after any clock change.
<#daylength>	Length of day in hours and minutes (sunrise to sunset) - The third party library that Cumulus uses each midnight UTC (in legacy cumulus), may take last sunrise from previous day and next sunset from next day, so the calculation may be off by a minute or so compared to true figure for current day.
<#IsSunUp>	A flag to indicate if the Sun is above the horizon or not, based on the sunrise and sunset times. Possible values are 0 or 1, where 1 is when the Sun is above the horizon for the station location.
<#dawn>	Start of last Civil Twilight at the station as at last midnight UTC
<#dusk>	End of next Civil Twilight at the station as at last midnight UTC
<#daylightlength>	Approximate length of daylight in hours and minutes (dawn to dusk) - if your timezone is UTC or a few hours off that, the dusk may well be that just passed, and the dawn that to come as at the zero hours UTC when Cumulus 1 does this calculation
<#isdaylight>	A flag to indicate if the location for the station is in civil daylight or not, based on the dawn and dusk times. Possible values are 0 or 1, where 1 notes that it is currently within the hours of daylight.
<#tomorrowdaylength>	A string giving an approximate predicted difference between the length of daylight (dawn to dusk) yesterday and length of daylight tomorrow. This web tag is unreliable, basically because of the note for <#daylightlength>, and its use was not recommended. Its use is therefore not supported by Steve Loft (i.e. you use it at your own risk) in the legacy Cumulus.
<#moonphase>	Current phase of the moon in words, eg "New Moon" etc. The names used can be altered in strings.ini.
<#MoonAge>	Current approximate age of the Moon in days (0-29.53) MX b3047 adds the 'dp' and 'rc' parameters Supports an optional 'dp' parameter, if supplied the result is returned to the specified number of decimal places. E.g <#MoonAge> gives "11" <#MoonAge dp=3> gives "11.234" There is some PHP script code below this table showing how this can be converted to days, hours, minutes, seconds* If the "dp" parameter is supplied, then supplying "rc=y" in addition will cause any decimal comma to be converted to a decimal point.
<#moonrise>	Current moonrise time at the station (if moon rises on current calendar day)
<#moonset>	Current moonset time at the station (if moon sets on current calendar day)
<#MoonPercent>	Current percentage of moon visible (negative value indicates 'waning') MX b3047 adds the 'dp' and 'rc' parameters as <#MoonAge> above
<#MoonPercentAbs>	Current percentage of moon visible (always positive) MX b3047 adds the 'dp' and 'rc' parameters as <#MoonAge> above
<#SunshineHours>	see #Today.ini Miscellaneous
<#SunshineHoursY>	see #Yesterday Miscellaneous
<#CurrentSolarMax>	Current theoretical maximum solar radiation
<#IsSunny>	Returns 1 if the sun is shining, otherwise 0 (Solar sensor needed)

* Footnote: PHP code extract:
	$MoonAgeDays 		= <#MoonAge dp=0> +0;
	$moonDecimalPart 		= <#MoonAge dp=4> - $MoonAgeDays;
	$MoonAgeHours 		= round($moonDecimalPart * 24, 0);
	$MoonAgeMinutes  		= round(($moonDecimalPart * 24 * 60) - ($MoonAgeHours * 60), 0);
	$MoonAgeSeconds		= round(($moonDecimalPart * 24 * 60 * 60) - ($MoonAgeHours * 60 * 60) - ($MoonAgeMinutes * 60), 3);
	$MoonAge       	=    $MoonAgeDays . ' days, ' .   $MoonAgeHours . ' hours, '
				. $MoonAgeMinutes . ' minutes, ' . $MoonAgeSeconds . ' seconds';
	// Change the English words 'days, ', ' hours, ', and 'minutes' to the equivalents in your language

Alarms

There are a set of tags available in Cumulus 1 for various alarm states. In Cumulus 1, the main page will change the colour of the relevant element when an alarm condition is entered or left. You can add sounds, and enable disable each alarm parameter on the Main Cumulus screen, Edit menu.

Alarms are also available in later MX versions. In MX, the alarm conditions are shown on the bottom of the Dashboard page of the user interface. You can add sounds, and enable/disable each alarm parameter on the Alarms screen within Settings menu.

For both flavours, there are web tags for each alarm condition, they give a value of '1' if the alarm condition is enabled and is still currently met; otherwise '0'.

Web tag_name	Function
<#LowTempAlarm>	Low temperature alarm
<#HighTempAlarm>	High temperature alarm
<#TempChangeUpAlarm>	Temperature increase alarm
<#TempChangeDownAlarm>	Temperature decrease alarm
<#LowPressAlarm>	Low pressure alarm
<#HighPressAlarm>	High pressure alarm
<#PressChangeUpAlarm>	Pressure increase alarm
<#PressChangeDownAlarm>	Pressure decrease alarm
<#HighRainTodayAlarm>	High rain today alarm
<#HighRainRateAlarm>	High rainfall rate alarm
<#HighWindGustAlarm>	High wind gust alarm
<#HighWindSpeedAlarm>	High wind speed alarm
<#DataStopped>	1 if the station has apparently stopped sending data to Cumulus, otherwise 0
<#DataSpikeAlarm>	Available from version 3.7.0 Alarm raised if a data spike is detected, or a data limit exceeded
<#HttpUploadAlarm>	Available from version 3.11.2 Alarm raised if a HTTP upload alarm has been triggered
<#MySqlUploadAlarm>	Available from version 3.11.2 Alarm raised if a MySQL upload alarm has been triggered
<#UpgradeAlarm>	Alarm raised if MX upgrade (a newer release) is available

Extreme Records

There are a set of tags for the Cumulus record states. They give a value of '1' if the record has been exceeded; otherwise '0'. For daily records (e.g. temperature range), the record cannot be set until the end of the day when rollover starts. The tag is cleared in Cumulus 1 once the record has been viewed (via main screen or web tag).

Differences depending on Cumulus versions

Cumulus 1.9.x supports all the web tags listed in table below, with the exception of those relating to "humidex" and "feels like".

For Cumulus 1 the tags are cleared in one of two ways:

1. Generation of a web page where the web tag is set, clears the record for that web tag.
2. Viewing of an extreme screen tab clears all records listed on that tab.

For versions up to 3.5.0 Cumulus MX works in a different way both in terms of how tags are set (see various topics in support forum) and how they are cleared (essentially the end of rollover clears records, so daily records are only shown for the few microseconds while rollover is being processed). From version 3.7.0, Cumulus MX offers all the web tags listed in table below, at earlier versions it offers a subset of those listed.

For MX these web tags will be set from the time of the record until a timeout value is met (by default each record remains set for 24 hours).

You can change the default MX timeout:

• Add a RecordSetTimeoutHrs=NN entry to [Station] section in Cumulus.ini
• NN can be set to any reasonable integer representing hours (for the default set the number NN to '24').

Table of web tags available for extreme records

Web tag_name	Function
<#recordsbegandate>	The date that Cumulus began tracking all time records (does not prevent earlier record dates being set manually)
<#newrecord>	Indicates when any tracked extreme is changed. In Cumulus MX: 1 from when new record is set until either all records have cleared or until next rollover is completed, or (in recent releases) until the number of hours for clearing extreme record notifications has passed 0 otherwise In Cumulus 1.x.x: 1 if 'new record' light is flashing, 0 if not
<#TempRecordSet>	1 if any temperature-based extreme has been updated, 0 if not
<#HighTempRecordSet>	1 if the all-time highest temperature extreme has been updated, 0 if not
<#LowTempRecordSet>	1 if the all-time lowest temperature extreme has been updated, 0 if not
<#HighTempRangeRecordSet>	1 if the all-time high daily temperature range extreme has been updated, 0 if not
<#LowTempRangeRecordSet>	1 if the all-time low daily temperature range extreme has been updated, 0 if not
<#HighAppTempRecordSet>	1 if the all-time high apparent temperature extreme has been updated, 0 if not
<#LowAppTempRecordSet>	1 if the all-time low apparent temperature extreme has been updated, 0 if not
<#HighHeatIndexRecordSet>	1 if the all-time high USA heat index extreme has been updated, 0 if not
<#HighHumidexRecordSet>	1 if the all-time high Canadian Humidity index extreme has been updated, 0 if not (from version 3.7.0)
<#LowWindChillRecordSet>	1 if the all-time greatest wind chill extreme has been updated, 0 if not
<#HighFeelsLikeRecordSet>	1 if the all-time high feels like temperature extreme has been updated, 0 if not (from version 3.6.0)
<#LowFeelsLikeRecordSet>	1 if the all-time low feels like temperature extreme has been updated, 0 if not (from version 3.6.0)
<#HighDewPointRecordSet>	1 if the all-time high dew point extreme has been updated, 0 if not
<#LowDewPointRecordSet>	1 if the all-time low dew point extreme has been updated, 0 if not
<#HighMinTempRecordSet>	1 if the all-time high minimum temperature extreme has been updated, 0 if not
<#LowMaxTempRecordSet>	1 if the all-time low maximum temperature extreme has been updated, 0 if not
<#HighWindGustRecordSet>	1 if the all-time high wind gust extreme has been updated, 0 if not
<#HighWindSpeedRecordSet>	1 if the all-time high wind speed extreme has been updated, 0 if not
<#RainRecordSet>	1 if any rainfall based extreme has been updated, 0 if not
<#HighRainRateRecordSet>	1 if the all-time high rain rate extreme has been updated, 0 if not
<#HighHourlyRainRecordSet>	1 if the all-time high hourly rain extreme has been updated, 0 if not
<#HighDailyRainRecordSet>	1 if the all-time high daily rain extreme has been updated, 0 if not
<#HighMonthlyRainRecordSet>	1 if the all-time high monthly rain extreme has been updated, 0 if not
<#LongestDryPeriodRecordSet>	1 if the all-time longest dry period extreme has been updated, 0 if not
<#LongestWetPeriodRecordSet>	1 if the all-time longest wet period extreme has been updated, 0 if not
<#HumidityRecordSet>	1 if either the highest or lowest humidity extreme has been updated, 0 if not
<#HighHumidityRecordSet>	1 if the all-time high humidity light extreme has been updated, 0 if not
<#LowHumidityRecordSet>	1 if the all-time low humidity extreme has been updated, 0 if not
<#PressureRecordSet>	1 if either the highest or lowest pressure extreme has been updated, 0 if not
<#HighPressureRecordSet>	1 if the all-time high pressure extreme has been updated, 0 if not
<#LowPressureRecordSet>	1 if the all-time low pressure extreme has been updated, 0 if not
<#WindRecordSet>	1 if any wind speed based extreme has been updated, 0 if not
<#HighWindrunRecordSet>	1 if the all-time high wind run extreme has been updated, 0 if not

Special tags

Davis

Please be aware that the tags available are not the same in all versions. At present this table has not yet been updated for latest MX version.

All (see note for THSWindex) of the following web tags for the Davis PWS are available from Cumulus 1.9.2. Most of the following web tags are available in Cumulus MX 3.0.0 beta from build 3019, Storm tags from 3021.

Both flavours update the values of the reception tags every 15 minutes. In Cumulus 1 this applies from 1.9.3, in 1.9.2 they were read, and updated, every minute, in earlier versions not available.

Web tag_name	Applicability	Function
<#DavisTotalPacketsReceived>	1.9.2 onwards and MX	Total number of data packets received. This stat is not supplied by the Davis WLL station.
<#DavisTotalPacketsMissed>	1.9.2 onwards and MX	Number of missed data packets. From version 3.6.0 build 3076, optionally add "tx=n" parameter, where n=1-8 and equals the desired transmitter id. The default is n=0 and will return the VP2 stats.
<#DavisMaxInARow>	1.9.2 onwards and MX	Longest streak of consecutive packets received. From version 3.6.0 build 3076, optionally add "tx=n" parameter, where n=1-8 and equals the desired transmitter id. The default is n=0 and will return the VP2 stats.
<#DavisNumCRCerrors>	1.9.2 onwards and MX	Number of packets received with CRC errors. From version 3.6.0 build 3076, optionally add "tx=n" parameter, where n=1-8 and equals the desired transmitter id. The default is n=0 and will return the VP2 stats.
<#DavisNumberOfResynchs>	1.9.2 onwards and MX	Number of times the console resynchronised with the transmitter. From version 3.6.0 build 3076, optionally add "tx=n" parameter, where n=1-8 and equals the desired transmitter id. The default is n=0 and will return the VP2 stats
<#DavisFirmwareVersion>	1.9.2 onwards and MX	The console/WLL firmware version
<#THWindex>	1.9.x	A derived temperature using Temperature/Humidity/Wind values read from Davis DLL in Cumulus 1.9.x. The THW Index uses humidity and temperature (like Heat Index), but includes the cooling effects of wind (like wind chill). Available from 1.9.2 Build 1009 (Aug 2011).
<#THSWindex>	(1.9.x and) MX	A heat stress indicator using Temperature/Humidity/Solar/Wind values. The THSW Index uses humidity and temperature (like the Heat Index), but also includes the heating effects of sunshine, and the cooling effects of wind. Therefore requires Davis station with solar sensor. Approx calculation: Decrease heat index by 1 unit for each 1 mph increase in wind speed, and for each, either 3 Langley increase in solar radiation, or 10% increase in cloud cover. IMPORTANT NOTES: Although this tag is available in Cumulus 1.9.x, there is an issue somewhere in the Davis code that prevents Cumulus 1 obtaining the value (so tag always displays zero). Search the forum for several discussions about "THSW". Cumulus MX reads "LOOP2" packets, and the correct value for this tag can be read there and displayed on 'Now' template.
<#battery>	1.x.x and MX	The console battery condition in volts. eg "4.82v"
<#txbattery> <#txbattery channel=1>	1.8.9 onwards and MX	The transmitter battery condition, by default it returns the status of all transmitters. (This was displayed from version 1.9.4 to 1.8.9 on the main screen). Cumulus 1.9.3 onwards Only: The optional 'channel' parameter returns the status for a particular transmitter, up to channel=8. The channel result is just the string "ok" or "LOW" for a low battery
<#StormRain>	1.x.x and MX	The console 'storm rain' current amount (build 1090 onwards for Cumulus 1; 3021 onwards for MX)
<#StormRainStart>	1.x.x and MX	The console reported date of the start of the 'storm', you can use date output format modifiers (Note that the console does not report start time, so the web tag cannot report time. It appears a minimum of 2 tips within 3 hours will trigger a storm start, so using <#LastRainTip> in a MX script might help)

Davis WLL

New from version 3.6.0. Not available for earlier MX, not available for Cumulus 1.

Web tag_name	Function
<#DavisReceptionPercent tx=1>	WLL transmitter reception percentage (replace 1 by any other transmitter number up to 8)
<#DavisTxRssi tx=0>	WLL RSSI of the WiFi connection
<#DavisTxRssi tx=1>	WLL RSSI of Transmitter #1 (replace 1 by any other transmitter number up to 8)

Fine Offset

The following tags are specific to the Fine Offset series of PWS

Web tag_name	Function
<#Light>	Current Lux value "Fine Offset only"
<#SensorContactLost>	1 if the station has lost contact with its remote sensors "Fine Offset only" 0 if contact has been established