Valetudo Vacuums Map Camera for Home Assistant

thanks @gsca075, I have already opened a discussion on github.

2026.5.0 Repair Notification for reset_trims and user languages

  • A repair notification will raise each time the deprecated reset_trims will run as it need to be replaced by the released on 2026.4.0 camera_update_floor_data. Please update your automations and scripts by August 2026 as there will remove the reset_trims service.

  • The Valetudo Map Parser 03.5 fix issue #448 thanks @gunjambi and @IT-BAER for the fix in the mvcrender. This release can cause some strange images cuttings due to the mvcrender new release do not panic use the brain and update your floor data if this happens before opening issues…

  • The issue raised by @tomlut in discussions 442 issue #441 whas a valid hint as HA sometime do not store the user languages by default, so instead of a warning we will debug log the failure on acquire the language data and set by default en in case of failures. If this happens the vacuum status text will be in English, just to be clear, don’t open issues for this..

There is still onenote to do, by working on #448 I noticed that on the instances of HA ā€œdocker and OSā€ it looks there is a ā€œcompilingā€ unexpected behaviour of the mvcrender, that works perfectly by the way, the trims actually are valid at rotation 0 but somehow are not reflected on the HA instance at 90, 180, 270.. it isn’t a bug, the library correctly behave on Mac OS for instance so it was confirm. I will investigate and try to better understand why this happens and hopefully found a solution for that soon.

Please open issues for real problems, if you need help just discussions. Thanks to you all.

Where else would this be set?

@tom_l I just come back from vacation, do you still get warnings? EN(gb) is not yet in the translations so it goes to EN. But I will probably add this new translation soon.

The code of 2025.5.0 is not generating warnings anymore if the ā€œlanguageā€ field is not defined.

Hopefully this clarify but please don’t hesitate to open again an issue if something do not work.

No. It is fixed.