Probleme avec Node red

steevy · Avril 2, 2024, 6:00

Désolée pour la mise la mise en forme je ne savais pas je dois utiliser texte préformater?
C’est mon HA qui plante? ou mon Raspberry?
Ce n’est pas moi qui redémarre HA

Ca devient embêtent car mes volets ne se ferme pas tous car sur certains j’ai un délais de 20 min pour fermer plus tard.

maintenant erreur 502 Bad Gateway

</>

[20:01:02] INFO: Service Node-RED exited with code 256 (by signal 9)
[20:01:03] INFO: Starting Node-RED...

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

2024/04/02 20:01:14 [error] 464#464: *1963 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:46836/", host: "192.168.1.141:8123", referrer: "http://192.168.1.141:8123/a0d7b954_nodered"
2 Apr 20:01:19 - [info] 

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

2 Apr 20:01:19 - [info] Node-RED version: v3.1.8
2 Apr 20:01:19 - [info] Node.js  version: v18.19.1
2 Apr 20:01:19 - [info] Linux 6.1.63-haos-raspi arm64 LE
2 Apr 20:01:31 - [info] Loading palette nodes
2 Apr 20:01:39 - [info] Node-RED Contrib Theme Collection version: v3.1.11
2024/04/02 20:02:03 [error] 464#464: *1977 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:46836/", host: "192.168.1.141:8123", referrer: "http://192.168.1.141:8123/a0d7b954_nodered"
2 Apr 20:02:44 - [info] Dashboard version 3.6.5 started at /endpoint/ui</>

Pulpy-Luke · Avril 2, 2024, 6:05

Oui texte préformaté, c’est très bien

Si c’est pas toi qui redémarre, il faut creuser dans les logs HA en premier pour y trouver des pistes.

Des taches qui trainent longtemps en mémoire, c’est jamais fiable … Il y a surement moyen de faire 2 déclencheurs (avec 20min) d’écarts plutot qu’1 déclencheur qui enchaine les actions avec 20 min de tempo

steevy · Avril 2, 2024, 6:08

j’ai modifier les message entre temps…

je dois regarder quels logs HA?

Des taches qui trainent longtemps en mémoire, c’est jamais fiable … Il y a surement moyen de faire 2 déclencheurs (avec 20min) d’écarts plutot qu’1 déclencheur qui enchaine les actions avec 20 min de tempo

ok donc je dois voir ça par apres

Pulpy-Luke · Avril 2, 2024, 6:10

L’addon n’est pas lancé

steevy:

[20:01:02] INFO: Service Node-RED exited with code 256 (by signal 9)
[20:01:03] INFO: Starting Node-RED...

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

2024/04/02 20:01:14 [error] 464#464: *1963 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: a0d7b954-nodered, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:46836/", host: "192.168.1.141:8123", referrer: "http://192.168.1.141:8123/a0d7b954_nodered"
2 Apr 20:01:19 - [info]

Pareil que la dernière fois, pas de connexion à HA, et redémarrage

steevy · Avril 2, 2024, 6:16

oui j’ai pas redemarrer HA

Je dois envoyer le rapport complets HA " télécharger les journaux complets?

Pulpy-Luke · Avril 2, 2024, 6:17

Oui regarde si tu vois un truc dans les journaux complets

steevy · Avril 2, 2024, 6:21

j’ai plein d’erreur

Pulpy-Luke · Avril 2, 2024, 6:23

Oui et c’est pas les logs complets.
Regarde en 1er les trucs en rapport avec MQTT.
C’est encore le même genre de trucs que la semaine dernière

steevy · Avril 2, 2024, 6:33

ci joint le rapport de mosquitto Brocker

J’ai modifier les mot de passe du Shelly peut etre ca vient de ca? mais ma porte s’ouvrait c’est normal?
Y a encore une erreur dans NR mais je vois pas ou…

