Hello.
I have had a similar (same?) issue using some ESP32's for work. We needed them to connect to a hotspot to be configured by a script. WPA1 is no longer available, and although the hotspot should have both WPA1 and WPA2 enabled on the raspberry, the ESP chooses to try on WPA1.
Our solution was disabling WPA1 on the RPi hotspot.
From my notes, bullseye and earlier should be setup correctly when enabling a hotspot. My notes translated:
ESP & WPA-PSK:
ESP cannot connect to a network with WPA-PSK anymore - it has been deactivated:
https://esp32.com/viewtopic.php?t=33317
Raspberry Pi with networkmanager (bookworm & onwards) will per default create a hotspot with WPA-PSK & WPA2 enabled when you choose "WPA/WPA2/WPA3 personal" from the gui. There is no "only WPA2" option.
(Raspberry Pi with hostapd & dnsmasq - Bullseye and earlier - Works out of the box after following guide:
https://thepi.io/how-to-use-your-raspbe ... ess-point/
https://raspberrypi-guide.github.io/net ... cess-point
)
By disabling WPA-PSK and only keeping WPA2, the networkmanager AP will be in a state where ESP can connect:
https://askubuntu.com/questions/1345284 ... untu-18-04
( sudo nmcli con modify "HOTSPOT_NAME" 802-11-wireless-security.proto rsn )
( Restart hotspot from GUI after )
( Check with nmcli device wifi list | grep HOTSPOT_NAME )
( Error: XX:XX:XX:XX:XX:XX HOTSPOT_NAME Infra 1 0 Mbit/s 0 ____ WPA1 WPA2 )
( Ok: XX:XX:XX:XX:XX:XX HOTSPOT_NAME Infra 1 0 Mbit/s 0 ____ WPA2 )
I have had a similar (same?) issue using some ESP32's for work. We needed them to connect to a hotspot to be configured by a script. WPA1 is no longer available, and although the hotspot should have both WPA1 and WPA2 enabled on the raspberry, the ESP chooses to try on WPA1.
Our solution was disabling WPA1 on the RPi hotspot.
From my notes, bullseye and earlier should be setup correctly when enabling a hotspot. My notes translated:
ESP & WPA-PSK:
ESP cannot connect to a network with WPA-PSK anymore - it has been deactivated:
https://esp32.com/viewtopic.php?t=33317
Raspberry Pi with networkmanager (bookworm & onwards) will per default create a hotspot with WPA-PSK & WPA2 enabled when you choose "WPA/WPA2/WPA3 personal" from the gui. There is no "only WPA2" option.
(Raspberry Pi with hostapd & dnsmasq - Bullseye and earlier - Works out of the box after following guide:
https://thepi.io/how-to-use-your-raspbe ... ess-point/
https://raspberrypi-guide.github.io/net ... cess-point
)
By disabling WPA-PSK and only keeping WPA2, the networkmanager AP will be in a state where ESP can connect:
https://askubuntu.com/questions/1345284 ... untu-18-04
( sudo nmcli con modify "HOTSPOT_NAME" 802-11-wireless-security.proto rsn )
( Restart hotspot from GUI after )
( Check with nmcli device wifi list | grep HOTSPOT_NAME )
( Error: XX:XX:XX:XX:XX:XX HOTSPOT_NAME Infra 1 0 Mbit/s 0 ____ WPA1 WPA2 )
( Ok: XX:XX:XX:XX:XX:XX HOTSPOT_NAME Infra 1 0 Mbit/s 0 ____ WPA2 )
Statistics: Posted by BlastDK — Thu Mar 06, 2025 12:33 pm