cd into ~/magicmirror/run folder and execute docker-compose up -d --force-recreate.

@ofb its probably the port number. change the port in config.js to 8090

I get a blank screen and says it cant reach a site. So I thought I would just restart the MagicMirror and all would be good. When I run the command npm start I get the following error. /home/mark/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory npm ERR! file sh npm ERR! code ELIFECYCLE npm ERR! errno ENOENT npm ERR! syscall spawn npm ERR! magicmirror@2.7.1 start: sh run-start.sh npm ERR! spawn ENOENT npm ERR! npm ERR! Failed at the magicmirror@2.7.1 start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. After looking I did an npm audit and npm audit fix. still the same issue. Any suggestions to fix this. Here is the full log 0 info it worked if it ends with ok 1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ] 2 info using npm@6.9.0 3 info using node@v10.15.3 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ] 5 info lifecycle magicmirror@2.7.1~prestart: magicmirror@2.7.1 6 info lifecycle magicmirror@2.7.1~start: magicmirror@2.7.1 7 verbose lifecycle magicmirror@2.7.1~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.7.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/mark/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin 9 verbose lifecycle magicmirror@2.7.1~start: CWD: /home/mark/MagicMirror 10 silly lifecycle magicmirror@2.7.1~start: Args: [ ‘-c’, ‘sh run-start.sh’ ] 11 info lifecycle magicmirror@2.7.1~start: Failed to exec start script 12 verbose stack Error: magicmirror@2.7.1 start: sh run-start.sh 12 verbose stack spawn ENOENT 12 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 12 verbose stack at ChildProcess.emit (events.js:189:13) 12 verbose stack at maybeClose (internal/child_process.js:970:16) 12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 13 verbose pkgid magicmirror@2.7.1 14 verbose cwd /home/mark/MagicMirror 15 verbose Linux 4.15.0-129-generic 16 verbose argv “/usr/bin/node” “/usr/bin/npm” “start” 17 verbose node v10.15.3 18 verbose npm v6.9.0 19 error file sh 20 error code ELIFECYCLE 21 error errno ENOENT 22 error syscall spawn 23 error magicmirror@2.7.1 start: sh run-start.sh 23 error spawn ENOENT 24 error Failed at the magicmirror@2.7.1 start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

hello, ive been using Face5 for a while pretty nice ,is there a way to change it to arabic numbers ? thanks

it works with bizType to tuya thx to slametps

@Egnos try this pm2 stop all export NODE_OPTIONS=--max_old_space_size=4096 npm start u can add that export line to the installers/mm.sh if using pm2

@sdetweil ok so what do I need to do to provide you the information you need?

@jew_lion openweather.com? appid shouldn’t change, just identifies u

Hi, I’m having an issue with the MMM-GooglePhotos module where it won’t display new pictures when I add them to my Google Photos album. The only way I can get the added pictures to show is to restart MagicMirror. Any ideas on getting this to work without using a workaround of programming a MagicMirror restart every so often?

@sdetweil I will have to mess with that when I have more time.

@kvicksson that code will be in the new release on Friday, 1/1

@jthewarrior7 weird… kiosk is what removes the titlebar

Perhaps you deal with these two great modules and could get them to work together without any impacts. I could not. After I installed and set up the MMM-NewPIR, I installed and set up the MMM-GoogleTasks. After that, the graphical output of the count-down bar disappeared. Did anybody experienced the same behaviour?

Sorry for replying in an old thread, but you wrote apikey in the config, it should be apiKey

[image: 1609094942954-d6fd1468-317f-4e2b-a778-e4b00cc5787e-image.png] Hi, the size of the modules of my Magic Mirror have changed from one day to the next. I’ve no idea why and am not sure what step to take next. I didn’t change anything in the system. I haven’t changed main.css file at all and have not changed anything in the modules for a number of weeks. It still works, it’s just a jumble of modules on top of each other. I’d appreciate any suggestions. Thanks in advance.

@ashishtank works as described and shown. So I have a workaround for now and can deal with the actual svg problem again later. Great, thanks a lot!

so I have had some issues with with from the get go, and I taught it was something I did in the programing but now im not sure. has anyone run into the problem with either the HDMI wire or the raspberry pi board given you issues for resolution? sometime I can jiggle the wire and it wont get me select certain resolutions (see pictures below [image: 1608873851200-screen-res.png] [image: 1608873868052-screen-res-2.png]

this helps a lot, thank you @ember1205

@mumblebaj Yes, there are many techniques to do this. If you also want to shutdown the Raspberry Pi then you can schedule it and using hardware plug like @adrian-k mentioned power on the Pi again.