Skip to content

Fix typos in qmc5883l.rst #5259

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

Open
wants to merge 2 commits into
base: current
Choose a base branch
from
Open

Fix typos in qmc5883l.rst #5259

wants to merge 2 commits into from

Conversation

mill1000
Copy link
Contributor

Description:

Fix small typos in the QMC5883L docs.

Related issue (if applicable): N/A
Pull request in esphome with YAML changes (if applicable): N/A

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 Aug 20, 2025
Copy link
Contributor

coderabbitai bot commented Aug 20, 2025

Walkthrough

Documentation-only edits for the QMC5883L sensor: corrected typos and capitalization, normalized unit notation (µT → uT), clarified I²C references, reworded oversampling descriptions, and added 128x and 64x oversampling options in the docs. No code or API changes.

Changes

Cohort / File(s) Summary
QMC5883L documentation
components/sensor/qmc5883l.rst
Corrected typos and grammar (e.g., “simular”→“similar”, “oftern”→“often”, “adverage”→“average”); standardized I²C capitalization and “I²C address”; normalized microtesla unit from “µT” to “uT”; clarified oversampling wording (reports average of N samples) and added documented oversampling values 128x and 64x. No code/API changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

  • nagyrobi
  • DjordjeMandic
  • jesserockz

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

✨ Finishing Touches
🧪 Generate unit tests
  • 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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@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: 0

🧹 Nitpick comments (4)
components/sensor/qmc5883l.rst (4)

11-14: Good typo fixes; minor style nits for clarity and correctness

  • Use “knock-off” (hyphenated).
  • Prefer “on par with” instead of “on par to”.
  • Consider tightening the last sentence.
-ESPHome. This sensor is very similar to the :ref:`HMC5883L <hmc5883l>` sensor and is often found
-as a knock off replacement. The QMC5883L sensor performs on par to the HMC5883L sensor,
-though the configuration differs. The :ref:`I²C Bus <i2c>` is required to be set up in your
-configuration for this sensor to work.
+ESPHome. This sensor is very similar to the :ref:`HMC5883L <hmc5883l>` sensor and is often found
+as a knock-off replacement. The QMC5883L sensor performs on par with the HMC5883L sensor,
+though the configuration differs. The :ref:`I²C Bus <i2c>` must be configured in your
+configuration for this sensor to work.

77-79: Clarify “average of the x samples” phrasing

“x” reads like a placeholder. Suggest clarifying that the sensor averages the configured number of samples.

-By default, the QMC5883L sensor measures each value 512 times when requesting a new value. You can, however,
-configure this amount. The result is the sensor will take the average of the x samples. Possible sampling values:
+By default, the QMC5883L sensor measures each value 512 times when requesting a new value. You can, however,
+configure this amount. As a result, the sensor reports the average of the configured number of samples (N). Possible sampling values:

47-47: Fix capitalization and extra space in “I²C address”

There’s a double space before “I²c” and the “c” should be capitalized.

-- **address** (*Optional*, int): Manually specify the  I²c address of the sensor. Defaults to ``0x0D``.
+- **address** (*Optional*, int): Manually specify the I²C address of the sensor. Defaults to ``0x0D``.

71-73: Align unit tokens with YAML example (uT vs µT)

The YAML example uses 200uT (Line 41) while the options list uses µ (micro sign). Recommend using uT in the options list for consistency with the example and to avoid non-ASCII characters in literals. Please verify that uT is the expected literal in configuration.

--  ``200µT`` (default)
--  ``800µT``
+-  ``200uT`` (default)
+-  ``800uT``

If the configuration truly expects µT, we should instead change the example at Line 41 to 200µT.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4faafc7 and 07450e4.

📒 Files selected for processing (1)
  • components/sensor/qmc5883l.rst (2 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**

⚙️ CodeRabbit Configuration File

  • Do not generate or add any sequence diagrams

Files:

  • components/sensor/qmc5883l.rst

Copy link

netlify bot commented Aug 20, 2025

Deploy Preview for esphome ready!

Name Link
🔨 Latest commit 87a6b03
🔍 Latest deploy log https://app.netlify.com/projects/esphome/deploys/68a6216185f1360008550c19
😎 Deploy Preview https://deploy-preview-5259--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 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: 0

🧹 Nitpick comments (1)
components/sensor/qmc5883l.rst (1)

68-73: Align magnetic field unit notation site-wide

Our documentation currently mixes Unicode “µT” and ASCII “uT” across several sensor pages, which can be confusing. Please pick one convention (we recommend the Unicode “µT” for proper SI notation) and update all occurrences:

• components/sensor/hmc5883l.rst
– Lines 39, 77–87: replace uT with µT
– Lines 58–59: already use µT—ensure consistency with the rest of the file

• components/sensor/qmc5883l.rst
– Lines 40, 68–72: replace uT with µT

• components/sensor/mlx90393.rst
– Already uses µT; no changes needed here

Making this change will ensure a consistent, professional presentation of units across the docs.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 07450e4 and 87a6b03.

📒 Files selected for processing (1)
  • components/sensor/qmc5883l.rst (3 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**

⚙️ CodeRabbit Configuration File

  • Do not generate or add any sequence diagrams

Files:

  • components/sensor/qmc5883l.rst
🔇 Additional comments (4)
components/sensor/qmc5883l.rst (4)

11-14: Intro wording improvements look good

The grammar/tone fixes read better and are accurate. No technical meaning changed.


47-47: I²C capitalization/style corrected

Nice consistency fix; matches typical style in the docs.


77-84: Clarify oversampling wording and confirm supported options
Confirmed that the QMC5883L component supports 512x (default), 256x, 128x, and 64x oversampling. Please apply this wording tweak in components/sensor/qmc5883l.rst (lines 77–84):

-By default, the QMC5883L sensor measures each value 512 times when requesting a new value. You can, however,
-configure this amount. The sensor reports the average of the configured number of samples (N). Possible sampling values:
+By default, the QMC5883L sensor samples each axis 512 times per measurement. You can configure this.
+The sensor reports the average of the configured number of samples (N). Possible sampling values:

40-40: Confirmed: ASCII ‘uT’ is supported
ESPHome’s QMC5883L sensor accepts both “200uT” and “800uT” in YAML as valid range values (the docs example is correct).

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.

1 participant