lovelace-xiaomi-vacuum-map-card: UI broken in 2022.3+

@escafoide it will be released when it is ready

Fixed in v2.0.11

Was coming here as I had an issue as well, but mentioning that would be redundant.

It’s good enough to know that there is being worked on even if development isn’t fast. As someone that creates experiences for Home Assistant myself I totally understand and you should definitely not feel pressured! If people want to move on they’ll move on, but I highly doubt there is anything much better than this card for vacuums.

So… Take ALL the time you need!

where solution?

Where brain?

He’s working on it, as he said above.

@befantasy Issue should be finally solved today 😉

I’m really fond of this card as well, it took a lot of work, but the result is quite satisfying 🙂 personally I really like its universality - it probably supports every vacuum that works with HA (some might require a bit of tinkering in config though)

The card has appeared like this to me. I’ve already cleared the cache, I’m on card + recent version and Home Assistant version 2022.3.

@jimz011 I receive notifications about every comment anyway, but it doesn’t bother me so much 😉 It’s much better than issues created by people that haven’t read the documentation 😃

It is an open issue, ANY open issue is basically unresolved. Would seem redundant to me and honestly people should stop being so lazy and just read. The developer puts months of work in cards like these, but people that use them are even too lazy to give it one minute of reading time?

@PiotrMachowski I’m no expert on github issues but i’ve been told in other places that one should not write like “don’t work for me either or following”

I guess this will only stress the developer with unnecessary notices. What I’ve been told it’s better to just subscribe to the issue.

Anyway, I didn’t buy you a beer but I bought you a coffee that has proven my coding experience better than beer 😃

Best regards Peter Sweden

@digitalit well, these comments are a bit unnecessary, because it won’t work for all 2022.03+ installations 😉

There is a lot of pressure on this issue, but I don’t have much time lately, so progress is quite slow 😕

@variada yup, that’s the cause. I will try to fix it as soon as possible

This issue is fixed in the latest version of the card and the below hack is not necessary anymore.

To clean this up a little until there’s a proper fix available, you can install Card Mod and then add this bit of css code to the end of your Vacuum Map Card in the YAML code editor:

style: |
 .modes-dropdown-menu > .modes-dropdown-menu-listbox {display: none;}
 .modes-dropdown-menu:hover > .modes-dropdown-menu-listbox {display: block;}
 .modes-dropdown-menu:hover > .modes-dropdown-menu-button {display: none;}
 .modes-dropdown-menu-entry-button-wrapper.first {border-start-start-radius: var(--map-card-internal-big-radius);}
 .modes-dropdown-menu-entry-button-wrapper.last {border-end-start-radius: var(--map-card-internal-big-radius);}
 .map-actions-list {height: 50px;}

Thank you @PiotrMachowski for working through this! I’m new to Home Assistant in general, and I must say I’m very impressed with this card and your work! Perhaps one day I’ll be able to contribute code myself. Sending some beers as a thank you!

The best thanks are those made by offering a beer … 1 beer fo you;)

@PiotrMachowski Thanks for working on this. I have the same problem

@PiotrMachowski Thanks for resolve the issue

@PiotrMachowski Thanks for getting on this issue!

@PiotrMachowski Thanks!

I think it’s also due to the language barrier. Though, that’s where Google Translate comes in.

I didn’t mean to start a wave of thanks as a pressure method. I don’t mind waiting for the fix - it’s not a critical issue being a UI glitch and I don’t use that component very often. It definitely is a little cherry on the cake on my setup though - love the map integration. But yeah, I’ve materialised the thanks into some beers.

@PiotrMachowski Thanks for looking into it Piotr.

I confirm this issue after upgrading Home Assistant to 2022.3

after reloading the cache everything is ok, ty

fix is working.

Thank you.

To clean this up a little until there’s a proper fix available, you can install Card Mod and then add this bit of css code to the end of your Vacuum Map Card in the YAML code editor:

style: |
 .modes-dropdown-menu > .modes-dropdown-menu-listbox {display: none;}
 .modes-dropdown-menu:hover > .modes-dropdown-menu-listbox {display: block;}
 .modes-dropdown-menu:hover > .modes-dropdown-menu-button {display: none;}
 .modes-dropdown-menu-entry-button-wrapper.first {border-start-start-radius: var(--map-card-internal-big-radius);}
 .modes-dropdown-menu-entry-button-wrapper.last {border-end-start-radius: var(--map-card-internal-big-radius);}
 .map-actions-list {height: 50px;}

Thank you @s-hutter this works perfectly!

I didn’t mean to start a wave of thanks as a pressure method. I don’t mind waiting for the fix - it’s not a critical issue being a UI glitch and I don’t use that component very often. It definitely is a little cherry on the cake on my setup though - love the map integration. But yeah, I’ve materialised the thanks into some beers.

Yep, this is plugin great. The breaking changes were expected/announced for some time, but I won’t complain. It’s still usable enough 😃

Don’t know if a beer it’s gonna help to resolve the issue but weekend is coming so I bought You few to relax. I’m no coder but if You need some help I’m here to assist.

can confirm. the reason for the malfunction is probably found here: https://developers.home-assistant.io/blog/2022/02/18/paper-elements/