I have the same situation here, and I just posted the topic yesterday. But seem there are no reply.
THX, it works! I can find the IP address now, but there’s another problem comes out that I can’t access the http://hassio.local:8123 or http://myPiAddress:8123 through the browser. Have you faced this problem?
Other than it take long time for everything to boot up no I have not. Maybe try a reboot and wait like 10-15 min before you go to http://hassio.local:8123/. Good luck
Thank you very much, you help a lot
Hi, for me USB magig somehow does not work
I’ve followed detailed guide here juanmtech but with wifi no way.
If I did it with LAN cable connected, no problem at all
But I need wifi connection.
Is this still true? It seems that the documentation changed:
hassos Documentation network.md
The file is now called “my-network” instead of “hassos-wifi” and the section markers are now [802-11-wireless] instead of just [wifi]?
Why did this change? What’s true now?
It is still true for HassOS-based Hassio. The tweaks were made to hopefully help some users that weren’t getting a connection. “my-network” is only a suggestion, as the name can be anything, and you can have more than one connection file (I use one that contains a wifi config, and one that contains an ethernet config)
But apparently saying “the name can be anything” is more confusing than simply providing a filename.
OK so the filename is not relevant, but what about the section heads like [802-11-wireless] or [wifi]? Are they not relevant too and can be chosen freely?
Thanks!
Chris
Those are the “tweaks” I referred to previously. Those should remain the same.
Hi, Has someone had to change hassio wifi network after it was installed and running for months, even years? I can’t find the wpa_supplicant file common to all linux OS systems.
How can I change the wireless network once the hassio in running?
Thanks a lot
Hi,
@juan-alvarez-1990, I did! Initially I installed hassio without the optional steps. I wanted to enable the wifi, and yes it is possible even after the installation. To do so, you have to follow the steps that @ Danek wrote. At first it did not work for unknown reason to me. I tried to use the content of hassos-wifi file with the the one you find in the following https://github.com/home-assistant/hassos/blob/dev/Documentation/network.md
Now it works, @Todor_Neykov it works also with WPA2.
Maybe it’s because the SSID’s channel of your router is set to auto and not to channel<=10.
Just in case if someone get here with problem on Raspberry Pi 4 and HassOS latest version (3.3 Beta)… I will safe few hours of googling for you, just go here: https://github.com/home-assistant/hassos/issues/435. For now there is no drivers for wi-fi that’s why it’s impossible to connect to your wi-fi network.
Hi all,
I’m quite new and wanted to have a look at home-assistant after 2,5 years experience with FHEM on my Raspi. I took the recommended image, put it with balena etcher on a sd and well went well. Until I tried to connect to my WIFI. I wonder, that a capsuled OS in 2020 is not able to connect to WIFI via standard or even an add-on. I tried now all the variants with USB-Stick, nmcli, nmtui (this wasn’t found at all), direct edit via file-manager… nothing worked.
Don’t tell me about the channels, there is one more Raspi3 and one Raspi connected to my wifi without any issue and seamlessly. There is also no hardware fault, if I put in the debian image, it will connect as usual. I put almost a day in this issue.
Personally I think, it’s a big blame for such a system providing a bunch of archaic configuration methods for a common connection type.
Is there any last idea?
cheers,
Shamal2008
nmcli is available on the host. You can also use it with this addon https://community.home-assistant.io/t/guide-connecting-pi-with-home-assistant-os-to-wifi-or-other-networking-changes/98768
I have had not a very good experience with Balena Etcher. In my case after completion it was giving message failed to unmount, flash completed. With Ethernet and us drive on the RPI powered it up. Only Ethernet connection worked. After many attempts recalled a famous quote “ if you keep doing the same thing, it is foolish to expect different results”
I used flasher from the RPI official website, there was no error and now for first power up did not use Ethernet, only the usb stick was in one of the usb sockets of the RPI.
In about fifteen minutes got an IP address of 192.168.86.53 and I could connect with http://homeassistant:8123
You folks not meeting success may try out not using the Ethernet for first power up on newly flashed image. And in the my-network file use a version 4 uuid. Don’t miss it.
I thought to share this.
Cheers
Thanks, this worked for me too.
Why isn’t WiFi setup formally part of the OS documentation?
Especially for first setup?
Because HA is a server and generally WiFi for for servers is not stable or recommended. It introduces lag and possible disconnects that ethernet doesn’t have.