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

@jconno03 Awesome!

@sdetweil That’s awesome, thanks!

@sdetweil Yes, sorry that’s what I had read about. So is the MagicRemote a PWA, or just a shortcut. Just hoping it doesn’t go away, I’ve found it pretty useful.

I’ve been using MagicRemote which I believe is part of RemoteControl app. I just read that IOS 17.4 is going to remove the ability to run personal web apps. Will this shut down MagicRemote?

I use MMM-BackgroundSlideshow for this. I like that it can display picture info. It also has the ability to move forward and back through the pictures, although it seems to have a problem with that in the latest version. I use it to randomly access thousand of images across many folders.

@whimsicality I have the MMM-Nest-Status module working. I set it up a couple months ago. I followed the pretty detailed process he laid out. I remember part of it didn’t seem to work, I had to back out or close something, but was able to get the needed Client ID, Client Secret, Project ID, and Refresh Token. It was confusing enough that I don’t think I could help walk you through, but I can at least confirm that it does work. It worked at the start and then started giving me authentication failed errors. It may have been a wifi issue, they seem to have gone away on their own.

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