Describe the issue you are experiencing

This issue appears related to PR home-assistant/operating-system#4529 by @sairon which was addressing home-assistant/operating-system#3832, home-assistant/operating-system#4408, and similar reports.

On this HAOS 17.2 Raspberry Pi 5 system, Wi-Fi becomes unreliable after some hours unless 802-11-wireless.powersave is manually changed from 1 (ignore) to 2 (disable) on the active Supervisor wlan0 profile.

The surprising part is that this still happens even though:

• HAOS 17.2 already contains the global wifi.powersave=2 default in NetworkManager.conf
• a persistent keyfile imported through the supported CONFIG/network/ path can temporarily set powersave=2
• but after reboot the active Supervisor wlan0 profile still goes back to 802-11-wireless.powersave: 1 (ignore)

What operating system image do you use?

rpi5-64 (Raspberry Pi 5 64-bit OS)

What version of Home Assistant Operating System is installed?

17.2

Did the problem occur after upgrading the Operating System?

No

Hardware details

Raspberry Pi 5 running Home Assistant OS 17.2 (rpi5-64).

Wi-Fi is used on the built-in wlan0 interface. Ethernet (end0) was also tested in parallel as a control path.

The Pi was physically moved to within approximately 10 cm of the router during troubleshooting, so weak signal is very unlikely to be the cause. BLE is also actively used on this system (multiple Govee BLE sensors), and BLE data continued to flow even when Wi-Fi later degraded.

Steps to reproduce the issue

1. Install Home Assistant OS 17.2 on a Raspberry Pi 5 (rpi5-64) and configure Wi-Fi on wlan0.

2. Confirm that HAOS contains the global NetworkManager setting introduced by PR Disable Wi-Fi powersave by default for all connections operating-system#4529:

   cat /etc/NetworkManager/NetworkManager.conf

   and verify that it includes:

   [connection]
   wifi.powersave=2

3. Let the system run on Wi-Fi for some hours. In this setup, Wi-Fi eventually degrades:

   • wlan0 remains associated with the AP
   • signal remains strong
   • IPv6 link-local remains present
   • IPv4 disappears from wlan0
   • Home Assistant becomes unreachable over Wi-Fi

4. Confirm the degraded state on the host, for example with:

   nmcli device show wlan0
   ip addr show wlan0
   dmesg | grep -Ei 'wlan|wifi|brcm|brcmfmac|cfg80211'

5. Apply this runtime workaround on the host:

   nmcli connection modify "Supervisor wlan0" 802-11-wireless.powersave 2
   nmcli connection down "Supervisor wlan0"
   nmcli connection up "Supervisor wlan0"

6. Verify that Wi-Fi recovers:

   nmcli device show wlan0
   nmcli -f 802-11-wireless.powersave connection show "Supervisor wlan0"

   In this setup, after applying the workaround:

   • IPv4 returns on wlan0
   • 802-11-wireless.powersave is shown as 2 (disable)

7. Create and import a persistent NetworkManager keyfile for Supervisor wlan0 through the supported CONFIG/network/ import path, with powersave=2 explicitly set in the [wifi] section.

8. Reboot the system.

9. Check the active Wi-Fi connection again:

   nmcli connection show
   nmcli -f 802-11-wireless.powersave connection show "Supervisor wlan0"
   cat /etc/NetworkManager/system-connections/supervisor-wlan0.nmconnection

10. Observe that after reboot the active profile again reports:

    802-11-wireless.powersave: 1 (ignore)
    

Anything in the Supervisor logs that might be useful for us?

No clear Supervisor-specific stack trace. The most useful signal is behavioral: after reboot/startup, the active Wi-Fi profile ends up with 802-11-wireless.powersave: 1 (ignore) again, even though HAOS 17.2
contains the global wifi.powersave=2 default and even after importing a persistent keyfile with powersave=2.

Anything in the Host logs that might be useful for us?

brcmfmac: brcmf_cfg80211_set_power_mgmt: power save enabled
ieee80211 phy0: brcmf_run_escan: error (-52)
ieee80211 phy0: brcmf_cfg80211_scan: scan error (-52)

These messages appear when Wi-Fi later degrades, and manually switching the active profile to 802-11-wireless.powersave=2 restores Wi-Fi immediately.

System information

System Information

Additional information

During failure, Wi-Fi does not always disappear completely. Instead:

• wlan0 can remain associated and reported as connected
• IPv6 link-local remains present
• IPv4 disappears from wlan0
• Home Assistant becomes unreachable over Wi-Fi

Example degraded state:

nmcli device show wlan0
GENERAL.STATE: 100 (connected)
GENERAL.CONNECTION: Supervisor wlan0
IP4.GATEWAY: --

Applying the following runtime workaround restores Wi-Fi immediately:

nmcli connection modify "Supervisor wlan0" 802-11-wireless.powersave 2
nmcli connection down "Supervisor wlan0"
nmcli connection up "Supervisor wlan0"

After that, IPv4 returns and Wi-Fi works again.

The imported keyfile is successfully applied by ha os import and can temporarily become the active persistent file with powersave=2, but after reboot the active Supervisor wlan0 profile still ends up as 802-11-wireless.powersave: 1 (ignore).