"miiocli cloud" Login failed with verified correct password

[schweini]

Using 100% correct credentials (copied and pasted), I still get login failed when running miiocli cloud.

Version: 0.5.12 installed through pip on Ubuntu running on WSL.

AFAIK, I don't have 2FA enabled, and Ihave removed Google as a 'third part account' in the Xiaomi account.

The same is happening with "Mi home Kit" ( ApplY3D/mi-home-toolkit#11 )

[llewelynb]

I'm having the same issue... Please help!

[juancabe]

Same

[Shaw9]

Same

[d1b]

It seems like the second stage of the login is not working -

{'qs': '%3Fsid%3Dxiaomiio%26_json%3Dtrue', 'code': 87001, 'description': '验证码输入错误', 'securityStatus': 0, '_sign': '<sign_here>', 'sid': 'xiaomiio', 'result': 'error', 'captchaUrl': '/pass/getCode?icodeType=login&<stuff>', 'callback': 'https://sts.api.io.mi.com/sts', 'location': '', 'pwd': 0, 'child': 0, 'desc': '验证码输入错误'}

the description and field fields both translate to The verification code was entered incorrectly.

[killembien]

Same issue here !
Login suceeded 3 day ago.
I try today and the same error message.
Login on xiaomi.com : OK

[rilence]

I've validated this same behavior through 3 different HA integrations for Xiaomi devices, which use this library.

[LarrysGIT]

use Xiaomi-cloud-tokens-extractor to get the token, xiaomi added captcha not long ago, micloud doesn't support it.

[rytilahti]

This library does use the micloud library in the background for cloud communications. If someone knows another library that supports the modern login workflow, we could swap this project to use the new library. Alternatively, it would be great if micloud could be improved to fix the situation :-)

[BlueRoar]

This repo works to grab tokens:

https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor

I was able to get it to work by integrating the QR code login, just having it open the link for me, saving the session to get all the goodies and then doing local control.

[Tzxhy]

use Xiaomi-cloud-tokens-extractor to get the token, xiaomi added captcha not long ago, micloud doesn't support it.

Really helps.

[Wirsing84]

anyone ever figure out how to use miiocli cloud again? I still cannot log in.

...in _login_step2 raise MiCloudAccessDenied("Access denied. Did you set the correct api key and/or username?")

Logging in to https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor works fine but it only gives me tokens. I need to log into the cli to set a key to access dev mode for home assistant.

Please help, anyone! Thank you!

[alexissan]

I hit this too and had a go at it — PR #2089.

Short version: Xiaomi's captcha only affects the password flow. The QR code login is unaffected, so #2089 adds a small built-in backend for it rather than a new dependency:

$ miiocli cloud --qr list --locale de
Scan this QR code with the Xiaomi Home app: /tmp/miio-cloud-login-qr.png
== Robot Vacuum (Device online) ==
	Model: xiaomi.vacuum.b108gl
	Token: ...

@rytilahti, on your question about swapping libraries — I went the other way and implemented just the two methods CloudInterface actually used from micloud (login() and get_devices(country=...)), hitting the same /home/device_list endpoint so the records are identical and CloudDeviceInfo parses them unchanged. Verified against a live account rather than assumed. Password login is untouched and QR is opt-in, so nothing changes for anyone it still works for.

No new install footprint: requests was already coming in via micloud, and RC4 is ~15 lines inline because cryptography moved ARC4 to hazmat.decrepit in 43.0 and there's no import path valid across all of cryptography>=35. That also means the micloud dependency could be dropped later without taking this path with it.

For anyone blocked right now and not wanting to wait on review: @LarrysGIT and @BlueRoar are right that Xiaomi-cloud-tokens-extractor works today. The PR follows its signing scheme, credited in the module.

Entirely understand if you'd rather shape it differently — happy to rework it, or for it to be closed if you'd prefer to fix micloud upstream instead.