oberkc

That would be my conclusion, as well.

As I understand STATUS conditions, any change in status would trigger the program evaluation.

I tend to agree that your first program should work, assuming that I understand your requirements. I suspect issues other than the program are in play here. What happens when you choose the program>>run then? Does the keypad turn off? When the main KPL is off, what is the status of the program? Is it TRUE?

Yes, since you are using "control", Both would need to be there, separated by an 'or'.

My first instinct would be to make sure your ISY software is latest (though having worked before suggests that this will not solve your problem). You did remove the device from the ISY before readding, correct?

I am curious why you have "Run Program 'kitchen day light action' (Then Path)" in two programs. I see that you also have "Run Program 'kitchen night action' (Then Path)" in two programs. I suspect these two programs can, at times, fight each other. Perhaps taking these actions out of the reminder program will help reduce your problems?

The best settings are, partially, dependent on how one intends to control the IOLinc. Other settings are more universal. One most certainly should use momentary mode. Whether using A, B, or C depends on other factors. Personally, i use a keypad button to trigger the door, set to non-toggle ON mode, withIOLinc set to respond to ON commands (momentary C?). Some settings are dependent on how you have the sensor wired and the type of sensor. Status of the relay is not always accurate. The relay is not a controller capable, so it does not transmit status. Displayed status is typically the last command sent...not necessarily accurate. I do not find relay status to be anything useful. Regarding mobilinc, i believe it is best to use scenes to trigger. Look at the sensor node to determine door status.

If you have no scenes, then I believe the scene test difficult. I recall it being something like tools or diagnostics. Mi cannot access my control panel right now to verify. I am sure you can find it in the wiki if you care to check out.

One- or two-second delays may be the result of marginal communications. Have you ever performed scene tests? Do they generally pass?

I think I once asked such a question, and the answer was "no". I have no recently explored newer versions of mobilinc, but I have not noticed this capability having been added. I use android version. May be different in iOS.

The physical indications from the switch gives me concerns. It is certainly strange to me that you would have multiple failures so quickly. I would certainly be looking for any unusual conditions....high voltage....noisy devices....high loads. My temptation would be to perform a factory reset on the switch. If the switch begins to behave normally after that, try a restore from the ISY.

Is it possibly a wiring problem? Are these intended to be part of a three-way installation, or did they replace devices that were?

The theory is that "control" will trigger whenever either (or) either of the switches is turned on manually. When that happens, the timer program, if it is in a wait state, will halt, and the program run the ELSE clause (which has nothing in it).

The only other thing I can think is to choose the questionable device and "show device link tables" then "compare". If there are mismatches, once again "restore" the device.

For a given H button, have you looked at scene membership...."is controller of", "controlled by"? When you press the H button, do devices come on that are not listed in one of the scenes? Have you observed your program status list when you press the H button? Do any programs activate? Open an event viewer. Press one of the H buttons. Do you see any signs of an X-10 address? There is nothing in my experience where devices respond to other devices without a reason such as being in a scene, a program, or having X-10 addresses assigned.

I understand the scene test is not conclusive...only an indication of the quality of communication. Sometimes, too, the devices respond as expected, but the return confirmation fails. This would, I understand, cause a failure of the test. It is also, in my mind, something that should be corrected. Another thing that can cause a failure is if you have programs enabled that are triggered by the devices in the scene test. Make sure you disable any such programs. Finally, I have found it necessary to run a test several times, and am generally satisfied if it pass most. Do you notice any particular slowness in the response by your devices? Is it near instantaneous?

Other than those goofy, toyish buttons, I don't see anything remarkable. A button besides your bed that, when pushed, turns on some lights and coffee maker. A button by the front door that advises you when your daughter gets home. Did I miss something?

It sounds like you are wise and practical. I am with you regarding the price of devices. I expect that smart devices will not last as long as the dumb ones, so there will be a noticable cost maintaining your system as devices fail. Still, I enjoy conversations about this topic, and the general state of automation. Given the recent proliferation of protocols, and given things like the new apple "home kit", one capability I value highly (and suspect the marketplace will reward) is the ability to integrate different types of devices, beyond insteon. I suspect prices will come down on these as competition heats up. In fact, I was shopping recently and stumbled upon a random clearance table of stuff, and saw a couple of z-wave modules for about $20 each. Back to the ISY, as much as I have enjoyed this thing so far, I believe the potential is still relatively untapped. The introduction of the z-wave module for the ISY and the initial inquiry into the home kit and insteon/microsoft partnership can potentially be the biggest benefit of having an ISY. This could let you pick and choose from a wider assortment of devices (beyond insteon) and choose those that meet your needs for price and value. Over time, it could be cheaper overall for those with an ISY than those without if one is a careful shopper.

I would use a program. If Control switch is switched on Then Wait 10 minutes Set switch off Else Nothing

At the risk of repeating some of xathros explanation... Which is, as explained by xathros, what the CONTROL condition does. Well, that is why we are all here...to help each other see things. At the risk of repeating (think of it as emphasising): this is exacly how a CONTROL condition works. CONTROL only triggers when a device, itself, initiates an action. When the device state is changed indirectly, CONTROL conditions do not trigger. Please note in my suggested status program, I used a lot of CONTROL conditions. This was not an arbitrary choice, and should handle the concerns about which you speak. This could be true if one were using a STATUS condition, but not if using a CONTROL condition. I do not believe that this is the case, so long as you are willing to live with the limitations associated with a scene. It is only because you are trying to add conditions to WHEN and IF and HOW BRIGHT that force one into a program and contribute to the delays. Reading many of your responses, it seems to me that the struggles that you are having are due to an incomplete familiarization between STATUS and CONTROL conditions, and when programs are triggered. I am happy to elaborate further if you are interested in trying to make the ISY work.

I understand you may be finding that the ISY is more than you need and taking too much time to be worth it. Many enjoy the challenges and benefits. It sounds as if you are not one of them. That is fine. Having said that, it does seem like you are comparing apples to oranges. In my mind, you actually are trying to accomplish a relatively complicated set of criteria and responses, far beyond what the hub is capable of doing, and probably more than one should attempt on first try. It also sounds as if you are dealing with some issues beyond the programming. If I may offer a suggestion, why don't you try something a little easier to start with? Why not set up a simpler program to trigger upon motion, but to reset the timer when motion is sensed again? For now, skip the time constraints, the variable response levels, and the manual disabling (all things that I don't believe the hub can even do). Most of us, I suspect, learned by starting simpler, then expanded our reach from there. If interested in continuing, let us know. If not, have fun with the hub and the money saved. (saving money is always nice and, yes, this can get expensive.)

I think I would first create a very simple program that serves, simply, to act as a condition for other programs. if control switchlinc is switched on or control switchlinc is switched fast on or control switchlinc is fade up or control switchlinc is fade down or control switchlinc is not switched off or control switchlinc is not switched fast off then stop timer program else nothing This program is looking for manual presses of the switchlinc and will evaluate TRUE (runs THEN path) when the switch is manually turned on or brighten or dim, and will evaluate FALSE (runs ELSE path) when turned off. It will also stop any ongoing timer countdown if runs true. Create a timer program (probably needs to be done first, in order to create the first program, above). This program needs no conditions, but will be called by subsequent programs: if nothing then set switchlinc to 100% wait 10 minutes set switchlinc off else set swithlinc to 9% wait 10 minutes set switchlinc off From there, I would create a couple of programs similar to those suggested by stusviews: if time is from 3pm to 10pm (same day) and first program is false and control motion sensor is switched on then run timer program (THEN PATH) else nothing next program: if time is from 10pm to 3am (next day) and first program is false and control motion sensor is switched on then run timer program (ELSE PATH) Syntax is, I am sure, not exact, but I hope you can get some ideas. For the sake of time, I offer no commentary or explanation why I suggest this approach, so feel free to ask if the purpose of these is unclear, or if how this approach meets your needs is unclear.

I know that I am late to the party here. Been gone a bit, enjoying some time with friends. I would have thought that this could, and should, be done entirely with scenes. It may depend, however, on the age of your keypad device. I fear, however, I don't fully understand what you want to happen in a couple of scenerios. First, what do you want to happen to the lights and fan when press master ON? If, in fact, you want the lights to go on full and the fan to come on, this should work with scenes. This is what I am assuming. Second, if button A is on, and you press again button A, what do you want to happen? I will assume you want it (and the linked lights) to go off. Third, do you want anything to happen to the master button when you press buttons A, B, or D? Do you want it to turn OFF? Do you want it to stay in whatever state it started? I will assume such. Given these assumptions : - I would not use radio buttons. - Create a scene with buttons A and B as controllers and light micro as responder. For controller A, set Light ON level to 100%, set Button B ON level to zero. For controller B, set Light ON level to 65% and button A ON level to zero. - Create a scene with button D as controller and fan micro as responder. -Create a scene with Main button as controller and buttons A, B, and D and both micros as responders. For Main controller, set responder levels to A=100%, B=zero, D=ON, Light Micro=100%, Fan micro=on. - consider that there is also the possibility of configuring this keypad into an 8-button configuration and creatively modifying a frame and using large buttons across two to achieve very interesting possibilities. In response to a couple of your original questions: buttons can be manipulated by scenes. Set responder ON levels to zero, if need be. Yes, they would, depending on how you define "on". Thus my question: what DO you want to happen when you press master ON if not have the lights and fan come on?

I cannot help with problems specific to irule. for those...yes...probably better luck in irule forum.

Great point.