Roborock Map/Camera is not shown every 24h

tonka3000 · May 20, 2023, 8:42am

Hi,

I have strange problems with my Roborock S7+ for the last 4-6 weeks. I used the Miio integration to display the map of the roborock and this work great for 1 year. In the last 4-6 weeks I have problem with the map. It is often not shown with the message Failed to retrieve map from vacuum. I have the same problem in the Xiaomi app. Sometimes I can get it back to work when restart the roborock.
When I wait 1-2 days the map get back without doing anything, but often the map fetching fails after 1-6h again.

The strange thing is that I can still contact the robot to send it “home”, start cleaning and I can send it custom commands (segments) to clean a specific room.

I have a unifi network with a UDM Pro. I already restarted every AP and switch, but nothing really changed.

Does anybody had similar experience or have some advice?

Greetings
Michael

Mats789 · May 20, 2023, 11:58am

I have notised this myself (Roborock S6+). I also have problems to get it into the phone app (or HA) the same way that you have with the Xiaomi app. I thinking of going back to the Roborock app since we now have proper integration for it.

tom_l · May 20, 2023, 1:10pm

There are many people reporting this for the third party map extractor camera integration. I think a limit has been put on the number of API calls. If you exceed that limit for the day it stops responding.

tonka3000 · May 20, 2023, 2:32pm

Does this also support the camera integration? Do you have any link to the new integration?

tonka3000 · May 20, 2023, 2:33pm

Thanks for the answer. Rate-Limiting would make sense, but only for the map?

Mats789 · May 20, 2023, 2:34pm

No sure about the camera, I have not tested it yet but according to the docs it should.

EDIT: No, it should not according to the docs but may be added in the future.

tonka3000 · May 20, 2023, 2:47pm

It seems that they add the map feature in future versions according to the docs. It seems that I have to patient until this is officially integrated.

Mats789 · May 21, 2023, 6:50am

github.com/PiotrMachowski/Home-Assistant-custom-components-Xiaomi-Cloud-Map-Extractor

Failed to retrieve map from vacuum

opened 07:15PM - 07 Apr 23 UTC

closed 03:36PM - 12 Apr 23 UTC

kimme1024

bug

### Checklist - [X] I have updated the integration to the latest version availa…ble - [X] I have checked if the problem is already reported ### The problem First of all thanks for this great integration! I've been using it for more than a year now without any issues. However for the last couple of days I don't receive any maps anymore. I only see "Failed to retrieve map from vacuum" for both my vacuums (S5 &S7). I've checked the logs but nothing's showing. I only have the custom integration error about that it's not tested by Home Assistant. But after that, nothing at all. Always difficult when something breaks when you didn't change anything... Any idea's? ### What version of an integration has described problem? v2.2.0 ### What was the last working version of an integration? v2.2.0 ### What vacuum model do you have problems with? S5 and S7 ### What version of Home Assistant do you use? 2023.3.6 ### What type of installation are you running? Home Assistant Core ### Camera's configuration ```yaml camera: - platform: xiaomi_cloud_map_extractor name: Roborock S5 host: 192.168.1.30 token: xxx username: xxx password: xxx draw: ['all'] attributes: - calibration_points - room_numbers - rooms colors: color_map_inside: [21, 21, 21] color_map_outside: [28, 28, 28] color_map_wall: [142, 142, 142] color_map_wall_v2: [142, 142, 142] color_grey_wall: [142, 142, 142] color_ignored_obstacle: [0, 0, 0, 127] color_ignored_obstacle_with_photo: [0, 0, 0, 127] color_obstacle: [0, 0, 0, 127] color_obstacle_with_photo: [0, 0, 0, 127] color_path: [255, 255, 255] color_goto_path: [0, 255, 0] color_predicted_path: [255, 255, 0, 0] color_cleaned_area: [127, 127, 127, 127] color_zones: [0, 0, 0, 0] color_zones_outline: [0xAD, 0xD8, 0xFF] color_virtual_walls: [255, 0, 0] color_new_discovered_area: [64, 64, 64] color_no_go_zones: [255, 33, 55, 127] color_no_go_zones_outline: [255, 0, 0] color_no_mop_zones: [163, 130, 211, 127] color_no_mop_zones_outline: [163, 130, 211] color_charger: [0x66, 0xfe, 0xda, 0x7f] color_robo: [75, 235, 149] color_room_names: [0, 0, 0] color_unknown: [0, 0, 0] color_scan: [0xDF, 0xDF, 0xDF] room_colors: 1: [21, 21, 21] 2: [21, 21, 21] 3: [21, 21, 21] 4: [21, 21, 21] 6: [21, 21, 21] 7: [21, 21, 21] 5: [21, 21, 21] map_transformation: rotate: 270 scale: 3 trim: top: 0 bottom: 0 left: 0 right: 0 - platform: xiaomi_cloud_map_extractor name: Roborock S7 host: 192.168.1.181 token: xxx username: xxx password: xxx draw: ['all'] attributes: - calibration_points - room_numbers - rooms colors: color_map_inside: [21, 21, 21] color_map_outside: [28, 28, 28] color_map_wall: [142, 142, 142] color_map_wall_v2: [142, 142, 142] color_grey_wall: [142, 142, 142] color_ignored_obstacle: [0, 0, 0, 127] color_ignored_obstacle_with_photo: [0, 0, 0, 127] color_obstacle: [0, 0, 0, 127] color_obstacle_with_photo: [0, 0, 0, 127] color_path: [255, 255, 255] color_goto_path: [0, 255, 0] color_predicted_path: [255, 255, 0, 0] color_cleaned_area: [127, 127, 127, 127] color_zones: [0, 0, 0, 0] color_zones_outline: [0xAD, 0xD8, 0xFF] color_virtual_walls: [255, 0, 0] color_new_discovered_area: [64, 64, 64] color_no_go_zones: [255, 33, 55, 127] color_no_go_zones_outline: [255, 0, 0] color_no_mop_zones: [163, 130, 211, 127] color_no_mop_zones_outline: [163, 130, 211] color_charger: [0x66, 0xfe, 0xda, 0x7f] color_robo: [75, 235, 149] color_room_names: [0, 0, 0] color_unknown: [0, 0, 0] color_scan: [0xDF, 0xDF, 0xDF] room_colors: 1: [21, 21, 21] 16: [21, 21, 21] 20: [21, 21, 21] 17: [21, 21, 21] 18: [21, 21, 21] 19: [21, 21, 21] 21: [21, 21, 21] map_transformation: rotate: 270 scale: 3 trim: top: 0 bottom: 0 left: 0 right: 0 ``` ### Errors shown in the HA logs (if applicable) ```shell sadly, none :( ``` ### Additional information _No response_

