Googlr Photos not syncing with MagicMirror

sdetweil

@synint said in Googlr Photos not syncing with MagicMirror:

“MasterJH,”

hmm…that trailing comma i bet

Can't find "MasterJH,"

looks like you might have had a list and decided against it

all commands I give you are from a terminal window, or ssh session

synint

@sdetweil Hi Sam,

I have removed the trailing comma and has made no difference.

Entered the following text in terminal and got the following message:

synint@raspberrypi:~ $ f running pm2 to auto launch, then
pm2 logs --lines=50
bash: f: command not found
bash: pm2: command not found

Entered the following text in terminal and Magic Mirror started but only showing 2 images

pm2 stop all
cd ~/MagicMirror
npm start

The following is the text he terminal returned after entering the above text. I have also noticed that he Google News Feed is repeating the same two items.

10.5.0; pm2: 
### OTHER:    timeZone: Europe/London; ELECTRON_ENABLE_GPU: undefined 
[2024-04-29 19:28:18.876] [INFO]  Initialization complete! 
[2024-04-29 19:28:18.877] [INFO]  Start first scanning. 
[2024-04-29 19:28:18.880] [INFO]  Start Album scanning 
[2024-04-29 19:28:18.883] [INFO]  Getting album list 
[2024-04-29 19:28:19.725] [INFO]  Newsfeed-Fetcher: Broadcasting 37 items. 
[2024-04-29 19:28:20.767] [WARN]  Can't find "M" in your album list. 
[2024-04-29 19:28:20.769] [WARN]  Can't find "a" in your album list. 
[2024-04-29 19:28:20.770] [WARN]  Can't find "s" in your album list. 
[2024-04-29 19:28:20.772] [WARN]  Can't find "t" in your album list. 
[2024-04-29 19:28:20.773] [WARN]  Can't find "e" in your album list. 
[2024-04-29 19:28:20.775] [WARN]  Can't find "r" in your album list. 
[2024-04-29 19:28:20.776] [WARN]  Can't find "J" in your album list. 
[2024-04-29 19:28:20.778] [WARN]  Can't find "H" in your album list. 
[2024-04-29 19:28:20.798] [INFO]  Finish Album scanning. Properly scanned : 0 
[2024-04-29 19:28:20.809] [INFO]  Albums:  
[2024-04-29 19:28:20.814] [WARN]  There is no album to get photos. 
[2024-04-29 19:28:20.821] [INFO]  Next scan will be at 2024-04-29T19:23:18.879Z 
[2024-04-29 19:28:25.332] [INFO]  Calendar-Fetcher: Broadcasting 130 events from https://calendar.google.com/calendar/ical/john%40totrain.co.uk/public/basic.ics. 
[2024-04-29 19:28:31.192] [INFO]  Used last pic in list 
[3011:0429/192844.418749:ERROR:atom_cache.cc(229)] Add WM_CHANGE_STATE to kAtomsToCache
[2024-04-29 19:28:52.172] [INFO]  Used last pic in list 
[2024-04-29 19:29:12.169] [INFO]  Used last pic in list 
[2024-04-29 19:29:32.167] [INFO]  Used last pic in list 
[2024-04-29 19:30:06.212] [INFO]  Used last pic in list

sdetweil

@synint show the changed config for the album name .

albums is a list even if only one
from the doc

albums: [],

so you need

albums: ["MasterJH"],

if there were more than one album

albums: ["MasterJH", "sams list"],

synint

@sdetweil

Hi Sam, I have changed the reference to albums as detailed in your response above e.g. albums: [“MasterJH”], and still have the same issue of only two images showing.

I have now deleted MasterJH on Google Photos and and created a MagicMirror2024 folder see Config file below and when I run MagicMirror it still show the two images from the original folder even after I have deleted the folder. I am thinking may be the next step would be to rebuild MagicMirror on a new SD card and see if I cam run it without the errors. However, any other suggestions would be appreciated as I feel I am so close to getting MajgicMirror up and running.

Latest Config file

{
				module: "MMM-GooglePhotos",
				position: "fullscreen_below",
				
				config: {
				albums: ["MagicMirror2024"], // Set your album name. like ["My wedding", "family share", "Travle to Paris"]
				updateInterval: 10 * 800, // minimum 10 seconds.
				sort: "new", // "old", "random"
				uploadAlbum: null, // Only album created by `create_uploadable_album.js`.
				condition: {
				fromDate: null, // Or "2018-03", RFC ... format available
				toDate: null, // Or "2019-12-25",
				minWidth: 1366, // Or 400
				maxWidth: 1366, // Or 8000
				minHeight: 768, // Or 400
				maxHeight: 768, // Or 8000
				minWHRatio: null,
				maxWHRatio: null,
				// WHRatio = Width/Height ratio ( ==1 : Squared Photo,   < 1 : Portraited Photo, > 1 : Landscaped Photo)
				},
				showWidth: 800, // These values will be used for quality of downloaded photos to show. real size to show in your MagicMirror region is recommended.
				showHeight: 1200,
				timeFormat: "YYYY/MM/DD HH:mm", // Or `relative` can be used.
  }
},

sdetweil

@synint the module builds a cache folder… so maybe erasing that will help?

what are the log messages?

synint

@synint

RESOLVED

Hi Sam, I have resolved it and thank you, thank you and thank you it was only through your guidance and help that made me look deeper to resolve the issue.

SOLUTION

In a YouTube video I had seen it advised setting the minWidth 1366 and maxHeight to 768 this is the resolution of the TV I am using. Looking at a post on Git hub some one said change the minWidth and maxHeight to null and it does not matter what size your images are (see config file below) and after reboot everything works as it should.

Cheers,
John

{
				module: "MMM-GooglePhotos",
				position: "fullscreen_below",
				
				config: {
				albums: ["MagicMirror2024"], // Set your album name. like ["My wedding", "family share", "Travle to Paris"]
				updateInterval: 15 * 800, // minimum 10 seconds.
				sort: "random", // "old", "random"
				uploadAlbum: null, // Only album created by `create_uploadable_album.js`.
				condition: {
				fromDate: null, // Or "2018-03", RFC ... format available
				toDate: null, // Or "2019-12-25",
				minWidth: null, // Or 400
				maxWidth: null, // Or 8000
				minHeight: null, // Or 400
				maxHeight: null, // Or 8000
				minWHRatio: null,
				maxWHRatio: null,
				// WHRatio = Width/Height ratio ( ==1 : Squared Photo,   < 1 : Portraited Photo, > 1 : Landscaped Photo)
				},
				showWidth: 800, // These values will be used for quality of downloaded photos to show. real size to show in your MagicMirror region is recommended.
				showHeight: 1200,
				timeFormat: "YYYY/MM/DD HH:mm", // Or `relative` can be used.
				debug: true,
  }
},

sdetweil

@synint yes, the example in the module doc uses null. and I never set the sizes