+1 Restoring to pre-16 now.
Restoring the backup to 15 did nothing for me. The flows were still gone.
1 Like
i had the same problem. After restoring the backup the node red directory was empty. I manually copied over the files from a backup, restarted and had to start the service up again. Finally my flows were back. Ugh.
Can you explain how you got the files from a backup?
I had a manual backup of the contents of my config directory from earlier and luckily had not changed the node-red flows at all.
I did not extract the files from the node-red backup that was created from HA when the latest upgrade happened. Not much help for other people… sorry.
1 Like
Which backup would this be? A Core backup?
3 Likes
It was in my ‘full’ backup (I exclude /Media)
Extract homeassistant.tar then look in \homeassistant\data
That’s where I found my node-red folder. I’m currently copying mine to my install.
OMFG…everything is GONE!!!..
When you say clear out, do yo mean delete the contents completely?? Will this work???
1 Like
read the post. Yes it works if you do the procedure correctly.
This right here will be the reason I do NOT allow automatic updates on add-ons anymore. The directions by @frenck are not working and my home is completely down.
4 Likes
Not quite. I’ve reverted the backup and the /addon_config/ directory is already empty. The Node-red addon won’t even start now.
Not every clear about the reason why:
[14:14:34] INFO: Starting Node-RED…
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
start
node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
Error loading settings file: /etc/node-red/config.js
[14:14:37] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[14:14:37] INFO: Service NGINX exited with code 256 (by signal 15)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
ayayay…5 years worth of work completely GONE! Is there any way to get this back???
1 Like
you ALSO need to restore a copy of your node red config - that’s in your HA backup. You either need to do a restore of HA config (the ha core backup has it) OR open up the backup - extract the homeassistant.tar from backup - then extract the homeassistant.tar itself and grab the ENTIRE node-red folder out of that backup and copy it and ALL contents to \config\node-red (That’s your ACTUAL flows and config) the Addon restore only restores the addon itself.
I don’t have that anymore…all the attempts to reinstall node red overwrote all of my other backups
Still having issues here, restored my full HA backup to prior, then restored the Node-red to 15.1.1, copied over the whole node red folder from the Full backup, and still the addon will not start. Nothing even shows up in the logs for the addon. Sort of lost at this point. I updated to 16.0.2, restarted HA, and still the addon will not start.
Do you have a recent full backup? What I did was:
- restore full backup
- delete all flows
- imported recent backup of all flows and replaced any nodes as part of that
- imported a recent backup of all YAML
- restarted
Seems to be working so far. Obviously things here and there are a few days old … so will have to work thru that but hecka better than loosing everything,
Good luck guys!
1 Like
- restore to a pre - 16.x build.
- clear the /addon_configs/ folder if it has anything (latest Samba Add-in will share it if you don’t see it (this is what prevents it from wiping stuff out again)
Note the next two steps may be the same step for you depending on your backup strategy… I didn’t want to full restore HA - it takes an hour for me
- Restore your PRE 16.x Addon (addon restore of NR - 15.x build or earlier)
- either full restore HA OR get a full backup and do the fiile procedure above,
- once all the files are where they need to be - THEN start Node red (it should start on your pre 16.x build, if it doesnt repeat above until you have a clean start here on a good build.)
- update to 16.0.2 (DO NOT install 16.0 or 16.1 or you’re back at step 1)
(edit - sorry forgot about layinng down NR itself - update step3)
Starting that now, will take a bit, thanks for the help.
1 Like
is this step still necessary if you restore from a full backup and then only upgrade to 16.0.2?
thanks.
PS: good seeing you here.
1 Like