@sdetweil No - I need to click on the “play” button on the stream.

Okay, thank you! I’ll try my best. Richard_Fish

Hello, Is your problem is solved? Recently, I am also facing the same issue, I tried to contact the customer care service of the monitor. Later I released, I am using the outdated drivers and hence it is creating the issues to display the pictures. I think you have the same scenario. I am linking to the resource, you can check them for step by step troubleshoot. Thanks, Jeffer James

@cheapdad I sent u a chat message

Has the google tts module stoped working or is it just me. I’m having trouble getting it to work. Here is my debug 1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ] 2 info using npm@6.14.11 3 info using node@v10.24.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle magicmirror@2.13.0-develop~prestart: magicmirror@2.13.0-develop 6 info lifecycle magicmirror@2.13.0-develop~start: magicmirror@2.13.0-develop 7 verbose lifecycle magicmirror@2.13.0-develop~start: unsafe-perm in lifecycle true 8 verbose lifecycle magicmirror@2.13.0-develop~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/home/pi/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games 9 verbose lifecycle magicmirror@2.13.0-develop~start: CWD: /home/pi/MagicMirror 10 silly lifecycle magicmirror@2.13.0-develop~start: Args: [ '-c', 10 silly lifecycle 'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js' ] 11 info lifecycle magicmirror@2.13.0-develop~start: Failed to exec start script 12 verbose stack Error: magicmirror@2.13.0-develop start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 12 verbose stack spawn ENOENT 12 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 12 verbose stack at ChildProcess.emit (events.js:198:13) 12 verbose stack at maybeClose (internal/child_process.js:982:16) 12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 13 verbose pkgid magicmirror@2.13.0-develop 14 verbose cwd /home/pi/MagicMirror 15 verbose Linux 5.10.17-v7l+ 16 verbose argv "/usr/bin/node" "/usr/bin/npm" "start" 17 verbose node v10.24.0 18 verbose npm v6.14.11 19 error code ELIFECYCLE 20 error syscall spawn 21 error file sh 22 error errno ENOENT 23 error magicmirror@2.13.0-develop start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js` 23 error spawn ENOENT 24 error Failed at the magicmirror@2.13.0-develop start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ] I have zero knowledge to debug this issue, someone please look into this and let me know of a solution if there is any. Thanks

@gnomemcgmome Hi. Take a look at this to see if it will help with your loading issue. https://forum.magicmirror.builders/topic/14919/weather-module-location-id Cheers.

@hango Aaand now that works! Great, thanks! :ok_hand: So how did you find the others nbames like “newsfeed-source”, “newsfeed.title” etc…? I would like to do it by myself next time :winking_face:

@sdetweil Thank you very much! Update successful. :white_heavy_check_mark:

@ashtonian I was just mentioning that my scripts are listed on the mm main site as alternative ways to install.

@cheapdad read the links in my signature below

@sdetweil cool… will experiment :thumbs_up:

@sdetweil I’ll check that out; thank you!

Hello, I want to display a picture which is bigger than the screen. The height of the pic is bigger than the height of the screen, so I used the backgroundAnimationEnabled Option of the MMM-BackgroundSlideshow module. Now the picture scrolls either from top to bottom, or from bottom to top. But I want that it only scrolls from top to bottom. Is there any option to set that? Here is my config entry of the module: { module: 'MMM-BackgroundSlideshow', position: 'fullscreen_below', config: { imagePaths: ['modules/MMM-BackgroundSlideshow/bt-background/'], slideshowSpeed: 86400, transitionImages: true, randomizeImageOrder: true, transitionSpeed: '0s', backgroundAnimationEnabled: true, backgroundPosition: 'top', backgroundSize: 'cover', animations: ['slide'], backgroundAnimationLoopCount: '1', backgroundAnimationDuration: '5s', }, }, Thanks for any help

hi @sdetweil, in deed that was the problem, thank you!

@mykle1 Thank you. This was very helpful and I think I’m heading in the right direction.

Reinstalled MM and modules from scratch. Backup was too old and I had changed too much since it was done. Reinstalling was faster.

@skuethe That did it! Thank you so much. SOLVED

@avolaid said in SD Card - no Space: How did you got the Fronius fork with the MMM-ioBroker? MMM-fronius ist sending the data direktly to the Mirror. MMM-ioBroker sends my ioBroker data to the Mirror and has a adaptor to fronius. So both adaptors are working not together.

@sdetweil oh. thank you

@paulyp2k6 said in RSS-Parser error?: /MMM-MyWeather we took out a bunch of modules that use code that is recommended to be discontinued some modules used things without documenting them… here is another case to fix in a terminal window cd ~/MagicMirror/modules/MMM-MyWeather npm install rss-parser then restart MagicMirror