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

    norm

    @norm

    0
    Reputation
    47
    Profile views
    5
    Posts
    0
    Followers
    0
    Following
    Joined
    Last Online

    norm Unfollow Follow

    Latest posts made by norm

    • MMM-TFL-ARRIVALS

      Does anybody else experience the data displayed by this module freezing after about 2 days running time?

      Norm

      posted in Troubleshooting
      N
      norm
    • Transport for London - domain change and widget decommissioning - INFORMATION

      I have just received an email from the TfL Open Data and am sharing it for every bodies information, etc:

      ===========================================================================

      As a registered user on our Open Data portal, there is a possibility you may be using some of our open data resources that we will need to change.

      Important: if you are using the TfL Open Data feeds mentioned below, you will need to make updates to apps using these:

      1. Legacy Trackernet and ESUI feeds - re-platforming (hosted on cloud.tfl.gov.uk)
        An ‘ALERT’ post on our Tech Forum containing full details about this change/timescales, is available here.

      2. Tube Status Widget - to be decommissioned on Thursday 4 July 2024
        An ‘ALERT’ post on our Tech Forum containing full details about this change/alternative options, is available here.

      If you have any questions or comments about either of these TfL Open Data changes, please add a comment to a relevant Tech Forum post and we will try to help.

      Yours sincerely,

      TfL Open Data Team

      ============================================================================
      Hopefully the form links have copied through ok.

      Best regards
      N

      posted in Troubleshooting
      N
      norm
    • RE: Black Screen on Startup

      @sdetweil

      Yes and no:
      Yes - it did not give any error message.
      No - it did not install the folder and file.

      To recap:
      I did a new install using the bash auto install script, but for whatever reason the node_helper sub-folder and index.js file were not installed.
      Running the git checkout command similarly did not install the sub-folder and file (as the sub-folder and file were not originally installed, it seems logical to me that the git checkout command would not ‘reinstall’ them).
      Installed the missing sub-folder and file manually.
      Re-started with “pm2 restart mm”.

      I guess the pertinent question is why the original install exercise did not include the node_helper sub-folder and index.js file???

      posted in Troubleshooting
      N
      norm
    • RE: Black Screen on Startup

      @sdetweil

      I am not very familiar with the various git commands beyond ‘clone’, but as @jasaronii said above, that git checkout command did nothing, hence manual approach.

      But thanks for the guess - inspired and very helpful.

      N.

      posted in Troubleshooting
      N
      norm
    • RE: Black Screen on Startup

      @Jasaronii

      I had a similar issue following a reinstall on a Pi 3B, where known good module configurations simply gave a black screen (though the sample config file did initially work but then gave the same black screen after other modules were installed).

      I was also missing ‘node_helper’ folder and ‘index.js’ file as you describe.

      Manually installed the ‘node_helper’ folder and copied in the ‘index.js’ file (from the github page https://github.com/MichMich/MagicMirror/blob/master/modules/node_modules/node_helper/index.js).

      Restarted and now all good. :-)

      posted in Troubleshooting
      N
      norm