Public/fhem-mirror
1
0
Fork 0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-05-01 20:20:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Adding missing </li> in the documentation

Browse Source 
git-svn-id: https://svn.fhem.de/fhem/trunk/fhem@2411 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
rudolfkoenig 2013-01-03 13:05:04 +00:00
parent f9bcb48068
commit 8226fb364f
13 changed files with 132 additions and 126 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
FHEM/00_CUL.pm
View File

@ -1122,8 +1122,8 @@ CUL_Attr(@)
Issue a CUL firmware command. See the <a
href="http://culfw.de/commandref.html">this</a> document
for details on CUL commands.
</li><br>
<li>freq / bWidth / rAmpl / sens<br>
<a href="#rfmode">SlowRF</a> mode only.<br>
Set the CUL frequency / bandwidth / receiver-amplitude / sensitivity<br>
@ -1135,16 +1135,17 @@ CUL_Attr(@)
<li>freq sets both the reception and transmission frequency. Note:
although the CC1101 can be set to frequencies between 315 and 915
MHz, the antenna interface and the antenna of the CUL is tuned for
exactly one frequency. Default is 868.3MHz (or 433MHz)
exactly one frequency. Default is 868.3MHz (or 433MHz)</li>
<li>bWidth can be set to values between 58kHz and 812kHz. Large values
are susceptible to interference, but make possible to receive
inaccurate or multiple transmitters. It affects tranmission too.
Default is 325kHz.
Default is 325kHz.</li>
<li>rAmpl is receiver amplification, with values between 24 and 42 dB.
Bigger values allow reception of weak signals. Default is 42.
</li>
<li>sens is the decision boundery between the on and off values, and it
is 4, 8, 12 or 16 dB. Smaller values allow reception of less clear
signals. Default is 4dB.
signals. Default is 4dB.</li>
</ul>
</li><br>
<a name="hmPairForSec"></a>
@ -1209,11 +1210,11 @@ CUL_Attr(@)
<a name="CULattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
<li><a href="#attrdummy">dummy</a></li><br>
<li><a href="#showtime">showtime</a></li><br>
<li><a href="#loglevel">loglevel</a></li><br>
<li><a href="#model">model</a> (CUL,CUN,CUR)</li><br>
<li><a href="#do_not_notify">do_not_notify</a></li>
<li><a href="#attrdummy">dummy</a></li>
<li><a href="#showtime">showtime</a></li>
<li><a href="#loglevel">loglevel</a></li>
<li><a href="#model">model</a> (CUL,CUN,CUR)</li>
<li><a name="sendpool">sendpool</a><br>
If using more than one CUL/CUN for covering a large area, sending
different events by the different CUL's might disturb each other. This
@ -1235,13 +1236,13 @@ CUL_Attr(@)
<ul>
<li>SlowRF<br>
To communicate with FS20/FHT/HMS/EM1010/S300/Hoermann devices @1kHz
datarate. This is the default.
datarate. This is the default.</li>
<li>HomeMatic<br>
To communicate with HomeMatic type of devices @20kHz datarate
To communicate with HomeMatic type of devices @20kHz datarate</li>
<li>MAX<br>
To communicate with MAX! type of devices @20kHz datarate
To communicate with MAX! type of devices @20kHz datarate</li>
</ul>
</li><br>

121
FHEM/00_KM271.pm
View File

