MMM-GooglePhotos+MMM-NFL=WTF-Refresh Rates?

[JeffreyDaro]

I am working to get the MMM-GooglePhotos module working on my first MM project. I have noticed that I get odd refreshes of the images sometimes. An image may be displayed for 10-15 seconds, or 1-2 seconds before the next image is displayed. No rhyme. No reason.

I figured it was something I was doing wrong, but then over the weekend I installed the MMM-NFL module. Love it. Real time game updates across all divisions? Awesome. But then…I realized that my photos were no longer showing up because I hit my API peak. Huh? How?

Tonight, I experimented and removed the MMM-NFL module. My photos now refresh about every 30 seconds. My refreshInterval is set to 1000 * 60, so I thought this should be every 60 seconds, but at least I am at a consistent refresh rate.

My hypothesis is that when an NFL game is going on, the MMM-NFL module is updating like crazy, and that is triggering notifications causing other modules to fire and refresh.

As I mentioned above, this is my first foray into MM, so I may be off base…but…am I?

[MMRIZE]

@JeffreyDaro
As an original author of GP,(I delegated the ownership a few years ago) if not many things changed;

• the default updateInterval would be 1000 * 30. If you set refreshInterval, the wrong term, so would be ignored.
• updateInterval:30_000 doesn’t mean that displaying a new photo every 30 seconds. The exact meaning is “After 30 seconds, requesting a new photo” , So the internet speed and the filesize to transfer affect the real taken time for new image.
• undocumented scanInterval may affect your certain weird too-short-life of the image symptom. Due to Google Photo’s API condition, each image only has short-life url to be used. To prevent lost its validity, the module needs to rescan repeatedly. The issue may lay on this; After rescan and initialize the list of image, previous list might be replaced with new one, at that time your symptom might happen. Sorry, not clear solution at this moment.

For MMM-NFL things, I have no idea.

[JeffreyDaro]

@MMRIZE, I appreciate you taking the time to respond. I will double check my settings, but what you are describing sounds like what I am seeing. Maybe the NFL module+This Module theory was a bit premature. I will tweak my settings, and give it a go.

Thank you for this module, it is wonderful.

[MMRIZE]

@JeffreyDaro
To save the daily quota,

• Specify the album to scan, not whole or many albums. Scanning will consume your Quota, And the number of files in target albums will also affect consumption.
• You can only show 8640 pictures in a day at most, even with 10 seconds. With 60 seconds, you can show around 1400 pictures per day. If you have thousands of pictures in the album, unused pictures would also scanned. (scan 50 pictures would consume 1 call) It could be more efficient.
• Let’s compute: If you have 5000 pictures in your target album, you will consume 100 calls per scan, and to serve each image, at least 1 call per image would be consumed. But most of the scanned pictures would not be used at all.
• So, optimise your album. Carefully collect/select pictures to be shown with a proper number. Gather the pictures in one album like 'MM Wallpaper". Keep the number as low as possible, and assign longer updateInterval as some minutes, not seconds. It will help your quota consumption.