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 jpick View Post
    Hi Spud, great plugin really has helped me get up-to speed on HS3 and what I can do with scheduling more generally. I am looking at using sunrise / sunset in my schedule but want to put limits on the time. For example I want a blind to open at sunrise but not before 7am. I want them to close at sunset but at least by 8:30pm. Is this something that is already available? I could see a not before / not after being useful against both sunrise / sunset in different scenarios. Thanks
    why don't you use some simple "AND IF the time is before/after" additional conditions in your events?

    Leave a comment:


  • jpick
    replied
    Sunrise / Sunset (Not before / Not after)

    Hi Spud, great plugin really has helped me get up-to speed on HS3 and what I can do with scheduling more generally. I am looking at using sunrise / sunset in my schedule but want to put limits on the time. For example I want a blind to open at sunrise but not before 7am. I want them to close at sunset but at least by 8:30pm. Is this something that is already available? I could see a not before / not after being useful against both sunrise / sunset in different scenarios. Thanks

    Leave a comment:


  • AutomatedJim
    replied
    Originally posted by rprade View Post
    You are correct. Setting the light manually to a value that is not enumerated in the toggle values results in it stepping to the next successive value from the last used toggle value, regardless of the device's value. In the examples above, Off was not one of the toggle values.
    I like the toggle feature but not being able to have it 'start over' if someone manually changes the light had me confused.

    Can an action be added to reset the toggle to the beginning if someone manually operates the switch?

    IE: I set up a light to start at on, then dim to 75%, 50%, 25%, off. It has toggled through to 25%, someone walks up to the switch and manually turns the light on to 100%. The reset action would start the toggle process over. Another scenario, the light has toggled down to 25%, someone raised the dim level to 80%. The toggle process doesn't reset completely, only to the next value, IE in my example 75%.

    Thanks,

    Jim

    Leave a comment:


  • rprade
    replied
    Originally posted by spud View Post
    That's not exactly true. If "On" is both a control and a status, and if when you manually set the light to On, it actually sets it to the On status, then the toggle action should behave as you expect, i.e it should always set it to 10%.
    The plugin reads the current status value of the device, and if this value is also one of the control value that you have in your toggle action, then it uses that as the reference. If the current value doesn't match any of the control value in the list, then it uses the last known toggle action as the reference.

    What I suspect in your example, is that manually turning on the light actually set the light to a value that is not one of the controls.
    You are correct. Setting the light manually to a value that is not enumerated in the toggle values results in it stepping to the next successive value from the last used toggle value, regardless of the device's value. In the examples above, Off was not one of the toggle values.

    Leave a comment:


  • spud
    replied
    Originally posted by rprade View Post
    With a series of values, in my case it is 10%, 25%, 40% 60% and On. Regardless of where the light is set, toggle, takes it to the next value after the last. For Example if I run the action with the light Off, it might set to 10%. If I manually turn the light off then run the action again it will set to 25%. If I manually set the light to On, the action will set it to 60%. It seems that the toggle action just steps through the values in order regardless of what the value of the light is.
    That's not exactly true. If "On" is both a control and a status, and if when you manually set the light to On, it actually sets it to the On status, then the toggle action should behave as you expect, i.e it should always set it to 10%.
    The plugin reads the current status value of the device, and if this value is also one of the control value that you have in your toggle action, then it uses that as the reference. If the current value doesn't match any of the control value in the list, then it uses the last known toggle action as the reference.

    What I suspect in your example, is that manually turning on the light actually set the light to a value that is not one of the controls.

    Leave a comment:


  • rprade
    replied
    Is there a way the "Toggle" function can be aware of the current value of a device in choosing the next step. If you have a toggle set to Off, On it seems to work fine, always toggling to the opposite of where the device is set.


    With a series of values, in my case it is 10%, 25%, 40% 60% and On. Regardless of where the light is set, toggle, takes it to the next value after the last. For Example if I run the action with the light Off, it might set to 10%. If I manually turn the light off then run the action again it will set to 25%. If I manually set the light to On, the action will set it to 60%. It seems that the toggle action just steps through the values in order regardless of what the value of the light is.

    Would it be possible for the action to evaluate the current value of the device then "toggle" to the next logical successive value. In order for this to work, the toggle values would have to be sorted in order of value, which is not currently enforced as illustrated here:

    Click image for larger version

