HAOS on Raspberry pi 4 don't run on wifi

I performed a fresh installation of HAOS on a Raspberry Pi 4 following the documented procedure. For the initial boot, I connected via Ethernet and then configured the Wi-Fi through the GUI.

Everything appears to be in order when checking via the command line, yet as soon as I unplug the Ethernet cable, the system stops responding. The Wi-Fi connection is active, and I can see from the router that the device remains connected.

As long as Ethernet is plugged in, communication works fine (even when accessing via the wireless IP), but the moment I disconnect it, everything stops. It almost seems like the web server is only listening on the Ethernet interface or that a default route is forcing traffic through Ethernet.

Any ideas on how to fix this?

Why not just run it on ethernet? That is the recommended way to run it.

Because itā€™s not what I needā€¦ Why not run it on different hardware then? Because this is what I have.

Connect a monitor and keyboard to your RPi. From the command interface, you can modify the network settings.

ha network update --help

Make sure to reboot the host after any changes.

I donā€™t think the problem is the docker. Most probably is the OS level.
when i do an ā€˜ip aā€™ I see only the eth0 and not the wlan.

Different hardware? I meant connect the pi with a cable, not wifi.

of course with cable works, but is not what Iā€™m looking. Iā€™m looking for a fix, not for a workaround

Using wifi is a workaround, cable is the recommended fix. You run it head-less anyway so shouldnā€™t be hard to have it connected to a switch or your router. Up to you of course, but best practice is using a cable, not wifi.

Michael just recently finally solved all his raspberry pi 4 WiFi problems with a simple cable :point_down:

Also changing the hardware is certainly a solution, but it does not address the technical issue I am trying to resolve. Suggesting infrastructure changes in response to configuration adjustment requests does not provide a real solution.

You are offering me a workaround that is not what I am looking for, without knowing the details of the context. Using a cable is not an option in my implementation.

If you donā€™t know how to solve the problem, there is no need to reply.

I never told you to change any infrastructure, the only one suggesting that is you.
I told you to use a cable, which you already stated works. Wifi is less than ideal running a server, but if you donā€™t want to listen thatā€™s fine. Have a nice day!

1 Like

Have you tried this: Changing Connectivity to Wifi via cli.

Iā€™ve been running HA over WiFi for over 5 years now. Never had an issue with that.

I get it. Iā€™m an old-school tech guy who always believed wired is ā€œbetterā€ than wireless, too. It can still be a bit hard for me to accept, but times have changed. Wireless can be just as robust, and unless youā€™re demanding massive amounts of throughput, it can perform just as well.

I was able to login on SSH on 22222 and tried to follow that guide, but every time that i remove the lan the wlan lost the connection too.

Sorry, that guide is outdated but it does point to some relevant documentation: operating-system/Documentation/network.md at f56130af1915ceba732ba940e820be370ca8655d Ā· home-assistant/operating-system Ā· GitHub.

Did you try:

ha network update wlan0 --ipv4-method auto --wifi-auth wpa-psk --wifi-mode infrastructure --wifi-ssid "MY-SSID" --wifi-psk MY_PASS

the problem is not to join the wifi apparently. my rpi is on the correct wifi.
it seems to be that the rpi is accepting traffic over wifi but is sending out the answer over the ethā€¦ once eth is disconnected there is no answer from the system

I would try fresh install again to reset to default then try the ha network update command.

There may be a hardware/firmware problem if that doesnā€™t work.

I tested other OS version and wifi works fine without the lan. so it really seems a config problem.