Read the statement by Michael Teeuw here.
How to disable auto update from MMM-GooglePhotos
-
@JohnDelta said in How to disable auto update from MMM-GooglePhotos:
MMM-GooglePhotos
sorry, let me feed that back…
u want to force download all the files (at module startup) and then load them from the local disk?
-
I got the sense that there is only one file and that it gets updated once per week. So, there is no need to cycle through a batch of photos because there is only one. I don’t see a way of changing the behavior without modifying the underlying code because it’s built to cycle through a collection of photos, not just display a single one.
-
@ember1205 i was being general… 1 file or more, its the same problem.
-
@sdetweil said in How to disable auto update from MMM-GooglePhotos:
@ember1205 i was being general… 1 file or more, its the same problem.
Yes, true.
To me, the solution here seems to be a combination of a cron tool to download an image when it gets updated, a trigger to either restart MM or send a notification to the module to re-read the image, and the ability to simplistically display that singular image as the background for MM.
-
@ember1205 if you used a cron job, then you could use a different module to display the images
-
@sdetweil Agreed. And, if it were me, I would do it that way.
Cron job to check for updates and determine if the file gets updated
If the file was updated, either send notification to load new image in the module, or just restart MM
Use something along the lines of MMM-EasyBack as a module to load the background image -
@ember1205 or MMM-ImagesPhotos (which updates its list)
-
@JohnDelta
Well, if only one photo be used, why do u use cloud?Anyway, in that case, you can give very enough time for scanning and refreshing, maybe 24 hour(1000 * 60 * 60 * 24).
But the only problem is, public opened url of photo which is served by google photos, has not permanent or long-lived lifetime. url would be invalid usually after 1-2hours from its serving
I made this module for whom has hundreds, thousands photos and is managing them with cloud service, so has trouble with storing whole pictures locally (That’s why it is handling only one picture at once)
Just this module is not for your purpose. Try different approach.
-
Thank you guys for all the responses.
So the reason I was thinking on doing it by cloud was that I can manage the files remotely on an easy user interface and also i could just share the folder with the Person in charge of updating it.@Sean you wrote “But the only problem is, public opened url of photo which is served by google photos, has not permanent or long-lived lifetime. url would be invalid usually after 1-2hours from its serving”
But does the URL of the Pictures matter? I mean since its working via the Album_Id. Or what does the Album Id stand for?
@sdetweil can you help me out what a cron tool is? Haven’t heard about it yet.
Merry Christmas everybody ;)
-
@JohnDelta said in How to disable auto update from MMM-GooglePhotos:
@sdetweil can you help me out what a cron tool is? Haven’t heard about it yet.
Cron is a scheduling tool that’s available in various linux, BSD, Mac, Unix, etc. operating systems. It allows you to schedule “jobs” (scripts, typically) to run on certain days, at certain times, with certain privileges to get things done.
On my mirror, I have a script that I’ve written to rsync images from a server on my network over to the Pi. Cron allows me to schedule the execution of that script at times that I want it to run (every 30 minutes, in this case) and copy over changes from the server. You could do something similar with a tool that could connect to a Google photo album, Google Drive, or wherever and copy the most current image to a local directory. After that, whatever module you’re using to display that image would be able to update what’s on the screen either by itself, or you could integrate a “notification” within your script to tell the module to reload the image once the copy is done.
