Defective M1XEP?

reko19

Active Member
Attempting to communicate with my M1 from the outside world using Ekeypad M1. Port forwarded to 2601, It connected properly, list of zones, keypads, area name is all correct. Got ready to arm indication. However for some reason when I faulted a zone I wasn't able to see it thru the app. I restarted the app, still did not show a faulted zone but indicated "not ready to arm". Took a zone fault out, nothing on ekeypad pro, still not ready to arm. As soon as I reboot M1XEP I was able to arm the system and see "armed". To disarm the system I had to reboot M1XEP again. Bottom line after M1 changes state I have to reboot M1XEP to gain control from my iPhone. As soon as the state changes I loose my com until next M1XEP reboot. No issues using ElkRP2 with direct connect over Rs232 or over LAN. Although to establish initial communication I had to reboot M1XEP once.

Any ideas? Thanks.
 
What about when you are inside your LAN? Try setting up ekeypad to use your local wifi and local ip address. If it works in that environment then the problem would likely be with your routing
 
What about when you are inside your LAN? Try setting up ekeypad to use your local wifi and local ip address. If it works in that environment then the problem would likely be with your routing
same deal while on my LAN, mind you ElkRP2 works fine after that first initial reboot.
 
Did you enable all the globals (g29-g42) on the serial port on the M1 per the eKeypad setup guide? Those are not enabled by default and are what allows the M1 to send proactive updates to clients like eKeypad.
 
Did you enable all the globals (g29-g42) on the serial port on the M1 per the eKeypad setup guide? Those are not enabled by default and are what allows the M1 to send proactive updates to clients like eKeypad.
nope, this might be it looking into what the heck g29-g42 are...thanks
 
Follow the instructions here http://www.ekeypad.net/eK_Family/Downloads_files/eK%20M1%20-%20Config%20Guide.pdf
 
Back
Top