X40 Valetudo Setup Issues

[squishdacat]

Are you already using Valetudo?

Yes, for a few months

Your questions

Hi, I am currently installing Valetudo on my new X40 Ultra and am having some issues with connecting it to Wi-Fi initially.

To be clear, I am not having intermittent Wi-Fi issues as I can't get the robot setup on Wi-Fi to begin with.

What I am experiencing is Valetudo booting on the robot (this isn't a given as I will get into) and then when I try to connect the robot to Wi-Fi I get a timeout error:

[1970-01-01T00:19:26.292Z] [DEBUG] local request 1166 miIO.config_router timed out
[1970-01-01T00:19:26.293Z] [WARN] Unable to reach vacuum. Giving up after 100 tries
[1970-01-01T00:19:26.304Z] [WARN] WifiConfigurationCapabilityRouter: Error while handling route "/" {
  body: {
    ssid: 'MY_SSID',
    credentials: {
      type: 'wpa2_psk',
      typeSpecificSettings: { password: 'REDACTED' }
    }
  },
  message: 'request timed out:{"method":"miIO.config_router","params":{"ssid":"MY_SSID","passwd":"REDACTED","uid":1337,"cc":"de","country_domain":"de","config_type":"app"},"id":1166}'
}

I struggle to see this being an issue with my Unifi AP as I get the same when I attempt to connect it to my iPhone's hotspot. It looks to be like the issue is internal to the robot given the miIO.config_router call seems to be timing out? I'm not familiar with miio so don't haven't a real idea how this communication is occuring. I will say iptables is not showing any firewall rules:

[root@r2416_release:~]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

...but I don't even know if the firewall is managed by iptables on this device.

Whether the following other issues I had are relevant I am unsure but I thought it prudent to add:

1. When first installing Valetudo it couldn't automatically detect the robot and the binary would not start
2. Changing the /data/valetudo_config.json file to include the correct robot instead of just "auto" (as suggested in a comment somewhere) for the implementation value in the config didn't help because;
3. Valetudo is only pulling the config file from /tmp/valetudo_config.json and if it doesn't find one it generates a default one that has the "auto" robot type
4. After fixing the /tmp/valetudo_config.json file and a line in the post boot file to copy the /data/valetudo_config.json file to /tmp on boot,
5. Still can't get robot to boot because it can't find the deviceID... I provide the deviceId in the implementationSpecificConfig as stated is possible here
6. Now it boots but I still have those Wi-Fi issues
7. I tried adding ip, cloudSecret and localSecret values to the config but this did not change anything.

Something that may be of interest is that most of the time I can get Valetudo to scan and detect Wi-Fi networks.

I have tried on Valetudo 2025.08.0 and 2025.10.1. I am currently running firmware v1702 on the robot but experienced the same behaviour with v1652.

I am genuinely at a loss. Any advice people could provide would be greatly appreciated

[Hypfer]

Take a step back, clean everything and start from the beginning.

You're jumping from one hack to the next and none address whatever underlying cause there might be.
Why would you for example automatically copy the config file. That doesn't make sense.

I and I guess we all know these situations and they're usually being solved by not continuing down the path but walking backwards and maybe even giving it a night of sleep.