@ -869,7 +869,6 @@ KM271_SetReading($$$$$)
<li>nacht: manual by night working mode, no timer program is in effect</li>
<li>tag: manual by day working mode, no timer program is in effect</li>
</ul></li>
</li>
<li>hk2_betriebsart [automatik|nacht|tag]<br>
sets the working mode for heating circuit 2<br>
(see above)</li>
@ -961,66 +960,66 @@ KM271_SetReading($$$$$)
<a name="KM271events"></a>
<b>Generated events:</b>
<ul>
<li>Abgastemperatur
<li>Aussentemperatur
<li>Aussentemperatur_gedaempft
<li>Brenner_Ansteuerung
<li>Brenner_Ausschalttemperatur
<li>Brenner_Einschalttemperatur
<li>Brenner_Laufzeit1_Minuten2
<li>Brenner_Laufzeit1_Minuten1
<li>Brenner_Laufzeit1_Minuten
<li>Brenner_Laufzeit2_Minuten2
<li>Brenner_Laufzeit2_Minuten1
<li>Brenner_Laufzeit2_Minuten
<li>Brenner_Mod_Stellglied
<li>ERR_Fehlerspeicher1
<li>ERR_Fehlerspeicher2
<li>ERR_Fehlerspeicher3
<li>ERR_Fehlerspeicher4
<li>ERR_Letzter_Fehlerstatus
<li>HK1_Ausschaltoptimierung
<li>HK1_Betriebswerte1
<li>HK1_Betriebswerte2
<li>HK1_Einschaltoptimierung
<li>HK1_Heizkennlinie_+10_Grad
<li>HK1_Heizkennlinie_-10_Grad
<li>HK1_Heizkennlinie_0_Grad
<li>HK1_Mischerstellung
<li>HK1_Pumpe
<li>HK1_Raumisttemperatur
<li>HK1_Raumsolltemperatur
<li>HK1_Vorlaufisttemperatur
<li>HK1_Vorlaufsolltemperatur
<li>HK2_Ausschaltoptimierung
<li>HK2_Betriebswerte1
<li>HK2_Betriebswerte2
<li>HK2_Einschaltoptimierung
<li>HK2_Heizkennlinie_+10_Grad
<li>HK2_Heizkennlinie_-10_Grad
<li>HK2_Heizkennlinie_0_Grad
<li>HK2_Mischerstellung
<li>HK2_Pumpe
<li>HK2_Raumisttemperatur
<li>HK2_Raumsolltemperatur
<li>HK2_Vorlaufisttemperatur
<li>HK2_Vorlaufsolltemperatur
<li>Kessel_Betrieb
<li>Kessel_Fehler
<li>Kessel_Integral
<li>Kessel_Integral1
<li>Kessel_Vorlaufisttemperatur
<li>Kessel_Vorlaufsolltemperatur
<li>Modulkennung
<li>NoData
<li>Versionsnummer_NK
<li>Versionsnummer_VK
<li>WW_Betriebswerte1
<li>WW_Betriebswerte2
<li>WW_Einschaltoptimierung
<li>WW_Isttemperatur
<li>WW_Pumpentyp
<li>WW_Solltemperatur
<li>Abgastemperatur</li>
<li>Aussentemperatur</li>
<li>Aussentemperatur_gedaempft</li>
<li>Brenner_Ansteuerung</li>
<li>Brenner_Ausschalttemperatur</li>
<li>Brenner_Einschalttemperatur</li>
<li>Brenner_Laufzeit1_Minuten2</li>
<li>Brenner_Laufzeit1_Minuten1</li>
<li>Brenner_Laufzeit1_Minuten</li>
<li>Brenner_Laufzeit2_Minuten2</li>
<li>Brenner_Laufzeit2_Minuten1</li>
<li>Brenner_Laufzeit2_Minuten</li>
<li>Brenner_Mod_Stellglied</li>
<li>ERR_Fehlerspeicher1</li>
<li>ERR_Fehlerspeicher2</li>
<li>ERR_Fehlerspeicher3</li>
<li>ERR_Fehlerspeicher4</li>
<li>ERR_Letzter_Fehlerstatus</li>
<li>HK1_Ausschaltoptimierung</li>
<li>HK1_Betriebswerte1</li>
<li>HK1_Betriebswerte2</li>
<li>HK1_Einschaltoptimierung</li>
<li>HK1_Heizkennlinie_+10_Grad</li>
<li>HK1_Heizkennlinie_-10_Grad</li>
<li>HK1_Heizkennlinie_0_Grad</li>
<li>HK1_Mischerstellung</li>
<li>HK1_Pumpe</li>
<li>HK1_Raumisttemperatur</li>
<li>HK1_Raumsolltemperatur</li>
<li>HK1_Vorlaufisttemperatur</li>
<li>HK1_Vorlaufsolltemperatur</li>
<li>HK2_Ausschaltoptimierung</li>
<li>HK2_Betriebswerte1</li>
<li>HK2_Betriebswerte2</li>
<li>HK2_Einschaltoptimierung</li>
<li>HK2_Heizkennlinie_+10_Grad</li>
<li>HK2_Heizkennlinie_-10_Grad</li>
<li>HK2_Heizkennlinie_0_Grad</li>
<li>HK2_Mischerstellung</li>
<li>HK2_Pumpe</li>
<li>HK2_Raumisttemperatur</li>
<li>HK2_Raumsolltemperatur</li>
<li>HK2_Vorlaufisttemperatur</li>
<li>HK2_Vorlaufsolltemperatur</li>
<li>Kessel_Betrieb</li>
<li>Kessel_Fehler</li>
<li>Kessel_Integral</li>
<li>Kessel_Integral1</li>
<li>Kessel_Vorlaufisttemperatur</li>
<li>Kessel_Vorlaufsolltemperatur</li>
<li>Modulkennung</li>
<li>NoData</li>
<li>Versionsnummer_NK</li>
<li>Versionsnummer_VK</li>
<li>WW_Betriebswerte1</li>
<li>WW_Betriebswerte2</li>
<li>WW_Einschaltoptimierung</li>
<li>WW_Isttemperatur</li>
<li>WW_Pumpentyp</li>
<li>WW_Solltemperatur</li>
</ul>
<br>
As I cannot explain all the values, I logged data for a period and plotted

