@Old_Death
I updated it to 1.4.4. Please update or reinstall the module.
I found a bug about twice applying the user event filter/transformer on the drawing miniMonth and agenda board.
However, that is not the real reason for your symptoms. You just made a mistake on your filtering. (You drop out “Natalia” events by filtering, so they were not able to be transformed.)

Anyway, here is my example.

eventFilter: (ev) => {
	return (ev.title.search('Test') > -1)
},
eventTransformer: (ev) => {
	ev.title = ev.title.replace('Test', '@')
	return ev
}

This code means

1. Filter out all other events except the event which has Test in the title.
2. Then transform Test to @.

You can see the result below;

ORIGINAL

CONFIGURED

@Old_Death
Sorry, there was a bug that filtering or transforming performs twice, I’ll fix it soon.

@Old_Death
You want;

1. Only events which have title “Natalia” would be shown, others should be filtered out.
2. Then the event (with title “Natalia”) should change its title. Right?

@Old_Death
It is contradiction. You can’t do both thing - drop the event or replace the title at same time. What is your purpose? (And filtering is executed primarily than transforming)

@jlward73
I updated CX3J to 1.0.1 to represent more detailed selectors. And by default, the border would be shown on today’s column.

@jlward73

Is there a way to isolate the entire day’s column?

It is not supported. Well, at least not in a simple, easy way. But I’ll add that in the next update soon.

canton means the top-left corner of the table. I’m not sure of the exact term in native English. :)
index means hour-index(left edged) of the table.
gridCell means the table’s rectangle grid (usually 30 minutes of the day).

@jlward73
Default hourLength is 4, so it seems your config is missing or mistyping that value.

@Sickdove
By the way, why do you consider Beaglebone Black? It is more expensive than RPI3B+ (at least in Germany now). Is there any benefit to that form factor?

@jlward73

/* config/config.js */

{
	module: "MMM-CalendarExt3Journal",
	position: "bottom_bar",
	config: {
		height: '50vh', // Half of the screen
		hourLength: 12, // Display 12 hours
		beginHour: 7, // From 7 o'clock
		staticWeek: true, // Since Monday
		days: 7, // For 7 days
	}
},

@fedale @Welle05

See this.
https://github.com/MMRIZE/MMM-CalendarExt3/wiki/To-fix-wrong-repeated-fullday-event-displaying-(MM-2.27)

@jlward73
Let’s make things simpler.
What is your current major problem. CX3J is not showing? Or Button is not working?
Solve it one-by-one.

If your issue is about Button, create a new post about it. You don’t have to mention CX3J not to make things complex. Only focus on the Button’s work (and its notification maybe.)

If your issue is CX3J’s working, Forget Button things.
Backup your current config then remove all other modules from config except clock, calendar, MMM-CalendarExt3Journal. Then execute MM.
Show me the whole front-end log.

@jlward73
You can do it with only 1 instance by notification juggling. Tomorrow I’ll show you the example. (Of course you can swap 2 of instances also)

PS.
Sorry. MMM-Carousel2 Doesn’t emit any notification to use.

@bramsel
This may be related
https://github.com/MMRIZE/MMM-CalendarExt3/wiki/To-fix-wrong-repeated-fullday-event-displaying-(MM-2.27)

@lightfixer2000
Happy to hear. I’ll reveal that option in the readme. Recently, someone else reported me the same issue, and the solution was the same. I’ll change the default value soon.

@lightfixer2000
At this moment, I’m unsure the exact symptom what you said.
There is an undocumented options for more detail configuration.
Try expand: false, in your module config.

{
  module: "MMM-CalDAV", 
  config: {
    servers: [
      { 
        envPrefix: "ICLOUD_", // I assumed.
        serverUrl: "https://caldav.icloud.com", 
        expand: false,  // <== This.
        targets: [
        ...

I’m not sure whether this will help yours or not. I just suspect.

PS. (more detail).
This option is related to expanding repeated events to a series of single independent events. As far as I remember, in some prior calendars, there were some issues handling repeated events by RRULE. So, I made this module to forcefully avoid that issue by default. I think recently things might be changed, so hidden option expand: true might cause your symptom.

@ffingers6

/* config/config.js */
{
  module: "calendar",
  config: {
    broadcastEvents: true,
    defaultSymbolClassName: "", // This is needed to use the iconify icons instead of the font-awesome icons
      calendars: [
        {
          symbol: "noto:calendar",
          url: "...",
          color: "violet",
    ...
  }
},
{
  module: "MMM-CalendarExt3Agenda",
  position: "bottom_bar",
  config: {
    showMiniMonthCalendar: false,
    locale: "en-US",
    startDayIndex: 0,
    endDayIndex: 2,
    useIconify: true,
  }
},

/* css/custom.css */
.CX3A {
  max-width: 100%;
}

.CX3A .agenda {
  display: flex;
  flex-flow: row nowrap;
  justify-content: space-between;
  gap: 10px;
  mask-image: none;
}

.CX3A .agenda .cell {
  flex-grow: 1;
  flex-basis: 0;
  border-bottom: none;
}

.CX3A .agenda .cell .cellHeader {
  border-bottom: 2px solid gray;
  margin-bottom: 5px;
}

.CX3A .agenda .cell .cellHeaderMain {
  justify-content: space-between;
  flex-grow: 1;
  padding: 5px;
}

.CX3A .event.singleday {
  border-left: 2px solid var(--calendarColor);
  padding-left: 3px;
  margin-bottom: 1px;
  background-color: color-mix(in srgb, var(--calendarColor), transparent 75%);
}

.CX3A .event .time {
  order: 2;
}

.CX3A .event .title {
  flex-grow: 2;
}

.CX3A .cellBody {
  line-height: 120%;
}

.CX3A .cellBody .fullday {
  padding-bottom: 5px;
}

.CX3A .cellBody .fullday .event {
  max-width: 100%;
}

For the size, you may need some manual adjustment for your view.

@shall_
Are you using MMM-GoogleCalendar?

@ffingers6
I’ll try soon.

@sdetweil
Of course I can. I have already provided that manual method to my CX3 users. (https://github.com/MMRIZE/MMM-CalendarExt3/wiki/To-fix-wrong-repeated-fullday-event-displaying-(MM-2.27))

However, the value of notification should be trustable or consistent. All other kinds of events, like In-A-Day single events, Multiday-but-not-fullday-event, and even Repeated-Not-Fullday-event, could deliver the proper time, but only Repeated-Fullday events delivered the wrong value. That is out of common sense.

At least, it should have been guided as an intentional design. (I wasted several hours trying to guess what happened. Who could imagine the notification value was wrong?)

PS. Ah, I forgot there was another case; imperial units on broadcasted weather information. :)