Operating-system: Ver 4.10 RPI4 WiFi don't work anymore.

[dianlight]

HassOS release with the issue:

• Operating System: 4.10

Kernel logs:
.. alot of log like:

[  556.305711] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[  558.917741] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[  558.917766] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
....

Description of problem:
After uprgading my RPi4 installation to ver 4.10 the wifi don't work anymore.
I also try with a new installation and the problem is the same. No Wifi connection. If I revert to a 4.9 backup with the same config all work.

This is my-network config:

[connection]
id=my-network
uuid=72111c67-4a5d-4d5c-925e-f8ee26efb3c3
type=802-11-wireless

[802-11-wireless]
mode=infrastructure
ssid=LTOfficenet
# Uncomment below if your SSID is not broadcasted
#hidden=true

[802-11-wireless-security]
auth-alg=open
key-mgmt=wpa-psk
psk=<private>

[ipv4]
method=auto

[ipv6]
addr-gen-mode=stable-privacy
method=auto

[cogneato]

What is the hardware for this install?

[dianlight]

RasperryPi 4 Model B 4GB.

[da-anda]

maybe missing kernel driver due to the kernel downgrade to 4.19 in #723 ?

[dianlight]

The device is list in nmcli device show.

....
GENERAL.DEVICE:                         wlan0
GENERAL.TYPE:                           wifi
GENERAL.HWADDR:                         DC:A6:32:42:EF:27
GENERAL.MTU:                            1500
GENERAL.STATE:                          50 (connecting (configuring))
GENERAL.CONNECTION:                     my-network
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/ActiveConnection/6807
...

Also in nmcli d

DEVICE       TYPE      STATE                     CONNECTION
eth0         ethernet  connected                 Wired connection 1
wlan0        wifi      connecting (configuring)  my-network
docker0      bridge    unmanaged                 --
hassio       bridge    unmanaged                 --
...

Also nmcli d wifi listwork:

IN-USE  SSID          MODE   CHAN  RATE        SIGNAL  BARS  SECURITY
        --            Infra  1     270 Mbit/s  100     ****  WPA2
        LTOfficenet   Infra  1     270 Mbit/s  100     ****  WPA1 WPA2
        LTOfficenet   Infra  36    270 Mbit/s  100     ****  WPA1 WPA2
        LTOfficenet   Infra  36    270 Mbit/s  100     ****  WPA1 WPA2
        --            Infra  36    270 Mbit/s  100     ****  WPA2
        --            Infra  1     270 Mbit/s  75      ***   WPA2
        LTOfficenet   Infra  36    270 Mbit/s  50      **    WPA1 WPA2
        LTOfficenet   Infra  36    270 Mbit/s  24      *     WPA1 WPA2
#

If I try to connect manually:

$ nmcli d wifi connect LTOfficenet password <password>
# Error: Connection activation failed: (53) The Wi-Fi network could not be found.

The only error in dmesg is:

