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.

@sdetweil

I thought I had tried setting it to 0, but apparently I hadn’t. Now that I have made that change, it is working fine.

The filetype for HEIC is supposed to “image/heic”. I added that to the enabledTypes array in node_helper.js and it now it is also working!

Awesome, as always, thank you Sam!

@sdetweil It’s working great now. No longer freezing on image files that it cannot open. And it is properly reflecting the error with the file name in the console! THANKS!

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!

@sankum probably not the fix you needed, but I avoided this issue by giving one calendar read access within Google to the other.

@sdetweil It’s working great now. No longer freezing on image files that it cannot open. And it is properly reflecting the error with the file name in the console! THANKS!

@sdetweil great, thanks. I’ll let you know how it goes.

@sdetweil I’m not seeing any errors in the console.

@sdetweil this is what I did which is creating an uncaught syntax error on the line with the first “{”.

	img.onerror(){
	this.updateDom()
	}
        img.onload = (evt) => {
          // Get the image of the event
          const eventImage = evt.currentTarget;
          Log.log(
            `image loaded=${eventImage.src} size=${eventImage.width}:${eventImage.height}`

@sdetweil if it helps when I dig into the elements it shows:

<img src="/MMM-ImagesPhotos/photo/module_9_MMM-ImagesPhotos/IMG_3259-Copy.HEIC" style="left: 0px; position: relative; opacity: 0;">

So it thinks it is loading the file.

@sdetweil yes I’ve been looking at it. If it works I’ll get a message that the image loaded and link, image setting size … , and setting top. If it doesn’t it won’t show anything.

@sdetweil I am still have trouble with some of the HEIC files.

If the module runs across an unsupported HEIC (or corrupted jpg) file it will just stop and continue showing the last image.

I couldn’t find any log or error for files that won’t open. I’ve compared the files it can and can’t open and don’t see any difference in the file details or exif data. Is there a way to have it just skip the unsupported file?

The module does get locked up, it will not continue with a new image even after the update interval has passed. Thanks for your help.

@sdetweil

I thought I had tried setting it to 0, but apparently I hadn’t. Now that I have made that change, it is working fine.

The filetype for HEIC is supposed to “image/heic”. I added that to the enabledTypes array in node_helper.js and it now it is also working!

Awesome, as always, thank you Sam!

Hi,

Two questions really. I’ve noticed in MMM-ImagesPhotos that an image will flash off and on before it is replaced with a new image. My config looks like:

{
	module: "MMM-ImagesPhotos",
	position: "fullscreen_below",
	config: {
		opacity: 0.9,
		animationSpeed: 500, // was 500
		updateInterval: 120000,
		backgroundColor: 'rgba(0,0,0,.3)',  // not used if fill is true
		fill: false,   // fill around image with blurred copy of image
		blur: 10,   // only used if fill is true
		sequential: false  // process the image list randomly
	}
},

Any idea what would cause the picture to flash black then return and then transition to the new photo?

The second question: I’ve noticed that HEIC images are skipped and not shown at all. I’m still running Buster and although I can see an HEIC image with image viewer I’m not able to with Chromium. Is there a way to see HEIC images with MMM-ImagesPhotos?

Thanks for any help!