@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