Skip to content

Update espressif dependencies for ESP32-P4 and ESP32-H2 compatibility#67

Open
pham-tuan-binh wants to merge 2 commits intolivekit:mainfrom
pham-tuan-binh:binh/esp-hosted-versioning
Open

Update espressif dependencies for ESP32-P4 and ESP32-H2 compatibility#67
pham-tuan-binh wants to merge 2 commits intolivekit:mainfrom
pham-tuan-binh:binh/esp-hosted-versioning

Conversation

@pham-tuan-binh
Copy link
Collaborator

@pham-tuan-binh pham-tuan-binh commented Feb 6, 2026

On newer ESP32-P4 devkits, the esp32 c6 slave come with a higher firmware version, which isn't compatible with current dependencies.

This updates the dependencies so the example can be compatible in such cases.

@CLAassistant
Copy link

CLAassistant commented Feb 6, 2026

CLA assistant check
All committers have signed the CLA.

@coderabbitai
Copy link

coderabbitai bot commented Feb 6, 2026

📝 Walkthrough

Walkthrough

Updated IDF component dependency configuration to broaden platform support. The esp_wifi_remote dependency now targets both esp32p4 and esp32h2 with version constraint ">=0.10,<2.0", and esp_hosted dependency was added with support for the same targets.

Changes

Cohort / File(s) Summary
IDF Component Configuration
components/livekit/examples/minimal_video/main/idf_component.yml
Updated espressif/esp_wifi_remote to version ">=0.10,<2.0" with multi-target support for esp32p4 and esp32h2. Added espressif/esp_hosted dependency with the same target configuration.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A dependency hop, so neat and clean,
Two targets now dance where one has been,
esp_hosted joins the party today,
While esp_wifi_remote extends its way! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The pull request title directly and accurately summarizes the main change: updating espressif dependencies to support ESP32-P4 and ESP32-H2 microcontrollers, which is exactly what the changeset accomplishes.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Fix all issues with AI agents
In `@components/livekit/examples/minimal_video/main/idf_component.yml`:
- Around line 13-15: Update the top comment in idf_component.yml that currently
references only "ESP32-P4-based development board" to include "ESP32-H2" as well
(e.g., "ESP32-P4- and ESP32-H2-based development boards") so the guidance
applies to both targets; edit the comment block shown in the diff to mention
"ESP32-H2" alongside "ESP32-P4" and keep the rest of the explanatory text
unchanged.
🧹 Nitpick comments (1)
components/livekit/examples/minimal_video/main/idf_component.yml (1)

20-22: esp_hosted has no version constraint — consider adding one for reproducibility.

esp_wifi_remote is correctly bounded with ">=0.10,<2.0", but esp_hosted is completely unpinned. A future major-version bump could silently break builds. Adding a version range (similar to esp_wifi_remote) would keep builds reproducible while still allowing compatible updates.

📌 Suggested fix
   espressif/esp_hosted:
+    version: ">=0.5,<2.0"
     rules:
       - if: "target in [esp32p4, esp32h2]"

(Adjust the lower bound to match the minimum version you've tested against.)

📜 Review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0b70346 and 0f59e92.

📒 Files selected for processing (1)
  • components/livekit/examples/minimal_video/main/idf_component.yml
🧰 Additional context used
📓 Path-based instructions (2)
components/**

📄 CodeRabbit inference engine (AGENTS.md)

Place LiveKit ESP32 SDK sources and supporting components in the components/ directory

Files:

  • components/livekit/examples/minimal_video/main/idf_component.yml
components/livekit/examples/**

📄 CodeRabbit inference engine (AGENTS.md)

Place example applications in components/livekit/examples/ directory

Files:

  • components/livekit/examples/minimal_video/main/idf_component.yml
🧠 Learnings (1)
📚 Learning: 2026-01-31T02:18:39.165Z
Learnt from: CR
Repo: livekit/client-sdk-esp32 PR: 0
File: AGENTS.md:0-0
Timestamp: 2026-01-31T02:18:39.165Z
Learning: Applies to components/** : Place LiveKit ESP32 SDK sources and supporting components in the `components/` directory

Applied to files:

  • components/livekit/examples/minimal_video/main/idf_component.yml
🔇 Additional comments (1)
components/livekit/examples/minimal_video/main/idf_component.yml (1)

16-22: No issues found. The target in [esp32p4, esp32h2] syntax and version constraint >=0.10,<2.0 are valid according to ESP-IDF component manager documentation. The rules block correctly specifies conditional dependency inclusion for the specified targets.

✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments