@Jalibu Looking good. Well done.

Very nice mirror. Well done

@pat59 I assume you have the module installed and you are just trying to update? If yes, do the following.

cd ~/MagicMirror/modules/MMM-Remote-Control 
git pull
npm install

The command you are running is to do a fresh install and not an update.

@Datfatboi You should only add the following to your config.js

{
module: “MMM-RottenTomatoes”,
position: “top_left”,
config: {
showHeader: “true”
showBoxOffice: “true”
showOpeningThisWeek: “true”
}
},

@ashishtank I use MMM-Networkscanner and control my screen via that. If it does not detect my device residents then it powers the monitor off and when the device is detected on the network then it powers the monitor on. That way when I go out it powers the monitor off automatically and powers it on when I am back home.

@Bugsounet said in Summary of my own modules and npm library:

I will code other in 2021, don’t worry it’s planned

Thanks Bugs. Will await your release.

@Bugsounet HI Bugs, do you have an ETA for the MMM-ModemRouter? I can’t wait for this one.

@Bugsounet Updated and it now works fine. Thanks @Bugsounet

@Bugsounet Thanks for the response. Will update and try again.

Hi @Bugsounet Thanks for the great module but I am having issues with installing the above module. I managed to install it fine on my Laptop running Ubuntu on Windows. When I tried to install it on my Raspberry Pi 3B+ I get an error. The error I get right at the end of the install is as follows:

8734 silly lifecycle MMM-SpeedTest@1.0.0~postinstall: Args: [ '-c',
8734 silly lifecycle   'echo \'Building SpeedTest module, please wait...\' && electron-rebuild 2>/dev/null >/dev/null' ]
8735 silly lifecycle MMM-SpeedTest@1.0.0~postinstall: Returned: code: 1  signal: null
8736 info lifecycle MMM-SpeedTest@1.0.0~postinstall: Failed to exec postinstall script
8737 verbose stack Error: MMM-SpeedTest@1.0.0 postinstall: `echo 'Building SpeedTest module, please wait...' && electron-rebuild 2>/dev/null >/dev/null`
8737 verbose stack Exit status 1
8737 verbose stack     at EventEmitter.<anonymous> (/home/pi/.npm-global/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
8737 verbose stack     at EventEmitter.emit (events.js:180:13)
8737 verbose stack     at ChildProcess.<anonymous> (/home/pi/.npm-global/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
8737 verbose stack     at ChildProcess.emit (events.js:180:13)
8737 verbose stack     at maybeClose (internal/child_process.js:936:16)
8737 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
8738 verbose pkgid MMM-SpeedTest@1.0.0
8739 verbose cwd /home/pi/MagicMirror/modules/MMM-SpeedTest
8740 verbose Linux 4.14.52-v7+
8741 verbose argv "/usr/bin/node" "/home/pi/.npm-global/bin/npm" "install"
8742 verbose node v9.11.2
8743 verbose npm  v6.14.8
8744 error code ELIFECYCLE
8745 error errno 1
8746 error MMM-SpeedTest@1.0.0 postinstall: `echo 'Building SpeedTest module, please wait...' && electron-rebuild 2>/dev/null >/dev/null`
8746 error Exit status 1
8747 error Failed at the MMM-SpeedTest@1.0.0 postinstall script.
8747 error This is probably not a problem with npm. There is likely additional logging output above.
8748 verbose exit [ 1, true ]

I tried uploading the full log but keep getting an error.

@sdetweil Still don’t like the response he made to you about not advising people to use your scripts.

@Zar You could just issue a pm2 delete mm and then pm2 save which will get rid of pm2 restarting the mirror. The feature helps with crashes and restarts the mirror automatically.
The scripts from @sdetweil is awesome and has helped 100’s on the forum.

@trix2k This is my config that works.

    {
            module: "MMM-COVID19",
            header: "COVID-19 Stats",
            position: "middle_center",
            config: {
                     updateInterval: 86400000,
                     worldStats: true,
                     orderCountriesByName: true,
                     orderAscending: true,
                     delta: true,
                     lastUpdateInfo: true,
                     countries: [ "South Africa", "USA", "UK", "India", "Brazil", "France", "Spain", "Russia", "Argentina" ],
                     headerRowClass: "small",
                     infoRowClass: "small",
                     highlightCountry: "South Africa",
                     rapidapiKey: "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
                    }
    },

@ankonaskiff17 The

--depth=1

means the following. Git shallow clone lets you pull down just the latest commits, not the entire repo history. So if your project has years of history, or history from thousands of commits, you can select a particular depth to pull.

@sdetweil Yeah, doesn’t seem to play well with pages. The minute you remove paged the module works fine.

@buzzkc I see the developer took down the API?

@sdetweil I have had a look and I see the following:

Will not show MMM-Traffic. LockStrings active: module_7_MMM-pages

I assume this is why the MMM-Traffic is not showing when used in MMM-Pages? I have added the modules on my test machine and I can’t get the module to show either. I see that the above error comes from the main.js of MM. maybe you can shed more light on the issue for @kusselin

@kusselin You are rotating the pages every 60 seconds? Correct? From what I understand, ever time the pages rotate a call is done to get data which would be true in the case of mmm-traffic. It could be that by the time the module get it’s data that the rotation has happened and then it does not display? I may be wrong. I don’t use the module myself.

@kusselin Have you tried running the module without the extra config? animationTime has default value of 0, disabled you probably don’t need to set and the rotationTime you probably don’t need to set for now.

@kusselin This is an example of mine.

Modules are either on Page1 or Page 2 and then I have modules (fixed) that display on all pages.