Announcement

Collapse
No announcement yet.

Easy Trigger plug-in - Feature Requests

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • kideon
    replied
    Originally posted by rprade View Post
    It will send to every device in succession, it does not check the status of the devices. It takes 25 seconds, but what do I care - I'm in bed and going to sleep. I launch the group control at the beginning of the event, just after the Occupancy mode is set to "Home Asleep". My bedroom lights are in a separate action with a 15 second delay. The flow is this:
    • Doors and windows are checked to make sure they are closed
    • Doors are checked that they are locked
    • Occupancy is put in Home Asleep mode - This changes the power and lighting modes as well
    • Any lights that are dimmable and controlled by my default levels are immediately reduced to sleep levels, this includes the master bedroom lights. This is done by Events that look for the Occupancy Mode Device to change to Home Asleep
    • The Easy Trigger group action is launched after a 5 second wait to allow time for all of the dimming actions to take place.
    • The bedroom lights are turned off after a 10 second wait
    This method will reduce the levels for any dimmable lights that are still on in the house, giving a visual cue to anyone elsewhere in the house. It also dims the bedroom lights for about 10 seconds before they go off. You can see the flow by last night's log entries, note that I do not log device controls, but you can see the Events. The "Sleep Finisher" event is what initiates the shutdown about 7 seconds after I press the button. The 7 seconds is caused by delays I insert into the door and window checking routines.
    Code:
    Jan-10 10:10:28 PM Event Event Trigger "Remote MBR MBRMM 4 Long Pressed"
    Jan-10 10:10:28 PM Event Event Trigger "House To Sleep 01) House to sleep initiator"
    Jan-10 10:10:28 PM DoorWindow Window Count: 0
    Jan-10 10:10:30 PM Event 'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02a) House to Sleep Door open
    Jan-10 10:10:30 PM Event 'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02b1) House to Sleep Window open
    Jan-10 10:10:30 PM Event 'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02b2) House to Sleep Window open - bypass
    Jan-10 10:10:30 PM Event Event Trigger "House To Sleep 02d) House to Sleep Doors and Windows closed"
    Jan-10 10:10:30 PM Event 'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 03a) House to sleep Front Door unlocked
    Jan-10 10:10:33 PM DoorWindow Door Count: 0
    Jan-10 10:10:35 PM Event 'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 03b) House to sleep Workshop Door unlocked
    Jan-10 10:10:35 PM Event Event Trigger "House To Sleep 04a) House to sleep Doors locked"
    Jan-10 10:10:35 PM Event Event Trigger "House To Sleep 05) House to sleep finisher"
    Jan-10 10:10:35 PM Event Event Trigger "Power - General Power to Sleep"
    Jan-10 10:10:35 PM Event Event Trigger "Power - General MR Power OFF"
    Jan-10 10:10:35 PM Event Event Trigger "Arduino LCD LCD Backlights off"
    Jan-10 10:10:35 PM Event Event Trigger "Lights - US Bathroom Nightlight US Bathroom Nightlight Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Curio Cabinet b01) Curio Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Bronco Lamp b01) Bronco Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - US Bathroom Nightlight US Bathroom Nightlight Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Curio Cabinet b08) Curio Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Back Table b01) Back Table Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Grabrail b01) Grabrail Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Bronco Lamp b08) Bronco Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Front Table b01) Front Table Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - LR Track LR Track Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - FP Pole b01) FP Pole Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - MBR Track MBR Track Default Level Enters New Time"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Grabrail b08) Grabrail Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Back Table b08) Back Table Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lighting - General Lighting to Sleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - LR Track LR Track Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Front Table b08) Front Table Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Hydronic - TStat & DHW Pgm 2a) Change in Thermostat Programming Status"
    Jan-10 10:10:36 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Hydronic - TStat & DHW Pgm 3b)Thermostat Programming Check Away
    Jan-10 10:10:36 PM Event 'Run Event' action execution skipped, the conditions applied were not met: Hydronic - TStat & DHW Pgm 3c) Thermostat Program Check Vacation
    Jan-10 10:10:36 PM Event Event Trigger "Hydronic - TStat & DHW Pgm DHW Work Mid"
    Jan-10 10:10:36 PM Device Control Device: Lighting Kitchen Counter LED Strips to Dim 1% (1)
    Jan-10 10:10:36 PM Event Event Trigger "Power - General Fans Off"
    Jan-10 10:10:36 PM Event Event Trigger "Hydronic - TStat & DHW Pgm Non-vacation Programming - Bathrooms"
    Jan-10 10:10:36 PM Event Event Trigger "Hydronic - TStat & DHW Pgm Work 7:30 - No Setback"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - MBR Track MBR Track Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - FP Pole b08) FP Pole Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM Event Event Trigger "Lights - Bronco Lamp b10) Bronco light set"
    Jan-10 10:10:36 PM Event Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/BroncoLight.vb
    Jan-10 10:10:37 PM Event Event Trigger "Power - General Living Room Power OFF"
    Jan-10 10:10:42 PM Event Event Trigger "Lights - Back Table b11) Back Table Lamp off"
    Jan-10 10:10:48 PM Event Event Trigger "Lights - FP Pole b11) FP Pole Lamp Off"
    Jan-10 10:10:49 PM Event Event Trigger "Lights - Front Table b11) Front Table Lamp Off"
    Jan-10 10:10:51 PM Event Event Trigger "Delayed Actions MBR Track Level (Delayed Action)"
    I’ll be implementing something like this as well. “Sleep Finisher” brilliant!

    Leave a comment:


  • spud
    replied
    Originally posted by adwuk View Post
    Please can we have the ability to use expressions in a group condition, similar to those available for group triggers. Here is an example:

    Click image for larger version

