Pairing a Garage Door With TaHoma Switch, Step by Step

This post may contain affiliate links. As an Amazon Associate we earn from qualifying purchases. Disclosure.

Blinds are forgiving. If a shade ignores a command you shrug and press the button again. A garage door is the heaviest thing in my house that moves on a schedule, and it was the last motor I put on the network precisely because I expected it to be the fussiest. It was, though not in the way I expected.

The pairing worked on the first attempt. Everything after the pairing is where the afternoon went.

What Do You Need Before You Start?

Four things, and only one of them is the hub.

• An io-homecontrol garage operator. Mine is the Somfy Dexxo Smart io, rated for doors up to 10 m2 and 200 kg. The same unit is sold under some door manufacturers' own brand names, so check the radio, not the badge.
• A Somfy TaHoma Switch on your network, already set up in the TaHoma app.
• The Somfy Keygo io remotes that came in the box. You need a physical transmitter to test with, and you will need it again later.
• The installation manual for your operator. I mean it. The button sequences on the motor head are model-specific, and I am not going to guess them for you.

Worth measuring before any of this: my door is 4750 by 2100 mm, which is 9.975 m2 against a 10 m2 limit. Headroom was 400 mm, side clearance 110 mm each side, garage depth 3310 mm for a 2900 mm belt rail. If your door does not fit inside those numbers, no amount of clever pairing helps.

Why Does the Order of Operations Matter?

Because the app encourages the wrong one, and the wrong one fails silently.

The obvious sequence is to mount the operator, open the TaHoma app, add the device, and start pressing buttons on your phone. That is what the app's flow suggests, and the pairing step genuinely does succeed. You get a tile. The tile looks exactly like a working tile.

The sequence that works puts the motor first. Set the travel limits on the motor head first. Prove the door runs end to end from the handheld remote, and only then let a hub anywhere near it. A hub can expose a motor. It cannot commission one. Everything a garage operator needs to know about your particular door lives in the motor's own memory, and the hub has no visibility into whether any of it is there.

That is not a Somfy quirk; it is how these operators are built. It is just badly signposted.

How Do You Set the Travel Limits on the Motor?

The travel limits are the closed position and the open position, taught to the motor by walking the door to each end and confirming. Until both exist, the operator has no idea how far to run or when to stop, and it treats every remote command as unsafe.

Do this with the door mechanically finished: springs balanced, rail level, arm attached, and the carriage engaged. Fit and test the safety accessories at this stage too. Mine has photocells across the opening, and the point of testing them now is that they change how the motor behaves. Break the beam while the door is closing and it should reverse. If it does not, stop and fix that before anything else, because no amount of automation makes an unsafe door acceptable.

The Buttons on the Motor Head

The head carries four controls: PROG, SET, plus and minus. PROG handles radio and pairing, SET walks you through the setup and parameter list, and plus and minus move the door or change the value you are on. The exact press-and-hold pattern differs between the 800 io and 1000 io variants and between firmware revisions, so follow your manual rather than a sequence you found in a forum.

What you should end up with is a door that runs fully closed to fully open and back from the Keygo io remote alone, with no hub involved and no phone in your hand. That is the checkpoint. Do not move on without it.

The parameter list behind SET is worth a slow read rather than a skim. It holds the force settings, the behavior after an obstacle, and how the operator treats its safety inputs, and those are the settings that decide whether the door is safe rather than merely convenient. If you are not certain what a value does, leave it at the factory setting and ask the installer.

How Do You Pair the Door With TaHoma Switch?

Once the motor knows its own door, the hub part is genuinely quick.

1. Put the motor head into radio programming mode using the PROG button, following the manual for your variant.
2. In the TaHoma app, choose to add a device, then select the io-homecontrol category and the garage door type.
3. Let the app scan. The hub finds the operator over io-homecontrol on 868.300 and 868.950 MHz.
4. Confirm the pairing on the motor when prompted, then name the device in the app.
5. Test open, stop, and close from the app while standing where you can see the door.

Mine went through on the first attempt, which surprised me, and I have since seen enough forum threads to think that is the normal case rather than luck. The pairing is not the hard part of this job.

Name it something a human would say out loud. Whatever the installer called it during commissioning is not that. This name becomes the voice command later, and renaming things after you have exposed them to Google causes more mess than doing it properly now.

What If the Door Ignores the App?

This is what happened to me, and it is worth the whole article on its own.

