@sdetweil yeah Google was one of my backups. We are primarily an Apple family but there’s no iCloud module that I’m aware of. I’ll have to do an export or figure something else out.

@sdetweil The way they want it to work is that the user makes the selection, the app gets the items, the session ends. In this case, that would mean the module would have to pull the photos locally which would limit the number of photos available by the amount of space available. I might as well just use a different module and put all my photos somewhere on my network.

@sdetweil so the user wouldn’t have to Re-select after an hour? That can’t be right.

@sdetweil Maybe. I don’t know how the picker stores the relationship to the app and the permissions. If it’s in the browser in some way, launching from a phone might not work. It might need to be from the browser on the MM.

@sdetweil I have an idea but I’m not sure how to make it happen.
I’m not a module developer beyond being able to adjust some code here and there.

Maybe if you have time, you can think about if it’s possible?

What if there was a config flag for “PickPhotos” that if it was true, it would open a picker interface. Then after it’s been done, the user can re-set it to false and the module can go back to just loading photos.

I’m sure there are some other tweaks to the API that will impact this but it’s the only thought I’ve had so far to implement something inside the existing framework.

@sdetweil I know! This is the highlight of my MM. Without it, I think other members of my family will certainly be less impressed. I understand the logic on google’s part, but I wish there was a way on the photos side to share with the application instead of having to implement the picker in the application.

With the Google API changing , the MMM-GooglePhotos module is going to stop working Unless someone develops a way to utilize the new picker API. It looks like the users will need to select photos to share with the application.

This would change the workflow and I’m not sure how it would be implemented.

@Klinge If you find you need an alterantive- https://github.com/Tom-Hirschberger/MMM-GPIO-Notifications/blob/master/examples/HC-SR501/HC-SR501-GPIO4-README-EN.md

@sdetweil No. I had not seen that. Installing now. Thanks!

I just did a new build of my MM to upgrade to Bookworm and update to no longer use unsupported modules. Everything went well for the most part except my calendars aren’t showing. This is in the Error log from start up -

[2025-02-17 11:56:43.570] [WARN]  [MMM-CalendarExt3.js:390:11] [CX3] Module is not prepared yet, wait a while. 
[2025-02-17 11:56:43.576] [WARN]  [MMM-CalendarExt3.js:390:11] [CX3] Module is not prepared yet, wait a while. 
[2025-02-17 11:56:43.668] [WARN]  [MMM-CalendarExt3Agenda.js:186:11] [CX3A] Module is not prepared yet, wait a while. 
[2025-02-17 11:56:43.673] [WARN]  [MMM-CalendarExt3Agenda.js:186:11] [CX3A] Module is not prepared yet, wait a while. 
[2025-02-17 11:56:43.690] [WARN]  [MMM-CalendarExt3Agenda.js:186:11] [CX3A] Module is not prepared yet, wait a while. 

I can see in the main log that the Calendar module is getting data -

[2025-02-17 17:12:47.050] [INFO]  Calendar-Fetcher: Broadcasting 584 events from https://calendar.google.com/calendar/ical/XXXXXXX/basic.ics. 
[2025-02-17 17:12:47.215] [INFO]  [calendar.js:699:7] sorting events count=130 
[2025-02-17 17:12:47.297] [INFO]  [calendar.js:699:7] sorting events count=112 
[2025-02-17 17:12:47.309] [INFO]  [calendar.js:739:7] slicing events total maxcount=10 

I’ve tried the

git submodule update --init --recursive

from the install instructions and it didn’t seem to help. Thoughts?

@sdetweil No worries. Thanks for the response.

@sdetweil Wondering if there was a resolution here. I just did a brand new install on a Pi4b v1.5 using the script. I’ve not added any modules or changed the default config file in any way.

During the setup, I saw this (probably unrelated)

/usr/lib/aarch64-linux-gnu/plymouth/.so does not exist
Splashscreen: Couldn't change theme to MagicMirror!
don't know how to disable screen saver on labwc compositor

I added the

export ELECTRON_DISABLE_GPU=1

to the mm.sh
but had no effect.
I noticed this in the log

ELECTRON_ENABLE_GPU: undefined .

and tried adding

export ELECTRON_ENABLE_GPU =0

but it had no effect except to change the “undefined” to “0”

@sdetweil Just to close the loop on this. I updated MMM-Pir (there was another update soon after I posted) and switched to the updated MMM-Scenes2 and everything seems stable now.

Also, I’m using the xrandr mode for mmm-pir since I’m in Raspbian 11 and when I use dpms it doesn’t wake the screen for some reason.

@sdetweil I know. It used to all work great. I don’t think Scenes has updated in a while.
MMM-CalendarExt3 and MMM-pir have both had updates though.

To clarify, when I say disappear, I mean that they are no longer on the screen.Not just that the data is empty. The headers, dates, etc. All not visible. I’ve just restarted recently, I’ll try to look at the page source next time it happens.

Recently I noticed my Calendars disappear after a few hours. I’m not sure when it started. If I VNC into my mirror and refresh or restart the mirror they come back only to stop appearing a few hours later. I see no errors in the log.

I’m using
MMM-CalendarExt3 and MMM-CalendarExt3Agenda in conjunction with MMM-Scenes, the instances that are only on specific scenes are the ones that disappear. I have another instance of MMM-CalendarExt3Agenda that is on all the scenes and that one seems to stay, so I’m wondering if it’s an MMM-Scenes issue.

Edit: I’m also using MMM-Pir. I’m wondering if that might be doing something.

@sdetweil This is helpful, thank you. I guarantee I made no changes though. I think it’s just that it needs to use npm run update

@bugsounet and that’s what I did wrong! thank you!

I just did a reinstall for now, but I would like to know what I should do to fix this in the future

Okay, sorry to revive this. I saw there was an update available so I went to update.

I did a git pull and got this

hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint: 
hint:   git config pull.rebase false  # merge (the default strategy)
hint:   git config pull.rebase true   # rebase
hint:   git config pull.ff only       # fast-forward only
hint: 
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
From https://github.com/bugsounet/MMM-Pir
   3a5bcdb..1fee537  master     -> origin/master
   fc5b3f6..658a322  dev        -> origin/dev
Updating 3a5bcdb..1fee537
error: Your local changes to the following files would be overwritten by merge:
	MMM-Pir.js
	components/cronJob.js
	components/governorLib.js
	components/motion.js
	components/motionLib.js
	components/pirLib.js
	components/screenDisplayer.js
	components/screenLib.js
	components/screenTouch.js
	node_helper.js
Please commit your changes or stash them before you merge.
Aborting

The thing is, I know I have made NO CHANGES to any of those files.
Should I run a pull.rebase? Would that fix it ?