Homelink issue

greylock

New Member

Verified Owner
Joined
Aug 5, 2026
Messages
16
Reaction score
25
Location
Westchester County, NY
Cars
26 Gravity GT
I'm four days into ownership and everything has worked perfectly so far, with one exception.

I open the garage door before I get in the car, back out of the garage and hit the Homelink button and the garage door starts to close... Great. But then it starts to rise again on its own. I'm not doing anything, although it is possible that shifting into drive after pressing the button might be the problem... I'm still experimenting. In any case, at that point it appears that Homelink doesn't react to the button at all, or only after several presses. So I'm relegated to using my old garage remote to close the door. There is NO problem on returning to the garage... one press lifts the door, and I use the control on the garage wall to close the door.

Also, is there a reason that if you've only input one garage door that you still get a dropdown to pick a garage? I have a second garage that I'm planning to add eventually, but I'm trying to get the one-garage routine to work flawlessly first.
 
[…] I open the garage door before I get in the car, back out of the garage and hit the Homelink button and the garage door starts to close... Great. But then it starts to rise again on its own. […]
Is your garage door signaling that there is an obstruction and is your receiver facing the sun?

I used to have random failures that would require multiple tries to close my garage door. I put up with this for a few years since it didn’t happen very often and I’m too busy driving off to debug. Then, one day, I couldn’t get the garage door to close. It kept signaling an obstruction, but there was nothing there. The stars, err sun, was perfectly aligned - literally.

It turned out the sun was shining into the receiver and interfering with the sensor. The garage closed fine when I put the sensor in shadow. The angle of the sun had to be just right, as most of the time the sensor worked with the sun shining on it.

I swapped the transmitter and receiver so that the receiver would not be facing the sun, and my garage door has worked perfectly since then. Also check for spiderwebs, as that can also cause intermittent obstruction.
 
I think I've figured it out. After backing out, shifting from reverse to drive while still pointing in the general direction of the garage appears to to stop the close operation. If I wait until the garage door fully closes to shift into drive, there seems to be no problem. While I kinda halfway understand this as a "feature," it's going to take some getting used to.
 
Did you install the latest 3.6.3 in your Gravity? Has this issue started prior to 3.6.3? Did it resolve or change after 3.6.3?
My Homelink experience has variety of weird bugs and difficult to explained behaviors, which is fluid day to day that I can't figure out when it started and if anything gets better or worse with each update. I've seen the same behavior you describe, in addition to plenty of other situations related to having 3 entries in my Homelink devices list.
I have a gate and a garage door at my new home and Homelink could randomly act on either one, regardless of what I touch or don't touch on the screen.
I still can't figure out if it's all random or if there is some organized madness in that software.
 
I think I've figured it out. After backing out, shifting from reverse to drive while still pointing in the general direction of the garage appears to to stop the close operation. If I wait until the garage door fully closes to shift into drive, there seems to be no problem. While I kinda halfway understand this as a "feature," it's going to take some getting used to.
You could also shift into drive before hitting the homelink button to keep it from interrupting when changing from R to D. Seems less annoying that waiting to me. That said, I'd report that as a bug to the [email protected] email as it doesn't seem like intended behavior.
 
Did you install the latest 3.6.3 in your Gravity? Has this issue started prior to 3.6.3? Did it resolve or change after 3.6.3?
My Homelink experience has variety of weird bugs and difficult to explained behaviors, which is fluid day to day that I can't figure out when it started and if anything gets better or worse with each update. I've seen the same behavior you describe, in addition to plenty of other situations related to having 3 entries in my Homelink devices list.
I have a gate and a garage door at my new home and Homelink could randomly act on either one, regardless of what I touch or don't touch on the screen.
I still can't figure out if it's all random or if there is some organized madness in that software.
I am on 3.6.3 (It's the only version I've had here in my fifth day). So I have no pre 3.6.3 experience.
 
Homelink works pretty well for us anymore. Three things:
1) Getting the right button press takes getting used to. We did a lot of light tapping, which didn't register, or over holding, which caused it to start and immediately stop, before we got it right. This is a simple touchscreen read and should work better.
2) When you back out of the garage you may see a full list of all programmed doors, because it hasn't had time to get a solid GPS signal yet. On returning home it should show only the local garage doors on the list.
3) Getting it set up in the beginning is a bit persnickety. When it asks for it, put your remote on the bumper just below the 2nd driver side headlight and hold the button down long enough to hear it beep.

Per #2, at the Charlotte event the dev lead said the GPS location code on the NVidia stack will be faster, when they move over to it.
 
You could also shift into drive before hitting the homelink button to keep it from interrupting when changing from R to D. Seems less annoying that waiting to me. That said, I'd report that as a bug to the [email protected] email as it doesn't seem like intended behavior.
Yeah, but at least for the moment, I'm waiting either way, since the last thing I want is to mistakenly take off with the garage door open. Just happy with making it useable for the moment. And I can't stress enough how trouble-free everything else has been.
 
Yeah, but at least for the moment, I'm waiting either way, since the last thing I want is to mistakenly take off with the garage door open. Just happy with making it useable for the moment. And I can't stress enough how trouble-free everything else has been.
Ah, true. My garage door lets me know if I left it open when I drive away so it makes it easier to not forget (or fix it when I do!).
 
On returning home it should show only the local garage doors on the list.
You don't have the issue where the list is rendered on screen with only one line, while in fact there are more than one entries?
In my case I have an entrance gate and a garage door, both within 100ft of the car on approach, so it detects location based on GPS, but only shows one entry, sometimes it's a gate, sometimes it's a door. Sometimes when it's a gate, which I need to open first, I reach to touch it, but at the moment of touching the screen it changes to the door.
Sometimes I can clearly see the right name and response to touch, but it's actually opening/closing the other one.
When leaving garage and GPS is not locked in yet the list shows all entries, but often it's acting on the wrong one. For example I touch the gate, but instead it's closing the garage.
I've done my share of UI programming back in my youth, so this random or convoluted UI behavior is driving me nuts as I'm trying to seek logical explanations and find workarounds.
 
oo! what setup do you use for that? Wyze?
A Home Assistant automation that sends a notification if the garage door is open when I leave home. And then I can close it using HA.
 
Back
Top