@thartley cool. Happy that it works. Have fun! Warm regards, Ralf

@Megawaldi it is fixed in the develop branch for next release You can get the develop branch, Currently we only release 4 times a year January ,April, July, October See https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

@SdR awesome. Sorry it took so long. Got sidetracked by the MagicMirror install problem, which wasn’t the cause

@gonzonia you didn’t mention scenes before. But it’s just another module

@KristjanESPERANTO or fix the package.json

@tommyk glad you got it working. Hopefully the other system won’t be so hard.

@kkmirr04 ah, that’s why I dont use the calenderSet list in ext3 config. Show all Glad you found it!! ( it is there in the config you posted) Thx for the feedback

@dangerousden AWESOME!!! thanks for the great post… one thing from above, when posting config content or log info, please use the code block wrapper past the text, blank line above and below, select the text you just pasted, hit the </> button to use the wrapper…

@BKeyport yes, if I discover you are not on the master branch, I move you to master, then update from there. For exactly this situation. Trying a specific fix or all of develop branch.

@KristjanESPERANTO thanks for the great info

@sdetweil , @kristjanesperanto , I’ve decided to resolve it by myself - with Sam’s hint/advice/helper-file. It seems to work - will double check my cache size in a few days. Thanks again for your great support. Migration is a bigger task and wihout any need currently too much - even cache-growth wouldn’t change this. never touch a running system :-) Warm regards, Ralf

@tommyk glad you got it working As for remote control , open another topic. I’m sure someone can help

@FrostByte cool… we try to stay in sync with electron, because there is a scenario for some modules, where mm running npm run server generates one binary version, need node rebuild to match current node binary and npm run start:… requires a different binary , fixed with electron rebuild (which we don’t ship, but I add in the scripted install AND when the module ships from the author, it may have a DIFFERENT binary than BOTH those choices… (SOOOOO much fun) anyhow, we have tried to keep from having that problem rear is head all the time… also, starting with node 24, there are no more 32 bit nodejs pre-compiled binaries… which means it won’t run on older 32 bit (smaller memory footprint) systems…

@smegbadger you would have to load the develop branch of MagicMirror, as we don’t distribute less than the full package… see this link https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code

@Richard238 generally I recommend sticking with the one that comes w the nodejs version.

@RonR Thanks for the positive feedback. I found it amusing that you thanked Sam first, since he provides most of the support here — something for which, honestly, I often lack the time and patience… The problem itself seemed familiar to me; I just had to track down the corresponding issue.

@heath1066 awesome.

@Phantomkommander this fix is now in 2.36 released today

@TiLow awesome! As moderator here, I think my job is to help users make and keep their mirrors running. Watch for trouble and find ways to resolve it. Your clear description of the problem helped identify a good resolution. I didn’t do any of the work. Just connected the dots.

@Lmagenis ok, understood We changed npm start to use the Wayland compositor, instead of x11 because the pi os has that as default now If you used my install script and selected pm2, then my startup script (mm.sh) detects which compositor is running, and issues the appropriate start command