This randomly started working again. So not sure what’s going on with it. I can only think that it was the amount of entries or something it didn’t like when reading.

@DehJango show me your config… you can send as a private message, please don’t change anything…

@DDE12 try this edit js/electron.js and change this , approx line 70 in the develop branch let address = (config.address === void 0) | (config.address === "") ? (config.address = "localhost") : config.address; to this let address = (config.address === void 0) | (config.address === "") | (config.address === "0.0.0.0") ? (config.address = "localhost") : config.address; previous issue, reopened https://github.com/MichMich/MagicMirror/issues/2550

i followed this to get my starting again https://forum.magicmirror.builders/topic/10840/problems-with-starting-pm2-start-mm-sh/7

@sdetweil The temp fix worked. Thank you!

@fribse Ok, that is weird, after doing the force, and waiting for quite a while, it works again??? So I’m changing it to solved, running the update once more, with “force”, made it work

@nakulbende on the createRequire see https://github.com/MichMich/MagicMirror/issues/2772

@calcio if you used my install script, I create that script ~/MagicMirror/installers/mm.sh

Dears Even I’ve showDeviceColums: true, in config.js, each device is on own row, means no columns. Just in one config I’ve showInNewRow: true, so, I shoudl see only 2 rows any idea, what I did wrong? thanks Zdeněk

Hi all, I have a problem mmm-weatherornot works well when I start it but it does not update, the temperatures remain as at startup. do you have an idea ? my config.js: { disabled: false, module: ‘MMM-WeatherOrNot’, position: ‘top_right’, config: { location: “champagne-saint-hilaire”, // See instructions locationCode: “46d320d32”, // See instructions languages: “fr”, // See Languages list tempUnits: “C”, // F or C font: “Tahoma”, // See Font list textColor: “#ffffff”, // Hex color codes. htColor: “#ffffff”, // high temp color. Hex color codes. ltColor: “#00dfff”, // low temp color. Hex color codes. sunColor: “#febc2f”, // Hex color codes. moonColor: “#dfdede”, // Hex color codes. cloudColor: “#dfdede”, // Hex color codes. cloudFill: “#1f567c”, // Hex color codes. rainColor: “#93bffe”, // Hex color codes. snowColor: “#dfdede”, // Hex color codes. height: “600px”, // module is responsive to changes width: “600px”, // module is responsive to changes label: “Champagné Saint Hilaire”, // Location seems logical . . days: “5”, // 3, 5 or 7 theme: “Background”, // See Themes list *** theme overrides bgColor. *** bgColor: “#000000”, // theme overrides bgColor. icons: “Climacons Animated”, // Iconvault, Climacons or Climacons Animated animationSpeed: 3000, currentWeather: true, updateInterval: 1 * 60 * 1000, } }, Thanks

Never mind, I found it :) And it works, thanks again !

@oldskoolz rule 1… never change MagicMirror or a module source code, it breaks the ability to update. all config goes in MagicMirror/config/config.js you don’t add devices for pages, all you do is set the number of pages you want to navigate to … pages: 3 this will give you devices for page 1, page 2 and page 3 in the npm start output you should see the number of devices created that you can access via Alexa turn on page 2 as the devices are fake outlets if u want a different voice command, you can use an actual alexa routine select voice go to page 2 action smart home devices page 2 power on alexa does not provide any symbolic replacement functions go to page {n} replace n with a number on execute

@sdetweil Ok thanks for the answer, I didn’t know that

@MMRIZE I would love to see it reworked, mostly to add the missing 2 positions. (middle left, middle right)

Good morning my mirror works thank you

@smartroad https://forum.magicmirror.builders/topic/17773/calendar/8?_=1683543891403 that is a copy/paste of a module’s content from the developers window. note that the class=" module and modulename" both occur only on the same element, so using just .modulename will select the same content as using both when there is no space between the selector clause class names, this means BOTH must occur on the same element, and in this case there is only one of those to select. and just as food for thought, it takes a little more cpu cycles to look up TWO things together than just one.

All, Got it to work. Thank you for the help with this. I appreciate it.

@sdetweil Tnx, that did the trick. I imagine thats been a problem with other modules that I started with. I’ll try the same on them. Cheers!

@sdetweil Thanks for the catch. I appreciate it and the tips for future post. First time posting here.

@djlagaffe - I was able to get it working with xrandr with a small modification to the node_helper.js file. I’ll submit a PR soon.