oberkc

If you are refering to the remotelinc, the answer is yes. Two caveats: 1. You need an access point to recieve the remotelinc signals and put them on the powerlines 2. The remotelinc needs to be put into program mode when making changes

As one who is yet to understand the details of program status, how long does Ampoff program remain true, and under which events or conditions would it become false?

I can only speculate about Mobilelinc, but I would have assumed that it is just a fancy, finger-friendly shell in place of the admin panel. It would surprise me very much if it re-defined scenes in ways different than programmed at the ISY admin panel. Out of curiosity, I will follow this topic on the mobilelinc forum.

I have a question. Do you want one KPL to indicate that you are in school mode, and a second button as an override? Do you want the override to stay on indefinitely, until you manually turn it off, or do you want it to reset itself each day? My intial reaction, were I doing it, would be to use a single button as indication and override. I would set up a program to turn the KPL on at a set time each afternoon (sun - thurs at 200p for example) indicating that school mode will run the following morning. If I did not want it to run the next morning, then I would simply turn it off each evening beforehand. I believe also that I would have a program to turn the KPL off on Fri and Sat afternoons. As you suggested, you could have a folder that contains your morning program with the folder condition to include the KPL button being on. Without knowing why, my temptation would be to create a scene to include desire devices as responders, then create a simple program: if KPL button is on and time from 0600 - 0900 (or whatever time you want) then set school scene on else set school scene off While simple, it does not account for holidays or extended breaks (Christmas, summer, presidents day, etc). One would have to remember to turn it off each day, rather than turn it on. Of course, you could disable the program during extended times, but that is inelegant. Perhaps a better option would be to simply have a manual KPL button. Leave it on always, unless there was a scheduled break from the M-F school schedule planned. The program above could be modified as follows: if KPL button is on and time from 0600 - 0900 on m-f (or whatever time you want) then set school scene on else set school scene off Please understand that these programming suggestions are not precise. I cannot recall the exact programming verbage, but I am hoping it can spark some ideas. I am sure there are other good options out there that others will suggest.

Controllers are, by definition, also responders. Like the others, I have no explanation why this is not working, but have the same thought process as sub-routine. Restore the device. Perhaps, also, you can compare the links table to see if you have something amiss. In addition, what happens when you turn on the scene from the ISY admin table? Does the KPL respond as it should? If not, is it possible that we have some communication issues between the PLM and KPL? Perhaps a scene test on this scene would be enlightening. Troubleshooting is fun, huh!?

Based on your latest description, I think I understand what you are seeing. That is not what I would expect, either. I would expect to be able to set the kit or dining KPL main ramp/dim levels based on buttons H from that same KPL. I would also expect your main buttons to react to scene commands, based on the way you have your scene defined. Unfortunately, I will not have time to compare and confirm with my admin screen until later this afternoon. I would like to confirm that I don't have similar issues. I can tell you, however, that I have a couple of 6-key KPL where the main and secondary buttons are part of the same scene, and it works flawlessly. Unfortunately, I don't recall having any 8-key dimmer KPLs where a main and secondary button are part of the same scene. I may have to experiment. Hopefully, someone can offer suggestions before then. I am also guessing that it may be important to know which version of ISY software you are using.

If, in the admin console, you choose the KPL H button on the left, you don't see, at the right of the screen, where it manages the KPL Main device? If you select the scene in question, do you see both devices listed below? As I understand it, you should see KPL H button as a controller and KPL Main button as a responder. If you don't see both, add the missing one to the scene.

I use only X-10, but based on reading these posts, reciept of an X-10 off command does not halt programs based on X-10 on commands. I consider this a benefit of the X-10, at least for motion sensors.

I have a scene, called landscape, where I use a six-button KPL button C to control a scene which also includes the primary button of that same KPL. On the other hand, I think I may have read somewhere where one cannot control a primary button of a given KPL via one of the other buttons. (Obviously, that is inconsistent with my experience.) Perhaps, too, this is peculiar to certain versions of a KPL. While I cannot explain why you cannot do what I am able to do, perhaps there is a work-around until we can get to the root cause. You can consider setting up a program to activate the scene, based on the control of a keypad button. Try something like: if: control 'kitchen KPL H' is switched on then set scene 'main' on else

Originally, I thought it was that your scene had to be in a consistent (either on or off) state. Now I wonder if it must be off in order to succesfully write. It is my understanding that device or scene state, in and of itself, will not prevent the ISY from writing to devices. If you are having trouble writing with devices on, but can write with the devices being off, I cannot help but wonder if the loads on those devices are causing (or further contributing to) noise and interference. Are the loads connected to your insteon devices something other than incadescent bulbs? Of course, it is possible that you have faulty devices. I understand that certain versions can have problems (v3.5 switchlincs, if I recall). I do not recall hearing that "older" versions are necessarily a problem. Based on your latest post, I would check a couple of things: a. what versions of switchlincs to you have and are any v3.5? b. perform a scene test on your trouble scene and see if you have any indication of communication problems. Try it with the scene on and with it off.

