ESPHome sensors disappeared after yaml update

jacoscar · October 28, 2025, 9:31am

I have an esp32 loaded with esphome and connected to various sensors: two contact sensors and a time of flight sensor. Everything was working fine until today I decided to change the interval update for the time of flight sensor from 10s to 18000s. I updated it wirelessly and when it was done none of the sensors were there. I’ve tried removing it and readding it multiple times and reupdating the esphome yaml multiple times, including removing the encryption but nothing worked.

When I look at the device logs I see the sensors working correctly

INFO ESPHome 2025.10.3
INFO Reading configuration /config/esphome/esphome-web-f91e88.yaml…
INFO Starting log output from 192.168.0.226 using esphome API
INFO Successfully resolved esphome-web-f91e88 @ 192.168.0.226 in 0.000s
INFO Successfully connected to esphome-web-f91e88 @ 192.168.0.226 in 0.113s
INFO Successful handshake with esphome-web-f91e88 @ 192.168.0.226 in 0.083s
[08:37:44.297][I][app:185]: ESPHome version 2025.10.3 compiled on Oct 27 2025, 15:55:41
[08:37:44.301][C][wifi:679]: WiFi:
[08:37:44.303][C][wifi:458]: Local MAC: 24:0A:C4:F9:1E:88
[08:37:44.306][C][wifi:465]: IP Address: 192.168.0.226
[08:37:44.313][C][wifi:469]: SSID: [redacted]
[08:37:44.313][C][wifi:469]: BSSID: [redacted]
[08:37:44.313][C][wifi:469]: Hostname: ‘esphome-web-f91e88’
[08:37:44.313][C][wifi:469]: Signal strength: -44 dB ▂▄▆█
[08:37:44.313][C][wifi:469]: Channel: 1
[08:37:44.313][C][wifi:469]: Subnet: 255.255.255.0
[08:37:44.313][C][wifi:469]: Gateway: 192.168.0.1
[08:37:44.313][C][wifi:469]: DNS1: 192.168.0.1
[08:37:44.313][C][wifi:469]: DNS2: 0.0.0.0
[08:37:44.317][C][logger:261]: Logger:
[08:37:44.317][C][logger:261]: Max Level: DEBUG
[08:37:44.317][C][logger:261]: Initial Level: DEBUG
[08:37:44.326][C][logger:267]: Log Baud Rate: 115200
[08:37:44.326][C][logger:267]: Hardware UART: UART0
[08:37:44.344][C][logger:274]: Task Log Buffer Size: 768
[08:37:44.344][C][i2c.arduino:072]: I2C Bus:
[08:37:44.345][C][i2c.arduino:073]: SDA Pin: GPIO21
[08:37:44.345][C][i2c.arduino:073]: SCL Pin: GPIO22
[08:37:44.345][C][i2c.arduino:073]: Frequency: 50000 Hz
[08:37:44.353][C][i2c.arduino:089]: Recovery: bus successfully recovered
[08:37:44.357][I][i2c.arduino:099]: Results from bus scan:
[08:37:44.360][I][i2c.arduino:105]: Found device at address 0x29
[08:37:44.383][C][gpio.binary_sensor:016]: GPIO Binary Sensor ‘Overflow_sensor’
[08:37:44.386][C][gpio.binary_sensor:072]: Pin: GPIO17
[08:37:44.392][C][gpio.binary_sensor:073]: Mode: interrupt
[08:37:44.396][C][gpio.binary_sensor:075]: Interrupt Type: ANY_EDGE
[08:37:44.397][C][gpio.binary_sensor:016]: GPIO Binary Sensor ‘Drain_sensor’
[08:37:44.400][C][gpio.binary_sensor:072]: Pin: GPIO16
[08:37:44.408][C][gpio.binary_sensor:073]: Mode: interrupt
[08:37:44.409][C][gpio.binary_sensor:075]: Interrupt Type: ANY_EDGE
[08:37:44.417][C][vl53l0x:015]: VL53L0X ‘VL53L0x Distance’
[08:37:44.417][C][vl53l0x:015]: State Class: ‘measurement’
[08:37:44.417][C][vl53l0x:015]: Unit of Measurement: ‘m’
[08:37:44.417][C][vl53l0x:015]: Accuracy Decimals: 2
[08:37:44.420][C][vl53l0x:029]: Icon: ‘mdi:arrow-expand-vertical’
[08:37:44.428][C][vl53l0x:362]: Update Interval: 10.0s
[08:37:44.437][C][vl53l0x:026]: Address: 0x29
[08:37:44.441][C][vl53l0x:030]: Timeout: 10000us
[08:37:44.444][C][vl53l0x:031]: Timing Budget 33971us
[08:37:44.466][C][captive_portal:116]: Captive Portal:
[08:37:44.477][C][esphome.ota:093]: Over-The-Air updates:
[08:37:44.477][C][esphome.ota:093]: Address: esphome-web-f91e88.local:3232
[08:37:44.477][C][esphome.ota:093]: Version: 2
[08:37:44.488][C][safe_mode:018]: Safe Mode:
[08:37:44.488][C][safe_mode:018]: Successful after: 60s
[08:37:44.488][C][safe_mode:018]: Invoke after: 10 attempts
[08:37:44.488][C][safe_mode:018]: Duration: 300s
[08:37:44.498][C][web_server.ota:241]: Web Server OTA
[08:37:44.509][C][api:222]: Server:
[08:37:44.509][C][api:222]: Address: esphome-web-f91e88.local:6053
[08:37:44.509][C][api:222]: Listen backlog: 4
[08:37:44.509][C][api:222]: Max connections: 8
[08:37:44.511][C][api:229]: Noise encryption: YES
[08:37:44.516][C][mdns:179]: mDNS:
[08:37:44.516][C][mdns:179]: Hostname: esphome-web-f91e88
[08:37:47.472][D][vl53l0x:310]: ‘VL53L0x Distance’ - Got distance 0.258 m
[08:37:47.476][D][sensor:131]: ‘VL53L0x Distance’: Sending state 0.25800 m with 2 decimals of accuracy
[08:37:51.880][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:51.905][D][api:160]: Accept 192.168.0.123
[08:37:51.912][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:51.946][D][api:160]: Accept 192.168.0.123
[08:37:51.954][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:52.887][D][api:160]: Accept 192.168.0.12
[08:37:52.955][D][api.connection:1383]: Home Assistant 2025.3.0 (192.168.0.12) connected
[08:37:53.000][D][api:160]: Accept 192.168.0.123
[08:37:53.000][D][api:160]: Accept 192.168.0.123
[08:37:53.004][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:53.017][D][api:160]: Accept 192.168.0.116
[08:37:53.024][D][api:160]: Accept 192.168.0.116
[08:37:53.033][W][api.connection:1880]: 192.168.0.116 (192.168.0.116): Socket operation failed BAD_INDICATOR errno=11
[08:37:54.135][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:54.143][W][api.connection:1880]: 192.168.0.116 (192.168.0.116): Socket operation failed BAD_INDICATOR errno=11
[08:37:54.147][D][api:160]: Accept 192.168.0.116
[08:37:54.152][D][api:160]: Accept 192.168.0.123
[08:37:54.160][W][api.connection:1880]: 192.168.0.123 (192.168.0.123): Socket operation failed BAD_INDICATOR errno=11
[08:37:54.167][W][api.connection:1880]: 192.168.0.116 (192.168.0.116): Socket operation failed BAD_INDICATOR errno=11
[08:37:54.176][D][api:160]: Accept 192.168.0.123
[08:37:54.184][D][api:160]: Accept 192.168.0.116
[08:37:54.188][W][api.connection:1880]: 192.168.0.116 (192.168.0.116): Socket operation failed BAD_INDICATOR errno=11

