ich nutze jetzt Home Assistant seit ca 1 Jahr und bin eigentlich sehr zufrieden auch funktionierte immer die Node-Red Integration aber jetzt geht auf einmal nix mehr sämtliche Dinge die ich in Node-Red gemacht habe scheinen keine Verbindung mehr zu Home Assistant haben auch wenn ich eine neue Automation in Node-Red schreiben will bekomme ich keine Vorschläge mehr also ob die Verbindung zwischen Node-Red und Home Assistant nicht mehr funktioniert, ich habe alles mögliche ausprobiert bin dann nach viel suchen auf einen Tipp getroffen das bei Home Assistant die Rest API vielleicht nicht funktioniert. ich habe jetzt versucht die Rest API zu testen das hat zumindest nicht funktioniert, ich habe mit dem Curl Befehl versucht wie im bespiel unter Home Assistant die Info dazu beschreibt, vor zu gehen, das war leider nicht von Erfolg gekrönt, immer Antwort 404. deshalb beführchte ich das es an der Rest API liegt aber wie kann ich dies wieder grade biegen ?
hast du mal in die Logs geschaut? Müsste unter Addons → Note Red → Protokolle zu finden sein.
Ich habe auch angefangen wie du, meine Automation in Node Red anfangs implementiert bin aber um nicht früher oder später auf Probleme zu stoßen auf die Automationen von HA gewechselt.
Ich habe dann angefangen immer Stück für Stück das ganze abzulösen, was erstaunlicher weise sehr schnell ging.
Aber logs vom Addon wären hilfreich um zu schauen wo das Problem liegt.
Ja ich weiß das ein Protokoll sehr hilfreich wäre aber ich habe leider schon soviel probiert und gemacht das ich den Anfang nicht mehr finde, ich weiß auch nicht ob es Sinn macht Node-Red neu zu installieren und ob ich die einzelnen Flows alle sichern kann oder ob ich mir beim Import den Fehler wieder rein hole.
Ich mache eigentlich fast von Anfang an, alles mit NR und bin auch bis vor ungefähr 8 Wochen extrem zufrieden gewesen.
Angefangen hat es mit einem Update der “websocket”-node in NR, die Probleme gemacht hat (findest Du hier im Forum einen ausführlichen Thread zu), als das dann durch den Entwickler gefixed war, gab es das Supervisor-Update von HA (auch mit vielen Problemen bei Integrationen und Add-Ons). Auch hier wurden die meisten Probleme gefixed, aber leider ist ein Thema mit NR bei mir übrig geblieben:
Jeden Abend gegen 18:25 Uhr trennt der Supervisor die Verbindung zu NR was zu unterstehenden Fehlermeldungen führt. Die Wiederherstellung der Verbindung geht oft sehr schnell, manchmal dauert es bis zu 30 Minuten, wenn ich vorher NR nicht neu starte (was gelegentlich auch automatisch passiert).
Das alles ist sehr ärgerlich, zumal @frenck von HA NR doch etwas stiefmütterlich betreut.
Bisher sind die Probleme aber noch nicht so groß, dass ich mit meinen sehr umfangreichen NR-Flows (>1.100 nodes) zu der doch recht unübersichtlichen HA-Automation Wechsel möchte.
Hier noch die Log’s aus dem Supervisor:
2024-12-16 18:18:53.842 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-12-16 18:27:33.870 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:27:33.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:28:35.453 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2024-12-16 18:28:35.578 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2024-12-16 18:28:35.580 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
2024-12-16 18:30:00.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:30:00.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:30:33.712 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2024-12-16 18:30:33.831 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2024-12-16 18:30:33.833 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
2024-12-16 18:31:56.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:31:56.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:32:33.027 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2024-12-16 18:32:33.206 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2024-12-16 18:32:33.208 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
2024-12-16 18:37:28.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:37:28.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:40:26.463 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2024-12-16 18:40:26.590 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2024-12-16 18:40:26.592 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
2024-12-16 18:41:47.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:41:47.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:42:14.031 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
2024-12-16 18:42:14.148 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
2024-12-16 18:42:14.149 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
2024-12-16 18:48:53.925 INFO (MainThread) [supervisor.homeassistant.api] Updated Home Assistant API token
2024-12-16 18:48:59.870 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API error: Cannot proxy websocket message of unsupported type: 258
2024-12-16 18:48:59.871 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API for a0d7b954_nodered closed
2024-12-16 18:50:31.685 WARNING (MainThread) [supervisor.addons.addon] Watchdog found addon Node-RED is failed, restarting...
2024-12-16 18:50:31.688 INFO (SyncWorker_0) [supervisor.docker.manager] Cleaning addon_a0d7b954_nodered application
2024-12-16 18:50:32.140 INFO (MainThread) [supervisor.docker.addon] Starting Docker add-on ghcr.io/hassio-addons/node-red/amd64 with version 18.1.1
und hier aus NR:
16 Dec 18:28:30 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
16 Dec 18:28:30 - [error] [api-call-service:AUS] Error: Unrecognized error: {"type":"result","success":false,"error":{"code":3,"message":"Connection lost"}}
16 Dec 18:28:35 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Dec 18:28:35 - [info] [server:Home Assistant] Connected to http://supervisor/core
16 Dec 18:30:28 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
16 Dec 18:30:33 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Dec 18:30:34 - [info] [server:Home Assistant] Connected to http://supervisor/core
16 Dec 18:32:27 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
16 Dec 18:32:32 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Dec 18:32:33 - [info] [server:Home Assistant] Connected to http://supervisor/core
16 Dec 18:40:19 - [error] [api-call-service:Fernsehlicht EIN] Error: Unrecognized error: 3
16 Dec 18:40:21 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
16 Dec 18:40:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Dec 18:40:26 - [info] [server:Home Assistant] Connected to http://supervisor/core
16 Dec 18:42:08 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
16 Dec 18:42:13 - [info] [server:Home Assistant] Connecting to http://supervisor/core
16 Dec 18:42:14 - [info] [server:Home Assistant] Connected to http://supervisor/core
Hi, habe NOde Red mal neugestartet oder besser gesagt die Integration und das Protokoll für den Neustart kommt jetzt aber vorsicht einen ganze Menge
[13:53:15] INFO: Service NGINX exited with code 0 (by signal 0)
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
17 Dec 13:53:15 - [info] Stopping flows
17 Dec 13:53:15 - [info] Stopped flows
[13:53:15] INFO: Service Node-RED exited with code 0 (by signal 0)
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
-----------------------------------------------------------
Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 18.1.1
You are running the latest version of this add-on.
System: Home Assistant OS 14.0 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.12.3
Home Assistant Supervisor: 2024.12.0
-----------------------------------------------------------
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 192 packages in 2s
48 packages are looking for funding
run `npm fund` for details
8 vulnerabilities (3 moderate, 5 high)
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
npm notice
npm notice New major version of npm available! 10.7.0 -> 11.0.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.0.0
npm notice To update run: npm install -g npm@11.0.0
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
[13:53:21] 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
17 Dec 13:53:22 - [info]
Welcome to Node-RED
===================
17 Dec 13:53:22 - [info] Node-RED version: v4.0.3
17 Dec 13:53:22 - [info] Node.js version: v18.20.4
17 Dec 13:53:22 - [info] Linux 6.6.51-haos-raspi arm64 LE
17 Dec 13:53:22 - [info] Loading palette nodes
17 Dec 13:53:23 - [info] Node-RED Contrib Theme Collection version: v4.0.11
17 Dec 13:53:24 - [info] Dashboard version 3.6.5 started at /endpoint/ui
17 Dec 13:53:24 - [info] node-red-contrib-home-assistant-websocket v0.74.2 nodes initialized
17 Dec 13:53:24 - [info] Settings file : /etc/node-red/config.js
17 Dec 13:53:24 - [info] Context store : 'default' [module=memory]
17 Dec 13:53:24 - [info] User directory : /config/
17 Dec 13:53:24 - [warn] Projects disabled : editorTheme.projects.enabled=false
17 Dec 13:53:24 - [info] Flows file : /config/flows.json
17 Dec 13:53:24 - [info] Server now running at http://127.0.0.1:46836/
17 Dec 13:53:24 - [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.
---------------------------------------------------------------------
17 Dec 13:53:24 - [info] Starting flows
17 Dec 13:53:24 - [error] [server:ea850f4b.b174d] Error: Invalid property expression: unterminated expression
Error: Circular config node dependency detected: 01579226d22105a1
at Flow.start (/opt/node_modules/@node-red/runtime/lib/flows/Flow.js:227:43)
at Object.start [as startFlows] (/opt/node_modules/@node-red/runtime/lib/flows/index.js:403:17)
17 Dec 13:53:24 - [error] [api-call-service:4050fd308bfcd3ab] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:892db100ee43b6ab] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:27cfac25a93e2305] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:ababfa1a02a956aa] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:4f2af862d6f80eb8] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:7e67a562cddf4947] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:78e8201c65dab967] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:ab96ce576fffc407] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:fe1eca5fc2c2a640] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:ba60f6e3018dc224] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:13aa7825891ab36e] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:58ba10641f231b1b] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:1a0c2adca6136475] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:fff90ef549ea1741] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:4edceda109513469] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:aaf00d866c95cddf] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:b782b5cb633e070f] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:86e02a4cb864609b] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:2ff8bc84af9e644c] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:ec4dd736f52cdd91] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:c7e16b81eee31dfc] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:eacd7cad5fb3c9cd] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:cc139a6c0ff78143] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-events-calendar:dd541ff67712967d] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:762681c91c0707f1] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:97edcbf50f36e2f0] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:f37b25ea5814857c] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:019c367f81827ef8] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:f6994c62adc6b076] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:031e59947c32f526] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:6d33fde197b61239] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:ac8e50feb4096676] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:50fa100cd50648d3] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:a4bc7267e8568906] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:94e9577d98b3e9b7] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:0180a4a166830bf6] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:618471e4c944842d] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:ecd51dbb167f84ee] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:8a632b135e75cc58] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:b3fb99cda21461f4] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:d49aa92807e9398b] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:0c0fb69e2117ee7f] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:02e85216d62efe06] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:3f9ed5b151106220] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:02e9c46374727512] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:c119aa309dbc87fe] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:08c07e3cc092b6c5] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:373ef36f687b8baa] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:de01084aaeb3326d] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:1bc84d559631ed9a] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:89699574a52712a5] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:c2ed6fbbb2bf6006] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:8900ddefcaafd9fb] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:f609293aee9069f9] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-sensor:67550f9d804a0813] Error: Invalid entity config
17 Dec 13:53:24 - [error] [ha-sensor:a22dabf99b150a7f] Error: Invalid entity config
17 Dec 13:53:24 - [error] [api-current-state:02f5d8017090a348] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-sensor:17752c7cea439c80] Error: Invalid entity config
17 Dec 13:53:24 - [error] [poll-state:f2f9d60544474cf4] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:5d71bab898eb4a5c] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:bf87a2dbeddbee27] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:57c94bbe066cd592] Error: Invalid server config
17 Dec 13:53:24 - [error] [ha-sensor:fd050df1d48f7ebd] Error: Invalid entity config
17 Dec 13:53:24 - [error] [server-state-changed:3f44ca8c4a744b52] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:c2043e6df9bb481e] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:0cdfcdbff455a031] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:d86fe4c3d309100d] Error: Invalid server config
17 Dec 13:53:24 - [error] [server-state-changed:810643b5ebe9842d] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:2dcc6bc09c7eb6f5] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:3cf8b620f19fa1cd] Error: Invalid server config
17 Dec 13:53:24 - [error] [server-state-changed:f622a7aa96eb5e52] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:00b822f379472b8f] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:02b87fea4e4ad9ca] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:511165e1bb6883a2] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:4be8fc46b53b4ffa] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:8273a7ea8ced581b] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:04968e0fd9d2a94b] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:fba8408e589212f0] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:3431e32ba494807c] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:43e4e4a662672dc3] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:72bed67b4692d92d] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:fb24bf818f2872ba] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:37ba761a6f2b27dc] Error: Invalid server config
17 Dec 13:53:24 - [error] [poll-state:5fce3feb6e683c65] Error: Invalid server config
[13:53:24] INFO: Starting NGinx...
17 Dec 13:53:24 - [error] [poll-state:dc67b5f94e58d340] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:4917568b86f829da] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:2722e7364d2a64a5] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:bcb7c3b8a9197596] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:69617c83b65ad44b] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-current-state:4e3049bbe3b2b06e] Error: Invalid server config
17 Dec 13:53:24 - [error] [api-call-service:39304091fd903022] Error: Invalid server config
17 Dec 13:53:25 - [info] Started flows
ich hoffe da habt Ihr mehr Plan von wie ich !
Wenn ich das richtig sehe hat es irgendwas mit der Server config zu tun da passt die IP auf jeden Fall nicht.
by HarryP:
. Zusammenführung Doppelpost (bitte “bearbeiten” Funktion nutzen)
. Code-/Logzeilen formatiert (bitte immer in </> einbinden)
by HarryP: