Update sx126x.md - Minor typo, heirachy of heading

[PaulSchulz]

Configuration variable (dtata) is part of the sx126x.send_packet action.

Description:

Related issue (if applicable): fixes

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

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	8d6d7a3
🔍 Latest deploy log	https://app.netlify.com/projects/esphome/deploys/68c8c467aaae910008794ee0
😎 Deploy Preview	https://deploy-preview-5364--esphome.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

Walkthrough

Documentation formatting updates in content/components/sx126x.md: removed the “Triggers” section header and changed two “Configuration variables” headings from H3 to H4. No code or behavioral changes.

Changes

Cohort / File(s)	Summary
Docs formatting content/components/sx126x.md	Removed “Triggers” header; downgraded two “Configuration variables” headings from H3 to H4; no logic or configuration changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested labels

current

Suggested reviewers

• frenck
• nagyrobi

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title directly references the primary change (updating sx126x.md) and mentions both a minor typo fix and a heading hierarchy adjustment, which match the PR's documented edits. It is concise and focused on the main change. However, the title contains a spelling error ("heirachy" → "hierarchy") that should be corrected for clarity.
Description Check	✅ Passed	The PR description discusses the "dtata" configuration variable in the sx126x.send_packet action and includes standard template/checklist content, so it is on-topic and related to the documented changes. Although the body contains boilerplate and a misspelling ("dtata"), it is not unrelated to the changeset. The description does omit links to the referenced esphome PR/issue and left checklist items unmarked, but that does not make it off-topic.
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 6aa8434 and 8d6d7a3.

📒 Files selected for processing (1)

• content/components/sx126x.md (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**

⚙️ CodeRabbit configuration file

• Do not generate or add any sequence diagrams

Files:

• content/components/sx126x.md

🔇 Additional comments (1)

content/components/sx126x.md (1)

194-199: Approved — heading level and docs typo scan OK.

H4 "Configuration variables" under sx126x.send_packet is correct; ran the rg check for "dtata" and found no occurrences.

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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