Statut Démon toujours NOK

Plugins Passerelle domotique
1

Bonjour à tous et bonne année.
Après une panne de Jeedom (carte µSD H.S.) j’ai réinstallé ESPEasy mais le démon « statut » passe à OK pendant 10 s puis repasse à NOK définitivement ! Ai-je fait une erreur d’installation ? Merci pour une aide

2

Bonjour,

Il est impossible de savoir, nous n’avons pas accès à votre jeedom donc il faut fournir des infos pour que l’on puisse avoir une chance de voir ce qu’il se passe.

Au minimum:

  • capture écran page santé jeedom
  • capture écran page config plugin
  • tous les logs du plugin
3

Bonsoir, je vous joint le commentaire du Espeasy_node qui n’arrive pas à communiquer avec le 169.254.128.138.
Cordialement.
Jccnc85
"Error:listen EADDRNOTAVAIL:adress not avaible 169.254.128.138:8121

4

Bonjour,

Mais du coup, ça n’a plus rien à voir avec le le status du daemon ??? Si ?

Sinon, tu as donc la réponse, Jeedom n’arrive pas à communiquer avec ton esp: Mauvaise adresse, mauvaise configuration de l’esp, mauvaise configuration réseau … impossible de savoir avec si peu d’information.

(Petite analogie:

  • Bonjour Mr Darty, ma machine à laver est en panne.
  • Darty: OK, donnez mio du détail sur la panne
    Et 4jours plus tard,
  • j’ai une chaussette rouge dans ma machine. Aidez moi !
    => Tout ça pour dire que sans information ou avec des informations changeantes, vu qu’on ne vit pas dans la même maison, impossible de savoir ce qui se passe chez toi avec si peu de détail))
5

Bonjour

Cette adresse est auto assignée et est visible lorsque le serveur dhcp n’a pas répondu. Pour comprendre ce système, je t’invite à faire une petite recherche sur les adressses apipa.
Mise à part ce point, et comme il a été dit, tu ne donnes pas assez d’infos pour qu’on puisse t’aider correctement

6

Bonjour Monsieur.
Je vous remercie pour vous être penché sur mon problème.
Deux précisions : Je suis un ancien professeur d’électronique « analogique » mais je suis néophyte en réseaux et ce trouble est aussi en coïncidence avec le passage d’une livebox Orange 3306 en 22A 0 (fibre optique).
Aussi, je ne sais pas rechercher une adresse apipa et si oui comment la modifier ou passer outre.
Cordialement.
Jccnc

7

PS : comment fait-on pour vous envoyer une copie d’écran ?
Cordialement.
Jccnc

8

copier / faire la capture et ensuite coller dans l’éditeur, l’image sera automatiquement chargée et insérée.

ou utiliser ce bouton:
image

9

Bonjour Monsieur.
Je vous remercie pour les renseignements et je vais tenter de vous envoyer les documents demandés.

image
image1920×1080 254 KB

image
image1920×1080 243 KB
.
Cordialement.
Jccnc

10

Il faudrait en plus les log espeasy (juste au dessus des log espeasy_node)

11

Est-ce cette page ?

image
image1920×1080 286 KB

12

Non.
1- Passer le niveau de log en debug
2- Redémarrer le daemon
3- Ouvrir les logs Espeasy

image
image758×512 28.9 KB

4- Les copier coller dans cette discussion en utilisant les balises adéquates
image

13

Je vous remercie de passer tant de temps sur mon problème.

ESPeasy

[2024-01-19 17:37:54][ERROR] : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé 
plus de 3 fois consécutivement
[2024-01-19 17:39:49][ERROR] : Attention je pense qu'il y a un soucis avec le démon que j'ai relancé plus de 3 fois consécutivement

ESPeasy_node

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121
}

