@payno4 that typically means there is some config problem for a module, that causes MM to fail, and then pm2 starts it back up again… we need to see the output of pm2 logs --lines=100

u can look at an example of how to connect the two to insure correct connection, see my two posts starting here https://forum.magicmirror.builders/topic/12021/making-my-first-module-issue-with-notifications/7 modulename.js creates a random number on startup (per client) and that is appended to the module identifier (per module: in config.js on server) to create a unique module/client pair, and that is passed in/out on any requests to/responses from the node_helper

This is a layout I made for a native 1366x768 TV that I use in my kitchen as an information centre. I’ve used a LOT of custom CSS to make this work. It does indeed use the standard clock module. The weather has been repositioned with CSS to make it look like it’s part of the top-left module, but they are in fact two separate modules. I no longer use this layout as it didn’t really work for my needs and there were several modules that I didn’t actually use at all. So I use something now that is simpler. I could share the custom.css and config for my current layout but it would be useless to anyone else unless the TV uses a native 1366x768 display. You can read about it here in case it inspires you to do something similar: http://jeffsnerdyprojects.blogspot.com/2018/04/information-center-v2.html?m=1

@DennisFaucher said in Sacrilegious Non-MM MagicMirror : I could display the clock but not the Dark Sky weather module. I wrote the Dark Sky module. It uses the Nunjucks HTML templating system… I wonder if that has anything to do with why you couldn’t get it to run? Maybe it’s just a case of manually installing Nunjucks.

I can confirm my version of https://github.com/jclarke0000/MMM-MyWeather is no longer working or supported due to the doomed nature of the weather underground API. I wrote MMM-DarkSkyForecast to replace it. It uses the Dark Sky API for weather data. Find it here if you’re interested. https://github.com/jclarke0000/MMM-DarkSkyForecast

Hi, since I updated MagicMirror I have a Problem running MMM-Fuel. I’m using the Provider “Spritpreisrechner” and it’s only “Loading”. npm start dev puts out the error TypeError: collection[type] is not iterable at Object.getData (/home/pi/MagicMirror/modules/MMM-Fuel/apis/spritpreisrechner.js:141:41) at process._tickCallback (internal/process/next_tick.js:68:7) Anybody an idea what I can do to solve this problem? Thanks S

Merci beaucoup top. Peux tu me dire quel module tu utilise pour la météo ? Il est joli. J’aimerai aussi avoir un temps de trajet comme toi, mais je viens de regarder et découvrir Jeedom vu que t’en parlais, est ce compliqué d’installer un truc comme ça sachant que mon seul but et d’avoir un temps de trajet ? Tu peux me donner plus de détail sur ce sujet ? (Nota : J’ai peu regardé le MMM-Traffic mais j’ai pas de clé API donc je regarde pour une alternative) Merci

@RoadRunnr1469 ok, YOU have to actually update the fileUrl file with new contents. it loads the SAME fileUrl over and over and over and over it adds a fake timestamp to the URL to force the browser cache to see a different file which loads a new instance into the cache… so somehow you have to do cp whatever_source_path/new_logo_to_display.jpg ~/MagcMirror/modules/MMM-SimpleLogo/public/Amc.JPG I have tested this and it works also I think the content of the new logo image TYPE must match the file extension… it is expecting jpg so cannot change to gif/png for next ones to load

@supersinus MMM-CalendarExt2 could do.

@BKeyport sorry, not quite sure what you said

I purchased my glass from @Goldjunge_Chriz for some time a go, and got it to wall just now (couple of years later). I am happy with how the SW side works and is easy to code, but the mirror is not reflecting very well. I have couple of pictures above showing the reflection with and without ceiling lights on. The small makeup mirror is below for the reference. Any ideas what I have done wrong? I have few weeks time to fix it or it will be replaced by Ikea mirror I have plywood back ground (against the glass) which I sprayed with mat-black and no light should get behind or sides to the glass. https://www.dropbox.com/s/evand929hewdqod/20191111_071511_720x1280.jpg?dl=0 https://www.dropbox.com/s/ekf7iqsr0j57pr6/20191111_071940720x1280.jpg?dl=0

