@sdetweil Well that sorted it. Thank you so much.

@sdetweil A few things: The main issue being: MagicMirror is now using a flat npm config, and the start scripts are handled differently, node --run start:x11 is not a valid Node.js command — unless you are using a custom wrapper or an internal script, this will fail silently or do nothing. As Crontab runs in a minimal environment, so any graphical (X11) application must explicitly export DISPLAY. Previously I had the command as DISPLAY=:0 npm start. Now, I had to export DISPLAY=:0 first and then start MM.

@kusselin you cannot run electron from root user without additional parameters you should logon as a normal user

@mumblebaj Sorry but no. I am out of pi’s to test on. And it is not something that matters to me . What is a few minutes in the grand scheme of things.

@captsi Can you reconfigure the new router to the same settings you had in the old one. or update the pi to the new wifi?

@aaronaxvig because you are using monthly calendar and calendar is using an array of symbols, 2.30 has bugs in both with fixes in develop can you try the develop branch https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code when did you try my script? i added installing the two fixes just a couple days ago

@casper1 can you explain more?? what did you do? update node??

@emwtur my upgrade script will handle that it will say that the calendar.js is modified, do you want to save that, say no… https://github.com/sdetweil/MagicMirror_scripts if you run the test version first, it wont change anything, but still will warn you (how to remember if you changed files…)

@sdetweil ok thx

@chndrcks said in Blank Screen in Electron - fresh install on Pi Zero 2 W: line 55 “if [ 0 -eq 1 ]; then yes I just disabled that section. for install the log has to be outside the MM folder (as it doesn’t exist yet, until the git clone, a long way down)

@sdetweil Thank you for the useful hints! I will soon work on them, and consider making a pull request to the community.

@reilley It works. Thank you

@Amenity4882 its solved glad you found it

@sdetweil, great, thank you very much!

@dathbe said in UnhandledPromiseRejectionWarning: TypeError: fetch failed: Platform: Raspbian 12 Node Version: 18.19.0 MagicMirror Version: 2.27 Description: I am seeing the following errors in my logs, though I’m not necessarily seeing any problems on my display (at least not regularly). 0|mm | 024-05-16 14:10:44.296] [ERROR] 2024-05-16T14:10:44 <error> (node:26446) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 97) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:11:12.283] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) UnhandledPromiseRejectionWarning: TypeError: fetch failed 0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11) 0|mm | (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:11:12.291] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 119) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | /home/username/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT 0|mm | [2024-05-16 14:12:49.844] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) UnhandledPromiseRejectionWarning: TypeError: fetch failed 0|mm | at Object.fetch (node:internal/deps/undici/undici:12293:11) 0|mm | 0|mm | (Use `electron --trace-warnings ...` to show where the warning was created) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:12:49.851] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 52) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 0|mm | [2024-05-16 14:13:09.544] [ERROR] 2024-05-16T14:13:09 <error> (node:28645) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) It seems to come up most often when I load the MMM-Pinfo module in my config, though I have seen it at other times as well. The problem is that I don’t see enough information in these logs to find a source myself. Steps to Reproduce: Load MM, usually with MMM-Pinfo module enabled. If anyone has any ideas, that would be great. pinfo doesn’t use fetch… Sadly, best way is to comment out, or disabled:true each module til you find the culprit

@sdetweil I am running raspbian (debian 11 bullseye) with no pending updates on a pi3B+. I have cd’d into MagicMirror/fonts, run npm install and restarted the MM. No change. Still displays a square where there should be an icon.

@Dresch360 The Pi5 has new GPIO hardware. It is not compatible with software written for earlier Pi models. So look at what gpio library is being called by the modules you are wanting to use. I’ve been rewriting my own code to use gpiozero . gpiozero works and isrecommend by raspberry pi foundation and works on older pis too. Lgpio works on rpi5 Gpiod works on rpi5 Pigpio WILL NOT WORK RPi.GIPO WILL NOT WORK I haven’t tried rpi-lgpio which supposed to be a drop in replacement for rpi.gpio.

@OldSunGuy 1st image, round up current time, 6:49+21 mins = 7:10, sunrise time second image, round up time 7:13, +10:05 =17:18. sunset time

@sdetweil Just letting you know that this fix corrected my issue where my calendar module (setup for iCal) would not show repeating events. The repeating events are showing again. Thanks.