Node.js v18.19.0
Server running
node:events:495
      throw er; // Unhandled 'error' event
      ^

Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121
    at Server.setupListenHandle [as _listen2] (node:net:1800:21)
    at listenInCluster (node:net:1865:12)
    at doListen (node:net:2014:7)
    at process.processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on Server instance at:
    at emitErrorNT (node:net:1844:8)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: 'EADDRNOTAVAIL',
  errno: -99,
  syscall: 'listen',
  address: '169.254.128.138',
  port: 8121




Node.js v18.19.0

ESPeasy_dep

Début de l'installation
--2023-12-28 16:56:45--  https://raw.githubusercontent.com/lunarok/jeedom_nodejs/master/nodejs.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 2606:50c0:8003::154, 2606:50c0:8002::154, 2606:50c0:8000::154, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|2606:50c0:8003::154|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1554 (1.5K) [text/plain]
Saving to: 'dependencies.sh'

     0K .                                                     100% 4.29M=0s

2023-12-28 16:56:45 (4.29 MB/s) - 'dependencies.sh' saved [1554/1554]

dependencies.sh: 3: [: espeasy: unexpected operator
Version actuelle : 14
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Get:3 https://deb.nodesource.com/node_14.x buster InRelease [4584 B]
Fetched 4584 B in 1s (3446 B/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (10.2019051400+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 343 not upgraded.
dependencies.sh: 29: dependencies.sh: [[: not found
KO, version obsolète à upgrader
Suppression du Nodejs existant et installation du paquet recommandé
Reading package lists...
Building dependency tree...
Reading state information...
Package 'npm' is not installed, so not removed
The following packages will be REMOVED:
  nodejs*
0 upgraded, 0 newly installed, 1 to remove and 343 not upgraded.
After this operation, 115 MB disk space will be freed.
(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 ... 112688 files and directories currently installed.)
Removing nodejs (14.21.3-deb-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
dependencies.sh: 38: [: armv7l: unexpected operator
Utilisation du dépot officiel

================================================================================
================================================================================

                              DEPRECATION WARNING                            

  Node.js 14.x is no longer actively supported!

  You will not receive security or critical stability updates for this version.

  You should migrate to a supported version of Node.js as soon as possible.
  Use the installation script that corresponds to the version of Node.js you
  wish to install. e.g.

   * https://deb.nodesource.com/setup_16.x — Node.js 16 "Gallium"
   * https://deb.nodesource.com/setup_18.x — Node.js 18 LTS "Hydrogen" (recommended)
   * https://deb.nodesource.com/setup_19.x — Node.js 19 "Nineteen"
   * https://deb.nodesource.com/setup_20.x — Node.js 20 "Iron" (current)

  Please see https://github.com/nodejs/Release for details about which
  version may be appropriate for you.

  The NodeSource Node.js distributions repository contains
  information both about supported versions of Node.js and supported Linux
  distributions. To learn more about usage, see the repository:
    https://github.com/nodesource/distributions

================================================================================
================================================================================

Continuing in 20 seconds ...


================================================================================
â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“â–“
================================================================================

                           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 14.x repo...


## Populating apt-get cache...

+ apt-get update
Hit:1 http://archive.raspberrypi.org/debian buster InRelease
Get:2 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Get:3 https://deb.nodesource.com/node_14.x buster InRelease [4584 B]
Fetched 19.6 kB in 1s (16.4 kB/s)
Reading package lists...

## Confirming "buster" is supported...

+ curl -sLf -o /dev/null 'https://deb.nodesource.com/node_14.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 14.x repo...

+ echo 'deb [signed-by=/usr/share/keyrings/nodesource.gpg] https://deb.nodesource.com/node_14.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_14.x buster main' >> /etc/apt/sources.list.d/nodesource.list

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

+ apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian buster InRelease
Get:2 https://deb.nodesource.com/node_14.x buster InRelease [4584 B]
Hit:3 http://archive.raspberrypi.org/debian buster InRelease
Fetched 4584 B in 1s (3969 B/s)
Reading package lists...

## Run `sudo apt-get install -y nodejs` to install Node.js 14.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
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
debconf: unable to initialize frontend: Readline
debconf: (This frontend requires a controlling tty.)
debconf: falling back to frontend: Teletype
dpkg-preconfigure: unable to re-open stdin: 
0 upgraded, 1 newly installed, 0 to remove and 343 not upgraded.
Need to get 0 B/23.3 MB of archives.
After this operation, 115 MB of additional disk space will be used.
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 ... 107770 files and directories currently installed.)
Preparing to unpack .../nodejs_14.21.3-deb-1nodesource1_armhf.deb ...
Unpacking nodejs (14.21.3-deb-1nodesource1) ...
Setting up nodejs (14.21.3-deb-1nodesource1) ...
Processing triggers for man-db (2.8.5-2) ...
ln: failed to create symbolic link '/usr/bin/nodejs': File exists
Version actuelle : v14.21.3
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
added 48 packages from 58 contributors and audited 48 packages in 10.924s

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

found 2 moderate severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details
Fin de l'installation

ESPeasy_packages

+ echo '*******************Begin of package installation******************'
*******************Begin of package installation******************
+ touch /tmp/jeedom_install_in_progress_espeasy
+ 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
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro InRelease
Fetched 15.0 kB in 1s (11.3 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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
The following package was automatically installed and is no longer required:
  chromium-codecs-ffmpeg-extra
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 321 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  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://archive.raspberrypi.org/debian buster InRelease
Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:3 https://deb.nodesource.com/node_18.x nodistro 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).
git is already the newest version (1:2.20.1-2+deb10u8).
lsb-release is already the newest version (10.2019051400+rpi1).
The following package was automatically installed and is no longer required:
  chromium-codecs-ffmpeg-extra
Use 'sudo apt autoremove' to remove it.
0 upgraded, 0 newly installed, 0 to remove and 321 not upgraded.
[Check Version NodeJS actuelle : v18.19.0 : [  OK  ]
[Check Prefix : /usr and sudo prefix : /usr and www-data prefix : /usr : [  OK  ]
+ echo 4
+ cd /var/www/html/core/class/../../plugins/espeasy/resources
+ rm -rf node_modules
+ sudo npm install
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

added 48 packages, and audited 49 packages in 10s

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

2 moderate severity vulnerabilities

Some issues need review, and may require choosing
a different dependency.

Run `npm audit` for details.
+ chown -R www-data:www-data espeasy.js node_modules package-lock.json package.json
+ echo 5
+ php /var/www/html/core/class/../php/jeecli.php plugin dependancy_end espeasy
+ rm /tmp/jeedom_install_in_progress_espeasy
+ echo '*******************End of package installation******************'
*******************End of package installation******************

Bien cordialement.

JCCNC

14

Dans ta page santé, je vois que la configuration réseau interne n’est pas configurée.
Et dans la page du plugin ESPeasy, que l’IP à saisir est 169.254.128.138. Or ça devrait etre l’IP de ton Jeedom. Ce qui confirmerait que soit ton jeedom n’est pas connecté à ton réseau, soit il est mal configuré.

Dans ton log ESPeasy_Node, l’erreur est que le plugin tente des communications sur cette adresse par défaut qui n’est pas lié à ton réseau:
Error: listen EADDRNOTAVAIL: address not available 169.254.128.138:8121

Il faut donc renseigner la configuration réseau:
Réglage-> Système->Réseaux

image
image1608×277 25.9 KB

1 « J'aime »
15

@bad pointe son nez…

Bonjour, l’IP a saisir dans l’accès interne est 192.168.1.11, d’après les captures d’écran précédentes.

16

Bien joué inspecteur, j’avais pas vu cet indice dans la barre d’adresse :slight_smile:

1 « J'aime »
17

Bonjour Messieurs
Je tiens à vous remercier pour vos conseils. Je les ai suivis à la lettre et tout refonctionne à merveille !
Le statut du démon est repassé à OK et j’ai pu remonter 4 Wemos programmés avec ESPEasy.
Encore merci pour votre temps passé et votre savoir.
Cordialement.
Jccnc

18

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