HM-SWI-3-FM support

git-svn-id: https://svn.fhem.de/fhem/trunk@1454 2b470e98-0d58-463d-a4d8-8e2adae1ed80

fhem/FHEM/10_CUL_HM.pm

@@ -92,7 +92,7 @@ my %culHmModel=(
   "0043" => "HM-SEC-TIS",
   "0044" => "HM-SEN-EP",
   "0045" => "HM-SEC-WDS",     # Tested by peterp
-  "0046" => "HM-SWI-3-FM",
+  "0046" => "HM-SWI-3-FM",    # Tested by NorbertW
   "0047" => "KFM-Display",
   "0048" => "IS-WDS-TH-OD-S-R3",
   "0049" => "KFM-Sensor",
@@ -112,9 +112,9 @@ my %culHmModel=(
   "0059" => "HM-LC-DIM1T-FM",
   "005A" => "HM-LC-DIM2T-SM",
   "005C" => "HM-OU-CF-PL",
-  "005F" => "HM-SCI-3-FM",
+  "005F" => "HM-SCI-3-FM",     # Tested by fhem-hm-knecht
   "0060" => "HM-PB-4DIS-WM",   # Tested
-  "0061" => "HM-LC-SW4-DR",    # Tested by fhem-hm-knecht.
+  "0061" => "HM-LC-SW4-DR",    # Tested by fhem-hm-knecht
   "0062" => "HM-LC-SW2-DR",
   "0066" => "HM_LC_Sw4-WM",    # Tested by peterp
   "006C" => "HM-LC-SW1-PCB",   # By jan (unsure if working)
@@ -613,7 +613,17 @@ CUL_HM_Parse($$)
         CUL_HM_SendCmd($shash, "++8002".$id.$src."0101".    # Send Ack.
                 ($state =~ m/on/?"C8":"00")."00", 1, 0);
       }
+    }
 
+  } elsif($st eq "swi") { ################################################
+    # Raw data by NorbertW
+    if($cmd =~ m/^..4./ && $p =~ m/^(..)(..)$/) {
+      my ($button, $bno) = (hex($1), hex($2));
+      push @event, "state:Btn$button toggle$target";
+
+      if($id eq $dst && $cmd ne "8002") {  # Send Ack
+        CUL_HM_SendCmd($shash, "++8002".$id.$src."01010000",1,0) # Send Ack.
+      }
     }
 
   } elsif($st eq "motionDetector") { #####################################

fhem/docs/commandref.html

@@ -2793,10 +2793,44 @@ A line ending with \ will be concatenated with the next one, so long lines
 <h3>CUL_HM</h3>
 <ul>
   Support for eQ-3 HomeMatic devices via the <a href="#CUL">CUL</a> or the <a
-  href="#HMLAN">HMLAN</a>.
+  href="#HMLAN">HMLAN</a>.<br>
-
   <br>
-  Prerequisites:
+  <a name="CUL_HMdefine"></a>
+  <b>Define</b>
+  <ul>
+    <code>define &lt;name&gt; CUL_HM &lt;6-digit-hex-code&gt;</code>
+    <br><br>
+    Normally this command is generated by the <a
+    href="#autocreate">autocreate</a> module, together with the necessary
+    hmClass and subType attributes. Usually you issue a <a
+    href="#CULset">hmPairForSec</a> command and press the corresponding button
+    on the device to be paired, or issue a <a href="#CULset">hmPairSerial</a>
+    set command if the device is a receiver and you know its serial number.
+    Autocreate will then create a fhem device and set all necessary attributes.
+    Without pairing the device will not accept messages from fhem.
+    fhem may create the device even if the pairing is not successful. Upon a
+    successful pairing you'll see a CommandAccepted entry in the details
+    section of the CUL_HM device.
+
+    <br><br>
+    If you cannot use autocreate, then you have to specify:<br>
+    <ul>
+      <li>the &lt;6-digit-hex-code&gt;<br>
+          which is the hardcoded address of the device (no, you cannot choose
+          it arbitrarily like for FS20 devices). You may detect it by
+          inspecting the fhem log.
+      <li>the hmClass attribute<br>
+          which is either sender or receiver
+      <li>the subType attribute<br>
+          which is one of switch dimmer blindActuator remote sensor  swi
+          pushButton threeStateSensor motionDetector  keyMatic winMatic
+          smokeDetector<br>
+          Without these attributes fhem won't be able to decode device messages
+          appropriately.
+
+    </ul>
+    <br>
+    <b>Notes</b>
     <ul>
     <li>If the interface is a CUL device, the <a href="#rfmode">rfmode </a>
         attribute of the corresponding CUL/CUN device must be set to HomeMatic.
@@ -2804,15 +2838,6 @@ A line ending with \ will be concatenated with the next one, so long lines
         FS20/HMS/EM/S300 messages via this device. Previously defined FS20/HMS
         etc devices must be assigned to a different input device (CUL/FHZ/etc).
         </li>
-  <li>The protocol used by HomeMatic devices (BidCos, known as AskSin
-      in the culfw) must be enabled in the culfw firmware. This is done for all
-      CUN and for newer CUL (i.e. V3.0 and greater) devices with culfw firmware
-      version 1.38 and newer. For CUL hardware version before 3.0 there is a
-      separate firmware with HomeMatic support which lacks FHT support.
-      </li>
-  </ul>
-  <b>Notes</b>
-  <ul>
     <li>Currently supported device families: remote, switch, dimmer,
         blindActuator, motionDetector, smokeDetector, threeStateSensor, THSensor,
         winmatic. Special devices: KS550, HM-CC-TC and the KFM100.
@@ -2849,38 +2874,7 @@ A line ending with \ will be concatenated with the next one, so long lines
             recommend using Homematic encryption at all.
         </ul>
     </ul>
-  <br><br>
 
-  <a name="CUL_HMdefine"></a>
-  <b>Define</b>
-  <ul>
-    <code>define &lt;name&gt; CUL_HM &lt;6-digit-hex-code&gt;</code>
-    <br><br>
-    Normally this command is generated by the <a
-    href="#autocreate">autocreate</a> module, together with the necessary
-    hmClass and subType attributes. Usually you issue a <a
-    href="#CULset">hmPairForSec</a> command and press the corresponding button
-    on the device to be paired, or issue a <a href="#CULset">hmPairSerial</a>
-    set command if the device is a receiver and you know its serial number.
-    Autocreate will then create a fhem device and set all necessary attributes.
-    Without pairing the device will not accept messages from fhem.
-    <br><br>
-    If you cannot use autocreate, then you have to specify:<br>
-    <ul>
-      <li>the &lt;6-digit-hex-code&gt;<br>
-          which is the hardcoded address of the device (no, you cannot choose
-          it arbitrarily like for FS20 devices). You may detect it by
-          inspecting the fhem log.
-      <li>the hmClass attribute<br>
-          which is either sender or receiver
-      <li>the subType attribute<br>
-          which is one of switch dimmer blindActuator remote sensor  swi
-          pushButton threeStateSensor motionDetector  keyMatic winMatic
-          smokeDetector<br>
-          Without these attributes fhem won't be able to decode device messages
-          appropriately.
-
-    </ul>
   </ul><br>
 
   <a name="CUL_HMset"></a>
@@ -3092,6 +3086,9 @@ A line ending with \ will be concatenated with the next one, so long lines
       Btn$x offLong $counter (to $dest)<br>
       Btn$x onLongRelease $counter (to $dest)<br>
       Btn$x offLongRelease $counter (to $dest)<br>
+  <li>swi<br>
+      Btn$x toggle<br>
+      Btn$x toggle (to $dest)<br>
   <li>motionDetector<br>
       brightness:$b<br>
       alive<br>