mikek

Eisy Z-Wave migration instructions (from ISY-994) state "You must be using a 500 Series Board in the ISY-994." How do I determine which board I have?

Can someone post a photo of this combo? I'm replacing my 994 and just curious about real estate. The 994 is a tight fit already, and I'm wondering if I'll need to relocate things. I found the dimensions, but it would still be helpful to see it. Thanks.

Thanks, much appreciated!

Thanks. I looked at that Ecolink but can't find the user manual. The support tab on that page doesn't bring up any information. Any chance you can point me in the direction of some documentation?

Thanks for the reply. When you say "goes off", do you mean that it stops working/communicating or that the siren sounds? This would be a new device. Mainly looking for something for low volume notifications rather than a high volume siren, but the Aeotec seems to have enough options for that purpose. I don't really like the wall wart idea (I think I saw that the previous generation was a plug-in). In general, I'm not finding a lot of alternatives. Ecolink has one and I found a few other knock-offs, but the Aeotec seems to be the most popular.

Can anyone confirm compatibility of the Aeotec Siren 6 with the 994? Does anyone have experience with this device? Recommendations for an alternative?

? That did it! Thanks very much!

Yes, a low battery in a wireless sensor also reports as trouble. That's what I'm trying to accomplish with my notifications - a low battery alert. I already have my "violated" programs running and notifying as they should.

Thanks for your input. But I've already done that. According to Elk itself, status is trouble. According to ISY, status is trouble. According to alert, status is violated.

Since I'm just trying to see if this concept ("trouble" notification) works, I'm simply using the default subject (${alert.subject) and body (${alert.body}) for now. My programs and notifications work fine for a true "violated" status. But 'trouble" and "violated" are two unique statuses.

I originally posted this in the Elk board, but it seems like the problem is actually ISY related. What I want to do is receive an email alert when any of my Elk wireless zones report status as "trouble" (not "violated"). Simple code, looks like this (for one of the zones): If Elk Zone 'Office-WestWind' is Trouble Then Send Notification to 'Me' Else Wait 0 seconds However, instead of receiving a "trouble" alert I get this: Security Zone 'Office-WestWind' Violated Any ideas?

That is an ISY program (reading an Elk zone). I am asking for an alert when the Elk zone reports "trouble". What I am getting instead is an alert when that zone reports "violated". If Elk Zone 'Office-WestWind' is Trouble Then Send Notification to 'Me' Else Wait 0 seconds Here's the alert I get: Security Zone 'Office-WestWind' Violated

If Elk Zone 'Office-WestWind' is Trouble Then Send Notification to 'Me' Else Wait 0 seconds Here's the alert I get: Security Zone 'Office-WestWind' Violated

I'm trying to set up an ISY program to notify me of low battery status on some Elk wireless sensors. There are reported by Elk and displayed on the ISY console as "trouble". However, I am getting notifications every time one of the wireless zones is violated. It seems like the ISY is considering trouble and violated to be the same status. Any ideas on how to resolve this?

I have a HomeSeer Z-wave wall switch that I want to remove and replace with a different HomeSeer wall switch that has the multi-colored indicators. Is there an easy way to do this without messing up my configuration and programs? Is it possible to use the administrative console to simply point my old device configuration to the new switch? Thanks in advance.