PiotrMachowski / Xiaomi-cloud-tokens-extractor

This tool/script retrieves tokens for all devices connected to Xiaomi cloud and encryption keys for BLE devices.
MIT License
3.23k stars 333 forks source link

stoped working today with viomi.vacuum.v8 #50

Closed radimsejk closed 2 years ago

radimsejk commented 2 years ago

I have installed the Xiaomi Miot Auto to he Home Assistant and it worked with my robot until today. Now is the device unavailable. When I tried the python script for extracting cloud token, it says "unable to get devices". The vacuum is working normaly and I can see it or control it via the Mi Home app normaly.

Tamsy commented 2 years ago

I have installed the Xiaomi Miot Auto to he Home Assistant and it worked with my robot until today. Now is the device unavailable. When I tried the python script for extracting cloud token, it says "unable to get devices". The vacuum is working normaly and I can see it or control it via the Mi Home app normaly.

Did you lately update the Xiaomi Home app to the latest v.7?

I did and since yesterday afternoon (UTC +7) my 2 Roborock s5 max are unable to retrieve their maps anymore with Xiaomi Cloud Vacuum Map Extractor. Tried to recheck the tokens through token_extractor.exe (as admin) but nothing more than:

.....
Server (one of: cn, de, us, ru, tw, sg, in, i2) Leave empty to check all available:
de

Logging in...
Logged in.

Unable to get devices.
Press ENTER to finish

Note that I am using the server for "de"

So I retried leaving "Server" empty to check on all Xiaomi Servers:

......
Server (one of: cn, de, us, ru, tw, sg, in, i2) Leave empty to check all available:

Logging in...
Logged in.

No devices found for server "cn".
Unable to get devices.
No devices found for server "us".
No devices found for server "ru".
No devices found for server "tw".
No devices found for server "sg".
No devices found for server "in".
No devices found for server "i2".

Press ENTER to finish

Maybe the server for "de" is down (or even removed)?

What is strange is that the maps for the vacuums are showing in the Xiaomi Home app (after the maps where gone there too for a couple of hours).

peterhoe commented 2 years ago

Looks like Xiaomi are having some problems with their server / cloud infrastructure

https://www.reddit.com/r/Xiaomi/comments/rsrwtk/eu_servers_31122022_not_working/

Tamsy commented 2 years ago

Looks like Xiaomi are having some problems with their server / cloud infrastructure

Thank you for the info.

What worries me is that I can control both S5 Max through the Mi Home app (maps are showing) but they fail with HA. Lets hope Xiaomi fixes this any time soon.

radimsejk commented 2 years ago

@Tamsy thank you for writing down every detail of this problem. Looks like we both have the same errors. I can too control my vacuum through the Mi Home app but HA cannot connect to it. I hope it is some bad luck new years git commit and it will be fixed soon :)

fritanga commented 2 years ago

Same problem here with rockrobo_vacuum_v1, i'm also 'de' server.

rezmus commented 2 years ago

they forced rc4 on eu cloud, it won't accept plain data anymore.

@PiotrMachowski you should use rc4 by default now, because mi home use rc4 only for over a year so it's just matter of time other clouds will be switched to rc4 only.

https://github.com/al-one/hass-xiaomi-miot/blob/master/custom_components/xiaomi_miot/core/xiaomi_cloud.py

Tamsy commented 2 years ago

@rezmus, thank you for clarifying. So we have to wait for @PiotrMachowski to update Xiaomi-cloud-tokens-extractor and xiaomi_cloud_map_extractor to access xiaomi cloud through rc4 to be able to get it back to work again.

canedje commented 2 years ago

Ahh I do have the same problem. I don't know what rc4 means but I will wait

Tamsy commented 2 years ago

I don't know what rc4 means

RC4 (Rivest Cipher 4): https://en.wikipedia.org/wiki/RC4

JelleMarc commented 2 years ago

Same issue here, following this thread for a fix :) Just want to add that I have a token configured (it was working fine before) but it broke. So even if you can retrieve a token it will most probably not work.

lweberru commented 2 years ago

Same issue here.

lweberru commented 2 years ago

Any alternative manual way to get the token?

18rrs commented 2 years ago

Since 31 dec '20, DE server do now show token. At first the Mi home app was down too but now only the DE server not showing the token. Other region servers are working. HA intergration is not controling the vacuum. Hope for a update soon.

axcs commented 2 years ago

Same issue here. there is no way to add rc4?

PricelessToolkit commented 2 years ago

Same issue here.

PiotrMachowski commented 2 years ago

A fix is almost ready, it just needs some polishing

r3pek commented 2 years ago

A fix is almost ready, it just needs some polishing

damn.... I was working on it when you posted the message :( oh well.... feel free to close it if you want :P

PiotrMachowski commented 2 years ago

@r3pek I got it working ~10h ago, but it was already 7AM and I decided that I finally need to get some sleep ;)

r3pek commented 2 years ago

@r3pek I got it working ~10h ago, but it was already 7AM and I decided that I finally need to get some sleep ;)

I just figured you were busy or something so I hacked a solution really fast :P

sagitt commented 2 years ago

same here, no calibraiton points

calibration_points: null

PiotrMachowski commented 2 years ago

It should work now

r3pek commented 2 years ago

Confirmed! Will you update your other repos today?

PiotrMachowski commented 2 years ago

I think so :)

wind1980 commented 2 years ago

Only for help I have the same problem to retrieving the map one of my two xiaomi robot (registred in DE server) in HA and also trying to verify the token (with token extractor app) i have this error whan i try to connect to DE server:

Logging in... Logged in.

Unable to get devices.

Thanks for your work!

r3pek commented 2 years ago

@wind1980 update to the latest version. @PiotrMachowski just updated the repo to make it work

wind1980 commented 2 years ago

Which version? I found the 2.1.1 in HACS but with this one i have always the problem

PiotrMachowski commented 2 years ago

@wind1980 this is a repo of Tokens Extractor, Map Extractor has not been updated yet

r3pek commented 2 years ago

this is the token extractor repo mate ;) this one isn't on HACS... You're probably talking about https://github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor which he will update next (I think)

wind1980 commented 2 years ago

Sorry, i confused the token extractor app with the Xiaomi cloud extractor integration for HA!

Now the app extractor works with DE server again but i have the same token before for my S5 Max so i have the same problem in HA integration yet. From the last HA update i have the message " failed to retrieve the model" in camera map preview. Instead for my other Xiaomi vacuum ( model 1S) all continue to work fine like ever

wind1980 commented 2 years ago

@wind1980 this is a repo of Tokens Extractor, Map Extractor has not been updated yet

Right, I noticed my mistake..sorry!

I'll wait for the update of xiaomi maps extractor integration HA.

Thanks for your great work again!

pipip commented 2 years ago

Thank you so much for the update. The docker version is missing gcc I think :) `Running setup.py install for pycryptodome: finished with status 'error'

copying lib/Crypto/Math/_IntegerGMP.pyi -> build/lib.linux-x86_64-3.10/Crypto/Math running build_ext building 'Crypto.Hash._MD2' extension creating build/temp.linux-x86_64-3.10 creating build/temp.linux-x86_64-3.10/src gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -DPYCRYPTO_LITTLE_ENDIAN -DSYS_BITS=64 -DLTC_NO_ASM -Isrc/ -I/usr/local/include/python3.10 -c src/MD2.c -o build/temp.linux-x86_64-3.10/src/MD2.o error: command 'gcc' failed: No such file or directory`

PiotrMachowski commented 2 years ago

@pipip whoops, I haven't tested it with docker. I will fix it soon. Thank you!

pipip commented 2 years ago

@pipip whoops, I haven't tested it with docker. I will fix it soon. Thank you!

Thanks for the fast reply. No worries, the fix itself works great. Thanks

To fix the Dockerfile I just added: RUN apk add build-base before RUN pip3...

PiotrMachowski commented 2 years ago

@pipip ok, I have fixed it + finally added GitHub action for release 👍

N3rdix commented 2 years ago

I can confirm it’s working as expected, thanks for the quick resolution

Tamsy commented 2 years ago

Thank you for the quick fix, Piotr

All back to normal now and getting the tokens of my vacuums is working again like before. Excellent work!

digitalit commented 2 years ago

Working again. Thank you Piotr