From 1a6929f5417020f539fad2193740c11cc4827f5e Mon Sep 17 00:00:00 2001
From: wherzig <>
Date: Fri, 24 Feb 2012 18:03:11 +0000
Subject: [PATCH] OREGON minor changes

git-svn-id: https://svn.fhem.de/fhem/trunk@1281 2b470e98-0d58-463d-a4d8-8e2adae1ed80
---
 fhem/docs/commandref.html | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/fhem/docs/commandref.html b/fhem/docs/commandref.html
index 57fcd1934..5fa307f4f 100644
--- a/fhem/docs/commandref.html
+++ b/fhem/docs/commandref.html
@@ -3213,6 +3213,7 @@ A line ending with \ will be concatenated with the next one, so long lines
     </ul> <br>
 
   <a name="CUL_RFRset"></a>
+
   <b>Set</b> <ul>Same as for the <a href="#CULset">CUL</a>.</ul><br>
 
   <a name="CUL_RFRget"></a>
@@ -5654,6 +5655,7 @@ audio</pre>
     &lt;deviceid&gt; is the device identifier of the Oregon sensor. It consists of the sensors name and a one byte hex string (00-ff) that identifies the sensor. The define statement with the deviceid is generated automatically by autocreate. The following sensor names are used:
 BTHR918, BTHR918N, PCR800 RGR918, RTGR328N, THN132N, THGR228N, THGR328N, THGR918, THR128, THWR288A, THGR810, UV138, UVN800, WGR918, WGR800, WTGR800_A, WTGR800_T.
     <br>
+The one byte hex string 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 exampple the author uses three BTHR918 sensors at the same time. All have different deviceids. The drawback is that the deviceid changes after changing batteries.
     <br><br>
       Example: <br>
     <code>define Kaminzimmer OREGON BTHR918N_ab</code>