DevelopmentFHEMWEB - Versionsgeschichte

Trelle: /* Links */

2017-12-22T06:42:01Z

Links

← Nächstältere Version		Version vom 22. Dezember 2017, 08:42 Uhr
Zeile 70:		Zeile 70:

	== Links ==		== Links ==
	* [DevelopmentFHEMWEB-API\|DevelopmentFHEMWEB-API(german)]		* [[DevelopmentFHEMWEB-API\|DevelopmentFHEMWEB-API(german)]]

	[[Kategorie:Development]]		[[Kategorie:Development]]

Trelle am 22. Dezember 2017 um 06:40 Uhr

2017-12-22T06:40:39Z

← Nächstältere Version		Version vom 22. Dezember 2017, 08:40 Uhr
Zeile 68:		Zeile 68:

	For more details refer to {{Link2Forum\|Topic=12460\|LinkText=original thread in fhem-forum}}.		For more details refer to {{Link2Forum\|Topic=12460\|LinkText=original thread in fhem-forum}}.

			== Links ==
			* [DevelopmentFHEMWEB-API\|DevelopmentFHEMWEB-API(german)]

	[[Kategorie:Development]]		[[Kategorie:Development]]

Justme: /* webCmdFn */

2016-12-30T12:47:07Z

webCmdFn

← Nächstältere Version		Version vom 30. Dezember 2016, 14:47 Uhr
Zeile 60:		Zeile 60:

	=== webCmdFn ===		=== webCmdFn ===
			NOTE: webCmdFn is deprecated. the new javascript widgets should be used.

	Provides the possibility to display own data instead of the command-list of a device.		Provides the possibility to display own data instead of the command-list of a device.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:

Ph1959de: Von html- auf wiki-Formatierung geändert, Forenlink korrigiert, weitere kleinere Änderungen

2015-02-16T12:54:19Z

Von html- auf wiki-Formatierung geändert, Forenlink korrigiert, weitere kleinere Änderungen

