Skip to content

Sync dev to main: Apollo mmWave 2.3.0 guides - #1198

Merged
Bunton33 merged 1 commit into
mainfrom
dev
Oct 31, 2026
Merged

Bunton33 merged 1 commit into
mainfrom
dev

Conversation

@Bunton33

Copy link
Copy Markdown
Contributor

Publishes #1197 (Apollo mmWave 2.3.0 guides, Radar setup card, slider lock clip, zone map in feet, Zone Type tips on the R PRO-1 and MTR-1 zone pages, Homey pages kept free of the Home Assistant-only tips). dev carries only that commit ahead of main.

🤖 Generated with Claude Code

…in feet (#1197)

* docs: Apollo mmWave 2.3.0 dashboard guides and screenshots

Update the setup and tuning guides for Apollo mmWave 2.3.0: the Start
here card, the Radar setup cards (gate radar and LD2450), locked
sliders with Unlock, the Device card, the 24 hour occupancy history,
gate rows named by distance, Any zone, and resets that ask first.

The zone map section covers the fitted 120 degree view and its range
caption, feet or meters with the m / ft switch, the Locked button that
also locks Cone rotation, and the Zone presence, LD2450 Live and
LD2450 Controls cards. Troubleshooting adds an empty or single-dot
map, the 2.2.7 inches fix, locked sliders and the support file.

Replace the Start here, Controls and zone map screenshots and add
screenshots of the Radar setup, Detection Range, Still Thresholds,
Device and LD2450 Live cards, plus a slider lock clip. The MTR-1
wrapper's intro no longer calls the zone map the whole tab.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: Zone Type notes for the Apollo mmWave zone map

Apollo mmWave 2.3.0's Radar setup card recommends Zone Type Disabled,
because the zone map replaces the LD2450's built-in zones. On
Detection with no built-in zones set, the radar reports nobody.

The R PRO-1 zone pages and the MTR-1 HLK page now say to leave Zone
Type on Disabled (Close detection in the HLK app) when drawing zones on
the dashboard. The MTR-1 zones page and both sensor definition pages
are included by Homey pages, so they only gain the platform-neutral
note that Detection with no zones set detects nobody.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: Point the home page at the Apollo mmWave zone map

The Radar & zones list linked to the standalone Zone Mapper beta,
which the Apollo mmWave zone map has replaced. Link the zone drawing
section of the Apollo mmWave dashboard guide instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: Review fixes for the Apollo mmWave 2.3.0 guides

Setup guide: "What to do first" now runs Dynamic Background Correction
before calibrating on an R PRO-1, says to skip calibration without the
LD2412 in step 2 instead of step 3, and nests the Auto-calibrate and
dimmed Gate Energy screenshots under the steps they show. MTR-1 readers
get a draw-zones link where the page only pointed at calibration, and
a taken-control dashboard is said to miss the updated Start here steps.

Tuning guide: label the Start here screenshot as the MSR-1 card, add
the R PRO-1 background correction step before "Run a calibration",
turn the walk test and the Cone rotation steps into numbered lists, and
point MTR-1 readers to the LD2450 Radar setup section. The Device card
now covers the MTR-1 (LD2450 firmware, no Firmware update row) and the
"Restart device (also restarts the radar)" label, the R PRO-1 history
names its LD2412 lines, and the tour's images sit under their bullets.
Smaller fixes: R PRO-1 Start here stays at the top of the tab, the
m / ft switch is in the bottom-right corner (undo sits next to it),
"Use recommended settings" can replace the Multi Target Tracking
button, and moving the sensor means redrawing zones as well.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: Point zone pages at the Apollo mmWave zone map, keep Homey clean

HLK app pages: the "Drawing zones with the Apollo mmWave dashboard?"
tip now sits above step 4, so dashboard users pick Close detection
before the step that selects Area Detection, and step 4's screenshot
follows its own tip again. The R PRO-1 HLK page gets the same tip; no
Homey page includes it.

The MTR-1 Home Assistant zones tip now says to leave Zone Type on
Disabled, like the R PRO-1 one. The orphan Homey copy of that page
includes it by line range so it skips this Home Assistant-only tip.

Choosing an mmWave sensor replaces the Zone Mapper beta tip with a
pointer to the Apollo mmWave zone map. Its Homey copy now includes the
page by line range and skips that tip; the rest renders unchanged.
The Homey home page drops the Zone Mapper beta link, a Home Assistant
HACS tool (Homey's Radar regions guides are listed below it), and the
Zone Mapper pages say Apollo mmWave already has a zone map and to keep
Zone Type on Disabled.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* docs: Address review: support file privacy note, Close detection in step 4, keep a chosen grid

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 31, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review: 1
  • beta

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 636ac279-4df9-45ea-bd5d-d69b1755b4fd

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@Bunton33
Bunton33 merged commit 12d7116 into main Oct 31, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants