Unhandled Promise Error - Calendar Related?

[wolffenstine]

First time poster, let me know if I messed up here :)

I am running into the following in my error log after reducing my config to only MMM-CalendarExt2 and MMM-CalendarExtPlan. Any ideas here? I don’t think its related to my configs at all since they are very basic and worked previously. The only change is a cross-country move and trying to set it all up again. All other modules (now commented out) are working fine. This is the entire error file.

[07.05.2022 15:01.53.586] [ERROR] (node:2234) ExperimentalWarning: The ESM module loader is experimental.
[07.05.2022 15:01.53.649] [ERROR] (node:2234) UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:698:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:47:40)
    at link (internal/modules/esm/module_job.js:46:36)
[07.05.2022 15:01.53.650] [ERROR] (node:2234) 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: 6)
[07.05.2022 15:01.53.651] [ERROR] (node:2234) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
[07.05.2022 15:01.53.652] [ERROR] (node:2234) UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:698:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:47:40)
    at link (internal/modules/esm/module_job.js:46:36)
[07.05.2022 15:01.53.653] [ERROR] (node:2234) 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: 7)
[07.05.2022 15:01.53.654] [ERROR] (node:2234) UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:698:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:47:40)
    at link (internal/modules/esm/module_job.js:46:36)
[07.05.2022 15:01.53.656] [ERROR] (node:2234) 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: 8)
[07.05.2022 15:01.53.657] [ERROR] (node:2234) UnhandledPromiseRejectionWarning: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only file and data URLs are supported by the default ESM loader
    at Loader.defaultResolve [as _resolve] (internal/modules/esm/resolve.js:698:11)
    at Loader.resolve (internal/modules/esm/loader.js:97:40)
    at Loader.getModuleJob (internal/modules/esm/loader.js:243:28)
    at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:47:40)
    at link (internal/modules/esm/module_job.js:46:36)
[07.05.2022 15:01.53.658] [ERROR] (node:2234) 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: 9)

[sdetweil]

@wolffenstine what is the result of

node -v

[wolffenstine]

@sdetweil v14.17.4

[sdetweil]

@wolffenstine is this a windows system?

[wolffenstine]

@sdetweil No, Raspberry Pi Ubuntu

[chubbs]

I am raspbian, just upgraded nodejs to 16.15.0 and receiving the exact same error.

edited to add: I tried the URL in a browser and it downloads the ICS file to my machine just fine. I also tried https and http, and using a public calendar as well.

[sdetweil]

@chubbs is this a windows system?

does your cal url start with webcal?

[chubbs]

@sdetweil I tried with all options (http, https, webcal). The only thing that worked for me was backing up the config files, removing, and re-installing.

[sdetweil]

@chubbs weird. that says it was some kind of disk corruption…

u just reinstalled MagicMirror, right?