No longer connecting to WiFi / Valetudo uninstalled (itself?) #2410
-
Are you already using Valetudo?Yes, for a long time Your questionsI've had Valetudo running for a while now without any issues (installed 2023-02-03), but today randomly in the middle of the day I noticed that the robot suddenly left the WiFi network and never came back. I decided to reboot the robot and noticed that it also started talking again, despite me having disabled all the chimes/voices, which made me think it must have factory reset itself. I decided to try and log into the robot with SSH, which still works and shows the MOTD (built with dustbuilder…), thought maybe it was just a WiFi issue and tried to connect to the WiFi config (http://192.168.5.1) but the page cannot load (no HTTP server listening on port 80). I'm tempted to just try and setup WiFi through the CLI, but since the documentation explicitly recommends against that I thought I'd reach out first. I'm using the Dreame Z10 Pro. I did try to just reboot the robot. I don't see any processes or files containing "valetudo" when I explore through SSH. Do I need to reinstall the device? If so, do I just get a new dustbuilder firmware and run the install script from within the existing dustbuilder OS, or should I try and install valetudo without reinstalling everything (considering that it seems like dustbuilder is 'fine')? I'm not entirely sure what happened, so I'd like to avoid the scenario where I have two things running simultaneously and it just causes more (worse) issues in the future. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Yes, that occasionally happens on the NAND-based dreames. The result however is corruption of the ext4 fs on So yeah. You can just put it back like described in the rooting guide |
Beta Was this translation helpful? Give feedback.
Yes, that occasionally happens on the NAND-based dreames.
I suspect that there is something not quite right in the storage layer of that custom kernel but I don't know for sure.
The result however is corruption of the ext4 fs on
/data, which the robot detects during the daily reboot and then recreates a new fs there.As valetudo is stored on
/data, with that, the binary is gone.So yeah. You can just put it back like described in the rooting guide
Or you do the easy thing, build a new dustbuilder package with Valetudo prepackaged and install that via ssh.