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

  • Originally posted by jvm View Post
    spud Thank you for the many recently added features that I and other had requested. I've already found them quite helpful in implementing some new feature that I was trying to get working (I find the stack operations incredibly useful for a use case I had of adjusting and then restoring volume levels for Chromecast devices using your Chromecast plugin - in particular, using stacks to adjust volume to play an announcement but then being able to restore the original volumes).

    There are two remaining changes that I'm interested in. One that seems simple, and one that seems more complex. Each of these are intended to have wide applicability, rather than being narrow use-case focused.

    I realize you've been busy on adding features and so you may have limited time to work on these ideas now, but your thoughts on whether you can add these at some point would be appreciated.

    1. Probably Simple - For the "clear stack" operations, a check box whereby the device is set back to its original value -- i.e., the final value to be popped off the stack. Use case: restore an item or group of items to its/their original value, regardless of pending intermediate changes that have been stored on the stack. I was thinking of using this for a HomeSeer shutdown routine to make sure things are stored to their original values before a shutdown. I'm sure there are other use cases.

    2. More Complex (but a lot of power) - For the "EasyTrigger: Set Group of Devices to Expression" action, the ability to evaluate the expression individually for each item in the group, combined with (a) a new global variable etDeviceType which has the type of the triggering device; and (b) a set of variables that you can use in the expression that are analogous to the "et" global variables but which would hold the values for the current device in the group as the expression part is evaluated for that device.

    This proposal was explained a bit more in post #462. The basic idea is to allow some individualized processing for each member in the group using an "If" statement in the expression to individually calculate a value for each device to be set based on its individualized current values and the triggering device's values.

    Example use cases:
    • If I wanted to turn on all lights in Group "MyGroup" to 50%, but only if they are not already on, I could then do a "Set Group of Devices to Expression, Select the group "MyGroup" and then use an expression like: "IF($ThisDeviceValue == 0, 50, $ThisDeviceValue)" to set the device to 50 if it isn't on, but to leave it at the same value (i.e., set it to its already existing value $ThisDeviceValue) if it is already on (maybe even including a "do nothing if action would set to same value" option).
    • Similarly, if I wanted to turn on all lights in a group, but only if they are in the same floor / room as the triggering device and not already on, I would use and expression like: "IF($ThisDeviceLocation1 == $ETDeviceLocation1 && $ThisDeviceLocation2 == $ETDeviceLocation2 && $ThisDeviceValue == 0, 50, $ThisDeviceValue)". The idea here is that if I have a number of similar events each of which triggers off of something in the room and acts on other devices in the room, I could reduce my event could by writing a single event that can use the location information of the triggering device to filter out which devices to act on. For example, I have motions sensors in 10 rooms and want to turn on lights in the rooms with the motion sensor, rather than 10 events, I could have one group with all my motion sensors and another with all the lights and use a single event that considers the Location1 / Location2 in the expression evaluation.

    I could give a number of additional use cases for #2 if that's helpful for your consideration. Your thoughts on these would be appreciated. Best regards, JVM.
    I added $DEVICEVALUE and $DEVICEREF as possible variables for the "Set Group of Devices to Expression" action in version 3.0.0.61 (available in beta section of the updater)
    I cannot add things like name, location, etc... because the library that evaluate the expression can only work with numerical values, not with strings.

    Regarding stacks, I will add some more advanced options to the push/pop/clear actions later.

    Comment


    • Originally posted by spud View Post

      I added $DEVICEVALUE and $DEVICEREF as possible variables for the "Set Group of Devices to Expression" action in version 3.0.0.65 (available in beta section of the updater)
      I cannot add things like name, location, etc... because the library that evaluate the expression can only work with numerical values, not with strings.

      Regarding stacks, I will add some more advanced options to the push/pop/clear actions later.
      Awesome. This works great. I'm amazed you got this implemented so fast!

      By the way, I assumed that if I used $$DVR:$DEVICEREF: it would give the same result as using $DEVICEVALUE, but from my quick test, using $$DVR:$DEVICEREF: will generate an error. Again, thanks for this addition.

      Comment


      • Originally posted by jvm View Post
        By the way, I assumed that if I used $$DVR:$DEVICEREF: it would give the same result as using $DEVICEVALUE, but from my quick test, using $$DVR:$DEVICEREF: will generate an error. Again, thanks for this addition.
        This is because, global variables are evaluated before $DEVICEREF and $DEVICEVALUE, I guess I should do the opposite. It will be fixed in the next version.

        Comment


        • Originally posted by spud View Post

          I added $DEVICEVALUE and $DEVICEREF as possible variables for the "Set Group of Devices to Expression" action in version 3.0.0.65 (available in beta section of the updater)
          I cannot add things like name, location, etc... because the library that evaluate the expression can only work with numerical values, not with strings.
          Is version .65 correct? I'm showing .61 as the latest available in the updater. My updater has been acting screwy lately, so want to make sure I'm not missing something...

          --Barry

          Comment


          • Originally posted by logman View Post

            Is version .65 correct? I'm showing .61 as the latest available in the updater. My updater has been acting screwy lately, so want to make sure I'm not missing something...

            --Barry
            My bad, it's a typo in the forum post, .61 is the correct version.

            Comment


            • Originally posted by spud View Post

              My bad, it's a typo in the forum post, .61 is the correct version.

              By the way, in case you're interested in some simple examples to add to the instructions, here are a few that I'm already using . . .



              To turn on all dimmers to 25% if they are off, but leave them at their current value if a user has already turned them on, use the expression:
              if( $DEVICEVALUE == 0, 25, $DEVICEVALUE)

              To increase each dimmers by 10% of its current value if the device is already 5% or greater, or set to 5% if the device is currently less than 5%, use the expression:
              if ($DEVICEVALUE < 5, 5, Min(Ceiling($DEVICEVALUE * 1.10), 99) )

              * Note that the expression
              Min(Ceiling($DEVICEVALUE * 1.10), 99) will increase a dimmer value by 10%, but limit the maximum to 99 which is the maximum Z-Wave dimmer value that is allowed. The "Ceiling" command ensures that there be at least a 1-point increase if the multiplication by 1.10 would, otherwise, result in a calculated increase of less than 1.


              Comment


              • I´m trying to use $DEVICEVALUE and $DEVICEREF with 'Set Group of Devices to Expression' but I always get an error in the log: " ERROR Parameter was not defined Nome do parâmetro: DEVICEVALUE .The same error happens if I use $DEVICEREF. The event below for example throws the error:

                IF Any device in group Luzes_Quartos_Terreo was set and has a value that is not equal to 0
                Then Set all Devices in Luzes_Quartos_Terreo to $DEVICEVALUE

                Any advice on what am I doing wrong ? I´m on EasyTrigger Beta 3.0.0.62.

                Comment


                • Originally posted by Hans View Post
                  I´m trying to use $DEVICEVALUE and $DEVICEREF with 'Set Group of Devices to Expression' but I always get an error in the log: " ERROR Parameter was not defined Nome do parâmetro: DEVICEVALUE .The same error happens if I use $DEVICEREF. The event below for example throws the error:

                  IF Any device in group Luzes_Quartos_Terreo was set and has a value that is not equal to 0
                  Then Set all Devices in Luzes_Quartos_Terreo to $DEVICEVALUE

                  Any advice on what am I doing wrong ? I´m on EasyTrigger Beta 3.0.0.62.
                  this is a bug I have introduced in version 3.0.0.62. I will fix it ASAP

                  however, note that your action "Set all devices in Group to $DEVICEVALUE" will have almost no effects because it means each device in the group will bet set to its current value. Maybe what you wanted to do is use the global variable $$GLOBALVAR:ETDeviceValue: which contains the current value of the triggering device

                  see end of this post: https://forums.homeseer.com/forum/ul...175#post864175

                  Comment


                  • Originally posted by spud View Post

                    this is a bug I have introduced in version 3.0.0.62. I will fix it ASAP

                    however, note that your action "Set all devices in Group to $DEVICEVALUE" will have almost no effects because it means each device in the group will bet set to its current value. Maybe what you wanted to do is use the global variable $$GLOBALVAR:ETDeviceValue: which contains the current value of the triggering device

                    see end of this post: https://forums.homeseer.com/forum/ul...175#post864175
                    OK then. Actually I was using an IF statement as the expression, but as this didn´t work after some tries, I just used the simplest form to see if it would work. Thanks for the quick reply.

                    Comment


                    • Originally posted by Hans View Post

                      OK then. Actually I was using an IF statement as the expression, but as this didn´t work after some tries, I just used the simplest form to see if it would work. Thanks for the quick reply.
                      it's fixed in version 3.0.0.63 available in the beta section of the updater

                      Comment


                      • Originally posted by kriz83 View Post
                        What is the behaviour when the stack is 'full' (50 items). Will the oldest one be removed ?
                        If not, could we add a pop without assigning it to a device ?
                        If the stack is full, a push will do nothing.
                        In version 3.0.0.63 available in the beta section of the updater the clear stacks has now some advanced option which let you remove only the top N items:

                        Click image for larger version

