TellStick Duo
Model: TSDUO
- Batch number: 13062
- serial number: 201653
- Frequency: 433.92 MHz
- Range: 30 meters
- connection: usb 2.0, 1.1
- firmware version: 12 (was: 5)
Links
Telldus developer, TellStick duo firmware, current firmware versions, Firmware upgrade, TellStick Duo flasher, telldus-core, TellStick installation - Linux, Telldus blog: tellstick-duo, HomeAutomation, Steelsquid Tellstick Server, tellcore-py, Linux FT232R Projects and Stuff!, Arduino bibliotek,
HA links
local links
[v2 - FreeBSD], [Banana Pi] - [Bananian],
back to home automation page.
History / work log
2021-08-09: I re-created this page on my self-hosted web server.
2018-01-03: v2 - test the TellStick Duo
tingo@kg-v2$ pwd /usr/home/tingo/work/telldus-core-2.1.1 tingo@kg-v2$ pgrep -lf tell 79740 service/telldusd
check /var/log/messages
tingo@kg-v2$ tail /var/log/messages | grep telldusd Jan 3 19:40:15 kg-v2 telldusd: telldusd daemon starting up Jan 3 19:40:15 kg-v2 telldusd: Could not open pid file /var/run/telldusd.pid: Permission denied Jan 3 19:40:15 kg-v2 telldusd: Connecting to TellStick (1781/C31) with serial A6028ED8
interesting
tingo@kg-v2$ tellcore_controllers Error: unable to list controllers (are you using telldus-core >= 2.1.2?) Undefined symbol "tdController"
ok, that won't work. But this does:
tingo@kg-v2$ tellcore_tool --list-sensors Number of sensors: 3 PROTOCOL MODEL ID TEMP HUMIDITY RAIN WIND LAST UPDATED mandolyn temperaturehumidity 11 24.4 C 0 % 2018-01-03 19:44:51 fineoffset temperature 206 7.8 C 2018-01-03 19:44:58 mandolyn temperaturehumidity 12 -21.8 C 51 % 2018-01-03 19:45:11
ok, so something is wrong with my Banana Pi setup.
2015-03-15: a quick check of sensors, to see if firmware upgrade has improved sensor protocol understanding:
tingo@kg-bpi:~$ tellcore_tool --list-sensors Number of sensors: 9 PROTOCOL MODEL ID TEMP HUMIDITY RAIN WIND LAST UPDATED fineoffset temperature 255 -204.7 C 2015-03-15 00:47:04 fineoffset temperature 186 4.8 C 2015-03-15 01:31:46 fineoffset temperaturehumidity 22 9.2 C 30 % 2015-03-14 21:29:59 fineoffset temperaturehumidity 62 1.8 C 36 % 2015-03-14 03:25:10 fineoffset temperaturehumidity 10 0.8 C 39 % 2015-03-14 07:00:22 fineoffset temperature 93 1.8 C 2015-03-14 06:49:21 fineoffset temperaturehumidity 54 18.8 C 22 % 2015-03-14 13:39:35 fineoffset temperature 254 57.5 C 2015-03-14 17:44:34 mandolyn temperaturehumidity 11 -22.2 C 0 % 2015-03-15 00:03:44
well, mandolyn looks new. Or not - that sensor (id 11) is in the 2014-04-09 output.
2015-03-15: firmware - after the upgrade, I plug the TSDUO back int the Banana Pi again, and use tellcore_controllers to check firmware version:
tingo@kg-bpi:~$ tellcore_controllers TellStick Duo name: <unnamed> serial: A6028ED8 firmware: 12 available: 1 Found 1 controller(s)
nice.
2015-03-15: firmware - upgrade; second try - I booted my laptop into Win7, downloaded TellStickNetFlasher and tried it. It didn't find my TSDUO, and win7 couldn't find any drivers to install. Next up was TelldusCenter, install, stop Telldus Service, find TellStick Flasher in the TelldusCenter directory, start it, allow it to pass win firewall, and it finds the TSDUO, says firmware is version 5, latest is 12. I select the Duo, and it starts the firmware upload process. The process took a while, afterwards the TSDUO runs firmware version 12.
2015-03-14: firmware - upgrade; first try - Mac mini G4, doesn't work because the Flasher is for Intel. Next Try, Mac mini Intel, running OSX 10.7.5. Here the Flasher crashes every time I try to start it. Oh, crap.
2015-03-13: firmware - try to change the cbus 0,1,2,3 pins with ft232r_prog:
tingo@kg-bpi:~$ sudo /home/tingo/work/ft232r_prog-1.24/ft232r_prog --old-vid 0x1781 --old-pid 0xc31 --cbus0 IO --cbus1 IO --cbus2 IO --cbus3 IO ft232r_prog: version 1.24, by Mark Lord. eeprom_size = 128 vendor_id = 0x1781 product_id = 0x0c31 self_powered = 0 remote_wakeup = 0 suspend_pull_downs = 0 max_bus_power = 90 mA manufacturer = Telldus product = TellStick Duo serialnum = A6028ED8 high_current_io = 0 load_d2xx_driver = 1 txd_inverted = 0 rxd_inverted = 0 rts_inverted = 0 cts_inverted = 0 dtr_inverted = 0 dsr_inverted = 0 dcd_inverted = 0 ri_inverted = 0 cbus[0] = IO cbus[1] = IO cbus[2] = IO cbus[3] = IO cbus[4] = Sleep Rewriting eeprom with new contents.
cool. verify:
tingo@kg-bpi:~$ sudo /home/tingo/work/ft232r_prog-1.24/ft232r_prog --dump --old-vid 0x1781 --old-pid 0xc31 ft232r_prog: version 1.24, by Mark Lord. eeprom_size = 128 vendor_id = 0x1781 product_id = 0x0c31 self_powered = 0 remote_wakeup = 0 suspend_pull_downs = 0 max_bus_power = 90 mA manufacturer = Telldus product = TellStick Duo serialnum = A6028ED8 high_current_io = 0 load_d2xx_driver = 1 txd_inverted = 0 rxd_inverted = 0 rts_inverted = 0 cts_inverted = 0 dtr_inverted = 0 dsr_inverted = 0 dcd_inverted = 0 ri_inverted = 0 cbus[0] = IO cbus[1] = IO cbus[2] = IO cbus[3] = IO cbus[4] = Sleep No change from existing eeprom contents.
nice.
2015-03-13: firmware - check if ft232r_prog will talk to the device. First, stop telldusd:
tingo@kg-bpi:~$ sudo service telldusd stop tingo@kg-bpi:~$ sudo service telldusd status [FAIL] telldusd is not running ... failed!
Next, try ft232r_prog:
tingo@kg-bpi:~/work/ft232r_prog-1.24$ sudo /home/tingo/work/ft232r_prog-1.24/ft232r_prog --dump --old-vid 0x1781 --old-pid 0xc31 ft232r_prog: version 1.24, by Mark Lord. eeprom_size = 128 vendor_id = 0x1781 product_id = 0x0c31 self_powered = 0 remote_wakeup = 0 suspend_pull_downs = 0 max_bus_power = 90 mA manufacturer = Telldus product = TellStick Duo serialnum = A6028ED8 high_current_io = 0 load_d2xx_driver = 1 txd_inverted = 0 rxd_inverted = 0 rts_inverted = 0 cts_inverted = 0 dtr_inverted = 0 dsr_inverted = 0 dcd_inverted = 0 ri_inverted = 0 cbus[0] = TxLED cbus[1] = RxLED cbus[2] = TxDEN cbus[3] = PwrEn cbus[4] = Sleep No change from existing eeprom contents.
now that is interesting.
2015-03-13: firmware - perhaps ft232r_prog from Linux FT232R Projects will work as a MProg standin?
tingo@kg-bpi:~/dl$ wget http://rtr.ca/ft232r/ft232r_prog-1.24.tar.gz --2015-03-13 22:16:58-- http://rtr.ca/ft232r/ft232r_prog-1.24.tar.gz Resolving rtr.ca (rtr.ca)... 24.53.243.190 Connecting to rtr.ca (rtr.ca)|24.53.243.190|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 13509 (13K) [application/x-gzip] Saving to: `ft232r_prog-1.24.tar.gz' 100%[===========================================================================>] 13,509 13.8K/s in 1.0s 2015-03-13 22:16:59 (13.8 KB/s) - `ft232r_prog-1.24.tar.gz' saved [13509/13509]
ok. Try to build it:
tingo@kg-bpi:~/dl$ cd ~/work tingo@kg-bpi:~/work$ tar xvf ~/dl/ft232r_prog-1.24.tar.gz ft232r_prog-1.24/ ft232r_prog-1.24/Changelog ft232r_prog-1.24/ft232r_prog.c ft232r_prog-1.24/LICENSE.txt ft232r_prog-1.24/Makefile tingo@kg-bpi:~/work$ cd ft232r_prog-1.24/ tingo@kg-bpi:~/work/ft232r_prog-1.24$ make cc -Wall -O2 -s -Werror -o ft232r_prog ft232r_prog.c -lusb -lftdi -s
try it:
tingo@kg-bpi:~/work/ft232r_prog-1.24$ ./ft232r_prog ft232r_prog: version 1.24, by Mark Lord. Usage: ft232r_prog [<arg> <val>].. where <arg> must be any of: --help # (show this help text) --dump # (dump eeprom settings to stdout)) --verbose # (show debug info and raw eeprom contents) --save # (save original eeprom contents to file) --restore # (restore initial eeprom contents from file) --cbus0 [TxDEN|PwrEn|RxLED|TxLED|TxRxLED|Sleep|Clk48|Clk24|Clk12|Clk6|IO|WR|RD|RxF] --cbus1 [TxDEN|PwrEn|RxLED|TxLED|TxRxLED|Sleep|Clk48|Clk24|Clk12|Clk6|IO|WR|RD|RxF] --cbus2 [TxDEN|PwrEn|RxLED|TxLED|TxRxLED|Sleep|Clk48|Clk24|Clk12|Clk6|IO|WR|RD|RxF] --cbus3 [TxDEN|PwrEn|RxLED|TxLED|TxRxLED|Sleep|Clk48|Clk24|Clk12|Clk6|IO|WR|RD|RxF] --cbus4 [TxDEN|PwrEn|RxLED|TxLED|TxRxLED|Sleep|Clk48|Clk24|Clk12|Clk6|IO|WR|RD|RxF] --manufacturer <string> # (new USB manufacturer string) --product <string> # (new USB product name string) --old-serial-number <string> # (current serial number of device to be reprogrammed) --new-serial-number <string> # (new USB serial number string) --self-powered [on|off] # (self powered) --max-bus-power <number> # (max bus current in milli-amperes) --high-current-io [on|off] # (enable high [6mA @ 5V] drive current on CBUS pins) --suspend-pull-down [on|off] # (force I/O pins into logic low state on suspend) --old-vid <number> # (current vendor id of device to be reprogrammed, eg. 0x0403) --old-pid <number> # (current product id of device to be reprogrammed, eg. 0x6001) --new-vid <number> # (new/custom vendor id to be programmed) --new-pid <number> # (new/custom product id be programmed) --invert_txd Inverts the current value of TXD --invert_rxd Inverts the current value of RXD --invert_rts Inverts the current value of RTS --invert_cts Inverts the current value of CTS --invert_dtr Inverts the current value of DTR --invert_dsr Inverts the current value of DSR --invert_dcd Inverts the current value of DCD --invert_ri Inverts the current value of RI
interesting.
2015-03-13: firmware - the thread Tellstick duo. Custom firmware ? mentions the flasher. See if we can get it to compile:
tingo@kg-bpi:~$ cd work tingo@kg-bpi:~/work$ mkdir duo_flasher tingo@kg-bpi:~/work$ cd duo_flasher/ tingo@kg-bpi:~/work/duo_flasher$ get the source tingo@kg-bpi:~/work/duo_flasher$ wget http://developer.telldus.com/browser/TellStick%20Duo/flasher/CMakeLists.txt --2015-03-13 21:37:39-- http://developer.telldus.com/browser/TellStick%20Duo/flasher/CMakeLists.txt Resolving developer.telldus.com (developer.telldus.com)... 46.21.105.96 Connecting to developer.telldus.com (developer.telldus.com)|46.21.105.96|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10482 (10K) [text/html] Saving to: `CMakeLists.txt' 100%[===========================================================================>] 10,482 --.-K/s in 0.04s 2015-03-13 21:37:40 (268 KB/s) - `CMakeLists.txt' saved [10482/10482] tingo@kg-bpi:~/work/duo_flasher$ wget http://developer.telldus.com/browser/TellStick%20Duo/flasher/main.cpp --2015-03-13 21:38:11-- http://developer.telldus.com/browser/TellStick%20Duo/flasher/main.cpp Resolving developer.telldus.com (developer.telldus.com)... 46.21.105.96 Connecting to developer.telldus.com (developer.telldus.com)|46.21.105.96|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 58494 (57K) [text/html] Saving to: `main.cpp' 100%[===========================================================================>] 58,494 232K/s in 0.2s 2015-03-13 21:38:12 (232 KB/s) - `main.cpp' saved [58494/58494] tingo@kg-bpi:~/work/duo_flasher$ wget http://developer.telldus.com/browser/telldus-core/driver/libtelldus-core/osx/ftd2xx.h?rev=c01bd73a3177b5295250af009241d29cdef3bea5 -O ftd2xx.h --2015-03-13 21:41:15-- http://developer.telldus.com/browser/telldus-core/driver/libtelldus-core/osx/ftd2xx.h?rev=c01bd73a3177b5295250af009241d29cdef3bea5 Resolving developer.telldus.com (developer.telldus.com)... 46.21.105.96 Connecting to developer.telldus.com (developer.telldus.com)|46.21.105.96|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 117364 (115K) [text/html] Saving to: `ftd2xx.h' 100%[===========================================================================>] 117,364 229K/s in 0.5s 2015-03-13 21:41:17 (229 KB/s) - `ftd2xx.h' saved [117364/117364] tingo@kg-bpi:~/work/duo_flasher$ wget http://developer.telldus.com/browser/telldus-core/driver/libtelldus-core/osx/WinTypes.h?rev=c01bd73a3177b5295250af009241d29cdef3bea5 -O WinTypes.h --2015-03-13 21:42:06-- http://developer.telldus.com/browser/telldus-core/driver/libtelldus-core/osx/WinTypes.h?rev=c01bd73a3177b5295250af009241d29cdef3bea5 Resolving developer.telldus.com (developer.telldus.com)... 46.21.105.96 Connecting to developer.telldus.com (developer.telldus.com)|46.21.105.96|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 24146 (24K) [text/html] Saving to: `WinTypes.h' 100%[===========================================================================>] 24,146 --.-K/s in 0.1s 2015-03-13 21:42:07 (244 KB/s) - `WinTypes.h' saved [24146/24146] now I just need the library from D2XX, I chose the ARM one (suitable for Raspberry Pi): tingo@kg-bpi:~/dl$ wget http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.12.tar.gz --2015-03-13 21:49:03-- http://www.ftdichip.com/Drivers/D2XX/Linux/libftd2xx1.1.12.tar.gz Resolving www.ftdichip.com (www.ftdichip.com)... 212.227.193.68 Connecting to www.ftdichip.com (www.ftdichip.com)|212.227.193.68|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 950540 (928K) [application/x-tar] Saving to: `libftd2xx1.1.12.tar.gz' 100%[===========================================================================>] 950,540 2.72M/s in 0.3s 2015-03-13 21:49:04 (2.72 MB/s) - `libftd2xx1.1.12.tar.gz' saved [950540/950540] tingo@kg-bpi:~/dl$ wget http://www.ftdichip.com/Drivers/D2XX/Linux/ReadMe-linux.txt --2015-03-13 21:50:45-- http://www.ftdichip.com/Drivers/D2XX/Linux/ReadMe-linux.txt Resolving www.ftdichip.com (www.ftdichip.com)... 212.227.193.68 Connecting to www.ftdichip.com (www.ftdichip.com)|212.227.193.68|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 3101 (3.0K) [text/plain] Saving to: `ReadMe-linux.txt' 100%[===========================================================================>] 3,101 --.-K/s in 0s 2015-03-13 21:50:46 (26.9 MB/s) - `ReadMe-linux.txt' saved [3101/3101]
The ReadMe says
2015-03-13: firmware - after installing tellcore-py, I can check the firmware version of my Duo:
tingo@kg-bpi:~$ tellcore_controllers TellStick Duo name: <unnamed> serial: A6028ED8 firmware: 5 available: 1 Found 1 controller(s)
now, how do I figure out if this is the latest firmware? OK, the firmware is here: http://download.telldus.com/TellStick/Software/firmware/ it looks like firmware version 12 is the latest. There is also this thread:
"batch 13062 has a programming error that causes the upgrade to fail" Telldus fix: "1) Du behöver verktyget MProg: http://www.ftdichip.com/Support/Utilities/MProg3.5.zip 2) Se till att TelldusService är avstängt och kör sedan MProg 3) Tryck "Tools->Read and parse" 4) Under "I/O Controls" sätt C0, C1, C2 och C3 till "I/O Mode" 5) Tryck Save och sedan Device->Program 6) Koppla ur TellStick Duo och avsluta MProg Nu ska din TellStick du vara uppgraderingsbar igen."
I wonder if ftx-prog would work? Probably not, as the TellStick Duo uses a FT2xx chip.
2015-03-12: now running telldus-core 2.1.2 on a Banana Pi, running Bananian Linux:
tingo@kg-bpi:~$ cat /etc/motd ------------------------------------------------------------------------ Welcome to Bananian Linux! For news and updates check: https://www.bananian.org Any questions? Read the FAQ first: https://www.bananian.org/faq Run 'bananian-config' to set up Bananian Linux Run 'bananian-update' to check for distribution updates ------------------------------------------------------------------------ tingo@kg-bpi:~$ cat /etc/bananian_version 150101 tingo@kg-bpi:~$ cat /etc/debian_version 7.8 tingo@kg-bpi:~$ uname -a Linux kg-bpi.kg4.no 3.4.104+ #1 SMP PREEMPT Thu Jan 8 15:40:40 CET 2015 armv7l GNU/Linux
telldus-core:
tingo@kg-bpi:~$ sudo tdadmin --version tdadmin 2.1.2 devices found: tingo@kg-bpi:~$ tdtool --list Number of devices: 1 1 Example device OFF SENSORS: PROTOCOL MODEL ID TEMP HUMIDITY RAIN WIND LAST UPDATED fineoffset temperature 255 -204.7° 2015-03-12 22:39:34 fineoffset temperature 186 6.1° 2015-03-12 22:39:41 fineoffset temperature 93 2.5° 2015-03-12 22:10:53 fineoffset temperaturehumidity 22 7.0° 47% 2015-03-12 22:35:32
nice.
2014-04-09: still running telldusd from telldus-core 2.1.1, and getting lots of sensors:
tingo@kg-v2$ tellcore_tool -l Number of devices: 0 ID NAME STATE PROTOCOL MODEL PARAMETERS Number of sensors: 45 PROTOCOL MODEL ID TEMP HUMIDITY RAIN WIND LAST UPDATED fineoffset temperature 255 -204.7 C 2014-04-09 12:09:34 mandolyn temperaturehumidity 11 -22.0 C 0 % 2014-04-09 12:09:39 fineoffset temperature 186 5.6 C 2014-04-09 12:09:28 fineoffset temperature 253 -204.7 C 2014-04-09 09:46:14 fineoffset temperature 151 115.1 C 2014-04-07 14:41:24 fineoffset temperature 187 -204.7 C 2014-04-07 14:51:25 fineoffset temperature 0 0.7 C 2014-04-09 06:09:37 fineoffset temperature 233 204.7 C 2014-04-07 16:30:12 fineoffset temperature 254 -204.7 C 2014-04-07 17:31:14 fineoffset temperature 143 -204.7 C 2014-04-07 18:50:13 fineoffset temperature 1 -204.7 C 2014-04-07 18:55:28 fineoffset temperaturehumidity 22 5.9 C 71 % 2014-04-09 12:06:39 fineoffset temperature 75 -204.7 C 2014-04-09 09:52:40 fineoffset temperature 23 -204.7 C 2014-04-07 20:20:13 fineoffset temperature 44 51.1 C 2014-04-09 08:28:15 fineoffset temperature 12 -204.7 C 2014-04-07 22:49:01 fineoffset temperature 252 127.9 C 2014-04-07 23:01:25 fineoffset temperature 205 -204.7 C 2014-04-08 00:12:37 fineoffset temperature 95 -204.7 C 2014-04-08 00:30:13 fineoffset temperature 239 -204.7 C 2014-04-08 22:18:15 fineoffset temperature 35 -204.7 C 2014-04-08 02:46:13 fineoffset temperature 22 12.7 C 2014-04-08 04:40:13 fineoffset temperature 90 51.1 C 2014-04-08 05:00:13 fineoffset temperaturehumidity 6 -153.5 C 17 % 2014-04-08 06:21:26 fineoffset temperature 3 102.3 C 2014-04-08 06:22:37 fineoffset temperaturehumidity 27 204.4 C 71 % 2014-04-08 07:44:38 fineoffset temperature 175 -200.2 C 2014-04-08 10:40:38 fineoffset temperature 207 -192.8 C 2014-04-08 10:53:26 fineoffset temperaturehumidity 13 102.1 C 71 % 2014-04-08 11:22:14 fineoffset temperature 127 -204.7 C 2014-04-08 11:39:50 fineoffset temperature 29 70.3 C 2014-04-08 11:53:50 fineoffset temperature 116 12.5 C 2014-04-08 12:52:38 fineoffset temperature 20 -28.7 C 2014-04-08 13:05:02 fineoffset temperaturehumidity 239 -203.4 C 63 % 2014-04-08 13:28:38 fineoffset temperature 191 -204.7 C 2014-04-08 16:04:38 fineoffset temperaturehumidity 15 -153.6 C 0 % 2014-04-08 19:33:35 fineoffset temperature 93 2.5 C 2014-04-09 04:02:16 fineoffset temperature 25 -204.7 C 2014-04-09 04:50:16 fineoffset temperature 160 83.1 C 2014-04-09 04:50:16 fineoffset temperature 47 -180.3 C 2014-04-09 04:59:04 fineoffset temperature 79 -204.7 C 2014-04-09 05:50:16 fineoffset temperature 228 204.7 C 2014-04-09 08:15:52 fineoffset temperature 165 -131.1 C 2014-04-09 08:35:52 fineoffset temperature 223 102.3 C 2014-04-09 08:47:04 fineoffset temperature 250 -25.5 C 2014-04-09 09:11:04
Some are "don't understand this code", but still lots of sensors.
2014-04-08: telldus-core I fetch the missing file:
tingo@kg-v2$ fetch http://developer.telldus.com/export/4342bbaa1dcd90011b66e8c1540db6ba904877fe/telldus-core/Doxyfile.in Doxyfile.in 100% of 71 kB 98 kBps
and try cmake again:
tingo@kg-v2$ cmake . -- Configuring done -- Generating done -- Build files have been written to: /home/tingo/work/telldus-core-2.1.2
Ok, that worked. Next is make:
tingo@kg-v2$ make [ 1%] Building CXX object common/CMakeFiles/TelldusCommon.dir/Socket_unix.cpp.o /home/tingo/work/telldus-core-2.1.2/common/Socket_unix.cpp: In member function 'void TelldusCore::Socket::connect(const std::wstring&)': /home/tingo/work/telldus-core-2.1.2/common/Socket_unix.cpp:64: error: 'SOCK_CLOEXEC' was not declared in this scope *** Error code 1 Stop in /usr/home/tingo/work/telldus-core-2.1.2. *** Error code 1 Stop in /usr/home/tingo/work/telldus-core-2.1.2. *** Error code 1 Stop in /usr/home/tingo/work/telldus-core-2.1.2.
fail.
2014-04-07: telldus-core was updated to version 2.1.2 on April 3rd, so try to build it:
tingo@kg-v2$ pwd /home/tingo/work/telldus-core-2.1.2
trying cmake:
tingo@kg-v2$ cmake . -- The C compiler identification is GNU 4.2.1 -- The CXX compiler identification is GNU 4.2.1 -- Check for working C compiler: /usr/bin/cc -- Check for working C compiler: /usr/bin/cc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Check for working CXX compiler: /usr/bin/CC -- Check for working CXX compiler: /usr/bin/CC -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Looking for include file pthread.h -- Looking for include file pthread.h - found -- Looking for pthread_create -- Looking for pthread_create - not found -- Looking for pthread_create in pthreads -- Looking for pthread_create in pthreads - not found -- Looking for pthread_create in pthread -- Looking for pthread_create in pthread - found -- Found Threads: TRUE -- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.28") -- checking for one of the modules 'libftdi' -- Found Doxygen: /usr/local/bin/doxygen (found version "1.8.3.1") CMake Error: File /home/tingo/work/telldus-core-2.1.2/Doxyfile.in does not exist. CMake Error at CMakeLists.txt:64 (CONFIGURE_FILE): configure_file Problem configuring file -- Configuring incomplete, errors occurred!
not so great.
2014-04-07: v2 - testing telldus-core:
tingo@kg-v2$ pwd /home/tingo/work/telldus-core-2.1.1
try tdtool first:
tingo@kg-v2$ tdtool/tdtool Usage: tdtool/tdtool [ options ] Options: -[bdefhlnrv] [ --list ] [ --help ] [ --on device ] [ --off device ] [ --bell device ] [ --learn device ] [ --dimlevel level --dim device ] [ --raw input ] --list (-l short option) List currently configured devices and all discovered sensors. --help (-h short option) Shows this screen. --on device (-n short option) Turns on device. 'device' could either be an integer of the device-id, or the name of the device. Both device-id and name is outputed with the --list option --off device (-f short option) Turns off device. 'device' could either be an integer of the device-id, or the name of the device. Both device-id and name is outputed with the --list option --dim device (-d short option) Dims device. 'device' could either be an integer of the device-id, or the name of the device. Both device-id and name is outputed with the --list option Note: The dimlevel parameter must be set before using this option. --dimlevel level (-v short option) Set dim level. 'level' should an integer, 0-255. Note: This parameter must be set before using dim. --bell device (-b short option) Sends bell command to devices supporting this. 'device' could either be an integer of the device-id, or the name of the device. Both device-id and name is outputed with the --list option --learn device (-e short option) Sends a special learn command to devices supporting this. This is normaly devices of 'selflearning' type. 'device' could either be an integer of the device-id, or the name of the device. Both device-id and name is outputed with the --list option --raw input (-r short option) This command sends a raw command to TellStick. input can be either - or a filename. If input is - the data is taken from stdin, otherwise the data is taken from the supplied filename. Example to turn on an ArcTech codeswitch A1: echo 'S$k$k$k$k$k$k$k$k$k$k$k$k$k$k$k$k$k$k$kk$$kk$$kk$$}+' | tdtool --raw - Report bugs to <info.tech@telldus.se>
try it:
tingo@kg-v2$ tdtool/tdtool --list Error fetching devices: Could not connect to the Telldus Service
Ok, perhaps the daemon needs to run first:
tingo@kg-v2$ service/telldusd I doesn't look like it did anything, but /var/log/messages says: Apr 7 13:54:15 kg-v2 telldusd: Could not open pid file /var/run/telldusd.pid: Permission denied Apr 7 13:54:15 kg-v2 telldusd: telldusd daemon starting up Apr 7 13:54:15 kg-v2 telldusd: Connecting to TellStick (1781/C31) with serial A6028ED8
and the daemon is running:
root@kg-v2# pgrep -lf tel 18413 service/telldusd
re-test tdtool:
tingo@kg-v2$ tdtool/tdtool --list Number of devices: 0 SENSORS: PROTOCOL MODEL ID TEMP HUMIDITY LAST UPDATED fineoffset temperature 255 -204.7° 2014-04-07 13:57:52 mandolyn temperaturehumidity 11 -21.8° 0% 2014-04-07 13:57:27 fineoffset temperature 186 5.4° 2014-04-07 13:57:24
wow, interesting. Apparently, the value "-204.7" for the fineoffset protocol means "sensor not supported". More sensors now:
tingo@kg-v2$ tdtool/tdtool --list Number of devices: 0 SENSORS: PROTOCOL MODEL ID TEMP HUMIDITY LAST UPDATED fineoffset temperature 255 -204.7° 2014-04-07 15:01:21 mandolyn temperaturehumidity 11 -21.2° 0% 2014-04-07 15:01:27 fineoffset temperature 186 5.9° 2014-04-07 15:01:24 fineoffset temperature 253 -204.7° 2014-04-07 14:05:27 fineoffset temperature 151 115.1° 2014-04-07 14:41:24 fineoffset temperature 187 -204.7° 2014-04-07 14:51:25
Seems my neighbors also have wireless temperature sensors.
2014-04-07: v2 - connecting the TSDUO to the machine gives this in the log (/var/log/messages):
Apr 7 13:44:37 kg-v2 kernel: ugen0.3: <Telldus> at usbus0 Apr 7 13:44:37 kg-v2 root: Unknown USB device: vendor 0x1781 product 0x0c31 bus uhub0
the machine is running
tingo@kg-v2$ uname -a FreeBSD kg-v2.kg4.no 8.4-STABLE FreeBSD 8.4-STABLE #7 r256430: Sun Oct 13 19:43:35 CEST 2013 root@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC amd64
and the TSDUO blinks blue now and then.
2014-04-07: I unpacked the TellStick Duo package. It contaions the TellStick Duo, one usb cable (usb A to Mini-B), and a "quick guide" leaflet.
2014-04-03: Domoticz may have TellStick support in the future, and there is a workaround now: Domoticz considering Tellstick support.
2014-04-02: FreeBSD compile fixes for telldus-core: FreeBSD compile fixes #6.
2014-04-02: telldusd is part of telldus-core. There is evidence that telldus-core can be compiled under FreeBSD: automating your home - it easy!.
2014-04-02: OpenNetHome has support for Tellstick Duo: http://opennethome.org/hardware/install-tellstick/
2013-09-07: My local Teknikmagasinet had a TellStick Duo, and they wanted NOK 699.- for it, so I bought it.