oberkc

Perhaps, also, I missed this....which device actually powers the room lighting? Is it one of the two dimmers, or is there a third device in the mix somewhere?

If the LED indicators on a switch move, but the light does not come on, I would tend to consider three possibilities: - loose wiring connection somewhere - failed bulb - failed switch I would be checking voltages at red wire on switch to see if present. If not, switch is possibly failed. (Sometimes a factory reset can "fix" a failed switch.) If the voltage is present, I would consider the other two possibilities.

I expect (made no attempt to locate a user manual) this to be a simple on/off switch. If so, I do not expect that you could use it as part of a three-way installation. I don't know how official you need, but that is as "official" as I can be. How many wires does it have coming from the switch, and what color are they?

Does scene 'Scene: Mbath Off' include any of these devices : 'Main House / Master Bath / Main: MBath Toilet Light' 'Main House / Master Bath / Main: Mbath Shower' 'Main House / Master Bath / Main: MBath Keypad' If so, your second program may be retriggering your first, which re-fires your second, which retriggers the first, etc..... You may have created another infinite loop here.

A quick lookup on 2470D switchlinc suggests that this is a "non-communicating" switch. I have no idea what benefit such a switch would have over any other dimmer switch, but I assume it is NOT insteon or X-10 capable.

"If I come home while the program is in the wait state and push the KPL button, turning the away variable back to a zero, the program seems to stop and never turns the light back on" I am a little confused. If the program is in a WAIT state, is not the light already on? Why would you expect the program to turn it "back on"? I would describe things a little different than LeeG. I undedstand programs can, in fact, run when in a disabled folder. They will not, however, self-initiate from their own conditions. They would run only if called externally, such as from another program. I am not confident with this, but I expect that a program, once running, would continue to run even after a parent folder becomes disabled. If I wanted to be certain, I would set up a simple experiment, with a temporary program that includes a wait statement and disable the folder while the program is executing. I would watch program status at the point the folder is disabled and observe whether the program continues to run. Is it possible, in your case, that the program has a condition based upon the away button or variable?

Absolutely. The responder levels will be based upon the "scene" parameters.

I would first confirm which of your nodes is changing when the drum is rotated. Once determined, I would follow the programming suggestions of LeeG. With the ISY, one can test for "status" and/or "control" for any given device.

I which case, you might not be getting signals from both nodes and one node moght be stopping at OFF. Best bet from here is to identify which nodes are changing status as the drum rotates.

My inclination would be to configure the buttons as non-toggle (off) and trigger a program from the button OFF command to turn on the scene.

My first inclination to wonder whether the use of of a sensor triggered on each drum rotation is a practical solution. I wonder if flooding the powerlines with insteon commands more than once per second will have unintended consequences, or whether it will even work reliably. Second, I am a little unclear how your sensor works. Does it have both an OPEN and CLOSED node? (Is it one of those wireless door sensors?) Does each node change status once per drum rotation? Is it possible that the status of your sensors are not updating fast enough that the ISY believes both sensors are OFF at the same time? I dont see anything wrong with the program that would cause intermittent problems. Have you ever watched the device status, program status, or the event viewer while the dryer is in operation?

Based on my experience, non toggle buttons will all blink a few times then settle into final status.

Yes, it seems that the definition of "scene" varies based on controller. With the ISY, create a single "scene" adding all keypad buttons that you want to trigger the scene as controllers. If there are other devices that actually power the load, but are not to be used as scene controllers, add them to thesceneas a responder. Each controller in this scene can be configured to drive different responses by the other devices in the scene. Click on each controller and adjust reponder ON levels and ramp rates for each reponder.

The only time this set of conditions will trigger AND evaluate as true would be when the button D changes to ON for any reason except (possibly) when it changes to ON as a result of FASTON action directly from the keypad button, itself.

This is consistent with my understanding. Secondary (non load controlling) buttons are either ON or OFF. They can send dim and bright commands as scene controllers, but, themselves, are either on or off.

I would take a simpler approach. One scene, including only the keypad button. One program: If From 8am to 4pm Or from 11pm to 7am (next day) Then Set keypad button scene on Else Set keypad button scene off I would then use the status of the keypad button as the indicator whether your system is armed. I would use that as a folder condition: If Status keypad button is not off Then allow programs in this folder to run In the folder, I would put any program I want to trigger, but only when the system is armed.

Alsorrell, I suspect the single problem you had was that you did not configure your button as NON-TOGGLE ON. Perhaps a single scene would work, but your scenes looked correct as described. Set up this way, there is only one way for the KPL to be off...that is, for the sensor to turn it off. Given this, there is a high level of confidence that if the sensor is off, the door is closed.

I use two separate scenes, rather than a single scene, but this is an intriguing thought. Is there not concern that the sensor (as controller of the relay) might cause the relay to trigger as it changes state? Perhaps there are built in protections for this that I have not heard of or forgotten.

Your described behavior sounds abnormal from my experience. If a program runs, I expect it to show one of two outcomes: TRUE OR FALSE. I also expect this state to be reflected in the program listing. Next chance I get, I will confirm, but something sounds not quite right with your program status.

To LeeG's response.... Disabling a folder, by itself, does NOT cause the included programs to trigger, nor does it cause them to turn false. Disabling a folder simply disables the trigger inherent in each program condition. The included programs, simply, will not self-initiate. If a program last ran true at 4pm and the parent folder became false at 5pm, the program is still true. Programs in a folder, even if the folder condition is false, can still be triggered externally, such as when called by other programs or through the admin panel. When called in this manner, they will evaluate and execute the same, regardless of folder condition.

Jumper 5 allows control of motion sensor options via external sources. Yes, ISY can set those options if jumper 5 is in place.

To double check, have you written the changes to the motion sensor as you adjust the settings? Watch for little funny symbols down at the lower left of your program and device listing. They can sometimes indicate the need to write changes to the device. Battery devices are especially important to pay attention to that detail. They cannot be written to without putting them into linking mode.

Don't get too hung up on the actual programming words I used. This was conceptual (though it IS easy to miss "next day" in the condition). The ISY will create these for you.

Try something like: If Time is from sunset To sunrise (next day) Then Turn lights on Else Turn lights off If you actually prefer two programs, this is an possible as well

If you can figure out how to enable the motion sensor mode where it sends only ON commands, then, yes. What is jumper 5 set to? Is there a reason you are not setting this configuration through the ISY?