getting the same issue with v0.69.1
I have even started in safe mode and tried to update all the HA nodes, then start, still getting

[red] Uncaught Exception:
8 Dec 10:48:03 - [error] UnhandledPromiseRejection: 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(). The promise rejected with the reason "#<Object>".

Add the following snippet to your settings.js file to get more detailed information about the rejected promise:

process.on('unhandledRejection', (reason, p) => {
  console.log('Unhandled Rejection: ', p, 'reason:', reason);
});

Add the following snippet to your settings.js file to get more detailed information about the rejected promise:

process.on('unhandledRejection', (reason, p) => {
  console.log('Unhandled Rejection: ', p, 'reason:', reason);
});

So after adding that to the end of my settings.js, your addon loads but gives this:

24 Dec 10:36:36 - [debug] [server:Home Assistant] States Loaded
24 Dec 10:36:36 - [debug] [server:Home Assistant] Services Loaded
24 Dec 10:36:36 - [debug] [server:Home Assistant] HA State: running
24 Dec 10:36:36 - [debug] [server:Home Assistant] Integration: notloaded
Unhandled Rejection:  Promise {
  <rejected> { code: 'unknown_command', message: 'Unknown command.' }
} reason: { code: 'unknown_command', message: 'Unknown command.' }
Unhandled Rejection:  Promise {
  <rejected> { code: 'unknown_command', message: 'Unknown command.' }
} reason: { code: 'unknown_command', message: 'Unknown command.' }

@ctark you getting the same issue? I don't have time to test adding this to my nodes, as its doing it in my production environment :(
And I don't have a way to test without taking lots of time reloading from backups, back and forth.

Set debug logging and audit true, i get a bit moreinformation...

6 Dec 14:36:10 - [error] UnhandledPromiseRejection: 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(). The promise rejected with the reason "#<Object>".

    at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)

    at processPromiseRejections (node:internal/process/promises:470:17)

    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

I get the same as ctark

Unhandled Rejection:  Promise {

  <rejected> { code: 'unknown_command', message: 'Unknown command.' }

} reason: { code: 'unknown_command', message: 'Unknown command.' }

Unhandled Rejection:  Promise {

  <rejected> { code: 'unknown_command', message: 'Unknown command.' }

} reason: { code: 'unknown_command', message: 'Unknown command.' }

but now NR doesn't crash, which is good.
I also get this in NR GUI, which are two objects, so may give a hint where in your code the issue is

Not sure those are related. But find it interesting that I get two Unhandled rejections, and your code is displaying two nodes with issues.

@ctark you getting the same issue? I don't have time to test adding this to my nodes, as its doing it in my production environment :( And I don't have a way to test without taking lots of time reloading from backups, back and forth.

Yes, started when I updated node red and all nodes to latest. I then got a log entry saying that home assistant needed to be 2023.12 or later (I was pinned to 2023.08 at the time).
Then, when I updated to 2023.12, node red loaded but then crashed due to the above issue.
I have not tried fully updating HA as there are some breaking changes I have to deal with first. The snipped Zachowj suggested stops node red from crashing atleast, so it's good enough for now. I don't have a dev environment so I loose control of the lights in the house when I don't have node red active.

Add the following snippet to your settings.js file to get more detailed information about the rejected promise:

process.on('unhandledRejection', (reason, p) => {
  console.log('Unhandled Rejection: ', p, 'reason:', reason);
});

Do you need anything else? @zachowj

The unhandled exception is caused by Node-RED sending a command over the WebSocket connection that isn’t registered with Home Assistant. This could happen if Node-RED thinks the custom integration is installed when it’s not or if a required component isn’t loaded.

To identify the command sent to Home Assistant, set the logger level for websocket_api to info. You can do this in the Home Assistant configuration or by using the logger.set_level service.

homeassistant.components.websocket_api: info

https://www.home-assistant.io/integrations/logger/

The unhandled exception is caused by Node-RED sending a command over the WebSocket connection that isn’t registered with Home Assistant. This could happen if Node-RED thinks the custom integration is installed when it’s not or if a required component isn’t loaded.

To identify the command sent to Home Assistant, set the logger level for websocket_api to info. You can do this in the Home Assistant configuration or by using the logger.set_level service.

homeassistant.components.websocket_api: info

https://www.home-assistant.io/integrations/logger/

The exception is caused by the Node code not catching exceptions. In my case, looks like it may not be handling errors when entity ids do not exist.

i'll try to do more debugging for you when i have a chance to shutdown my production machine.

Hopefully you have time to check the code for where exceptions are not captured.

Thanks!

In my case, looks like it may not be handling errors when entity ids do not exist.

It’s unrelated to entity IDs. As mentioned earlier, the issue arises from Node-RED sending a command that Home Assistant doesn’t have a handler for. The "unknown command" log you shared confirms this.

Here’s the relevant code in Home Assistant that returns the error message:
https://github.com/home-assistant/core/blob/249d93574ad42e5acc29b04753f607fe86ab3851/homeassistant/components/websocket_api/connection.py#L220-L227

Identifying the specific command being sent would save time and avoid the need to search through the entire codebase.

@zachowj

2024-12-31 14:19:12.306 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [140039597697600] Received unknown command: config/floor_registry/list
2024-12-31 14:19:12.307 INFO (MainThread) [homeassistant.components.websocket_api.http.connection] [140039597697600] Received unknown command: config/label_registry/list

On HA
Core 2024.1.6
Frontend 20240104.0

That makes sense. The label and floor registries were introduced in Home Assistant 2024.3.0. The minimum Home Assistant version requirement should have been updated when version 0.66.0 was released.

Thanks for helping pinpoint the exact cause of this issue!

That makes sense. The label and floor registries were introduced in Home Assistant 2024.3.0. The minimum Home Assistant version requirement should have been updated when version 0.66.0 was released.

Thanks for helping pinpoint the exact cause of this issue!

Thanks for the awesome integration and putting up with me, and helping me learn how to better debug. hopefully should I find another one I can provide better details from the start.

Could the code not catch these errors to maintain backward compatibility? I don't like updating HA very often on the one system as its a customer facing production "system" that runs.

take care!

Could the code not catch these errors to maintain backward compatibility? I don't like updating HA very often on the one system as its a customer facing production "system" that runs.

Maintaining backward compatibility is always a priority, but in this case, the floor and label registries are now core requirements for several nodes. Adding workarounds or version gates to handle older Home Assistant versions would significantly increase maintenance complexity.