New Device Model Xiaomi Robot Vacuum X10 (dreame.vacuum.r2209)
Closed this issue · 11 comments
Supply the device details
- Name: Xiaomi Robot Vacuum X10
- Model ID: dreame.vacuum.r2209
- MIoT spec: https://home.miot-spec.com/s/dreame.vacuum.r2209
Current support
The token can be extract but the device (via the windows app by https://github.com/Maxmudjon).
The problem is that with the token and ip adresse that the Xiaomi Robot Vacuum X10 can not add to the homey pro system.
I use the app "Xiaomi Mi Home -Control Xiaomi Mi Home devices using Homey by Jelger Haanstra" and get the following by all versions of vacuum robots.
Additional information
This device is already supported and the error you get is because you are using the wrong token. Sometimes you need to reset the device to get a fresh working token. If you need support, use the support forum: https://community.homey.app/t/app-pro-xiaomi-mi-home-app/118
I was mistaken, this model isnt supported yet. I will add it with the next release. I do doubt if this is the cause of this error though as that is usually a token (or a networking) error. But it's best to wait until I have implemented and test it again on the new release.
Ok perfect. I will test the next release and will provide active feedback
Support for this device model has been added in release 3.2.21 which is now pending approval in the app store. Please test it.
Any idea?
The error "Could not connect to device, handshake timeout" usually means you are using an incorrect token or there are networking issues. Try resetting the device and start from scratch. There is nothing more I can do for you
The first one. See https://github.com/jghaanstra/com.xiaomi-miio/wiki/Supported-Devices.
@jghaanstra : unfortunatelly it does not work. I reset the device and got a new token but still the same error. when i ping the dreame robot a get an answer. how can I troubleshoot the problem?
how can I troubleshoot the problem?
The error indicates there is something wrong with the network traffic between Homey and the device. That's either the token or something in your network config (not using correct Ip adddres, the devices are not in the same LAN, etc. etc.). You should look into that.