Name:	event.png
Views:	17
Size:	41.2 KB
ID:	1275306
    In version 3.0.0.56 available in the Beta section of the updater, I have added the condition "Any/All device's value in this group make this expression true..."

    Click image for larger version

Name:	GroupExpressionCondition.png
Views:	19
Size:	16.9 KB
ID:	1276095

    Leave a comment:


  • adwuk
    replied
    Please can we have the ability to use expressions in a group condition, similar to those available for group triggers. Here is an example:

    Click image for larger version

Name:	event.png
Views:	17
Size:	41.2 KB
ID:	1275306

    Leave a comment:


  • rprade
    replied
    Originally posted by The Profit View Post

    Were you able to tell when the event triggered to turn off your lights if the event was sending an off command to every device in the list or just the devices that had an “On” status? Just wondering if you will experience a full 25 second delay before all lights are “Off” or if it’s just for the number of lights that are actually on.


    Sent from my iPad using Tapatalk
    It will send to every device in succession, it does not check the status of the devices. It takes 25 seconds, but what do I care - I'm in bed and going to sleep. I launch the group control at the beginning of the event, just after the Occupancy mode is set to "Home Asleep". My bedroom lights are in a separate action with a 15 second delay. The flow is this:
    • Doors and windows are checked to make sure they are closed
    • Doors are checked that they are locked
    • Occupancy is put in Home Asleep mode - This changes the power and lighting modes as well
    • Any lights that are dimmable and controlled by my default levels are immediately reduced to sleep levels, this includes the master bedroom lights. This is done by Events that look for the Occupancy Mode Device to change to Home Asleep
    • The Easy Trigger group action is launched after a 5 second wait to allow time for all of the dimming actions to take place.
    • The bedroom lights are turned off after a 10 second wait
    This method will reduce the levels for any dimmable lights that are still on in the house, giving a visual cue to anyone elsewhere in the house. It also dims the bedroom lights for about 10 seconds before they go off. You can see the flow by last night's log entries, note that I do not log device controls, but you can see the Events. The "Sleep Finisher" event is what initiates the shutdown about 7 seconds after I press the button. The 7 seconds is caused by delays I insert into the door and window checking routines.
    Code:
    Jan-10 10:10:28 PM         Event    Event Trigger "Remote MBR MBRMM 4 Long Pressed"
    Jan-10 10:10:28 PM         Event    Event Trigger "House To Sleep 01) House to sleep initiator"
    Jan-10 10:10:28 PM         DoorWindow    Window Count: 0
    Jan-10 10:10:30 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02a) House to Sleep Door open
    Jan-10 10:10:30 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02b1) House to Sleep Window open
    Jan-10 10:10:30 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 02b2) House to Sleep Window open - bypass
    Jan-10 10:10:30 PM         Event    Event Trigger "House To Sleep 02d) House to Sleep Doors and Windows closed"
    Jan-10 10:10:30 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 03a) House to sleep Front Door unlocked
    Jan-10 10:10:33 PM         DoorWindow    Door Count: 0
    Jan-10 10:10:35 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: House To Sleep 03b) House to sleep Workshop Door unlocked
    Jan-10 10:10:35 PM         Event    Event Trigger "House To Sleep 04a) House to sleep Doors locked"
    Jan-10 10:10:35 PM         Event    Event Trigger "House To Sleep 05) House to sleep finisher"
    Jan-10 10:10:35 PM         Event    Event Trigger "Power - General Power to Sleep"
    Jan-10 10:10:35 PM         Event    Event Trigger "Power - General MR Power OFF"
    Jan-10 10:10:35 PM         Event    Event Trigger "Arduino LCD LCD Backlights off"
    Jan-10 10:10:35 PM         Event    Event Trigger "Lights - US Bathroom Nightlight US Bathroom Nightlight Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Curio Cabinet b01) Curio Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Bronco Lamp b01) Bronco Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - US Bathroom Nightlight US Bathroom Nightlight Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Curio Cabinet b08) Curio Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Back Table b01) Back Table Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Grabrail b01) Grabrail Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Bronco Lamp b08) Bronco Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Front Table b01) Front Table Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - LR Track LR Track Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - FP Pole b01) FP Pole Lamp Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - MBR Track MBR Track Default Level Enters New Time"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Grabrail b08) Grabrail Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Back Table b08) Back Table Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lighting - General Lighting to Sleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - LR Track LR Track Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Front Table b08) Front Table Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Hydronic - TStat & DHW Pgm 2a) Change in Thermostat Programming Status"
    Jan-10 10:10:36 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: Hydronic - TStat & DHW Pgm 3b)Thermostat Programming Check Away
    Jan-10 10:10:36 PM         Event    'Run Event' action execution skipped, the conditions applied were not met: Hydronic - TStat & DHW Pgm 3c) Thermostat Program Check Vacation
    Jan-10 10:10:36 PM         Event    Event Trigger "Hydronic - TStat & DHW Pgm DHW Work Mid"
    Jan-10 10:10:36 PM         Device Control    Device: Lighting Kitchen Counter LED Strips to Dim 1% (1)
    Jan-10 10:10:36 PM         Event    Event Trigger "Power - General Fans Off"
    Jan-10 10:10:36 PM         Event    Event Trigger "Hydronic - TStat & DHW Pgm Non-vacation Programming - Bathrooms"
    Jan-10 10:10:36 PM         Event    Event Trigger "Hydronic - TStat & DHW Pgm Work 7:30 - No Setback"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - MBR Track MBR Track Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - FP Pole b08) FP Pole Lamp Default Level Night - Asleep"
    Jan-10 10:10:36 PM         Event    Event Trigger "Lights - Bronco Lamp b10) Bronco light set"
    Jan-10 10:10:36 PM         Event    Running script in background: C:/Program Files (x86)/HomeSeer HS3/scripts/BroncoLight.vb
    Jan-10 10:10:37 PM         Event    Event Trigger "Power - General Living Room Power OFF"
    Jan-10 10:10:42 PM         Event    Event Trigger "Lights - Back Table b11) Back Table Lamp off"
    Jan-10 10:10:48 PM         Event    Event Trigger "Lights - FP Pole b11) FP Pole Lamp Off"
    Jan-10 10:10:49 PM         Event    Event Trigger "Lights - Front Table b11) Front Table Lamp Off"
    Jan-10 10:10:51 PM         Event    Event Trigger "Delayed Actions MBR Track Level (Delayed Action)"

    Leave a comment:


  • The Profit
    replied
    Originally posted by rprade View Post

    This worked perfectly. I moved my goodnight lighting check to a group with a 1 second delay between each device. I check about 25 light switches and dimmers at night. This would invariably cause Z-Wave errors without the delays, last night was very smooth. Since dimmers and switches are both set to 0, I could put them all in the same group. This also makes it much easier to add or remove lights from the goodnight check.
    Were you able to tell when the event triggered to turn off your lights if the event was sending an off command to every device in the list or just the devices that had an “On” status? Just wondering if you will experience a full 25 second delay before all lights are “Off” or if it’s just for the number of lights that are actually on.


    Sent from my iPad using Tapatalk

    Leave a comment:


  • rprade
    replied
    Originally posted by spud View Post

    In version 3.0.0.55 available in the beta section of the updater, I have added the possibility to add a delay between each action of a "Set group":
    Click image for larger version

