rand256/valetudo

WebUI / http is no longer worker

domibarton opened this issue · 1 comments

Describe the bug

I installed 2022.01.0 on my Roborock S50. It worked flawlessly, even with the Home Assistant / MQTT integration.
Unfortunately, now the WebUI is no longer reachable / working. I can ping the vacuum and ssh into it. I can also reboot the vacuum and it works. However, the WebUI is no longer working (properly).

I get the HTTP 401 response and I can authenticate, so I get a HTTP 200 back. But when the static files are loaded, the files are pending, the WebUI hangs and there's no more response.

Funnily enough, the Home Assistant integration via MQTT works!

How to Reproduce

  1. Go to the web URL
  2. Enter the credentials
  3. Login
  4. Wait…

Expected behavior

  1. The WebUI and all static files area loaded

Screenshots

image

The /static/js/2.b5dc54c8.chunk.js file is pending.
When I open the URL directly, it will load endlessly:

image

Questions

Is there any way how I can further debug this issue? What I did after the stock setup:

  • Configured HTTP Basic Auth
  • Configured MQTT (Host, Port, Credentials, Prefix, Topic Name)
  • Activated the MQTT map thingy
  • Reduced the volume

Vacuum Model: S50

Valetudo Version: 2022.01.0

User-Agent Google Chrome 97.0.4692.71 & Safari 15.2 (17612.3.6.1.6)

Additional context

What I've tried so far:

Found valetudo running:

  • SSH'd into the robo and rebooted it (several times)
  • Deactivated mqtt via /mnt/data/valetudo_config.json and rebooted again
  • Browsed other issues in this repo to find similar issues

What I found was was this discussion.
What is _root_postboot.sh, because this is missing:

[root@rockrobo bin]# ls -l /mnt/data
drwx------    2 root     root         16384 Jan  1  1970 lost+found
drwxr-xr-x    2 root     root          4096 Jan 20 00:00 miio
drwxr-xr-x    6 root     root          4096 Jan 20 00:00 rockrobo
drwxr-xr-x    3 root     root          4096 Jan 18 22:16 rriot
-rw-r--r--    1 root     root          1829 Jan 19 23:53 valetudo_config.json
drwxr-xr-x    2 root     root          4096 Jan 18 22:18 wlan

However, valetudo is running:

[root@rockrobo bin]# ps | grep vale
  365 root      132m S    /usr/local/bin/valetudo
 8098 root      2268 S    grep vale

Please note I'm using private CIDR network ranges (not like others ^^). My client is in a different VLAN / subnet than the roborock. There's masquerading between does networks. However, I can also connect the client to the same subnet as the robo and it still doesn't work.

stupid me… sorry wrong repo!