Download data from URI using Curl at the specified interval. The interval may be a floating point value greater than 0, otherwise defaults to 15 minutes. Most useful when used in conjunction with Lua and the Lua API. This object is threaded, and once a thread
is created it can't be explicitly destroyed. One thread will run for each URI specified. You can use any protocol that Curl supports.

• double - Argument consists of only digits and a single dot.
• long - Argument consists of only digits.
• string - Argument is enclosed in quotation marks (")

Valid operands are: '>', '<', '>=', '<=', '==', '!='.

Loads the configfile at path, places the configsettings behind the configsettings in the orginal config and places the vars where the includevar stood.

• threshold - The thresholdtemperature at which the gpu slows down
• temp - Gives the gpu current temperature
• ambient - Gives current air temperature near GPU case
• gpufreq - Gives the current gpu frequency
• memfreq - Gives the current mem frequency
• imagequality - Which imagequality should be chosen by OpenGL applications

• status - Display if battery is fully charged, charging, discharging or absent (running on AC)
• percent - Display charge of battery in percent, if charging or discharging. Nothing will be displayed, if battery is fully charged or absent.
• time - Display the time remaining until the battery will be fully charged or discharged at current rate. Nothing is displayed, if battery is absent or if it's present but fully charged and not discharging.

Download and parse RSS feeds. The interval may be a floating point value greater than 0, otherwise defaults to 15 minutes. Action may be one of the following: feed_title, item_title (with num par), item_desc (with num par) and item_titles (when using this action
and spaces_in_front is given conky places that many spaces in front of each item). This object is threaded, and once a thread is created it can't be explicitly destroyed. One thread will run for each URI specified. You can use any protocol that Curl supports.

TCP port (both IPv6 and IPv4) monitor for specified local ports. Port numbers must be in the range 1 to 65535. Valid items are:

• count - Total number of connections in the range
• rip - Remote ip address
• rhost - Remote host name
• rport - Remote port number
• rservice - Remote service name from /etc/services
• lip - Local ip address
• lhost - Local host name
• lport - Local port number
• lservice - Local service name from /etc/services

The connection index provides you with access to each connection in the port monitor. The monitor will return information for index values from 0 to n-1 connections. Values higher than n-1 are simply ignored. For the "count" item, the connection index must
be omitted. It is required for all other items.

Examples:

• ${tcp_portmon 6881 6999 count} - Displays the number of connections in the bittorrent port range
• ${tcp_portmon 22 22 rip 0} - Displays the remote host ip of the first sshd connection
• ${tcp_portmon 22 22 rip 9} - Displays the remote host ip of the tenth sshd connection
• ${tcp_portmon 1 1024 rhost 0} - Displays the remote host name of the first connection on a privileged port
• ${tcp_portmon 1 1024 rport 4} - Displays the remote host port of the fifth connection on a privileged port
• ${tcp_portmon 1 65535 lservice 14} - Displays the local service name of the fifteenth connection in the range of all ports

Note that port monitor variables which share the same port range actually refer to the same monitor, so many references to a single port range for different items and different indexes all use the same monitor internally. In other words, the program avoids
creating redundant monitors.

Evaluate the content of the templateN configuration variable (where N is a value between 0 and 9, inclusively), applying substitutions as described in the documentation of the corresponding configuration variable. The number of arguments is optional, but must
match the highest referred index in the template. You can use the same special sequences in each argument as the ones valid for a template definition, e.g. to allow an argument to contain a whitespace. Also simple nesting of templates is possible this way.

Here are some examples of template definitions:

• template0 $\1\2
• template1 \1: ${fs_used \2} / ${fs_size \2}
• template2 \1 \2

The following list shows sample usage of the templates defined above, with the equivalent syntax when not using any template at all:

using template same without template ${template0 node name} $nodename ${template1 root /} root: ${fs_free /} / ${fs_size /} ${template1 ${template2\ disk\ root} /} disk root: ${fs_free /} / ${fs_size /}

Download, parse and display METAR data.

For the 'URI', there are two possibilities:

• http://weather.noaa.gov/pub/data/observations/metar/stations/
• http://xoap.weather.com/weather/local/

The first one is free to use but the second requires you to register and obtain your partner ID and license key. These two must be written, separated by a space, into a file called .xoaprc which needs to be placed into your home directory.

'locID' must be a valid location identifier for the required uri. For the NOAA site this must be a valid ICAO (see for instance https://pilotweb.nas.faa.gov/qryhtml/icao/). For the weather.com site this must be a valid location ID (see for instance http://aspnetresources.com/tools/locid.aspx).

'data_type' must be one of the following:

• last_update -

  The date and time stamp of the data. The result depends on the URI used. For the NOAA site it is date (yyyy/mm/dd) and UTC time. For the weather.com one it is date ([m]m/[d]d/yy) and Local Time of the station.

• temperature -

  Air temperature (you can use the 'temperature_unit' config setting to change units)

• cloud_cover -

  The highest cloud cover status

• pressure -

  Air pressure in millibar

• wind_speed -

  Wind speed in km/h

• wind_dir -

  Wind direction

• wind_dir_DEG -

  Compass wind direction

• humidity -

  Relative humidity in %

• weather -

  Any relevant weather event (rain, snow, etc.). This is not used if you are querying the weather.com site since this data is aggregated into the cloud_cover one

• icon -

  Weather icon (only for www.weather.com). Can be used together with the icon kit provided upon registering to their service.

'delay_in_minutes' (optional, default 30) cannot be less than 30 minutes.

This object is threaded, and once a thread is created it can't be explicitly destroyed. One thread will run for each URI specified.

Note that these variables are still EXPERIMENTAL and can be subject to many future changes.

Download, parse and display weather forecast data for a given day (daytime only).

For the 'URI', for the time being only http://xoap.weather.com/weather/local/ is supported. See 'weather' above for details of usage

'locID', see 'weather' above.

'day' is a number from 0 (today) to 4 (3 days after tomorrow).

'data_type' must be one of the following:

• day - Day of the week
• date - Date, in the form MMM DD (ie. Jul 14)
• low - Minimun temperature (you can use the 'temperature_unit' config setting to change units)
• hi - Maximum temperature (you can use the 'temperature_unit' config setting to change units)
• icon - Weather icon. Can be used together with the icon kit provided upon registering to the weather.com service
• forecast - Weather forecast (sunny, rainy, etc.)
• wind_speed - Wind speed in km/h
• wind_dir - Wind direction
• wind_dir_DEG - Compass wind direction
• humidity - Relative humidity in %
• precipitation - Probability of having a precipitation (in %)

'delay_in_minutes' (optional, default 210) cannot be lower than 210 min.

This object is threaded, and once a thread is created it can't be explicitly destroyed. One thread will run for each URI specified. You can use any protocol that Curl supports.

Note that these variables are still EXPERIMENTAL and can be subject to many future changes.