Jason

Are there any browser errors when the trigger fails to load?

All those experiencing the same issue, please share your diagnostic information. https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html

@johnculviner Why does each entity-config show an exclamation error? Does it have a Home Assistant server selected in the configuration?

@johnculviner Does this happen immediately after deployment? Is your deployment method set to "Full"? If so, each deployment creates a new connection to Home Assistant, which isn't instant and may...

> Sorry. I am only getting a blank window when trying that. Looks like you clicked on the button on the bottm of the debug tab not the Home Assistant...

@casekhor Your diagnostic info shows **Companion version: 0.0.0**, meaning the custom component isn't installed in Home Assistant. If you installed it via HACS, you likely missed a step—specifically **step 6**...

@mrkrb The "Companion version" shown in your diagnostic info indicates that the custom integration isn’t installed. Can you double-check that you followed **all** the steps in the installation guide? [https://github.com/zachowj/hass-node-red?tab=readme-ov-file#installation](https://github.com/zachowj/hass-node-red?tab=readme-ov-file#installation)

@mkcologne Not sure why it's now showing in HACS for you but Home Assistant 2025.10.0 broke this integration. >Home Assistant 2025.10.0 broke compatibility with any version of this integration prior...

The wait-until node doesn't support running multiple timers simultaneously. If a new input arrives while a timer is active, the existing one is replaced by the new timer. What you're...

try it with some extra debug info and post the debug panel