MiHome 2FA Verification Issue

[MarioKuester]

I tried both versions but both say "Verification failed" so the issue seems to persist.

Fixed.

https://github.com/Tasshack/dreame-vacuum/releases/tag/v1.0.10
https://github.com/Tasshack/dreame-vacuum/releases/tag/v2.0.0b24

Originally posted by @Tasshack in #1647

[James-Lee-007]

Same here. Also the authentication message seems a little strange:

[akcasoy]

same here.

[Felixstro-dev]

I have the same Problem

[Tasshack]

Looks like I have made a backport error because Beta v2.0.0b24 works fine but v1.0.10 not. I will release a new version for stable but you can swich to the Beta if you don't want to wait.

[MarioKuester]

Looks like I have made a backport error because Beta v2.0.0b24 works fine but v1.0.10 not. I will release a new version for stable but you can swich to the Beta if you don't want to wait.

The Beta didn t work for me either.

[Tasshack]

Looks like I have made a backport error because Beta v2.0.0b24 works fine but v1.0.10 not. I will release a new version for stable but you can swich to the Beta if you don't want to wait.

The Beta didn t work for me either.

I need little more information than that...

[divisioneIT]

Problem

I am trying to configure Dreame Vacuum v1.0.10 with a Xiaomi Home account for a Xiaomi Robot Vacuum X20+.

The 2FA/login flow still fails for me, or the integration does not complete setup after verification.

Environment

• Integration: Dreame Vacuum
• Integration version: v1.0.10
• Home Assistant version: 2026.6.0
• Robot model: xiaomi.vacuum.c102gl
• Robot name: Xiaomi Robot Vacuum X20+
• Firmware: 4.5.6_1087
• Region/server: de
• Configuration type: Xiaomi Home account, with map support / prefer cloud

Additional context

The same Xiaomi account works correctly in the Xiaomi Home app.
The robot is visible in Xiaomi Home.
The Xiaomi Home integration in Home Assistant detects the device as xiaomi.vacuum.c102gl.

[R7tur]

v2.0.0b24
Logger: custom_components.dreame_vacuum.dreame.protocol
Source: custom_components/dreame_vacuum/dreame/protocol.py:1520
Integration: Dream Vacuum (documentation, issues)
First recorded: 06:31:39 (4 instances)
Last recorded: 08:10:03

Execute api call failed with response: {"code":0,"message":"SERVICETOKEN_EXPIRED"}
This error occurred in the custom integration.

Logger: custom_components.dreame_vacuum
Source: config_entries.py:822
Integration: Dreame Vacuum (documentation, issues)
First recorded: 08:10:04 (1 instance)
Last recorded: 08:10:04

Config entry 'Petrovich' for dreame_vacuum integration could not authenticate: Authentication Failed!

[interkom]

confirm
v2.0.0b24 does not work 2FA

[Tasshack]

"Not working" is not an actionable information for me...
I cannot reproduce any issue on v2.0.0b24.

[seybojanokorn]

Same here.

[hamelinboyerj]

hello,

Using the version 2.0.0b24, the above issue was solved on my side.

The mistake was using a xiaomi cloud account instead of the dreame account. The above users probably have the same issue, but didn't try to use the 2.0.0b24 version.

Example of seybojanokorn > 1.0.10.

Didn't have any 2FA authentification on the DreameAccount

[divisioneIT]

Hi,

I tested both releases, Official and Beta. I have a Xiaomi account with two-factor authentication enabled, which is the default setting.

With xiaomi_token_extractor, the same procedure works correctly: it creates a valid token after I enter my credentials and verify via email.

Based on the logs, this application should also be doing the same. The procedure works correctly up to the verification step. However, it seems there is no confirmation that the received code was entered correctly.

[Tasshack]

Hi,

I tested both releases, Official and Beta. I have a Xiaomi account with two-factor authentication enabled, which is the default setting.

With xiaomi_token_extractor, the same procedure works correctly: it creates a valid token after I enter my credentials and verify via email.

Based on the logs, this application should also be doing the same. The procedure works correctly up to the verification step. However, it seems there is no confirmation that the received code was entered correctly.

There must be some errors or warnings in logs.