Easy Trigger plug-in - Beta Testing

[TechHA]

what about the trigger called "This device had its value set and is greater than" ?

Doesn't work in this situation, the value wasn't just set, nor do I want to trigger on value change. This is a manually triggered event I only want to execute if the value is greater than XX.

[randy]

Doesn't work in this situation, the value wasn't just set, nor do I want to trigger on value change. This is a manually triggered event I only want to execute if the value is greater than XX.

The condition "This Device had its value set and is greater than..." will work. Despite the clumsy wording, a condition never looks for a value to have changed or to be set, the more correct wording for the condition would be "If xx has a value that is greater than yy" which is how it reads when you set up the condition.

[TechHA]

The condition "This Device had its value set and is greater than..." will work. Despite the clumsy wording, a condition never looks for a value to have changed or to be set, the more correct wording for the condition would be "If xx has a value that is greater than yy" which is how it reads when you set up the condition.

Maybe I have something setup wrong but this doesn't work for me. No matter what the value is the IR get's sent.

The first pic below is my event, i use a button in HSTouch to activate it.

The second pic is the Heater in the off state. Disregard the On light bulb, that's for the Aeotec switch not the actual infrared heater.

The Third pic is the heater in the off state but with the fan still running.

Finally the fourth pic in the heater on.

[spud]

Maybe I have something setup wrong but this doesn't work for me. No matter what the value is the IR get's sent.

The first pic below is my event, i use a button in HSTouch to activate it.

The second pic is the Heater in the off state. Disregard the On light bulb, that's for the Aeotec switch not the actual infrared heater.

The Third pic is the heater in the off state but with the fan still running.

Finally the fourth pic in the heater on.

I don't know how it works from HSTouch, but when you try run an event from another event, the conditions are not honored unless you tick the "Run only if other conditions are true", so it is likely to behave the same from HSTouch.

[randy]

I don't know how it works from HSTouch, but when you try run an event from another event, the conditions are not honored unless you tick the "Run only if other conditions are true", so it is likely to behave the same from HSTouch.

That is correct in HSTouch as well. There is an easy workaround. Run a manually triggered event from HSTouch. The manually triggered event calls the event you showed above and the advanced option "Run only if other event options are true" is selected. if I run "test" from HSTouch, the light will only come on at night. If I run "test1" it will come on regardless of the time.

[randy]

This goes back to my obsession that HomeSeer should observe conditions in a manually triggered event by default, whether called from another event or run from HSTouch. It would eliminate a ton of confusion. You should have the option to "Ignore conditions in other event", but the default behavior should treat a manual trigger the same as any other trigger. Taken one step further, I would ignore the trigger but observe the conditions in any event that is called from another event, because observing the trigger would prevent the event from running in 99%+ of the cases. If I had an event that triggers at 8:00 PM and checks that the all of my outside doors are closed and speaks a warning if any are not, it would be nice to be able to call that event from another event , ignoring the trigger but observing the conditions.

I fully understand the logic that triggers and conditions are ignored when an event is manually run from the Event Management page.

[TechHA]

That is correct in HSTouch as well. There is an easy workaround. Run a manually triggered event from HSTouch. The manually triggered event calls the event you showed above and the advanced option "Run only if other event options are true" is selected. if I run "test" from HSTouch, the light will only come on at night. If I run "test1" it will come on regardless of the time.

That worked! You guys are awesome, I would have NEVER of figured that one out! Thank you very much!

[S-F]

@ Spud,

Could you add a condition for a plugin being active or not? I ask because I have some events which fire up a remote Kinect instance and I don't want them to run if the remote instance is already connected.

[spud]

@ Spud,

Could you add a condition for a plugin being active or not? I ask because I have some events which fire up a remote Kinect instance and I don't want them to run if the remote instance is already connected.

yes I can, it will be in the next version

[ewkearns]

one thing I could add is to to let you enter global variables value for each time range, for example you would set intensity=X with different values for each time range. Then in the event you would use the trigger "The time enters this schedule time range" and in the action you would set your light or thermostat device to the value set in the intensity global variable.

How does it sound? is it something you would use?

Note that you would still need a small script for the event action to set the device value, because I don't think there is any HS action capable of setting a device value using a global variable.

I might have to play with that a bit.... but I think I could get it to work....

[spud]

@ Spud,

Could you add a condition for a plugin being active or not? I ask because I have some events which fire up a remote Kinect instance and I don't want them to run if the remote instance is already connected.

done in version 3.0.0.3 attached to first post of this thread.

the new conditions are:

"This plugin IS running"
"This plugin IS NOT running"

then you provide the name and instance of the plugin you want to check

[Automated]

Please add actions to set a devices value to the value of either a replacement variable, global variable, or other device's value, as it doesn't seem like Rich will add that in the built in actions.







Hurry up, so we can throw our money at it.

[S-F]

done in version 3.0.0.3 attached to first post of this thread.

the new conditions are:

"This plugin IS running"
"This plugin IS NOT running"

then you provide the name and instance of the plugin you want to check

Thank You!


EDIT:

Works like a dream!

[spud]

Please add actions to set a devices value to the value of either a replacement variable, global variable, or other device's value, as it doesn't seem like Rich will add that in the built in actions.

Hurry up, so we can throw our money at it.

in version 3.0.0.4 (attached to first post of this thread) I have added an action to set a device value to any replacement variable: this can be a global variable, another device value, a counter, basically anything that is in this list and has a numerical value

set device value to a global variable:


set device value to another device value:

[kideon]

How about a trigger for if a device has changed in a specified amount of time, if it was one value and became another value and if it has been a value in a certain amount of time.