2024-04-02 20:24:17: New connection from 192.168.1.141:54560 on port 1883.
2024-04-02 20:24:17: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:24:23: New connection from 172.30.32.1:36901 on port 1883.
2024-04-02 20:24:23: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:24: New connection from 172.30.32.1:53497 on port 1883.
2024-04-02 20:24:25: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:27: New connection from 172.30.32.1:47331 on port 1883.
2024-04-02 20:24:27: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:31: New connection from 172.30.32.1:36669 on port 1883.
2024-04-02 20:24:31: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:33: New connection from 192.168.1.141:47148 on port 1883.
2024-04-02 20:24:33: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:24:39: New connection from 172.30.32.1:38307 on port 1883.
2024-04-02 20:24:39: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:48: New connection from 192.168.1.141:54992 on port 1883.
2024-04-02 20:24:48: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:24:55: New connection from 172.30.32.1:50437 on port 1883.
2024-04-02 20:24:55: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:24:57: New connection from 172.30.32.2:42518 on port 1883.
2024-04-02 20:24:57: Client <unknown> closed its connection.
2024-04-02 20:25:03: New connection from 192.168.1.141:51420 on port 1883.
2024-04-02 20:25:03: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:25:10: New connection from 192.168.1.148:52254 on port 1883.
2024-04-02 20:25:10: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:25:19: New connection from 192.168.1.141:37372 on port 1883.
2024-04-02 20:25:19: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:25:27: New connection from 172.30.32.1:49003 on port 1883.
2024-04-02 20:25:27: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:25:35: New connection from 192.168.1.141:48204 on port 1883.
2024-04-02 20:25:35: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:25:50: New connection from 192.168.1.141:50142 on port 1883.
2024-04-02 20:25:50: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:26:04: New connection from 192.168.1.148:52255 on port 1883.
2024-04-02 20:26:04: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:26:05: New connection from 192.168.1.141:52772 on port 1883.
2024-04-02 20:26:05: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:26:21: New connection from 192.168.1.141:46216 on port 1883.
2024-04-02 20:26:21: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:26:31: New connection from 172.30.32.1:58539 on port 1883.
2024-04-02 20:26:31: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:26:40: New connection from 192.168.1.141:46550 on port 1883.
2024-04-02 20:26:40: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:26:57: New connection from 172.30.32.2:33128 on port 1883.
2024-04-02 20:26:57: Client <unknown> closed its connection.
2024-04-02 20:26:59: New connection from 192.168.1.148:52256 on port 1883.
2024-04-02 20:26:59: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:27:02: New connection from 192.168.1.141:43222 on port 1883.
2024-04-02 20:27:02: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:27:17: New connection from 192.168.1.141:46544 on port 1883.
2024-04-02 20:27:17: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:27:32: New connection from 192.168.1.141:36962 on port 1883.
2024-04-02 20:27:32: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:27:47: New connection from 192.168.1.141:41890 on port 1883.
2024-04-02 20:27:47: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:27:59: New connection from 192.168.1.148:52257 on port 1883.
2024-04-02 20:27:59: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:28:03: New connection from 192.168.1.141:37198 on port 1883.
2024-04-02 20:28:03: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:28:18: New connection from 192.168.1.141:36984 on port 1883.
2024-04-02 20:28:18: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:28:32: New connection from 172.30.32.1:59371 on port 1883.
2024-04-02 20:28:32: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:28:33: New connection from 192.168.1.141:42694 on port 1883.
2024-04-02 20:28:33: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:28:48: New connection from 192.168.1.141:52430 on port 1883.
2024-04-02 20:28:48: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:28:54: New connection from 192.168.1.148:52258 on port 1883.
2024-04-02 20:28:54: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:28:57: New connection from 172.30.32.2:36360 on port 1883.
2024-04-02 20:28:57: Client <unknown> closed its connection.
2024-04-02 20:29:03: New connection from 192.168.1.141:43394 on port 1883.
2024-04-02 20:29:03: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:29:18: New connection from 192.168.1.141:33892 on port 1883.
2024-04-02 20:29:19: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:29:34: New connection from 192.168.1.141:59164 on port 1883.
2024-04-02 20:29:34: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:29:49: New connection from 192.168.1.141:38384 on port 1883.
2024-04-02 20:29:49: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:29:53: New connection from 192.168.1.148:52259 on port 1883.
2024-04-02 20:29:53: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:30:04: New connection from 192.168.1.141:37368 on port 1883.
2024-04-02 20:30:04: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:30:19: New connection from 192.168.1.141:52772 on port 1883.
2024-04-02 20:30:19: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:30:32: New connection from 172.30.32.1:53345 on port 1883.
2024-04-02 20:30:32: Client 2ecg5c9Wzhqd9YRFqOO2tE disconnected, not authorised.
2024-04-02 20:30:36: New connection from 192.168.1.141:52990 on port 1883.
2024-04-02 20:30:36: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:30:49: New connection from 192.168.1.148:52260 on port 1883.
2024-04-02 20:30:49: Client shellyplus1-083af2024b14 disconnected, not authorised.
2024-04-02 20:30:51: New connection from 192.168.1.141:57988 on port 1883.
2024-04-02 20:30:51: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:30:57: New connection from 172.30.32.2:33480 on port 1883.
2024-04-02 20:30:57: Client <unknown> closed its connection.
2024-04-02 20:31:07: New connection from 192.168.1.141:33808 on port 1883.
2024-04-02 20:31:07: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:31:23: New connection from 192.168.1.141:43866 on port 1883.
2024-04-02 20:31:23: Client nodered_675dd9dddd11ed51 disconnected, not authorised.
2024-04-02 20:31:38: New connection from 192.168.1.141:56762 on port 1883.
2024-04-02 20:31:38: Client nodered_675dd9dddd11ed51 disconnected, not authorised.

Pulpy-Luke · Avril 2, 2024, 6:35

ça c’est pas les shelly

ça oui

Bref, tu as plusieurs problèmes…

steevy · Avril 2, 2024, 6:47

Oui plusieurs problème …
justement je voulais reconfigurer MQTT et plus rien ne fonctionne

ca doit venir de la le problème?

Pulpy-Luke · Avril 2, 2024, 6:51

C’est pas que ça mais clairement tant que tu n’as pas les 4 bonnes valeurs (ip ou nom/port/user/password) et que c’est pas répliqué partout (HA/NR/Shelly etc), tu vas avoir des erreurs

steevy · Avril 2, 2024, 7:54

je vais reessayer demain

steevy · Avril 3, 2024, 3:44

je viens de reconfigurer MQTT

Il me semble que c’est bon?

ci joint le journal

2024-04-03 13:22:03: New connection from 192.168.1.148:52734 on port 1883.
2024-04-03 13:22:03: Client shellyplus1-083af2024b14 already connected, closing old connection.
2024-04-03 13:22:03: New client connected from 192.168.1.148:52734 as shellyplus1-083af2024b14 (p2, c1, k60, u'mqtt').
2024-04-03 13:26:31: Saving in-memory database to /data//mosquitto.db.
2024-04-03 13:56:32: Saving in-memory database to /data//mosquitto.db.
2024-04-03 14:26:33: Saving in-memory database to /data//mosquitto.db.
2024-04-03 14:56:34: Saving in-memory database to /data//mosquitto.db.
2024-04-03 15:26:35: Saving in-memory database to /data//mosquitto.db.
2024-04-03 15:56:36: Saving in-memory database to /data//mosquitto.db.
2024-04-03 16:26:37: Saving in-memory database to /data//mosquitto.db.
2024-04-03 16:56:38: Saving in-memory database to /data//mosquitto.db.
2024-04-03 17:05:52: New connection from 172.30.32.1:48291 on port 1883.
2024-04-03 17:05:52: New client connected from 172.30.32.1:48291 as 6OtKVEDLhxGdv9CjxjaU7l (p2, c1, k60, u'homeassistant').
2024-04-03 17:05:53: Client 6OtKVEDLhxGdv9CjxjaU7l disconnected.
2024-04-03 17:05:54: New connection from 172.30.32.1:46951 on port 1883.
2024-04-03 17:05:54: New client connected from 172.30.32.1:46951 as 2hh4YTM8DMHeXn0auLsVGz (p2, c1, k60, u'homeassistant').
2024-04-03 17:10:21: New connection from 172.30.32.1:36779 on port 1883.
2024-04-03 17:10:21: New client connected from 172.30.32.1:36779 as 7I81lIsoVybuqOfhbOO736 (p2, c1, k60, u'mqtt').
2024-04-03 17:10:27: Client 7I81lIsoVybuqOfhbOO736 disconnected.
2024-04-03 17:10:44: New connection from 172.30.32.1:50999 on port 1883.
2024-04-03 17:10:44: New client connected from 172.30.32.1:50999 as 0OJISzUx1JsnBZFS1IJGjr (p2, c1, k60, u'homeassistant').
2024-04-03 17:10:44: Client 0OJISzUx1JsnBZFS1IJGjr disconnected.
2024-04-03 17:10:54: New connection from 172.30.32.1:46555 on port 1883.
2024-04-03 17:10:54: New client connected from 172.30.32.1:46555 as 6lV4cBlU2alsZ7f8pmQiaz (p2, c1, k60, u'homeassistant').
2024-04-03 17:12:27: Client 2hh4YTM8DMHeXn0auLsVGz has exceeded timeout, disconnecting.
2024-04-03 17:17:27: Client 6lV4cBlU2alsZ7f8pmQiaz has exceeded timeout, disconnecting.
2024-04-03 17:18:20: New connection from 172.30.32.1:54403 on port 1883.
2024-04-03 17:18:20: New client connected from 172.30.32.1:54403 as 3IX6yVnDEifW74Fp4KfjCQ (p2, c1, k60, u'homeassistant').
2024-04-03 17:26:39: Saving in-memory database to /data//mosquitto.db.

