User @CP-Mach-E reported that he had issues connecting to his home WiFi, when connecting to other access points like his phone hotspot worked fine.
He brought it to the dealer, and their responseProblem #2 - Wi-Fi
As soon as I got home, I tried connecting to my home Wi-Fi network. I was unable to connect. I spent a significant amount of time trying to get this to work. Nothing I did made any difference. I have two Wi-Fi Access Points in my house. I tried connecting to both of them. No luck with either one.
When I type in the wrong password, it tells me that the password is wrong. When I type in the correct password, it just says that it was "Unable to connect". This tells me two things. 1 - It is definitely communicating with the access point. 2 - I'm not typing in the wrong password.
I was able to connect the Mach-E to the Wi-Fi access point on my phone when I set the phone up as a Wi-Fi hotspot, so I know that the car is able to connect to a Wi-Fi network. Just not the network in my house. We have countless Wi-Fi devices in the house, and they are all connected just fine, so I know my home Wi-Fi is working properly. I have no idea why the car won't connect to it, but for some reason it just won't.
The issue ended up being an incompatibility with DNSmasq running on the user's Synology NAS.I just got back from picking up the car. The result is pretty much what I expected:
They connected it to the Wi-Fi at the dealer and concluded that it was working fine. It still refused to connect to my Wi-Fi when I got home.
I'll be spending the weekend to see if I can get the Wi-Fi working. I'm pretty sure it is an DHCP issue. I'll update the thread as I find out more.
Good news. I finally got my Mach-E connected to my Wi-Fi.
My suspicion was correct. It was the DHCP server that the Mach-E didn't like. It appears as though there is an incompatibility between the Sync 4 software and the DHCP software that is running on the Synology NAS (Synology uses Dnsmasq for its DHCP server).
I disabled the DHCP server on my NAS and configured the DHCP server on my Ubiquity EdgeRouter X. Once I did that the Mach-E connected right away.
While I was troubleshooting the issue last night, I discovered in the Synology DHCP server's log files that it was assigning an address to the car (i.e. an ACK was being sent), but for some reason the Mach-E just wasn't accepting it.
Now I just need to figure out how to let Ford know about the incompatibility. Not that it matters to me anymore. I'll just keep using the DHCP server on my router, but it would be great if Ford could fix it so that nobody else runs into the same issue.