I have started my new build from scratch and used your install script.
There are a number of ‘vulnerability’ warnings that show, and I’m curious if I should actually try and repair them with the suggested npm commands or not.
Also, so far, the screensaver does seem to be disabled, but I haven’t yet jumped into the MM configuration to put in place the same modules I had been using on the other setup as of yet.
@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.
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.
@sdetweil said in Initial Setup Q's and Some Doc Feedback:
@ember1205 thanks… I wished we had worked on it a little more…
i have a script that just does setting screensaver off…
haven’t had it fail on anything in a while… just tested Zorin OS. it worked properly
I’m going to try a fresh build and will use your script to see how it fares on this exact version of Raspbian…
@dsegel said in Initial Setup Q's and Some Doc Feedback:
@ember1205 There are three locations where the screensaver might be starting from, and only one of them is actually run (I believe the first found in this order):
/home/pi/.config/lxsession/LXDE-pi/autostart
/etc/xdg/lxsession/LXDE-pi/autostart
/etc/xdg/lxsession/LXDE/autostartRaspbian recently changed to not having the first one, so the second is now the preferred method.
So… None of that works. The ONLY way I could get the screensaver to shut off was to do:
sudo apt install xscreensaver
And then run the Screensaver Preferences setup and set it to disabled. Anything else I tried ultimately allowed the screen to go blank (black) after about 15 minutes.
@BD0G said in PDF Implementation:
If others load one .pdf file to the google drive and then delete all other files in that directory well then the file extension would still be .pdf (right) ? So then one could script it using *.pdf (file that ends in .pdf)
So whatever actions that were taken were performed upon a file that ended with .pdf
The file name becomes inconsequential. Just grab all .pdf files (as there will only be one) , download them to a specific directory you create on a local system (ftp sounds like it may be a good option for this) and then use the convert action that @ember1205 speaks of within ImageMagick, upload back to Google Drive via ftp and then (damn! Google Drive will then rename it with another file ID and then the URL that is within the config.js that points to the url will be broken and not display -ugggggg) . I think I understand now.
Here is a Google Chrome Add on that allows one to Overwrite the same file without changing the file name. It “may” be helpful?
https://chrome.google.com/webstore/detail/drive-overwrite-file-repl/llanhaaigblafdecdihpppjaeekpddfl?hl=en-USIt really sounds like you may have to delve into Google App Script to accomplish this. https://developers.google.com/apps-script
If you have questions about using this scripting tool then I think there is support over on www.stackoverflow.com
I am not a Google Script Coder so I cannot be of any help there.
Download from Google drive to the MM device. Convert. Store converted file locally. Load local file.
Less complicated than downloading, converting, pushing back up, figuring out new ID, etc.
@JohnDelta said in PDF Implementation:
@ember1205 so I’ve tried. But that’s just a few unnecessary steps to take once a week so I find.
That was why I had mentioned doing it with ‘convert’ from ImageMagick - you can script it and then make it into a cron job. Pull the PDF down to the local device, detect that it’s a different PDF (not necessary), and run the convert tool to make it into an image file stored someone on the local filesystem. Done.
You could also convert the PDF to JPG or similar with the ‘convert’ utility from imagemagick and then just display it as an image.
Sigh. Best laid plans… lol
At any rate - I actually rm’ed the original dir and re-did the clone using YOUR version. Came right up and started working properly right out of the gate.
Thanks for not only all of the help, but all of the patience. I do learn quickly, and this should now remain fairly firmly entrenched in my brain going forward.
Now I’m off to see how to modify the CSS of MM to change some of the font aspects for text!
I followed the directions on the page for your module:
Clone this repository inside your MagicMirror's modules folder
cd ~/MagicMirror/modules
git clone https://github.com/roramirez/MMM-ImagesPhotos.git.
I saw the reference to roramirez, but as I said - I don’t do a lot with git, so I have to go with what’s on the page. Did that install the original?
git pull says everything up to date and didn’t do anything. No image size info available.
I tried reverting TO the fake driver as I was not using it (real one instead) and that hasn’t made any difference. I also tried editing the startup file to remove the rotate setting, also didn’t help.
“do a get pull”… To date, I’ve done little with repositories - can you elaborate on how I do this to make sure I do it correctly?
Also… Some updates.
CTRL - does not affect image size in any way. It DOES affect the sizing of the text for the other modules, though.
I believe that I have determined that the desktop / browser “believes” that it is in portrait mode. The images seem to be getting constrained properly, but because the browser is configured to be as tall as it is, I’m losing all kinds of content off the bottom of the screen. If I do a CTRL-SHIFT-I and then turn on the device toolbar, I see a full vertical representation of the browser and I can see the entire image. As I increase the zoom, it becomes apparent where the image is getting clipped vertically.
Thoughts?
I’ll definitely give it a try. But… If it were a browser zoom issue, wouldn’t that prevent the other module from displaying them properly as well?
I tried with the config you provided:
{
module: "MMM-ImagesPhotos",
position: "fullscreen",
config: {
opacity: 0.9,
animationSpeed: 0,
updateInterval: 30000, // how often to change pic
backgroundColor: "#808080", // color around pic (if u want something other than black)
},
},
This results in the photos running off the edges of the screen and not being able to view the entire image. I have also tried using the config on the project page, and adding the maxHeight and maxWidth variables as well.
Just for the heck of it, I even tried using the “fullscreen_below” positioning area that the other module uses.
The photos always run off the edge of the screen. And by a lot.
As of right now, these are all photos that were shot on a 24MP DSLR and they are being displayed on a 1080 TV. There is definitely more pixels in the photo and the device needs to ‘resize’ them down to fit the screen (which it does not appear to be doing).
While you don’t ‘contain’ the images, I do recall that was an option being used in the other module that would ensure they did not overrun the screen edges. Is there a config option for yours that would enable it?
Quoting the values corrected the issues I was having with them. I think I’m good with this now and appreciate the help.
[TAILING] Tailing last 100 lines for [all] processes (change the value with --lines option)
/home/pi/.pm2/pm2.log last 100 lines:
PM2 | 2019-12-12T14:19:37: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:19:37: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:41:26: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:26: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:41:27: PM2 log: pid=4285 msg=process killed
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:41:27: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:43:33: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:43:33: PM2 log: pid=4543 msg=process killed
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:43:33: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:46:33: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:46:33: PM2 log: pid=4667 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:46:33: PM2 log: pid=4667 msg=process killed
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:46:33: PM2 log: App [mm:0] online
PM2 | 2019-12-12T14:47:42: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T14:47:43: PM2 log: pid=4822 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T14:47:43: PM2 log: pid=4822 msg=process killed
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] starting in -fork mode-
PM2 | 2019-12-12T14:47:43: PM2 log: App [mm:0] online
PM2 | 2019-12-12T15:00:40: PM2 log: Stopping app:mm id:0
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:41: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=failed to kill - retrying in 100ms
PM2 | 2019-12-12T15:00:42: PM2 log: App [mm:0] exited with code [0] via signal [SIGINT]
PM2 | 2019-12-12T15:00:42: PM2 log: pid=4943 msg=process killed
/home/pi/.pm2/logs/mm-error.log last 100 lines:
0|mm | [5004:1212/145553.006275:FATAL:memory.cc(22)] Out of memory. size=96641024
/home/pi/.pm2/logs/mm-out.log last 100 lines:
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm |
0|mm | > magicmirror@2.9.0 start /home/pi/MagicMirror
0|mm | > sh run-start.sh
0|mm |
0|mm | Starting MagicMirror: v2.9.0
0|mm | Loading config ...
0|mm | Loading module helpers ...
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: MMM-ImagesPhotos
0|mm | No helper found for module: alert.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: updatenotification
0|mm | No helper found for module: clock.
0|mm | Initializing new module helper ...
0|mm | Module helper loaded: calendar
0|mm | No helper found for module: currentweather.
0|mm | No helper found for module: weatherforecast.
0|mm | All module helpers loaded.
0|mm | Starting server on port 8080 ...
0|mm | Server started ...
0|mm | Connecting socket for: MMM-ImagesPhotos
0|mm | Starting node helper for: MMM-ImagesPhotos
0|mm | Connecting socket for: updatenotification
0|mm | Connecting socket for: calendar
0|mm | Starting node helper for: calendar
0|mm | Sockets connected & modules started ...
0|mm | Launching application.
0|mm | Create new calendar fetcher for url: https://calendar.google.com/calendar/ical/EDITED%40gmail.com/EDITED/basic.ics - Interval: 900000
0|mm | Shutting down server...
0|mm | Stopping module helper: MMM-ImagesPhotos
0|mm | Stopping module helper: updatenotification
0|mm | Stopping module helper: calendar
I will try quoting them.
It hadn’t occurred to me that “words” need to be quoted since true and false do not.
Why do some of the more general config options throw errors stating that they are undefined? For example, I can’t set tableClass or timeFormat as the values I chose (xmall and absolute, respectively) throw errors and prohibit MM from starting. I have these defined in the general config section.
Thanks for the reply. While adjusting as you’ve mentioned does give me the expected result, I have to say that it seems counter-intuitive.
Placing those settings OUTSIDE of the calendar definition seems to make them overrides for the defaults and would make them be the settings used for all calendars. Shouldn’t setting them per-calendar need to be done within the definition of the calendar itself?
At a minimum, the apt-get update / upgrade seems to have at least helped. After installing the updates and restarting, I’ve been running this module with clock, calendar, current weather, and weather forecast all enabled and it hasn’t crashed in about an hour.
I stopped everything and reverted to the BackgroundSlideshow module to see if it would also run clean, but it died pretty quickly. I’ve flushed the logs again (although I did capture their contents from the other module’s crash) and once again changed over to ImagesPhotos to see what happens after another run.
While I’m waiting to see if it will crash, I have some questions about the rendering configuration.
I’ve tried both the “fullscreen” and “middle_center” settings and the photos are not constrained to the screen (in terms of the actual image, not where it’s shown). I can change the details so that I use less than full height and/or width, and there is a black border. However, the image itself is getting cropped - badly.
How can I get this to display the entire image on the screen like I can with the other module?