PiotrMachowski / lovelace-xiaomi-vacuum-map-card

This card provides a user-friendly way to fully control map-based vacuums in Home Assistant. Supported brands include Xiaomi (Roborock/Viomi/Dreame/Roidmi/Valetudo/Valetudo RE), Neato, Wyze, Roomba, Ecovacs (and probably more).
MIT License
1.48k stars 254 forks source link

Missing vacuum status and fan speed in display #610

Closed idogrf closed 1 year ago

idogrf commented 1 year ago

Checklist

The problem

Ever since updating to v2.2.0 I'm missing the Status and Fan Speed in the display My vacuum is the 1gen xiaomi mi robot

image

What version of a card has described problem?

v2.2.1

What was the last working version card?

v2.1.2

What vacuum model do you have problems with?

xiaomi mi robot (1st gen)

Which integration do you use to control your vacuum (link)?

https://www.home-assistant.io/integrations/xiaomi_miio/

What browser (browsers/apps) does have this problem?

Chrome/Brave

What version of Home Assistant do you use?

2022.8.3

What type of installation are you running?

Home Assistant Container

Card's configuration

type: custom:xiaomi-vacuum-map-card
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
entity: vacuum.xiaomi_vacuum_cleaner
vacuum_platform: default

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

No response

Additional information

No response

PiotrMachowski commented 1 year ago

Have you tried clearing cache? Does anything happen when you click the tile?

idogrf commented 1 year ago

Yes, I tried clearing the cache I also tried different devices and I get the same results on 2 pcs and an android

Nothing happens when I click the tile - the animation plays but nothing opens

PiotrMachowski commented 1 year ago

I have noticed that you use quite old HA version, I suspect that this might be a reason of your problems

PiotrMachowski commented 1 year ago

Can you follow these steps?

PiotrMachowski commented 1 year ago

Fixed in v2.2.2

idogrf commented 1 year ago

Amazing, v2.2.2 did the trick! Thanks @PiotrMachowski for the quick response