MMM-GooglePhotos

[kaltec-w]

I left pretty much everything default.

pi@photoframe1:~/MagicMirror $ pwd
/home/pi/MagicMirror
pi@photoframe1:~/MagicMirror $ ls ./config/
config.js  config.js_old  config.js.sample
pi@photoframe1:~/MagicMirror $

config.js_old is the original, i modified config.js to what my previous comment said.

The CSS i can deal with/remove as necessary. It was a recommendation in a different post.

This is my first foray into magic mirror, so I may be missing something simple here…

-kal

[A Former User]

@kaltec-w
Your logs looks like typical “no config” case. But as I’ve seen in your last post, the file exists in right directory. Weird.
If you sespect some specific module, remove it from config.js then try again. If the result is right as your expectation, you can confirm the module has a problem.
Anyway, in the case of the configuration fail, It might spit out error message, not your previous log.

[kaltec-w]

Copying over the default config.js does indeed result in normal behavior.

With my custom config.js (with GooglePhotos), the clock is displayed but the rest of the screen is blank.

Any idea where there may be logging from that module? Do I need to post in a different forum for module-specific issues?

-kal

[A Former User]

@kaltec-w

With my custom config.js (with GooglePhotos), the clock is displayed but the rest of the screen is blank.

If so, your logs in the previous post is not matched. Check log again. Or you can stop pm2 then execute MM directly in your terminal with ‘npm start’ or ‘npm start dev’. The latter can show not only serverside log but also frontend log. It will help to diagnose.

Any idea where there may be logging from that module? Do I need to post in a different forum for module-specific issues?

If you think that is real bug-like issue, you can post it on the issue board of that module github repository. I’m the developer of that module.

[kaltec-w]

I ended up removing the ~/MagicMirror folder entirely, reinstalling, and reinstalling MMM-GooglePhotos and all seems to be working now!

thanks for your help, @Sean !

-kal