MMM-GooglePhotos

[bowlofred]

@wumpst If you look at the logs, you should see the count of photos in the folder every time it scans. Do they show a scan and is the count of photos increasing (and correct)?

[A Former User]

@wumpst it means scanning will repeat in every 1000x60x10 milliseconds (10minutes)

[wumpst]

@bowlofred where do I find the log?

[bowlofred]

@wumpst Depends on how you start it. If you run node serveronly (what I usually do for debugging), you’ll see it on your commandline. If you start it with pm2, it’ll probably be in ~/.pm2/logs. See https://github.com/MichMich/MagicMirror/wiki/Module-Debugging.

[krishnatnl]

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

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

2. Can I add different albums (example: Travel; Wedding; Food) and make it work random?

3. 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]

@krishnatnl

1. 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",
...

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

3. What sort method are you using?

[A Former User]

@bowlofred

1. 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.
2. Not possible at this moment, but I’m considering that feature.
3. For last photo repeat issue : No. I think it might be bug. But on my test it didn’t happen. I’ll look inside.
4. 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

1. Thanks for your reply. I will set the Interval as you said.
2. Regarding multiple albums - Now i get it based on your reply and Sean’s reply.
3. 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.