No device and no entities from esp32 in esphome

ESPHome
1

I am completely lost. I have tried everything i have seen in the other posts here about this issue and used AI to try and help and nothing works.

I make afresh install of a esp32 in esphome and it always shows up to be added to HA but it always appears in esphome with “No device no entities” even though the entities show in the logs in esphome…

I am completely lost and loosing my mind. I have setup and been using about 20 esp8266’ si in my house to control stuff for years without any issues. No idea whats happening.

see my yaml file here

esphome:
  name: esp8-utility-relaisboard-new
  friendly_name: esp8-utility-relaisboard-new

esp32:
  board: esp32dev
  framework:
    type: esp-idf

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "redacted"

ota:
  - platform: esphome
    password: "redacted"

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

  manual_ip:
    static_ip: 192.168.0.16
    gateway: 192.168.0.1
    subnet: 255.255.255.0

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esp8-Utility-Relaisboard-New"
    password: "redacted"

captive_portal:


switch:
  - platform: gpio
    pin: 13
    name: "Living Heater"
    inverted: true
   
  - platform: gpio
    pin: 18
    name: "Kitchen Heater"
    inverted: true
    
  - platform: gpio
    pin: 14
    name: "Utility Room Heater"
    inverted: true
   
  - platform: gpio
    pin: 27
    name: "Bathroom Heater"
    inverted: true
   
  - platform: gpio
    pin: 26
    name: "Cave Heater"
    inverted: true
   
  - platform: gpio
    pin: 25
    name: "Guestroom Heater"
    inverted: true
  
  - platform: gpio
    pin: 33
    name: "Abrielle Heater"
    inverted: true
   
one_wire:
  - platform: gpio
    pin: 21
  

sensor:
  - platform: dallas_temp
    address: 0xFE0300A2795EA528
    name: "Utility Temp"
    update_interval: 10s

Any help would be highly appreciated as my wife is starting get annoyed with the house getting colder…I NEED HELP :wink:

1 Like
2

image
this is how it looks like when i open the esphome integration

1 Like
3 
[W][api.connection:1880]: 192.168.0.40 (192.168.0.40): Reading failed BAD_INDICATOR errno=11

