I have a 38mm S2 updated several weeks ago 1/29/2018) to the latest watchOS 4. Though spikes seemed to have been reducedthey still occur without relation to my activity level. I see spikes while I was in deep sleep. Some are unnatural levels that would trigger obvious physical reactions. I have a rower with a chest band, and it never reports jumps like the watch records; such as today a pulse of 208. I do note that many of the spikes are suspiciously close to a double of the rates the watch reports in the data points before or after the spike. Though my resting pulse is naturally slow, regularly in the 45-50 range, I also see occasional drops to 32-35, which seem like they would cause some reaction.
My magnetic watch band is usually snug enough the pressure lines are visible in my skin when the watch is taken off my wrist. I have used the watch both on top and under my wrist, and donor observe different spike behavior.
Battery life has been god, allowing charging on alternate days, and a charge in the time I’m changing and showering is enough to stretch another day if need be. So I have a lot of history at night. I do see some strings of elevated readings I assume relate to dreams, but those are usually in my normal activity range.
I am sure Apple is doing a lot of filtering and averaging of the light based measurements, but I agree with the preceding writers that the algorithm needs to reject solitary readings of these spikes. There are not related to loose watch movements or sudden impact movements of my arm when I’m lying in bed. I do wonder if Apple has properly studied differences in results for people with slight mourners or different average rates or ekg patterns.
Do anyone know if this forum is monitored by the watch engineers? Is there a way to determine if Apple recognizes the issue is more than users not snugging their watch band tightly?