@MMRIZE Ha! I swear I’d tried that! When I did it would just show it as a numeric month and add the year.

Working now though. Thanks

Thanks for all the help!
Ideally I was hoping for weekly view but where the first day is the current day, so that on Friday I can still see what’s coming up in the next week.

I understand that CX3A shows this information but it’s not in the same format and I prefer the look of the weekly format with CX3

@MMRIZE said in MMM-CalendarExt3:

Weird. cellDateOptions: {day:‘numeric’} should show only the number of the day. What is your locale? or check the typo.

Locale is en-US.

I’m in weekly view.

It’s only on the first of the week and the current day. I’ve worked around it in CSS but I wouldn’t have expected it to show using

cellDateOptions: {day:'numeric'}

This image is without any custom CSS applied

This is the config.

{
		  module: "MMM-CalendarExt3",
		  position: "lower_third",
		  classes: "SceneFamily",
		  header: 'Family Week',
		  config: {
			mode: "week",
			instanceId: "FamilyCalendar",
			weekIndex: 0,
			firstDayOfWeek: 0,
			weeksInView: 1,
			locale: 'en-US',
			maxEventLines: 5,
			firstDayOfWeek: 1,
			calendarSet: ['us_holiday', '1', '2', '3', '4', '5'],
			useWeather: false,
			displayWeatherTemp: false,
			useSymbol: true,
			fontSize: "16px",
			displayEndTime:true,
			
			
		  }
		},

Working on moving from CX2 to CX3.

A few things I’m being challenged by. Some might be limitations but figured I’d ask

1. In CX2 there were more icon sets available. Is CX3 limited to Font Awesome because the default calendar is?

2. Can CX3 in weekly view start from the current day vs. beginning of the week?

3. I can see there’s a module-header. How can I make the CX3 title from the config show there?

