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

  • spud
    replied
    Originally posted by usLEDsupply View Post
    i don't see that one anywhere?
    do you have version 3.0.0.17 or later installed?

    see screenshot below:
    Click image for larger version

Name:	range.png
Views:	1
Size:	13.7 KB
ID:	1182411

    Leave a comment:


  • usLEDsupply
    replied
    sorry i just checked and see that i am using an older version before that was added so will have to update.
    i guess i thought it was in the updater and none of my plugins showed an update so i thought i was up to date

    Leave a comment:


  • usLEDsupply
    replied
    i don't see that one anywhere?

    Leave a comment:


  • spud
    replied
    Originally posted by usLEDsupply View Post
    Since you can't have "has been in a rang for x" could you have one that would trigger on the device change and then count for x seconds and if it is still triggered run the event?

    i have an event that checks to see the any of the temp sensors are above 104deg as a backup fire alarm but about once a month one of the z-wave sensors will give a false read and set off my alarm so it would be nice to be able to say if it has been above 104 for 30 seconds then trigger the alarm? i cant seem to figure any other way of doing this without lots of extra events/timers

    if not it's not a big deal but would be nice and the Easy Trigger Device Value Option box it so empty looking with only one option to compare between 2 device values :-)
    why don't you use the EasyTrigger: "This device's value has been in range [X,Y] for exactly..." ?
    What I can't implement is the condition similar to this trigger, but the trigger already exists.

    Am I missing something?

    Leave a comment:


  • usLEDsupply
    replied
    Since you can't have "has been in a rang for x" could you have one that would trigger on the device change and then count for x seconds and if it is still triggered run the event?

    i have an event that checks to see the any of the temp sensors are above 104deg as a backup fire alarm but about once a month one of the z-wave sensors will give a false read and set off my alarm so it would be nice to be able to say if it has been above 104 for 30 seconds then trigger the alarm? i cant seem to figure any other way of doing this without lots of extra events/timers

    if not it's not a big deal but would be nice and the Easy Trigger Device Value Option box it so empty looking with only one option to compare between 2 device values :-)

    Leave a comment:


  • rprade
    replied
    It does exactly what I needed and then some! This one is going to be fun to play with. Thanks!

    Leave a comment:


  • spud
    replied
    in version 3.0.0.20 I have added the "Set Device to Expression" action.
    The supported operators are listed here
    The supported functions are listed here

    For example in the screenshot below the "Ecobee Target Temperature Low" device is increased by 2%.
    Note the use of the Round function, as most of control values for devices are integer, you will often have to round the result of your expression to the nearest integer.
    Click image for larger version

