ISY 994 and Elk M1 Trigger Event

[hmatos]

I've looked around this forum and don't see any mention of this. I was wondering if there's any way to trigger an Elk Event, such as the events listed on page 58, "Appendix A - Event Codes", of the M1 Install Guide:

 

1055 = CO Alarm in Area 1

 

I have an Insteon Water Leak sensor and I'd like to trigger, "1013 = Water Alarm, Any Area".

 

Thanks,

 

hm

[hmatos]

I take it this means no? Does anyone know of any home automation controller that does?

[gatchel]

Can you explain this in more detail? What is the end result of what you are trying to accomplish?

 

Also, while there are Elk users in this forum you may have better luck posting in the Elk subforum at http://www.cocoontech.com

 

 

Here is the sub forum link:

 

http://cocoontech.com/forums/forum/42-e ... s-inc-elk/

[NHWA]

You can't have something directly set off an alarm but I did find a work around by assigning an F key to set off an alarm. I wanted my smoke detectors to set off a firm alarm but my smoke detectors were on a separate system. I connected them to my insteon network and if they go off then I have the ISY send a double F1 hit to a specific keypad which is set up in the Elk to set off a fire alarm. It works and the only risk is someone hitting the F1 key on the keypad (hence why I have it set for two presses).

 

You should be able to do the same for the water/leak detector.

[MWareman]

Here is how I did it - for a smoke bridge connected to my ISY for things like CO alerts where I wanted the elk to respond to the even as an alarm condition.

 

I have nothing wired to Zone 16 on the ELK. I configured it as a '17 - Carbon Monoxide' zone type. I selected '0 = EOL Hardwire / Wireless' as the type. I have a resistor directly connected to the terminal on the Elk. I named the Zone 'CO Detected'.

 

