Symptoms:
- The controller is not connecting to the Wi-Fi network, even though the password is correct.
- The device remains in configuration mode (AP).
- Network connection errors occur during configuration.
- Other devices are working correctly, but the controller cannot access the network.
Possible causes:
- The Wi-Fi network is configured exclusively with WPA3 security.
- The router enforces the use of WPA3 and does not support WPA2/WPA3 compatibility mode.
- The network uses WPA/WPA2-Enterprise (802.1X) corporate authentication.
- Access to the network requires you to log in using certificates, user accounts or a RADIUS server.
- A non-standard wireless network security configuration has been implemented.
Suggested solutions:
- Check the Wi-Fi security settings on your router or network controller.
- Set the network security to WPA2-Personal (PSK).
- If your router supports WPA2/WPA3 mixed mode, check whether you can switch to WPA2.
- Do not use networks that require you to log in via WPA-Enterprise (802.1X), certificates or a RADIUS server.
- For corporate networks, set up a separate Wi-Fi network for IoT devices using WPA2-Personal security.
- Once you have changed the settings, restart the router and reconfigure the driver.
- Make sure the controller connects to a network operating in the 2.4 GHz band.
Note for the installer:
BleBox controllers support networks secured with WPA2-Personal (PSK). Networks operating exclusively on the WPA3 standard, or those using WPA/WPA2-Enterprise (802.1X), authentication via certificates, user accounts or RADIUS servers, are not supported. In such cases, a dedicated Wi-Fi network using the WPA2-Personal standard should be set up for IoT devices.