@butchkemper Is this the default weather module or an additional one?

@karsten13 how do I update this specifically.

Everything was working fine prior to the latest MM update.

I’ve just updated the MM to the latest version, everything seems to have gone fine except the default weather module, which is now stuck in a “loading” phase.

I found an older post saying the newer version of this module needed an APIkey over an APIid but the MM setup is newer than this post so already has this change.

Has anyone had this same issue since this latest update, or have any ideas how to sort this?

Seems I can’t even update the MM without causing an issue.

for completeness I got this at the bottom of the update using
git pull && npm run install-mm,

npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Not compatible with your version of node/npm: magicmirror@2.29.
npm ERR! notsup Required: {“node”:“>=20.9.0 <21 || 22”}
npm ERR! notsup Actual: {“npm”:“10.1.0”,“node”:“v20.8.0”}

npm ERR! A complete log of this run can be found in: /home/MagicMirror/.npm/_los/2024-10-06T07_38_42_762Z-debug-0.log

would these errors cause the issue I’m seeing?
cheers.

@sdetweil That was exactly how PIR sensor lite worked on the same pi 3.
screen would turn off after time interval - i had it set to 5 minutes - pi would detect a hand swipe past the PIR sensor, pi would wake the screen up and the 5 minute cycle would start again.

do we (you) think the mode 4 for HDMI in this module will function the same?

@sdetweil
So if I stick with MMM-Pir am I right in thinking if u set the mode to mode 4 in the script it would turn the screen off via the HDMI?

Just read that it is set to mode 1 by default which uses vgencmd but my screen and pi are connected via HDMI.

Would be handy to get this one turning the screen off entirely (if possible) and use the PIR to turn it back on, as the rest of the MM is working nicely.

I had a MM set up and running nicely before the SD card failed (lesson learnt).

It was using MMM-PIR sensor lite and working perfectly with this sensor.
This module is no longer developed/maintained and has been achieved so now I’m using MMM-PIR which works.

However, the difference between the 2 is that the PIR sensor lite would physically turn the screen off and put it in standby, then wake the screen up when the PIR sensed movement.
MMM-PIR appears to only blank the screen of modules so the screen stays on (albeit black) but the screen is still on.
Not ideal at night/for mirror usage/power use.

Can MMM-PIR be configured to put the screen in standby?
With PIR sensor lite, will this still work even though the module is no longer maintained or will this become an issue as MM evolves?

Cheers.

@sdetweil wherever I position the module it’s always at the correct height on the screen but always up against the right hand edge of the screen.

edit to add by setting the show width/height, it’s sensible size.

any thoughts on this?

so I added,
#GPHOTO_CURRENT {
background-size: cover;
}
to the custom.css in the MagicMirror/css folder,

from your list this appears to be the correct place to put it, yet it appears to make no difference.

I’ve got this module up and running with a small number of photos in an album - just for testing purposes.

I initially had the module set up to display over the entire screen using the position background_below.
I didn’t like this and have set the module to bottom_bar, the same position as MMM-CalendarExt3 so I can use MMM-Carousel to switch between these two.

I’m using the default code example from the module
{
module: “MMM-GooglePhotos”,
position: “bottom_bar”,
config: {
albums: [albumname],
updateInterval: 1000 * 60, // minimum 10 seconds.
sort: “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,
originalWidthPx: 1920,
originalHeightPx: 1080,
timeFormat: “YYYY/MM/DD HH:mm”, // Or relative can be used.
}
},

I’ve // ShowWidth, showHeight, originalHeightPx and originalwidthPx.

from the module install info I’ve tried adding
#GPHOTO_CURRENT {
background-size: cover;
}
to the custom.css file in the MagicMirror/css as the guidance says this should make it cover one position on the screen (I’ve again used bottom_bar).

But when launching the MM the Googlephoto overlays everything else on the screen.

what am I missing to get the photo to only take up the lower portion of the screen so it can be switched at set time intervals with my calendar in the same bottom_bar position?

