Support for Telldus TellStick

git-svn-id: https://fhem.svn.sourceforge.net/svnroot/fhem/trunk/fhem@1215 2b470e98-0d58-463d-a4d8-8e2adae1ed80
This commit is contained in:
real-wusel
2012-01-23 21:36:46 +00:00
parent 8a5ef48724
commit a6e70be3c5
2 changed files with 397 additions and 6 deletions

View File

@@ -114,6 +114,7 @@
<a href="#SISPM">SISPM</a> &nbsp;
<a href="#SIS_PMS">SIS_PMS</a> &nbsp;
<a href="#TCM">TCM</a> &nbsp;
<a href="#TellStick">TellStick</a> &nbsp;
<a href="#USF1000">USF1000</a> &nbsp;
<a href="#USBWX">USBWX</a> &nbsp;
<a href="#VantagePro2">VantagePro2</a> &nbsp;
@@ -6203,11 +6204,6 @@ Forecast Cloudy</pre>
<!--<div style="background-color: #ffaaaa;"> -->
<div>
<i><b>PLEASE NOTE:</b> This module is still work in progess; please treat it as such.
(That is, don't but your central heating on SISPM in a cold winter just yet ;))</i><br><br>
Further tests should be done regarding the interaction between "set" commands and the sheduled
status reading. (Testing with FIFOs seems as if it's working without blocking nor interference,
but that's on a mostly unloaded, fast system.)<br><br>
When <i>using multiple SIS PMs on one host</i>, sispmctl up to and including V 2.7 has a bug:
<pre>plug-2:# sispmctl -v -s -d 1 -g all -d 2 -g all
@@ -6253,7 +6249,8 @@ Terminating
"Silver Shield Power Manager" devices. Usually these are connected to the local computer
via USB, more than one "sispm" device per computer is supported. (Please note that, due
to neglections in their USB driver, AVM's Fritz!Box 7170 (and derivates, like Deutsche
Telekom's Speedport W901V) <b>is not</b> able to talk to these devices ...)
Telekom's Speedport W901V) <b>is not</b> able to talk to these devices ... The Fritz!Box
72xx and 73xx should be fine.)
The communication between FHEM and the Power Manager device is done by using the open
source <a href="http://sispmctl.sourceforge.net/">sispmctl</a> program. Thus, for the
@@ -6390,6 +6387,67 @@ Terminating
<li><a href="#loglevel">loglevel</a></li><br>
</ul>
</ul>
<a name="TellStick"></a>
<h3>TellStick</h3>
<ul>
<br>
<a name="TellStickdefine"></a>
<b>Define</b>
<ul>
<code>define &lt;name&gt; TellStick &lt;/path/to/tdtool&gt;</code>
<br><br>
<!--<div style="background-color: #ffaaaa;"> -->
<div>
Defines a path to the program "tdtool", which is used to control a (locally attached)
"Telldus TellStick [Duo]" USB device. A TellStick controls a wide range of 433 MHz
devices, like the widely available switchable power outlets from InterTechno.<br><br>
To keep things simple, FHEM interfaces with the telldus-core suite (available
for Linux, Windows, Mac OSX) via the supplied tool, "tdtool". This FHEM module
will initially use "tdtool --list" to receive a list of configured devices, then let
autocreate (if enabled) create them as <a href="#SIS_PMS">SIS_PMS</a> devices.<br></br>
<i>Please make sure</i> that the user running FHEM under ("fhem" in a standard setup on
Linux) has the <i>r/w-right to access the stick's device</i> ("/dev/tellstick"
in telldus-core version 2.0) &mdash; if the state of your devices do not change when
modified im FHEM, access rights problems are the most probable cause
(<code>chmod o+rw /dev/tellstick</code> should fix that; you may want to automate it
via udev or adding the fhem user to the proper group ;))<br></br>
This module has only been tested with the 2.0 branch of teldus-core because of a known bug
in 2.1, <a href="http://www.telldus.com/forum/viewtopic.php?f=15&t=1645"> preventing
version 2.1 working properly with some TellSticks</a> and/or "tdtool" application; FTR, the
"Batch: 8" version a was granted usage of for writing this module was impacted by it ...
To actually control any power sockets, you need to define a <a href="#SIS_PMS">SIS_PMS</a>
device &mdash; TellStick.pm uses SIS_PMS devices ("socket" is te:ll:st:ck:01, "socketnr"
is the ID of the device in "tdtool"), as as of now only on/off switching is supported and
this was the easiest implementation path. SIS_PMS is supported by <a href="http://sites.google.com/site/andfhem/">andFHEM</a>, the Android
frontend, so this make some sense. (Furthermore, I don't own dimmable devices and they are
actually not really cheap; >15 EUR/socket compared to the 15 EUR for 5 switch-only, non-self
learning socket adapters from Intertechno at your local home improvement store.)
<br><br>
Example:
<ul>
<code>define TStick TellStick /usr/bin/tdtool</code><br>
<code>define Deckenfluter SIS_PMS te:ll:st:ck:01 2</code><br>
</ul>
<br>
</ul>
<a name="TellStickset"></a>
<b>Set</b> <ul>N/A</ul><br>
<a name="TellStickget"></a>
<b>Get</b> <ul>N/A</ul><br>
<a name="TellStickattr"></a>
<b>Attributes</b>
<ul>
<li>none <!--<a href="#model">model</a> (TellStick)--></li>
</ul>
<br>
</ul>
<a name="IPWE"></a>
<h3>IPWE</h3>