roborock-tuya-token
roborock-tuya-token copied to clipboard
The sniffer finds nothing
I've done all the required steps 1 to 4 then executed the sniffer command on 5. then launching the app on my phone, login (with email), entering the robot, playing with it..
but the sniffer remains empty
yarden@Yardens-Air platform-tools % ./adb devices
List of devices attached
RF8N81ENT3X device
yarden@Yardens-Air platform-tools % ./adb logcat -s "ROBOROCK-name", "ROBOROCK-devId", "ROBOROCK-localKey"
--------- beginning of crash
--------- beginning of system
--------- beginning of main
how to fix it / debug it?
My devices are:
- Macbook (M1 chip)
- Galaxy Note 20 (android 11)
- Roborock S6 MaxV
I tried it several times (clearing data so the login will be cleared), with both versions of apps (the older one doesn't show my S6 maxV on the app, perhaps its too old?) also tried both USB debugging as well as wireless debugging
Same stuff.
Windows 10 Poco F3 (android 11) Roborock S5 MAX
Looks like the app changed the model of exchanging the token. The file which this sniffer was designed to look at is empty (or hashed with some sort of mechanism). I'm afraid there is no hope. I've ended up even striping the original apk of the roborock app hoping to find some sort of hints when debug mode enabled via adb however no luck :(
@redphx : Same problem:
Bluestacks 5.5.10.1001 with OnePlus5 roborock_2.3.32_token.apk Roborock S6 MaxV (Firmware: 02.62.28)
Has anybody found a new solution for getting the token?
Same here. Empty log.
Bluestacks 5.5.10.1001 with OnePlus5 roborock_2.3.32_token.apk Roborock S6 MaxV (Firmware: 02.62.28)
` ➜ ~ adb logcat -s "ROBOROCK-name", "ROBOROCK-devId", "ROBOROCK-localKey" --------- beginning of system --------- beginning of main --------- beginning of crash
`
Same here,empty log.
Anyone had any luch finding a new way to extract the token with the roborock app? I really don't want to switch to the xiamo home app :/
You can pull the token directly from the app cache files using zcat. Instructions here: https://community.home-assistant.io/t/custom-component-roborock-communication/229032/142
Sam here, but I see this in the log, is that the ID we need?
12-21 11:44:44.372 18953 18953 I roborock-MqttMessageDispatcher: ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────── 12-21 11:44:44.372 18953 18953 I roborock-MqttMessageDispatcher: │ topic(102) rr/m/o/4rh2e5vzpXDqN4naUm4sGw/37c1d490/20VSqqbG3uDD6e9TNWAX7v 12-21 11:44:44.372 18953 18953 I roborock-MqttMessageDispatcher: └──────────────────────────────────────────────────────────────────────────────────────────────────────────────── 12-21 11:44:44.377 18953 19143 I roborock-RR: ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────── 12-21 11:44:44.377 18953 19143 I roborock-RR: │ {log_type=dp_update_recv, duid=20VSqqbG3uDD6e9TNWAX7v, is_cloud=true, command={"122":79}} 12-21 11:44:44.378 18953 19143 I roborock-RR: └────────────────────────────────────────────────────────────────────────────────────────────────────────────────