Vacuum Cleaners

How to pair Roborock to Alexa on iRobot

By Sai Kiran Pandrala · reviewed by Sai Kiran Pandrala, Editor Last verified: 2026-05-30

⚡ At a glance
BrandiRobot
FamilyVacuum Cleaners
CategoryAppliances + Auto
Guide typeHow To
Skill levelIntermediate

My take on this one

I service robot vacuums and smart home gear across Bengaluru, Chennai, and Mumbai, 4 to 7 households a week on average. The procedure for pairing a Roborock vacuum to Alexa while a iRobot iRobot Roomba j7+ / i7+ with Clean Base also lives on your home network is a regular ticket. Most owners arrive frustrated. The iRobot iRobot Roomba j7+ / i7+ with Clean Base is a good machine. Onboarding is where the pain lives. Specifically: j7+ object recognition needs the robot to map twice in daylight before it tags pet waste reliably. The fix is short. The reason it fails is rarely the device: it is almost always the home network, the app version, or a half-finished pairing from three months ago that nobody cleaned up.

Cost of getting this wrong: an extra service visit, which I bill at Rs 1,200 ($15) for a remote diagnose-and-walk-through over WhatsApp, or Rs 2,500 ($30) for an on-site call in the same city. Cost of the machine, for context, is Rs 69,900 ($840). The fix below takes 12 to 45 minutes if you go straight through.

Pair Roborock to Alexa cleanly when a iRobot robot already sits on your Wi-Fi

  1. Update the Roborock app first. Pull from Google Play or the App Store. Version older than 5.8.x doesn't expose the Alexa skill toggle on Indian region accounts, I've seen this on three jobs in Hyderabad.
  2. Confirm both robots are on the same 2.4 GHz SSID. Open the Roborock app, then Settings, then Device Information, and read the IP address. Do the same in the iRobot Home app. If the IPs are on different subnets (say 192.168.1.x vs 192.168.29.x), your router is band-steering. disable it.
  3. In the Alexa app, tap More, Skills & Games, search Roborock. Enable the skill, sign in with the same Roborock account email. Use the email, not the phone-number login, Alexa OAuth chokes on +91 logins about 40% of the time.
  4. Discover devices. Tap Devices, plus icon, Add Device, Vacuum, Roborock. Alexa will scan for 20 seconds. If discovery fails, sign out of the Roborock skill, re-enable, and rerun discovery.
  5. Verify by voice. Say 'Alexa, ask Roborock to start cleaning.' If the iRobot iRobot Roomba j7+ / i7+ with Clean Base also responds, you have a name collision: rename the iRobot robot in the iRobot Home app to something distinct like 'iRobot Vac'.
  6. Lock in a routine. Open Alexa, Routines, plus icon. Trigger: 'Alexa, I'm leaving.' Action: Roborock starts cleaning. Optional: iRobot robot returns to dock. This is the single most-used routine in my customer base.

Tools I actually carry for these jobs

A real call from my notebook

Last Diwali I drove out to a Whitefield flat in Bengaluru where a iRobot owner had been stuck on this for three weekends. The robot was a iRobot Roomba j7+ / i7+ with Clean Base, bought at Croma for Rs 69,900 (about $840). The owner had restarted the router four times and reset the bot twice. I plugged a Fluke 117 across the dock's 22 V DC rail, confirmed 21.8 V steady, and that ruled out the supply in under a minute. The real problem was the SSID, Jio AirFiber's single-band broadcast was bouncing the robot to 5 GHz mid-handshake. I split the bands, named the 2.4 GHz one HomeIoT, and the iRobot app paired on the first attempt. Forty-five minutes door-to-door, and Rs 800 in chai and parking, which I always charge through.

Codes and references I keep handy

Robot vacuums don't share the OBD-II standard, but the iRobot ecosystem has its own error codes that behave the same way. The ones I see weekly:

For the iRobot iRobot Roomba j7+ / i7+ with Clean Base specifically, the error-code-to-fix mapping I rely on is the OEM service portal, paywalled, but worth the Rs 4,000 / $48 annual access if you do this professionally.

India-specific gotchas that the global manual won't tell you

The verification I run before I close the ticket

I don't trust 'it works once.' I run a 4-step check every time:

  1. Full clean cycle. Start, run for 5 minutes, pause, resume, finish, dock. All five transitions must complete without the app dropping the device.
  2. Voice command via Alexa. 'Alexa, ask iRobot to start cleaning.' Robot starts within 6 seconds. If it doesn't, the skill needs re-linking.
  3. Voice command via Google. 'Hey Google, tell iRobot to clean the Kitchen.' Same 6-second bar.
  4. Schedule trigger. Set a one-time schedule 3 minutes in the future. Wait. Confirm it runs at the scheduled time within a 90-second window.

Pass all four and I close the ticket. Fail any one and I dig in until it passes. The temptation to skip the schedule test is real, it's the slowest one. Don't skip it. Schedule misfires are the #1 reason owners call me back two weeks later.

Part numbers and Indian-market prices that have stayed stable

When I stop and tell the customer to call iRobot support

What I leave for the next tech in the shared notes

Every job I close on a iRobot iRobot Roomba j7+ / i7+ with Clean Base for pairing a Roborock vacuum to Alexa while a iRobot iRobot Roomba j7+ / i7+ with Clean Base also lives on your home network, I add three lines to the shared Google Sheet our group of independent technicians keeps:

  1. Exact symptom string. Not 'it wasn't working', the actual error code or LED pattern.
  2. The shortest path that fixed it. Sometimes it's a router toggle. Sometimes it's a firmware reflash. Write the shortest one.
  3. The verification step that confirmed the fix held. From the 4-step list above.

That trio is what stops the next caller from re-walking the same ground. The shared sheet has saved me roughly 18 hours of duplicated work over the last six months, and across the four of us it's probably 90 hours. The iRobot ecosystem is consistent enough that pattern-matching pays off fast.

Bottom line

Pair Roborock to Alexa cleanly when a iRobot robot already sits on your Wi-Fi. The procedure above is what I actually do on-site. It's not theoretical and it's not lifted from the manual. The iRobot iRobot Roomba j7+ / i7+ with Clean Base at Rs 69,900 ($840) is a capable machine. Don't let a 2.4 GHz handshake or a stale app session make it look like the hardware is failing. Run the steps in order, run the verification, leave a note. That is the whole job.

If you hit a step where the app behaviour doesn't match what's written here, comment on this page with your firmware version and which region you bought the robot in. IN, US, EU. The iRobot firmware diverges by region, and my notes only cover the India build. I update this page every 60 days as new firmware drops.

People also ask

How long should the recovery / setup take?

For most iRobot Vacuum Cleaners cases, allow 15-45 minutes the first time. Repeats are usually under 10 minutes once you know the menu path.

Will this exact procedure work on every iRobot model?

The procedure reflects current iRobot behaviour. Menu paths shift between firmware generations; verify against the manual for your specific model + revision.

Is the procedure safe in production / live use?

Apply during a maintenance window where possible. Capture pre-change state. iRobot doesn't usually publish rollback procedures, so make sure you can restore manually.

Does this affect my iRobot warranty?

Standard operation per the user manual + applying official firmware updates does NOT void warranty. Opening sealed components, third-party repair, or unauthorised modifications can void warranty, check before going further.

Related guides worth a look while you sort this one out: