reconnecting issue

[mevton123]

Hi Ben,

I've had a pretty thorough read of the other reconnecting issues and still can't figure out where I have gone wrong. I am new to HA.

I booted up a new HA green yesterday. I created an account and a device on your website set up the skill on Alexa no issue I installed node-red on HA I have one alexa home config node and that's it I entered my credentials from the website and it sits as reconnecting. I cannot see any devices to select from. I tried creating a new account on your website incase I somehow had two instances (other account is mevton

I have not really adjusted anything from factory settings so I am at a loss.

[mevton123]

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[09:14:18] FATAL: [31m[0m
[09:14:18] FATAL: [31mSSL has been enabled using the 'ssl' option,[0m
[09:14:18] FATAL: [31mthis requires an SSL certificate file which is[0m
[09:14:18] FATAL: [31mconfigured using the 'certfile' option in the[0m
[09:14:18] FATAL: [31madd-on configuration.[0m
[09:14:18] FATAL: [31m[0m
[09:14:18] FATAL: [31mUnfortunately, the file specified in the[0m
[09:14:18] FATAL: [31m'certfile' option does not exist.[0m
[09:14:18] FATAL: [31m[0m
[09:14:18] FATAL: [31mPlease ensure the certificate file exists and[0m
[09:14:18] FATAL: [31mis placed in the '/ssl/' directory.[0m
[09:14:18] FATAL: [31m[0m
[09:14:18] FATAL: [31mIn case you don't have SSL yet, consider getting[0m
[09:14:18] FATAL: [31man SSL certificate or setting the 'ssl' option[0m
[09:14:18] FATAL: [31mto 'false' in case you are not planning on using[0m
[09:14:18] FATAL: [31mSSL with this add-on.[0m
[09:14:18] FATAL: [31m[0m
[09:14:18] FATAL: [31mCheck the add-on manual for more information.[0m
[09:14:18] FATAL: [31m[0m
s6-rc: warning: unable to start service init-nginx: command exited 1
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[09:14:18] INFO: [32mService Node-RED exited with code 256 (by signal 15)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[09:14:52] FATAL: [31m[0m
[09:14:52] FATAL: [31mSSL has been enabled using the 'ssl' option,[0m
[09:14:52] FATAL: [31mthis requires an SSL certificate file which is[0m
[09:14:52] FATAL: [31mconfigured using the 'certfile' option in the[0m
[09:14:52] FATAL: [31madd-on configuration.[0m
[09:14:52] FATAL: [31m[0m
[09:14:52] FATAL: [31mUnfortunately, the file specified in the[0m
[09:14:52] FATAL: [31m'certfile' option does not exist.[0m
[09:14:52] FATAL: [31m[0m
[09:14:52] FATAL: [31mPlease ensure the certificate file exists and[0m
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
[09:14:52] FATAL: [31mis placed in the '/ssl/' directory.[0m
s6-rc: info: service nodered successfully started
[09:14:52] FATAL: [31m[0m
[09:14:52] FATAL: [31mIn case you don't have SSL yet, consider getting[0m
[09:14:52] FATAL: [31man SSL certificate or setting the 'ssl' option[0m
[09:14:52] FATAL: [31mto 'false' in case you are not planning on using[0m
[09:14:52] FATAL: [31mSSL with this add-on.[0m
[09:14:52] FATAL: [31m[0m
[09:14:52] FATAL: [31mCheck the add-on manual for more information.[0m
[09:14:52] FATAL: [31m[0m
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[09:14:52] INFO: [32mService Node-RED exited with code 256 (by signal 15)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[09:17:44] FATAL: [31m[0m
[09:17:44] FATAL: [31mSSL has been enabled using the 'ssl' option,[0m
[09:17:44] FATAL: [31mthis requires an SSL certificate file which is[0m
[09:17:44] FATAL: [31mconfigured using the 'certfile' option in the[0m
[09:17:44] FATAL: [31madd-on configuration.[0m
[09:17:44] FATAL: [31m[0m
[09:17:44] FATAL: [31mUnfortunately, the file specified in the[0m
[09:17:44] FATAL: [31m'certfile' option does not exist.[0m
[09:17:44] FATAL: [31m[0m
[09:17:44] FATAL: [31mPlease ensure the certificate file exists and[0m
[09:17:44] FATAL: [31mis placed in the '/ssl/' directory.[0m
[09:17:44] FATAL: [31m[0m
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
[09:17:44] FATAL: [31mIn case you don't have SSL yet, consider getting[0m
s6-rc: info: service nodered successfully started
[09:17:44] FATAL: [31man SSL certificate or setting the 'ssl' option[0m
[09:17:44] FATAL: [31mto 'false' in case you are not planning on using[0m
[09:17:44] FATAL: [31mSSL with this add-on.[0m
[09:17:44] FATAL: [31m[0m
[09:17:44] FATAL: [31mCheck the add-on manual for more information.[0m
[09:17:44] FATAL: [31m[0m
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[09:17:44] INFO: [32mService Node-RED exited with code 256 (by signal 15)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[09:18:07] FATAL: [31m[0m
[09:18:07] FATAL: [31mSSL has been enabled using the 'ssl' option,[0m
[09:18:07] FATAL: [31mthis requires an SSL certificate file which is[0m
[09:18:07] FATAL: [31mconfigured using the 'certfile' option in the[0m
[09:18:07] FATAL: [31madd-on configuration.[0m
[09:18:07] FATAL: [31m[0m
[09:18:07] FATAL: [31mUnfortunately, the file specified in the[0m
[09:18:07] FATAL: [31m'certfile' option does not exist.[0m
[09:18:07] FATAL: [31m[0m
[09:18:07] FATAL: [31mPlease ensure the certificate file exists and[0m
[09:18:07] FATAL: [31mis placed in the '/ssl/' directory.[0m
s6-rc: info: service init-nodered successfully started
[09:18:07] FATAL: [31m[0m
s6-rc: info: service nodered: starting
[09:18:07] FATAL: [31mIn case you don't have SSL yet, consider getting[0m
s6-rc: info: service nodered successfully started
[09:18:07] FATAL: [31man SSL certificate or setting the 'ssl' option[0m
[09:18:07] FATAL: [31mto 'false' in case you are not planning on using[0m
[09:18:07] FATAL: [31mSSL with this add-on.[0m
[09:18:07] FATAL: [31m[0m
[09:18:07] FATAL: [31mCheck the add-on manual for more information.[0m
[09:18:07] FATAL: [31m[0m
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[09:18:07] INFO: [32mService Node-RED exited with code 256 (by signal 15)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[09:18:16] FATAL: [31m[0m
[09:18:16] FATAL: [31mSSL has been enabled using the 'ssl' option,[0m
[09:18:16] FATAL: [31mthis requires an SSL certificate file which is[0m
[09:18:16] FATAL: [31mconfigured using the 'certfile' option in the[0m
[09:18:16] FATAL: [31madd-on configuration.[0m
[09:18:16] FATAL: [31m[0m
[09:18:16] FATAL: [31mUnfortunately, the file specified in the[0m
[09:18:16] FATAL: [31m'certfile' option does not exist.[0m
[09:18:16] FATAL: [31m[0m
[09:18:16] FATAL: [31mPlease ensure the certificate file exists and[0m
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
[09:18:16] FATAL: [31mis placed in the '/ssl/' directory.[0m
s6-rc: info: service nodered successfully started
[09:18:16] FATAL: [31m[0m
[09:18:16] FATAL: [31mIn case you don't have SSL yet, consider getting[0m
[09:18:16] FATAL: [31man SSL certificate or setting the 'ssl' option[0m
[09:18:16] FATAL: [31mto 'false' in case you are not planning on using[0m
[09:18:16] FATAL: [31mSSL with this add-on.[0m
[09:18:16] FATAL: [31m[0m
[09:18:16] FATAL: [31mCheck the add-on manual for more information.[0m
[09:18:16] FATAL: [31m[0m
s6-rc: warning: unable to start service init-nginx: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service nodered: stopping
[09:18:16] INFO: [32mService Node-RED exited with code 256 (by signal 15)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service init-nginx successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:21:45] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 09:21:48 - [info] 

Welcome to Node-RED
===================

5 Nov 09:21:48 - [info] Node-RED version: v4.0.9
5 Nov 09:21:48 - [info] Node.js  version: v22.16.0
5 Nov 09:21:48 - [info] Linux 6.12.43-haos arm64 LE
5 Nov 09:21:49 - [info] Loading palette nodes
5 Nov 09:21:50 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 09:21:55 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 09:21:57 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 09:21:58 - [info] Settings file  : /etc/node-red/config.js
5 Nov 09:21:58 - [info] Context store  : 'default' [module=memory]
5 Nov 09:21:58 - [info] User directory : /config/
5 Nov 09:21:58 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 09:21:58 - [info] Flows file     : /config/flows.json
5 Nov 09:21:58 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 09:21:58 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 09:21:58 - [warn] Encrypted credentials not found
5 Nov 09:21:58 - [info] Starting flows
5 Nov 09:21:58 - [info] Started flows
[09:21:59] INFO: [32mStarting NGinx...[0m
5 Nov 09:22:03 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:22:03 - [info] [server:Home Assistant] Connected to http://supervisor/core
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[09:26:51] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 09:26:51 - [info] Stopping flows
5 Nov 09:26:51 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 09:26:51 - [info] Stopped flows
[09:26:52] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 1 package in 3s

found 0 vulnerabilities
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:27:00] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 09:27:04 - [info] 

Welcome to Node-RED
===================

5 Nov 09:27:04 - [info] Node-RED version: v4.0.9
5 Nov 09:27:04 - [info] Node.js  version: v22.16.0
5 Nov 09:27:04 - [info] Linux 6.12.43-haos arm64 LE
5 Nov 09:27:05 - [info] Loading palette nodes
5 Nov 09:27:06 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 09:27:11 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 09:27:13 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 09:27:14 - [info] Settings file  : /etc/node-red/config.js
5 Nov 09:27:14 - [info] Context store  : 'default' [module=memory]
5 Nov 09:27:14 - [info] User directory : /config/
5 Nov 09:27:14 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 09:27:14 - [info] Flows file     : /config/flows.json
5 Nov 09:27:14 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 09:27:14 - [warn] Encrypted credentials not found
5 Nov 09:27:14 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 09:27:14 - [info] Starting flows
5 Nov 09:27:14 - [info] Started flows
[09:27:14] INFO: [32mStarting NGinx...[0m
5 Nov 09:27:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:27:19 - [info] [server:Home Assistant] Connected to http://supervisor/core
5 Nov 09:35:04 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
5 Nov 09:35:09 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:14 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:19 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:24 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:29 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:34 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:40 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:45 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:55 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:35:55 - [info] [server:Home Assistant] Connected to http://supervisor/core
5 Nov 09:45:28 - [info] Installing module: node-red-contrib-alexa-home-skill, version: 0.1.19
5 Nov 09:45:49 - [info] Installed module: node-red-contrib-alexa-home-skill
5 Nov 09:45:50 - [info] Added node types:
5 Nov 09:45:50 - [info]  - node-red-contrib-alexa-home-skill:alexa-home-conf
5 Nov 09:45:50 - [info]  - node-red-contrib-alexa-home-skill:alexa-home
5 Nov 09:45:50 - [info]  - node-red-contrib-alexa-home-skill:alexa-home-resp
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
5 Nov 09:49:21 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
5 Nov 09:49:27 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:37 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:42 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:47 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:52 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:49:57 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:50:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:50:07 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:50:12 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:50:12 - [info] [server:Home Assistant] Connected to http://supervisor/core
5 Nov 09:51:11 - [info] Stopping flows
5 Nov 09:51:11 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 09:51:11 - [info] Stopped flows
5 Nov 09:51:11 - [info] Updated flows
5 Nov 09:51:11 - [info] Starting flows
5 Nov 09:51:11 - [info] Started flows
5 Nov 09:51:16 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:51:16 - [info] [server:Home Assistant] Connected to http://supervisor/core
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[09:54:00] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 09:54:00 - [info] Stopping flows
5 Nov 09:54:00 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 09:54:00 - [info] Stopped flows
[09:54:01] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.2  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 6s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[09:54:13] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 09:54:17 - [info] 

Welcome to Node-RED
===================

5 Nov 09:54:17 - [info] Node-RED version: v4.0.9
5 Nov 09:54:17 - [info] Node.js  version: v22.16.0
5 Nov 09:54:17 - [info] Linux 6.12.43-haos arm64 LE
5 Nov 09:54:17 - [info] Loading palette nodes
5 Nov 09:54:19 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 09:54:25 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 09:54:27 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 09:54:27 - [info] Settings file  : /etc/node-red/config.js
5 Nov 09:54:27 - [info] Context store  : 'default' [module=memory]
5 Nov 09:54:27 - [info] User directory : /config/
5 Nov 09:54:27 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 09:54:27 - [info] Flows file     : /config/flows.json
5 Nov 09:54:27 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 09:54:27 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 09:54:27 - [info] Starting flows
[09:54:28] INFO: [32mStarting NGinx...[0m
5 Nov 09:54:28 - [info] Started flows
5 Nov 09:54:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:54:32 - [info] [server:Home Assistant] Connected to http://supervisor/core
5 Nov 09:57:26 - [info] Stopping flows
5 Nov 09:57:26 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 09:57:26 - [info] Stopped flows
5 Nov 09:57:26 - [info] Updated flows
5 Nov 09:57:26 - [info] Starting flows
5 Nov 09:57:26 - [info] Started flows
5 Nov 09:57:31 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 09:57:31 - [info] [server:Home Assistant] Connected to http://supervisor/core
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[10:08:54] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 10:08:54 - [info] Stopping flows
5 Nov 10:08:54 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 10:08:54 - [info] Stopped flows
[10:08:54] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.3  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 7s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[10:11:17] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 10:11:21 - [info] 

Welcome to Node-RED
===================

5 Nov 10:11:21 - [info] Node-RED version: v4.0.9
5 Nov 10:11:21 - [info] Node.js  version: v22.16.0
5 Nov 10:11:21 - [info] Linux 6.12.51-haos arm64 LE
5 Nov 10:11:22 - [info] Loading palette nodes
5 Nov 10:11:24 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 10:11:31 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 10:11:33 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 10:11:33 - [info] Settings file  : /etc/node-red/config.js
5 Nov 10:11:33 - [info] Context store  : 'default' [module=memory]
5 Nov 10:11:33 - [info] User directory : /config/
5 Nov 10:11:33 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 10:11:33 - [info] Flows file     : /config/flows.json
5 Nov 10:11:33 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 10:11:33 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 10:11:33 - [info] Starting flows
5 Nov 10:11:34 - [info] Started flows
[10:11:34] INFO: [32mStarting NGinx...[0m
5 Nov 10:11:39 - [info] [server:Home Assistant] Connecting to http://supervisor/core
5 Nov 10:11:39 - [info] [server:Home Assistant] Connected to http://supervisor/core
5 Nov 10:15:33 - [info] Stopping flows
5 Nov 10:15:33 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
5 Nov 10:15:33 - [info] Stopped flows
5 Nov 10:15:33 - [info] Updated flows
5 Nov 10:15:33 - [info] Starting flows
5 Nov 10:15:33 - [info] Started flows
5 Nov 10:16:10 - [info] Stopping flows
5 Nov 10:16:10 - [info] Stopped flows
5 Nov 10:16:10 - [info] Updated flows
5 Nov 10:16:10 - [info] Starting flows
5 Nov 10:16:10 - [info] Started flows
5 Nov 10:28:58 - [info] Stopping flows
5 Nov 10:28:58 - [info] Stopped flows
5 Nov 10:28:58 - [info] Updated flows
5 Nov 10:28:58 - [info] Starting flows
5 Nov 10:28:58 - [info] Started flows
5 Nov 10:55:55 - [info] Stopping flows
5 Nov 10:55:55 - [info] Stopped flows
5 Nov 10:55:55 - [info] Updated flows
5 Nov 10:55:55 - [info] Starting flows
5 Nov 10:55:55 - [info] Started flows
5 Nov 10:57:06 - [info] Stopping flows
5 Nov 10:57:06 - [info] Stopped flows
5 Nov 10:57:06 - [info] Updated flows
5 Nov 10:57:06 - [info] Starting flows
5 Nov 10:57:06 - [info] Started flows
5 Nov 10:57:13 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 10:57:13 - [info] Stopping flows
5 Nov 10:57:13 - [info] Stopped flows
5 Nov 10:57:13 - [info] Starting flows
5 Nov 10:57:13 - [info] Started flows
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[10:58:36] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 10:58:36 - [info] Stopping flows
5 Nov 10:58:36 - [info] Stopped flows
[10:58:36] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.3  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 6s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[10:58:49] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 10:58:52 - [info] 

Welcome to Node-RED
===================

5 Nov 10:58:52 - [info] Node-RED version: v4.0.9
5 Nov 10:58:52 - [info] Node.js  version: v22.16.0
5 Nov 10:58:52 - [info] Linux 6.12.51-haos arm64 LE
5 Nov 10:58:53 - [info] Loading palette nodes
5 Nov 10:58:54 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 10:59:00 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 10:59:02 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 10:59:03 - [info] Settings file  : /etc/node-red/config.js
5 Nov 10:59:03 - [info] Context store  : 'default' [module=memory]
5 Nov 10:59:03 - [info] User directory : /config/
5 Nov 10:59:03 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 10:59:03 - [info] Flows file     : /config/flows.json
5 Nov 10:59:03 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 10:59:03 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 10:59:03 - [info] Starting flows
5 Nov 10:59:03 - [info] Started flows
[10:59:03] INFO: [32mStarting NGinx...[0m
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[12:34:42] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 12:34:42 - [info] Stopping flows
5 Nov 12:34:42 - [info] Stopped flows
[12:34:42] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.3  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[34mLog level is set to DEBUG[0m
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 6s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[12:34:55] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 12:34:58 - [info] 

Welcome to Node-RED
===================

5 Nov 12:34:58 - [info] Node-RED version: v4.0.9
5 Nov 12:34:58 - [info] Node.js  version: v22.16.0
5 Nov 12:34:58 - [info] Linux 6.12.51-haos arm64 LE
5 Nov 12:34:59 - [info] Loading palette nodes
5 Nov 12:35:00 - [debug] Module: node-red-contrib-alexa-home-skill 0.1.19 /config/node_modules/node-red-contrib-alexa-home-skill
5 Nov 12:35:00 - [debug] Module: @node-red-contrib-themes/theme-collection 4.0.11 /opt/node_modules/@node-red-contrib-themes/theme-collection
5 Nov 12:35:00 - [debug] Module: node-red-contrib-bigtimer 2.8.6 /opt/node_modules/node-red-contrib-bigtimer
5 Nov 12:35:00 - [debug] Module: node-red-contrib-cast 0.2.17 /opt/node_modules/node-red-contrib-cast
5 Nov 12:35:00 - [debug] Module: node-red-contrib-counter 0.1.6 /opt/node_modules/node-red-contrib-counter
5 Nov 12:35:00 - [debug] Module: node-red-contrib-home-assistant-websocket 0.77.1 /opt/node_modules/node-red-contrib-home-assistant-websocket
5 Nov 12:35:00 - [debug] Module: node-red-contrib-influxdb 0.7.0 /opt/node_modules/node-red-contrib-influxdb
5 Nov 12:35:00 - [debug] Module: node-red-contrib-interval-length 0.0.6 /opt/node_modules/node-red-contrib-interval-length
5 Nov 12:35:00 - [debug] Module: node-red-contrib-modbus 5.43.0 /opt/node_modules/node-red-contrib-modbus
5 Nov 12:35:00 - [debug] Module: node-red-contrib-moment 5.0.0 /opt/node_modules/node-red-contrib-moment
5 Nov 12:35:00 - [debug] Module: node-red-contrib-persistent-fsm 1.2.1 /opt/node_modules/node-red-contrib-persistent-fsm
5 Nov 12:35:00 - [debug] Module: node-red-contrib-sunevents 3.1.1 /opt/node_modules/node-red-contrib-sunevents
5 Nov 12:35:00 - [debug] Module: node-red-contrib-time-range-switch 1.2.0 /opt/node_modules/node-red-contrib-time-range-switch
5 Nov 12:35:00 - [debug] Module: node-red-dashboard 3.6.5 /opt/node_modules/node-red-dashboard
5 Nov 12:35:00 - [debug] Module: node-red-node-base64 1.0.0 /opt/node_modules/node-red-node-base64
5 Nov 12:35:00 - [debug] Module: node-red-node-email 3.0.3 /opt/node_modules/node-red-node-email
5 Nov 12:35:00 - [debug] Module: node-red-node-feedparser 0.3.0 /opt/node_modules/node-red-node-feedparser
5 Nov 12:35:00 - [debug] Module: node-red-node-ping 0.3.3 /opt/node_modules/node-red-node-ping
5 Nov 12:35:00 - [debug] Module: node-red-node-random 0.4.1 /opt/node_modules/node-red-node-random
5 Nov 12:35:00 - [debug] Module: node-red-node-serialport 2.0.3 /opt/node_modules/node-red-node-serialport
5 Nov 12:35:00 - [debug] Module: node-red-node-smooth 0.1.2 /opt/node_modules/node-red-node-smooth
5 Nov 12:35:00 - [debug] Module: node-red-node-suncalc 1.2.0 /opt/node_modules/node-red-node-suncalc
5 Nov 12:35:00 - [debug] Module: node-red-node-twitter 1.2.0 /opt/node_modules/node-red-node-twitter
5 Nov 12:35:00 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 12:35:06 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 12:35:08 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 12:35:09 - [info] Settings file  : /etc/node-red/config.js
5 Nov 12:35:09 - [info] Context store  : 'default' [module=memory]
5 Nov 12:35:09 - [info] User directory : /config/
5 Nov 12:35:09 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 12:35:09 - [info] Flows file     : /config/flows.json
5 Nov 12:35:09 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 12:35:09 - [debug] loaded flow revision: 82267cbc817c5adc99b9ced59d93c2bbe37d8fb1aab04c182a91b5985f6db5f6
5 Nov 12:35:09 - [debug] red/runtime/nodes/credentials.load : no user key present
5 Nov 12:35:09 - [debug] red/runtime/nodes/credentials.load : using default key
5 Nov 12:35:09 - [debug] red/runtime/nodes/credentials.load : keyType=system
5 Nov 12:35:09 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 12:35:09 - [info] Starting flows
5 Nov 12:35:09 - [debug] red/nodes/flows.start : starting flow : global
5 Nov 12:35:09 - [debug] red/nodes/flows.start : starting flow : 178a5af67f5c290c
[12:35:09] INFO: [32mStarting NGinx...[0m
5 Nov 12:35:09 - [info] Started flows
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[13:08:27] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
5 Nov 13:08:27 - [info] Stopping flows
5 Nov 13:08:27 - [debug] red/nodes/flows.stop : stopping flow : 178a5af67f5c290c
5 Nov 13:08:27 - [debug] red/nodes/flows.stop : stopping flow : global
5 Nov 13:08:27 - [info] Stopped flows
[13:08:27] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.3  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[34mLog level is set to DEBUG[0m
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 6s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[13:08:42] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

5 Nov 13:08:45 - [info] 

Welcome to Node-RED
===================

5 Nov 13:08:45 - [info] Node-RED version: v4.0.9
5 Nov 13:08:45 - [info] Node.js  version: v22.16.0
5 Nov 13:08:45 - [info] Linux 6.12.51-haos arm64 LE
5 Nov 13:08:46 - [info] Loading palette nodes
5 Nov 13:08:46 - [debug] Module: node-red-contrib-alexa-home-skill 0.1.19 /config/node_modules/node-red-contrib-alexa-home-skill
5 Nov 13:08:46 - [debug] Module: @node-red-contrib-themes/theme-collection 4.0.11 /opt/node_modules/@node-red-contrib-themes/theme-collection
5 Nov 13:08:46 - [debug] Module: node-red-contrib-bigtimer 2.8.6 /opt/node_modules/node-red-contrib-bigtimer
5 Nov 13:08:46 - [debug] Module: node-red-contrib-cast 0.2.17 /opt/node_modules/node-red-contrib-cast
5 Nov 13:08:46 - [debug] Module: node-red-contrib-counter 0.1.6 /opt/node_modules/node-red-contrib-counter
5 Nov 13:08:46 - [debug] Module: node-red-contrib-home-assistant-websocket 0.77.1 /opt/node_modules/node-red-contrib-home-assistant-websocket
5 Nov 13:08:46 - [debug] Module: node-red-contrib-influxdb 0.7.0 /opt/node_modules/node-red-contrib-influxdb
5 Nov 13:08:46 - [debug] Module: node-red-contrib-interval-length 0.0.6 /opt/node_modules/node-red-contrib-interval-length
5 Nov 13:08:46 - [debug] Module: node-red-contrib-modbus 5.43.0 /opt/node_modules/node-red-contrib-modbus
5 Nov 13:08:46 - [debug] Module: node-red-contrib-moment 5.0.0 /opt/node_modules/node-red-contrib-moment
5 Nov 13:08:46 - [debug] Module: node-red-contrib-persistent-fsm 1.2.1 /opt/node_modules/node-red-contrib-persistent-fsm
5 Nov 13:08:47 - [debug] Module: node-red-contrib-sunevents 3.1.1 /opt/node_modules/node-red-contrib-sunevents
5 Nov 13:08:47 - [debug] Module: node-red-contrib-time-range-switch 1.2.0 /opt/node_modules/node-red-contrib-time-range-switch
5 Nov 13:08:47 - [debug] Module: node-red-dashboard 3.6.5 /opt/node_modules/node-red-dashboard
5 Nov 13:08:47 - [debug] Module: node-red-node-base64 1.0.0 /opt/node_modules/node-red-node-base64
5 Nov 13:08:47 - [debug] Module: node-red-node-email 3.0.3 /opt/node_modules/node-red-node-email
5 Nov 13:08:47 - [debug] Module: node-red-node-feedparser 0.3.0 /opt/node_modules/node-red-node-feedparser
5 Nov 13:08:47 - [debug] Module: node-red-node-ping 0.3.3 /opt/node_modules/node-red-node-ping
5 Nov 13:08:47 - [debug] Module: node-red-node-random 0.4.1 /opt/node_modules/node-red-node-random
5 Nov 13:08:47 - [debug] Module: node-red-node-serialport 2.0.3 /opt/node_modules/node-red-node-serialport
5 Nov 13:08:47 - [debug] Module: node-red-node-smooth 0.1.2 /opt/node_modules/node-red-node-smooth
5 Nov 13:08:47 - [debug] Module: node-red-node-suncalc 1.2.0 /opt/node_modules/node-red-node-suncalc
5 Nov 13:08:47 - [debug] Module: node-red-node-twitter 1.2.0 /opt/node_modules/node-red-node-twitter
5 Nov 13:08:47 - [info] Node-RED Contrib Theme Collection version: v4.0.11
5 Nov 13:08:53 - [info] Dashboard version 3.6.5 started at /endpoint/ui
5 Nov 13:08:55 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
5 Nov 13:08:56 - [info] Settings file  : /etc/node-red/config.js
5 Nov 13:08:56 - [info] Context store  : 'default' [module=memory]
5 Nov 13:08:56 - [info] User directory : /config/
5 Nov 13:08:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Nov 13:08:56 - [info] Flows file     : /config/flows.json
5 Nov 13:08:56 - [info] Server now running at http://127.0.0.1:46836/
5 Nov 13:08:56 - [debug] loaded flow revision: 82267cbc817c5adc99b9ced59d93c2bbe37d8fb1aab04c182a91b5985f6db5f6
5 Nov 13:08:56 - [debug] red/runtime/nodes/credentials.load : no user key present
5 Nov 13:08:56 - [debug] red/runtime/nodes/credentials.load : using default key
5 Nov 13:08:56 - [debug] red/runtime/nodes/credentials.load : keyType=system
5 Nov 13:08:56 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

5 Nov 13:08:56 - [info] Starting flows
5 Nov 13:08:56 - [debug] red/nodes/flows.start : starting flow : global
5 Nov 13:08:56 - [debug] red/nodes/flows.start : starting flow : 178a5af67f5c290c
[13:08:56] INFO: [32mStarting NGinx...[0m
5 Nov 13:08:56 - [info] Started flows

[hardillb]

Please clarify the orginal username, as I can't find either melmelmel or meimeimei in the database.

Also if the list of devices doesn't populate, even after clicking on the refresh arrows next to the dropdown, at all that strongly implies either a typo in the username or the password (also password can not container the @ character.

[mevton123]

Hi Ben,

The original user name was mevton, which I linked to the alexa skill.

Then I created melmelmel, which also didn't work.

Passwords do not contain @.

I am very sure I'm not making a typo in username or password, and can successfully log on to https://alexa-node-red.bm.hardill.me.uk/devices

On Wed, 5 Nov 2025, 6:52 pm Ben Hardill, @.***> wrote:

hardillb left a comment (hardillb/node-red-alexa-home-skill-web#205) https://github.com/hardillb/node-red-alexa-home-skill-web/issues/205#issuecomment-3489799832

Please clarify the orginal username, as I can't find either melmelmel or meimeimei in the database.

Also if the list of devices doesn't populate at all that strongly implies either a typo in the username or the password (also password can not container the @ character.

— Reply to this email directly, view it on GitHub https://github.com/hardillb/node-red-alexa-home-skill-web/issues/205#issuecomment-3489799832, or unsubscribe https://github.com/notifications/unsubscribe-auth/BZVW7EC4ASWCLXZVIDX6ZNT33GUDXAVCNFSM6AAAAACLFHVCRKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIOBZG44TSOBTGI . You are receiving this because you authored the thread.Message ID: @.***>

[hardillb]

What happens if you run

curl -u <username>:<password> -v https://alexa-node-red.bm.hardill.me.uk/api/v1/devices

You should run this INSIDE the node-red container

p.s. if pasting multiline output please wrap it in triple back ticks (on their own lines), not single

[mevton123]

Hi Ben,

See below. The password for mevton contained a : After changing the password to remove :, it also worked. However, still no joy in the node red UI I did update the password on the alexa config node

root@a0d7b954-nodered:/opt$ curl -u mevton:******** https://alexa-node-red.bm.hardill.me.uk/api/v1/devices
Unauthorized

root@a0d7b954-nodered:/opt$ curl -u melmelmel:******** https://alexa-node-red.bm.hardill.me.uk/api/v1/devices
[{"friendlyName":"dummy","friendlyDescription":"dummy","applianceId":"248544","isReachable":true,"actions":["turnOn","turnOff"],"applianceTypes":["SWITCH"],"additionalApplianceDetails":{},"modelName":"Node-RED Endpoint","version":"0.0.1","manufacturerName":"Node-RED"}]

root@a0d7b954-nodered:/opt$ curl -u mevton:******** https://alexa-node-red.bm.hardill.me.uk/api/v1/devices
[{"friendlyName":"Kitchen Dining","friendlyDescription":"clean the kitchen and Dining rooms","applianceId":"248542","isReachable":true,"actions":["turnOn","turnOff"],"applianceTypes":["SWITCH"],"additionalApplianceDetails":{},"modelName":"Node-RED Endpoint"}]

[mevton123]

I noticed a little more info on the log for node red, if it helps.

5 Nov 13:08:56 - [info] Starting flows
5 Nov 13:08:56 - [debug] red/nodes/flows.start : starting flow : global
5 Nov 13:08:56 - [debug] red/nodes/flows.start : starting flow : 178a5af67f5c290c
[13:08:56] INFO: Starting NGinx...
5 Nov 13:08:56 - [info] Started flows
5 Nov 19:09:07 - [debug] red/runtime/nodes/credentials.export : encrypting
5 Nov 19:09:07 - [debug] saved flow revision: 41196362791659158be1e5bd91267d19358e385b03e8f0c04c015097146eef81
5 Nov 19:09:07 - [info] Stopping flows
5 Nov 19:09:07 - [debug] red/nodes/flows.stop : stopping flow : 178a5af67f5c290c
5 Nov 19:09:07 - [debug] red/nodes/flows.stop : stopping flow : global
5 Nov 19:09:07 - [info] Stopped flows
5 Nov 19:09:07 - [info] Updated flows
5 Nov 19:09:07 - [info] Starting flows
5 Nov 19:09:07 - [debug] red/nodes/flows.start : starting flow : global
5 Nov 19:09:08 - [debug] red/nodes/flows.start : starting flow : 178a5af67f5c290c
5 Nov 19:09:08 - [info] Started flows
2025/11/06 19:08:34 [error] 383#383: *442 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "POST /alexa-home/new-account HTTP/1.1", upstream: "http://127.0.0.1:46836/alexa-home/new-account", host: "homeassistant.local:8123", referrer: "http://homeassistant.local:8123/api/hassio_ingress/xA2EgItW186PchBo-zvCLTwaGUzjWWBB7JP4VeX28HU/"

[hardillb]

2025/11/06 19:08:34 [error] 383#383: *442 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "POST /alexa-home/new-account HTTP/1.1", upstream: "http://127.0.0.1:46836/alexa-home/new-account", host: "homeassistant.local:8123", referrer: "http://homeassistant.local:8123/api/hassio_ingress/xA2EgItW186PchBo-zvCLTwaGUzjWWBB7JP4VeX28HU/"

That is not related to my nodes at all, but does raise the question of what other nodes you have installed as there are some clashes.

Please attach the /data/package.json file from inside the container as this should list all the nodes you have installed.

Also now you've fixed the password, do you get the list of devices in the drop down when you click on the refresh arrows next to it? (you will have to wait 2-3 seconds after click the refresh)? Doing this should also write a log message if it fails like:

Problem looking up mevton's devices

[mevton123]

package attached.

No devices show up. The refresh button does not seem to work, looks like just a picture of the arrows rather than a button.

package.json

[hardillb]

It is just an image, but you can still click on it

And as I asked, can you please show the logs covering the time you clicked on it, it would also be useful to see the brower console when you click on the refresh icon to see if the request are even making it to the backend.

But this is very much starting to smell like a Home Assistant problem

[mevton123]

Hey Ben, yeah really doesn't seem like a you problem, thanks for helping anyway. I am literally teaching myself as I go to meet each of your requests, sorry for being a pain! I'll definitely send you a beer from Aus :)

I can't see anything in the Node-Red logs when I click on it.

Here are some screenshots from the browser console. Let me know if you need more than this.

s6-rc: info: service init-nodered: starting
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 5s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[21:52:11] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

7 Nov 21:52:14 - [info] 

Welcome to Node-RED
===================

7 Nov 21:52:14 - [info] Node-RED version: v4.0.9
7 Nov 21:52:14 - [info] Node.js  version: v22.16.0
7 Nov 21:52:14 - [info] Linux 6.12.51-haos arm64 LE
7 Nov 21:52:15 - [info] Loading palette nodes
7 Nov 21:52:16 - [info] Node-RED Contrib Theme Collection version: v4.0.11
7 Nov 21:52:22 - [info] Dashboard version 3.6.5 started at /endpoint/ui
7 Nov 21:52:24 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
7 Nov 21:52:25 - [info] Settings file  : /etc/node-red/config.js
7 Nov 21:52:25 - [info] Context store  : 'default' [module=memory]
7 Nov 21:52:25 - [info] User directory : /config/
7 Nov 21:52:25 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Nov 21:52:25 - [info] Flows file     : /config/flows.json
7 Nov 21:52:25 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

7 Nov 21:52:25 - [warn] Encrypted credentials not found
7 Nov 21:52:25 - [info] Server now running at http://127.0.0.1:46836/
7 Nov 21:52:25 - [info] Starting flows
7 Nov 21:52:25 - [info] Started flows
[21:52:25] INFO: [32mStarting NGinx...[0m
7 Nov 21:52:30 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 21:52:30 - [info] [server:Home Assistant] Connected to http://supervisor/core
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
Can't refresh until deployed
7 Nov 21:53:24 - [info] Stopping flows
7 Nov 21:53:24 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
7 Nov 21:53:24 - [info] Stopped flows
7 Nov 21:53:24 - [info] Updated flows
7 Nov 21:53:24 - [info] Starting flows
7 Nov 21:53:24 - [info] Started flows
7 Nov 21:53:29 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 21:53:29 - [info] [server:Home Assistant] Connected to http://supervisor/core
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[22:48:53] INFO: [32mService NGINX exited with code 0 (by signal 0)[0m
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
7 Nov 22:48:53 - [info] Stopping flows
7 Nov 22:48:53 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
7 Nov 22:48:53 - [info] Stopped flows
[22:48:53] INFO: [32mService Node-RED exited with code 0 (by signal 0)[0m
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service base-addon-banner: starting

[34m-----------------------------------------------------------[0m
[34m Add-on: Node-RED[0m
[34m Flow-based programming for the Internet of Things[0m
[34m-----------------------------------------------------------[0m
[34m Add-on version: 20.0.0[0m
[32m You are running the latest version of this add-on.[0m
[34m System: Home Assistant OS 16.3  (aarch64 / green)[0m
[34m Home Assistant Core: 2025.10.4[0m
[34m Home Assistant Supervisor: 2025.11.1[0m
[34m-----------------------------------------------------------[0m
[34m Please, share the above information when looking for help[0m
[34m or support in, e.g., GitHub, forums or the Discord chat.[0m
[34m-----------------------------------------------------------[0m
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[34mLog level is set to TRACE[0m
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service init-nginx: starting
s6-rc: info: service init-customizations: starting
[22:48:58] TRACE: bashio::config.has_value: system_packages
[22:48:58] TRACE: bashio::addon.ip_address
[22:48:58] TRACE: bashio::addons self addons.self.ip_address .ip_address // empty
[22:48:58] TRACE: bashio::config: system_packages
[22:48:58] TRACE: bashio::cache.exists: addons.self.ip_address
[22:48:58] TRACE: bashio::addon.config
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.ip_address.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::var.false: self
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::cache.get: addons.self.options.config
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::cache.get: addons.self.info
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:58] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.system_packages == null) then
            null
        elif (.system_packages | type == "string") then
            .system_packages // empty
        elif (.system_packages | type == "boolean") then
            .system_packages // false
        elif (.system_packages | type == "array") then
            if (.system_packages == []) then
                empty
            else
                .system_packages[]
            end
        elif (.system_packages | type == "object") then
            if (.system_packages == {}) then
                empty
            else
                .system_packages
            end
        else
            .system_packages
        end
[22:48:58] TRACE: bashio::var.has_value: .ip_address // empty
[22:48:58] TRACE: bashio::jq: {"name":"Node-RED","slug":"a0d7b954_nodered","hostname":"a0d7b954-nodered","dns":["a0d7b954-nodered.local.hass.io"],"description":"Flow-based programming for the Internet of Things","long_description":"# Home Assistant Community Add-on: Node-RED

[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]

[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]

[![Sponsor Frenck via GitHub Sponsors][github-sponsors-shield]][github-sponsors]

[![Support Frenck on Patreon][patreon-shield]][patreon]

Flow-based programming for the Internet of Things.

## About

[Node-RED][nodered] is a programming tool for wiring together hardware devices,
APIs and online services in new and interesting ways.

It provides a browser-based editor that makes it easy to wire together flows
using the wide range of nodes in the palette that can be deployed to its
runtime in a single click.

![Node-RED in the Home Assistant Frontend][screenshot]

[discord-shield]: https://img.shields.io/discord/478094546522079232.svg
[discord]: https://discord.me/hassioaddons
[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg
[forum]: https://community.home-assistant.io/t/home-assistant-community-add-on-node-red/55023?u=frenck
[github-sponsors-shield]: https://frenck.dev/wp-content/uploads/2019/12/github_sponsor.png
[github-sponsors]: https://github.com/sponsors/frenck
[maintenance-shield]: https://img.shields.io/maintenance/yes/2025.svg
[nodered]: https://nodered.org
[patreon-shield]: https://frenck.dev/wp-content/uploads/2019/12/patreon.png
[patreon]: https://www.patreon.com/frenck
[project-stage-shield]: https://img.shields.io/badge/project%20stage-production%20ready-brightgreen.svg
[release-shield]: https://img.shields.io/badge/version-v20.0.0-blue.svg
[release]: https://github.com/hassio-addons/addon-node-red/tree/v20.0.0
[screenshot]: https://github.com/hassio-addons/addon-node-red/raw/main/images/screenshot.png","advanced":false,"stage":"stable","repository":"a0d7b954","version_latest":"20.0.0","protected":true,"rating":5,"boot_config":"auto","boot":"auto","options":{"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"},"schema":[{"name":"log_level","optional":true,"type":"select","options":["trace","debug","info","notice","warning","error","fatal"]},{"name":"credential_secret","optional":true,"type":"string","format":"password"},{"name":"theme","optional":true,"type":"select","options":["default","aurora","cobalt2","dark","dracula","espresso-libre","github-dark","github-dark-default","github-dark-dimmed","midnight-red","monoindustrial","monokai","monokai-dimmed","noctis","oceanic-next","oled","one-dark-pro","one-dark-pro-darker","solarized-dark","solarized-light","tokyo-night","tokyo-night-light","tokyo-night-storm","totallyinformation","zenburn"]},{"name":"http_node","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"http_static","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"ssl","required":true,"type":"boolean"},{"name":"certfile","required":true,"type":"string"},{"name":"keyfile","required":true,"type":"string"},{"name":"system_packages","multiple":true,"required":true,"type":"string"},{"name":"npm_packages","multiple":true,"required":true,"type":"string"},{"name":"init_commands","multiple":true,"required":true,"type":"string"},{"name":"leave_front_door_open","optional":true,"type":"boolean"},{"name":"safe_mode","optional":true,"type":"boolean"},{"name":"max_old_space_size","optional":true,"type":"integer"}],"arch":["aarch64","amd64"],"machine":[],"homeassistant":"2023.3.0","url":"https://github.com/hassio-addons/addon-node-red","detached":false,"available":true,"build":false,"network":{"80/tcp":1880},"network_description":{"80/tcp":"Web interface"},"host_network":true,"host_pid":false,"host_ipc":false,"host_uts":false,"host_dbus":false,"privileged":[],"full_access":false,"apparmor":"default","icon":true,"logo":true,"changelog":true,"documentation":true,"stdin":false,"hassio_api":true,"hassio_role":"manager","auth_api":true,"homeassistant_api":true,"gpio":false,"usb":false,"uart":true,"kernel_modules":false,"devicetree":false,"udev":false,"docker_api":false,"video":false,"audio":false,"startup":"application","services":[],"discovery":[],"translations":{},"ingress":true,"signed":false,"state":"startup","webui":null,"ingress_entry":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g","ingress_url":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g/","ingress_port":64653,"ingress_panel":true,"audio_input":null,"audio_output":null,"auto_update":false,"ip_address":"172.30.32.1","version":"20.0.0","update_available":false,"watchdog":true,"devices":[],"system_managed":false,"system_managed_config_entry":null} .ip_address // empty
[22:48:58] TRACE: bashio::var.has_value: 
[22:48:58] TRACE: bashio::config.has_value: npm_packages
[22:48:58] TRACE: bashio::config: npm_packages
[22:48:58] TRACE: bashio::cache.set: addons.self.ip_address 172.30.32.1
[22:48:58] TRACE: bashio::addon.config
[22:48:58] TRACE: bashio::fs.directory_exists: /tmp/.bashio
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::addon.ingress_port
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::addons self addons.self.ingress_port .ingress_port // empty
[22:48:58] TRACE: bashio::cache.exists: addons.self.ingress_port
[22:48:58] TRACE: bashio::cache.get: addons.self.options.config
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.ingress_port.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::var.false: self
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.npm_packages == null) then
            null
        elif (.npm_packages | type == "string") then
            .npm_packages // empty
        elif (.npm_packages | type == "boolean") then
            .npm_packages // false
        elif (.npm_packages | type == "array") then
            if (.npm_packages == []) then
                empty
            else
                .npm_packages[]
            end
        elif (.npm_packages | type == "object") then
            if (.npm_packages == {}) then
                empty
            else
                .npm_packages
            end
        else
            .npm_packages
        end
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:58] TRACE: bashio::cache.get: addons.self.info
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:58] TRACE: bashio::var.has_value: .ingress_port // empty
[22:48:58] TRACE: bashio::var.has_value: 
[22:48:58] TRACE: bashio::config.has_value: init_commands
[22:48:58] TRACE: bashio::jq: {"name":"Node-RED","slug":"a0d7b954_nodered","hostname":"a0d7b954-nodered","dns":["a0d7b954-nodered.local.hass.io"],"description":"Flow-based programming for the Internet of Things","long_description":"# Home Assistant Community Add-on: Node-RED

[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]

[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]

[![Sponsor Frenck via GitHub Sponsors][github-sponsors-shield]][github-sponsors]

[![Support Frenck on Patreon][patreon-shield]][patreon]

Flow-based programming for the Internet of Things.

## About

[Node-RED][nodered] is a programming tool for wiring together hardware devices,
APIs and online services in new and interesting ways.

It provides a browser-based editor that makes it easy to wire together flows
using the wide range of nodes in the palette that can be deployed to its
runtime in a single click.

![Node-RED in the Home Assistant Frontend][screenshot]

[discord-shield]: https://img.shields.io/discord/478094546522079232.svg
[discord]: https://discord.me/hassioaddons
[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg
[forum]: https://community.home-assistant.io/t/home-assistant-community-add-on-node-red/55023?u=frenck
[github-sponsors-shield]: https://frenck.dev/wp-content/uploads/2019/12/github_sponsor.png
[github-sponsors]: https://github.com/sponsors/frenck
[maintenance-shield]: https://img.shields.io/maintenance/yes/2025.svg
[nodered]: https://nodered.org
[patreon-shield]: https://frenck.dev/wp-content/uploads/2019/12/patreon.png
[patreon]: https://www.patreon.com/frenck
[project-stage-shield]: https://img.shields.io/badge/project%20stage-production%20ready-brightgreen.svg
[release-shield]: https://img.shields.io/badge/version-v20.0.0-blue.svg
[release]: https://github.com/hassio-addons/addon-node-red/tree/v20.0.0
[screenshot]: https://github.com/hassio-addons/addon-node-red/raw/main/images/screenshot.png","advanced":false,"stage":"stable","repository":"a0d7b954","version_latest":"20.0.0","protected":true,"rating":5,"boot_config":"auto","boot":"auto","options":{"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"},"schema":[{"name":"log_level","optional":true,"type":"select","options":["trace","debug","info","notice","warning","error","fatal"]},{"name":"credential_secret","optional":true,"type":"string","format":"password"},{"name":"theme","optional":true,"type":"select","options":["default","aurora","cobalt2","dark","dracula","espresso-libre","github-dark","github-dark-default","github-dark-dimmed","midnight-red","monoindustrial","monokai","monokai-dimmed","noctis","oceanic-next","oled","one-dark-pro","one-dark-pro-darker","solarized-dark","solarized-light","tokyo-night","tokyo-night-light","tokyo-night-storm","totallyinformation","zenburn"]},{"name":"http_node","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"http_static","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"ssl","required":true,"type":"boolean"},{"name":"certfile","required":true,"type":"string"},{"name":"keyfile","required":true,"type":"string"},{"name":"system_packages","multiple":true,"required":true,"type":"string"},{"name":"npm_packages","multiple":true,"required":true,"type":"string"},{"name":"init_commands","multiple":true,"required":true,"type":"string"},{"name":"leave_front_door_open","optional":true,"type":"boolean"},{"name":"safe_mode","optional":true,"type":"boolean"},{"name":"max_old_space_size","optional":true,"type":"integer"}],"arch":["aarch64","amd64"],"machine":[],"homeassistant":"2023.3.0","url":"https://github.com/hassio-addons/addon-node-red","detached":false,"available":true,"build":false,"network":{"80/tcp":1880},"network_description":{"80/tcp":"Web interface"},"host_network":true,"host_pid":false,"host_ipc":false,"host_uts":false,"host_dbus":false,"privileged":[],"full_access":false,"apparmor":"default","icon":true,"logo":true,"changelog":true,"documentation":true,"stdin":false,"hassio_api":true,"hassio_role":"manager","auth_api":true,"homeassistant_api":true,"gpio":false,"usb":false,"uart":true,"kernel_modules":false,"devicetree":false,"udev":false,"docker_api":false,"video":false,"audio":false,"startup":"application","services":[],"discovery":[],"translations":{},"ingress":true,"signed":false,"state":"startup","webui":null,"ingress_entry":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g","ingress_url":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g/","ingress_port":64653,"ingress_panel":true,"audio_input":null,"audio_output":null,"auto_update":false,"ip_address":"172.30.32.1","version":"20.0.0","update_available":false,"watchdog":true,"devices":[],"system_managed":false,"system_managed_config_entry":null} .ingress_port // empty
[22:48:58] TRACE: bashio::config: init_commands
[22:48:58] TRACE: bashio::addon.config
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::cache.get: addons.self.options.config
[22:48:58] TRACE: bashio::cache.set: addons.self.ingress_port 64653
[22:48:58] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:58] TRACE: bashio::fs.directory_exists: /tmp/.bashio
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:58] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.init_commands == null) then
            null
        elif (.init_commands | type == "string") then
            .init_commands // empty
        elif (.init_commands | type == "boolean") then
            .init_commands // false
        elif (.init_commands | type == "array") then
            if (.init_commands == []) then
                empty
            else
                .init_commands[]
            end
        elif (.init_commands | type == "object") then
            if (.init_commands == {}) then
                empty
            else
                .init_commands
            end
        else
            .init_commands
        end
[22:48:58] TRACE: bashio::var.has_value: 
s6-rc: info: service init-customizations successfully started
s6-rc: info: service init-nodered: starting
[22:48:58] TRACE: bashio::addon.port 80
[22:48:58] TRACE: bashio::addons self addons.self.network.80-tcp .network["80/tcp"] // empty
[22:48:58] TRACE: bashio::cache.exists: addons.self.network.80-tcp
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.network.80-tcp.cache
[22:48:58] TRACE: bashio::var.false: self
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:58] TRACE: bashio::cache.get: addons.self.info
[22:48:58] TRACE: bashio::cache.exists: addons.self.info
[22:48:58] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.info.cache
[22:48:59] TRACE: bashio::var.has_value: .network["80/tcp"] // empty
[22:48:59] TRACE: bashio::jq: {"name":"Node-RED","slug":"a0d7b954_nodered","hostname":"a0d7b954-nodered","dns":["a0d7b954-nodered.local.hass.io"],"description":"Flow-based programming for the Internet of Things","long_description":"# Home Assistant Community Add-on: Node-RED

[![Release][release-shield]][release] ![Project Stage][project-stage-shield] ![Project Maintenance][maintenance-shield]

[![Discord][discord-shield]][discord] [![Community Forum][forum-shield]][forum]

[![Sponsor Frenck via GitHub Sponsors][github-sponsors-shield]][github-sponsors]

[![Support Frenck on Patreon][patreon-shield]][patreon]

Flow-based programming for the Internet of Things.

## About

[Node-RED][nodered] is a programming tool for wiring together hardware devices,
APIs and online services in new and interesting ways.

It provides a browser-based editor that makes it easy to wire together flows
using the wide range of nodes in the palette that can be deployed to its
runtime in a single click.

![Node-RED in the Home Assistant Frontend][screenshot]

[discord-shield]: https://img.shields.io/discord/478094546522079232.svg
[discord]: https://discord.me/hassioaddons
[forum-shield]: https://img.shields.io/badge/community-forum-brightgreen.svg
[forum]: https://community.home-assistant.io/t/home-assistant-community-add-on-node-red/55023?u=frenck
[github-sponsors-shield]: https://frenck.dev/wp-content/uploads/2019/12/github_sponsor.png
[github-sponsors]: https://github.com/sponsors/frenck
[maintenance-shield]: https://img.shields.io/maintenance/yes/2025.svg
[nodered]: https://nodered.org
[patreon-shield]: https://frenck.dev/wp-content/uploads/2019/12/patreon.png
[patreon]: https://www.patreon.com/frenck
[project-stage-shield]: https://img.shields.io/badge/project%20stage-production%20ready-brightgreen.svg
[release-shield]: https://img.shields.io/badge/version-v20.0.0-blue.svg
[release]: https://github.com/hassio-addons/addon-node-red/tree/v20.0.0
[screenshot]: https://github.com/hassio-addons/addon-node-red/raw/main/images/screenshot.png","advanced":false,"stage":"stable","repository":"a0d7b954","version_latest":"20.0.0","protected":true,"rating":5,"boot_config":"auto","boot":"auto","options":{"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"},"schema":[{"name":"log_level","optional":true,"type":"select","options":["trace","debug","info","notice","warning","error","fatal"]},{"name":"credential_secret","optional":true,"type":"string","format":"password"},{"name":"theme","optional":true,"type":"select","options":["default","aurora","cobalt2","dark","dracula","espresso-libre","github-dark","github-dark-default","github-dark-dimmed","midnight-red","monoindustrial","monokai","monokai-dimmed","noctis","oceanic-next","oled","one-dark-pro","one-dark-pro-darker","solarized-dark","solarized-light","tokyo-night","tokyo-night-light","tokyo-night-storm","totallyinformation","zenburn"]},{"name":"http_node","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"http_static","type":"schema","optional":true,"multiple":false,"schema":[{"name":"username","required":true,"type":"string"},{"name":"password","required":true,"type":"string","format":"password"}]},{"name":"ssl","required":true,"type":"boolean"},{"name":"certfile","required":true,"type":"string"},{"name":"keyfile","required":true,"type":"string"},{"name":"system_packages","multiple":true,"required":true,"type":"string"},{"name":"npm_packages","multiple":true,"required":true,"type":"string"},{"name":"init_commands","multiple":true,"required":true,"type":"string"},{"name":"leave_front_door_open","optional":true,"type":"boolean"},{"name":"safe_mode","optional":true,"type":"boolean"},{"name":"max_old_space_size","optional":true,"type":"integer"}],"arch":["aarch64","amd64"],"machine":[],"homeassistant":"2023.3.0","url":"https://github.com/hassio-addons/addon-node-red","detached":false,"available":true,"build":false,"network":{"80/tcp":1880},"network_description":{"80/tcp":"Web interface"},"host_network":true,"host_pid":false,"host_ipc":false,"host_uts":false,"host_dbus":false,"privileged":[],"full_access":false,"apparmor":"default","icon":true,"logo":true,"changelog":true,"documentation":true,"stdin":false,"hassio_api":true,"hassio_role":"manager","auth_api":true,"homeassistant_api":true,"gpio":false,"usb":false,"uart":true,"kernel_modules":false,"devicetree":false,"udev":false,"docker_api":false,"video":false,"audio":false,"startup":"application","services":[],"discovery":[],"translations":{},"ingress":true,"signed":false,"state":"startup","webui":null,"ingress_entry":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g","ingress_url":"/api/hassio_ingress/fcq3rmIrKdxWq60mteCsjw5CVRYNVRnfv1JJW9n125g/","ingress_port":64653,"ingress_panel":true,"audio_input":null,"audio_output":null,"auto_update":false,"ip_address":"172.30.32.1","version":"20.0.0","update_available":false,"watchdog":true,"devices":[],"system_managed":false,"system_managed_config_entry":null} .network["80/tcp"] // empty
[22:48:59] TRACE: bashio::fs.file_exists: /config/settings.js
[22:48:59] TRACE: bashio::cache.set: addons.self.network.80-tcp 1880
[22:48:59] TRACE: bashio::fs.file_exists: /config/settings.js
[22:48:59] TRACE: bashio::fs.directory_exists: /tmp/.bashio
[22:48:59] TRACE: bashio::addon.port 80
[22:48:59] TRACE: bashio::var.has_value: 1880
[22:48:59] TRACE: bashio::addons self addons.self.network.80-tcp .network["80/tcp"] // empty
[22:48:59] TRACE: bashio::config.true: ssl
[22:48:59] TRACE: bashio::cache.exists: addons.self.network.80-tcp
[22:48:59] TRACE: bashio::config: ssl
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.network.80-tcp.cache
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::cache.get: addons.self.network.80-tcp
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.network.80-tcp
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.network.80-tcp.cache
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.ssl == null) then
            null
        elif (.ssl | type == "string") then
            .ssl // empty
        elif (.ssl | type == "boolean") then
            .ssl // false
        elif (.ssl | type == "array") then
            if (.ssl == []) then
                empty
            else
                .ssl[]
            end
        elif (.ssl | type == "object") then
            if (.ssl == {}) then
                empty
            else
                .ssl
            end
        else
            .ssl
        end
[22:48:59] TRACE: bashio::var.true: false
[22:48:59] TRACE: bashio::config: certfile
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.certfile == null) then
            null
        elif (.certfile | type == "string") then
            .certfile // empty
        elif (.certfile | type == "boolean") then
            .certfile // false
        elif (.certfile | type == "array") then
            if (.certfile == []) then
                empty
            else
                .certfile[]
            end
        elif (.certfile | type == "object") then
            if (.certfile == {}) then
                empty
            else
                .certfile
            end
        else
            .certfile
        end
[22:48:59] TRACE: bashio::var.has_value: 1880
[22:48:59] TRACE: bashio::config.true: ssl
[22:48:59] TRACE: bashio::config: ssl
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::config: keyfile
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.ssl == null) then
            null
        elif (.ssl | type == "string") then
            .ssl // empty
        elif (.ssl | type == "boolean") then
            .ssl // false
        elif (.ssl | type == "array") then
            if (.ssl == []) then
                empty
            else
                .ssl[]
            end
        elif (.ssl | type == "object") then
            if (.ssl == {}) then
                empty
            else
                .ssl
            end
        else
            .ssl
        end
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.keyfile == null) then
            null
        elif (.keyfile | type == "string") then
            .keyfile // empty
        elif (.keyfile | type == "boolean") then
            .keyfile // false
        elif (.keyfile | type == "array") then
            if (.keyfile == []) then
                empty
            else
                .keyfile[]
            end
        elif (.keyfile | type == "object") then
            if (.keyfile == {}) then
                empty
            else
                .keyfile
            end
        else
            .keyfile
        end
[22:48:59] TRACE: bashio::var.true: false
[22:48:59] TRACE: bashio::config: leave_front_door_open
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::fs.file_exists: /config/package.json
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.leave_front_door_open == null) then
            null
        elif (.leave_front_door_open | type == "string") then
            .leave_front_door_open // empty
        elif (.leave_front_door_open | type == "boolean") then
            .leave_front_door_open // false
        elif (.leave_front_door_open | type == "array") then
            if (.leave_front_door_open == []) then
                empty
            else
                .leave_front_door_open[]
            end
        elif (.leave_front_door_open | type == "object") then
            if (.leave_front_door_open == {}) then
                empty
            else
                .leave_front_door_open
            end
        else
            .leave_front_door_open
        end
[22:48:59] TRACE: bashio::config: ssl
[22:48:59] TRACE: bashio::addon.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::cache.get: addons.self.options.config
[22:48:59] TRACE: bashio::cache.exists: addons.self.options.config
[22:48:59] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:48:59] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.ssl == null) then
            null
        elif (.ssl | type == "string") then
            .ssl // empty
        elif (.ssl | type == "boolean") then
            .ssl // false
        elif (.ssl | type == "array") then
            if (.ssl == []) then
                empty
            else
                .ssl[]
            end
        elif (.ssl | type == "object") then
            if (.ssl == {}) then
                empty
            else
                .ssl
            end
        else
            .ssl
        end
s6-rc: info: service init-nginx successfully started
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

up to date, audited 163 packages in 7s

19 packages are looking for funding
  run `npm fund` for details

4 vulnerabilities (2 moderate, 2 critical)

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
s6-rc: info: service init-nodered successfully started
s6-rc: info: service nodered: starting
s6-rc: info: service nodered successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service nginx successfully started
s6-rc: info: service legacy-services: starting
[22:49:07] TRACE: bashio::config.exists: max_old_space_size
[22:49:07] TRACE: bashio::config: max_old_space_size
[22:49:07] TRACE: bashio::net.wait_for 46836 localhost 300
s6-rc: info: service legacy-services successfully started
[22:49:07] TRACE: bashio::addon.config
[22:49:07] TRACE: bashio::cache.exists: addons.self.options.config
[22:49:07] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:49:07] TRACE: bashio::cache.get: addons.self.options.config
[22:49:07] TRACE: bashio::cache.exists: addons.self.options.config
[22:49:07] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:49:07] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.max_old_space_size == null) then
            null
        elif (.max_old_space_size | type == "string") then
            .max_old_space_size // empty
        elif (.max_old_space_size | type == "boolean") then
            .max_old_space_size // false
        elif (.max_old_space_size | type == "array") then
            if (.max_old_space_size == []) then
                empty
            else
                .max_old_space_size[]
            end
        elif (.max_old_space_size | type == "object") then
            if (.max_old_space_size == {}) then
                empty
            else
                .max_old_space_size
            end
        else
            .max_old_space_size
        end
[22:49:07] TRACE: bashio::config.true: safe_mode
[22:49:07] TRACE: bashio::config: safe_mode
[22:49:07] TRACE: bashio::addon.config
[22:49:07] TRACE: bashio::cache.exists: addons.self.options.config
[22:49:07] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:49:07] TRACE: bashio::cache.get: addons.self.options.config
[22:49:07] TRACE: bashio::cache.exists: addons.self.options.config
[22:49:07] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[22:49:07] TRACE: bashio::jq: {"theme":"default","http_node":{"username":"","password":""},"http_static":{"username":"","password":""},"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","system_packages":[],"npm_packages":[],"init_commands":[],"log_level":"trace"} if (.safe_mode == null) then
            null
        elif (.safe_mode | type == "string") then
            .safe_mode // empty
        elif (.safe_mode | type == "boolean") then
            .safe_mode // false
        elif (.safe_mode | type == "array") then
            if (.safe_mode == []) then
                empty
            else
                .safe_mode[]
            end
        elif (.safe_mode | type == "object") then
            if (.safe_mode == {}) then
                empty
            else
                .safe_mode
            end
        else
            .safe_mode
        end
[22:49:07] TRACE: bashio::var.true: null
[22:49:07] INFO: [32mStarting Node-RED...[0m
npm warn Unknown builtin config "globalignorefile". This will stop working in the next major version of npm.
npm warn Unknown builtin config "python". This will stop working in the next major version of npm.

> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js

7 Nov 22:49:10 - [info] 

Welcome to Node-RED
===================

7 Nov 22:49:10 - [info] Node-RED version: v4.0.9
7 Nov 22:49:10 - [info] Node.js  version: v22.16.0
7 Nov 22:49:10 - [info] Linux 6.12.51-haos arm64 LE
7 Nov 22:49:11 - [info] Loading palette nodes
7 Nov 22:49:12 - [debug] Module: node-red-contrib-alexa-home-skill 0.1.19 /config/node_modules/node-red-contrib-alexa-home-skill
7 Nov 22:49:12 - [debug] Module: @node-red-contrib-themes/theme-collection 4.0.11 /opt/node_modules/@node-red-contrib-themes/theme-collection
7 Nov 22:49:12 - [debug] Module: node-red-contrib-bigtimer 2.8.6 /opt/node_modules/node-red-contrib-bigtimer
7 Nov 22:49:12 - [debug] Module: node-red-contrib-cast 0.2.17 /opt/node_modules/node-red-contrib-cast
7 Nov 22:49:12 - [debug] Module: node-red-contrib-counter 0.1.6 /opt/node_modules/node-red-contrib-counter
7 Nov 22:49:12 - [debug] Module: node-red-contrib-home-assistant-websocket 0.77.1 /opt/node_modules/node-red-contrib-home-assistant-websocket
7 Nov 22:49:12 - [debug] Module: node-red-contrib-influxdb 0.7.0 /opt/node_modules/node-red-contrib-influxdb
7 Nov 22:49:12 - [debug] Module: node-red-contrib-interval-length 0.0.6 /opt/node_modules/node-red-contrib-interval-length
7 Nov 22:49:12 - [debug] Module: node-red-contrib-modbus 5.43.0 /opt/node_modules/node-red-contrib-modbus
7 Nov 22:49:12 - [debug] Module: node-red-contrib-moment 5.0.0 /opt/node_modules/node-red-contrib-moment
7 Nov 22:49:12 - [debug] Module: node-red-contrib-persistent-fsm 1.2.1 /opt/node_modules/node-red-contrib-persistent-fsm
7 Nov 22:49:12 - [debug] Module: node-red-contrib-sunevents 3.1.1 /opt/node_modules/node-red-contrib-sunevents
7 Nov 22:49:12 - [debug] Module: node-red-contrib-time-range-switch 1.2.0 /opt/node_modules/node-red-contrib-time-range-switch
7 Nov 22:49:12 - [debug] Module: node-red-dashboard 3.6.5 /opt/node_modules/node-red-dashboard
7 Nov 22:49:12 - [debug] Module: node-red-node-base64 1.0.0 /opt/node_modules/node-red-node-base64
7 Nov 22:49:12 - [debug] Module: node-red-node-email 3.0.3 /opt/node_modules/node-red-node-email
7 Nov 22:49:12 - [debug] Module: node-red-node-feedparser 0.3.0 /opt/node_modules/node-red-node-feedparser
7 Nov 22:49:12 - [debug] Module: node-red-node-ping 0.3.3 /opt/node_modules/node-red-node-ping
7 Nov 22:49:12 - [debug] Module: node-red-node-random 0.4.1 /opt/node_modules/node-red-node-random
7 Nov 22:49:12 - [debug] Module: node-red-node-serialport 2.0.3 /opt/node_modules/node-red-node-serialport
7 Nov 22:49:12 - [debug] Module: node-red-node-smooth 0.1.2 /opt/node_modules/node-red-node-smooth
7 Nov 22:49:12 - [debug] Module: node-red-node-suncalc 1.2.0 /opt/node_modules/node-red-node-suncalc
7 Nov 22:49:12 - [debug] Module: node-red-node-twitter 1.2.0 /opt/node_modules/node-red-node-twitter
7 Nov 22:49:12 - [info] Node-RED Contrib Theme Collection version: v4.0.11
7 Nov 22:49:18 - [info] Dashboard version 3.6.5 started at /endpoint/ui
7 Nov 22:49:20 - [info] node-red-contrib-home-assistant-websocket v0.77.1 nodes initialized
7 Nov 22:49:21 - [info] Settings file  : /etc/node-red/config.js
7 Nov 22:49:21 - [info] Context store  : 'default' [module=memory]
7 Nov 22:49:21 - [info] User directory : /config/
7 Nov 22:49:21 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Nov 22:49:21 - [info] Flows file     : /config/flows.json
7 Nov 22:49:21 - [info] Server now running at http://127.0.0.1:46836/
7 Nov 22:49:21 - [debug] loaded flow revision: 9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388
7 Nov 22:49:21 - [debug] red/runtime/nodes/credentials.load : no user key present
7 Nov 22:49:21 - [debug] red/runtime/nodes/credentials.load : using default key
7 Nov 22:49:21 - [debug] red/runtime/nodes/credentials.load : keyType=system
7 Nov 22:49:21 - [warn] 

---------------------------------------------------------------------
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.

You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------

7 Nov 22:49:21 - [trace] runtime event: {"id":"runtime-state","retain":true}
7 Nov 22:49:21 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388"},"retain":true}
7 Nov 22:49:21 - [info] Starting flows
7 Nov 22:49:21 - [debug] red/nodes/flows.start : starting flow : global
7 Nov 22:49:21 - [debug] red/nodes/flows.start : starting flow : e8af4a0670769295
7 Nov 22:49:21 - [trace] [flow:global] start flow [global]
7 Nov 22:49:21 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] [flow:global]  id               | type         | alias
7 Nov 22:49:21 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] [flow:global]  a293fdb4.ea051   | server       | 
7 Nov 22:49:21 - [trace] [flow:global]  f5138830dea2ac04 | alexa-home-conf | 
7 Nov 22:49:21 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295] start flow [e8af4a0670769295]
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295]  id               | type         | alias
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295]  21ef2b0f388d0ffe | alexa-home   | 
7 Nov 22:49:21 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:49:21 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"start"},"retain":true}
7 Nov 22:49:21 - [info] Started flows
[22:49:21] INFO: [32mStarting NGinx...[0m
7 Nov 22:49:22 - [trace] comms.open NbMQsblfrxeSEdvOGlXGvH2IOlCGzkVl0r0O64Qf+7w=
7 Nov 22:49:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 22:49:26 - [info] [server:Home Assistant] Connected to http://supervisor/core
7 Nov 22:49:26 - [debug] [server:Home Assistant] States Loaded
7 Nov 22:49:26 - [debug] [server:Home Assistant] Services Loaded
7 Nov 22:49:26 - [debug] [server:Home Assistant] HA State: running
7 Nov 22:49:26 - [debug] [server:Home Assistant] Integration: notloaded
7 Nov 22:49:26 - [debug] [server:Home Assistant] Registries Loaded
7 Nov 22:49:28 - [trace] comms.close NbMQsblfrxeSEdvOGlXGvH2IOlCGzkVl0r0O64Qf+7w=
7 Nov 22:49:30 - [trace] comms.open wOYxyBn5wbUpiUXgJDC8JvZOBCj46Apy7tRyUhnLUgg=
7 Nov 22:50:49 - [trace] utils.writeFile - copied /config/flows.json TO /config/.flows.json.backup
7 Nov 22:50:49 - [trace] utils.writeFile - written content to /config/flows.json.$$$
7 Nov 22:50:49 - [trace] utils.writeFile - renamed /config/flows.json.$$$ to /config/flows.json
7 Nov 22:50:49 - [debug] saved flow revision: ce0ec78a4a92358df067162e3b8eb5e9bbf5a1a37363eafb14ffb7c7251fb304
7 Nov 22:50:49 - [info] Stopping flows
7 Nov 22:50:49 - [debug] red/nodes/flows.stop : stopping flow : e8af4a0670769295
7 Nov 22:50:49 - [trace] [flow:e8af4a0670769295] stop flow
7 Nov 22:50:49 - [trace] Stopping node alexa-home:21ef2b0f388d0ffe
7 Nov 22:50:49 - [debug] red/nodes/flows.stop : stopping flow : global
7 Nov 22:50:49 - [trace] [flow:global] stop flow
7 Nov 22:50:49 - [trace] Stopping node server:a293fdb4.ea051
7 Nov 22:50:49 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
7 Nov 22:50:49 - [trace] Stopping node alexa-home-conf:f5138830dea2ac04
7 Nov 22:50:49 - [trace] Stopped node alexa-home-conf:f5138830dea2ac04 (3ms)
7 Nov 22:50:49 - [trace] Stopped node alexa-home:21ef2b0f388d0ffe (20ms)
7 Nov 22:50:49 - [trace] Stopped node server:a293fdb4.ea051 (15ms)
7 Nov 22:50:49 - [info] Stopped flows
7 Nov 22:50:49 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"stop","deploy":true},"retain":true}
7 Nov 22:50:50 - [info] Updated flows
7 Nov 22:50:50 - [info] Starting flows
7 Nov 22:50:50 - [debug] red/nodes/flows.start : starting flow : global
7 Nov 22:50:50 - [debug] red/nodes/flows.start : starting flow : e8af4a0670769295
7 Nov 22:50:50 - [trace] [flow:global] start flow [global]
7 Nov 22:50:50 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:50:50 - [trace] [flow:global]  id               | type         | alias
7 Nov 22:50:50 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:50:50 - [trace] [flow:global]  a293fdb4.ea051   | server       | 
7 Nov 22:50:50 - [trace] [flow:global]  f5138830dea2ac04 | alexa-home-conf | 
7 Nov 22:50:50 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:50:50 - [trace] [flow:e8af4a0670769295] start flow [e8af4a0670769295]
7 Nov 22:50:50 - [error] [alexa-home:21ef2b0f388d0ffe] TypeError: Cannot read properties of null (reading 'register')
7 Nov 22:50:50 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"start","deploy":true},"retain":true}
7 Nov 22:50:50 - [info] Started flows
7 Nov 22:50:50 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"ce0ec78a4a92358df067162e3b8eb5e9bbf5a1a37363eafb14ffb7c7251fb304"},"retain":true}
7 Nov 22:50:55 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 22:50:55 - [info] [server:Home Assistant] Connected to http://supervisor/core
7 Nov 22:50:55 - [debug] [server:Home Assistant] States Loaded
7 Nov 22:50:55 - [debug] [server:Home Assistant] Services Loaded
7 Nov 22:50:55 - [debug] [server:Home Assistant] HA State: running
7 Nov 22:50:55 - [debug] [server:Home Assistant] Integration: notloaded
7 Nov 22:50:55 - [debug] [server:Home Assistant] Registries Loaded
7 Nov 22:51:57 - [trace] utils.writeFile - copied /config/flows.json TO /config/.flows.json.backup
7 Nov 22:51:57 - [trace] utils.writeFile - written content to /config/flows.json.$$$
7 Nov 22:51:57 - [trace] utils.writeFile - renamed /config/flows.json.$$$ to /config/flows.json
7 Nov 22:51:57 - [debug] saved flow revision: 9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388
7 Nov 22:51:57 - [info] Stopping flows
7 Nov 22:51:57 - [debug] red/nodes/flows.stop : stopping flow : e8af4a0670769295
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295] stop flow
7 Nov 22:51:57 - [debug] red/nodes/flows.stop : stopping flow : global
7 Nov 22:51:57 - [trace] [flow:global] stop flow
7 Nov 22:51:57 - [trace] Stopping node server:a293fdb4.ea051
7 Nov 22:51:57 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
7 Nov 22:51:57 - [trace] Stopping node alexa-home-conf:f5138830dea2ac04
7 Nov 22:51:57 - [trace] Stopped node alexa-home-conf:f5138830dea2ac04 (0ms)
7 Nov 22:51:57 - [trace] Stopped node server:a293fdb4.ea051 (4ms)
7 Nov 22:51:57 - [info] Stopped flows
7 Nov 22:51:57 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"stop","deploy":true},"retain":true}
7 Nov 22:51:57 - [info] Updated flows
7 Nov 22:51:57 - [info] Starting flows
7 Nov 22:51:57 - [debug] red/nodes/flows.start : starting flow : global
7 Nov 22:51:57 - [debug] red/nodes/flows.start : starting flow : e8af4a0670769295
7 Nov 22:51:57 - [trace] [flow:global] start flow [global]
7 Nov 22:51:57 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] [flow:global]  id               | type         | alias
7 Nov 22:51:57 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] [flow:global]  a293fdb4.ea051   | server       | 
7 Nov 22:51:57 - [trace] [flow:global]  f5138830dea2ac04 | alexa-home-conf | 
7 Nov 22:51:57 - [trace] [flow:global] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295] start flow [e8af4a0670769295]
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295]  id               | type         | alias
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295]  21ef2b0f388d0ffe | alexa-home   | 
7 Nov 22:51:57 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
7 Nov 22:51:57 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"start","deploy":true},"retain":true}
7 Nov 22:51:57 - [info] Started flows
7 Nov 22:51:57 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388"},"retain":true}
7 Nov 22:52:02 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 22:52:02 - [info] [server:Home Assistant] Connected to http://supervisor/core
7 Nov 22:52:02 - [debug] [server:Home Assistant] States Loaded
7 Nov 22:52:02 - [debug] [server:Home Assistant] Services Loaded
7 Nov 22:52:03 - [debug] [server:Home Assistant] HA State: running
7 Nov 22:52:03 - [debug] [server:Home Assistant] Integration: notloaded
7 Nov 22:52:03 - [debug] [server:Home Assistant] Registries Loaded

[hardillb]

First, please trim the logs down to just a single Node-RED restart, masses of logs like this really are not helpful, just show the single start where you have done the thing I asked for

But there are 2 useful things here.

1. you need to deploy the config node before the refresh button will work. When you hit update on the diaglog where you enter the username/password it will send it to the backend once to be able to get the device list, but the refresh button depends on you actually deploying the changes to have access to the username/password.

   Can't refresh until deployed
   Can't refresh until deployed
   Can't refresh until deployed
   Can't refresh until deployed
   Can't refresh until deployed
   Can't refresh until deployed
   Can't refresh until deployed
   

2. The Browser Console shows "problem getting devices" but that is probably related to the first point, but as mentioned this is most likely linked to you not deploying the flow.

So pick the username/password that has the live device, input this in the config node (make sure there is only one, not one for each username/password). Deploy the flow, then open the device node again an press the refresh button.

[mevton123]

First, noted. Here is only a little bit of the log from this morning. I have opened Node-red, deployed, then opened the device node again and hit the refresh button. These refreshes are being noted on the browser console, but not the node-red log.

7 Nov 23:03:34 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
7 Nov 23:05:10 - [info] [server:Home Assistant] Connecting to http://supervisor/core
7 Nov 23:05:10 - [info] [server:Home Assistant] Connected to http://supervisor/core
7 Nov 23:05:10 - [debug] [server:Home Assistant] States Loaded
7 Nov 23:05:10 - [debug] [server:Home Assistant] HA State: running
7 Nov 23:05:10 - [debug] [server:Home Assistant] Integration: notloaded
7 Nov 23:05:10 - [debug] [server:Home Assistant] Services Loaded
7 Nov 23:05:16 - [trace] comms.open jAHc1sCCheQcBA1hlbTelF/PSsSrXIOm7/i+TVoraB4=
7 Nov 23:22:12 - [trace] comms.close jAHc1sCCheQcBA1hlbTelF/PSsSrXIOm7/i+TVoraB4=
8 Nov 06:25:45 - [trace] comms.open gjfgwrtv/avImtEs9wsJZWxk4tH6j0ByjivTEjTqSb8=
8 Nov 06:25:53 - [trace] comms.open joBrhUaSPr/Xd73xdAg1d0XAuShvN4GSvJj9sGIVyuU=
8 Nov 06:25:59 - [trace] comms.close joBrhUaSPr/Xd73xdAg1d0XAuShvN4GSvJj9sGIVyuU=
8 Nov 06:26:37 - [debug] loaded flow revision: 9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388
8 Nov 06:26:37 - [debug] red/runtime/nodes/credentials.load : no user key present
8 Nov 06:26:37 - [debug] red/runtime/nodes/credentials.load : using default key
8 Nov 06:26:37 - [debug] red/runtime/nodes/credentials.load : keyType=system
8 Nov 06:26:37 - [warn] 
---------------------------------------------------------------------
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.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
8 Nov 06:26:37 - [trace] runtime event: {"id":"runtime-state","retain":true}
8 Nov 06:26:37 - [info] Stopping flows
8 Nov 06:26:37 - [debug] red/nodes/flows.stop : stopping flow : e8af4a0670769295
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295] stop flow
8 Nov 06:26:37 - [trace] Stopping node alexa-home:21ef2b0f388d0ffe
8 Nov 06:26:37 - [debug] red/nodes/flows.stop : stopping flow : global
8 Nov 06:26:37 - [trace] [flow:global] stop flow
8 Nov 06:26:37 - [trace] Stopping node server:a293fdb4.ea051
8 Nov 06:26:37 - [info] [server:Home Assistant] Closing connection to http://supervisor/core
8 Nov 06:26:37 - [trace] Stopping node alexa-home-conf:f5138830dea2ac04
8 Nov 06:26:37 - [trace] Stopped node alexa-home-conf:f5138830dea2ac04 (2ms)
8 Nov 06:26:37 - [trace] Stopped node alexa-home:21ef2b0f388d0ffe (11ms)
8 Nov 06:26:37 - [trace] Stopped node server:a293fdb4.ea051 (8ms)
8 Nov 06:26:37 - [info] Stopped flows
8 Nov 06:26:37 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"stop","deploy":true},"retain":true}
8 Nov 06:26:37 - [info] Starting flows
8 Nov 06:26:37 - [debug] red/nodes/flows.start : starting flow : global
8 Nov 06:26:37 - [debug] red/nodes/flows.start : starting flow : e8af4a0670769295
8 Nov 06:26:37 - [trace] [flow:global] start flow [global]
8 Nov 06:26:37 - [trace] [flow:global] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] [flow:global]  id               | type         | alias
8 Nov 06:26:37 - [trace] [flow:global] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] [flow:global]  a293fdb4.ea051   | server       | 
8 Nov 06:26:37 - [trace] [flow:global]  f5138830dea2ac04 | alexa-home-conf | 
8 Nov 06:26:37 - [trace] [flow:global] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295] start flow [e8af4a0670769295]
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295]  id               | type         | alias
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295]  21ef2b0f388d0ffe | alexa-home   | 
8 Nov 06:26:37 - [trace] [flow:e8af4a0670769295] ------------------|--------------|-----------------
8 Nov 06:26:37 - [trace] runtime event: {"id":"runtime-state","payload":{"state":"start","deploy":true},"retain":true}
8 Nov 06:26:37 - [info] Started flows
8 Nov 06:26:37 - [trace] runtime event: {"id":"runtime-deploy","payload":{"revision":"9abec401043e8755bc302f9300b37d757fd5c2fe375c3af39c4d15232ac0b388"},"retain":true}
8 Nov 06:26:42 - [info] [server:Home Assistant] Connecting to http://supervisor/core
8 Nov 06:26:42 - [info] [server:Home Assistant] Connected to http://supervisor/core
8 Nov 06:26:42 - [debug] [server:Home Assistant] States Loaded
8 Nov 06:26:42 - [debug] [server:Home Assistant] Services Loaded
8 Nov 06:26:42 - [debug] [server:Home Assistant] HA State: running
8 Nov 06:26:42 - [debug] [server:Home Assistant] Integration: notloaded
8 Nov 06:26:42 - [debug] [server:Home Assistant] Registries Loaded
8 Nov 06:46:57 - [trace] comms.open VJwQ5ForuyHX0qaOGTtLtyIiQF7aXp/5LzKwrMbT4UI=```

[hardillb]

OK, finally got round to looking at the package.json you sent, it's not what I was expecting, it appears to be the one used to install Node-RED, not the one with the list of packages you have installed.

It appears that they have moved everything round and the one I need is in /config not /data

It would be useful to see the entries in the network tab in the browser developer tools to see what address and error are generated.

e.g. load the editor, open the node, clear the both the console and the network area (this is done by clicking on the crossed out circle in the top left of both sections).

Then click the refresh

It will look a little like this:

There will be 2 entries in the network section, please take screen shots of both the headers tab and the response tab for both entries

The first will be a POST and the second a GET

[hardillb]

But I also want to point out that the only entries in the logs are from curl, not from the Node-RED node.

[mevton123]

package (1).json

package-lock (1).json

But I also want to point out that the only entries in the logs are from curl, not from the Node-RED node.

I've set the log level to trace and am retrieving the logs from the Node-Red addon, is there somewhere else I need to look for logs to get more detail for you?

[hardillb]

The comment was about the logs on the backend server, not something you can change, and turn the Node-RED logging back down, it just generates more stuff that is not useful.

The only other thing to try is to edit the file at /config/node-modules/node-red-contrib-alexa-home-skill/alexa.js inside the container, I don't know what command line editing tools are available in the HA NR container, but hopefully vi is.

On line 327 there is a commented out console.log line. Remove the // from the start of that line and restart Node-RED, it should log errors it has trying to reach backend to get the device list

[mevton123]

done. now getting err: AggregateError when I click refresh

[hardillb]

Add and 2 extra lines after the original that is as follows

console.log(err)
console.log(err.cause)

And let me know the full output, thanks

[hardillb]

Please add a third line

console.log(err.errors)

[mevton123]

AggregateError: 
    at internalConnectMultiple (node:net:1139:18)
    at internalConnectMultiple (node:net:1215:5)
    at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
    at listOnTimeout (node:internal/timers:590:11)
    at processTimers (node:internal/timers:523:7) {
  code: 'ETIMEDOUT',
  [errors]: [
    Error: connect ETIMEDOUT 34.253.228.78:443
        at createConnectionError (node:net:1677:14)
        at Timeout.internalConnectMultipleTimeout (node:net:1736:38)
        at listOnTimeout (node:internal/timers:590:11)
        at processTimers (node:internal/timers:523:7) {
      errno: -110,
      code: 'ETIMEDOUT',
      syscall: 'connect',
      address: '34.253.228.78',
      port: 443
    },
    Error: connect ENETUNREACH 2a05:d018:8c4:3201:34e4:429d:e434:22f:443 - Local (:::0)
        at internalConnectMultiple (node:net:1211:16)
        at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
        at listOnTimeout (node:internal/timers:590:11)
        at processTimers (node:internal/timers:523:7) {
      errno: -101,
      code: 'ENETUNREACH',
      syscall: 'connect',
      address: '2a05:d018:8c4:3201:34e4:429d:e434:22f',
      port: 443
    }
  ]
}
undefined
[
  Error: connect ETIMEDOUT 34.253.228.78:443
      at createConnectionError (node:net:1677:14)
      at Timeout.internalConnectMultipleTimeout (node:net:1736:38)
      at listOnTimeout (node:internal/timers:590:11)
      at processTimers (node:internal/timers:523:7) {
    errno: -110,
    code: 'ETIMEDOUT',
    syscall: 'connect',
    address: '34.253.228.78',
    port: 443
  },
  Error: connect ENETUNREACH 2a05:d018:8c4:3201:34e4:429d:e434:22f:443 - Local (:::0)
      at internalConnectMultiple (node:net:1211:16)
      at Timeout.internalConnectMultipleTimeout (node:net:1741:5)
      at listOnTimeout (node:internal/timers:590:11)
      at processTimers (node:internal/timers:523:7) {
    errno: -101,
    code: 'ENETUNREACH',
    syscall: 'connect',
    address: '2a05:d018:8c4:3201:34e4:429d:e434:22f',
    port: 443
  }
]```

[hardillb]

OK, that explains things.

The NodeJS app can not reach the server, the IPv4 and IPv6 addresses are correct, so it has resolved the hostname to it's IP addresses but is failing to connect. Do you have a working IPv6 connection (I'm guessing not as that is showing unreachable)?

What is strange is that curl inside the same container can which doesn't really make any sense.

Do you have a home proxy enabled or something like Pi Hole (though that is unlikely as the addresses are correctly resolved)

But this is now beyond what I can help with, you will need to try and ask the Home Assistant NR folk for help here. Feel free to point them at this issue for context, but this is 100% not a problem with my node/service at this point.

Best guess is there is a firewall somewhere that is dropping the packets, but it's not on my end.

[mevton123]

Success. New Router, defaulted to IPv6 disabled. Turned it on and everything is working! Thanks mate.