FHEM2FHEM and associated changes

git-svn-id: https://fhem.svn.sourceforge.net/svnroot/fhem/trunk/fhem@732 2b470e98-0d58-463d-a4d8-8e2adae1ed80

docs/commandref.html

@@ -121,6 +121,7 @@
   <b>Helper modules</b>
   <ul>
     <a href="#DbLog">DbLog</a> &nbsp;
+    <a href="#FHEM2FHEM">FHEM2FHEM</a> &nbsp;
     <a href="#FHEMRENDERER">FHEMRENDERER</a> &nbsp;
     <a href="#FHEMWEB">FHEMWEB</a> &nbsp;
     <a href="#FileLog">FileLog</a> &nbsp;
@@ -506,7 +507,7 @@ A line ending with \ will be concatenated with the next one, so long lines
 <a name="inform"></a>
 <h3>inform</h3>
 <ul>
-  <code>inform [on|off|timer]</code> <br>
+  <code>inform [on|off|timer|raw]</code> <br>
   <br>
   If set to on, and a device state changes, send a notification to the current
   client. This command can be used by other programs/modules to receive a
@@ -4694,6 +4695,66 @@ Terminating
 
 </ul>
 
+<a name="FHEM2FHEM"></a>
+<h3>FHEM2FHEM</h3>
+<ul>
+  FHEM2FHEM is a helper module to connect separate fhem installations.
+
+  <a name="FHEM2FHEMdefine"></a>
+  <b>Define</b>
+  <ul>
+    <code>define &lt;name&gt; FHEM2FHEM &lt;host:portnr&gt; [LOG:regexp|RAW:devicename]
+    </code>
+  </ul>
+  <br>
+  Conect to the <i>remote</i> fhem on host. portnr is the global port
+  attribute of the remote fhem. The next parameter specifies the connection
+  type:
+  <ul>
+  <li>LOG<br>
+    Using this type you will receive all events generated by the remote fhem,
+    just like when using the <a href="#inform">inform on</a> command, and you
+    can use these events just like any local event for <a
+    href="#FileLog">FileLog </a> or <a href="#notify">notify</a>.
+    The regexp will prefilter the events distributed locally, for the syntax
+    see the notify definition.<br>
+    Drawbacks: the remote devices wont be created locally, so list wont
+    show them and it is not possible to manipulate them from the local
+    fhem. It is possible to create a device with the same name on both fhem
+    instances, but if both of them receive the same event (e.g. because both
+    of them have a CUL attached), then all associated FileLogs/notifys will be
+    triggered twice.  </li>
+
+  <li>RAW<br>
+    By using this type the local fhem will receive raw events from the remote
+    fhem device <i>devicename</i>, just like if it would be attached to the
+    local fhem.
+    Drawback: only devices using the Dispatch function (CUL, FHZ, CM11,
+    SISPM, RFXCOM) generate raw messages.
+  </ul>
+  Examples:
+  <ul>
+    <code>define ds1 FHEM2FHEM 192.168.0.1:7072 LOG:.*</code><br>
+    <code>define ds2 FHEM2FHEM 192.168.0.1:7072 RAW:CUL</code><br>
+  </ul>
+  <br>
+
+  <a name="FHEM2FHEMset"></a>
+  <b>Set</b> <ul>N/A</ul><br>
+
+  <a name="FHEM2FHEMget"></a>
+  <b>Get</b> <ul>N/A</ul><br>
+
+  <a name="FHEM2FHEMattr"></a>
+  <b>Attributes</b>
+  <ul>
+    <li><a href="#dummy">dummy</a></li>
+    <li><a href="#loglevel">loglevel</a></li>
+  </ul>
+
+</ul>
+
+
 <a name="FHEMWEB"></a>
 <h3>FHEMWEB</h3>
 <ul>