Bunton33 · Nov 5, 2026 · Nov 2, 2026 · Nov 2, 2026 · Nov 2, 2026 · Nov 2, 2026
diff --git a/docs/_snippets/zone-mapper-tool.md b/docs/_snippets/zone-mapper-tool.md
@@ -110,6 +110,10 @@ The card needs to know which X/Y coordinate sensors to track:
 
     Changing the card's units instead also works, but then you need to adjust the grid distances to match, so converting the sensors is the recommended path.
 
+!!! tip "Apollo mmWave does this for you"
+
+    With the Apollo mmWave integration 2.4.0 or newer installed, you can skip the conversion above. Apollo mmWave shows the Target X and Y of an Apollo MTR-1 or R PRO-1 in mm on its own: on a new sensor as soon as you add it, and on one you already had once, after Home Assistant starts, with the notification **Apollo mmWave: Target X and Y now in mm**. Zone Mapper's card reads them in mm then too. Apollo mmWave leaves alone a sensor whose unit you picked in its settings, which you change there, and one that an automation, a script, or a helper uses. For a sensor in use, first change any number it's compared to into mm, 25.4 times as large, then, as an administrator, press **Show Target X and Y in mm** on the **Radar setup** card above its zone map. The button switches only sensors whose unit Home Assistant picked on its own, never one whose unit you picked. To go back to inches, choose **in** under **Unit of measurement** in the sensor's settings. See [Target X and Y units](/products/general/setup/apollo-mmwave-dashboard.md#target-x-and-y-units).
+
 ### Add zones
 
 1. Click the **Configure** drop-down, then **Zones**.

diff --git a/docs/assets/apollo-mmwave-calibrate-idle.png b/docs/assets/apollo-mmwave-calibrate-idle.png
diff --git a/docs/assets/apollo-mmwave-calibrate-r-pro-1.png b/docs/assets/apollo-mmwave-calibrate-r-pro-1.png
diff --git a/docs/assets/apollo-mmwave-calibrate-result.png b/docs/assets/apollo-mmwave-calibrate-result.png
diff --git a/docs/assets/apollo-mmwave-gate-energy-engineering-off.png b/docs/assets/apollo-mmwave-gate-energy-engineering-off.png
diff --git a/docs/assets/apollo-mmwave-gate-energy-live.png b/docs/assets/apollo-mmwave-gate-energy-live.png
diff --git a/docs/assets/apollo-mmwave-gate-energy.mp4 b/docs/assets/apollo-mmwave-gate-energy.mp4
diff --git a/docs/assets/apollo-mmwave-ld2450-live-count.png b/docs/assets/apollo-mmwave-ld2450-live-count.png
diff --git a/docs/assets/apollo-mmwave-ld2450-live.png b/docs/assets/apollo-mmwave-ld2450-live.png
diff --git a/docs/assets/apollo-mmwave-radar-setup-and-zone-map.png b/docs/assets/apollo-mmwave-radar-setup-and-zone-map.png
diff --git a/docs/assets/apollo-mmwave-radar-setup-target-units-in-use.png b/docs/assets/apollo-mmwave-radar-setup-target-units-in-use.png
diff --git a/docs/assets/apollo-mmwave-start-here.png b/docs/assets/apollo-mmwave-start-here.png
diff --git a/docs/assets/apollo-mmwave-zone-list.png b/docs/assets/apollo-mmwave-zone-list.png
diff --git a/docs/assets/apollo-mmwave-zone-map-configure.png b/docs/assets/apollo-mmwave-zone-map-configure.png
diff --git a/docs/assets/apollo-mmwave-zone-map-draw-poster.jpg b/docs/assets/apollo-mmwave-zone-map-draw-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-map-draw.mp4 b/docs/assets/apollo-mmwave-zone-map-draw.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map-empty.png b/docs/assets/apollo-mmwave-zone-map-empty.png
diff --git a/docs/assets/apollo-mmwave-zone-map-expand-poster.jpg b/docs/assets/apollo-mmwave-zone-map-expand-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-map-expand.mp4 b/docs/assets/apollo-mmwave-zone-map-expand.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map-expanded-phone.png b/docs/assets/apollo-mmwave-zone-map-expanded-phone.png
diff --git a/docs/assets/apollo-mmwave-zone-map-history-poster.jpg b/docs/assets/apollo-mmwave-zone-map-history-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-map-history.mp4 b/docs/assets/apollo-mmwave-zone-map-history.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map-ignore.png b/docs/assets/apollo-mmwave-zone-map-ignore.png
diff --git a/docs/assets/apollo-mmwave-zone-map-live-poster.jpg b/docs/assets/apollo-mmwave-zone-map-live-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-map-live.mp4 b/docs/assets/apollo-mmwave-zone-map-live.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map-offline.png b/docs/assets/apollo-mmwave-zone-map-offline.png
diff --git a/docs/assets/apollo-mmwave-zone-map-view-only.png b/docs/assets/apollo-mmwave-zone-map-view-only.png
diff --git a/docs/assets/apollo-mmwave-zone-map-walk-poster.jpg b/docs/assets/apollo-mmwave-zone-map-walk-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-map-walk.mp4 b/docs/assets/apollo-mmwave-zone-map-walk.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map-zoom-poster.png b/docs/assets/apollo-mmwave-zone-map-zoom-poster.png
diff --git a/docs/assets/apollo-mmwave-zone-map-zoom.mp4 b/docs/assets/apollo-mmwave-zone-map-zoom.mp4
diff --git a/docs/assets/apollo-mmwave-zone-map.png b/docs/assets/apollo-mmwave-zone-map.png
diff --git a/docs/assets/apollo-mmwave-zone-name-poster.jpg b/docs/assets/apollo-mmwave-zone-name-poster.jpg
diff --git a/docs/assets/apollo-mmwave-zone-name.mp4 b/docs/assets/apollo-mmwave-zone-name.mp4
diff --git a/.../homey/products/general/calibrating-and-updating/zone-configuration/zones-ha.md b/.../homey/products/general/calibrating-and-updating/zone-configuration/zones-ha.md
@@ -4,4 +4,6 @@ description: "Tutorial for MTR-1 Home Assistant Zone Configuration."
 ---
 --8<-- "products/mtr1/setup/zones-ha.md:5:6"
 
