Announcement

Collapse
No announcement yet.

Bootup errors with HS3 beta 383

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

    Bootup errors with HS3 beta 383

    Hi Spud

    I just upgraded to HS3 beta 383 and found 2 errors in my logs during EasyTrigger initialisation.

    Nov-09 9:45:37 PM Plug-In Finished initializing plug-in EasyTrigger
    Nov-09 9:45:37 PM EasyTrigger INFO Found 0 device group value triggers
    Nov-09 9:45:37 PM EasyTrigger INFO Refreshing list of device group value triggers to monitor
    Nov-09 9:45:37 PM EasyTrigger INFO Found 0 random triggers
    Nov-09 9:45:37 PM EasyTrigger INFO Refreshing list of random triggers to monitor
    Nov-09 9:45:37 PM EasyTrigger INFO Found 12 schedule triggers
    Nov-09 9:45:37 PM EasyTrigger INFO Refreshing list of schedule triggers to monitor
    Nov-09 9:45:37 PM EasyTrigger INFO Found 0 device's value conditions that need monitoring
    Nov-09 9:45:37 PM EasyTrigger INFO Found 0 device's value triggers
    Nov-09 9:45:37 PM EasyTrigger INFO Refreshing list of device's value triggers to monitor
    Nov-09 9:45:37 PM EasyTrigger INFO Found 0 device's string triggers
    Nov-09 9:45:37 PM EasyTrigger INFO Refreshing list of device's string triggers to monitor
    Nov-09 9:45:34 PM EasyTrigger ERROR System.FormatException: Input string was not in the correct format at System.Int32.Parse (System.String s) [0x00000] in :0 at System.Linq.Enumerable+c__Iterator10`2[System.String,System.Int32].MoveNext () [0x00000] in :0 at System.Collections.Generic.List`1[System.Int32].AddEnumerable (IEnumerable`1 enumerable) [0x00000] in :0 at System.Collections.Generic.List`1[System.Int32]..ctor (IEnumerable`1 collection) [0x00000] in :0 at System.Linq.Enumerable.ToList[Int32] (IEnumerable`1 source) [0x00000] in :0 at HSPI_EasyTrigger.DeviceGroup.SetDevices (System.String devices) [0x00000] in :0
    Nov-09 9:45:34 PM EasyTrigger ERROR System.ArgumentNullException: Argument cannot be null. at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse (System.String s) [0x00000] in :0 at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots (System.String timeSlots) [0x00000] in :0

    Nov-09 9:45:34 PM EasyTrigger INFO EasyTrigger version 3.0.0.40
    Nov-09 9:45:34 PM Info Plugin EasyTrigger has connected. IP:127.0.0.1:44317
    This error was not present in earlier HS3 betas. I just came from beta 382.

    Any idea what the error is related to?

    ----------------------------------------------------
    Current Date/Time: 11/9/2017 9:55:33 PM
    HomeSeer Version: HS3 Standard Edition 3.0.0.383
    Linux version: Linux hometrollerSEL 3.16.0-031600-generic #201408031935 SMP Sun Aug 3 23:56:17 UTC 2014 i686 i686 i686 GNU/Linux System Uptime: 0 Days 0 Hours 10 Minutes 13 Seconds
    IP Address: 192.168.100.101
    Number of Devices: 432
    Number of Events: 228
    Available Threads: 199
    HSTouch Enabled: True
    Event Threads: 0
    Event Trigger Eval Queue: 0
    Event Trigger Priority Eval Queue: 0
    Device Exec Queue: 0
    HSTouch Event Queue: 0
    Email Send Queue: 0
    Anti Virus Installed:

    Enabled Plug-Ins
    2.0.48.0: BLBackup
    2.0.35.0: BLLAN
    2.0.10.0: BLPlex
    3.0.0.8: Chromecast
    3.0.0.5: CM15A
    1.0.0.0: drhsEventEnabler
    3.0.0.40: EasyTrigger
    3.0.1.109: PHLocation
    3.0.4.8: SDJ-Health
    3.0.5917.35093: UltraLog3
    3.0.6413.20219: UltraNetCam3
    3.0.1.152: Z-Wave

    #2
    Please post the content of your EasyTrigger.ini file. Thanks

    Comment


      #3
      Originally posted by spud View Post
      Please post the content of your EasyTrigger.ini file. Thanks
      Here you go ...

      [SCHEDULES]
      WaterFalls=[Mon 06:30;Mon 08:00],[Tue 06:30;Tue 08:00],[Wed 06:30;Wed 08:00],[Thu 06:30;Thu 08:00],[Fri 06:30;Fri 08:00],[Sat 07:00;Sat 08:30],[Sun 07:00;Sun 08:30],[Mon 11:00;Mon 12:30],[Tue 11:00;Tue 12:30],[Wed 11:00;Wed 12:30],[Thu 11:00;Thu 12:30],[Fri 11:00;Fri 12:30],[Sat 11:00;Sat 12:30],[Sun 11:00;Sun 12:30],[Mon 17:45;Mon 19:30],[Tue 17:45;Tue 19:30],[Wed 17:45;Wed 19:30],[Thu 17:45;Thu 19:30],[Fri 17:45;Fri 19:30],[Sat 17:45;Sat 20:00],[Sun 17:45;Sun 20:00]
      WaterPumpBottom=[Mon 05:00;Mon 10:00],[Mon 10:01;Mon 16:00],[Mon 16:01;Tue 00:00],[Tue 05:00;Tue 10:00],[Tue 10:01;Tue 16:00],[Tue 16:01;Wed 00:00],[Wed 05:00;Wed 10:00],[Wed 10:01;Wed 16:00],[Wed 16:01;Thu 00:00],[Thu 05:00;Thu 10:00],[Thu 10:01;Thu 16:00],[Thu 16:01;Fri 00:00],[Fri 05:00;Fri 10:00],[Fri 10:01;Fri 16:00],[Fri 16:01;Sat 00:00],[Sat 05:00;Sat 10:00],[Sat 10:01;Sat 16:00],[Sat 16:01;Sun 00:00],[Sun 05:00;Sun 10:00],[Sun 10:01;Sun 16:00],[Sun 16:01;Mon 00:00]
      HomeSeerBackup=[Sun 00:00;Sun 01:05],[Wed 23:00;Wed 23:55]
      KidsWakeUpTime=[Mon 06:00;Mon 07:05],[Tue 06:00;Tue 07:05],[Wed 06:00;Wed 07:10],[Thu 06:00;Thu 07:05],[Fri 06:00;Fri 07:05],[Sat 06:45;Sat 07:45]
      KidsBedtime=[Mon 21:30;Mon 22:40],[Tue 21:30;Tue 22:35],[Wed 21:30;Wed 22:45],[Thu 21:30;Thu 22:40],[Fri 21:30;Fri 22:40],[Sat 21:45;Sat 22:50],[Sun 21:30;Sun 22:40]
      GoogleHomeSpeakers=[Mon 07:00;Mon 21:00],[Tue 07:00;Tue 21:00],[Wed 07:00;Wed 21:00],[Thu 07:00;Thu 21:05],[Fri 07:05;Fri 21:00],[Sat 07:10;Sat 21:00],[Sun 07:00;Sun 21:00]
      KidsBathTime=[Thu 17:30;Thu 19:00],[Mon 18:00;Mon 19:00],[Tue 18:00;Tue 19:05],[Wed 18:00;Wed 18:55],[Fri 18:00;Fri 18:55],[Sat 18:00;Sat 19:00],[Sun 18:00;Sun 19:05]
      Test=
      [DEVICE_GROUPS]
      Test=

      Comment


        #4
        delete the "Test=" line in both [SCHEDULES] and [DEVICE_GROUPS] section then restart the plugin.

        Comment


          #5
          Originally posted by spud View Post
          delete the "Test=" line in both [SCHEDULES] and [DEVICE_GROUPS] section then restart the plugin.
          That fixed it. Thanks.

          So it would appear that the schedule is not being deleted cleanly from the ini file. I deleted that test schedule from the plugin config interface about a week ago.

          Comment


            #6
            Originally posted by abwyatt View Post
            That fixed it. Thanks.

            So it would appear that the schedule is not being deleted cleanly from the ini file. I deleted that test schedule from the plugin config interface about a week ago.
            yeah there was some bugs introduced in some of the HS3 beta versions when dealing with ini files. I believe they have been fixed now. Could you try it with .383, i.e create a non empty schedule, make sure it is written to the ini, then delete it, and make sure it is deleted from the ini. Thanks

            Comment


              #7
              Originally posted by spud View Post
              yeah there was some bugs introduced in some of the HS3 beta versions when dealing with ini files. I believe they have been fixed now. Could you try it with .383, i.e create a non empty schedule, make sure it is written to the ini, then delete it, and make sure it is deleted from the ini. Thanks
              Appears the bug is still there with 383. It deleted the values but left the schedule name in the ini file.

              Comment


                #8
                I reported the problem to Rich, and he fixed it in version 3.0.0.384

                You will still need to manually delete the "Key=" lines in your ini if you have some.

                Comment

                Working...
                X