More Devices, Firmware

[AmazingHorst]

Hi,

I recently bought a TellStick Duo and found out that my electric shutters were not support by the device. No surprise there, as it wasn't listed in the compatibility list anyway. So I took an oscilloscope and figured out what my remotes were sending to the shutters, then I translated it to a string that I could feed to tdtool.
That worked great, so I built the tools for OpenWRT, extended the web interface a bit and now i have a control panel on the access point to control my shutters.

Is there any way I can give you guys the information so you can build support for these devices in telldus center?
I haven't figured out the entire protocol, but I have three remotes and two shutters, so in my captures it is quite obvious which part of the code is a serial number of the remote, controlled by dip switches and which part is the actual function (on/off/stop).
Also it would be nice if I could get the source code for the TellStick Duo firmware for further hacking.
On a related note: Is there a way to open the device without destroying its case?

[micke.prag]

Is there any way I can give you guys the information so you can build support for these devices in telldus center?

Yes, we would like that information. To implement a new protocol it is enough to extend the software in the computer.
You will see some Protocol* files here:
http://developer.telldus.com/browser/te ... re/service

Also it would be nice if I could get the source code for the TellStick Duo firmware for further hacking.

We have not yet opened the complete firmware for TellStick Duo. The RF-protocol part is acctually the same as in TellStick Net. You can find the source here: http://developer.telldus.com/browser/TellStick%20Net/

On a related note: Is there a way to open the device without destroying its case?

Unfortunately not. The case is welded together.

[AmazingHorst]

Is there any way I can give you guys the information so you can build support for these devices in telldus center?

Yes, we would like that information. To implement a new protocol it is enough to extend the software in the computer.
You will see some Protocol* files here:
http://developer.telldus.com/browser/te ... re/service

Yeah I already saw the source code for the service, but since I just got it working a couple of days ago I wasn't quite ready to start hacking it just yet.
Nevertheless I can give you all the information on the remotes I have right now:
I have three remotes, two hand held ones and a wall mounted remote.
One of the hand held remotes can be seen here
It has three buttons for up, stop and down. The remotes are not configurable in any way and appear to have (somewhat) unique codes that need to be learned by the receiver.
For my first remote I use these strings:
Up:

Code: Select all

echo 'S$$D$DD$$D$D$D$DD$$D$DD$D$$D$DD$D$D$D$+' | tdtool --raw -

Stop:

Code: Select all

echo 'S$$D$DD$$D$D$D$DD$$D$DD$D$$D$DD$D$$DD$+' | tdtool --raw -

Down:

Code: Select all

echo 'S$$D$DD$$D$D$D$DD$$D$DD$D$$D$DD$$D$D$D+' | tdtool --raw -

For the second remote:
Up:

Code: Select all

echo 'S$$DD$$D$D$D$D$D$DD$$DD$D$D$$DD$D$D$D$+' | tdtool --raw -

Stop:

Code: Select all

echo 'S$$DD$$D$D$D$D$D$DD$$DD$D$D$$DD$D$$DD$+' | tdtool --raw -

Down:

Code: Select all

echo 'S$$DD$$D$D$D$D$D$DD$$DD$D$D$$DD$$D$D$D+' | tdtool --raw -

As you can see here the last 6 characters seem to control the function, the rest is unique per device or serves some kind of other function.
The codes do not change when pressing buttons on the remote multiple times. Also the remote sends each sequence about 10 times, although I found that sending the sequence once with the TellStick is sufficient.

The wall mounted remote only has two buttons: up and down. Other than that it doesn't seem to have a unique code but it is configurable by 12 dip switches, as you can see in the picture. I did not fiddle with the switches at this point, but the pattern on the dip-switches roughly corresponds to the pattern in the sequence I send out. So here's the picture:


The codes I use for this remote are:
Up:

Code: Select all

echo 'S$$DD$$DD$$DD$$DD$$DD$D$$D+' | tdtool --raw -

Down:

Code: Select all

echo 'S$$DD$$DD$$DD$$DD$$DD$$DD$+' | tdtool --raw -

Here the last 4 characters seem to be the function and each pair of preceding characters is probably the same as the setting of the dip switches.

Also it would be nice if I could get the source code for the TellStick Duo firmware for further hacking.

We have not yet opened the complete firmware for TellStick Duo. The RF-protocol part is acctually the same as in TellStick Net. You can find the source here: http://developer.telldus.com/browser/TellStick%20Net/.

Thanks for the link. I already saw this link in your blog somewhere, but I wasn't sure if the RF part is really the same in TellStick Net and Duo.
I wanted to fiddle with the firmware because my TellStick's LEDs don't light up when I press a button on the remote for my shutters, leading me to believe that firmware hacking is necessary to support receiving signals from these remotes. The LEDs do light up when I press a button on my Intertechno remote for some switches I have here.

I don't know if the information here is really useful to you guys, but I'd like to take the opportunity to thank you for your great product and your openness.

[micke.prag]

On the remote, there is an IC just left of the buttons. What is written on that?

I wanted to fiddle with the firmware because my TellStick's LEDs don't light up when I press a button on the remote for my shutters, leading me to believe that firmware hacking is necessary to support receiving signals from these remotes.

You are correct. In order to receive signals the firmware needs updating as well.

[AmazingHorst]

On the remote, there is an IC just left of the buttons. What is written on that?

On the hand held remote:

Code: Select all

PIC16F630
-1/SL
072851C

On the wall mounted remote:

Code: Select all

PIC16F628A
-1/SO
07222WA