Is GT911 Capacitive Touch Controller Compatible with Home Assistant (ESPHome)?
Electrical Specifications
Always confirm pin assignments against the manufacturer datasheet before wiring.
Compatibility Overview
5-point capacitive multi-touch panel controller for interactive LCD screen displays and smart switch panels.
Typical I²C Wiring Reference
Standard I²C signal names. This is a bus reference, not a pinout for this specific board — check the silkscreen and datasheet for its actual pin order.
Reference circuit only. A shifter is needed when the host and peripheral run at different logic levels — check both datasheets to confirm whether this applies to your pairing.
Technical Specification Matrix
| Feature / Attribute | Specification / Status |
|---|---|
| Hardware Protocol | I2C Bus / 3.3V |
| Bridge Required | NO |
| Border Router Needed | None |
| Hardware Capabilities & Peripherals | Touch X Position Touch Y Position Gesture Events Note: these entities come from the ESPHome configuration you flash — each one needs its matching component in that YAML before it appears. |
| Pairing Complexity | Intermediate |
| Factory Reset Instruction | Hold BOOT button while cycling reset. |
Wire, Flash, Adopt, Check
Wire it up
Follow the bus reference above. The host pins in the configuration are defaults — any free GPIO of the right kind will do, as long as the YAML names the pin you actually used.
Flash the configuration
Create a new device in the ESPHome dashboard (the Home Assistant add-on) and paste the configuration below into it, or save it as emb_esp32s3_gt911_touch.yaml and run esphome run emb_esp32s3_gt911_touch.yaml. The first flash goes over USB. If it is not detected, hold BOOT button while cycling reset to put it in download mode. Every update after that is over the air.
Adopt it in Home Assistant
Settings → Devices & Services. A node on the same network shows up as a discovered ESPHome device within a minute of joining Wi-Fi; choose Configure and enter the API encryption key from your secrets.yaml. If discovery does not find it, add the ESPHome integration by hand with the node's IP address.
Check it works
The entities on this page appear under the device in Home Assistant and update at the configured interval. The ESPHome log (Logs in the dashboard, or esphome logs) reports the setup of each component and any bus scan results at boot.
ESPHome Configuration
Starting configuration for GT911 Capacitive Touch Controller on ESP32-S3. Untested on hardware — verify wiring and pins against your own board.
# ESPHome configuration for GT911 Capacitive Touch Controller
# Host: ESP32-S3. Pin numbers below are host-side defaults — any free
# GPIO will do, and you should change them to match your own wiring.
esphome:
name: emb_esp32s3_gt911_touch
friendly_name: "GT911 Capacitive Touch Controller"
esp32:
board: esp32-s3-devkitc-1
framework:
type: esp-idf
logger:
api:
encryption:
key: !secret api_encryption_key
ota:
- platform: esphome
password: !secret ota_password
wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
i2c:
id: i2c_main
sda: GPIO8
scl: GPIO9
scan: true
# A touch controller needs a display to map its coordinates onto. The
# GT911 is usually laminated to an ILI9341-class panel, wired here on the
# SPI bus.
spi:
clk_pin: GPIO12
mosi_pin: GPIO11
miso_pin: GPIO13
# GPIO8 and GPIO9 are the I2C bus the touch controller sits on, so the
# display's control lines move off the S3 defaults.
display:
- platform: ili9xxx
id: tft
model: ILI9341
cs_pin: GPIO10
dc_pin: GPIO14
reset_pin: GPIO21
invert_colors: false
update_interval: 1s
lambda: |-
it.print(0, 0, id(roboto), "Touch me");
# 0x5D or 0x14, chosen by the level on INT during reset. The component
# scans both, so no address is set here.
touchscreen:
- platform: gt911
display: tft
interrupt_pin: GPIO4
reset_pin: GPIO5
on_touch:
- logger.log:
format: "Touch at x=%d y=%d"
args: [touch.x, touch.y]
font:
- file: "gfonts://Roboto"
id: roboto
size: 20
Before you flash:
the !secret values come from your
secrets.yaml, and the GPIO numbers are host-side
defaults rather than properties of this part — change them to match how you actually wired it.
If the device is not found:
it is usually the I2C address, not the config. Many breakouts strap their address with
solder jumpers, so two boards of the same part can differ. This config leaves
scan: true on — the boot log lists every address
actually present on the bus, and you can copy the right one from there.
Report a Pinout Error or Submit Tested Code Snippets
Found a pin mapping quirk or built a custom ESPHome YAML driver for GT911 Capacitive Touch Controller? Submit a pull request or report corrections to our index.