Well, I hope it’s really working as it’s supposed to. Reading through that other thread is not pleasant. 
It was NOT fun.
We usually get more notice of a breaking change this significant. But all of my hundreds of Node-Red flows appear to be working.
1 Like
The part that killed the flows was purely accident.had it worked correctly your stuff would have moved transparently.
Good news now the change moves all NR related stuff into a folder now controlled by the container so after how many years our flows will now be IN the backup of the addon.
Funny. My Node-Red has always been in the backups.
About 6 months ago my Intel NUC that was running Home Assistant had a RAM problem, so I swapped in another NUC, installed HAOS then the backup from the previous night. Everything was there.
Oh it’s in the backup. But the flows are in /config/node-red before 16. X (and therefore in the core backup) and in 16.0.3 and higher it will be in the addon_config folder for the node red container (under the node red container and therefore in its addon backup) that’s why a full restore of the addon AND core (or moving files back by hand) were required
1 Like
I don’t know how you are backing up, but this is not my experience. In the few times that I have restored from backup (usually because my clumsy experiments hosed my system) all of my Node-Red flows restored along with all of my Home Assistant files and folders.
I ran a bunch of experiments last night - and tried to restore a LOT of folks yesterday. Your flows lived in /config/node red until 16.x That folder was not backed up IN THE ADDON Backup, but was included in the core until it was moved into /addons_config.
Documentation is here.
(read item #1 Mike stated that was the reason for the change)
I didn’t believe it either at first but went back and ran a BUNCH of experiments yesterday… That’s how it DID work. Now (post 16.0.) it works like you expect it does. Side effect - folder move.
What i think is being said is:
Previously = restore a core backup. Restores everything including node red flows because they were stored in the core folder.
Now = restore core backup. Restores everything because it restores the addon and the flows are now stored in the addon like it should be.
The outcome is the same.
However crucially this opens the door for restoring nodered backup on its own and it restoring to a backed up flow along with it instead of just restoring the version and keeping the flow that may have been altered in the meantime.
@NathanCu correct me if i am wrong please.
BIngo. Thats how it works.
1 Like
Hello, I have read this and other threads, but I’m still confused. I have upgraded nodered from 15.0.0 to 16.0.2 and the /config/nodered folder is now empty. A folder named “addon_configs” is not there, even after migration of the “samba share” add-on to 12.1.0 which supports access to that folder. Nodered is running fine, but where is e.g. the flows.json file?
I found no solution in this thread, which adresses my problem “Where did my Node-Red folder go?”. I’m on a raspy pi4, latest system updates.
It is in the root. The latest Samba Share add-on is how I get to it.
That’s the /config share. Look a level up…
/Addon_config is at the same level
Thats the root!! You can see the /config in the screenshot…
1 Like
Great![quote=“NathanCu, post:21, topic:641467, full:true”]
That’s the root of THAT share… /addon_config is its OWN share…
[/quote]
Great! I found it with separate smb share! Thank you!
I then tried to read a user file (mittagskarte.pdf) from inside the addon_configs folder from nodered but did not get it. Any idea?
SOLVED! I have to use the same path as before: /config/… for read and write from nodered, the data will be found in the new folder /addon_configs/…
Thank you!
1 Like
Good morning,
I have a flow within Node red that takes the flow.json file and emails it to my gmail, for backup. How do I do this with the new folder path?
The error message is Error: ENOENT: no such file or directory, open '/addons_config/node-red/2023-11-26T10_38_04_flows.json
I have tried googling and lurking on the forums, but cannot see any answer.
I want to backup just the flows.json automatically each night.
(After multiple tries, I have given up on the whole idea and disabled the flow that backs up the flow.json)
Many thanks.
On my updated system, flow.json is now located here (as seen via ssh):
/addon_configs/a0d7b954_nodered/flow.json
It can be accessed from within node-red using this path:
/config/flow.json
I used the “node-red-contrib-fs” module to compare what I was seeing in SSH vs what is seen from within node-red. I hope this helps someone.
1 Like