oskrypuch

That was bad juju. My wife acts likes she has "transparent eyelids", and insists on the LEDs being turned off at night in the bedroom. Leaving them that way during the day would make the switches largely useless, so I'm in a bit of bind. I've left my sunrise routine to switch to 12 ON/1 OFF, and at night it switches to 1 ON/0 OFF. I'll keep an eye out. * Orest

Ah, good, that makes things easier. * Orest

I suppose that is what folks do, easy enough to create at least a Boolean variable, and set/reset it by running the then/else clauses. When checking the status of the program (variable) in the condition group, I presume that it will act like the Insteon "status" check, vice an Insteon "control" check, IOW it would not trigger from a change in the program state but would simply allow you to branch based on its value. Yes, no? * Orest

KeyLincs using 2.7.15 This does not seem well described, or I've missed it. A couple questions ... 1) What is the "default" initial setting for the LED ON and OFF (background) levels? I understand that ON can vary 0 to 15, and the OFF from 0 to 7. 2) When you send an ISY program command for LED brightness, it has you select a specific keylinc button, I presume that that will still affect each of the device's buttons equally, that is only on preset brightness? * Orest

No, they were set to default toggle on/toggle off. But, there were two programs triggering on FKey1 - B, on was blocked by the status of FKey1 - G, but the other was just a straight through IF/THEN. Both THEN's just did a ding-dong. No matter what you did to the first program, the second would still ding dong. The other issue that confused the picture, somehow the labels in ISY for FKey1 - D and FKey1 - E and had been swapped, no doubt when I was labeling them. I finally realized that by looking at the status report. Things are working as they should now. * Orest

Tried a few things, and then changed the trigger button from FKey1 - B to FKey1 - D, then it worked! I had another little program I had set up earlier just to test out the ding-donger, it had been triggered by FKey - B, so it would keep running and ding-dong, when the program in question that we were puzzling over, did not. Ah well. I'm sure I'll have more questions for you. Thanks. * Orest

I'm new to ISY, was all X-10 and had a great setup with an old DOS program IDE which allowed for surprisingly complicated programming (including multi type variables!). Then lighting hit, literally, and killed a lot of units, and the controller. So I explored around and decided to go Isteon and ISY-99, a whole bunch of modules are on the way. Have done a lot of reading here, as well as the Wiki, and read through the manual. There certainly are some quirky aspects to the programming, but that isn't different from any other language when you first learn it. In any case, to the matter at hand ... If Control 'family rm / F-Key1 - B' is switched On And From 8:00:00AM To 11:59:00PM (same day) And Status 'family rm / F-Key1 - G - sensor' is On Then Repeat 2 times Send X10 'P9/On (3)' Else - No Actions - (To add one, press 'Action') Set up this simple routine to test the logic of a motion triggering an X10 ding-donger. Iinstead of the X-10 motion (will soon be replaced) I am just using the "B" key on the F-Key1 keylinc to trigger the event instead. The status of F-Key1-G is intended to toggle whether the ding-dong should be active, and of course it is time limited in its activity to the day. Unfortunately, regardless of the status of the"G" key on the F-Key1 keylinc, toggling F-Key1-B on the keyline to ON will always sound the gong. It just seems like it is ignoring this statement as a disqualifier ... And Status 'family rm / F-Key1 - G - sensor' is On ISY confirms that F-Key - G is OFF for the test. What am I doing wrong? * Orest