---8<-- "products/mtr1/setup/zones-ha.md:11:"
+--8<-- "products/mtr1/setup/zones-ha.md:11:57"
+
+--8<-- "products/mtr1/setup/zones-ha.md:63:"
diff --git a/docs/products/general/setup/apollo-mmwave-dashboard-setup.md b/docs/products/general/setup/apollo-mmwave-dashboard-setup.md
diff --git a/docs/products/general/setup/apollo-mmwave-dashboard.md b/docs/products/general/setup/apollo-mmwave-dashboard.md
diff --git a/docs/products/mtr1/faq.md b/docs/products/mtr1/faq.md
@@ -47,7 +47,8 @@ description: Frequently asked questions about the MTR-1 mmWave sensor.
 * The LD2450 radar in the MTR-1 has no sensitivity setting, and ESPHome has none to offer, so it can't be tuned gate by gate like the MSR-2. Here's what you can adjust instead:
     * **Where it's mounted and where it points.** This decides what the radar sees, including a little of the next room and reflections off mirrors and glass. See the [mounting tips](setup/general-tips.md#mounting).
     * **Zones.** Draw zones on the [Apollo mmWave zone map](setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) and automate on a zone's presence sensor: only someone inside the zone turns it on.
-    * **Spots to ignore.** Leave a spot outside every zone, such as a mirror, a fan, or the doorway to the next room, and nobody there turns a zone on.
+    * **Spots to ignore.** Draw an [ignore zone](setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) over a spot such as a mirror, a fan, or the doorway to the next room (Apollo mmWave 2.4.0 or newer), or leave the spot outside every zone, and nobody there turns a zone on.
+    * **Hold.** Give a zone a [hold time](setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) so it stays on for a while after the radar loses someone who sits still (Apollo mmWave 2.4.0 or newer).
     * **Timeout** (**Radar Timeout** on the Apollo mmWave dashboard). It sets how long **LD2450 Presence** stays on after the radar stops seeing anyone in its whole view. It doesn't hold the zones you draw.
     * **A delay in your automation.** Give the "turn off" trigger a delay, such as 2 minutes, so a short dropout doesn't turn the lights off.
 * Judge detection only while the MTR-1 is mounted where it will stay. Held in your hand, the whole room moves around the radar, so the dots and zones won't match the room.

diff --git a/docs/products/mtr1/setup/apollo-mmwave-dashboard.md b/docs/products/mtr1/setup/apollo-mmwave-dashboard.md
@@ -5,6 +5,6 @@ description: Draw occupancy zones for your Apollo MTR-1 over the radar's live ta
 
 # Draw MTR-1 zones with the Apollo mmWave dashboard
 
