Elk Integration Not Working

[timekiller]

Hello!

Today I received the M1XEP for the M1 Gold I installed last week. Very excited!

 

I have followed the steps outlined in the Elk training video here: 

 

 

I am at the point where I have the ISY talking to the Elk (non secure, port 2101 which I'd like to correct, but that's another topic). I know this is connected by the new "Arm" buttons at the top of the admin console.

 

I have exported my devices to an XML file which I then imported into the Elk through ElkRP2. I have my list of devices in the Elk, and per the training video I tried to confirm this works by controlling a light at the keypad. I browsed to a light I could see from the keypad and hit '#' to change it. The keypad indicated it was changed, but the light did not come on. I tried several other lights and got the same results. According to the Elk they come on, but in reality nothing happens.

 

Some answers to obvious questions:

 

Yes I 'Saved' and 'Sent to controller' for everything I needed to.

 

Yes the lights can be controller by the ISY (tested)

 

No I do not have the Elk module (will probably purchase it at some point, but for now I'm writing rules in the Elk). According to everything I've seen the Elk module is not necessary for what I'm doing.

 

My ISY is on firmware 5.0.8 (Yes I know this is experimental, but I need it so I can talk to my Nest thermostats (Don't get me started on THAT). UI is also version 5.0.8

 

Elk system is M1G, Hardware Version 0.13, Boot Version 3.3.6, Firmware Version 5.3.10.

 

M1XEP Hardware Version 1.0, Boot Version 2.0.4, Firmware Version 2.0.42

 

Any help is appreciated!

[shannong]

That you're running on v5.x means there's no value to anybody (including you) to post here. You need to be in the ISY ALPHA Developers 5.x forum. http://forum.universal-devices.com/forum/108-50/   That stuff isn't even Beta, yet. So basically non-existent. It's been Alpha for over 2 years now. If it doesn't work, only UDI directly can help you.

 

However, I will share my opinion that avoiding the few dollars for the ISY-Elk Integration module is pretty silly from my opinion. It gives you the ability to see all relevant states of the M1 at the zone, output, arm-state, etc in addition to being able to set just about anything on it from a drop-drown selection in the ISY. Speak phrases easily.... You name it!

 

Can you avoid it, sure? But days and weeks of my time saved in addition to knowing my physical security works with my HA as expected aren't worth something that costs less than a dinner date out on the town. Your time-value may vary.

 

Good luck.

[timekiller]

That you're running on v5.x means there's no value to anybody (including you) to post here. You need to be in the ISY ALPHA Developers 5.x forum. http://forum.universal-devices.com/forum/108-50/   That stuff isn't even Beta, yet. So basically non-existent. It's been Alpha for over 2 years now. If it doesn't work, only UDI directly can help you.

 

However, I will share my opinion that avoiding the few dollars for the ISY-Elk Integration module is pretty silly from my opinion. It gives you the ability to see all relevant states of the M1 at the zone, output, arm-state, etc in addition to being able to set just about anything on it from a drop-drown selection in the ISY. Speak phrases easily.... You name it!

 

Can you avoid it, sure? But days and weeks of my time saved in addition to knowing my physical security works with my HA as expected aren't worth something that costs less than a dinner date out on the town. Your time-value may vary.

 

Good luck.

 

Thanks, I'll just post in the 5.0 forum then...

[larryllix]

Most people in V5 know nothing about Elk security systems. Elk support hasn't changed in v5.

 

Your post doesn't seem v5 related at all, and those forums are typically for reporting bugs in alpha/beta software.

 

In the advanced editor "more reply options" a new thread can de deleted before anyone answers.

[timekiller]

Most people in V5 know nothing about Elk security systems. Elk support hasn't changed in v5.

 

Your post doesn't seem v5 related at all, and those forums are typically for reporting bugs in alpha/beta software.

 

In the advanced editor "more reply options" a new thread can de deleted before anyone answers.

 

Ok, so you are saying I should keep this thread open?

 

If so I'll ask here: How does the Elk even know where to send lighting commands. I checked the XML export and the IP of the ISY is not in there at all. Does the Elk just broadcast messages on the network, or does it have some internal "Find ISY" mechanism?

[Michel Kohanim]

Hi timekiller,

 

The connection is from ISY to ELK. So, once you configure ISY to ELK's IP/Port, ISY makes a connection to ELK and ELK keeps that connection open (unless you have ELK RP connected in which ISY's connection is severed and ISY has to keep trying to connect). In short, and as I mentioned previously, the connection information is saved in ISY and the connection itself is originated from ISY.

 

Please make sure you have the non-secure port available on your ELK AND make sure ELK RP is NOT connected.

 

With kind regards,

Michel

[shannong]

I'm confused. The OP said he didn't have the Elk module for the ISY. However, he's configuring access to it? I think there might be some confusion. At least I know I am.

[timekiller]

Thanks for the replies guys. I actually got advice from a tech at Elk. Looks like you have to enable all possible logging to the serial port (Event Logs are disabled by default). I will test this when I get home, but now that I understand how the communication works, this makes a lot of sense. The ISY connects to the Elk and listens to events streamed from it's serial port. The "Event Log" likely includes things like "turn on the living room light" which the ISY then sees and executes. Pretty good feeling this is the answer.

 

shannong: the Elk module is only necessary for the ISY to read and control things like zones and outputs in the Elk. Then you could write a program, for example, to say "when the front door opens, turn on the entrance light". But you cando the same logic from the Elk without the Elk module.

 

Difference is, with the Elk module you are reading the state of the door from ISY and executing the action. Without the Elk module, the Elk sees the front door status change, then executes the light turning on through the ISY.

 

I have not yet come up with a action I can't initiate from the Elk (I'm sure I will), so for now writing my logic in the Elk works fine for me. $99 is a lot of money for edge case programming. Especially when you consider the ISY was $200, the M1 was $500, adn the Ethernet module was $190! That's almost $900 just to get STARTED with home automation, then you still have to buy all the switches.

 

Not complaining, just saying another $99 on top of that when I can do everything without spending it is kind of silly.

[apostolakisl]

Programming ISY is much more versatile than Elk Rules.  Also it is much easier to write the programs and way easier to edit since ISY has a file structure whereas Elk is just one big long list of "rules" that have no names.  If you only have a few needs, then probably not a big deal.  But when you start trying to cover all kinds of if/then scenarios with unique responses, Elk rules will drive you nuts.  Plus Elk Rules has an upper limit of programs which is not that hard to fill.  ISY programs also have a handful of things that they can get Elk to do that Elk can't get itself to do. 

[timekiller]

Programming ISY is much more versatile than Elk Rules.  Also it is much easier to write the programs and way easier to edit since ISY has a file structure whereas Elk is just one big long list of "rules" that have no names.  If you only have a few needs, then probably not a big deal.  But when you start trying to cover all kinds of if/then scenarios with unique responses, Elk rules will drive you nuts.  Plus Elk Rules has an upper limit of programs which is not that hard to fill.  ISY programs also have a handful of things that they can get Elk to do that Elk can't get itself to do. 

 

Very true, but most of the ISY functionality works without the Elk module. It would be very possible for me to write a bunch of programs in the ISY and only write a few in the Elk for when I need something specific to the Elk.

 

That being said, I fully expect to be buy the Elk module. I'm just not splurging on it until I have an actual need I can't fill otherwise.

 

 

Regarding my original issue though, My problem is solved. Here is the fix in case anyone else goes searching:

 

Open ElkRP and go to the Globals page. Go to the G29-G42 (Special) tab and make sure all  checkboxes are checked under "Serial Port 0 Transmit Options"

 

Power cycle the Elk and the ISY. Close ElkRP.

 

Done.