Zigbee2mqtt problème de connexion depuis nouvelle version

Pareil pour moi,
VonOx j’ai installé la version de Gladys que tu indiques. au bout de 6 fois de reinstall, je constate que si je restaure Gladys avec sauvegarde Gladys +, avant d’installer NodeRed, tous les services de Gladys s’installent et fonctionnent correctement, puis je charge Node red tout va bien , je reinstalle mes palettes (qui elles ne sont pas dans la sauvegarde de node red, je restaure mes flows tout se charge correctement, mais après" perte de connexion au serveur “, je n’ai plus de connexion de la gateway Xiaomi , plus de connexion Mqtt. Et en passant il ne faut pas oublier de réinitialiser le broker Mqtt de Gladys, (car il ne redémarre pas tout seul). Et quand je relance Node red je n’ai plus de connexion au dashboard de Node RED( IpGladys:1880). Oui j’ai aussi le redémarrage de Node Red en boucle, moi tous les 15secondes environ (ça me rappelle mon problème avec Zigbbe2Mqtt. " il semble que le container reboote toutes les 20 secondes environ.”)
koenkk/zigbee2mqtt:latest “docker-entrypoint.s…” 12 days ago Up 18 seconds gladys-z2m-zigbee2mqtt
koenkk/zigbee2mqtt:latest “docker-entrypoint.s…” 12 days ago Up 18 seconds gladys-z2m-zigbee2mqtt
koenkk/zigbee2mqtt:latest “docker-entrypoint.s…” 12 days ago Up 1 second gladys-z2m-zigbee2mqtt``)

Et en vérifiant, je me rend compte que gladys-z2m-zigbee2mqtt, boucle également lui toutes les 30 secondes
C’est grave docteur?

Hello, bon ben voila c’est reparti tout refonctionne, juste un capteur que j’ai du reapairé, détecteur de fuite, merci pour l’aide, j’ai lancer toutes les commandes même si je sais pas trop à quoi sa correspond ni ce que sa fait, c’est aussi cela qui me fait peur lol

T’as combien de conteneur zigbee2mqtt là ?

docker ps-a

Aussi ça m’étonne qu’on voit une date de 12jours si tu viens de réinstaller

Rassures toi les logs sont ceux d’il y a 12 jours ce ne sont pas ceux du problème actuel
Voila ceux d’aujourd’hui

pi@gladys:~ $ docker ps
CONTAINER ID   IMAGE                       COMMAND                  CREATED        STATUS                             PORTS      NAMES
a3aadc45bb2d   nodered/node-red            "npm --no-update-not…"   10 hours ago   Up 11 seconds (health: starting)              node_red
3de89db60721   eclipse-mosquitto:2         "/docker-entrypoint.…"   10 hours ago   Up 31 minutes                                 eclipse-mosquitto
6ac1456a52ad   koenkk/zigbee2mqtt:latest   "docker-entrypoint.s…"   10 hours ago   Up 32 seconds                                 gladys-z2m-zigbee2mqtt
3194c5b7a37c   eclipse-mosquitto:2         "/docker-entrypoint.…"   10 hours ago   Up 31 minutes                                 gladys-z2m-mqtt
fd45f079236e   gladysassistant/gladys:v4   "docker-entrypoint.s…"   10 hours ago   Up 31 minutes                                 gladys
7ae977fecca2   containrrr/watchtower       "/watchtower --clean…"   10 hours ago   Up 31 minutes                      8080/tcp   watchtower
pi@gladys:~ $ docker ps
CONTAINER ID   IMAGE                       COMMAND                  CREATED        STATUS                                  PORTS      NAMES
a3aadc45bb2d   nodered/node-red            "npm --no-update-not…"   10 hours ago   Restarting (0) Less than a second ago              node_red
3de89db60721   eclipse-mosquitto:2         "/docker-entrypoint.…"   10 hours ago   Up 31 minutes                                      eclipse-mosquitto
6ac1456a52ad   koenkk/zigbee2mqtt:latest   "docker-entrypoint.s…"   10 hours ago   Up Less than a second                              gladys-z2m-zigbee2mqtt
3194c5b7a37c   eclipse-mosquitto:2         "/docker-entrypoint.…"   10 hours ago   Up 31 minutes                                      gladys-z2m-mqtt
fd45f079236e   gladysassistant/gladys:v4   "docker-entrypoint.s…"   10 hours ago   Up 31 minutes                                      gladys
7ae977fecca2   containrrr/watchtower       "/watchtower --clean…"   10 hours ago   Up 31 minutes                           8080/tcp   watchtower
pi@gladys:~ $

