MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    MMM-GooglePhotos

    Scheduled Pinned Locked Moved Entertainment
    294 Posts 56 Posters 297.5k Views 59 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • K Offline
      kykzzang
      last edited by

      @Sean
      I have same error with @zolabus.
      but it works very occasionally.
      Perhaps it got worse recently.

      condition :

      rpi 4B
MM 2.11.0
npm 6.14.4
nodejs 10.20.1
photo counts : about 3000

      errorlog:

      [2020-04-24 13:03:05.421] [LOG]    [GPHOTOS:CORE] Getting Album info chunks.
[2020-04-24 13:03:06.566] [LOG]    [GPHOTOS:AUTH] Token is alive.
[2020-04-24 13:03:06.567] [LOG]    [GPHOTOS:CORE] Getting Album info chunks.
[2020-04-24 13:03:07.519] [LOG]    [GPHOTOS] Finish Album scanning. Properly scanned : 1
[2020-04-24 13:03:07.533] [LOG]    [GPHOTOS] Initialized
[2020-04-24 13:03:07.535] [LOG]    [GPHOTOS] Start first scanning.
[2020-04-24 13:03:07.537] [LOG]    [GPHOTOS] Start Album scanning
[2020-04-24 13:03:07.541] [LOG]    [GPHOTOS:AUTH] Token is alive.
[2020-04-24 13:03:07.543] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:10.195] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:12.284] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:13.953] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:15.580] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:18.212] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:27.554] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:29.439] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:31.248] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:32.969] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:41.248] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:43.034] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:54.235] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:56.981] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:03:58.694] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:04:02.317] [LOG]    [GPHOTOS:CORE] Indexing photos now.
[2020-04-24 13:04:17.583] [LOG]    [GPHOTOS:CORE] Error: Client network socket disconnected before secure TLS connection was established
[2020-04-24 13:04:17.587] [ERROR]  (node:1902) UnhandledPromiseRejectionWarning: Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1355:19)
    at Object.onceWrapper (events.js:288:20)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[2020-04-24 13:04:17.589] [ERROR]  (node:1902) UnhandledPromiseRejectionWarning: Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1355:19)
    at Object.onceWrapper (events.js:288:20)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[2020-04-24 13:04:17.590] [ERROR]  (node:1902) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[2020-04-24 13:04:17.591] [ERROR]  (node:1902) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
[2020-04-24 13:04:17.591] [ERROR]  (node:1902) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[2020-04-24 13:04:17.592] [ERROR]  (node:1902) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

      config.js

      module: "MMM-GooglePhotos",
position: "fullscreen_below",
config: {
      albums: ["딸래미들"], // Set your album name. like ["My wedding", "family share", "Travle to Paris"]
      updateInterval: 1000 * 30, // 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: 1700,
      timeFormat: "YYYY/MM/DD HH:mm", // Or `relative` can be used.
      autoInfoPosition: true,
      debug: true,
},
      ? 1 Reply Last reply Reply Quote 0
      • ? Offline
        A Former User @kykzzang
        last edited by

        @kykzzang said in MMM-GooglePhotos:

        [GPHOTOS:CORE] Error: Client network socket disconnected before secure TLS connection was established

        It means, your network is not stable.

        G 1 Reply Last reply Reply Quote 0
        • G Offline
          gonzonia @Guest
          last edited by

          @Sean I’m thinking it might be something on Google’s end. I’m having the same issue.

          [2020-04-23 18:54:25.134] [LOG] 2020-04-23T18:54:25 [GPHOTOS:CORE] Error: Client network socket disconnected before secure TLS connection was established (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:124 GPhotos.log)

          Is it possible to handle this error at all? Everything works fine for hours, then this error. Then it never recovers to try again but just stays on the last photo displayed.

          ? 2 Replies Last reply Reply Quote 0
          • ? Offline
            A Former User @gonzonia
            last edited by

            @gonzonia
            I’ll add some routine for graceful logging and retry in a few days. However, network stability issue couldn’t be solved by this module.

            1 Reply Last reply Reply Quote 0
            • ? Offline
              A Former User @gonzonia
              last edited by

              @gonzonia
              For staying the last photo displayed, It is not so easy as our hope.
              Because, the URL of GooglePhotos has short term life - 1 hour. Without downloading and storing, the image will be expired. Anyway I’ll consider how to solve this problem.

              G 1 Reply Last reply Reply Quote 0
              • Z Offline
                zolabus @Guest
                last edited by

                @Sean
                Hi from npm start dev I have only this error
                [ERROR] (node:1472) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

                bheplerB 1 Reply Last reply Reply Quote 0
                • D Offline
                  dumitrudany
                  last edited by dumitrudany

                  Hi,
                  I’m using this module. Thank you for developing it. Everything seems to work normal except that it’s not scanning for new added or deleted photo from the albums.
                  I’m using the node serveronly command to start the MagicMirror2 without no errors reporting. I couldn’t figured with npm start dev. I have activated the debug, and only once it’s scanning the album.

                  Is this config parameter still working: scanInterval: 1000*60*10,?
                  As for me it isn’t and I saw it’s not described in readme doc. Or is there any other way to let the module scan automatically for new added photos?
                  I only found the way of refreshing the browsing page, which works but it’s not what I need.

                  Thanks!

                  This is my config:

                  {
			  module: "MMM-GooglePhotos",
			  position: "fullscreen_below",
			  config: {
					albums: ["TESTARE"], 
					updateInterval: 100 * 60, // minimum 10 seconds.
					scanInterval: 1000*60, //10 minutes
					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: 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: 1080, // These values will be used for quality of downloaded photos to show. real size to show in your MagicMirror region is recommended.
					showHeight: 1920,
					//timeFormat: "YYYY/MM/DD HH:mm", // Or `relative` can be used.
			  }
			}
                  ? 1 Reply Last reply Reply Quote 0
                  • ? Offline
                    A Former User @dumitrudany
                    last edited by

                    @dumitrudany
                    Not possible immediately as you wish. There is no way to detect whether you add/modify photos or not. Maybe frequent scanning would get a similar result, but it will consume and waste too many API quota. I can’t recommend it at all.

                    1 Reply Last reply Reply Quote 0
                    • G Offline
                      gonzonia @Guest
                      last edited by

                      @Sean Thanks. I think if you can gracefully handle the bad connection (no matter where it’s from) and reconnect once the connection works again, the image being stuck won’t be an issue. Right now once the connection breaks the module can’t recover.

                      G 1 Reply Last reply Reply Quote 0
                      • G Offline
                        gonzonia @gonzonia
                        last edited by

                        @Sean I’ve been looking into this, because I’m really don’t think it’s my network (no other module has this issue and there’s no similar problems anywhere else on the network). The first error doesn’t seem to be fatal, but the second is.

                        These are the errors I’m seeing in my Out.log

                        [2020-04-27 17:33:15.365] [LOG]    2020-04-27T17:33:15 <log> [GPHOTOS:CORE] Error: socket hang up (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:124 GPhotos.log)

                        and

                        [2020-04-27 18:51:15.155] [LOG]    2020-04-27T18:51:15 <log> [GPHOTOS:CORE] Error: Client network socket disconnected before secure TLS connectionwas established (/home/pi/MagicMirror/modules/MMM-GooglePhotos/GPhotos.js:124 GPhotos.log)

                        I came across this issue on gitub related to Google APIs. https://github.com/googleapis/nodejs-bigquery/issues/624
                        Not sure it’s related.

                        In Error.log I see

                        2020-04-27 17:33:15.356] [ERROR]  2020-04-27T17:33:15 <error> Error: socket hang up
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.socketOnEnd (_http_client.js:436:23)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) {
  code: 'ECONNRESET'
} (/home/pi/MagicMirror/js/app.js:40 process.<anonymous>)
[2020-04-27 17:33:15.361] [ERROR]  2020-04-27T17:33:15 <error> Error: socket hang up
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.socketOnEnd (_http_client.js:436:23)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) {
  code: 'ECONNRESET'
} (/home/pi/MagicMirror/js/app.js:40 process.<anonymous>)
[2020-04-27 17:33:15.367] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Error: socket hang up
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.socketOnEnd (_http_client.js:436:23)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 17:33:15.368] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Error: socket hang up
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.socketOnEnd (_http_client.js:436:23)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 17:33:15.369] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 17:33:15.369] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 17:33:15.370] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 17:33:15.371] [ERROR]  2020-04-27T17:33:15 <error> (node:17589) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)

                        and

                        [2020-04-27 18:51:15.161] [ERROR]  2020-04-27T18:51:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1355:19)
    at Object.onceWrapper (events.js:288:20)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 18:51:15.164] [ERROR]  2020-04-27T18:51:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Error: Client network socket disconnected before secure TLS connection was established
    at connResetException (internal/errors.js:559:14)
    at TLSSocket.onConnectEnd (_tls_wrap.js:1355:19)
    at Object.onceWrapper (events.js:288:20)
    at TLSSocket.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 18:51:15.166] [ERROR]  2020-04-27T18:51:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
[2020-04-27 18:51:15.168] [ERROR]  2020-04-27T18:51:15 <error> (node:17589) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4) (/home/pi/MagicMirror/internal/process/warning.js:27 writeOut)
                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 20
                        • 21
                        • 22
                        • 23
                        • 24
                        • 29
                        • 30
                        • 22 / 30
                        • First post
                          Last post
                        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