By PulsHealth. Updated
Research reviewed .
What is Audio Exposure Event?
Audio Exposure Event is the deprecated environmental-noise event identifier. Apple’s documentation directs developers to environmentalAudioExposureEvent and its corresponding category values. Existing exported records still need their original identifier and meaning preserved.
The legacy named value is loudEnvironment, numeric code 1. It is an event category, not a one-decibel reading or a severity score. Apple’s legacy value documentation identifies the loud-environment case.
What did the checked example contain?
The reporting year contained 56 legacy-identifier records across two source groups. July–September contained 19 records: 17 in the larger source and two in the smaller. Every observed code was 1, consistent with the named legacy event.
| Property | Example result | Interpretation |
|---|---|---|
| Larger source | 17 events on 15 days | Recorded notifications, not monitored-day risk |
| Stored duration | About 160–175 seconds | Event interval, not a validated harmful-dose duration |
| Workout overlap | Two events in the larger source | Timing overlap only |
| Recorded-sleep overlap | None in either focus source | No conclusion about unrecorded nights |
The year’s use of a deprecated identifier is an export observation. It does not prove that the underlying recording device or notification algorithm was an old version. Do not silently relabel rows as a different HealthKit type or merge them with a successor stream without checking the source and possible duplicates.
How does this differ from the current Noise notification?
Apple’s current environmental event documentation describes an alert after a three-minute average meets a configured threshold. That current rule helps explain the feature; it is not enough to independently reconstruct the trigger of every legacy row.
The legacy snapshot includes HKMetadataKeyAudioExposureLevel. Inspect this associated level separately from the category code and the stored interval. Metadata at an event cannot recover threshold-setting history or notification eligibility on days without events.
Can notification counts show how noisy life is?
They can describe when notifications were recorded, but the required observation denominator is missing. Counts depend on settings, wearing and measurement coverage, as well as sound. A gap between alerts is a logging interval, not the duration of quiet surroundings.
How does this relate to the numeric audio stream?
Environmental Audio Exposure contains interval-level dB(A) observations. The notebook inspects numeric samples overlapping event windows, without assuming an explicit link to the triggering observation. Sparse neighbors and long summaries cannot recreate the alert’s internal calculation.
Headphone Audio Exposure Event describes a different, seven-day headphone-exposure notification. Its code and exposure window must not be conflated with this environmental category. Neither notification category diagnoses hearing damage, and an absent category stream does not certify safe listening.
Understanding your records
Recording frequency, source and coverage affect what you can conclude from this data. Read the recording guide.