Garage Door Opening

FYI, if you have an Elk system, you can do this pretty easy. Before I had my Vera, I had garage door control working. I have garage door sensors from Automated Outlet on each door hooked into Elk zones. Then I have a relay board. Each relay went to one garage door switch on the wall. I’ve since changed it by just putting a remote in my security panel and soldering wires into a remote and triggering them with the relay.

I have a task for each garage door which closes the relay for one second. The Close door task will only activate if the door is open, and the open door task will only activate if it’s closed. This way, I don’t really need to know the state of the door, I can just hit F4 on my panel for “Close All Doors” before I go to bed, and not worry about it.

Since I got the Vera, I’ve installed the Elk plugin. But it doesn’t support outputs or tasks on the Elk. But if you want to control outputs and tasks on the Elk, you can just create a “Text” such as “CloseGarageAll^M”. Then you create a rule that says when that text is received on serial port 0, then execute a task you’ve created or control an output. On the vera, you create a scene with the following LUUP code:

local socket = require("socket") host = "10.1.1.40" -- IP of your Elk c = assert(socket.connect(host, 2101)) c:send("CloseGarageAll\r") c:close()

It’s been working flawlessly for me. I took all of the garage door remotes out of the cars since we sometimes park outside and I don’t want to make it easy for someone to open my garage door if they bust out a window. I used the HomeBuddy widget and attached it to a scene for each of Open and Close. Now, I don’t even have to launch HomeBuddy and wait for it to connect. I just hit the widget, lock the phone, and wait for it to do it’s thing. It only takes about 5 seconds when you’re not on wifi, and instantaneous when you are.

@signal15, great post, i think you just solved a major problem for me the elk plugin was missing…
so you are sending a text message through Veras notification system or does that luup code send a raw message directly to the Elk?
Maybe its because of my phone, but there is a special character in the text that is not present is the luup code, was that intentional?

Do you have the ability to create a a simple plugin that requires only the IP of the elk, and text box for the message to send?
I imagine it would be a device that you call in advanced scenes and can type the text to send?
Then setup a rule on elk to execute as you explained…
I’m currently relying on @RichardTSchaefer’s plugin for my garage door, but it seems I can free up my aeon labs door sensor and lfm20 by using elk. Can you provide more detail on how you wired this? I hate to hijack a thread so maybe create a new post, or move the response to the ELK Plugin Thread?
Thanks in advance, you have helped me out a lot already.

2

[quote=“big517, post:82, topic:166907”]@signal15, great post, i think you just solved a major problem for me the elk plugin was missing…
so you are sending a text message through Veras notification system or does that luup code send a raw message directly to the Elk?
Maybe its because of my phone, but there is a special character in the text that is not present is the luup code, was that intentional?

Do you have the ability to create a a simple plugin that requires only the IP of the elk, and text box for the message to send?
I imagine it would be a device that you call in advanced scenes and can type the text to send?
Then setup a rule on elk to execute as you explained…
I’m currently relying on @RichardTSchaefer’s plugin for my garage door, but it seems I can free up my aeon labs door sensor and lfm20 by using elk. Can you provide more detail on how you wired this? I hate to hijack a thread so maybe create a new post, or move the response to the ELK Plugin Thread?
Thanks in advance, you have helped me out a lot already.

2[/quote]

The text string is being sent to the Elk via LUUP code. I create a scene called something like “Close all garage doors” and put the code I posted above into the LUUP tab. Then, when I want to call it from my phone, I just use HomeBuddy for Android. For things like this, I add a HomeBuddy widget to one of my screens and attach that scene to it so I don’t actually have to launch the app and wait for it to refresh. I have one screen dedicated to HomeBuddy widgets.

As far as wiring goes to the elk, I just purchased garage door sensors from Automated Outlet and wired them into the elk just like you would for a door sensor. They are basically just a door sensor, mounted on a little bracket with armored cable coming off of it. A lot of people mount them to the floor, I mounted mine to the top of the door. For the “button press”, I have an Elk Output board. If you have doorbell type for the garage door buttons, you can wire each output straight to the two wires on the back of the button. If you have displays like I have, you need to solder wires to the buttons inside the display, or get a remote and solder wires to the buttons in the remote. Then you create tasks on the elk for opening and closing. For example, to close, “When Task 1 executes and garage door 1 is not secure, then turn on output 10 for 1 second”. You want to have that check to see if the door is open or closed so you can operate it without visually checking where it’s at. Of course, you need to be careful when doing this if you have kids and aren’t sure where they are at. If you use a remote and you create a task to close all garage doors, you need to creatively use a timer to stagger the button presses as garage door remotes with more than one button won’t allow a simultaneous button press.

The new version of the Elk plugin is supposed to have direct control over outputs and tasks. But it’s not there yet, so sending a string to the Elk’s serial port via the M1XEP is the only option at this point. And when you create the Text string in the Elk, there’s a dropdown to insert the ^M at the end of it. This translates into the “/r” in the code I posted above.

I have released this with woodsby’s permission the Garage Door Plugin to the App store.