Name:	groupdelay.png
Views:	36
Size:	13.2 KB
ID:	1274529
    Note that now the "Set Group" action run in its own thread, so if you have subsequent actions after the "Set Group" they will run immediately and will not wait for the devices to be set.
    This worked perfectly. I moved my goodnight lighting check to a group with a 1 second delay between each device. I check about 25 light switches and dimmers at night. This would invariably cause Z-Wave errors without the delays, last night was very smooth. Since dimmers and switches are both set to 0, I could put them all in the same group. This also makes it much easier to add or remove lights from the goodnight check.

    Leave a comment:


  • kideon
    replied
    Originally posted by spud View Post

    Each device has its own stack, the maximum height of the stack is 50. So, for each device you can push 50 values.
    I will look into groups later.
    Dude that's like game changing. Especially with groups. Bien joué! If you could add the device control to the Airplay Speakers then I can finally get my notification engine put together.

    Leave a comment:


  • spud
    replied
    Originally posted by jvm View Post
    Seems like a great addition. Is it a true "stack" or is it more like a single value storage? In other words, if I have a device and I push its value (A), then change the device and push the changed value (B), then change the device and push its changed value (C), can I then pop values C, B, then A back in succession? Or is it really "store value" and "retrieve stored value"? Either way (true "stack" or not), this looks really useful!
    Yes this is a real LIFO (Last In First Out) stack

    Leave a comment:


  • spud
    replied
    Originally posted by kideon View Post


    This is awesome! Is there a limit to how many devices can be pushed/popped simultaneously and also would it be possible to implement in device groups? That would really clean up a lot of events.
    Each device has its own stack, the maximum height of the stack is 50. So, for each device you can push 50 values.
    I will look into groups later.

    Leave a comment:


  • jvm
    replied
    Seems like a great addition. Is it a true "stack" or is it more like a single value storage? In other words, if I have a device and I push its value (A), then change the device and push the changed value (B), then change the device and push its changed value (C), can I then pop values C, B, then A back in succession? Or is it really "store value" and "retrieve stored value"? Either way (true "stack" or not), this looks really useful!

    And a second on the post #393 suggestion that this be extended to groups - perhaps as a future development - it would be great to be able to "push" a group, change some of the values of some of the group's members, then restore the group to what it was.

    Leave a comment:


  • kideon
    replied
    Originally posted by spud View Post
    In version 3.0.0.55 available in the beta section of the updater I have added the following actions:
    - Push Device's value to stack
    - Pop Device's value from stack and Set Device
    - Clear Stack

    So, if you push the device value to stack and then set it to another value like that:
    Click image for larger version

