I’ve been using nodered for a very long time where I mainly use modbus and mqtt to retrieve data from several devices. This data is stored in an external database, but some of the parameters I want to see on my hassio dashboard.
In order to to this I’ve been using the ‘sensor’ node in nodered and this was working up until an update I performed a few months ago.
After the update, the sensor nodes in nodered seem to work properly (I can see live data being displayed underneath the icon), but in the dashboard there seems to be no data available.
This is what I have observed:
Data from an inverter (modbus over TCP) is properly retrieved in nodered. Underneath the value nodes and sensor node I can see the correct values in real time. It’s the sensor node indicated in red I want to see on my dashboard (this was working up until a few months ago)
(added embedded picture here, but new users can only upload 1 embedded picture per post…)
The sensor is recognized in home assistant and I used it to display a graph. But the graph is empty (and remains empty)
(added embedded picture here, but new users can only upload 1 embedded picture per post…)
I tried adding the same sensor node as an entity card and there it shows “unavailable”
(added embedded picture here, but new users can only upload 1 embedded picture per post…)
When I go to settings - devices - nodered companion I can see there is a red exclamation mark next to every sensor node I have used in nodered that says “This entity is no longer being provided by the nodered integration. If the entity is no longer in use, delete it in settings.”
Are you running the latest version of the custom integration (Node-RED Companion) for node-red-contrib-home-assistant-websocket?
You can verify this by using the Diagnostics button in Node-RED.
Node.js version: v22.16.0 x64 linux
OS: Linux 6.12.43-haos x64
Before posting I had already updated the node-red-contrib-home-assistant-websocket by updating it in the node red pallet as I did find posts mentioning this. And appearantly home assistant does not update this.
But assuming this is indeed the latest version, it doesn’t solve the problem in my initial post…
This is the component you need to update — the Node-RED Companion custom integration.
The latest version is 4.1.3, and you currently have 1.1.2 installed.
Most users install it via HACS, but you can also install it manually if you prefer.
Awesome, thanks!! Seems I was still running win95 :-).
Just for reference in case somebody else has this issue:
I was indeed running nodered companion 1.1.2 (settings - devices and services - nodered companion. You can see the version in that page).
This is a custom integration and is NOT updated automatically
If you create a backup in home assistant (settings - system - backups - backup now) the custom integration is NOT backed up. If you tru to restore, there is no checkbox ‘nodered companion’. I’m using zfs in truenas and was able to rollback a snapshot, but keep this in mind!
To update nodered companion, I could not update it via HACS. I got the error message nodered companion was already configured and I could have only 1 instance. Easiest way to update was manually by simply overwriting the files in /custom_components/noderred with the files found on github (Link Kermit provided) and restart home assistant.
Kermit - Thanks again! Was looking for a solution for quite a while.
