The addon have kind of two parts, the addon in itself, and the data you will find in /config/node-red.
When you do a full backup, the addon is backed up to “itself”, and the datafound in /config/node-red is in the homeassistant file.
When you backup only the addon, what’s in config/node-red will not be backed up.
So when you do a restore of the addon, it will not restore whats in /config/node-red
I think I got it so far.
So, what happened to me is that I updated a node that didn’t behave well and wanted to go back to the previous version and that raised some questions.
How to do that the best way? Because if I restore homeassistant, that will also restore a lot of other things I’m not interested in restoring. And just take the old files from a previous back-up didn’t seem to quite work either…
So, what good solutions are there to specifically when you want to revert a node that didn’t like to be upgraded?
I do a full backup every midnight. I just don’t trust partial backups because the one time I tried restoring a partial backup, it failed.
I am using Samba Backup to a 2TB NAS, so file size is immaterial.
If you don’t have a stable system, then you need to fix that. Then your full backup would be safe to use.
When I am working in Node Red, I just work on a copy of the flow. I export the nodes to a text file, then if I mess it up, I just reimport the original nodes.
I do a full backup everynight as well, the question is more about when you need to restore.
And it’s not the flows that are the problem, its a node.
In my case I updated a node in Node-red, (one of these you add and manage from the palette) and that didn’t turn out well so I wanted to revert to a previous version, but not of the addon, of the data in /config/node-red.
So the question is how to do that the best way, without restoring everything in hass, just the /config/node-red part.
So it’s not the flows you are working on that my question is about, it’s the nodes, you know the ones you have in the sidebar.
I tried to replace the files with backed-up versions, but didn’t solve the problem.
I should have added that for whatever f-ing reason, that didn’t work. Despite removing all nodes on configurations and servers and whatnot.
But if one eventually get rid of it, how to install a previous version? A long time ago, before i run hass, NR had an cli where you could do things like this, and it’s still aorund, but not sure how to use it with the NR-addon.
So the question is still there, how to downgrade a node?
knolleary responded to this on the Node Red forums. It can only be done manually. Delete the newer node then install the older version. This may be the CLI method you are referring to.
cd ~/.node-red
npm install <package>@n.n.n
where n.n.n is the version you want to install.
BUT, it depends on how you have installed Home Assistant and Node Red. I am running HAOS from the X86 image of Home Assistant and npm is not installed.
BUT, if you are having a problem with an existing node, go to the Github page for the node and submit an issue.
What node is giving you trouble and what are the issues with it?
Yes, that sounds like the method I used when running NR stand alone.
Running hass supervised and node-red addon, so no npm, and no way to install to my knowledge.
The problem-node is join that talks to tasker, so one I use and rely heavily on… And it seems like I’m not the only one. The dev is usually very fast on fixing things, so hope this will resolve soon.
And to make it even more interesting. The bug is fixed, but for what ever reason there is still the old version in the palette, and since I can’t use npm… Well…
