RJ45 8-pin Network Jack. – mm barrel type power connector (center positive). – LED Indicators for Power, Link, and Data. ELK-M1XEP Manual. The Elk M1XEP is the ethernet interface for the Elk M1 alarm panel. This allows users or programmers to access the device remotely over the internet. The ELK-M1XEP is an Ethernet Device Server with a RS Serial Port Interface . It may be used to connect a Control in the M1 Family to an Ethernet network.
|Published (Last):||13 February 2017|
|PDF File Size:||14.13 Mb|
|ePub File Size:||18.8 Mb|
|Price:||Free* [*Free Regsitration Required]|
The ELK M1 has a defined serial protocol.
ELK M1 Interface – Third party integrations – Home Assistant Community
Link to an older version of the spec: It can be programmed to send updates over serial on events i. That should be straightforward, I think….
Does anyone know of something similar in Home Assistant that I could use as a starting point? I agree, this tool would be a lot more helpful with ELK integration…I just dont know where to start. If you want to interface to the Elk M1 over ethernet, I el, some people have already got this working: It was actually much easier than I was thinking. PS, is there any way to private message on this forum?
ELK-M1XEP M1 Ethernet Interface
If you send me your e-mail address I will forward you the e-mail I got from Elk. Another person at Elk just pointed me here: I have created a pull request to the Elk github project to enable the generation of the python3 library.
At some point when I get an Elk M1 I will use this to integrate with home-assistant. This is a really cool project and im interested in checking it out as soon as I am able flk try it. It would be faster and would support more than one RP connected to the ELK M1, if I understand the benefits of rs over rs correctly. This might be something to look into, but more complicated.
In particular, the messages the ellk around on the RS bus do not correspond to the messages on the serial interface and which also appear on the Ethernet interface over a TCP connection.
I looked briefly at this, and the messages use 9 bit bytes which is not uncommon for RS buses; bytes slk the 9th bit set are used to denote an address, and some UART devices can be configured to match on this and generate an interrupt or other attention signal.
I think the right way forward is using the API documentation for the serial messages.
Just pinging this thread, are there any seasoned HASS developers interested in pursuing this integration? Look at the M1XEP as a simple “pass-through” device. These messages simply pass through the XEP to the M1 and vice-versa.
The protocol is available for download from our web site http: Timing here is tricky, because you must type the whole rlk in-between receiving messages. A program could easily do it, though.
Troubleshooting Guide – Elk -M1XEP Installation Manual [Page 24]
This demonstrates communication via a LAN. Communication via the Internet is similar. The router must be programmed to forward port from the Internet side to the XEP side.
Since port is “non-secure,” we do not recommend forwarding it on the Internet. Therefore, the XEP has a “secure” port – port by default. The remote site will need to accept the XEP’s certificate. If the remote site responds with the correct username and password, the connection is allowed and everything works from there on as described above, except that the data sent over the wire is now automatically encrypted. Helping you learn that is beyond the scope of what Elk Products can do.
I have real work in the way, so no prediction on when something useful actually pops out. Anything you can add?