0.6.0 - Women's Health & FIT files (Garmin) #1178
KaliszS
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Highlights
Women's Health
We now support
menstrual cycle trackingfor Garmin wearables. The new women's health tab is only available if the user has fetched any related data. Otherwise, it is invisible.Ingest workout samples (high data granularity)
We have added an option to enable second-by-second granularity for certain data from Garmin, such as
heart rate,speed,cadence,power,latitude,longitude,elevationandrunning dynamics(which require a FIT file), as well asair temperature(also requires FIT file to be available).Caution
This option is disabled by default. To enable it, you must set the
INGEST_WORKOUT_SAMPLESenvironment variable totrue.Warning
According to our tests, this will increase database memory usage by approximately
170 MBper user per month.FIT file parser and saving to S3
A parser for FIT files has been implemented. Currently, there is no option to upload these files manually; they are processed automatically via Garmin webhooks. However, the same parser will eventually support other providers.
Garmin currently extracts the following data from FIT files and saves it to the database:
INGEST_WORKOUT_SAMPLESrequired)INGEST_WORKOUT_SAMPLESrequired)INGEST_WORKOUT_SAMPLESrequired)INGEST_WORKOUT_SAMPLESrequired)INGEST_WORKOUT_SAMPLESrequired)INGEST_WORKOUT_SAMPLESrequired)Note
We have added a new environment variable called
STORE_FIT_FILES, which is set tofalseby default. When this is set totrue, raw FIT files from Garmin will be saved to a previously configured S3 bucket. See the S3 configuration guide for more information: https://openwearables.io/docs/dev-guides/raw-payload-storageMany Oura bugs fixed
We have fixed several bugs relating to the Oura integration. We have added
time zone offsetsaving to the database, supportedsleep summary metrics, improved data retrieval forcurrent day summariesand migratedHRV from SDNN to RMSSD. Existing SDNN values in the database will be migrated by an automatic script that runs when the application starts.Added redis TLS support
To enable TLS support (
rediss://), set the new environment variableREDIS_SSLto true.The day prefix for sleep start times that began before midnight
From now on, the start time of a sleep session in the sleep section will be prefixed with the previous day’s name if it was before midnight. If a sleep session ends after midnight, it will be displayed under the following day in the admin UI (as it always has been). Please note that this is dynamic and will adjust to the user’s time zone.
Support for synchronising the same data across multiple accounts
We have added dedicated support for users who need to synchronise their devices with several Open Wearables accounts for testing purposes. No configuration is required to use this feature. Simply pair the relevant accounts with your wearables account and synchronise any of them. A badge will appear in each account to indicate which accounts are
linked, along with the relevant sync statuses. This shows that, for a given account, the source of the currently syncing data is alinked Open Wearables account. This means that, instead of repeatedly syncing the same data - which is virtually impossible with Garmin during backfilling, for example - it will be synced once and copied to the other accounts.What's Changed
Garmin FIT files & high granularity data support
Garmin Women's Health
Oura bugs
Apple Health bugs
Suunto bugs
Polar bugs
Infrastructure improvements
Other improvements
Docs & chores
New Contributors
Full Changelog: 0.5.2...0.6.0
This discussion was created from the release 0.6.0 - Women's Health & FIT files (Garmin).
Beta Was this translation helpful? Give feedback.
All reactions