EDIT: Nevermind…changed channel below 10 and now it works.
My Wifi SSID is not listed at all… Use Timecapsule of Apple with a 2Ghz and 5Ghz wifi. The 2Ghz must show right?
1 Like
I cant find any wifi networks using ssh. I put raspberry next to the router, but it cant find anything, but for sure it is there (my laptop itself can find ~20 SSIDs near by). maybe something else should be enabled for wifi?
This is my log:
Our Cli:
$ hassio help
➜ ~ nmcli radio
WIFI-HW WIFI WWAN-HW WWAN
enabled enabled enabled enabled
➜ ~ nmcli device wifi rescan
Error: No Wi-Fi device found.
➜ ~ nmcli device wifi
➜ ~
Raspberry Pi 4 Model B 4GB
hassos_rpi4-64-3.3
Router TP-Link mode: 802.11b/g/n mixed 2.4GHz + 5 GHz
Channel width: Auto
Channel: Auto (Current Channel 6)
1 Like
I think wifi on the Pi4 is still an issue.
Edit: As of HassOS dev build 3.4, the pi4 wifi is working.
Thanks for a great guide!
I had some issues with this part: nmcli device wifi connect YOUR_SSID password YOUR_WIFI_PASSWORD.
When executing that line nothing first happend, but then the same line was ready to be executed again except for that part of my password that is !!0 was excanged to nmcli.
I added ’ around my password so the line looks like this instead: nmcli device wifi connect YOUR_SSID password ‘YOUR_WIFI_PASSWORD’. And that solved the problem for me!
Hopefully this could help some one else have trouble setting up their wifi for hass.io
4 Likes
Do I have the wrong version of hassio? I have the docker based one for Raspi 3B which identifies itself as hassio.local on the local network. I don’t have nmcli in the root console 
While you could access nmcli by directly connecting to your pi with keyboard and monitor, this guide instead makes use of a specific addon.
Neither with the ssh addon, which gives me another docker image to ssh to, nor with a keyboard and monitor on the PI itself I have nmcli.
the command “hassio hassos info” gives me the following information
core-ssh:~# hassio hassos info
board: rpi3
version: "2.12"
version_cli: "14"
version_cli_latest: "14"
version_latest: "2.12"
core-ssh:~#
when I try nmcli:
core-ssh:~# nmcli
-bash: nmcli: command not found
core-ssh:~#
I’m totally lost! What am I missing?
1 Like
Found it! I used the ssh server addon form the official addons, not the ssh & Webterminal from the community addons.
1 Like
I would also like to know if anyone has had any luck with 5 Ghz (hidden SSID too)
I don’t recommend wifi for a server, but I would think 2.4 is better suited anyway as it has more range and better penetration. 5 Ghz is shorter and fatter and is better used for media devices. Home automation tends to be many things all over a house transmitting small messages.
That said, I tried connecting a pi4 to a test wifi network just now and it defaulted to the 2.4Ghz after I chose the SSID to connect to, which is combined.So I then split them into separate SSIDs and the pi4 could not see the 5Ghz option, only the 2.4. Then I found this thread https://www.raspberrypi.org/forums/viewtopic.php?t=246170 so maybe it is a pi4 issue.
Connecting to a hidden SSID is simply a matter of entering that SSID and password when using the nmcli device wifi connect command. You might want to experiment with it unhidden at first, just so you know that it is seen in any way by your device.
My Wifi is regulary goes down and does not reconnect despite the settings. It can happen in a day sometimes 3 or 4 days after reboot. I am running on pi4B 4Gb server, latest Hassio 0.100, connecting to 2,4Ghz Wifi.
What is wrong with my settings?
Below wifi settings:
connection.id: b.net
connection.uuid: wwwweeee-aaaa-bbbb-cccc-111122223333
connection.stable-id: --
connection.type: 802-11-wireless
connection.interface-name: --
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 1571350233
connection.read-only: no
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
802-11-wireless.ssid: b.net
802-11-wireless.mode: infrastructure
802-11-wireless.band: --
802-11-wireless.channel: 0
802-11-wireless.bssid: --
802-11-wireless.rate: 0
802-11-wireless.tx-power: 0
802-11-wireless.mac-address: --
802-11-wireless.cloned-mac-address: --
802-11-wireless.generate-mac-address-mask:--
802-11-wireless.mac-address-blacklist: --
802-11-wireless.mac-address-randomization:default
802-11-wireless.mtu: auto
802-11-wireless.seen-bssids: 11:44:55:66:77:88
802-11-wireless.hidden: no
802-11-wireless.powersave: 0 (default)
802-11-wireless.wake-on-wlan: 0x1 (default)
802-11-wireless-security.key-mgmt: wpa-psk
802-11-wireless-security.wep-tx-keyidx: 0
802-11-wireless-security.auth-alg: open
802-11-wireless-security.proto: --
802-11-wireless-security.pairwise: --
802-11-wireless-security.group: --
802-11-wireless-security.pmf: 0 (default)
802-11-wireless-security.leap-username: --
802-11-wireless-security.wep-key0: <hidden>
802-11-wireless-security.wep-key1: <hidden>
802-11-wireless-security.wep-key2: <hidden>
802-11-wireless-security.wep-key3: <hidden>
802-11-wireless-security.wep-key-flags: 0 (none)
802-11-wireless-security.wep-key-type: unknown
802-11-wireless-security.psk: <hidden>
802-11-wireless-security.psk-flags: 0 (none)
802-11-wireless-security.leap-password: <hidden>
802-11-wireless-security.leap-password-flags:0 (none)
802-11-wireless-security.wps-method: 0x0 (default)
802-11-wireless-security.fils: 0 (default)
ipv4.method: manual
ipv4.dns: 84.2.46.1,84.2.44.1
ipv4.dns-search: --
ipv4.dns-options: ""
ipv4.dns-priority: 0
ipv4.addresses: 192.168.0.11111/24
ipv4.gateway: 192.168.0.1
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: --
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (default)
ipv6.method: auto
ipv6.dns: --
ipv6.dns-search: --
ipv6.dns-options: ""
ipv6.dns-priority: 0
ipv6.addresses: --
ipv6.gateway: --
ipv6.routes: --
ipv6.route-metric: -1
ipv6.route-table: 0 (unspec)
ipv6.routing-rules: --
ipv6.ignore-auto-routes: no
ipv6.ignore-auto-dns: no
ipv6.never-default: no
ipv6.may-fail: yes
ipv6.ip6-privacy: -1 (unknown)
ipv6.addr-gen-mode: stable-privacy
ipv6.dhcp-duid: --
ipv6.dhcp-send-hostname: yes
ipv6.dhcp-hostname: --
ipv6.token: --
proxy.method: none
proxy.browser-only: no
proxy.pac-url: --
proxy.pac-script: --
Maybe this is seen as 111 but I would fix that.
the address is ok. I have just changed it to post here…
worked on Rasberry pi v3 b+ 64 bit. thank you
My Hassio has been installed with a WiFi configuration using a specific SSID.
I just changed my Internet Service Provider. Using the describe methods in the first post, I have successfully managed to change the SSID to my new one.
Thanks for taking the time to write this guide !
1 Like
Hey, I was stupidly deleted wired connection using nmcli,how could I reset all the connections or enable the wired connection again please ? Thank you for your help
Thank you for these directions. Finally know how to make my changes. One issue, both my WiFi and Ethernet have the same name. How do you handle this?
Thank you for this guide.
I enabled Wi-Fi, and it does work. However, upon a reboot, if the Ethernet cable is not connected, the Raspberry pi won’t connect to Wifi. How can I solve this ?
1 Like
@mat44150 - I’m having the same issue. Were you able to solve this? @cogneato is this a known issue?
I would never use wifi for Home Assistant. 
But no this is not a known issue that I’ve heard of. Maybe remove and re-create the wifi network connection?