. I came away with this same understanding. And I have the same situation as MarkJames. None of mine are consistently consistent because of multiple scenes with the same devices. I would look again at the rest of the statement:

i have not experienced any problems writing to devices based on device status. I don't recall having seen any green arrow-like symbol, either. A couple of things come to mind, however, based on your post. I don't think it is necessary to go to each device to put them all in the same state. Could you not do this from the ISY? From the admin panel, choose the scene in question, and toggle it on or off. This is a shot in the dark, but I wonder if this is the batch processing capability in one of the recent software builds. I am currently using 2.7.7, which does not have batch mode as far as I understand. Which version are you using? Is it possible that you have yours set for batch mode and the ISY is waiting for further action on your part before initiating the changes? Another shot in the dark....are you writing to "scenes" or to "programs"? There is a little green symbol when one makes changes to programs. This is an indication of pending changes and one must press the "save" button in order to make the changes permanent.

I think I am with MarkJames on this one. Please elaborate. I am not following your thoughts here.

If the ISY queries the controller, then it will show whatever state is in. If it was off before you turned on the light, then it will remain off and the query will show this state. I don't expect any errors as a result. Based on the configuration you describe, if you toggle the controller switch, the responder devices should respond. If you toggle one of the responder devices, it will have no effect on the other devices within the scene. Of course, if a load is attached to a device, it will come on if you toggle the switch controlling that load, regardless of whether it is a controller or responder. It is my understanding that the ISY/PLM is also a controller of this (and all) scenes. It can control any scene, even those without a defined controller device.

First, I am not sure that devices have true or false status. They are on or off, dim or bright, etc... Programs can have true or false status. Second, I understand that turning on or off a responder device within a scene will have no effect on other devices within the scene. That is, the status of one device will remain unchanged as a result of the action of another reponder device. If a device (whether responder or controller) was off before another responder within the same scene was changed, it will remain off. If on, it will remain so. etc...

iceberg5xx, I am curious about the difference between buttons remotelinc and remotelinc-2? Did you intend your second "if" line to be a different button that all the rest? Perhaps, also, a statement about your intention for this program would help. What are you attempting to achieve? Also, you state that you are using buttons 1-3 to trigger various scenes in your house. Is 'remotelinc - 2' one of those buttons 1-3? Is it possible that 'remotelinc - 2' is a controller of one scene yet a program trigger of another? Barring conflicting scene controls, I wonder if whether you have so many "if" conditions that they are competing with each other. Why do you include both status and control? My instinct is to start fresh with your conditions, to see if you can trigger the scene with a simple: If control 'Remotelinc-2' is switched on. If this works, then add the other conditions until you find the one that breaks your program.

I apologize for the confusion. It is actually "from". Under the program details tab, add to program: "schedule". In the little schedule window, choose the drop down arrow at "time is", and you can choose "from". This will give you beginning and end times. The actual condition will end up looking like: If From Sunset To Sunrise (next day) Then Else

First, perhaps we have not been as clear as we should. One does not actually "write" programs. The ISY does this for you, based on conditions and schedules and actions you define. I believe you will have a problem with your program. It may not actually shut the lights off (it is always "after" sunset, whether a few minutes or 23 hours). I believe you should set the second condition to: "and time is between sunset and sunrise".

see bktong post. Apparently, newer models beep or something when you press them

1. You now have a spare 2. You can use the old one in a different application, making your system better Other than that (and the dimming and, I guess, sound), I am unaware of any major advantages.

Can you not manually dim the older KPLs? Perhaps this is not dim enough?

How is your exterior post light controlled? By the switchllinc? What does your switchlinc control directly, if anything? Perhaps I understand your question a little differently now. If your switch is off, you want your lamplinc to go off at sunrise and to 30% at sunset. You want this to happen continuously for as long as you switch remains off, not just at the moment your switch is turned off, based on the conditions at the time. If I understand correctly, there are a couple of ways that I would consider tackling this problem. One way would be to substitute status for control in my previously suggested two programs: if from sunrise to sunset same day and status of switch is off then set lamp to off The second program would look something like: if from sunset to sunrise next day and status of switch is off Alternatively, you may consider creating a program folder which is active when the status of the switch is off. In this folder, place a program: if from sunset to sunrise then set lamp to 30% else set lamp to off Of course, you will want to test these to confirm that they work as you intend.

It is possible that I misunderstood, but the two requests I see are for 30% and off. Did I miss something?

I would try this with two programs. The first would cover the period between sunrise and sunset: if from sunrise to sunset same day and control switch is set off then set lamp to off The second program would look something like: if from sunset to sunrise next day and control switch is set off then set lamp 30%

You can also check the log file. While I have not taken advantage of this, you can also set up a program to send you an EMail message.