Depuis mise a jour MQTT2 probleme avec zwaveJs et Jeezigbee

Lemars · Octobre 5, 2023, 11:24

Bonjour
Je suis sous Docker pour Jeedom en version 4.3
et aussi sous Docker pour Moquitto
Tout fonctionnait bien mais depuis les 2 mises à jour successive sur MQTT et bien je n’arrive a commander les modules sous zwavejs ou z2m
les daemon des plugins sont tous ok
et voici les messages d’erreurs :

2023-10-05 13:20:50	z2m	Erreur exécution de la commande [JEEZIGBEE][ZBMini01 - Ventilateur Bureau][state on] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused		
	2023-10-05 13:20:40	zwavejs	Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][Off-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused		
	2023-10-05 13:20:35	zwavejs	Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][Off-1 pompe] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused		
	2023-10-05 13:20:34	zwavejs	Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused		
	2023-10-05 13:20:26	zwavejs	Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][On-1 pompe] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused		
	2023-10-05 13:20:14	zwavejs	Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][On-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused

la santé jeedom est tout au vert je ne sais pas comment faire
seules les commande zwavejs passent mais avec des erreurs

Mips · Octobre 5, 2023, 11:26

Bonjour,
ces messages veulent dire que non les démons ne sont pas ok puisque jeedom ne sait pas s’y connecter (55035 c’est le port par défaut du démon mqtt2)

donc comme pour toutes demandes sans aucune exception:

capture page santé jeedom
capture page config du plugin
tous les logs du plugin

Lemars · Octobre 5, 2023, 11:29

page santé jeedom :

pour zwavejs:

et ses logs :


[2023-10-05 12:48:43][INFO] : Arrêt du démon ZwaveJS
[2023-10-05 12:48:44][INFO] : Arrêt du démon ZwaveJS
[2023-10-05 12:48:44][INFO] : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=5675FDAA45FCAC2DC046A6AA58781F92 KEY_S2_Unauthenticated=14C1E7A95F03AE1F30AF9A09EEE9626A KEY_S2_Authenticated=9586BD96471F9451FE328676D5018A02 KEY_S2_AccessControl=848CE74F5D1236545BE212217B63FC8A SESSION_SECRET=jeedomSession yarn start
[2023-10-05 12:50:30][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 12:55:32][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 12:57:10][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][On-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 12:57:27][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][Off-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:00:18][ERROR] : Erreur sur la fonction cronHourly du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:00:36][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:05:32][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:13:46][INFO] : Arrêt du démon ZwaveJS
[2023-10-05 13:13:46][INFO] : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=5675FDAA45FCAC2DC046A6AA58781F92 KEY_S2_Unauthenticated=14C1E7A95F03AE1F30AF9A09EEE9626A KEY_S2_Authenticated=9586BD96471F9451FE328676D5018A02 KEY_S2_AccessControl=848CE74F5D1236545BE212217B63FC8A SESSION_SECRET=jeedomSession yarn start
[2023-10-05 13:15:44][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:18:58][INFO] : Arrêt du démon ZwaveJS
[2023-10-05 13:19:04][INFO] : Arrêt du démon ZwaveJS
[2023-10-05 13:19:04][INFO] : Démarrage du démon ZwaveJS : STORE_DIR=/var/www/html/plugins/zwavejs/data/store KEY_S0_Legacy=5675FDAA45FCAC2DC046A6AA58781F92 KEY_S2_Unauthenticated=14C1E7A95F03AE1F30AF9A09EEE9626A KEY_S2_Authenticated=9586BD96471F9451FE328676D5018A02 KEY_S2_AccessControl=848CE74F5D1236545BE212217B63FC8A SESSION_SECRET=jeedomSession yarn start
[2023-10-05 13:20:14][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][On-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:20:26][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][On-1 pompe] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:20:34][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:20:35][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][Off-1 pompe] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:20:40][ERROR] : Erreur exécution de la commande [ZWAVE-JS][30 - FGS224 Piscine Palmier][Off-2 Ecl palmier] : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused
[2023-10-05 13:25:30][ERROR] : Erreur sur la fonction cron du plugin : Echec de la requête HTTP : http://127.0.0.1:55035/publish?apikey=2u4anHBAhMPCjOEBkEZ9nO8Lv3rQ6tyOda4Ndu1LLcyXxS999HOnCpBphQciNVHs cURL error : Failed to connect to 127.0.0.1 port 55035: Connection refused

Mips · Octobre 5, 2023, 11:35

c’est la config et le log plugin-zwavejs
on est sur un problème avec plugin-mqtt2 donc c’est bien la config et les logs de ce dernier qu’il faut

Lemars · Octobre 5, 2023, 11:41

Ben dans le plugin MQTT j’avais tout effacer les logs pour repartir propre

j’ai installé les dépendances

Et j’ai regardé dans les logs : ils restent vide : mqtt2 et mqtt2d meme en lancant le plugin MQTT !

Désolé !

copie de la config du plugin :

Y a un nouveau bouton ? Faut il cliquer comme j’ai fait ?
Capture2

copie des dépendances :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_mqtt2
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://deb.debian.org/debian buster InRelease
Get:2 http://deb.debian.org/debian-security buster/updates InRelease [34.8 kB]
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Get:5 http://deb.debian.org/debian-security buster/updates/main amd64 Packages [547 kB]
Fetched 582 kB in 2s (358 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 php7.3-json : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-ldap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mbstring : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mysql : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-opcache : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-readline : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-snmp : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-soap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xml : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xmlrpc : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-zip : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
[Check Version NodeJS actuelle : v16.20.2 : [  KO  ]
Installation de NodeJS 18
Utilisation du dépot officiel

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

                           SCRIPT DEPRECATION WARNING                    

  
  This script, located at https://deb.nodesource.com/setup_X, used to
  install Node.js is deprecated now and will eventually be made inactive.

  Please visit the NodeSource distributions Github and follow the
  instructions to migrate your repo.
  https://github.com/nodesource/distributions

  The NodeSource Node.js Linux distributions GitHub repository contains
  information about which versions of Node.js and which Linux distributions
  are supported and how to install it.
  https://github.com/nodesource/distributions


                          SCRIPT DEPRECATION WARNING

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

TO AVOID THIS WAIT MIGRATE THE SCRIPT
Continuing in 60 seconds (press Ctrl-C to abort) ...

## Installing the NodeSource Node.js 18.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Confirming "buster" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/buster/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 18.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn


Reading package lists...

Building dependency tree...
Reading state information...
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 php7.3-json : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-ldap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mbstring : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mysql : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-opcache : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-readline : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-snmp : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-soap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xml : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xmlrpc : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-zip : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
[Check Version NodeJS après install : v16.20.2 : [  KO  ] -> relancez les dépendances
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 3
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...

Reading package lists...

Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 php7.3-json : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-ldap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mbstring : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mysql : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-opcache : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-readline : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-snmp : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-soap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xml : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xmlrpc : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-zip : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
[Check Version NodeJS actuelle : v16.20.2 : [  KO  ]
Installation de NodeJS 18
Utilisation du dépot officiel

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

                           SCRIPT DEPRECATION WARNING                    

  
  This script, located at https://deb.nodesource.com/setup_X, used to
  install Node.js is deprecated now and will eventually be made inactive.

  Please visit the NodeSource distributions Github and follow the
  instructions to migrate your repo.
  https://github.com/nodesource/distributions

  The NodeSource Node.js Linux distributions GitHub repository contains
  information about which versions of Node.js and which Linux distributions
  are supported and how to install it.
  https://github.com/nodesource/distributions


                          SCRIPT DEPRECATION WARNING

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

TO AVOID THIS WAIT MIGRATE THE SCRIPT
Continuing in 60 seconds (press Ctrl-C to abort) ...

## Installing the NodeSource Node.js 18.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Confirming "buster" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/buster/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 18.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn


Reading package lists...

Building dependency tree...
Reading state information...
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 php7.3-json : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-ldap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mbstring : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-mysql : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-opcache : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-readline : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-snmp : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-soap : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xml : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-xmlrpc : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
 php7.3-zip : Depends: php7.3-common (= 7.3.31-1~deb10u5) but 7.3.31-1~deb10u4 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution).
[Check Version NodeJS après install : v16.20.2 : [  KO  ] -> relancez les dépendances
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 4
+ cd /var/www/html/core/class/../../plugins/mqtt2/resources/mqtt2d
+ rm -rf node_modules
+ sudo npm install

added 110 packages, and audited 111 packages in 16s

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

found 0 vulnerabilities
+ chown -R www-data:www-data jeedom mqtt2d.js node_modules package-lock.json package.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end mqtt2
+ rm /tmp/jeedom_install_in_progress_mqtt2
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Jeandhom · Octobre 5, 2023, 11:45

Lemars · Octobre 5, 2023, 11:51

Je viens de tester et je n’ose pas aller plus loin :

Jeandhom · Octobre 5, 2023, 11:55

Je ne connais pas docker, mais si c’est comme une VM, il faut que tu sois dans l’environnement de Jeedom.

Jeandhom · Octobre 5, 2023, 11:57

Il doit falloir ajouter un -y dans la commande pour passer la question.

Lemars · Octobre 5, 2023, 12:00

J’ai donc lancé dans Jeedom

sudo apt --fix-broken install -y

c’est en cours

Mips · Octobre 5, 2023, 12:01

Comment / qui a installé le broker mqtt?
car tu as paramétré un « broker distant » donc quelque chose ou quelqu’un à fait l’install ou pas?
et l’ip 192.168.1.2 c’est jeedom ou c’est autre chose?

pourquoi tu parles de docker? je n’ai pas suivi ca, ni vu quelque chose en lien avec docker

Jeandhom · Octobre 5, 2023, 12:03

Mips · Octobre 5, 2023, 12:03

non, désactives l’auto-découverte

Lemars · Octobre 5, 2023, 12:07

merci

et bien j’ai relancé les démendances de MQQT2 et cela ne fonctionne toujours pas

Jeandhom · Octobre 5, 2023, 12:10

Et les logs des dépendances ?

Lemars · Octobre 5, 2023, 12:13

et voici les logs des dépendances :
J’ai supprimer le plugin / installé un nouveau plugin mqtt / install des dépendances que voici :

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_mqtt2
+ echo 1
+ echo 2
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 45 not upgraded.
[Check Version NodeJS actuelle : v16.20.2 : [  KO  ]
Installation de NodeJS 18
Utilisation du dépot officiel

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

                           SCRIPT DEPRECATION WARNING                    

  
  This script, located at https://deb.nodesource.com/setup_X, used to
  install Node.js is deprecated now and will eventually be made inactive.

  Please visit the NodeSource distributions Github and follow the
  instructions to migrate your repo.
  https://github.com/nodesource/distributions

  The NodeSource Node.js Linux distributions GitHub repository contains
  information about which versions of Node.js and which Linux distributions
  are supported and how to install it.
  https://github.com/nodesource/distributions


                          SCRIPT DEPRECATION WARNING

================================================================================
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
================================================================================

TO AVOID THIS WAIT MIGRATE THE SCRIPT
Continuing in 60 seconds (press Ctrl-C to abort) ...

## Installing the NodeSource Node.js 18.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Confirming "buster" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_18.x/dists/buster/Release'

## Adding the NodeSource signing key to your keyring...

+ curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | gpg --dearmor | tee /usr/share/keyrings/nodesource.gpg >/dev/null

## Creating apt sources list file for the NodeSource Node.js 18.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' > /etc/apt/sources.list.d/nodesource.list
+ echo 'deb-src [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x buster main' >> /etc/apt/sources.list.d/nodesource.list

## Running `apt-get update` for you...

+ apt-get update
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...


## Run `sudo apt-get install -y nodejs` to install Node.js 18.x and npm
## You may also need development tools to build native addons:
     sudo apt-get install gcc g++ make
## To install the Yarn package manager, run:
     curl -sL https://dl.yarnpkg.com/debian/pubkey.gpg | gpg --dearmor | sudo tee /usr/share/keyrings/yarnkey.gpg >/dev/null
     echo "deb [signed-by=/usr/share/keyrings/yarnkey.gpg] https://dl.yarnpkg.com/debian stable main" | sudo tee /etc/apt/sources.list.d/yarn.list
     sudo apt-get update && sudo apt-get install yarn


Reading package lists...

Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  nodejs
0 upgraded, 1 newly installed, 0 to remove and 44 not upgraded.
Need to get 28.9 MB of archives.
After this operation, 188 MB of additional disk space will be used.
Get:1 https://deb.nodesource.com/node_18.x buster/main amd64 nodejs amd64 18.17.1-deb-1nodesource1 [28.9 MB]
Fetched 28.9 MB in 2s (16.9 MB/s)
Selecting previously unselected package nodejs.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 50187 files and directories currently installed.)
Preparing to unpack .../nodejs_18.17.1-deb-1nodesource1_amd64.deb ...
Unpacking nodejs (18.17.1-deb-1nodesource1) ...
Setting up nodejs (18.17.1-deb-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
[Check Version NodeJS après install : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 3
+ sudo chmod +x /var/www/html/core/class/../../resources/install_nodejs.sh
+ sudo /var/www/html/core/class/../../resources/install_nodejs.sh
Hit:1 http://deb.debian.org/debian buster InRelease
Hit:2 http://deb.debian.org/debian-security buster/updates InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Hit:4 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...

Reading package lists...

Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.8.2.3).
build-essential is already the newest version (12.6).
lsb-release is already the newest version (10.2019051400).
git is already the newest version (1:2.20.1-2+deb10u8).
0 upgraded, 0 newly installed, 0 to remove and 44 not upgraded.
[Check Version NodeJS actuelle : v18.17.1 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 4
+ cd /var/www/html/core/class/../../plugins/mqtt2/resources/mqtt2d
+ rm -rf node_modules
+ sudo npm install

added 111 packages, and audited 112 packages in 12s

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

found 0 vulnerabilities
+ chown -R www-data:www-data jeedom mqtt2d.js node_modules package-lock.json package.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end mqtt2
+ rm /tmp/jeedom_install_in_progress_mqtt2
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Lemars · Octobre 5, 2023, 12:15

et la tout fonctionne !
Je ne sais pas pourquoi !

J’ai donc supprimer le plugin MQTT / installer a nouveau le plugin

et tout a fonctionner

merci, désolé du dérangement

Jeandhom · Octobre 5, 2023, 4:53

Capture d’écran du 2023-10-05 18-51-22

Tu es trop fort.
Tu ne sais pas pourquoi mais tu as trouvé la solution !!!

system · Octobre 6, 2023, 4:54

Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.