Is there a known bug with the Beken devices regarding not accepting the password for the captive portal?
I have the config below, the same wifi config is used on several esp32 devices as well (minus the web server), where there are no issues with logging into the AP. The correct AP password is simply not accepted on the Beken device. Trying to connect from an iphone. Esphome 2026.7.4
esphome:
comment: "Tuya Smart Socket EU 20A with Power Monitor"
name: power-plug
friendly_name: power-plug
bk72xx:
board: generic-bk7231n-qfn32-tuya
logger:
api:
encryption:
key: !secret encryption_key
ota:
- platform: esphome
password: !secret ota_password
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "esphome-power-plug"
password: !secret ap_password
captive_portal:
# Local web server for direct browser access and remote server reboots if HA is down
web_server:
port: 80
“connection failed”, on both android and iphone. Tested also without a password for the AP now, so a bit clueless.
why I came to this point was due to switching wifi router with a new one, where I kept the same ssid and password, but the esphome devices didn’t connect to the new one, so I just went through the captive portal and updated the wifi details, all good but not this beken device…
Same 2.4Ghz SSID? Not 5 or 6Ghz?
WPA2 or 3?
Same IP Address, both on router DHCP allocation and entity configuration?
Same IP Range?
DNS? VPN? VM? DDNS?
What is the IP address of your router?
What is the configured IP address of your device?
What is the IP Address of your phone? The other one?
Is your fallback web server accessible from the configured ap?
What does ESPHOME debugging mode say for return codes?
Password content and length reasonable?
Is your SECRETS file contents matching what your ESPHome file is expecting?
Is your old router still powered on?
A copy of both your compile and run log (suitably formatted </> for forum readability) may assist in troubleshooting.