dreame-vacuum: goto is not working (with Dreame D9)

Hello,

Describe the bug I have installed latest Beta v2.0.0B16. The goto feature is not working with my Dreame D9. I send following command to my device:

action: dreame_vacuum.vacuum_goto
target:
  device_id: XXXXXXXXXXXXXXXXXXXXXXX
data:
  x: 2468
  y: -4428

Vacuum is answering me the following:

"start zone cleaning"
"unable to reach the specified area"
"please try to clear obstacles in the path"
"returning to the dock to charge"
"paused"
  • there are no obstacles in the way.

  • the vacuum has not even start to move.

  • it just has left the charging station.

  • i tried different coordinates.

  • i extracted the coordinates via lovelace-xiaomi-vacuum-map-card  

the button of the service is green: image

  • If I send totally bad coordinates (f.e. -999999999999) the button is red and i get the log message Error handling message: Coordinate is not inside the map
  • dreame_vacuum.vacuum_clean_spot with this coordinates is also working
  • so i don’t think it’s caused by wrong coordinates.    

To Reproduce

  • send mentioned yaml via HASS dev tools to Dreame D9    

Expected behavior The vacuum should go to a specific coordinate and stop there until further commands.    

Screenshots no    

Additional Information (please complete the following information)

  • Model Name [e.g. dreame.vacuum.p2028]: dreame-vacuum-p2009
  • Firmware Version [e.g. 1156]: 1132
  • Home Assistant Version: 2024.9.3
  • Configuration Type [With or without map support]: with map support
  • Errors or warnings shown in the HA logs (if applicable): none

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 17 (10 by maintainers)

Most upvoted comments

Thanks for your help. I will close the issue when a new Beta version has been released.

If it works with 100 then I can update the integration, it is not much difference between 5cm and 10cm for operation of the go to feature. Your device firmware probably uses < symbol for checking the area coordinates instead of <= like mine so it cannot find valid a point when coordinates are set to 50x50 because that means 0x0 square cm area for it.