@lavolp3 it is/was installed as part of the original install script raspberry.sh, I didn’t change that except to add some logging # Check if plymouth is installed (default with PIXEL desktop environment), then install custom splashscreen. echo -e "\e[96mCheck plymouth installation ...\e[0m" | tee -a $logfile if command_exists plymouth; then THEME_DIR="/usr/share/plymouth/themes" echo -e "\e[90mSplashscreen: Checking themes directory.\e[0m" | tee -a $logfile if [ -d $THEME_DIR ]; then echo -e "\e[90mSplashscreen: Create theme directory if not exists.\e[0m" | tee -a $logfile if [ ! -d $THEME_DIR/MagicMirror ]; then sudo mkdir $THEME_DIR/MagicMirror fi if sudo cp ~/MagicMirror/splashscreen/splash.png $THEME_DIR/MagicMirror/splash.png && sudo cp ~/MagicMirror/splashscreen/MagicMirror.plymouth $THEME_DIR/MagicMirror/MagicMirror.plymouth && sudo cp ~/MagicMirror/splashscreen/MagicMirror.script $THEME_DIR/MagicMirror/MagicMirror.script; then echo if [ "$(which plymouth-set-default-theme)." != "." ]; then if sudo plymouth-set-default-theme -R MagicMirror; then echo -e "\e[92mSplashscreen: Changed theme to MagicMirror successfully.\e[0m" | tee -a $logfile else echo -e "\e[91mSplashscreen: Couldn't change theme to MagicMirror!\e[0m" | tee -a $logfile fi fi else echo -e "\e[91mSplashscreen: Copying theme failed!\e[0m" | tee -a $logfile fi else echo -e "\e[91mSplashscreen: Themes folder doesn't exist!\e[0m" | tee -a $logfile fi else echo -e "\e[93mplymouth is not installed.\e[0m" | tee -a $logfile fi

I have open an issue for this for try to correct it but it’s an unstable branch (nightly build / dev) If you have it, you can test

@trawson I’m the one that submitted the compliments changes, but it shouldn’t have affected any date/time selection . If u send me the js file and your config/file I will see if I can fix what’s wrong Same userid as here, at gmail

@DæmonEyes said in Something went wrong after updating MM: how do I update a module when the top banner comes up saying there is an update? in the terminal, navigate to that modules folder then run git pull

@sdetweil sorry, typo on run-start #!/bin/bash -x

@kellogg76 also, the first script u listed is raspberry.sh which is new install. Upgrade-script is the one that does version upgrades of existing installations (get rid of that message)

I have tried to search for this problem but to no avail. My mirror uses MMM-PIR-Sensor to turn on the screen when detecting motion, and then off again after 10 seconds. But most times the screen turns on, the UI is “out of sync” with the current time – the clock is wrong, modules haven’t been shown/hidden on schedule with MMM-ModuleScheduler, any Alerts that were triggered won’t show, etc. Sometimes I can see the screen “catch up” if I stay in front of it for a few seconds; sometimes the screen never catches up, and I have to restart the service. I can pull up a browser from another computer or on the Pi, point it at the MM server, and everything is fine on that device – this only seems to be a problem with the default npm start MM process. Has anyone experienced this issue?

Added a video (two years later): https://youtu.be/2Hi9IDfrqPQ The Mirror is used daily and I have upgraded from a RPi 3 to a NUC instead to get more CPU-Power to play with.

@binderth said in Microsoft To-Do (wunderlist replacement?): first: I think, the URL is broken (spaces here: https://github.com/thobach/MMM-MicrosoftToDo#authorization-code-generation-code). only after replacing the whitespaces with “%20” it worked and I got the code. For me the link worked as it is. What whitespaces do you mean? This might be helpful: @sdetweil said in no result from mvgmunich modul: @Babene1 open the developers window, using the keyboard, ctrl-shift-i, select the tab labeled ‘console’ and then scroll up… to find any errors (usually red text) you can also filter to messages from a single module, by putting some part of its unique name into the file labeled ‘filter’, like mvgm let us know what u find if you use pm2 to manage the mirror runtime, you might also look at the logs, by doing pm2 logs