oberkc

I am simply making a guess here, but there are different ramp rates, depending on whether you speak of local control of a given device, versus control of a scene from one of the scene controllers. Are you trying to control a scene or a local device? Is the switch you control set up as a scene controller? I like your ideas, and it has inspired me to try something like this myself.

Good news on your new program. The one consequence to be aware of is that if you ever happen to use the individual controls to set the dim levels to exactly 40 and 30 percent, then the KPL will come on. Perhaps that is good? It is my understanding that all programs run all the time (unless disabled). I don't see why this one would be any worse than any other. It is looking for changes to the input conditions. When it sees them, it reacts per the if/then actions. I would expect no unique problems with added powerline communication traffic. I am not sure what program uses your "living room" switch. Is this a different program? When you refer to "adding" the familly room main, do you mean adding to a program, or to a scene?

Despite the definition of control versus status, I continue to be amazed at how many times suggestions on this forum are opposite of what I would have assumed. Back to your problem, I started to think your program is turning off your keypad before the scene is fully engaged. Do you suppose this is possible? I don't understand how long it takes a scene to react versus a program, but I suspect your program itself is acting quicker than the scene. What would one simply looked at this more simply? If 'Family Room Main' is 40% AND 'Family Room Recessed' is 30% Then Set scene 'MovieStatus' on Else Set scene "MovieStatus" off Would this achieve the results you are looking for?

I still remain uncertain about the differences between control and status. I recall some discussion about how one sends an on the off status. Since it is so easy to experiment, I would change the input condition from status to control and see what happens. As a troubleshooting attempt, I would also open the event viewer and watch the signal traffic as things happen. This may give a clue as to why your KPL goes off after a short time. Sorry I could not be more help. I will think more about it.

This approach sounds like it might be incloude some unintended consequenses, but that is only a gut feel. I don't know enough about the inner workings of the ISY to help much. As much trouble as I have had getting exact dimming values, I would first check to see if you have not accidentally set 39% or 41% as the programmed dim value and confirm that, in fact, 40% is the posted value when the movie scene is triggered. Assuming all is good.... Your program may need a couple of parentheses in it. Based on my understanding of boolean logic and your program, the first two conditions are evaluated as a group, with the third condition evaluated independent of the first two. Your progam may need to look more like... If Status '06.6E.FB.D KPL Movie' is not off and ( 'Family Room Main' is not 40% or 'Family Room Recessed' is not 30% ) Then Set scene 'MovieStatus' off Also, what are your ramp rates? Is it possible that a slow ramp rate would cause this program to evaluate mulitple times over a short time period?

You say that the device will run scenes on all buttons but that the ISY does not recognize it. How did you set the scenes up if the ISY did not recognize it? Did it once recognize it but now it does not? At the risk of sounding stupid: a. did you set all scenes up using ISY or did you create some directly with the devices? b. is it possible you changed the configuration of the switch from 6 to 8 key configuration after it was linked to the ISY? c. what buttons are now showing up in the event viewer, all eight or just the four you mentioned? d. have you added some new electronic device, appliance, or charger to you house since this was last working?

One has to reprogram them from one type to another. The steps are in the instructions, available online from smarthome if you have lost them.

Hopefully, the suggestion to use status, rather than control, is a quick fix for you. If it were me (having a vague understanding of the difference between the two can mean), I would be tempted to play around some to get a better understanding of how these motion sensors work. I would take the motion sensor down and bring it to the room where the computer is visible. Open the ISY admin box, then open event viewer. From there, trigger some motion in front of the sensor and see what kinds of signals it transmits. You can also see what kind of responses the ISY gives. Find out where the command to turn off the light comes from. Is shutting down before turning on the normal response of a device when it recieves an on command when it is already on? Another option to consider it to use the ISY to turn the lights off after motion sensed. Simply put a five-minute wait in your program, then send an off command. You will need to address the possibility of sunrise occuring during the five-minute countdown, but this is pretty easy to solve. There is a very interesting discussion of motion sensors in the UDI Wiki. Check it out. There are many threads on this topic in the forum here.

It may help to post your ISY program to be able to determine if it is a bug or program fault.

There is a post about this in the X-10 forum under the index. It is the sticky one on top. I understand the X-10 support is an add-on module. One requires, however, v2.7.7 to be able to access the module. I was unable to get the module on 2.7.6.

Assuming one has downloaded the add-on module, from the admin console showing your main tab, choose: link management>>new insteon/a10/x10 device In the pop-up window, give your device a name of your choice, in the address field, add house code and number (example A12), in the device type choose generic X10 device. Worked for me. You can move the new device to folders if you wish. In programs, the device name shows up in conditions and actions. I understand you cannot use X-10 devices in scenes.

