1. A watch or app records data
The watch hardware and its source app determine what is captured. That may include a sleep session, estimated stages, heart rate, oxygen saturation or respiratory rate, but the exact set varies by device and app.
Wear OS sleep tracking
Wear OS sleep tracking: what Health Connect may add to a SomnoRoute report.
A Wear OS watch does not give every app one standard sleep dataset. A compatible watch or source app may write supported sleep and wellness records to Health Connect; SomnoRoute's planned private-beta Android route may then read only the categories the user permits and that actually contain data.
Product author: Mark McEnroe, SomnoRoute founder and product owner. Source review: SomnoRoute Editorial Team, updated 2 August 2026. Independent clinical review of health-context wording is pending. Health Connect context is planned for private beta, not generally available through Google Play, and it cannot diagnose a sleep condition. Read our editorial standards.
How the route works
Watch, source app, Health Connect, then report.
Keeping this chain visible avoids implying that Health Connect measured something it only stored, or that all Wear OS devices support the same categories.
2. The source writes supported records
Health Connect can store a completed sleep session with start and end times and stage estimates, alongside separate heart-rate, oxygen-saturation or respiratory-rate records. It does not create missing measurements.
3. The user controls permission
Android requires declared and runtime permissions for each Health Connect category. Users can deny, pause or revoke access. SomnoRoute should request only what the optional report feature needs.
4. SomnoRoute keeps sources labelled
The planned report route may place available Health Connect context beside phone-recorded sound and SomnoRoute evidence. It should retain source attribution, sample coverage and missing-data labels rather than merge everything into one unexplained score.
What may be available
Useful categories depend on the source.
Sleep sessions and stages
A Health Connect sleep session can include start time, end time and source-provided deep, light, REM or awake stages. These remain estimates produced by the source, not clinical sleep staging.
Heart-rate records
A compatible source may write heart-rate samples recorded during sleep. The report should show the source and coverage and avoid claiming that a heart-rate change was caused by a nearby sound.
Oxygen and respiratory records
Compatible sources may provide oxygen-saturation or respiratory-rate records. Their frequency and coverage vary; they are not automatically equivalent to a continuous clinical channel.
Missing or duplicated sources
More than one app may write overlapping records, or no app may write the category at all. SomnoRoute's planned route needs source attribution and deduplication rather than assuming Health Connect holds one definitive answer.
Product evidence
Current private-beta Android report screens.
These are SomnoRoute Android interface screenshots. They show the existing report and Plus workflow; they are not proof that a given Wear OS or Health Connect category was present.
What this shows
SomnoRoute's Android reporting route exists before Health Connect is assumed.
The app can organise its own report workflow without connected health data. Wear OS and Health Connect context remains a planned, optional beta layer that should appear only when source support, permission and records are available.
Limitations
What a Wear OS report cannot establish.
Not every watch is compatible
Wear OS is a platform, not one sensor specification. A device may omit a category, use a different source app, require different setup or not write historical data to Health Connect.
Permission is not proof of coverage
Granting permission allows an app to request records; it does not guarantee that the source wrote them or that they cover the whole SomnoRoute monitoring window.
Timing does not prove cause
A nearby snore, movement, heart-rate sample or oxygen value can be useful to review, but proximity alone does not establish a physiological or medical cause.
Consumer context is not a sleep test
SomnoRoute is designed for awareness and evidence organisation. Read what sleep trackers can and cannot tell you and seek professional advice about concerning symptoms.
Questions
Wear OS, Health Connect and SomnoRoute FAQ.
How may Wear OS sleep data reach SomnoRoute?
A compatible watch or source app may record data and write supported records to Health Connect. SomnoRoute's planned private-beta Android route may then read only the categories the user permits, where the source, device and app support them.
Does Health Connect measure sleep by itself?
No. Health Connect is a user-controlled store and exchange layer for records written by compatible apps and devices. The source app determines which sleep, heart-rate, oxygen-saturation or respiratory-rate records exist.
Does every Wear OS watch provide the same sleep data?
No. Capabilities vary by watch, source app, software version, region, Health Connect support, permission and whether data was recorded and synced. Missing categories must remain unavailable.
Is SomnoRoute's Health Connect route generally available?
No. SomnoRoute is in private beta and Health Connect context remains a planned beta capability where support, permission and data are available. It is not generally available from Google Play.
Primary sources
Official Android documentation used for this guide.
Health Connect sleep records
Android's Health Connect sleep guide describes sleep sessions, source-provided stages and separate heart-rate, oxygen-saturation and respiratory-rate records.
Permissions and user control
Android's Health Connect permission guidance describes pausing sync, managing access, insufficient access and revoking permission.
Supported data types
Android's Health Connect data-type reference lists record types and their separate read permissions.
SomnoRoute routes
Review the planned Health Connect route, privacy and safety, or go to the private-beta application route.