oberkc

You can actually perform a quick, and simple, test. Get a short wire. Locate the two terminals on the opener where the wall button is wired. Quickly (less than a second) short the two terminals. If the door responds, the IOLinc will work fine.

I don't know for sure, but my guess is that it will work. I cannot help but suspect that this is similar to a chamberlain model that I have (which does work with the IOLinc). If you are reasonably handy, I also suspect that were this not compatible with normal methods, you could tap the IOLinc into the wall button contacts, somehow, and make this work.

I can tell you both that I have not two, but three, keypad buttons which both control my garage doors, with all three providing an indicator regarding status (ON= OPEN). I did it just as I described, just as the wiki described. The suggested approach handles just fine the condition where one tried to close a door, but the door automatically reverses itself. . No problem. I use NO programs, so if your goal is specifically to use a given program rather than rely exclusively on scenes, then my suggested approach will fail to meet such a given "need". If, however, your goal is simply to have an indication of door status with the same button that controls the door, I continue to recommend the wiki approach. I suspect you are thinking in terms of solutions rather than requirements. I think you should think of your needs in terms of function and interface (press button, door closes/opens. same button displays status.) rather than solution (use a program). Yes, I think you are making it harder than it needs to be.

I looked back upon your original post. Unfortunately, the problem you describe (false OFF conditions) is not one that I experience. If set up as described (with the KPL in non-toggle ON mode), there is only one way for the keypad to be off (barring comm problems)...if the sensor tells it to be so. So...I remain a little confused as to what problem is being solved here. Of course, there is more risk of false OPEN indications, but I consider this the lesser of two problems. Another thing I am struggling with is the evolving approach of jdm5. As I read through the various posts, I start to suspect I am unsure what he is trying to accomplish and what problem is being solved here.

There are, I notice, a couple of other programs referenced: 'Garage Left Door Close', and 'Garage Left Door Open'. It might help to post those, as well. It is hard to picture what you are trying to accomplish with some of the pieces missing. Is 'Master Bedroom 8KL / Master Bedroom 8KL - Garage R' part of the scene 'Garage Master Bed KPL Right B'? I have looked back at the thread, and I am a little uncertain what "this" is. If your intention is to see the status and control a garage door from the same keypad button, or from several buttons around the house, I prefer scenes. I find the method in the wiki to be the best approach. - Locate the sensor in such a way that ON = Open. The location should be such that it is OFF only when fully closed, otherwise ON. - configure the keypad button (or buttons, if more than one) as NON-TOGGLE ON - configure the IOLinc relay to respond to ON commands - create a scene with the button (or buttons) as controller and relay as responder - create another scene with sensor as controller and button (or buttons) as responder Everything works together in such a way that if you don't have the IOLinc configured properly, the keypad configured properly, the sensor mounted in the correct location, the correct sensor, and the controller/responder relationship properly set up, it will not work well. Using programs is likely just as dependent on attention to these details.

To add to Michel kohanin, though there are links to the PLM, device-to-device scenes work just fine were one to loose the ISY for some reason.

LeeG, Early you suggested (I think) using a direct command to trigger the relay. I vaguely recall other posts where I thought I understood the IOLinc responds in momentary mode only to scene commands. Am I recalling incorrectly? Yes, I agree that the button looks like a simple momentary contact button. This should work, yes! Pintu1228, If you wall button still works, make sure that the wires connected to the IOLinc go to the same wires as the wall button.

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.