tonka3000 · May 27, 2023, 11:33am

I tried the hint from the linked GitHub issue an after 6 days it works perfect. It is a rate limiting problem which makes sense when you think about it.

Roborock Integration

In the long-run the native roborock integration will be the goal because camera and controls are handle by one integration and can there lower the GET requests to the xiaomi cloud. But there are many missing features right now. I assume 2-3 months to get all the features.

Solution via Automations

Adding 2 automations fix the problem for now and works perfectly (there are some rare edge cases). Here are my 2 automation for the case somebody need this as well.

Increase update of the camera

First increase the update interval scan_interval in your configuration.yaml to ensure that it does not update that often.

camera:
  - platform: xiaomi_cloud_map_extractor
    host: !secret xiaomi_vacuum_host
    token: !secret xiaomi_vacuum_token
    username: !secret xiaomi_cloud_username
    password: !secret xiaomi_cloud_password
    scan_interval: 14400 # 4 hours, automations make the real update.

Start/Stop Automation

Add following automation. Basically it start and stop the second automation which do the update in a interval.

alias: Start/Stop Xiaomi Fast Scan Interval
description: ""
trigger:
  - platform: state
    entity_id:
      - vacuum.roborock_s7
condition: []
action:
  - if:
      - condition: state
        entity_id: vacuum.roborock_s7
        state: docked
    then:
      - service: automation.turn_off
        data: {}
        target:
          entity_id: automation.update_xiaomi_map_extractor
      - service: homeassistant.update_entity # updatet the card after be in docked state make sure that the last camera image is the one where the roborock is at home
        data: {}
        target:
          entity_id: camera.xiaomi_cloud_map_extractor
    else:
      - service: automation.turn_on
        data: {}
        target:
          entity_id: automation.update_xiaomi_map_extractor
mode: single

Update Automation

Add the following automation which update the camera every 15th second of a mintute (every 60 seconds).

alias: Update Xiaomi Map Extractor
description: ""
trigger:
  - platform: time_pattern
    seconds: "15"
condition: []
action:
  - service: homeassistant.update_entity
    data: {}
    target:
      entity_id: camera.xiaomi_cloud_map_extractor
initial_state: "off"
mode: restart

Thanks for the help @Mats789

peter.rieks · June 7, 2023, 7:21pm

Great explanation, great workaround! The Xiaomi Map Extractor worked for me until 11am every day, but after that also got the “Failed to retrieve…”. After adding the automation, I can now enjoy the maps again throughout the day. Thanks again!

ltechdnb · June 8, 2023, 8:05am

What an actual hero! Thanks so much mate, not often you can literally just copy and paste and it just works and fixes it. Big ups. Cheers

tom_l · June 8, 2023, 9:54am

The only thing I changed was to add this extra state to the turn off fast updates condition:

  action:
  - if:
    - condition: or
      conditions: 
      - condition: state
        entity_id: vacuum.robovac_downstairs
        state: docked
      - condition: state
        entity_id: vacuum.robovac_downstairs
        state: error
    then:
    - service: automation.turn_off
      target:
        entity_id: etc...

The vacuum can be stuck in this error state for long periods of time while I am away from home.

tinkererer · June 8, 2023, 8:20pm

sorry but how do you guys get the roborock onto Xiaomi servers? I use Roborock app and just tried to download the Mi Home app in which it could see the vacuum but couldnt see that it was turned on. Is there another pathway?

tonka3000 · June 9, 2023, 6:35am

tom_l · June 16, 2023, 2:01am

another change:

alias: Start/Stop Xiaomi Fast Scan Interval
description: ""
trigger:
  - platform: state
    entity_id:
      - vacuum.roborock_s7
    to:

The null “to:” ensures the automation only triggers on state changes, not attribute changes.

BeastHouse · July 24, 2023, 11:19am

Awesome work @tonka3000 and @tom_l - had been pulling my hair out over this one!

BeastHouse · July 25, 2023, 10:01am

Hmm even with this running my card is now not reloading again, any ideas?

tonka3000 · July 25, 2023, 5:18pm

Give it some time. Will take 12h-24h after being already rate limited.

BeastHouse · July 26, 2023, 12:02pm

48 hours later and still no good

tonka3000 · July 26, 2023, 12:12pm

Maybe deactivate the whole integration for a day or so.
Did you increase the scan_interval ?