SelfSync

Time in zone message

Time in zone messages tell how long was spent in each heart rate, speed, cadence and power zone during a session or a lap, along with the zone boundaries and thresholds used for the computation.

FIT name
time_in_zone
Global message number
216
JavaScript SDK key
timeInZoneMesgs
Fields
18

Fields

  • timestampDateTimes

    Moment the message refers to, in UTC. FIT stores it as seconds since the FIT epoch (December 31, 1989, 00:00:00 UTC); decoders usually expose it as a regular date.

  • Kind of message the times refer to: session or lap.

    127 possible values
    • length
    • split
    • set
    • record
    • session
    • hr
    • video
    • event
    • sport
    • activity
    • workout
    • course
    • totals
    • bloodPressure
    • mfgRangeMin
    • mfgRangeMax
    • fileId
    • capabilities
    • deviceSettings
    • userProfile
    • hrmProfile
    • sdmProfile
    • bikeProfile
    • zonesTarget
    • hrZone
    • powerZone
    • metZone
    • trainingSettings
    • goal
    • lap
    • deviceInfo
    • workoutStep
    • schedule
    • weightScale
    • coursePoint
    • software
    • fileCapabilities
    • mesgCapabilities
    • fieldCapabilities
    • fileCreator
    • speedZone
    • monitoring
    • trainingFile
    • hrv
    • antRx
    • antTx
    • antChannelId
    • monitoringInfo
    • battery
    • pad
    • slaveDevice
    • connectivity
    • weatherConditions
    • weatherAlert
    • cadenceZone
    • segmentLap
    • memoGlob
    • segmentId
    • segmentLeaderboardEntry
    • segmentPoint
    • segmentFile
    • workoutSession
    • watchfaceSettings
    • gpsMetadata
    • cameraEvent
    • timestampCorrelation
    • gyroscopeData
    • accelerometerData
    • threeDSensorCalibration
    • videoFrame
    • obdiiData
    • nmeaSentence
    • aviationAttitude
    • videoTitle
    • videoDescription
    • videoClip
    • ohrSettings
    • exdScreenConfiguration
    • exdDataFieldConfiguration
    • exdDataConceptConfiguration
    • fieldDescription
    • developerDataId
    • magnetometerData
    • barometerData
    • oneDSensorCalibration
    • monitoringHrData
    • timeInZone
    • stressLevel
    • maxMetData
    • diveSettings
    • diveGas
    • diveAlarm
    • exerciseTitle
    • diveSummary
    • spo2Data
    • sleepLevel
    • jump
    • aadAccelFeatures
    • beatIntervals
    • respirationRate
    • hsaAccelerometerData
    • hsaStepData
    • hsaSpo2Data
    • hsaStressData
    • hsaRespirationData
    • hsaHeartRateData
    • splitSummary
    • hsaBodyBatteryData
    • hsaEvent
    • climbPro
    • tankUpdate
    • tankSummary
    • sleepAssessment
    • hrvStatusSummary
    • hrvValue
    • rawBbi
    • deviceAuxBatteryInfo
    • hsaGyroscopeData
    • chronoShotSession
    • chronoShotData
    • hsaConfigurationData
    • diveApneaAlarm
    • skinTempOvernight
    • hsaWristTemperatureData
    • napEvent
    • sleepDisruptionSeverityPeriod
    • sleepDisruptionOvernightSeverity
  • messageIndex of the session or lap the times refer to.

  • timeInHrZoneFloat64[]s

    Time spent in each heart rate zone. The first element is the time below zone 1, then zone 1, zone 2 and so on.

  • timeInSpeedZoneFloat64[]s

    Time spent in each speed zone.

  • Time spent in each cadence zone.

  • timeInPowerZoneFloat64[]s

    Time spent in each power zone. The first element is the time below zone 1, then zone 1, zone 2 and so on.

  • Upper boundary of each heart rate zone.

  • Upper boundary of each speed zone.

  • Upper boundary of each cadence zone (the typo is part of the FIT profile).

  • Upper boundary of each power zone.

  • How heart rate zones are computed: custom values, percentage of max heart rate, of heart rate reserve or of lactate threshold heart rate.

    4 possible values
    • custom
    • percentMaxHr
    • percentHrr
    • percentLthr
  • Maximum heart rate of the user used to compute the zones.

  • Resting heart rate of the user used to compute the zones.

  • Lactate threshold heart rate (LTHR) of the user, used to compute heart rate zones.

  • How power zones are computed: custom values or percentage of functional threshold power.

    2 possible values
    • custom
    • percentFtp
  • Functional threshold power (FTP) of the user: the highest power they can sustain for about an hour. Used to compute power zones.

  • mesgNumString

    Global message number identifying the kind of message. Decoders use it to know which profile to apply to the data.

Other activity messages

See all the FIT messages