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.
@anon11644107 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.
This has happened again. Almost exactly the same for the downstairs map. Updating the floor data has not corrected it.
Service or normal options?
@anon11644107 I don't get it why you need to reset the floor data? The idea in background for this option is to record and use the recorded trims for the floors.. the vacuum work upstairs then "floor upstairs" is select instead of the old "reset trims" and if the vacuum need to work downstairs well the "downstairs floor" is selected and the map will be trimmed for that floor.
I changed the values on on my floor, reseted the floor data with the action and it worked fine.. so once again if you use the floors in HA as I suppose you do why reset the data??
Because that was how you told me to reset it last time this happened.
Well to recovery this situation:
- all trims to 0 in edit floor data for down.
- save the data from the options.
- update the data from the floor down confirm the new data on this floor.
- save the options after that..
This should solve this... I undesrtand this floor managment is a little too complex I will try to make it more simple..
reset trims is deprecated as per it should be in theory not required anymore... please change the floors instead to reset or touch the setup data.
Thanks. That worked.
1 Like
Small heads up for the August 2026 release tomorrow. The camera will now be shown as a linked device rather than part of the valetudo vacuum device.
It does not affect operation in any way.
1 Like
Hi Sandro,
Does the map data “expire” after a given time and is this time configurable?
The reason I ask is that I have not run my vacuum for a couple of weeks due to there being no one home to make a mess. The card currently displays “No Map Data”
However the data is still present in Veletudo.
I’m seeing the reverse - ‘No Map Data’ has appeared as an overlay on the map for my vacuum that ran yesterday evening, and with no vacuum trace or vacuum icon. But it isn’t showing on the maps for the two vacuums that haven’t run since I updated them to Valetudo 2026.08.0.
Is it something to do with the new camera streaming capability introduced in the latest Valetudo? Can’t find the settings to enable it in mine, but they may be too old ( Roborock S50 and Dreame S10).
My data overlay came back. Not sure when or how. I’ve dome a few restarts today while fixing other things.
Try a HA restart.
I was just going to post the same - did a restart for another component update, and now it’s back. Wonder if it will stay though.
never experienced that, the last update camera versation is more a maintenance one.. anyway I read that after a couple of reboot it load correctly.. I think just for general…
The camera refresh the images when:
- the vacuum works.
- the vacuum disconnect from HA.
- Camera reload vacuum connected to HA.
Idle all the rest of the time.
Hope this helps to understand better for the next time if any 
mean that the vacuum has no maps, although there is no correlation with the camera streaming I suppose, I did not update the S5 as actually made no sense… but I can give it a try… If the vacuum has the map, it can take that you need to reload the component not restart.
I just tested the L20 with new firmware and works as before.. I’m sorry this may not help you.
No worries - it seems to have corrected itself. The weird thing was that ‘No Map Data’ was overlaid on the actual map.