Hi... I have exactly the same experience. The one thing I'd add is that the watch 3 seems to stop being able to do accurate BPM monitoring when being "slightly active with BPM approaching or just exceeding 100". I noticed that my Watch 3 will in these circumstances be unable to provide BPM NOW but reports the BPM of 'x' minutes ago. It takes a few minutes when stopping the exercise for the BPM function to again start providing the BPM NOW.
Fairly useless for BPM under many exercise conditions therefore.
For information, I have also posted about issues I have noticed with: Sleep data failing to sync to the mobile phone S Health app (fails frequently and app needs to be reset), and "hard to achieve", "irratic" and "unlikely" blood oxygen levels.
It's very good at telling the time though.
Similar on the deep sleep time to you. Mine is usually just a few minutes. 5 minutes last night for example, and none the night before. Overall sleep scores are usually 30. I had one night when deep sleep was recorded as 1Hr 10min and overall sleep score was 55. Screen image attached (I hope). Looking at it now though, the timings are rather unlikely as total of awake + REM + Light + Deep is 2Hr 16m + 2Hr 26m + 11Hr 18 + 1Hr 10 = 17 Hr 10m which apparantly was achieved between 22:41 on Thursday and 07:16 on Friday.... just 8hr 35 minutes. 😅
I now have my doubts on the accuracy of the sleep recording too... thanks for pointing that one out! Perhaps I won't bother with restting teh app next time the sync fails. It seems hardly worth the effort for results like this.
Do let me know if I am misreading the report I have taken a screen shot of (thanks).
I have noticed that the total for the sleep are exactly double the total. 17Hr 10m = 2 x 8hr 35, and so maybe a bug caused it to record it twice. No way to correct this of course🤔
I had a similar moment of inspiration recently and I decided to place it into "walking" mode. Like you, I noticed that the pulse rate was more reliably tracked and it captured instances above 100.
Strange that the auto detected "walking" and the manually instated "walking" should have different bpm capability(?).
We'll have to see if we can work out "why"?