Announcement

Collapse
No announcement yet.

Email Trigger for Aeon Sensor Not Working

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

    Email Trigger for Aeon Sensor Not Working

    We have a sensor that monitors temperature, humidity, and luminescence and when one of them falls below/above it should be sending an email except none of the events are working. We are using office 365 to send the email and here is a screenshot of one of the events:



    Events don't show that any of them has run. Please help. Thank you
    Attached Files
    Last edited by dablumberg; August 23, 2017, 08:57 AM. Reason: Image of screenshot was not appearing

    #2
    Originally posted by dablumberg View Post
    We have a sensor that monitors temperature, humidity, and luminescence and when one of them falls below/above it should be sending an email except none of the events are working. We are using office 365 to send the email and here is a screenshot of one of the events:



    Events don't show that any of them has run. Please help. Thank you
    It can never be less than 30% and more than 70% humidity at the same time. Change your AND IF to an OR IF and it should work. You can also use a replacement variable to include the actual humidity in the email.
    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

    Comment


      #3
      I tried this one and it seemed to work. Since humidity doesn't change very quickly I left out the 'don't rerun for 30 min' but you can still use it.
      Attached Files

      Comment


        #4
        Followup for luminescence

        Is there a way to setup one of the events to be between the hours at 7pm and 6am. Thank you

        Comment


          #5
          Originally posted by cowinger View Post
          I tried this one and it seemed to work. Since humidity doesn't change very quickly I left out the 'don't rerun for 30 min' but you can still use it.
          Your first Trigger/Condition pair if functionally identical to "IF Main Garage ZSE40 Relative Humidity was set and has a value greater than 70%", just like your second Trigger - there is no need for a Trigger and a Condition.

          You are correct, the email will be sent every time the humidity device updates to a value of less than 30% or greater than 70%. It would depend on the reporting interval of the device as to how frequently the Event will run. The "Cannot Re-Run for:" option would limit the frequency the email is sent.
          HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

          Comment


            #6
            Originally posted by dablumberg View Post
            Is there a way to setup one of the events to be between the hours at 7pm and 6am. Thank you
            There are several options. Since HomeSeer time Conditions cannot cross midnight you can create an IF/OR IF pair inside the event. Read this thread for clarification of how time Conditions work.

            A condition of "Nighttime" is also available that would allow your event to run between sunset and sunrise.

            You can create an event that turns a Virtual Device On at 7PM and another Event that turns it off at 6AM. Then you can use the virtual device as a condition.

            You can purchase Spud's Easy Trigger plug-in and use it's scheduling function to set a schedule when emails will be sent. The Easy Trigger plug-in offers quite a number of enhancements to Triggers, Conditions and Actions that can be very useful as you develop events.
            HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

            Comment


              #7
              Originally posted by rprade View Post
              Your first Trigger/Condition pair if functionally identical to "IF Main Garage ZSE40 Relative Humidity was set and has a value greater than 70%", just like your second Trigger - there is no need for a Trigger and a Condition.
              So you are saying that the first IF statement is not necessary and it should look like this.
              Attached Files

              Comment


                #8
                Originally posted by cowinger View Post
                So you are saying that the first IF statement is not necessary and it should look like this.
                Yes, that should work the same.

                IF the humidity reports less than 30% the event will run. If the humidity reports greater than 70% the event will run. It will run every time the device reports within those values. It doesn't have to report a change in humidity either. If it last reported 77% and 5 minutes later it reports 77% the event will run again. As you suggested, one possibility is the Cannot Re-Run advanced option to limit the emails to once every XXh, XXm, XXs when the humidity reports outside the 30-70% range.

                Another possibility is a virtual device that is set by the event and also used as conditions on both Triggers. A second event would turn the virtual device when the humidity is greater than 30% and less than 70%. This would have it send one email when the humidity is out of range the first time and not again until it has gotten within range then goes outside range again. IT just depends on how often you want to be notified.
                HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                Comment


                  #9
                  We should have had an event where one of the sensors temp recorded a value of 94 degree F and it still did not send an email. Is there a way to debug and test? Thank you
                  Attached Files

                  Comment


                    #10
                    Originally posted by dablumberg View Post
                    We should have had an event where one of the sensors temp recorded a value of 94 degree F and it still did not send an email. Is there a way to debug and test? Thank you
                    You show two temperature events and neither has run. Can you expand the one you think should have run and post a screenshot? That is the first step in debugging - make sure the event logic is valid.
                    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                    Comment


                      #11
                      We reset the device and it is starting to work, thank you.

                      Last thing we need to try and do is setup the alert to only work from 7pm to 6am. What would be the best way to do that?

                      Comment


                        #12
                        Originally posted by dablumberg View Post
                        We reset the device and it is starting to work, thank you.

                        Last thing we need to try and do is setup the alert to only work from 7pm to 6am. What would be the best way to do that?
                        In post #6 there are 4 options. Your choice might depend on how many events will be constrained by that time range. If you have a single event with that time constraint you would likely want to build the logic into that event. If you have multiple events a virtual device or Easy Trigger schedule might be easier. If you want to post a screenshot of your event, I'm sure that someone will offer suggestions.
                        HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                        Comment

                        Working...
                        X