MMM-GooglePhotos

bowlofred

@sean You mention 10,000 requests per day. Does the number of requests go up with the number of photos in the album? If the album had 1000 photos, would that be a problem? Or is that fine as long as the photos aren’t changing too often?

A Former User

@bowlofred
If you have 1000 Photos in an album, and scanning per 10 minutes

on each scan; 20 API quota will be consumed. (max items driven per request are 50)
for 24H running, 144 scans will be performed.
Total consumption : 20 * 144 = 2880 APIs
Around 3000 photos could be safely scanned with 10min scan cycle.

However after this calculation, I think I’d better to add a feature to suspend and resume for unused(or hidden) module status.

A Former User

@krishnatnl
See above post.
I think your problem might be caused by number of photos. API request quota might be over the limits. It could not get new photos from server, so last picture is only you could have at the moment.
I’m guessing how to solve this kind of problem now. Hmmm…
Growing scanInterval up is not so safe, Because Life of temp url of photo is somewhat short, the url could be expired. Hmmmm… difficult.

krishnatnl

@Sean :
Got the scan calculation of how you got 2880 . thanks.

Question:
Does the Scan calculation mean If scanned every 10 mins, a total of 2880 photos will be scanned in 24 hours?

If refresh Interval is every 1 minute, then 60*24 = 144 photos out of the 2880 photos will be shown?

A Former User

@krishnatnl
1api request could get 50 pics. 1000 pics need 20 api request. (1 scan)
1440scan(1min for 24h) needs 28800 api requests. Thats quota over.

uzair82

Hello,
I have installed this module and all options are working Except Fullscreen. When i setup to 100% nothing appears in Google Photos.
If i set resolution manually it works fine. what could be the reason.
Here is the setting.

 sort: "time", //'time', 'reverse', 'random'
    showWidth: "100%", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
    showHeight: "100%",
    originalWidthPx: 1024, // original size of loaded image. (related with image quality)
    originalHeightPx: 768, // Bigger size gives you better quality, but can give you network burden.
    mode: "cover", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)

A Former User

@uzair82 There is no reason not to work. Where(position) did you put your module for fullscreen?

krishnatnl

@sean
This is working fine now.
Below is my config snippet:

refreshInterval: 1000*30,  
scanInterval: 1000*60*60, // too many scans might cause API quota limit also.
//note(2018-07-29). It is some weird. API documents said temporal image url would live for 1 hour, but it might be broken shorter. So, per 10 min scanning could prevent dead url.

sort: "random", //'time', 'reverse', 'random'
showWidth: "100%", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
showHeight: "100%",
originalWidthPx: 1920, // original size of loaded image. (related with image quality)
originalHeightPx: 1080, // Bigger size gives you better quality, but can give you network burden.
mode: "cover", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)

Question:
My monitor is in Landscape mode. My Landscape pictures displays fine (Fitting exactly in screen). But portraits display in full size cropping the pic mostly and in an expanded view. Only part of image is visible since it large.

Is there a way to “Fit the picture into the screen” when it is Portrait just like Landscape? I tried other mode. It is too small and has borders. I want the pic to fit exactly in the screen.
My monitor is 22 inch, Full HD (1080P) if that helps.

A Former User

@krishnatnl
Fit the picture into the screen has obvious meaning.
Portrait image in Landscape Area (and vice versa) Is something like real pictures in real photoframe, you cannot fit your portrait picture into the landscape frame without cutting(mode:cover) or extra margin of both left&right sides(mode:contain). The bigger difference of ratio makes the more uncomfortable looks.
Could be the 3rd option? Give me a suggestion.

PS
I thought options available to consider :

stretch the width of portrait picture fully to fit to landscape area. It makes your person in portrait looks like a hobbit.
cut the top and both moderately and also stretch horizontally not too much. Not displaying entire image and not covering whole area, but it will look nicer than current issue. The only problem is, where to cut and how much to expand is not be done automatically.

Is there any idea?

krishnatnl

@Sean
Maybe i did not explain properly. I need a layout for the portrait oriented pictures to fit in the screen without disturbing the aspect Ratio.

MODE:COVER

Works perfectly for the landscape oriented pictures since it is fitting the picture perfectly in the screen. There is no stretch or crop.

Portrait oriented pictures are cropped to landscape orientation (technically).

MODE:CONTAIN

Works fine for the portrait oriented pictures i.e: The full image is visible in the screen, no crop, no stretch

Landscape pictures are also displayed without crop, but there are borders.

Need something like this:
If the pic is a Landscape oriented one, Mode should be COVER, else should be CONTAIN.
In Other words, need an AUTO-SCALING option.

From a programming perspective, is this feasible? If not, I will try the COVER mode but not liking black borders for all the images.

A Former User

@krishnatnl
In my MMM-DropboxWallpaper, I applied already that feature(automatically changing mode by ratio). I have been doubting whether it has really usefulness in real usage. Anyway I’ll consider this feature in this module too.

A Former User

@krishnatnl
I’ve updated. mode:hybrid is available for changing mode:cover or mode:contain automatically by aspect ratio.

krishnatnl

