Hello guys,
@Mark520 when you configured your account in the official roborock app you were normally required to enter a region. Do you recall which one? You might check in the roborock app itself under your personal settings. With me it mentions the region as belgium.
@Vinni_Mata can you try with V3.3.1? That should already fix some issues like with @CtlAltDel
Hey @Mark520
I think I am going to try to implement a region override, as your account seems to refer to EU, which might lead to these errors too.
That wonāt be for today though.
Kind regards
Hey @Mark520
To prevent that I couldnāt sleep due to thinking about this, Iāve quickly drafted a new version which allows region selection, v3.3.2 available as test now via Roborock Cloud | Homey
If you use āauto-detectā in the dropdown, I would expect the same behaviour as you have now. I hope that when you select āUnited Statesā it will work better.
Let me know the results!
9ef0b5f6-6dbe-4a8b-9f00-c1f8d90188ed
Ok I tried selecting United States and password and token did not work.
Also tried just token but never received email.
Also tried auto select same result as before.
I also logged out of app and logged in again to insure credentials are correct.
I logged in with username and password not the authentication token in the app.
Just tried again on pc same result. Not sure that this makes any difference but the app says USA not united states. I have also logged into the website directly with my current credentials. https://us.roborock.com/ with no issue.
Could you try all different regions to see if it makes a difference?
same error with all region.
7476ab5e-569e-49ec-a13e-43c62ed13051
Yeah in that case you have to wait typically it unlocks at midnight.
Hmm from your diagnostics report it shows me that no region was selected in all cases. Maybe some bug Iāll check tomorrow.
Hi @KennyMoens . Iām having issues similar to the ones mentioned above me using 3.3.3.
Iāve tried variations of token, password, auto-detect region and United States. Password & Token authentication brings error 2012 and Token Only claims to send an email (token) to my email address but never does (Iāve also checked my Spam folder).
Thanks for being so helpful. I am excited for when this gets fixed.
Hello @Vinni_Mata @Mark520 ,
The pairing logic still had a bug related to the region selection, which led to that it was not picked up correctly. In the repairing logic it was picked up correctly.
Iāve pushed v3.3.4 now to test, this should allow the region override for the pairing logic too.
I really hope it will now work 
Kind regards,
Hey, @KennyMoens
Alright hereās the new breakdown. Updated to 3.3.4 experimental. Picking āRobot Vacuumā (not Zeo Series).
Email address entered.
On Authenticate with Password and Token - Region: Auto Detect āFailed to retrieve the home details: invalid token (code: 2010). No email sent.
On same settings but region entered (United States) we get the same error. No email sent.
Strangely, I did this process earlier and I did receive some confirmation emails with tokens but those did not work. I canāt duplicate these options with token only since now it wonāt even send me the confirmation email. I do have some photos though from when I tried earlier. See attached.
Keep up the great work. I never worked with helping a programmer before and I can tell this is frustrating work!
Hey @Vinni_Mata
Thatās a very good sign! The error you are getting is from later in the process, when Iām trying to retrieve the devices themself.
At that moment we are effectively using another instance of the API already, and I didnāt implement the region overriding there yet.
This should be fixed with v3.3.5 which is available for test now.
Iām quite confident that this will solve it!
PS: the auto-detect will probably never work for your accounts. For some reason the Roborock servers donāt answer the correct information for some accounts. Therefore that the region override should fix it.
7f471223-9daf-4a6b-aae8-ce1927f9d626
Was able to select United States and enter password and then received token .
However once in received an error message.
Also tried token only
0dc9e320-cbde-4105-bc66-f1b8cf465037
Same error as before.
Will try with 3.3.5
