Jason

The error indicates that the action field, now replacing the `domain` and `service` fields, expects a valid format like `button.press`. However, it's receiving an invalid format, such as `off-press`. Are...

The action node (formerly the call-service node) has always supported [config overrides](https://zachowj.github.io/node-red-contrib-home-assistant-websocket/node/action.html#input) via the `msg.payload` object. This should maintain backward compatibility with existing flows, except for the deprecation of the...

@MostHated `msg.payload.action` is now an input property of the action node, which was introduced as a breaking change. When you set `msg.payload.action = "";` it overrides the action field in...

The intended use case for Home Assistant nodes has always been to allow setting default values in the node configuration, with the flexibility to override some or all of these...

@MostHated, In the action node update the data field to only include the default value: {"transitions": 0.5}. Then, pass any overrides through msg.payload.data in your function. Alternatively, if you prefer...

When the Home Assistant server configuration is deployed, the integration establishes a persistent WebSocket connection to Home Assistant. At that point, several event listeners are registered to monitor things like...

To narrow down the `UnhandledPromiseRejection` can you add the following code to your `settings.js` file to help capture a better description of the error? This can removed once the error...

> here is the file after editing, I assume this is at the right scope within this module ? correct

How many entities does your Home Assistant instance have? You can find out by running this template in the Developer Tools > Template section: ```jinja {{ states | count }}...

Try updating to the latest release, v0.74.2, and check if there's any improvement in the output speed.