|
|
|
|
@@ -56,7 +56,6 @@
|
|
|
|
|
<a href="#sleep">sleep</a>
|
|
|
|
|
<a href="#trigger">trigger</a>
|
|
|
|
|
<a href="#update">update</a>
|
|
|
|
|
<a href="#updatefhem">updatefhem</a>
|
|
|
|
|
<a href="#usb">usb</a>
|
|
|
|
|
<a href="#xmllist">xmllist</a>
|
|
|
|
|
|
|
|
|
|
@@ -813,10 +812,6 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
version after the update has finished.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
Notice: The former used command "updatefhem" will be replaced by the new
|
|
|
|
|
command "update" in the 5.3 distribution.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
The new update function will process more advanced distribution information
|
|
|
|
|
as well as control commands for updating, removing or renaming existing files.
|
|
|
|
|
New file structures can also be set up by the new control command files.
|
|
|
|
|
@@ -844,77 +839,6 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="updatefhem"></a>
|
|
|
|
|
<h3>updatefhem</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>updatefhem [<changed>|<filename>|<housekeeping> [<clean>] [<yes>]|<preserve> [<filename>]]</code> <br>
|
|
|
|
|
<br>
|
|
|
|
|
<b>This command is deprecated as of Fhem 5.3</b>
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
Update the fhem modules and documentation from a nightly SVN checkout. For
|
|
|
|
|
this purpose Fhem contacts http://fhem.de/fhemupdate, compares the stored
|
|
|
|
|
timestamps of the local files with the filelist on the server, and
|
|
|
|
|
downloads the files changed on the server. For all downloaded modules a
|
|
|
|
|
reload will be scheduled if the corresponding module is loaded.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
Note: Since Version 5.3 a new directory structure is used by Fhem. The
|
|
|
|
|
WebInterface pgm2 is separated from <a href="#modpath">modpath</a>/FHEM
|
|
|
|
|
directory. The directory modpath/www/pgm2 is the new home of pgm2 and
|
|
|
|
|
of its files. It is recommended to update to the new structure via the
|
|
|
|
|
<housekeeping> arguments.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
The complete installation of Fhem will be saved via the <a href="#backup">backup</a>
|
|
|
|
|
command on every update. You can skip this backups by setting
|
|
|
|
|
the global attribute <a href="#backup_before_update">backup_before_update</a> to 0.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
Have you change or replace original files of the Fhem Distribution,
|
|
|
|
|
these files will normally be overwritten during an update. To protect
|
|
|
|
|
your locally modified or replaced files during an update, you can exclude
|
|
|
|
|
these files with the global attribute <a href="#exclude_from_update">exclude_from_update</a>.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
If <changed> is specified, updatefhem returns a list of new or
|
|
|
|
|
modified files since the last update. Furthermore it returns the last
|
|
|
|
|
changes from the CHANGED file (if the file exists on the update server).
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
If an explicit <filename> is given, then only this file will be
|
|
|
|
|
downloaded.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
If <housekeeping> is specified, then updatefhem switch your Fhem
|
|
|
|
|
installation to the new directory structure for the pgm2 WebInterface.
|
|
|
|
|
The old files are archived like the <backup> argument and the new
|
|
|
|
|
files are stored to modpath/www/pgm2. None of the existing files of pgm2
|
|
|
|
|
in modpath/FHEM will be deleted, but are no longer in use.<br>
|
|
|
|
|
If you like to delete the no more needed files for pgm2 in modpath/FHEM,
|
|
|
|
|
you should call <housekeeping> with the argument <clean> <yes>.
|
|
|
|
|
All files of pgm2 are removed from modpath/FHEM and files like
|
|
|
|
|
.*example.*, .gplot, .html .css, .js, and .(gif|jpg|png|svg) are moved
|
|
|
|
|
to modpath/www/pgm2.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
If <preserve> is specified, you could preserve the old directory
|
|
|
|
|
structure. All files of pgm2 are updated and stored in modpath/FHEM like
|
|
|
|
|
the former (before Fhem 5.3) updatefhem funktion. To update an explicit
|
|
|
|
|
file to the old structure append the file as <filename>.<br>
|
|
|
|
|
Note: After running the housekeeping process, the argument <preserve>
|
|
|
|
|
is no longer necessary and no more supported.
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
Notes:
|
|
|
|
|
<ul>
|
|
|
|
|
<li>If the main program (fhem.pl) is changed, a manual restart of fhem
|
|
|
|
|
will be necessary to apply the changes.</li>
|
|
|
|
|
<li>After running <housekeeping> it is recommended to restart Fhem.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="CULflash"></a>
|
|
|
|
|
<h3>CULflash</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
@@ -1230,8 +1154,6 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<h2>Devices</h2>
|
|
|
|
|
|
|
|
|
|
<a name="global"></a>
|
|
|
|
|
<h3>global</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
@@ -2517,7 +2439,7 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<a name="FHT8Vdefine"></a>
|
|
|
|
|
<a name="PIDdefine"></a>
|
|
|
|
|
<b>Define</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>define <name> PID sensor[:reading:regexp] actor[:cmd:min:max] [p i d]</code>
|
|
|
|
|
@@ -2566,14 +2488,14 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<a name="FHT8Vget"></a>
|
|
|
|
|
<a name="PIDget"></a>
|
|
|
|
|
<b>Get </b>
|
|
|
|
|
<ul>
|
|
|
|
|
N/A
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<a name="FHT8Vattr"></a>
|
|
|
|
|
<a name="PIDattr"></a>
|
|
|
|
|
<b>Attributes</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<li><a href="#disable">disable</a></li>
|
|
|
|
|
@@ -5118,7 +5040,6 @@ A line ending with \ will be concatenated with the next one, so long lines
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
<a name="KS300define"></a>
|
|
|
|
|
<a name="KS300"></a>
|
|
|
|
|
<b>Define</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>define <name> KS300 <housecode> [ml/raincounter [wind-factor]]</code>
|
|
|
|
|
@@ -5223,6 +5144,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<br><br>
|
|
|
|
|
|
|
|
|
|
<a name="MSGFile"></a>
|
|
|
|
|
<h3>MSGFile</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
@@ -5233,7 +5155,8 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
A MSGFile device needs the operating systems rights to write to the filesystem.
|
|
|
|
|
To set the rights for a directory, please use OS related commands.
|
|
|
|
|
<br><br>
|
|
|
|
|
<a name="#MSGFileDefine"></a>
|
|
|
|
|
|
|
|
|
|
<a name="MSGFileDefine"></a>
|
|
|
|
|
<b>Define</b>
|
|
|
|
|
<ul><br>
|
|
|
|
|
<code>define <name> MSGFile <filename></code><br><br>
|
|
|
|
|
@@ -5245,7 +5168,8 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>define myFile MSGFile</code>
|
|
|
|
|
</ul><br>
|
|
|
|
|
<a name="#MSGFileSet"></a>
|
|
|
|
|
<a name="MSGFileSet"></a>
|
|
|
|
|
|
|
|
|
|
<b>Set</b><br>
|
|
|
|
|
<ul><code>set <name> add|clear|list [text]</code><br>
|
|
|
|
|
Set is used to manipulate the message buffer of the device. The message
|
|
|
|
|
@@ -5274,6 +5198,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
<code>set myMsg write myFile</code><br>
|
|
|
|
|
<code>set myFile clear</code><br>
|
|
|
|
|
</ul><br>
|
|
|
|
|
|
|
|
|
|
<a name="MSGFileVattr"></a>
|
|
|
|
|
<b>Attributes</b>
|
|
|
|
|
<ul>
|
|
|
|
|
@@ -5304,7 +5229,8 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
To send an email, a MSG device is necessary.<br>
|
|
|
|
|
<b>MAIL::Lite</b> and <b>Net::SMTP::SSL</b> from CPAN is needed to use MSGMail!!
|
|
|
|
|
<br><br>
|
|
|
|
|
<a name="#MSGMailDefine"></a>
|
|
|
|
|
|
|
|
|
|
<a name="MSGMailDefine"></a>
|
|
|
|
|
<b>Define</b>
|
|
|
|
|
<ul><br>
|
|
|
|
|
<code>define <name> MSGMail <from> <to> <smtphost> <authfile></code><br><br>
|
|
|
|
|
@@ -5317,7 +5243,8 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>define myMail MSGMail from@address.com to@address.com smtp.provider.host /etc/msgauthfile</code>
|
|
|
|
|
</ul><br>
|
|
|
|
|
<a name="#MSGMailSet"></a>
|
|
|
|
|
|
|
|
|
|
<a name="MSGMailSet"></a>
|
|
|
|
|
<b>Set</b><br>
|
|
|
|
|
<ul><code>set <name> add|clear|list [text]</code><br>
|
|
|
|
|
Set is used to manipulate the message buffer of the device. The message
|
|
|
|
|
@@ -6167,7 +6094,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
|
|
|
|
|
<br>
|
|
|
|
|
<br>
|
|
|
|
|
<a name="POKEYS_define"></a>
|
|
|
|
|
<a name="POKEYSdefine"></a>
|
|
|
|
|
<b>Define</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>define <name> POKEYS <ip-address> <pin> <io-state> [<time in ms>]</code> <br>
|
|
|
|
|
@@ -6189,7 +6116,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul> <br>
|
|
|
|
|
|
|
|
|
|
<a name="POKEYS_set"></a>
|
|
|
|
|
<a name="POKEYSset"></a>
|
|
|
|
|
<b>Set</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>set <name> <state> [<time in ms>]</code> <br>
|
|
|
|
|
@@ -6204,7 +6131,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul><br>
|
|
|
|
|
|
|
|
|
|
<a name="POKEYS_get"></a>
|
|
|
|
|
<a name="POKEYSget"></a>
|
|
|
|
|
<b>Get</b>
|
|
|
|
|
<ul>
|
|
|
|
|
<code>get <name> <type> </code> <br>
|
|
|
|
|
@@ -6219,7 +6146,7 @@ To send the data, both send or write could be used.<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul><br>
|
|
|
|
|
|
|
|
|
|
<a name="POKEYS_attr"></a>
|
|
|
|
|
<a name="POKEYSattr"></a>
|
|
|
|
|
<b>Attributes</b>
|
|
|
|
|
<ul>
|
|
|
|
|
todo <br>
|
|
|
|
|
@@ -7918,7 +7845,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWAD"></a>
|
|
|
|
|
<h3>OWAD</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with 1-Wire A/D converters<br /><br /> Note:<br /> This
|
|
|
|
|
@@ -8055,7 +7982,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWCOUNT"></a>
|
|
|
|
|
<h3>OWCOUNT</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with 1-Wire Counter/RAM DS2423 #<br /><br /> Note:<br />
|
|
|
|
|
@@ -8165,7 +8092,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWID"></a>
|
|
|
|
|
<h3>OWID</h3>
|
|
|
|
|
<ul>FHEM module for 1-Wire devices that know only their unique ROM ID<br />
|
|
|
|
|
@@ -8200,7 +8127,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
</ul>
|
|
|
|
|
<br />
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWLCD"></a>
|
|
|
|
|
<h3>OWLCD</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with the <a
|
|
|
|
|
@@ -8288,7 +8215,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWMULTI"></a>
|
|
|
|
|
<h3>OWMULTI</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with 1-Wire multi-sensors, currently the DS2438 smart battery monitor<br /><br /> Note:<br /> This
|
|
|
|
|
@@ -8392,9 +8319,9 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
</ul>
|
|
|
|
|
</li>
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="OWSWITCH"></a>
|
|
|
|
|
<h3>OWSWITCH</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with 1-Wire Programmable Switches <br /><br /> Note:<br />
|
|
|
|
|
@@ -8493,7 +8420,7 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
|
|
|
|
|
<li>Standard attributes alias, comment, <a href="#eventMap">eventMap</a>, <a href="#loglevel">loglevel</a>, <a href="#webCmd">webCmd</a></li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
<!--+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-->
|
|
|
|
|
|
|
|
|
|
<a name="OWTHERM"></a>
|
|
|
|
|
<h3>OWTHERM</h3>
|
|
|
|
|
<ul>FHEM module to commmunicate with 1-Wire bus digital thermometer devices<br /><br />
|
|
|
|
|
@@ -9807,7 +9734,6 @@ href="http://www.elv.de/output/controller.aspx?cid=74&detail=10&detail2=29870">U
|
|
|
|
|
<br>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="TCM120"></a>
|
|
|
|
|
<a name="TCM"></a>
|
|
|
|
|
<h3>TCM</h3>
|
|
|
|
|
<ul>
|
|
|
|
|
@@ -10388,6 +10314,7 @@ volume</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="ZWDongle"></a>
|
|
|
|
|
<h3>ZWDongle</h3>
|
|
|
|
|
@@ -11504,13 +11431,13 @@ volume</pre>
|
|
|
|
|
"Put" the newly created device in this room. The name can contain the
|
|
|
|
|
wildcards %TYPE and %NAME, see the example above.</li><br>
|
|
|
|
|
|
|
|
|
|
<a name="filelog"></a>
|
|
|
|
|
<a name="filelogattr"></a>
|
|
|
|
|
<li>filelog<br>
|
|
|
|
|
Create a filelog associated with the device. The filename can contain
|
|
|
|
|
the wildcards %TYPE and %NAME, see the example above. The filelog will
|
|
|
|
|
be "put" in the same room as the device.</li><br>
|
|
|
|
|
|
|
|
|
|
<a name="weblink"></a>
|
|
|
|
|
<a name="weblinkattr"></a>
|
|
|
|
|
<li>weblink<br>
|
|
|
|
|
Create a weblink associated with the device/filelog.</li><br>
|
|
|
|
|
|
|
|
|
|
@@ -12126,6 +12053,7 @@ volume</pre>
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="watchdog"></a>
|
|
|
|
|
<h3>watchdog</h3>
|
|
|
|
|
@@ -12183,7 +12111,6 @@ volume</pre>
|
|
|
|
|
<li>a generic watchdog (one watchdog responsible for more devices) is
|
|
|
|
|
currently not possible.</li>
|
|
|
|
|
</ul>
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<br>
|
|
|
|
|
</ul>
|
|
|
|
|
@@ -12204,7 +12131,6 @@ volume</pre>
|
|
|
|
|
</li>
|
|
|
|
|
</ul>
|
|
|
|
|
<br>
|
|
|
|
|
|
|
|
|
|
</ul>
|
|
|
|
|
|
|
|
|
|
<a name="telnet"></a>
|
|
|
|
|
|