Skip to content

Conversation

swoboda1337
Copy link
Member

Description:

Add note about hardware version

Related issue (if applicable): fixes esphome/esphome#10738

Pull request in esphome with YAML changes (if applicable):

  • esphome/esphome#

Checklist:

  • I am merging into next because this is new documentation that has a matching pull-request in esphome as linked above.
    or

  • I am merging into current because 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.rst when creating new documents for new components or cookbook.

New Component Images

If you are adding a new component to ESPHome, you can automatically generate a standardized black and white component name image for the documentation.

To generate a component image:

  1. Comment on this pull request with the following command, replacing COMPONENT_NAME with your component name in UPPER_CASE format with underscores (e.g., BME280, SHT3X, DALLAS_TEMP):

    @esphomebot generate image COMPONENT_NAME
    
  2. The ESPHome bot will respond with a downloadable ZIP file containing the SVG image.

  3. Extract the SVG file and place it in the images/ folder of this repository.

  4. Use the image in your component's index table entry in /components/index.rst.

Example: For a component called "DHT22 Temperature Sensor", use:

@esphomebot generate image DHT22

@esphome esphome bot added the current label Sep 22, 2025
Copy link

netlify bot commented Sep 22, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 51cb675
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/68dd44e051791e0008db75ee
😎 Deploy Preview https://deploy-preview-5390--esphome.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link
Contributor

coderabbitai bot commented Sep 22, 2025

Walkthrough

Documentation for the HTU21D sensor model option was expanded with an advisory note that some boards may be mislabeled and to try HTU21D if I2C errors occur; the default remains HTU21D. No functional, configuration, or public API changes.

Changes

Cohort / File(s) Summary
Docs: HTU21D model guidance
content/components/sensor/htu21d.md
Expanded the model option description to note possible board mislabeling and advise trying HTU21D when I2C errors occur; default unchanged (HTU21D).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

current

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Linked Issues Check ⚠️ Warning The change only adds documentation advising users to try the default HTU21D model if I2C errors occur, but the linked issue required diagnosing and implementing a code‐level mitigation for hardware NACK and boot loops on ESP32 boards. Please implement or reference a code‐level handling or detection of mislabeled HTU21D devices to fully address the I2C hardware NACK and continuous reboot issue described in issue #10738.
✅ Passed checks (4 passed)
Check name Status Explanation
Title Check ✅ Passed The title “[htu21d] Add note about hardware version” clearly identifies that the primary change is adding a note regarding hardware version in the htu21d documentation and concisely summarizes the main adjustment without unnecessary noise or vagueness.
Out of Scope Changes Check ✅ Passed All modifications are confined to the htu21d documentation file and directly relate to the stated objective of adding a hardware version note without introducing unrelated files or code changes.
Description Check ✅ Passed The pull request description succinctly states the addition of a hardware version note and references the related issue, which directly pertains to the documented change in the htu21d component.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 45047bd and 51cb675.

📒 Files selected for processing (1)
  • content/components/sensor/htu21d.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • content/components/sensor/htu21d.md

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.

@swoboda1337 swoboda1337 requested a review from bdraco October 1, 2025 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

I2C Hardware NACK and continuous boot loop on wt32-eth01 and ESPHome 2025.8.3

1 participant