Persistent maps suddenly not working anymore. How can i troubleshoot?

[m4dm4xi]

Are you already using Valetudo?

Yes, for a long time

Your questions

Hello,

I have been using valetudo for years. Originally on the Xiaomi Mi Robot Vacuum (V1) and some years ago I switched to the S5 Max which I flashed with firmware 1668.

I have been regularly updating the valetudo releases and I´ve done the update to 2026.02.0 some days ago.

My issue which I would like to discuss started also a few days ago. I really don´t know if it started before the newest valetudo release or after... I also tried checking but I found no definite answer in case it may be relevant.

Anyways... back to my issue: Suddenly my robot wouldn´t execute my daily cleaning timer anymore but would immediately fail. After a few days of me not checking what the issue was I logged in and saw that the persistent map was gone. I thought to myself "hm, that has never happened before..." and simply tried to start a new mapping process.

However, that is failing. When clicking "Map Reset" in "Map Options" I am displayed the error:
An error occurred while sending command to MapResetCapability: map resource unavailable
When clicking "Mapping Pass" in "Map Options" I am displayed the error:
An error occurred while sending command to MappingPassCapability: error max map count

I have tried restoring the default configuration which did not change anything.

I have attached a log file.
maxmapcount.log

What are my questions...

• how do I identify if the rootcause of this error lies within the firmware or within valetudo?
• could this be an hardware issue? For example could the flash memory used for storing the persistent map be corrupted?
• does anyone have an idea what I could try to fix this?

Thank you :).

[Hypfer]

I have tried restoring the default configuration which did not change anything.

Correct. That only applies to Valetudo. You would want to factory-reset the firmware

how do I identify if the rootcause of this error lies within the firmware or within valetudo?

It doesn't lie within Valetudo.

could this be an hardware issue?

Possible

does anyone have an idea what I could try to fix this?

Try disabling persistent maps, then re-enabling it. If that doesn't help, factory-reset. That might then require a valetudo reinstall