Announcement

Collapse
No announcement yet.

ISY Error Trigger Communication Error

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

    ISY Error Trigger Communication Error

    I started noticing these in my logs tonight as well.
    Code:
    Mar-07 21:53:27     ISYInsteon   TriggerEventHandler : TRIGGER: ISY Error Trigger Communication Error       Mar-07 21:53:27     ISYInsteon   RaiseTriggers : ----> Watchdog timeout.       Mar-07 21:53:27     ISYInsteon   watchdog timeout occured.       Mar-07 21:53:27     ISYInsteon   Add : Event added to queue. Queue size = 1       Mar-07 21:53:18     Blue-Iris   Successfully logged in to BlueIris server: Unnamed (ver 4.8.5.1) as john.       Mar-07 21:52:27     ISYInsteon   Event Queue is now empty.       Mar-07 21:52:27     ISYInsteon   QueueLoop : Event removed from queue. Queue size = 0       Mar-07 21:52:27     ISYInsteon   TriggerEventHandler : TRIGGER: Searching full trigger list for match.       Mar-07 21:52:27     ISYInsteon   TriggerEventHandler : Reason [Communication Error] Trigger [ISY_COMM_ERROR] Data [] instance []       Mar-07 21:52:27     ISYInsteon   TriggerEventHandler : TRIGGER: ISY Error Trigger Communication Error       Mar-07 21:52:27     ISYInsteon   RaiseTriggers : ----> Watchdog timeout.       Mar-07 21:52:27     ISYInsteon   watchdog timeout occured.       Mar-07 21:52:27     ISYInsteon   Add : Event added to queue. Queue size = 1       Mar-07 21:51:27     ISYInsteon   Event Queue is now empty.       Mar-07 21:51:27     ISYInsteon   QueueLoop : Event removed from queue. Queue size = 0       Mar-07 21:51:27     ISYInsteon   TriggerEventHandler : TRIGGER: Searching full trigger list for match.       Mar-07 21:51:27     ISYInsteon   TriggerEventHandler : Reason [Communication Error] Trigger [ISY_COMM_ERROR] Data [] instance []       Mar-07 21:51:27     ISYInsteon   TriggerEventHandler : TRIGGER: ISY Error Trigger Communication Error       Mar-07 21:51:27     ISYInsteon   RaiseTriggers : ----> Watchdog timeout.       Mar-07 21:51:27     ISYInsteon   watchdog timeout occured.       Mar-07 21:51:27     ISYInsteon   Add : Event added to queue. Queue size = 1       Mar-07 21:51:14     Blue-Iris   Successfully logged in to BlueIris server: Unnamed (ver 4.8.5.1) as john.       Mar-07 21:50:27     ISYInsteon   Event Queue is now empty.       Mar-07 21:50:27     ISYInsteon   QueueLoop : Event removed from queue. Queue size = 0       Mar-07 21:50:27     ISYInsteon   TriggerEventHandler : TRIGGER: Searching full trigger list for match.       Mar-07 21:50:27     ISYInsteon   TriggerEventHandler : Reason [Communication Error] Trigger [ISY_COMM_ERROR] Data [] instance []       Mar-07 21:50:27     ISYInsteon   TriggerEventHandler : TRIGGER: ISY Error Trigger Communication Error       Mar-07 21:50:27     ISYInsteon   RaiseTriggers : ----> Watchdog timeout.       Mar-07 21:50:27     ISYInsteon   watchdog timeout occured.
    Neither code tags or html tags is formatting that into readable content... uughh...

    #2
    The plug-in is supposed to have a constant connection to the ISY via the ISY subscription channel. The ISY should be sending data, including a heartbeat message at a fairly constant rate. If the plug-in doesn't see anything from the ISY after 60 seconds, it assumes something is wrong and creates a trigger event for HomeSeer.

    It looks like something has happened to that connection and it is raising triggers to notify that the connection to the ISY is not working.

    The plug-in should have attempted to restart the connection, but possibly that failed also and now it is running with a closed connection. The only recourse would be to restart the plug-in.
    --
    Bob Paauwe
    ISYInsteon Plug-in
    http://www.bobsplace.com/ISYInsteon/

    Comment


      #3
      Originally posted by bpwwer View Post
      The plug-in is supposed to have a constant connection to the ISY via the ISY subscription channel. The ISY should be sending data, including a heartbeat message at a fairly constant rate. If the plug-in doesn't see anything from the ISY after 60 seconds, it assumes something is wrong and creates a trigger event for HomeSeer.

      It looks like something has happened to that connection and it is raising triggers to notify that the connection to the ISY is not working.

      The plug-in should have attempted to restart the connection, but possibly that failed also and now it is running with a closed connection. The only recourse would be to restart the plug-in.
      I've restarted... a lot

      After running for a few minutes I get that error repeated in the logs.

      Comment

      Working...
      X