@boybay7 said in Changing the colour of all text on screen:

@lavolp3 So just to confirm, even though I have edited code in like modules or custom.css for the font colour, it won’t be replaced when I update with git pull?

Short answer without a bunch of confusing and unneeded parts: Yes.

Long answer in simple form but more detail:
These aren’t updated when you follow recommended upgrade path (usually just git pull && npm install in magicmirror directory):
config.js
custom.css
modules directory structure except for the default directory tree

There are scripts out there to stash any changes you have made to changed items, however, 99.99% of the time, changes are not needed to updated parts of the MagicMirror ecosystems. the remaining time, it’s a change to get around a short term bug (like currently, the calendar applet), that will be included in the next update, so there’s no reason to stash it.

Bottom line - your customizations, unless done in a poor way, will never be deleted, until you rm -rf the whole mess or the boot device (Not just SD anymore!) crashes.

If you’ve decided to customize a module within it’s own code, that isn’t a official fix of the module, I would highly recommend forking the project, switching to your fork, then modifying to your needs. Then, if you think everyone else would benefit from it, please do a merge request, and let the author(s) decide to do so, or, in the case of dead modules, change the name and take over the project (I’ve done that with MMM-Worldclock, for instance)

@ZiggidyZ That could be a good unit… I’d personally take it off the stand if you’re going to put it in an enclosure, and use a low profile vesa mount like this. You could also build up like a mirror project, just use a clear piece of front material in lieu of a 2 way mirror.

@sdetweil both are set low, and it worked before. - – whoops - forgot I moved refresh up on those as they don’t change very much. Restored them to 1 minute for testing.

– and it don’t seem to be targeting correctly. does nothing.

Got it working guys, thanks for your help, I’ve created a merge request with Mr. Wong as well.

If anyone else runs across the thread, and it’s still not merged, my code mods are:

https://github.com/BKeyport/MMM-iFrame

@Hugo the only real thing that is a concern really is the OS. As the Pi foundation (and the community as a whole) continues to move away from old windowing systems into new ones, there may be compatibility issues with underlying tech MM uses as it catches up. As long as node.js and electron moves with the core windowing system we’re fine…

just a dance you do with any open source…

@UncleRoger No, it wasn’t that. I forgot about that code. I might go back in and grab it and offer it to the other version once updated.

@binog Even though it’s fixed, there could be another issue - something else running on port 8080. I always change the default ports… 60001, 60002, etc. Less mess.

@ankonaskiff17 take a look at the https://github.com/Tom-Hirschberger/MMM-CommandToNotification module, along with it’s co-module https://github.com/Tom-Hirschberger/MMM-ValuesByNotification

I use these to convert two physical sensor’s API calls to MagicMirror, as well as a JSON format web based outdoor sensor.

Effective 8/14/2025 - @dathbe has been provided contributor role in my active modules. I’m not ready to turn them over full time, however, I am glad that someone is willing to work with them. I no longer use the modules myself and I’m welcoming a fresh view on the topic, and hopefully the project will continue in a more effective way, including clean up and improvement of my pre-amateur code.

Thanks for the support over my time handling this code - and if I do decide to pick it back up, I know that it is in good hands.

– Brendan

On new card it worked flawlessly. I’m assuming the old conditions of partial installs and whatnot had the old install broke things.

Nothing but warnings about depreciated modules.