LILYGO T-ETH-Lite ESP32 not connecting via Ethernet

ESPHome
1

I updated to the latest ESPHome version and was trying to hook up my “LILYGO T-ETH-Lite ESP32 (POE)” but it is not recognized by the network anymore via Ethernet (wifi works)?

My config:

esphome:
  name: eth2
  friendly_name: eth2

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

# Enable Home Assistant API
api:
  encryption:
    key: "(...)"

ota:

ethernet:
  type: RTL8201
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO0_IN
  phy_addr: 0
  power_pin: GPIO12
2

“latest” is not a version.

What version does it work with? What version does it not work with?

What do your logs tell you?

3

ESPHome version 2024.5.2 compiled on May 23 2024, 09:52:35

I cannot read the logs when connected via Ethernet, Wifi Works.

4

You didn’t answer this fully.

5

I’m having the same issue with both of them that I have. Mine aren’t the POE version though. It looks like I tried to upgrade to 2024.5.x when it disconnected. It was probably upgraded from 2024.3 or 2024.4. I haven’t been able to pull logs but I was able to downgrade one to 2023.12.5 and it works fine on that version. I know it’s pretty vague. Just throwing it out there that I have the same problem in the same hardware

1 Like
6

Hi @Twillist, yes that was in fact it. Basically confirmed my suspicion because for me it was working before as well.

So I reinstalled ESPHome version 2023.12.5 compiled a basic script:

esphome:
  name: eth-test
  friendly_name: eth-test

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:

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

ota:
  password: "..."

ethernet:
  type: RTL8201
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO0_IN
  phy_addr: 0
  power_pin: GPIO12

… and it works again. Doing the same with a newer version (up to the newest ESPHome version 2024.5.4) the ethernet connection does not work.

I filed an issue with the esphome community. Expect updates here:

7

Awesome thanks for doing that. Some one on the discord had the same issue and it’s being discussed over there as well

8

Feel free to copy the link to the GitHub issue into the discord discussion if you are active there.

9

Will do. I’ll respond back here if anything is figured out

10

Wow those people in the discord are great. There’s already a fix posted on the GitHub linked above

1 Like