Announcement

Collapse
No announcement yet.

2 Schedules one time?

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

    2 Schedules one time?

    Hello

    One of my Schedules is:
    [Mon Sunset-01:00;Mon Sunset+01:00]

    The second is:
    [Mon Sunset+01:00;Mon Sunset+02:30]



    My question is, should the second schedule be +01:00 or +01:01
    if it was used as a condition for a triggering event such as a PIR going OPEN?

    Thank you

    #2
    I'm not sure I understand the question

    You can have overlapping time ranges, as long as they are in different schedules.

    Comment


      #3
      Sorry

      Two Schedules, I want one to follow the other directly... and not overlap at all.

      Between hh:00 and hh:01 - there are 59 seconds....


      • So should it be 16:00 to 18:00, then the next schedule 18:01 to 20:00
      • Or is it 16:00 to 18:00, the next schedule 18:00 to 20:00





      So with the seconds from HomeSeer clock:
      .
      16:00:00 to 18:00:59 / 18:01:00 to 20:00:59
      or
      16:00:59 to 17:59:59 / 18:00:00 to 19:59:59

      Comment


        #4
        still not sure what you want to do, are you using the schedules as triggers or conditions?

        For triggers:
        if you have 2 events looking like

        1) IF Time leaves [16:00 ; 18:00]
        THEN ...

        2) IF Time enters [18:00 ; 20:00]
        THEN ...

        then both those event will be fired at almost the same time (sometime between 18:00:00 and 18:00:29, because schedule triggers are only checked every 30 seconds), but the order in which they are fired is unknown.

        if in the second event you use 18:01 instead of 18:00, then it will be fired 1 minute after the first one.

        For conditions:
        18:00 in a schedule means exactly 18:00:00

        Comment


          #5
          So I am using them as conditions

          Event 1
          IF landing PIR is Open
          and if time is in schedule1 (16:00-18:00)

          Event 2
          IF landing PIR is Open
          and if time is in schedule2 (18:01-20:00)

          =====================================

          Basically I want to know at

          18:00:25
          Will it be event 1 or event 2 or neither

          Same at 18:00:47
          Will it be event 1 or event 2 or neither


          I'm sorry I'm being unclear hopefully this will allow me to understand
          I do feel very dumb.

          Comment


            #6
            Originally posted by smokeycoles View Post
            So I am using them as conditions

            Event 1
            IF landing PIR is Open
            and if time is in schedule1 (16:00-18:00)

            Event 2
            IF landing PIR is Open
            and if time is in schedule2 (18:01-20:00)

            =====================================

            Basically I want to know at

            18:00:25
            Will it be event 1 or event 2 or neither

            Same at 18:00:47
            Will it be event 1 or event 2 or neither


            I'm sorry I'm being unclear hopefully this will allow me to understand
            I do feel very dumb.
            18:00:25: neither
            18:00:47: neither

            Comment


              #7
              Chris;

              Use the same starting time for the second schedule as the ending time for the first, you do not need to use any offset.

              Times stated in whole minutes are still subject to the resolution of the HS3 clock in microseconds

              In a nutshell a period ending at 18:00 actually ends after 17:00:00.999999 and a schedule that begins at 18:00 actually begins at 18:00:00.000000. There is no overlap or gap. Since spud evaluates the time once every 30 seconds, there is no chance it will be in both schedules at the same time. Even if it was evaluated every millisecond, there still would not be an overlap.
              HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

              Comment


                #8
                Ah I see, thanks both.
                I have done my schedules wrong then - I will amend now.


                I have to say; I initially only used EasyTrigger for one function, but this schedule feature is one very good and cool tool, along with the toggle ability.

                Sorry for all the questions - I am still learning, even tonight on the run another event - I learned the value of the tickbox "run if conditions are true", it was 30minutes of fault finding with some very odd features - my house was telling me it was disarmed night, disarmed stay and disarmed away mode all at once I do think Spud you would be impressed to see how I implement your plugins, I'm very proud of what the house is doing. I really wish the UK was as far ahead as the US.


                Thanks again
                Chris

                Comment


                  #9
                  Easy Trigger is the single most useful plug-in I have purchased.

                  Don't worry about the questions. People have the same questions about the native HS3 time triggers. Even though they only are entered using hours and minutes, they are evaluated to a much higher resolution. Just like Easy Trigger the native "The time is before 18:00" is true from 12:00 am that day until a microsecond before 18:00:00 and "The time is after 18:00" is true the first microsecond after 18:00:00.
                  HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

                  Comment

                  Working...
                  X