mikek

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?

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.

apostolakisl - I think your option #2 is just what I need. Keeping the programs separate and triggering one or the other with a third program. Thanks! oberkc - There is nothing preventing the two programs from triggering simultaneously, but the likelihood is low enough where I wouldn't concern myself with it happening. Thanks for the idea about the added conditions. Yes, the secondary program does have a wait.

I have a Homeseer HS-WS200+ wall switch. Unlike the dimmer in the same series, the switch only has one indicator LED. This LED has several configuration parameters associated with it, and I use a program to set those parameters based on time of day, a motion detector and a timer. That all works well. I have another program that controls those same parameters (but configured differently) based on the status of a handful of door/window sensors. That also works well. Both programs end with setting the parameters back to my default status. I'm trying to figure out what to do when the conditions of both programs are met. I'd like to somehow define one program as primary and the other as secondary, and allow the primary to override the secondary. So if the primary program is triggered and active, ignore the secondary. And if the secondary is already active, and the primary is triggered, abort the secondary and enable the primary. I think I can accomplish this with nested conditions, but I was hoping to keep the two programs independent and simply tell the ISY which one takes precedence.

In a situation where two programs are giving conflicting instructions, is there a simple way to prioritize or define which takes precedence?

I'm also thinking that if the UDI is finding it, then I don't need another way to get it out of the Elk. Seems like I should be able to take advantage of what the ISY is seeing and reporting - I just don't know what that method should be. Anyone ever tried something like this?

I did look at ekeypad, but as far as I can tell, there is still no Android version.

Thanks for the reply, Paul. That seems like a great approach to get notifications, but unfortunately I don't think I can go that way. This is the first of several temperature zones that I plan to install (if this one works) and my goal is to be able to monitor all of them at a glance and at will. Notifications for out of range conditions will eventually become part of my overall system, but for now I just want to be able to take a quick look at current conditions.

I originally posted a similar message in the Agave thread, but it doesn't look like Agave can do what I need so I am looking for alternate solutions. I have an M1ZTSR temperature sensor on my ELK M1. I can read the temperature (in degrees F) on both the ELK keypad and also in the UDI administrative console (see screenshot). However, the Agave app only shows "normal" and M1ToGo just shows the usual green checkmark as if the zone status is okay. Neither of these do me any good. What I really need is a way to get the actual temperature shown in the console to be displayed either on an Android device or a PC. I have no idea how to accomplish this, and am hoping someone has either done it successfully or has some good ideas for possible solutions. Thanks in advance. .

Thanks for the reply. It included just fine (admin console and module status indicator show that it's included), but then nothing. I tried with a second module - same problem. Tried excluding then including as a latched output (for bench testing) and still the same issues - nothing. It seems like it's not getting along with the ISY (v.5.0.11B). Sometimes I can write and read a parameter with no problem. Other times it gets hung up. I tried a Restore and I get "PLATFORM_ERRORS--7". When I do a query on the sensor (with nothing connected) or the switch, I either get no response or a "Request Failed" error. I haven't seen this anywhere in the documentation, but an input isn't required for output operation, is it?

I'm stuck. I have a MimoLite module wired (no input) into my opener per the Fotrezz instructions and added to my z-wave network, but I don't know what to do next. I assumed that I could eventually find the proper momentary "on time" (parameter 11) and at first just use admin console to prove functionality. But I can't get it to work. Any suggestions?

Thanks, Scott. I'm just getting started with the ISY, and want to add a thermostat. Trying to understand what happens if I have issues and be sure that I can use it as a stand-alone unit (including local programming).

Thank you.

I have some questions about the interaction between an ISY and a Z-Wave or Insteon thermostat. Does the ISY only send down a command only when there is need (a setpoint change, for example) or is communication constant? Does the ISY receive any feedback from the thermostat indicating that the programmed setpoint change was accepted? What happens when communication fails? Does the thermostat retain its "last" settings indefinitely? What happens when communication is restored? Does the thermostat get updated to the current program setpoint or does it wait until the next time- or event-based step in the program? Are the Z-Wave and Insteon thermostats typically programmable locally, or is a controller required? Thanks very much!