Node red version 17.0.7
Node Red companion v3.1.3
node-red-contrib-home-assistant-websocket 0.63.0
When I update core from 1.6 to 2.1 a whole load of sensors that i’ve created in Node Red become unavailable. These have been working fine for the last 2 years or so through various updates.
So I’m not sure what the exact issue is. Its totally reproducible if I upgrade i lose the sensor… restore backup of 1.6 and it comes back and works fine.
The message in HAS is this:
There is no error reported in Node Red that I can see…
Go to manage palette in the hamburger menu. Look for home assistant web socket. Is there an update available? If yes update them. It should be ver 0.63
The entity node was removed quite sometime ago. Earlier updates auto updated to the new format. You will need to find any sensors you created with entity nodes and replace them with the individual sensors nodes unfortunately.
In the debug panel choose the info tab. There is a search bar. Problem is it’s a regex search and the name of the node is entity node. Every HA node contains “entity”.
If you know the sensor name you can search it. If there are errors showing up in the debug you can use the node id of the message. If the node is named it will be a name otherwise a number.
If you restart NR addon, then check the logs it may show all the errors with node id’s
This is no small task / joke… how come my installation has ended up silently with no longer supported entities… this is going to take a lot of work, I will loose a lot of historical data…
This was changed a long time ago, I remember this being an issue when it first happened. I believe later upgrades did this change automatically.
I say that because a month or 2 later I updated and everything changed over by itself. At least I don’t remember having to make any changes. Perhaps @Kermit could shed some light on how to correct this.
If you go to one of the old entity nodes, double click on it to open, don’t change anything. Hit the done button. Is the deploy button active. in other words can you click it and will it deploy. If yes deploy, did that fix that one node?
Sorry for delay. The forum was read only for a while this morning. So I tired the above, opening the node itself did nothing to the deploy button. Opening the entity configuration, clicking update then deploy also did not change anything when I subsequently updated to 2.1. I then tried again once I updated still to no avail.
I had a look through the other posts you tagged. I understand that the newer version split the node and configuration and where to find them etc. all that seems to be set up correctly…… it’s just not available in HASS.
My hand was forced as a subsequent upgrade of an essentialHACS package meant it stopped working on HASS 1.6. Downgrading the package didn’t work either so I upgraded to 2.2.
In the end I deleted all 36 nodes in node red. Restarted everything. Some were still listed in the node red companion entities so I removed them there. A few would not allow me to delete them so I removed them from the .config/core_entities file manually. Restarted again. Once they were no longer listed in HASS I recreated the sensor node in node red and this time it worked.
