LILYGO TTGO T-Internet-POE ESP32-WROOM LAN8270A

RGN01 · February 27, 2021, 8:06am

What board type did you end up using, please, @jonathanpearce ?

Maco65 · February 27, 2021, 3:04pm

Looking forward for more information related to stability and performance of Lilygo.
Lilygo module seem to be half price of Olimex (app.13€ vs. 24€).

jonathanpearce · February 27, 2021, 5:57pm

My config - not saying it’s right but it’s working.

esphome:
  name: $hostname
  platform: ESP32
  board: esp-wrover-kit
logger:
ota:
api:
time:
  - platform: homeassistant
    id: homeassistant_time 
ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

Reliability wise, I’ve only been running it for less than a week but no concerns so far.

RGN01 · February 27, 2021, 6:51pm

Thank you - looks like we ended up with the same config!

assaff · May 16, 2021, 9:15pm

Thank you for this. Used the Lilygo POE unit and it works well. No more lost wifi connection issues or needing local power.

bremby · May 17, 2021, 7:12pm

Hi,
I’m using the same model, quick question:
the output pins are only 6 (4,14,15,16,32,33), correct?
what about the 34,35,36,39?

regards

nmatt25 · September 30, 2021, 2:12am

This is my current configuration for the LilyGo ESP32 POE and all is working great.

esphome:
  name: poe-esp32
  platform: ESP32
  board: esp32dev

#enable project name
  project:
    name: "matts.poe_esp32"
    version: "1.0.0"

# Enable logging
logger:

# Enable Home Assistant API
api:

#enable ethernet
ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

#enable web server
web_server:
  port: 80

#enable OTA updates
ota:
  password: "your_password"

#binary sensor inputs
binary_sensor:
  - platform: gpio
    pin:
      number: GPIO39
      mode: INPUT_PULLUP
    name: Front Door Bell
  - platform: gpio
    pin:
      number: GPIO36
      mode: INPUT_PULLUP
    name: Mailbox
  - platform: gpio
    pin:
      number: GPIO35
      mode: INPUT_PULLUP
    name: Back Door Bell
    filters:
      - delayed_on: 10ms

gregoinc · August 11, 2024, 7:21am

Rather than starting another thread, I am hopeful some of my questions can be answered here. My configuration is expected to run entirely on POE, with no USB C power.

I followed the examples here, see my code below:-

esphome:
  name: test-lilygo
  friendly_name: test-lilygo

esp32:
  board: esp32dev
  framework:
    type: arduino

# 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

# Enable fallback hotspot (captive portal) in case wifi connection fails
# ap:
#  ssid: "Test-Lilygo Fallback Hotspot"
#   password: "<REDACTED>"

# captive_portal:

#enable web server
web_server:
  port: 80

time:
  - platform: homeassistant
    id: homeassistant_time

ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

When the T-Internet-POE is connected to the POE port on my switch that is 802.3af standard compatible, the blue LED beside the USB C port slowly flashes.

The T-Internet-POE does not start or boot. I noted there was a config here that included a power pin (see below), but I haven’t seen that option used anywhere else?

ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO0_OUT
  phy_addr: 0
  **power_pin: GPIO04**

If you are using this board with POE any suggestions or tips would be appreciated.

andyboeh · August 12, 2024, 8:55pm

I do. I do not have the power pin defined. However, PoE failed on two of three boards after about a year. They still work fine when powered from USB-C.

gregoinc · August 12, 2024, 11:47pm

Hi Andy,

Thanks for coming back to me. Would you be willing to share your yaml code?

Thanks, Mark

andyboeh · August 14, 2024, 7:01pm

Yeah, I just realized that mine is differently configured, but IIRC, there are multiple versions of this device.

ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0

See the example section and make sure to pick the right config: Ethernet Component — ESPHome

T-Internet-PoE is not T-Internet!

Newt · October 31, 2024, 8:10pm

Any updates on this? I just got a board and I can’t get it to work with the examples in this thread

DG-Lt · December 28, 2024, 5:08pm

Hi,

here is my yaml that I can confirm working on my LILYGO® TTGO T-Internet-POE ESP32 Ethernet Adapter LAN8720A:

I have also managed to flash it without the official add on board. Just used some “pin wires” to connect to my regular USB to TTL adapter.

esphome:
  name: hvac-sensors2

esp32:
  board: esp32dev
  framework:
    type: arduino

# Enable logging
logger:
  baud_rate: 0
  level: DEBUG

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

ota:
  - platform: esphome
    password: "xxxxxxxxxxxxxx"
ethernet:
  type: LAN8720
  mdc_pin: GPIO23
  mdio_pin: GPIO18
  clk_mode: GPIO17_OUT
  phy_addr: 0
  manual_ip:
    static_ip: 192.168.1.x
    gateway: 192.168.1.x
    subnet: 255.255.255.0
 
web_server:
  port: 80

debug:
  update_interval: 5s

button:
  - platform: restart
    name: "Restart"
    icon: mdi:restart

DG-Lt · December 28, 2024, 5:19pm

Hi,

Despite above success, after a couple of months working my “LILYGO® TTGO T-Internet-POE ESP32 Ethernet Adapter LAN8720A” stopped today (no connection, no blue power LED, no LAN port indicators).

first I checked whether POE comes through. The switch POE indicator ON but network OFF.
Then I brought a new board and connected to the same LAN cable. The Blue power LED came on, both of the Lan port Indicators lit up.
Then I connected the USB-C cable to the malfunctioning board. The Blue LED came on. When plugged the same Lan cable into the LAN port, the Board got the network.

So my conclusion is that the POE circuitry stopped working. The very thing I have chosen this board for

The visual inspection did not give any clues. Did not see any fried parts or feel any hot parts. Checked under the ESD sticker as well. All look good.

Anyone experienced something like this? Any advice?

I hoped to use this POE thingy far away from my wifi (In a metal Electrical box on a street, ran a LAN cable there), now I am not so sure…

Newt · December 28, 2024, 5:38pm

After some time playing with it for me it was not the code but I think it’s my switch it gives PoE to the board but refuses to let it connect to the network when using a PoE injector while it’s plugged directly into my router it works without any problems. My switch is a cisco catalyst 2960s and I still can’t get it to work with the switch I don’t know what to do.

Maco65 · December 28, 2024, 6:54pm

Not a real advice I am afraid but looking for similar solution I am using WT32-ETH01 over the year now and no problems. This board does not have PoE build-in but with some DIY skills I have made Ethernet connection with only data to this module and power cables are “taken out” of the network connector and put to DC-DC converter so I get 5V to power the board. The other end of Ethernet cable is connected to PoE switch so no changed on this side.
This has in my case another advantage that I can take PoE power to use (separate to WT32 board power unit) to other purpose.

DG-Lt · December 28, 2024, 8:41pm

thanks for an advice. thinking this route too

found this product (PoE Splitter 5v POE usb tpye-C), that I think should solve my problem similarly

Maco65 · December 28, 2024, 11:17pm

This should work and no cable “manipulation” is needed. Actually this is very nice - have bulit-in DC-DC converter!

DG-Lt · January 9, 2025, 5:28pm

Received the POE Splitter today. Tried for a couple of hours. Seems to be working.

Installing to a “production environment”

andyboeh · January 16, 2025, 5:35am

Yes, this happened already to two of these boards, both were mounted outside. I still have a working one mounted inside.

I migrated the board to Olimex ESP32 PoE boards, so far they are working fine.