mirror of
https://github.com/fhem/fhem-mirror.git
synced 2025-01-31 06:39:11 +00:00
10_EIB.pm 70_WS3600.pm 98_HourCounter.pm 40_RFXCOM.pm 00_MAXLAN.pm 50_HP1000.pm 70_TellStick.pm: fixing commandref_join warnings (Forum #51779)
git-svn-id: https://svn.fhem.de/fhem/trunk@11307 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
parent
24c5afbc41
commit
98f0e3eed0
@ -866,7 +866,6 @@ MAXLAN_RemoveDevice($$)
|
||||
<a name="MAXLAN"></a>
|
||||
<h3>MAXLAN</h3>
|
||||
<ul>
|
||||
<tr><td>
|
||||
The MAXLAN is the fhem module for the eQ-3 MAX! Cube LAN Gateway.
|
||||
<br><br>
|
||||
The fhem module makes the MAX! "bus" accessible to fhem, automatically detecting paired MAX! devices. It also represents properties of the MAX! Cube. The other devices are handled by the <a href="#MAX">MAX</a> module, which uses this module as its backend.<br>
|
||||
|
@ -1251,7 +1251,7 @@ eib_name2hex($)
|
||||
|
||||
<a name="EIB"></a>
|
||||
<h3>EIB / KNX</h3>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<p>EIB/KNX is a standard for building automation / home automation.
|
||||
It is mainly based on a twisted pair wiring, but also other mediums (ip, wireless) are specified.</p>
|
||||
|
||||
@ -1266,7 +1266,7 @@ eib_name2hex($)
|
||||
show the correct value.</p>
|
||||
|
||||
<p><a name="EIBdefine"></a> <b>Define</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code>define <name> EIB <main group> [<additional group> ..]</code>
|
||||
|
||||
<p>Define an EIB device, connected via a <a href="#TUL">TUL</a>. The
|
||||
@ -1286,7 +1286,7 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBset"></a> <b>Set</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code>set <name> <value> [<time> g<groupnr>]</code>
|
||||
<p>where value one of:</p>
|
||||
<li><b>on</b> switch on device</li>
|
||||
@ -1340,13 +1340,13 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBget"></a> <b>Get</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<p>If you execute get for a EIB/KNX-Element there will be requested a state from the device. The device has to be able to respond to a read - this is not given for all devices.<br>
|
||||
The answer from the bus-device is not shown in the toolbox, but is treated like a regular telegram.</p>
|
||||
</div>
|
||||
|
||||
<p><a name="EIBattr"></a> <b>Attributes</b></p>
|
||||
<div style="margin-left: 2em"><br>
|
||||
<div>
|
||||
<a href="#IODev">IODev</a><br>
|
||||
<a href="#alias">alias</a><br>
|
||||
<a href="#comment">comment</a><br>
|
||||
@ -1375,7 +1375,7 @@ eib_name2hex($)
|
||||
<br>
|
||||
|
||||
<p><a name="EIBreadingX"></a> <b>EIBreadingX</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Enable additional readings for this EIB-device. With this Attribute set, a reading setG<x> will be updated when a set command is issued from FHEM, a reading getG<x> will be updated as soon a Value is received from EIB-Bus (<x> stands for the groupnr. - see define statement). The logic for the state reading remains unchanged. This is especially useful when the define statement contains more than one group parameter.
|
||||
<p>If set to 1, the following additional readings will be available:</p>
|
||||
<pre>
|
||||
@ -1393,7 +1393,7 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBreadingSender"></a> <b>EIBreadingSender</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Enable an additional reading for this EIB-device. With this Attribute set, a reading sender will be updated any time a new telegram arrives.
|
||||
<p>If set to 1, the following additional reading will be available: <pre>sender</pre></p>
|
||||
<pre>
|
||||
@ -1407,7 +1407,7 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBanswerReading"></a> <b>EIBanswerReading</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
If enabled, FHEM answers on read requests. The content of state is send to the bus as answer.
|
||||
<p>If set to 1, read-requests are answered</p>
|
||||
<p>Example:</p>
|
||||
@ -1418,7 +1418,7 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBreadingRegex"></a> <b>EIBreadingRegex</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
You can pass n pairs of regex-pattern and string to replace, seperated by a slash. Internally the "new" state is always in the format getG[n]:[state]. The substitution is done every time, a new object is received. You can use this function for converting, adding units, having more fun with icons, ...
|
||||
This function has only an impact on the content of state - no other functions are disturbed.
|
||||
<p>Example:</p>
|
||||
@ -1430,7 +1430,6 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="EIBwritingRegex"></a> <b>EIBwritingRegex</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
You can pass n pairs of regex-pattern and string to replace, seperated by a slash. Internally the "new" state is always in the format setG1:[state]. The substitution is done every time, after an object is send. You can use this function for converting, adding units, having more fun with icons, ...
|
||||
This function has only an impact on the content of state - no other functions are disturbed.
|
||||
<p>Example:</p>
|
||||
@ -1441,7 +1440,7 @@ eib_name2hex($)
|
||||
</div>
|
||||
|
||||
<p><a name="model"></a> <b>model</b></p>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<p>This attribute is mandatory!</p>
|
||||
Set the model according to the datapoint types defined by the (<a href="http://www.sti.uniurb.it/romanell/110504-Lez10a-KNX-Datapoint%20Types%20v1.5.00%20AS.pdf" target="_blank">EIB / KNX specifications</a>). The device state in FHEM is interpreted and shown according to the specification.<br>
|
||||
<br>
|
||||
|
@ -378,8 +378,6 @@ RFXCOM_Ready($)
|
||||
<a name="RFXCOM"></a>
|
||||
<h3>RFXCOM</h3>
|
||||
<ul>
|
||||
<table>
|
||||
<tr><td>
|
||||
This module is for the old <a href="http://www.rfxcom.com">RFXCOM</a> USB or LAN based 433 Mhz RF receivers and transmitters (order order code 80002 and others). It does not support the new RFXtrx433 transmitter because it uses a different protocol. See <a href="#RFXTRX">RFXTRX</a> for support of the RFXtrx433 transmitter.<br>
|
||||
These receivers supports many protocols like Oregon Scientific weather sensors, RFXMeter devices, X10 security and lighting devices and others. <br>
|
||||
Currently the following parser modules are implemented: <br>
|
||||
@ -430,7 +428,6 @@ These receivers supports many protocols like Oregon Scientific weather sensors,
|
||||
<br>
|
||||
</ul>
|
||||
<br>
|
||||
</table>
|
||||
<ul>
|
||||
<li><a href="#attrdummy">dummy</a></li><br>
|
||||
<li>longids<br>
|
||||
|
@ -269,9 +269,9 @@ sub HP1000_CGI() {
|
||||
<h3>
|
||||
HP1000
|
||||
</h3>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<a name="HP1000define" id="HP10000define"></a> <b>Define</b>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code>define <WeatherStation> HP1000 [<ID> <PASSWORD>]</code><br>
|
||||
<br>
|
||||
Provides webhook receiver for weather station HP1000 and WH2600 of Fine Offset Electronics.<br>
|
||||
@ -281,7 +281,7 @@ sub HP1000_CGI() {
|
||||
As the URI has a fixed coding as well there can only be one single HP1000/WH2600 station per FHEM installation.<br>
|
||||
<br>
|
||||
Example:<br>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code># unprotected instance where ID and PASSWORD will be ignored<br>
|
||||
define WeatherStation HP1000<br>
|
||||
<br>
|
||||
@ -303,9 +303,9 @@ sub HP1000_CGI() {
|
||||
<h3>
|
||||
HP1000
|
||||
</h3>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<a name="HP1000define" id="HP10000define"></a> <b>Define</b>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code>define <WeatherStation> HP1000 [<ID> <PASSWORD>]</code><br>
|
||||
<br>
|
||||
Stellt einen Webhook für die HP1000 oder WH2600 Wetterstation von Fine Offset Electronics bereit.<br>
|
||||
@ -315,7 +315,7 @@ sub HP1000_CGI() {
|
||||
Da die URI ebenfalls fest kodiert ist, kann mit einer einzelnen FHEM Installation maximal eine HP1000/WH2600 Station gleichzeitig verwendet werden.<br>
|
||||
<br>
|
||||
Beispiel:<br>
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code># ungeschützte Instanz bei der ID und PASSWORD ignoriert werden<br>
|
||||
define WeatherStation HP1000<br>
|
||||
<br>
|
||||
|
@ -346,8 +346,6 @@ sub nonblockGetLinesTellStick {
|
||||
<code>define <name> TellStick </path/to/tdtool></code>
|
||||
<br><br>
|
||||
|
||||
<!--<div style="background-color: #ffaaaa;"> -->
|
||||
<div>
|
||||
Defines a path to the program "tdtool", which is used to control a (locally attached)
|
||||
"Telldus TellStick [Duo]" USB device. A TellStick controls a wide range of 433 MHz
|
||||
devices, like the widely available switchable power outlets from InterTechno.<br><br>
|
||||
|
@ -371,7 +371,7 @@ WS3600_Read($)
|
||||
how to implement a "networked setup" is left as an excercise to the
|
||||
reader. <br>
|
||||
For the records, this is an output of fetch3600:<br>
|
||||
<div style="height: 120px; width: 215px; border: 1px solid #cccccc; overflow: auto;">
|
||||
<div>
|
||||
<pre>Date 14-Nov-2009
|
||||
Time 10:50:22
|
||||
Ti 22.8
|
||||
@ -555,7 +555,7 @@ Forecast Cloudy</pre>
|
||||
<wsreaderprog> muss grundsätzlich eine zu fetch3600 vergleichbare
|
||||
Ausgabe auf der Standardausgabe liefern. <br>
|
||||
Als Beispiel für das erwartete Format hier die Ausgabe von fetch3600:<br>
|
||||
<div style="height: 120px; width: 215px; border: 1px solid #cccccc; overflow: auto;">
|
||||
<div>
|
||||
<pre>Date 14-Nov-2009
|
||||
Time 10:50:22
|
||||
Ti 22.8
|
||||
|
@ -808,15 +808,15 @@ sub HourCounter_Run($)
|
||||
=pod
|
||||
=begin html
|
||||
|
||||
<div id="includedContent">
|
||||
<div>
|
||||
<a name="HourCounter" id="HourCounter"></a>
|
||||
|
||||
<h3>HourCounter</h3>
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<a name="HourCounterdefine" id="HourCounterdefine"></a> <b>Define</b>
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<br />
|
||||
<code>define <name> HourCounter <pattern_for_ON> [<pattern_for_OFF>]</code><br />
|
||||
<br />
|
||||
@ -837,25 +837,25 @@ sub HourCounter_Run($)
|
||||
<b>Example:</b><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<code>define BurnerCounter HourCounter SHUTTER_TEST:on SHUTTER_TEST:off</code>
|
||||
</div>
|
||||
</div><br />
|
||||
<a name="HourCounterset" id="HourCounterset"></a> <b>Set-Commands</b>
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<br />
|
||||
<code>set <name> calc</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
starts the calculation of pulse/pause-time.<br />
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> clear</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
clears the readings countsPerDay, countsOverall,pauseTimeIncrement, pauseTimePerDay, pauseTimeOverall,
|
||||
pulseTimeIncrement, pulseTimePerDay, pulseTimeOverall by setting to 0.<br />
|
||||
The reading clearDate is set to the current Date/Time.
|
||||
@ -864,14 +864,14 @@ sub HourCounter_Run($)
|
||||
<code>set <name> countsOverall <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading countsOverall to the given value.This is the total-counter.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> countsPerDay <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading countsPerDay to the given value. This reading will automatically be set to 0, after change
|
||||
of day.
|
||||
</div><br />
|
||||
@ -879,7 +879,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pauseTimeIncrement <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pauseTimeIncrement to the given value.<br />
|
||||
This reading in seconds is automatically set after a rising edge.
|
||||
</div><br />
|
||||
@ -887,7 +887,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pauseTimeEdge <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pauseTimeEdge to the given value.<br />
|
||||
This reading in seconds is automatically set after a rising edge.
|
||||
</div><br />
|
||||
@ -895,7 +895,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pauseTimeOverall <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pauseTimeOverall to the given value.<br />
|
||||
This reading in seconds is automatically adjusted after a change of pauseTimeIncrement.
|
||||
</div><br />
|
||||
@ -903,7 +903,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pauseTimePerDay <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pauseTimePerDay to the given value.<br />
|
||||
This reading in seconds is automatically adjusted after a change of pauseTimeIncrement and set to 0 after
|
||||
change of day.
|
||||
@ -912,7 +912,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pulseTimeIncrement <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pulseTimeIncrement to the given value.<br />
|
||||
This reading in seconds is automatically set after a falling edge of the property.
|
||||
</div><br />
|
||||
@ -920,7 +920,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pulseTimeEdge <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pulseTimeEdge to the given value.<br />
|
||||
This reading in seconds is automatically set after a rising edge.
|
||||
</div><br />
|
||||
@ -928,7 +928,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pulseTimeOverall <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pulseTimeOverall to the given value.<br />
|
||||
This reading in seconds is automatically adjusted after a change of pulseTimeIncrement.
|
||||
</div><br />
|
||||
@ -936,7 +936,7 @@ sub HourCounter_Run($)
|
||||
<code>set <name> pulseTimePerDay <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Sets the reading pulseTimePerDay to the given value.<br />
|
||||
This reading in seconds is automatically adjusted after a change of pulseTimeIncrement and set to 0 after
|
||||
change of day.
|
||||
@ -945,54 +945,54 @@ sub HourCounter_Run($)
|
||||
<code>set <name> forceHourChange</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
This modifies the reading tickHour, which is automatically modified after change of hour.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> forceDayChange</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
This modifies the reading tickDay, which is automatically modified after change of day.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> forceWeekChange</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
This modifies the reading tickWeek, which is automatically modified after change of week.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> forceMonthChange</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
This modifies the reading tickMonth, which is automatically modified after change of month.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> forceYearChange</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
This modifies the reading tickYear, which is automatically modified after change of year.
|
||||
</div><br />
|
||||
<br />
|
||||
<code>set <name> app.* <value></code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Any reading with the leading term "app", can be modified.<br />
|
||||
This can be useful for user-readings.
|
||||
</div><br />
|
||||
</div><br />
|
||||
<a name="HourCounterget" id="HourCounterget"></a> <b>Get-Commands</b><br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
<br />
|
||||
<code>get <name> version</code><br />
|
||||
<br />
|
||||
|
||||
<div style="margin-left: 2em">
|
||||
<div>
|
||||
Get the current version of the module.
|
||||
</div><br />
|
||||
</div><br />
|
||||
|
Loading…
Reference in New Issue
Block a user