...
[197178.813015] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197178.813067] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197181.946464] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197181.946508] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197184.572739] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197184.572765] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197197.159010] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197197.159042] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197207.270486] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197207.813833] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197207.813868] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197210.960805] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197210.960877] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197213.547975] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197213.548007] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197226.133887] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197226.133920] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197236.271295] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197236.816647] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197236.816692] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197239.931568] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197239.931652] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197242.527777] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197242.527809] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197255.120989] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197255.121021] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197265.268141] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197265.806150] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197265.806220] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197268.920250] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197268.920282] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197271.507958] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197271.507992] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197284.099109] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197284.099136] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197294.271998] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197294.816354] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197294.816410] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197297.888147] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197297.888180] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197300.489916] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197300.489972] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197313.073469] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197313.073501] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197323.275584] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197323.818391] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197323.818438] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197326.957792] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197326.957836] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197329.573850] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197329.573883] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197342.165059] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197342.165092] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197352.273422] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197352.814614] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197352.814679] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197355.950578] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197355.950633] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197358.552071] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197358.552116] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197371.137830] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197371.137862] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197381.274414] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197381.816903] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197381.816947] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197384.931069] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197384.931145] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197387.528042] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197387.528070] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197400.120091] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197400.120116] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197410.273265] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197410.819026] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197410.819072] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197413.962572] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197413.962606] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197416.511344] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197416.511384] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197429.101816] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197429.101849] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197439.273432] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197439.820115] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197439.820205] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197440.393586] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197440.393626] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197440.484748] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197440.484766] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197453.067004] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197453.067035] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197465.273956] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197465.825830] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197465.825862] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197468.992590] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197468.992843] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197471.615556] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197471.615589] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197484.197897] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197484.197930] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197494.274384] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197494.815627] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197494.815668] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197497.963697] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197497.963732] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197500.581337] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197500.581370] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197513.177388] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197513.177424] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197523.274179] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197523.828981] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197523.829022] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197526.962454] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197526.962531] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197529.563996] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197529.564030] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197542.158069] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197542.158094] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197552.274864] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197552.821974] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197552.822051] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197555.933509] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197555.933540] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197558.542458] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197558.542488] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197571.134718] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197571.134751] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197581.275548] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197581.817908] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197581.817950] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197584.931406] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197584.931438] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197587.523677] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197587.523710] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197600.118560] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197600.118581] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197610.275121] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197610.829663] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197610.829857] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197613.893105] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197613.893145] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197616.501139] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197616.501169] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197629.090036] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197629.090066] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197639.276118] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197639.820501] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197639.820542] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197642.876003] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197642.876040] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197645.490982] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197645.491016] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197658.077863] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197658.077894] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
[197668.282910] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197668.831018] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197668.831080] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197671.963668] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[197671.963724] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[197674.562136] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027074)
[197674.562163] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)
...

[LoermansA]

Can I revert back to 4.9 without a reinstall? I have this same issue. Plugging in an ethernet cable doesn't seem to work. I have no monitor connected to the pi so I cannot see the bootlog (but I can get that from the sdcard). So; no network, no display but I do have access to the sdcard ofcourse. Can I downgrade? I can open all partitions from a Linux laptop, if that helps

[LoermansA]

I managed to get the pi running on eth0 instead of wifi by altering the NetworkManager config in one of the overlay partitions (i think). So it is running again. Now to get wifi back online...

[cogneato]

Pi4 with HassOS 4.10

The network config file @dianlight is using as formatted does not work for me. Creating a file with the following format does work on my pi4 when imported from usb CONFIG stick (the name of the file does not matter, as long as it is in CONFIG/network/ and has no extension).

[connection]
id=wovenomena
uuid=9344b185-51e9-4483-921d-d64572f9bf21
type=wifi
interface-name=wlan0
permissions=

[wifi]
mac-address-blacklist=
mode=infrastructure
ssid=wovenomena

[wifi-security]
auth-alg=open
key-mgmt=wpa-psk
psk=test password

[ipv4]
dns-search=
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=auto

[proxy]

I had no issue connecting to wifi using nmcli commands.

[jetatomic]

I'm getting the same errors on RPi 3B+.

...brcmf_set_key_mgmt: invalid cipher group
...wl_set_key_mgmt failed

First appeared on upgrade to 4.10 via Supervisor GUI. Still happening on a clean install with new 4.10 image.

[dianlight]

@cogneato don't understand the difference format of your config and why my format not work for you. ( my come from official documentation )

I also made other tests by changing the wifi network and I discovered that the problem is the connection to the Wifi Mesh. If I connect to a Wifi without Mesh ( or disabled) it works.

@jetatomic , @LoermansA your wifi is mesh or normal?

This are my tests, Work on:

• [x] Iphone hotspot IOS 13.5.1
• [x] Deco M5 Firmware 1.4.4 --> Mash OFF
• [x] Sercom VSDL router (TIM Firmware)

Don't work on:

