oberkc

A few quick thoughts: Keypad buttons in their default state will toggle between ON and OFF. There is typically no logical statement that is equivalent to "keypad button is pushed". One can put the button into a state where each push is ON or where each push is always OFF. In such a state, the program would then look for the ON or OFF command, as configured. Furthermore, you might actually be able to do this in a single program. ISY has THEN and ELSE paths. In the logical form, it might be something like: if keypad button is pressed ON (keypad button configured to always send ON commands) and status outlet is off then turn on outlet push relay else push relay wait xx amount of time turn off outlet turn off keypad button I suspect, however, that you will want to add further stuff which could drive you to multiple programs. Things always get more complicated after you try things out and come up with new requirements. Also, if it is imperative to wait for direct feedback from the computer being off, this will likely drive you to a second program.

Clearly, you have not been around many electric guitar players.

Yes, i looked at the 1608 mackie. The one that best matched my interests was the behringer x18 air, but it was only a rumor when I was upgrading. I have used one of the yamaha boards like that one, and also regularly use the 32AI Presonus boards (really like the workflow and ipad app). Sound mixing is one of my hobbies and passions.

Hijack alert!!! Turning myself in. Cannot pass this one up. What mixer? (I use the Behringer X32 rack, and it has been very nice.) Sorry I could not help myself. Alert terminated.

Logically, the second (outside) set of brackets is not needed.

Xathros, $fanspeed is an integer variable accordong to original post, but one does wonder. I suspect all programs are running because the are all triggered by the same remote button.

Sorry, mango. Lost track.

First, i am not sure that I can accurateli infer you full intention fron the program. Is it your intention to turn the fan from low to medium when you press the remote OFF?! Personally, I would probably use scenes to control the fan via keypad and a program to relate remote commands to the scenes. One think that appears suspicous is your parenthesese. (I believe the last one is in the wrong place...should be ahead of AND statement.) I am also suspicous that, somehow, your variable is defined as a STATE type, but without seeing all your programs and knowing what buttons you pressed, it would be speculation on my aprt why your other programs would be running

Mango, if you decide to try the program solution, I want to emphsise the last pont made by larrylix: make sure the buttons are NOT in a scene that includes the iolinc as controller.

Well, broken is relative. Insteon is a known commodity. Broken, to me, suggests that it does not do something that it claims to do. This is like claiming that since insteon does not wash your car, it is, therefore, broken. There are no claims made about scene commands such as discussed. Perhaps a better way of putting is it that insteon is not well suited to meet everyone's desires...not suited for all purposes. Of this, I am more confident. This could be done with a program(s). Then, one would have create the echo>ISY command relationships. There may be some around here that can help with that. I am not one of them.

Yes, it could be done with logic. Yes, trigger reverse is an option. Both have subtle downsides. I prefer the alternate sensor. This is a topic that comes up pretty regularly.

From a purely intellectual and logical perspective, one would want to do this for the same reason that one would want to set a scene members level to something LESS than the pre-defined ON level. If we accept that there are times that one may want to turn on a scene a reduced values, it seems logical that there might also be times that one might also want to turn them on at increased levels, no? Fortunately, I find stusviews assessment spot on....nothing is broken. The insteon design allows for this by allowing the creation of multiple scenes. Pre-define scenes at the levels desired and call it a day. I would add, also, that insteon DOES include the options to redefine scene responder levels, correct? Given this, another question that could be asked is why echo cannot properly interpret a request to set set scene levels to something other than pre-defined levels is not properly executed using the tools at hand...ie, when is the echo going to get fixed? Ultimately, neither insteon, echo, or the ISY is "broken" in this case and expectations of any being fixed are misplaced. Instead, there are existing methods to solve this problem and that is: scenes and more scenes.

Without providing detais and explanation, your best bet is likely going to be to replace your sensor with a different type: normally closed, or NC. I dont believe they are very expensive.

Perhaps I misunderstand your problem, but I have not experienced a case where a program ran but the ISY status did not update. From where are you observing the status? Admin panel? Mobile app? But then, like larrylix, I don't use "fadeup" commands.

No need. Barring comm problems, status is maintained automatically. Switches report status when changed. Programs will update device status.

Further thoughts....is it possible that other program or insteon activity is happening between the separated programs? Might this activity delay the response of the subsequent programs? Have you ever opened an event viewer while executing the goodnight action?

Hey jerry, While I have never noticed programs, themselves, causing much delay, it seems to me your exeriments are petty conclusive. But...15 seconds!? Wow. It is almost hard for me to imagine that separating programs would introduce this kind of a delay.

"Normal" refers to the sensor state when sensor and magnet are separated. "Normally closed", then, is a sensor whos contacts are closed (zero resistance) when so separated. With the IOLinc, ON is when the sensor is closed. If you desire to install your sensor such that the magnet is seprated from sensor ("normal" condition) when the door is open, and an open door to be reflected by ON with the IOLinc, you would need, therefore, a NC sensor. Whether one way or another is backwards depends on viewpoint and installation.

Substitution variables. Not something I have ever used or needed, but I may try one out. I understand the "#" represents the address of the device that causes a program to run, correct? Thanks for the tip!

Nothing is jumping out at me as far as ideas to reduce number of programs. My only thoughts are to put all these into a program folder for organizational purposes only.

That is what most do, I suspect. Add an insteon motion sensor....door sensors.....fun times!

For me, remote control via phone is a minor concern. I don't have a lot of interest in such things. As others have mentioned, for android, it is the integration with Tasker that most excites me. This provides the ability to automate things based on cell phone conditions, such as location, connection to a car Bluetooth, things like that. But, for those few devices for which I occasionally control via cell phone (garage door, outside lights, door locks) I like the widgets that one can create, either through tasker or directly with mobilinc. I do not like the idea of opening an app and navigating through pages just to turn on a light.

Jeff, I use mobilinc app (android version) to gain access to my system. It DOES provide ability to rename states. I use it for doors and locks.

All you are trying to do is manually control an irrigation zone from a keypad button? Sounds like you have done everything correct to me, but make sure you added the KPL button as a "controller" of the scene. I believe controllers show up as red in the scene listing.

Yes, that would explain things. Also, if they come on at night and sunrise occurs before they turn off, they will remain on.