oberkc

apostolakisl understanding is consistent with mine, but I think there can be times when the ISY DOES assume status. I understand that if the ISY does not recieve an acknowlegement, it WILL assume that a device responded properly. Also, I understand that scene commands are not acknowledged, by design. Regardless, a system being out of sync tends to point to communication problems, in my mind. I think it is a little bit more (barely) than a guessing game, but apostolakisl point is well made. It is often not easy to identify electrical devices that cause problems with insteon communication. The ISY does provide a tool that I can be useful in this task: the scene test. While it does not identify sources of noise, it is a baseline against which one can judge the presence of interference (noise or other types) and changes to communication integrity as one attempts to troubleshoot problems. Otherwise, yes, identifying sources of problems is often little more than observing cause-and-effect relationships as one isolates and removes potential sources of "interference". Often times, it is the summation of multiple devices that can cause problems.

There are a lot of those posts. I suggest starting with the wiki.

I don't know if it is too much, but the fact that you feel there is a need would concern me. If you are getting a lot of devices out of sync, I would be trying to find out why.

I assume that "flood HVAC" is the inlinelinc that controls the two floodlights and that "B1-Porch/B5" is the keypad button. Is this correct? What is the device "Flood Master"? Is this the scene you reference (if so, I expected the program line to read set SCENE "flood master" on)? I assume you have checked the event log to confirm receipt of the trigger condition. If not, I would. If you are receiving the trigger condition, have you checked program status (programs>>summary>>last run time) to confirm that it is running or not? Assuming you are receiving the trigger condition, and the program is running, I only assume that there is something going on with one of your scenes which counteracts the effect of the program. Regardless, I don't understand the purpose of your second "then" statement. Why not a more simple program: If Control 'B1 - Porch / B5 - Floods Master' is switched On or Control 'B1 - Porch / B5 - Floods Master' is switched Fast On Then Set 'Flood HVAC' Fast On Else - No Actions -

To "cross-link" two insteon devices, create a new ISY-99 scene, with both devices as controller. I doubt that the creation of scenes broke anything. I suspect is was the adding them to the ISY that removed the existing link records. I am unsure what your "expected behavior" is. It may help to describe what you want to happen in response to an "on" and "off" command from each switch.

No problems in my mind. I have been considering doing the same thing for some ceiling fans.

I am not sure that one can query a "scene". Sounds like the program ran, but the device failed to respond. Make sure your PLM is not plugged into surge suppressors or UPS. Make sure your PLM is not plugged into the same outlet or circuit with lots of computer stuff, including surge suppressors and UPS, power supplies, etc.... I understand that the PLM status and actual device status can be different during times of communication difficulties.

That looks like a nice solution, if a bit pricey. Plus, it adds volume control. I may have to consider for my own use.

While I have not attempted this, would not an EZIO40 suffice?

One of the consequences is that if the "scene" is turned on by another mechanism (manually, other program) between time yyyy and xxxx, it will stay on. If this "scene" is turn off by another mechanism between time xxxx and yyyy, it will stay off. This program does not enforce the scene being on or off, other than at those two specific "from" and "to" times.

But still, it is rated for incandescent loads, 120V, 400watts, 2.5 amps. Unless you are suggesting that one is a transient rating and another is steady state, there appears to me to be an inconsistency here.

I thought the same thing...except that it is "rated" for incandescent lamps only. Pure resistance. No power factors.

Agreed. This seems a little strange.

Last I checked, I still had the option for a "mutually exclusive" relationship, programmable from the ISY. It has, however, been a while since I looked. In addition to this ability, I vaguely recall that one can program this behavior directly at the keypad (I think it is called button grouping in the keypad manual). I also percieve a bias here in favor of scenes. As I understand, mutually exclusive relations are managed by the device itself, and apply only within a single device. Your desire to turn muliple secondary buttons off in response to a scene "on" command suggests that a mutually exclusvie relationship would not work for you. A program would be necessary.

How about an inlinelinc at each fixture? I am not sure that you are going to be able to avoid climbing the ladder. I have heard of folks around here who use a relay, controlling the relay with an IOLinc, but that would be for others to provide any details.

I use Gmail, and continue to get notifications. I use the "default" server, as well. I don't expect or get a lot of messages, but I continue to get them as expected.

The program looks to me as if it should work. Have you checked to see whether the ISY is tracking the correct status and seeing the commands? While I don't believe it makes a difference, have you tried switching the order of the "status" and "control" conditions?

The link I provided: viewtopic.php?f=26&t=635 has been available for a long time. It is the first sticky topic under "how to and tutorials".

Wow! I am not that would have ever occured to me without further details from the OP. Impressive! Are you one of those that can guess wheel-of-fortune puzzles with 90% of the letters missing?

I fail to see why your second program (including parentheses) does not work. Have you confirmed that the isy is seeing the correct status for the various devices? Check to see when the second program was last run...what is the current program status (true or false)? Given that your first program is triggered by many of the same variables as the second, is it possible that they are conflicting with each other?

You are partly correct, I was not fully understanding your problem. It now sounds as if you have two problems? One, you have a scene defined which has devices (not keypad D) that don't respond. Two, you cannot add a particular keypad button (Keypad D) to that scene. When you select the scene at the admin panel, and it shows the included devices, which of those does not turn off? Furthermore, you confirm that keypad button D is not listed in the included devices, correct? If you find keypad D in the admin panel device listing, and select it, you should notice (at the right extreme of the admin panel) a list showing "controls" and "is controlled by". Is there any indication here that keypad D is controlled by the device that is controller of your "all off" scene? I still suspect communication issues.

Thus the suggestion to first REMOVE it from the scene, then to add it back.

I believe LeeG was suggesting removing the offending keypad button(s) from the scene, then readding. If you do this, confirming that all desired devices and buttons are in the "All Off" scene, identified as controllers and responders as you desire, and still have problems, then I generally suspect communication errors. This assume there are no device failures. How are you turning the scene off? What do you mean by "load is off"? Is the device controlling the load defined as a controller of the "all off" scene?

I have no recommendations on utilities. I began to suspect my port conflict when I tried to remotely log into my ISY and got the stora instead. So far, so good.

The short (and flippant) answer is: because this is the way you have it programmed. I believe that your second program is the culprit here, and that it has to do with the priority of "and" versus "or". Without knowing your intentions regarding these programs, allow me to offer a suggested change to your second program that I hope clarifies the priorities between "and" and "or": If Time is 10:21:00PM And ( Status 'Fam Rm Table' is On Or Status 'Kitchen Ceiling Keypad - A' is On Or Status 'Kitchen Ceiling Keypad - A / Kitchen Cabinets Upper - B' is On Or Status 'Kitchen Pool' is On ) Then - No Actions - (To add one, press 'Action') Else Set 'Fam Rm Key - Ceiling' Off As a further point that I hope is instructive, I DON'T believe the parentheses you have in your first program are necessary.