Skin Temperature - two different data sets

[appetite4]

My Sense is doing the skin temperature. In the Android app this gets presented in two places - a dedicated skin temperature tile and a graph in the Health Metrics tile. The data in these two locations is totally different with reported values for the same day differing by as much as 1.1c.

Are these somehow subtly different skin temperature metrics? If so the descriptions need reviewing because I can't see what the difference is. OR is there some other systemic problem?

I think I have ruled out them simply using different baselines for my skin temp because the differences in reading vary so wildly. Over the last seven days they have disagreed by 1.1, 0.7, 0, 0.6, 0.1, 0.4 and 0 degrees c.

It seems the Skin Temp tile is usually lower. The only time they agree is when the variance from baseline temp overnight is itself zero. 

Can anyone help explain what is happening here?

Thanks - Paul

[Guy_]

Try this to see if it resolves the issue, [my graphs are the same]

In Android phone Settings *

Apps

Fitbit

Storage - clear cache [not data]

Force Fitbit shutdown

[though it doesn't seem to fully]

Log back in to the Fitbit app

*Quick Shortcut: Press and hold the Fitbit launch icon, then App info [on some phones]

[appetite4]

Thanks but it didn't seem to clear it for me. I'm going to repost because I don't know how the "answered" status came up (probably my fat fingers) and I noted is got my two sets of data misaligned. Still different but do agree when the reported value is zero variance from baseline. 

[Guy_]

You can click to unanswer I believe.

Did you also try logout and clear the cache again?

[appetite4]

I've cleared cache (not main storage), logged out of the app, cleared the cache again, force stopped the app, rebooted the phone and logged back in but the data is still the same. I'll keep watching it over coming days to see if it lines up from here on in. Thanks for your help Guy. 

[Guy_]

Thanks for the troubleshooting and feedback. As you say it might correct itself in the days that come.

Interesting if it is a bug, as its not been noted before.