@plainbroke said in MMM-NFL update ?: the options are on the github page. which is the README.md file in the module folder after git clone

That fixed the issue Chris after an upgrade. Thanks for the help!

@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

@lightsaberluke yes, system is tricky sometimes if you had used the install or upgrade script it would have handled this problem for you see https://github.com/sdetweil/MagicMirror but you can use one of the selective node tools i recommend n do this sudo npm install n -g sudo n 22.14 hash -r node -v you should now have node 22.14 or 22.15 now cd ~/MagicMirror npm run install-mm

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

Installed the pi 4 today. Was getting up to 4 days on the 02W without it crashing, so will need to give it a week to know for sure.

@sdetweil That worked i picked the right start because there is apparently 2 of them in the text code

@British_Kiwi its running, dont worry about the warnings

@plainbroke Happy to help.

@rkorell yes meant grep ssh good info on ps failure impacts

@sdetweil I changed it back now it works again thanks!

@plainbroke yes, maybe pass a folder name

@redux703 calendarSet should only pick the different default calendar (s) the filter function allows you to check different event characteristics, title, date…

@sdetweil Thanks! This worked like a charm. Also had to add to normal calendar module

@KristjanESPERANTO Its working again, thanks buddy!

@sdetweil Sadly another failure I’ve emailed the log.

This fix is in the next release , Oct 1

@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 } }, } },

Sam, Yes, it was the file content. I had copied it from the git example but obviously did something wrong.

@sdetweil Thank you Sam, That fixed my issue, and let me use the default clock files… Cool thing is with the old setting in the Custom.css file I can change the colon : color between the numbers a different color. Fun Fun Fun.