RESOLVED: Problem with isy 99i and Elk M1G

[sactobob]

Add me to the list of users with linking issues. Can't seem to get the Elk M1 talking to the isy via the Ethernet module.

 

M1G Boot/Firmware : 3.3.6/5.2.10

Ethernet Expander: 1.2.0/1.3.28

Isy 99i pro: v3.2.6

 

I've gotten the isy to go as far as showing the status of the Elk (Disarmed) and network name, IE event viewer for ISY shows:

 

Fri 07/20/2012 08:36:51 PM : [ELK ] Connect

Fri 07/20/2012 08:36:57 PM : [ELK 0 0 0] (157/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 0 0 0] (156/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 1 0 0] Area : Home Net : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 1 0 0] Area : Home Net : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 1 0 0] Area : Home Net : Not Ready To Arm (2/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 2 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 2 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 2 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 3 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 3 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 3 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 4 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 4 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 4 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 5 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 5 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 5 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 6 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 6 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 6 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 7 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 7 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 7 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:36:57 PM : [ELK 8 0 0] Area : : No Alarm Active (1/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 8 0 0] Area : : Disarmed (3/0/0)

Fri 07/20/2012 08:36:57 PM : [ELK 8 0 0] Area : : Ready To Arm (2/1/0)

Fri 07/20/2012 08:37:04 PM : [ELK-TX ] Refresh Topology

 

So it is talking to the Elk at least in this regard. But there is no lighting control from the Elk. And when I try to do a Refresh Topology I get:

 

ri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [11pcA05030100000041\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [11pcA05030100000041\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [ELK-ERR ] Refresh Topology

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [11pcA11030100000044\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [11pcA11030100000044\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [11pcA14030100000041\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [11pcA14030100000041\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [11pcB02030100000043\r\n]

Fri 07/20/2012 08:46:34 PM : [ELK-ERR ] Refresh Topology

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [11pcB02030100000043\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 2 of 2 [06zp0050\r\n]

Fri 07/20/2012 08:46:34 PM : [Elk ] ELK-WAIT Waiting for retry 1 of 2 [11pcC0503010000003F\r\n]

Fri 07/20/2012 08:46:34 PM : [ELK-ERR ] Refresh Topology

 

 

Executing a rule on the Elk to turn on a light does nothing and the event viewer doesn't display any type of communication.

 

I read in another thread that upgrading firmware fixed the issue, but I'm on the latest firmware and using the same version now mentioned in the thread. I've power cycled both ELK/ISY just to be sure.

 

Any ideas what to try next?

[sanders2222]

Sorry, but I think we need a little more information about your set up and what it is you are trying to do. Do you have the ELK module on your ISY?

 

Are you trying to control lighting directly from your ELK rules? And doesn't that require a serial connection to the PLM?

[sactobob]

Sorry, but I think we need a little more information about your set up and what it is you are trying to do. Do you have the ELK module on your ISY?

 

Are you trying to control lighting directly from your ELK rules? And doesn't that require a serial connection to the PLM?

 

With the M1G and its built-in Ethernet interface a serial PLM is not required (it's linked to the ISY), the ELK and isy communicate via Ethernet port 2101.

[Brian H]

Do you have the ELK Integration Module also?

[sactobob]

Do you have the ELK Integration Module also?

No I don't, I didn't realize there's another purchase, when I originally bought this (3 years ago) I was told I had everything needed! Sigh, another $99!!???!!!???

 

Edit: Are you sure that's needed? This module seems to allow ELK events/programming from the ISY? That's not what I'm doing, I'm using programming/rules in the ELK for lighting commands to the ISY, that's the other way around and I think is already supported with what I have. That module/software was introduced last year too, the capabilities of ELK/Lighting I think was already there via IP.

 

The Basic Idea of this Module

 

This module is designed to expose ELK Security commands and events to ISY's Programming environment.

 

Yes, that module is basically to allow the ISY to send commands to ELK. Elk to ISY events should be supported with my existing setup.

[Brian H]

OK then we can cross that one off the list.

[sactobob]

I'm wondering now even though the ISY is logging into the ELK side of things, if the serial PLM for the ELK is indeed needed. When I look at the lighting objects in the ELK they are all marked "Serial Expander*" under the Format field, there are other options of "Standard, Extended, Preset Dim, and Compose". The "*" is marked below with the following:

 

* Select Serial Expander format to communicate with the following lighting products: ....... and Insteon."

 

So possibly the customer service rep that sold me the system was wrong that the isy99i/m1G with ethernet is all I need. Unless there's a way to tell the ELK to communicate to the ISY over Ethernet/IP that I don't have properly configured a serial connection to a PLM is probably what is needed. Maybe since I was sold a PLM (for the ISYi) the Rep assumed that it was for the Elk.

 

Is there a UD rep here that can tell me exactly what is needed?

[Brian H]

You may have seen the ELK info in the wiki but if you didn't

http://www.universal-devices.com/mwiki/ ... figuration

http://www.universal-devices.com/mwiki/ ... Elk_IP-232

[sanders2222]

So possibly the customer service rep that sold me the system was wrong that the isy99i/m1G with ethernet is all I need.

It's my understanding you do not need the Elk module. Check this thread for more on that.

http://forum.universal-devices.com/viewtopic.php?f=27&t=7830&p=59552&hilit=do+not+need+elk+module#p59552

 

But, depending on what you want to do or if you want full integration between the security system and home automation, you do need the module. This allows all lighting & device control from the ISY. With the module, you would never need to use rules in the ELK as the ISY can monitor everything the ELK will report.

[Michel Kohanim]

Hello sactobob,

 

You do not need a serial PLM for ELK. What you need is M1XEP which allows ISY to communicate with ELK over Ethernet.

 

Do you already have an M1XEP?

 

With kind regards,

Michel

[sactobob]

Hello sactobob,

 

You do not need a serial PLM for ELK. What you need is M1XEP which allows ISY to communicate with ELK over Ethernet.

 

Do you already have an M1XEP?

 

With kind regards,

Michel

Yes, I have the M1XEP. It's on Serial Port 0, (all 6 flags are checked).

 

I'm able to access all the Elk functions with ElkRP2. The ISY can see the Elk as well, as the admin console comes up with arming status' and stuff (just not the complete functions as I do not have the Elk module for the ISY). So the ISY can clearly see the Elk, but I'm not sure if the Elk is properly communicating with the ISY.

[Michel Kohanim]

Hi sactobob,

 

If you have exported the ELK configuration from ISY into your ELK, then please do let me know if you see all your devices listed under ELK-RP/lighting. And, if so, try turning on/off some of your INSTEON devices ... does the status change in ELK?

 

If you are seeing ELK status in ISY but no status in RP (from ISY), my first suggestion is to export your ELK config and then import it again to ELK (Lighting).

 

With kind regards,

Michel

[apostolakisl]

Just to jump you ahead a little.

 

Things may be slightly different in the newer firmware and since I have the Elk module I am not exactly sure that my menus are the same as yours. But, it should be under configuration/elk/export on the ISY.

 

Then, go to your ElkRP2 software and right click on "lighting" in the tree on the left. You will see "import". Go ahead and point it to the file you saved from ISY.

 

Your integration is limited without the module. 3 years ago this was the only integration. The module just came last winter and it gives virtually 100% integration. It is really very nice and almost eliminates the need to have Elk rules since ISY programs have essentially 100% access. Without the module, you will be able to control scenes and individual devices from Elk programs. Elk can also respond to changes in devices. That is pretty much it. . . but that may be all you want.

[sactobob]

Hi sactobob,

 

If you have exported the ELK configuration from ISY into your ELK, then please do let me know if you see all your devices listed under ELK-RP/lighting. And, if so, try turning on/off some of your INSTEON devices ... does the status change in ELK?

 

If you are seeing ELK status in ISY but no status in RP (from ISY), my first suggestion is to export your ELK config and then import it again to ELK (Lighting).

 

With kind regards,

Michel

 

Good news, it works! I think it's been working all along, but here's the reason why in case someone else stumbles along this thread. It all had to do with the way I was initially testing, I had configured a rule via ElkRP2 that basically says turn a light on outside my den. And then using the "Test" button to bypasses the "Whenever" rule and trigger the "Then" statements. However, I think because I'm using the rule from ElkRP2 to trigger, the Ethernet port, and hence serial port 0, is busy. So when the Elk tries to execute lighting commands, the commands are not going out.

 

So to rule out something strange with triggering from ELKRP2, last night I changed the rule to trigger based on time. Set the time to a couple of minutes from current, and BINGO the light came on! So the Ethernet port/serial port appear to be able to handle only 1 communication stream at a time and since that stream was coming from ELKRP2 the lighting command was never going out!

 

Everything is good, thanks everyone for all the help!

 

-sactobob

 

 

That is pretty much it. . . but that may be all you want.

Yep, that's really all I need. I might still go with the module to have the cross-rule flexibly. For now the main goal to get this working (after 2+ years) was some idiot drove by the neighborhood around 4:30am and pried open the locked part of our mailbox. It's kind of a rural area, 5 acre lots, houses set back a few hundred feet with long driveways. The mailbox is setup in the Elk with a switch that announces "Mailbox Open" in the house, which lets us know USPS has been by, but they don't come at 4:30am!

 

So now when the mailbox opens that early I trigger the outside bell for about 30 seconds, but I also want to blink the lights built into the columns on the entry gates, as well as the light on the mailbox column itself. That should let someone know they're not as stealthy as they thought!

 

I'm thinking of adding a siren inside the column too so I can trigger that via a spare X10 module I have, or I may swap out the plug with another Insteon plug. Insteon is so much more reliable (and fun!).

 

Thanks again everyone...

 

Edit: Ha! Wish I'd found this message sooner too, it was on the ELK forums.. lol

 

Re: Lighting Rules Not Working

Posted by dlamb on 06/27/2010 08:03 PM

While ELK-RP is connected to the M1XEP it has full communication with the M1G. You'll need to disconnect from ELK-RP so that the M1G's lighting commands can be transmitted to the ISY over the network.