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

  • popeye
    replied
    I would add a voice to the 3 other advocates of adding HS4 category support. Even just static groups would be fine. Though I don't think there is any notification when members of a category change, so you might have to add some manual update to your UI and a plug-in call. Just wildly guessing. In any case, it would make categories a lot more useful.

    Leave a comment:


  • rge
    replied
    Originally posted by rge View Post
    Another nice time feature would be to specify "earlier of" or "later of", so sunrise and sunset can be used but with a limit. e.g. I want to open my blinds 15 minutes after sunrise, but not before 06:30, and close them at sunset but not later than 21:00.

    It could be specified using > and < for example:

    >06:30,sunrise+00:15 = later of 06:30 and sunrise+15m
    <21:00,sunset = earlier of 21:00 and sunset
    Thinking about this a bit more, it could also be done by adding composition of schedules - so a schedule can be created from two others by joining with AND (i.e. only the overlap, which would be my scenario) or OR (combining both).

    But it would need to allow composed schedules to be composed further, to cope with both earlier/later and start/end conditions. On the bright side, it would only change when sunrise and sunset change, same as with the other schedules.

    Leave a comment:


  • rge
    replied
    Another nice time feature would be to specify "earlier of" or "later of", so sunrise and sunset can be used but with a limit. e.g. I want to open my blinds 15 minutes after sunrise, but not before 06:30, and close them at sunset but not later than 21:00.

    It could be specified using > and < for example:

    >06:30,sunrise+00:15 = later of 06:30 and sunrise+15m
    <21:00,sunset = earlier of 21:00 and sunset

    Leave a comment:


  • adamgreenberg
    replied
    Originally posted by ZoRaC View Post

    Moskus has made a solution for this.
    It’s written in Norwegian, but the screenshots and Google translate should make it understandable:

    https://www.hjemmeautomasjon.no/foru...#comment-63553
    Given I haven't been able to get that script working in HS4, I'd still like for this feature request to be considered

    Leave a comment:


  • ZoRaC
    replied
    Originally posted by adamgreenberg View Post
    Would be great to be able to compare the actual time (in a virtual device that updates every minute) vs. a virtual device that has a time set to trigger an event. The specific use case is as an alarm in the morning. Some days, I want the lights to come on at 7:30 and some days 8:00. I'd set a regular schedule (e.g., weekday vs. weekend) and then some events that would enable me to turn off the alarm for a day or until turned back on, ability to easily change the time of the alarm etc... The missing piece that I can't get to work is the comparison of the time in two virtual devices. I've seen so many posts about people wanting to create an alarm function.
    Moskus has made a solution for this.
    It’s written in Norwegian, but the screenshots and Google translate should make it understandable:

    https://www.hjemmeautomasjon.no/foru...#comment-63553

    Leave a comment:


  • adamgreenberg
    replied
    Would be great to be able to compare the actual time (in a virtual device that updates every minute) vs. a virtual device that has a time set to trigger an event. The specific use case is as an alarm in the morning. Some days, I want the lights to come on at 7:30 and some days 8:00. I'd set a regular schedule (e.g., weekday vs. weekend) and then some events that would enable me to turn off the alarm for a day or until turned back on, ability to easily change the time of the alarm etc... The missing piece that I can't get to work is the comparison of the time in two virtual devices. I've seen so many posts about people wanting to create an alarm function. I can't believe it isn't native in HS4, but easytrigger might be the next logical place for it to be.

    Leave a comment:


  • popeye
    replied
    I saw one thread mentioning renaming groups. That is, changing how groups are stored such that they use a UID, so the name does not matter.

    Additionally, sub-groups. I presume the INI file would have to designate them a bit differently than the ID of a device: {group:xxxx} or some such

    Leave a comment:


  • Ltek
    replied
    Originally posted by logman View Post
    I could be wrong, but I believe as long as the timestamp has been changed, then that is considered a device change even if the value stays the same. Therefore I believe the event is only returning devices that have been unresponsive for 5 days. I've been using the event for a couple of years now, and it seems to work as intended. The reason I have mine stretched out to 5 days is because I have a ton of ZigBee devices that are very sleepy (which helps conserve battery life) so I stretch the reporting period out to avoid catching those in the net.

    I also have a similar event that I use to monitor door lock batteries. Those tend to die when they get around 50% and will leave you locked out of the house. So I created a separate battery group containing only door lock batteries which monitors for unresponsiveness and less than 60% battery level.

    --Barry
    spud
    can you weigh in on this? I'd also like an event to trigger based on "Any device in group <group> has NOT changed for exactly..." but for different reasons than stefxx.
    I would expect that "has NOT changed for at least..." would trigger frequently since any time 'after' the time set would also be true? Thus it could trigger frequently... vs "has NOT changed for exactly..." would only trigger once.

    thx for clarifying for us

    Leave a comment:


  • TC1
    replied
    Originally posted by logman View Post



    By the way the free plugin SDJ-Health will also do what you are looking for plus much more (such as let you know the date when the battery was last replaced, monitor for high discharge rates, etc.). Very good plugin!
    Yep.

    Leave a comment:


  • stefxx
    replied
    Originally posted by logman View Post
    I could be wrong, but I believe as long as the timestamp has been changed, then that is considered a device change even if the value stays the same.
    Not in my experience. That is why several event triggers have been created for both "changed" and "set".

    Thanks!

    Leave a comment:


  • logman
    replied
    Originally posted by stefxx View Post

    Hi Barry, thanks! However, that is not what I requested. I don't even think the event is working as you think it is. You will get a message when the battery is at exactly the same level for 5 days, and below 20%. Depending on the device, the device might be unresponsive for 5 days already...



    So have I. But this seems irrelevant in your event. If the device reports every hours the same value, the condition "Any device in group Batteries has NOT changed for at least 5.00:00:00" would still be true after 5 days.

    I want to be informed if the battery value has not been SET for a specified amount of time.
    Hi stefxx,

    I could be wrong, but I believe as long as the timestamp has been changed, then that is considered a device change even if the value stays the same. Therefore I believe the event is only returning devices that have been unresponsive for 5 days. I've been using the event for a couple of years now, and it seems to work as intended. The reason I have mine stretched out to 5 days is because I have a ton of ZigBee devices that are very sleepy (which helps conserve battery life) so I stretch the reporting period out to avoid catching those in the net.

    I also have a similar event that I use to monitor door lock batteries. Those tend to die when they get around 50% and will leave you locked out of the house. So I created a seperate battery group containing only door lock batteries which monitors for unresponsiveness and less than 60% battery level.

    By the way the free plugin SDJ-Health will also do what you are looking for plus much more (such as let you know the date when the battery was last replaced, monitor for high discharge rates, etc.). Very good plugin!

    --Barry

    Leave a comment:


  • stefxx
    replied
    Originally posted by logman View Post

    This is possible to do now by using the condition "has not changed for at least" and by utilizing the ETGlobalVariables.
    Hi Barry, thanks! However, that is not what I requested. I don't even think the event is working as you think it is. You will get a message when the battery is at exactly the same level for 5 days, and below 20%. Depending on the device, the device might be unresponsive for 5 days already...

    IMPORTANT: I have all battery devices set to update their timestamp with each report received regardless of whether the device value changes.
    So have I. But this seems irrelevant in your event. If the device reports every hours the same value, the condition "Any device in group Batteries has NOT changed for at least 5.00:00:00" would still be true after 5 days.

    I want to be informed if the battery value has not been SET for a specified amount of time.

    Leave a comment:


  • logman
    replied
    Originally posted by stefxx View Post
    Hi! I have a couple of battery operated devices that sometimes simply run out of battery power while still at 75+ battery percentage. These devices should report their battery status every hour, so I was thinking of monitoring their "last update" timestamp to see if they are still alive.

    I know there is a "Any device in group <group> has NOT changed for exactly...", but that doesn't work. It seems that this actually looking for a change in the value. So, my suggestion is to add a "Any device in group <group> has NOT been set for exactly...", that looks at the last change timestamp.

    Thanks for considering!
    This is possible to do now by using the condition "has not changed for at least" and by utilizing the ETGlobalVariables. In the example below I'm looking for any battery device that last reported a battery level less than 20% AND has not updated the battery condition for at least 5 days. Any found will be sent as a text to my phone.

    IMPORTANT: I have all battery devices set to update their timestamp with each report received regardless of whether the device value changes.

    Click image for larger version

Name:	battery_monitor_event.png
Views:	126
Size:	501.5 KB
ID:	1444031

    --Barry

    Leave a comment:


  • stefxx
    replied
    The $$GLOBALVAR:ETDeviceXxxx variables are great. But I store general information (like name etc) on the root device, not the child device. Would it be possible to have variables for the root device as well? Like $$GLOBALVAR:ETRootName etc?

    Thanks!

    Leave a comment:


  • Ltek
    replied
    Originally posted by stefxx View Post
    Hi! I have a couple of battery operated devices that sometimes simply run out of battery power while still at 75+ battery percentage. These devices should report their battery status every hour, so I was thinking of monitoring their "last update" timestamp to see if they are still alive.

    I know there is a "Any device in group <group> has NOT changed for exactly...", but that doesn't work. It seems that this actually looking for a change in the value. So, my suggestion is to add a "Any device in group <group> has NOT been set for exactly...", that looks at the last change timestamp.

    Thanks for considering!
    +1

    Leave a comment:

Working...
X