> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/no-data/connected-but-no-data-arriving/huawei-permissions-and-toggles-required.md).

# Why does my Huawei connection send no data?

Huawei connecting without data almost always traces to a **permission or toggle on the user's side**, or missing key scopes.

Checklist:

* During the link flow, permissions are **deselected by default**, so the user must tap **select all**.
* Enable the **Health Service Kit** toggle under **Me > Privacy Management > Health service kit**. It is often off by default and is a common cause of `401`/no-data.
* Confirm cloud sync is on (**Me > Settings > Data sharing & Privacy**).
* Confirm they linked with the **same Huawei ID the watch is paired to**, with the watch paired and showing recent activity. Non-Huawei phones still need Huawei Health installed with cloud sync on.

For data **before** authentication, your dev team must add historical-data permissions to your Huawei keys in the Huawei console and re-submit the app for verification. Without them, you only get data after auth.

A screen recording of the full link flow helps confirm the permission step.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/no-data/connected-but-no-data-arriving/huawei-permissions-and-toggles-required.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.