LILYGO PoE not connected to HA

ESPHome
1

Hi,

I want to use ESPHome for Presence detection in multiple rooms and bluetooth proxy to connect to devices like scale or WC.

I installed ESPHome Addon, created a new device and flashed is with the bin file to my LILYGO T-Internet-PoE. The device is directly connected to wifi,
I used this siite to flash.
https://web.esphome.io/?dashboard_install

Then I remove the wifi part and add this line and also remove captive portal line. After a wireless push to the device I connected with PoE Port of my switch and the LILYGO is connected with my LAN. All fine

In Home Assistant I see a discovered device and add it to my integrations

I see some device information, sensors, configuration and diagnostic.
But connectivity is disconnected, configuration is grayed out and diagnostic is unavailable

image
image1554×1160 83.4 KB

INFO ESPHome 2025.12.4 INFO Reading configuration /config/esphome/esphome-azt.yaml... INFO Starting log output from 192.168.178.186 using esphome API INFO Successfully resolved esphome-azt @ 192.168.178.186 in 0.000s INFO Successfully connected to esphome-azt @ 192.168.178.186 in 0.001s INFO Successful handshake with esphome-azt @ 192.168.178.186 in 0.062s
[02:55:45.025][I][app:194]: ESPHome version 2025.12.4 compiled on Jan 2 2026, 02:50:58 
[02:55:45.026][C][logger:261]: Logger: 
[02:55:45.026][C][logger:261]: Max Level: DEBUG 
[02:55:45.026][C][logger:261]: Initial Level: DEBUG 
[02:55:45.028][C][logger:267]: Log Baud Rate: 115200 
[02:55:45.028][C][logger:267]: Hardware UART: UART0 
[02:55:45.030][C][logger:274]: Task Log Buffer Size: 768 
[02:55:45.050][C][ethernet:384]: Ethernet: 
[02:55:45.050][C][ethernet:384]: Connected: YES 
[02:55:45.051][C][ethernet:647]: IP Address: 192.168.178.186 
[02:55:45.051][C][ethernet:647]: Hostname: 'esphome-azt' 
[02:55:45.051][C][ethernet:647]: Subnet: 255.255.255.0 
[02:55:45.051][C][ethernet:647]: Gateway: 192.168.178.1 
[02:55:45.051][C][ethernet:647]: DNS1: 192.168.178.9 
[02:55:45.051][C][ethernet:647]: DNS2: 192.168.178.1 
[02:55:45.054][C][ethernet:668]: MAC Address: 1C:69:20:C9:1A:EB 
[02:55:45.054][C][ethernet:668]: Is Full Duplex: YES 
[02:55:45.054][C][ethernet:668]: Link Speed: 100 
[02:55:45.056][C][ethernet:412]: CLK Pin: 17 
[02:55:45.056][C][ethernet:412]: MDC Pin: 23 
[02:55:45.056][C][ethernet:412]: MDIO Pin: 18 
[02:55:45.056][C][ethernet:412]: PHY addr: 0 
[02:55:45.058][C][ethernet:419]: Type: LAN8720 
[02:55:45.067][C][esphome.ota:092]: Over-The-Air updates: 
[02:55:45.067][C][esphome.ota:092]: Address: esphome-azt.local:3232 
[02:55:45.067][C][esphome.ota:092]: Version: 2 
[02:55:45.069][C][esphome.ota:099]: Password configured 
[02:55:45.084][C][safe_mode:018]: Safe Mode: 
[02:55:45.084][C][safe_mode:018]: Successful after: 60s 
[02:55:45.084][C][safe_mode:018]: Invoke after: 10 attempts 
[02:55:45.084][C][safe_mode:018]: Duration: 300s 
[02:55:45.087][W][safe_mode:030]: Last reset too quick; invoke in 8 restarts 
[02:55:45.098][C][api:211]: Server: 
[02:55:45.098][C][api:211]: Address: esphome-azt.local:6053 
[02:55:45.098][C][api:211]: Listen backlog: 4 
[02:55:45.098][C][api:211]: Max connections: 8 
[02:55:45.100][C][api:218]: Noise encryption: YES 
[02:55:45.115][C][mdns:177]: mDNS: 
[02:55:45.115][C][mdns:177]: Hostname: esphome-azt

What is the issue on my site?

My current yaml


esphome:
  name: esphome-azt
  friendly_name: esphome-azt
esp32:
  board: esp32dev
  framework:
    type: esp-idf
# Enable logging
logger:
# Enable Home Assistant API
api:
  encryption:
    key: "MY_KEY"
ota:
  - platform: esphome
    password: "MY_PASSWORD"
ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk:
    pin: GPIO17
    mode: CLK_OUT
  phy_addr: 0
2

Have you tried removing it from HA in

Settings > Devices > ESPHome

And then let HA auto discover again? I find unless I do when swapping ESPs I get the same as you. Think it remembers the MAC address which has now changed.

I have the same board as you and works well as BLE proxy. I’d try removing from devices and allow it to be rediscovered.

Edit sometimes a HA reboot as well helps.

3

As I wrote I let HA discover the device and added from there.

An tried to remove and add again also also restart HA but still the same issue.

What is your yaml configuration?

4

Hi

My YAML is not dissimilar to yours relevant bits below, I use to connect to an CC1101 RF transmitter and receiver as well which is a challenge but does work. I have removed this config from below as not relevant to you. This one was of my first few ESP’s I used so has been around a couple of years but is running latest firmware 2025.12.4 as I added the CC1101 recently.


esphome:
  name: esp433poe
  friendly_name: ESP433POE


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

# Enable logging
logger:
#  level: VERY_VERBOSE
  
# Enable Home Assistant API
api:
  encryption:
    key: "redacted"

ota:
  - password: "redacted"
    platform: esphome


ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18

  clk:
    pin: GPIO17
    mode: CLK_OUT
  phy_addr: 0



esp32_ble_tracker:
  scan_parameters:
    interval: 1100ms
    window: 1100ms
    active: true



bluetooth_proxy:
  active: true


sensor:

  - platform: uptime
    type: seconds
    name: Uptime Sensor
5

With that configuration I get this error

WARNING Can't connect to ESPHome API for esphome-azt @ 192.168.178.186: Error connecting to [AddrInfo(family=<AddressFamily.AF_INET: 2>, type=<SocketKind.SOCK_STREAM: 1>, proto=6, sockaddr=IPv4Sockaddr(address='192.168.178.186', port=6053))]: [Errno 113] Connect call failed ('192.168.178.186', 6053) (SocketAPIError)

Just before finishing the flash the ESP disconnects.

Just with esp32_ble_tracker part there are some disconnects from ping. Before that is was working smooth

6

You could try removing the interval and window lines, originally they were recommended for Ethernet connected devices but caused issues with Wi-Fi. I think latest recommendation is to leave as default, as I said this was from way back.

I’d also have a look at how much memory you have as I noticed from your screen shot you have other components and it might be on the edge, BLE proxy uses a lot of memory. One of my other ESP32 I have to set BLE tracker active as false and then start it after everything else has finished starting.


esp32_ble_tracker:
  scan_parameters:
    active: false
7

I removed it and ble_tracker and proxy is now possible and more stable. But the esp device in HA is still disconnected.

How can I check how much memory is used and available?

8

Hi, the other day I found a GitHub page that helps you see the memory, partitions, etc. of any ESP32. You just have to connect it and everything appears.

The address is:
ESPConnect
I hope this helps.