Set up the Apollo mmWave Dashboard for the MSR-1¶
A new Apollo radar sensor detects presence out of the box, but every room is different: a ceiling fan or a moving curtain can make it trigger with nobody there, and someone sitting still can be missed. The Apollo mmWave Dashboard is where you fix that. On an Apollo MSR-1, MSR-2, or R PRO-1 with the LD2412 addon, one button, Calibrate with empty room, sets the radar's thresholds for your room in about a minute and a half. On an Apollo MTR-1 or R PRO-1, the same dashboard is where you draw zones over the radar's live targets.
The Apollo mmWave Dashboard integration gives every Apollo radar sensor in your home its own workspace in Home Assistant. When you add it, it offers to add an Apollo mmWave Dashboard to your sidebar with one tab per radar, built from the devices Home Assistant already knows about. Add a sensor later and its tab appears on its own; remove one and its tab goes away. Before 2.4.2 it was called Apollo mmWave, and a setup from then keeps that name until you rename it (see Updating to Apollo mmWave Dashboard 2.4.2).
What each tab holds depends on the radar inside the sensor:
| Sensor | Radar chip | What its tab shows |
|---|---|---|
| Apollo MSR-1, Apollo MSR-2 | LD2410 | Radar tuning: setup checks, auto-calibration, distance and gate energy charts, thresholds, detection range, and occupancy |
| Apollo R PRO-1 | LD2450, plus the optional LD2412 addon | The same radar tuning cards for the LD2412, plus a zone map for drawing occupancy zones over the LD2450's live targets, with the LD2450's setup check, live status, and controls beside it |
| Apollo MTR-1 | LD2450 | A zone map, with the radar's setup check, live status, and controls beside it |
Every tab starts with a Start here card that lists your sensor's first steps, and ends with a Device card that shows its firmware versions and restarts it. LD2410, LD2412, and LD2450 are the model numbers of the radar chips, and the card titles use them.
If you built the MSR-2 tuning dashboard by hand, this replaces it. The integration ships its own cards and updates them along with itself, so Streamline Card, Plotly Graph Card, and the YAML generator are no longer needed.
Before you start
-
You're running Home Assistant 2026.8.1 or newer. Settings → About shows your version.
-
You have a way to install community integrations like this one. Which one depends on your Home Assistant version:
- Home Assistant 2026.11 or newer has the Marketplace built in, under Settings → Marketplace. It replaces HACS, and it moves an existing HACS setup over on its own, Apollo mmWave Dashboard included. Installing from a search needs nothing more. Only adding a repository from a link needs a free GitHub account, which the Marketplace asks you to connect then. A GitHub connection you made for HACS carries over.
-
Home Assistant 2026.10 or earlier needs HACS 2.0.5 or newer, installed and set up. HACS is a community store for Home Assistant that installs and updates custom integrations. If you don't have it yet, follow the HACS download guide and then the initial configuration guide. Setup asks you to sign in with a free GitHub account. On Home Assistant OS, the button below opens the Get HACS app that the download guide uses.
-
Your Apollo sensor is already in Home Assistant through the ESPHome integration. If it isn't, work through getting started first.
Install Apollo mmWave Dashboard through HACS or the Marketplace¶
Apollo mmWave Dashboard is in the community list that HACS and the Marketplace both search, so you find it with a search and install it like any other integration. On Home Assistant 2026.11 or newer you install it from the built-in Marketplace, and on older versions from HACS, so pick the tab for your version (Settings → About shows it). The button under step 1 works with both. Updates arrive the same way as for any other integration.
If you installed Apollo mmWave from the original repository, bharvey88/apollo-mmwave, which is no longer on GitHub, follow From the original Apollo mmWave repository instead. It switches HACS over without setting anything up again.
-
Go to Settings → Marketplace. Or use the button below, which opens Apollo mmWave Dashboard in the Marketplace, and go on at step 3. The first time, the Marketplace may show a warning: tick I understand the risks and agree and click Continue.
-
Search for Apollo mmWave and open Apollo mmWave Dashboard. For a short while after the rename, the listing may still read Apollo mmWave.
- Click Install, then Install again in the dialog that opens.
If the search doesn't find it, add the repository yourself: click Add from link (a link icon on a narrow screen), paste https://github.com/ApolloAutomation/apollo-mmwave-main into the GitHub link field, and click Add. If a Type field appears, set it to Integration and click Add again. Then search again and go on at step 3. If the button above shows an Add custom repository box, clicking Add there does the same. Adding a repository from a link needs a connected GitHub account. If yours isn't connected yet, Add opens Connect GitHub first, which gives you a code to enter on GitHub. In that case the button above shows Connect GitHub to add the custom repository ApolloAutomation/apollo-mmwave-main, then open the link again. instead: connect GitHub, then click the button again.
-
Open HACS from your Home Assistant sidebar. Or use the button below, which opens Apollo mmWave Dashboard in HACS, and go on at step 3.
-
Search HACS for Apollo mmWave and open Apollo mmWave Dashboard. For a short while after the rename, the listing may still read Apollo mmWave.
- Click Download, then confirm with Download in the dialog that opens.
If the search doesn't find it, add the repository yourself: click the three-dot menu in the upper right corner and choose Custom repositories. Paste https://github.com/ApolloAutomation/apollo-mmwave-main into the Repository field, set Type to Integration, and click Add. Close the dialog, then search again and go on at step 3. If the button above shows an Add custom repository box, clicking Add there does the same.
The Marketplace can usually load a new integration without a restart. If it opens the Apollo mmWave Dashboard setup dialog after the install, skip the restart and go on at step 3 of Add the integration.
Otherwise, restart Home Assistant: go to Settings → System, click the power icon in the upper right corner, choose Restart Home Assistant, then click Restart. Wait for it to come back. Until then, HACS lists Apollo mmWave Dashboard as Pending restart, and the Marketplace as Restart required.
With HACS, Home Assistant only loads a new integration when it starts, so the restart is what makes Apollo mmWave Dashboard available to add in the next step.
Add the integration¶
This is the step that builds your dashboard. You add Apollo mmWave Dashboard once and it covers every Apollo radar you own, so there's no need to repeat it per sensor. Adding it a second time stops with This entry is already configured.
-
Go to Settings → Devices & services and click Add integration. Or use the button below, which opens the Apollo mmWave Dashboard setup dialog directly, and skip to step 3.
-
Search for Apollo mmWave Dashboard and select it. If it isn't in the list, refresh the browser page (your browser may still hold the list from before the restart) and search again. In the Home Assistant app, close the app fully and open it again instead.
- The dialog notes that the integration serves its own cards and dashboard, with nothing else to download, and offers to add the dashboard for you. Leave both boxes ticked (they're on by default) to get the dashboard this guide describes:
- Add the Apollo mmWave Dashboard to the sidebar creates the dashboard once, when you click Submit. Untick it only if you'd rather place the cards on your own dashboards; you can still add the dashboard later from the integration options.
- Only administrators can see it keeps the dashboard out of other users' sidebars. Untick it to show the dashboard to everyone in your home. You can change this later in the dashboard's settings under Settings → Dashboards.
- Click Submit, then Finish on the success message.
Apollo mmWave Dashboard now appears under Settings → Devices & services. With the first box ticked, a new Apollo mmWave Dashboard entry with a radar icon also sits in your sidebar, at the apollo-mmwave address. The integration registers its cards with Home Assistant itself, so they load in browser tabs that were already open without a refresh. If the dashboard couldn't be created, setup still finishes without it, and The Apollo mmWave Dashboard isn't in the sidebar shows how to add it.
Created once, then it's yours
From 2.2.6, the dashboard is created once, when you click Submit. The integration never recreates, rewrites, or deletes it on its own: not when Home Assistant restarts, and not when the integration reloads or updates. It's an ordinary dashboard, so you can rename it, change its icon, hide it, or delete it under Settings → Dashboards like any other. To add it again later, remove it, or add a second one, see Manage the dashboard.
Open the dashboard¶
Click Apollo mmWave Dashboard in the sidebar (Apollo mmWave on a setup from before 2.4.2). With two or more radars you'll see one tab per radar along the top, each named after the device the way it appears in Home Assistant. With one radar, Home Assistant shows the dashboard title instead of a tab bar, and that radar's cards fill the page. The tabs keep themselves current: add a sensor and its tab appears, no page reload needed.
The cards on each tab are laid out in columns that stack into one on a phone. Here's what a working first load looks like for each sensor. A row only appears when its entity is enabled in Home Assistant, so some cards can be shorter than described.
MSR-2 and MSR-1 tabs¶
Both sensors use the LD2410 radar chip, so their tabs look the same, and the tuning card titles start with LD2410.
- Start here sits at the top. It names your sensor and lists five steps, from Fix anything the Radar setup card flags. to walking the room while you watch the Gate Energy chart. Under the steps it says to use Radar Target in automations for the whole room, and to raise Radar Timeout to 60 s or more if it turns off while someone sits still. Its links open the tuning guide on this wiki and your sensor's own page in Home Assistant.
- Under it, the Radar setup card checks the radar's settings and offers a fix when one is off. On a sensor that's ready to go it reads Radar settings look good.
- Auto-calibrate comes next, with the Calibrate with empty room and Preview only buttons. If your sensor still has its factory thresholds and has never been calibrated, the card adds These look like factory thresholds. Calibrating sets them for your room.
-
The LD2410 Gate Energy chart is dimmed behind Turn on Radar Engineering Mode to see gate energy values, with a Turn on Radar Engineering Mode button below. That's expected: the radar only reports gate energy while Radar Engineering Mode, a diagnostic setting, is on. You don't need to press the button before calibrating; the calibration turns the mode on for its listen and puts it back the way it was afterward.
-
The other cards hold the radar's settings and live readings: controls, distances, detection range, occupancy, a threshold for each gate (from G0 (at the sensor) to G8, each named for how far out it reaches), and a day of occupancy history. The sliders on the range and threshold cards start locked, so a scroll can't move them: press Unlock above them to change one. The Device card at the bottom shows the firmware versions and restarts the sensor. The tour of the radar tab explains each one.
R PRO-1 tabs¶
The R PRO-1 tab starts with the same tuning cards, titled LD2412 instead of LD2410, for the optional LD2412 radar addon, and adds a zone map for its LD2450 radar. Without the addon, the LD2412 cards still appear but have no radar behind them, so skip to the zone map, and Start here gives the zone map steps instead. The differences from an MSR-2 tab:
-
Start here says what each radar is for: the LD2412 senses people anywhere in range, even sitting still, and the LD2450 tracks where people are and drives the zone map. For automations that cover the whole room, it names Combined Presence (on while either radar sees someone) on firmware newer than 26.3.2.1, which has that sensor, and LD2412 Presence on earlier firmware.
-
LD2412 Controls adds Start Dynamic Background Correction and Background Correction Running. The Auto-calibrate card reminds you to run background correction first, with the room empty, and wait for its status to turn off before you calibrate.
- LD2412 Detection Range holds Radar Timeout, Max Gate, and Min Gate, plus Distance Resolution if you've enabled that entity (it's hidden on a new sensor).
- The thresholds cards and the Gate Energy chart cover 14 gates, G0 to G13.
- There's no Zone Config card, and the LD2412 Distances chart shows the gates and your Max Gate and Min Gate limits without distance bars.
- After the first column (Start here, the LD2412's Radar setup card, Auto-calibrate, LD2412 Controls, and LD2412 Target / Occupancy), a Zone Map heading introduces the LD2450's cards: its own Radar setup card and the zone map, in a section two columns wide, then Zone presence, LD2450 Live, and LD2450 Controls, described below. The rest of the LD2412 cards follow, so on a phone you reach the zone map before the 28 threshold rows. On a screen wide enough for Home Assistant's four columns, the first column, the zone map, and the LD2450's cards make up the first row, and the LD2412's tuning cards fill the second. With room for only two columns, the LD2450's cards move up beside the first column, and the zone map spans the full width under them.
MTR-1 tabs¶
An MTR-1 tab is built around the zone map, with everything for its LD2450 radar beside it. On a computer, Start here and Radar setup share the row above the zone map, and the map's section is two columns wide:
- Start here lists three steps (fix anything the Radar setup card flags, set Cone rotation under Map settings on the zone map, then press Add zone under the map, draw the zone, and walk into it), says which presence sensor to use in automations, and links to your sensor's own page.
- Radar setup checks Zone Type and Multi Target Tracking, the two radar settings that decide whether the map can show people, and fixes them when you press its button. Zone Type should be Disabled, because the zone map replaces the radar's own built-in zones.
- The zone map, titled with your sensor's name, shows the radar's view, a cone 120 degrees wide and about 6 m (20 ft) out, with a numbered dot for each target the LD2450 is tracking, and fills in each zone while someone is in it. It's in feet or meters to match Home Assistant, and the m / ft switch on the map changes it. Shapes, the icon with a triangle over a square and a circle in the lower left, opens the drawing modes, and the lower right holds the unit switch and the undo and lock buttons, with the zoom buttons (−, +, and Fit) above them. Under the grid are the Coverage button (on a phone or tablet, with 🚶 Mark corners by walking before it for administrators), the Zones panel, and a collapsed Map settings section. Zones holds Add zone, a button for each zone, and an editor for the zone you pick, with its name, size, Type, Hold time, Draw shape (Redraw shape once the zone has a shape), which gets the map ready to draw that zone, and Delete zone. Map settings holds the cone rotation slider with the hint to mount the sensor first, Flip the map left to right (display only), Movement history (for administrators), and Clear all shapes. Expand in the map's top-right corner (the icon alone on a phone) gives the map the whole window when the card feels cramped.
- Zone presence, LD2450 Live, and Occupancy History show each zone's presence sensor, what the radar reports right now, and the last 24 hours. LD2450 Presence, the first row of LD2450 Live and a line in Occupancy History, is on while the radar sees anyone anywhere in its view, whether or not they're in a zone.
- LD2450 Controls, the radar's built-in zones (only while Zone Type isn't Disabled), and the Device card end the tab.
The integration finds the sensor's target entities itself, so there's nothing to pick before you start drawing. The R PRO-1's zone map and the cards beside it work the same way.
What to do first¶
Your dashboard is working. Follow the Start here card on each tab, from the top:
- Look at the Radar setup card near the top of the tab. If it flags a setting, follow what it says: most problems have a button that fixes them, and the card changes nothing until you press one. An R PRO-1 tab has a second one above the zone map, for the LD2450.
-
On an MSR-1 or MSR-2 tab, or an R PRO-1 tab with the LD2412 addon, calibrate the radar. Skip this step on an R PRO-1 without the LD2412. On an R PRO-1, first clear the room, press Start Dynamic Background Correction on the LD2412 Controls card, and wait for Background Correction Running to turn off. Then press Calibrate with empty room on the Auto-calibrate card and leave the room for about a minute and a half. You don't need to turn on Radar Engineering Mode: the calibration does that for you. The tuning guide walks you through it.
-
On an MTR-1 or R PRO-1 tab, press Add zone under the zone map and draw your first zone. The eight zone steps take you from Cone rotation to a zone that lights up when you walk into it.
The rest of this page covers managing the dashboard, upgrading from an older setup, and troubleshooting, so come back to it when you need it.
Manage the dashboard¶
After setup, the integration changes its dashboard only when you ask it to, from the integration options: add the dashboard, remove it, restore it, or choose which sensors get a tab. Open Settings → Devices & services → Apollo mmWave Dashboard → Configure to reach the Apollo mmWave Dashboard options menu. It reads These actions change only the dashboard this integration created, at /apollo-mmwave. A dashboard you made on another URL is never touched. and lists the actions that fit:
- Add the Apollo mmWave Dashboard to the sidebar is listed while the integration has no dashboard of its own: you unticked the box during setup, setup couldn't create it, or you deleted it. It describes the dashboard it creates and asks Only administrators can see it again. Click Submit to create it, once, with the sensors you chose under Choose the dashboard's devices.
- Remove the dashboard at /apollo-mmwave is listed while the integration has one. Click Submit to delete the dashboard at
/apollo-mmwavethat the integration created, along with any title, icon, or strategy options you changed on it. Your sensors, zones, and calibration values stay, and the cards still work on your own dashboards. You can add the dashboard again from the same menu. - Restore the automatic dashboard is listed instead of those two while the dashboard is a saved copy, made with Take control. Click Submit to keep your copy as a dashboard of its own and put the automatic one back, as If your dashboard is missing cards describes.
- Choose the dashboard's devices opens Dashboard devices, which is empty by default and shows every Apollo mmWave device Home Assistant knows about, online or not. Select one or more devices to show exactly those and hide the rest; a selected device keeps its tab even while it's offline. Clear the selection to go back to automatic detection. The picker only lists Apollo MSR-1, MSR-2, MTR-1, and R PRO-1 sensors added through ESPHome.
Each action takes effect as soon as you click Submit, with no restart, and an open dashboard picks up a new device selection without a reload. The device selection is written only into the dashboard the integration created, while it still builds itself. Otherwise the selection is kept and used when you add or restore the dashboard from the options.
You can also delete the dashboard under Settings → Dashboards, like any other. It stays deleted until you add it again from the options.
Add another Apollo mmWave Dashboard¶
Want a second dashboard, say one with only the bedroom sensors, or one at another address because something else already uses apollo-mmwave? Home Assistant's dashboard picker adds one that builds its tabs the same way as the integration's own:
-
Go to Settings → Dashboards and click Add dashboard.
-
Pick Apollo mmWave Dashboard under Community dashboards.
- Give it a title and a URL other than
apollo-mmwave, then click Create.
A dashboard you add this way is yours from the start, and the integration options never change it. It shows every detected Apollo mmWave device; to limit it, set devices in its raw configuration, as the Apollo mmWave Dashboard configuration guide shows.
Give it a URL other than the integration's
The integration forgets its own dashboard when you delete it, but not while it isn't running, for example while it's disabled. If you delete the integration's dashboard then and add one of these at apollo-mmwave, the integration can mistake it for the dashboard it created, and its options and removal would then act on yours.
Use your own layout¶
Want to rearrange the cards? Click the pencil icon in the upper right corner of the dashboard and choose Take control in the dialog that opens. From then on the layout is yours: the integration stops offering to remove the dashboard, writes no device selection into it, and leaves it in place when you remove the integration. The dashboard also stops adding and removing tabs as sensors come and go. Changed your mind? Choose Restore the automatic dashboard in the integration options: you get the automatic dashboard back, and your layout is kept as a dashboard of its own (see If your dashboard is missing cards). If you add the Apollo tabs to a dashboard of your own, take control of that dashboard before you edit them; editing an auto-built tab directly discards its cards.
A dashboard you took control of keeps the cards it had, so it doesn't pick up new cards from later releases, such as the updated Start here steps, the Radar setup cards, the Device card, and the slider lock that came with 2.3.0, or the wider zone map section, the Radar Target advice, the LD2450 Presence label, and Target Count as a whole number, which came with 2.4.0. Nothing on the dashboard says so, so from 2.4.0 the integration checks for it and offers to restore it (see If your dashboard is missing cards). The zone map card itself always runs the current version, so its Zones panel and other new tools show up on a dashboard you took control of too.
The cards also work on their own: in the card picker they're listed as Apollo Radar Auto-Calibrate, Apollo Radar Distance Chart, Apollo Radar Gate Energy Chart, Apollo Radar Setup, and Apollo Zone Map. The Apollo mmWave Dashboard configuration guide has the YAML for placing them.
For a phone or a wall tablet where nobody draws zones, use the zone map's view-only mode. Add the Apollo Zone Map card to a dashboard of your own, pick your sensor under Radar, and turn on View only (the map without drawing tools), or set view_only: true in the card's YAML. The card then shows its title and the live map, with lit zones, numbered dots and their trails, and the Radar offline note, but no drawing tools, buttons, zoom, Zones panel, or Map settings, and a swipe on it scrolls the page. The Apollo mmWave Dashboard keeps the full map.
If your dashboard is missing cards¶
Is the dashboard at /apollo-mmwave missing cards this guide describes, such as the Radar setup card, LD2450 Controls with Zone Type and Multi Target Tracking, Zone presence, or the Device card? Then someone used Take control on it under an earlier release, and it's a saved copy: it holds the cards it had at that moment and no longer builds itself.
From 2.4.0, the integration checks for this each time it starts and whenever you save its options. While the dashboard it created is a saved copy, still made of Apollo cards, you get two ways to put the automatic dashboard back. Both say what they do, and neither changes anything until you click Submit:
- Settings → System → Repairs lists The dashboard at /apollo-mmwave is a saved copy. Click it to open Restore the automatic dashboard at /apollo-mmwave.
- The integration options (Settings → Devices & services → Apollo mmWave Dashboard → Configure) list Restore the automatic dashboard.
When you click Submit:
- Your copy is saved first, as a new dashboard named Apollo mmWave Dashboard (saved copy) at
apollo-mmwave-saved, orapollo-mmwave-saved-2and so on when that address is taken. It isn't in the sidebar, so open it from Settings → Dashboards. It's for administrators only if your dashboard was. - Only once the copy is saved does
apollo-mmwaveget the automatic dashboard back, with the sensors you chose under Choose the dashboard's devices. Its title, icon, sidebar setting, and admin-only setting stay as they were.
The repair then reads The issue is repaired! and goes away. Open the dashboard from the sidebar, or reload it if it's already open, to see every current card. Keep the saved copy as long as you want something from it, and delete it under Settings → Dashboards when you don't.
If the restore can't finish, it says what happened, and the repair stays so you can try again. The log under Settings → System → Logs has a warning that starts with Apollo mmWave: and says why:
- Nothing was changed: your copy could not be saved as a separate dashboard, so the dashboard at /apollo-mmwave was left as it is. No copy was made, and your dashboard is as it was.
- Your copy is saved as the Apollo mmWave Dashboard (saved copy) dashboard under Settings > Dashboards, but the dashboard at /apollo-mmwave could not be restored and was left as it is. The copy is kept, and your dashboard is as it was. Each try keeps another copy, so delete the extra ones under Settings → Dashboards.
A dashboard you rebuilt with no Apollo cards on it is yours, and gets no repair. When you delete the integration's dashboard, the integration forgets it, so a dashboard you make at apollo-mmwave later gets no repair either. The exception is a dashboard you deleted while the integration wasn't running, for example while it was disabled: a new dashboard at that address with Apollo cards on it then gets the repair too, and still nothing changes until you click Submit. Removing the integration removes the repair and keeps the saved copy.
No repair, and no Restore in the options? The check only looks at the dashboard the integration recorded as the one it created, and it no longer knows yours if you took control of it under Apollo mmWave 2.2.5 or earlier, or saved the integration options after taking control of it, under a release before 2.4.0. To get the automatic dashboard back then:
- Open your old dashboard, click Edit dashboard, open the three-dot menu, and choose Raw configuration editor. Copy its contents somewhere safe if you want to keep anything from it.
- Delete the dashboard under Settings → Dashboards.
- In the integration options, choose Add the Apollo mmWave Dashboard to the sidebar (see Manage the dashboard).
Or keep your old dashboard as it is and add a second one that builds itself, at another address, as Add another Apollo mmWave Dashboard shows.
Upgrade from an older setup¶
If this is your first Apollo dashboard, skip this section and calibrate your radar or draw your zones. Troubleshooting is at the end of this page if something didn't load.
Before any upgrade, make a full Home Assistant backup under Settings → System → Backups, so you can go back if something goes wrong. Then update Apollo mmWave Dashboard, restart Home Assistant, and reload the dashboard so it loads the new cards, as the next two sections show.
Update Apollo mmWave Dashboard¶
Home Assistant lists an Apollo mmWave Dashboard update with its other updates under Settings → System → Updates: open it and click Update. You can also update from the Marketplace on Home Assistant 2026.11 or newer, or from HACS on 2026.10 or earlier. Both also let you pick a different version:
HACS 2.0.5: retry a failed download before you restart
On Home Assistant 2026.10 or earlier, every update path downloads through HACS. If a download fails, don't restart: retry it until it finishes with no error, because a failed download on HACS 2.0.5 can remove the installed files. Update one integration at a time.
- Go to Settings → Marketplace and open Apollo mmWave Dashboard. The Installed tab lists it. When a new version is out, its page reads Update available.
- Click Update, then Update again in the dialog that opens.
To install a different version, open the three-dot menu in the upper right corner of the Apollo mmWave Dashboard page and choose Install another version. Pick the version under Version, then click Update. The dialog reminds you that restoring a backup is the safer way to go back to an earlier version, so use the backup you made when you can.
- Open HACS and open Apollo mmWave Dashboard. When a new version is out, HACS lists it as Pending update.
- Click the three-dot menu in the upper right corner, choose Redownload, and click Download in the dialog that opens. The dialog names the version it downloads.
- Wait for the download to finish. If it shows an error, don't restart: click Download again until it finishes with no error, because a failed download on HACS 2.0.5 can remove the installed files. Update one integration at a time.
To install a different version, open Need a different version? in the same dialog and pick it under Release before you click Download. HACS warns there that a rollback is better done by restoring a backup, so use the backup you made when you can.
Load the new cards¶
An update takes effect after a restart, and a browser or the Home Assistant app can keep showing the previous version's cards until it loads them again:
-
Restart Home Assistant: go to Settings → System, click the power icon in the upper right corner, choose Restart Home Assistant, then click Restart. Until you do, HACS lists Apollo mmWave Dashboard as Pending restart, and the Marketplace as Restart required.
-
In a browser on a computer, reload the dashboard with Ctrl+Shift+R (Cmd+Shift+R on a Mac). If a card still looks old, reload once more.
- In the Home Assistant app on a phone or tablet, close the app fully (swipe it away in the app switcher) and open it again. If a card still looks old, clear the app's cache:
- Android: Settings → Companion app → Troubleshooting → Reset frontend cache.
- iPhone and iPad: Settings → Companion app → Debugging → Clear web view cache, then Clear Cache. Older versions of the app call it Reset frontend cache.
On updates from 2.4.0 or later, the cards tell you when one of these steps is still to do. The Radar setup card shows a notice above its checks. A zone map card, view-only ones included, shows it under its title when it comes before any Radar setup card on the page, as on a dashboard of your own:
- Apollo mmWave was updated to 2.4.2, but this page still runs 2.4.1., with a Reload button and the line In the Home Assistant app, if Reload does not help, close the app fully and open it again. The page still runs the cards from before the update. Press Reload. Cards from 2.4.2 on start this notice with Apollo mmWave Dashboard instead of Apollo mmWave.
- Apollo mmWave Dashboard 2.4.2 is installed, but Home Assistant still runs 2.4.1. Restart Home Assistant to finish updating. The page already runs the new cards, but Home Assistant hasn't restarted since the update. Restart it as step 1 shows, and the notice turns into the Reload one if the page needs it.
The version numbers are the ones on your system. Only one card on the page shows the notice, and it goes away once the page and Home Assistant run the same version. Cards from earlier releases have no such check, so on the update to 2.4.0 itself, no notice doesn't mean the page runs the new cards: do the steps above anyway.
Updating to Apollo mmWave Dashboard 2.4.2¶
2.4.2 gives the integration a new name, gives the zone map's drawing modes a button of their own, and gets zone sensors ready for a Home Assistant change due in 2027.11. Your zones, calibration values, and automations carry over as they are, and nothing needs doing by hand unless your dashboard resources are managed in YAML. After the restart and a reload, check these if they apply to you:
-
A new name. Apollo mmWave is now called Apollo mmWave Dashboard. HACS, the Marketplace, Settings → Devices & services, and Community dashboards in the dashboard picker (where it was Apollo Radar Tuning) show the new name, and a new setup names its entry and its sidebar dashboard Apollo mmWave Dashboard. A setup from before 2.4.2 keeps its entry and its sidebar dashboard under the old name, Apollo mmWave, until you rename them:
- The entry: go to Settings → Devices & services → Apollo mmWave Dashboard, open the three-dot menu on the Apollo mmWave entry, and choose Rename. Change Entry name to Apollo mmWave Dashboard and click OK.
- The dashboard: go to Settings → Dashboards, open the three-dot menu at the end of the Apollo mmWave row, the dashboard at
/apollo-mmwave, and choose Edit. Change Title to Apollo mmWave Dashboard and click Update. A click on the row itself opens the dashboard instead.
The
/apollo-mmwaveaddress, your entity IDs, device names, and actions don't change, so automations need nothing. Messages about the integration's dashboard now name it by that address, such as The dashboard at /apollo-mmwave is a saved copy, and a copy that a restore keeps from now on is named Apollo mmWave Dashboard (saved copy). -
A card still looks like 2.4.1. Reload it as Load the new cards shows. Until the page runs the 2.4.2 cards, the Radar setup card shows Apollo mmWave was updated to 2.4.2, but this page still runs 2.4.1. with a Reload button. It still says Apollo mmWave because the 2.4.1 cards write that line.
- Shapes has its own button. The button in the zone map's bottom-left corner that opens the drawing modes is now Shapes, with an icon of a triangle over a square and a circle instead of ✎. ✎ now only means Draw shape, beside the picked zone's button. Draw a zone shows both.
- Changing a zone sensor's entity ID. On Home Assistant 2026.11 or newer, a zone's sensors take a new entity ID in place, the way Home Assistant 2027.11 will require, instead of being removed and added again. Nothing changes on 2026.10 or earlier. On every version, the zone map, zone presence, and a hold that's running follow the new ID (see Use the zone sensors).
- Dashboard resources managed in YAML. Replace both
?v=addresses with the ones the log warning lists (see An Apollo card shows an error after an update).
Updating to Apollo mmWave 2.4.1¶
2.4.1 changes the zone map of R PRO-1 and MTR-1 tabs, and nothing on the radar. After the restart and a reload, check these if they apply to you:
- One zone habit changes. A drag on an unlocked map no longer redraws the picked zone on its own. Press Redraw shape in the zone's editor (Draw shape for a zone with no shape yet), or ✎ beside its button, and a banner on the map names the zone your drag draws, such as Drawing Couch. Add zone still goes straight to drawing its new zone. Until you press it, one finger on the map scrolls the page. Draw a zone shows the steps.
- A shape can come back. After each shape saves, the message offers Undo, and the zone's editor keeps Restore previous shape, which works after a reload or from another device. A shape you changed before the update has no previous shape kept, so Restore previous shape shows up after a zone's next shape change. Undo a shape change has the details.
- The map looks a little different. While you edit on an unlocked map, a picked zone that has a shape is bright with a dot on each corner and the other zones fade, zone names move apart where zones overlap, and the expand button reads Expand where the map has room. Pick a zone in the Zones panel covers it.
- A card still looks like 2.4.0. Reload it as Load the new cards shows. Until the page runs the 2.4.1 cards, the Radar setup card shows Apollo mmWave was updated to 2.4.1, but this page still runs 2.4.0. with a Reload button.
- Dashboard resources managed in YAML. Replace both
?v=addresses with the ones the log warning lists (see An Apollo card shows an error after an update). - Going back to 2.4.0. Nothing needs restoring: 2.4.0 ignores the previous shape Apollo mmWave keeps for each zone, and drops it the next time it changes that zone's shape. Under 2.4.0 a drag on an unlocked map redraws the picked zone again.
Updating to Apollo mmWave 2.4.0¶
After the restart and a reload, the zone map fills in each zone while someone is in it and numbers the dots, zooms in up to 8 times, and snaps the corners you draw to round values, and administrators get new tools: walking a zone's corners, ignore zones, hold times, a left-to-right flip, and movement history. The expand button in the map's top-right corner gives the map the whole window. Your zones move out of Configure → Zones into a Zones panel right under the map, with Add zone, a button for each zone, and an editor for the zone you pick. Configure is now Map settings, at the bottom of the card. Nothing changes on its own: every zone stays a detect zone with no hold, the map isn't flipped, and movement history stays off until an administrator turns it on. A dashboard you took control of gets these too, because they're part of the card. Draw zones on the R PRO-1 and MTR-1 covers them.
The Apollo mmWave dashboard also gives the zone map a section two columns wide on a computer, which a dashboard you took control of doesn't get. If the integration's own dashboard is one, Home Assistant lists a repair that restores it and keeps your copy (see If your dashboard is missing cards). Check these if they apply to you:
- Zone habits from 2.3.0. A zone's name has no Save button any more: type it and press Enter, or leave the box. Clear All Zones is now Clear all shapes under Map settings. It and Delete zone ask before they act, and a double-click on a zone's button no longer clears its shape. Pick a zone in the Zones panel shows the rest.
- Automations that use zone presence. A zone's presence sensor now reads unavailable while its radar is offline, and after every Home Assistant restart until the radar connects. Before 2.4.0 it read off. A trigger with
to: "off"and nofrom:now also fires when the radar comes back, after every restart. That's harmless for lights-off automations, and such a trigger still catches a zone that emptied while the radar was offline. A trigger withfrom: "on"skips both, so use it only where the trigger must see someone leave, such as a notification or a counter. Use the zone sensors shows both. A zone can also turn on up to about half a second later than under 2.3.0, because zone presence now waits for both halves of the radar's position report. - Automations, templates, and history graphs that use Target X or Y. Once after the update, Apollo mmWave shows an R PRO-1's or MTR-1's Target X and Y in mm instead of the inches Home Assistant picked on US customary units, and a notification titled Apollo mmWave Dashboard: Target X and Y now in mm (Apollo mmWave: Target X and Y now in mm under 2.4.0 and 2.4.1) lists what it switched. It leaves alone a sensor that an automation, a script, or a helper uses. A YAML template sensor, a dashboard card, or another tool that reads them, such as Node-RED, reads mm from then on, 25.4 times the inch value. Target X and Y units shows how to go back.
- Automations on an MSR-1 or MSR-2's zone sensors. The dashboard now recommends Radar Target for automations that cover the whole room, instead of Any zone: the zone sensors also need the radar's distance, which can read unknown while someone is there. Keep Any zone only where you want to ignore people past End Zone 3.
- A card still looks like 2.3.0. Reload it as Load the new cards shows: Ctrl+Shift+R (Cmd+Shift+R on a Mac) in a browser, or close the Home Assistant app fully and open it again.
- Dashboard resources managed in YAML. Replace both
?v=addresses with the ones the log warning lists (see An Apollo card shows an error after an update). - Going back to 2.3.0. Before going back to 2.3.0, turn Movement history off on every radar. 2.3.0 neither reads nor deletes the history file, so it would stay on disk and in every later backup, even after you remove the integration. Under 2.3.0, ignore zones act as ordinary zones and no zone holds. A zone you redraw, clear, or undo there loses its type and hold, and 2.3.0 forgets the flip the next time it saves your zones. 2.3.0 also ignores view-only mode, so a view-only zone map shows the full map with its drawing tools again, and on a phone a swipe that starts on the map doesn't scroll the page: remove or replace those cards first. A saved copy that a restore kept stays a dashboard of its own.
Updating to Apollo mmWave 2.3.0¶
In most setups 2.3.0 needs nothing from you. After the restart and a reload, each tab gets the new layout: Start here and Radar setup at the top, locked sliders, the zone map in your units with the LD2450's cards beside it, and the Device card at the bottom. Check these if they apply to you:
- Zones drawn before 2.2.7 with Home Assistant in US customary units. Before 2.2.7, the zone map read the radar's positions in inches as if they were millimeters, so the dots sat at or near the sensor. A zone drawn around those dots may not cover where people show up now. Walk through the room, watch the dots, and redraw any zone that's off.
- A dashboard you took control of keeps the cards it had. To get the new ones, see If your dashboard is missing cards.
- A zone map card you added from the card picker before 2.3.0 keeps the fixed grid saved in its YAML, with no distance labels or range caption. If you didn't choose that grid yourself (the card picker saved
x_min: -6000,x_max: 6000,y_min: 0,y_max: 12000withgrid_units: mm), open the card's code editor, deletegridandgrid_units, and setunit_display: trueto get the map fitted to the radar's view, in your units. A grid you set on purpose can stay. - Dashboard resources managed in YAML. Replace both
?v=addresses with the ones the log warning lists (see An Apollo card shows an error after an update).
From Apollo mmWave 2.2.5 or earlier¶
Up to 2.2.5, Apollo mmWave rebuilt its dashboard every time it loaded, and the Auto-create the Apollo mmWave dashboard option decided whether the dashboard existed. From 2.2.6 that option is gone: the dashboard is created once, and Apollo mmWave adds or removes it only when you ask in its options (see Manage the dashboard). The update needs nothing from you:
- The dashboard you already have stays as it is, including who can see it. Dashboards made before 2.2.6 are visible to every user; to limit yours to administrators, turn on Admin-only in its settings under Settings → Dashboards.
- If it still builds itself (you never took control of it), the integration records it as the dashboard it created. The options can then remove it or write a device selection into it, and deleting the integration deletes it too. A dashboard you took control of is yours, and the integration leaves it alone.
- If you had turned the auto-create option off, the integration records no dashboard, and setup no longer deletes a dashboard you made yourself at
apollo-mmwave. Add the integration's dashboard from the options whenever you want it.
Going back to 2.2.5 or earlier with HACS or the Marketplace turns the old behavior back on, as if the auto-create option were on: the dashboard is recreated or rewritten at every start, even if you had turned the option off. To go back, restore the backup you made before updating.
From the MSR-2 tuning dashboard¶
Your thresholds, detection range, and every other setting live on the sensor itself, and the new dashboard reads the same entities. There's nothing to migrate: once your MSR-2 tab works in the Apollo mmWave Dashboard, you can delete the old view.
Back up before you edit raw YAML
The raw configuration editor holds your whole dashboard. Copy its contents somewhere safe before you delete anything, so you can paste it back if a cut goes wrong.
- Open the dashboard you pasted the old YAML into, click Edit dashboard, open the three-dot menu, and choose Raw configuration editor.
-
Find the old view. It starts like this:
-
Delete that view, from its
- type: sectionsline down to the line before the next view (or beforestreamline_templates:). If you ran the generator for more than one MSR-2, repeat for each MSR-2 Configuration view. - At the bottom, delete the
ld2410_templates understreamline_templates:. If nothing else on your dashboards uses Streamline Card, delete the wholestreamline_templates:block. - Click Save.
If no other cards use them, you can also remove Streamline Card and Plotly Graph Card from HACS, or from the Marketplace on Home Assistant 2026.11 or newer. Apollo mmWave Dashboard doesn't need either.
From the original Apollo mmWave repository¶
Apollo mmWave used to install from the original repository, bharvey88/apollo-mmwave, which is no longer on GitHub. If HACS installed your copy from there, point HACS at the new repository, ApolloAutomation/apollo-mmwave-main, so you keep getting updates. It's the same integration in the same folder, so nothing needs to be set up again: what you already have carries over, such as your Apollo mmWave entry, its dashboard, your zones, the saved calibration values that Undo uses, and your entity IDs. The switch takes one Home Assistant restart.
If the old copy is version 1.x or 2.0, not everything carries over on its own. Read the upgrade notes in the changelog first. Some cards and automations need a change by hand, and From Apollo mmWave 1.x zone mapping below sums them up.
Switch before Home Assistant 2026.11
These steps need HACS, so make the switch while Home Assistant is on 2026.10 or earlier. Home Assistant 2026.11 moves HACS into the built-in Marketplace, old entry included, and the Marketplace can't make this switch: under Custom repositories it won't remove an entry that's still installed (Uninstall it first), and it won't install the new repository while the old entry owns the custom_components/apollo_mmwave folder. Don't uninstall the old entry to get around this. While your Apollo mmWave entry exists, the Marketplace only offers Delete and uninstall, which deletes that entry with its dashboard, zones, and saved calibration values. If you're already on 2026.11, contact Apollo support before you change anything.
Keep your Apollo mmWave entry in Home Assistant
The switch happens in HACS only. If you choose Delete from the three-dot menu on the entry under Settings → Devices & services → Apollo mmWave, Home Assistant asks Delete Apollo mmWave? and warns that its devices and entities will be permanently deleted. Deleting it also deletes the Apollo mmWave dashboard it created, every zone, and the saved calibration values that Undo uses. Setting it up again starts from nothing.
Leave Remove and Redownload alone in HACS
Both entries in HACS, Apollo mmWave from the original repository and Apollo mmWave Dashboard, use the same custom_components/apollo_mmwave folder. Remove, on either entry, first shows Integration is configured and tells you to delete the configuration. Don't: Navigate leads to the integrations page, where Delete wipes your zones. Ignore, or closing the box, opens a Remove box whose Remove button deletes the folder, new download included, so the integration won't load after the next restart. Redownload on the old entry fails because its repository is gone, and the folder can end up missing. Step 3 takes the old entry off the list without touching any files.
- Check two versions first. Home Assistant needs to be 2026.8.1 or newer, and older than 2026.11 (Settings → About). In HACS, click the three-dot menu in the upper right corner, choose About HACS, and check that Integration version is 2.0.5 or newer. The new repository won't download on older versions. Then make a full Home Assistant backup under Settings → System → Backups (see Upgrade from an older setup).
- In HACS, click the three-dot menu in the upper right corner and choose Custom repositories.
- Find the row whose second line reads bharvey88/apollo-mmwave (integration) and click the trash can icon on that row. There's no confirmation, so read the second line before you click: removing the wrong row deletes no files, but you have to add that repository again. This only takes the old entry off the HACS list. The files in
custom_components/apollo_mmwavestay where they are, and the integration keeps running.- If you already added the new repository, there are two rows. Remove only the bharvey88/apollo-mmwave one.
- If there's no bharvey88/apollo-mmwave row, there's nothing to remove. Go on to step 4.
-
If the dialog closed after step 3, open Custom repositories again. Paste
https://github.com/ApolloAutomation/apollo-mmwave-maininto the Repository field, set Type to Integration, click Add, and close the dialog. Or use the button below instead: it opens the repository page in HACS for you. If it shows an Add custom repository box first, click Add there. -
Search HACS for Apollo mmWave and open Apollo mmWave Dashboard (for a short while after the rename, the listing may still read Apollo mmWave). Only one entry is left, and if you used the button in step 4, it's already open. Click Download in the lower right corner, then click Download again in the dialog. The dialog says the files go to
/config/custom_components/apollo_mmwave, the same folder as before. Wait for it to finish.- If it shows an error, don't restart. Fix the cause and click Download again until it finishes with no error. On a first download HACS saves no backup copy of the folder, so a download that stops partway can leave old and new files mixed together.
- Look at the HACS list. Apollo mmWave Dashboard now shows Pending restart, and the old entry is gone.
-
Restart Home Assistant: go to Settings → System, click the power icon in the upper right corner, choose Restart Home Assistant, then click Restart. The Restart required repair that HACS adds does the same when you click Submit.
After the restart, HACS shows one Apollo mmWave Dashboard entry with the status Downloaded. Everything else is where you left it: your same entry, still named Apollo mmWave, under Settings → Devices & services → Apollo mmWave Dashboard, its dashboard in the sidebar, your zones on the zone map, your previous calibration values behind Undo, and the same entity IDs. If a card looks old or doesn't load, reload it as Load the new cards shows: Ctrl+Shift+R (Cmd+Shift+R on a Mac) in a browser, or close the Home Assistant app fully and open it again. From here on, HACS tracks updates from the new repository, and Home Assistant 2026.11 hands that over to the Marketplace.
HACS may leave its own update entity for the old repository behind, showing as unavailable. It belongs to HACS, not Apollo mmWave Dashboard, so deleting it is optional and doesn't touch your zones.
From Apollo mmWave 1.x zone mapping¶
Most of the move to 2.x happens on its own the first time the integration starts. If you wrote cards or automations by hand, change these yourself:
- Card name. A hand-written zone card set to
custom:zone-mapper-cardnow shows as a missing card. Change it tocustom:apollo-radar-zone-map-cardand give it the radar'sdevice_id(plus an optionaltitle) in place oflocation. - The
apollo_mmwave.update_zoneaction. Passdevice_id.locationstill works as a deprecated alias, logs a warning once per restart, and will be removed in a later release. - Zone change triggers. The
apollo_mmwave_zone_updatedevent now carriesdevice_idwhere it used to carrylocation, so a trigger readingtrigger.event.data.locationstops matching. - Empty
entitieslists. In anupdate_zonecall, an emptyentitieslist now leaves the tracked targets alone instead of erasing them. To empty the list on purpose, passclear_entities: true. dark_mode. The zone map follows your Home Assistant theme now, anddark_modein the card config is an override. Remove it if you want the card to track your theme.
And here's what changes without you doing anything:
- Target sensors are found automatically. The old Device and Targets picker is gone; the integration locates each radar's LD2450 target sensors itself.
- Zone entities move onto the radar's device page. Your entity IDs, custom names, and area assignments are kept, and you can rename the entities freely.
- Renaming a radar no longer loses its zones, because zones are stored per device rather than per display name. If you renamed a radar before upgrading, its zones are kept but not shown: the card comes up empty and the zone entities read as unavailable. Rename the radar back to its old name and reload the integration to bring them back, or keep the new name and redraw the zones.
- Zones from the standalone Zone Mapper integration are imported when Apollo mmWave Dashboard has no zone data of its own yet: on a fresh install, or when upgrading from a version before 1.2.0. The import only reads; nothing belonging to Zone Mapper is renamed or removed. Upgrading from 1.2.0 or later, the import is skipped and your existing zones are kept. Redraw any Zone Mapper zones you want on the zone map, then remove the old integration once you're happy with them.
Keep Zone Mapper until your zones have moved over
Don't uninstall the standalone Zone Mapper integration until you've confirmed your zones moved over. Its restore data is the only copy, and it goes away with its entities.
If a zone you expected is missing, search your Home Assistant log for apollo_mmwave. When the same zone number exists both on a device and in leftover pre-2.0 data, the copy already on the device wins, and the dropped copy is written to the log.
Troubleshooting¶
If none of these match, send Apollo a support file with your question.
The Apollo mmWave Dashboard isn't in the sidebar¶
Work through these in order:
- Sign in as an administrator. The dashboard is for administrators only unless you unticked Only administrators can see it. To show it to everyone, turn off Admin-only in its settings under Settings → Dashboards.
-
Look under Settings → Dashboards. The integration's dashboard, at
/apollo-mmwave, is listed there even when it's hidden. If you find it, check that its Add to sidebar setting is on and that you haven't hidden it from your own sidebar in your profile. -
If it isn't listed, the integration has no dashboard: you unticked Add the Apollo mmWave Dashboard to the sidebar during setup, setup couldn't create it, or it was deleted. The integration never recreates it on its own, so add it from the integration options with Add the Apollo mmWave Dashboard to the sidebar (see Manage the dashboard).
- If another dashboard already uses the
apollo-mmwaveaddress, such as one you made yourself, the integration leaves that one as it is and doesn't create its own. Adding it from the options then shows The dashboard could not be created. Another dashboard may already use /apollo-mmwave; the Home Assistant log says why. You can add one from Settings > Dashboards > Add dashboard > Apollo mmWave Dashboard instead. -
Open Settings → System → Logs and look for a warning that starts with Apollo mmWave:. If setup or the options couldn't create the dashboard, the warning says why and points you to the dashboard picker: Add one from Settings > Dashboards > Add dashboard > Apollo mmWave Dashboard (strategy type 'custom:apollo-radar-tuning'). You'll also see a warning that
apollo_mmwaveis a custom integration Home Assistant hasn't tested. Every custom integration installed through HACS or the Marketplace logs that one, so you can ignore it. -
If the integration can't create the dashboard, add one yourself from the dashboard picker, as described in Add another Apollo mmWave Dashboard.
The integration options show an error¶
When an action in the integration options fails, it changes nothing, and its form stays open with the reason:
- The dashboard could not be created. Another dashboard may already use /apollo-mmwave; the Home Assistant log says why. You can add one from Settings > Dashboards > Add dashboard > Apollo mmWave Dashboard instead. Check Settings → Dashboards for a dashboard at
apollo-mmwaveand the log for a warning that starts with Apollo mmWave:. Delete that other dashboard and try again, or add another Apollo mmWave Dashboard at a different URL. - The dashboard could not be removed. The Home Assistant log says why. You can delete it in Settings > Dashboards. Delete it there instead. The next time you open the options, they offer to add it again.
- The dashboard could not be updated. The Home Assistant log says why. The new device selection wasn't saved, and the dashboard keeps the one it had. Check the log for a warning that starts with Apollo mmWave:, then try again.
If the options open straight on Dashboard devices, with no menu, the integration couldn't read Home Assistant's dashboards, so it offers only the device selection. A selection you save there is kept but not written into the dashboard. Check the log, then open the options again and save the selection once the menu is back.
The dashboard shows no devices¶
The dashboard starts with No Apollo mmWave devices found. It found no radar to build a tab for. Confirm your sensor shows up under Settings → Devices & services → ESPHome, and check that Dashboard devices, under Choose the dashboard's devices in the integration options, is empty or lists your current devices. On a dashboard you added from Community dashboards, check the devices list in its raw configuration instead.
One sensor has no tab¶
Work through these in order:
- If Dashboard devices has any devices selected, the dashboard shows only those. Add the missing sensor under Choose the dashboard's devices in the integration options, or clear the selection to go back to automatic detection.
- A dashboard you took control of no longer adds tabs on its own. Add the sensor's cards yourself, or restore the automatic dashboard as If your dashboard is missing cards shows.
- The dashboard only picks up radars added through the ESPHome integration. A copy of the same sensor that another integration created (a network integration tracking it by its MAC address, for example) doesn't get a tab.
- A sensor you added a moment ago gets its tab once Home Assistant has registered its entities. It appears on its own, without a page reload.
- DIY builds that don't report an Apollo model only get a tab while one of their radar entities is live.
The dashboard is missing cards¶
A tab without the Radar setup card, LD2450 Controls (with Zone Type and Multi Target Tracking), Zone presence, or the Device card, while your sensor has those settings, is on a saved copy: someone used Take control on the dashboard under an older release. Look under Settings → System → Repairs for The dashboard at /apollo-mmwave is a saved copy, or in the integration options for Restore the automatic dashboard. If your dashboard is missing cards explains both, and what to do when neither is there.
If the cards are all there but one looks like an older release, the page still runs the old cards: reload it as Load the new cards shows.
A tab says the sensor is offline¶
The Start here card adds Offline right now., and the Radar setup card reads Radar is offline. Its settings are checked once it reconnects. On an MSR-1, MSR-2, or R PRO-1 tab, the Auto-calibrate card reads Radar is offline. Calibration needs the radar online and its gate entities enabled. with its buttons disabled. On an MTR-1 or R PRO-1 tab, the zone map shows Radar offline and no targets until the sensor reconnects. The tab stays so the sensor isn't silently missing, and the cards fill in once it reconnects. Check its power and Wi-Fi, and that it shows as online on the ESPHome integration page. If you replaced or reflashed the sensor under a new name, the old device entry is what's showing as offline: delete the old device under Settings → Devices & services and its tab goes away. If the sensor works but its tab still says Offline right now., reload the page: from 2.4.0, a tab keeps that note until the page reloads, for example when you opened the dashboard while the radars were reconnecting after a restart.
An Apollo card shows an error after an update¶
After you update Apollo mmWave Dashboard and restart, a browser that still holds the previous version's files can show the Apollo cards as error boxes that read Custom element doesn't exist. Refresh the page. Each release loads its cards under a new versioned address, so a fresh page load picks up the current version. If the error is still there, do a hard refresh with Ctrl+Shift+R (Cmd+Shift+R on a Mac). In the Home Assistant app on a phone or tablet, close the app fully and open it again, then clear its cache if the error stays, as Load the new cards shows. On updates from 2.4.0 or later, a card that does load, such as the Radar setup card, or a zone map that shows an error instead of its map, says which version the page runs and which one Home Assistant runs, with a Reload button when a reload fixes it. If that doesn't clear it either, check Settings → System → Logs for a warning that starts with Apollo mmWave: about Lovelace resources. On a system that manages its dashboard resources in YAML, the warning lists the two resource addresses to add by hand.
If the element named in the error is zone-mapper-card, a refresh won't help: that's the old card name, so update the card as described in From Apollo mmWave 1.x zone mapping.
The Auto-calibrate card is still loading¶
The card reads Apollo mmWave Dashboard is still loading... right after a restart while the integration starts, and clears on its own. If it changes to Apollo mmWave Dashboard is not loaded, so calibration is unavailable., check that Apollo mmWave Dashboard is enabled under Settings → Devices & services, then click Retry on the card.
Next step: calibrate your radar or draw zones
Your dashboard is up and every sensor has its tab. Now put it to work: the usage guide walks you through calibrating with an empty room, reading the charts, adjusting thresholds by hand, and drawing zones on the zone map.




