LILYGO TTGO T-Internet-POE ESP32-WROOM LAN8270A

ESPHome
6

I got Tasmota on there without much effort, maybe give that a try?

7

I’ve never used that but will go and have a look.

What did you think of them once you got them working? Are they any good? Once you got Tasmota going, did you find a way to integrate them to HASS / ESPHome?

Apologies for all the questions!

8

@PaulNL
I am looking for similar solution. Can you kindly share your experience and what finally have you selected ?

9

Has a full featured usb port for programming as well

10

I was having the same disaster til I realised the programmer board fits from the underside of the PCB not the top. Worked first time using ESPHomeFlasher as soon as I actually connected it properly, and is now happily running some BLE bits with Xaomi sensors.

11

I started with these Olimex boards - and am looking for an alternative after having most boards fail quickly. In some cases getting less than 48 hours use from them. It’s a real pity as I like their features.

12

You’ve made me question myself on this! I’ll re-test and report back. Thanks.

1 Like
13

OK, mea culpa (well mostly)! The board works when you plug it in the correct way around but you also need to use the correct USB cable! Thank you @jonathanpearce

First, the code:

esphome:
  name: test_lilygo
  platform: ESP32
  board: esp-wrover-kit

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

# Enable logging
logger:

# Enable Home Assistant API
api:
ota:

I’m not sure about the board type, I’ll try a few others to try to find the most suitable one but the basic ESP32 board works.

The USB C cable connector is a bit strange - a few of my decent quality USB C to USB C cables don’t work when plugged into the board itself (there is no power) yet a cheapo USB A to USB C cable works fine.

I’ll test this for a while and report back.

Thanks again!

1 Like
14

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

15

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€).

16

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.

17

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

19

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

20

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

21

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
2 Likes
22

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.

23

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.

24

Hi Andy,

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

Thanks, Mark

25

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!

1 Like
26

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