@tommyk you can get rid of these noise errors

Open a terminal window, and do

cd ~/MagicMirror 
cd config
touch custom.css

Next time you start MagicMirror you won’t get those errors reported

If you use my/the scripted install, it does this for you

@tommyk the module instructions, step 5

@tommyk the app on phone says syntax error?

can you open the app on a computer web browser so we can examine the browser logs?
once loaded(or not) open the developers window, console

ctrl-shift-i, then select the console tab, maybe the javascript error is listed there

@kkmirr04 ok, the design here is MM calendar module broadcasts events, fairly at random

CalExt3 (family) consumes those events, and draws new view…

but it doesn’t want to flash the screen on every event arrival,
refreshInterval

sort of like a train station stop, when the interval fires, all the events that have arrived til then are shown
miss the schedule, wait til next time
default 10 MINUTES

but you don’t want to wait at the start for 10 minutes, you want it to draw NOW…
so waitFetch controls a short wait at startup
but if you miss that window, then you wait the refreshInterval

I suspect that if the module is not shown on the 1st page, it doesn’t get its dom created signal til the page is shown. so you have 40 seconds (page 0/page1) til the first draw starts, which is after the waitfetch.

how long did you wait?? have to wait at least 10 minutes, til Ext3 will draw again

@tommyk can you go to the MM folder and do

npm run config:check

and show the output

@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.

@BKeyport yes. If you use my upgrade script it will move you back to the mainline, or I’ll give you instructions

@reilley insufficient permissions on git
Sounds like you might have used

sudo git clone 

Otherwise, this is a sign of sd card troubles coming soon

this permissions trouble could also explain the module update problems

@KristjanESPERANTO thanks for the great info

@reilley ok, the fix came in on 2.36 I think

Do this for a quick test

Stop MagicMirror
If using pm2 to launch, then

pm2 stop all

Then

cd ~/MagicMirror 
npm start >somefile.txt 2>&1

Wait 30 seconds after MagicMirror is up, then
ctrl-q on the MagicMirror screen

Now back at terminal window

nano somefile.txt

ctrl-w
updaten
Hit enter

Will scroll to location, repeat ctrl-w enter,
Should come to status of git search the repo and repo error

Ctrl-x to exit nano

If using pm2 to Launch MagicMirror

pm2 status

Then

pm2 start xx

Where xx is the name or number on the row of the app to start
Typically MagicMirror or 0

@reilley what MagicMirror version are you on? There was a bug fixed when scanning for changes

@DerHerrB awesome!! Don’t know why node 24 causes so much trouble.

@BKeyport awesome!! Thanks for the feedback

@DerHerrB I see the first scripted run had a problem w a docker update.

Sounds like you did some other things before MagicMirror

@DerHerrB thanks. Did you install node 24 in advance?

There is a problem w node 24

So do

pm2 stop all 
cd ~/MagicMirror 
rm -rf node_modules
rm package-lock.json
sudo npm install -g n
sudo n 22.22.1
hash -r
node -v

If that produces 22.22.1 ,
then do

npm run install-mm 

And because you selected pm2

installers/mm.sh

MagicMirror should launch now

Please advise results to here

@DerHerrB if you run the scripted install and have trouble show me the ~/install.log

The scripted install is here
https://github.com/sdetweil/MagicMirror_scripts

@BKeyport thanks… I see an other change submitted today

https://github.com/MagicMirrorOrg/MagicMirror/pull/4180
which references this topic

if you want to try that do

cd ~/MagicMirror
# restore calendar.js 
git checkout defaultmodules/calendar/calendar.js
git fetch origin pull/4180/head:_fix_304
rm package-lock.json
git switch _fix_304
npm run install-mm
restart MM

@reilley I just did the git pull on my installation

git pull
remote: Enumerating objects: 58, done.
remote: Counting objects: 100% (36/36), done.
remote: Compressing objects: 100% (14/14), done.
remote: Total 58 (delta 25), reused 27 (delta 22), pack-reused 22 (from 1)
Unpacking objects: 100% (58/58), 205.78 KiB | 1.34 MiB/s, done.
From https://github.com/randomBrainstormer/MMM-GoogleCalendar
   8679522..faf438e  main       -> origin/main
 * [new tag]         v1.2.7     -> v1.2.7
 * [new tag]         v1.2.5     -> v1.2.5
 * [new tag]         v1.2.6     -> v1.2.6
Updating 8679522..faf438e
Fast-forward
 .github/workflows/version-bump.yml   |  55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 MMM-GoogleCalendar.js                | 108 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++----
 __tests__/MMM-GoogleCalendar.test.js | 102 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 node_helper.js                       |  49 +++++++++++++++++++++++++++++++++++++++++++++++--
 package-lock.json                    |   4 ++--
 package.json                         |   2 +-
 translations/en.json                 |   3 ++-
 7 files changed, 313 insertions(+), 10 deletions(-)
 create mode 100644 .github/workflows/version-bump.yml
sam@sams:~/MagicMirror.2.36.dev/modules/MMM-GoogleCalendar$ npm install 

up to date, audited 383 packages in 2s

65 packages are looking for funding
  run `npm fund` for details

12 vulnerabilities (8 moderate, 4 high)

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

and updatenotification does not report being behind

@reilley the module was updated this morning by the author

@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…