You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the idea or improvement
Xiaomi is seemingly ending support for newer non-Xiaomi Vacuums in their app. This means that the "Gen 2" version of my Dreame L10s Pro Robot Vacuum (dreame.vacuum.r2364a) is only supported in the Dreame Home app and not able to be added in the Xiaomi Home app.
Describe the solution you'd like
Possibility to sign in with a Dreame Home account to support newer Dreame Robot Vacuum models which are compatible with the Xiaomi Home app.
Additional context Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered:
Hi, I unfortunately do not have a dreame device and never created an account so I am not sure if and how close the protocol is to the xiaomi one. Someone with experience in that would need to provide some support here...
I am not sure if and how close the protocol is to the xiaomi one.
The Xiaomi/Dreame/Roborock mobile apps are all cut from the same cloth to my knowledge. I would be surprised if the Dreame protocols/api are not identical to Xiaomi.
I will check it out. I am sure there must be some differences, because if the protocol and APIs would be identical then it should work with the existing implementation.
Describe the idea or improvement
Xiaomi is seemingly ending support for newer non-Xiaomi Vacuums in their app. This means that the "Gen 2" version of my Dreame L10s Pro Robot Vacuum (dreame.vacuum.r2364a) is only supported in the Dreame Home app and not able to be added in the Xiaomi Home app.
Describe the solution you'd like
Possibility to sign in with a Dreame Home account to support newer Dreame Robot Vacuum models which are compatible with the Xiaomi Home app.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: