Have not used much yet, just console output. As i use usb keybaord input but have not connected it up - with the larger display - https://www.youtube.com/watch?v=zAN8VrhhglE
Try adding bgr=<1>; to dts ?
Here are some related issue to this display only supporting 18-bit pxel format ?
opened 05:30PM - 15 Jun 23 UTC
### The problem
With a fully wired ILI9488 connected over 4-wire SPI, any col… ors are rendered inverse to their definitions (i.e pink is green, white is black, black is white, etc.)
### Which version of ESPHome has the issue?
2023.5.5
### What type of installation are you using?
Docker
### Which version of Home Assistant has the issue?
_No response_
### What platform are you using?
ESP32
### Board
Wemos S2 mini
### Component causing the issue
ili9xxx
### Example YAML snippet
```yaml
esp32:
board: lolin_s2_mini
framework:
type: arduino
font:
- file: 'fonts/OpenSans-Regular.ttf'
id: font_opensans_regular
size: 28
spi:
clk_pin: GPIO14
mosi_pin: GPIO13
miso_pin: GPIO12
color:
- id: c_primary
red: 0%
blue: 100%
green: 0%
display:
- id: disp
platform: ili9xxx
model: "ILI9488"
cs_pin: GPIO9
dc_pin: GPIO10
reset_pin: GPIO11
update_interval: 5s
color_palette: NONE
lambda: |-
it.fill(Color::WHITE);
it.print(0, 0, id(font_opensans_regular), id(c_primary), TextAlign::TOP_LEFT, "Hello World!");
```
### Anything in the logs that might be useful for us?
```txt
[17:26:48][C][spi:101]: SPI bus:
[17:26:48][C][spi:102]: CLK Pin: GPIO14
[17:26:48][C][spi:103]: MISO Pin: GPIO12
[17:26:48][C][spi:104]: MOSI Pin: GPIO13
[17:26:48][C][spi:106]: Using HW SPI: YES
[17:26:49][C][ili9xxx:047]: ili9xxx
[17:26:49][C][ili9xxx:047]: Rotations: 0 °
[17:26:49][C][ili9xxx:047]: Dimensions: 480px x 320px
[17:26:49][C][ili9xxx:050]: Color mode: 16bit
[17:26:49][C][ili9xxx:060]: 18-Bit Mode: YES
[17:26:49][C][ili9xxx:063]: Reset Pin: GPIO11
[17:26:49][C][ili9xxx:064]: DC Pin: GPIO10
[17:26:49][C][ili9xxx:070]: Update Interval: 5.0s
[17:26:49][C][psram:020]: PSRAM:
[17:26:49][C][psram:021]: Available: YES
[17:26:49][C][psram:024]: Size: 2047 KB
```
### Additional information
My gut says that simply doing `this->invert_display_(true);` in the ili9488 setup routine ([ili9xxx_display.cpp#403](https://github.com/esphome/esphome/blob/467e42d8aa5c1dd8a6ec13b09075117d2f209e6a/esphome/components/ili9xxx/ili9xxx_display.cpp#L403)) should be sufficient - but I'm hesitating on bringing up a PR for this just in case people have perfectly colorful implementations (and we end up inverting everyone's except mine!)
Perhaps a YAML flag to invert colours would be a better idea, with a suggested default for the ili9488 (and m3stack) of `true`?
esphome:dev ← lnicolas83:ili9xxx_a
opened 09:58PM - 29 Jun 23 UTC
# What does this implement/fix?
Add model "ili9488_A" so that some screens th… at had the correct colors before PR #4849 can continue to work as before.
## Types of changes
- [ ] Bugfix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Other
**Related issue or feature (if applicable):** fixes https://github.com/esphome/issues/issues/4603
**Pull request in [esphome-docs](https://github.com/esphome/esphome-docs) with documentation (if applicable):** https://github.com/esphome/esphome-docs/pull/3031
## Test Environment
- [X] ESP32
- [ ] ESP32 IDF
- [ ] ESP8266
- [ ] RP2040
## Example entry for `config.yaml`:
```yaml
# Example config.yaml
display:
- platform: ili9xxx
model: ili9488_A
id: my_display
cs_pin: GPIO14
dc_pin: 10
reset_pin: 9
spi_id: spi_display
```
## Checklist:
- [X] The code change is tested and works locally.
- [ ] Tests have been added to verify that the new code works (under `tests/` folder).
If user exposed functionality or configuration variables are added/changed:
- [X] Documentation added/updated in [esphome-docs](https://github.com/esphome/esphome-docs).
and on Raspberry Pi
1 Like