Mais je viens de voir, que Pascal avait un device deconnecté, moi j’en ai plusieurs suite a coupure secteur, je vais investiguer de ce coté là
Merci pour ta réponse VonOx

Génial, content que tout re-fonctionne ! :wink:

Justement j’ai exporté mes flow pour sauvegarde.
Et je me suis dit sur Gladys version 64 bits j’aurai ces nouvelles mises à jour d’installer donc j’ai fait la mis à jour sur la version 32 bits qui était en production pensant pouvoir faire un nouvel export des flows une fois cette mise à jour effectué, mais celle-ci n’a jamais eu lieu puisque Node-red a planté.

Je vais tout de même tenter l’installation de Gladys en 64 bits, je vous tiens au parfum.

Bonsoir Bjm
Je viens de faire ça. ça fait 4 fois que je réinstalle tout. 4 fois planté , quand j’installe Node_red, soit Node REd plante plus ''d’accès au dashboard Node RED (avant j’ai un message qui me dit "perte de connexion au serveur ", et quand j’arrête Node Red (docker stop node_red) , je n’ai plus de connexion Zigbee2Mqtt. A l’heure actuelle Gladys et Zigbee2Mqtt fonctionne (une journée de boulot) et j’ai la hantise de réinstaller Node Red (mais je vais le faire). Courage :crazy_face:

je viens d’avoir droit à la “connexion perdu”

Et Node-red et repartie en boucle

Ah c’est ça :face_with_open_eyes_and_hand_over_mouth:, tiens moi au courant pour la suite .

pareil , est ce que tu as Zigbbe2Mqtt?
Ben non sinon il serait sur ton post

Ils ont fait une mise à jour eux aussi le 1 Avril :wink:

1 Like

un docker stop node_red
et
docker start node_red
Ne change rien

surtout un logs node_red pour voir pourquoi il reboot

oui ça ne résout rien , je voulais arreter node red pour recuperer Zigbee2Mqtt, car pour moi ça me plante Zigbee2Mqtt.
ET Gladys fonctionne toujours pour toi.

c’est pas drôle comme poisson d’avril :laughing:

Oui Gladys fonctionne toujours.
Mais Node-red est la première chose que j’ai installé, je n’ai rien d’autre.

tu n’as même pas restauré tes flows?
tu peux afficher les logs de node red ( docker logs node_red) pour VonOx

docker logs node_red

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 16:42:34 - [info] 

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

4 Apr 16:42:34 - [info] Node-RED version: v2.2.2
4 Apr 16:42:34 - [info] Node.js  version: v14.18.2
4 Apr 16:42:34 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 16:42:35 - [info] Loading palette nodes
4 Apr 16:42:38 - [info] Settings file  : /data/settings.js
4 Apr 16:42:38 - [info] Context store  : 'default' [module=memory]
4 Apr 16:42:38 - [info] User directory : /data
4 Apr 16:42:38 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 16:42:38 - [info] Flows file     : /data/flows.json
4 Apr 16:42:38 - [info] Creating new flow file
4 Apr 16:42:38 - [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 Apr 16:42:38 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 16:42:38 - [info] Starting flows
4 Apr 16:42:38 - [info] Started flows
4 Apr 16:52:01 - [info] Stopping flows
4 Apr 16:52:01 - [info] Stopped flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 16:52:05 - [info] 

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

4 Apr 16:52:06 - [info] Node-RED version: v2.2.2
4 Apr 16:52:06 - [info] Node.js  version: v14.18.2
4 Apr 16:52:06 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 16:52:07 - [info] Loading palette nodes
4 Apr 16:52:09 - [info] Settings file  : /data/settings.js
4 Apr 16:52:09 - [info] Context store  : 'default' [module=memory]
4 Apr 16:52:09 - [info] User directory : /data
4 Apr 16:52:09 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 16:52:09 - [info] Flows file     : /data/flows.json
4 Apr 16:52:09 - [info] Creating new flow file
4 Apr 16:52:09 - [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 Apr 16:52:09 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 16:52:09 - [info] Starting flows
4 Apr 16:52:09 - [info] Started flows
4 Apr 16:57:16 - [info] Installing module: node-red-contrib-google-home-notify-volume-adjustable, version: 0.0.11
4 Apr 16:58:17 - [info] Installed module: node-red-contrib-google-home-notify-volume-adjustable
4 Apr 16:58:17 - [info] Added node types:
4 Apr 16:58:17 - [info]  - node-red-contrib-google-home-notify-volume-adjustable:googlehome-config-node
4 Apr 16:58:17 - [info]  - node-red-contrib-google-home-notify-volume-adjustable:googlehome-notify
4 Apr 16:59:39 - [info] Installing module: node-red-node-serialport, version: 1.0.1
4 Apr 17:00:05 - [info] Installed module: node-red-node-serialport
4 Apr 17:00:05 - [info] Added node types:
4 Apr 17:00:05 - [info]  - node-red-node-serialport:serial in
4 Apr 17:00:05 - [info]  - node-red-node-serialport:serial out
4 Apr 17:00:05 - [info]  - node-red-node-serialport:serial request
4 Apr 17:00:05 - [info]  - node-red-node-serialport:serial-port
4 Apr 17:00:36 - [info] Installing module: node-red-contrib-rflink, version: 0.1.1
4 Apr 17:00:43 - [info] Installed module: node-red-contrib-rflink
4 Apr 17:00:43 - [info] Added node types:
4 Apr 17:00:43 - [info]  - node-red-contrib-rflink:rflink device
4 Apr 17:00:43 - [info]  - node-red-contrib-rflink:rflink in
4 Apr 17:00:43 - [info]  - node-red-contrib-rflink:rflink out
4 Apr 17:01:16 - [info] Installing module: node-red-dashboard, version: 3.1.6
4 Apr 17:02:20 - [info] Installed module: node-red-dashboard
4 Apr 17:02:21 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:02:21 - [info] Added node types:
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_base
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_button
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_dropdown
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_switch
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_slider
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_numeric
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_text_input
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_date_picker
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_colour_picker
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_form
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_text
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_gauge
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_chart
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_audio
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_toast
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_ui_control
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_template
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_link
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_tab
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_group
4 Apr 17:02:21 - [info]  - node-red-dashboard:ui_spacer
4 Apr 17:03:20 - [info] Installing module: node-red-node-ui-list, version: 0.3.6
4 Apr 17:03:32 - [info] Installed module: node-red-node-ui-list
4 Apr 17:03:32 - [info] Added node types:
4 Apr 17:03:32 - [info]  - node-red-node-ui-list:ui_list
4 Apr 17:12:09 - [info] Stopping flows
4 Apr 17:12:09 - [info] Stopped flows
4 Apr 17:12:09 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:12:18 - [info] 

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

4 Apr 17:12:18 - [info] Node-RED version: v2.2.2
4 Apr 17:12:18 - [info] Node.js  version: v14.18.2
4 Apr 17:12:18 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:12:19 - [info] Loading palette nodes
4 Apr 17:12:22 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:12:23 - [info] Settings file  : /data/settings.js
4 Apr 17:12:23 - [info] Context store  : 'default' [module=memory]
4 Apr 17:12:23 - [info] User directory : /data
4 Apr 17:12:23 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:12:23 - [info] Flows file     : /data/flows.json
4 Apr 17:12:23 - [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 Apr 17:12:23 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:12:23 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:12:31 - [info] 

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

4 Apr 17:12:31 - [info] Node-RED version: v2.2.2
4 Apr 17:12:31 - [info] Node.js  version: v14.18.2
4 Apr 17:12:31 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:12:33 - [info] Loading palette nodes
4 Apr 17:12:36 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:12:36 - [info] Settings file  : /data/settings.js
4 Apr 17:12:36 - [info] Context store  : 'default' [module=memory]
4 Apr 17:12:36 - [info] User directory : /data
4 Apr 17:12:36 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:12:36 - [info] Flows file     : /data/flows.json
4 Apr 17:12:36 - [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 Apr 17:12:36 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:12:36 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:12:45 - [info] 

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

4 Apr 17:12:45 - [info] Node-RED version: v2.2.2
4 Apr 17:12:45 - [info] Node.js  version: v14.18.2
4 Apr 17:12:45 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:12:46 - [info] Loading palette nodes
4 Apr 17:12:49 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:12:50 - [info] Settings file  : /data/settings.js
4 Apr 17:12:50 - [info] Context store  : 'default' [module=memory]
4 Apr 17:12:50 - [info] User directory : /data
4 Apr 17:12:50 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:12:50 - [info] Flows file     : /data/flows.json
4 Apr 17:12:50 - [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 Apr 17:12:50 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:12:50 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:12:58 - [info] 

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

4 Apr 17:12:58 - [info] Node-RED version: v2.2.2
4 Apr 17:12:58 - [info] Node.js  version: v14.18.2
4 Apr 17:12:58 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:12:59 - [info] Loading palette nodes
4 Apr 17:13:03 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:13:03 - [info] Settings file  : /data/settings.js
4 Apr 17:13:03 - [info] Context store  : 'default' [module=memory]
4 Apr 17:13:03 - [info] User directory : /data
4 Apr 17:13:03 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:13:03 - [info] Flows file     : /data/flows.json
4 Apr 17:13:03 - [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 Apr 17:13:03 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:13:03 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:13:12 - [info] 

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

4 Apr 17:13:12 - [info] Node-RED version: v2.2.2
4 Apr 17:13:12 - [info] Node.js  version: v14.18.2
4 Apr 17:13:12 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:13:14 - [info] Loading palette nodes
4 Apr 17:13:17 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:13:17 - [info] Settings file  : /data/settings.js
4 Apr 17:13:17 - [info] Context store  : 'default' [module=memory]
4 Apr 17:13:17 - [info] User directory : /data
4 Apr 17:13:17 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:13:17 - [info] Flows file     : /data/flows.json
4 Apr 17:13:17 - [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 Apr 17:13:17 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:13:17 - [info] Starting flows

> node-red-docker@2.2.2 start /usr/src/node-red
> node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"

4 Apr 17:13:26 - [info] 

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

4 Apr 17:13:26 - [info] Node-RED version: v2.2.2
4 Apr 17:13:26 - [info] Node.js  version: v14.18.2
4 Apr 17:13:26 - [info] Linux 5.10.103-v8+ arm64 LE
4 Apr 17:13:27 - [info] Loading palette nodes
4 Apr 17:13:30 - [info] Dashboard version 3.1.6 started at /ui
4 Apr 17:13:30 - [info] Settings file  : /data/settings.js
4 Apr 17:13:30 - [info] Context store  : 'default' [module=memory]
4 Apr 17:13:30 - [info] User directory : /data
4 Apr 17:13:30 - [warn] Projects disabled : editorTheme.projects.enabled=false
4 Apr 17:13:30 - [info] Flows file     : /data/flows.json
4 Apr 17:13:30 - [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 Apr 17:13:31 - [info] Server now running at http://127.0.0.1:1880/
4 Apr 17:13:31 - [info] Starting flows


Cela se répète à l’infini

Si j’ai installé les flows, c’est quand j’ai déployé que cela a merdé.