No new measurements

[scattym]

I have just installed and setup omramin and gone through the init process, logging both into garmin and omron without any trouble.

In the app on my phone I can see measurements and I have hit the "sync" button to sync with the device by bluetooth.

When I run the omramin sync or omramin sync --days 6, it just comes up with "No measurements".

Device: Omron 7361T

Debug:

[2026-02-07 10:02:22] [D] Debug mode enabled (all loggers at DEBUG level)
[2026-02-07 10:02:22] [D] Detected system keyring: keyring.backends.SecretService.Keyring
[2026-02-07 10:02:22] [D] Loaded garmin tokens from keyring backend
[2026-02-07 10:02:22] [D] Attempting Garmin login using cached tokens for REDACTED
[2026-02-07 10:02:23] [D] Garmin login successful using cached tokens for REDACTED
[2026-02-07 10:02:23] [I] Logged in to Garmin Connect
[2026-02-07 10:02:23] [D] Loaded omron tokens from keyring backend
[2026-02-07 10:02:23] [D] Attempting OMRON token refresh for REDACTED (country=AU)
[2026-02-07 10:02:23] [D] HTTP Request: POST https://data-sg.omronconnect.com/api/oauth2/token
[2026-02-07 10:02:23] [D] HTTP Request Headers: Headers({'host': 'data-sg.omronconnect.com', 'accept': '*/*', 'accept-encoding': 'gzip, deflate, br, zstd', 'connection': 'keep-alive', 'user-agent': 'OmronConnect/010.003.00001.001 CFNetwork/1335.0.3.4 Darwin/21.6.0)', 'x-ogsc-sdk-version': '000.101', 'x-ogsc-app-version': '010.003.00001', 'x-kii-appid': 'lou30y2xfa9f', 'x-kii-appkey': '392a4bdff8af4141944d30ca8e3cc860', 'content-length': '1851', 'content-type': 'application/json'})
[2026-02-07 10:02:23] [D] HTTP Request Body:
{REDACTED}
[2026-02-07 10:02:24] [D] HTTP Response: https://data-sg.omronconnect.com/api/oauth2/token 200
[2026-02-07 10:02:24] [D] HTTP Response Headers: Headers([('content-type', 'application/json;charset=UTF-8'), ('transfer-encoding', 'chunked'), ('connection', 'keep-alive'), ('date', 'Fri, 06 Feb 2026 23:02:24 GMT'), ('feature-policy', "geolocation 'none'; midi 'none'; sync-xhr 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; fullscreen 'self'; payment 'none'"), ('content-encoding', 'gzip'), ('vary', 'Origin'), ('vary', 'Access-Control-Request-Method'), ('vary', 'Access-Control-Request-Headers'), ('vary', 'origin,access-control-request-method,access-control-request-headers,accept-encoding'), ('x-content-type-options', 'nosniff'), ('x-xss-protection', '1; mode=block'), ('cache-control', 'no-cache, no-store, max-age=0, must-revalidate'), ('pragma', 'no-cache'), ('expires', '0'), ('x-frame-options', 'DENY'), ('content-security-policy', "default-src 'self'; frame-src 'self' data:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://storage.googleapis.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:"), ('referrer-policy', 'strict-origin-when-cross-origin'), ('x-cache', 'Miss from cloudfront'), ('via', '1.1 00f0469d54a973389150a36c64065326.cloudfront.net (CloudFront)'), ('x-amz-cf-pop', 'SYD62-P1'), ('x-amz-cf-id', '')])
[2026-02-07 10:02:24] [D] HTTP Response Body:
{REDACTED}
[2026-02-07 10:02:24] [D] GZip decompression failed: Error -3 while decompressing data: incorrect header check
[2026-02-07 10:02:24] [I] Logged in to OMRON connect
[2026-02-07 10:02:24] [I] Start synchronizing device 'HEM-7361T-AP:0' from 2026-02-07 to 2026-02-07
[2026-02-07 10:02:24] [D] Device details: MAC=bf:ff:fe:58:6b:d1, Serial=d16b58fefffeffbf, User=0, Category=BPM
[2026-02-07 10:02:24] [D] HTTP Request: POST https://data-sg.omronconnect.com/api/apps/lou30y2xfa9f/server-code/versions/current/measureData
[2026-02-07 10:02:24] [D] HTTP Request Headers: Headers({'host': 'data-sg.omronconnect.com', 'accept': '*/*', 'accept-encoding': 'gzip, deflate, br, zstd', 'connection': 'keep-alive', 'user-agent': 'OmronConnect/010.003.00001.001 CFNetwork/1335.0.3.4 Darwin/21.6.0)', 'x-ogsc-sdk-version': '000.101', 'x-ogsc-app-version': '010.003.00001', 'x-kii-appid': 'lou30y2xfa9f', 'x-kii-appkey': '392a4bdff8af4141944d30ca8e3cc860', 'authorization': '[secure]', 'content-length': '197', 'content-type': 'application/json'})
[2026-02-07 10:02:24] [D] HTTP Request Body:
{
  "containCorrectedDataFlag":1,
  "containAllDataTypeFlag":1,
  "deviceCategory":"0",
  "deviceSerialID":"d16b58fefffeffbf",
  "userNumberInDevice":0,
  "searchDateFrom":1770382800000,
  "searchDateTo":1770469199000
}
[2026-02-07 10:02:24] [D] HTTP Response: https://data-sg.omronconnect.com/api/apps/lou30y2xfa9f/server-code/versions/current/measureData 200
[2026-02-07 10:02:24] [D] HTTP Response Headers: Headers([('content-type', 'application/json;charset=UTF-8'), ('content-length', '63'), ('connection', 'keep-alive'), ('date', 'Fri, 06 Feb 2026 23:02:24 GMT'), ('feature-policy', "geolocation 'none'; midi 'none'; sync-xhr 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; fullscreen 'self'; payment 'none'"), ('vary', 'Origin'), ('vary', 'Access-Control-Request-Method'), ('vary', 'Access-Control-Request-Headers'), ('vary', 'Origin'), ('vary', 'Access-Control-Request-Method'), ('vary', 'Access-Control-Request-Headers'), ('x-content-type-options', 'nosniff'), ('x-xss-protection', '1; mode=block'), ('cache-control', 'no-cache, no-store, max-age=0, must-revalidate'), ('pragma', 'no-cache'), ('expires', '0'), ('x-frame-options', 'DENY'), ('content-security-policy', "default-src 'self'; frame-src 'self' data:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://storage.googleapis.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:"), ('referrer-policy', 'strict-origin-when-cross-origin'), ('x-cache', 'Miss from cloudfront'), ('via', '1.1 00f0469d54a973389150a36c64065326.cloudfront.net (CloudFront)'), ('x-amz-cf-pop', 'SYD62-P1'), ('x-amz-cf-id', '')])
[2026-02-07 10:02:24] [D] HTTP Response Body:
{
  "returnedValue":{
    "deviceCategory":"0",
    "deviceModelList":null
  }
}
[2026-02-07 10:02:24] [D] {'returnedValue': {'deviceCategory': '0', 'deviceModelList': None}}
[2026-02-07 10:02:24] [I] No new measurements
[2026-02-07 10:02:24] [I] Device 'HEM-7361T-AP:0' successfully synced.
[2026-02-07 10:02:24] [I] Start synchronizing device 'HEM-7361T-AP:1' from 2026-02-07 to 2026-02-07
[2026-02-07 10:02:24] [D] Device details: MAC=bf:ff:fe:58:6b:d1, Serial=d16b58fefffeffbf, User=1, Category=BPM
[2026-02-07 10:02:24] [D] HTTP Request: POST https://data-sg.omronconnect.com/api/apps/lou30y2xfa9f/server-code/versions/current/measureData
[2026-02-07 10:02:24] [D] HTTP Request Headers: Headers({'host': 'data-sg.omronconnect.com', 'accept': '*/*', 'accept-encoding': 'gzip, deflate, br, zstd', 'connection': 'keep-alive', 'user-agent': 'OmronConnect/010.003.00001.001 CFNetwork/1335.0.3.4 Darwin/21.6.0)', 'x-ogsc-sdk-version': '000.101', 'x-ogsc-app-version': '010.003.00001', 'x-kii-appid': 'lou30y2xfa9f', 'x-kii-appkey': '392a4bdff8af4141944d30ca8e3cc860', 'authorization': '[secure]', 'content-length': '197', 'content-type': 'application/json'})
[2026-02-07 10:02:24] [D] HTTP Request Body:
{
  "containCorrectedDataFlag":1,
  "containAllDataTypeFlag":1,
  "deviceCategory":"0",
  "deviceSerialID":"d16b58fefffeffbf",
  "userNumberInDevice":1,
  "searchDateFrom":1770382800000,
  "searchDateTo":1770469199000
}
[2026-02-07 10:02:24] [D] HTTP Response: https://data-sg.omronconnect.com/api/apps/lou30y2xfa9f/server-code/versions/current/measureData 200
[2026-02-07 10:02:24] [D] HTTP Response Headers: Headers([('content-type', 'application/json;charset=UTF-8'), ('content-length', '63'), ('connection', 'keep-alive'), ('date', 'Fri, 06 Feb 2026 23:02:24 GMT'), ('feature-policy', "geolocation 'none'; midi 'none'; sync-xhr 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; fullscreen 'self'; payment 'none'"), ('vary', 'Origin'), ('vary', 'Access-Control-Request-Method'), ('vary', 'Access-Control-Request-Headers'), ('vary', 'Origin'), ('vary', 'Access-Control-Request-Method'), ('vary', 'Access-Control-Request-Headers'), ('x-content-type-options', 'nosniff'), ('x-xss-protection', '1; mode=block'), ('cache-control', 'no-cache, no-store, max-age=0, must-revalidate'), ('pragma', 'no-cache'), ('expires', '0'), ('x-frame-options', 'DENY'), ('content-security-policy', "default-src 'self'; frame-src 'self' data:; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://storage.googleapis.com; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:"), ('referrer-policy', 'strict-origin-when-cross-origin'), ('x-cache', 'Miss from cloudfront'), ('via', '1.1 00f0469d54a973389150a36c64065326.cloudfront.net (CloudFront)'), ('x-amz-cf-pop', 'SYD62-P1'), ('x-amz-cf-id', '')])
[2026-02-07 10:02:24] [D] HTTP Response Body:
{
  "returnedValue":{
    "deviceCategory":"0",
    "deviceModelList":null
  }
}
[2026-02-07 10:02:24] [D] {'returnedValue': {'deviceCategory': '0', 'deviceModelList': None}}
[2026-02-07 10:02:24] [I] No new measurements
[2026-02-07 10:02:24] [I] Device 'HEM-7361T-AP:1' successfully synced.```

```bash
omramin list
[2026-02-07 10:08:29] [I] ----------------------------------------
[2026-02-07 10:08:29] [I] Name:        HEM-7361T-AP:0
[2026-02-07 10:08:29] [I] MAC Address: bf:ff:fe:58:6b:d1
[2026-02-07 10:08:29] [I] Category:    BPM
[2026-02-07 10:08:29] [I] User:        0
[2026-02-07 10:08:29] [I] Enabled:     True
[2026-02-07 10:08:29] [I] ----------------------------------------
[2026-02-07 10:08:29] [I] Name:        HEM-7361T-AP:1
[2026-02-07 10:08:29] [I] MAC Address: bf:ff:fe:58:6b:d1
[2026-02-07 10:08:29] [I] Category:    BPM
[2026-02-07 10:08:29] [I] User:        1
[2026-02-07 10:08:29] [I] Enabled:     True
[2026-02-07 10:08:29] [I] ----------------------------------------

