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.
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.
Once you restore your backup - just give it a check before you attempt to start your 15.x (or pre 16) build If it has stuff in it that’s what hoses you.
(nice seeing you to, hope you’re well, B)
I had to revert to a full system backup from 2 weeks ago. Node-red isn’t starting currently, but at least I can see a config file in the system with my flows in there. Lost two weeks of data and changes though
This is … messy to be gentle about it
Yeah I was lulled into a false sense of security with the relatively straightforward updates for so long. I punched update while shaving this morning and now have to tend to the cut I gave myself when I saw about 30 VERY complex flows blown away.
now i can’t find the /addon_configs/ folder - is that the full path?
also, on 2023.9.3 now - any way to force an update check thru UI?
(will drop you a note once i get my full system up )
If you have the samba addon it exposes the folder as a share I’ll have to look up where it actually is in the file system.
15 Nov 09:15:23 - [info] Node-RED version: v3.1.0
15 Nov 09:15:23 - [info] Node.js version: v18.18.2
15 Nov 09:15:23 - [info] Linux 6.1.59 x64 LE
15 Nov 09:15:23 - [info] Loading palette nodes
15 Nov 09:15:24 - [info] Dashboard version 3.6.1 started at /endpoint/ui
15 Nov 09:15:24 - [info] Settings file : /etc/node-red/config.js
15 Nov 09:15:24 - [info] Context store : ‘default’ [module=memory]
15 Nov 09:15:24 - [info] User directory : /config/node-red/
15 Nov 09:15:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
15 Nov 09:15:24 - [info] Flows file : /config/node-red/flows.json
15 Nov 09:15:24 - [info] Server now running at http://127.0.0.1:46836/
15 Nov 09:15:24 - [info] Starting flows
15 Nov 09:15:25 - [info] Started flows
15 Nov 09:15:25 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:15:25 - [info] [server:Home Assistant] Connected to http://supervisor/core
[09:15:25] INFO: Starting
Node-Red is at 15.1.1
Node-red folder was copied over from the backup prior to all this mess
Started HA
Node-red still not starting:
15 Nov 09:15:23 - [info] Node-RED version: v3.1.0
15 Nov 09:15:23 - [info] Node.js version: v18.18.2
15 Nov 09:15:23 - [info] Linux 6.1.59 x64 LE
15 Nov 09:15:23 - [info] Loading palette nodes
15 Nov 09:15:24 - [info] Dashboard version 3.6.1 started at /endpoint/ui
15 Nov 09:15:24 - [info] Settings file : /etc/node-red/config.js
15 Nov 09:15:24 - [info] Context store : ‘default’ [module=memory]
15 Nov 09:15:24 - [info] User directory : /config/node-red/
15 Nov 09:15:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
15 Nov 09:15:24 - [info] Flows file : /config/node-red/flows.json
15 Nov 09:15:24 - [info] Server now running at http://127.0.0.1:46836/
15 Nov 09:15:24 - [info] Starting flows
15 Nov 09:15:25 - [info] Started flows
15 Nov 09:15:25 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:15:25 - [info] [server:Home Assistant] Connected to http://supervisor/core
[09:15:25] INFO: Starting NGinx…
15 Nov 09:28:52 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
15 Nov 09:28:52 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:28:57 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:07 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:12 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:17 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:22 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:27 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:37 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:42 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:47 - [info] [server:Home Assistant] Connecting to http://supervisor/core
15 Nov 09:29:47 - [info] [server:Home Assistant] Connected to http://supervisor/core
Showing that there is an update for Node-Red, but have NOT done it, trying to get it to work on 15.1.1.
its like ChatGPT did the coding on this one!
tbh … that all really s*cks! if you say that you have to restore everything “correctly” make me worry once again. damn… so much work invested for nothing now?
my learning from this one: starting backups on my flows every day from now on
can I somehow use a backed up copy of the flows_cred.json file to restore access to my flows?
or, can I start an new instance of nodered and import my flows from a json file?
it’s weird… i restored 15.1.1 and now i cant even start node-red anymore…
any ideas?
B - here’s the doc for the new addon_configs folder:
Public Addon Config | Home Assistant Developer Docs (home-assistant.io)
Looks like /addon_configs is only a mapping done completely through Docker.
From there Supervisor is mounting the Addon’s specific files to slug_addonname in that folder. I can only see it through the SMB share.
I imported my flows from 4 days ago - but they are all giving me a 502 error when anything in the flow executes
same here! But at least I can see my flows again…its something to work off of. I am updating to 16.02 to see if it changes anything
Leopold - What does your
Log say?
\config\node-red folder look like? (pre 16.x this is where your stuff lives)
\addon_configs\ folder look like?
if it exists - what’s in
\addon_configs\a0d7b954_nodered\ (I believe the slug is the same for everyone, POST 16.0.2 this is where your stuff will live, and it will start being backed up with the addonn. Ironic huh?)
thanks. ok, since i am on 2023.9.3 that won’t be there for now.
Same here. Managed to get a backup of my node config downloaded, but been trying to get node-red started for the past 45 minutes now.
Doing a full upgrade again, see if that helps
If it doesnt work Jeroen, same stuff as leopold we can help each other get started back up. But if it does - let us know and keep track of your process.
Hello Nathan,
thanks for the help. I’ll have to check it out. Do you know how I can access my folders with HA OS?
Cheers