Newly Added ESPHome Device Missing from Home Assistance

Hello Guys,

I am having some issues getting a newly configured ESPHome device to appear in Home Assistant.

The device is set up in ESPHome no issues are reported, I can see it is online and I can connect to the device without issue, when doing so it produces a log output a expected.

When I went into HA I could see the device had been auto-discovered, I clicked the configure button which then prompted me for the encryption key, which I provided and it told me the device had been added successfully. However when I checked the list of devices under the ESPHome section in HA the device is not listed.

I tried searching through all my devices and entities but couldn’t find anything, at this point I assumed it was unsuccessful and I attempted to manually adde the device.

however I am presented with the following error when doing so:

I can’t find any reference of the device anywhere so unsure how to correctly remove it to attempt to re-add it.

I have rebooted Home Assistant and ESPHome, both of these are running in docker containers if that matters:

Home Assistant Core : 2024.2.1
ESPHome: 2023.12.9

Device Config:

  name: pantry-fabric-softener-monitor
  friendly_name: Pantry Fabric Softener Monitor

  board: firebeetle32
    type: arduino

# Enable logging

# Enable Home Assistant API
    key: [redacted]

  password: [redacted]

  ssid: "Reactor No. 4"
  password: [redacted]

  # Enable fallback hotspot (captive portal) in case wifi connection fails
    ssid: "pantry-fabric-softener-monitor"
    password: [redacted]

  - platform: uptime
    id: uptime_sec
  - platform: ultrasonic
    trigger_pin: GPIO13
    echo_pin: GPIO2
    name: "Liquid Level"
    update_interval: 10s
    pulse_time: 10us

  - platform: status
    name: "Status"

  - platform: restart
    name: "Reboot"

Log Output from ESPHome:

INFO ESPHome 2023.12.9
INFO Reading configuration /config/pantry-fabric-softener-monitor.yaml...
WARNING GPIO2 is a strapping PIN and should only be used for I/O with care.
Attaching external pullup/down resistors to strapping pins can cause unexpected failures.
INFO Starting log output from using esphome API
INFO Successfully connected to pantry-fabric-softener-monitor @ in 0.030s
INFO Successful handshake with pantry-fabric-softener-monitor @ in 0.103s
[10:11:06][I][app:102]: ESPHome version 2023.12.9 compiled on Feb 17 2024, 01:24:44
[10:11:06][C][wifi:573]: WiFi:
[10:11:06][C][wifi:405]:   Local MAC: 08:3A:F2:31:84:DC
[10:11:06][C][wifi:410]:   SSID: [redacted]
[10:11:06][C][wifi:411]:   IP Address:
[10:11:06][C][wifi:413]:   BSSID: [redacted]
[10:11:06][C][wifi:414]:   Hostname: 'pantry-fabric-softener-monitor'
[10:11:06][C][wifi:416]:   Signal strength: -66 dB ▂▄▆█
[10:11:06][C][wifi:420]:   Channel: 6
[10:11:06][C][wifi:421]:   Subnet:
[10:11:06][C][wifi:422]:   Gateway:
[10:11:06][C][wifi:423]:   DNS1:
[10:11:06][C][wifi:424]:   DNS2:
[10:11:06][C][logger:439]: Logger:
[10:11:06][C][logger:440]:   Level: DEBUG
[10:11:06][C][logger:441]:   Log Baud Rate: 115200
[10:11:06][C][logger:443]:   Hardware UART: UART0
[10:11:06][C][uptime.sensor:031]: Uptime Sensor 'uptime_sec'
[10:11:06][C][uptime.sensor:031]:   Device Class: 'duration'
[10:11:06][C][uptime.sensor:031]:   State Class: 'total_increasing'
[10:11:06][C][uptime.sensor:031]:   Unit of Measurement: 's'
[10:11:06][C][uptime.sensor:031]:   Accuracy Decimals: 0
[10:11:06][C][uptime.sensor:031]:   Icon: 'mdi:timer-outline'
[10:11:06][C][template.text_sensor:020]: Template Sensor 'Uptime'
[10:11:06][C][template.text_sensor:020]:   Icon: 'mdi:clock-start'
[10:11:06][C][ultrasonic.sensor:045]: Ultrasonic Sensor 'Liquid Level'
[10:11:06][C][ultrasonic.sensor:045]:   State Class: 'measurement'
[10:11:06][C][ultrasonic.sensor:045]:   Unit of Measurement: 'm'
[10:11:06][C][ultrasonic.sensor:045]:   Accuracy Decimals: 2
[10:11:06][C][ultrasonic.sensor:045]:   Icon: 'mdi:arrow-expand-vertical'
[10:11:06][C][ultrasonic.sensor:046]:   Echo Pin: GPIO2
[10:11:06][C][ultrasonic.sensor:047]:   Trigger Pin: GPIO13
[10:11:06][C][ultrasonic.sensor:048]:   Pulse time: 10 µs
[10:11:06][C][ultrasonic.sensor:049]:   Timeout: 11661 µs
[10:11:06][C][ultrasonic.sensor:050]:   Update Interval: 10.0s
[10:11:06][C][status:034]: Status Binary Sensor 'Status'
[10:11:06][C][status:034]:   Device Class: 'connectivity'
[10:11:06][C][restart:068]: Restart Switch 'Reboot'
[10:11:06][C][restart:070]:   Icon: 'mdi:restart'
[10:11:06][C][restart:091]:   Restore Mode: always OFF
[10:11:06][C][captive_portal:088]: Captive Portal:
[10:11:06][C][mdns:115]: mDNS:
[10:11:06][C][mdns:116]:   Hostname: pantry-fabric-softener-monitor
[10:11:06][C][ota:097]: Over-The-Air Updates:
[10:11:06][C][ota:098]:   Address:
[10:11:06][C][ota:101]:   Using Password.
[10:11:06][C][api:139]: API Server:
[10:11:06][C][api:140]:   Address:
[10:11:06][C][api:142]:   Using noise encryption: YES
[10:11:06][C][wifi_info:009]: WifiInfo IPAddress 'IP Address'
[10:11:06][C][wifi_info:009]:   Icon: 'mdi:ip'
[10:11:06][D][text_sensor:064]: 'Uptime': Sending state '0d 0h 11m 52s'
[10:11:07][D][text_sensor:064]: 'Uptime': Sending state '0d 0h 11m 52s'
[10:11:08][D][text_sensor:064]: 'Uptime': Sending state '0d 0h 11m 52s'
[10:11:09][D][text_sensor:064]: 'Uptime': Sending state '0d 0h 11m 52s'
[10:11:10][D][ultrasonic.sensor:040]: 'Liquid Level' - Got distance: 0.170 m
[10:11:10][D][sensor:094]: 'Liquid Level': Sending state 0.16996 m with 2 decimals of accuracy

Really unsure what else to try, any help would be greatly appreciated.


You sure it is not a caching issue?

Did you repurpose this ESP and is it listed under another name? Maybe look for the liquid level entity? it seems to indeed be communicating with HA.

Doesn’t appear to be I have cleared my browser cache and tested from another browser, still can’t see it. thanks though

Thank you yes this was it, used it previously for another project which is since been retired, original device was disabled in the ESPHome integration. Thanks again!