esphome / esphome/feature-requests

several xpt2046, please implement "touch:" like "display:" to have more than one xpt2046

Open
#1,272 1 comment 0 reactions 0 assignees View on GitHub
alternative-offered component: xpt2046
Dominant language
No language data
Stars
450
Forks
29
PR merge metrics
No merged PRs in 30d

Description

**Describe the problem you have/What new integration you would like**

Hello,

like the "display:" then you can add many display, can you please implement "touch:" to have more than only one xpt2046?

i just want to make a big remote and use 2 TFT ILI9341 screen with xpt2046, but with the "xpt2046:" i cannot put more than one touchscreen...like :
```
touch:
- platform: xpt2046
xpt2046_id: touchscreen_up
id: touch_1
x_min: 165
x_max: 320
y_min: 205
y_max: 240

- platform: xpt2046
xpt2046_id: touchscreen_down
id: touch_2
x_min: 165
x_max: 320
y_min: 205
y_max: 240
```
just like display: is used in EspHome :
```
display:
- platform: ili9341
model: "TFT_2.4"
cs_pin: 32
dc_pin: 33
led_pin: 5
reset_pin: 26
rotation: 270
id: display
```

like this all the "touch" component like xpt2046, mpr121, ttp229_lsf, esp32_touch can be add several times on the same ESP32 or others arduino board...

Thanks for your reply,

Olivier
**Please describe your use case for this integration and alternatives you've tried:**

**Additional context**

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the existing display: multi-instance configuration with the xpt2046: configuration and the other touch components named in the request. Define how a touch: list would identify multiple xpt2046 devices, then verify the supplied two-touchscreen example and confirm that several touch components can coexist on one board.

Written by the indexing model from the issue text.

Assessment

Tech stack
arduino
Domain
embedded-iot
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.