Read the statement by Michael Teeuw here.
Config file not working when i add MMM-GooglePhotos
-
@sdetweil sorry yep i did that once i notice the issue were i placed still the same
-
@paddyhughes change to tests/configs folder and run
node check_config.js
-
@sdetweil said in Config file not working when i add MMM-GooglePhotos:
@paddyhughes change to tests/configs folder and run
node check_config.js
Not sure what the tests/configs folder is. Do you want me to back up the folder and run node check_config.js
Sorry about this and thanks for your help
-
Inside the mm folder is the tests folder, etc
-
@sdetweil Line 61 col 149 Unclosed string.
Line 62 col 32 Unclosed string.
Line 63 col 82 Unclosed string.
Line 64 col 183 Unclosed string.
Line 65 col 1 Unclosed string.
Line 66 col 48 Unclosed string.
Line 67 col 17 Unexpected ‘8’.
Line 60 col 3 Expected ‘}’ to match ‘{’ from line 57 and instead saw ‘config’.
Line 60 col 9 Expected ‘]’ to match ‘[’ from line 28 and instead saw ‘:’.
Line 60 col 11 Expected ‘}’ to match ‘{’ from line 11 and instead saw ‘{’.
Line 60 col 12 Missing semicolon.
Line 61 col 14 Label ‘albumId’ on [ statement.
Line 66 col 12 Expected ‘]’ to match ‘[’ from line 61 and instead saw ‘time’.
Line 66 col 12 Expected an assignment or function call and instead saw an expression.
Line 66 col 16 Missing semicolon.
Line 67 col 1 Expected an assignment or function call and instead saw an expression.
Line 67 col 17 Missing semicolon.
Line 68 col 17 Label ‘showHeight’ on 600px statement.
Line 69 col 5 Expected an assignment or function call and instead saw an expression.
Line 69 col 20 Missing semicolon.
Line 69 col 5 Unrecoverable syntax error. (72% scanned). -
Start at the first error, fix and try again
-
@sdetweil Thanks
Went true it and fixed the issues [MY CODE ************* ]
needed to be removedWorking Config for MMM-Googlephotos
{ module: "MMM-GooglePhotos", position: "top_right", config: { albumId: "MY CODE ******************************", // your album id 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: "time", //'time', 'reverse', 'random' showWidth: "800px", // how large the photo will be shown as. (e.g;'100%' for fullscreen) showHeight: "600px", originalWidthPx: 800, // original size of loaded image. (related with image quality) originalHeightPx: 600, // Bigger size gives you better quality, but can give you network burden. mode: "cover", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp) } },
-
-
-
@paddyhughes said in Config file not working when i add MMM-GooglePhotos:
@sdetweil Thanks
Went true it and fixed the issues [MY CODE ************* ]
needed to be removedWorking Config for MMM-Googlephotos
{ module: "MMM-GooglePhotos", position: "top_right", config: { albumId: "MY CODE ******************************", // your album id 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: "time", //'time', 'reverse', 'random' showWidth: "800px", // how large the photo will be shown as. (e.g;'100%' for fullscreen) showHeight: "600px", originalWidthPx: 800, // original size of loaded image. (related with image quality) originalHeightPx: 600, // Bigger size gives you better quality, but can give you network burden. mode: "cover", // "cover" or "contain" (https://www.w3schools.com/cssref/css3_pr_background-size.asp) } }, ```I think you. Would need to changing screen size it mite make a difference if