MMM-GooglePhotos

A Former User

@teitlebot yes but… image itself will not be rotated by frames direction. It should be rotated again by direction. Think about it. It is totally different work.

A Former User

@teitlebot
There could be some issues.

Just rotation will not be what you expect

Unfortunately, as far as I know GooglePhotos remove all your EXIF and it’s metadata has no direction info. So cannot catch the photo direction.

With local stored original photos (or in Dropbox), it might be able to be done.
But it would be totally different program.

teitlebot

@Sean cant you also catch the direction by height/width?

A Former User

@teitlebot
impossible only with width/height. Imagine some pictures in your mind and rotate it. :D
Or…

Which direction should this photo be rotated? clockwise? counterclockwise? How can we know the direction with only width/height?

teitlebot

@Sean Interesting but Google Photos already rotates the picture correctly for us before it sends it to the mirror. So assuming it shows correct in the google photos album it will be correct in the mirror. Now take any picture that is width/height >1 and rotate the picture one way and rotate the screen in the opposite direction and it should work.

A Former User

@teitlebot
If so, you can do that without notification. Just add eventlistener to target photo container element and check whether src be changed. Then you can activate xmlHTTPrequest to send request to your IFTTT server.

teitlebot

@Sean Thank You. Will learn up on this and see if I can do it myself

mirrorman2

Brilliant module - thanks for the development.

I am trying to get two instances of this module running on one magic mirror, so I can show one photo at the top and one at the bottom.

I have copied the module into a different folder, renaming it (and in the CSS files as necessary). I also set up a separate google API project and separate authorisation to see if that was an issue.

Both modules run, but the photos get loaded one on top of the other despite having different positions:

modules: [

{
  module: "MMM-GooglePhotos",
  position: "top_center",
  config: {
    albumId: "blanked for posting", // your album id(s) from result of `auth_and_test.js`
    refreshInterval: 1000*20,  
    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: "800px", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
    showHeight: "400px",
    originalWidthPx: 1024, // original size of loaded image. (related with image quality)
    originalHeightPx: 728, // 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.
  }
},



{
  module: "MMM-GooglePhotos2",
  position: "bottom_left",
  config: {
    albumId: "blanked for posting", // your album id(s) from result of `auth_and_test.js`
    refreshInterval: 1000*15,  
    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: "1024px", // how large the photo will be shown as. (e.g;'100%' for fullscreen)
    showHeight: "728px",
    originalWidthPx: 1024, // original size of loaded image. (related with image quality)
    originalHeightPx: 728, // 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.
  }
},


]

};

Any ideas where I have gone wrong? Thanks!

A Former User

@mirrorman2
Each instance would be rendering different doms but they have same “Id”. That would make this behavior. Sorry, I haven’t considered duplicated instances on development.
If you want duplicated instances, modify source where “id” is used.
By example;
wrapper.id = “GPHOTO”

stephaniesal

This post is deleted!