The door appeared in the app. The tile rendered normally. I pressed open and nothing moved. I pressed close, still nothing. No error message, no warning triangle, no timeout, just a control that did precisely nothing while reporting no problem at all. I spent longer than I want to admit convinced the pairing had half-failed, and I kept re-running it.

The pairing was fine. The operator had lost its end-point calibration. An operator with no end points refuses every remote command, accepting only the buttons on its own head, and it will not tell the hub why. The fix was to go back to the motor and walk the travel limits again by hand, teaching it the closed position and the open position from the head. After that the phone worked instantly, with no re-pairing needed.

Four symptoms come up again and again on a freshly paired door, and each one points at a different cause. Read the symptom, not the tile.

So if your newly added door does nothing: stop touching the app. Walk to the motor, confirm the door runs end to end from the physical remote, and if it does not, the limits are your problem and not the radio.

Adding Voice Through Google Home

With the door working in the TaHoma app, voice is an account link rather than a configuration job. Link Somfy in the Google Home app, or link Google to Home Assistant if you are running the chain with Home Assistant in the middle, which is what I recommend, and that article explains why. Home Assistant reaches a TaHoma hub through the Overkiz integration, and the door arrives there as a cover entity.

One thing to check first: Somfy's own Google Assistant page talks about blinds, shades, RTS channels, and scenes. I could not find a garage operator listed on it. If the device type you care about is not there, routing through Home Assistant is what gets it a voice command at all.

The PIN Google Asks For

Google will ask you to speak a PIN before it opens a garage door, and it does not ask when you close one. That asymmetry is correct for a device that is a hole in the wall of your house, but budget a few seconds for it and expect it to struggle in a noisy car.

The payoff is real, though. No more digging through the door pocket for the remote on the approach. I say "Hey Google, open the garage door" into Android Auto somewhere before the turn, answer the PIN, and the door is already moving by the time I get there.

Pick the device name with that sentence in mind. Whatever you called the door in the app is what you will be saying out loud in a moving car, so short and unambiguous beats descriptive. One word plus "door" works. A name that shares its first syllable with a room or a blind will get matched to the wrong thing often enough to be annoying.

Why the Keyfob Still Lives on the Car Keys

The voice chain runs Assistant, Google Home, the Somfy cloud, the hub, then the door. Five links, and four of them are somebody else's servers. Kill the router and that sentence does nothing at all.

The Keygo io remote talks straight to the motor and skips every one of those links. It works with the hub unplugged, the internet down, and the phone dead. Because io-homecontrol is two-way, a press on the keyfob still reports back to the hub, so opening the door from the car does not leave your automations blind. You get the resilience without losing the logging.

Keep one on the keys. A house that can only be opened by a charged phone with signal is not a smart house; it is a single point of failure with an app.

The same argument applies indoors, where the physical control is a wall button rather than a keyfob. Pairing an Izymo transmitter puts an io radio behind an ordinary pushbutton, so the plate people have pressed on the way past for years keeps working whatever the hub is doing.

Why This Is the Category Where You Pay Up

Most of this house is deliberately cheap where cheap works. Unbranded Zigbee controllers behind the light switches, no bridge, no vendor app. I'd make that trade again for lighting without a second thought.

Not here. A gate or a garage door is a couple of hundred kilos of moving metal at chest height, on a path children and cars use every day. That puts it in a different category from a bulb, and it should change what you're willing to spend. Photocells that fail safe, force detection that actually reverses when it meets a shoulder instead of an obstacle, and a motor that behaves identically on the two-thousandth cycle as on the first, those are the things you're buying, and they're exactly the things a cheaper motor quietly economises on.

So yes, Somfy costs more than the generic kit, and I paid it on purpose. Peace of mind is a real feature, even though no spec sheet lists it. The rule I use across the whole build: pay for the category where a failure hurts somebody, save on the category where a failure means walking to a switch.

What I Would Do Differently

Nothing about the hardware. The order, entirely.

If I did this again I would finish the door completely before the TaHoma app was even open: mechanics, photocells, travel limits, force, safety reverse tested, and a full run from the handheld remote. Then pair. Then name. Then expose to voice. Every problem I had came from doing step four before step two, encouraged by an app that was perfectly happy to let me.

The other thing I would change is expectations rather than actions. I assumed the hub would tell me something useful when the door did not respond. It cannot. The hub knows the radio link is up and nothing more, so a silent tile means go and look at the motor. A connected garage has more to it than the door alone, presence detection, EV charging, and climate control are all easier problems than this one was, and worth tackling once the door itself works.