ISY variables and ELK integration

[jlv]

I have looked through a couple of old articles (2013) on issues setting ISY variables from ELK but I can't see anything in the last year or so.  Given this functionality would be useful, I'm hoping the issue is resolved.  I have the latest ISY release (4.2.30) and a new M1 Gold Panel with and M1XEP.

 

I'm trying to set an ISY variable from the ELK.  That simple.  I don't have the integration module because I can't validate that it will help me.

 

Can anyone point out what I'm missing in order to do this?  Here's what I have tried:

- looked for straight integration of variables within ISY

 

- played around with whether you read a scene state as a conditional.  In ISY, it appears scenes are just collection of devices, so you must get to a device state.

 

- I have looked for evidence that the integration module can allow ISY to read an ELK counter.  If so, then one could at least poll for state from the ELK.  Not as good as event-driven, but it's something.

 

- create a "dummy device" in the ISY to signal.  So far, can't see an easy way to do this.

 

So far, I can't see an obvious way to achieve this functionality.  I hope it doesn't take dedicating a real device just to act as a software variable (yeck).

 

Any ideas?

 

 

[shannong]

Can you share what you're specifically trying to accomplish? Context is helpful for offering solutions.

 

You can do this, and you'll definitely need the Elk integration module.

 

I use dummy outputs to accomplish this. The Elk supports up to 208 outputs (e.g. connecting a siren). The Outputs from 65-208 are not physical on the system board and are for use when connecting expansion boards. However, you can still turn them on/off. I use Elk Automation Rules and programs on the ISY to manipulate these outputs to signal things I care about. For example, you could have an Elk Automation Rule that turns on an output for 5 secs that is included in an ISY program that sets a variable whenever it is turned on. This can be done in reverse also. I have ISY programs that momentarily turn on Elk Outputs that trigger Automation Rules.

[Mike Ippolito]

I have looked through a couple of old articles (2013) on issues setting ISY variables from ELK but I can't see anything in the last year or so.  Given this functionality would be useful, I'm hoping the issue is resolved.  I have the latest ISY release (4.2.30) and a new M1 Gold Panel with and M1XEP.

 

I'm trying to set an ISY variable from the ELK.  That simple.  I don't have the integration module because I can't validate that it will help me.

 

 

 

I'd highly recommend the Elk module.  Buy it, the UDI team has been more than gracious to refund users if you don't find modules useful for your application.

[DennisC]

Can you share what you're specifically trying to accomplish? Context is helpful for offering solutions.

 

You can do this, and you'll definitely need the Elk integration module.

 

I use dummy outputs to accomplish this. The Elk supports up to 208 outputs (e.g. connecting a siren). The Outputs from 65-208 are not physical on the system board and are for use when connecting expansion boards. However, you can still turn them on/off. I use Elk Automation Rules and programs on the ISY to manipulate these outputs to signal things I care about. For example, you could have an Elk Automation Rule that turns on an output for 5 secs that is included in an ISY program that sets a variable whenever it is turned on. This can be done in reverse also. I have ISY programs that momentarily turn on Elk Outputs that trigger Automation Rules.

This also what I do and it works fine with no issues.

 

Dennis

[jlv]

I appreciate the various responses.  I'll head into the ELK integration module next week.  The dummy outputs should work as a shared variable of sorts.

 

I use a number of state variables in ISY to have the house work in a particular mode, including emergency mode, or something frivolous like a "party mode."  I'd like to trigger some of those states from the ELK, so this output model should work fine.

 

Thanks for the quick and helpful advice.

[PLCGuy]

I love both Elk and ISY, but trying to assign an Elk variable to a ISY variable is an exercise in hair pulling. Several years ago I needed to grab an analog value out of the Elk (a water level) and move it to the ISY. I was moving it to the ISY because there I could do some simple math for scaling (FYI The reason I was doing the math in the ISY and not the Elk was that math and Elk Automation Rules should not be used in the same sentence).

 

Well in version 4.x of the ISY, Elk to ISY variable assignment is not an option, no matter what integration module you buy. I ended up creating a collection of 100 compare statements as conditions to set a hard value to the ISY variable I wanted to scale. Messy, but it works.

 

Now if you only want to pass boolean values around, shannog's idea is perfect. But do get the Elk Integration module because it will save a lot of other hair pulling. It also seamlessly integrates all your Elk zone status info back into the ISY, which can be really handy. I use the zone status of various doors to automatically turn lights on when a door is opened. For example, if it is dark out and the front door is opened, the front stairway lights are turned on.

 

Hope this helps a bit.

[Morris Hansen]

Has there been any variable improvements in the later releases of the ISY?  I have 3 thermostats connected to my Elk and I am able to control them easily from the ISY.  I would like to have the ability to read the current temperature and heat/cool setpoints from the thermostat and update variables in the ISY.  I can easily read all these values from the admin interface and/or via a REST url.  Nothing I have found has these values available to us for actions.

 

For example: This would allow me to have a program to increase the heat setpoint by 2 degrees for 2 hours and then go back to normal programming.

[Michel Kohanim]

Hi mohansen,

 

Not on the ELK side yet. Currently available foe INSTEON and shortly thereafter for ZWAVE.

 

With kind regards

Michel