o.k., so your question was about using a newer node version than 10? Maybe the latest lts version, I’m not sure, think this is 12.

thats your decision, this problem seems unrelated to the node/npm version, but so old stuff can cause other problems, so may you should warn at least …

yes, saw that, but my tests were run with

node@pi4:/opt/magic_mirror$ node -v
v13.5.0
node@pi4:/opt/magic_mirror$ npm -v
6.13.4

thx, so you are on the develop branch with electron 6.x

may you can give us more infos about your setup.

Please navigate to your magic mirror dir (/home/pi/MagicMirror) and post the result of

• cat package.json
• git status
• node -v
• npm -v

node@pi4:/opt/magic_mirror$ cat package.json
{
  "name": "magicmirror",
  "version": "2.10.0",
  "description": "The open source modular smart mirror platform.",
  "main": "js/electron.js",
  "scripts": {
    "start": "./run-start.sh",
    "install": "cd vendor && npm install",
    "install-fonts": "cd fonts && npm install",
    "postinstall": "sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts",
    "test": "NODE_ENV=test ./node_modules/mocha/bin/mocha tests --recursive",
    "test:unit": "NODE_ENV=test ./node_modules/mocha/bin/mocha tests/unit --recursive",
    "test:e2e": "NODE_ENV=test ./node_modules/mocha/bin/mocha tests/e2e --recursive",
    "config:check": "node tests/configs/check_config.js",
    "lint": "grunt"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/MichMich/MagicMirror.git"
  },
  "keywords": [
    "magic mirror",
    "smart mirror",
    "mirror UI",
    "modular"
  ],
  "author": "Michael Teeuw",
  "contributors": [
    "https://github.com/MichMich/MagicMirror/graphs/contributors"
  ],
  "license": "MIT",
  "bugs": {
    "url": "https://github.com/MichMich/MagicMirror/issues"
  },
  "homepage": "https://magicmirror.builders",
  "devDependencies": {
    "chai": "^4.1.2",
    "chai-as-promised": "^7.1.1",
    "current-week-number": "^1.0.7",
    "danger": "^3.1.3",
    "grunt": "latest",
    "grunt-eslint": "latest",
    "grunt-jsonlint": "latest",
    "grunt-markdownlint": "latest",
    "grunt-stylelint": "latest",
    "grunt-yamllint": "latest",
    "http-auth": "^3.2.3",
    "jsdom": "^11.6.2",
    "jshint": "^2.10.2",
    "mocha": "^7.0.0",
    "mocha-each": "^1.1.0",
    "mocha-logger": "^1.0.6",
    "spectron": "^8.0.0",
    "stylelint": "latest",
    "stylelint-config-standard": "latest",
    "time-grunt": "latest"
  },
  "optionalDependencies": {
    "electron": "6.0.12"
  },
  "dependencies": {
    "colors": "^1.1.2",
    "console-stamp": "^0.2.9",
    "express": "^4.16.2",
    "express-ipfilter": "^1.0.1",
    "feedme": "latest",
    "helmet": "^3.21.2",
    "iconv-lite": "latest",
    "lodash": "^4.17.15",
    "module-alias": "^2.2.2",
    "moment": "latest",
    "request": "^2.88.0",
    "rrule": "^2.6.2",
    "rrule-alt": "^2.2.8",
    "simple-git": "^1.85.0",
    "socket.io": "^2.1.1",
    "valid-url": "latest"
  },
  "_moduleAliases": {
    "node_helper": "js/node_helper.js"
  }
}

node@pi4:/opt/magic_mirror$ npm install
npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
npm WARN deprecated @types/vfile-message@2.0.0: This is a stub types definition. vfile-message provides its own type definitions, so you do not need this installed.

> electron-chromedriver@6.0.0 install /opt/magic_mirror/node_modules/electron-chromedriver
> node ./download-chromedriver.js


> core-js@2.6.11 postinstall /opt/magic_mirror/node_modules/core-js
> node -e "try{require('./postinstall')}catch(e){}"


> console-stamp@0.2.9 postinstall /opt/magic_mirror/node_modules/console-stamp
> node ./msg.js

Attention
    Console-stamp version 3.0.0 Release Candidate is out. Install by using the tag '@next'. NB: Breaking changes.
    For more details goto: https://www.npmjs.com/package/console-stamp/v/next


> electron@6.0.12 postinstall /opt/magic_mirror/node_modules/electron
> node install.js

Downloading tmp-433-1-SHASUMS256.txt-6.0.12
[============================================>] 100.0% of 5.2 kB (5.2 kB/s)

> magicmirror@2.10.0 install /opt/magic_mirror
> cd vendor && npm install

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