23
FHEM/00_TCM.pm
View File

@ -710,17 +710,18 @@ TCM_Undef($$)
<ul>
<li>idbase<br>
Set the ID base. Note: The firmware executes this command only up to
then times to prevent misuse.<br><br>
<li>modem_off<br>
<li>modem_on<br>
<li>reset<br>
<li>sensitivity<br>
<li>sleep<br>
<li>wake<br>
then times to prevent misuse.
</li>
<li>modem_off</li>
<li>modem_on</li>
<li>reset</li>
<li>sensitivity</li>
<li>sleep</li>
<li>wake
For details see the datasheet available from
www.enocean.com. If you do not understand it, than you probably don't
need it :)
</li><br>
</li><br><br>
</ul>
<a name="TCMget"></a>
@ -729,9 +730,9 @@ TCM_Undef($$)
<li>idbase<br>
Get the ID base. You need this command in order to control EnOcean
devices, see the <a href="#EnOceandefine">EnOcean</a>
paragraph.<br><br>
<li>modem_status<br>
<li>sensitivity<br>
paragraph.</li>><br>
<li>modem_status</li><br>
<li>sensitivity</li><br>
<li>sw_ver<br>
for details see the datasheet available from www.enocean.com
</li><br>

27
FHEM/00_ZWDongle.pm
View File

