@sdetweil

Calendar still does not pick up any CSS controls from the main custom.css file. Here is a snippet of what I added:

.calendar {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

I modified the other sections to look like this:

.module.clock {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

.module.currentweather {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

.module.weatherforecast {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

They work fine “either way”. Calendar refuses to pick up the formatting from the custom.css file it seems and I have to put the controls into the calendar.css file in the module’s directory.

@sdetweil

Ok. I will look into making those changes and see if I can get it working the way that I want.

Why does “module.currentweather” work fine, though (along with the others that I mentioned)? CSS has always been a weak spot for me…

@sdetweil What does “not the world module” mean? Just seeing that now, and not following…

@sdetweil

Sigh. Thanks. :)

@sdetweil

That’s how it is in my config.js (no quotes). The quotes were used here to isolate it in the post only.

                {
                        module: "clock",
                        position: "top_left",
                        displaySeconds: false,
                },

It has no effect.

@sdetweil

In custom.css, this does not work:

.module.calendar {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

Also, in custom.css, this DOES work:

.module.currentweather {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

.module.weatherforecast {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

.module.clock {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

Although I can not find any statements that would say or imply that the digital clock doesn’t support “displaySeconds: false”, setting that value seems to have no effect.

I attempted to add the following to my custom.css:

.module.calendar {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

It did not work as expected, nor as it did for clock, currentweather, or weatherforecast. I had to insert that code into the ~/MagicMirror/modules/default/calendar/calendar.css module as:

.calendar {
  background-color:rgba(32,32,32,0.6);
  border-radius:8px;
  padding:8px;
}

This is the only way it would provide the opaque background that I wanted.

Thoughts?

@sdetweil

I believe the rules are less important than the consequences. I don’t believe WLAN has a good track record overall of waking up from a sleep state. And, regardless of how much it’s directly used, you can bet that the one time it won’t work is when you try using the remote control module to power it down. :)

@sdetweil

-Should- the WLAN power setting be changed? It would seem that this would be a wise approach to ensure it doesn’t go into powersave mode.

Some additional notes:

• The screensaver settings appear to have been set in the /etc/xdg/lxsession/LXDE-pi/autostart file
• No settings have been adjusted in /etc/lightdm/lightdm.conf
• The mouse pointer auto remove configuration has not been completed, but there appears to be no issue with the pointer remaining on the screen once Electron loads
• There was no change made to the system to disable power saving on the WLAN interface - as a result, the interface seemingly “could” go into powersave mode and affect network connectivity (I have not yet experienced an issue with this)

install starting  - Fri Dec 20 08:32:44 EST 2019
installing on armv7l processor system
the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster
Updating packages ...
Hit:1 http://archive.raspberrypi.org/debian buster InRelease Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB] Get:3 http://raspbian.raspberrypi.org/raspbian buste
r/main armhf Packages [13.0 MB] Fetched 13.0 MB in 15s (852 kB/s) Reading package lists...
apt-get update  completed ok
apt upgrade result =rc=0 Reading package lists...
Building dependency tree...
Reading state information...
Calculating upgrade...
The following package was automatically installed and is no longer required:
  point-rpi
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installing helper tools ...
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v10.1.0
Installed Node version: v10.15.2
No Node.js upgrade necessary.
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V6.0.0
Installed npm version: V5.8.0
npm should be upgraded.
Installing npm ...
Reading package lists...
Building dependency tree...
Reading state information...
npm is already the newest version (5.8.0+ds6-4).
npm set to manually installed.
The following package was automatically installed and is no longer required:
  point-rpi
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
upgrading npm to latest
/usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js
/usr/local/bin/npx -> /usr/local/lib/node_modules/npm/bin/npx-cli.js
+ npm@6.13.4
added 430 packages from 854 contributors in 42.042s
npm installation Done! version=V6.13.4
Cloning MagicMirror ...
Cloning MagicMirror Done!
Installing dependencies ...
Dependencies installation Done!
setting up initial config.js
Check plymouth installation ...
Splashscreen: Checking themes directory.
Splashscreen: Create theme directory if not exists.
Splashscreen: Changed theme to MagicMirror successfully.
install and setup pm2
pm2 not installed, installing
pm2 install result /usr/local/bin/pm2 -> /usr/local/lib/node_modules/pm2/bin/pm2 /usr/local/bin/pm2-dev -> /usr/local/lib/node_modules/pm2/bin/pm2-dev /usr/local/bin/pm2-docker -> /usr/lo
cal/lib/node_modules/pm2/bin/pm2-docker /usr/local/bin/pm2-runtime -> /usr/local/lib/node_modules/pm2/bin/pm2-runtime npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_
modules/pm2/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arc
h":"arm"}) + pm2@4.2.1 added 207 packages from 202 contributors in 38.506s
get the pm2 platform specific startup command
startup command = sudo env PATH=$PATH:/usr/bin:/bin /usr/local/lib/node_modules/pm2/bin/pm2 startup systemd -u pi --hp /home/pi

                        -------------

__/\\\\\\\\\\\\\____/\\\\____________/\\\\____/\\\\\\\\\_____
 _\/\\\/////////\\\_\/\\\\\\________/\\\\\\__/\\\///////\\\___
  _\/\\\_______\/\\\_\/\\\//\\\____/\\\//\\\_\///______\//\\\__
   _\/\\\\\\\\\\\\\/__\/\\\\///\\\/\\\/_\/\\\___________/\\\/___
    _\/\\\/////////____\/\\\__\///\\\/___\/\\\________/\\\//_____
     _\/\\\_____________\/\\\____\///_____\/\\\_____/\\\//________
      _\/\\\_____________\/\\\_____________\/\\\___/\\\/___________
       _\/\\\_____________\/\\\_____________\/\\\__/\\\\\\\\\\\\\\\_
        _\///______________\///______________\///__\///////////////__


                          Runtime Edition

        PM2 is a Production Process Manager for Node.js applications
                     with a built-in Load Balancer.

                Start and Daemonize any application:
                $ pm2 start app.js

                Load Balance 4 instances of api.js:
                $ pm2 start api.js -i 4

                Monitor in production:
                $ pm2 monitor

                Make pm2 auto-boot at server restart:
                $ pm2 startup

                To go further checkout:
                http://pm2.io/


                        -------------

[PM2] Init System found: systemd
Platform systemd
Template
[Unit]
Description=PM2 process manager
Documentation=https://pm2.keymetrics.io/
After=network.target

[Service]
Type=forking
User=pi
LimitNOFILE=infinity
LimitNPROC=infinity
LimitCORE=infinity
Environment=PATH=$PATH:/usr/bin:/bin:/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Environment=PM2_HOME=/home/pi/.pm2
PIDFile=/home/pi/.pm2/pm2.pid
Restart=on-failure

ExecStart=/usr/local/lib/node_modules/pm2/bin/pm2 resurrect
ExecReload=/usr/local/lib/node_modules/pm2/bin/pm2 reload all
ExecStop=/usr/local/lib/node_modules/pm2/bin/pm2 kill

[Install]
WantedBy=multi-user.target

Target path
/etc/systemd/system/pm2-pi.service
Command list
[ 'systemctl enable pm2-pi' ]
[PM2] Writing init configuration in /etc/systemd/system/pm2-pi.service
[PM2] Making script booting at startup...
[PM2] [-] Executing: systemctl enable pm2-pi...
[PM2] [v] Command successfully executed.
+---------------------------------------+
[PM2] Freeze a process list on reboot via:
$ pm2 save

[PM2] Remove init script via:
$ pm2 unstartup systemd
pm2 startup command done
configure the pm2 config file for MagicMirror
start MagicMirror via pm2 now
save MagicMirror pm2 config now
disable screensaver via lxsession
We're ready! Run pm2 start MagicMirror from the ~/MagicMirror directory to start your MagicMirror.
install completed - Fri Dec 20 08:59:08 EST 2019

@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

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.

@sdetweil

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/autostart

Raspbian 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-US

It 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.