Announcement

Collapse
No announcement yet.

Group issue

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • jblogs12
    replied
    If you read my post, I am triggering the "time testing" event from a second event "if conditions are met".
    I am not running the first event directly, therefore the conditions are indeed tested.
    Please re-read my last post and test it for yourself.

    Leave a comment:


  • The Profit
    replied
    Originally posted by jblogs12 View Post
    I agree with you that the time "should" be based on the time stamp of the device.
    Firstly, I have to point out that in my scenario I am using a condition to test for time exceeds 7 days. I am not using a trigger to test for the 7 days.

    To prove my point, create an event with a manual trigger and a condition to test (for example) a light to see if it has been off for at least an hour (when you know it has been off for many hours).
    Now, create another event to trigger the first event "if conditions are met".
    Finally, make sure that easytrigger logging has been set to debug mode.
    Run the second event, and check your logs.

    You will see that "'Run Event' action execution skipped, the conditions applied were not met: whatever your event name is".
    You will also note "
    EasyTrigger - DEBUG has (NOT) been condition has been true for 5.594292s "

    The amount of time shown is however many seconds has elapsed since you created the first event.

    At least, this is what I am seeing. Anyone else have any test results?
    One thing to understand about events is that if you press the Run Event button (White Arrow with blue button) then Homeseer will execute the event actions and will never look at the trigger or conditions in the event.

    In order to test the event to see if it is working correctly, the trigger and conditions of the event have to be true at the moment the event is triggered by the trigger set in the event.


    Sent from my iPad using Tapatalk

    Leave a comment:


  • jblogs12
    replied
    I agree with you that the time "should" be based on the time stamp of the device.
    Firstly, I have to point out that in my scenario I am using a condition to test for time exceeds 7 days. I am not using a trigger to test for the 7 days.

    To prove my point, create an event with a manual trigger and a condition to test (for example) a light to see if it has been off for at least an hour (when you know it has been off for many hours).
    Now, create another event to trigger the first event "if conditions are met".
    Finally, make sure that easytrigger logging has been set to debug mode.
    Run the second event, and check your logs.

    You will see that "'Run Event' action execution skipped, the conditions applied were not met: whatever your event name is".
    You will also note "
    EasyTrigger - DEBUG has (NOT) been condition has been true for 5.594292s "

    The amount of time shown is however many seconds has elapsed since you created the first event.

    At least, this is what I am seeing. Anyone else have any test results?

    Leave a comment:


  • The Profit
    replied
    Originally posted by jblogs12 View Post
    Well, I figured out something about this test. It seems like the time span test for "if any device in group "batteries" has been in range 255,255 for at least 7d" is based on the initial time stamp of the event when it is created or modified. It does not use the time stamp of the device's update. So in my case, if a battery has been in the warning state for 2 weeks, and I modified the event that monitors battery condition today, the event would not fire because the event has only just started to monitor the batteries and I would have to wait another 7 days before I would get the email.
    It won’t be based on the date that your event was created, it should be based on when a device has been in that state for exactly 7 days. So if you created that event after a device had been in that range for 7 days, then the device has exceeded the 7 day trigger and will not trigger after that time. In order to get it to trigger 7 days or more you would have to change your event. The only option I can think of is that it has been for at least but that will trigger every second after it reaches 7 days unless you add a condition not to trigger again for a certain time period in the advanced options for an event.

    I would still suggest using the plugin option, it would be much better than an event you could create. There are times when a z-wave device stops reporting it’s battery level and sometimes it stops before the battery reports below 20% battery level, in which case your event wouldn’t trigger. The plugin will trigger in the above scenario....again....would be much better than any event you could create.


    Sent from my iPad using Tapatalk

    Leave a comment:


  • jblogs12
    replied
    Well, I figured out something about this test. It seems like the time span test for "if any device in group "batteries" has been in range 255,255 for at least 7d" is based on the initial time stamp of the event when it is created or modified. It does not use the time stamp of the device's update. So in my case, if a battery has been in the warning state for 2 weeks, and I modified the event that monitors battery condition today, the event would not fire because the event has only just started to monitor the batteries and I would have to wait another 7 days before I would get the email.

    Leave a comment:


  • The Profit
    replied
    Originally posted by jblogs12 View Post
    I have several battery devices. Some of these generate a battery low warning, only to be followed a few hours later with a battery level of 52% (or some other low 50s value). What I wanted to do is run an event periodically (say weekly) that would tell me if a battery was in the low warning state for at least a week, and the me an email to that effect.
    So I created an event as follows:
    if event is manually triggered
    and if a device in group "batteries" has a value of 255
    and if any device in group "batteries" has been in range 255,255 for at least 7d
    then send email

    I then have another event that calls this event weekly "if conditions are met".

    My manual event never runs because conditions are not met. If I change the statement above to test for at least 1 second, it runs fine. If the time test is for several hours, again it fails.

    What am i doing wrong. Please don't comment on syntax because I am away from my system right now and am typing it in from memory.
    Using an event like this might work in some cases, however a developer named Steve Jones created a free plugin called SDJHealth that automatically monitors all of your battery levels. It will send you an email/text/pushover based on your customized settings.


    Sent from my iPhone using Tapatalk

    Leave a comment:


  • jblogs12
    started a topic Group issue

    Group issue

    I have several battery devices. Some of these generate a battery low warning, only to be followed a few hours later with a battery level of 52% (or some other low 50s value). What I wanted to do is run an event periodically (say weekly) that would tell me if a battery was in the low warning state for at least a week, and the me an email to that effect.
    So I created an event as follows:
    if event is manually triggered
    and if a device in group "batteries" has a value of 255
    and if any device in group "batteries" has been in range 255,255 for at least 7d
    then send email

    I then have another event that calls this event weekly "if conditions are met".

    My manual event never runs because conditions are not met. If I change the statement above to test for at least 1 second, it runs fine. If the time test is for several hours, again it fails.

    What am i doing wrong. Please don't comment on syntax because I am away from my system right now and am typing it in from memory.
Working...
X