Page 1 of 2

[SOLVED] Conditions Not Working For Me Either

PostPosted: Wed May 14, 2014 4:59 pm
by dman2112
I have tried evaluating conditions for trigger events but they do not work. Do conditions work in the trial versions?

Re: Conditions Not Working For Me Either

PostPosted: Thu May 15, 2014 6:41 am
by matt (support)
They do work in the trial version.

How are you evaluating the conditions? Note the Execute Actions Now button skips the conditions and just executes the actions (its purpose is to test the actions, not the conditions).

If that isn't the problem, then please provide details about exactly how you have your conditions defined and how you are testing them.

Re: Conditions Not Working For Me Either

PostPosted: Thu May 15, 2014 11:31 am
by dman2112
Yes the actions work fine with the execute now button. Sent you condition under separate email

Re: Conditions Not Working For Me Either

PostPosted: Sat May 17, 2014 9:24 pm
by dman2112
I'm assuming silence from what I sent you for 5 days means your product does not work?

Re: Conditions Not Working For Me Either

PostPosted: Sat May 17, 2014 10:17 pm
by matt (support)
Ummm, definitely not. We tried to reproduce the problem multiple times and could not, then asked you for more details. Last I heard you were going to send Event Log details but we never received them.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 8:25 am
by dman2112
Sent on the 15th. You should have received two emails. One with the screen shots and one with the event logs.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 8:38 am
by dman2112
Just regenerated and resent the event log of the trigger

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 9:22 am
by jay (support)
Your reply just arrived this morning at 9:37am. We've both attempted to recreate your issue and the condition always works for us and we've not had any reports of those not working for anyone else. We've asked for your database to see if we can use that to help us recreate the problem.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 9:43 am
by jay (support)
Before I go into too much more - how are you testing? If you're using the "Execute Actions Now" button then conditions are ignored. That button is to test the functionality in the Actions tab. To test with the condition you need to actually trigger the I/O-Linc.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 10:10 am
by ckeyes888
Maybe one for the suggestion box to have a "test with conditions" button.

Carl

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 10:16 am
by jay (support)
On the list Carl, just haven't gotten to it yet... ;)

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 10:25 am
by dman2112
Nope. I am triggering the "trigger, by operating my driveway alarm so its a real trigger condition.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 10:32 am
by dman2112
You have my database, my screen shots, and my conditions

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 10:52 am
by jay (support)
Here's my testing results with your database with step-by-step descriptions of what I did:

Database prep steps to make it works correctly in my environment:

  1. Switched my Indigo Registration to be a normal trial.
  2. Opened your database file.
  3. Defined and synced your Driveway Alarm device to an I/O-Linc I have here in my office.
  4. Disabled the Driveway Alert Trigger Off so the only trigger firing on the I/O-Linc is Driveway Alert Trigger On.
  5. Changed your action from an Execute INSTEON Scene action to a Server Actions->Log Actions->Write to Log action since I don't have your PowerLinc scene. I just have it write "Driveway Alert Trigger On Fired" to the Event Log window.

So I now have the I/O-Linc set up and the trigger configured. I didn't touch the conditions in the condition tab:

Code: Select all
   "All" "of the following rules are true"
      "If current time" "is between" "23:00:00" "and" "05:30:00"


I then closed/opened/closed/opened the I/O-Linc's sensor by shorting two wires I have attached to the inputs. This is the event log from that:

Code: Select all
May 18, 2014, 11:31:10 AM
  Received INSTEON                "Driveway Alarm" off
  Received INSTEON                "Driveway Alarm" on
  Received INSTEON                "Driveway Alarm" off
  Received INSTEON                "Driveway Alarm" on


The trigger did not fire because it was outside of the time range. I then changed my Mac's clock to be pm rather than am, which should fire because it's within your time frame. Here's the event log from that:

Code: Select all
May 18, 2014, 11:34:14 PM
  Received INSTEON                "Driveway Alarm" off
  Trigger                         Driveway Alert Trigger On
  Action Collection               Driveway Alert Trigger On Fired
  Received INSTEON                "Driveway Alarm" on
  Received INSTEON                "Driveway Alarm" off
  Trigger                         Driveway Alert Trigger On
  Action Collection               Driveway Alert Trigger On Fired
  Received INSTEON                "Driveway Alarm" on


As you can see, the trigger fired as it was supposed to. Next, I changed the time to 5am instead:

Code: Select all
May 18, 2014, 5:00:58 AM
  Received INSTEON                "Driveway Alarm" off
  Trigger                         Driveway Alert Trigger On
  Action Collection               Driveway Alert Trigger On Fired
  Received INSTEON                "Driveway Alarm" on
  Received INSTEON                "Driveway Alarm" off
  Trigger                         Driveway Alert Trigger On
  Action Collection               Driveway Alert Trigger On Fired
  Received INSTEON                "Driveway Alarm" on


Again, they fired appropriately. I then changed the time to 6am:

Code: Select all
May 18, 2014, 6:01:00 AM
  Received INSTEON                "Driveway Alarm" off
  Received INSTEON                "Driveway Alarm" on
  Received INSTEON                "Driveway Alarm" off
  Received INSTEON                "Driveway Alarm" on


This time the log write didn't fire. Which it shouldn't have because it's outside the time range.

So, bottom line, I can't reproduce your problem given your database, so I can't explain why it isn't working for you. We've also had no other reports of time ranges not working, and in fact I have a lot of them in my production database so I would definitely see if they aren't working. Using a trial makes no difference since there's nothing in the trial that limits conditions.

Re: Conditions Not Working For Me Either

PostPosted: Sun May 18, 2014 11:39 am
by dman2112
Jay,

Thanks for the testing, but I have fixed the problem. Your testing does not reproduce the issue as you are using Action groups and not scenes. In my scenario, my "action" was an Insteon Scene. This causes the links to be written to the devices. In this case Indigo "broke" the condition as the "on" and "off" manipulation of the scene was written to the individual devices, not controlled by the server. From that point forward, any time the I/O controller would get a sensor inout close, the Powerlink, acting as a controller, would execute the scene (it has not direct knowledge of the condition).

I discovered this by completely deleting the triggers altogether and then manipulating the driveway alarm. The scene was still firing!!!!

My fix was this:

Delete the links between the Powerinc I/O and the switches.

Change the Indigo "Action" to individual device On commands and allow the Auto off feature to turn them off after 5 min...negating the need for a corresponding "Off" trigger.

Once I did this the Indigo serve wa now in control of everything and the condition works fine. Just a note if I were to recreate the old trigger using scenes it would break the condition of itself as it would re-sync the links to the devices.

Thanks for your time.