1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether b8:27:eb:ee:09:64 brd ff:ff:ff:ff:ff:ff
3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 00:0f:60:04:20:d4 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.100/24 brd 192.168.1.255 scope global dynamic noprefixroute wlan0
valid_lft 45176sec preferred_lft 34376sec
inet6 fe80::3e7d:5421:775:6ad0/64 scope link
valid_lft forever preferred_lft forever
Read the statement by Michael Teeuw here.
Posts made by redink
-
RE: MMM-CalendarExt3 stopped working
-
RE: MMM-CalendarExt3 stopped working
@sdetweil thanks for taking the time. It’s sent.
-
RE: MMM-CalendarExt3 stopped working
@sdetweil Thank you, but that didn’t seem to help. I use this script to update MM https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh
So, I wonder if something isn’t getting updated.
-
RE: MMM-CalendarExt3 stopped working
@sdetweil I must be missing something, I don’t see what file this code should go in.
-
MMM-CalendarExt3 stopped working
I updated Magic Mirror today and my calendar is no longer working.
Here’s the error that I get
[02.01.2024 17:08.23.640] [ERROR] Calendar Error. Could not fetch calendar: https://calendar.google.com/calendar/ical/xxxxx/basic.ics TypeError: fetch failed at Object.fetch (node:internal/deps/undici/undici:11576:11) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) { cause: ConnectTimeoutError: Connect Timeout Error at onConnectTimeout (node:internal/deps/undici/undici:8522:28) at node:internal/deps/undici/undici:8480:50 at Immediate._onImmediate (node:internal/deps/undici/undici:8511:13) at process.processImmediate (node:internal/timers:476:21) { code: 'UND_ERR_CONNECT_TIMEOUT'
And here’s my config
{ module: "MMM-CalendarExt3", position: "bottom_bar", title: "", config: { mode: "week", instanceId: "basicCalendar", locale: 'en-EN', weekIndex: 0, weeksInView: 4, maxEventLines: 5, firstDayOfWeek: 0, fontSize: "22px", eventTimeOptions: { hour12: false, hour: "2-digit", minute: "2-digit" }, useSymbol: false, calendarSet: ['School', 'Family'], } }, { module: "calendar", config: { broadcastPastEvents: true, // <= IMPORTANT to see past events calendars: [ { name: "Family", url: "https://calendar.google.com/calendar/ical/xxxxxxxxxxxx/basic.ics", color: "green" }, { name: "School", url: "https://calendar.google.com/calendar/ical/xxxxxxxxxx%40group.calendar.google.com/public/basic.ics", color: "blue", filter: (event) =>{ if (event.title.search("......") > -1) { return true } else { return false } }, } ] }, },
I tested both calendar URLs and they do download the ICS file just fine. I’d appreciate any help.
-
MMM-AQI display help
I am trying to get MMM-AQI running, but it’s not displaying correctly. It’s showing the wrong location, not matter what I try. The most recent thread on this module is a few years old, so I am starting a new one.
-
RE: MMM-CalendarExt3
Can anyone help me make one last tweak? I would like to get rid of the icon next to the event name and display the event time in just a 24 hour format (23:30 instead of 11:30 PM). Here’s my current config
{ module: "MMM-CalendarExt3", position: "bottom_bar", title: "", config: { mode: "week", instanceId: "basicCalendar", locale: 'en-EN', weekIndex: 0, weeksInView: 4, maxEventLines: 5, firstDayOfWeek: 0, fontSize: "22px", eventTimeOptions: { hour: "2-digit", minute : "2-digit" }, useSymbol: false, calendarSet: ['School', 'Family'], } },
-
RE: Every time I run an update, something breaks. This time is no exception
@sdetweil What I kept trying to do is get node and npm updated, but I royally screwed things up where nothing is working anymore. I can’t use the PM2 command to start and stop things or see the status. So, I just nuked the SD card and am starting from scratch. I will use your scripts.
-
RE: Every time I run an update, something breaks. This time is no exception
@sdetweil, i just kinda kept trying random things, including your script and I think I made things worse. I did try to update node and npm, but something is really out of whack.
The error I keep seeing over and over again is
npm WARN npm npm does not support Node.js v10.24.0 npm WARN npm You should probably upgrade to a newer version of node as we npm WARN npm can't make any promises that npm will work with this version.
when I run “node -v”, i see v19.8.1, so I have no idea where 10.24.0 is coming from. I am close to just nuking my pi and starting from scratch.