Back on ISY - I refreshed the topology (so the new zone showed up.

 

In a program - you can now use "Set Elk zone 'CO Detected' Trigger Zone Open" in the 'Then' or 'Else' clause as you need. This causes the Elk zone to trigger momentarily. I have the Elk dial the monitoring company - and they know to react to Zone 16 as a CO alarm.

 

I repeated with Zone 15 - but for Smoke. Seems to work well the couple of tests I have done. You could use this method for any other triggering you need to do I suspect - the 'Water' detected is zone type definition 25.

 

Michael.

[apostolakisl]

Alarms can not be triggered by rules or by ISY programs directly.

 

There is a workaround that does not involve hardwiring anything. F-keys can trigger alarms and ISY can simulate an f-key press. So if one of your keypads has an unused f-key, then program it as the alarm you want. Then have ISY "push" that f-key when you want to trigger that alarm.

 

EDIT: My apologies, just saw that the f-key trick was already listed.

[daxiang28]

Here is how I did it - for a smoke bridge connected to my ISY for things like CO alerts where I wanted the elk to respond to the even as an alarm condition.

 

I have nothing wired to Zone 16 on the ELK. I configured it as a '17 - Carbon Monoxide' zone type. I selected '0 = EOL Hardwire / Wireless' as the type. I have a resistor directly connected to the terminal on the Elk. I named the Zone 'CO Detected'.

 

Back on ISY - I refreshed the topology (so the new zone showed up.

 

In a program - you can now use "Set Elk zone 'CO Detected' Trigger Zone Open" in the 'Then' or 'Else' clause as you need. This causes the Elk zone to trigger momentarily. I have the Elk dial the monitoring company - and they know to react to Zone 16 as a CO alarm.

 

I repeated with Zone 15 - but for Smoke. Seems to work well the couple of tests I have done. You could use this method for any other triggering you need to do I suspect - the 'Water' detected is zone type definition 25.

 

Michael.

 

That's awesome. I was able to to get as far as having the Elk recognize the alarm. However, the alarm company was not able to see it on their end. I'm assuming it's because it was a momentary open and they need a longer duration for them to see it. Is this a setting in the Elk somewhere. I don't see any way to open it for a duration in the Isy programming.

 

Steve

[apostolakisl]

Here is how I did it - for a smoke bridge connected to my ISY for things like CO alerts where I wanted the elk to respond to the even as an alarm condition.

 

I have nothing wired to Zone 16 on the ELK. I configured it as a '17 - Carbon Monoxide' zone type. I selected '0 = EOL Hardwire / Wireless' as the type. I have a resistor directly connected to the terminal on the Elk. I named the Zone 'CO Detected'.

 

Back on ISY - I refreshed the topology (so the new zone showed up.

 

In a program - you can now use "Set Elk zone 'CO Detected' Trigger Zone Open" in the 'Then' or 'Else' clause as you need. This causes the Elk zone to trigger momentarily. I have the Elk dial the monitoring company - and they know to react to Zone 16 as a CO alarm.

 

I repeated with Zone 15 - but for Smoke. Seems to work well the couple of tests I have done. You could use this method for any other triggering you need to do I suspect - the 'Water' detected is zone type definition 25.

 

Michael.

 

That's awesome. I was able to to get as far as having the Elk recognize the alarm. However, the alarm company was not able to see it on their end. I'm assuming it's because it was a momentary open and they need a longer duration for them to see it. Is this a setting in the Elk somewhere. I don't see any way to open it for a duration in the Isy programming.

 

Steve

 

If the Elk goes into alarm state, then your "momentary" was long enough. Elk wouldn't recognize it at all if the duration was too short.

 

Did you check your Elk globals where you set up your reporting codes and make sure that water alarm is reported?

[daxiang28]

It doesn't go into alarm state. It just beeps the keypad. I am only able to verify by seeing it in the logs.

 

Steve

 

Here is how I did it - for a smoke bridge connected to my ISY for things like CO alerts where I wanted the elk to respond to the even as an alarm condition.

 

I have nothing wired to Zone 16 on the ELK. I configured it as a '17 - Carbon Monoxide' zone type. I selected '0 = EOL Hardwire / Wireless' as the type. I have a resistor directly connected to the terminal on the Elk. I named the Zone 'CO Detected'.

 

Back on ISY - I refreshed the topology (so the new zone showed up.

 

In a program - you can now use "Set Elk zone 'CO Detected' Trigger Zone Open" in the 'Then' or 'Else' clause as you need. This causes the Elk zone to trigger momentarily. I have the Elk dial the monitoring company - and they know to react to Zone 16 as a CO alarm.

 

I repeated with Zone 15 - but for Smoke. Seems to work well the couple of tests I have done. You could use this method for any other triggering you need to do I suspect - the 'Water' detected is zone type definition 25.

 

Michael.

 

That's awesome. I was able to to get as far as having the Elk recognize the alarm. However, the alarm company was not able to see it on their end. I'm assuming it's because it was a momentary open and they need a longer duration for them to see it. Is this a setting in the Elk somewhere. I don't see any way to open it for a duration in the Isy programming.

 

Steve

 

If the Elk goes into alarm state, then your "momentary" was long enough. Elk wouldn't recognize it at all if the duration was too short.

 

Did you check your Elk globals where you set up your reporting codes and make sure that water alarm is reported?

[apostolakisl]

You mean beep your keypad because you have your chime on and it is detecting a zone violation? What does the log say?

 

It kind of sounds like an improperly defined zone.

 

And, I apologize, it is not in globals that you set the alarm reporting, it is under communicator.

[daxiang28]

You mean beep your keypad because you have your chime on and it is detecting a zone violation? What does the log say?

 

It kind of sounds like an improperly defined zone.

 

And, I apologize, it is not in globals that you set the alarm reporting, it is under communicator.

 

I attached a screenshot of the log and the Communicator Zone Config. Not sure how any of the config works with all the acronyms.

 

Steve

[apostolakisl]

Are we talking about zone 14 here?

 

Zone 14 never alarmed according to the log, it had a trouble state. That means it went to a voltage that indicates a wire tamper, not an alarm. Trouble state makes a beep sound which is different than other beeps, like the chime beep.

 

Try EOL supervised on short for your zone type.

 

And carbon monoxide is CO, not CO2 (carbon dioxide), just to be accurate.

[daxiang28]

Are we talking about zone 14 here?

 

Zone 14 never alarmed according to the log, it had a trouble state. That means it went to a voltage that indicates a wire tamper, not an alarm. Trouble state makes a beep sound which is different than other beeps, like the chime beep.

 

Try EOL supervised on short for your zone type.

 

And carbon monoxide is CO, not CO2 (carbon dioxide), just to be accurate.

 

Thanks Apostolakis,

It is set to EOL and yes, I'm super embarrassed to have listed is as CO2! I added a screenshot of the Elk config. I called alarm relay and the mentioned that they need to see the signal for at least 30 seconds. Which leads me to believe that the TEST from the detector wasn't long enough for it to trigger.

 

Steve

[apostolakisl]

Try type 3, "eol supervised ON SHORT"

[daxiang28]

Try type 3, "eol supervised ON SHORT"

I only see the following. Should I change the zone definition?

 

 

Steve

[apostolakisl]

Yes, at least for testing purposes, set as a burglar zone then type 3. I'll have to think about why type 3 isn't available on CO.

 

EDIT: Or, get rid of the resistor and jumper the zone closed and set it as normally closed. I can't think of any reason that having an eol resistor in this situation would be of any benefit.

[daxiang28]

Yes, at least for testing purposes, set as a burglar zone then type 3. I'll have to think about why type 3 isn't available on CO.

 

EDIT: Or, get rid of the resistor and jumper the zone closed and set it as normally closed. I can't think of any reason that having an eol resistor in this situation would be of any benefit.

 

cool, thanks again for all the help.

 

Steve