oberkc

While "going into" your switches may offer clues, the obvious failure point sounds like the fixture wiring, itself. (This is where you originally "opened" or disturbed the circuit, correct?). Even if you observed no wires having broken free from wire nuts or terminals, this is still the place I would start. I have experienced open connections between two wires visibly connected by wire nut, but not making good connection for some reason. It seems easy enough to open the fixture again and simply tug on each of the wire connections to see if anything comes loose or free. Obviously, such action should be performed carefully, and with the power shut off from that circuit and any other in the box (if more than one circuit). Failing this, were you to post some pictures or detailed description of the wiring in your ceiling box, it may be possible to recommend some further troubleshooting suggestions. Pay special attention to: a) color of each conductor insulation (black? White? Red? Green? Other?) groups of conductors in a cable (one cable with black, red, and white conductor?) c) any markings on conductors (expecially white ones) that appear to be an attempt to identify it as a different color. This can include paint, ink, electrical tape. d) what conductors are connector to what other conductors, or to the fixture, itself.

I am with LeeG. I would be amazed if all six on a single circuit failed. I suspect this is a wiring issue. I would be checking for the proper voltages and neutrals at the various boxes.

One way to confirm this would be to temporarily disable the program, then see if your devices still respond to the motion sensor. If so, you still have scenes somewhere. You may consider performing a device restore from the ISY. Like LeeG suggests, in order to reprogram/restore/configure/set up scenes in a motion sensor, one must put the motion sensor in the linking mode, then write the changes to it. Do you see any little green arrows next to the motion sensor in the device listing? Failing those things, the best approach would be to remove the devices from the ISY, perform a factory reset on the devices, add back, then recreate any needed programs. Unless you see signs of communication errors, this may not be an issue. Long term, however, I believe it best that the ISY on a really-good circuit. Given this, I would filter your servers, and any other electronic gizmo on that circuit. The PLM is too important.

Which is why, at this point, simple is good. The program is fine. If you are having behavior that is hard to explain, look to issues other than the program. 1) As suggested by LeeG, it appears you may still have scenes in play, where a motion sensor is controller and some devices are responder, and the motion sensor is set with a 1-minute timeout. If you created these scenes manually (running around the house tapping buttons) , make sure you delete these scenes. Perhaps this could be done by "restoring" the device through the ISY. Alternatively, the instructions for each device describe how to do this. If the only devices you have in the ISY are the motion sensor, plug, and a few bulbs, perhaps it would be better to factory reset each, removing from the ISY and reading. 2) If you are seeing INCONSISTENT behavior, I would look for communication issues. Does it work sometimes or do the lights ALWAYS go off after 1 minute? Do all the lights go off sometime, or only 2 of 3 go off every time. When things work sometimes, but not always, I tend to think communication. With the ISY, WAIT statements can be interrupted. A program in a WAIT condition can retrigger and start over. I would not do this. I might try restoring the individual devices, or removing them all from the ISY and factory resetting them, but I don't believe restoring the PLM will solve whatever problems you are having. This might help if you are experiencing communication problems. It seems to me that the most common problems people continue to fail to understand is that one needs to couple the "phases" ("Legs" is more technically correct, I understand) of your electrical system, and that plugging the PLM into the same outlet as computers/UPS/surge supressors/printers/modems/routers can create difficulties. Next to the fuse box is good. A dedicated circuit would be good, if an overkill. Access points are good. Filters are your friend.

Yes. Until it all works then mine understands.

Putting a program in a folder may "disable" a program, but I do not expect this to halt a program, once running. When you say "some of the lights", are you stating that some lights within the scene "office lights" are responding as intended, but not all? Otherwise, please elaborate on "some". With your existing program, I see two possibilities that would prevent your lights from turning off. First, if the motion sensor continues to detect motion, it will reset the 15-minute timer. (This is how most would prefer, I suspect.) Second, the scene command fails to reach the intended recipients. There is a third possibility I can think of, but it would involve an ill-timed power failure. Otherwise, this program WILL continue to count down and execute the off command. If the program sends the command to turn the scene on (or off) and you notice only SOME of the lights responding, this tends to suggest (to me) that you have a communication problem.

Without seeing your program, it will probably be hard to state definitively. It could depend on whether you use status or control. It could be that something is interrupting the wait statement. It could be that you have scenes in play. It could be something else.

To continue the thought process started by LeeG, you may also consider a combination of things... Perhaps you would choose to use a scene to directly turn them on from a motion senso (perhaps a little quicker responding) and a program to turn them off. Make sure you explore the "options" for the motion sensor. You can configure the motion sensor to only send an ON command, using the ISY to shut them off after a period of time. But...you don't want both a program and a scene to turn them off. But, my preference is like Michel's: keep it simple. I would even go simpler than his example If Control 'Main Bath Motion.1-Sensor' is switched On Then Set Scene 'sMain Bath Lights' On Wait 4 minutes Set Scene 'sMain Bath Lights' Off Else - No Actions - (To add one, press 'Action') Like LeeG suggests, make sure your motion sensor is not part of any scene, and make sure it sends only ON commands. Unless you have some specific concerns (such as power failure during 4-minute countdown or need some type of manual override), I would expect this to work fine.

Yes, you would do this via a scene. Make the sensor a controller and rest responders. Depending on other factors (such as whether you want ISY to turn them off or take other action) you may need to configure the motion sensor to send only ON commands.

I see continued development. Micromodules have been recently released. 220V50Hz devices are now available. Over the recent years, we have seen the migration to dual-band devices. I see no signs of a near-term demise of insteon. Still, it is hard to predict the future.

If the EZIO is similar to the IOLinc in this regard, "Inputs" cannot control anything. Only the relay outputs can.

Yes, I think that is a unique capability to the iOS version of mobilinc. With Android, one can use the tasker app, now integrated with mobilinc, to initiate such triggers. I am not entirely sure if the iOS version allows location based on proximity to certain wifi networks, but tasker does this.

Yes. This is generally consistent for all programs. Conditions are triggers. One needs to understand how each condition triggers a program evaluation. Once triggered, it will either evaluate True (run then path) or False (run else path). Well, then, you will have to decide how to tell the ISY that you are home. I use a keypad button. I have experimented around with using cell phone location. Perhaps motion sensors? Garage door status? However you decide to do it, you would have to update your program: if I am away and time from 530 for 2 hours then....

I had no idea. This is not the case with the IOLinc. Plug it in. Add it to the ISY. Go. I guess I would consider this an advantage.

I also suspect that sending an insteon command from the ISY is more tolerant of local interference than listening for a status message from a remote device. Given this, do you have other insteon devices? Does the ISY have any trouble hearing from them? Is it possible that you have some devices on the same circuit as the PLM which might be obscuring the status messages?

It sounds as if you have asked all the right questions. I might perform a "show links" from one of your devices and compare to the ISY records. If there reveals a mismatch, the only thing I can think would be to restore one of the devices to see if this solves your problems. I have no idea if this would help, but it is not overly difficult to do, and with little risk.

I use an IOLinc, but have no EZIO-anything, so have no first-hand experience which could indicate one being better than another. I can say that my IOLinc seems to communicate pretty consistently, and that I recall reading no posts around here to suggest speculation that the IOLinc is more robust than one of the EZIO-series modules. One thing that strikes me as strange is having "isy991 with 3.3.10 and 4.05 ui ". Do you have an ISY-99 or -994 (I am not familiar with a -991). If -994, my temptation would be to update to latest software, in the hopes that this would solve your problem.

Not that I would expect. Purchase a second filter. Plug the HDMI matrix/switch into a filter, which would then be plugged into an appliancelinc. Plug the appliancelinc into an outlet outside your power strip (possibly even the same outlet as the PLM). I suspect this would be cheaper than purchasing one (or two) more access points.

The only one that I know about is on the wiki: http://wiki.universal-devices.com/index ... r_Messages

Phase test sounds performed correctly to me. My understanding is that nearly all houses in the US have two legs from the electrical system. Numbers of electrical panels does not matter, so long as you have bridged those two legs...which you have done. Your testing of the PLM is quite revealing. Since you prefer the mechanical room location, I would focus there, and on the six suspect devices. First, run the scene test several times. If it passes some, I would declare victory and move on to other things. If it failed consistently, I would take the time to search for a cause. First, I would filter your computer stuff. That type and absolute quantity of stuff is almost certainly causing some problems, and I would hope to knock it all off from a single filter. Once done, identify the circuit(s) on which the failing devices reside. Seek out other suspect electronics on that circuit. Temporarily unplug any to see if the situation improves. If so, filter those. Finally, given how important is the PLM, I would take extra precautions to ensure a clean circuit for it. Temporarily unplug all devices and run some scene tests to see if there is any improvement. If so, filters are cheap!

I believe you got bad advice from smarthome. Odd and even circuits are not necessarily on different "phase". My suggestions stand....perform the access point test in the manual to confirm and check to see what other devices are plugged in the same circuit as the PLM.

As Brian H mentioned, there are instructions in the user manual to determine whether your access points are on opposite phases. It is worth confirming. The other common problem is that folks can install the PLM on a circuit with lots of other gadgets and electronics. This can interfere with insteon communications. Yes, there are solutions if this is your case.

Program folders are really nice method to keep things organized.

My experience is identical to Xathros'

You can remove the remotelinc from the ISY. Instructions for this are in the wiki: http://wiki.universal-devices.com/index ... ice#Remove You can "factory reset" the remotelinc. Instructions for this are in the manual, as well.