After update to 16.0.1 all flows gone

[Bloodpack]

Did update from 15.x to 16.0 and then to 16.0.1 and all my flows are gone.
tried to restore backup from 15.x and nodered does not start anymore.

EDIT: Read about the solution here: #1736 (comment)

[DieMetRik]

After update from 16.0.0 to 16.0.1 flows not appear
Credential error after open NR

[frenck]

tried to restore backup from 15.x and nodered does not start anymore.

Did you also restore a Home Assistant backup? As the flows are stored in the Home Assistant configuration folder prior to v16

[Bloodpack]

Did you also restore a Home Assistant backup? As the flows are stored in the Home Assistant configuration folder prior to v16

No, because i did not know the flows are not stored in nodered backup.

can i just import the flows.json from the homeassistant backup in to the nodered 16.0.1?

[dannyleong74]

Same here all flow are gone after upgrage to 16.0.1. Restore back to 15.1.1 but addon could not start.

[frenck]

ℹ️ Please stop raising small useless comments. I will hide them if they don't add to triaging the issue or if they add things that already have been said.

removed these instructions New ones below.

../Frenck

[jossiee]

Probably a dumb question but where can i find the /addon_configs/ folder?

[Steini1984]

FYI did a zfs rollback on the whole VM and tried to update from 15.1.1 > 16.0.1, but still all the flows were gone after the update. Did a second rollback and sticking with 15.1.1 for now.

[DieMetRik]

My flows back.
Stop NR
Restore /config/node-red from backup
Restore Addon from 16.0.1 to 15.1.1
Start NR

[Mangomc]

Upgraded from 15.1.1 directly to 16.0.1. Never had 16.0.0 before but All my fkows are also gone

[andonevris]

After that upgrade from the restored pre-v16 version directly to v16.0.1.

This doesn't work, restored my VM back to 15.x did an upgrade straight to 16.0.1 and all flows are missing.

I imported the flows manually and everything works but when you restart the addon the flows disappear again. This seems like still a bugged release, sticking to 15.x for now

[henriklund]

Can confirm after import it works again. But after restart of NodeRED flows are gone again.

Reverting is not an option since that does not work in my case.

[frenck]

Found the issue that keeps nagging this. Will create a hotfix release.

[LsVzqz]

ℹ️ Please stop raising small useless comments. I will hide them if they don't add to triaging the issue or if they add things that already have been said.

