Algorithm

cherokeesix, If by "pressed-on twice" you mean FastOn (a quick double-press of the paddle), then this program should do what you want: If Control 'Front Yard Lights' is switched Fast On Then Set 'Back Yard Lights' On Else - No Actions - (To add one, press 'Action') Another program could similarly turn the back yard lights off when the front yard light switch is turned FastOff. If, on the other hand, you want a single press of the front yard light switch paddle top to turn on the back yard lights, but only if the front yard lights are already on, then try this: If Status 'Front Yard Lights' is not Off And Control 'Front Yard Lights' is switched On Then Set 'Back Yard Lights' On Else - No Actions - (To add one, press 'Action') and a similar program for Off. The reason for the Status line looking for is not Off rather than for is On is so that it will be true if the light is at some arbitrary on-level, such as 44%. That will never be the case with relay switches, but it allows the program to work equally well with dimmer switches.

That's a good question. The switch would first send the INSTEON command, followed by the X-10 command. It should appear in the Event Viewer. Please do let us know what you find.

Hello John, Please change your program to: If ( X10 'M3/On (3)' is Received Or X10 'M/All Lights On (5)' is Received ) And X10 'M3/Off (11)' is not Received And X10 'M/All Units Off (13)' is not Received Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') which should reflect the correct status. In the Event Viewer, please try changing the Level to 1 or 2, and you should see the X-10 traffic.

cherokeesix, That sounds suspiciously like X-10 addresses in your switches. It is frequently reported that Smarthome devices are often shipped with X-10 addresses in them, left over from testing. Please check the manuals for your devices, for the procedure to remove an X-10 address. Alternatively, you could factory reset each device (to remove the X-10 address), followed by a Restore Device in ISY. Many users make it a habit to do a factory reset on every device received from Smarthome, before putting it into service.

drw, Thanks so much for reporting it. The problem, though minor, does manifest itself in various ways, so some users may see differing symptoms.

drw, Thanks so much for the tests and update. The problem is that the current version of the 2.7 client has a minor issue with the release version firmware (2.6 for ISY-26; 1.0.0 for ISY-99i) which manifests itself in various ways, such as that which you have experienced. You should have no such problems when using the client from ISY, which is of course matched to the firmware within ISY.

Thanks so much.

drw, What firmware level is your ISY-26 at? And, does this problem present itself if you log in using your local IP address?

Hello sigdoc, Welcome to the forum! If you know the INSTEON address of your KeypadLinc, you can choose New INSTEON Device from the Link Management menu, and then enter your device's address. If you do not know the address, choose Start Linking from the Link Management menu, and then put your KeypadLinc into linking mode by holding the Main or On button (for 8-button or 6-button mode) for about 10 seconds, until the light blinks.

Hello Walter, Welcome to the forums! Although the stated specifications of the ICON devices were at one time true, there was also a time when the ICON devices being sold actually did have the same capabilities as their INSTEON counterparts (600W vs 300W, adjustable ramp-rate, etc.). So please do try actually setting some scene ramp-rates for your devices and see whether they respond accordingly.

Hi Mike, No that is not something new; the ICON device pages have always read that way. What isn't clear to me is whether they are saying that the ramp-rate is not adjustable only when locally controlled, or in scenes as well. If it applied to scenes, it would be extremely limiting.

jwagner, If you dismiss the Java socket error, are you able to access the Administrative Console? Are you using the same computer for both local and remote access? If it is a different machine, please check your version of Java on the remote access machine.

Hello Illusion, Thanks so much for the update, and the confirmation that it was not well managed with 2.6, but is with 2.6.6. I'm so glad all is now well.

I don't believe features of the newer KPLs are supported in this release. Please let Darrell or Michel confirm, but I think you'll need to upgrade to the beta firmware. That is correct. As I wrote in a previous post, if your KPL is v1.5 or above, you need the beta firmware for it to be properly recognized. However, that does not explain why your current firmware is properly managing your v1.65 KPL (except of course for the above mentioned anomaly), which is what I find strange.

Illusion, That is very strange. If your KPL is indeed v1.5 or above, you need the beta firmware for it to be properly recognized. Please do confirm the KPL version.

Do you have sliders for the other devices? There should be a slider for every load device in the scene.

In the 'off' scene tree, click on the KPL secondary button which is the controller of the scene, and in the right pane adjust the on-level slider for the load device of that KPL.

Hello Illusion, Yes, that is correct, that it is not possible on early versions of the KPL. Even on newer versions, a KPL secondary button can not actually turn the same KPL's load OFF--though it can turn it on and set its level. So the workaround is to have it set the lowest possible level (1% or 2%). Give this a try; if it does not work, it is likely that you have an older KPL.

The article has bee updated to: - reflect changes in 2.6.4 through 2.6.6 - add more detail and correct event sequence at startup - add info. re: initialization of folders and programs

Dave and Dave, Thanks so very much for the kind words; the accolades are really appreciated. We are working very hard on the wiki, and hope it will continue to increase in value to our users. Mark Sanctuary has been a great help with the wiki, and we sincerely appreciate the efforts of all the wiki contributors.

A new wiki article titled Scope, Precedence and Execution Order has been added. Its table of contents: 1 Scope 2 Operator Precedence 3 Evaluation Order 4 Statement Execution Order 5 Boot/Startup Sequence and Program Execution Order 6 Program Enabled Checkbox 7 Folder Conditions

Zellerman, Excellent! Glad it's working, and thanks for keeping us updated.

Here's another idea posted by user dBeau on cocoontech.com: use a single-gang box and install a regular outlet into it. Use an attractive three-conductor extension cord in a colour that matches your table-top enclosure (white/black). Cut the female end off the cord and discard. Cut the remaining cord into two sections, the shorter section having the plug on it. Wire the short (plug) section of the cord into the gang box, and the longer section of the cord from the gang box to the table-top enclosure, so the SwitchLinc/KeypadLinc load controls the outlet. This way, the table-top enclosure still has only one cord leaving it, rather than two, and there should be no problem with the strain-relief grommet. dBeau provided a picture; the thread is at Hardwired lighting control and desk lamps, free-standing lamps, plug-in lamps and it is post #5.

Zellerman, If I understand correctly, your bathroom exhaust fan (presumably controlled by an InlineLinc, SwitchLinc, or something similar) is a responder in a scene of which the bathroom light switch is the controller. So when the light is switched on, the fan turns on; when the light is switched off, the fan turns off. You use a program that watches for the light switch being turned off, and then turns the fan back on, waits a period of time, and turns the fan off. The problem is to prevent the fan being turned off by the program, should the lights be turned back on. Is all of that correct? If so, try this program: If ( Control 'Main Bath Lights' is switched Off Or Control 'Main Bath Lights' is switched Fast Off ) And Control 'Main Bath Lights' is not switched On And Control 'Main Bath Lights' is not switched Fast On Then Set 'Main Bath Fan' On Wait 10 minutes Set 'Main Bath Fan' Off Else - No Actions - (To add one, press 'Action') Though it is not shown, the parenthesis are an And ( .. ) parenthesis, and the line Control 'Main Bath Lights' is switched Off is an Or condition. This program watches for the light switch being turned off or fast off, then turns the fan on, waits 10 minutes, and turns the fan off. If the light switch is turned on during that period, the program stops running the Then clause, so the fan does not get switched off. When the light is again switched off, the sequence begins fresh. You don't have to watch for the Fast Off. If you leave that out, you no longer need the parenthesis: If Control 'Main Bath Lights' is switched Off And Control 'Main Bath Lights' is not switched On And Control 'Main Bath Lights' is not switched Fast On Then Set 'Main Bath Fan' On Wait 10 minutes Set 'Main Bath Fan' Off Else - No Actions - (To add one, press 'Action') Though not shown, the line Control 'Main Bath Lights' is switched Off is now an And condition, rather than an Or condition. With this program, turning the light fast off will not turn the fan back on. This might be useful if you want to have that option.

ozone, I do believe Clarence was suggesting adding a socket to the table-top enclosure, and that will work fine. However, your solution would work equally as well, whether with a SwitchLinc or KeypadLinc in the enclosure, and would not require modifying the enclosure in any way. But you would need to link the enclosed switch to the lamp module of course. While your solution does not eliminate the lamp module, it also does not require local control of that module via the lamp's own switch. Dave, Yes, I agree completely with your assessment of a two-way device with local control, which does not report its control! Do we dare hope that Smarthome may eventually address that shortcoming?