www.linearcorp.com/product_detail.php?productId=1719
It is now available at Lowes. Just bought one, but am hesitant to open it until I know it will work (I have 90 days to return it).
Lowes Garage Door Controller
- 167 Views
- Last Post 25 May 2015
arichter5
posted this
27 July 2014
Ryan-Scott
posted this
28 July 2014
Does anyone know if the new Lowes Garage Door Controller works with inControl and the USB stick? I read somewhere that is made by Linear and is z-wave based. This looks like a perfect solution for my vacation home.
Can you provide a link to a website showing info about the device?
arichter5
posted this
28 July 2014
www.linearcorp.com/product_detail.php?productId=1719
It is now available at Lowes. Just bought one, but am hesitant to open it until I know it will work (I have 90 days to return it).
arichter5
posted this
09 August 2014
Any news?
christopher.bright@gmail.com
posted this
17 August 2014
I just purchased one of these today and tried installing it and I could not get it to work. InControl reported it as an "EntryControl" device. It seemed to recognize the tilt switch but I could not get it to actually drive my garage door.
Ryan-Scott
posted this
17 August 2014
I just purchased one of these today and tried installing it and I could not get it to work. InControl reported it as an "EntryControl" device. It seemed to recognize the tilt switch but I could not get it to actually drive my garage door.
That's interesting... it sounds like they built it with the same security class that the deadbolt locks use, which means you'd need to use a similar method to add it to InControl (as is shown in this tutorial).
You mentioned that it recognized the tilt switch -- is this a separate device that came with the purchase or is it built into the garage door opener?
christopher.bright@gmail.com
posted this
21 August 2014
I didn't know that there is a special setup for the deadbolts. It definitely seemed to think it was a lock. I'll have to play around with it again using that tutorial and post an update.
The tilt sensor was a separate device that comes with the unit powered by a watch battery. You attach it to the garaged door directly. I think it communicate with the opener unit and not the zwave controller directly.
arichter5
posted this
22 August 2014
I finally decided to open the one I had bought a few weeks ago. I tried to add it in the same way I did my door lock. It does get added, but for me it shows up as a dimmer switch. Pushing the power button icon does not seem to do anything. The thing is supposed to flash and beep when it is ready to open/close the door. Since I have up to 90 days to return it, I'll wait a bit and see if anyone else has any luck getting it to work.
christopher.bright@gmail.com
posted this
30 August 2014
Well I tried adding it following the steps outlined above. It definitely detected the tilt sensor and accurate represented the lock state, but attempting to lock/unlock the door did nothing.
At this point I think I'm just going to return it.
bquaresma@gmail.com
posted this
11 September 2014
I also have this device and would love to see some help in setting it up.
iam2xlt@mindspring.com
posted this
29 September 2014
any update on this? is anyone working on getting this working with incontrol?
rjwerntz
posted this
30 September 2014
I had a reply in: wired relay
Author: is.wave.is@gmail.com
that speaks to an alternative to the Lowe's product because I didn't see any succesful results from any direction utilizing it. My choice is slightly more expensive with a couple extra bells and whistles but it can be done cheaper if warnings aren't desired.
Ryan-Scott
posted this
06 October 2014
Just as way of an update... we have attempted contact with the manufacturer about how the commands are to be implemented, but they've been tight lipped about it. I imagine it's related to some agreement which Lowes has mandated so they don't lose potential sales.
We'll keep trying - it may come to be that we attempt to reverse engineer the device.
tnamey
posted this
06 October 2014
How about this unit. It looks identical to the iris unit but isn't tied to that service.
http://www.linearcorp.com/productdetail.php?productId=1719
arichter5
posted this
11 October 2014
I purchased the Linear version. As far as I can tell, it behaves exactly like the Lowes version. The instructions do give a small amount of info about the z-wave interface. The instructions confirm it is a security enabled z-wave device and therefore does not respond to basic CC commands. Also says that it supports 1 group and 1 node and that group 1 must be assigned the Node ID of the controller to which unsolicited notifications from the device will be sent. The z-wave controller should set this association automatically after inclusion. Not sure what any of that means, but perhaps it may be useful in getting inControl to work with it. I am going to hang on to the device in hopes that a future inControl update allows it to work.
Axial-User
posted this
14 October 2014
Amazon has these now
http://www.amazon.com/gp/product/B00M75TEIU
Here is a comment I ran across - maybe it will help. If there is a way to get it to work with InControl, I may buy one. I also may just get a MiMoLite...
"One of the highlights of the system is its security - it uses the same secure Z-Wave protocol you'll find on Schlage locks. In addition to this, it is also a rare secure Z-Wave repeater - this means any Z-Wave products you have in the area of the controller will repeat through this, which should increase the range. On some Z-Wave setups, you may need to do a rescan or reinitialize of the Z-Wave devices to get them all synced."
Axial-User
posted this
20 October 2014
I did get a MimoLite. Really, it seems to be the perfect solution for a garage door, it works perfectly and even includes a power supply.
Ryan-Scott
posted this
01 November 2014
Hey everyone, just an update... I've got my hands on a test unit from Lowes and I'm starting to see some success with it. I
Anyone interested in giving it a beta/trial run?
bquaresma@gmail.com
posted this
01 November 2014
I have a unit and would be happy to do some trial work with you. Let me know
arichter5
posted this
01 November 2014
I would like to beta test also.
Ryan-Scott
posted this
01 November 2014
Ok everyone, here it is! I'm pretty excited about this, as so far it has worked much better than my current garage door setup with the Evolve LFM-20.
If you'd like to give it a beta run, you can download version 3.151 from here. Be sure to see the instructions on including the garage door into your z-wave network.
Just be aware that you must use InControl to include this into your network, which means either moving your computer to the opener or moving the opener to your computer. [b]It will not work if you use a z-stick to perform the inclusion[/b].
I've only been running with this for a few hours and version 3.151 has had very little testing; I'd test more, but my wife is literally hollering at me to get in the car for a family function.
Please report back your success at setting up and using the opener.
bquaresma@gmail.com
posted this
01 November 2014
Got it set up easily! Everything working well so far. However shows up as a dimmer in the Andriod App and does not function. Also as an FYI mine wouldn't work until I installed the tilt sensor, not an InControl issue, but maybe good to know for someone else.
pir8radio
posted this
01 November 2014
Works, but not useable yet... I cant seem to use it in scenes (prob user error). I cant see it or change its state from the phone APPS. So unless im strapping my HA server to my back when im outside of the garage door.. uhh it doesn't do me any good. :-) lol I'm just being a smart A$$ I'm very happy that it functions though... but how do I go about getting the above things to work? Maybe change it to show as an EntryControl device rather than garage door?
pir8radio
posted this
01 November 2014
I also keep getting an error:
Command expired:
Node:22
date time
Command:
COMMANDCLASSBARRIEROPERATOR.BARRIEROPERATOR_GET
Ryan-Scott
posted this
01 November 2014
I also keep getting an error:
Command expired:
Node:22
date time
Command:
COMMANDCLASSBARRIEROPERATOR.BARRIEROPERATOR_GET
You are probably outside of your optimal range for communicating with the device. You may consider purchasing a few devices to add in between, like an Aeon Labs repeater.
Ryan-Scott
posted this
01 November 2014
In order to control this from a phone, you'll need to find the device in the "light" list - once we update the app, we'll add a new category for it.
Ryan-Scott
posted this
02 November 2014
Works, but not useable yet... I cant seem to use it in scenes (prob user error). I cant see it or change its state from the phone APPS. So unless im strapping my HA server to my back when im outside of the garage door.. uhh it doesn't do me any good. :-) lol I'm just being a smart A$$ I'm very happy that it functions though... but how do I go about getting the above things to work? Maybe change it to show as an EntryControl device rather than garage door?
You should be able to see it in the list of "lights" on your device and control it; note, I've tested this on Android only so far, so if you are on iPhone, that might be why - I'll have to charge up my iPhone and see if there's something odd. For the scene... yes, we do need to add some controls for it.
bquaresma@gmail.com
posted this
02 November 2014
I do see it as a light, however there seems to be no effect to turning the "light" on and off
Yokel
posted this
03 November 2014
It's working pretty reliably for me. I have it working with a couple of scenes. One based on GPS location & another tied to a door sensor. I'm getting the same error as above occasionally too(i have a couple of other Zwave devices within a few feet of the garage door controller). My only gripe is it takes 45 seconds between commands to to respond to the next command. Pretty darn good for an initial beta.
Ryan-Scott
posted this
03 November 2014
It's working pretty reliably for me. I have it working with a couple of scenes. One based on GPS location & another tied to a door sensor. I'm getting the same error as above occasionally too(i have a couple of other Zwave devices within a few feet of the garage door controller). My only gripe is it takes 45 seconds between commands to to respond to the next command. Pretty darn good for an initial beta.
Where's the 45 second delay coming in? Is it that the opener itself won't respond until 45 seconds later or are all device unresponsive?
Yokel
posted this
04 November 2014
I went back & timed it. It's right at 30 secs. I think it's coming from the garage controller(a safety feature peehaps). Controlling other devices works fine in the same time period. Not a big deal, just a little annoying to wait 30 secs in your driveway for it to begin responding to the close command. A moot point really as I have it completely automated now.
Update - This is from the manual:
If, due to an obstruction or other cause, the door does not completely open or close when it is activated remotely, the Controller will pause for 30 seconds. After the delay, a second remote activation can be attempted. If the door does not complete it's motion on the second attempt, the Controller will suspend operation until the door is operated locally with the opener's pushbutton wall console.
arichter5
posted this
08 November 2014
Is 3.151 still the most recent beta version? I plan to try it with my garage door opener this weekend.
arichter5
posted this
08 November 2014
Success! Seems to be working well. I do not have the 30 second delay issue. Very quickly starts beeping, then opens/closes. I guess my next request is for the Android App to treat it as a garage door rather than a light.
CasualSurveyor
posted this
09 November 2014
Just as way of an update... we have attempted contact with the manufacturer about how the commands are to be implemented, but they've been tight lipped about it. I imagine it's related to some agreement which Lowes has mandated so they don't lose potential sales.
Well, they're losing my potential sale.
arichter5
posted this
09 November 2014
How do I control this from a scene? I can add it to a scene, but there is no choice to set it as open or closed (or on/off) within the scene setup window. Usually this setting would be right below the name of the device in the right hand panel. All I see is the gear for advanced options.
CasualSurveyor
posted this
09 November 2014
It's great that you are working on this, Ryan.
My garage is stand-alone building about 100 feet from the house where my Z-Wave system is running. Is there a way to extend the Z-Wave system out to another building?
pir8radio
posted this
10 November 2014
Works, but not useable yet... I cant seem to use it in scenes (prob user error). I cant see it or change its state from the phone APPS. So unless im strapping my HA server to my back when im outside of the garage door.. uhh it doesn't do me any good. :-) lol I'm just being a smart A$$ I'm very happy that it functions though... but how do I go about getting the above things to work? Maybe change it to show as an EntryControl device rather than garage door?
You should be able to see it in the list of "lights" on your device and control it; note, I've tested this on Android only so far, so if you are on iPhone, that might be why - I'll have to charge up my iPhone and see if there's something odd. For the scene... yes, we do need to add some controls for it.
It does not show up in lights, I use windows phone 8 how do i use it in scenes? there isnt an "OPEN" or "CLOSED" or TOGGLE option.
Yokel
posted this
11 November 2014
"How do I control this from a scene? I can add it to a scene, but there is no choice to set it as open or closed (or on/off) within the scene setup window. Usually this setting would be right below the name of the device in the right hand panel. All I see is the gear for advanced option."
It functions as a toggle now. Just add it to a scene & activate it. Your door should open/close.
Here's a scene i have tied to a door sensor leading from the garage into the house. I open the entry door & the garage door closes. Condition keeps it from firing when the door is closed. 255 is the value for open.
Sample
Device: Garage door
Trigger: device @ state - door sensor changes to open
Condition: Device @ state - Garage door is > level 0
mattshane
posted this
11 November 2014
Hello all. First time posting here so If I screw it up, my bad.
Just wanted to clear a few things up as there seems to be some questions on how this thing works.
This is relating to the device itself. I work for Linear and this is one of my projects.
First things first:
- This is a barrier command class device, not a lock. They seem similar and controllers that do not support that command class will see them as a lock.
- The delay, Unfortunately there are three delays in the device that are not published (not my fault, I thought they should be)
- First delay - The tilt sensor is a 345MHz transmitter that gives the door state to the linear door control. It has a ball tilt sensor in it that is prone to send open closes when the door shakes. Because all doors shake while closed, we programmed a 4 sec debounce (delay) into the software of the device.
- Second delay - UL Requirements forced us to have warning lights (the really annoying strobe) and sounder before the door can be allowed to move.
- Third delay - After the device has received a command, it will ignore all other commands until BOTH of the following happen:
- It gets the change of state from the tilt sensor.
- 30 Seconds has passed since the last command.
We also do not recommend using this device in a scene. It should work but we don't recommend it.
I am happy to see a lot of people using the device (it seems my time wasn't spent in vain testing the dang thing.)
Thanks
Ryan-Scott
posted this
12 November 2014
Hello all. First time posting here so If I screw it up, my bad.
Just wanted to clear a few things up as there seems to be some questions on how this thing works.
This is relating to the device itself. I work for Linear and this is one of my projects.
First things first:
- This is a barrier command class device, not a lock. They seem similar and controllers that do not support that command class will see them as a lock.
- The delay, Unfortunately there are three delays in the device that are not published (not my fault, I thought they should be)
- First delay - The tilt sensor is a 345MHz transmitter that gives the door state to the linear door control. It has a ball tilt sensor in it that is prone to send open closes when the door shakes. Because all doors shake while closed, we programmed a 4 sec debounce (delay) into the software of the device.
- Second delay - UL Requirements forced us to have warning lights (the really annoying strobe) and sounder before the door can be allowed to move.
- Third delay - After the device has received a command, it will ignore all other commands until BOTH of the following happen:
- It gets the change of state from the tilt sensor.
- 30 Seconds has passed since the last command.
We also do not recommend using this device in a scene. It should work but we don't recommend it.
I am happy to see a lot of people using the device (it seems my time wasn't spent in vain testing the dang thing.)
Thanks
Thanks for dropping by and giving us this update - very useful info, especially about the built-in delays.
Ryan-Scott
posted this
12 November 2014
Here's an update that includes scene on/off options for the GDO. Version 3.157 found here.
mattshane
posted this
12 November 2014
@Ryan. Is there a way to get your email. I have some docs that you may find useful.
Matt
pir8radio
posted this
23 November 2014
I still can not use this via WinPhone8 app.. any update on adding the garage door opener to the app? Kind of useless if i cant open the garage door unless im sitting in front of my HA server INSIDE the house.. :-) Seems to work well otherwise...
Ryan-Scott
posted this
23 November 2014
I still can not use this via WinPhone8 app.. any update on adding the garage door opener to the app? Kind of useless if i cant open the garage door unless im sitting in front of my HA server INSIDE the house.. :-) Seems to work well otherwise...
Did you update to the latest version? It adds scene control options for it, that would at least let you control it from your phone.
I'm making some big changes to how rooms work in the main InControl server program. Once that's done, I'll move those changes to the phone apps along with the garage door controls. Should happen fairly soon.
arichter5
posted this
24 November 2014
All seems to be working well with 3.157. Successfully added the garage door opener to a scene to close the door if it is open. The scene activates every 30 minutes between sunset and 6 AM.
joey10e
posted this
26 April 2015
I just got one of these devices and I am trying to include it using Incontrol. I have the linear device inside right next to my computer with the aeon labs z-stick as my main controller. I have tried the Tools\Z-Wave Commands\Add New Device after waiting for the controller to lock I press the button on the linear device and hear one beep and then three beeps. It seems like Incontrol just does not pick up the signal from the device. I would love any help or suggestions. Thanks in advance.
Ryan-Scott
posted this
27 April 2015
I just got one of these devices and I am trying to include it using Incontrol. I have the linear device inside right next to my computer with the aeon labs z-stick as my main controller. I have tried the Tools\Z-Wave Commands\Add New Device after waiting for the controller to lock I press the button on the linear device and hear one beep and then three beeps. It seems like Incontrol just does not pick up the signal from the device. I would love any help or suggestions. Thanks in advance.
You might try to exclude it first to make sure the device is reset back to factory settings. After that, try to give it another inclusion.
joey10e
posted this
27 April 2015
Thanks Ryan,
I tried that and I was able to get the device to add to incontroll but now when I try to open the garage door from incontroll nothing happens. Any Ideas?
Ryan-Scott
posted this
27 April 2015
[quote=joey10e]Thanks Ryan, I tried that and I was able to get the device to add to incontroll but now when I try to open the garage door from incontroll nothing happens. Any Ideas?[/quote]
Can you enable your audit for that node (double click it, set the option, then restart your InControl server), enable a 30 second poll then use a Github Gist to send the contents of your logfile? Also, what do you see when you select the device? Here's mine, you should see a "Barrier State" :
arichter5
posted this
25 May 2015
Ryan,
I just noticed that my garage door opener (and the door state device) no longer shows up in the mobile (Android) app. I think they used to show up as lights. If the garage door is open, they do show up in the list of powered on devices, but as soon as I close the door, they are no longer found anywhere. I can't be exactly sure when this started as it's been a while since I looked for the garage door opener, so I just noticed yesterday.
Any ideas? Did a recent update reclassify them as a different type of device that is not shown in the mobile app? Also, I made sure that neither device had the Hide in Mobile box checked in properties.
Alan
rscott
posted this
25 May 2015
Ryan,
I just noticed that my garage door opener (and the door state device) no longer shows up in the mobile (Android) app. I think they used to show up as lights. If the garage door is open, they do show up in the list of powered on devices, but as soon as I close the door, they are no longer found anywhere. I can't be exactly sure when this started as it's been a while since I looked for the garage door opener, so I just noticed yesterday.
Any ideas? Did a recent update reclassify them as a different type of device that is not shown in the mobile app? Also, I made sure that neither device had the Hide in Mobile box checked in properties.
Alan
If you are talking Android, then yes, there's a new update that introduced a garage door opener type. You could add this type to a shortcut on your home screen and access the GDO directly from there.
