@ctilt glad you found it. basically it crashed mm but the modules kept running. but couldn’t find their content to update

@Untitled Is not the right Forum. Ask here : https://forum.bugsounet.fr

@djboob66 Oh I didn’t I will try

@saltyriver said in Calendar module EHOSTUNREACH error: I removed the configuration for the static IP adress for the Pi and that solved it for some reason. weird… but still a networking problem

I solved it by myself. So here for the rest of the world or maybe for myself in a couple of months. The following config is working: { module: 'MMM-BackgroundSlideshow', position: 'fullscreen_below', config: { imagePaths: ['modules/MMM-BackgroundSlideshow/BackgroundImages'], transitionImages: true, transitions: ['opacity'], randomizeImageOrder: true, slideshowSpeed: 500000, gradientDirection: 'both', gradient: [ "rgba(0, 0, 0, 0.00) 0%", "rgba(0, 0, 0, 0.00) 0%", "rgba(0, 0, 0, 0.00) 90%", "rgba(0, 0, 0, 0.75) 100%" ], //von oben nach unten, % = wo im Bildschirm startet es horizontalGradient: [ "rgba(0, 0, 0, 0.75) 0%", "rgba(0, 0, 0, 0) 15%", "rgba(0, 0, 0, 0.00) 85%", "rgba(0, 0, 0, 0.75) 100%" ] //von links nach rechts, % = wo im Bildschirm startet es } }, In addition, you have to change a line in the MMM-BackgroundSlideshow.js file in the getDom function (line 316) OLD: this.createGradientDiv('right', this.config.gradient, wrapper); NEW: this.createGradientDiv('right', this.config.horizontalGradient, wrapper); I will put this on GitHub as well.

@sdetweil I was in the MMM-LAMetro directory. I used the “node install” command from the readme. Forgot the correct command was “npm install”. No issues once I used that command.

@BKeyport said in Config Error: @evroom “convention” isn’t the right word here, perhaps. I’m almost leaning to “peer pressure” perhaps? Doing it because it seems everyone else is? I had to read the beginning of the thread first before starting ‘name-calling’ :-) And perhaps had to address it to the thread starter @PHAGE-GOV, for learning purposes Some people treat the config.js file as code and think that they are actually coding. In principle a JS file is a text file containing JavaScript code, so it is a bit misleading, although it contains “var config =”, which suggests it being a part of some code. IMHO it would be better to use the json extension, so config.json, as it is based on JSON and stores data structures and objects in this format. One should’t care less how coders use variables in their programs (as Sam said: “make names meaningful, use case where appropriate”, especially if you want to keep it maintainable or want to hand it over to someone else), but in case of config.js one should make at least a bit of an effort to keep it simple and understandable. Again: IMHO. In my book this is for example a no-go: { location: "New York", locationID: "", appid: "YOUR_OPENWEATHER_API_KEY" } This is just waiting for an accident to happen. What is wrong using locationName, locationId and apiId ? Or location, location_id and api_id ? Probably nitpicking from my side, but it hurts my eyes :-) I would say “make names meaningful, use case where appropriate and keep it consistent”. I also know it it all voluntary work and it does not cost a dime (unless you donate something to the author, like I did) and therefore one is not really allowed to complain :-) I hope some constructive criticism is allowed though. Do not want to offend anyone. That being said, just enjoy your MagicMirror. :-)

@traustisig also, there is a new upgrade script in next release… see https://forum.magicmirror.builders/topic/10859/new-update-upgrade-script-ready-for-testing to use it now

@steak just a warning… try the updated installer (to be in next release) see https://forum.magicmirror.builders/topic/10171/anyone-want-to-try-updated-installer have to rename the current MM folder out of the way

@Doogain I submitted the changes to the project this morning so in the next release they should be included

Hey Guys! it works now! i did it as described with the mm script here: https://github.com/MichMich/MagicMirror/wiki/Auto-Starting-MagicMirror thank you for all your replies! Regards Dario

I have tried to run the MMM-Hover module with the mirror, but it’s giving an error which seems odd. ERROR! Could not validate main module js file. /home/pi/MagicMirror/modules/MMM-Hover/MMM-Hover.js: i2cBus: 0, ^^^^^^

This is not out of disk space ( memory card). This is runtime memory out of space. Typically when u see this kind of error, some code has allocated space for data, but didn’t free it ( over and over) when it was no longer needed. GC is garbage collection, which reclaims memory space no longer referenced.

hey guys , i have problem with my email module. this is my npm start dev: uncought (in promise) TypeError: cannot read property ‘host’ of undefined: at … . it can update email list for 2 minute but after than that this is my error and module not showing new emails. but i have new email objects?

Create a branch on top of the master one. When an update is available, go back to the master, do the pull. Then rebase your branch onto master.

A couple things. First, please use the markdown features of the forum to make your code easier to read. There’s a nice tutorial on Git. Secondly, you need to run the npm install command in the Magic Mirror folder. So try this: cd ~/MagicMirror npm install

@giulianomondin comma missing after updateinterval

@MatthewCowell I ran it through a validator and it said no issues and I can’t find any … Why are you using Noobs? I would install this: https://www.raspberrypi.org/downloads/raspbian/ When you restart copy your sample config js file to config.js and just make sure it starts… Once you do that do not delete your sample config file as that is your temp backup… Once you get it working and you add a module and it works then back up your config.js to something like config.bak that way you always have a working backup… in terminal window: cd ~MagicMirror/config then cp config.js config.bak

I, like (I assume) many of RPi tinkerers and hackers, make code changes on my desktop or laptop and then use git to push new code to the RPi. Since MagicMirror doesn’t track css/custom.css, the mirror fails to load up if the file is missing. I tried to come up with a PR to have the loader.js file check if the file exists before appending it to index.html. However, since this is client side JavaScript, it does not have access to the file system and can’t use the fs JavaScript module. I then tried to use code like: var fileDoesNotExist= function(url) { var http = new XMLHttpRequest(); http.open("HEAD", url, false); http.send(); return http.status==404; } to do an http request to the server for the file, but realized that it’s just as bad as the actual http request that tries to load the file and will result in the same errors. So, I’m posting this here in case anyone has ideas and can help me with creating a PR to solve this problem. It’s not really a bug and not really a feature. Just an error check that’s missing. Thanks.