• Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
MagicMirror Forum
  • Recent
  • Tags
  • Unsolved
  • Solved
  • MagicMirror² Repository
  • Documentation
  • 3rd-Party-Modules
  • Donate
  • Discord
  • Register
  • Login
  1. Home
  2. mirrorman2
A New Chapter for MagicMirror: The Community Takes the Lead
Read the statement by Michael Teeuw here.
M
Offline
  • Profile
  • Following 0
  • Followers 0
  • Topics 0
  • Posts 1
  • Groups 0

mirrorman2

@mirrorman2

0
Reputation
107
Profile views
1
Posts
0
Followers
0
Following
Joined Mar 18, 2019, 8:57 PM
Last Online Aug 30, 2019, 3:30 PM

mirrorman2 Unfollow Follow

Latest posts made by mirrorman2

  • RE: MMM-GooglePhotos

    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!

    posted in Entertainment
    M
    mirrorman2
    Mar 18, 2019, 9:17 PM
Enjoying MagicMirror? Please consider a donation!
MagicMirror created by Michael Teeuw.
Forum managed by Sam, technical setup by Karsten.
This forum is using NodeBB as its core | Contributors
Contact | Privacy Policy