add ignore attribute for RFXCOM and TRX. Add longids to RFXCOM. Changes on RFXCOM to be compatible with TRX. Changes to commandref to reflect the changes

git-svn-id: https://fhem.svn.sourceforge.net/svnroot/fhem/trunk/fhem@1534 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
wherzig
2012-05-05 11:40:56 +00:00
parent a8e6f94f58
commit 88aa0ffe24
9 changed files with 458 additions and 261 deletions

View File

@@ -6043,7 +6043,13 @@ The one byte hex string is generated by the Oregon sensor when is it powered on.
<a name="OREGONget"></a>
<b>Get</b> <ul>N/A</ul><br>
<br>
<a name="OREGONattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
</ul>
<a name="OWFS"></a>
@@ -6354,6 +6360,25 @@ These receivers supports many protocols like Oregon Scientific weather sensors,
</ul>
<br>
</table>
<ul>
<li><a href="#attrdummy">dummy</a></li><br>
<li>longids<br>
Comma separated list of device-types for RFXCOM that should be handled using long IDs. This additional ID is a one byte hex string and is generated by the Oregon sensor when is it powered on. The value seems to be randomly generated. This has the advantage that you may use more than one Oregon sensor of the same type even if it has no switch to set a sensor id. For example the author uses two BTHR918N sensors at the same time. All have different deviceids. The drawback is that the deviceid changes after changing batteries. All devices listed as longids will get an additional one byte hex string appended to the device name.<br>
Default is to use long IDs for all devices.
<br><br>
Examples:<PRE>
# Do not use any long IDs for any devices:
attr RFXCOMUSB longids 0
# Use any long IDs for all devices (this is default):
attr RFXCOMUSB longids 1
# Use longids for BTHR918N devices.
# Will generate devices names like BTHR918N_f3.
attr RFXCOMUSB longids BTHR918N
# Use longids for TX3_T and TX3_H devices.
# Will generate devices names like TX3_T_07, TX3_T_01 ,TX3_H_07.
attr RFXCOMUSB longids TX3_T,TX3_H</PRE>
</li><br>
</ul>
</ul>
<a name="RFXMETER"></a>
@@ -6390,6 +6415,13 @@ These receivers supports many protocols like Oregon Scientific weather sensors,
<a name="RFXMETERget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="RFXMETERattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
</ul>
<a name="RFXX10REC"></a>
@@ -6460,6 +6492,13 @@ These receivers supports many protocols like Oregon Scientific weather sensors,
<a name="RFXX10RECget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="RFXX10RECattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
</ul>
<a name="WS2000"></a>
@@ -7352,9 +7391,14 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.</li>
<ul>
<li><a href="#attrdummy">dummy</a></li><br>
<li>longids<br>
Comma separated list of device-types for TRX_WEATHER that should be handled using long IDs. This additional ID is a one byte hex string and is generated by the Oregon sensor when is it powered on. The value seems to be randomly generated. This has the advantage that you may use more than one Oregon sensor of the same type even if it has no switch to set a sensor id. For example the author uses two BTHR918N sensors at the same time. All have different deviceids. The drawback is that the deviceid changes after changing batteries. All devices listed as longids will get an additional one byte hex string appended to the device name.
Comma separated list of device-types for TRX_WEATHER that should be handled using long IDs. This additional ID is a one byte hex string and is generated by the Oregon sensor when is it powered on. The value seems to be randomly generated. This has the advantage that you may use more than one Oregon sensor of the same type even if it has no switch to set a sensor id. For example the author uses two BTHR918N sensors at the same time. All have different deviceids. The drawback is that the deviceid changes after changing batteries. All devices listed as longids will get an additional one byte hex string appended to the device name.<br>
Default is to use no long IDs.
<br><br>
Examples:<PRE>
# Do not use any long IDs for any devices (this is default):
attr RFXCOMUSB longids 0
# Use long IDs for all devices:
attr RFXCOMUSB longids 1
# Use longids for BTHR918N devices.
# Will generate devices names like BTHR918N_f3.
attr RFXTRXUSB longids BTHR918N
@@ -7427,6 +7471,13 @@ attr RFXTRXUSB longids TX3_T,TX3_H</PRE>
<a name="TRX_SECURITYget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="TRX_SECURITYattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
</ul>
<a name="TRX_LIGHT"></a>
@@ -7513,6 +7564,14 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. <br> You need to define an RFXtrx433
<a name="TRX_LIGHTget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="TRX_LIGHTattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
</ul>
<a name="TRX_WEATHER"></a>
@@ -7548,8 +7607,8 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. <br> You need to define an RFXtrx433
"PCR800",<br>
"TFA_RAIN" (for TFA rain sensor),<br>
"WTGR800_A" (for wind sensor of WTGR800),<br>
"WGR800_A" (for wind sensor of WGR800),<br>
"WGR918_A" (for wind sensor of STR918 and WGR918),<br>
"WGR800" (for wind sensor of WGR800),<br>
"WGR918" (for wind sensor of STR918 and WGR918),<br>
"TFA_WIND" (for TFA wind sensor)
<br>
<br><br>
@@ -7561,11 +7620,18 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK. <br> You need to define an RFXtrx433
</ul>
<br>
<a name="OREGONset"></a>
<a name="TRX_WEATHERset"></a>
<b>Set</b> <ul>N/A</ul><br>
<a name="OREGONget"></a>
<a name="TRX_WEATHERget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="TRX_WEATHERattr"></a>
<b>Attributes</b>
<ul>
<li><a href="#ignore">ignore</a></li><br>
<li><a href="#do_not_notify">do_not_notify</a></li><br>
</ul>
<br>
</ul>