Read the statement by Michael Teeuw here.
MMM-GooglePhotos
-
@Sean Any news for me? Still not working
Thanks -
@zolabus
Without more details, I have nothing to say…You can get a backend-log and frontend-log together by
npm start dev
on MagicMirror directory. (If you are using pm2, stop it first) -
@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, },
-
@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.
-
@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.
-
@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. -
@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. -
@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. -
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. } }
-
@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.