[22:11:17.845][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:11:17.845][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:11:27.848][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:11:27.852][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:11:28.505][D][api:160]: Accept 192.168.0.40
[22:11:28.516][W][api.connection:1880]: 192.168.0.40 (192.168.0.40): Reading failed BAD_INDICATOR errno=11
[22:11:37.850][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:11:37.854][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:11:47.852][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:11:47.854][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:11:57.854][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:11:57.857][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:07.858][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:07.862][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:17.863][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:17.867][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:27.860][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:27.864][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:28.612][D][api:160]: Accept 192.168.0.40
[22:12:28.623][W][api.connection:1880]: 192.168.0.40 (192.168.0.40): Reading failed BAD_INDICATOR errno=11
[22:12:37.862][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:37.868][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:47.867][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:47.871][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy
[22:12:57.887][D][dallas.temp.sensor:054]: 'Utility Temp': Got Temperature=17.9°C
[22:12:57.894][D][sensor:131]: 'Utility Temp': Sending state 17.93750 °C with 1 decimals of accuracy

keep getting this error in between good readings from the sensor. i tried with API and without, fresh installs same as the ones using the old code. even got new ESP32’s just to be sure as i read esp8266 are not the most relieble. I have very good wifi connection. everything has been working as is for years just started when i updated the esp8266 to add a sensor. ever since i just cant get any new device to register properly, even with the old copied code.

I am in deep trouble, my wife is freezing in the house! PLEASE HELP :wink:

4

Please anybody help… I am desperate. I am installing from scratch brand new ESP32 with no code extra through esphome and i get the same API errors. i have about 10 old esp8266 running in the house 365 for 4 years without any issues. why can i not setup new devices anymore??? I am so confused I am close to give up on homeassistant after 4 years of success if I cant fix this…

5

Perhaps something similar to this?

1 Like
6

Thanks so much for your help but this didnt solve it for me tried a million times deleting and re-adding. restarting HA rebooting the pi its running on. With API key and without.

At the moment i have another ESP8266 with the newest updated esphome code structure etc that is working flawlessly without any api set.

If I even copy that code to a new device it has the api errors. it doesnt even make sense…

I literally want to cry

7

hmmm pretty strange if you ask me, since an ESP with a dallas sensor on its own is sort of a 20 liner in YAML or perhaps 10 lines more.

I’d suggest to compile it with a more detailed debug level since your log from an earlier post tells next to nothing. Perhaps verbose or very_verbose?

1 Like
8

Then your uploads are not successful and you keep on running same old code.
If you don’t have anything related to API on your code, it would be really weird to get api-errors…

1 Like
9

yeah thats what i thought too. i dont get errors when uploading code so i assume its working okay? any other changes I make in the code always come threw so I guess its working…

10

thanks i will look into this, never heard about these before

11

i just dont understand I had so much success with this over the last 4 years and now i am close to throwing it all out, is this all because of the “recent” updates to esphome in relation to API?
Sorry for my tone… I am just frustrated AF with this, battling with this super simple thing of setting up a new esp device for weeks without heating in the house…

12

clicked “update” within esphome on another previously working esp8266 device and now its also reporting API error 1880 and sensor has become unavailable…

13 
[20:30:10.070][D][sensor:131]: 'Utility5 WiFi Signal': Sending state -36.00000 dBm with 0 decimals of accuracy
[20:30:12.966][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:30:12.973][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:30:12.974][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:30:22.975][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:30:22.981][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:30:22.982][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:30:32.973][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:30:32.986][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:30:32.987][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:30:42.973][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:30:42.979][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:30:42.979][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
INFO Processing unexpected disconnect from ESPHome API for esp8-utility5 @ 192.168.0.181
WARNING Disconnected from API
INFO Successfully resolved esp8-utility5 @ 192.168.0.181 in 0.001s
INFO Successfully connected to esp8-utility5 @ 192.168.0.181 in 0.004s
INFO Successful handshake with esp8-utility5 @ 192.168.0.181 in 0.026s
[20:31:26.472][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.6°C
[20:31:26.518][V][sensor:079]: 'Utility5 Temp': Received new state 20.625000
[20:31:26.518][D][sensor:131]: 'Utility5 Temp': Sending state 20.62500 °C with 1 decimals of accuracy
[20:31:36.475][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:31:36.482][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:31:36.482][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:31:46.472][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:31:46.476][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:31:46.476][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:31:56.469][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:31:56.476][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:31:56.476][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:32:01.437][I][safe_mode:042]: Boot seems successful; resetting boot loop counter
[20:32:06.474][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:32:06.481][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:32:06.482][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy
[20:32:13.568][V][sensor:079]: 'Utility5 WiFi Signal': Received new state -37.000000
[20:32:13.575][D][sensor:131]: 'Utility5 WiFi Signal': Sending state -37.00000 dBm with 0 decimals of accuracy
[20:32:16.481][D][dallas.temp.sensor:054]: 'Utility5 Temp': Got Temperature=20.7°C
[20:32:16.485][V][sensor:079]: 'Utility5 Temp': Received new state 20.687500
[20:32:16.485][D][sensor:131]: 'Utility5 Temp': Sending state 20.68750 °C with 1 decimals of accuracy

not sure what to make of this, right after freshly installed on esp8266 without an api config…

esphome:
  name: esp8-utility5
  friendly_name: esp8-utility5

esp8266:
  board: esp01_1m

# Enable logging
logger:
  level: VERBOSE  

# Enable Home Assistant API
api:

ota:
  - platform: esphome
    password: "5d5c5741b7d92bce90aacaeae742ea76"

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

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Esp8-Utility5 Fallback Hotspot"
    password: "pw"

captive_portal:


one_wire:
  - platform: gpio
    pin: 3

sensor:
  - platform: dallas_temp
    address: 0xFE0300A2795EA528
    name: "Utility5 Temp"
    update_interval: 10s

  - platform: wifi_signal
    name: "Utility5 WiFi Signal"
    update_interval: 60s

any ideas?

14

but still you have api there…

1 Like
15

thanks, removed that line and now i get this error when compiling…

Compiling .pioenvs/esp8-utility5/FrameworkArduino/umm_malloc/umm_integrity.c.o
Compiling .pioenvs/esp8-utility5/FrameworkArduino/umm_malloc/umm_local.c.o
Compiling .pioenvs/esp8-utility5/FrameworkArduino/umm_malloc/umm_malloc.cpp.o
Compiling .pioenvs/esp8-utility5/FrameworkArduino/umm_malloc/umm_poison.c.o
Compiling .pioenvs/esp8-utility5/FrameworkArduino/wpa2_eap_patch.cpp.o
Archiving .pioenvs/esp8-utility5/libFrameworkArduino.a
Linking .pioenvs/esp8-utility5/firmware.elf
RAM:   [====      ]  39.2% (used 32104 bytes from 81920 bytes)
Flash: [====      ]  38.3% (used 392321 bytes from 1023984 bytes)
Building .pioenvs/esp8-utility5/firmware.bin
esp8266_copy_factory_bin([".pioenvs/esp8-utility5/firmware.bin"], [".pioenvs/esp8-utility5/firmware.elf"])
esp8266_copy_ota_bin([".pioenvs/esp8-utility5/firmware.bin"], [".pioenvs/esp8-utility5/firmware.elf"])
======================== [SUCCESS] Took 280.03 seconds ========================
INFO Successfully compiled program.
INFO Connecting to 192.168.0.181 port 8266...
INFO Connected to 192.168.0.181
INFO Uploading /data/build/esp8-utility5/.pioenvs/esp8-utility5/firmware.bin (396480 bytes)
INFO Compressed to 282884 bytes
Uploading: [============================================================] 100% Done...

INFO Upload took 4.23 seconds, waiting for result...
INFO OTA successful
INFO Successfully uploaded program.
ERROR No remote or local logging method configured (api/mqtt/logger)
16

and this below when start log of that device with above firware…

INFO ESPHome 2025.10.4
INFO Reading configuration /config/esphome/esp8-utility5.yaml...
ERROR All specified devices ['OTA'] could not be resolved. Is the device connected to the network?
17

Likely a mismatch between the devicename, the deviceIp and the OTA keys known to HA I’d say.

A pure guess you OTA flashed to a wrong IP, let it be you mixed it up or you used DHCP and didn’t check if different IPs got spread, perhaps a router changed or such like since you flashed the device last time?

18

my last 2 posts only happened after removing “api:” from the code.

All my other old devices that are still running have “api:” in the code but no key etc underneath it.

Lets go back to the original issue of not being able to setup a new device from scratch, new name, DHCP, so there shouldnt be any conflicts right?
Any idea why these will have this API error 1880?

19

If you say “NEW” device. Is it really a “NEW” device or one grabbed from the box of spare electronics which perhaps was once discovered by HA in the past with an API line and an API key?

And perhaps not being removed/deleted but only grabbed when where it was in use and dropped into a box with electronic components half a year ago? Since if, HA might recognise it treating it similar to a device which became unavailable for a while and then trying to communicate using it’s last know API key from the past whereas you defined none or a new key right now.

20

that “New” device was reprogrammed about 10times in the last couple weeks for troubleshooting so its not NEW anymore to HA now but it was on first use. I will try with an actual NEW one out of the bag never used and try again.
But should i do this with or without api key? and with or without the “api:”

Thanks again for your help super appreciated!