This node requires Node-RED custom integration version 1.1.0+ to be installed in Home Assistant for it to function.

[jannic24]

Describe the bug

Add on is installed but doesn´t work

To Reproduce

No response

Expected behavior

No response

Screenshots

Example Flow

No response

Environment Information

Home Assistant Core 2024.10.3 Supervisor 2014.10.3 Node-Red 18.1.1 Node Red Companion 4.1.1

Additional context

No response

[Jscifu]

I have the same problem: Nodered: 4.0.3 - Node-RED Companion 4.1.1.

[Basik-dev]

I have the same problem: Nodered: 4.0.3 - Node-RED Companion 4.1.1. and HA 13.2

[wifiuk]

I already have it installed, and i get the same error, also seems nodered isn't able to automatically list entities from dropdowns anymore.

[shangjiazi]

The same problem exists

[ZijdeglansLak]

Probably the same issue here. Reinstalled everything, nothing helps! Please help! Everything worked great for years.

Installed the latest version, I tried older versions, I tried removing it and reinstalled it..

[Coroebus]

Same issue here...

[thekitehunter]

Same issue here. But I would add that the Node RED add-on seems to be working, in that I can access and work on it directly via http://'ha ip address':1880, rather than the web interface inside Home Assistant.

[dirkvdb2]

Same here

[johnculviner]

I'm having the same issue. What happened?!

[zachowj]

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]

Sure thing. Thanks for the help!

Version: 0.75.0

Home Assistant instances: 2
Server: 68734f10.b46e9
Home Assistant version: 2025.1.3
Companion version: 4.1.2
Server: 
Home Assistant version: 2025.1.3
Companion version: 4.1.2

Node-RED version: 4.0.8
Docker: yes
Add-on: 19.0.0

Node.js version: v22.11.0 arm64 linux
OS: Linux 6.6.62-haos-raspi arm64

Note, this same thing happens if I'm in Home Assistant's GUI looking at this or if I visit it directly like below...

[zachowj]

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

[johnculviner]

It wasn't. I fixed that now. Now you can see the only thing blocking is the not loaded issue. Any ideas @zachowj? Thanks for the help or any more info I can provide you?

[sanbudewoniujun]

必须在设置——设备与服务——添加集成——Node-RED Companion,然后重启设备应该就可以了

提交以后 然后重启系统

[zachowj]

@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 take a few seconds. If an MQTT message is received during this reconnection window, Node-RED and Home Assistant may not be fully connected, potentially causing this error.

[Ahriman]

Same issue here.

[finbom]

After running for years with HA + NR addon/integration, I today face same issue. The NR integration try to connect but it looks like the addon does not connect.

Getting the "This node requires Node-RED custom integration version 1.1.0+ to be installed in Home Assistant for it to function." all over in Node Red.

The HA addon is every second flooded with.. [info] [server:Home Assistant] Connected to http://supervisor/core [info] [server:Home Assistant] Connection closed to http://supervisor/core

Core: 2025.3.1 Supervisor: 2025.03.2 Operating System: 14.2 Interface: 20250306.0 Node Red: 4.1.2

[finbom]

All those experiencing the same issue, please share your diagnostic information.

https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html

Sorry. I am only getting a blank window when trying that.

[zachowj]

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 tab.

[casekhor]

Installed the node-red-contrib-home-assistant-websocket palette in Node Red a while back. Got the error (in Node Red) while trying to configure my first switch entity node today. I'm sure I saw the error before. I only just installed HACS and the Node-Red Companion Integration today.

Version: 0.75.0

Home Assistant version: 2025.2.4
Companion version: 0.0.0

Node-RED version: 4.0.9
Docker: yes
Add-on: 19.0.2

Node.js version: v22.13.1 arm64 linux
OS: Linux 6.6.62-haos-raspi arm64

[zachowj]

@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 in the installation guide:

https://github.com/zachowj/hass-node-red?tab=readme-ov-file#option-1-hacs-home-assistant-community-store

[lubricatedcactus]

`Version: 0.75.0

Home Assistant version: 2025.3.3 Companion version: 4.1.2

Node-RED version: 4.0.9 Docker: yes Add-on: 19.0.2

Node.js version: v22.13.1 x64 linux OS: Linux 6.6.73-haos x64 `

[SouzaDeivite]

Version: 0.75.0

Home Assistant version: 2025.5.0 Companion version: 4.1.2

Node-RED version: 4.0.9 Docker: yes Add-on: 19.0.2

Node.js version: v22.13.1 x64 linux OS: Linux 6.12.23-haos x64

[r2d22028]

Hy,

Same here.

How do you get the diagnostic data ?

Regards

[niwzo]

i got the same issue "Node-RED custom integration version 1.1.0+ to be installed in Home Assistant for it to function." which is installed.

[mrkrb]

Same issue here:

"This node requires Node-RED custom integration version 1.1.0+ to be installed in Home Assistant for it to function." message, and every sensor node output "InputError: Integration not loaded" in the debug panel

Version: 0.77.0

Home Assistant version: 2025.5.3
Companion version: 0.0.0

Node-RED version: 4.0.9
Docker: yes
Add-on: 19.0.2

Node.js version: v22.13.1 arm64 linux
OS: Linux 6.6.74-haos-raspi arm64

[zachowj]

@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

[26miller]

Version: 0.77.0

Home Assistant version: 2025.5.3 Companion version: 1.0.8

Node-RED version: 4.0.9 Docker: yes Add-on: 19.0.2

Node.js version: v22.13.1 x64 linux OS: Linux 6.12.23-haos x64

I have the same issue. I think my companion version is not at the version which it supposed to be looking at previous posts. I tried removing an reinstalling but that didnt work. Is there a specific way how to update this?

As soon as I upgrade my Home Assistant to version 2025.6.x the integration seems to stop completely for my installation so I suspect this lower version which is reported might be the cause of this

Just finished another but now succesfull attempt. I think I made a mistake by not downloading the latest version in HACS ending up with same version I already had installed.

Now everything is looking good and running on latest version.

Version: 0.77.1

Home Assistant version: 2025.6.1 Companion version: 4.1.2

Node-RED version: 4.0.9 Docker: yes Add-on: 19.0.2

Node.js version: v22.13.1 x64 linux OS: Linux 6.12.23-haos x64

[mkcologne]

Version: 0.78.0

Home Assistant instances: 2
Server: 1679aec.5e27851
Home Assistant version: 2025.10.0
Companion version: 0.0.0
Server: 1265decc.ac6211
Home Assistant version: 2025.10.0
Companion version: 0.0.0

Node-RED version: 4.0.9
Docker: yes
Add-on: 20.0.0

Node.js version: v22.16.0 arm64 linux
OS: Linux 6.12.34-haos-raspi arm64

The error started with HA Update to 2025.10

I See, that my companion Version is also 0.0.0, but it is installed:

I also have the Folder in the Custom Components.

I also couldn't find components in HACS!?

When I try to add this repo maually I get this:

When I try to add a new instance:

{"message":"Invalid handler specified"}

[zachowj]

@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 to 4.1.3. If you haven’t upgraded to at least that version, that’s likely the issue you’re seeing.

https://github.com/zachowj/hass-node-red/issues/355#issuecomment-3358648315