This working fine and solved my issue @Sean . Happy Holidays :)

krouton

Hi Sean,

I keep getting the “[GPHOTO] Scan finished : 0/There is no scanned photo currently.” error however there are 3000 photos in the folder. Sometimes it will successfully scan and display the photos fine but more and more recently it fails.

{
		module: "MMM-GooglePhotos",
		position: "fullscreen_below",
		disabled: false,
	config: {
		albumId: "xxxxx", // your album id from result of `auth_and_test.js`
		refreshInterval: 1000*60*5,  
		scanInterval: 1000*60*10, // too many scans might cause API quota limit also.
			//note(2018-07-29). It is some weird. API documents said temporal image url would live for 1 hour, but it might be broken shorter. So, per 10 min scanning could prevent dead url.

		sort: "random", //'time', 'reverse', 'random'
		showWidth: "1380px", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
		showHeight: "1060px",
		originalWidthPx: 1380, // original size of loaded image. (related with image quality)
		originalHeightPx: 1060, // Bigger size gives you better quality, but can give you network burden.
		mode: "contain", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)
  }
},

Connecting socket for: MMM-GooglePhotos
MMM-GooglePhotos started
Connecting socket for: MMM-MyCalendar
Starting node helper for: MMM-MyCalendar
Sockets connected & modules started …
Ready to go! Please point your browser to: http://0.0.0.0:8080
MMM-ModuleScheduler is removing all scheduled jobs
MMM-ModuleScheduler received CREATE_GLOBAL_SCHEDULE
MMM-ModuleScheduler is creating a global schedule for all modules using “30 6 * * *” and “00 18 * * *” with dim level 40
MMM-GooglePhotos initialized after loading.
[RCREPO] Repository scanning…
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.
[RCREPO] Repository scanning…
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.
[GPHOTO] Scan finished : 0
There is no scanned photo currently.
[RCREPO] modules.json is updated.

Inspector shows it loads the module but not an actual photo.

Any help would be greatly appreciated.

A Former User

@krouton
Move to some smaller folder than try again. 3000 would be so many photos, and ther could be more in your subdirectories.

A Former User

@krouton
By the way, sorry for out of topic, but…
RCREPO seems too many times working. Scanning should be executed at start of MM once. Why did the log say so many times?
Would you try again after removing MMM-Remote-Control-Repository from config.js??

yupwho

@Sean , thanks a ton for this great module. My wife would have never been ok with a Smart display in our family room without having family pictures on it.
I have MMM-Google photos on full screen mode (monitor is in portrait mode). It works perfectly as expected - although the pictures come up as pixelated or not as sharp in lower resolution. All photos in my configured album are uploaded in full resolution. Is there any way to display it in high(est/er) resolution?

My configuration is as below:-

		{
		  module: "MMM-GooglePhotos",
		  position: "fullscreen_below",
		  config: {
		    albumId: "XXXXX", // your album id from result of `auth_and_test.js`
		    refreshInterval: 1000*60,  
		    scanInterval: 1000*60*10, // too many scans might cause API quota limit also.
		    //note(2018-07-29). It is some weird. API documents said temporal image url would live for 1 hour, but it might be broken shorter. So, per 10 min scanning could prevent dead url.
		
		    sort: "random", //'time', 'reverse', 'random'
		    showWidth: "100%", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
		    showHeight: "100%",
		    originalWidthPx: 1920, // original size of loaded image. (related with image quality)
		    originalHeightPx: 1080, // Bigger size gives you better quality, but can give you network burden.
		    mode: "hybrid", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp)
		    //ADDED. "hybrid" : if you set as "hybrid" it will change "cover" and "contain" automatically by aspect ratio.
		  }
		},

bhepler

@yupwho - Hmm. If you uploaded at full resolution, they are probably higher than 1920x1080. Specifying those parameters may be causing some weird resizing artifacts.

As an experiment, trying taking out the orginalWidthPix and originalHeightPx parameters and see what you get.

yupwho

@bhepler Thanks! Removing it seemed to worsen the quality. I think I am going to experiment with different values here - https://en.wikipedia.org/wiki/Display_resolution#Common_display_resolutions.
I have tried the 2560*1440 and it looks little bit better.

Still looking if there is a more definite solution.

Thanks!

A Former User

@yupwho
Set originalWidthPx and originalHeightPx to higher value.

But dithering would be unescapable destiny. Because Max Screen Size of supported in RPI would be 1920*1080 and your pictures are larger than, so Dithering should be happened.

Usually Dithering - Scaling up/down, by index of 2 (e.g: X2, X4, X1/2, X1/4) would be better than other values.
So, dithering to 800X480 from 1600x960 could be better from 2000X1200.

And I think the best values would be the same size to display.
Because, if dithering would be happened, it would be done twice - once when your Google Photo send picture to RPI by OriginalWidth/Height and once again when my module showing it by showWidth/Height.
So, The best case would be all the same sizes - your picture original, OriginalWidth/Height, showWidth/Height are same. In other case, somewhat quality down is unavoidable. My module has no correction/manipulation method because this is not photoshop. sorry.