Connecting to Wifi Post update

ESPHome
1

Hi,

I’ve just updated my ESP Wroom 32 and am now struggling to get it connected to my network.
I have several ESP32s on my network and haven’t had to update them for sometime. However, my instance of ESPHome has remained upto date and am running version 24.8.3 which now means i am unable to communicate (observe logs etc) wirelessly.

Having just attempted to add a binary sensor to one of my ESP 32s I ended up updating it and can no longer connect it to the Wifi.

I have also attempted to flash a new ESP32 but get the same results. Even with a basic config it won’t connect.

Blockquote
esphome:
name: tester
friendly_name: Tester

esp32:
board: esp32dev
framework:
type: arduino

Enable logging

logger:

Enable Home Assistant API

api:
encryption:
key: “HEnNfgzv29zQxnOP/yVXbwQk8ADtR48ya1MfJx5FUVA=”

ota:

  • platform: esphome
    password: “3ed3acbce50af2b5d19a568b2ab4a682”

wifi:
ssid: “myssid”
password: “mypassword”

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: “Tester Fallback Hotspot”
password: “tbg94DM3MmFr”

captive_portal:

Clearly something has changed that I am missing since the latest updates. Any help would be appreciated.

Thanks in advance

2

Please post your yaml properly.

3

On it now mate…just reading back through the guides cheers

1 Like
4 
esphome:
  name: tester
  friendly_name: Tester

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "HEnNfgzv29zQxnOP/yVXbwQk8ADtR48ya1MfJx5FUVA="

ota:
  - platform: esphome
    password: "3ed3acbce50af2b5d19a568b2ab4a682"

wifi:
  ssid: "myssid"
  password: "mypassword"

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Tester Fallback Hotspot"
    password: "tbg94DM3MmFr"

captive_portal:
6

How are you flashing? I presume via serial/USB.

When you do so you get a log, and can download that log. Could you please post it?

7

I can connect fine via USB and flashing always returns as a success. However the log is clearly showing issues connecting to the network

[22:06:57]ets Jun  8 2016 00:22:57
[22:06:57]
[22:06:57]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[22:06:57]configsip: 0, SPIWP:0xee
[22:06:57]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[22:06:57]mode:DIO, clock div:2
[22:06:57]load:0x3fff0030,len:1184
[22:06:57]load:0x40078000,len:13132
[22:06:57]load:0x40080400,len:3036
[22:06:57]entry 0x400805e4
[22:06:57][I][logger:156]: Log initialized
[22:06:57][C][safe_mode:079]: There have been 10 suspected unsuccessful boot attempts
[22:06:57][D][esp32.preferences:114]: Saving 1 preferences to flash...
[22:06:57][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[22:06:57][E][safe_mode:086]: Boot loop detected. Proceeding to safe mode
[22:06:57][E][component:164]: Component safe_mode set Error flag: unspecified
[22:06:57][I][app:029]: Running through setup()...
[22:06:57][C][wifi:048]: Setting up WiFi...
[22:06:57][C][wifi:061]: Starting WiFi...
[22:06:58][C][wifi:062]:   Local MAC: C8:C9:A3:D2:44:40
[22:06:58]
[22:06:58]Brownout detector was triggered
[22:06:58]
[22:06:58]ets Jun  8 2016 00:22:57
[22:06:58]
[22:06:58]rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[22:06:58]configsip: 0, SPIWP:0xee
[22:06:58]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[22:06:58]mode:DIO, clock div:2
[22:06:58]load:0x3fff0030,len:1184
[22:06:58]load:0x40078000,len:13132
[22:06:58]load:0x40080400,len:3036
[22:06:58]entry 0x400805e4
[22:06:58][I][logger:156]: Log initialized
[22:06:58][C][safe_mode:079]: There have been 0 suspected unsuccessful boot attempts
[22:06:58][D][esp32.preferences:114]: Saving 1 preferences to flash...
[22:06:58][D][esp32.preferences:143]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[22:06:58][I][app:029]: Running through setup()...
[22:06:58][C][wifi:048]: Setting up WiFi...
[22:06:58][C][wifi:061]: Starting WiFi...
[22:06:58][C][wifi:062]:   Local MAC: C8:C9:A3:D2:44:40
[22:06:58]
[22:06:58]Brownout detector was triggered
[22:06:58]

Let me know if there’s a better way to post the log
Thanks

1 Like
8

Thanks. Posting is fine.

Brownout detector probably means a power supply issue. Could be crappy USB cable, crappy power being supplied by your computer, faulty esp32.

Recent example I can't get my esp32 connected with esphome on home assistant

1 Like
9

That last line leads me to believe it is a power supply issue. Try a different cable or a powered hub and see if that solves it.

1 Like
10

That seems to have fixed it. I changed the Power supply (old phone charger) and it’s connected now.
Thanks for your help. Hugely appreciated! :slight_smile:

2 Likes