ISY connected to ELK without the M1XEP

[Planet]

I just wanted to mention that instead of buying the M1XEP, I used a beaglebone (or Raspberry Pi) connected via serial to the elk to provide the same interface the M1XEP does.

 

It works perfect with the ISY's Elk module and I can even use the ElkRP2 software via network connection to manage the Elk.

 

If anyone is interested in my node.js code, I would gladly put it up somewhere.

[apostolakisl]

Considering how much cheaper a raspberry pi is I am sure anyone who doesn't already have an xep would be very interested.

 

I guess the main issue would be if it is robust.  The xep seems to always work. . . aside from when you try to change settings on it, which sometimes is buggy.

[MWareman]

The other issue with the XEP is when ElkRP2 is connected, nothing else can (including the ISY). Does this solution solve that? If so, I may even consider switching.

[apostolakisl]

The other issue with the XEP is when ElkRP2 is connected, nothing else can (including the ISY). Does this solution solve that? If so, I may even consider switching.

 

I thought of that, but I really doubt it.  I suspect that when rp2 connects there is a deliberate shutting down of the system to all other IP traffic.  One test that might confirm this would be directly hooking up your computer with rp2 to the serial port and see if other things can simultaneous connect via the xep.

[MWareman]

The XEP connects to the serial port - so you cannot connect the XEP and RP2 (via serial) at the same time.

[Planet]

I used a beaglebone instead of a raspberry pi and its been working for years. I did try a raspberry pi and it worked just the same. Its been very robust and only a couple times has needed to be restarted. The Elk sends ping style messages that you have to reply too otherwise the Elk will throw a 'Ethernet Trouble' on your keypads. When RP2 connects it uses a binary protocol, so the ISY does get disconnected until RP2 disconnects. 

 

I basically created a bridge that relays the RS-232 communications of the Elk to a standard TCP socket. I use a separate port for connecting via RP2 so that I can switch into handling the binary protocol vs. the line based ascii protocol.

[tgpaul]

I'm VERY interested in any code you've written for this, Planet

 

I used a beaglebone instead of a raspberry pi and its been working for years. I did try a raspberry pi and it worked just the same. Its been very robust and only a couple times has needed to be restarted. The Elk sends ping style messages that you have to reply too otherwise the Elk will throw a 'Ethernet Trouble' on your keypads. When RP2 connects it uses a binary protocol, so the ISY does get disconnected until RP2 disconnects. 

 

I basically created a bridge that relays the RS-232 communications of the Elk to a standard TCP socket. I use a separate port for connecting via RP2 so that I can switch into handling the binary protocol vs. the line based ascii protocol.

[Reelsea]

Sorry to bump an old topic but - Hey Planet / I'd be really interested in your code - I jut got an ez8 and already have a pi. Been debating on the m1xep but if this works would much rather use what I have

[2112]

Planet,

 

Could you please elaborate on the method that you used to convert a beaglebone (and Raspberry Pi) to provide a compatible interface to the Elk M1 Serial Port via IP (in lieu of the ELK-M1XEP / Elk M1 Ethernet Interface)?

 

I just ran through an INSTEON PLM (after about 2 1/2 years of use) and I am also on my 2nd ELK-M1XEP at this time (with this one in service for about 2 1/2 years of use... the first ELK-M1XEP that I purchased was defective within about a month before it was replaced).

 

Anyway, we've grown quite accustomed to the functionality of the ISY / ELK (as well as other modules) integrated together and would love to have an option available to replace the ELK-M1XEP with an inexpensive single-board computer now and then place the ELK-M1XEP into storage as a backup device.

 

Plus, I have multiple Raspberry Pi 2s available for conversion for this function (as I moved some functions / services from previously used Pi 2s to virtual machines)...

 

Therefore, could you please provide some information regarding your implementation method and your node.js code for this?

 

I believe that the community (and most certainly including tgpaul, Reelsea, and I) would be very appreciate of your efforts and ingenuity!

 

-- IMHO, I'd think that this might interest Michel Kohanim as well for inclusion as a UDI Web Site referenced customer provided "how to" guide for ISY / Elk M1 users as well.

 

Please let us know.

 

Thank you!

[Planet]

I have never had a m1xep and my goal was to be able to connect my isy to the elk without it. So I have not emulated all the fuctions of the m1xep (it would  be easy enough to implement). I will get my code up on Github so you can grab it, I will warn you that its not very 'polished' . The only requirements is a serial port and the ability to run node. 

 

Are there any other functions of the m1xep (aside from a bridge to the isy) that you use?

[2112]

I simply use the ELK-M1XEP as a bridge to the ISY.

 

-- tgpaul and Reelsea as well as others may have an interest in more functions though...

 

As far as the code being "not very 'polished'", as long as the ELK M1 is O.K. with it, I'm O.K. with it.

 

Thanks again for your assistance as well as timely response!

[billchurch]

Well, since Planet has gone away never to be heard from again I decided to start a project of my own. You can check out my progress at http://billchurch.github.io/node-elkether/ and on github under https://github.com/billchurch/node-elkether.

 

I have some sample code that works, though it's far from complete at https://github.com/billchurch/node-elkether/tree/master/samples. You need tcp2101-2webSocketServer.js and webSocket2serial.js to get tcp/2101 functionality working. It also will respond to the Ethernet health check queries from the Elk M1. I've not done extensive testing yet so use at your own risk, worth playing with at least.

 

The Wiki, https://github.com/billchurch/node-elkether/wiki, is where most of the activity is right now. Any thoughts or questions please feel free to let me know.

 

-Bill

[tgpaul]

Nice work Bill. Earlier this year I'd started my own project using C++/Boost but got sidetracked after I couldn't get the thing enrolled. I'll definitely be checking out your wiki when I dust it off the shelf and finish it.

[Planet]

I put my code here.

 

https://github.com/PlanetJ/node-elk

[Planet]

Sorry guys, so busy these days and notifications to this form get lost in my read mail as I usually check on my phone.

 

Its not really a clean node module. I like to make it more complete so it can be used easily in other node apps. Its been working for me for years and i will gladly answer any questions regading getting it to work or anything else regarding getting the elk and isy talking.

[billchurch]

Nice work Bill. Earlier this year I'd started my own project using C++/Boost but got sidetracked after I couldn't get the thing enrolled. I'll definitely be checking out your wiki when I dust it off the shelf and finish it.

Thanks!

 

Enrollment isn't something I've tackled yet, however the messages come out over this thing regardless. The main point for enrollment is for notifications (email, etc) and allowing the Elk to "dial" internet connected central stations. Again, something else I've not tackled yet.