oberkc

The reason to use control condition is that a control will trigger a program evaluation upon EACH receipt of the anticipated command. Unlike control, a "status" condition will trigger an evaluation only after a CHANGE in status. If a device status is off, and you turn it off again, the status has not changed and no program evaluation will take place.

I assume box 1 includes supply (2-conductor), box two has the 3-conductor cable from box 1 and box 3, plus the switch power to the fixture, and box three is just the end of the three-conductor cable. I am hoping you can confirm these assumptions on site. If so, in box 1, connect supply black (hot) to 3-conductor black and to switch black. connect supply white to 3-conductor white and switch white. Cap red from switch. Cap 3-conductor red. In box 2, you now have supply provided by the black and white from the 3-conductor cable from box 1. Connect this to the other 3-conductor black and white, as well as to the switch black and white. Connect 2-conductor white to the other whites. Connect 2-conductor black to switch red. Cap remaining red conductor. In box 3, you now have supply provided by black and white conductor from box 2. Connect switch black and white. Cap red from switch and cable. ALL switches must be insteon if you want control from all three locations. All bare grounds should be tied together in each box. Again, confirm the wiring on site. Best to use a volt meter.

Certainly a factory reset on the devices will eliminate all traces of your PLM and ISY. My suggestion is to try a quick attempt at establishing communication with your plm. Try moving it to where you had your smartlinc. Feel free to use an extension cord, if necessary. Hopefully, it will work better. If it does work better, you can try "removing" each device from the ISY. It is hard to know if this will work. The difficulties you have experienced may have corrupted some of your devices. If removing the devces does not work, a factory reset of each may be your only option.

Make sure you put your smartlink back in its original location. I suspect it, too, will have difficulty at the location where you added your ISY. Were you to put the ISY where you had your smartlinc, you may find the problems go away.

I am with LeeG on this. I, too, believe you have a communication issue between your PLM and rest of your system. This tends to suggest that the PLM is plugged into an outlet or circuit with other things that don't play well with insteon. My impression is that the most common cause of this is plugging in the PLM into outlets near computer stuff, including surge suppressors, UPS, and lots (and lots) of other gadgets. If you are having trouble communicating with the PLM, then...yes...it will probably be easier to manually link your devices and ignore the PLM. Once you figure out the PLM, however, I respectfully disagree that this method is easier. I assume that you transitioned in order to exploit some capability in the ISY that is lacking in the smartlinc. I am curious, however. Did you install the ISY/PLM in the same location as the smartlinc?

I don't mean to overly stress these types of questions, but I think it worth spending time thinking through how you intend this sytem to work. Answers to these questions will affect how you program things, and you can waste a lot of time coming up with programs that you quickly discover "don't work" as you intended, because you didn't give enough attention to your "intentions". It is a lot like "ready, fire, aim". What if the livingroom lights are at some setting other than 50% because someone manually adjusted them for some reason? what about 10%? 80%? 1%? Do you want the living room lights to go full on only if they at that magical 50% level, or any level greater than zero? Or any level greater than 50%? Most of the program suggestions so far are based on the first option. OK...you bring up another consideration...do you want the livingroom lights to respond to kitchen lights only if they are at 50% AND only if they reached that state in response to the kitchen lights turning on? Or do you not care how the livingroom lights came to be on, whether manually or in response to a program? There are a variety of conditions one can use to check for such things, but one condition that does NOT exist is "scene status". There is not status for any scene, such as your livingroom scene. Typically, one would have to check for the status of a selected device within that scene as a representative status. Another condition that could prove to be handy here is in program status (true or false). This represents the results of the most recent evaluation of a given program. For example, if you have a program who's else statement turns on livingroom lights as a result of kitchen lights, if that program status is currently "true", then you know that the most recent execution of that program turned on the livingroom lights. I believe it worth spending more time understanding your needs and intentions before writing a lot of programs. Your particular situation is, in my mind, has a lot of subtle variations.

To be clear...when someone turns off the kitchen lights (regardless of whether the living room lights are on or off or anywhere in between), you want the living room lights to turn on to full, correct?

"Automating" the humidifier is one of those things that, to me, is a solution looking for a problem. My thermostat takes care of this. It appears to work well. Yes, it would be pretty cool to integrate HVAC with my ISY so that pressing my "away" button resets HVAC, but I otherwise percieve little value. My thermostat has all the programming I need. It handles humidity. The fan circulates the air when needed and I have control over that. I have remote access. I am not sure what other benefit I would get. It seems a lot of people do it, however. I am sure I am just missing something.

