Metric Displays “MET?”
The “Metric Not Available” message appears on the screen when the selected metric is unavailable on your device. For example, if your device has not yet been updated to Garmin System 6, your device will not include support for metrics provided by Garmin’s “Complications” system.
To resolve this message, you’ll want to see if there are any updates available for your watch. Note that Garmin sometimes rolls out updates to certain watches before others, so it’s possible that you’re trying to access a feature that’s available for some watches but just not yours yet.
Or it’s possible that your device is not compatible with the given metric. Review the Garmin website and forums to learn more, or feel free to get in touch.
Metric Displays “N/D”
The “No Data” message will display if data was currently unavailable for this field. This could happen for a variety of reasons, and it’s likely only temporary.
For example, if this is a metric reported by a local weather station, and equipment malfunction at the weather station may prevent this information from being available to Garmin and, by extension, your watch face.
Another example would be if your metric is “Respiration Rate” and your watch couldn’t calculate a valid value. That could occur because the watch is not on your wrist, too loose on your wrist, or just because… In any event, once the information becomes available again, the data should come through again.
In general, your watch is indicating that it just doesn’t have this value available to display.
To resolve this message, you can wait a while and see if it resolves itself. Otherwise, select another metric that is available.
Metric Displays “INV”
This means that Garmin provided some invalid data to one of the metrics your watch face requested via the new “Complications” API. For example, if you set a metric to display “Respiration Rate”, Garmin is supposed to provide a number, like 14. It’s important for that to be a number so the watch face can plot it. But you’ll see this message if Garmin send something odd, like text. That’s not supposed to happen, but the Complications API is new and Garmin sometimes doesn’t get things right on the first try.