Name:	clearstackadvanced2.PNG
Views:	1
Size:	49.2 KB
ID:	1296814

                        Comment


                        • Originally posted by jvm View Post

                          1. Probably Simple - For the "clear stack" operations, a check box whereby the device is set back to its original value -- i.e., the final value to be popped off the stack. Use case: restore an item or group of items to its/their original value, regardless of pending intermediate changes that have been stored on the stack. I was thinking of using this for a HomeSeer shutdown routine to make sure things are stored to their original values before a shutdown. I'm sure there are other use cases.

                          .
                          In version 3.0.0.63 I have added some advanced option to the "Clear Stack" action, which let you remove all items except the N bottom ones:

                          Click image for larger version

Name:	clearstackadvanced1.PNG
Views:	1
Size:	23.8 KB
ID:	1296816

                          Comment


                          • Wouldn't it be better if the oldest value was removed iso doing nothing?

                            Verstuurd vanaf mijn SM-G965F met Tapatalk

                            Comment


                            • Originally posted by spud View Post

                              In version 3.0.0.63 I have added some advanced option to the "Clear Stack" action, which let you remove all items except the N bottom ones:

                              Click image for larger version

Name:	clearstackadvanced1.PNG
Views:	1
Size:	23.8 KB
ID:	1296816
                              Looks Good. So as I understand it, I could run a "clear stack operation" leaving 1 value, and then do the Pop and Set devices to set each device each back to its original value, or Do a clear leaving 0 values and the entire stack is simply emptied so a "Pop and Set" after that will effectively do nothing. That works for me. Thanks again for the help.

                              Comment


                              • spud

                                As another Feature Request for your consideration, I propose a Group Action to run a script or set a Z-Wave Parameter.

                                The feature that I describe below is analogous to the "Set Group of devices to Expression" Action, but allows running scripts for each device.

                                Background / Use Case: This feature request came about as I was thinking about how to easily set Z-Wave device parameters for a large group of devices. What I was after was a way to define a group of devices (e.g., all of my dimmers) and then be able to set a parameter for each device in the group. For example, to set them all to the same ramp speed. Another use case was to be able to use this to manipulate the LED colors for my HomeSeer WD200 dimmers in response to different events. As I was thinking about this, it may make sense to make this a more "general" function where you can run a script for each device (I think I can set the parameter via a script, and scripts would give more functions). Here's how I was thinking this could operate:

                                For sake of description, I'm calling the Action " Easy Trigger: Run Script or Script Command for Each Device in Group"
                                1. This Action is performed on a defined Group or a single device
                                2. Optionally, the Action includes a boolean expression test (i.e., "only run Script if test is true") where you can have a test that is evaluated for each device (so the test should be able to consider device variables such as $DEVICEVALUE or other global variables).
                                3. If the test is "true" for a device, then run either (a) an immediate script, or (b) a "full script" from as script file -- basically, you'd be replicating the same capability that you get from the regular HomeSeer "Run a Script or Script Command" function but you'd run it for each device in a group. Here, I was envisioning you could do an Immediate script or one from a file and you should be able to pass the file parameter such as the device reference ($DEVICEREF) for each device (and other variables like value, status, etc). Thus, for each device in the group, the script parameters.would include a different reference allowing the script to act on each device individually


                                As help to the user, and since scripting can be a bit confusing, maybe this is two functions - one as I've described above, and a related one where step #4 is a "Set Parameter" and you just select a specific parameter and a specific value to set

                                Let me know your thoughts on this. Thanks for your help / consideration of these ideas.
                                JVM

                                Comment

                                Working...
                                X