oberkc

There are a variety of potential causes for this. Perhaps the ISY is not working (unlikely, in my mind). Perhaps there is communication problems between the ISY and IOLinc (possible, but not yet concerned with this). IOLinc may be wired incorrectly (given the answers so far, I am tending to discount this possibility). Garage door opener does not respond to momentary contact. Right now, I am mostly focused on this problem. You stated that you shorted out the wires connected to the opener and the door did not move. From this I conclude that either the wires are not connected to the proper connections, or that the door opener does not respond to this. Since you believe you have confirmed that the wires are connected properly, I have to conclude that your opener does not work like this. Unfortunately for those of us who use the IOLinc, some of the newer doors appear to require more than a simple momentary contact in order to activate the door. Until you are able to get the door to respond to a momentary short in the two wires, there is little that can be done with insteon and the IOLinc. My focus, were I you, would be to triple check this again. Remove the two wires from the IOLinc that connect to the garage door and, again, quickly short. Again, check for the proper connections. If you are unable to get this to work, there is little else to be done, I am afraid.

And this still concerns me. The sensor LED indicator on the IOLinc should change state when the door is manually opened or closed.

That was a question I was going to ask you. I don't have the garage door model or manual, do you? Are you able to trace the wire from the wall button to the opener? Into which positions do they go? These should be the same as from the IOLinc.

We have a couple of power outages each year for various reasons. They are usually less than a few hours. A couple of years ago, we had some pretty serious wind storms come through and we lost power for a couple days. Never a problem. Never requires manual intervention to get back working.

I am confused. What do you want to happen if you press button G (arm the alarm)? What do you want to happen if you press button H (lock the door)? Since this is in four-scene mode, pressing button G will send an OFF command, correct? Pressing button H will send an ON command, correct? I don't believe remotes have a "status", so pressing button G twice will send two OFF commands, and pressing button H twice will send two ON commands. What is wrong with a program like: if control button GH is set off and control button GH is not set on then arm the alarm else lock door

So, it appears that your keypad can communicate with the inlinelinc, but not the PLM. I would start: 1) what is the load on the inlinelinc? LED bulb? CFL? If you temporarily unscrew the bulb, does this solve the problem? 2) is the PLM plugged into a surge suppressor or UPS? Is it plugged into an outlet with such devices? If you get an extension cord and plug it into an outlet on another circuit, then plug the PLM into the extension cord, does it solve the problem? 3) anything new electronic gadgets added to your house lately?

I am hoping you can help us out here a bit. You say you have created some scenes. With what devices? Are there any controllers in the scene? With what device do you wish to control the door? A keypad button? Have you created a scene with the keypad button as controller and relay as responder? How is the IOLinc set up? Is it in momentary mode? Does it respond to OFF commands? ON commands? Either? Do you have a sensor installed with the IOLinc? Is it working? Does the ISY see the state of the sensor? Is it ON when the door is opened or when closed? Have you tried closing the door simply by quickly shorting the to wires connecting it to the IOLinc, just to test if it works. Since your chamberlain button appears to be a simple contact, I remain hopeful that this can be made to work.

Yes, I suspect you will find xathros' proposed solution will take care of this. I asked these types of questions only rhetorically...to point out the various considerations that come into play. One (of several) of the problems of your original prgram is that the "status" condition would have prevented this.

More specifically, have you created any ISY "scenes"? Have you created any manual links? How have you configured the IOLinc. One issue that happens more in recent times is that thenewer garage door openers are sometimes not compatible with the IOLinc. Describe the wall buttons. Is it a simple button, or can it also control the lights and other things?

There is a variation on this...what if motion sensor initially turns on the light. At 2:55 during the three-minute countdown, something triggers the motion. Do you want to reset the countdown? Make sure you consider the various possibilities. These motion sensor problems are not as simple to think out as first impressions might lead. I have not looked through xathros example completely, but it looks like his suggestion includes these variations. His example also lets you halt a running timer by manually turning on the switch. Nice.

Your "status" condition is the culprit. Take it out, I suggest. I am curious why did you put it there and what problems do you foresee by removing it?

be sure to check out the user manual and wiki: http://www.universal-devices.com/mwiki/ ... =Main_Page

I always could connect via a mac...no special procedures that I recall. I recall using simply: http://xxx.yyy.aa.bb/portnumber make sure you use forward slash /

Much can depend on how you have your buttons configured. Are they in "Non-toggle" mode? Are you using the same button to show status and to control? As far as the buttons showing status, i assume putting them in the same scene, as responders, would accomplish this. I must admit that your use of "resources" is beyond my experience, so I am not getting a handle on how these programs are supposed to execute and how they interface with your garage door opener. Still, have you tried "control" versus "status" in the conditions? I am wondering aloud if you have some keypad conditions which are changing as a result of the program execution.

Yes...confusion on my part.

Thanks. It is worth checking out the program. In my mind, the program is simple enough and should work. Any responses to my other questions?

Post your program. Did this program once work with the mini remote and now does not? A few obvious possibilities: -Is you program "disabled"? -Is you program in a folder who's conditions are not met?

I understand that the hub accomplishes this by employing a cloud-based capability. I am not willing to give up my direct access to the ISY for a static IP address. There are other alternatives that don't require this sacrifice.

To the other posts, I will add my own understanding. First, I also understand that the insteon cameras are simply foscams in disguise. Second, unlike mobilinc for android, the iOS version of mobilinc can display camera images. Given this, you would have the same app (mobilinc) that provides remote access to the ISY and insteon also display your video images. While I cannot confirm that mobilinc is compatible with the insteon camera (I suspect it is), I am more confident that mobilinc IS compatible with a much larger selection of cameras than is the insteon software for the hub. Regardless, it is not too hard to come up with a camera app for your remote devices for video images, and use mobilinc for insteon. I can tell you that IP Cam Viewer lists the insteon camera as compatible. I am quite satisfied viewing video imagery from a separate app than I use to control insteon. I suppose that you could leave the 2412 in place after you install insteon, but I am not sure that it plays a role with the imagery. I suspect that would, in the end, create more problems than it is worth. Instead, I would use a generic camera app for the video imagery after you install the ISY-994. But, if you are seriously committed to that software for you video imagery, I suggest temporarily unplugging the 2412 module and see if you still receive imagery data. If so, I see no reason why you could not use it after the ISY-994 is installed. Of course, you could not use that software for control of your insteon system via the ISY.

BTW, the exclamation point is indicative of a communication error with that specific device. The green icon is telling you that there are changes made to that devices that are to be written.

Put a filterlinc in, and plug the bitcoin gadget into the filterlinc.

Not to my knowledge.

I understand you could use your power supply through an IOLinc relay.

resetting the KPL is something that is worthwhile trying before concluding the device is faulty. I tend to like to try the easy things first, but you can try performing a factory reset, then restoring the device from the ISY. Another option is to get an extension cord and plug it into an outlet on the same circuit as your keypad, then plug the PLM into the cord. If that helps, then a communication problem it is. If that does not work, then a factory reset is definitely in order.

Can you control it from the ISY? My first inclination is to suspect communication problems. Is the load on that switch something other than incandescent? What happens if you temporarily remove the bulb?