Strava Integration: Bad Weather Data
-
My data flow is to run with a Garmin -> Auto-upload to Strava -> Auto-import Strava to Day One.
However, today I noticed that Day One is pulling in the temp field from my Garmin, which is *very* heavily influenced by my skin and body heat! Today when I ran it was 67°F, but my Garmin (and therefore Day One), pulled in the temp as 81°F. I was able to tap on the entry and use the “Update Weather” command, but it would be nice to have this improved at the import step.
Strava’s own website shows accurate weather conditions, but I’m not sure what data Strava passes down via whatever private API integration Day One might be calling.So, I think we either need to have Day One itself poll for accurate weather data for the date and location of the activity, OR see if Strava can make that data available via its API.
-
What you’re seeing lines up with how the Strava import handles temperature specifically: for entries that come in through Strava, Day One normally pulls weather for the entry’s location and time, but the temperature value itself is taken from the activity data Strava provides rather than that outdoor lookup. For activities like hiking, that number can reflect what your watch is reading, skin and body heat included, rather than the true air temperature, which is likely why you saw 81°F when it was actually 67°F.
The workaround you found, tapping the entry and using Update Weather, is the right one: it replaces that value with Day One’s own location and time based weather. One thing to note is that if the entry ever gets re-synced from Strava, the temperature will revert to the activity-sourced value, so you’d need to run Update Weather again after a resync.
Your suggestion, having Day One pull accurate weather directly at import instead of relying on Strava’s activity data, is something the team is already aware of. We don’t have a timeline to share, but I’ll make sure this report is included in that request.
-
Cool, thanks! Garmin should label that data as “wrist_temp” or something, it’s confusing to everyone who uses their API. Intervals.icu also interprets that field as “temperature,” so everyone is doing it. Might make sense for a bike-mounted device but certainly not a wrist one!
-
I filed this as a bug report in January, along with the reason that it was happening. There has been plenty of time for it to be fixed if it was deemed important enough to fix.
For me, the workaround was to disable temperature recording in the individual activity types. Without the temperature in the GPX file, the weather is always fetched by Day One. This workaround isn’t for everyone, but I personally don’t find much value in recording the wrist temperature during an activity.
All that said, I think the auto-importing of Strava activities has been a great addition to Day One. I can live with some quirks.
-
Can I ask how you disabled temperature recording? Is that just in the Garmin Connect app or on the watch somewhere?
-
-
Thanks for circling back, and glad the Garmin setting turned up.
This issue is still open and this thread has been added to it, including the reason you both identified, that the activity temperature is a device reading rather than an air temperature.
We can’t offer a timeline, and it’s fair to say it hasn’t been picked up yet. If others hit the same thing, feel free to leave a comment here.
