Sylvia van Os

Sadly, this will have to wait a bit, because my Valetudo locks up when I try to create a zone: https://github.com/Hypfer/Valetudo/issues/344. After that though, my plan is as follows: 1....

Valetudo doesn't yet expose this in MQTT, so this would require calling the API and wouldn't work for MQTT users. So that needs to change first.

https://github.com/TheLastProject/lovelace-valetudo-map-card#displaying-as-overlay may help you. I guess it kinda solves your issue but I still want to add support for zones anyway so I'm leaving this open.

Your change introduced a very annoying flickering effect every few seconds: https://user-images.githubusercontent.com/1885159/148106832-a0600b4f-937b-44e3-8961-813d6433d23c.mp4

The assumption IS true by default for recent Home Assistant versions, as written in the release notes. But yes getting the option back to override this was requested by multiple...

> My map entity is also still named camera.map_data, after updating the card (and vacuum). That is only the case if you [didn't read the release notes](https://github.com/TheLastProject/lovelace-valetudo-map-card/releases/tag/v2022.01.0).

And you are both certain you are running the latest version of Valetudo? Because if so I really cannot explain that behaviour. Anyway, as with all requested features, I may...

Good it's working for you at least. It's really ironic how that went, given Valetudo was changed to only update 1 release at a time because... people kept not reading...

Not yet, I would happily accept a patch for it but nobody bothered to implement it.

The cropping code is very bad, see also #1 and #3. Someone else will have to fix this as my spatial reasoning is a bit weak.