BTW… fresh install, there is no ‘default’ directory under modules… Thoughts?
default modules moved from modules/default to MagicMirror/defaultmodules
“server”: “node ./serveronly”
looks like a bug in 2.36 , fixed in 2.37-develop
3 more weeks til 2.37
you could get develop branch
https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code
@ember1205 mm version is in package.json
2.35/2.36
all custom.css stuff moved to config folder (user managed files go here)
default modules moved from modules/default to defaultmodules
@ember1205 what MM version is this?
@ember1205 did you redo the MM npm install after upgrading node? to make sure any dependencies with node version requirements are resolved?
@tommyk glad you got it working. Hopefully the other system won’t be so hard.
@tommyk no joy at what? Opening the MagicMirror page?
@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
@tommyk and using
That url in browser on phone does not work? (Bypass qr)
But if you do
Brings up the MagicMirror page on phone?
@tommyk ok, I just added the QR to mine,
what is the address shown under the QR code??
mine shows
http://192.168.2.106:8090/remote.html
which is my server address, and port
here is those values in my config.js
address: "0.0.0.0",
port: 8090,
ipWhitelist: [],
the app opens on my phone correctly
same view as on my computer
@tommyk only anyone on your home network… not anyone in the world…
I don’t know on the phone app… I didnt install the app…
@tommyk mm is meant to be a closed system on the wall…
no one needs to access this, as its output only… SO
the default config says ONLY apps INSIDE this SAME machine can access the MM server
localhost is the name of the network connection (loop back)
now, it so happens one could add controls to limit JUST ONE (or a few) machines too…
this is the ipWhitelist
but as we’ve seen that (output only with no external access) doesn’t work for a number of use cases.
remote control, my mmm-config, …
SO, changing the config
address means listen for incoming requests on A network adapter, wifi OR ethernet…
address=“192.168.2.106” (for my desktop ethernet address)
but what if you have both? or more than one…
you can ONLY put ONE address there…
so there is a shortcut , “0.0.0.0”, means listen on ALL adapters, regardless their address…
now… i’ll just make an example, not implying anything…
you built this thing, and if ANYONE in your house could get in and fiddle with the MM parts, or others,
they might take the system down or something else…
kids that don’t know, but LOVE to explore…!!
how can i keep THEM out…
we I could limit access to ONLY MY phone, laptop,… then they couldn’t get in…
so you could put your phone and laptop ip addresses in the ipWhitelist:[] list
and then only YOU can get into the MM app system …
the RemoteControl readme, mentions this change in the config…
@ember1205 understand… please advise your results when you can
@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…
package-lock.json
package.json
erase those and git pull again
@ember1205 upgrade of the core code is
cd MagicMirror_folder
git pull
npm install
if it will run… needs at least node 22.22.1
let me know how I can help
you can fall back to a prior version by switching to one of the earlier releases, thru the git tag we created.
if you try the upgrade (manual) and it fails and want to try this, let me know i’ll provide the commands needed
@ember1205 you can attempt to upgrade modules…
each is separate
cd module_folder
git pull
if successful, npm install
restart mm… to load the new modules…
only a few have latest as dependencies… which would force all the above work
@ember1205 the difficulty is that the core has been kept up to date, and it requires new system parts that require new system parts…
you MUST upgrade nodejs if not on node 22
upgrading on older systems fails, the next node upgrade, 24 or above, drops support for 32bit systems completely… we are holding off as long as we can… but the clock is ticking…
my install and upgrade scripts enforce the systems path… if they fail now, there is no manual way to get there from where you are… (without rebuild)
and if you use my installer script, its a copy/paste… not a lot of work
make the backup regardless
@ember1205 I recommend
make a backup, store to github
make a new SD card, latest OS
install MM, verify it starts (full service, UI etc)
run restore from github to restore your configuration and modules…
restart and verify
old system is untouched
@ember1205 by default, install puts down all the code, with three different start options
// server only - probably what you have now
npm run server
// npm start, npm run start , npm run start:x11, npm run start:wayland (last two in latest releases)
// launch UI, thru embedded electron browser or browser on system thru my browser over server setup
npm run start
// or client
npm run client
the latest releases will need a new OS, and new JS, and a new …
one thing you can use to move between environments, is my backup/restore scripts.
https://github.com/sdetweil/MagicMirror-backup-restore
which backup the config.js, custom.css (and any other files related)
and the list of modules installed… NOT the BINARY
this backup can be placed on github, so you don’t have to store it on the local machine
storing with git, also allows you to keep track of changes/versions of your setup
because it is NOT a binary, you can use it to transition to new SD cards, or new systems (pi->minipc…etc)
backup here, restore there
restore assumes MM is installed and runnable…
as an example
backup now, save to github (still free today)
make new sd card,
boot
install MM
then run restore to put saved config and modules on the new system
you can run the backup/restore by copy/pasting the links and adding parms if need be (like push to repo, not default)
in the meantime, you can just change the start command from run server to run start to start the MM ui on the same machine (needs a head of course)
ps. you cannot upgrade ONE feature and not others… its all or nothing
we ALWAYS start the server, and sometimes start the UI depending on the command used
but the files are all one instance at the same version
@tommyk I installed RC, and used the default config…
then started mm and used my MM address and port, from the same machine
http://localhost:8090/remote.html
and from my phone
http://sams:8090/remote.html
both worked find
you DO have address and ipWhitelist set as “0.0.0.0”, and [], respectively, correct…
this allows any host (phone, laptop,… system other than MM machine) to connect to the MM server
otherwise the connection will be refused/blocked