Roborock re-auth loop: RoborockException: parameter error - response code: 1002 on Core 2026.3.0 (Python 3.14)

[widowsson7]

The problem

After updating to Core 2026.3.0, the Roborock integration is stuck in a persistent re-authentication loop. While the verification code is received and accepted by the UI, the backend fails to finalize the token exchange, resulting in a "parameter error - response code: 1002".
Environment
Home Assistant Core: 2026.3.0
Installation Type: Home Assistant OS 17.1
Python Version: 3.14 (bundled with 2026.3.x)
Integration: Roborock (Core)
Steps to Reproduce
Trigger the "Re-authenticate" repair flow.
Submit the email and enter the received verification code.
The UI displays a generic error or the "Authentication expired" notification returns within minutes.
Logs show the 1002 exception immediately following the code entry.
Logs:

2026-03-05 09:01:XX ERROR (MainThread) [homeassistant.components.roborock.config_flow] Unexpected exception
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/roborock/config_flow.py", line 114, in async_step_code
user_data = await self._client.code_login_v4(code)
File "/usr/local/lib/python3.14/site-packages/roborock/web_api.py", line 348, in code_login_v4
raise RoborockException(f"{login_response.get('msg')} - response code: {response_code}")
roborock.exceptions.RoborockException: parameter error - response code: 1002

(Note: Log excerpt confirms the failure occurs during the code_login_v4 function call.)
Additional Information
The Roborock mobile app functions normally; this appears to be an API/handshake issue specific to the integration on Python 3.14.
Similar issues have been reported in previous version jumps where the underlying roborock library required updates for new API requirements.
I have verified that there are no pending EULAs or User Agreements to sign in the mobile app.

What version of Home Assistant Core has the issue?

2026.3.0

What was the last working version of Home Assistant Core?

2026.2.3

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Roborock

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

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, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@widowsson7 Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20roborock%22%20
_{^{(message by IssueContext)}}

---

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

[AlbibiG]

I’m having the same issue. It started occurring in 2026.2.3 (about a week ago). Currently on 2026.3.0 and still happening. Roborock is on latest version. API lasts at most 12 hours before needing reauth. I posted on Reddit and multiple people have this issue.

[widowsson7]

I should mention that it was also happening on 2026.2.3, and for about the past week, just as reported by AlbibiG. I think my issue is an exact mirror of his.

[Lash-L]

Hi @AlbibiG @widowsson7 - do you mind sharing roughly where you are located? In the US or not in the US should be sufficient.

[AlbibiG]

I’m northeast US based

[Lash-L]

I may have found a partial cause, but it does not explain the symptoms you described @AlbibiG. @widowsson7 were you have the same thing? You could successfully reauth - but then it would make you reauth again in 12 hours? Or were you having an issue where you cannot reauth at all?

@AlbibiG - can you please share logs. I'm not sure what would be happening to make you have to reauth at that high of a frequency.

[yieldhog]

I am also having the same issue -- located in the United States. The integration is asking me to re-authenticate every 7-8 hours.

[widowsson7]

I may have found a partial cause, but it does not explain the symptoms you described @AlbibiG. @widowsson7 were you have the same thing? You could successfully reauth - but then it would make you reauth again in 12 hours? Or were you having an issue where you cannot reauth at all?

@AlbibiG - can you please share logs. I'm not sure what would be happening to make you have to reauth at that high of a frequency.

I may have found a partial cause, but it does not explain the symptoms you described @AlbibiG. @widowsson7 were you have the same thing? You could successfully reauth - but then it would make you reauth again in 12 hours? Or were you having an issue where you cannot reauth at all?

@AlbibiG - can you please share logs. I'm not sure what would be happening to make you have to reauth at that high of a frequency.

[widowsson7]

Hi. I'm in the US, Arizona. While I haven't exactly noticed the number of hours between requirements to re-authenticate, my sense is that it's the same as what's being reported by everyone else. I'll reauthorize now and see when it comes up again.

[Ali229]

Same issue and very annoying keeps asking reauthenticate.