Originally posted by SteveMSJ
View Post
Announcement
Collapse
No announcement yet.
Easy Trigger plug-in - Feature Requests
Collapse
This is a sticky topic.
X
X
-
Originally posted by SteveMSJ View PostSpud,
Thanks for a great plugin which I keep finding more uses for.
I can call the plugin functions GetSchedule and SetSchedule fine from a script but I would like to create a new schedule. Is it possible for SetSchedule to create a new schedule if the schedule name doesn't already exist? Alternatively expose another function to create a new schedule?
Thanks,
Steve
Comment
-
Originally posted by spud View Postdone in version 3.0.0.33 available in the BETA section of the updater, now the SetSchedule function will create the schedule if it doesn't exist already.Originally posted by SteveMSJ View PostThanks, I wii give it a try tomorrow.
Steve
Steve
Comment
-
Spud,
Would you be able to add these:
<event> was just ran
This Event was triggered by <event>
... good for basic sequences
<event> was last triggered manually/directly
... good to determine if it was automation logic, or human intervention. For instance, if it was human intervention, you may want to leave the lights on, not
Device value is set and NOT Equal to <value> for at least <time>
Device value Just changed based on; <keyword> and/or Location and/or Name
Time is NOT <between or after or before>
example use cases:
a. Trigger an event based on anything happening within a room or location, with 1 single IF... instead of multiples
b. Currently I trigger a script and the event requires over 20 IFs where all devices the same <keyword> in the Name (Window)... if you add this to Easy Trigger, I would be able to replace 20 IFs with 1 IF.
Similarly, there are many cases where the negative (NOT IF) is needed. Can you add new 'qualifiers'?
We need qualifiers that allow EXCEPTIONS (aka NOT IF) - in some cases without Exceptions in the event, some things are just not possible in the Event engine and when a work-around is possible it requires logic to be verbose and tedious, and in many cases redundant across multiple events
The below would Massively enhance the capabilities, IMO
NOT IF <event> was last triggered manually, not from an event
NOT IF <vDevice> was last triggered manually, not from an event
... currently a painful and only partial workaround is to create a separate Event which the first Event calls, where the 2nd Event includes exceptions in the form of more Conditions that further narrow the scope of the IF's. Completely inadequate and does not cover most situations that a NOT IF would easily handle within a single Event.
Comment
-
One thing I would like to see is the ability to use the delayed device action in HS3 when controlling a device using EasyTrigger..
I am setting a device value to a global variable but the normal HS3 delayed device option does not appear. I am having to use a Wait statement which I'd prefer not to use.
Comment
-
Originally posted by andyf View PostOne thing I would like to see is the ability to use the delayed device action in HS3 when controlling a device using EasyTrigger..
I am setting a device value to a global variable but the normal HS3 delayed device option does not appear. I am having to use a Wait statement which I'd prefer not to use.
Comment
-
Originally posted by teladog01 View PostI'll add a +1 to this request, as I've encountered this situation several times where I've wanted to use a delayed device action and had to use a Wait action instead.
If so, is there any difference between this option and adding a wait action before the control device action?
Comment
-
Originally posted by spud View PostAre you talking about the "After Waiting X days Y hours..." option there is at the bottom of the "Control Device" action?
If so, is there any difference between this option and adding a wait action before the control device action?
Comment
-
Originally posted by spud View PostAre you talking about the "After Waiting X days Y hours..." option there is at the bottom of the "Control Device" action?
If so, is there any difference between this option and adding a wait action before the control device action?
It may be a plug-in doesn't have access to this but if it does I would really like to see this implemented.
This is a really great general use must have plug-in. Every couple of days I find events in my system that I realize I can make much simpler using an EasyTrigger feature.
Comment
-
Originally posted by spud View PostAre you talking about the "After Waiting X days Y hours..." option there is at the bottom of the "Control Device" action?
If so, is there any difference between this option and adding a wait action before the control device action?
A delayed device action is always preferable to a Wait.HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon
Comment
-
Thoughts?
Originally posted by Ltek View PostSpud,
Would you be able to add these:
<event> was just ran
This Event was triggered by <event>
... good for basic sequences
<event> was last triggered manually/directly
... good to determine if it was automation logic, or human intervention. For instance, if it was human intervention, you may want to leave the lights on, not
Device value is set and NOT Equal to <value> for at least <time>
Device value Just changed based on; <keyword> and/or Location and/or Name
Time is NOT <between or after or before>
example use cases:
a. Trigger an event based on anything happening within a room or location, with 1 single IF... instead of multiples
b. Currently I trigger a script and the event requires over 20 IFs where all devices the same <keyword> in the Name (Window)... if you add this to Easy Trigger, I would be able to replace 20 IFs with 1 IF.
Similarly, there are many cases where the negative (NOT IF) is needed. Can you add new 'qualifiers'?
We need qualifiers that allow EXCEPTIONS (aka NOT IF) - in some cases without Exceptions in the event, some things are just not possible in the Event engine and when a work-around is possible it requires logic to be verbose and tedious, and in many cases redundant across multiple events
The below would Massively enhance the capabilities, IMO
NOT IF <event> was last triggered manually, not from an event
NOT IF <vDevice> was last triggered manually, not from an event
... currently a painful and only partial workaround is to create a separate Event which the first Event calls, where the 2nd Event includes exceptions in the form of more Conditions that further narrow the scope of the IF's. Completely inadequate and does not cover most situations that a NOT IF would easily handle within a single Event.
Comment
-
Originally posted by andyf View PostYes, that's the one. Same reason, a Wait hangs up the thread rather than just scheduling a future device action and continuing. I did read in one of the how to's or clinics that it really wasn't recommended to use Wait.
It may be a plug-in doesn't have access to this but if it does I would really like to see this implemented.
This is a really great general use must have plug-in. Every couple of days I find events in my system that I realize I can make much simpler using an EasyTrigger feature.
Comment
-
Originally posted by Ltek View Post
<event> was just ran
This Event was triggered by <event>
... good for basic sequences
<event> was last triggered manually/directly
... good to determine if it was automation logic, or human intervention. For instance, if it was human intervention, you may want to leave the lights on, not
Originally posted by Ltek View PostDevice value is set and NOT Equal to <value> for at least <time>
Originally posted by Ltek View PostDevice value Just changed based on; <keyword> and/or Location and/or Name
Originally posted by Ltek View PostTime is NOT <between or after or before>
Time is NOT after = Time is before
Comment
Comment