MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. KristjanESPERANTO
    3. Best
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    Offline
    • Profile
    • Following 6
    • Followers 2
    • Topics 14
    • Posts 308
    • Groups 1

    Posts

    Recent Best Controversial
    • RE: MMM-euro2024

      @0m4r Nice! Thanks! 👏
      Don’t forget to add it to the module list 🙂

      posted in Sport
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: Having issues with MMM-MktIndex, again

      @leonids The module got an update some days ago. Have you updated the module?

      posted in Troubleshooting
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: MMM-GoogleMapsTraffic error removal

      @chrisfr1976 Great. I have just adjusted the list in the wiki accordingly :-)

      posted in Transport
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: MMM-MagicReplicator

      Nice. Don’t forget to add it to the modules list: https://github.com/MichMich/MagicMirror/wiki/3rd-party-modules :smiley:

      posted in Productivity
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: Starting MM Crontab

      @mumblebaj Just an idea: Maybe the node version used in Cron could be to old. When you run a script manually in your terminal, your full user environment (including things like .bashrc or .zshrc) is loaded. Cron runs in a much more minimal environment — it often doesn’t load your shell config files, so tools like nvm (Node Version Manager) might not be available.

      How to fix it:

      • Use the full path to Node: Find it with which node and use that path in your cron job.
      • Set the environment manually in cron: You can define your PATH at the top of the cron file.
      • Source nvm in your script: If you use nvm, add source ~/.nvm/nvm.sh and nvm use <version> before calling node.
      posted in Bug Hunt
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: MMM-OpenWeatherForecast - loading issue

      Side note: If you are having problems with MMM-OpenWeatherForecast, make sure you are using Tom Hirschberger’s active fork. You can check this by running git remote -v in the module’s directory.

      posted in Troubleshooting
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: Raspberry Pi 5 out with PCI Express

      Nice! I think the real-time clock is a useful new feature for the MM. With that we should be able to wake up the Raspberry Pi automatically without any external device.

      posted in Hardware
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: display issue MMM-PublicTransportHafas

      That is interesting. Apparently, the transport company defined the station ‘Am Zwingerteich, Dresden’ as a related station of ‘Postplatz, Dresden’. Please try stationID: "975242" - this is another ID for ‘Postplatz, Dresden’, which is not related to ‘Am Zwingerteich, Dresden’.

      posted in Troubleshooting
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: This my first MagicMirror aka Dashboard

      Nice! :thumbs_up:

      posted in Show your Mirror
      KristjanESPERANTOK
      KristjanESPERANTO
    • RE: Cannot find module 'node-fetch' error with multiple MM modules

      @myayo001 Just remove the the line const fetch = require("fetch"); in the file node-helper.js in the module’s directory.

      posted in Troubleshooting
      KristjanESPERANTOK
      KristjanESPERANTO
    • 1 / 1