Announcement

Collapse
No announcement yet.

Errors at plug-in startup, 3.0.0.42.

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

  • Errors at plug-in startup, 3.0.0.42.

    I'm getting three errors at plug-in startup. The ArgumentNullException seems related to weekly schedules, which I have two of and there are two errors. I've posted the schedules below, though both appear to be working correctly and show the desired windows in the GUI editor.

    EasyTrigger
    ERROR System.FormatException: Input string was not in a correct format. at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info) at System.Int32.Parse(String s) at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext() at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection) at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source) at HSPI_EasyTrigger.DeviceGroup.SetDevices(String devices)
    Dec-29 5:09:20 PM

    EasyTrigger
    ERROR System.ArgumentNullException: Value cannot be null. at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse(String s) at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots(String timeSlots)
    Dec-29 5:09:20 PM

    EasyTrigger
    ERROR System.ArgumentNullException: Value cannot be null. at HSPI_EasyTrigger.WeekScheduleTimeSlot.Parse(String s) at HSPI_EasyTrigger.WeekSchedule.SetTimeSlots(String timeSlots)


    The two schedules I presently have configured...


    [Mon Sunset-00:05;Tue 00:00],[Tue Sunset-00:05;Wed 00:00],[Wed Sunset-00:05;Thu 00:00],[Thu Sunset-00:05;Fri 00:00],[Fri Sunset-00:05;Sat 00:00],[Sat Sunset-00:05;Sun 00:00],[Sun Sunset-00:05;Mon 00:00]

    [Sun Sunset-00:10;Mon 00:00],[Mon 00:00;Mon 01:45],[Mon Sunset-00:10;Tue 01:45],[Tue Sunset-00:10;Wed 01:45],[Wed Sunset-00:10;Thu 01:45],[Thu Sunset-00:10;Fri 01:45],[Fri Sunset-00:10;Sat 01:45],[Sat Sunset-00:10;Sun 01:45]


    Current Date/Time: 12/29/2017 5:15:09 PM
    HomeSeer Version: HS3 Pro Edition 3.0.0.398
    Operating System: Microsoft Windows 10 Enterprise - Work Station
    System Uptime: 0 Days 0 Hours 6 Minutes 8 Seconds
    Number of Devices: 527
    Number of Events: 71
    Available Threads: 400
    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: Windows Defender

    Enabled Plug-Ins
    3.2.0.5: APCUPSD
    2.0.49.0: BLBackup
    3.0.0.42: EasyTrigger
    3.0.0.20: Ecobee
    3.0.0.39: EnvisaLink
    2.0.1.6: JowiHue
    3.0.0.14: NetCAM
    0.0.0.35: Pushover 3P
    3.0.6104.19146: UltraRachio3
    3.0.0.76: weatherXML
    3.0.1.173: Z-Wave

  • #2
    edit Config/EasyTrigger.ini and if you have some calendars with no values, i.e. looking something like that:

    cal=

    then delete them.

    same thing for groups

    then restart the EasyTrigger plugin

    Comment


    • #3
      Thank you, Spud, that was it. I had deleted the following objects via the UI, but they were still showing in the EasyTrigger.ini.

      [DEVICE_GROUPS]
      ExteriorLightSwitches=

      [SCHEDULES]
      OurdoorLightingMaster=
      OurdoorLighting=


      Editing the .ini allowed me to fix a couple other things I wouldn't mind putting forth for future consideration.

      The Schedule and Device Groups page appears to list the items in the order they are in the .ini file rather than say alphabetically. I was able to clean up the ordering to be alphabetical by editing the .ini.

      The ability to rename groups/schedules from the config page would also be marvelous. Those two "Ourdoor" groups were deleted because of the typo as there did not appear to be a way to rename. Now that I know the .ini file is there I could do it manually if I currently have access to the server's file system.

      Thanks and happy new year!

      Comment

      Working...
      X