• [ ] Deco M5 Firmware 1.4.4 --> Mash ON
• [ ] Google Wifi Firmware 12371.52.22 --> Mash ON ( I don't know how disable mash )

Is not a hw issue because version 3.13 and 4.9 works and also raspbian works.

L.

[LoermansA]

@dianlight yes I'm running a Deco M9 mesh.

I'm oke with running with a wired connection for the time being but that seems to have broken now also. There were some updates last night (supervisor and home assistant) that I ran thinking they might have solved the wifi problem, but as of now I cannot get hassio up, even with a wired connection...

So, what I'm doing to get the pi to run on eth0 is mounting the hassos-overlay partition and opening etc/NetworkManager/system-connections/my-network and modifying that with default wired settings as per the documentation. I've also tried using the usb stick procedure, but with that inserted it doesn't appear to boot at all (logs remain empty).

[cogneato]

@dianlight

The one I posted comes from creating a working connection using nmcli and then looking at the resulting network file as generated by the system itself. I then used that to create another working connection. I am aware of the official docs, and that is why I shared.

[LoermansA]

With a wired connection I now get this:

jun 12 18:42:08 homeassistant systemd[1]: Starting HassOS supervisor... jun 12 18:42:08 homeassistant docker[2087]: Error response from daemon: No such container: hassio_supervisor jun 12 18:42:08 homeassistant systemd[1]: Started HassOS supervisor. jun 12 18:42:08 homeassistant hassos-supervisor[2099]: Error: No such object: homeassistant/aarch64-hassio-supervisor jun 12 18:42:08 homeassistant hassos-supervisor[2117]: Error: No such object: hassio_supervisor jun 12 18:42:08 homeassistant hassos-supervisor[2097]: [WARNING] Supervisor image missing, downloading a fresh one: latest jun 12 18:42:23 homeassistant dockerd[372]: time="2020-06-12T16:42:23.549237299Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeou> jun 12 18:42:23 homeassistant dockerd[372]: time="2020-06-12T16:42:23.549426076Z" level=info msg="Attempting next endpoint for pull after error: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connecti> jun 12 18:42:23 homeassistant dockerd[372]: time="2020-06-12T16:42:23.549635204Z" level=error msg="Handler for POST /v1.40/images/create returned error: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for > jun 12 18:42:23 homeassistant hassos-supervisor[2136]: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) jun 12 18:42:23 homeassistant hassos-supervisor[2097]: [WARNING] Supervisor downloading failed trying: latest jun 12 18:42:38 homeassistant dockerd[372]: time="2020-06-12T16:42:38.644248273Z" level=warning msg="Error getting v2 registry: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeou> jun 12 18:42:38 homeassistant dockerd[372]: time="2020-06-12T16:42:38.644396680Z" level=info msg="Attempting next endpoint for pull after error: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connecti> jun 12 18:42:38 homeassistant dockerd[372]: time="2020-06-12T16:42:38.644586939Z" level=error msg="Handler for POST /v1.40/images/create returned error: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for > jun 12 18:42:38 homeassistant hassos-supervisor[2153]: Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) jun 12 18:42:38 homeassistant systemd[1]: hassos-supervisor.service: Main process exited, code=exited, status=1/FAILURE jun 12 18:42:38 homeassistant systemd[1]: hassos-supervisor.service: Failed with result 'exit-code'. jun 12 18:42:43 homeassistant systemd[1]: hassos-supervisor.service: Scheduled restart job, restart counter is at 19. jun 12 18:42:43 homeassistant systemd[1]: Stopped HassOS supervisor.
Perhaps this does not belong in this issue anymore...

It appears that hassio is missing the supervisor docker container and is trying to download the latest but failing. Pinging the pi after letting it settle for a while results in around 80% packet loss. So it seems that the network is up, somewhat, but very, very slow...

[jetatomic]

@jetatomic , @LoermansA your wifi is mesh or normal?

I don't have a mesh. 802.11r fast roaming might be enabled, but there aren't any other APs in range.

I fiddled with this for a while, including swapping in @cogneato 's config (adjusting for my network), but kept getting the same errors on wifi. It worked fine on eth in my tests. At the moment, I just need it to work, so I went back to a Supervised install, and wifi is working fine.

[LoermansA]

I've reverted to 4.9 using a clean install and restoring a snapshot. Everything is working again. I'll skip 4.10 for now.

[corvy]

Any way to downgrade HassOS? I have the same issue. Wi-Fi not working, but wired is fine.

[kirava]

I had a similar issue when I upgraded to 4.10 with raspberry connected to a Deco M5 MESH wifi.
I connected screen & keyboard, boot the raspberry up and ran:
ha os update --version 4.9
at first it gave me an error but after a while downgraded to 4.9 and wifi was functional again

[corvy]

Thank you! I could not get it to work so I have started a new install with snapshot restore to get back on 4.9. Should be working within a few hours (hopefully before my wife gets home!).

[edwardreed81]

I had these wifi issues on my raspberry pi 3 with 4.10 and fixed them by disabling 802.11r (Fast Roaming) on my wifi network (Unifi).

[corvy]

