I can weigh in here. I struggled with this for a long time. Truthfully it really shouldn’t be a problem. In my case it was more of an annoyance. Running around looking for a Pi I left somewhere in the building, or trouble connecting to hassio because browser history pointed to the wrong ip. I recently plugged in the AP that had the SSID the pi knew. There in my router was a pi again with 2 IP’s! Arg!!! I ran it to ground this time and here is what i observed and did with success. THIS SHOULD BE IN THE DOCUMENTATION OR THE GUI in my opinion
Home Assistant on Rpi should work fine connected to both, i was often unaware of the dual connection. If Live ethernet is present during boot or reboot it will be default, wifi will be connected but unusable, It didn’t seem to provide a fall back during my testing. If ethernet not present wifi will be primary and ethernet even if plugged in will not work at all till a reboot. If you connect locally vs cloud you will have to point to the correct LAN ip. You may be OK if you use homeassistant.local:8123 instead of a raw ip address, but it balked for me sometimes on my network.
to the point!! I used HA command line to delete the SSID. I have NO idea what I’m doing really, but it worked. My linux usually is more cut and paste than learning what to type
Either in the terminal add on in the GUI, SSH, or with a monitor & keyboard. The HDMI is not hot unless an awake powered monitor is plugged in when pi is powered on. I used the add on first, but I repeated it using the keyboard and monitor and it also worked. The preceding “ha” is uneeded but tolerated when directly connected. Also got wifi working again b4 sharing.
-h or --help is for help
at the prompt enter
ha os -h
led me to other commands and flags, add a command and another -h and your on your way
ha network info
can be helpfull b4 and after to verify wlan0 is the right interface B4 and that you killed it after
This is what fixed it:
ha network update wlan0 -e
or this they are the same
ha network update wlan0 -disabled
I imagine you could restore or make a new connection here but back to GUI for me
its instant, but it disables ipv4 and ipv6 on the interface in your command. If later you rescan in the GUI it will connect but won’t get a resolved network connection. Go back to the GUI and change WLAN0 ipv4 and ipv6 to back to DHCP from disabled for future you or another.