@chris47803 https://www.theregister.com/2025/08/21/microsoft_365_outage/

@kinggiotai did you setup the spotify.config.json from the auth callback example? [ { "USERNAME": "A_NAME_TO_IDENTIFY_YOUR_ACCOUNT", "CLIENT_ID": "PUT_YOUR_SPOTIFY_APP_CLIENT_ID", "CLIENT_SECRET": "PUT_YOUR_SPOTIFY_APP_CLIENT_SECRET", "TOKEN": "./USERNAME_token.json", "AUTH_DOMAIN": "http://YOUR_DEVICES_IP", "AUTH_PORT": "8889" } ] I had to do that just now the domain/port MUST match the callback address in the spotify app config from my app config callback http://localhost:8100/callback json file strings to match domain is http://localhost port is 8100

@KristjanESPERANTO said in MMM-Pages: I can’t take a closer look at it right now, but I have an idea for a workaround: But it only works if MM restarts regularly. Some users shut MM down at night and start it up again in the morning. https://eldfall-chronicles.com/en-si/pages/dungeoncrawl Then you could set the timer for the homepage to over 24 hours, https://www.viberate.com/ this should have the desired effect that the homepage is always visible. That’s a smart workaround

@GRR lol, yeh does whack you. im the moderator here. as well as user. module author

perfect thanks so much

@RonR there a bunch of config options not listed in the readme i think showMarquee:false [image: 1754787212070-img_2117.png]

@joey the backup approach gives you the ability to restore the modules and config/css to another system , after install, so you get a migration tool AND it provides git versioning… so if you need to go back 2 revs you can it also supports putting the backup on a (private recommended) github repo, so you can restore directly from there and don’t have any local file system failure issues… disk drives, usb sticks, etc AND it doesn’t matter WHERE you are at the time,

@sdetweil Many thanks for the input. I’ll have a tinker when I find a gap and explore the commands and their respective soft switches. Just so that I’m future proof !

@sdetweil This works and I get the logic now… thanks a ton!!!

@OwenLars Unfortunately I am not too familiar with the project and don’t have a TodoIst account to test this myself. Have you logged an issue on the modules Github page? Maybe the author can have a look at it?

Hello everyone. I installed MMM-WhisperGPD but I am keep getting some errors whatever I do. I am not familiar with coding so I am trying everything I find in the web. Below are the errors: 0|mm | [2025-07-28 20:39:44.253] [ERROR] (node:183837) UnhandledPromiseRejectionWarning: Error: PvRecorder failed to initialize. 0|mm | at pvRecorderStatusToException (/home/anthonypi/MagicMirror/modules/MMM-WhisperGPT/node_modules/@picovoice/pvrecorder-node/dist/errors.js:35:20) 0|mm | at new PvRecorder (/home/anthonypi/MagicMirror/modules/MMM-WhisperGPT/node_modules/@picovoice/pvrecorder-node/dist/pv_recorder.js:45:40) 0|mm | at Class.setupAudioRecorder (/home/anthonypi/MagicMirror/modules/MMM-WhisperGPT/node_helper.js:75:22) 0|mm | at Class.socketNotificationReceived (/home/anthonypi/MagicMirror/modules/MMM-WhisperGPT/node_helper.js:44:12) 0|mm | at Socket.<anonymous> (/home/anthonypi/MagicMirror/js/node_helper.js:91:10) 0|mm | at Socket.onevent (/home/anthonypi/MagicMirror/node_modules/socket.io/dist/socket.js:462:26) 0|mm | at Socket._onpacket (/home/anthonypi/MagicMirror/node_modules/socket.io/dist/socket.js:430:22) 0|mm | at /home/anthonypi/MagicMirror/node_modules/socket.io/dist/client.js:214:24 0|mm | at process.processTicksAndRejections (node:internal/process/task_queues:85:11) 0|mm | (Use `electron --trace-warnings ...` to show where the warning was created) 0|mm | [2025-07-28 20:39:44.253] [ERROR] (node:183837) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) Any help apreciated. Thanks in advance.

@starz22 weird i use imagesPhotos myself

@chrisfr1976 Thank you! That actually pointed me in the direction of another thing I wanted to solve which was to only show the lunch menu and not the breakfast and lunch menus.

@KristjanESPERANTO Its working again, thanks buddy!

@khrusher I don’t know the effect. but given how fast you are cycling with carousel, I don’t think it should matter

@Eagleyes27 I recently updated the NOAA3 module. You can use my fork which you can find here: NOAA3.

@svenpisa I created this module based on the OpenWeatherForecastDeluxe project but the backend AccuWeather API is obviously different than the OpenWeather API. It only supports forecasts for a couple different time periods. It could be updated to filter those however, the big issue at the moment is the upcoming deprecation of the free limited license for the API. There will soon be only a 14-day trial and paid licenses which $25 a month appears to be the cheapest which is a no-go. [image: 1753131120160-63590778-ec41-40f5-b2f4-7a3c53ac1189-image.png]

@sdetweil yes, and that is how I started, but it didn’t work.

@KristjanESPERANTO said in Can't get MMM-Carousel to work with MMM-BackgroundSlideshow: position: “bottom_right” Thanks for your reply, trying that now.

@rkorell @sdetweil Never mind I am stupid. I figured out that I had removed several sections of the config file that was in his readme. Then went and re numbered the lines. Which really upset the apple cart. I did have to change the parts you said @rkorell. But the rest was my doing. Compare the first Config i posted and this one and you will see what I did. { module: "MMM-Pinfo", position: "middle_center", config: { debug: false, refresh: 5000, itemAlign: "left", labelAlign: "left", valueAlign: "right", labelSize: 400, containerSize: 500, DEVICE: { labelModel: "Model", displayModel: true, orderModel: 1, labelSerial: "Serial", displaySerial: true, orderSerial: 2 }, OS: { labelOs: "OS", displayOs: true, orderOs: 3 }, NETWORK: { labelType: "NET Type", displayType: true, orderType: 4, labelIPv4: "IPv4", displayIPv4: true, orderIPv4: 5, labelIPv6: "IPv6", I deleted these 2 lines and then changed orderMac: 6 and so on down the List.. DISPLAYIPV6: FALSE, ORDERIPV6: 6, labelMac: "MAC", displayMac: true, orderMac: 7 }, RAM: { labelRam: "RAM", displayRam: true, orderRam: 8 }, STORAGE: { labelStorage: "Storage", displayStorage: true, orderStorage: 9, }, CPU: { labelType: "CPU Type", displayType: true, orderType: 10, labelUsage: "CPU Usage", displayUsage: true, orderUsage: 11, labelTemp: "CPU Temp", displayTemp: true, orderTemp: 12 }, UPTIME: { labelUptime: "Uptime", displayUptime: true, orderUptime: 13 }, WARNING: { enable: true, interval: 1000 * 60 * 5, check: { CPU_TEMP: 65, CPU_USAGE: 75, RAM_USED: 80, STORAGE_USED: 80 } }, } },