Help with Conditional events

neutron · #1 November 20th, 2009, 05:52 PM

I am having trouble using conditional events, I have a sensor hooked up to my GC100 that senses if the satelite receiver is powered on or off, then if I want to turn on the power for the receiver I first need to check that the receiver is off using that sensor, and if it is off send the power ir signal, if it's already on it shouldn't do anything.

When I check the GC100 Log, as the receiver goes on and off the device Bell Power Sensor gets set to 1 and 0, and the device shows on or off accordingly.

I have setup 2 manually triggered with conditions events (Sat Off and Sat On) that when trigered runs the events Bell Power Off or Bell Power On which check to see the status of the sensor then depending on the status will send the Power IR command.

I have attached a screenshot of the events, when I run the events The log says "Delayed event execution skipped, the conditions applied were not met: testing:Bell Power On" (or Off)

I don't see where I'm going wrong here, can somebody please help?

Thanks!!!!

Uncle Michael · #2 November 20th, 2009, 08:13 PM

I think you may have the conditions reversed.

neutron · #3 November 20th, 2009, 08:20 PM

Actually the sensor on the GC100 is reversed, it shows off when the device is on, and on when the device is off, sorry I should have mentioned that. (and I tried it both ways just to make sure too

)

Uncle Michael · #4 November 20th, 2009, 11:02 PM

I don't see any delayed actions, so I'm having trouble interpreting the error message. Am I missing something else?

Uncle Michael · #5 November 20th, 2009, 11:06 PM

Two more questions. You indicated values of 0 and 1. Those are not standard On and Off values in X10 land. Could it be that the test needs to be run on device value? Or does it need to test the actual value of the status integer?

neutron · #6 November 21st, 2009, 10:19 AM

Well, in the GC100 log it switches the value between 1 and 0, The only options it gives me for that device is `On `Off or and `Any Value, there isn't anything else I can select.

Uncle Michael · #7 November 21st, 2009, 10:51 AM

Quote:

Originally Posted by neutron

Well, in the GC100 log it switches the value between 1 and 0, The only options it gives me for that device is `On `Off or and `Any Value, there isn't anything else I can select.

I'm not following you here. When you enter the condition of the power sensor on the IR event trigger, you should be presented with a drop down box. One of the selections should be 'Value equals'.

neutron · #8 November 21st, 2009, 02:23 PM

The Device Condition for the GC100 Sensor gives me the following options:

Is or Has Been Status: Condition:

~On Currently
~Off For At Least
~Any Value For Exactly

Then I can specify a time

There is no value equals.

From your other post (which appears to have been deleted) I did manage to make a virtual device go on or off with the change of the power sensor, but I'm still haveing trouble sending an event using that condition as well.

Scott

neutron · #9 November 21st, 2009, 02:23 PM

This should show what I tied with the virtual device

Uncle Michael · #10 November 21st, 2009, 06:29 PM

I think your attachment got lost.

Just to be sure we're on the same page, I've attached a screen shot from the setup screen of a Manual with Conditions event, that illustrates the value equals condition. If I understand correctly, when you try to do this with your two events that send IR, you do not get this option. Is that correct?

neutron · #11 November 21st, 2009, 09:21 PM

If I use the virtual device that now get's switched automatically when the real GC100 sensor switches I get that, if I use the actuall GC100 Sensor Device I don't get that.

I think the trouble now is running the manual with conditions event, I remember reading about an option that needs to be selected to actually check the conditions, I think I just need to find that again.

I won't be working on this again till Monday (it's at the office) and my brain was starting to hurt on it when I was working on it earlier....

I will go over it again on Monday and let you know how it goes.

Thanks for your help so far....

Uncle Michael · #12 November 21st, 2009, 10:08 PM

Good plan. A break is usually good.

I deleted my earlier post because I realized I was jumping to a conclusion with too little information. I can repeat it if it would help. But, I think you are definitely on the right track about enabling conditions on a manual event. That may make all of my ideas moot.

It looks like a plug-in is controlling the options you are getting. Does your power monitor interface to HS through a plug-in?

neutron · #13 November 22nd, 2009, 11:54 AM

The sensor is through the GC100 plugin, using the post you deleted, I made a virtual device that go set to on or off when the GC100 sensor changes status. Now I have to go back and figure out how to make a manual with conditions or a conditional event that checks the status of the virtual device. I did it before using the GC100 device and it didn't work, I'm thinking that using the virtual device status it should work now since that is giving me real on / off status whre the GC100 device wasn't.

Uncle Michael · #14 November 22nd, 2009, 05:07 PM

How is support on the GC forum? Have you raised the question there? I am puzzled that you cannot use the device state as a condition. Either there is a bug, or there's a step required you haven't discovered yet.