After some version changes I began to realise my fallback config is not kicking in with my ESPDevices anymore. I’ve been rebuilding my configs with the https://web.esphome.io/ wizard, but it seems something broke and now I can’t get my devices to start the local AP in fallback mode. Can someone please check my config and let me know if something is obviously wrong.
substitutions:
name: esphome-web-0c955c
friendly_name: "Sump 3"
esphome:
name: ${name}
friendly_name: ${friendly_name}
min_version: 2024.6.0
name_add_mac_suffix: false
project:
name: esphome.web
version: dev
rp2040:
board: rpipicow
framework:
# Required until https://github.com/platformio/platform-raspberrypi/pull/36 is merged
platform_version: https://github.com/maxgerhardt/platform-raspberrypi.git
wifi:
ssid: "Arkeo"
password: !secret wifi_password
# Enable fallback hotspot (captive portal) in case wifi connection fails
ap:
ssid: "PicoW-1 Fallback Hotspot"
password: !secret wifi_password
# Enable logging
logger:
# Enable Home Assistant API
api:
# Allow Over-The-Air updates
ota:
- platform: esphome
# Allow provisioning Wi-Fi via serial
improv_serial:
Thanks, by “wifi setup” you mean the actual wifi routers? Not really, but regardless, if I start up my ESP device out of range of the router it’s been configured for, it’s internal AP never shows. And it’s the same with all 11 of my devices. Used to work in the past before many upgrades / updates. Maybe I need to make a manual change to get it working again, just not sure what that is.
Thanks but at times I want to bring the device to my workbench and test it, which is out of range of the “production” wifi ssid. So it will never find it. But it fallback ap should kick on so I can change it and test it. Then take it back to the site where it’s supposed to run and repeat the process.
Yes that is what I remember, but now my devices just stops abruptly if its network is not found as in the log above.
However - I’ve set up a new ESP32 device and it works as expected! I went back to 2 of my Raspberry devices and they still had the problem with the same code. Seems to be Raspberry specific. I’ll see if I can get a serial connection going and it might be a power issue according to some sources.
Thanks for your answers really helps getting closer to the source.