@sdetweil Thank you, Sam.

i STRONGLY recommend NOT USING pm2 while you develop your system

Thanks for the tip. I am not using pm2 yet — I figured that would be the last step once everything is stable and I transfer everything to my actual screen / frame / final position in the kitchen.

ctrl-r only refreshes the browser side.

Thanks — I was unsure if this stuff runs locally in-browser or if there was a server component. In any case, ctrl-q followed by npm start should clear anything browser side and reload everything server side, right? Or am I starting multiple instances here? Is there a better set of commands I should be using during development?

if a module has a node helper and it was not loaded at npm start time, the node helper will not be loaded by ctrl-r

Should there be an obvious entry in the log for helpers that are NOT loaded?
Is it common for helpers to not get loaded and how can I check why they failed to load?

Thanks again for all your help. I really appreciate it!

@sdetweil

Thanks for your reply.
I don’t see any errors but then I’m not sure if I’m in proper debug mode.
I’ve added "DEBUG" to the logLevel config parameter but there is still nothing that looks like an exception or stack trace in the terminal window.

UPDATE:
Ok, so it wasn’t working yesterday but when I rebooted everything today it all started working — got the wallpaper showing from both bing and from iCloud.

BUT… here is the weird thing: this was with JUST the MMM-Wallpaper module active in my config.js. When I uncomment all of my other modules, they sit there doing nothing until I reboot, at which point they all work but the wallpaper stops loading.

SO… am I hitting some kind of memory limit? I have only been looking at MagicMirror for a couple of days so I have no idea how it all works internally, but It would appear that if modules are loaded in the order they appear in config.js then I am running out of memory at some point before it gets to the end.
On top of that, it appears that once modules have been loaded once they don’t release that memory even if I change my config.js and reload (ctrl-r) or restart (ctrl-q followed by npm start).
Is any of this even close to what actually happens?

I am running on a re-purposed 3B+ from an old HA build. Is it worth running MM on a newer Pi? I do have a spare 5 and I could scavenge a 4 if needed.

My modules (in order) are:

• alert
• clock
• MMM-WiFiPassword
• weather
• MMM-Flights
• MMM-AnyList
• calendar
• MMM-Wallpaper
• MMM-CalendarExt3

I was looking to add motion detection and some kind of paging/scene change mechanism to cycle between Mirror — Family Info Hub — Photo Frame — and back to Mirror mode, based on a combination of motion detected and time.

I’ve spent the afternoon staring at this and I just can’t see what I’m doing wrong.

I’ve followed the instructions and installed, re-installed, updated, deleted and re-installed MMM-Wallpaper, but whenever I add a config item for it, I get nothing.
If I attach it to a position with my other modules then the entire section gets blanked out.
If I use fullscreen_below then nothing shows, no matter how long I wait.

I ultimately want to use iCloud Shared Albums for this but right now, in order to find out what’s wrong I’ve pared it back to just the bing source, as per the example. Nothing.

My config is simply:

{
	module: "MMM-Wallpaper",
	position: "fullscreen_below",
	config: { // See "Configuration options" for more information.
		source: "bing",
		slideInterval: 60 * 1000
	}
},

What am I missing?