@sdetweil
Thanks for your explanation always.
I’ll add small message in the screen on waiting - “Waiting calendar fetch…” or something informative in the next update…

@MDWEBB said in New module installer:

[ERROR] ReferenceError: HTMLElement is not defined

This error message seems to be caused by some JS validator trying to check the browser-oriented syntax on the nodeJS environment.

@MDWEBB
You’d better start from a clean configuration and then add one by one to find what was wrong.

@oquendo421

maximumEntries: 4,

Hmmmm… I think you’d better increase this value more.

@rkorell
Do you have any sketch for AS-IS and TO-BE?

@plainbroke @reverendz
Instead of .date_xx, use .today to point today’s cell.

And about the circle; https://forum.magicmirror.builders/topic/18324/mmm-calendarext3-show-color/11?_=1736098133616

@rkorell
CX3A is identified with CSS selector “.CX3A” to be distinguished from CX3.

I think I found it.

Add these into the default calendar module.

maximumEntries: 100,
maximumNumberOfDays: 365,

@tke499
Send me your ics file or url. (eouia0819@gmail.com)

@redfishbluefish
At first, I thought the New Year's Day event wasn’t visible because of a time zone issue (since I live in Germany, it’s already January 2nd here).

So, I downloaded the ICS file and changed the date of the New Year's Day event from 20250101 to 20250102 for testing. When I tested it, I encountered the same issue you mentioned!!!

I was quite confused, but to confirm, I used the following:

eventPayload: (events) => {
	console.log(events)
	return events
},

The eventPayload function is a great place to check what data has actually been broadcasted since it executes whenever events are received.

As a result…
??? New Year's Day isn’t being broadcasted?? I still don’t know why.

You can compare the display(left) and the console(right). In right, there is no New Year's Day event. the calendar module doesn’t emit that event. CX3 cannot draw undelivered events.

@sdetweil I think it’s better you check this symptom. the default calendar miss this event to broadcast, but don’t know why.

@tke499

Generally,

This message is just an warning can be ignored.
However, in practice, stopping at that point usually corresponds to the following cases:

1. (Most common case): The CX3 module has not been properly installed. In most situations, this happens because the CX3_Shared library is not correctly installed. To resolve this, navigate to the CX3 directory, run git pull, and then execute npm install. This resolves most issues. If it doesn’t, simply delete the entire CX3 directory and reinstall it. It only takes about 15 seconds.

2. In very rare cases, other modules may cause errors during DOM creation, which can have an impact. However, this is highly uncommon, so the cause is typically case 1.