Important, v16.0.0 has an issue with credentials secret (see #1733 for the original report and the fastest resolution I could provide). That is unfortunate, but did happen and didn't show up in testing.

If you have upgraded from pre-v16 to v16.0.0 you will encounter a migration problem. To solve this:

* Restore a backup **(node-red + home assistant config as that is where the flows are stored)**

* Clear out the node-red folder in `/addon_configs/` which contains the invalid migration.

After that upgrade from the restored pre-v16 version directly to v16.0.1.

I've addressed the issue as quickly has humanly possible, but I cannot revert what has been done.

../Frenck

Hello! I'm sure this is an obvious answer, but I can't find it. How do I clear out the node-red folder in /addon_configs/? I'm using the "File editor" and I can't seem to browse to /addon_configs/

[Caligo82]

Silly question, so the backup of the node-red flows is not within the actual node-red backups folder?

As answer to LsVzqz, you'd probably need to attach to the container in console to get to this folder.

[canedje]

Where to find backup /config/nodered?
After installing backup 15.1.1 and update to 16.0.1 Nodered is not starting at all.
Only install backup 15.1.1 is not starting at all

EDIT: is installing afull backup also restore the /config directory?

[Caligo82]

Well that's exactly what I'm trying now, it just takes ages, as it is also restoring my db's. :D
I'll get back here if it worked.

[MiguelCosta]

I have the same issue and restore backup is not working.
Does anyone know why the restore isn't working? 😕

[canedje]

I have the same issue and restore backup is not working. Any knows why de restore is not working? 😕

I get it installed, but is not starting up anymore

[h0bbel]

I encountered the migration issue, and had no luck reverting to a backup (I forgot to clear out the addon_configs directory it seems). Anyway, I took flows.json from my backups and imported it into Node Red 16.0.1, and all seems well (Apart from missing Node-Red packages that I manually installed) but as soon as Node-Red is restarted all flows are gone again and I have to re-import my flows.json file.

[henriklund]

I encountered the migration issue, and had no luck reverting to a backup (I forgot to clear out the addon_configs directory it seems). Anyway, I took flows.json from my backups and imported it into Node Red 16.0.1, and all seems well (Apart from missing Node-Red packages that I manually installed) but as soon as Node-Red is restarted all flows are gone again and I have to re-import my flows.json file.

Wait for the hotfix @frenck is working on.

[Caligo82]

Complete backup restore did the trick for me..., I'll wait for the fix before updating again, thats for sure. :)

I'm sure that's what @frenck was looking for today. Creating a hotfix for thousands of sweaty node-red users. Hahahaha

[henriklund]

I have the same issue and restore backup is not working. Does anyone know why the restore isn't working? 😕

You should have a /config/node-red.backup. You can get hold of the flows.json in that folder and use the method of import mentioned above (worked for me). Do not restart NodeRED until the hotfix is available.

[Zagitta]

This is a good reminder for everyone to disable automatic updates. This addon isn't the first nor the last to push an update that breaks everyone's home automation 🙂

It's deeply ingrained in the entire ecosystem's culture to "move fast and break things" at this point, even core homeassistant loves making breaking changes that require manual intervention in one way or another

[BobRathke]

UPDATED 11/16/2023 8:39 EST

After a series of full restores, and attempted/failed recoveries, I am back to 15.1.1 working/starting correctly with all my flows. I am not sure what the "magic sauce" was, but I am going to let it run a day or two before attempting the 16.X upgrade again.

Good luck friends, this was a rough one! Years of flows are once again running here.

---

After full restore of HA & NR to 15.1.1, NR IS running and can be accessed directly via IP (http://192.168.50.200:1880/#flow/8fb13690.c3e5e), but NOT Via HA dashboard. HA reports service will not start, but it is started and running.

Please advise. I am unable to move forward or backward.

I have exported all my flows and just need to get NR updated and running properly at this point.

---

I am still struggling to recover back to my 15.1 OR upgrade to 16.2

After a failed upgrade from 15.X I have attempted to do full restores and NR still fails to start after full restore back to 15.X. It appears node red is "working" but the NR logs stop and it appears to Hang. Flows are still running, but HA reports NR is not started?

After restoring back to 15.X I do not see the new addon folders to execute suggested resolution. I even restored from several days ago (Full) with no joy.

Help.......

[mikebaileyz]

I am sorry but this didn't work for me.
I have restored back to V15 and the HA 2023.11.2
then looked in \addon_config\ but it is empty.
Tried V16.0.2 but still won't start
I am really lost here and need some detailed help
I have thousands of hours of NR work but cannot access them

[borfang]

If Node-RED fails to start after an update, you can follow my solution. First, restore to a version that works correctly, uninstall Node-RED 15.1.1, and then follow these steps in the Advanced SSH & Web Terminal:

Navigate to the home assistant directory:

cd /homeassistant

List the contents to identify directories related to Node-RED:

ls -llh
Identify directories related to Node-RED (e.g., node-red and node_modules).

Rename the Node-RED directories for backup:

mv node-red node-red_bak
mv node_modules node_modules_bak

Reinstall Node-RED version 16.0.2.

After installation, perform basic configuration and check if Node-RED starts correctly.

Once confirmed, stop Node-RED and copy the flows configuration from the backup:

cd /addon_configs
ls
cd a0d7b954_nodered
cp /homeassistant/node-red_bak/flows.json .

Start Node-RED and reinstall any missing nodes.

After confirming everything is working fine, you can remove the backup directories:

rm -rf /homeassistant/node-red_bak
rm -rf /homeassistant/node_modules_bak

This process involves backing up and restoring Node-RED directories, reinstalling the updated version, copying the flows configuration, and ensuring that all necessary nodes are installed.

[mikebaileyz]

I am really grateful for your help but there is lots in your note I don’t understand I have not been able yet to find a previous version of node Red that worksI have tried partial restoring from my daily backups but all fail to startRemove node red? Does this mean uninstall or delete or what?Will I lose my flows if I delete it?I don’t understand ls or mv or cp or any of these functionsAre you working from terminal?My lack of knowledge here makes me so scared that I will screw it upRegardsMikeOn 16 Nov 2023, at 12:05, borfang ***@***.***> wrote: If Node-RED fails to start after an update, you can follow my solution. First, restore to a version that works correctly, remove Node-RED 15.1.1, and then follow these steps in the terminal: Navigate to the home assistant directory: cd /homeassistant List the contents to identify directories related to Node-RED: ls -llh Identify directories related to Node-RED (e.g., node-red and node_modules). Rename the Node-RED directories for backup: mv node-red node-red_bak mv node_modules node_modules_bak Reinstall Node-RED version 16.0.2. After installation, perform basic configuration and check if Node-RED starts correctly. Once confirmed, stop Node-RED and copy the flows configuration from the backup: cp /homeassistant/node-red_bak/flows.json /addon_configs/new_node-red_folder/. Start Node-RED and reinstall any missing nodes. After confirming everything is working fine, you can remove the backup directories: rm -rf /homeassistant/node-red_bak rm -rf /homeassistant/node_modules_bak This process involves backing up and restoring Node-RED directories, reinstalling the updated version, copying the flows configuration, and ensuring that all necessary nodes are installed. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>

[droneman83]

can some one make small clip on how to fix it again, i have triede to restore from back up. once i start up NR it do look like a normal start up (reading 205 nodes) once it start up i just show Credential erro. I might just do somthing wrong??

[Caligo82]

I wonder, is there a scenario where the flows.json got wiped by the update process?
I have it all updated and working again, when I try to get to these old files in my updated system, they're gone. When I open my backups from a few days ago, they're still there (in the path where they're not anymore now). This is unfortunate as it means if you didn't have a homeassistant core backup laying around somewhere... flows.json is gone...

[marc115uk]

Every time try to use a back up. I select home assistant config and node red 15, however once it has finished restoring back up I open home assistant and still have node red 16.0.2 installed? also have a warning Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.

[SynoUser-NL]

SynoUser-NL's tip worked for me: dropped flows.json and flows_cred.json into the new nodered folder within addon_configs I was able to manage palette to find and install most of my old modules that were missing. Still have to modify 14 flows "stoptimer3" was popular with me. Looking for a timer that will do the same action.

Thanks

Note that the actual name of the node (once added with Palette Manager) can be different from the name it is displayed as in Palette Manager. So if you install a node "stoptimer" from Palette Manager, the node that is added may very well be stoptimer3.
The actual name of the node is displayed briefly on installation, and after installation you will find it in the node list.

After installation of a node, flows will automatically update to use it on the next deployment of your flows.

[CrallH]

I just did this, was I just lucky to get it all back? https://community.home-assistant.io/t/after-update-to-16-0-0-all-flows-and-notes-are-gone/641103/45?u=christian_hollbjar

[BjornBP]

Followed Frenck's instructions to the letter. Several times. No joy.
What eventually fixed it was a hardware power-down and reboot. Previously we were simply doing a soft reboot and something must have remained in memory, causing the fix not to have any effect.
Thanks Frenck for being on top of this issue and supporting it so well.

[a24me]

What I did...

1. Restore the backup.
   I restored the more recent full one before the incident, but I suppose that the NodeRed one could also be enough.
   If you restore only the node red backup, possibly you will need to use the Terminal addon or the SAMBA addon (share) or a SSH connection, to delete the directory named xxxxxxxx_nodered under the /addon_configs/ directory, before the restore.
2. System -> Power button -> Advanced options -> Reboot system.
3. Wait to load everything and check that everything works.
4. System -> Power button -> Advanced options -> Shut down system.
5. Wait for about 10 min for the system to shut down.
6. After system shut down power off the device.
7. Power on the device.
8. Apply all pending updates.

Voila, all back and working in an extremely large and complicated setup! Fingers crossed!

[klio-klio]

I've got Node Red working again so far. I get error messages when deploying.

Does anyone have the problem?

[henriklund]

Think I found out why: Have a look at this issue; looks as this is 'working per design'. After changing the deploy model back to 'Modified Nodes' (did not note it had changed), the errors have gone.

[mikebaileyz]

I wanted to update on my situation having been frustrated for several days trying to solve this and hope it may help some others.
Having followed the instructions and restored from back-ups still couldn't get v15.1.1 NR UI to start. All my flows were working in the background.
I was stuck until I read in this post that someone did a system re-boot, (not a restart). Tried this and it started working! I was then able to upgrade to v16.0.2 and it also started OK.
Hope this helps anyone else who thinks they have followed all the instructions but cannot get NR to start.

[github-actions]

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

[aavosnl]

is there any update on the problems after the update node-red-contrib-home-assistant-websocket ? trying everything that others have done but with no positive results so far

[PrathikGopal]

Manually installed the node-red-contrib-home-assistant-websocket module to get the flows working, but that’s a temp fix. Hopefully we have a better solution.

[lensherm]

is there any update on the problems after the update node-red-contrib-home-assistant-websocket ? trying everything that others have done but with no positive results so far

In the same boat here. Got to 16.0.2 without realizing there were any issues. At that point I updated the node-red-contrib-home-assistant-websocket, which resulted in missing nodes and missing node-red-contrib-home-assistant-websocket.

[henriklund]

At that point I updated the node-red-contrib-home-assistant-websocket

A few things... Do you have a backup and considered reverting? Secondly, (regarding the websocket) there are a few issues on that:

• Current Behavior Flows stopped due to missing node types #1779
• No connection to home assistant anymore / cant update websocket #1781

For me, the lesson learned is to never update the websocket through the palette manager in NodeRed.

[indicato]

Sorry , when will it fixed .. The solution is very easy .. (i hope so)

node-red-contrib-home-assistant-websocket need : Node-RED v3.1.1+ but the addon has only v3.1.0.

So what´s up with an update ?

Thanks Lars

[frenck]

Going to close this issue, as it has been open long enough at this point.

The latest comments are not related to this specific issue presented here.

../Frenck

[indicato]

Thanks for updating .