> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/integrations/hme-integration.md).
# HME Integration
Learn how to manage your HME system with Solink.
This section provides information to help you manage your HME system with Solink.
### Set or Reset HME Password
Please call the [HME support line](https://www.hme.com/qsr/contact/) (1-800-848-4468) if you have never set an HME password or have forgotten your password.
You can also refer to the HME website for a video on how to set or reset your HME password.
Select the link [here](https://www.hme.com/training/DTOS/) to access the **Setting Passwords** video:
### Identify HME Equipment
Please refer to the HME [Drive-Thru Equipment Identification Guide](https://www.hme.com/qsr/support/equipment-identification-guide/) on the HME website to help identify your equipment.
### External Communication Setup
To set up external communication (IP TCP connection setup), please refer to the [HME guide here](https://www.hme.com/techPdfs/400G758B.pdf) and navigate to the **Advanced Settings - External Communication** section on page 66.
---
# 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://help.solink.com/docs/install-connect-and-integrate/integrations/hme-integration.md?ask=&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.