@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

@Drunkenkun yes, calendarweek does need the config, it fetches the events itself too

@angeliKITTYx awesome. Thanks for the feedback

@sdetweil many thanks for your help once again sam!

@MarNog one thing about the ext3 family of modules. They get the events from the default calendar module. But the events are broadcast by url separately. Some will take longer than others. Ext3 doesn’t want to flash the screen every time it receives a block of events. It doesn’t know when the events will come. So, it has its own refreshInterval time (10 mins default), then it draws whatever it has, and then waits again But, you don’t want to wait 10 minutes for the first display , so it has a second timer waitFetch:5000, 5 second wait before drawing any events If the events arrive after 5 seconds, they dont get displayed til refreshInterval time. So, you can adjust those two to improve your viewing experience Note that longer waitFetch means more time after start before any events are displayed If you use pm2 to launch MagicMirror, it captures the log messages about startup and events being broadcast. You could examine those time stamps to determine how long each cal Might take, and use that as a guide to waitFetch time The longer waitFetch means no events are displayed after startup til waitFetch expires

@KristjanESPERANTO Finally got time to fix things up and move forward (Complete reinstall, honestly) Everything is working as I desire now.

@sdetweil I switched back to X11 in raspi-config, rebooted and added the parameter DISPLAY=:0 npm run start:x11 That works! :-) As it is quite after midnight here, I’ll do these tests with wayland tomorrow and respond here. So far, thank you a lot.

@Hepkat awesome. Thx for the feedback

@sdetweil Great! I’m glad I helped you while you were helping me. :)

@DarrenO-0 I understand. You might be able to switch to a different provider on the weather module, depending on where you are. Not all providers are world wide

@sdetweil Yup, it’s working now. Awesome, thank you so much. (The translations/en.json is just a single word change, so easy to fix manually without being stashed.)

@oskisch we need the browser log, Can’t get without keyboard