-
Hello, who can help. Since the last core update to 2025.6.1 nodered works (in the ui I see all values), but these are no longer displayed by nodered 0.5.2 in the ha dashboards. Where am I right to report the problem |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
I found this online: Problem Description Essentially, Home Assistant indicates that the entities previously exposed by Node-RED are no longer linked to any active integration. In addition to the "Unavailable" status of Node-RED entities in the frontend, you can also see errors in the logs. For example, Node-RED logs show messages like “NoConnectionError” or “Entity could not be found in cache for entityId,” which indicates that Node-RED flows are no longer able to communicate with Home Assistant to update the state of those entities. In short, all automations and virtual sensors created via Node-RED stopped working after the update. Cause of the Malfunction In particular, Home Assistant now invalidates or ignores entities created by custom integrations that do not comply with the new internal requirements. It's important to remember that the Node-RED Companion integration is an unofficial (third-party) add-on that allows Node-RED to create and manage entities in Home Assistant via WebSocket. Thanks to this integration, Node-RED can generate entities like sensors, switches, buttons, etc., directly from automation flows. However, because it is a custom integration not distributed with Home Assistant Core, it relies on certain internal APIs and mechanisms of the core. With Home Assistant 2025.6.x, those internal entity registration mechanisms have changed, causing the Node-RED integration to fail during startup. In other words, Home Assistant can no longer configure the nodered integration at startup and therefore marks all its entities as orphaned (hence the message “entity no longer provided by the nodered integration”). This type of breaking change is not unprecedented: for example, an internal change in Home Assistant 2024.5 (removal of the HomeAssistantType) required an urgent update of the Node-RED integration to restore compatibility. |
Beta Was this translation helpful? Give feedback.
-
I tested both an existing sensor and a newly created one—both were updated from Node-RED without any issues. Here’s the environment I was running:
Go ahead and post your diagnostic info so we can compare setups. https://zachowj.github.io/node-red-contrib-home-assistant-websocket/guide/diagnostics.html |
Beta Was this translation helpful? Give feedback.
I found this online:
Problem Description
After updating Home Assistant to Core version 2025.6.1, the Node-RED Companion integration (installed via HACS) stopped working correctly. Specifically, all entities created by Node-RED appear as unavailable in the Home Assistant interface. If you open one of these entities in the UI, Home Assistant displays a warning like: “This entity is no longer being provided by the nodered integration”
(in Italian: “questa entità non viene più fornita dall’integrazione nodered”).
Essentially, Home Assistant indicates that the entities previously exposed by Node-RED are no longer linked to any active integration. In addition to the "Unavailable" status of Node…