Elk M1G with XEP, no remote access through Smartphone apps, works with ElkRP...

palepimp

New Member
Hello All,
 
I have a customer with an Elk M1G with the Elk XEP unit.  I have forwarded TCP port 2601 through the firewall.  I've tested with canyouseeme.org and the port is open.  I can also prove the remote access is working as I can remote into the unit using ElkRP software from outside the network to access the panel (using secure port 2601 and public DNS name).  Firmware version of the Elk M1G is 5.3.10, boot version 3.3.6, hardware version 0.13.
 
The problem lies when trying to access the panel using eKeypad for iOS devices, and also ElkDroid for Android from outside the network.  I cannot connect and receive errors each time.  The ElkDroid app reports Connect Failed: Socket Closed.  The eKeypad app reports an error (I don't have an iOS device in front of me), but it does work within the network.
 
In the devices I have tried using the public DynamicDNS hostname with port 2601, and also the public IP with port 2601.  On the eKeypad device, I have used the "failover" option with the internal IP as the backup, and it does work while on the LAN, but not from the internet.
 
I have NOT setup the insecure port 2101, as we wouldn't be using that anyway.
 
I do have a username and password setup on the panel as well.
 
I was able to get in using the Windows application M1ToGo as well from outside the network, this works as expected (as long as the access/pin code did NOT have a leading zero).
 
Forgive me as I do NOT have a background in Security systems, as I am in IT.
 
Thank you and any help would be greatly appreciated!
 
If M1TOGO and RP are both able to communicate with the Elk through the firewall then what else can it be but an eKeypad setup problem? I say double check all of the ekeypad detailed configuration settings.
 
Another thought is that maybe it would help to upgrade the XEP firmware if you are several versions behind.
 
Mike.
 
Hi Mike, and thank you for the information.
 
First off, I would like to check the XEP firmware, is that visible somewhere in the ElkRP2 client?
 
Also, the strange thing is is that i have used the Android app and the iOS on 2 different devices with still no luck.  I think I am going to download the eKeypad app on my iPad and test it there as well (I will post back and info).  Unfortunately the owner is the one with the iPhone app, and I don't always have access to his phone to test.  I just keep asking him to "try again" after I make any changes, always with a "still not working" response.
 
Either way, thank you!  I will test and reply back.
 
To see the XEP firmware as well as other device versions you have to connect to the panel with RP2 and go to "Send/Receive" >  "Enroll/Update"
 
Have you checked the gateway address, port number, username and passwod in ekeypad?
 
OK, so I downloaded the eKeypad M1 for my iPad and configured the connection settings.  I actually got in right away avoiding the "Use Failover" option (I'm offsite).  I then configured the failover with the internal IP and secure port, and spit out the error we were seeing before.  I then changed the "Use Failover" option to "Use Timeout" instead of "Try to Detect".  It connected that time right away.  I'm not sure if this will work while I am on the LAN, but I will find out next week when I am there.
 
I think part of this problem as due to the Failover settings, but also I believe the owner kept his eKeypad app the same and moved into a new house.  He purchased a new Elk M1G and kept using the same device configuration in his app, modifying the connection info.  We moved his internal network to the new home, but the panel was new.  I'm going to have him create a new "System Device" on his phone if he has any problems connecting.
 
I'm going to mark your reply as the answer Mike, since you pinpointed that it had to be in the config on the eKeypad app.  Thank you for pointing me in the right direction.
 
I tried to use the fail-over option when I first installed ekeypad and had trouble. I set up the Wide Area Network as the primary connection and the LAN as a fail-over and couldn't get it to work. When I contacted Jayson (ekeypad support) he steered me away from using the fail-over. I don't know why but he pushed me away from using it. I felt that maybe it was buggy and he didn't want to admit it but if he was strongly against using it I could save a lot of time by taking his advice.
 
I was disappointed but it's no big deal because I can use m1togo for lan connection if necessary. That was many software upgrades ago, has anyone setup fail-over successfully?
 
Mike.
 
EDIT
 
Also be aware that ekeypad can export and import configuration files. You can take your time setting up the system on your IOS device and then just transfer it to his.
 
palepimp said:
I think part of this problem as due to the Failover settings, but also I believe the owner kept his eKeypad app the same and moved into a new house.  He purchased a new Elk M1G and kept using the same device configuration in his app, modifying the connection info.  We moved his internal network to the new home, but the panel was new.  I'm going to have him create a new "System Device" on his phone if he has any problems connecting.
 
Have the owner create a new customer account in elkrp2, log in to the panel and receive all from the panel to elkrp. There is no point in trying to use the customer account from another system.
 
Back
Top