> For the complete documentation index, see [llms.txt](https://docs.bluefletch.com/bluefletch-enterprise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application-1/sa-6/features/device-health-diagnostics.md).

# Device Health Diagnostics

A Support Application 6 feature that runs a guided pass/fail health check of a device's major subsystems.

## Overview

Use Device Health Diagnostics to walk through a sequential, pass/fail health check of the device's major subsystems. The feature presents a wizard-style flow through each category, runs the underlying check, and records a pass or fail result so problems can be triaged on-device without needing help-desk involvement.

## User Guide

To run Device Health Diagnostics, complete the following steps:

1. Open the Support Application on the device.
2. Navigate to Device Health Diagnostics.
3. Follow the wizard-style flow through each category in sequence.
4. Review the aggregated results summary once all checks are complete.

The diagnostics run through the following categories, in order: Battery → Network → Location → Bluetooth → NFC → RFID → Storage → Memory → Host/IP/Ports.

Each category runs its underlying check and records a pass/fail result. Results are aggregated into HealthTestResults and presented as a summary via HealthChart.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bluefletch.com/bluefletch-enterprise/product-guides/support-application-1/sa-6/features/device-health-diagnostics.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
