Add VL53L1X time-of-flight distance sensor documentation

[will-tm]

Description:

Add documentation for the VL53L1X time-of-flight distance sensor component.

The VL53L1X is the successor to the VL53L0X with improved range (up to 4m) and additional features:

• Distance modes (short/medium/long) for different range/accuracy trade-offs
• Configurable timing budget (15-500ms)
• Region of Interest (ROI) configuration for narrower field of view
• Multi-sensor support via XSHUT pin control
• Calibration offset support

Related issue (if applicable): N/A

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

• [vl53l1x] Add VL53L1X time-of-flight distance sensor esphome#13605

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.md when creating new documents for new components or cookbook.

[esphome]

As this is a feature matched with a PR in https://github.com/esphome/esphome, please target your PR to the next branch and rebase.

[esphome]

Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍

Learn more about our pull request process.

[netlify]

✅ Deploy Preview for esphome ready!

Name	Link
🔨 Latest commit	a960dc8
🔍 Latest deploy log	https://app.netlify.com/projects/esphome/deploys/6994b871f7d7920008b09741
😎 Deploy Preview	https://deploy-preview-5994--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.

Base branch has been corrected - dismissing previous review.

[coderabbitai]

Walkthrough

A new VL53L1X distance sensor component is added to the ESPHome documentation. This includes an index entry and a comprehensive guide covering the sensor's configuration, wiring, operating modes, Region of Interest settings, multi-sensor setups, and calibration procedures.

Changes

Cohort / File(s)

Summary

VL53L1X Sensor Documentation content/components/_index.md, content/components/sensor/vl53l1x.md

Index entry added for the VL53L1X sensor; comprehensive new documentation file created with front-matter metadata, sensor platform overview, wiring instructions, YAML configuration variables (distance_mode, timing_budget, timeout, signal_rate_limit, ROI parameters, offset, address, enable_pin, update_interval), distance modes (short/medium/long), ROI details, multi-sensor guidance on single I2C bus, and calibration workflow.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Suggested labels

has-parent, next

Suggested reviewers

• jesserockz
• swoboda1337

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title clearly and accurately summarizes the main change: adding documentation for the VL53L1X time-of-flight distance sensor component.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description clearly relates to the changeset, which adds VL53L1X sensor documentation with comprehensive details about features, configuration options, and multi-sensor support.

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

✨ Finishing touches

• 📝 Generate docstrings

---

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.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@content/components/sensor/vl53l1x.md`:
- Around line 152-155: The ordered list in content/components/sensor/vl53l1x.md
currently uses sequential numbers (1., 2., 3.) which triggers markdownlint rule
MD029; change each ordered list item so every line starts with "1." (e.g.,
replace "2." and "3." with "1.") so the three lines under the list use "1."
consistently; keep the same text/content and spacing so the driver
initialization explanation and steps remain unchanged.