See: [url=http://RTS-Services.com/Vera/Plugin/GarageDoor]http://RTS-Services.com/Vera/Plugin/GarageDoor[/url] for details.

There are variables to set the Door And Sensor Devices ID’s … So no need to edit the file. I have two doors I use this plugin for.

I have a fix for the GC100 that I still need to release if you want to use an iTach to trigger the Garage Door.

[quote=“RichardTSchaefer, post:84, topic:166907”]I have released this with woodsby’s permission the Garage Door Plugin to the App store.

See: [url=http://RTS-Services.com/Vera/Plugin/GarageDoor]http://RTS-Services.com/Vera/Plugin/GarageDoor[/url] for details.

There are variables to set the Door And Sensor Devices ID’s … So no need to edit the file. I have two doors I use this plugin for.

I have a fix for the GC100 that I still need to release if you want to use an iTach to trigger the Garage Door.[/quote]

That’s great news RichardTSchaefer! I got word that my GC100 is scheduled to arrive by UPS today so I will need the fix as I will be using that to trigger the garage door. If you happen to have a guide or tutorial on how to accomplish this it would be really helpful, or if you could point me in the direction of where I can go to piece it all together. Much appreciated. Will let you know how it goes…

Install the iTach.
Make sure you can change the Relay states.
You will notice that Vera Does not show the state properly … but it does change
the relay states (LED’s on back will change).

My fix is so the Vera state is displayed properly for the relays.
I can email you the file and instructions to install.

I do not have a Vera2 anymore … I traded up …
If you can’t get the Garage Door plugin from the App store … drop me an email.

Email me at schaefer@RTS-Services.com

Is there any reason why you can’t connect the ip2cc directly to the bell wire of the garage door instead of to a remote?

I do not have a simple push button garage door opener on the wall.
It has UP/Down/Stop (More like a commercial setup). But for the simple 2 wire garage door buttons you can hook that right up to the iTach.
However if you did not want to mess with the wiring … the remote control works well!

Yes you can, I have my lfm20 wired directly to the terminals at the motor.

Personally I would like to remove the need for this by using outputs from the elk to the back of the wall mount controller.

Sent from my SPH-D710 using Tapatalk 2

N5NHL - Can you provide how you created scene in Vera for garage door to open, wait 5 seconds or so, and then close? Just installed all last night as you described but not having luck creating scene. Thanks John

Need some advice…

I have 2 garage doors both wired in series to my DSC alarm. I want to be able to remotely open/close them both. Seems like there are lots of ways to do this, so would like the cheapest and most reliable option. I realize since they are both wired to a single sensor that I won’t be able to use any of the combo plug-ins.

  1. Z-wave outlet with 110v relay. ($35 x 2 + $10 x 2 = $90)
  2. 2 x LFM20 switches ($60 x 2 = $120)
  3. 2 x ZFM80 switches ($50 x 2 = $100)
  4. GC Itach unit ($120)

I am leaning towards option 1 as it will require the least wiring and work. Anyone had issues with the newer openers (going to replace mine) and their wall control units in conjunction with this?

Thanks,
Roy

Verify you have good Z-Wave coverage in the Garage.

I have option 1 set up and the only issue I run into is when the zwave outlet turns on and the power gets sent through the relay to the opener, the wall control turns off/gets reset. And actually last night I had closed the garage with Vera and for some reason the outlet didn’t turn off properly and left the wall control useless until I figured out the outlet was on and turned it off. The wireless keypad and the car remote still worked though. This rarely happens and thankfully it didn’t seem to affect the garage opener. The second half of the scene to turn the outlet back off didn’t get received by the outlet, I guess.

Well that would definitely lower the WAF… maybe option 3 would be a better bet since it is a momentary contact. The two ZFM80 I could put in a double-gang right below the current wall openers and right above the garage light switch. Cabling would be pretty easy…

Would the LFM20 work the same way, just with the module in the ceiling next to the opener? Where are people putting the LFM20 module? I would think it might have signal issues in the ceiling…

The lost packet is why I caution you about checking your Z-Wave coverage.

If you just go for the simple Scene with On wait for a few seconds then Off.
If it misses the first packet … the Door will not open … If it misses the second packet you are at the discretion of the Garage Door Designer relative to a hung switch. I know some garage doors will stop the door if the door switch is pressed for too long a period … You could have a half open door. The hung switch could keep the normal switch and remotes from operating properly.

The Garage Door Plugin monitors the Status of the controlled device and makes sure it get’s a pulse (Checking for the return status of the controlled relay). It also check the Status of the door switch to make sure things are operating properly. But since you only have logically one door sensor (two in series) … this plugin is not useful.

If you spring for another sensor … You can have Automation actually close the door that was left open. What’s the posibiloity of running another wire pair to the Alarm System ?

Search the Vera app store. There’s a plugin on there that can control a cheap network connected relay box. That would probably be your cheapest option.

You’ll also want door sensors on your garage doors to sense the state of them. Then you can have “door open” and “door close” scenes, instead of just a “door toggle”. Most importantly, for safety. You don’t want to attempt to open your garage door if it’s already open and there might be kids playing around it.

Richard,

I don’t seem to have the best luck with the Plugin. One time I’ll hit the icon from my phone and nothing happens and the next time it will work fine. I’ll try using it again and see if I continue to have stability issues.

Like all automation, the plugin can only work as good as the sensor and controlling device you use to initiate motion.

How do you have your Sensor and Control Device configured ?
Device Type ?
Do they have a reliable access to Vera ?

I’m running a zwave outlet through a relay to power the opener. The sensor is an Everspring door sensor that is externally wired. I do admit that the sensor seems to be very sensitive to heat so I do plan on moving it at some point. But when I use the plugin it’s reporting the correct status. The garage has two zwave outlets. And there are two light bulb modules just outside so there shouldn’t be any issues with Vera talking to any of the devices.

Wiring another sensor to have 1 per door would be extremely difficult and I don’t want to deal with wireless. I plan on putting a camera in the garage to verify it’s safe to close the door. I have excellent Z-wave coverage in the garage as there is already a z-wave light switch that has worked reliably for a year.

I have heard the LFM-20 units sometimes lock up… anyone else had issues with this?

Thanks,
Roy