I put them both in, and that fixed it - thanks, Tom.

Tom, is it updateDomOnShow or updateDomOnResume ?

Documentation shows the latter.

@sdetweil

It shows, then resets, takes 2-3 seconds to show back up, then runs normally. The problem is that it’s just annoying to have it flash in and then blank, then come up and run.

@sdetweil The only modules I’d have animating is the pages module.

I’m not finding any way to change the animation/fade on MMM-Pages - I’d like to change it to something else - It appears to be the default that is system wide.

Anyone know how to change it?

Thanks

I have MMM-pages (@sdetweil 's version) and MMM-EmbedURL (@wishmaster270) - working together on my system. Evertthing is great, EXCEPT this code below.

What happens is that the website at my docker is loading, then it stops itself and reloads - blanking the screen area for 2-3 seconds while it thinks about it. Unfortunately, even though it’s a docker container and I have “Full control” – it is a very rudimentary program - and the web API is weak at best (Thus the turning off of the time stamp, etc)

What’s going on here? Is there anything I can do to keep it from blanking and restarting (I think when it’s hidden it’s paused?)

If it helps, the page is this program -> https://www.clearskyinstitute.com/ham/HamClock/ - you can look around for suggestions.

Thanks.

	{
    		module: "MMM-pages",
    		config: {
      			modules: [
        			["page1"],
        			["page2"],
        			["page3"],
      			],
      			animationTime: 2000,
      			rotationTime: 10000,
      		}
      	},
		{
			module: "MMM-EmbedURL",
			position: "top_right",
			classes: "page2",
			config: {
				updateInterval: 3600,
				animationSpeed: 0, 
				appendTimestamp: false,
		
				embed: [
					"http://docker.local:8081/live.html",
					
				],
			},
		},

(any malformed JS above is a paste error, it is correct in code)

@mumblebaj Course, I just switched back to X11 for now. 🙃

@Future-Mirror It may be wayland causing that - Try this:

sudo raspi-config

then use
option 6 “Advanced options”,
option A6, “Wayland”, then
option W1 “X11”
and approve the change.

This will switch you over to the old screen design system, where the instructions in the documentation is known to work.

If you would like, I’d be happy to share my configuration files up to the modules and how I did it. Let me know.

@DarrenO-0 Ahh, gotcha. Yes, this is for two on the same system, which linux treats as one huge monitor.

As I rewrote that section in the docs - I’ll give a (semi) live example (My second mirror is down due to lack of space, I’m working on a solution) - this is what works for me at the moment. I do realize I’m doubling up on some things.

In my Pi’s config, I also reverted to X11 desktop rather than wayland for reasons unrelated. I have not tested this on Wayland.

---

mm.sh

cd /home/bkey1970/MagicMirror
DISPLAY=:0 npm start

mm2.sh

cd /home/bkey1970/MagicMirror
export MM_CONFIG_FILE=config/config2.js
export MM_PORT=8081
DISPLAY=:0 npm start

the start of config.js:

var config = {
	address: "0.0.0.0",
	port: 8080,
	ipWhitelist: [],
	language: "en",
	timeFormat: 12,
	units: "imperial",
	//logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
	modules: [

The start of config2.js:

var config = {
	address: "0.0.0.0",
	port: 8081, 
	electronOptions: { 
		x: 1920
	},
	ipWhitelist: [], 
	language: "en",
	timeFormat: 12,
	units: "imperial",
	//logLevel: ["INFO", "LOG", "WARN", "ERROR", "DEBUG"],
	customCss: "css/custom2.css",
	modules: [

PM2 commands to tie it all together:

pm2 start /home/<username>/<path>/mm.sh --name "MM Main"
pm2 start /home/<username>/<path>/mm2.sh --name "MM 2nd"
pm2 save