I may not be a lot of help, but I can at least confirm that it is possible. I have two scenes involving the same devices, and the transition is as you desire. We at least know it is possible. I guess the trick is to figure out how yours is set up differently than mine. Perhaps a few more details about your installation would help. Are you using an ISY? What device is controlling the kitchen light? What device (keylinc? keypadlink?) are you using to initiate the scene? Are you using the ISY to establish all these scenes?

I think the simple solution would be simply to create a program to perform the actions you want, then enable or disable the program as your needs apply. This would avoid having to rely on a KPL button. I have a "guest" scene that I control in such a way.

I see no v at the center/top of the Admin Console. Mine says "13.F6.8A - Unsupported Device:2.6".

I can confirm this being the case. I used capital letters, no spaces, in the address field (example "A8"). Once done, the x-10 devices shows up in the device list. I can move the x-10 devices to room folders and I can use them in programs. I cannot use them in scenes, which is consistent with my understanding of the design intention.

I have recieved mine and it appears to work just like any other insteon module, with a couple of extra options, including ability to disable the load sense. The current draw, when off, appears to be lower.

I upgraded without problem. This allowed me to download X-10 module without apparent problem. The thing I observe immediately is that each time I log onto the admin console, there is an initial time period where the system gives a busy indication with the percentage bar showing in a dialog box. During this period, much of my system turns off. This did not happen in 2.7.6 or earlier, as best I can remember. I find it a nuissance to have my lights turn off as a result of opening the admin console. Hopefully, this is a result of something I did, rather than a characteristic of the new version.

While not quite as elegant, I have one of those X-10 key fobs that would work well. Unfortunately, it would require a manual press of the button. I would imagine that those are still available and pretty inexpensive.

I assume the lamp is controlled with a plug-in module? My experience is exactly as described by the others. Communication problems cause errors when adding devices to scenes. To confirm, you may wish to try moving the newly-introduced lamp module to a different location. I suggest a location close to the access point you are using. Once there, try again to add it to a scene. Hopefully, you will find that the ISY can now add the device to the scene. If so, you have almost certainly identified communication as your problem. Then you get to enjoy identifying the culprit(s) behing your communication problems.

Around 3000K is pretty close to incadescent, or soft white, based on my visual assessment. 5000K is pretty stark. over that, and it gets to near daylight. Regarding the elimination of incadescents, I understand that this is not a forgone conclusion. The new law requires certain efficiency, rather than banning specific types of bulbs. I also understand that there will be new-and-improved incadescents that will meet these new requirements.

I am not sure that I follow this statement. I have several programs which turn on and off scenes. Are you saying you could not find a way to use this program to set a scene to off?

That sounds like the same problem I had, which was corrected in a later version (2.7.4, I think). I suggest updating your software.

I think, that after the cleanup, the mismatches are gone and the only s "strange" ones are marked extra. That is good to know that they are normal. I continue to get a lot of flashing keypads, and I understand that is an indication of a failure to communicate with one or more of the linked devices. I am unsure how to positively troubleshoot those kinds of problems and thought that the extra links may have been a suspect. I guess not. One of the things that did change when I added the dedicated ISY ciruit is that I also included a plug close to the panel, where I positioned one of the access points. This is the second plug next to the panel, the first one already having an access point. They are on different phases, so this seemed like a good opportunity to ensure good phase coupling. Perhaps this is causing some unintended consequences. I may try to move around some of my other two access points to see it I can achieve some better communication.

I thought I would continue this post, just in case there was any further interest. For the recent couple of months, I have continued to run with the plm on an extension cord to a location further from the computer stuff. Scene tests have been mostly successful in this configuration. Lately, I finally got around to installing the dedicated circuit to the computer room, as suggested and agreed, to power the PLM (and ISY) and only the plm. While the house looks nicer without the extension cord running through the hall, the system does not work as well. I get more communication problems. Most keypad presses are followed by flashing buttons and lights that fail to come on. I also have been checking device link tables and am now finding mismatches between the ISY and devices. I tried a factory reset on one of the devices, then reload the links from the ISY, and continue to get "extra" records. Mismatches, however, are now gone. Perhaps I am simply not destined to achieved that state of near flawless insteon operation. Perhaps there is simply just too much problem with our power supply. For now, the ambition is exhausted. I will have to wait until the supply is replenished.

I can't be a lot of help, but is it possible your remote batteries are getting low? Batteries in a remote can rebound a bit after not being used, but then quit after a couple of commands.