Cannot connect to captive portal / fallback hotspot

ESPHome
1

I was flashing an new smart plug, but something went wrong when migrating from tasmota.

The new fallback hotspot is showing up as a wifi network, but I can also see the device connected to my router.

The wifi hotspot is secured, and I have no idea what the password would be (deleted yaml to reconfigure another plug). It is lists the ESPhome name in the ssid - ESPhome Switch Fallback Hotspot

The weirder thing is I can still see the device listed as a client on my router. The IP is inaccessible and it is still named ‘sonoff-4761’ leftover from the tasmota config.

Is there a default password for the captive portal? If not is there a way to reset the switch or reflash it OTA? I jut about destroyed one of these plugs trying to open it when I was having tuya-convert issues so I would prefer not having to crack it open.

1 Like
2

You set the password in the wifi AP setup:

# Example configuration entry
wifi:
  # ...
  ap:
    ssid: "Livingroom Fallback Hotspot"
    password: "W1PBGyrokfLz"

captive_portal:

If you didn’t set a password, it should be blank. But if you are seeing a Sonoff AP, then I would say the flash didn’t complete successfully.

As a last effort, you can try this - it is also listed on the release notes:

When you connect to the fallback network, the web interface should open automatically (see also login to network notifications). If that does not work, you can also navigate to http://192.168.4.1/ manually in your browser.

Good Luck!
DeadEnd

3

That may just mean the IP lease is still in the router’s cache.

1 Like
4

Same here actually. When I updated to new Esphome, the WiFi won’t connect at all. The name sonoff-xxxx was what it was originally named in Tasmota and even though I was running esphome on this one (a nodemcu) it was reporting the same name in the router with Esphome.

But the new Esphome - It won’t connect to Wifi at all even though it was working great before today with the old version. The captive-portal and AP I setup and it sees that but won’t connect either when I try to connect with my phone. If I reflash Tasmota again it instantly connects. It seems this is a common problem when you look at the Esphome issues forum with no solution. So if I was you, I’d jus use Tasmota which will work. In my case I’m trying to use it with a LCD display and don’t think that’s an option (it actually probably is but I need to research it to find out)

5

It happened to me on a Sonoff basic, it was a PITA since I had to reflash it manually (captive portal was not on old firmware yet).
I think that the " (double quote) should be avoided and used just the ’ (single one). I changed every configuration to avoid using double quote and it never happened again.

1 Like