The comma, it’s always the comma. Thank you.
Read the statement by Michael Teeuw here.
Posts
-
RE: Weather, how to remove GB-ENG from the header?
-
RE: Weather, how to remove GB-ENG from the header?
appendLocationToHeader
module: "weather", ---->appendLocationNameToHeader: false //header: 'Current My_City weather: ', position: "top_right", config: { weatherProvider: "openmeteo", ----> appendLocationNameToHeader: false type: "current", lat: 51.12345 lon: -0.12345 }Spelling shown in docs is appendLocationNameToHeader
Neither of the two position above work, mirror fails to load. -
Weather, how to remove GB-ENG from the header?
Using openmeteo, weather display, header line commented out.
MM shows “city, GB-ENG”How do I remove, disable the GB-ENG bit?
-
April update says "New major version of npm available" - should I install this?
I just applied the April update, during which I spotted this message:
npm notice npm notice New major version of npm available! 10.9.4 -> 11.14.0 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.14.0 npm notice To update run: npm install -g npm@11.14.0 npm noticeShould I run this update, or leave npm as it is?
Thanks! -
RE: Calendar module to show day name for all day entries
Tried various combinations of…
timeFormat: "relative", //"absolute", dateFormat: "ddd Do MMMM", //"LLLL",…but still only timed items show a day name, not whole day items.
LLLL or llll is the only mention in the moments doc of named week day.
-
Calendar module to show day name for all day entries
Calendar module shows day name only for calendar entries which are not all day items.
How then do I get calendar module to show day name for all entries, regardless of whether they are all-day thing (e.g., birthdays, no day name shown) or meetings (09:00 - 10:00, day name shown) ?
Current workaround is to change all-day items in my g/calendar to 00:00 - 23:59 , which is messy, clumsy and really not a solution!
Thank you.
-
RE: Calendar failed to load - check the logs
If perhaps it could show the nature of the error?
And the route to the logs, because most of us have to look up where they are! ;-) -
Calendar failed to load - check the logs
Noticed neither of my two calendars were working on my MM over the weekend.
Not having time to investigate, I left it for another day.
Then one calendar worked but not the other, then they swapped over!
Now they’re both working.
On checking the logs, there are a lot of these timeout errors:[2025-12-07 16:11:33.349] [ERROR] Calendar Error. Could not fetch calendar: https://calendar.google.com/calendar/ical/#################group.calendar.google.com/private-5##############################/basic.ics TypeError: fetch failed at node:internal/deps/undici/undici:13510:13 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { [cause]: ConnectTimeoutError: Connect Timeout Error (attempted address: calendar.google.com:443, timeout: 30000ms) at onConnectTimeout (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:876:19) at Immediate._onImmediate (/home/pi/MagicMirror/node_modules/undici/lib/core/util.js:845:11) at process.processImmediate (node:internal/timers:485:21) { code: 'UND_ERR_CONNECT_TIMEOUT' }Looks like a timeout error at calendar_dot_google_dot_com and nothing to do with MM.
However, a more user friendly error message in place of the failed calendar would be nice to see. -
RE: Update, unable to connect.
Hahhahaaaa! Yes, well I do make regular backups of config and CSS, it was the modules folder I was missing. Lesson learned there.
-
RE: Embed Grafana Charts - xframe issue
@hs said in Embed Grafana Charts - xframe issue:
allow_embedding=true
For future me and of course anyone else looking for this, the setting is in the [Security] section of /etc/grafana/grafana.ini (Assumes Grafana is hosted on a Pi or other Linux distro)
-
RE: Update, unable to connect.
I couldn’t use that as I the Pi had no network, no file manager. It was bricked :(
New OS, new default vanilla MM all good.
And then I remembered the orig MM was still on a SD Card before I swapped over to a USB drive.
Copied all I needed, seems to be all good so far!Thanks for your help. :)
-
MMM-doomsDay
Apologies if this request is in the wrong place…
MMM-doomsDay isn’t listed anywhere, yet is still on GitHub and working just fine on my MM.
What’s the reason for it not being on the module list or the module wiki page?Thank you.
-
RE: Request: Flight tracker using PiAware
+1 for this, please. I have a Pi Aware in the loft and would be interested in adding its data to MM.
-
RE: Update, unable to connect.
Pi (Pi4 in metal heat-sink case) was running really warm. Powered it off and left it for a while.
Powered on, it has no networking and file manager does nothing.
If I can get networking enabled, I’ll make a config and CSS backup.Looks like it’s going to need an OS reinstall which will have to wait until I have time to do so.
I’ll report back when that’s done. -
RE: Update, unable to connect.
pi@mmv2:/ $ pm2 stop all [PM2] Applying action stopProcessId on app [all](ids: [ 0 ]) [PM2] [MagicMirror](0) â ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ â id â name â mode â ⺠â status â cpu â memory â ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼ââââââââââ⤠â 0 â MagicMirror â fork â 300 â stopped â 0% â 0b â ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ pi@mmv2:/ $ cd ~/MagicMirror pi@mmv2:~/MagicMirror $ rm -rf node_modules pi@mmv2:~/MagicMirror $ npm install npm error code EIO npm error syscall read npm error errno -5 npm error EIO: i/o error, read npm error A complete log of this run can be found in: /home/pi/.npm/_logs/2025-08-17T11_35_16_106Z-debug-0.log pi@mmv2:~/MagicMirror $ npm start > magicmirror@2.32.0 start > node --run start:x11 /bin/sh: 1: ./node_modules/.bin/electron: not found -
RE: Update, unable to connect.
@mumblebaj said in Update, unable to connect.:
npm run config:check
pi@mmv2:~/MagicMirror $ npm run config:check > magicmirror@2.32.0 config:check > node js/check_config.js [2025-08-17 12:14:16.030] [INFO] Checking config file /home/pi/MagicMirror/config/config.js ... [2025-08-17 12:14:16.285] [ERROR] Your configuration file contains syntax errors :( Line 99 column 21: 'Log' is not defined.Lines 97/98/99:
// Override start method. start: function () { Log.log("Starting module: " + this.name); -
RE: Update, unable to connect.
@sdetweil said in Update, unable to connect.:
pm2 logs --lines=20
Seems to loop through this:
0|MagicMirror | > magicmirror@2.32.0 start 0|MagicMirror | > node --run start:x11 0|MagicMirror | [2025-08-16 19:11:31.316] [LOG] Starting MagicMirror: v2.32.0 0|MagicMirror | [2025-08-16 19:11:31.359] [LOG] Loading config ... 0|MagicMirror | [2025-08-16 19:11:31.363] [LOG] config template file not exists, no envsubst 0|MagicMirror | [2025-08-16 19:11:31.976] [INFO] Checking config file /home/pi/MagicMirror/config/config.js ... 0|MagicMirror | [2025-08-16 19:11:32.117] [ERROR] Your configuration file contains syntax errors :( 0|MagicMirror | Line 99 column 21: 'Log' is not defined. PM2 | App [MagicMirror:0] exited with code [1] via signal [SIGINT] PM2 | App [MagicMirror:0] starting in -fork mode- PM2 | App [MagicMirror:0] online 0|MagicMirror | bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8) -
RE: Update, unable to connect.
pi@mmv2:~/MagicMirror $ node -v v22.14.0 pi@mmv2:~/MagicMirror $ pm2 stop MagicMirror [PM2] Applying action stopProcessId on app [MagicMirror](ids: [ 0 ]) [PM2] [MagicMirror](0) â ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ â id â name â mode â ⺠â status â cpu â memory â ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼ââââââââââ⤠â 0 â MagicMirror â fork â 2120 â stopped â 0% â 0b â ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ pi@mmv2:~/MagicMirror $ pm2 start MagicMirror [PM2] Applying action restartProcessId on app [MagicMirror](ids: [ 0 ]) [PM2] [MagicMirror](0) â [PM2] Process successfully started ââââââ¬âââââââââââââââââââââ¬âââââââââââ¬âââââââ¬ââââââââââââ¬âââââââââââ¬âââââââââââ â id â name â mode â ⺠â status â cpu â memory â ââââââ¼âââââââââââââââââââââ¼âââââââââââ¼âââââââ¼ââââââââââââ¼âââââââââââ¼ââââââââââ⤠â 0 â MagicMirror â fork â 2120 â online â 0% â 2.6mb â ââââââ´âââââââââââââââââââââ´âââââââââââ´âââââââ´ââââââââââââ´âââââââââââ´âââââââââââ pi@mmv2:~/MagicMirror $ -
RE: Update, unable to connect.
Same issue today. Tried with force but still no MM.
node -v = v22.14.0
-
RE: MMM-ClosestFlight stuck at "Checking the airspace...."
Is this module no longer supported?