X10 RF (motion sensors) with EventGhost?

[Flyingsubs]

This is great! The only issue is when i drag from the event log on the left it still says X10.on not the new log that is displayed with the 'A1'. Maybe I am doing something wrong? Thank you guys for your hardwork. I am glad we are all working together on this.

[Livin]

unfortunately eg does not carry over the payload. you Will need to edit the item and add the pay load info you can also copy/paste from the log and it will copy text

[Flyingsubs]

I tried that and even with copying it over, event ghost doesn't recognize the new payload. Any ideas?

Thanks
Flyingsubs

[Livin]

I tried that and even with copying it over, event ghost doesn't recognize the new payload. Any ideas?

Thanks
Flyingsubs

try using the new beta of this plugin...
viewtopic.php?f=9&t=3881&p=25364#p25364

[Flyingsubs]

ooh this could possibly work. Thank you! I'll have to try it out. I won't have time this weekend but i'll give it a try during the week!

Thank you!

[Flyingsubs]

Everything is working well with this new plugin and the eventlogging plugin. My new question is I have 2 motion sensors. One in my room and one out side my room. I want to make it so when i leave my room everything turns off and when i come back into my room, everything turns on. The problem is, if I have someone come into my room, it trips the outside sensor and it turns everything off.

I was thinking about having a timeout where if i go outside my room, i have 10 seconds to trip the inside sensor to cancel it. I can't think of away to implement that in eventghost. I tried trigger event with a timer and then another event to disable that, but it seems once an event is triggered it can't be stopped. Any ideas?

Thanks,
Flyingsubs

[piert]

I think if you use the standard Timer plugin, you could initiate a timer with an event as a result (say in 10 seconds time). You can then make another macro with a separate event and an action for the SAME timer name, but with a stop command to cancel the running timer if you want to interrupt.

[blaher]

Another way might be to trigger an event after 10 secs of say: 'lights off' that's in a separate folder. Then if the motion sensor in the bedroom gets tripped it could disable that folder, so when the event is fired it does nothing. After another few secs you could reenable the folder so that when you leave the lights go off.

[Flyingsubs]

Excellent! I think it works! Thank you

-Flyingsubs

[Chris]

I've been having trouble with the CM15a Plugin because it seems to lock up after receive the first signal from a motion sensor and will not show an event after the first one until the power is cycled. I just tried using this plugin instead and it works perfect, receives every X10 signal on my CM15a and logs each one, perfect for using with motion or door sensors etc. The only problem is this plugin does not have any of the Transmit capabilities of the CM15 module. Anyone know if its possible to merge the 2 plugins together to make a really functional one that should work for all X10 devices? Because the CM15a module work for the CM19a as well.

I'm referring to the plugin here :

viewtopic.php?f=9&t=667

Thanks

[Livin]

Hi,

This is an updated experimental version, right now I do not know how we shall handle this in general, if we need to make a separate one, if this update doesn't break anything from previous or if we just keep it as experimental for now.

This version is mapping house/units from A1-A16, B1-B16 and C1-C16. It is rather straight forward to add more house addresses (D-P), please feel free to edit the specific section accordingly.

BestR

__init__.py

I've finally been using this plugin regularly, since yesterday , and found a problem...

2013-03-18 14:06:24 pythoncom error: Python error invoking COM method.
2013-03-18 14:06:24
2013-03-18 14:06:24 Traceback (most recent call last):
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 277, in _Invoke_
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 282, in _invoke_
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 585, in _invokeex_
2013-03-18 14:06:24 File "C:\Users\ha\Documents\EventGhost\plugins\X10\__init__.py", line 258, in OnX10Command
2013-03-18 14:06:24 house_unit = HOUSE_UNITS[str(lAddress)]
2013-03-18 14:06:24 KeyError: '192'
2013-03-18 14:06:24 pythoncom error: Python error invoking COM method.
2013-03-18 14:06:24
2013-03-18 14:06:24 Traceback (most recent call last):
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 277, in _Invoke_
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 282, in _invoke_
2013-03-18 14:06:24 File "win32com\server\policy.pyc", line 585, in _invokeex_
2013-03-18 14:06:24 File "C:\Users\ha\Documents\EventGhost\plugins\X10\__init__.py", line 258, in OnX10Command
2013-03-18 14:06:24 house_unit = HOUSE_UNITS[str(lAddress)]
2013-03-18 14:06:24 KeyError: '192'

[krambriw]

I told you, I only added support for house units up until C16 (47).

You have (192) and that is not added so you get the error. I also wrote that you could easily add support for more, it is just a matter of sweat, just do it. Check the code starting at line 201 in the plugin.

BR

[Livin]

I told you, I only added support for house units up until C16 (47).

You have (192) and that is not added so you get the error. I also wrote that you could easily add support for more, it is just a matter of sweat, just do it. Check the code starting at line 201 in the plugin.

BR

Yeah, I thought that might be it so right after I posted I added all the other house codes. You just beat me to my post edit

Attached is the updated file with all the house codes. Testing now.

[krambriw]

Excellent, very nice!

Did it work with your device afterwards?

BR Walter

[Livin]

yup. works fine