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
ha network update wlan0 without required params causes internal server error #4977
Comments
The network configuration has no WiFi mode/SSID/authentication information, that is why that stack trace is caused. Granted, Supervisor should handle this a bit more gracefully and send back an appropriate error. But when passing WiFi information ( |
I’ll try. Even if that’s the case and it’s about providing proper network details and not graceful response… Is it expected that my network details can be wiped during update from 11.5 to 12.1? Maybe that’s my actual issue ? |
@agners I've connected using Ethernet and successfully enabled and connected to WiFi. This leaves us with two issues:
I'll redact my report to reflect the first issue. Where should I report second one? |
This would go to the Home Assistant Operating System repository. |
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. |
(report re-written to reflect actual issue, pointed out by @agners)
Configuring wlan using
ha network update
without providing all required parameters causes internal server error with no feedback to the user.What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
Anything in the Supervisor logs that might be useful for us?
System Health information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Recorder
Supervisor diagnostics
config_entry-hassio-8302e49fdefff51c8551e0885c7aa39f.json
Additional information
No response
The text was updated successfully, but these errors were encountered: