The latest iot_button version (≥4) is not used in esp_lvgl_port. (BSP-716)

[ehsanziyaee]

Board

LiLyGo S3

Hardware Description

lilygo-s3_amoled

IDE Name

vscode

Operating System

ubuntu 24.04

Description

If someone uses the latest iot_button version (≥4) in the .yml file of a custom project and also uses esp_lvgl_port, there will be a conflict in the iot_button API version, because only one version is downloaded in the managed_components folder.

Sketch

there is no code

Other Steps to Reproduce

update iot_button version in esp_lvgl_port (esp_lvgl_port_button.h/c)

I have checked existing issues, README.md and ESP32 Forum

• I confirm I have checked existing issues, online documentation and Troubleshooting guide.

[github-actions]

Hi @ehsanziyaee! Please be aware that (1) the following suggestions are generated by a bot and haven't been fact-checked by Espressif Systems, (2) burning eFuses and enabling security features are irreversible operations and can damage your ESP32 device. We hope that this message will help you until an Espressif Engineer looks at your issue.

---

Thanks for reporting this. You’re right: esp_lvgl_port recently changed how it integrates with the iot_button component, and mixing iot_button v4+ in your project with an older esp_lvgl_port setup can cause API conflicts because only one version of iot_button is pulled into managed_components.

What changed:

• Since esp_lvgl_port v2.5.0, the port no longer creates buttons internally; you must create iot_button handles in your app and pass them to esp_lvgl_port. This update was made specifically to align with iot_button v4 API and avoid version conflicts. [Changelog]

What to do:

• Ensure you’re using esp_lvgl_port v2.5.0 or newer in your project. With v2.5.0+, create your buttons using iot_button v4 in your application and then register them with the LVGL port via the navigation buttons API, as shown in the usage docs. [Changelog; LVGL port usage]

Reference usage (create buttons in app, then add to LVGL port):

/* Configure your GPIO buttons (iot_button v4) */
const button_gpio_config_t bsp_button_config[] = {
    { .gpio_num = GPIO_NUM_37, .active_level = 0 },
    { .gpio_num = GPIO_NUM_38, .active_level = 0 },
    { .gpio_num = GPIO_NUM_39, .active_level = 0 },
};

const button_config_t btn_cfg = {0};
button_handle_t prev_btn_handle = NULL;
button_handle_t next_btn_handle = NULL;
button_handle_t enter_btn_handle = NULL;
iot_button_new_gpio_device(&btn_cfg, &bsp_button_config[0], &prev_btn_handle);
iot_button_new_gpio_device(&btn_cfg, &bsp_button_config[1], &next_btn_handle);
iot_button_new_gpio_device(&btn_cfg, &bsp_button_config[2], &enter_btn_handle);

const lvgl_port_nav_btns_cfg_t btns = {
    .disp = disp_handle,
    .button_prev = prev_btn_handle,
    .button_next = next_btn_handle,
    .button_enter = enter_btn_handle
};

/* Register with LVGL */
lv_indev_t* buttons_handle = lvgl_port_add_navigation_buttons(&btns);

/* ... later on deinit ... */
lvgl_port_remove_navigation_buttons(buttons_handle);

This pattern matches the current esp_lvgl_port guidance and avoids internal dependency pinning. [LVGL port usage; Registry usage page]

If you’re on esp_lvgl_port <2.5.0, you may see API mismatches with iot_button v4 (breaking changes), as captured in the button changelog. Upgrading esp_lvgl_port is the recommended fix. [Changelog; Button changelog]