Announcement

Collapse
No announcement yet.

EnvisaLink Socket error

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

  • EnvisaLink Socket error

    Hello Spud,

    One of my lighting events is based on a DSC door/window sensors being opened and last night the event didn't trigger. When I checked the HS Log it shows an EnvisaLink Socket error:

    Dec-05 8:39:33 PM EnvisaLink INFO 3rd Garage Door status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Side Main Garage Door status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Upstairs Motion status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Downstairs Motion status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Guestroom Window status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Familyroom Window3 status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Familyroom Window2 status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Familyroom Window1 status change: Closed
    Dec-05 8:39:33 PM EnvisaLink INFO Familyroom Glass Break status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Kitchen Sliding Door status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Kitchen Window status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Diningroom Window3 status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Diningroom Window2 status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Diningroom Window1 status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Livingroom Sliding Door2 status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Livingroom Sliding Door1 status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Garage Entry status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Front Entry status change: Closed
    Dec-05 8:39:32 PM EnvisaLink INFO Reconnection OK
    Dec-05 8:39:32 PM EnvisaLink INFO Trying to reconnect to: 192.168.X.XX:XXXX
    Dec-05 8:39:21 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
    Dec-05 8:39:21 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
    Dec-05 8:39:21 PM EnvisaLink INFO Reconnection OK
    Dec-05 8:39:21 PM EnvisaLink INFO Trying to reconnect to: 192.168.X.XX:XXXX
    Dec-05 8:39:10 PM EnvisaLink INFO Connection Lost, will try to reconnect in 10 seconds
    Dec-05 8:39:10 PM EnvisaLink ERROR Receiver::Run() A socket error has occured: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.

    After I checked the log, the plugin had time to restart and the event started working properly again, so I just wanted to see if this has anything to do with the plugin or if it's an EnvisaLink4 issue?
    HS3 3.0.0.500 &HSTouch Designer 3.0.71 with 782 Devices, 479 Events
    Plugin's:
    BLBackup, BLOccupied, BLShutdown, EasyTrigger, Ecobee,
    EnvisaLink DSC, PHLocation, Pushover, SONOS, Blue Iris, UltraRachio3,
    weatherXML, Jon00 Alexa Helper, Network Monitor, Z-Wave 3.0.1.252

  • #2
    This error happens when the connection is lost (the EVL4 drop the connection or there is a problem on your network). As long as it does not happen too often and that the plugin reconnect successfully, you can ignore it.

    Comment

    Working...
    X