-
-
Couldn't load subscription status.
- Fork 2.1k
Add installation guide for ESPHome with uv #5481
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: current
Are you sure you want to change the base?
Conversation
Added instructions for installing ESPHome using the uv package manager.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR adds installation instructions for ESPHome using the uv package manager, providing users with an alternative cross-platform installation method that is faster and simpler than traditional pip-based installations.
- Added a new section documenting uv as a cross-platform installation option
- Included commands for both temporary execution and permanent tool installation
- Provided upgrade instructions for maintaining the installation
|
Note Other AI code review bot(s) detectedCodeRabbit has detected other AI code review bot(s) in this pull request and will avoid duplicating their findings in the review comments. This may lead to a less comprehensive review. WalkthroughAdds a new cross-platform "Cross-platform using uv" installation section to the ESPHome installation guide, describing how to install Changes
Sequence Diagram(s)(No sequence diagram: changes are documentation-only and do not modify runtime control flow.) Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Suggested reviewers
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
✅ Deploy Preview for esphome ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
♻️ Duplicate comments (1)
content/guides/installing_esphome.md (1)
21-21: Use uppercase PATH.Refer to the PATH environment variable in uppercase: “Now esphome will be available on your PATH.”
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/guides/installing_esphome.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**
⚙️ CodeRabbit configuration file
- Do not generate or add any sequence diagrams
Files:
content/guides/installing_esphome.md
🪛 LanguageTool
content/guides/installing_esphome.md
[grammar] ~6-~6: Use a hyphen to join words.
Context: ...stalling ESPHome Manually" --- ## Cross platform using uv [uv](https://docs.ast...
(QB_NEW_EN_HYPHEN)
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/guides/installing_esphome.md (1)
26-26: Consider formatting the upgrade instruction as a shell code block for consistency.The upgrade instruction is currently inline code within plain text, while the installation (lines 16–18) and verification (lines 22–24) steps use shell code blocks. Making this a separate code block would improve visual consistency and make the command easier to copy-paste.
-Upgrade to the latest version using `uv tool upgrade esphome` +Upgrade to the latest version: + +```shell +uv tool upgrade esphome +```
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/guides/installing_esphome.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**
⚙️ CodeRabbit configuration file
- Do not generate or add any sequence diagrams
Files:
content/guides/installing_esphome.md
🔇 Additional comments (1)
content/guides/installing_esphome.md (1)
12-12: The uv installation documentation link is valid and accessible.The URL
https://docs.astral.sh/uv/guides/install-python/has been verified as a working, current documentation page (last updated July 17, 2025). No issues found.
|
@swoboda1337 - all good? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
content/guides/installing_esphome.md (1)
26-26: Consider wrapping the upgrade command in a shell code block for consistency.The upgrade instruction is currently inline text with backticks. The verification command above it (lines 22–24) uses a dedicated shell code block. For visual consistency and scannability, consider applying the same pattern:
-Upgrade to the latest version using `uv tool upgrade esphome` +```shell +uv tool upgrade esphome +```
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
content/guides/installing_esphome.md(1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**
⚙️ CodeRabbit configuration file
- Do not generate or add any sequence diagrams
Files:
content/guides/installing_esphome.md
🔇 Additional comments (1)
content/guides/installing_esphome.md (1)
12-12: External documentation links verified as valid.Both uv documentation links have been confirmed as currently accessible and up-to-date:
- https://docs.astral.sh/uv/guides/install-python/ is valid and accessible
- https://docs.astral.sh/uv/guides/tools/ is valid and accessible
No link rot detected. The content is ready as-is.
Added instructions for installing ESPHome using the uv package manager.
Description:
Related issue (if applicable): fixes
Pull request in esphome with YAML changes (if applicable):
Checklist:
I am merging into
nextbecause this is new documentation that has a matching pull-request in esphome as linked above.or
I am merging into
currentbecause this is a fix, change and/or adjustment in the current documentation and is not for a new component or feature.Link added in
/components/index.rstwhen creating new documents for new components or cookbook.