Roborock S7 Max Ultra Token Issue

[Vacxe]

** Describe issue **
Behavior:

Trying to add new Roborock S7 Max Ultra

Vac have static IP

Due token request having this issue:

** Hardware / Software **
  - Node Red in Docker on Synology

[jerome83136]

Hello,
Also have a similar need but with the Xiaomi Roborock S7 Pro Ultra.
As this is not the same model than the one of the author; do I have to open a dedicated issue ?

I will test this node on it and keep you up to date anyway; hoping it could help :)

Best regards and thanks for this node !

[andreypopov]

Try to use other tool for extracting token

[jerome83136]

Hi,
I tried with this other tool: https://github.com/PiotrMachowski/Xiaomi-cloud-tokens-extractor/releases/latest/download/token_extractor.exe

It shows my Roborock S5 token with no problem.

But for the Roborock S7 Pro Ultra (my 2nd robot) it can't retrieve any token.

The tool checks on the following servers: cn, de, us, ru, tw, sg, in, i2
Maybe the Roborock S7 Pro Ultra registers on another (unknown) server ? Or maybe is it because for this model; I had to use the "Roborock" APP (rather than the legacy "Xiaomi Home" APP) ?
I can see the robot making DNS requests to this server: awsde0.fds.api.xiaomi.com

And I can't sniff the traffic between the robot and this server because it's encrypted.
I could try sniffing between my mobile phone and the servers; but it seems I cannot because I need a rooted phone for PCAP

Any suggestions about tests I could try to help everyone ?

Thank you for your help

Regards

[jerome83136]

I just tried something that seems to work:

• reset my S7 Pro Ultra
• connected it by using the legacy "Xiaomi Home" APP
• put my phone in plane mode to prevent the Xiaomi Home APP from disturbing the process (not sure if its usefull thoughts)

Then I was able to retrieve the token from your NodeRed node.
And now it works. Commands and events are OK

I've seen new DNS requests from the robot: de.ot.io.mi.com

I also checked with the token_extractor.exe tool and now I can see the robot listed on the "de" server (it was not the case on my previous try)

So I think the robot "registration" server has something to do with this token retireval problem.

Now time for reverse-engineering the new commands and associated params to send for this specific robot (dock auto-emptying, etc...)

Hope it will help.

Best regards