← Nächstältere Version		Version vom 16. Februar 2015, 14:54 Uhr
Zeile 1:		Zeile 1:
	This page describes the FHEMWEB module from a developer's perspective.		This page describes the [[FHEMWEB]] module from a developer's perspective.
	= Global Variables =		== Global Variables ==

	The following global variables are used throughout FHEMWEB, and should be used if you are extending it:		The following global variables are used throughout FHEMWEB, and should be used if you are extending it:
			;$FW_ME
			:When using FHEMWEB, you have to specify a base path in all requests; this value is stored in the variable $FW_ME and defaults to /fhem. The user may change it by setting the webname attribute.

	~~<dl><dt>~~$~~FW_ME<dd> When using~~ FHEMWEB~~, you have~~ to ~~specify a base path in all requests, this value is stored in the variable~~ $~~FW_ME and defaults to~~ /~~fhem. The user may change it by setting the webname attribute~~.		;$FW_dir
	~~</dl>~~		:base directory from which FHEMWEB serves files. Defaults to $attr{global}{modpath}/www.

	~~<dl><dt>~~$~~FW_dir<dd>~~ base directory from which FHEMWEB serves ~~files~~. Defaults to $~~attr{global}{modpath}~~/~~www~~.		;$FW_icondir
	~~</dl>~~		:base directory from which FHEMWEB serves icons. Defaults to $FW_dir/images.

	~~<dl><dt>~~$~~FW_icondir<dd>~~ base directory from which FHEMWEB serves ~~icons~~. Defaults to $FW_dir/~~images~~.		;$FW_cssdir
	~~</dl>~~		:base directory from which FHEMWEB serves HTML and SVG style sheets and javascript files. Defaults to $FW_dir/pgm2.

	~~<dl><dt>~~$~~FW_cssdir<dd>~~ base directory ~~from which~~ FHEMWEB ~~serves HTML and SVG style sheets and javascript~~ files. Defaults to $FW_dir/~~pgm2~~.		;$FW_gplotdir
	~~</dl>~~		:base directory where FHEMWEB searches for gplot files. Defaults to $FW_dir/gplot.

	~~<dl><dt>$FW_gplotdir<dd> base directory where FHEMWEB searches for gplot files. Defaults to $FW_dir/gplot.~~		== Special URLs ==
	~~</dl>~~

	= Special URLs =
	You can request any file directly by specifying its exact path starting with $FW_dir, but there are also some special URLs available:		You can request any file directly by specifying its exact path starting with $FW_dir, but there are also some special URLs available:

	== Icons ==		=== Icons ===
	~~[http://hostname:port/~~ http://hostname:port/]<webname>/icons/<device>		<code><nowiki>http://hostname:port/<webname>/icons/<device></nowiki></code>

	This is the standard mechanism to get an icon representing a device.		This is the standard mechanism to get an icon representing a device.

	For finding an icon for a device, the directories are scanned by the iconPath FHEMWEB attribute, default ist stylesheetDir:fhemSVG:openautomation:default. Then the icon is chosen depending on the device name,type and state. The user can specify a devStateIcon to change this behaviour, and the module can also override it by specifying its FW_summaryFn, see below.		For finding an icon for a device, the directories are scanned by the iconPath FHEMWEB attribute, default ist stylesheetDir:fhemSVG:openautomation:default. Then the icon is chosen depending on the device name, type, and state. The user can specify a devStateIcon to change this behaviour, and the module can also override it by specifying its FW_summaryFn (see below for details).

	Due to historic reasons, you can still load any image from the iconPath directly by specifying its name without extension, but this feature may go away in the future.		Due to historic reasons, you can still load any image from the iconPath directly by specifying its name without extension, but this feature may go away in the future.

	== Documentation ==		=== Documentation ===
	[http://hostname:port/ http://hostname:port/]<webname>/docs/file		<code><nowiki>http://hostname:port/ http://hostname:port/<webname>/docs/file</nowiki></code>

	This is the standard mechanism to retrieve documentation, especially commandref.html: ~~[http://hostname~~:~~port/~~ http://hostname:port/]<webname>/docs/commandref.html.		This is the standard mechanism to retrieve documentation, especially commandref.html:
			:<code><nowiki>http://hostname:port/<webname>/docs/commandref.html</nowiki></code>

	== Usage in your own code ==		=== Usage in your own code ===
	If you need an icon to be visualized in a web site, use the function FW_makeImage(<icon>). It returns the img tag for the icon plus a comment where the icon is located. It even ~~return~~ an error message if no icon file exists that fits the requested logical name.		If you need an icon to be visualized in a web site, use the function FW_makeImage(<icon>). It returns the img tag for the icon plus a comment where the icon is located. It even returns an error message if no icon file exists that fits the requested logical name.

	Other useful functions are FW_iconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ ~~http://hostname:port/]~~<webname>/icons/lamp.off.		Other useful functions are FW_iconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. <code><nowiki>http://hostname:port/<webname>/icons/lamp.off</nowiki></code>.

	= Plugins =		== Plugins ==
	FHEMWEB provides some meachnisms to plug-in own functionality. To do so, own routines can be registered in the hashes $data or $hash respectively, see details below.		FHEMWEB provides some meachnisms to plug-in own functionality. To do so, own routines can be registered in the hashes $data or $hash respectively, see details below.
	== FW_detailFn ==
	Provides the possibility to display additional data on the details-screen of a device, will be ~~dosplayed above~~ the "Internals"-section.		=== FW_detailFn ===
			Provides the possibility to display additional data on the details-screen of a device, will be displayed preceding the "Internals"-section.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:
	$hash->{FW_detailFn} = "my_Routine";		:<code>$hash->{FW_detailFn} = "my_Routine";</code>
	my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.		my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
	== FW_summaryFn==
			=== FW_summaryFn===
	Provides the possibility to display own data instead of the state-icon of a device.		Provides the possibility to display own data instead of the state-icon of a device.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:
	$hash->{FW_summaryFn} = "my_Routine";		:<code>$hash->{FW_summaryFn} = "my_Routine";</code>
	my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.		my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
	The return-value of my_routine can ~~bei~~ any of		The return-value of my_routine can be any of
	* html-code, checked by regexp <.*>		* html-code, checked by regexp <.*>
	* empty (""), will display the state as a text link ~~usual~~		* empty (""), will display the state as a plain text link
	* undef, will continue the default search mechanism for a matching icon for STATE		* undef, will continue the default search mechanism for a matching icon for STATE

	== webCmdFn ==		=== webCmdFn ===
	Provides the possibility to display own data instead of the command-list of a device.		Provides the possibility to display own data instead of the command-list of a device.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:
	$data{webCmdFn}{myModule} = "my_Routine";		:<code>$data{webCmdFn}{myModule} = "my_Routine"; </code>
	my_Routine will be called with parameters $FW_wname, $deviceName, $FW_room, $cmd, $values.		my_Routine will be called with parameters $FW_wname, $deviceName, $FW_room, $cmd, $values.

	For more details refer to ~~[http://forum.fhem.de/index.php?t=msg&th~~=12460~~&goto=74762&rid~~=~~86#msg_74762 the~~ original thread in fhem-forum].		For more details refer to {{Link2Forum\|Topic=12460\|LinkText=original thread in fhem-forum}}.

	[[Kategorie:Development]]		[[Kategorie:Development]]

Rudolfkoenig: FW_docdir removed,

2013-07-25T12:33:34Z

FW_docdir removed,

Änderungen zeigen

Justme: /* FW_summaryFn */

2013-07-25T10:47:53Z

FW_summaryFn

← Nächstältere Version		Version vom 25. Juli 2013, 12:47 Uhr
Zeile 133:		Zeile 133:
	The return-value of my_routine can bei any of		The return-value of my_routine can bei any of
	* html-code, checked by regexp <.*>		* html-code, checked by regexp <.*>
	* empty (""), will display the state~~-icon~~ as usual		* empty (""), will display the state as a text link usual
	* undef, will ~~display ???~~		* undef, will continue the default search mechanism for a matching icon for STATE

	== webCmdFn ==		== webCmdFn ==
	Provides the possibility to display own data instead of the command-list of a device.		Provides the possibility to display own data instead of the command-list of a device.

Uli: /* Plugins */

2013-07-25T09:55:20Z

Plugins

← Nächstältere Version		Version vom 25. Juli 2013, 11:55 Uhr
Zeile 124:		Zeile 124:
	Provides the possibility to display additional data on the details-screen of a device, will be dosplayed above the "Internals"-section.		Provides the possibility to display additional data on the details-screen of a device, will be dosplayed above the "Internals"-section.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:
	$hash->{FW_detailFn} = "~~my_routine~~";		$hash->{FW_detailFn} = "my_Routine";
	~~my_routine~~ will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.		my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
	== FW_summaryFn==		== FW_summaryFn==
	Provides the possibility to display own data instead of the state-icon of a device.		Provides the possibility to display own data instead of the state-icon of a device.
	Registration in a modules' initialize-Routine:		Registration in a modules' initialize-Routine:
	$hash->{FW_summaryFn} = "~~my_routine~~";		$hash->{FW_summaryFn} = "my_Routine";
	~~my_routine~~ will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.		my_Routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
	The return-value of my_routine can bei any of		The return-value of my_routine can bei any of
	* html-code, checked by regexp <.*>		* html-code, checked by regexp <.*>
	* empty (""), will display the state-icon as usual		* empty (""), will display the state-icon as usual
	* undef, will display ???		* undef, will display ???
			== webCmdFn ==
			Provides the possibility to display own data instead of the command-list of a device.
			Registration in a modules' initialize-Routine:
			$data{webCmdFn}{myModule} = "my_Routine";
			my_Routine will be called with parameters $FW_wname, $deviceName, $FW_room, $cmd, $values.

			For more details refer to [http://forum.fhem.de/index.php?t=msg&th=12460&goto=74762&rid=86#msg_74762 the original thread in fhem-forum].

	[[Kategorie:Development]]		[[Kategorie:Development]]

Uli: Added "plugins"-section

2013-07-25T09:50:40Z

Added "plugins"-section

← Nächstältere Version		Version vom 25. Juli 2013, 11:50 Uhr
Zeile 118:		Zeile 118:

	Other useful functions are FW_IconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ http://hostname:port/]<webname>/icons/lamp.off.		Other useful functions are FW_IconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ http://hostname:port/]<webname>/icons/lamp.off.

			= Plugins =
			FHEMWEB provides some meachnisms to plug-in own functionality. To do so, own routines can be registered in the hashes $data or $hash respectively, see details below.
			== FW_detailFn ==
			Provides the possibility to display additional data on the details-screen of a device, will be dosplayed above the "Internals"-section.
			Registration in a modules' initialize-Routine:
			$hash->{FW_detailFn} = "my_routine";
			my_routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
			== FW_summaryFn==
			Provides the possibility to display own data instead of the state-icon of a device.
			Registration in a modules' initialize-Routine:
			$hash->{FW_summaryFn} = "my_routine";
			my_routine will be called with the parameters $FW_wname, $deviceName, $FW_room. Have a look at 01_FHEMWEB.pm for examples.
			The return-value of my_routine can bei any of
			* html-code, checked by regexp <.*>
			* empty (""), will display the state-icon as usual
			* undef, will display ???



	[[Kategorie:Development]]		[[Kategorie:Development]]

Markusbloch: /* Usage in your own code */

2013-05-13T19:22:14Z

Usage in your own code

← Nächstältere Version		Version vom 13. Mai 2013, 21:22 Uhr
Zeile 118:		Zeile 118:

	Other useful functions are FW_IconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ http://hostname:port/]<webname>/icons/lamp.off.		Other useful functions are FW_IconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ http://hostname:port/]<webname>/icons/lamp.off.

			[[Kategorie:Development]]

Generix: Die Seite wurde neu angelegt: „This page describes the FHEMWEB module from a developer's perspective. = Global Variables = In the source code [http://hostname:port/ http://hostname:port/]<…“

2013-05-10T20:28:56Z

Die Seite wurde neu angelegt: „This page describes the FHEMWEB module from a developer's perspective. = Global Variables = In the source code [http://hostname:port/ http://hostname:port/]&lt…“

Neue Seite

This page describes the FHEMWEB module from a developer's perspective.
= Global Variables =
In the source code [http://hostname:port/ http://hostname:port/]<webname> is in $FW_ME. The following global variables are used throughout fhem:

<dl><dt>$FW_dir</dt><dd> base directory from which FHEMWEB serves files. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$modpath/www
$modpath/FHEM</nowiki>
<dl><dt>$FW_icondir</dt><dd> base directory from which FHEMWEB serves icons. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$FW_dir/images [which is $modpath/www/images in the new layout]
$FW_dir/pgm2 [which is $modpath/www/pgm2 in the interim layout]
$FW_dir [which is $modpath/FHEM in the old layout]</nowiki>
<dl><dt>FW_docdir</dt><dd> base directory from which FHEMWEB serves documentation. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$FW_dir/docs [usually does not exist]
$modpath/docs [this is where the documentation has ever been residing, no need to copy commandref.html etc. anymore]
$FW_dir [which is $modpath/FHEM in the old layout]</nowiki>
<dl><dt>$FW_cssdir</dt><dd> base directory from which FHEMWEB serves style sheets and svg definitions. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$FW_dir/pgm2 [which is $modpath/www/pgm2 in the new and in the interim layout]
$FW_dir [which is $modpath/FHEM in the old layout]</nowiki>
<dl><dt>$FW_jsdir</dt><dd> base directory from which FHEMWEB serves javascript includes. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$FW_dir/pgm2 [which is $modpath/www/pgm2 in the new and in the interim layout]
$FW_dir [which is $modpath/FHEM in the old layout]</nowiki>
<dl><dt>$FW_gplotdir</dt><dd> base directory from which FHEMWEB serves gplot files. The first existing directory from the following list is taken:
</dd></dl>
<nowiki>$FW_dir/gplot [which is $modpath/www/gplot in the interim layout]
$FW_dir/pgm2 [which is $modpath/www/pgm2 in the interim layout]
$FW_dir [which is $modpath/FHEM in the old layout]</nowiki>

= Special URLs =
Why do we need special URLs?

One would expect, that the URLs correspond to paths in the local filesystem relative to the document root. This was the case with the directory FHEM being the document root but not with the more tidier interim and new directory structures. Thus, one layer of indirection was required to transparently map the below URLs to the respective directories no matter what the actual directory structure is.

== Icons ==
[http://hostname:port/ http://hostname:port/]<webname>/icons/<icon>

This is the standard mechanism to retrieve image files.

==== Documentation ====
[http://hostname:port/ http://hostname:port/]<webname>/docs/file

This is the standard mechanism to retrieve documentation, especially commandref.html: [http://hostname:port/ http://hostname:port/]<webname>/docs/commandref.html.

html, txt and pdf files are recognized by their extensions. They are served from $FW_docdir (no subdirectories possible at this stage).

==== Style Sheets ====
[http://hostname:port/ http://hostname:port/]<webname>/css/file

This is the standard mechanism to retrieve style sheets, e.g. default.css: [http://hostname:port/ http://hostname:port/]<webname>/css/default.css.

They are served from $FW_cssdir (no subdirectories possible at this stage).

==== Javascript Includes ====
[http://hostname:port/ http://hostname:port/]<webname>/js/file

This is the standard mechanism to retrieve style sheets, e.g. default.css: [http://hostname:port/ http://hostname:port/]<webname>/js/svg.css.

They are served from $FW_jsdir (no subdirectories possible at this stage).

==== GPlot Files ====
[http://hostname:port/ http://hostname:port/]<webname>/gplot/file

This is the standard mechanism to retrieve gplot files, e.g. temp4hum8.gplot: [http://hostname:port/ http://hostname:port/]<webname>/gplot/temp4hum8.gplot.

They are served from $FW_gplotdir (no subdirectories possible at this stage).

= Icon subsystem =
== General ==
fhem adds one layer of indirection to the icons in the $FW_icondir directory structure. The icon is requested under its logical name <icon>, e.g. ''lamp.on''or ''weather/sunny''or ''myicons/klaus''. <icon> can thus be a path.

fhem serves icons from the URL [http://hostname:port/ http://hostname:port/]<webname>/icons/<icon>

If <icon> is requested, a physical file needs to be served. Its filename must be <icon> with a suffix of .ico, .gif, .jpg, or .png. For example, the logical icon ''lamp.on''could be stored in a file named ''lamp.on.ico''and the logical icon ''weather/sunny''could be in a file named ''weather/sunny.png''.

The physical file that is actually served for <icon> is determined as follows: Per default, the icon file is taken from $FW_icondir/default. If the stylesheetPrefix attribute of the underlying FHEMWEB instance is set to <style>, then icon files from $FW_icondir/<style> take precedence over those with same file names in $FW_icondir/default. Highest priority has the path specified in the ''iconpath''attribute of the FHEMWEB instance. ''iconpath''is relative to $FW_icondir. Icons not found in the style-specific subdirectories are taken from the default subdirectory anyway. Only if absolutely no icons can be found in any of these subdirectories, $FW_icondir itself is searched.

Serving icons from a subdirectory is not even tidier but also required to place third party collections together with a copyright notice in the structure as it is the case for Martin Preidel's weather icons.

If more than one physical file exists for <icon> in a subdirectory, the priority is as follows: 1. <icon>.png (highest), 2. <icon>.jpg, 3. <icon>.ico, 4. <icon>.gif (lowest).

Conclusions:

# Put the icons into $FW_icondir/default and its subdirectories. If you need style-specific icons, put them into $FW_icondir/<style> and its subdirectories.
# The actual icons you get from <nowiki>[http://hostname:port/ http://hostname:port/]</nowiki><webname> and b) the stylesheetPrefix attribute of that FHEMWEB instance.
== Source code for server mechanism ==
For some reason FHEMWEB uses global variables to certain extent (this is no problem since fhem is not multi-threaded). FW_SetDirs() is the essential function to set $FW_icondir (and other directories) relative to the document root $FW_dir of the FHEMWEB server. It must be called before any action involving icons to assure $FW_icondir is correctly set for the FHEMWEB instance that serves the requested icon.

The mapping between the physical icon files in the $FW_icondir directory structure and the logical icon structure is done in FW_ReadIcons($). FW_ReadIcons() is called once upon definition of the FHEMWEB device or explicitely with ''set myFHEMWEB rereadicons''.

The mapping table is stored in $hash->{fhem}{icons} as semicolon-separated list of ''<icon>;<filename>''pairs with <filename> relative to $FW_icondir.

The strategy for collection the icons is as follows (see FW_ReadIcons):

1. First collect all icons in the directory $FW_icondir/default.
2. If the stylesheetPrefix attribute is set, then collect all icons in the directory $FW_icondir/<stylesheetPrefix>.
3. If the iconpath attribute ist set, then collect all icons in the directory $FW_icondir/<iconpath>.
4. If no icons have been found so far, then collect all icons in the directory $FW_icondir.

Step #4 is required to find icons in the FHEM subdirectory $modpath/FHEM, where the icons used to reside in the old layout.

If a previously icon is found again in a later step, this icon is given preference over the previously found icon. For example, if <stylesheetPrefix> is "dark" and we have fhemicon both in $FW_icondir/default and in $FW_icondir/dark, the fhemicon from $FW_icondir/dark is taken.

The icon files can be in gif, ico, jpg or png format. If two or three icon files for the same logical icon name are available in the same directory, e.g. fhemicon.png and fhemicon.gif, png is preferred over jpg and jpg is preferred over ico and ico is preferred over gif.

== Usage in your own code ==
If you need an icon to be visualized in a web site, use the function FW_makeImage(<icon>). It returns the img tag for the icon plus a comment where the icon is located. It even return an error message if no icon file exists that fits the requested logical name.

If a connection to the webserver is made, the underlying FHEMWEB instance needs to be determined that serves the request. After this has been done the global variables still need to be set. Thus make sure to call FW_SetDirs() at the appropriate place.

Other useful functions are FW_IconPath(<icon>) to determine the full(!) path to the icon, e.g. $FW_icondir/dark/lamp.off.png. and FW_IconURL(<icon>) to determine the URL of the icon, e.g. [http://hostname:port/ http://hostname:port/]<webname>/icons/lamp.off.