-On an Apollo MTR-1, the dashboard tab is built around the zone map, so [Draw zones on the R PRO-1 and MTR-1](#draw-zones-on-the-r-pro-1-and-mtr-1) is the section you need, and its troubleshooting starts at [The zone map shows nobody, or only one person](#the-zone-map-shows-nobody-or-only-one-person). The calibration and tuning sections are for the Apollo MSR-1, MSR-2, and R PRO-1.
+On an Apollo MTR-1, the dashboard tab is built around the zone map, so [Draw zones on the R PRO-1 and MTR-1](#draw-zones-on-the-r-pro-1-and-mtr-1) is the section you need: its eight steps take you from a new sensor to a zone that lights up when you walk into it. Its troubleshooting starts at [The zone map shows nobody, or only one person](#the-zone-map-shows-nobody-or-only-one-person). The calibration and tuning sections are for the Apollo MSR-1, MSR-2, and R PRO-1.
 
 --8<-- "products/general/setup/apollo-mmwave-dashboard.md:7:"
diff --git a/docs/products/mtr1/setup/sensor-definitions.md b/docs/products/mtr1/setup/sensor-definitions.md
@@ -58,7 +58,7 @@ Once added to Home Assistant you can configure different settings for your MTR-1
     |---------|:-------:|--------------|
     | **ESP Reboot** | — | Restarts the device. Helpful for troubleshooting or refreshing the connection. |
     | **Multi Target Tracking** | from module | Turns multi-target tracking on or off. Initial state is read from the LD2450 at boot. |
-    | **Timeout** | 5 s | How long **LD2450 Presence**, **LD2450 Moving Target**, and **LD2450 Still Target** stay on after the radar stops seeing a target of their kind. **LD2450 Presence** starts counting only once the radar sees nobody anywhere in its view, so it stays on while any target is in view. **LD2450 Moving Target** and **LD2450 Still Target** each count on their own, from the last moving or the last still target. It holds only those three, not zones: a zone you draw on the Apollo mmWave zone map turns off as soon as nobody is in it, because Apollo mmWave 2.3.0 zones have no hold. The Apollo mmWave dashboard calls this setting **Radar Timeout**. See the <a href="https://esphome.io/components/sensor/ld2450.html#ld2450-binary-sensors" target="_blank" rel="noopener">ESPHome LD2450 docs</a>. |
+    | **Timeout** | 5 s | How long **LD2450 Presence**, **LD2450 Moving Target**, and **LD2450 Still Target** stay on after the radar stops seeing a target of their kind. **LD2450 Presence** starts counting only once the radar sees nobody anywhere in its view, so it stays on while any target is in view. **LD2450 Moving Target** and **LD2450 Still Target** each count on their own, from the last moving or the last still target. It holds only those three, not zones: a zone you draw on the Apollo mmWave zone map turns off as soon as nobody is in it. From Apollo mmWave 2.4.0, a zone's [hold time](/products/mtr1/setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) keeps it on for a while after the radar loses someone who sat still inside it, but someone who walks out usually turns it off without waiting for the hold. The Apollo mmWave dashboard calls this setting **Radar Timeout**. See the <a href="https://esphome.io/components/sensor/ld2450.html#ld2450-binary-sensors" target="_blank" rel="noopener">ESPHome LD2450 docs</a>. |
     | **Zone Type** | Disabled | Zone detection mode: `Disabled`, `Detection` (only detect targets inside the zone), or `Filter` (exclude the zone from detection). With `Detection` and no zones set, the radar detects nobody, so keep `Disabled` unless you use the radar's own zones (the **Zone-1 / Zone-2 / Zone-3** settings below). |
     | **Zone-1 / Zone-2 / Zone-3 X1, X2** | — | Start and end X coordinates of the zone in mm (-4860 left to 4860 right). |
     | **Zone-1 / Zone-2 / Zone-3 Y1, Y2** | — | Start and end Y coordinates of the zone in mm (0 to 7560). |

diff --git a/docs/products/mtr1/setup/zones-ha.md b/docs/products/mtr1/setup/zones-ha.md
@@ -6,7 +6,7 @@ description: Set up the three radar zones on your MTR-1 in Home Assistant by ent
 
 !!! tip "Prefer a guided dashboard?"
 
-    The Apollo mmWave integration gives your Apollo MTR-1 its own dashboard tab with a zone map where you draw zones over the radar's live targets, with no Plotly card or YAML to set up. The [Apollo mmWave dashboard guide](/products/mtr1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) walks you through it as a guided alternative to the manual steps below. If you draw zones there, leave **Zone Type** on **Disabled** instead of entering zones below: the dashboard's zone map replaces the radar's built-in zones, and its **Radar setup** card offers **Set Zone Type to Disabled** when it isn't.
+    The Apollo mmWave integration gives your Apollo MTR-1 its own dashboard tab with a zone map where you draw zones over the radar's live targets, with no Plotly card or YAML to set up. The [Apollo mmWave dashboard guide](/products/mtr1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) walks you through it as a guided alternative to the manual steps below. If you draw zones there, leave **Zone Type** on **Disabled** instead of entering zones below: the dashboard's zone map replaces the radar's built-in zones, and its **Radar setup** card offers **Set Zone Type to Disabled** when it isn't. To keep a fan or a curtain from turning those zones on, draw an [ignore zone](/products/mtr1/setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) over it on the map.
 
 This guide shows you how to set up your MTR-1's three zones by entering the X and Y coordinates for each one. First you add a card to your dashboard that shows the radar's live targets, then you use it to work out the coordinates for each zone, in millimeters. You can enter the values in Home Assistant, as shown below, or directly on the device's web page by visiting its IP address or hostname.local.
 
@@ -56,6 +56,10 @@ The target sensors and zone settings are on your MTR-1's page in the ESPHome int
 
     If your Home Assistant uses the metric system, go straight to [Enter your zones](#enter-your-zones).
 
+!!! tip "Apollo mmWave does this for you"
+
+    With the Apollo mmWave integration 2.4.0 or newer, you can skip this section too. Apollo mmWave shows your MTR-1's Target X and Y in mm on its own: on a new MTR-1 as soon as you add it, and on one you already had once, after Home Assistant starts, with the notification **Apollo mmWave: Target X and Y now in mm**. It leaves alone a sensor whose unit you picked in its settings, which you change there, and one that an automation, a script, or a helper uses. For a sensor in use, first change any number it's compared to into mm, 25.4 times as large, then, as an administrator, press **Show Target X and Y in mm** on the **Radar setup** card above the zone map. The button switches only sensors whose unit Home Assistant picked on its own, never one whose unit you picked. To go back to inches, choose **in** under **Unit of measurement** in the sensor's settings. The [Apollo mmWave dashboard guide](/products/mtr1/setup/apollo-mmwave-dashboard.md#target-x-and-y-units) has the details.
+
 If you use the imperial system, your Target 1-3 X and Y sensors report in inches (in). For the targets to show up correctly on the card, change all three X and all three Y target sensors to millimeters (mm).
 
 1\. In the **Sensors** section, find the Target 1-3 X and Y sensors and select one of them.

diff --git a/docs/products/mtr1/setup/zones-hlk.md b/docs/products/mtr1/setup/zones-hlk.md
@@ -42,7 +42,7 @@ With the app installed, you'll turn on the radar's Bluetooth, connect to it from
 
 !!! tip "Drawing zones with the Apollo mmWave dashboard?"
 
-    In step 4, pick **Close detection** instead of **Area Detection** (Zone Type **Disabled** in Home Assistant). The dashboard's [zone map](/products/mtr1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) replaces the app's areas. On **Area Detection**, the radar reports only people inside the app's areas, so anyone else is missing from the map, and **Area Filtering** hides the people inside them.
+    In step 4, pick **Close detection** instead of **Area Detection** (Zone Type **Disabled** in Home Assistant). The dashboard's [zone map](/products/mtr1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) replaces the app's areas. On **Area Detection**, the radar reports only people inside the app's areas, so anyone else is missing from the map, and **Area Filtering** hides the people inside them. To keep a fan or a curtain from turning the map's zones on, draw an [ignore zone](/products/mtr1/setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) over it on the map.
 
 4\. Select **Area Detection** (drawing zones on the Apollo mmWave dashboard instead? Pick **Close detection** and skip the areas; see the tip above), then toggle Area 1, 2, or 3 and you will see a box with the corresponding number pop up. Then you can press and hold the box to move it and resize it. When your zones are set then select Submit and you should see Setup successfully.
 

diff --git a/docs/products/rpro1/setup/apollo-mmwave-dashboard.md b/docs/products/rpro1/setup/apollo-mmwave-dashboard.md
@@ -5,4 +5,6 @@ description: Draw occupancy zones over the live targets of your Apollo R PRO-1,
 
 # Draw R PRO-1 zones and tune the LD2412 addon with the Apollo mmWave dashboard
 
+An Apollo R PRO-1 tab has a job for each radar. For the LD2450, [Draw zones on the R PRO-1 and MTR-1](#draw-zones-on-the-r-pro-1-and-mtr-1) takes you from a new sensor to a working zone in eight steps. For the optional LD2412 addon, start at [Calibrate with an empty room](#calibrate-with-an-empty-room), and [R PRO-1 and its LD2412 radar](#r-pro-1-and-its-ld2412-radar) covers what's different from an MSR-1 or MSR-2.
+
 --8<-- "products/general/setup/apollo-mmwave-dashboard.md:7:"
diff --git a/docs/products/rpro1/setup/rpro1-sensor-definitions.md b/docs/products/rpro1/setup/rpro1-sensor-definitions.md
@@ -35,7 +35,7 @@ The R PRO-1 pairs two radars: an **LD2450** that tracks the position of up to th
 
     | Sensor | Default Update | Details |
     |--------|:--------------:|---------|
-    | **Combined Presence** | real-time | Combined occupancy: shows **Detected** when either the LD2450 or the LD2412 radar sees a target, and **Clear** when neither does. Use this entity for automations and dashboards instead of the individual radar presence sensors. |
+    | **Combined Presence** | real-time | Combined occupancy: shows **Detected** when either the LD2450 or the LD2412 radar sees a target, and **Clear** when neither does. Use this entity for automations and dashboards instead of the individual radar presence sensors. It comes with R PRO-1 firmware newer than 26.3.2.1. On 26.3.2.1 and earlier, use **LD2412 Presence** for the whole room, or **LD2450 Presence** on an R PRO-1 without the LD2412. |
 
     #### Radar presence (LD2412 mmWave)
 
@@ -55,7 +55,7 @@ The R PRO-1 pairs two radars: an **LD2450** that tracks the position of up to th
 
     | Sensor | Default Update | Details |
     |--------|:--------------:|---------|
-    | **LD2450 Presence** | real-time | Whether the radar currently detects any target. Great for occupancy automations. |
+    | **LD2450 Presence** | real-time | Whether the LD2450 currently detects any target, anywhere in its view. For automations, use **Combined Presence** where your firmware has it. |
     | **LD2450 Moving Target** | real-time | Whether a moving target is detected. |
     | **LD2450 Still Target** | real-time | Whether a stationary target is detected. |
     | **LD2450 Presence Target Count** | real-time | Count of all presence targets (max 3). |

diff --git a/docs/products/rpro1/setup/zones-ha.md b/docs/products/rpro1/setup/zones-ha.md
@@ -14,7 +14,7 @@ description: Tutorial for R PRO-1 Home Assistant Zone Configuration.
 
 !!! tip "Prefer a guided dashboard?"
 
-    The Apollo mmWave integration gives your R PRO-1 a dashboard tab where you draw LD2450 zones over live targets and tune the LD2412 gates with a **Calibrate with empty room** button. The [Apollo mmWave dashboard guide](/products/rpro1/setup/apollo-mmwave-dashboard.md) walks you through it as a guided alternative to the manual steps below. If you draw zones there, leave **LD2450 Zone Type** on **Disabled** instead of entering zones below: the dashboard's zone map replaces the radar's built-in zones, and its **Radar setup** card offers **Set Zone Type to Disabled** when it isn't.
+    The Apollo mmWave integration gives your R PRO-1 a dashboard tab where you draw LD2450 zones over live targets and tune the LD2412 gates with a **Calibrate with empty room** button. The [Apollo mmWave dashboard guide](/products/rpro1/setup/apollo-mmwave-dashboard.md) walks you through it as a guided alternative to the manual steps below. If you draw zones there, leave **LD2450 Zone Type** on **Disabled** instead of entering zones below: the dashboard's zone map replaces the radar's built-in zones, and its **Radar setup** card offers **Set Zone Type to Disabled** when it isn't. To keep a fan or a curtain from turning those zones on, draw an [ignore zone](/products/rpro1/setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) over it on the map.
 
 Manually enter in the X and Y coordinates for each zone in Home Assistant or directly from the device's webserver by visiting the IP address or hostname.local. It's much easier to <a href="https://wiki.apolloautomation.com/products/rpro1/setup/zones-hlk/" rel="noreferrer nofollow">tune using the HLK Radartool App</a> and we suggest using that to set up your R PRO-1 LD2450.
 
@@ -76,6 +76,10 @@ Follow these steps to add a Plotly card that shows your LD2450 targets, then set
     * The Plotly chart will still render the rectangles even if the X1/X2 and Y1/Y2 values are reversed.
     * The zones cannot overlap.
 
+!!! tip "Apollo mmWave does this for you"
+
+    With the Apollo mmWave integration 2.4.0 or newer, you can skip steps 10 to 13. Apollo mmWave shows your R PRO-1's Target X and Y in mm on its own: on a new R PRO-1 as soon as you add it, and on one you already had once, after Home Assistant starts, with the notification **Apollo mmWave: Target X and Y now in mm**. It leaves alone a sensor whose unit you picked in its settings, which you change there, and one that an automation, a script, or a helper uses. For a sensor in use, first change any number it's compared to into mm, 25.4 times as large, then, as an administrator, press **Show Target X and Y in mm** on the **Radar setup** card above the zone map. The button switches only sensors whose unit Home Assistant picked on its own, never one whose unit you picked. To go back to inches, choose **in** under **Unit of measurement** in the sensor's settings. The [Apollo mmWave dashboard guide](/products/rpro1/setup/apollo-mmwave-dashboard.md#target-x-and-y-units) has the details.
+
 10\. If you use the imperial system (Freedom Units) then you will need to do this step. Metric users can skip this. For the targets to show up correctly we first need to update the Target 1-3 X and Y measurements from inches (in) to millimeters (mm). Find Target 1-3 X and Y under the Sensors section and select them. You will want to update all 3 X and Y target values.
 
 ![LD2450 Target-1 X and Y sensors in Home Assistant with their inch values highlighted](/assets/r-pro-1-card-change-units-from-inches.png)

diff --git a/docs/products/rpro1/setup/zones-hlk.md b/docs/products/rpro1/setup/zones-hlk.md
@@ -46,7 +46,7 @@ Follow these steps to turn on the LD2450's Bluetooth and set up its zones in the
 
 !!! tip "Drawing zones with the Apollo mmWave dashboard?"
 
-    In step 4, pick **Close detection** instead of **Area Detection** (**LD2450 Zone Type** **Disabled** in Home Assistant). The dashboard's [zone map](/products/rpro1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) replaces the app's areas. On **Area Detection**, the radar reports only people inside the app's areas, so anyone else is missing from the map, and **Area Filtering** hides the people inside them.
+    In step 4, pick **Close detection** instead of **Area Detection** (**LD2450 Zone Type** **Disabled** in Home Assistant). The dashboard's [zone map](/products/rpro1/setup/apollo-mmwave-dashboard.md#draw-zones-on-the-r-pro-1-and-mtr-1) replaces the app's areas. On **Area Detection**, the radar reports only people inside the app's areas, so anyone else is missing from the map, and **Area Filtering** hides the people inside them. To keep a fan or a curtain from turning the map's zones on, draw an [ignore zone](/products/rpro1/setup/apollo-mmwave-dashboard.md#ignore-a-spot-or-hold-a-zone) over it on the map.
 
 4\. Enable Area Detection (drawing zones on the Apollo mmWave dashboard instead? Pick **Close detection** and skip the areas; see the tip above), then toggle Area 1, 2, and 3 to display a colored box with the matching number. You can press and hold the box to move or resize it as needed. Once your zones are configured, click **Submit**. You should see a confirmation message: **"Setup successfully."**
Original file line number	Diff line number	Diff line change
Expand Up		@@ -5,4 +5,6 @@ description: Draw occupancy zones over the live targets of your Apollo R PRO-1,

		# Draw R PRO-1 zones and tune the LD2412 addon with the Apollo mmWave dashboard

		An Apollo R PRO-1 tab has a job for each radar. For the LD2450, [Draw zones on the R PRO-1 and MTR-1](#draw-zones-on-the-r-pro-1-and-mtr-1) takes you from a new sensor to a working zone in eight steps. For the optional LD2412 addon, start at [Calibrate with an empty room](#calibrate-with-an-empty-room), and [R PRO-1 and its LD2412 radar](#r-pro-1-and-its-ld2412-radar) covers what's different from an MSR-1 or MSR-2.

		--8<-- "products/general/setup/apollo-mmwave-dashboard.md:7:"