Don't wait for more problems to come back. Check in regularly, even if you don't need help. Your experience may be needed to help out another.

When I suggested to "chain" a remotelinc to the lamp, this was only half joking. At one point, I had one of those X-10 keyfob remotes, hanging from the lamp via a short loop of that light chain material often used as keychains and fixture pull-chain.

It appears to me that this combination of conditions SHOULD fire true, based on the logic. The problem is to find out why. Is it possible that the ISY does not accurately reflect the status as you believe it? Can you recreate the conditions, making sure that the ISY accurately knows all the relevant statuses (stati?).

There is not really a good way. Your fewer hop=0 messages is a good clue. The ISY has a scene test, which is a gross indication of communication goodness. This may be the closest to what you are looking for.

In addition to the remotelinc, I also use the table-top enclosures. I also have keypads mounted in wall boxes that control lighting. I use a couple of android tablets for lighting control. Ultimately, my strategy is to minimize the need for local control by programs, motion sensors, and sunrise/sunset. We just don't often need to turn on a single lamp at this point.

Chain a remotelinc to the lamp.

Xathros, You are, as normal, correct. Unfortunately, this was not a stated requirement that I noticed? Perhaps it is the engineer in my personality, but I have ceased attempting to guess people's requirements, or add my own. I try to offer simple solutions to the stated problem. If the scope of a question evolves, and I feel as if I am chasing a rabit, or if I have to start guessing at what the real (and total) requirements are, I become quickly frustrated.

I, too, had already made a suggestion, based upon your original statement that everything was working and that the only problem you were having was dimming to 50% at 1000. In case that suggestion was unclear... Create an entirely new scene, keeping intact existing scenes. The new scene would include all devices that you want to change at 1000, all as responders. At the scene level, define the ON levels (which includes zero) you desire for each device to assume at 1000. Create a program to turn on that scene at 1000. Done.

Your latest program introduces a device: 'Entry, Hallways, Steps / Entryway 8BKP'. I have no idea what that is relative to your original request. Sorry. I see nothing that turns any front porch or outside can lights off or to 50%, I see nothing that turns light back to full bright at 1 hour before sunrise. I see nothing that turns lights off at sunrise. No, I don't think this will do what you originally asked about.

I have only a single v.41 switch, but it is a relay. The two switches I tested (both v.38) behaved just as did MikeD. When off, pressing the on button brings it up to preset levels. This happens always, regardless of recent paddle presses fast on or not.

Yes, the KPL button should come on and off with the motion sensor.

Based on memory, mine is the same as LeeG. At step four, mine would go to defined level, not full on. I will confirm when I get home, as well as check to see if I have any v.41 devices.

This is not something I routinely do with my system, however, my recollection is that if I press ON once, it goes to the pre-defined level. If starting at the pre-defined level and I press ON again (regardless of wait time) it goes to full bright. If starting at full bright and I press ON again, the device will revert back to the the local ON settings. In effect, repetitive presses of the ON button would toggle between full and the locaol ON level. I don't know why mine would be different than yours, other than some change made by smarthome, or a device defect. Is it possible that you have some program running which would cause this behavior? Do you see any program status who's last run time corresponds to switch input?

I only have a couple of things to observe. One is unrelated. First, the hop cound (hops left = 0) I see in your event viewer suggest (to me at least) that you have something going on that makes communication between devices a little troublesome. Regarding your stated problem, I don't see anything in the program that would cause the observed behavior. I cannot help but wonder about your switchlinc, however. It sounds as if it is reverting to last state, somehow, for "on" levels. I had a couple of X-10 devices that did this. What kind of device is this "switchlinc dimmer"?

. I forget whether ISY programs have the ability to command a device to go to a specified level. If so, one could use that capability. If not (and maybe even if so), I would create a new, additional scene. I will call that scene the "10pm scene". To that scene I would add Outside Front Can Lights and the Front Porch Can Lights. At the scene levels, I would set "ON" levels to be 0 (off) and 50% for each of the two devices, respectively. Modifiy your program (or create a new one) to turn this new scene on at 10pm.

LeeG's advice is probably most productive. Short of that, I would expect a program such as this to work: if from time xx:xx to yy:yy then run other program (then path) wait 1 hour run this program (then path) else other program if then do whatever you want done every hour else

I can only speculate, but I would be inclined to take it with me if needing to sell soon. But...everything is up for negotiation.