MagicMirror² v2.14.0 is available! For more information about this release, check out this topic.

MMM-GooglePhotos now says 'Loading...' in bottom right

  • 2 things have changed since my Google Photos module stopped working.

    1. I change my Google Password
    2. I updated MMM-GooglePhotos

    For 1 deleted the token.json and went back through the authorization routine. Got a new token and authorized the app. Nothing out of the ordinary there

    For 2 did a normal update (git pull, npm install, …)

    Now I have no images and ‘Loading…’. It’s been this way for 24 hours.


  • Module Developer

    Check your log what happened.

  • Hey @0YXmEQ , were you able to fix this?

    @Sean , where can I find the log? Thanks

  • @NathTheDude
    MESA-LOADER: failed to retrieve device information
    in my /home/pi/.pm2/logs/mm-error.log

    Looking into that it’s a libGL error not sure if that’s it.

    apt-get upgrade didn’t fix it digging deeper

  • magicmirror@2.10.1 start /home/pi/MagicMirror
    ./ “dev”

    [18:16:17.394] [LOG] Starting MagicMirror: v2.10.1
    [18:16:17.426] [LOG] Loading config …
    [18:16:17.447] [LOG] Loading module helpers …
    [18:16:17.453] [LOG] No helper found for module: internet-monitor.
    [18:16:17.456] [LOG] No helper found for module: alert.
    [18:16:17.639] [LOG] Initializing new module helper …
    [18:16:17.642] [LOG] Module helper loaded: updatenotification
    [18:16:17.645] [LOG] No helper found for module: clock.
    [18:16:18.582] [LOG] Initializing new module helper …
    [18:16:18.584] [LOG] Module helper loaded: MMM-GooglePhotos
    [18:16:18.587] [LOG] No helper found for module: MMM-forecast-io.
    [18:16:18.588] [LOG] All module helpers loaded.
    [18:16:18.591] [LOG] Starting server on port 8080 …
    [18:16:18.638] [LOG] Server started …
    [18:16:18.642] [LOG] Connecting socket for: updatenotification
    [18:16:18.646] [LOG] Connecting socket for: MMM-GooglePhotos
    [18:16:18.649] [LOG] Sockets connected & modules started …
    [18:16:19.103] [LOG] Launching application.
    Well that wasn’t helpful

  • Had to use the new config format on the in the module readme. Now it’s working in the top_right working through how to use the custom.css to make it the background image.

    position: “fullscreen_below” //Still works good enough for now

    Is this how custom.css is done?


    .clock {
    padding: 10px;
    background-color: rgba(0, 0, 0, 0.5);

    body {

  • Module Developer

    So, still have problem? Or tell me more details what you have done and what you have expected and what you get now. Screenshot will be also the help to understand the problem.

Log in to reply