Sense logged 9989 steps between 3:45 am and 4:00am , I am told it was the wind, or heat?

[Pillywiggen]

Im 72. my sense showed 9989 steps between 3:45 am ridiculous dataand 4:00am. 

I called fitbit, i pay for premium. My sense is in pristine condition as a senior who has been under a rock for the pandemic. I wear the fitbit to bed. I was told by the service rep it was probably the wind or the heat or air condition. All absurd. My 75 y o friend had a middle of the night HR spike, followed it through an was found to have Afib. We depend of reliable data at our age.   So FYI the wind will give you an extra 9989 steps in 15 minutes per support staff. Absurd.

[Kris98]

Mine has done this twice now...

Messes up all my activity and averages, no way to just delete the hour or anything...

[eezeepee]

@Pillywiggen @Kris98 Does this happen regular like a few times a week?

These are my steps from yesterday and today so far:

In just over 8 weeks of use, I have yet to experience a huge step count spike like that overnight. The most I've gotten is still less than 50 steps total while sleeping which is negligible for me.

It's not great that you can't delete those steps but I would restart your Sense to see if they clears things up.

[Kris98]

2x this past month, absolutely destroys my average and goals

[eezeepee]

@Pillywiggen @Kris98 It's not ideal but this other thread appears to have a workaround so that the steps get deleted or not counted.

https://community.fitbit.com/t5/Fitbit-com-Dashboard/How-to-Delete-Steps/td-p/1511807 

[Pillywiggen]

I am not as worried about wrong step count  as much as I am concerned I will miss data indicative of a health problem due to some "glitch" caused by  the "wind" while I am sleeping. That answer was so ridiculous yet disturbing.  

[Pillywiggen]

This happened 1x to me. I am not worried about the steps as much as health data. I am disturbed fitbit staff say the wind did it. The health data, H R while sleeping,  is what cued my husband to a problem. He was aymptomatic for a heart problem and had surgery only weeks after the fitbit  HR data in the middle of the night showed something wrong.   If he called, rather than take HR data at face value, and they told him it was the wind...... see what I am talking about ?

[eezeepee]

@Pillywiggen Okay but the steps and heart rate are two different sensors. Are you having any issues with the heart rate monitoring?

[Rich_Laue]

Most have been some marathon you where dreaming about. 

[Pillywiggen]

Yes different sensors.

The sensor in posting about, 9989 steps between 345 am and 4 am
Was explained as caused by wind. I was in a windless bedroom.
Are you saying the explanation of wildly inaccurate step data being caused
by wind is acceptable? Do you think this wild malfunction of a pricey
wearble, absurd explanation inspires confidence in the product?

Accepting its just the wind causing 9989 steps while sleeping in 15 min
period is a bit like ignoring the smoke alarm because it was just the wind
last time.

Mass General hospital is doing a study on fitbit wearables for health. They
are giving credibilty to the device as a way to monitor health. I expect
minor imperfections but wild numbers with absurd company response damaged
my confidence .

[eezeepee]

@Pillywiggen It's not acceptable but it's also not a huge widespread issue. Problems with syncing, connections, or even heart rate monitoring during activities is more common than random thousands of steps from what I've seen here in the Fitbit community or Google searching. My wife was a Fitbit user for several years her Alta, Versa, and Sense never had an issue with thousands of steps over night. And she would definitely let me know if she had that.

[primortal]

Do you have MobileTrack enabled?  If so, disable it.  I had a similar issue with MobileTrack enabled where it said I took "12k" steps in as little as 15 minutes while sleeping, then a month or so later it did the same thing while the Sense was charging, recorded "8k" steps.  Since disabling it, I haven't had those phantom steps anymore.

[eezeepee]

@primortal Good recommendation. Hopefully that's the fix.