Name:	Capture1.png
Views:	1
Size:	21.2 KB
ID:	1187766

    In order fort this to work, the values would have to be in ascending order. If it was to work in descending order, there might have to be a Toggle (or Step) Up and a Toggle (or Step) Down function.

    Another thing that came up in the same discussion was the "Set Device to another Device" action. Perhaps there could be a minimum or maximum value such as Set Device1 to Device2 +10 Max 99 -or- Set Device1 to Device2 -10 Min 1. I realize this could be done with "Set Device to expression, but it might be easier for some to set the values in an controlled event environment.

    Leave a comment:


  • stefxx
    replied
    Originally posted by rprade View Post
    Not to be contrary, but once an event is built and working, who would see that it is "messy"?

    I would be interested to hear how it could be designed to be equally flexible, yet not messy in its own right.
    I have a lot of events that run only at nighttime. Some have several triggers/conditions. And some already contain "OR IF". To make use of the +/- time feature I basically have to duplicate all triggers/conditions at all of those events and every change in trigger/condition require twice the work. The events that already have "OR IF" needs to be duplicated or they get really complicated.

    So... I think we should be able to group AND and OR statements, just as in any programming language. That would really make it powerful and flexible. But I believe HomeSeer's statement is that that would become too complicated for the average user, if I recall correctly. Nothing Spud can do about, but making a "nighttime" (and "daytime"?) +/- time condition would make it less likely to become a "messy" event.

    Just my 2 cents...

    Leave a comment:


  • rprade
    replied
    Originally posted by stefxx View Post
    Thanks. That is why I hate "OR IF", because you have to duplicate all the other triggers/conditions as well. It gets messy quickly.
    Not to be contrary, but once an event is built and working, who would see that it is "messy"?

    I would be interested to hear how it could be designed to be equally flexible, yet not messy in its own right.

    Leave a comment:


  • stefxx
    replied
    Thanks. That is why I hate "OR IF", because you have to duplicate all the other triggers/conditions as well. It gets messy quickly.

    Leave a comment:


  • rprade
    replied
    Originally posted by stefxx View Post
    Exactly! That is why I was requesting a "Between sunset +/- time and sunrise +/- time" condition

    There is a standard condition "If the time is nighttime (after sunset, before sunrise)" but I can't do a +/- time on the sunset/sunrise unfortunately.
    You would duplicate your triggers (using Easy Trigger Conditions) to make it work.

    IF Trigger
    AND IF The time is after (sunset +/- T)

    OR IF Trigger
    AND IF The time is before (sunrise +/- T)

    Then Action(s)

    Leave a comment:


  • stefxx
    replied
    Originally posted by spud View Post
    - "before sunrise AND after sunset" can never be true because the current date-time is compared to sunrise/sunset time of the current day.

    Exactly! That is why I was requesting a "Between sunset +/- time and sunrise +/- time" condition

    There is a standard condition "If the time is nighttime (after sunset, before sunrise)" but I can't do a +/- time on the sunset/sunrise unfortunately.

    Leave a comment:


  • spud
    replied
    Originally posted by stefxx View Post
    Great! Two questions:
    - It doesn't seem to work for group actions (time is always reset to 0). Is this a bug of by design?
    - What about Between Sunrise +/- ? hour to Sunset +/- ? hour? I tried to combine the conditions to make a "between" condition but it doesn't seem to work (before sunrise +/- and after sunset +/-, one is always false )
    - group conditions are buggy when the conditions comes from a plugin. I have reported it several times, but no luck so far.

    - "before sunrise AND after sunset" can never be true because the current date-time is compared to sunrise/sunset time of the current day.

    Leave a comment:


  • stefxx
    replied
    Makes sense. Thanks!

    Leave a comment:


  • spud
    replied
    Originally posted by stefxx View Post
    Hi Spud,

    Never got a response on this request. Is this something you want to consider?

    Thanks again!
    The HS3 API limits to 2 minutes the delay for a plugin action to respond, so if I would implement a "random wait" action it would be limited to 2 minutes, so I think this is one feature that must be implemented in HS3 itself.

    Leave a comment:


  • stefxx
    replied
    Originally posted by spud View Post
    in version 3.0.0.29 available here
    I have added 4 time conditions:
    • The time is before (sunrise +/- T)
    • The time is after (sunrise +/- T)
    • The time is before (sunset +/- T)
    • The time is after (sunset +/- T)

    [ATTACH]56106[/ATTACH]
    Great! Two questions:
    - It doesn't seem to work for group actions (time is always reset to 0). Is this a bug of by design?
    - What about Between Sunrise +/- ? hour to Sunset +/- ? hour? I tried to combine the conditions to make a "between" condition but it doesn't seem to work (before sunrise +/- and after sunset +/-, one is always false )

    Leave a comment:

Working...
X