a quoi correspond cette connexion?

2024-04-03 17:10:54: New client connected from 172.30.32.1:46555 as 6lV4cBlU2alsZ7f8pmQiaz (p2, c1, k60, u'homeassistant').

Pulpy-Luke · Avril 3, 2024, 3:56

Oui, c’est mieux, il ne semble plus y avoir de rejet

un addon qui utilise un user homeassistant…

Là c’est aussi un addon mais qui utilise le compte mqtt

steevy · Avril 3, 2024, 3:59

Merci pour ta réponse rapide

Donc c’est normal ces connexions?

J’ai juste un Shelly qui se connecte a MQQt et un node dans NR

Pulpy-Luke · Avril 3, 2024, 4:04

Oui. N’importe quel truc qui à besoin de MQTT doit s’y connecter et génère ce genre de trace

steevy · Avril 3, 2024, 4:08

ok parfait merci des explications.

par contre dans NR red je n’ai pas modifier les connexion et maintenant les valeurs s’affichent et ce n’était pas le cas avant

c’est normal?

MQTT

Pulpy-Luke · Avril 3, 2024, 4:41

Je ne sais pas combien de compte, tu as en tout mais là il y en a au moins 3

homeassistant
ha-mqtt
mqtt

Pour 2 trucs qui consomment ça fait beaucoup mais is ça fonctionne (valeurs qui s’affichent) …

Argonaute · Avril 3, 2024, 5:05

Peut-être l’occasion de passer sur les automatisation HA ? Perso j’ai encore du node-red pour du très spécifique.

Mais avec toutes les mises à jours de HA qui ont été faites, c’est maintenant bien plus simple avec les automatisations HA à créer, debugger et maintenir, documenter, e ce sans compter sur la facilité de partage en YAML, l’utilisation des blueprints et la nouvelle gestion des catégories/ tags arrivant avec la version 2024.4… La syntaxe est celle de HA, les liens avec les entités sont bien gérés, etc, etc

Le choix node-red avait du sens autrefois, mais c’est vraiment plus difficile à défendre maintenant.