Can't add ESPhome integration

WallyR · January 27, 2023, 12:27am

God this problem is annoying.

The first you need to do is make sure you only use a basic ESP device with no extra attached, like no sensors.
The yaml config needs to be the most simple, which is

esphome:
  name: esptest
  platform: ESP32
  board: esp32dev

wifi:
  ssid: <insert your ssid>
  password: <insert your wifi password
  manual_ip:
    static_ip: 192.168.0.<choose an unused number that can not be pinged before flashing and not 229 or another number you used before!>
    gateway: 192.168.0.1
    subnet: 255.255.255.0

  logger:

  api:

  webserver:
    port: 80

This should set up an ESP device with the most basic settings and you should be able to ping it once it is online.

Then check your router that no wifi segregation is enabled or guest network or private devices or similar, which might stop devices from communicating with each other.
Once that is done, then restart your router, access points and HA host (not just the core, but the entire host by going Settings → System → Hardware → 3 dots in upper right corner → Reboot system)

This should reset your network, if something messed up the different caches in network devices and services.

Then check that you can still ping the ESP device and when you disconnect the power to the ESP device, then the ping stops.

If that happens, then see if you can connect with a browser to port 80 on the IP you have chosen.

tom_l · January 27, 2023, 2:08am

I gave up repeatedly asking for that.

WallyR · January 27, 2023, 2:28am

I do not think there is an OTA case here at all.
The flashing seems to be done with USB and then the connection fails with everything but a ping, so OTA, logger and webserver is void from other devices.
We only have the serial port output if there is a serial port connected and then the attempts to fix the network where the issue most likely is located.

WallyR · January 27, 2023, 2:29am

You are using ESPHome Flasher, so you should use the Legacy format, just like the text below “Legacy Format” says.

tom_l · January 27, 2023, 3:03am

Which I also repeatedly said:

We are going in circles because Rob is not listening to our help. I’m out.

Rob_Heselwood · January 27, 2023, 8:38am

@tom_l ,
I did also select legacy format as well, but it made no difference. It’s not just you going round in circles, I am as well, I just neglected to say so

Rob_Heselwood · January 27, 2023, 9:01am

Using 'COM7' as serial port.
Writing at 0x000f5ee7... (100 %)Wrote 952528 bytes (630259 compressed) at 0x00010000 in 17.7 seconds (effective 431.1 kbit/s)...
Hash of data verified.

Leaving...
Hard Resetting...
Hard resetting via RTS pin...
Done! Flashing is complete!