[bugficks]

Is this log from --days 6? It says from 2026-02-07 to 2026-02-07, and the timestamps show:

searchDateFrom: 1770382800000 -> UTC 2026-02-06 13:00:00 | Local time 2026-02-06 20:00:00
searchDateTo: 1770469199000 -> UTC 2026-02-07 12:59:59 | Local time 2026-02-07 19:59:59

This looks correct to me. There isn’t much I can do if omron does not return any measurements for the requested date range.

I found this, but it’s from years ago:
https://apps.apple.com/au/app/omron-connect/id1003177043

Maybe try an even bigger range? Like 30 or 100 days?

[scattym]

Yeah, I tried setting days to 365 and still nothing.

I suspect the data is in a different api endpoint or appid.

How did you find the current api endpoints and the current appids? Just wondering if there are other endpoints I could poke around to see.

[bugficks]

A capture would certainly help to compare the original request parameters with the ones used by omramin.

To get all endpoints, regions, etc you need to decompile the android apk or decrypt ios ipa :)

Capturing traffic used to be pretty simple by using a proxy like https://proxyman.com or https://www.charlesproxy.com. But recent omron connect versions seem to have introduced SSL pinning, though I don’t remember if that was EU version only. To bypass this you can use https://github.com/mitmproxy/android-unpinner with an Android emulator using this image

