Valetudo "Unable to reach vacuum." #1843
Replies: 1 comment
-
The issue you've reported is usually caused by the user joining the robot to a Wi-Fi network using some shell commands and/or editing config files. As noted in the docs this is not recommended as it will lead to issues such as this one. The reason for that is that being connected to a Wi-Fi network and being provisioned are two different things. Here it is important to keep in mind that we're simply replacing the cloud. That means that the logic still assumes that the device would be bound to a specific MiHome account and only if it has that data would it start responding to commands and reporting data because only then the firmware would know who is allowed to access it etc. Configuring Wi-Fi using Valetudo takes care of this correct provisioning process. Running any random shell commands to join a Wi-Fi network does not. To fix this, simply reset Wi-Fi by pressing and holding the two outer buttons until the robot talks to you and then connect to the Wi-Fi AP and configure Wi-Fi as documented in the docs |
Beta Was this translation helpful? Give feedback.
-
I have a:
It has been running Valetudo fine for about a year.
Suddenly though I'm unable to interact with the robot via Valetudo. I can access the web interface on the device, but everything just spins forever.
If I SSH into the device I see things like this in the
valetudo.log
The robot still responds to button presses, so I can still manually run a cleaning cycle. It just seems like Valetudo and the firmware aren't communicating. Any ideas how to debug or fix this?
Beta Was this translation helpful? Give feedback.
All reactions