Support / Why some buttons are missing
Yardstick shows a view once it has the data behind it. That data belongs to one core, not to your property.
Yardstick hides a control rather than showing one that would do nothing. If you have never mowed, there is no cut grass to compare against, so there is nothing for a Missed grass button to color. If Yardstick has not read your yard map yet, it does not know where your areas are, so there is no Yard map to draw.
Nothing is broken and nothing is missing from your install. The view appears on its own once the data behind it exists.
This is the part that surprises people, so it is worth being blunt about.
So if you switch cores and the buttons change, that is not an inconsistency. It means the two cores have different amounts of data behind them. The core you set up first, or the one that does most of the mowing, will usually have more.
To bring a quieter core up to the same level, do two things for that core specifically, with that core selected:
Use the robot picker at the top of the page. Everything below it, including the buttons, refers to the core you have chosen.
This reads the yard map from that robot. Yard map and Whole property appear once it has one.
Planned route and Missed grass need a job to look at. They appear after that core has completed some work with Yardstick running.
The same idea applies to the map itself. Yardstick draws where your robot has actually been. On the first day that is a thin trail. After a few jobs it is a yard.
Gray or empty ground on the map is not a fault and it does not mean the grass was missed. It means the robot has not been there yet while Yardstick was recording. Areas you have never asked the robot to mow will stay empty for as long as that is true.
A view that has never appeared is waiting for data. A view that used to work and has stopped is worth reporting, and so is a figure that contradicts what you saw the robot do.
If you are not sure which you have, send us a diagnostic report from Settings, then Something wrong?. It tells us what each core has recorded, and we can usually answer from that without any back and forth.