sdkmanager --list_installed | grep "system-images;android-33;google_apis;arm64-v8a"
  system-images;android-33;google_apis;arm64-v8a | 17      | Google APIs ARM 64 v8a System Image | system-images/android-33/google_apis/arm64-v8a

One major problem with the Android emulator: it does not natively support Bluetooth for connecting to physical Bluetooth devices. You can only use it for fetching data from the cloud.

I did set up an AU account today to verify the endpoint; looks good to me:

POST /api/apps/lou30y2xfa9f/server-code/versions/current/synchronizeLoggingData HTTP/1.1
X-Kii-AppID: lou30y2xfa9f
X-Kii-AppKey: 392a4bdff8af4141944d30ca8e3cc860
X-OGSC-App-Version: 011.004.00000
X-OGSC-SDK-Version: 000.005
...
Host: data-sg.omronconnect.com

[AndersHogqvist]

Check that "Save my values in the cloud" is enabled in the OMRON connect app under account settings.

[JoelBrenstrum]

Im seeing the same issue with a HEM-7361T

Im in NZ and have my country set to AU (Initial setup failed using NZ but found my device when set to AU)

omramin --debug sync --days 365

{
  "returnedValue":{
    "deviceCategory":"0",
    "deviceModelList":null
  }
}
[2026-05-12 10:36:15] [D] {'returnedValue': {'deviceCategory': '0', 'deviceModelList': None}}
[2026-05-12 10:36:15] [I] No new measurements
[2026-05-12 10:36:15] [I] Device 'HEM-7361T-AP:1' successfully synced.```

[bugficks]

Did you enable cloud sync in app settings before taking measurements?
See e.g.: https://help.validic.com/space/VCS/4940759063/Ensuring+Omron+Connect+App+Data+Syncs+to+the+Cloud

[JoelBrenstrum]

That link doesn't seem to work for me.

I believe I have had it syncing with the cloud for a long time.

[JoelBrenstrum]

Employed some AI help and managed to find my BP readings on another endpoint https://elb-sg.bp-manager.com/api/get_vital_data

Here is a summary of the steps taken to get to this point

Root Cause Found: Measurements are on a separate "BP Manager" API

I've been investigating this issue with a HEM-7361T-AP in the NZ (SG region) and have found the root cause. The OMRON Connect app does not use the Kii v1 measureData endpoint for blood pressure readings — it uses a completely separate service.

Discovery

By capturing TLS SNI traffic from the OMRON Connect Android app during a sync, I found the app connects to three OMRON-related hosts:

Host	Purpose
data-sg.omronconnect.com	Kii v1 API — device config/metadata only
elb-sg.bp-manager.com	BP Manager API — actual measurement data
cdn-s3-prod-apse1-hi817sg.bp-manager.com	CDN for BP Manager static assets

Architecture

The OMRON Connect app has two layers:

1. Native layer — handles Bluetooth pairing, Kii cloud sync (device metadata, sequence numbers, etc.)
2. WebView layer — a Vue.js SPA ("BP Manager") served from elb-sg.bp-manager.com that displays and manages the actual BP readings

The native layer authenticates with AWS Cognito (ap-southeast-1), and the resulting access token is passed to the WebView via a JavaScript bridge. The WebView uses this token to call the BP Manager REST API.

This is why omramin can successfully authenticate and get device metadata from the Kii API, but measureData returns deviceModelList: null — the measurements are simply not stored there.

BP Manager API

Base URL: https://elb-sg.bp-manager.com

Endpoints (extracted from decompiled JS bundle)

Endpoint	Method	Description
/api/get_vital_data	POST	Fetch BP measurements
/api/get_settings	POST	Get user settings
/api/register_setting	POST	Update settings
/api/set_memo	POST	Update memo/notes
/api/bp_notebook	POST	Export notebook (PDF/CSV)
/api/get_device_info	POST	Get device info
/api/get_regular_report_setting	POST	Report settings
/api/set_regular_report	POST	Configure reports
/get_access_token	—	Token exchange (unused in current app)
/user-info	—	User information

Authentication

The API uses AWS Cognito access tokens (not Kii tokens):

• Cognito User Pool: ap-southeast-1_byhQyfpyM
• Client ID: 3r0hqg0f0oivg1vok4dqci8mhh
• Auth header: Authorization: Bearer <cognito_access_token>

Fetching Measurements — Working Example

curl -X POST https://elb-sg.bp-manager.com/api/get_vital_data \
  -H "Authorization: Bearer <cognito_access_token>" \
  -H "Content-Type: application/json" \
  -d '{
    "start_date_time": "202604120000",
    "end_date_time": "202605132359",
    "traceId": "omramin",
    "screenName": "fetch",
    "vital_category": "0"
  }'

Response Format

{
  "success": true,
  "vitals": [
    {
      "deviceModel": "HEM-7361T-AP",
      "systolic": "122",
      "diastolic": "88",
      "pulse": "84",
      "strange_pulse": "0",
      "is_motion": "0",
      "tight_fit": "1",
      "afib_detect": "0",
      "afib_mode": "0",
      "measure_date": "2026-05-12T21:52:10",
      "timeZone": "Pacific/Auckland"
    }
  ],
  "memo": []
}

Request Parameters for get_vital_data

Parameter	Type	Description
start_date_time	string	Start date YYYYMMDDHHmm format
end_date_time	string	End date YYYYMMDDHHmm format
vital_category	string	"0" for blood pressure
traceId	string	Trace identifier (any string)
screenName	string	Screen name (any string)
total_count	int	(optional) Limit records returned

What omramin Needs to Change

For SG-region users (AU, NZ, and potentially others), omramin should:

1. Authenticate with Cognito instead of (or in addition to) Kii — the Cognito user pool and client ID are listed above. Standard USER_PASSWORD_AUTH flow with the same email/password used for OMRON Connect.
2. Call /api/get_vital_data on elb-sg.bp-manager.com with the Cognito access token.
3. Map the response — the fields map straightforwardly to the existing BPM measurement model (systolic, diastolic, pulse, measure_date, etc.).

How I Found This

1. MikroTik packet capture → tshark TLS SNI extraction revealed elb-sg.bp-manager.com
2. APK decompilation (jadx) of jp.co.omron.healthcare.omron_connect showed the WebView architecture
3. JS bundle analysis of cdn-s3-prod-apse1-hi817sg.bp-manager.com/index.js.gz revealed all API endpoints and request formats
4. Successfully called the API with a Cognito token and received measurement data

Environment

• Device: HEM-7361T-AP
• Region: NZ (maps to SG/v1 server)
• OMRON Connect: Android, latest version
• omramin config: country: "NZ", category: "BPM"

[bugficks]

This is weird, to say the least. Maybe they changed that recently? When I logged traffic with an AU account, all measurements went to the data-sg endpoint.

Anyway, this is a completely different API and would require quite a few changes.

[JoelBrenstrum]

Maybe @scattym could run the curl example and confirm it's also returning his data before making any changes.

I did confirm I can see my latest readings via get_vital_data