Good tip. FYI I also have Unifi with fast roaming enabled. Have now turned it off pending next OS release.

[azan3l4t]

Similar issue here, using Rpi3+ and wifi mesh from Intelbras with Fast Roaming.
WIFI Stopped working. Tried disabling Fast Roaming, but still not working.

Have changed to wired connection and it's working fine on wired ethernet.

[guilhermelirio]

Same here. I using Rasp Zero W with Home Assistant, and not connect in Mesh wi-fi (Tenda MW6). I'm testing in my Android hotspot and working, but i need to connect in my wi-fi :/

[corvy]

Anyone tested 4.11? I still havent mustered enough motivation.... 👍

[LoermansA]

Anyone tested 4.11? I still havent mustered enough motivation.... +1

The new release contains a new(er) kernel; 4.19.127 instead of 4.19.126. Can't find anything about it containing any fixes for the Wifi issue, so I'll pass on this one until an official update is given regarding this issue.

[kirava]

Anyone tested 4.11? I still havent mustered enough motivation.... +1

The new release contains a new(er) kernel; 4.19.127 instead of 4.19.126. Can't find anything about it containing any fixes for the Wifi issue, so I'll pass on this one until an official update is given regarding this issue.

Same here :(

[guilhermelirio]

I disabled the Fast Roaming function on my router and it worked now, in version 4.10.

[corvy]

I did aswell but it still does not work.

[corvy]

The new 4.12 HassOS solves this problem. :) I think this issue can be closed. This is my Ubiquity Mesh settings and a working HassIO.

[agners]

@corvy hm, that is a bit curious, the kernel hash has been updated with 4.12, but there were only 3 commits made to it. And they do not seem to fix a WiFi related issue: https://github.com/raspberrypi/linux/commits/rpi-4.19.y. The bump to the Buildroot release 2020.02.3 also brought some updates to some user-space packages, but it also does not seem like something relevant got updated... Are you sure this bug was still present in 4.11? Otherwise I guess good thing if its resolved... :-)

[danilogd]

I tried the 4.12 HassOS on a Raspberry Pi 3 B+ before I update my working Homeassistant RPi and the issue isn't resolved yet. I have a TP-Link Deco M5 mesh wireless network, working on both 2,4 and 5 Ghz. Every time I try to connect to WiFi it says "invalid cipher group", but this issue is not present on release 4.9.

[glenn20]

I can also confirm that my Raspberry Pi 4 also fails to connect to wifi on Hassos 4.12 with Fast Roaming (802.11r) enabled.

It connects fine when I disable 802.11r - reproducibly (3 repeat enable/disable cycles).

My router is a TP-Link Archer C2600 running OpenWrt 19.07.3.

I do NOT have 802.11s Mesh enabled on my router - just 802.11r to enable fast roaming between the two wifi routers in my home.

[corvy]

At least it works fine on Ubiquity Unifi Mesh network now, sad to hear that this is not the case for you gents.

[danilogd]

I have found the cause of this problem. The driver for Broadcom WiFi on Raspberry Pi kernel, was updated to support 802.11r on release 4.20, this was included on Kernel 5.0+ that HassOs was using until release 4.9. When HassOs moved back to kernel 4.19 it started using a kernel branch that never included 802.11r support (even though this patch was made on 2018). I found the commit on Github that added 802.11r suppport patch and I guess that the solution would be to ask for this patch to be added to the kernel branch used today by HassOs (4.19.127), however I have no idea how to do this.
Can someone help?

[agners]

@danilogd interesting find! Not sure how the process is to send the patch back to the RPi community, I guess just a pull-request on Github. But maybe it would be good to give it a try first: I created a rel-4 build with the patch applied for RPi4 32-bit, can you give this image a try?

Sources: https://github.com/agners/operating-system/tree/rel-4-fix-wifi

[agners]

I can reproduce this with my RPi4 and OpenWrt with 802.11r enabled:

[  230.041056] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
[  232.686587] brcmfmac: brcmf_set_key_mgmt: invalid cipher group (1027076)
[  232.769848] brcmfmac: brcmf_cfg80211_connect: wl_set_key_mgmt failed (-22)

And I can confirm the above patch fixes the issue. Created a pull request: https://github.com/home-assistant/operating-system/pull/829

[agners]

This should be resolved with the 4.13 release (or 5.2).