Subcategories

• Showcase

  Present your module and help other users on how to use it.

  • Utilities
  • System
  • Transport
  • Productivity
  • Education
  • Health
  • Entertainment
  • Fun & Games
  • Sport
  1k Topics

  26k Posts

  S

  @videogame95 ok, I led you on the wrong path. did you translate the module github page into your preferred language? it has all the instructions install the module launch the web page Access it by going to https://onsp.fabriz.co/ create the app on the spotify developers site add the redirect URL Now add https://onsp.fabriz.co/ as the redirect URI (include the trailing /), so Spotify knows to redirect you here with the credentials scroll down and press save click on Save add you as a user Once you added yourself as a user, go back to the Basic Information tab, see/copy the clientid and client secret values into the fields on the web page [image: 1773809144039-snip20260317_2.png] press authorize with your Spotify account [image: 1773809463141-snip20260317_3.png] on return from authorize it will display the sample module definition for config.js (clipped here so you can see it) [image: 1773809557464-snip20260317_4.png] copy that blob to your config.js save and restart MagicMirror
• Requests

  Need a module? Maybe someone is interested in coding it.
  1k Topics

  7k Posts

  K

  @Divis Thanks! 😃 There was some feedback with ideas in the repo. So not alone my achievement.
• Development

  Need help developing a module? You just found it!
  687 Topics

  5k Posts

  R

  @KristjanESPERANTO said: Why are you using an very old version of axios instead of build-in fetch? You have given me food for thought. There’s no good reason. Axios 1.6.0 is not ancient, but it’s still an unnecessary dependency for what this client does. Many TypeScript libraries were originally written for Node 14/16 environments, so Axios became the default. The repo requires node >= 18, and Node 18 ships with the native fetch API built in. Every single method in client.ts is a simple GET or POST with JSON , exactly what fetch handles natively without any extra package. The only real reason to reach for axios in a Node 18+ project today is if you need interceptors for complex auth flows, automatic retry logic, or upload progress events . Axios was chosen for convenience and historical compatibility. However, for a modern Node.js TypeScript MCP server, native fetch is cleaner and preferable. For this project switching to native fetch seems logical. Axios adds more value in complex APIs, but here the benefit is minimal. So i guess, i need to strip it . Thanks, I will try and update ASAP.
• Troubleshooting

  You have a problem with a module? Ask for help.
  3k Topics

  20k Posts

  B

  Getting the orientation right for the training images was the trickiest part for me. If your PiCam or USB cam is mounted at an odd angle (or upside down for cable management), the recognition often fails because the training set doesn’t match the live feed. If anyone is struggling with mirrored images in their preview or while testing their training data, I found this quick tool helpful to flip them before feeding them into the trainer- https://www.thetoolapp.com/mirror-image-online/. It’s a lot faster than script-flipping every individual JPEG when you’re just trying to troubleshoot the dataset.