@jbat66 all good mate. I’m likely in a different geographic region to you. But anyway it was an issue that someone in GitHub that resolved for me so I can’t really take credit. I would point you to the GitHub but it was quite awhile back hence I can’t find the link anymore, therefore I went into my txt file and gave you guys the code.
Read the statement by Michael Teeuw here.
Best posts made by 1a2a3a
-
RE: MM current version on Raspberry Pi 5 cannot turn off monitor
-
RE: building a mirror 101
Probably going to use and try it out first. So it’s true film only works in the day?
-
RE: Magic mirror dual screen
Decided to drop this for now guys. The new monitor is a 27 qhd compared to the previous 24 fhd. With the extra real estate, everything doesn’t seems to be so cluttered now.
-
RE: How to schedule on off in magic mirror
ill be damned. managed to get it to work using this after some searching
Edit the “config.txt” in the “/boot” directory.
Go to:
“# Enable DRM VC4 V3D driver
dtoverlay=vc4-kms-v3d
max_framebuffers=2”And change “dtoverlay=vc4-kms-v3d” to “dtoverlay=vc4-fkms-v3d”.
There is a bug in the “vc4-kms-v3d” driver.
After changing in the “config.txt” “vcgencmd display_power 0” returns a “display_power=0”.
-
RE: magicmirror lagging
@sdetweil ok boss. Will just leave it as it is and wait for a future update. Don’t think I’ll go back to x11 given the amount of time spent configuring wayland crontab to schedule on off :D
Thanks anyway!
-
RE: unable to git pull successfully
@KristjanESPERANTO thanks, that fixed it now!
Latest posts made by 1a2a3a
-
RE: MMM-GooglePhotos
@sdetweil which option is the same as the previous ‘fullscreen’?
-
RE: MMM-GooglePhotos
Did something change here? I’m getting an invalid module position found for this configuration. My position is “fullscreen”. It used to be working fine…?
-
RE: MM failed after updating
@sdetweil i see. anyway, my calendar, stocks and google photo are not loading. it says check logs for details – where can i find the logs again?
edit—
its odd. when i run npm start dev, everything is working fine, everything loads.
but when i run pm2 start MagicMirror - my cal, stocks and photos are not loading. am i suppose to let it sit there for awhile?
-
RE: MM failed after updating
@sdetweil thanks. still in the midst of transferring.
why are you up so early? i recall you were some hours behind so when i posted this i figured i wouldnt get a response so soon hence my attempt of own answer.
-
RE: MM failed after updating
@sdetweil i cant. i deleted the entire folder. just installed using your script. now transferring the modules folder from backup to the pi.
thats what i did actually, installing the electron but it keep throwing error like npm ERR! signal sigint
npm ERR! code E404 -
RE: MM failed after updating
@sdetweil on pi 5. updated using your script. while attempting to google search for fixes, i seems to have broken more stuff. trying to rebuild again from scratch…using your script… to update again…
-
MM failed after updating
Hi, after updating my MM, when i try to start i get this error.
node_modules/.bin/electron: not found"
what should i do?
-
OAuth clients must support granular consent, starting June 17, 2024.
hi all
not sure if you received the same from google relating to OAuth clients consent.
Our records indicate that your app(s) has requested access to Google APIs and may be affected by an upcoming OAuth consent change. Starting June 17, 2024, Google will enable granular consent, which allows OAuth users to grant or deny Google account data permissions on a more granular level to third parties. We’ve provided more information below to help you through this change.
What do you need to know?
OAuth users will see a granular consent screen allowing them to grant or deny granular permissions to Google account data to your app(s) starting June 17, 2024.Note: Workspace Enterprise apps that are granted domain-wide delegation of authority or marked as Trusted will not be impacted by this change at this time.
What do you need to do?
We recommend that you test your app with granular consent and make any necessary updates to ensure an optimal user experience:Review our OAuth granular consent guide to learn about the requirements and best practices to handle granular consent.
If needed, update your app to ensure it supports granular consent.
If necessary, you may request a one-time extension, giving you until August 19, 2024, to support granular consent.
Here is a list of your client ID(s) that may be affected by this change. If you have Google Cloud Platform (GCP) console login issues, the Google Cloud Support team can help. Please submit a ticket in the Support Hub.and it seems like the affect module will be googlephoto. im checking in to see if theres anything ill need to change/make? i have look through the permission but it doesnt seems like theres any option for me to change anything to ensure a seamless transition?
-
RE: unable to git pull successfully
@KristjanESPERANTO thanks, that fixed it now!
-
RE: unable to git pull successfully
@sdetweil did as per your mentioned but still stuck with .vscode/setting.json