My apologies for how the code is formatted following it being copied and pasted.

Cheers.

@tdw
I’m currently looking at 3 files within the MagicMirror/css folder.
custom.css
custom.css-sample
main.css

so does it go in the custom.css file or do I have to make a new custom.css file containing the information for this one module and save it?

do all future css changes go within the custom.css file, or does each css change have it’s own file?

apologies for this one, I’m about to embark on my first steps into custom css for a module.

it’s a simple addition, but where do I put the modification, does it go in the css folder within the individual module, or the custom.css file within the main css folder in the MagicMirror directory?

I want to add this,
#GPHOTO_CURRENT {
background-size: cover;
}
as a change to MMM-GooglePhotos.

I have a very strong feeling its the latter but don’t want to mess this up, this feels like the movie Inception, I’ve only been in the first level of the dream and this is the dream within the dream.

cheers.

is that not the file it asked me to rename in step 9?
Nothing has downloaded following steps 10 and 11.

@sdetweil Hey, it worked today, I guessing I was trying to do everything too close together and not giving it time.
In the setup guide step 12 says,
Copy the file token.json and credentials.json to the folder MMM-GooglePhotos in the remote device

where am I copying those from?
when I go into the GooglePhotos folder on the Pi those 2 files are already there, do I assume those are the onces it wants me to copy?

Working through the install guide found here,
https://github.com/hermanho/MMM-GooglePhotos/blob/master/INSTALL.md

got to step 10 it opened the browser as expected, I click on the same email address used to set everything up with Google but I get,

Access blocked: MagicMirror photos has not completed the google verification process.
email addressed used

MagicMirror Photos has not completed the Google verification process. The app is currently being tested and can only be accessed by developer-approved testers. If you think you should have access contact the developer.

if you are the developer of MagicMirror photos, see error details.
Error 403:access_denied.

I’m pretty certain after following a step earlier it said verification wasn’t necessary.
I only went through the steps for this install an hour ago, is this something I need to give time to?

sorry this is a little vague, I’m doing some of these steps on the pi itself and it is painfully slow but if anyone can shed some light on where I should be looking that would be cool. I’ve never had to deal with Google in more than a search capacity.

Cheers.

@sdetweil new install of MM is one the new SD (failed the first time so had to run again and seemed to take a while).

when I run your backup script will it automatically find the previous MM install on the old SD card mounted with USB?

if not how do I get it to find the previous install to copy the files I need?

@sdetweil so I’m not manually moving the config and CSS files myself that will be done after via terminal?

@sdetweil right so when I copy those 2 file’s am I literally just dragging a copy to the new SD’s home screen (just so they’re on the new card) or do they need to go into a MM specific folder on the new card.

I can find both of those files on the old SD but I’m not understanding from

ls >~savedlist.txt.

am I doing that after I’ve installed a fresh MM on the new SD card once that MagicMirror/modules folder exists because running the above command won’t work as the new SD has no reference to MM’s existence.

@sdetweil So install the base of MM on the new SD then follow the steps in your previous post?

I have a feeling it definitely won’t be that easy.

@sdetweil hey Sam, I can still see the old list of modules on the old SD card.

If that’s the case can the old card still be used?

the new card is just a completely empty Pi OS, nothing to do with MM on there yet.

Do I need in run the basic install for MM on the new SD to get that running?

had a little crack at this again, the Mrs is bugging me to get “her” mirror back up and running.

So I’ve run sudo umount /dev/sda1
sudo umount /dev/sda2

Both drive folders from the mounted (old) SD disappeared from the home screen on the pi as expected.

then run, (and got)
sudo e2fsck -f -v /dev/sda2
e2fsck 1.46.2 (28-feb-2021)
rootfs: recovering journal
superblock needs_recovery flag is clear but journal has data.
Run journal anyway ? YES
e2fsck: unable to set superblock flags on rootfs

rootfs: *********** WARNING: filesytem still has errors *********