home assistant nodes with issues (but none show up) after updating to nodered 19.0.0

[mindgam3s]

Current Behavior

after updating my NodeRed addon to version 19.0.0 today, it showed me some issues that I resolved.
after resolving everything it still shows me that I would have one problem remaining but when I click on the message no node shows up.
see screenshot.

Expected Behavior

either no problematic nodes message shows or there are nodes shown in the table

Environment

• Node-RED version: 19.0.0
• Platform/OS: HomeAssistant OS
• Browser: Firefox

[woidler]

Same for me has been fixed after update of node-red-contrib-home-assistant-websocket.

[mindgam3s]

Same for me has been fixed after update of node-red-contrib-home-assistant-websocket.

how would I do that? there is no update available for any nodes as you can see in my screenshot

[mindgam3s]

it's getting worse!
after a reboot of HA I now have THIS

it says input_boolean.turn_on action is not found (and several others like turn_off or action recorder.enable etc.)
WTH?!

please help me!

[kbouchard111]

it's getting worse! after a reboot of HA I now have THIS it says input_boolean.turn_on action is not found (and several others like turn_off or action recorder.enable etc.) WTH?!

please help me!

I have the same problem and had to restore from backup (VM snapshot).
The problem happened after updating Home Assistant Core and HAOS(while using an older version of Node Red).
Updating Node Red after the fact didnt work and confirmed after updating Node Red that I was running the latest available version of node-red-contrib-home-assistant-websocket.

All actions aside from an automation on and automation off action were missing.

Home Assistant Core Update from 2024.11.1 to 2025.1.2
Home Assistant Operation System Update from 13.2 to 14.1

Using Node Red 18.1.1

Updating to 19.0.0 didnt fix it.

I took a snapshot before restoring the backup so if anyone needs logs or want me to test something, let me know.

[mindgam3s]

I actually resolved the problem by disabling both the integration and the addon, then rebooting hassio and turning them on one after another. no the problem seems to be gone.