-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't find token #12
Comments
Same thing with here. The app won't get any tokens with the latest version of MiHome 5.1.1 |
Worse... I tried downgrading to earlier version and I still can't get the
app to find the token. (The DB has an empty token column)
…On Thu, Feb 1, 2018, 07:32 Lars Nørgaard ***@***.***> wrote:
Same thing with here. The app won't get any tokens with the latest version
of MiHome 5.1.1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEgzVyqWvQm4jHyawEe6X1RMfTkmevKDks5tQLHVgaJpZM4RzqNF>
.
|
Seems like they pull the token from the servers now: |
Downgrade the app to version 5.0.19 and you'll be able to extract the token again. |
Ok will try thanks. Although I am pretty sure I did that last night and was
surprised not too have to pair my device (vacuum) again. Once I logged in,
it just showed up... And no token...
…On Thu, Feb 1, 2018, 08:17 Lars Nørgaard ***@***.***> wrote:
Downgrade the app to version 5.0.19 and you'll be able to extract the
token again.
I used this:
https://www.apkmirror.com/apk/xiaomi-inc/mihome/mihome-5-0-19-release/mihome-5-0-19-android-apk-download/download/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEgzV_9cfi_UpnSnmKnEcZjuH-MvWv7lks5tQLwugaJpZM4RzqNF>
.
|
confirm, now the only option is a rooted phone and a sniffer inside the app. YAY! |
same here, i tried on several device, with both Mi Home 5.0.19 and the newer but always the program didn't extrac any token |
same problem. thanks! |
@mscalone No idea ATM. |
oh god no. i just got my vacuum and was trying to get it to work in HASS... |
Since it's an update and what sounds like a big change from Xiaomi in the Mi Home app, I would assume it'll take the devs some time to figure out a new way to get the token. In the meantime, you can use your vacuum with the Mi Home app I would think. |
Yeah, the bad news is the app only seems to pair if you keep the locale on Mainland Chinese, and i'm guessing not a lot of us can read mandarin. The good news is i was able to extract my token with the apk @LarsNorgaard linked, but i have a spotty internet connection right now so its kinda harder :| |
You can connect to Mainland China and the app will be 95% in English still |
ok i got my token and i can ping\control from app just fine, but for some reason python-miio isn't able to discover the vacuum:
EDIT: my bad: was working with 0.3.2. EDIT2: make sure you are running HA 0.63.0, or else `python-miio is installed as 0.3.4 as a dependency and this happens:
EDIT3:
|
P.S. |
clearing data and installing |
My vacuum wants to update again. Im scare. |
Did this for a friend recently. No idea sniffing the traffic between the device - servers due to some of the certificates are pinned, this can be circumvented but you'll see that all traffic is encrypted inside the TLS session. Now, what made me find the token was by using a rooted android device, installing latest xiaomi app, and found a folder called rc4_cache containing clear text decrypted traffic including the token. Theres ways to get privileges within the app as well, without using a rooted device and that is by using a tool called 'objection'. This tool patches the apk, adding some code which spawns a shell within the app - thus giving you read/write on the entire installation directory |
Not sure if this is due to a recent update but my Xiaomi Mi Vacuum Cleaner has stoped being seen by my Home Assistant.
I tried to get the token again using MiToolkit but while the process goes through fine, I am not getting any token.
Note: I manually peeked inside miio2.db and I could see that the token column was indeed empty.
Am I missing something?
The text was updated successfully, but these errors were encountered: