@Kastore It depends on the device but the color of the wires is not random. Typically red = + but could either be 3.3V or 5V. Black will be - or grd. I can’t ever remember all of the pins but if you do an image search on GPIO Pinout you will get a ton of pictures of how all the pins are laid out. Yellow can be a bit more arbitrary but if you don’t have the device literature you can do a search on the devices name and/or number [image: 1690562516981-gpio-pinout-diagram-2-resized.png]

@Merowinger this is a pi config issue with the display driver in the short term you can turn off use of the gou.by electron by adding export ELECTRON_DISABLE_GPU=1 before npm start if u are using my install script and pm2, then the little startup script is ~/MagicMirror/installers/mm.sh

@bhepler also, https://crontab.guru/

Turned out to be a failing ssd drive. Replace SSD found old backup of MM so only had to do a little rebuilding of custom.css and config.js Used Sams backup restore program to restore all but a couple of the modules 33 at this time. Thanks Sam for the help…

@nschertz Electron appears to have changed their key mappings. alt-spacebar has always been the key sequence on keyboards w the windows key, between Alt and Ctrl, that will pop up the menu

Beautiful. That solved the issue. Thanks for the quick response.

@syedkhadri Is the underlying Pi OS desktop also stretched? Your question is way too broad. Rephrase your question and provide some detail.

@droidus did u perchance checkout the develop branch before to fix a problem. best way to get out of this, rename the MagicMirror folder to MagicMirror.2 install MagicMirror using my script see https://github.com/sdetweil/MagicMirror_scripts the in the new magic mirror temporarily rename the module defaults folder to something else, so this copy command does write over anything cd ~/MagicMirror/modules mv defaults temp copy the old mm module folder content here in the mm’s module folder, including the old defaults folder cp -r -p ~/MagicMirror.2/modules/ . (dot at the end means here) delete the defaults folder that was copied rm -rf defaults restore the new defaults folder mv temp defaults then copy your old config.js and custom.css from the old MagicMirror.2 folder over to the new one

@sdetweil your script worked, thank you. For now I will keep the 4b only running home assistant.

@DimChik2903 threat of exposure I say? lol

@sdetweil Thanx , got the clock back :zany_face:

@BKeyport https://raspberrypi.stackexchange.com/questions/104181/colored-emojis-in-chromium

@1a2a3a see https://forum.magicmirror.builders/topic/9707/save-performance-when-rotating-screen-e-g-on-raspberry-pi?_=1688210939324

@1a2a3a yes this is probably an older browser which doesn’t support the newer JavaScript language features we are using.

I’ll toss out a similar problem I had a long time ago and it was tied to the FontAwesome ICONS. I wish I could remember what all I did but it took me a while to figure out it was like padding around the icons or something like that.

@krouton display where, at a remote device? with what browser? the tv where the chromecast is installed is in physical portrait mode? portrait mode is just height is taller than width magicmirror doesn’t know, just uses the browser reported dimensions. you had the device in portrait mode before

@lillyhb yes. ignore this is electron trying to use the gpu. but it’s not configured like electron expects. you can get rid of the error message by adding export ELECTRON_DISABLE_GPU before doing npm start if you use pm2, then add it to the script pm2 uses to launch mm

@BKeyport also, there have been image size issues as well. many of the NASA images are huge

@wyovino yes. use a different calendar module see the 3rd party list