In addition: It’s possible that the old recovery script was part of my problems - due to the above mentioned ping problem.
For this reason I’ve edited my earlier post and deleted the content of the script.
I’ve added an “edit note” instead.
Sorry for confusion and any inconvenience!
Regards,
Ralf
Also, some modules document their css styles,
Some you have to look for a CSS file in their files list
And some you have to use the developers window to discover them
There are no rules enforced here by MagicMirror
@sdetweil said in MagicMirror problem:
Let’s try this
Change your config.js
address:”0.0.0.0”,
ipWhitelist:[],
Then
npm run server
Instead of npm start
Then use another system, phone to connect to that pi
http://pi-address:8080 geometry dash scratch
Thanks for your suggestion. I got it.
@Socrates note that without adding a parameter
The script does nothing. It only tests the ability to update the base MagicMirror
Update is two pass process
Test. Make no changes
Do. Apply the changes (with the parameter apply)
Many users have modified MagicMirror base code not knowing about the config and css file design. These changes block the ability to update normally
Over time they forget that they changed the files and what they actually changed. The force way to install is to wipe all changes, but now the result doesn’t work like it used to. Adding a lot of frustration.
@mumblebaj @KristjanESPERANTO @sdetweil
Thank you all for the information. I think I will stick with the way I already understand. setting up the docker and all seems like more work that is not in my wheelhouse. Interesting approach to the same end result.