Name:	pushtostack.png
Views:	3224
Size:	10.8 KB
ID:	1274537
    You can set back the device to its previous value like that:

    Click image for larger version

Name:	popfromstack.png
Views:	3175
Size:	6.3 KB
ID:	1274538

    Note that this will only work for device values that are both status and control, because when the plugin push a value to the stack it retrieves the current device's status value, if it is not a control value as well, the pop action will return an error as it will not be able to set the device.

    This is awesome! Is there a limit to how many devices can be pushed/popped simultaneously and also would it be possible to implement in device groups? That would really clean up a lot of events.

    Leave a comment:


  • spud
    replied
    In version 3.0.0.55 available in the beta section of the updater I have added the following actions:
    - Push Device's value to stack
    - Pop Device's value from stack and Set Device
    - Clear Stack

    So, if you push the device value to stack and then set it to another value like that:
    Click image for larger version

Name:	pushtostack.png
Views:	3224
Size:	10.8 KB
ID:	1274537
    You can set back the device to its previous value like that:

    Click image for larger version

Name:	popfromstack.png
Views:	3175
Size:	6.3 KB
ID:	1274538

    Note that this will only work for device values that are both status and control, because when the plugin push a value to the stack it retrieves the current device's status value, if it is not a control value as well, the pop action will return an error as it will not be able to set the device.

    Leave a comment:


  • rprade
    replied
    Perfect! This should help prevent swamping the Z-Wave network (or anything else) with too many commands at once. I’ll move my lighting and power controls to groups and give it a try.

    Thank you!

    Leave a comment:


  • logman
    replied
    Originally posted by logbuilder View Post

    It certainly would be neat if EZTrigger had a function that would:
    • Save current device state
    • turn a device on/off,
    • leave it in that state for n number of seconds/mins/hours
    • if device changes state during the timer interval, reset timer and cancel the whole function
    • if no device change, when timer expires, restore device to saved state
    That can be achieved now with HS3, albeit a bit more clunky.

    Use the "Wait" xx seconds function and at the beginning of each event use "Cancel a Delayed Device Action" for each device named in the event. That way the newest trigger takes precedence. In the example below each time the event fires (motion detected) the lights will remain on for 5 minutes. So if additional motion is detected within the initial 5 minute interval, everything resets and starts over.

    Click image for larger version

