Announcement

Collapse
No announcement yet.

Callback Error?

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

    Callback Error?

    Frequently getting this in the log...

    ERROR HSEvent callback. '0' is not a valid value for 'Interval'. 'Interval' must be greater than 0.

    ... I'm not using Easy Trigger in any Events.

    Debug...

    Jul-08 12:10:18 AM EasyTrigger DEBUG Device 386 value changed from 15933 to 15934
    Jul-08 12:10:18 AM EasyTrigger DEBUG Device 243 value changed from 15931 to 15932
    Jul-08 12:10:18 AM EasyTrigger DEBUG Device 217 value changed from 20666 to 20667
    Jul-08 12:10:12 AM EasyTrigger DEBUG Device 151 value changed from 255 to 0
    Jul-08 12:10:12 AM Z-Wave Device: Basement Office Motion Set to Off/Closed/No Motion
    Jul-08 12:10:04 AM EasyTrigger DEBUG Device 151 value changed from 0 to 255
    Jul-08 12:10:04 AM Z-Wave Device: Basement Office Motion Set to On/Open/Motion
    Jul-08 12:09:48 AM EasyTrigger DEBUG Device 151 value changed from 255 to 0
    Jul-08 12:09:48 AM Z-Wave Device: Basement Office Motion Set to Off/Closed/No Motion
    Jul-08 12:09:44 AM EasyTrigger DEBUG Stack: at System.Timers.Timer.set_Interval(Double value) at HSPI_EasyTrigger.EasyTriggerApp.RestartDeviceValueHasNotChan gedTrigger(DeviceValueTrigger valueTrigger, Boolean forceRestart) at HSPI_EasyTrigger.EasyTriggerApp.HSEvent(HSEvent eventType, Object[] parms)
    Last edited by Ltek; July 8, 2017, 01:13 AM.

    #2
    Are you sure you don't have an event configured with "This device's value has NOT changed for exactly..." as the trigger?
    It looks like the plug-in is seeing one, which is not configured with a valid interval.

    Set the log level to debug and restart the plug-in, do you still see this error?

    Comment


      #3
      Originally posted by spud View Post
      Are you sure you don't have an event configured with "This device's value has NOT changed for exactly..." as the trigger?
      It looks like the plug-in is seeing one, which is not configured with a valid interval.

      Set the log level to debug and restart the plug-in, do you still see this error?
      I don't remember doing that... is there a way to see a list of Events where ET is being used?

      Comment


        #4
        Originally posted by Ltek View Post
        I don't remember doing that... is there a way to see a list of Events where ET is being used?
        unfortunately no, but when you start the EasyTrigger plugin it will write in the logs how many trigger of each category it has found:, i.e "Found X device's value triggers"

        Comment


          #5
          yup, no events use Easy Trigger (see below), I havent yet explored it to see how I'd use it. But I've not seen the error today either... very odd.

          Jul-12 4:48:41 PM Plug-In Finished initializing plug-in EasyTrigger
          Jul-12 4:48:40 PM EasyTrigger INFO Found 0 random triggers
          Jul-12 4:48:40 PM EasyTrigger INFO Refreshing list of random triggers to monitor
          Jul-12 4:48:40 PM EasyTrigger INFO Found 0 schedule triggers
          Jul-12 4:48:40 PM EasyTrigger INFO Refreshing list of schedule triggers to monitor
          Jul-12 4:48:40 PM EasyTrigger INFO Found 0 device's value triggers
          Jul-12 4:48:40 PM EasyTrigger INFO Refreshing list of device's value triggers to monitor
          Jul-12 4:48:40 PM EasyTrigger INFO Found 0 device's string triggers
          Jul-12 4:48:40 PM EasyTrigger INFO Refreshing list of device's string triggers to monitor
          Jul-12 4:48:40 PM EasyTrigger INFO EasyTrigger version 3.0.0.32
          Jul-12 4:48:39 PM Info Plugin EasyTrigger has connected. IP:127.0.0.1:54875
          Jul-12 4:48:39 PM Plug-In Interface EasyTrigger is running as a trial, 10 days remaining.
          Jul-12 4:48:29 PM Info Plugin EasyTrigger with instance: has disconnected
          Jul-12 4:48:29 PM Plug-In Shutting down Plug-In: EasyTrigger

          Comment


            #6
            Originally posted by Ltek View Post
            yup, no events use Easy Trigger (see below), I havent yet explored it to see how I'd use it. But I've not seen the error today either... very odd.
            Since an Event using this Easy Trigger trigger cannot be collapsed (completed) until the interval is set, it may not show up as an Easy Trigger Event in the log until the interval is set.
            HS4 Pro, 4.2.19.16 Windows 10 pro, Supermicro LP Xeon

            Comment

            Working...
            X