@ -167,7 +167,7 @@ ZWDongle_Define($$)
my @a = split("[ \t][ \t]*", $def);
if(@a != 3) {
my $msg = "wrong syntax: define <name> ZWDongle {none | ".
my $msg = "wrong syntax: define <name> ZWDongle {none[:homeId] | ".
"devicename[\@baudrate] | ".
"devicename\@directio | ".
"hostname:port}";
@ -183,8 +183,9 @@ ZWDongle_Define($$)
my %matchList = ( "1:ZWave" => ".*" );
$hash->{MatchList} = \%matchList;
if($dev eq "none") {
Log 1, "$name device is none, commands will be echoed only";
if($dev =~ m/none:(.*)/) {
$hash->{homeId} = $1;
Log 1, "$name device is none (homeId:$1), commands will be echoed only";
$attr{$name}{dummy} = 1;
return undef;
@ -575,16 +576,16 @@ ZWDongle_Ready($)
mode. After activating inclusion mode usually you have to press a switch
three times within 1.5 seconds on the node to be included into the network
of the controller. If autocreate is active, a fhem device will be created
after inclusion.
after inclusion.</li>
<li>removeNode [on|off]<br>
Activate (or deactivate) exclusion mode. Note: the corresponding fhem
device have to be deleted manually.
device have to be deleted manually.</li>
<li>createNode id<br>
Request the class information for the specified node, and create a fhem
device upon reception of the answer. Used for previously included nodes,
see the nodeList get command below.
see the nodeList get command below.</li>
</ul>
<br>
@ -594,20 +595,21 @@ ZWDongle_Ready($)
<ul>
<li>nodeList<br>
return the list of included nodeIds. Can be used to recreate fhem-nodes
with the createNode command.
with the createNode command.</li>
<li>homeId<br>
return the six hex-digit homeId of the controller.
return the six hex-digit homeId of the controller.</li>
<li>caps, ctrlCaps, version<br>
return different controller specific information. Needed by developers only.
return different controller specific information. Needed by developers
only. </li>
<li>nodeInfo<br>
return node specific information. Needed by developers only.
return node specific information. Needed by developers only.</li>
<li>raw<br>
Send raw data to the controller. Developer only.
Send raw data to the controller. Developer only.</li>
</ul>
<br>
@ -625,8 +627,11 @@ ZWDongle_Ready($)
<b>Generated events:</b>
<ul>
<li>ZW_ADD_NODE_TO_NETWORK [learnReady|nodeFound|controller|done|failed]
</li>
<li>ZW_REMOVE_NODE_TO_NETWORK [learnReady|nodeFound|slave|controller|done|failed]
</li>
<li>UNDEFINED ZWave_${type6}_$id ZWave $homeId $id $classes"
</li>
</ul>
</ul>

8
FHEM/16_CUL_RFR.pm
View File

@ -162,15 +162,15 @@ CUL_RFR_AddPrefix($$)
<li>First give your base CUL (which remains connected to the PC) an RFR ID
by issuing the fhem command "set MyCUL raw ui0100". With this command
the base CUL will get the ID 01, and it will not relay messages to other
CUL's (as the second number is 00).
CUL's (as the second number is 00).</li>
<li>Now replace the base CUL with the RFR CUL, and set its id by issuing
the fhem command "set MyCUL raw ui0201". Now remove this CUL and attach the
original, base CUL again. The RFR CUL got the id 02, and will relay every
message to the base CUL with id 01.
message to the base CUL with id 01.</li>
<li>Take the RFR CUL, and attach it to an USB power supply, as seen on
the image. As the configured base id is not 00, it will activate RF
reception on boot, and will start sending messages to the base CUL.
<li>Now you have to define this RFR cul as a fhem device:
reception on boot, and will start sending messages to the base CUL.</li>
<li>Now you have to define this RFR cul as a fhem device:</li>
</ul>
</td><td>

6
FHEM/61_EMWZ.pm
View File

@ -217,15 +217,15 @@ EMWZ_Define($$)
<li>rperkw<br>
Number of rotations for a KiloWatt of the EM1000WZ device (actually
of the device where the EM1000WZ is attached to). Without setting
this correctly, all other readings will be incorrect.
this correctly, all other readings will be incorrect.</li>
<li>alarm<br>
Alarm in WATT. if you forget to set it, the default value is
rediculously low (random), and if a value above this threshold is
received, the EM1010PC will start beeping once every minute. It can
be very annoying.
be very annoying.</li>
<li>price<br>
The price of one KW in EURO (use e.g. 0.20 for 20 Cents). It is used
only on the EM1010PC display, it is of no interest for FHEM.
only on the EM1010PC display, it is of no interest for FHEM.</li>
</ul>
</ul>
<br>

2
FHEM/63_EMGZ.pm
View File

@ -203,7 +203,7 @@ EMGZ_Define($$)
<ul>
<li>price<br>
The price of one KW in EURO (use e.g. 0.20 for 20 Cents). It is used
only on the EM1010PC display, it is of no interest for FHEM.
only on the EM1010PC display, it is of no interest for FHEM.</li>
</ul>
</ul>
<br>

14
FHEM/91_notify.pm
View File

@ -171,20 +171,20 @@ notify_Attr(@)
<li>Following special events will be generated for the device "global"
<ul>
<li>INITIALIZED after initialization is finished.
<li>DEFINED &lt;devname&gt; after a device is defined.
<li>DELETED &lt;devname&gt; after a device was deleted.
<li>RENAMED &lt;old&gt; &lt;new&gt; after a device was renamed.
<li>INITIALIZED after initialization is finished.</li>
<li>DEFINED &lt;devname&gt; after a device is defined.</li>
<li>DELETED &lt;devname&gt; after a device was deleted.</li>
<li>RENAMED &lt;old&gt; &lt;new&gt; after a device was renamed.</li>
<li>UNDEFINED &lt;defspec&gt; upon reception of a message for an
undefined device.
</ul>
undefined device.</li>
</ul></li>
<li>Notify can be used to store macros for manual execution. Use the <a
href="#trigger">trigger</a> command to execute the macro.
E.g.<br>
<code>fhem> define MyMacro notify MyMacro { Log 1, "Hello"}</code><br>
<code>fhem> trigger MyMacro</code><br>
</li>
</ul>
</ul>

2
FHEM/91_watchdog.pm
View File

@ -195,7 +195,7 @@ watchdog_Undef($$)
definition time. Else it will be activated when the first matching
event is received.</li>
<li>&lt;regexp1&gt; resets the timer of a running watchdog, to avoid it
use the regexp1WontReactivate attribute.
use the regexp1WontReactivate attribute.</li>
<li>if &lt;regexp2&gt; is SAME, then it will be the same as the first
regexp, and it will be reactivated, when it is received.
</li>

12
FHEM/98_average.pm
View File

@ -236,12 +236,12 @@ average_Notify($$)
<a name="averageevents"></a>
<b>Generated events:</b>
<ul>
<li>&lt;eventname&gt;_avg_day: $avg_day
<li>&lt;eventname&gt;_avg_month: $avg_month
<li>&lt;eventname&gt;_min_day: $min_day
<li>&lt;eventname&gt;_min_month: $min_month
<li>&lt;eventname&gt;_max_day: $max_day
<li>&lt;eventname&gt;_max_month: $max_month
<li>&lt;eventname&gt;_avg_day: $avg_day</li>
<li>&lt;eventname&gt;_avg_month: $avg_month</li>
<li>&lt;eventname&gt;_min_day: $min_day</li>
<li>&lt;eventname&gt;_min_month: $min_month</li>
<li>&lt;eventname&gt;_max_day: $max_day</li>
<li>&lt;eventname&gt;_max_month: $max_month</li>
</ul>
</ul>

8
FHEM/98_telnet.pm
View File

@ -265,13 +265,13 @@ telnet_Undef($$)
attr tPort password secret<br>
attr tPort password {use FritzBoxUtils;;FB_checkPw("localhost","$password") }
</code>
<br><br>
</li><br>
<a name="globalpassword"></a>
<li>globalpassword<br>
Just like the attribute password, but a password will only required for
non-local connections.
<br><br>
</li><br>
<a name="SSL"></a>
<li>SSL<br>
@ -283,13 +283,13 @@ telnet_Undef($$)
ncat --ssl fhemhost fhemport<br>
openssl s_client -connect fhemhost:fhemport<br>
</ul>
<br><br>
</li><br>
<a name="allowfrom"></a>
<li>allowfrom<br>
Regexp of allowed ip-addresses or hostnames. If set,
only connections from these addresses are allowed.
<br><br>
</li><br>
</ul>

2
FHEM/98_weblink.pm
View File

@ -125,7 +125,7 @@ weblink_Define($$)
<li>Fhem config:<br>
attr wl_1 label "Max $data{max1}, Current $data{currval1}"</li>
<li>.gplot file entry:<br>
set title &lt;L1&gt;<br>
set title &lt;L1&gt;<br></li>
</ul></li>
</ul>
</li>

4
FHEM/99_SUNRISE_EL.pm
View File

@ -413,8 +413,8 @@ isday</pre>
All functions take up to three arguments:<br>
<ul>
<li>The first specifies an offset (in seconds), which will be added to the
event.
<li>The second and third specify min and max values (format: "HH:MM").
event.</li>
<li>The second and third specify min and max values (format: "HH:MM").</li>
</ul>
<br>
isday() can be used in some notify or at commands to check if the sun is up or