-
-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
wifi.powersave option reverts to default after host reboot #3832
Comments
Workaround: set powersave=2 in the connection file and make it immutable (chattr +i). |
I'm experiencing the same issue. Thanks a lot for sharing the workaround. I'll check if it works for me too :) |
So, HAOS tries to update connection settings file during host boot. In this case immutable attribute prevents it.
Why powersave option overwrites? How it corresponds with HAOS network configuration documentation? https://github.com/home-assistant/operating-system/blob/dev/Documentation/network.md#powersave |
Describe the issue you are experiencing
Exploring issue #3826 I tried to change powersave mode for my wireless adapter using nmcli tool and direct edit connection file using vi (/etc/NetworkManager/system-connections/Supervisor\ wlp1s0.nmconnection). Setting powersave=2 was successful in both cases but after host reboot I see powersave option reverts to its default value: powersave=1. So, I can't change powersave option.
What operating system image do you use?
generic-x86-64 (Generic UEFI capable x86-64 systems)
What version of Home Assistant Operating System is installed?
14.1
Did the problem occur after upgrading the Operating System?
No
Hardware details
G3 Mini PC Alder Lake N100 Intel 12th DDR4 8GB RAM 256GB ROM WiFi BT
https://aliexpress.ru/item/1005006340106437.html
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
Anything in the Host logs that might be useful for us?
System information
System Information
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Additional information
No response
The text was updated successfully, but these errors were encountered: