From 399d2114d37e2ca10c33f7c6ba8e9195755e89a6 Mon Sep 17 00:00:00 2001
From: rudolfkoenig <>
Date: Wed, 2 Oct 2013 12:46:16 +0000
Subject: [PATCH] FHT80b: housecode replaced with fhtaddress, as suggested by
 Christian

git-svn-id: https://svn.fhem.de/fhem/trunk@3992 2b470e98-0d58-463d-a4d8-8e2adae1ed80
---
 fhem/FHEM/11_FHT.pm | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/fhem/FHEM/11_FHT.pm b/fhem/FHEM/11_FHT.pm
index af583a8be..8a5ba402b 100755
--- a/fhem/FHEM/11_FHT.pm
+++ b/fhem/FHEM/11_FHT.pm
@@ -718,10 +718,10 @@ getFhtBuffer($)
   <a name="FHTdefine"></a>
   <b>Define</b>
   <ul>
-    <code>define &lt;name&gt; FHT &lt;housecode&gt;</code>
+    <code>define &lt;name&gt; FHT &lt;fhtaddress&gt;</code>
     <br><br>
 
-    <code>&lt;housecode&gt;</code> is a four digit hex number,
+    <code>&lt;fhtaddress&gt;</code> is a four digit hex number,
     corresponding to the address of the FHT80b device.
     <br>
 
@@ -809,7 +809,7 @@ getFhtBuffer($)
           <br>
 
       <li>The FHT is very economical (or lazy), it accepts one message from the
-          FHZ1x00 every 115+x seconds, where x depends on the housecode. Don't
+          FHZ1x00 every 115+x seconds, where x depends on the fhtaddress. Don't
           be surprised if your command is only accepted 10 minutes later by the
           device. FHT commands are buffered in the FHZ1x00/CUL till they are
           sent to the FHT, see the related <code>fhtbuf</code> entry in the