2
0
mirror of https://github.com/fhem/fhem-mirror.git synced 2025-01-31 06:39:11 +00:00

better explanation of longids for TRX

git-svn-id: https://svn.fhem.de/fhem/trunk@1448 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
wherzig 2012-04-12 17:49:24 +00:00
parent 36f0a27b8e
commit e0ea4ace7c

View File

@ -7259,13 +7259,17 @@ KlikAanKlikUit, NEXA, CHACON, HomeEasy UK.</li>
<ul>
<li><a href="#attrdummy">dummy</a></li><br>
<li>longids<br>
Comma separates list of device-types for TRX_WEATHER that should be handles 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.
<br>
Example: <br>
<code>attr RFXTRXUSB longids BTHR918N</code>
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><br>
Examples:<PRE>
# Use longids for BTHR918N devices.
# Will generate devices names like BTHR918N_f3.
attr RFXTRXUSB 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 RFXTRXUSB longids TX3_T,TX3_H</PRE>
</li><br>
</ul>
<br>
</ul>