Jump to content

ELK ERROR connection:connection_lost: [Errno 54] Connection reset by peer

Bob Gratton

By Bob Gratton
in ELK

Go to solution Solved by DennisC,

Recommended Posts

Bob Gratton Member

Bob Gratton

Posted
Posted

Hi all,
I'm still using my ISY994 with ELK module. In the process of finally migrating from the 994 to IoP, I installed PG3 and got the ELK NS.

I managed to transfer the other NS I had on PG2 to PG3 with minimal issues, but I'm having a hard with this one (I did not have the ELK NS installed on PG2).

In the AC, I have only the "ELK Controller" node related to this NS. The NS is connected (Node Server Online : Connected), but the M1XEP Status keeps flip flopping between "Connected" and "Disconnected" every couple seconds.

Here what's in the log. The same lines repeat constantly with the "WARNING" line coming once a while: 

2023-02-22 20:22:21,664 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:26,245 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:26,246 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:30,669 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:30,671 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:33,232 Thread-9   udi_interface      WARNING  Controller:handler_poll: waiting for sync and node initialization to complete
2023-02-22 20:22:35,189 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:35,191 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:39,612 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:39,614 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:44,247 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:44,249 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:48,750 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:48,752 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:53,201 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None

My ISY994 is on the last release (V5.3.4) and PG3 is on V3.1.17
I do not have ELKRP2 or any other device connected to the M1XEP (I disable the ELK module from the 994 when testing)

Any ideas?
Thanks

  • Solution
DennisC Advanced

DennisC

Posted
  • Solution
Posted
21 minutes ago, Bob Gratton said:

Hi all,
I'm still using my ISY994 with ELK module. In the process of finally migrating from the 994 to IoP, I installed PG3 and got the ELK NS.

I managed to transfer the other NS I had on PG2 to PG3 with minimal issues, but I'm having a hard with this one (I did not have the ELK NS installed on PG2).

In the AC, I have only the "ELK Controller" node related to this NS. The NS is connected (Node Server Online : Connected), but the M1XEP Status keeps flip flopping between "Connected" and "Disconnected" every couple seconds.

Here what's in the log. The same lines repeat constantly with the "WARNING" line coming once a while: 

2023-02-22 20:22:21,664 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:26,245 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:26,246 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:30,669 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:30,671 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:33,232 Thread-9   udi_interface      WARNING  Controller:handler_poll: waiting for sync and node initialization to complete
2023-02-22 20:22:35,189 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:35,191 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:39,612 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:39,614 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:44,247 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:44,249 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:48,750 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None
2023-02-22 20:22:48,752 ELK-13418  elkm1_lib.connection WARNING  connection:_disconnected_callback: ElkM1 at elk://192.168.135.120:2601 disconnected
2023-02-22 20:22:53,201 ELK-13418  elkm1_lib.connection ERROR    connection:connection_lost: [Errno 54] Connection reset by peer
NoneType: None

My ISY994 is on the last release (V5.3.4) and PG3 is on V3.1.17
I do not have ELKRP2 or any other device connected to the M1XEP (I disable the ELK module from the 994 when testing)

Any ideas?
Thanks

You need to use the non secure port to connect with the M1XEP. I am not home and don't remember which port is which, but I do remember it tells you in the M1XEP.

DennisC Advanced

DennisC

Posted
Posted

Here are the instructions for setting up the Elk Node server on the configuration page. Note the port :2101 after the IP address.

To Configure the ELK Node Server

Set temperature_unit to F or C

Set host to the host or ip address and port, e.g. 192.168.1.15:2101

Set user_code, suggested to create a unique usercode for this Node Server

Set areas to the range of areas you would like to include

Set outputs to the range of outputs to include

Set change_node_names to true makes ELK the source of node names so if they are changed then ISY names will be changed to match.

A range can be comma seperated to include just those numbers, or seperated with a dash to include numbers in between. For example 1-3,5,7-8 will be 1,2,3,5,7,8 All ranges start at one just like the numbering the Elk uses.

 

Note that if you remove an Area, it will not be removed from the ISY or Polyglot. This is intentional just in case it's an accident and your scenes or programs the reference the nodes. You can go to the Nodes Page in the Polyglot UI and delete them using the X to the right of the node.

 

When any value is changed you must restart the Node Server for it to take affect.

Bob Gratton Member

Bob Gratton

Posted
  • Author
Posted

Thanks Dennis, that was it. Nodes are currently populating..

I'm mad at myself cause I knew I needed to use the non secure port and I thought I had confirmed.

Thanks again!

Guest
This topic is now closed to further replies.
Go to topic listing
×
×
  • Create New...