Node red läuft nicht

Allgemein
1

Hallo zusammen

ich finde keinen call service oder anderes
Domain
Service
Area
Device

bleibt leer

was ist hier los

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.6
 You are running the latest version of this add-on.
 System: Home Assistant OS 11.5  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2024.2.1
 Home Assistant Supervisor: 2024.01.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 141 packages in 10s

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

13 vulnerabilities (2 low, 6 high, 5 critical)

To address all issues possible (including breaking changes), run:
  npm audit fix --force

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

Run `npm audit` for details.
npm notice 
npm notice New minor version of npm available! 10.2.3 -> 10.4.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v10.4.0>
npm notice Run `npm install -g npm@10.4.0` to update!
npm notice 
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:31:30] INFO: Starting Node-RED...

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

11 Feb 13:31:35 - [info] 

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

11 Feb 13:31:35 - [info] Node-RED version: v3.1.5
11 Feb 13:31:35 - [info] Node.js  version: v18.19.0
11 Feb 13:31:35 - [info] Linux 6.1.63-haos-raspi arm64 LE
11 Feb 13:31:36 - [info] Loading palette nodes
11 Feb 13:31:38 - [info] Node-RED Contrib Theme Collection version: v3.1.9
11 Feb 13:31:43 - [info] Dashboard version 3.6.2 started at /endpoint/ui
11 Feb 13:31:45 - [info] Settings file  : /etc/node-red/config.js
11 Feb 13:31:45 - [info] Context store  : 'default' [module=memory]
11 Feb 13:31:45 - [info] User directory : /config/
11 Feb 13:31:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
11 Feb 13:31:45 - [info] Flows file     : /config/flows.json
11 Feb 13:31:45 - [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.
---------------------------------------------------------------------

11 Feb 13:31:45 - [warn] Encrypted credentials not found
11 Feb 13:31:45 - [info] Server now running at http://127.0.0.1:46836/
11 Feb 13:31:45 - [info] Starting flows
11 Feb 13:31:45 - [info] Started flows
[13:31:45] INFO: Starting NGinx...
11 Feb 13:31:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
11 Feb 13:31:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
2

Hast Du was gemacht (Update o.ä.)?

Hast Du mal probiert ein Backup (Partiell nur Node-Red) von vor dem Problem einzuspielen?

HA incl. Hardware mal komplett neu gestartet?

Wie sieht Deine “Konfigurations-Nodes” aus, hast Du da evtl. jede Menge “fremder” Server drin?

3

Ich habe nix gemacht ich weiß auch nicht ob es über Haupt Mal ging wollte mich jetzt Mal näher mit dem Add on beschäftigen und es läuft nicht

Wenn ich es deinstalliere und neu installiere hat das Addon alle erstellen Flows noch drauf muss ich mehr löschen

Es ist nur der Home Assistent Server drin

4

Ja
Hast du das Samba Addon installiert?
Dann geh mal im Explorer auf \\192.168.133.6\addon_configs und lösch da den Ordner a0d7b954_nodered (Die IP natürlich durch die von deinem HA ersetzen.)

Mit dem File Editor kommt man meines Wissens nicht in den Ordner addon_configs.

LG
Tobi

5

Da komme ich auch nicht hin sehe ich nicht über Samba

6

Ich komme an den Ordner nur über Finder auf mein MacBook mit SMB.
Aber über das Terminal müsste es doch gehen, oder?

7

Addon ist Installiert, eingerichtet und gestartet?

Also so wie ich geschrieben habe nur das du Finder(Mac) nutzt und ich Explorer(Windows).

Kann sein, macht die Sache aber glaube ich nicht grad einfacher.

8

Ja das Samba Addon läuft muss ich den Ordner freigeben?