All of the sudden stopped working

[guedini]

Describe the bug

I'm working on my flows and suddenly I started getting a NoConnectionError. So all started failing.

After reviewing my entities, all text and number entities are displaying the message below.

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

I tried to update WebSocket but it is still not working. Not sure which version is it or how to fix it.

I appreciate help on this issue because I use text and number for almost all flows so nothing is working anymore.

Thanks

To Reproduce

No response

Expected behavior

No response

Screenshots

No response

Example Flow

No response

Environment Information

Version: 0.65.1

Home Assistant version: unknown Companion version: unknown

Node-RED version: 4.0.2 Docker: yes Add-on: no

Node.js version: v18.20.3 arm64 linux OS: Linux 6.6.31-haos-raspi arm64

Additional context

No response

[UncleLeoTheDad]

I'm seeing something similar. It keeps telling me my node needs version 1.6+, but I've checked and I have 4.1.0 installed.

[hanstornquist]

I have the same not using beta "This node requires Node-RED custom integration version 1.1.0+ to be installed in Home Assistant for it to function." I have v4.1.0 installed Home Assistant Core 2024.9.2 Supervisor 2024.09.1 Operating System 13.1 Frontend 20240909.1

[zachowj]

@guedini Was Node-RED connected to Home Assistant when you gathered the diagnostics info? The popup appears because it is unable to retrieve the necessary data from Home Assistant.

@UncleLeoTheDad @hanstornquist Please share your diagnostics information.

Are you accessing the Node-RED UI through an iframe in Home Assistant or directly via port 1880? Try connecting directly to Node-RED on port 1880.

[hanstornquist]

@zachowj My HA install Version: 0.72.4

Home Assistant version: 2024.9.3 Companion version: 4.1.0

Node-RED version: 4.0.2 Docker: yes Add-on: 18.0.5

Node.js version: v18.20.3 x64 linux OS: Linux 6.6.46-haos x64

And my Victron Cerbo GX that connects to my HA Version: 0.72.4

Home Assistant version: 2024.9.3 Companion version: unknown

Node-RED version: 3.1.10 Docker: no Add-on: no

Node.js version: v18.20.3 arm linux OS: Linux 5.10.109-venus-17 arm

Both have the same error, my HA is using the iframe option and the Victron is direct to port 1880

[UncleLeoTheDad]

Hmmm...woke up this morning and saw an update for node-red that was pending that wasn't there last night. Restarted and now I am not seeing an error. Hizzah! I will let you know if that changes. My config is now:

version: 0.73.0
Home Assistant version: 2024.9.3
Companion version: 4.1.0
Node-RED version: 4.0.2
Docker: yesAdd-on: 18.0.5
Node.js version: v18.20.3 x64 
linuxOS: Linux 6.6.46-haos x64

[UncleLeoTheDad]

Actually, I spoke too soon. Still there!

[MarkoBolt]

Since today, I have had exactly the same issue.

After updating "node-red-contrib-home-assistant-websocket" to 0.74.0 it worked a bit and now it is not working anymore.

version: 0.74.0 Home Assistant version: 2024.10.1 Companion version: 4.1.1 Node-RED version: 4.0.3

[MarkoBolt]

The buttons sometimes work, but I can not see any status information in Node-Red, and there is also no debugging information available. That's weird.

[zachowj]

@MarkoBolt, are you experiencing issues similar to those described below?

Related issues for tracking:

• https://github.com/hassio-addons/addon-node-red/issues/1938
• https://github.com/zachowj/node-red-contrib-home-assistant-websocket/issues/1480

[lucode]

Had the same/similar issue. Minor issues with HA V2024.10.1, but after upgrading to V2024.10.2 the integration stopped communicating to Node Red. Did manually redownload the HACS repo and after the restart of HA it works now, but I had to rename most of my companion entities, because they got added a "_2" at the end from the issue.

I guess the HACS integration didn't correctly got downloaded previously.

[MarkoBolt]

@MarkoBolt, are you experiencing issues similar to those described below?

Related issues for tracking:

• After upgrading to 0.67.1 debug nodes / inject are greyed out, HA nodes shows no status hassio-addons/addon-node-red#1938
• After upgrading to 0.67.1 debug nodes / inject are greyed out, HA nodes shows no status node-red-contrib-home-assistant-websocket#1480

Yes indeed these seem related.

I can access Node Red via http://localHASSIP:1880/#

[lucode]

Had the same/similar issue. Minor issues with HA V2024.10.1, but after upgrading to V2024.10.2 the integration stopped communicating to Node Red. Did manually redownload the HACS repo and after the restart of HA it works now, but I had to rename most of my companion entities, because they got added a "_2" at the end from the issue.

I guess the HACS integration didn't correctly got downloaded previously.

Unfortunately the error is back. But I noticed that the cause might be found somewhere else. I had suddenly a strange error caused by a missing entity. Node Red started to run havoc and this blocked somehow the entire communication between NR and HA. But after enabling and disabling the affected flow and some restarts everything seems to be ok again. No missing entity, I have nothing changed. Very strange behavior.

As the detected error (missing entity) has coming from the Smart Irrigation Integration I started to wonder if there might be an interference in using NR and this Integration. It seems there is at least an issue with I/O "register_static_path" about this Integration. https://github.com/jeroenterheerdt/HAsmartirrigation/issues/429

Does anyone else using the Smart Irrigation Integration in this thread?

[MarkoBolt]

There is an fix for the issues I had: #https://github.com/zachowj/node-red-contrib-home-assistant-websocket/issues/1480#issuecomment-2434005277

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.