Invalid calibration

Checklist

• I have updated the card to the latest version available
• I have cleared the cache of my browser
• I have checked if the problem is already reported

The problem

As described in title. It pops a messsage saying “Invalid calibration, please check your configuration”. It was working pre v2.0.

The only log i’ve is “Update of camera.xiaomi_cloud_map_extractor is taking over 10 seconds”. There is no “old configuration” in the yaml file as I’ve removed it long ago, and it seems that this log (1 occurrence) was only a hickup as it’s running every 10minutes.

I’ve also attempted to remove style, map_modes from my card configuration and the output is the same.

What version of a card has described problem?

v2.0.1

What was the last working version card?

No response

What vacuum model do you have problems with?

Roborock.vacuum.s5e

What version of Home Assistant do you use?

core-2021.11.3

What type of installation are you running?

Home Assistant OS

Card’s configuration

type: custom:xiaomi-vacuum-map-card
title: Jaqueline
preset_name: Live Map
entity: vacuum.xiaomi_vacuum_cleaner
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
map_modes:
  - template: vacuum_clean_zone
  - template: vacuum_goto
  - template: vacuum_follow_path
vacuum_platform: default
style: |
  ha-card {
    border-radius: 20px;
    background-color: var(--primary-background-color);
    }

Javascript errors shown in the browser’s console (if applicable)

No response

Additional information

No response

[michalzadkowski]

Weird. I’m getting the “Invalid calibration, please check your configuration” error despite attributes: calibration_points in my camera config. Reload of the xiaomi_cloud_map_extractor in server controls section of the GUI seems to solve the problem for a brief second, then it comes back.

[pannal]

Weird. I’m getting the “Invalid calibration, please check your configuration” error despite attributes: calibration_points in my camera config. Reload of the xiaomi_cloud_map_extractor in server controls section of the GUI seems to solve the problem for a brief second, then it comes back.

Same issue over here.

Edit: I use the blueprint “Disable vacuum camera update when docked”, if that helps.