@sdetweil thank you very much :) perfect answer for me :)

@olesoncrypto 1st… NEVER edit the source code always use config.js if u HAVE edited the source code and want it back then , in the MM folder do git checkout modules/default/calendar/calendar.js to restore the file from the source code repository this should make the default work again (if u restored that section of the config.js from config.js.sample) so, now we need to understand why 4 cals don’t work., 1st test take each URL from each cal entry, one by one in a browser ON the MM system and see if the url downloads an ics file … this is required for the cal module to work if not, fix that then try with your config.js, which looks ok. if not working, add ,"DEBUG" to the end of logLevel: ["INFO", "LOG", "WARN", "ERROR"], // Add "DEBUG" for even more logging and start MM like this (make sure to stop any previous running mm, if pm2, then pm2 stop all npm start >somefile.txt wait til u think cal entries should have shown, ctrl-c to stop mm in the terminal window where i started, (ctrl-m to minimize mm if doing ON the pi, I STRONLGY recommend learning to use ssh from other machine to do all maint, so u don’t have these problems ) and then edit somefile.txt to see what is going on

@liz looking at the code, this module doesn’t support multiple instances. you might be able to make a setup for this copy the MMM-Fuel folder to new folder MMM-Fuel1 inside MMM-Fuel1, rename everything MMM-Fuel to MMM-Fuel1 inside templates, rename MMM-Fuel.njk to MMM-Fuel1.njk inside the MMM-Fuel1.js, change places of MMM-Fuel to MMM-Fuel1 Module.register('MMM-Fuel', { // <- getStyles() { return ['font-awesome.css', 'MMM-Fuel.css']; .// <- }, getTemplate() { return 'templates/MMM-Fuel.njk'; // <- }, in your multi-instance config.js, change one of them to module:“MMM-Fuel1”

Thank you very much!

https://forum.magicmirror.builders/topic/15778/black-screen-fix-in-2-16-and-later

@rachee problem is not you. the commands used to turn on/off the displays are sensitive to what pi you are using. 1st thing to do is use some of the python setups for PIR and prove that the wiring is right and the sensor does what u expect then try out the commands that turn on/off the display, and determine which one works for you (none work for me) the commands are tvservice - pi only, turns off HDMI port vcgencmd - turns off HDMI port dpms - turns off HDMI port cec-client - turns off cec compliant monitor/tv on the newer, energy star displays/TV’s, when u turn off the HDMI port u get some sort of ‘No Input’ screen. no way to override that not all pir modules support all the commands if u look inside each u can see what commands they are issuing, and try those manually I recommend using an ssh session, cause when u turn off the monitor you are working on, it’s gets tough to get it back on. forced reboot most of the time. MMM-New-PIR by bugsounet seems to have the most commands enabled his code to turn in/off is in his screen library https://github.com/bugsounet/screen/blob/master/index.js

@mrsnatz can you explain what you mean with “only works when all modules are loaded”? Kannst du erklären, was du damit meinst?

@sdetweil Hi Sam. Yes, I did. Unfortunately because I am on a Pi4 they are unable to troubleshoot… I reinstalled the module fresh and retrieved a new API from api.mta.info, not clear on the error socketNotificationReceived: “TRAIN_TABLE”: Array(2) MMM-nyc-transit.js:332 Uncaught TypeError: Cannot read property ‘fadeSpeed’ of undefined at Class.socketNotificationReceived (:8080/modules/MMM-ny…-nyc-transit.js:332) at module.js:245 at Socket. (socketclient.js:38) at Socket…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915) at Socket.emit (socket.io.js:1544) at Socket.emitEvent (socket.io.js:1161) at Socket.onevent (socket.io.js:1135) at Socket.MMSocket.socket.onevent (socketclient.js:32) at Socket.onpacket (socket.io.js:1089) at Manager…/node_modules/component-emitter/index.js.Emitter.emit (socket.io.js:1915)

@jamesarm i don’t think there is anything already constructed to do that (never heard anyone using tts really before) SO, you would have to change the module that sends the text to send a notification to PIR to wake up, then when wake up happens and u get a ‘user precence’ notification back, THEN send the text to TTS

@hango oh my gosh sorry for such stupid mistake:person_facepalming_light_skin_tone:

@sg437 Version of Magic Mirror?

@mmrize fixed it ty :)

@sdetweil I seem to recall that’s how it worked. Bottom line is that it’s breaking more and more, and should likely be put in the “yeah, it’s unsupported” pile of past modules. FWIW, I use my MMM-Block module to slide modules out of the way, and just run the OMX stream directly for now. (Looking for a solution for H.265 streams)

@mmrize said in MMM-CalendarExt2 config: ’ ', This is my View: views: [ { mode: "daily", title: "Termine nächsten Tage", position: "top_center", locale: "de-DE", calendars: ["Speiseplan", "Michael", "Stefanie", "Phil", "Abfall-Wertstoff-Papier"], slotCount: 3, timeFormat:"LT", hideOverflow: false, slotSubTitleFormat: ' ', dateTimeFormat: { sameDay: "[Heute] HH:mm", nextDay: "[Morgen] HH:mm", nextWeek: "dddd HH:mm", lastDay: "[Gestern] HH:mm", lastWeek: "[Letzten] ddd HH:mm", sameElse: "M/D HH:mm" }, }, ], [image: 1634564708621-calendarext2-1.png]

@almightyyoshi ‘npm install request’ fixed this problem for me. Took me a while to find the fix though. Use ‘pm2 log’ to see what is causing mm to fail.

@wageck I do not know… but I would test by disabling every module (add disabled: true, after the module: … line ) but one and test to make sure that the one module u want works… for each such module then turn back on pages, u could also do this in another copy of MM (copy the folder and edit there) or use the default config in the copy and add your one definition, copy that folder from your full config

@earnestrichards cool… glad it worked out… and another thing, I write a log of the actions, so you can look back at it, or if there is a problem… ~/MagicMirror/installers/upgrade.log

@im_ibjo MMM-FaceReco-DNN is one of the most frequently used . yes, it is complicated. mm can hide or show modules. your new module has to add everything else reading the sensor associate it w a user (and somehow registering the user in your modules context) have a list of modules to be shown for a user decide how to handle if they are still present and then showing just their configured content

@nneuland see https://forum.magicmirror.builders/topic/15432/mm2-not-loading-text/16?_=1633980707624

@jamesarm Glad to hear it works for you now.