Possible CSS Questions
4) I’m having trouble getting the Day header to show only numeric for the whole week. It shows Month Day (Jul 3) in the first two days and then numeric for the rest. (I tried cellDateOptions: “{day: ‘numeric’}” in the config for the module and it shows “7/3/2023” and “7/4/2023” in the first two days. This is what I had to do to hide it with CSS.

.CX3 .week:nth-child(2) .cell:first-child .cellDate *
{
       display: none;
}

.CX3 .week:nth-child(2) .cell:first-child .cellDate .day
{
       display: inline-block;
}
   
.CX3 .today .cellDate :not(.day)
{
   display: none;
}

5. I had CX2 showing like this with the title on one line and the time on the next. Can that be done?
   
6. How to remove colored dot signifying calendar? I like a border instead?

@sdetweil Thanks

@MMRIZE MMM-Scenes is probably closer to what I’m looking for.
Currently I have 3 views in CalendarExt2.

1. Family Calendar (this includes multiple calendars for the whole family)
2. Kid 1 Calendar (this is multiple calendars for Kid 1 like school events, homework, and scheduled appointments)
3. Kid 2 Calendar (this is multiple calendars for Kid 1 like school events, homework, and scheduled appointments)

In addition along with each view I show a Daily Agenda for each kid which when it’s not summer shows their schedule for the day. (their school schedule isn’t the same each day)

I use MMM-Buttons to be able to cycle through the pages/views on demand (it also cycles on a time delay as well, but sometimes you need to get to one of them immediately).

@MMRIZE said in MMM-CalendarExt2:

Can you send me the calendars and your config? (eouia0819@gmail.com)

I actually got it working. I needed to do

npm install request

It started working after that. I’m working on setting up another Pi and I’m going to see if I can get CalendarExt3 working in a way that works for what I want it to do. I saw @sdetweil had an CalendarExt3Agenda module that might help. I think I just need to figure out the Views and paging between to move forward to CalendarExt3.

I know this module is inactive as @MMRIZE has moved on to CalendarExt3 but I’m hoping someone can point me where to look.

I hadn’t swapped because I was using some functionality in CalendarExt2 that I’m not sure is available in CalendarExt3. (multiple views, weekly and daily calendars)

With the latest update though my calendars aren’t loading. The module isn’t even appearing on screen despite no errors in the log.

@sdetweil Apologies. You did say that already and it didn’t penetrate. Replaced with your fork and it looks like I’m mostly back up. CalendarExt2 doesn’t seem to be loading though. I’ll have to dig into that later.

@MMRIZE I did an apt-update and upgrade . Actually the node version went too far. It was suddenly version 20+ I just reset it to 16.20.1 (which is what’s showing up as I do the clean install on the other machine). That seems to get me back to where I might be able to recover from this mess.

@sdetweil I used your upgrade script but I’m not sure what happened. I’m now at least back to this

pi@MagicMirror:~/MagicMirror/modules/MMM-Buttons $ npm install

> Magic-Mirror-Module-Buttons@1.0.0 postinstall
> node_modules/.bin/electron-rebuild -e ../../node_modules/electron

⠋ Searching dependency tree
An unhandled error occurred inside electron-rebuild
Could not detect abi for version 25.2.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron

Error: Could not detect abi for version 25.2.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron
    at Object.getAbi (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/node_modules/node-abi/index.js:36:9)
    at new Rebuilder (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/lib/src/rebuild.js:126:48)
    at rebuildWithOptions (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/lib/src/rebuild.js:404:23)
    at Object.doRebuild [as rebuild] (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/lib/src/rebuild.js:427:16)
    at /home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/lib/src/cli.js:124:33
    at Generator.next (<anonymous>)
    at fulfilled (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/electron-rebuild/lib/src/cli.js:6:58)
npm ERR! code 255
npm ERR! path /home/pi/MagicMirror/modules/MMM-Buttons
npm ERR! command failed
npm ERR! command sh -c -- node_modules/.bin/electron-rebuild -e ../../node_modules/electron

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/pi/.npm/_logs/2023-07-03T13_56_15_900Z-debug-0.log

Any ideas

@sdetweil I’m going to go ahead and start over on with a clean build on bullseye. This one is still running on buster which may be part of the issue. I’ve got another Pi I can use and I’ll just use the config from this one and rebuild it. Thanks for the quick reply.

So after I ran the update script, magicmirror wouldn’t start.

This was in the log

[03.07.2023 08:40.46.643] [ERROR] 2023-07-03T08:40:46 <error> (node:17008) UnhandledPromiseRejectionWarning: Error: The module '/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/build/Release/epoll.node'
was compiled against a different Node.js version using
NODE_MODULE_VERSION 93. This version of Node.js requires
NODE_MODULE_VERSION 116. Please try re-compiling or re-installing
the module (for instance, using `npm rebuild` or `npm install`).
    at process.func [as dlopen] (node:electron/js2c/asar_bundle:2:1822)
    at Module._extensions..node (node:internal/modules/cjs/loader:1354:18)
    at Object.func [as .node] (node:electron/js2c/asar_bundle:2:1822)
    at Module.load (node:internal/modules/cjs/loader:1124:32)
    at Module._load (node:internal/modules/cjs/loader:965:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
    at Module.require (node:internal/modules/cjs/loader:1148:19)
    at require (node:internal/modules/cjs/helpers:110:18)
    at bindings (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/bindings/bindings.js:112:48)
    at /home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/epoll.js:7:31
    at Object.<anonymous> (/home/pi/MagicMirror/modules/MMM-Buttons/node_modules/epoll/epoll.js:15:3)
    at Module._compile (node:internal/modules/cjs/loader:1269:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1324:10)
    at Module.load (node:internal/modules/cjs/loader:1124:32)
    at Module._load (node:internal/modules/cjs/loader:965:12)
    at f._load (node:electron/js2c/asar_bundle:2:13330)
(Use `electron --trace-warnings ...` to show where the warning was created) (/home/pi/MagicMirror/node:internal/process/warning:60 writeOut)
[03.07.2023 08:40.46.645] [ERROR] 2023-07-03T08:40:46 <error> (node:17008) 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: 1) (/home/pi/MagicMirror/node:internal/process/warning:60 writeOut)
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to retrieve device information
MESA-LOADER: failed to open kms_swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load driver: kms_swrast
MESA-LOADER: failed to open swrast (search paths /usr/lib/arm-linux-gnueabihf/dri:\$${ORIGIN}/dri:/usr/lib/dri)
failed to load swrast driver
Gdk-Message: 08:40:55.667: electron: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

I tried

npm rebuild

I tried

npm install

Wasn’t working.

An unhandled error occurred inside electron-rebuild
Could not detect abi for version 25.2.0 and runtime electron.  Updating "node-abi" might help solve this issue if it is a new release of electron

I saw a message

npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'lru-cache@10.0.0',
npm WARN EBADENGINE   required: { node: '14 || >=16.14' },
npm WARN EBADENGINE   current: { node: 'v16.13.1', npm: '9.7.1' }
npm WARN EBADENGINE }

I thought it was saying that my node was just a bit out of date, so I made the mistake of running

nvm install node

and now I get this

node: /usr/lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)

help?