Read the statement by Michael Teeuw here.
MMM-Strava stopped updating
-
@karsten13 Thanks … so I added “DEBUG” to this list, that should do it right?
logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"], // Add "DEBUG" for even more loggingDoesn’t seem to show much more than before though, just LOG and INFO as before … I’ll read up to see if there’s something else I need to do to trace that module in the meantime.
-
@levon said in MMM-Strava stopped updating:
so I added “DEBUG” to this list, that should do it right?
no… that is different… you will get a lot of calendar module debug
for normal modules
config: { debug: true, } -
@sdetweil Thanks for the info. I now get these additional informative messages, but it all looks right, though it doesn’t update the information.
10.08.2021 16:20.18.805] [LOG] MMM-Strava: "Getting data for module_8_MMM-Strava" [10.08.2021 16:20.18.819] [LOG] MMM-Strava: "Getting athlete activities for module_8_MMM-Strava after 2021-01-01" [10.08.2021 16:20.18.845] [INFO] Checking git for module: MMM-Pollen [10.08.2021 16:20.18.970] [INFO] Checking git for module: MMM-MoonPhase [10.08.2021 16:20.19.063] [INFO] Checking git for module: MMM-Strava [10.08.2021 16:20.19.644] [INFO] Checking git for module: MMM-Remote-Control [10.08.2021 16:20.20.433] [INFO] Newsfeed-Fetcher: Broadcasting 24 items. [10.08.2021 16:20.20.850] [INFO] Newsfeed-Fetcher: Broadcasting 15 items. [10.08.2021 16:20.21.204] [INFO] Newsfeed-Fetcher: Broadcasting 27 items. [10.08.2021 16:20.21.750] [INFO] Newsfeed-Fetcher: Broadcasting 9 items. [10.08.2021 16:20.22.632] [LOG] MMM-Strava: "Summarising athlete activities for module_8_MMM-Strava" [10.08.2021 16:20.22.925] [INFO] Newsfeed-Fetcher: Broadcasting 100 items. [10.08.2021 16:20.23.000] [INFO] Newsfeed-Fetcher: Broadcasting 52 items. [10.08.2021 16:25.20.708] [INFO] Newsfeed-Fetcher: Broadcasting 24 items. [10.08.2021 16:25.21.232] [INFO] Newsfeed-Fetcher: Broadcasting 15 items. [10.08.2021 16:25.22.021] [INFO] Newsfeed-Fetcher: Broadcasting 26 items. [10.08.2021 16:25.22.197] [INFO] Newsfeed-Fetcher: Broadcasting 9 items. [10.08.2021 16:25.23.983] [INFO] Newsfeed-Fetcher: Broadcasting 100 items. [10.08.2021 16:25.24.292] [INFO] Newsfeed-Fetcher: Broadcasting 52 items. [10.08.2021 16:30.18.841] [LOG] MMM-Strava: "Getting data for module_8_MMM-Strava" [10.08.2021 16:30.18.844] [LOG] MMM-Strava: "Getting athlete activities for module_8_MMM-Strava after 2021-01-01" [10.08.2021 16:30.20.841] [INFO] Newsfeed-Fetcher: Broadcasting 24 items. [10.08.2021 16:30.21.431] [INFO] Newsfeed-Fetcher: Broadcasting 15 items. [10.08.2021 16:30.21.558] [LOG] MMM-Strava: "Summarising athlete activities for module_8_MMM-Strava"For instance here’s the output of a Python program that uses the same API/credentials
[16:21 991] $ python strava_info.py Expired token .. Retriving information from year 2021 and onward. .Done. API requests/pages: 2 records read: 235 Saving to file "strava_activities_final.csv" Since 2021 ------------------------------------------------ # of runs : 136 total distance: 653.18 miles # of walks: 97 total distance: 232.63 miles # of other: 2 total distance: 3.62 miles ------------------------------------------------ Total # : 235 total distance: 889.44 miles [16:21 992] $The MM module has been stuck for a few weeks with these values
-
@levon Hi. Apologies for the late replies. Time difference. Can you check when last the tokens.js file was touched? That file is updated every time it does a call out to get data. Else I would suggest maybe just doing a git pull and npm install in the MMM-Strava folder. From the above replies I can’t see anything else that could be going wrong though.
-
@mumblebaj No apologies needed at all - I appreciate all the info/suggestions.
Looks like the file is up-to-date, though the file was last touched about 30 minutes ago, in the config file it says to be updated every 10 minutes, so perhaps that’s a bit odd?
pi@io:~/MagicMirror/modules/MMM-Strava $ ls -lrts total 256 24 -rw-r--r-- 1 pi pi 23415 Jun 3 07:09 README.md 16 -rw-r--r-- 1 pi pi 15048 Jun 3 07:09 node_helper.js 12 -rw-r--r-- 1 pi pi 12257 Jun 3 07:09 MMM-Strava.js 8 -rw-r--r-- 1 pi pi 6408 Jun 3 07:09 MMM-Strava.css 4 -rw-r--r-- 1 pi pi 1099 Jun 3 07:09 LICENSE 4 drwxr-xr-x 2 pi pi 4096 Jun 3 07:09 tests/ 4 drwxr-xr-x 2 pi pi 4096 Jun 3 07:09 templates/ 4 drwxr-xr-x 4 pi pi 4096 Jun 3 07:09 public/ 4 -rw-r--r-- 1 pi pi 1604 Jun 3 07:09 package.json 4 drwxr-xr-x 2 pi pi 4096 Jun 3 07:09 translations/ 4 drwxr-xr-x 57 pi pi 4096 Jun 3 07:10 node_modules/ 164 -rw-r--r-- 1 pi pi 166945 Jul 28 14:02 package-lock.json 4 -rw-r--r-- 1 pi pi 1034 Aug 11 15:40 tokens.json -
@mumblebaj Ok, so I did this:
pi@io:~/MagicMirror/modules/MMM-Strava $ git pull && npm install From https://github.com/ianperrin/MMM-Strava * [new branch] dependabot/npm_and_yarn/path-parse-1.0.7 -> origin/dependabot/npm_and_yarn/path-parse-1.0.7 Already up to date. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.3.2 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) added 380 packages from 277 contributors and audited 435 packages in 42s 75 packages are looking for funding run `npm fund` for details found 13 vulnerabilities (12 moderate, 1 high) run `npm audit fix` to fix them, or `npm audit` for details pi@io:~/MagicMirror/modules/MMM-Strava $I didn’t run any of the fixes, I looked at audit, but didn’t see anything that seemed related to Strava.
Should I be concerned that the package-lock.json time stamp is different from the other June 3 files when I initially installed this? In all other modules the file stamps have the same values.
The log seems to show this module working ok, trying to get data every 5 minutes (I made it shorter for testing) though the timestamp on the tokens.json file hasn’t changed from 15:40 today, now it’s over 2 hours since then.
pi@io:~/MagicMirror $ grep Strava nohup.out [11.08.2021 16:46.44.905] [LOG] Check MagicMirror version for node helper 'MMM-Strava' - Minimum version: 2.2.0 - Current version: 2.16.0 [11.08.2021 16:46.44.910] [LOG] Module helper loaded: MMM-Strava [11.08.2021 16:46.45.936] [LOG] Connecting socket for: MMM-Strava [11.08.2021 16:46.45.937] [LOG] Starting module helper: MMM-Strava [11.08.2021 16:46.54.215] [LOG] MMM-Strava: "Getting data for module_8_MMM-Strava" [11.08.2021 16:46.54.227] [LOG] MMM-Strava: "Getting athlete activities for module_8_MMM-Strava after 2021-01-01" [11.08.2021 16:46.54.961] [INFO] Checking git for module: MMM-Strava [11.08.2021 16:46.58.455] [LOG] MMM-Strava: "Summarising athlete activities for module_8_MMM-Strava" [11.08.2021 16:51.54.275] [LOG] MMM-Strava: "Getting data for module_8_MMM-Strava" [11.08.2021 16:51.54.279] [LOG] MMM-Strava: "Getting athlete activities for module_8_MMM-Strava after 2021-01-01" [11.08.2021 16:51.55.648] [LOG] MMM-Strava: "Summarising athlete activities for module_8_MMM-Strava"I think I’m going to try updating the Strava module again based on the instruction on their github page. If that doesn’t work, perhaps I’ll just try nuking that directory and reinstalling it from scratch.
I’m just puzzled it stopped working.
-
@levon npm install updates the package-lock.json file. ( its the record of what is installed under MM)
-
@levon I think check if it is successfully hitting the API on Strava. Check https://www.strava.com/settings/api.
Also check if the Authorization Callback Domain matches your MM IP.
-
@mumblebaj Yes, it is doing that for sure, I had kept an eye on that.
I think I finally tracked down the problem, however I don’t understand why it broke. The problem is with one of the options in the config.js file. I had used mode “chart” successfully since early June (ie for almost 2 months) as it also gave me stats on walks too, but for some reason the updates stopped happening with this mode (rather than the default “table” mode)
If I comment out the mode, or explicitly specify the default mode of “table”, I get the correct stats for runs, but it ignores the walk (as documented, it will only do run, swim, ride in “table” mode)
I think I will open an issue with this.
I appreciate all of your help/suggestions. Perhaps the code author can shed some light on this.
-
@levon Awesome. Glad you found the issue. The code uses the npm module strava-v3. It looks like the method used does not return walking.
