Great to hear!
I feel so lucky. I've been reading a couple of threads on this garage door control, and was dreading having issues.
It worked first time! I didn't even have to move my hub, and it's on the other end of the house!
Not gloating, just wanted to give hope to anyone else reading this thread!
I installed one for my mother this past weekend and it was flawless. Not sure if it is due to the updated software in the Hubitat or the newer garage door controller. Either way, it paired on the first go around.
I was able to exclude the iRis - Linear GD00Z-4 Garage Door Opener from my SmartThings and include it on the Hubitat Elevation hub in seconds. It was a breeze. However, upon testing I am finding out the door status is acting strange. When I opened the door the first time the devices menu show status correctly reporting Door Opening, then when it got fully open, the status changed to Open. So far so good. It was the closing part that is broken. When I execute a close from the devices menu, again the status is updated and correctly reports Door Closing but the door status show Open even after the door is fully closed. After a long time I will come back to check on the status and it eventually shows the change to Closed but that is much much later.
What is going on with my door tilt sensor and reporting the change so very slowly?
I have a monitoring rule setup to alert me if the garage door is open longer than 5 minutes so I can close it. This monitoring rule is being falsely triggered because it "thinks" the door is still open.
If you have a spare zwave plug I would give it a shot. The radio on the HE hub isn't as strong as ST. I had to add a repeater (iris smart outlet) in my garage to get consistent reporting for my contact sensor, lock and garage opener.
Not saying that is necessarily your issue, but it's worth a shot if you have an outlet laying around...and don't forget to do a zwave repair after adding the repeater. In fact, have you done a repair since adding your garage controller...that might be also worth a shot before adding the repeater. Open your logs before doing the repair so you can see if it generates any errors as well.
Yes that is a good idea. I am going to get a repeater in the garage. Right now I am having a weird issue with the hub not controlling things well, sometimes it does and sometimes it doesn't so I am not sure if this contact issue is related but I will watch.
UPDATE: Also there is no way for me to know the battery status on that Tilt Sensor? It might be the battery needs replacing? I don't remember when I last changed it.
I ran the Z-Wave repair and the it went without any hitches or errors logged. I will also try replacing the battery on the tile sensor to see if there are any changes? Maybe after that resetting the controller and starting from scratch and rejoining the tilt sensor with the controller again. I have lots of little issues that have cropped up with HE right now in my migration and I need to slow down and start tackling them head on one at time to isolate what is going on.
Right now I just need my Hubitat Safety Monitor (HSM) and Simple Lighting Rules (HSL) to work flawlessly. If she flips the bedroom WD100 or voice commands it, the lights need to go on or off immediately as desired. A voice command to set HSM to Arm-Away or Arm-Home needs to be set on immediately as desired. Unfortunately it just ain't happening and the system is either stuck or just slow as molasses.
Thanks to this thread I was able to my gd00z-04 to pair. I had to basically put the hub on it to exchange the secure key. Even three feet away was to far.
Coming from Wink, the app showed the total time the garage door was closed and open. Is there any way to get this in Hubitat?
Did you ever find a solution for this?
Im having the same issue.
The older ones used low power pairing so someone couldn't sniff the join. The newer ones will do nwi on normal power.
Try this RM4 rule. Mine updates ok so I can't exactly test it but it should work. I have a tilt sensor in addition to the GDZ to trigger as a second set of eyes.
Here are the options to pick for the refresh:
@lewis.heidrick I forgot about "Refresh"..... Thanks! It looks like it works now.
I added Refresh to my WebCore piston 30 seconds after I send a garage door open or close command to check the status after the door is done moving.
Unless your garage door is really slow you could probably cut that time in half. If it is slow, try the release handle to disconnect it from the motor. Open and close the garage door. It should open and close with equal force. If it's not you may need to adjust or replace the springs.
Thanks. I was being over cautious on the time. I could probably cut it in half, but was too lazy to go downstairs to the garage to time the opening.
If you can't display the same level of OCD-driven behavior about this stuff that we do, we may have to ask you to turn in your hub. Please bear that in mind in the future.
I am trying to follow these instructions. I have a Linear GD00Z-2 that I had working with my Smartthings hub. But I have now turned off my Smartthings hub and have changed everything to Hubitat.
I did verify the battery in my tilt sensor is good.
I am successful following your instructions up to step 4.
When I try to pair, I am holding the Linear pairing button for 7 seconds until it beeps, then doing a "Start Z-Wave Inclusion" but nothing is ever found.
Any suggestions? thx as always for the help.
How far is your Hub from the Garage Door Controller? I had to take my hub pretty close to the garage door controller before it would pair. I used a long ethernet extension cord and a phone battery pack to move the hub around to get everything to pair.
EDIT: I am assuming you were able to "exclude" the device successfully? If not, you may want to try Steps 2 and 3 in the "exclusion" section here:
Like @rakeshg mentioned, the garage door controller has to be pretty close to the Hubitat in order to pair. I had to run a 50 foot cat6 cable across the floor into my garage with the Hubitat on one end and the other connected to my router. My Linear controller wouldn't pair until it was within arms reach of the Hubitat.
I just put the hubitat within 1 ft of the Linear Controller.
I tried the pair process, the exclude process - no joy.
To pair, I am holding the button on the Linear controller for 7 seconds or so until it beeps.
These are Barrier devices and depending on vintage, might need a FLiRs repeater nearby. FLiRs is intended to help with battery devices but who knows what some individual coding engineer at Nortek decided to do.
I have one of these and I tried a lot of things to get it to pair, I gave up for a few days and when I came back, it worked first try, Hub a great distance away. I've always assumed that the other devices I added between giving up and the 2nd try convinced the hub and the GDO to use FLiRs.
The next time I needed to exclude-then-include was when I added a C-7 to that area of my home. I left it to "last" for that day's worth of device migration, but it worked first try.
I know it's not helpful, but think of this message as "cheerleading" to assist with motivation