Michel Kohanim

You cannot have the different KPL buttons of the same KPL in the same scene. Sorry; you might want to submit an enhancement request to SmartLabs!

The answer to your last question is: Not yet. We are working on it inconjunction with our triggers. With respect to your other questions, all you have to do is to create schedules for your already created scenes. i.e. you already have buttons, controlling a scene, which do the same thing that you want your scheduler to do. As such, simply create recurring schedules for that specific scene.

Sloop, please forget about the press and hold; you don't need press and hold again. All you have to do is: a. Create a scene and call it Whole House (e.g.) b. Drop in each and every one of the KPL buttons that you want to have control the Whole House Scene c. Click on the Whole House scene, assign on level and ramp rates for each and every one of the KPLs to your desired settings d. If you want all KPLs to have the same scene attributes (on level/ramp rate) then simply click on each and every KPL button, in Whole House scene, and then click on Copy Attributes from Whole House Your are done: each button will do the same exact thing as the others and when you click on one the others will be illuminated

You cannot have different buttons of the same KeypadLinc in a scene simply because you'll corrupt the KPL's database. You can try the press-and-hold method but a) your KPL will start acting up. The best solution for this scenario is a trigger!

Sloop, here we go with Scenes 101: 1. Scenes are are simply a group of devices. Scene is equal to a group in INSTEON vernacular 2. Each device in a scene can have its own on level and ramp rate regardless of its local on level and ramp rate. Example: If you have a scene called sloop, and you drop in slooplinc1 and slooplinc2 in there, then you could assign: slooplinc1- on level 50%, ramp rate 2 mins slooplinc2- on level 70%, ramp rate 5 mins So, now, when you go to your computer and click on the "sloop" scene node (on the tree to your left), and when you press the "on" button, then slooplinc1 is going to "start" turning on to 50% which should take 2 mins slooplinc2 is going to "start" turning on to 70% which should take 5 mins If you click on "fast on" or "fast off", neither the ramp-rate nor the on levels apply. 3. Now, let's go one step further. Let's assume that now you are going to drop in one of the KeypadLinc buttons into the sloop scene. If this is a the "load" KeypadLinc button, then you will be asked whether or not you want to make this button a "controller" or a "responder". If a "controller", then you can assign on levels and ramp rates for "slooplinc1" and "slooplinc2" in the same way that you assigned it for the "sloop" scene. The only difference is that now, instead of ISY, you can control slooplinc1/2 from the keypadlinc button you drop in Now, with this out of the way, the answer to question 1: If you already have all your devices linked in ISY, then you would never ever need to use the paddle press/set button on any of the linked Insteon devices unless you wish to reset them. For your scenario, all you need to do is create a scene, and drop your SwitchLinc relays in there and both as controllers . This shall mimic your three way set up since each relay controls the other. Whoooah .... On to the next question (how am I doing?) Question 2 Ditto (above). You would never ever have to ever never click on that set button unless you want to reset the device

sloop and Mark, Partly correct! If you set the ramprate and on level on a device and outside a scene, you would have to do a device reset (pull out the set button and then push it back in) before the settings take effect. That's an Insteon thing which is totally out of our control. This said, however, if you apply ramprates and onlevels to devices within a scene (either by clicking on the scene icon or by clicking on a controller within that scene and adjusting the on levels and ramprates for each device therein) then you do not need reset the Insteon devices. I hope in makes sense and, if it doesn't, please let me know and I can call and walk you through it. With regards,

My pleasure. Enjoy! With regards,

AeroWeb, ISY is compatible for Europe; INSTEON is NOT and, as such, it would not make sense to use ISY in Europe until such time that INSTEON becomes 220/230 friendly. We do not support X10 at all. With regards,

B.J. The url to be used for accessing ISY remotely is slightly different. You should use: http://external.ip.address:16142/0/x (note the last character is x - for external - rather than p) Please let us know if this resolves your issue. Thanks and regards,

Mark, firstly thanks for starting this thread. I really do appreciate it. --- Question 1 --- This is an excellent question the answer to which must be "ISY should never lock up" and we would like to strive to achieve this. Version 2.0 solves as many lock up situations as we could find. This said, however, we would sincerely appreciate it if any one experiencing lock up situations to notify us with some details of the situation when it happens. Apart from that - and if ISY locks up - what you outlined is (at the moment) the only viable solution. Thank you,