Panda88 Posted December 16, 2023 Posted December 16, 2023 Hi I have 2 system setup. One is working flawless and the other has issues on and off. I though there may be issues with the envisalink so I ordered a new one but it remains the same. It sometimes will not start - it retrieves the system (all nodes etc so it must be talking to the envisalink) but when it comes to panel1 it states there is no connection - some times it manages to get by this state and I will work ok Any idea log: 2023-12-16 14:54:08,500 Thread-51 udi_interface DEBUG nslib:start: In start() for node panel1... 2023-12-16 14:54:08,502 Command udi_interface.interface DEBUG interface:_handleResult: add node response: {'id': '53aad9c8-a83b-4776-9cc5-bd7b5a272909', 'uuid': '00:0d:b9:52:d9:38', 'profileNum': 5, 'address': 'panel1', 'name': 'Alarm Panel', 'nodeDefId': 'PANEL', 'nls': None, 'hint': '16843008', 'controller': 0, 'primaryNode': 'panel1', 'private': None, 'isPrimary': 1, 'enabled': 1, 'timeAdded': 1677029040739, 'timeModified': 1702767248422, 'dbVersion': 1} 2023-12-16 14:54:32,144 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:54:32,146 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:54:32,147 Thread-52 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:54:32,149 Thread-52 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:54:32,150 Thread-52 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:54:32,150 Thread-52 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:54:32,153 Thread-52 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:54:32,154 Thread-52 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:54:32,155 Thread-52 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:54:32,157 Thread-52 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:54:32,158 Thread-52 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:54:32,159 Thread-52 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:54:32,160 Thread-52 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:54:32,161 Thread-52 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-16 14:54:32,163 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'panel1', 'driver': 'ST', 'value': '0', 'uom': 2, 'text': None}]} 2023-12-16 14:54:32,165 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'key': 'notices', 'value': {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'}}]} 2023-12-16 14:54:32,449 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-12-16 14:54:32,451 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-12-16 14:54:32,452 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'} 2023-12-16 14:54:32,453 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking no_connect / Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. 2023-12-16 14:54:32,489 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-16 14:54:32,492 MQTT udi_interface.interface INFO interface:_message: Successfully set panel1 :: ST to 0 UOM 2 2023-12-16 14:55:02,124 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:55:02,126 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:55:02,127 Thread-53 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:55:02,129 Thread-53 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:55:02,130 Thread-53 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:55:02,131 Thread-53 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:55:02,133 Thread-53 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:55:02,134 Thread-53 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:55:02,135 Thread-53 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:55:02,136 Thread-53 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:55:02,137 Thread-53 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:55:02,138 Thread-53 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:55:02,139 Thread-53 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:55:02,140 Thread-53 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot. 2023-12-16 14:55:02,144 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': 'panel1', 'driver': 'ST', 'value': '0', 'uom': 2, 'text': None}]} 2023-12-16 14:55:02,147 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'key': 'notices', 'value': {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'}}]} 2023-12-16 14:55:02,260 MQTT udi_interface.interface INFO interface:_message: Successfully set panel1 :: ST to 0 UOM 2 2023-12-16 14:55:02,302 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message notices 2023-12-16 14:55:02,305 MQTT udi_interface.interface INFO interface:_message: Successfully set key = notices 2023-12-16 14:55:02,305 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING notices 2023-12-16 14:55:02,308 Command udi_interface.custom DEBUG custom:load: CUSTOM: load {'no_connect': 'Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver.'} 2023-12-16 14:55:02,309 Command udi_interface.custom DEBUG custom:load: CUSTOM: -- checking no_connect / Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. 2023-12-16 14:55:32,130 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message shortPoll 2023-12-16 14:55:32,131 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING shortPoll 2023-12-16 14:55:32,133 Thread-54 udi_interface DEBUG evldscns:shortPoll: In shortPoll()... 2023-12-16 14:55:32,135 Thread-54 udi_interface INFO nodes:shortPoll: Establishing connection to EnvisaLink device... 2023-12-16 14:55:32,135 Thread-54 udi_interface DEBUG evltpi_dsc:_connect_evl: Connecting to EnvisaLink device... 2023-12-16 14:55:32,136 Thread-54 udi_interface DEBUG evltpi_dsc:_connect: In connect()... 2023-12-16 14:55:32,138 Thread-54 udi_interface DEBUG evltpi_dsc:_get_next_cmd_seq: In _get_next_cmd_seq()... 2023-12-16 14:55:32,139 Thread-54 udi_interface ERROR evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer 2023-12-16 14:55:32,140 Thread-54 udi_interface ERROR evltpi_dsc:_connect_evl: Invalid sequence received from EnvisaLink upon connection: None 2023-12-16 14:55:32,142 Thread-54 udi_interface.node DEBUG node:setDriver: panel1:Alarm Panel Reporting set ST to 0 to Polyglot 2023-12-16 14:55:32,143 Thread-54 udi_interface.node DEBUG node:reportDriver: Updating value to 0 2023-12-16 14:55:32,143 Thread-54 udi_interface WARNING nodes:shortPoll: Could not connect to EnvisaLink device at 192.168.2.223. 2023-12-16 14:55:32,144 Thread-54 udi_interface.custom DEBUG custom:__setitem__: CUSTOM: no_connect = Could not connect to EnvisaLink device. Please check the network and Custom Configuration Parameter values for the nodeserver. ...saving 2023-12-16 14:55:32,145 Thread-54 udi_interface.custom INFO custom:_save: Sending data notices to Polyglot.
Goose66 Posted December 17, 2023 Posted December 17, 2023 Is it possible that something else is trying to connect to this EnvisaLink? Many times in the past the node server has exhibited the “connection reset by peer” error because another node server, version of PG2, NodeLink, or something else was attempting to connect to the EnvisaLink. The EnvisaLink can only have one UDP socket connection at a time.
Panda88 Posted December 17, 2023 Author Posted December 17, 2023 I doubt it - unless the web interface which I assume is operating on a different port
Recommended Posts