Can't connect to wifi Raspberry Pi 3A+

[adam_zzz]

You mean add the two lines below to the network block?

key_mgmt=WPA-PSK WPA-PSK-SHA256
ieee80211w=1

And then user no longer has to choose a security protocol?
Assume the "No security" option is removed.

That would be nice :-)

Those 2 lines should handle most of the security protocols (except WPA3-SAE) so the user doesn't need to chose from a dropdown.
Then you would need to provide a way for the user to use no security, like a checkbox, but I think this also shouldn't be needed if you put NONE as a last fallback in wpa_supplicant. So in theory what they fill in for the Password wouldn't matter, if they actually don't use any security then it will try and fail the security options and eventually end up on NONE anyways and connect successfully to No security. (I haven't tested this scenario yet but I don't see why it wouldn't work) 

Code:

key_mgmt=WPA-PSK WPA-PSK-SHA256 NONE
ieee80211w=1

The only disadvantage that I see is that it won't be as clear to the user when they are connecting to an unsecure network, so probably this needs to be explained somehow in the UI.

That would be confusing.

I like the idea of automatic protocol handling (we do a bit of this in our Samba SCAN) but I also want the user to know that a secure WiFI protocol is being used. Maybe having explicit choices is still best.

WPA2-Personal
WPA3-Personal Transition Mode
No Security

I understand if you want to make it clear for the user what security they are using but in that case maybe those 3 options wouldn't be enough and it would require more coding.

• Would WPA1 and WPA1/WPA2 mixed mode still be supported? Keep in mind with those 2 lines suggested it will still connect to WPA1 and WPA1/WPA2 mixed mode.
  
• WPA3-Personal Transition Mode gives a false sense of security, it gives you the feeling that it would use WPA3 when possible but that will never happen since Raspberry PI doesn't support it so it will actually use WPA2. 
  When WPA3 starts being supported by Raspbian OS, your option would still be misleading unless you update the config to support it in wpa_supplicant.
• There are less secure cyphers that will still work with the 2 lines (TKIP) and this is not visible to the user.
  

Maybe I'm a bit biased, but I would be satisfied with a message saying something like "moOde will make an effort to connect to the most secure protocol supported by your router, if your router has no security or week security it will use that. WPA3 is not yet supported in Raspberry PIs." 

So I would only have to enter an SSID and optional Password. Ideally whatever moOde/my router negotiated you should inform the user in the UI (wireless section), and for the cases when week or no security was negotiated, a warning message should be displayed.
It shouldn't be too hard to find out and display the protocol used:

Code:

wpa_cli -i wlan0 status