hassio-addons / addon-node-red

Node-RED - Home Assistant Community Add-ons
https://addons.community
MIT License
513 stars 117 forks source link

[info] [server:Home Assistant] Connecting to http://supervisor/core #1886

Open hoebanx opened 4 weeks ago

hoebanx commented 4 weeks ago

Problem/Motivation

I dont have any entry in node-red in my home assistant

Expected behavior

get my entities available

Actual behavior

logs shows only '[server:Home Assistant] Connecting to http://supervisor/core' again and again

Steps to reproduce

no idea, I tried with a friend, it is working well on his HA

Proposed changes

2024-05-31 17_03_20-Home Assistant 2024-05-31 17_04_26-10CS-0021683 Structure  - PDF-XChange Editor 2024-05-31 17_04_38-Home Assistant 2024-05-31 17_05_42-Home Assistant

hoebanx commented 3 weeks ago

for info:

Core 2024.5.5 Supervisor 2024.05.1 Operating System 12.3 Frontend 20240501.1 Node-RED Companion v4.0.0 Node-RED Current version: 17.0.12 -> 17.0.13

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


Add-on: Node-RED Flow-based programming for the Internet of Things

Add-on version: 17.0.13 You are running the latest version of this add-on. System: Home Assistant OS 12.3 (amd64 / generic-x86-64) Home Assistant Core: 2024.5.5 Home Assistant Supervisor: 2024.05.1

Please, share the above information when looking for help or support in, e.g., GitHub, forums or the Discord chat.

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

up to date, audited 1 package in 380ms

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 [14:03:00] INFO: Starting Node-RED... s6-rc: info: service legacy-services successfully started

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

4 Jun 14:03:00 - [info]

Welcome to Node-RED

4 Jun 14:03:00 - [info] Node-RED version: v3.1.9 4 Jun 14:03:00 - [info] Node.js version: v18.20.3 4 Jun 14:03:00 - [info] Linux 6.6.29-haos x64 LE 4 Jun 14:03:00 - [info] Loading palette nodes 4 Jun 14:03:00 - [info] Node-RED Contrib Theme Collection version: v3.1.11 4 Jun 14:03:01 - [info] Dashboard version 3.6.5 started at /endpoint/ui 4 Jun 14:03:01 - [info] Settings file : /etc/node-red/config.js 4 Jun 14:03:01 - [info] Context store : 'default' [module=memory] 4 Jun 14:03:01 - [info] User directory : /config/ 4 Jun 14:03:01 - [warn] Projects disabled : editorTheme.projects.enabled=false 4 Jun 14:03:01 - [info] Flows file : /config/flows.json 4 Jun 14:03:01 - [info] Server now running at http://127.0.0.1:46836/ 4 Jun 14:03:01 - [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.

4 Jun 14:03:01 - [info] Starting flows 4 Jun 14:03:01 - [info] Started flows [14:03:02] INFO: Starting NGinx... 4 Jun 14:03:06 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:11 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:16 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:22 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:27 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core 4 Jun 14:03:37 - [info] [server:Home Assistant] Connecting to http://supervisor/core

olibos commented 1 week ago

I've tried to help @hoebanx without success. Do you need more information to diagnose this issue?