audited 220 packages in 4.267s
found 5 vulnerabilities (4 low, 1 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> magicmirror@2.10.0 postinstall /opt/magic_mirror
> sh untrack-css.sh && sh installers/postinstall/postinstall.sh && npm run install-fonts

MagicMirror installation successful!

> magicmirror@2.10.0 install-fonts /opt/magic_mirror
> cd fonts && npm install

audited 1 package in 0.716s
found 0 vulnerabilities

npm WARN grunt-stylelint@0.13.0 requires a peer of stylelint@^12.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

added 1056 packages from 1151 contributors and audited 2946 packages in 119.117s

52 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

node@pi4:/opt/magic_mirror$ npm start

> magicmirror@2.10.0 start /opt/magic_mirror
> ./run-start.sh

[516:0131/000550.394975:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/magic_mirror/node_modules/electron/dist/chrome-sandbox is owned by root and has mode 4755.

you tested on a raspberry pi? And with a non-root user?

tested only 3.x, 6.x, 7.x
In 3.x sandbox was disabled, in >=6.x enabled

The “newer” electron versions are using sandboxing by default. But on master-branch is still the old electron 3.x active.

So are you using the develop-branch or have you edited package.json und upgraded electron?

The method to fix this is correct, an alternative way is disable sandboxing, which is not a good idea under security aspects. You can disable sandboxing e.g. by setting the environment variable ELECTRON_DISABLE_SANDBOX=1

The git pull command fails if files are locally changed, because the pull would override them.
With git diff you can see what has changed.

If you are not interested to save these local changes you can run git reset --hard. This will revert all changes and after this the git pull should work.

@rudibarani

@baschke, @karsten13, @Hein-Jan

@j-e-f-f has updated the module on GitHub. Go to the module folder and update it via git pull.

If the error still persists, leave out line

    concise: false,

from the config file. That solved it for me in the prior version.

Had already the newest version, but leaving out concise: false did the trick. Thanks!

Same here with “Loading” and nothing happens.

Seems to be a problem with lon/lat.

If i provide the example lon/lat it works.

your setup works for me, changed only strava_id’s and access_token’s.
Did you put every single strava_id and every single access_token in single quotes as provided in my example? In your post you put 2 things in one single quote …
Other possibilities: Wrong strava data (id/token)? Did you read the documentation how to get strava_id?
Did you take a look in the logs?
If I test it with your testdata xxx I find these lines in the logs:

Error performing request: Unauthorized. Access Token will be reset.
Error while fetching new athlete stats.

try it with the missing brackets:

		{
			module: 'MMM-Strava',
			position: 'top_left',
			config: {
				strava_id: ['xxx1', 'xxx2'],
				access_token: ['xxx1', 'xxx2'],
				activities: ['run'],
				athlete_text: ['Tine', 'Basti'],
			    auto_rotate: 'true'
				 }
		},

Hi,

sounds you took the client id from the strava api page as input for strava_id of the module?

Input of strava_id: https://support.strava.com/hc/en-us/articles/216928797-Where-do-i-find-my-Strava-ID-

Karsten.

The docker setup is outsourced to https://github.com/bastilimbach/docker-MagicMirror and I already posted an issue for the black screen problem there: https://github.com/bastilimbach/docker-MagicMirror/issues/2

replacing “npm install” with “npm install --unsafe-perm” solved my blackscreen problem.

Update: I found no valid mm container in the docker store.

You can build your own docker image locally with

docker build -t magic_mirror .

and run it with

docker run  -d --publish 8080:8080 --restart always --volume ~/magic_mirror/config:/opt/magic_mirror/config --volume ~/magic_mirror/modules:/opt/magic_mirror/modules --name magic_mirror magic_mirror

and open it in your browser with

http://localhost:8080/

Be aware of this issue.

Karsten.

Hi,
trying to work with docker after the release of MM v.2.1.1.

The documentation says to start docker with:

docker run  -d \
			--publish 80:8080 \
			--restart always \
			--volume ~/magic_mirror/config:/opt/magic_mirror/config \
			--volume ~/magic_mirror/modules:/opt/magic_mirror/modules \
			--name magic_mirror \
			MichMich/MagicMirror

That doesn’t work, so google helped and this is working:

docker run  -d \
			--publish 80:8080 \
			--restart always \
			--volume ~/magic_mirror/config:/opt/magic_mirror/config \
			--volume ~/magic_mirror/modules:/opt/magic_mirror/modules \
			--name magic_mirror \
			randyramsaywack/magicmirror

Now docker ps tells me that all is running but i can’t see the site in my browser.
I tried localhost:8080 and localhost:8183, doesn’t work.

The documentation says to update the config with the Docker Host IP address.
So I tried to get this with

# As of Docker v1.3 you can attach to a bash shell
docker exec -it  2e23d01384ac  bash
# That drops you into a bash shell then use the 'ip' command to grab the addr
root@2e23d01384ac:/# ip add | grep global
    inet 172.17.0.1/16 scope global eth0

but inserting this in whitelist still doesn’t work.

May someone here knows what I’m doing wrong …

Thanks,

Karsten.