Tellstick - modified

[krambriw]

Hi,

While waiting for an official release from Telldus, I have modified the original version to support the new Telldus Core library. This is installed when you install the Telldus Center

The advantage to use this one is that the old bug that caused error messages after 30-40 transmissions is gone (as far as I have been able to test)

To install:

Unzip the content to a new folder \plugins\TS2 (in this way you keep the original one in parallel

Restart EG and add plugin, you shall see the TS2 listed. It behaves like the original one from functionality point of view


Best regards, Walter

PS This plugin requires that you have installed Telldus Center


Latest version always here:

TS2_26052010.zip

2010-05-26 Introduced transmission retries

(40.05 KiB) Downloaded 157 times

Previous version here:

TS2_0.4.0.zip

(39.97 KiB) Downloaded 130 times

[krambriw]

EventGhost 0.4.0 update

I have updated the plugin with the mandatory GUID entry

[zeeke]

Do you know if this is working better with Waveman products?

[krambriw]

With Waveman, I have no idea, sorry for that.

The plugin requires that the Telldus Center is installed. In this case you will get the latest stuff from Telldus installed and if there are any improvements in respect to Waveman, they would be there in the TelldusCore I believe

The Waveman support by Telldus/Tellstick can be tested without EG

The EG plugin itself is fully independent from brand & type of devices (Nexa, Waveman, etc) and uses only already defined devices in Telldus Center

Best regards, Walter

[jaaahaaa]

I tried using thisone instead of the original tellstick plugin to send:
eg.plugins.TellStick.Dim(, )

Still doesn't work. Is this the correct command line using this plugin, tried
eg.plugins.TS2.Dim(, )

as well but didn't work at all. Getting the same error "Could not send" something using the first line

[krambriw]

The python script below works for me. I have Telldus Center 2.0 installed and I'm using TS2 plugin instead of the original one.
I have uploaded an updated plugin you can try

Code: Select all

a = 6
b = 150
eg.plugins.TellStick.Dim(a, b)

[krambriw]

Just another thing to think of: Do not run Telldus Center and EG at the same time. If your priimary use is EG, only start Telldus Center for configuration changes (but close EG first).
Try this out if you have problems, maybe it works in your setup as expected but I have a conflict between the two (this is not EG's fault however)

Best regards, Walter

[mickelin]

Walter,
Will you be adding support for the new TellStick Duo, which can send AND receive? It would be great to be able to receive e.g. Nexa IR detector events. (I use your NetHomeServer plugin and a home built receiver now, but the Duo would be a simpler solution.)

In fact, while you're at it, would it be possible to add support for a generic send function? It would be really cool to send Pronto Hex codes with the Tellstick, allowing RF control of not just switches, but all A/V equipment, with a RF/IR pyramid at the other end.

Cheers,
Micke

[krambriw]

Hi,
There is a new plugin for the Duo already published at Telldus site (beta section of the forum) and I will also publish it here as soon as the Duo is available

Everything you need to control (send to) must be configured in the Telldus center. For receiving, defined devices are recognized as well as undefined

generic send function

I would very much like to add support for this as well as for sending pronto codes but neither the Tellstick nor the Duo supports this at the moment. And it might not be so easy, to support pronto codes they would also need to add a carrier frequency, typically 38kHz, that they are missing today. Hopefully this is just new firmware but it could also be HW related. If you have a pyramid set, you can clearly see the difference with an oscilloscope when you use a standard IR remote and compare with the Tellstick (or a RF remote) what comes out from the second pyramid


Best regards, Walter

[mickelin]

Found the plugin, excellent! I knew I could count on you!

Yeah, I suspected the hardware might be a limiting factor for more sophisticated signaling. Maybe I'll use an iTach instead for that part.

Cheers,
Micke