Showing logs:
[08:41:29][I][logger:258]: Log initialized
[08:41:29][C][ota:469]: There have been 0 suspected unsuccessful boot attempts.
[08:41:29][D][esp32.preferences:113]: Saving 1 preferences to flash...
[08:41:29][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[08:41:29][I][app:029]: Running through setup()...
[08:41:29][I][i2c.arduino:175]: Performing I2C bus recovery
[08:41:29][C][bh1750.sensor:041]: Setting up BH1750 'BH1750 Illuminance'...
[08:41:29][E][component:113]: Component bh1750.sensor was marked as failed.
[08:41:29][C][bme280.sensor:086]: Setting up BME280...
[08:41:29][E][component:113]: Component bme280.sensor was marked as failed.
[08:41:29][C][wifi:037]: Setting up WiFi...
[08:41:29][C][wifi:038]:   Local MAC: 24:62:AB:F3:0B:70
[08:41:29][D][wifi:386]: Starting scan...
[08:41:35][D][wifi:401]: Found networks:
[08:41:35][I][wifi:445]: - 'TP-Link_0EEB' (46:D9:E7:A5:A5:19) ▂▄▆█
[08:41:35][D][wifi:446]:     Channel: 6
[08:41:35][D][wifi:447]:     RSSI: -47 dB
[08:41:35][I][wifi:445]: - 'TP-Link_0EEB' (E0:63:DA:B7:7B:B0) ▂▄▆█
[08:41:35][D][wifi:446]:     Channel: 6
[08:41:35][D][wifi:447]:     RSSI: -86 dB
[08:41:35][D][wifi:450]: - 'TP-Link_0EE8' (34:60:F9:A5:0E:E8) ▂▄▆█
[08:41:35][D][wifi:450]: - 'TP-Link_Guest_0EE8' (36:60:F9:A5:0E:E8) ▂▄▆█
[08:41:35][D][wifi:450]: - '' (56:60:F9:A5:0E:E8) ▂▄▆█
[08:41:35][D][wifi:450]: - 'TP-Link_0EE8_EXT' (C8:3A:35:32:FA:C1) ▂▄▆█
[08:41:35][D][wifi:450]: - 'NVR9ca3a962b42c' (9C:A3:A9:62:B4:2C) ▂▄▆█
[08:41:35][D][wifi:450]: - 'TP-Link_0EE8_2GEXT' (08:36:C9:9E:E3:E8) ▂▄▆█
[08:41:35][D][wifi:450]: - 'BT-R7CT8R' (A8:A2:37:8B:B9:A1) ▂▄▆█
[08:41:35][D][wifi:450]: - 'BTWi-fi' (6A:A2:37:8B:B9:A2) ▂▄▆█
[08:41:35][D][wifi:450]: - '' (6A:A2:37:8B:B9:A5) ▂▄▆█
[08:41:35][I][wifi:257]: WiFi Connecting to 'TP-Link_0EEB'...
[08:41:36][I][wifi:518]: WiFi Connected!
[08:41:36][C][wifi:362]:   Local MAC: 24:62:AB:F3:0B:70
[08:41:36][C][wifi:363]:   SSID: 'TP-Link_0EEB'
[08:41:36][C][wifi:364]:   IP Address: 192.168.0.229
[08:41:36][C][wifi:366]:   BSSID: 46:D9:E7:A5:A5:19
[08:41:36][C][wifi:367]:   Hostname: 'home'
[08:41:36][C][wifi:369]:   Signal strength: -48 dB ▂▄▆█
[08:41:36][C][wifi:373]:   Channel: 6
[08:41:36][C][wifi:374]:   Subnet: 255.255.255.0
[08:41:36][C][wifi:375]:   Gateway: 192.168.0.1
[08:41:36][C][wifi:376]:   DNS1: 0.0.0.0
[08:41:36][C][wifi:377]:   DNS2: 0.0.0.0
[08:41:36][C][web_server:092]: Setting up web server...
[08:41:36][C][ota:093]: Over-The-Air Updates:
[08:41:36][C][ota:094]:   Address: 192.168.0.229:3232
[08:41:36][C][ota:097]:   Using Password.
[08:41:36][C][api:025]: Setting up Home Assistant API server...
[08:41:36][I][app:062]: setup() finished successfully!
[08:41:36][I][app:102]: ESPHome version 2022.12.7 compiled on Jan 26 2023, 17:23:06
[08:41:36][C][wifi:504]: WiFi:
[08:41:36][C][wifi:362]:   Local MAC: 24:62:AB:F3:0B:70
[08:41:36][C][wifi:363]:   SSID: 'TP-Link_0EEB'
[08:41:36][C][wifi:364]:   IP Address: 192.168.0.229
[08:41:36][C][wifi:366]:   BSSID: 46:D9:E7:A5:A5:19
[08:41:36][C][wifi:367]:   Hostname: 'home'
[08:41:36][C][wifi:369]:   Signal strength: -48 dB ▂▄▆█
[08:41:36][C][wifi:373]:   Channel: 6
[08:41:36][C][wifi:374]:   Subnet: 255.255.255.0
[08:41:36][C][wifi:375]:   Gateway: 192.168.0.1
[08:41:36][C][wifi:376]:   DNS1: 0.0.0.0
[08:41:36][C][wifi:377]:   DNS2: 0.0.0.0
[08:41:36][C][logger:293]: Logger:
[08:41:36][C][logger:294]:   Level: DEBUG
[08:41:36][C][logger:295]:   Log Baud Rate: 115200
[08:41:36][C][logger:296]:   Hardware UART: UART0
[08:41:36][C][i2c.arduino:052]: I2C Bus:
[08:41:36][C][i2c.arduino:053]:   SDA Pin: GPIO21
[08:41:36][C][i2c.arduino:054]:   SCL Pin: GPIO22
[08:41:36][C][i2c.arduino:055]:   Frequency: 50000 Hz
[08:41:36][C][i2c.arduino:058]:   Recovery: bus successfully recovered
[08:41:36][C][bh1750.sensor:118]: BH1750 'BH1750 Illuminance'
[08:41:36][C][bh1750.sensor:118]:   Device Class: 'illuminance'
[08:41:36][C][bh1750.sensor:118]:   State Class: 'measurement'
[08:41:36][C][bh1750.sensor:118]:   Unit of Measurement: 'lx'
[08:41:36][C][bh1750.sensor:118]:   Accuracy Decimals: 1
[08:41:36][C][bh1750.sensor:119]:   Address: 0x23
[08:41:36][E][bh1750.sensor:121]: Communication with BH1750 failed!
[08:41:36][C][bh1750.sensor:124]:   Update Interval: 60.0s
[08:41:36][C][bme280.sensor:177]: BME280:
[08:41:36][C][bme280.sensor:178]:   Address: 0x77
[08:41:36][E][bme280.sensor:181]: Communication with BME280 failed!
[08:41:36][C][bme280.sensor:190]:   IIR Filter: OFF
[08:41:36][C][bme280.sensor:191]:   Update Interval: 60.0s
[08:41:36][C][bme280.sensor:193]:   Temperature 'BME280 Temperature'
[08:41:36][C][bme280.sensor:193]:     Device Class: 'temperature'
[08:41:36][C][bme280.sensor:193]:     State Class: 'measurement'
[08:41:36][C][bme280.sensor:193]:     Unit of Measurement: '°C'
[08:41:36][C][bme280.sensor:193]:     Accuracy Decimals: 1
[08:41:36][C][bme280.sensor:194]:     Oversampling: 16x
[08:41:36][C][bme280.sensor:195]:   Pressure 'BME280 Pressure'
[08:41:36][C][bme280.sensor:195]:     Device Class: 'pressure'
[08:41:36][C][bme280.sensor:195]:     State Class: 'measurement'
[08:41:36][C][bme280.sensor:195]:     Unit of Measurement: 'hPa'
[08:41:36][C][bme280.sensor:195]:     Accuracy Decimals: 1
[08:41:36][C][bme280.sensor:196]:     Oversampling: 16x
[08:41:36][C][bme280.sensor:197]:   Humidity 'BME280 Humidity'
[08:41:36][C][bme280.sensor:197]:     Device Class: 'humidity'
[08:41:36][C][bme280.sensor:197]:     State Class: 'measurement'
[08:41:36][C][bme280.sensor:197]:     Unit of Measurement: '%'
[08:41:36][C][bme280.sensor:197]:     Accuracy Decimals: 1
[08:41:36][C][bme280.sensor:198]:     Oversampling: 16x
[08:41:36][C][captive_portal:088]: Captive Portal:
[08:41:36][C][web_server:125]: Web Server:
[08:41:36][C][web_server:126]:   Address: 192.168.0.229:80
[08:41:36][C][mdns:103]: mDNS:
[08:41:36][C][mdns:104]:   Hostname: home
[08:41:36][C][ota:093]: Over-The-Air Updates:
[08:41:36][C][ota:094]:   Address: 192.168.0.229:3232
[08:41:36][C][ota:097]:   Using Password.
[08:41:37][C][api:138]: API Server:
[08:41:37][C][api:139]:   Address: 192.168.0.229:6053
[08:41:37][C][api:141]:   Using noise encryption: YES
[08:42:06]ets Jun  8 2016 00:22:57
[08:42:06]
[08:42:06]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[08:42:06]configsip: 0, SPIWP:0xee
[08:42:06]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[08:42:06]mode:DIO, clock div:2
[08:42:06]load:0x3fff0018,len:4
[08:42:06]load:0x3fff001c,len:1044
[08:42:06]load:0x40078000,len:8896
[08:42:06]load:0x40080400,len:5828
[08:42:06]entry 0x400806ac
[08:42:07][I][logger:258]: Log initialized
[08:42:07][C][ota:469]: There have been 1 suspected unsuccessful boot attempts.
[08:42:07][D][esp32.preferences:113]: Saving 1 preferences to flash...
[08:42:07][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[08:42:07][I][app:029]: Running through setup()...
[08:42:07][I][i2c.arduino:175]: Performing I2C bus recovery
[08:42:07][C][bh1750.sensor:041]: Setting up BH1750 'BH1750 Illuminance'...
[08:42:07][E][component:113]: Component bh1750.sensor was marked as failed.
[08:42:07][C][bme280.sensor:086]: Setting up BME280...
[08:42:07][E][component:113]: Component bme280.sensor was marked as failed.
[08:42:07][C][wifi:037]: Setting up WiFi...
[08:42:07][C][wifi:038]:   Local MAC: 24:62:AB:F3:0B:70
[08:42:07][D][wifi:386]: Starting scan...
[08:42:13][D][wifi:401]: Found networks:
[08:42:13][I][wifi:445]: - 'TP-Link_0EEB' (46:D9:E7:A5:A5:19) ▂▄▆█
[08:42:13][D][wifi:446]:     Channel: 6
[08:42:13][D][wifi:447]:     RSSI: -48 dB
[08:42:13][D][wifi:450]: - 'TP-Link_0EE8' (34:60:F9:A5:0E:E8) ▂▄▆█
[08:42:13][D][wifi:450]: - 'TP-Link_Guest_0EE8' (36:60:F9:A5:0E:E8) ▂▄▆█
[08:42:13][D][wifi:450]: - '' (56:60:F9:A5:0E:E8) ▂▄▆█
[08:42:13][D][wifi:450]: - 'TP-Link_0EE8_2GEXT' (08:36:C9:9E:E3:E8) ▂▄▆█
[08:42:13][D][wifi:450]: - 'TP-Link_0EE8_EXT' (C8:3A:35:32:FA:C1) ▂▄▆█
[08:42:13][D][wifi:450]: - 'NVR9ca3a962b42c' (9C:A3:A9:62:B4:2C) ▂▄▆█
[08:42:13][D][wifi:450]: - 'BT-R7CT8R' (A8:A2:37:8B:B9:A1) ▂▄▆█
[08:42:13][D][wifi:450]: - 'BTWi-fi' (6A:A2:37:8B:B9:A2) ▂▄▆█
[08:42:13][D][wifi:450]: - '' (6A:A2:37:8B:B9:A5) ▂▄▆█
[08:42:13][I][wifi:257]: WiFi Connecting to 'TP-Link_0EEB'...
[08:42:14][I][wifi:518]: WiFi Connected!
[08:42:14][C][wifi:362]:   Local MAC: 24:62:AB:F3:0B:70
[08:42:14][C][wifi:363]:   SSID: 'TP-Link_0EEB'
[08:42:14][C][wifi:364]:   IP Address: 192.168.0.229
[08:42:14][C][wifi:366]:   BSSID: 46:D9:E7:A5:A5:19
[08:42:14][C][wifi:367]:   Hostname: 'home'
[08:42:14][C][wifi:369]:   Signal strength: -46 dB ▂▄▆█
[08:42:14][C][wifi:373]:   Channel: 6
[08:42:14][C][wifi:374]:   Subnet: 255.255.255.0
[08:42:14][C][wifi:375]:   Gateway: 192.168.0.1
[08:42:14][C][wifi:376]:   DNS1: 0.0.0.0
[08:42:14][C][wifi:377]:   DNS2: 0.0.0.0
[08:42:14][C][web_server:092]: Setting up web server...
[08:42:14][C][ota:093]: Over-The-Air Updates:
[08:42:14][C][ota:094]:   Address: 192.168.0.229:3232
[08:42:14][C][ota:097]:   Using Password.
[08:42:14][C][api:025]: Setting up Home Assistant API server...
[08:42:14][I][app:062]: setup() finished successfully!
[08:42:14][I][app:102]: ESPHome version 2022.12.7 compiled on Jan 26 2023, 17:23:06
[08:42:14][C][wifi:504]: WiFi:
[08:42:14][C][wifi:362]:   Local MAC: 24:62:AB:F3:0B:70
[08:42:14][C][wifi:363]:   SSID: 'TP-Link_0EEB'
[08:42:14][C][wifi:364]:   IP Address: 192.168.0.229
[08:42:14][C][wifi:366]:   BSSID: 46:D9:E7:A5:A5:19
[08:42:14][C][wifi:367]:   Hostname: 'home'
[08:42:14][C][wifi:369]:   Signal strength: -48 dB ▂▄▆█
[08:42:14][C][wifi:373]:   Channel: 6
[08:42:14][C][wifi:374]:   Subnet: 255.255.255.0
[08:42:14][C][wifi:375]:   Gateway: 192.168.0.1
[08:42:14][C][wifi:376]:   DNS1: 0.0.0.0
[08:42:14][C][wifi:377]:   DNS2: 0.0.0.0
[08:42:14][C][logger:293]: Logger:
[08:42:14][C][logger:294]:   Level: DEBUG
[08:42:14][C][logger:295]:   Log Baud Rate: 115200
[08:42:14][C][logger:296]:   Hardware UART: UART0
[08:42:14][C][i2c.arduino:052]: I2C Bus:
[08:42:14][C][i2c.arduino:053]:   SDA Pin: GPIO21
[08:42:14][C][i2c.arduino:054]:   SCL Pin: GPIO22
[08:42:14][C][i2c.arduino:055]:   Frequency: 50000 Hz
[08:42:14][C][i2c.arduino:058]:   Recovery: bus successfully recovered
[08:42:14][C][bh1750.sensor:118]: BH1750 'BH1750 Illuminance'
[08:42:14][C][bh1750.sensor:118]:   Device Class: 'illuminance'
[08:42:14][C][bh1750.sensor:118]:   State Class: 'measurement'
[08:42:14][C][bh1750.sensor:118]:   Unit of Measurement: 'lx'
[08:42:14][C][bh1750.sensor:118]:   Accuracy Decimals: 1
[08:42:14][C][bh1750.sensor:119]:   Address: 0x23
[08:42:14][E][bh1750.sensor:121]: Communication with BH1750 failed!
[08:42:14][C][bh1750.sensor:124]:   Update Interval: 60.0s
[08:42:14][C][bme280.sensor:177]: BME280:
[08:42:14][C][bme280.sensor:178]:   Address: 0x77
[08:42:14][E][bme280.sensor:181]: Communication with BME280 failed!
[08:42:14][C][bme280.sensor:190]:   IIR Filter: OFF
[08:42:14][C][bme280.sensor:191]:   Update Interval: 60.0s
[08:42:14][C][bme280.sensor:193]:   Temperature 'BME280 Temperature'
[08:42:14][C][bme280.sensor:193]:     Device Class: 'temperature'
[08:42:14][C][bme280.sensor:193]:     State Class: 'measurement'
[08:42:14][C][bme280.sensor:193]:     Unit of Measurement: '°C'
[08:42:14][C][bme280.sensor:193]:     Accuracy Decimals: 1
[08:42:14][C][bme280.sensor:194]:     Oversampling: 16x
[08:42:14][C][bme280.sensor:195]:   Pressure 'BME280 Pressure'
[08:42:14][C][bme280.sensor:195]:     Device Class: 'pressure'
[08:42:14][C][bme280.sensor:195]:     State Class: 'measurement'
[08:42:14][C][bme280.sensor:195]:     Unit of Measurement: 'hPa'
[08:42:14][C][bme280.sensor:195]:     Accuracy Decimals: 1
[08:42:14][C][bme280.sensor:196]:     Oversampling: 16x
[08:42:14][C][bme280.sensor:197]:   Humidity 'BME280 Humidity'
[08:42:14][C][bme280.sensor:197]:     Device Class: 'humidity'
[08:42:14][C][bme280.sensor:197]:     State Class: 'measurement'
[08:42:14][C][bme280.sensor:197]:     Unit of Measurement: '%'
[08:42:14][C][bme280.sensor:197]:     Accuracy Decimals: 1
[08:42:14][C][bme280.sensor:198]:     Oversampling: 16x
[08:42:14][C][captive_portal:088]: Captive Portal:
[08:42:14][C][web_server:125]: Web Server:
[08:42:14][C][web_server:126]:   Address: 192.168.0.229:80
[08:42:14][C][mdns:103]: mDNS:
[08:42:14][C][mdns:104]:   Hostname: home
[08:42:14][C][ota:093]: Over-The-Air Updates:
[08:42:14][C][ota:094]:   Address: 192.168.0.229:3232
[08:42:14][C][ota:097]:   Using Password.
[08:42:14][C][api:138]: API Server:
[08:42:14][C][api:139]:   Address: 192.168.0.229:6053
[08:42:14][C][api:141]:   Using noise encryption: YES
[08:46:47]ets Jun  8 2016 00:22:57
[08:46:47]
[08:46:47]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[08:46:47]configsip: 0, SPIWP:0xee
[08:46:47]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[08:46:47]mode:DIO, clock div:2
[08:46:47]load:0x3fff0018,len:4
[08:46:47]load:0x3fff001c,len:1044
[08:46:47]load:0x40078000,len:8896
[08:46:47]load:0x40080400,len:5828
[08:46:47]entry 0x400806ac
[08:46:47][I][logger:258]: Log initialized
[08:46:47][C][ota:469]: There have been 2 suspected unsuccessful boot attempts.
[08:46:47][D][esp32.preferences:113]: Saving 1 preferences to flash...
[08:46:47][D][esp32.preferences:142]: Saving 1 preferences to flash: 0 cached, 1 written, 0 failed
[08:46:47][I][app:029]: Running through setup()...
[08:46:47][I][i2c.arduino:175]: Performing I2C bus recovery
[08:46:47][C][bh1750.sensor:041]: Setting up BH1750 'BH1750 Illuminance'...
[08:46:47][E][component:113]: Component bh1750.sensor was marked as failed.
[08:46:47][C][bme280.sensor:086]: Setting up BME280...
[08:46:47][E][component:113]: Component bme280.sensor was marked as failed.
[08:46:47][C][wifi:037]: Setting up WiFi...
[08:46:47][C][wifi:038]:   Local MAC: 24:62:AB:F3:0B:70
[08:46:47][D][wifi:386]: Starting scan...
[08:46:53]
Serial port closed!

Rob_Heselwood · January 27, 2023, 9:08am

It seems it doesn’t matter what I do or don’t do, and how I flash the board with either esphome-flasher or esp web, it all comes down to the same problem as I see it.

‘Can’t connect to ESP. Please make sure your YAML file contains an ‘api:’ line.’

tom_l · January 27, 2023, 9:16am

Thank you. Those logs are what we have been after for a long time.

Your device is successfully connecting to wifi but is then boot looping (resetting and starting again).

[08:46:47]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)

[08:46:47][C][ota:469]: There have been 2 suspected unsuccessful boot attemp

You likely have a bad power supply, or you may have something connected to a boot-strapping pin. See: ESP32 Pinout Reference: Which GPIO pins should you use? | Random Nerd Tutorials

Rob_Heselwood · January 27, 2023, 12:30pm

First , the pins that I am using for sda and scl are the ones I have always used when I first started 2 years ago, and there were no problems then. It only took me about 2 days to get it all up and running.

Also there are a few different esp32-wroom-32 boards, and to be honest it’s a bit of a minefield for me to make sure I do actually have the right pins. Again I am not sure if I should use GPIO21 in the yaml file or just 21 etc. I do have

i2c:
  - id: i2c_bus
    sda: 21
    scl: 22
    scan: false

The esp32 board was plugged into my laptop usb port, and I have also tried in my linux desktop usb port as well as a usb to 3 pin adaptor socket. They can’t all be bad, can they.
Since I last flashed the board with esphome-flasher, the led now doesn’t blink / flash now, except when I reset it.

So is it a case of a bad board.

Thanks

tom_l · January 27, 2023, 12:38pm

“Bad power supply” could also mean the 3.3v LDO (low drop-out) voltage regulator on the board. Or bad filter caps. The cheap Chinese clones are notorious for this. See this topic for some recommendations of good boards: What's your favourite ESP32 board? (# Best, good, cheap, quality, reliable)

As long as you have the board definition correct it does not matter if you use 21 or GPIO21.

Rob_Heselwood · January 27, 2023, 1:21pm

I measured the voltage from the usb port a few days ago, and it was reading 5.08v to the esp32 board., but I take your point about LDO. Mine is an AZ Delivery ESP32-WROOM-32, and I’m loath to buy another of those so I have just bought these:
ESP32 ESP-32S Development Board 2.4 GHz Dual Core WLAN WiFi + Bluetooth 2-In-1 Microcontroller ESP-WROOM-32 Chip CP2102 for Arduino (3PCS)

These look like they are in the list of board , in the link you gave.

Thanks

tom_l · January 27, 2023, 1:33pm

If you have a fast voltage meter or a DSO measure the 3.3V voltage rail while it is running.

WallyR · January 27, 2023, 1:48pm

You can’t really say that until you disconnects your sensors and other stuff and see the behavior without those connected.
They could easily be bugged too.

Rob_Heselwood · January 27, 2023, 1:52pm

I measured the voltage on the 3.3v rail while it was both in the usb port on laptop and in the usb mains adaptor, and it was fairly stable at 3.3v for a god few minutes. the led was not flashing tho’ so I do suspect the board is duff.

tom_l · January 27, 2023, 1:58pm

If you only measured it with a multimeter it won’t be fast enough to catch transients.

Rob_Heselwood · January 27, 2023, 2:26pm

Well that is all I have. It’s an old Fluke 77 meter which I’ve had for a long time. Anyway my new board should be here tomorrow so we’ll see how that goes.

aceindy · January 27, 2023, 2:51pm

Just disconnect all extenal IO, and see what happens.
There could be something wrong in there, causing it to fail when initialized

Rob_Heselwood · January 27, 2023, 5:02pm

I removed the esp32 board from the breadboard I had it on, and flashed it again with same file as I used earlier, but it made no difference.
All I had was the esp32 at the end of a usb lead.

orange-assistant · January 27, 2023, 5:45pm

So it still boot loops with no (external) hardware attached?

Showing this in the logs again?

Rob_Heselwood:

[08:42:06]rst:0x1 (POWERON_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
[08:42:06]configsip: 0, SPIWP:0xee
[08:42:06]clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
[08:42:06]mode:DIO, clock div:2
[08:42:06]load:0x3fff0018,len:4
[08:42:06]load:0x3fff001c,len:1044
[08:42:06]load:0x40078000,len:8896
[08:42:06]load:0x40080400,len:5828
[08:42:06]entry 0x400806ac

To rule out (or confirm) a hardware defect you can create a minimal yaml file with only the basics and flash this to the esp to see if it comes up normal or continues to boot loop (which will be a good indication that it is a hardware fault).

A minimal yaml can look like this:

esphome:
  name: minota
  platform: ESP32
  board: esp32dev

wifi:
  networks:
  - ssid: 'YOURSSIDHERE'
    password: 'YOURPASSWORDHERE'

ota:

logger:

As a site node there is no api: line in that yaml so you can’t connect it to HA that way. It is just to see if a minimal firmware is able to run stable or if that also causes boot loops