@sdetweil easier fix in css:

/* Disable alerts */
.MMM-OpenWeatherForecast .weather-alert .weather-alert-description,
.MMM-OpenWeatherForecast .weather-alert .weather-alert-source {
	display: none;
}

Module shouldn’t have interfered with wifi - Do you have a Pi 4? There’s a couple of problems with Pi 4’s and Wifi.

if you’re using a QHD resolution, it can jam wifi. second - if you’ve got 5ghz enabled, it can jam wifi.

Perfect. Actually, it appears to be that case. Thanks!

@thedoorsfanatic clearly you cut a wire when pulling it apart. use plastic, patience, and small moves.

@sdetweil It’s easy fixes. I just reverted to a point where I had the proto-settings but not the actual use of them. 🤪🤪🤪

One other thing you can do is run “npm run config:check” in the magicmirror root directory (~/MagicMirror) - it’ll run through and see if there’s anything that’s slightly out of wack to blank the mirror but not out of wack enough to throw an error. It’s saved me lots of headaches several times.

If you’ve got the sheet the right size, you shouldn’t need anything - the frame on top would do the job of holding it in place if built correctly. See standard woodworking videos on youtube for frame building ideas, or hit up a frame shop.

@p1lspeda I have it fixed. Remove the old from custom.css and replace it with the following and then set whichever backgrounds you’d like as before. (rgba(255, 255, 255, 0);)

Thanks for catching.

.MMM-Multimonth .settings {
  --background-dimmed: var(--color-background);
  --background-weekday: var(--color-background);
  --background-weekend: cornflowerblue;
  --background-current: Yellow;
  --background-header: Green;
  --background-weekno: grey;
  --background-dow: var(--color-background);
  --background-week: var(--color-background);	
  --color-weekday: var(--color-text);
  --color-weekend: var(--color-background);
  --color-current: var(--color-background);
  --color-dimmed: var(--color-text-dimmed);
  --color-header: var(--color-text-bright);
  --color-weekno: var(--color-text-bright);
  --color-day: var(--color-text);
  --color-dow: var(--color-text);
  --color-event: Red;
  --back-rounding: 8px;
  --alignment: center; 
  --fontsize: var(--font-size-xsmall);
}

the custom “.current” part is also not needed.

@Eric_H config:check hasn’t worked as of 2.12.

Gonna have to manually run through for now.

@lucas781 As I’ve said, I’ve repurposed it. I’m likely gonna repurpose the other 5" display I have too for SOMETHING… just donno what yet.

I am upgrading the module. Uploading a new release as soon as I’m done posting this.

This change is breaking old CSS.

Re-read the README.md before upgrading.

Updating from prior to 08 Jun 2024:

CSS is changed - please check all customizations. Old Elements, values, etc. have been deleted.

The following CSS code is all you need in custom.css if all you’re changing is the colors and/or background edge rounding:

(Key changes here: “current” has been changed to “today”, “background-week, color-week have been removed as redundant”)

Most of the changes are to implement feature changes.

Thanks for the support folks.

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

@harney that’s sexy. 🤣

@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

@oraturk75 My rules:

1. Must plug HDMI into the bottom, top, or side, not the back. (Flat against the case)

2. Must have VESA Mounting if I keep the shell on.

3. Must remember if it’s on or off through power outage.

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

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

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