Guide
Huawei Health and Health Connect: is there an official sync? (2026)
Huawei is not part of the Google Mobile Services ecosystem, so your Huawei smartwatch data does not automatically arrive in Health Connect. This is what works today and what is coming soon.
TL;DR
- Huawei Health does not write directly to Health Connect. This is a structural limitation of the HMS ecosystem, which is separate from GMS.
- The only available workaround today is a third-party bridge app. FitMesh is building direct cloud access via Huawei Health Kit for a native solution, coming soon.
- Native Huawei integration is under development and not available yet: when it ships, it will arrive with a FitMesh app update
In 2026 if you have a Huawei smartwatch, whether it's a Watch GT4, a Watch 4 Pro, or a Band 9, you might have noticed that your data does not appear in Health Connect. It is not a bug: it is a structural limitation of the HMS (Huawei Mobile Services) ecosystem, which is separated from GMS (Google Mobile Services). Huawei Health, the native Huawei app, does not write to Health Connect because it has not integrated Google's API. This post explains the current situation, the available options today, and where FitMesh is heading.
The problem: Huawei and Google are not talking to each other
Huawei has developed its own mobile service stack, HMS, as an alternative to GMS following the 2019 US sanctions. HMS includes Huawei Health as a reference health app. Google Health Connect is an open Android standard, but it depends on GMS for some core features. The result: Huawei Health and Health Connect live in separate ecosystems, and no native bridge exists between the two at the operating system level.
How synchronization works today
In 2026, the options for those who want to bring Huawei data into Health Connect are limited. The only known workaround so far has been a third-party bridge app that acts as a relay between Huawei Health and Health Connect. These apps work, but they have limitations: they require elevated permissions, synchronization is manual or semi-automatic, and the coverage of data types is not complete. There is no official native integration from Huawei.
The FitMesh solution: native Huawei Health Kit integration
FitMesh is building a native integration that reads your Huawei health and fitness data directly from the Huawei Health Kit cloud. This means it works on any Android device, with no Health Connect required. When the integration goes live, FitMesh will pull your data straight from Huawei's cloud and surface it in your unified dashboard. Data types covered in the planned integration: steps, sleep, heart rate, SpO2, calories.
| Data type | Current Support (via bridge) | FitMesh Support (planned) |
|---|---|---|
| Steps | Partial (bridge app) | Yes |
| Sleep | Partial (bridge app) | Yes |
| Heart rate | Limited | Yes |
| SpO2 | Not available | Yes |
| Calories | Partial | Yes |
Status of the Huawei integration
Native Huawei integration is actively under development and is not available yet. When it ships, it will arrive with a FitMesh app update, together with the release notes describing how it works.
Frequently asked questions
Does Huawei Health write to Health Connect?+
No. In 2026, Huawei Health does not have native integration with Health Connect. HMS and GMS are separate ecosystems. To transfer your data you currently need a third-party bridge app. FitMesh's native Huawei support, which reads directly from the Huawei Health Kit cloud on any Android device with no Health Connect required, is under development and not available yet.
Can I bridge Huawei Health data to Health Connect today?+
Yes, third-party bridge apps can connect Huawei Health to Health Connect. They work, but they are not a native solution: synchronization is typically manual or periodic, and not all data types are supported. FitMesh is building a direct alternative that reads your Huawei data straight from the Huawei Health Kit cloud, with no bridge or Health Connect needed.
When will Huawei support be available in FitMesh?+
FitMesh's native Huawei integration, which reads data directly from the Huawei Health Kit cloud, is actively under development. There is no specific date yet: the update will be announced in FitMesh's app release notes.
Are Huawei data accessible via Health Connect?+
Not natively. If you use a Huawei device on Android with GMS installed (as with some basic models), you might be able to configure a partial sync using a third-party bridge app. But HMS-only devices (like the Watch GT) do not communicate with Health Connect without an explicit bridge. FitMesh's upcoming Huawei integration bypasses this entirely by reading your data directly from the Huawei Health Kit cloud.
Disclaimer
FitMesh Sync is an independent product. Huawei, Google, Android are trademarks of their respective owners. This article implies no affiliation or sponsorship.
Medical disclaimer
The information in this article is for informational purposes only and does not replace advice from your physician, pharmacist or healthcare professional. FitMesh Sync is a fitness/wellness app, not a medical device, and does not diagnose or treat any conditions. For symptoms, clinical questions or treatment decisions always consult your primary care physician.
Written by
Matteo Pizzi
Founder & Solo Dev, FitMesh Sync · Fosforonero
Italian software developer. I built FitMesh Sync to fill the gap between my smartwatch and a real personal dashboard. Privacy-first, indie, EU servers.
More about the projectKeep reading
Comparison
Wearable sync app alternatives in 2026: full landscape
The 'bridge app' category has been crowded for years. With Health Connect arriving the landscape shifted: let's see what exists today and when each makes sense.
Guide
How Health Connect works: the complete guide for Android
Health Connect is not just an app: it's the data exchange layer that lets all Android health apps communicate. Here's what it actually does, how it manages your permissions, and what happens when something doesn't work.
Guide
Best health data sync app for Android: 2026 guide
Health Connect is the socket in the wall. An app that plugs in directly reads everything your wearable wrote there. An app that bypasses it needs its own cable to every single device, and that cable breaks constantly.