No wlan0 interface on Raspberry Pi 4 Model B 32bit

Installation Home Assistant OS
1

Hello,

I followed the instructions for installing Hass.io on Raspberry Pi 4 Model B 32bit.
I couldn’t get the Wifi configuration to work, so finally, I plugged the ethernet cable and was able to access the service on http://my_ip:8123.

Later, I configured SSH access to the host (via port 22222) and tried to figure out what is wrong with the wifi access. I can see that the wifi is enabled, but there’s no wlan0 interface available. I’m new to Hassio/OS, maybe someone is facing similar issues or can share some insights?

This is what I see:

# uname -a
Linux hassio 4.19.58-v7l #1 SMP Tue Jul 16 20:31:47 UTC 2019 armv7l Hassio/OS
# cat /etc/issue 
Welcome to HassOS
# nmcli radio
WIFI-HW  WIFI     WWAN-HW  WWAN    
enabled  enabled  enabled  enabled 
# nmcli device status
DEVICE       TYPE      STATE      CONNECTION         
eth0         ethernet  connected  Wired connection 1 
docker0      bridge    unmanaged  --                 
hassio       bridge    unmanaged  --                 
veth005d26e  ethernet  unmanaged  --                 
veth2856c98  ethernet  unmanaged  --                 
veth3b99adb  ethernet  unmanaged  --                 
veth77fc2a7  ethernet  unmanaged  --                 
lo           loopback  unmanaged  --                 
# nmcli con show
NAME                UUID                                  TYPE      DEVICE 
Wired connection 1  70699786-5ce7-3b67-8e0d-e9e4059c673d  ethernet  eth0   
my-network          72111c67-4a5d-4d5c-925e-f8ee26efb3c3  wifi      --     
# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq qlen 1000
    link/ether dc:a6:32:09:c0:3a brd ff:ff:ff:ff:ff:ff
    inet 192.168.3.190/24 brd 192.168.3.255 scope global dynamic eth0
       valid_lft 63440sec preferred_lft 63440sec
    inet6 fe80::8a63:76eb:e759:a1c5/64 scope link 
       valid_lft forever preferred_lft forever
3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:c4:56:7b:a4 brd ff:ff:ff:ff:ff:ff
    inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
       valid_lft forever preferred_lft forever
    inet6 fe80::42:c4ff:fe56:7ba4/64 scope link 
       valid_lft forever preferred_lft forever
4: hassio: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue 
    link/ether 02:42:98:b6:3a:bf brd ff:ff:ff:ff:ff:ff
    inet 172.30.32.1/23 brd 172.30.33.255 scope global hassio
       valid_lft forever preferred_lft forever
    inet6 fe80::42:98ff:feb6:3abf/64 scope link 
       valid_lft forever preferred_lft forever
6: veth2856c98@if5: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master docker0 
    link/ether 1e:a5:d9:65:89:c7 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1ca5:d9ff:fe65:89c7/64 scope link 
       valid_lft forever preferred_lft forever
8: veth005d26e@if7: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio 
    link/ether 1e:5a:ab:21:17:74 brd ff:ff:ff:ff:ff:ff
    inet6 fe80::1c5a:abff:fe21:1774/64 scope link 
       valid_lft forever preferred_lft forever
10: veth3b99adb@if9: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio 
    link/ether 8e:7b:3c:4b:6c:5f brd ff:ff:ff:ff:ff:ff
    inet6 fe80::8c7b:3cff:fe4b:6c5f/64 scope link 
       valid_lft forever preferred_lft forever
12: veth77fc2a7@if11: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 qdisc noqueue master hassio 
    link/ether 0a:71:67:e7:0b:ec brd ff:ff:ff:ff:ff:ff
    inet6 fe80::871:67ff:fee7:bec/64 scope link 
       valid_lft forever preferred_lft forever
2

I’ve not yet picked up a 4 so do not have firsthand experience… but maybe try loading Raspbian to first confirm everything is working as it should there?

…I recently… I was taking inventory of my Pis and swapping 2’s and 3’s and 3B+'s… OSMC went to a 3B+ from the 2 that was current when I deployed OSMC… that 2 replaced the 3 with OctoPrint, etc…

…anyway, I found that the WiFi of one of the 3’s was bad at the hardware level. (especially odd considering the same chip drives both WiFi and BlueTooth and BT was still woking fine)

3

@MithrasPan, good point, I’ll flash a new SD card with Rasbian OS to see if the wifi works there!

4

I’ve just tried two Pi 4’s and both have wlan0 missing, have you managed to get it up and running?

5

I’ll try Raspbian OS in a day or two, but so far my Home Assistant box runs via the ethernet cable.

6

I’ll try Raspbian too and feedback

7

I just noticed this issue reported 20 days ago:

8

Raspbian works for me but I have the same issue as other describe here when I switch to hass.io on this new rp4 using the 32bit image.

In the link aboive they mention 64bit but I didnt see a clear answser on 32bit.

I guess we conclude it exists on both versions.

9

Can also confirm that wifi is working as expected on Raspbian but not on hass.io

10

I have the same issue with my RPi 3+ (on 32 bit). So I tried openhabian and wifi works with it. Something is wrong with the lastest stable build of hassio.

11

HassOS 3.4 is out and I’m able to connect via wifi now:

# uname -a
Linux hassio 4.19.67-v7l #1 SMP Wed Aug 28 22:06:57 UTC 2019 armv7l Hassio/OS
# 
# 
# nmcli radio
WIFI-HW  WIFI     WWAN-HW  WWAN    
enabled  enabled  enabled  enabled 
# nmcli device status
DEVICE       TYPE      STATE      CONNECTION         
eth0         ethernet  connected  Wired connection 1 
wlan0        wifi      connected  my-network         

hostname: hassio
kernel: 4.19.67-v7l
operating_system: HassOS 3.4
12

My Rpi 4b with beta 3.4 has wifi but it drops frequently. Anyone else have that issue? Any ideas or suggestions? Thanks