Name:	delayed2.png
Views:	35
Size:	86.3 KB
ID:	1274534

    --Barry

    Leave a comment:


  • spud
    replied
    Originally posted by rprade View Post
    This one may be beyond the scope of this plug-in.

    First the situation. When we put our house to new modes (awake, asleep, vacant, occupied, vacation, etc.) we are frequently controlling quite a few Z-Wave devices at once. The downside is that Z-Wave is inherently a little slow and this flood of commands can introduce delays or occasional errors.due to traffic or collisions or whatever. To solve that, I use delayed device actions, delayed Events or wait times. While Rich has dramatically improved the Z-Wave plug-in and the devices have gotten much better since I started this practice, it is still better not to swamp the plug-in with several dozen commands at once. If I use Easy Trigger group actions, I put a wait action between them to slow it down a bit, but I still might send commands to a dozen or more power devices or lights.

    I was going through my "house to sleep" actions today and trying to clean them up. My thought would be to add an option for a configurable delay between the actions on a group of devices on the order of 0-30 seconds. Then the action would be "Easy Trigger: Set Group of Devices to Expression set all devices in group XYZ to {expression} and delay each action by XX seconds". Another thing that would be useful at reducing traffic would be to check the value of each device before setting it. If its value is already there, do not send the command. This also could be optional, for those who want to send a command regardless of the current value.
    In version 3.0.0.55 available in the beta section of the updater, I have added the possibility to add a delay between each action of a "Set group":
    Click image for larger version

Name:	groupdelay.png
Views:	37
Size:	13.2 KB
ID:	1274529
    Note that now the "Set Group" action run in its own thread, so if you have subsequent actions after the "Set Group" they will run immediately and will not wait for the devices to be set.

    Leave a comment:

Working...
X