Posts made by BerkSmash1984

@mumblebaj Thanks for the response.

• yes npm install was run the MMM-Strave folder
• yes I did the browser auth on the RPI as well
• no, I do not see a tokens file in the MMM-Strava folder after attempting the authorization:
  

@mumblebaj Any ideas here? Would really like to get this functional. Appreciate any help!

@mumblebaj Yes, I did:

@sdetweil changed it

No luck though. I see lots of errors with Dev tools from PiHole module if I change from 0.0.0.0 to the IP of the RPI4

@BerkSmash1984 Opening developer tools shows the following at this point in the authorization:

Note: I have my pihole disabled while testing, as it is also on this RPI

Hello, I am getting client id not authorized, despite having my client ID and client secret correct (from Strava API page). I also have the whitelist setup correctly and can access my MM from my local browser (the MM itself is on a RPI4). I receive the link within the magic mirror and am redirected to the authorization page on Strava, but after clicking authorize and restarting MM, I am still getting the same client ID not authorized. In looking in electron, I do so a ERR_HTTP_HEADERS_SENT error message…

Any help would be greatly appreciated. Screenshots below:

@MaXi-XCeL Hello, I am getting client id not authorized, despite having my client ID and client secret correct (from Strava API page). I also have the whitelist setup correctly and can access my MM from my local browser (the MM itself is on a RPI4). I receive the link within the magic mirror and am redirected to the authorization page on Strava, but after clicking authorize and restarting MM, I am still getting the same client ID not authorized. Any help would be greatly appreciated. Thanks!