MMM-GooglePhotos

[mcneilp]

@mcneilp If i let it run long enough it loads an image…but sometimes it goes blank for a while. I assume this is because its processing photos. Too bad it can’t just load a few at a time and run fast.

[A Former User]

@mcneilp
Show me your config. And Google Photos has its API request limit for usage.

[gonzonia]

Sean,
It seems you make my favorite modules. I’m trying to get the GooglePhotos to work and it does if I leave it long enough. On startup though nothing shows (makes it real hard to configure the appearance). I’m seeing this in the log. Is the album I chose too big? I’m using the config you posted for fullscreen (except I changed to mode: hybrid).

Error: { Error: Client network socket disconnected before secure TLS connection was established
at TLSSocket.onConnectEnd (_tls_wrap.js:1092:19)
at Object.onceWrapper (events.js:273:13)
at TLSSocket.emit (events.js:187:15)
at endReadableNT (_stream_readable.js:1090:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
code: ‘ECONNRESET’,
path: null,
host: ‘photoslibrary.googleapis.com’,
port: 443,
localAddress: undefined }

[A Former User]

@gonzonia
well, the error log is saying just network problem. However I’m not in front of machine at this moment, but i’ll check this tomorrow

[gonzonia]

Thanks. Seems to be working now. Like I said, it starts out that way and then eventually loads fine. The album has about 900 photos I’m showing randomly. Trying to decide if I want them fullscreen or not…

[gonzonia]

@Sean It’s weird. I had it working. I went to adjust the settings (sizing didn’t look good) and then it stopped. Getting the network error consistently.

This is my latest config. I’ve tried various configurations of showWidth/showHeight and originalWidthPx/originalHeightPx

{
  module: "MMM-GooglePhotos",
  position: "top_left",
  config: {
    albumId: ["XXX"], // your album id(s) from result of 
   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: "800", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
    showHeight: "600",
    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.
  }

[A Former User]

@gonzonia
There is nothing related to your network issue on this module. (At least, I think so)
I carefully guess these things;

1. WLAN sleeping feature might be activated in your RPI.
2. Your other module or other background process would make this.

[gonzonia]

@Sean
This module is the only one not working. though and you can see in the error I posted earlier it directly references the “photoslibrary.googleapis.com” which is why I suspected this module.

Currently I’m not running over wifi so it’s not that it’s sleeping.

I’ll keep trying things and see if I can find something with some consistency. Thanks for checking.

[gonzonia]

@Sean I’m starting to think the network error is irrelevant.
I am seeing the error sometimes not related to googleapis.com. In those cases the CalendarExt2 data isn’t fully loaded, I refresh and all seems good.

The config below seems to work.

{
  module: "MMM-GooglePhotos",
  position: "fullscreen_below",
  config: {
    albumId: ["AD8YTEgKjrQhxAA_30358v4J7I7CXoa1_QIgcebrp1qLcFUvsIU5Hql3wPIvUDesZ72DYwbEhxSz"], // your album id(s) 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.
  }
  	},

Change to

 position: "top_left",
showWidth: "800",
showHeight: "600",
originalWidthPx: 800,
originalHeightPx: 600,

and it doesn’t

[A Former User]

@gonzonia
Hmmmm…

With your config (but change albumId - I cannot use your albumId), I can display.

Here is mine.

{
  module: "MMM-GooglePhotos",
  position: "top_left",
  config: {
    refreshInterval: 1000*60,
    scanInterval: 1000*60*10, 
    sort: "random", 
    showWidth: "800px", 
    showHeight: "600px",
    originalWidthPx: 800, 
    originalHeightPx: 600,
    mode: "hybrid", 
    albumId: ["AJQR3DjzfO6BkH5eSY1e6Dm3m49QVOmpmXgPy6BOecEwg-f_82H_UJ1v-dvzVIjuezDmb_snettC"],
  }
},