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.
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.
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!
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.
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