Can't get Elk to open non secure port

[bbuchanan99]

Good morning all.  I have continued my saga with not being able to connect my ISY to my elk panel.  I have concluded that my elk M1XEP is not opening the 2101 port even though it is checked in the rp software and updated and sent to the M1XEP.  Anyone ever seen this issue of not being able to open the 2101 port?  Any ideas?

 

nmap report on the M1xep address only shows ports 21, 26, and 2601 open......

 

 

[kzboray]

bbuchanan99,

 

You can assign another port number as long as it's above 1024. Start with something like port 3101 and see if that works. I would also be curious to hear what nmap shows after the change. 

 

Don't forget to change it in both ElkRP2 and ISY admin.

 

Kaz

[bbuchanan99]

Thanks Kaz..  So I did that, changed it to 2107 and nmap showed it being opened up, but I still can't connect with the ISY.  Changed it back to 2101 and nmap does not show it.  I have read all the documents related around connecting the ISY and the M1 and at one time it all worked.  I have an ISY994 pro...According to the latest documentation I should be using the secure port to connect, but everyone says use the non secure port.  Either way, neither works.  Any ideas?

[Scottmichaelj]

Thanks Kaz.. So I did that, changed it to 2107 and nmap showed it being opened up, but I still can't connect with the ISY. Changed it back to 2101 and nmap does not show it. I have read all the documents related around connecting the ISY and the M1 and at one time it all worked. I have an ISY994 pro...According to the latest documentation I should be using the secure port to connect, but everyone says use the non secure port. Either way, neither works. Any ideas?

Secure port stopped working (I won't get into specifics search for my thread) and never will. You have to use the nonsecure port. I am on v4.5.4 with Elk module and can confirm its working on the nonsecure port. Maybe file a support ticket with UDI. I personally find the Elk module lacking.

[Michel Kohanim]

Hi bbuchannan99,

 

Unfortunately you cannot use the secure port. With the non secure port, there are only very limited number of things that could prevent ISY from connecting to ELK:

1. RP is already connected

2. ELK is on a different IP/Port/Network

3. Your Access code is neither 4 nor 6 characters long

4. M1XEP firmware is not up to date

 

Not much else.

 

With kind regards,

Michel

[Scottmichaelj]

Secure port stopped working (I won't get into specifics search for my thread) and never will. You have to use the nonsecure port. I am on v4.5.4 with Elk module and can confirm its working on the nonsecure port. Maybe file a support ticket with UDI. I personally find the Elk module lacking.

Just wondering what ISY FW and XEP FW are you on? Maybe there's a correlation here that UDI is not thinking about.

[apostolakisl]

FWIW

 

I'm on 5.0.8 ISY

I have the latest XEP firmware 2.0.34

I am back a few versions on M1G, because the most up to date firmware causes random reboots of m1g, even though Brad at Elk says it doesn't  5.2.10

 

I use both the secure and non-secure port.  Though this thread made me realize I no longer need to port forward anything to Elk since I am using Agave now through ISY and don't need direct access to Elk from outside my LAN.

 

I have never had any of the issues you describe here.  This includes my current configuration but also all other combos of my previous Elk/Xep/ISY firmwares.

[bbuchanan99]

Here is my firmware info:

 

M1 Gold with a MX1EP Firmware 2.0.42 on it, and an ISY (Ver 4.5.4) with the Elk module. 

 

My biggest issue thinking this is a bug is follows:  2101 port not showing as open in nmap and elkrp can connect on both the secure port (2601) and the non secure port of 2101.  So let me ask a few other questions maybe for some constructive feedback:

 

1.  Sequence of events:  Router reboot ---> M1XEP reboot---> ISY reboot?  My ISY is set up for DHCP but gets a static IP from the router tables based on MAC Address.

2.  Access code?  Is this one of the user codes in the user/pw tab?  RP Access code as shown on opening screen of ELKRP?  I think I know what it is but can someone explicitly confirm?

3.  When I telnet into ISY the elk.cnf is of zero size.  Corrupt? or does it only store data when a connection is made?  It also does not save the configuration when I exit and re-enter the ISY admin console.

 

Any thought on any of this would be appreciated.  When it was working it was great.  Had panic button keys on all keypads in the home, with someone working from home, this gave me peace of mind knowing a simple button push sent out notifications and a great amount of noise... ..

 

Thanks all.

[Michel Kohanim]

Hi bbuchanan99 ,

 

Can you backup your ISY?

 

With kind regards,

Michel

[bbuchanan99]

apostolakisl...Where did you get firmware 5.0.8 for you ISY?

Michael,

 

Not without deleting the elk.cnf file first.  It hangs and cannot complete the zip file backup.

[Michel Kohanim]

Hi bbuchanan99,

 

That is the issue. I think it's related to firewall. Please try:

http://wiki.universal-devices.com/index.php?title=Configure_Firewall_Software

 

Then save ELK config and make sure you can backup.

 

With kind regards,

Michel

[bbuchanan99]

Michel,

 

Thank you, Thank You, Thank You...that worked....

[Scottmichaelj]

FWIW

 

I'm on 5.0.8 ISY

I have the latest XEP firmware 2.0.34

I am back a few versions on M1G, because the most up to date firmware causes random reboots of m1g, even though Brad at Elk says it doesn't  5.2.10

 

I have seen this too on a few installs. One thing thats worked for me was to go to the keypad and do a factory reset to defaults. TWICE! Just to be sure. lol bc I am OCD. Then connect and send over the file to the M1 again through the RP software. I also had a install where the keypad would randomly say "lost communications" after working for months. The factory reset "seems" to have fixed that too. Not sure why this is happening but now all my installs I do a factory reset once the system is completely installed (modules enrolled), then I config it, send it over, then do another factory reset, and send the config again. I have 3 systems in the last month now solid and no issues using this procedure.

 

FWIW v42 of the XEP FW may have issues with connection. Still investigating.

[apostolakisl]

I have seen this too on a few installs. One thing thats worked for me was to go to the keypad and do a factory reset to defaults. TWICE! Just to be sure. lol bc I am OCD. Then connect and send over the file to the M1 again through the RP software. I also had a install where the keypad would randomly say "lost communications" after working for months. The factory reset "seems" to have fixed that too. Not sure why this is happening but now all my installs I do a factory reset once the system is completely installed (modules enrolled), then I config it, send it over, then do another factory reset, and send the config again. I have 3 systems in the last month now solid and no issues using this procedure.

 

FWIW v42 of the XEP FW may have issues with connection. Still investigating.

 

Well, I'm just not going to screw with it.  I have tried twice to go to 5.3.x Elk firmware and both times had issues.  5.2.10 is very stable, no problems at all.  I don't know that a factory reset would fix it.  When you move from 5.2.x to 5.3.x the system wipes clean and you have to do a full restore from ElkRP.  Seems like a factory reset is built in to the update.

[Scottmichaelj]

Well, I'm just not going to screw with it. I have tried twice to go to 5.3.x Elk firmware and both times had issues. 5.2.10 is very stable, no problems at all. I don't know that a factory reset would fix it. When you move from 5.2.x to 5.3.x the system wipes clean and you have to do a full restore from ElkRP. Seems like a factory reset is built in to the update.

If it works dont touch it right? I have seen screwy stuff so just sharing my experience.