Just upgraded from PG2 to PG3 (trial).  It was working nicely on pg2 but I cannot get a connection to the Envisa from PG3 - I can log in via browser without issues

Any suggestions - I cannot find anything in the log file but you may see something

 

Thanks 

debug.log

I can take a look in a few days. In the meantime, make sure the PG2 node server is shut down. The EnvisaLink will only accept one socket connection.

thanks

There was an issue when installing - I was asked if I wanted to install in in the existing slot(PG2) - I said yes - and after that both pg2 and pg3 showed the node.  I deleted the PG2 node but it did not solve the issue 

 

 

From what I can see in the log, it is trying to connect to the Envisalink  at 192.168.1.251. Not ever getting to login because the initial socket connection is being refused:

evltpi_dsc:_get_next_cmd_seq: TCP Connection to EnvisaLink unexpectedly closed. Socket error: [Errno 54] Connection reset by peer

The "connection reset by peer" error message has normally been the result of another connection to the Envisalink, e.g. another version of the node server, NodeLink, or some other controller connected to the Envisalink.

If you know there is no longer another process running somewhere that is connecting to the Envisalink, then I would suggest using the web interface of the Envisalink (http://192.168.1.251) to go to "Network" settings then click "Reboot Envisalink."

Edited December 15, 20222 yr by Goose66

thanks

Let me check - In the past I had issues with rain machine devices attaching to the envisalink - It is just strange it worked until changed to PG3

Also - I can log into device from browser, but it may be a different connection type  

Yes, the browser connection is different (HTTP). The specific socket connection to port 4025 that Nodelink and the node server use is the one that allows only one connection.

I had Envisalink check - there are no devices connected on teh TPI port (4025) - it still refuses connection 

And you rebooted the EnvisaLink?

yes - even power cycled it 

I wonder if my router/firewall updated FW and somehow blocked the port (on the LAN side) - I did submit a question there as well

Are the Polisy and EnvisaLink on the same LAN? If so, then the router/firewall wouldn’t come into play. Also, if the node server couldn’t reach the EnvisLink you would get a timeout on the connect. What’s happening is the node server is connecting to the EnvisaLink and the EnvisaLink is immediately resetting the connection. I’ve only ever seen this when there is another connection to the EnvisaLink.

I somehow got it to connect - not sure what happened - maybe the Envisalink people did somehting remotely