Erreur JeeZigBee

Bonsoir à tous,
Je ne m’en sors pas… malgré un nombre impressionnant de topics sur le sujet.
J’ai installé mqtt manager qui semble opérationnel et là je bloque sur une relance incessante du daemon z2m… :confused:
Je m’en remets à vous.
Je vous donne les infos qui semblent à la lecture des topics nécessaires :




logs z2md me renvoie

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-01-11T18_35_11_953Z-debug-0.log
npm WARN invalid config prefix=true set in command line options
npm WARN invalid config Must be valid filesystem path
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path /var/www/package.json
npm ERR! errno -2
npm ERR! enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/var/www/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2024-01-11T18_40_07_292Z-debug-0.log

je suis donc aller voir le log complet dans /root/.npm

 verbose cli /usr/bin/node /usr/bin/npm
1 info using npm@10.2.3
2 info using node@v18.19.0
3 timing npm:load:whichnode Completed in 4ms
4 timing config:load:defaults Completed in 9ms
5 timing config:load:file:/usr/lib/node_modules/npm/npmrc Completed in 1ms
6 timing config:load:builtin Completed in 3ms
7 warn invalid config prefix=true set in command line options
8 warn invalid config Must be valid filesystem path
9 timing config:load:cli Completed in 18ms
10 timing config:load:env Completed in 1ms
11 timing config:load:file:/var/www/.npmrc Completed in 0ms
12 timing config:load:project Completed in 5ms
13 timing config:load:file:/root/.npmrc Completed in 6ms
14 timing config:load:user Completed in 8ms
15 timing config:load:file:/usr/etc/npmrc Completed in 1ms
16 timing config:load:global Completed in 1ms
17 timing config:load:setEnvs Completed in 5ms
18 timing config:load Completed in 52ms
19 timing npm:load:configload Completed in 53ms
20 timing config:load:flatten Completed in 14ms
21 timing npm:load:mkdirpcache Completed in 38ms
22 timing npm:load:mkdirplogs Completed in 3ms
23 verbose title npm start
24 verbose argv "start" "--prefix"
25 timing npm:load:setTitle Completed in 4ms
26 timing npm:load:display Completed in 9ms
27 verbose logfile logs-max:10 dir:/root/.npm/_logs/2024-01-11T18_35_11_953Z-
28 verbose logfile /root/.npm/_logs/2024-01-11T18_35_11_953Z-debug-0.log
29 timing npm:load:logFile Completed in 43ms
30 timing npm:load:timers Completed in 0ms
31 timing npm:load:configScope Completed in 1ms
32 timing npm:load Completed in 253ms
33 timing command:run-script Completed in 13ms
34 timing command:start Completed in 59ms
35 verbose stack Error: Could not read package.json: Error: ENOENT: no such file or directory, open '/var/www/package.json'
36 verbose cwd /var/www
37 verbose Linux 5.10.103-v7+
38 verbose node v18.19.0
39 verbose npm  v10.2.3
40 error code ENOENT
41 error syscall open
42 error path /var/www/package.json
43 error errno -2
44 error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '/var/www/package.json'
45 error enoent This is related to npm not being able to find a file.
45 error enoent

relancer les dépendances

2 « J'aime »

Il semble que le problème soit déjà produit et corrigé ici mais je n’en suis pas sûr…

Merci @Furaxworld je relance !

@Furaxworld Je pense que ça a fait le taf…
Merci beaucoup !!

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