Strava Applet Not Displaying Correctly in App Preview or Tidbyt Display about community HOT 5 CLOSED

Great suggestion! I can certainly calculate the average speed from the distance and moving time provided (mi or km per hour).

May be some time before the change is able to be released given the current backlog but I will find time to implement this and submit for review. Thanks again for the feedback - let me know if you have other ideas!

from community.

Hey @OrianTheHunter, developer of the Strava applet here - thanks for the report.

Mine had been working earlier today presumably using cached data, but I just removed and re-added my own screens and had the same experience as you - black screen, skipped in the rotation. The demo data flashes briefly once I log in but as soon as it tries to grab my data it seems to crash.

I don't have the official API secrets but tried using my own ID/key locally and was able to pull data in again:

I suspect this means we've hit the rate limits - the default setting is 100 requests per 15 minutes and capped at 1,000 requests per day - it's very possible that the community has hit the level of installs that breaches these limits. I was able to reproduce the error locally by disabling the cache and refreshing until I hit the limit using my own API keys. If this is also what's causing the issue on device, the app should begin working again tomorrow and Tidbyt will need to reach out to Strava to resolve - I'm sure apps like VeloViewer have much higher limits than what's available by default!

In the interim, I'll be submitting a PR to replace the fail statements in the code with an error message so users aren't left in the dark when this type of thing happens You would see a screen like this instead:

Sorry for the interruption, hope we'll get everyone back online shortly!

from community.

Hi @rgkimball,

Thanks for the quick response and thanks for making the Strava applet! It's great motivation to see right before I start biking after work. I am not sure if it is a long term solution because of the rate limit as you described but it does appear to be working for me this morning (I just don't know how long that will continue to be the case).

I think this fix should be enough to close this issue, but while I have you I wanted to also provide two other issues/feature suggestions:

1. The number of rides/miles seems to be off by one between what the Strava app is reporting and what the Tidbyt display is showing (The Tidbyt has one less ride than the actual from Strava).
   
   

2. Would it be possible to include a toggle to hide the elevation field? I do not believe exercise bikes/programs such as Peloton/iFit/etc. report elevation to Strava, so it simply shows as a zero.

from community.

Thanks so much for the feedback, and really glad to hear that it's a helpful motivational tool!

On point 1, the all-time and YTD stats are displayed directly from the athlete stats endpoint, so my guess is the discrepancy here is that you have cached data, or that there is some lag between the website and the API. I could theoretically calculate these from activities, but this would require a lot more data and we appear to already be at the top end of our usage!

Regarding your second suggestion, I have to admit I didn't even think about exercise bikes but that is completely valid. I am a bit cautious of adding too many settings, but I could see auto-hiding the elevation if you have a positive ride/distance value but zero elevation gain - the issue here is if people are doing a mix of road/stationary cycling. For runners/swimmers I display the average mile/split time instead, is there a good stat you can think of that could replace elevation gain? Or should I just display two lines if elevation == 0?

Glad to hear you liked the applet. :)

from community.

I don't know if you can access it for a filtered period of time (such as All-Time stats or YTD Stats) but individual rides do have a Avg Speed value (in mi/h). If the API can easily show an Avg Speed for multiple ride sessions over different time periods (All-Time/YTD/etc) I think that would be the best to replace elevation with just because it would be applicable to the widest number of scenarios/users. If not just hiding the elevation line if it == 0 would also be a straightforward visual improvement .

from community.