Announcement

Collapse
No announcement yet.

Schedules Do Not Work Across Midnight -- Not documented in User Guide, so here it is

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

    Schedules Do Not Work Across Midnight -- Not documented in User Guide, so here it is

    I created 4 schedules just fine and then I wasted a30 min and a lot of trial and error to figure out that either there is a bug or this schedule has the same limitations that HS3 does with time management across midnight (e.g. no smarter than a 1st grader)

    I did not see this documented in the User Guide. So hope this saves someone time and maybe Spud can put this in the user guide.

    Ultimately I was hoping this plugin would work properly across midnight.

    these stick....

    [Mon 23:30;Mon 23:59],[Tue 23:30;Tue 23:59],[Wed 23:30;Wed 23:59],[Thu 23:30;Thu 23:59],[Fri 23:30;Fri 23:59],[Sat 23:30;Sat 23:59],[Sun 23:30;Sun 23:59]
    [Mon 00:00;Mon 06:00],[Tue 00:00;Tue 06:00],[Wed 00:00;Wed 06:00],[Thu 00:00;Thu 06:00],[Fri 00:00;Fri 06:00],[Sat 00:00;Sat 06:00],[Sun 00:00;Sun 06:00]

    these do not...

    [Mon 23:30;Mon 24:00],[Tue 23:30;Tue 24:00],[Wed 23:30;Wed 24:00],[Thu 23:30;Thu 24:00],[Fri 23:30;Fri 24:00],[Sat 23:30;Sat 24:00],[Sun 23:30;Sun 24:00]

    == BLANK

    Log:

    ERROR System.OverflowException: The TimeSpan could not be parsed because at least one of the numeric components is out of range or contains too many digits. at System.Globalization.TimeSpanParse.ProcessTerminal_HM(TimeSp anRawInfo& raw, TimeSpanStandardStyles style, TimeSpanResult& result) at System.Globalization.TimeSpanParse.ProcessTerminalState(Time SpanRawInfo& raw, TimeSpanStandardStyles style, TimeSpanResult& result) at System.Globalization.TimeSpanParse.TryParseTimeSpan(String input, TimeSpanStandardStyles style, IFormatProvider formatProvider, TimeSpanResult& result) at System.Globalization.TimeSpanParse.Parse(String input, IFormatProvider formatProvider) at HSPI_EasyTrigger.HSTimeSpan.Parse(String s) at HSPI_EasyTrigger.WeekScheduleTime.Parse(String s) at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse(String s) at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots(String timeSlots)


    [Mon 23:30;Mon 00:00],[Tue 23:30;Tue 00:00],[Wed 23:30;Wed 00:00],[Thu 23:30;Thu 00:00],[Fri 23:30;Fri 00:00],[Sat 23:30;Sat 00:00],[Sun 23:30;Sun 00:00]

    == [Mon 23:30;Mon 00:00]

    Log:

    ERROR System.FormatException: end time Tue 00:00 cannot be before start time Tue 23:30 at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse(String s) at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots(String timeSlots)



    [Mon 23:30;Mon 06:00],[Tue 23:30;Tue 06:00],[Wed 23:30;Wed 06:00],[Thu 23:30;Thu 06:00],[Fri 23:30;Fri 06:00],[Sat 23:30;Sat 06:00],[Sun 23:30;Sun 06:00]

    == BLANK

    Log:

    ERROR System.FormatException: end time Mon 06:00 cannot be before start time Mon 23:30 at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse(String s) at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots(String timeSlots)

    #2
    Monday 00:00 is 12:00 AM on Monday making your schedule beginning time before the ending time. If you want [Mon 23:30;Mon 00:00] it is expressed as [Mon 23:30;Tue 00:00]. A schedule that ends at Midnight is expressed as 00:00 the next day. A schedule that ends at 00:00 ends at midnight the day before. A schedule that begins at 00:00 begins at 12:00:00 AM That day.

    There is no Mon 24:00 - Monday 24:00 is expressed as Tue 00:00.

    In all of these:

    [Mon 23:30;Mon 06:00],[Tue 23:30;Tue 06:00],[Wed 23:30;Wed 06:00],[Thu 23:30;Thu 06:00],[Fri 23:30;Fri 06:00],[Sat 23:30;Sat 06:00],[Sun 23:30;Sun 06:00]
    Your start time is after your end time. Monday 23:30 (11:30 PM) is after Monday at 06:00 (6:00 AM).

    Perhaps you want:
    [Mon 23:30;Tue 06:00],[Tue 23:30;Wed 06:00],[Wed 23:30;Thu 06:00],[Thu 23:30;Fri 06:00],[Fri 23:30;Sat 06:00],[Sat 23:30;Sun 06:00],[Sun 23:30;Mon 00:00], [Mon 00:00;Monday 06:00]

    Note the break at Midnight on Sunday, which is a limitation of .NET and has been discussed here. A schedule cannot cross Midnight on Sunday Night/Monday Morning. You have to dig a little deeper for this one.
    Last edited by randy; July 20, 2017, 09:37 PM.
    HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

    Comment


      #3
      Thank you. Makes perfect sense I was not thinking about it proper. This would be good to put in the Easy Trigger User Manual

      Originally posted by rprade View Post
      Monday 00:00 is 12:00 AM on Monday making your schedule beginning time before the ending time. If you want [Mon 23:30;Mon 00:00] it is expressed as [Mon 23:30;Tue 00:00]. A schedule that ends at Midnight is expressed as 00:00 the next day. A schedule that ends at 00:00 ends at midnight the day before. A schedule that begins at 00:00 begins at 12:00:00 AM That day.

      There is no Mon 24:00 - Monday 24:00 is expressed as Tue 00:00.

      In all of these:

      [Mon 23:30;Mon 06:00],[Tue 23:30;Tue 06:00],[Wed 23:30;Wed 06:00],[Thu 23:30;Thu 06:00],[Fri 23:30;Fri 06:00],[Sat 23:30;Sat 06:00],[Sun 23:30;Sun 06:00]
      Your start time is after your end time. Monday 23:30 (11:30 PM) is after Monday at 06:00 (6:00 AM).

      Perhaps you want:
      [Mon 23:30;Tue 06:00],[Tue 23:30;Wed 06:00],[Wed 23:30;Thu 06:00],[Thu 23:30;Fri 06:00],[Fri 23:30;Sat 06:00],[Sat 23:30;Sun 06:00],[Sun 23:30;Mon 00:00], [Mon 00:00;Monday 06:00]

      Note the break at Midnight on Sunday, which is a limitation of .NET and has been discussed here. A schedule cannot cross Midnight on Sunday Night/Monday Morning. You have to dig a little deeper for this one.

      Comment


        #4
        Originally posted by Ltek View Post
        Thank you. Makes perfect sense I was not thinking about it proper. This would be good to put in the Easy Trigger User Manual
        Other than the .NET limitation for Sunday Night, the rest is pure 24 hour clock or military time. The day begins at 00:00 and ends at 00:00 (just after 23:59:59) there is no 24:00
        HS4 Pro, 4.2.19.0 Windows 10 pro, Supermicro LP Xeon

        Comment


          #5
          Originally posted by Ltek View Post
          I created 4 schedules just fine and then I wasted a30 min and a lot of trial and error to figure out that either there is a bug or this schedule has the same limitations that HS3 does with time management across midnight (e.g. no smarter than a 1st grader)
          Next time, before claiming something does not work, please make sure you are not the one doing something no smarter than a 1st grader

          An easy way to see how date/time should be formatted for the schedules, is to use the graphical editor. Click and drag to create a time range, then drag and drop it to move it, this way you would have seen that it works across midnight.

          Comment


            #6
            Tru... I did use the graphic editor on the first one but while it is cool, it was a bit difficult to align and takes longer than editing text and copying it in. But yes, it is nice!

            Sent from my SAMSUNG-SM-G935A using Tapatalk

            Comment

            Working...
            X