Program HomeLink for Two EVs on One Gate (Without Erasing)

Two electric vehicles, one driveway gate, and pairing the second car keeps erasing the first. To add a second EV to one gate without losing the first pairing, give each car its own HomeLink button slot and wait a full minute between LEARN-button sessions on the opener. Most failures come from presenting car 2 during car 1’s 30-second training window, or holding the LEARN button long enough to wipe every stored code.

HomeLink handles this well once paired. The procedure for pairing the second car is where most two-EV households stumble — often ending with one car working and the other erased, or a 30-minute troubleshooting session that didn’t need to happen.

Why It Is More Work Than One Car

HomeLink uses rolling-code encryption for modern gate openers. With a rolling-code system — LiftMaster, Chamberlain, and any opener using Security+ 2.0 among them — each button press sends a new code. The gate only opens when that code matches what it expects next in sequence. You cannot clone or copy the signal. Each vehicle goes through its own separate handshake with the opener.

That handshake requires a physical LEARN button press on the gate opener’s control board — one press per pairing. Most residential control boards hold memory for four to six different transmitters. Two EVs consume two of those slots. The ceiling is not the problem.

What causes failures is the sequence. The gate’s LEARN mode opens a brief window — typically 30 seconds — during which it accepts the next transmitter presented. If you present both cars inside the same window, or if you start car 2’s pairing before the board has fully closed car 1’s session, the gate may store only one of them, or neither. Getting the sequence right is the whole procedure.

For background on why rolling code works this way, see our piece on HomeLink’s rolling-code programming.

The Right Sequence

Before You Start

Decide which HomeLink button slot each car will use for the gate. In a two-EV household, a common arrangement:

• Car 1: button 1 = garage door, button 2 = driveway gate
• Car 2: button 1 = garage door (trained separately), button 2 = driveway gate

Each car trains its own button 2 independently. The gate opener stores both codes in separate memory slots.

Clear the slot before pairing to avoid writing over an existing pairing:

• Tesla (Model 3/Y/S/X/Cybertruck): Controls > HomeLink in the touchscreen. Select the button and choose Delete.
• Rivian (R1T/R1S): Center-console HomeLink panel. Each button has a delete option.
• F-150 Lightning / GMC vehicles: Hold the button down for about 20 seconds until the indicator flashes rapidly, then release.

Step 1 — Pair the First Vehicle

1. Position car 1 within 30 feet of the gate opener control board.
2. From inside car 1, hold a working gate remote 1 to 3 inches from the designated HomeLink button (button 2, in this example) and press both until the HomeLink indicator changes from a slow to a rapid blink. HomeLink has now captured the signal.
3. Press the LEARN button on the control board once — a brief press, not a long hold. The LEARN LED will light, opening a 30-second window.
4. Return to car 1 and press the trained HomeLink button, up to three times if needed, to close the rolling-code handshake.
5. Test: press the HomeLink button. The gate should open. Press again to close. Confirm it responds consistently.

Wait at least 60 seconds before moving to car 2. Some control boards remain in a sensitive accept state briefly after the LED goes out, and starting car 2’s session too soon can overwrite car 1’s slot on certain boards.

Step 2 — Pair the Second Vehicle

Repeat the procedure: press LEARN once on the control board, then use car 2’s designated HomeLink button. This opens a new memory slot. It does not erase car 1’s slot, provided the board is not already at its maximum capacity and no accidental clear was triggered.

After pairing car 2, test it. Then test car 1 again. Both should operate independently.

Common Failure Modes

Car 2 works, car 1 does not. Car 2 was presented to the LEARN button before car 1’s session fully closed, overwriting the first slot. Pair both again in order, with the full 60-second gap.

Neither car works after pairing car 2. The control board may have received a long LEARN button press, which on many Security+ 2.0 boards clears all stored transmitters rather than starting a new pairing session. A brief press begins pairing; a long hold (typically over 6 seconds on LiftMaster boards) resets memory. Re-pair both cars from scratch if this happened.

One car works intermittently. A rolling-code sync issue: that car’s counter advanced faster than the gate’s expected sequence during a failed pairing attempt. Each HomeLink button press advances the internal counter whether or not the gate receives it. Clear that vehicle’s HomeLink button and re-pair it fresh.

The gate ignores one car entirely. Confirm the correct vehicle is using the specific HomeLink button trained to the gate — not a different button that happens to look similar on the touchscreen. On Tesla, HomeLink button management lives under Controls > HomeLink, not in a generic shortcut menu. On Rivian, the center-console HomeLink panel is separate from multimedia controls.

Cross-EV Compatibility Note

Tesla and Rivian both ship with a Gentex-designed HomeLink module. The radio hardware, frequency range, and rolling-code protocol are the same underlying technology. A gate opener that pairs with a Tesla Model Y’s HomeLink will pair with a Rivian R1T’s HomeLink using the identical procedure — there is no frequency conflict between the two vehicles.

F-150 Lightning and GMC Hummer EV also use HomeLink, though button placement differs (visor-mounted on the Lightning, right visor panel on the Hummer EV). The pairing procedure is the same across all of them.

For why HomeLink sometimes fails with driveway gates specifically — regardless of car model — see how HomeLink actually works and where it breaks.

A Different Approach

The per-car pairing procedure works reliably once you get the sequence right. Its limitation is that each new vehicle — a lease return, a trade-in, a second car added to the household — means another LEARN button session, another pairing to track.

There is a newer category of gate automation that removes the per-car step entirely. Vehicle-paired auto-open uses the car’s GPS position rather than a HomeLink channel: the gate responds to the vehicle’s proximity, not to an in-car button. No LEARN press, no rolling-code sync, and no re-pairing when a vehicle changes. Proxly is building in this category — the Hub installs at the gate opener and opens the gate based on your car’s approach, regardless of make or model. Our piece on the premium-EV arrival stack covers how this layer fits into a two-EV driveway setup.

---

FAQ

Will pairing my second EV’s HomeLink erase my first EV’s pairing?

Not automatically. Most control boards store each pairing in a separate memory slot. The risk is pressing the gate’s LEARN button while the first car is still in the training window, or accidentally triggering a full memory clear. Follow the sequence above and wait a full minute between pairing sessions.

My gate opener has only one LEARN button — can it still learn two different cars?

Yes. A single LEARN button initiates a pairing session for any transmitter. You press it once per vehicle, at separate times. Memory capacity is a separate spec from the number of physical buttons on the board — a single LEARN button can serve four, six, or more paired transmitters over time.

How many vehicles can I pair to one gate opener?

Most residential rolling-code receivers hold four to six transmitter codes. Two EVs use two of those slots, well within the limit of any residential gate opener. Check your opener’s manual for the exact capacity — it varies by control board model.

Tesla and Rivian both use HomeLink — will they conflict with each other on one gate?

No. Each car’s HomeLink button sends a unique rolling-code sequence that only your specific gate is calibrated to accept. There is no shared-frequency conflict between a Tesla and a Rivian paired to the same opener. Both use the same Gentex-designed HomeLink hardware and frequency range, but separate rolling-code counters.

After pairing both EVs, one only works sometimes. What happened?

Most likely a rolling-code sync issue: that car’s code counter got ahead of what the gate expects, typically from pressing the HomeLink button multiple times during a failed pairing attempt. Clear that vehicle’s HomeLink button, re-pair it from scratch, and test with a single deliberate press at the gate.