drticcz

This just suddenly happened to me after upgrade to the 2022.08 version but I doubt the upgrade is actually the origin. It has been vacuuming for several cycles just fine...

So as expected, this has nothing to do with Valetudo or its version... When you install the HEPA filter to one of your tanks / dust bins, check carefully if...

I am having same issue, although slightly different symptoms - I don't see anything about the map upload attempt in the logs at all (level TRACE) ``` /etc/miio/device.conf: ... vendor=viomi...

Re adjusting the wifi settings did not help.. I am trying to decipher how this whole ecosystem should work in order to debug where it is failing but so far...

Seems like I will have to try dig deeper in the Valetudo code to figure out how exactly is it trying to set the TZ. I tried to disable the...

Valetudo conf: ``` { "embedded": true, "robot": { "implementation": "auto", "implementationSpecificConfig": { "ip": "127.0.0.1" } }, "webserver": { "port": 80, "basicAuth": { "enabled": false, "username": "valetudo", "password": "valetudo" }, "blockExternalAccess":...

I have 3.5.3_0047.. I found out, that if I switch the viomi to the debug mode (creating /mnt/UDISK/debug_mode file), the map suddenly appears including the segments. I now managed to...

.. and surprisingly after docking, I got the map back - strange! :)

> Huh. Are we redirecting those? if not, it almost seems like it's not entirely unclouded Yes, it is all localhost traffic - I have these URL's in the hosts...

Seems like this has been magically solved by resetting the map and disabling and enabling again the persistent maps in Valetudo.. it now just works