Name:	setdevicetoexpression.png
Views:	2
Size:	6.4 KB
ID:	1182409

    another interesting function is "if(condition, value if condition is true, value if condition is false)" that allows us to use expression like
    Code:
    if($$DVR:123: > $$DVR:234:, 60, 70)
    which means if device #123 has a value greater than device #234 then returns 60 else 70

    To test/troubleshoot your expression you can set the log level to debug, and you will see something like the following in the logs, everytime the expression is evaluated:
    Code:
     Expression Round($$DVR:3968: * 102/100, 0) evaluated to 65
    Last edited by spud; December 21st, 2015, 01:13 PM.

    Leave a comment:


  • sirmeili
    replied
    Originally posted by spud View Post
    To know the last time the value changed, I have to monitor the device for changes. So the plugin needs to know which devices to monitor when you start the plugin, thus the plugin needs to retrieve all the conditions at startup.
    Gotcha.....I was thinking that maybe HS allows you to check the properties of a devices (Such as last time changed) and since it's a condition, you only need to know when whatever trigger it is tied to fires (meaning you only have to check when it requests if it's true/false).

    Seems like an odd omission from HS, but perhaps they never thought anyone would want to know the last changed value.

    Thanks for the explanation

    Leave a comment:


  • rprade
    replied
    Originally posted by spud View Post
    Instead of adding specific operation like this one, I think I'm going to add a "Set Device to Expression" where you can use simple mathematical operations with global variables like for example:
    $$DVR:123: + $$DVR:345: * 2 / 100
    Perfect! And flexible.

    Leave a comment:


  • spud
    replied
    Originally posted by rprade View Post
    I have a specific need for dimmable devices that could be helped by setting to a device or variable +/- a percentage.

    I have some LED strips controlled by PWM and because each LED color produces a different output luminance at a given pulse width, to create White, blue needs to be about 20% down and green about 13% down from red. I would like to make a master level virtual device, so that I could raise and lower the dim level of the LEDs and maintain a similar color balance. +

    This also would allow a virtual device to control the relative dim level of a number of devices, always keeping the same level relationship to one another.
    .
    Instead of adding specific operation like this one, I think I'm going to add a "Set Device to Expression" where you can use simple mathematical operations with global variables like for example:
    $$DVR:123: + $$DVR:345: * 2 / 100

    Leave a comment:


  • spud
    replied
    Originally posted by sirmeili View Post
    Then all the plugin has to do is check if the value is correct and do a date/time span on the last time the value changed.
    To know the last time the value changed, I have to monitor the device for changes. So the plugin needs to know which devices to monitor when you start the plugin, thus the plugin needs to retrieve all the conditions at startup.

    Leave a comment:


  • sirmeili
    replied
    Originally posted by spud View Post
    This one is not possible to implement because AFAIK there is no way to get a list of all the conditions from the HS3 API, so the plugin can't know what devices to monitor.
    Why do you need a list of all the conditions? (serious question). So you already have a condition called "Easy Trigger: A Devices Value is...". Then in the next dropdown you have a list of options (Well 1 option). Could you not have an option that says "This devices has been/For at most..."? Then all the plugin has to do is check if the value is correct and do a date/time span on the last time the value changed.

    Understand, that it may be one of those times where doing something seems really easy, but in actually it's really hard (as a developer, I do understand this). I'm just wanting to make sure you understand the request.

    Leave a comment:


  • spud
    replied
    Originally posted by sirmeili View Post
    I don't think this is currently in there, but I would like to request a new condition: A devices value has changed to X in the last X time span. This is similar to the Trigger "A devices value has been [value] for at least/exactly [timespan], however it checks if it has been a value for less than a specified amount of time instead of if it has been longer.

    For example:

    Trigger: The Garage door was closed
    Condition: The Garage Lights were changed to On (value) in the last 5 minutes (time span).

    It could also be written:
    Trigger: The Garage door was closed
    Condition: The Garage Lights has been On (value) for no more than 5 minutes (time span).

    Thanks,
    Frank
    This one is not possible to implement because AFAIK there is no way to get a list of all the conditions from the HS3 API, so the plugin can't know what devices to monitor.

    Leave a comment:


  • lveatch
    replied
    What about a condition for if a device value has changed and is increasing / decreasing by +/- x?

    I was thinking of using this with my temperature monitoring of my freezer's and refrigerator's.

    I have been trying to figure out a way to easier way to check for "temperature is greater than x... and is increasing or decreasing" so I know how concerned I should be.

    Len

    Leave a comment:


  • sirmeili
    replied
    I don't think this is currently in there, but I would like to request a new condition: A devices value has changed to X in the last X time span. This is similar to the Trigger "A devices value has been [value] for at least/exactly [timespan], however it checks if it has been a value for less than a specified amount of time instead of if it has been longer.

    For example:

    Trigger: The Garage door was closed
    Condition: The Garage Lights were changed to On (value) in the last 5 minutes (time span).

    It could also be written:
    Trigger: The Garage door was closed
    Condition: The Garage Lights has been On (value) for no more than 5 minutes (time span).

    Thanks,
    Frank

    Leave a comment:

Working...
X