oberkc

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.

ISY would see insteon traffic. However, part of the process with ISY is to add (link) devices to it. One sets the ISY into linking mode, then does the same for the device. This process identifies each device to the ISY.

I am wondering, like TS99, if your "keypad A-F2" is in a scene with your kitchen lights. I am also wondering if you would be better served if you use "control" for your condition, rather than "status". A remote (in my mind) possibility is communication problems. Though I don't think I have seen this, I wonder if some devices flash their load if experiencing comm problems. I know that the keypad lights do.

I checked and stand corrected. My memory is worn out. I created this program: If From 4:45:00PM To 7:45:00PM (same day) And Control 'SW LRW Livingroom Wall' is switched Off Then Set 'PM LRT Livingroom Table' On Else - No Actions - (To add one, press 'Action') this one kept turning the lights back on, after I switch them off. Changing the condition from 'control' to 'status' produced the same results.

Depends on the program. If you have a program something like: if from 5p -10p then set light on else Such a program would ensure the lights stay on during that period. If you turn them off, the program would execute the else statement, because the condition (between 5 and 10 pm) is still true. A program such as if time = 5p then set light on else This is a one-time good deal, where the condition is only true for a moment on any given day. At 501, the condition is no longer true. If you turn the light off, the program will not re-execute anything.

I also look forward to understanding the benefit to two programs, one for light, and one for sunset. My inclination is to run two programs, on and off. On would be based on light or sunset. It would have no "else" conditions: if light = 0 or time = sunset then set scene 'outside lights' on else if time = 900p then set scene 'outside light' off else I suspect part of your problems ealier was with the program re-evaluating itself every time the conditions change, then running the else statements. Another potential problem with your first attempt would be that the program may prevent you from manually turning the lights off before 900 if you choose. That would bother me. Of course, there are many ways of doing what you want. You could use folders, you could nest programs within programs. You could use multiple programs. Experiment around and have fun.

I am unfamiliar about light levels, but is it possible that they don't get ever to 0? If so, this program might not work for you. If light >0 and sunset, I expect this program to run the "then" statement, but immediately run the "else" statement when time is not sunset. One can copy programs and paste to the forum. I am having to go by memory, but I am thinking right click on a given program, and choose copy.

I assume that your line would first go to your panels. Does the same main line feed both panels? 240 and 120 outlets would have to be wired from a panel. I understand that there are hard-wired phase couplers. I think if I had the flexibility to design my wiring for insteon, this is what I would use. I would also include a couple of access points for remote links and additional coverage. I am not sure about the ability to transmit signals from panel to panel, but assume that if the same lines feeds both, you should be good. If not, then a couple of access points may work well for you. I have had good experience with a dedicated circuit for the PLM. Mine is run from the panel to the office, where the computer is located. Nothing else is on that circuit. I don't believe that there is a plug-in coupler advertised specifically for insteon, but I have heard that the one for x-10 may indeed work for insteon. Regardless, I can report that x-10 couplers can at least coexist without any apparent problem.

I suppose there could be some type of hardware failure. Short of that, is it possible that some device came on in your house which would cause a lot of noise? Furnace? Refrigerator? Is your X-10 still working?