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)
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.
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
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.
Still will not start all the logs say is:
Welcome to Node-RED
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:
Welcome to Node-RED
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.
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?
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.
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?)