Has anyone tried to hook up the Linear GD00Z Garage Door Controller to their Vera system yet? It is designed for Nexia, but the instructions are generic about the hub.
On the surface, it seems like a nice piece of kit. It has a receiver module and comes with a tilt sensor to provide he state of the door. The receiver has a light that will flash when the door is about to be operated remotely to alert anyone that might be in the way and it also has an audible warning. According to the instructions, it simply connects to the same terminals as the garage door button. It also acts as a Z-Wave repeater.
I have one and it will not work with Vera. They say that u17 is going to support it but not u15. I tried u17 and had problems so I went back to u15.Good luck. They don’t seem to be in a hurry to support their customers.
I ordered it yesterday and it arrived today (good shipping points for the eBay seller!). I have included it in the system and I will hang it in the Garage later today. It added as a Window Covering controller device type.
The first attempt to add did not go smoothly, i ended up with an unknown device and the garage door opener but the opener would not configure. I deleted both and tried again. The 2nd attempt worked quickly and smoothly. It is now added.
We will see how it goes once I hang it in the garage.
You got this working! I have been sitting on ice waiting for the mysterious upgrade scheduled for mid-Nov and getting a cold tush. I have one installed but gave up on it until the upgrade.
Using UI7 fw1.7.388. Did this just take persistence or do I need to stand on one leg while hitting the inclusion button?
Life has gotten i the way and I have not had a chance to put it in the garage just yet. As far as inclusion, I really just followed the instructions.
Put UI7 (1.7.388) into add mode
Pressed the include button on the side of the GD00Z
waited and watched until it was added.
Like I said earlier, it did not seem to work the first try. I deleted all the artifacts that it created and tried again. It worked on the second try. I also had the unit sitting within 3 feet of the controller in my office for the include. I did not try and so the include with the unit near where it is going to be installed.
BTW, I have the GD00Z-3. Amazon is selling the GD00Z-4 (Only $90 on Amazon?). I do not know how much of a difference the version of the device will make.
Ok so the garage door opener paired and worked swimmingly. However there is an anomaly to report regarding its operation. The icon is a light bulb. The switch reports open and closed on its label but that is because all my binary lights now report open and closed.
Is this the same for all the others that got this device to pair? If it is not what is the device_type, device_file, and device_json for the device in the advanced settings for you?
I just installed mine this morning and it works awesome as well. I have the same issue though that the icon/classification are on/off switch so a light bulb.
Well, My problem is different. It is NOT working for me before the firmware upgrade. I am having a difficult time getting the firmware upgraded. However, my control for the device is not a light bulb. It is a Window covering control. It is paired and is sending and receiving commands but nothing is happening in the garage.
I will report back after getting the firmware installed.
I recently upgraded to the latest UI7 firmware which supports the Linear gd00z garage door opener. So I installed one of two units yesterday. I have 2 garage doors and expect to install 2 units but am concerned that the sensors may collide. However since I didn’t have to pair the sensor with the unit I installed yesterday I am assuming that they are prepaired at the factory (sensor to the actual gd00z unit). Can anyone confirm this?
It works but my experience has thus far been less than exciting:
As others already point out the device specific page uses the binary switch/light bulb metaphor. It is odd to see a light bulb setting of “on” to mean the garage door is open.
The “Devices” page get it partially right as it correctly show the words “opened” or “closed” as the device’s status (even though the device icon is still a light bulb).
The unit is very sloooow to detect the garage door’s state (from the wireless sensor mounted on the door) and update Vera. Example: If the door is “closed” and I manually tap the door close switch on the wall the garage door, of course, opens. But my Vera continues to show the gd00z with a “closed” state. This is a huge problem because if I have a scene that tries to close the garage door it will think it is already closed and not toggle the switch.
It is important to understand that this device can only toggle the garage door opener – just like your wall switch. It has to rely on a tilt sensor mounted to the garage door to determine what state the door is currently in.
If this state is not updated quickly enough then the logic applied is false: it thinks it is closing the door but really it is opening the door.
I can live with #1 and #2; those are just aesthetic annoyances. But #3 is a security risk. Another garage door tilt sensor already mounted to the door (Ecolink Garage Door Tilt Sensor) which is accurate and fast to update my Vera. This sensor and the gd00z are often out of sync. I see this as a problem.
I don’t know if it is a Vera issue or a Linear issue. Either way I am struggling to fix this. It would be a shame to have to return these units.
I am testing the GDC1 from a different manufacturer that also uses a similar connection with Vera it seems. If I use a different device than the GDC1 to open or close the door, eg the wall control or car remote, it’s sensor doesn’t update either. It generally takes a couple of minutes for this to update.
It’s been explained to me that when the opener sends a status report to Vera after the sensor triggers (without the opener being the one used to open/close the door) the new status doesn’t make it to the UI for some reason. The UI seems only to bey updated after Vera polls the GDO and notices the status change.
I’ve been tinkering with the PollSettings value in the advanced tab for the last few weeks and reduced it all the way down to 5 from 60. It now takes about 2 to 3 minutes at most for the door status to be correct. I’ll be setting it to 1 Monday and see if that shortens the delay even more.
Although a bit of a nuisance, to me it’s not a big deal as I have an ecolink tilt sensor installed already and all my scenes are triggered by that one rather than either of the openers.
Worst case, I’ll implement NASA protocol. Majority of the 3 sensors (ecolink, GDC1 and MyQ) status defines final status.
UPDATE: I FIXED IT!!!
Inspired by my own post (it made me rethink out the steps I have taken to troubleshoot) I worked through my diagnostic logic again. This time I focused on the sensor mounted to the garage door. After some monkeying around with it I found that the “engagement” switch was not closing. This is the little switch just under the battery when the sensor is detached from the wall mounting plate (that mounts to the garage door). In my case, for some reason, when I attached the sensor to the wall plate the little switch was not engaging. The wall plate has a small protrusion designed to push against this switch. For some reason that was not occurring.
When this switch is not pressed (in the open state) it does not send any signal therefore the gd00z assumes the door is open (presumably for security purposes: if the sensor falls off of the door or the battery dies).
I folded up a tiny piece of paper and placed it between the switch and the protrusion on the wall plate. Essentially forcing contact to occur. At this point it is working fine.
My next step is to install the second one.
@BOFH
I set my unit’s polling time to 15 seconds as well. For something like this where security is at play AND the unit is wall powered (not battery powered) I prefer the updated polling frequency.
I like your NASA approach. I typically do the same, but not by design-- more like I keep playing with new sensors until something finally works for me.
UPDATE (part 2):
I installed the second unit. The sensors don’t seem to conflict with the units. Each one works independently and there is no collisions. I need to test it out a bit more, but thus far it looks good!
[quote=“mrslother, post:16, topic:183965”]UPDATE (part 2):
I installed the second unit. The sensors don’t seem to conflict with the units. Each one works independently and there is no collisions. I need to test it out a bit more, but thus far it looks good! :)[/quote]
Thanks for the update! I am still trying to decide which option that I am going with. Does the device still show up as a light bulb? Is this issue being worked by vera?
In the latest UI7 it does show up as a light bulb. However in the devices view (not the specific device page) the text says “open” or “closed” (as opposed to “on” or “off”). Although I noticed my other light bulbs are now saying “open”/“close”. Fix one issue, break another.
Whereas the UI metaphors are a bit broken, the functionality works just fine. I am sure that, over time, they will refine and fix the UI.
I have also decided to revamp my open garage door monitoring. I set it up so that when the garage door is open it will use my Sonos to announce “A garage door is open”. It then sleeps for 15 minutes and repeats this process until the door is closed. I am going to change this to having a scene run every 15 minutes. That scene will test if a door is open. If it is then it will announce over Sonos.
I decided to do to accommodate scenarios like power outages. If the Vera reboots for whatever reason I want it to discover the problem. My previous implementation expected a trigger to start the process.
Just got the GD00Z-3, with Vera Lite 2, firmware v1.7.439. When following the steps to associate, nothing appears to happen. I hold the button on the GD00Z and after about 10 seconds it does a single beep, the after another few seconds it beeps every second or so. The Vera doesn’t respond (just keeps counting down). I’ve tried removing the association (unplugging Vera, going on battery power), and associating manually with the Vera (battery power, not via web interface) and via the web interface, with no response, anybody else? Suggestions?
