MMM-GooglePhotos

krishnatnl

@Module-Developers
I started with magicMirror and need to understand the following:

I want a picture to be displayed every minute (using it as photo frame). What should be the best Refresh and Scan Interval considering the API quota limit.
Can I add different albums (example: Travel; Wedding; Food) and make it work random?
Once the photos scan is done, the last photo scanned is displayed continuosly. Is there a repeat feature once the last photo is scanned?

A Former User

@krishnatnl
Tomorrow I’ll research then I’ll leave my reply.

bowlofred

That’s what I do. I just used the default scan interval (10 minutes) and set the refresh to 1 minute.

...
                                refreshInterval: 1000*60,
                                scanInterval: 1000*60*10,
                                sort: "random",
...

I’m not aware you can use multiple albums. I just add any photos I want to display on a separate “magicmirror” album. The photos are simultaneously in multiple albums. That gives me control over what’s displayed, but it does mean I have to manually add everything into all the albums I want.
What sort method are you using?

A Former User

@bowlofred

10,000 requests per project per day is allowed. In my calculation, 10 minutes as scanInterval is enough. Not only too short interval but also longer interval could be also problem, because temp URL of photo doesn’t live long. I fix scanInterval over 10 minutes to 10 minutes.
Not possible at this moment, but I’m considering that feature.
For last photo repeat issue : No. I think it might be bug. But on my test it didn’t happen. I’ll look inside.
sort algorithm is here; https://github.com/eouia/MMM-GooglePhotos/blob/master/node_helper.js#L112

EDITED
2-1. Suddenly I’ve remembered why I didn’t make that feature. It was related with API quota. Since multi-album searching is not supported by API, module should scan each album on every scan time. It can consume API quota very soon. So I thought it could be problem on real usage.

krishnatnl

@bowlofred

Thanks for your reply. I will set the Interval as you said.
Regarding multiple albums - Now i get it based on your reply and Sean’s reply.
I am using Random as the sort method.

@Sean
Thanks for response to all the questions.
Regarding the Scan Finishing issue, I will try to change the Sort method and try again.

Reason for asking multiple albums - I take family pics from 2 phones. Both syncing pictures to 2 different Google accounts. So there will be 2 albums. They are all automated and easy. I will work around by sharing one account into another, create an auto-album called ‘MagicMirror’. This should solve the issue.

A Former User

@krishnatnl
If multi-albums could be supported, multi-albums from different accounst would make a problem about managing 2 auths. It might be possible, but I have some doubt about whether it is really needed and useful.
As you’ve said, shared album would be a better solution. At the moment when I created this, I was regarding that usage.
Until now, I have half forgotten this module. After solving more urgent issues from my real life, I promise I’ll examine what lays about your scan finishing issue. Could you send me your configuration(without auth info) about this module via email? My email address is eouia0819@gmail.com. And tell me how much photos in your album also.
Thanks.

krishnatnl

Thanks @Sean
Will send in the config tonight in email.
I think Shared Album should work. Will try that once I find some time over weekend.
I have 3K pictures for now from one phone. More coming from other device (another account which I will try to put in shared album).

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.