TellStick Duo

[krambriw]

Is a good point, I haven't yet added support for projector screens, I'll look into that. Now when the new firmware is released I think I'll look into adding better support for sensors as well

BestR Walter

[krambriw]

New version uploaded in the first post. The UP/DOWN/STOP commands looks like they are sent ok from Telldus and the callbacks are coming in to EG as well (when I use Telldus Center) but I do not have a roxcore. Can you try how this works for you?

Best regards, Walter

[MrNilsson]

Dear Walter!

Thank you for your quick reply. I will try this as soon as I get home... crossing fingers!

[MrNilsson]

IT'S ALIVE!!!

:}

It works splendid!

Althought I get these following logs all the time in my eventghost log...

Starting TellStick Duo...
TellStickDuo.RawEvent: class:sensor;protocol:fineoffset;model:temperaturehumidity;temp:-0.1;humidity:0xFF;id:0x84;Duo_ID:3
TellStickDuo.fineoffset.temperaturehumidity.132.Temperature: '-0.1|2012-01-24 19:21:01'
TellStickDuo.fineoffset.temperaturehumidity.132.Humidity: '255|2012-01-24 19:21:01'
TellStickDuo.fineoffset.temperaturehumidity.132.Temperature: '-0.1|2012-01-24 19:21:49'
TellStickDuo.fineoffset.temperaturehumidity.132.Humidity: '255|2012-01-24 19:21:49'
TellStickDuo.fineoffset.temperaturehumidity.132.Temperature: '-0.1|2012-01-24 19:22:37'
TellStickDuo.fineoffset.temperaturehumidity.132.Humidity: '255|2012-01-24 19:22:37'
TellStickDuo.fineoffset.temperaturehumidity.132.Temperature: '-0.1|2012-01-24 19:23:25'
TellStickDuo.fineoffset.temperaturehumidity.132.Humidity: '255|2012-01-24 19:23:25'

(Don't have any temp sensor.) ;/

Thank you for your AWESOME work Walther!

[krambriw]

Althought I get these following logs all the time in my eventghost log...

Something is picked up from the air....it's anyway all down to the internal decoding done by the Duo itself, nothing that can be done in EG at this stage.

My log is not much prettier, multiple copies are generated:

Code: Select all

22:17:24   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=9,
22:17:24   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=8,
22:17:24   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=10,
22:17:24   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:10;group:0;method:turnoff;Duo_ID:3
22:17:25   Main.NHS|In|NexaL.Address|4539058|NexaL.Button|10|NexaL.Command|0|
22:17:26   Main.NHS|In|NexaL.Address|4539058|NexaL.Button|9|NexaL.Command|0|
22:17:26   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:27   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:10779;unit:1;method:learn;Duo_ID:3
22:17:27   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:11;group:0;method:turnoff;Duo_ID:3
22:17:27   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:27   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=9,
22:17:27   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=8,
22:17:27   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=10,
22:17:28   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:10;group:0;method:turnoff;Duo_ID:3
22:17:28   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:9;group:0;method:turnoff;Duo_ID:3
22:17:29   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:9;group:0;method:turnoff;Duo_ID:3
22:17:30   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:30   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:11;group:0;method:turnoff;Duo_ID:3
22:17:30   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:30   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:11;group:0;method:turnoff;Duo_ID:3
22:17:30   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:30   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=9,
22:17:30   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=8,
22:17:31   RFXcom.xpl-trig:homeeasy.confirm:mal-rfxcom.cdiyyy:*:command=off,address=0x004542b2,unit=10,
22:17:31   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:10;group:0;method:turnoff;Duo_ID:3
22:17:31   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:10;group:0;method:turnoff;Duo_ID:3
22:17:32   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:9;group:0;method:turnoff;Duo_ID:3
22:17:33   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3
22:17:33   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:10779;unit:1;method:learn;Duo_ID:3
22:17:33   TellStickDuo.RawEvent: class:command;protocol:arctech;model:selflearning;house:4539058;unit:11;group:0;method:turnoff;Duo_ID:3
22:17:33   TellStickDuo.RawEvent: class:command;protocol:everflourish;model:selflearning;house:5163;unit:1;method:learn;Duo_ID:3

I think I have to disable the rawevents

Best regards, Walter

[krambriw]

Just noticed that there was a small problem when I tried to disable raw events

# 2012-01-25 Checkboxes for selection of event types did not work correctly

Updated version in the first post

Best regards, Walter

[krambriw]

New version in first post

I have made a little change that since long has irritated me a bit. When changing the dim level, the macro name was not updated accordingly. Now it is

Best regards, Walter

[spidersprog]

Hi before I buy a duo I wanted to know if the following is possible, otherwise I'll buy a regular tellstick
I basically want to use a home easy light switch and have it generate an event in EG so I can use the switch to trigger macros, such as all lights and sockets in a certain room off or on. is this possible with a duo?

I want EG to handle the commands when it receives the signal rather than directly pairing the switch with the other modules

[krambriw]

Hi, simple answer is yes.

This is exactly the purpose with the plugin, to allow any kind of (EventGhost) event to control devices via macros.
When the duo receives the signals from your light switches, the plugin will generate events. Those can be dragged to trigger macros. Inside the macros you put actions that will execute the control.

Best regards, Walter

[spidersprog]

Great! now all I need to do is find a UK supplier, any ideas?

[krambriw]

If you mean finding a Duo right now, it is very hard, I think they are short of supply due to factory issues.

You may consider this one, the RFXtrx433:
http://www.rfxcom.com/transceivers.htm#12103


I hope that I can have a plugin for this device ready soon (no promises on dates)

Best regards, Walter

[krambriw]

I have added some new actions to the plugin to allow you to control dimming of lamps in steps during a configurable snooze time. It is getting popular with so called wake-up lamps and here is a variant you could use (I call them Good Morning and Good Night).

It works like this:

You define the lamp control action and set a snooze time. Then when the action is triggered it will automatically dim the lamp in delayed steps during the snooze time (the action calculates the number of steps and each dim level required to cover the snooze time). The action can be triggered by any type of event when it is put into a macro.

[Mossberg]

I am experiencing some problems with the plugin, or at least i expect it's the plugin.
The problem accurs when i've pushed my wall transmitter (wst-512) a feew times, then eventghost just stops reciving events. It's like the plugin is no more
Works like two or three times.

I don't know if it's anyting i'm doing wrong or if it's a bug.

Thanks for a nice plugin otherwise!

[cozmo]

I can't get this plugin to work properly.

When I add the plugin and adjust the "delay between events" so that I only receive one event, things seem fine when i test-trigger some of my sensors. Only one event shows in the log.

But as soon as I add macros and "listeners" for the events that are generated by triggering the sensors - I suddenly get like 5 events in the log, and subsequently the macros are executed the same number of times...

Am I missing something here? It's almost like adding macros with events disables the entire "delay between events"-setting....

[Pallantir]

Are there any possibilities this will be expanded to Tellstick.Net? I need something that can be contacted remotely, but I'm a little bit hesitant to use the .Net since that will be at the mercy of a company. Few companies lives forever, and corporate priorities change. So I don't think I can be absolutely sure that the online system for the Tellstick.Net will be there forever. Which means that a plan B would be very nice to have.