Roborock integration uses wrong account region

[hudochenkov]

The problem

Roborock integration assumes account region to be US, and fails to fetch the authentication code.

My account is in The Netherlands region. I've learned about importance of regions from Roborock support. Depending on the region you select in Roborock app on the login screen (top right corner) different Roborock account is used, even with the same email address.

In the provided logs you see user account is in deletion error is because I didn't know about regions, so I accidentally created an account in USA region. Which I have now deleted and got back to my old Netherlands account.

The important part is that US region is assumed by integration, which is not correct for my account.

We need to be able to select account region when adding Roborock integration.

What version of Home Assistant Core has the issue?

core-2025.12.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roborock

Link to integration documentation on our website

https://www.home-assistant.io/integrations/roborock

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

DEBUG (MainThread) [homeassistant.components.roborock.config_flow] Requesting code for Roborock account
DEBUG (MainThread) [roborock.web_api] Country determined to be US and code is 1
INFO (MainThread) [roborock.web_api] Request code failed for REDACTED with the following context: {'msg': 'user account is in deletion', 'data': None, 'code': 3030}

Additional information

No response

[home-assistant]

Hey there @Lash-L, @allenporter, mind taking a look at this issue as it has been labeled with an integration (roborock) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of roborock can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign roborock Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

roborock documentation
roborock source
_{^{(message by IssueLinks)}}

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[Lash-L]

We currently cycle through all the regions to dynamically find the right one, but because you made one in the us, it tries that first and thinks it is successful. I'll put some thought into this. But as a temporary solution, you can make a new account(under a different email) in your region, share your vacuums with the new account and use that account for home assistant as it will only exist in one region

[hudochenkov]

Thank you for answering so fast!

We currently cycle through all the regions to dynamically find the right one

I think it's a nice solution! The best interface is no interface :) I think I just hit an edge-case, because Roborock app logged me out and switched region, and I wasn't aware about regions and though Roborock deleted my account 🤦 :)

But as a temporary solution, you can make a new account(under a different email) in your region, share your vacuums with the new account and use that account for home assistant as it will only exist in one region

Interesting workaround! I'm going to try it.

[hudochenkov]

But as a temporary solution, you can make a new account(under a different email) in your region, share your vacuums with the new account and use that account for home assistant as it will only exist in one region

Workaround worked! I think I could try in 15 days (time to delete an account) again with my main account.

[bgoncal]

The workaround worked for me as well ✅

Perhaps a region picker during setup would be a cleaner/future proof solution?

[panther7]

Debug log:

2025-12-29 14:44:12.791 DEBUG (MainThread) [homeassistant.components.roborock.config_flow] Requesting code for Roborock account
2025-12-29 14:44:13.273 DEBUG (MainThread) [roborock.web_api] Country determined to be PH and code is 63
2025-12-29 14:44:31.878 DEBUG (MainThread) [homeassistant.components.roborock.config_flow] Logging into Roborock account using email provided code

Region in app:

[JoernBerkefeld]

I was hitting a very similar road block due to the app auto-selecting the region based on current location. I was traveling and without realizing, created a new account for the Philippines instead of logging into my account for Germany.

When I came back home, homeassistant could authenticate with roborock any more.

I the proceeded to delete the PH account but afterwards also just saw the "deleted" error in the logs.

The fact that you can have multiple accounts with the same email address is problematic to say the least... good job, roborock.

Solution option:

how about you provide a new region drop down that has "auto" as default value, which would continue to cycle through regions, but for those users that have issues with it, provide the manual selection option.

Thank you for all the good work here 😀

[itradesize]

Something happened to the integration.
Wrong account: Please authenticate with the right account

Always says that after typing the verification code.
I have an EU account in the Roborock app.

Is there any solution for that bug?
It worked perfectly for months before... This issue came from nowhere.

[mertvecoff]

I have the same issue. By mistake, I created an account for USA. My Roborock s8 pro ultra is linked to European account. So It was an error: no device was found. So I deleted an USA account, but now I still can’t add my European account to Roborock integration.

« user account is in deletion - response code: 3030»

[soberz-fld]

Same issue here. Strangely enough, the integration went down at exactly 3 a.m. on 1 January 2026. My Home Assistant runs in Germany, and the Roborock account has a .de email address.
Still the following error (translated): Setup error, retrying: None of the devices could be set up successfully
I already tried re-adding my account. The roborock itself is of course online. The proprietary app still works.

[Ongy]

@Lash-L can you point me at where that happens? I wanted to try a variant that continues iteration with more error types and lazily reports the most interesting one if all regions fail.

But looking at the code, the main entry point to configuration I see is code_login_v4(code) and no other login in the component.

So digging into the library, this just drops to legacy login which I don't see a loop in.

or does the old flow do the iteration internally?

If we can't fix it more automatically, I think it'd be ok to add a region dropdown to the login flow with

* Auto
* EU
* US
* ??? (China? I know there's a third, I don't remember which)

defaulting to Auto. Which should allow the default to work for most, but gives a way out for those of us that have a broken account in the US region.