Bonjour a tous
pour commander pas mal de fonction de mon installation, je passe par NodeRed pour envoyer des requetes HTTP
depuis la derniere mise a jour de Home assistant, il semblerait que NodeRed ne fonctionne plus
lorsque je veux ouvrir l’interface NodeRed, j’ai une erreur 502 (Bad Gateway)
est ce un probleme connus ou suis je le seul?
si quelqu’un a une idée, je suis preneur.
Merci de vos lumières
Salut,
Connu oui : 502 c’est que l’addon ne démarre pas (pas que NR d’ailleurs) … donc il faut analyser les logs de NR
pourquoi diable ne demarre t il pas
dans la page des modules complémentaires, il est pourtant bien démarré.
J’ai meme essayé de l’arreté puis de le redemarré, mais idem
et si je click sur l’onglet « Journal » il n’y a rien
mais en cherchant un peu, il semblerait qu’il y ait un lien avec HACS
car j’ai un message « Custom integration » et dans les log, un message me dit :
2023-06-26 08:26:02.234 WARNING (SyncWorker_2) [homeassistant.loader] We found a custom integration nodered which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
C’est un warning et ça concerne TOUT ce qui n’est pas dans la core HA… Donc il faut regarder ailleurs
je viens de re installer le module NodeRed et cela semble résoudre le probleme.
Pourquoi???
que c’est il passé ???
mystère
Bon, après quelques heures, le problème recommence
Je suis un peu perdu
ll n’y a que les logs qui peuvent te guider : ceux de HA ou de NR
Peux tu m’aider et me dire ou je peux les trouver?
dans l’interface graphique, les journaux de NodeRed sont vide
mais il doit y avoir les fichiers quelques part.
maintenant, lorsque j’oure l’interface NodeRed, elle bloque au chargements des Flows
Salut,
J’ai déjà eu ce type de comportement après avoir installé une palette vérolée dans NR.
Ne serait-ce pas le cas ?
Quelles sont les palettes que tu utilises ?
je n’ai rien installé de nouveau depuis longtemps
le probleme est apparut sans modification de HA (hormis la derniere mise a jour
Cela ne réponds pas à la questions des palettes que tu as d’installé.
Chez moi, la mise à jour n’a causé aucun problème.
uniquement les palettes par defauts de HA
Hello
Ce n’est pas très cohérents tout ça…
Si tu as un 502 (Bad Gateway), tu ne peux pas ouvrir l’interface…
Si tu arrives à ouvrir l’interface, tu as forcément des logs dans les journaux…
en fait, autrefois, NodeRed etait un plugin de HA
Maintenenat, il faut l’installer via HACS
les « journaux » que je regarde sont ceux de l’ancien NodeRed, donc forcement, il n’y a rien
il faut que je regarde les log de NodeRed, mais, a part passer par l’interface, je ne sais pas si je peux trouver les fichiers log quelques part
apres un redemarrage du systeme, cela fonctionne un moment, et apres quelques temps (environs 1 heure) re probleme
Je ne sais pas ce que tu appelles avant/après mais NR est toujours dispo comme un addon… L’intégration HACS c’est simplement un truc pour les websockets
C’est nouveau ou plutôt une mauvaise interprétation de ta part.
Il faut passer par l’addon pour faire l’installation de NR.
Le module companion installable par HACS t’apporte des fonctionnalités supplémentaires mais nécessite forcément que NR soit installer par Addon ou par container
je comprend mieux le fonctionnement.
apres re installation du addon HACS Nodered, cela a fonctionné toute la journée hier, et ce matin, de nouveau le probleme
je ne peux pas ouvrir l’interface NodeRed, les Node Switch ne fonctionnent pas
en revenche, j’ai d’autres Node (qui lise des données dans un base MySQL) qui fonctionnent puisque les valeurs sont bien affichés dans HA
et toujours rien dans les journaux du module complementaire NodeRed
ou puis je acceder au logs ?
je n’y comprend plus rien
Salut,
Ceux de HA ou ceux de l’addon. C’est juste pas possible que tu n’ai rien…
votre support a tous agit comme de la magie :
maintenant (alors que rien n’a été modifié) j’ai quelque chose dans les log NodeRed :
28 Jun 08:18:20 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:26 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:35 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:42 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:48 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:53 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:18:54 - [error] [ha-binary-sensor:presence_papa] NoConnectionError: No connection to Home Assistant
28 Jun 08:18:54 - [error] [ha-binary-sensor:presence_maman] NoConnectionError: No connection to Home Assistant
28 Jun 08:18:54 - [error] [ha-binary-sensor:presence_alienor] NoConnectionError: No connection to Home Assistant
28 Jun 08:18:54 - [error] [ha-binary-sensor:etat_portail] NoConnectionError: No connection to Home Assistant
28 Jun 08:18:59 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:19:06 - [info] [server:Home Assistant] Connected to http://supervisor/core
28 Jun 08:23:39 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
28 Jun 08:23:39 - [info] [server:Home Assistant] Connection closed to http://supervisor/core
28 Jun 08:23:40 - [error] [ha-binary-sensor:presence_papa] NoConnectionError: No connection to Home Assistant
28 Jun 08:23:40 - [error] [ha-binary-sensor:presence_maman] NoConnectionError: No connection to Home Assistant
28 Jun 08:23:40 - [error] [ha-binary-sensor:presence_alienor] NoConnectionError: No connection to Home Assistant
28 Jun 08:23:40 - [error] [ha-binary-sensor:etat_portail] NoConnectionError: No connection to Home Assistant
28 Jun 08:23:45 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:23:46 - [info] [server:Home Assistant] Connected to http://supervisor/core
[08:33:00] INFO: Service Node-RED exited with code 256 (by signal 9)
[08:33:02] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
28 Jun 08:33:14 - [info]
Welcome to Node-RED
===================
28 Jun 08:33:14 - [info] Node-RED version: v3.0.2
28 Jun 08:33:14 - [info] Node.js version: v18.16.0
28 Jun 08:33:14 - [info] Linux 6.1.34 x64 LE
28 Jun 08:33:17 - [info] Loading palette nodes
28 Jun 08:33:38 - [info] Dashboard version 3.5.0 started at /endpoint/ui
28 Jun 08:33:52 - [info] Settings file : /etc/node-red/config.js
28 Jun 08:33:53 - [info] Context store : 'default' [module=memory]
28 Jun 08:33:53 - [info] User directory : /config/node-red/
28 Jun 08:33:53 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Jun 08:33:53 - [info] Flows file : /config/node-red/flows.json
28 Jun 08:33:54 - [info] Server now running at http://127.0.0.1:46836/
28 Jun 08:33:56 - [info] Starting flows
28 Jun 08:34:01 - [info] Started flows
28 Jun 08:34:03 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 08:34:07 - [info] [server:Home Assistant] Connected to http://supervisor/core
[09:12:47] INFO: Service Node-RED exited with code 256 (by signal 9)
2023/06/28 09:12:48 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
[09:12:49] INFO: Starting Node-RED...
2023/06/28 09:12:49 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:12:52 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:12:53 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
> start
> node $NODE_OPTIONS node_modules/node-red/red.js --settings /etc/node-red/config.js
2023/06/28 09:12:55 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:12:57 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:12:59 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
28 Jun 09:13:01 - [info]
Welcome to Node-RED
===================
28 Jun 09:13:01 - [info] Node-RED version: v3.0.2
28 Jun 09:13:01 - [info] Node.js version: v18.16.0
28 Jun 09:13:01 - [info] Linux 6.1.34 x64 LE
2023/06/28 09:13:02 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:03 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
28 Jun 09:13:04 - [info] Loading palette nodes
2023/06/28 09:13:05 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:08 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:09 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:11 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:15 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:17 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:19 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:22 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:24 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:26 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:29 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:31 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:33 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:35 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
28 Jun 09:13:36 - [info] Dashboard version 3.5.0 started at /endpoint/ui
2023/06/28 09:13:37 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:39 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:42 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:45 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
2023/06/28 09:13:46 [error] 630#630: *220 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET /comms HTTP/1.1", upstream: "http://127.0.0.1:46836/comms", host: "roland.yt"
28 Jun 09:13:47 - [info] Settings file : /etc/node-red/config.js
28 Jun 09:13:47 - [info] Context store : 'default' [module=memory]
28 Jun 09:13:47 - [info] User directory : /config/node-red/
28 Jun 09:13:47 - [warn] Projects disabled : editorTheme.projects.enabled=false
28 Jun 09:13:47 - [info] Flows file : /config/node-red/flows.json
28 Jun 09:13:47 - [info] Server now running at http://127.0.0.1:46836/
28 Jun 09:13:47 - [info] Starting flows
28 Jun 09:13:49 - [info] Started flows
28 Jun 09:13:53 - [info] [server:Home Assistant] Connecting to http://supervisor/core
28 Jun 09:13:53 - [info] [server:Home Assistant] Connected to http://supervisor/core