My Node-Red folder is empty?? But flows are working and I can open Node-Red UI and edit flows???
I only discovered this when I went to put a sound file into /config/node-red/sounds only to discover the node-red folder is empty.
It’s always a good idea to read release notes when you upgrade, not just for HA but add-ons too. https://github.com/hassio-addons/addon-node-red/releases/tag/v16.0.0 (and 16.0.1 and 16.0.2). If you have auto-upgrade enabled, consider turning it off so you can review the changes before hand.
With this release, the
nodereddata folder will migrate/move out of the Home Assistant configuration folder into a dedicated folder for this add-on. You can access add-on configuration folders using SSH, Samba, VSCode, and similar add-ons by accessing theaddon_configsfolder/share.
More details at https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/.
But there’s also a bug logged, so make sure you’re fully up-to-date, and if that doesn’t fix it, keep watch here: https://github.com/hassio-addons/addon-node-red/issues/1736
EDIT: Not sure if the add-on change logs are cumulative? So if you were behind by several versions, then perhaps the breaking change was not visible? If that’s the case (then it’s a poor design) so here’s the actual add-on changelog for 16.0.0: repository/node-red/CHANGELOG.md at 3468345379107d44160bc7e04d3aeb9ab587ca25 · hassio-addons/repository · GitHub
2 Likes
Thanks- I usually do read the release notes. In fact I do not do auto updates because a breaking change snuck past me.
Oops.
However, I found the sound file I was looking for at:
\\HOMEASSISTANT\addon_configs\a0d7b954_nodered\sounds
In Node-red I previously addressed the file in a Read File node:
I tried changing the path to:
/addon_configs/a0d7b954_nodered/sounds/Unlock.wav
and Node Red can’t find it.
Any tips?
Here you go Stephen
Sorry it’s a long thread. The fix is in it.
Short version there was a bug in 16.0.0 and 16.0.1
Theted a couple different ways to fix it but in short you’re grabbing a backup copy of your flows reverting to 15.x, restoring your stuff. Killing a folder (to prevent recurrence) then ensuring NR starts properly. Once it does you’re clear to upgrade to 16.0.2
1 Like
The flows are working, but as @freshcoast indicated, the node-red folder moved.
I solved the problem by putting the sound files in /media.
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