Protoncek · October 28, 2025, 9:58am

It seems that HA doesn’t connect to your module. What are your API settings in yaml? Do you still use password? I think it’s been removed, you need to use encryption key now:
https://community.home-assistant.io/t/solved-reading-failed-bad-indicator-errno-11-after-esphome-2023-3-0-upgrade/550228/7

jacoscar · October 28, 2025, 10:08am

192.168.0.116 and 192.168.0.123 seems to be the ip addresses of the computers I’m using to connect to home assistant, but home assistant itself runs on 192.168.0.12

this is my yaml (redacted passwords and encryption key)

This is actually my only esphome device with an encription key, but I also haven’t updated the other ones in a while.
When I remove it and readd it, I’m not asked for an encryption key at all by the way


esphome:
  name: esphome-web-f91e88
  friendly_name: ESPHomeWebWaterSoftener

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

ota:
  - platform: esphome

# Enable Home Assistant API
api:
  encryption:
    key: "***************************s="




wifi:
  ssid: !secret wifi_ssid
  password: !secret wifi_password

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esphome-Web-F91E88"
    password: "3*********b"

captive_portal:
    

binary_sensor:
  - platform: gpio
    pin:
      number: 17
      mode:
        input: true
        pulldown: true
    name: Overflow_sensor
  - platform: gpio
    pin:
      number: 16
      mode:
        input: true
        pulldown: true
    name: Drain_sensor


# Individual sensors
# Simple configuration entry example
sensor:
  - platform: vl53l0x
    name: "VL53L0x Distance"
    address: 0x29
    update_interval: 10s
    long_range: false

i2c:
  sda: GPIO21
  scl: GPIO22
  scan: true
  id: bus_a
```

Protoncek · October 28, 2025, 1:52pm

Strange… try to reboot HA, or even restart device/VM/docker where HA runs. Sometimes it helps. One other thing would be change IP of this esp module - set a static one. Having DHCP for esphome modules is not a good idea in any case.

jacoscar · October 28, 2025, 2:20pm

Home assistant runs on a NUC, and I’ve already restarted HA.

I see this error (192.168.0.12 is HA)
[W] [api.connection:1880] Home Assistant 2025.3.0 (192.168.0.12): Reading failed CONNECTION_CLOSED errno=128

Protoncek · October 28, 2025, 3:18pm

Try to change esphome’s name and see if HA will find a new device and connect to it

jacoscar · October 30, 2025, 8:49am

I’ve tried deleting the device from EspHome builder and readd it from scratch, same issue

Here’s what I’ve done

clicked “delete” here

clicked “add new device” and download the bin file

open EspHome and select “install”, not “prepare for first use”
click connect, press the boot button on the device and then install, after 2 minutes it shows as done

The device was showing here with the “reconfigure” button highlighted, so I clicked it

it shows like this

mmm, wait, let me add the sensors in the yaml and reinstall wirelessly… no, still not showing any sensors

and this is what the logs show

jacoscar · October 30, 2025, 9:44am

Update, I updated Home Assistant and it just works fine now