FWIW, I did manage to do this. I added a line 155 to the MMM-BackgroundSlideshow.js:

image.src = encodeURI(this.imageList[this.imageIndex]);
this.sendNotification("IMAGEFILEPATH", image.src); //my stuff

Then I created a small module that displayed the notification.

Module.register("MMM-ShowMessage", {
	defaults: {},
	getDom: function() {
		var element = document.createElement("div");
		element.className = this.config.size;
		element.id = "IMGPATHFILE";
		return element;
	},
	notificationReceived: function(notification, payload, sender) {
		switch(notification) {
			case "IMAGEFILEPATH":
			        var elem = document.getElementById("IMGPATHFILE")
				var subpayload = payload.substring(53)
				elem.innerHTML = subpayload
				break
		}
	},
});

In my config.js I just added:

{
	module: "MMM-ShowMessage",
	position: "bottom_left",
		config: {
			size: "small"
			}
},

Now each time the image changes a notification is sent and picked up by the show message module which displays it on screen. I trim the path because the beginning was consistent among all the pictures.

n43 Boston, MA

I’ve been using MMM-BackgroundSlideshow, it allows me to randomly display an image from 1000’s stored in a many level folder structure on my NAS.

@jrotondo I’m using AlexaOnOff which allows me some control over MM.

Here is the thread.

@anthony Hi, I found this post maybe it will help? Also, custom.css is for all modules is in the css directory.

@strawberry-3-141 said in MMM-forecast-io -- Localized up to the minute weather:

.MODULENAME {
  transform: scale(0.5, 0.5);
}

if you replace modulename with your actual module name, this should give you a height and with of 50% of the actual size

@tanvir586 I’m no longer using the module, but this was an issue for me. I don’t remember the exact setting, but it helped to reduce the rate of refresh requests to the thermostat.

Re: MONITORON on does not work in schedule

So for the last two days, this has been working correctly. I think it may be a combination of @dazza120 fix to my config, not messing with the pi for a full 2 days to let it fully run through it’s schedule, and removing openGL.

Hi,

New here, just got an RPI and am thrilled with it, MM and the 3rd party modules. I’ve set up MMM-BackgroundSlideshow to randomly show backgrounds from a few thousand pictures on my NAS. Every once in a while I see an image that I’d like to remove or edit. Is there a way to get the image filename to show somewhere on the display? (I’m not much of a coder)
Thanks!

@blouzbee looks great!

@tanvir586 if you are not already using remote control it’s not worth the bother. I was already using it, so instead of restarting MM I would just hide and immediately display the nest module, that seemed to get it working again. Hope someone can help you out.

@tanvir586 Sorry, beyond my expertise. I remember I could use the remote control module to hide and display the nest module, and that would cause it to work again. That’s a bit better than restarting, but still not a fix.

@tanvir586 I’m no longer using the module, but this was an issue for me. I don’t remember the exact setting, but it helped to reduce the rate of refresh requests to the thermostat.

It’s been 24 hours and still working fine! Thanks!

@sdetweil just got the update, I’ll let you know what I find. Thanks!

Based upon the display, it stopped on me last night. I was running mm serveronly so I could see the dev output in browser. I couldn’t find any errors. It could have stopped when scheduler is set to hide all modules. I did see this in the console after this mornings schedule to show modules:

Whoops! There was an uncaught exception...
TypeError: Cannot read property 'statusCode' of undefined
    at Request._callback (/home/pi/MagicMirror/modules/mmm-nest-status/node_helper.js:20:25)
    at self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at Request.onRequestError (/home/pi/MagicMirror/node_modules/request/request.js:881:8)
    at emitOne (events.js:116:13)
    at ClientRequest.emit (events.js:211:7)
    at TLSSocket.socketErrorListener (_http_client.js:401:9)
    at emitOne (events.js:116:13)
    at TLSSocket.emit (events.js:211:7)
MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?

In the past I don’t think I ever had a conflict between scheduler and nest status.

I tried to open the console via remote but wasn’t able to. Sorry.

Bummer, mine has stopped as well.

I also have been having the same issue with this module. It worked well for months. I’ve just been restarting and haven’t had time to chase down the errors.