Default Calendar stuck on loading

[sdetweil]

@rushmuzik 2.29 uses socket.io 4.8 where 2.28 uses 4.7.5

you could install 4.7.5

cd~/MagicMirror 
npm remove  socket.io
npm install socket.io@4.7.5

i have company today so it will tomorrow really before i can test

[rushmuzik]

@sdetweil I reverted back to socket.io@4.7.2 that was used on MagicMirror@2.26.0 and that fixed the issue! I tried socket.io@4.7.5 but that didnt work. So I went back to @4.7.2 and that fixed it. It might just be a compatibility issue with Firefox ESR. Mystery Solved! Thanks for all your help!

[sdetweil]

@rushmuzik awesome!!! thanks for the feedback

[rushmuzik]

@sdetweil Thanks for all you do to help the MM community!

[sdetweil]

@rushmuzik that change to socket.io@4.7.2 didn’t help my pi0w MM with firefox (running on next release or 2.29.0)

[sdetweil]

@rushmuzik
I had to change the code to add an increased timeout for fetch…
which required node 20.18.1
then the 4.8 socket.io worked with the surf browser

couldn’t get firefox to work

[rushmuzik]

@sdetweil For some mysterios reason it worked for me for 10 good minutes then crashed. I still don’t know what caused it to work that period. How is the overal experience with Surf Browser? Would you recommend I use that instead?

[sdetweil]

@rushmuzik my surf based system has bern running for 3 days without trouble

[rushmuzik]

@sdetweil I have two followup questions.

1. How do I install that surf based system.
2. Do you know how I can nun Node@20.17.0 or greater on a pie zero?

[sdetweil]

@rushmuzik

surf is installed via apt

sudo apt install surf

on armv6l installing node is a pain

quickest way is to run my installer again, as it is set to install 20.18.1
rename your MagicMirror folder out of the way first as the installer wont install over an existing MagicMirror setup

OR wait til jan 1 and run the upgrade script, which will install the new version with longer timeout and node 20.18.1