Comments (35)
Bonjour,
le démon ne parvient pas à communiquer avec jeedom.
il y a deux cas qui peuvent causer ce problème :
- jsonrpc qui est désactivé dans la configuration > api de jeedom
- une erreur dans l'un de vos équipement, la seule solution pour résoudre ceci, c'est de tout retirer et ajouter les éqiupements un par un jusqu'à avoir le problème. quand vous l'avez, vous pouvez m'envoyer le log debugInfo "commande" de cet équipement.
from jeedom_docs.
from jeedom_docs.
je ne vois pas vos images
from jeedom_docs.
pouvez-vous aussi décrire votre système ? (ou m'envoyer la première ligne du log homebridge-dep)
from jeedom_docs.
from jeedom_docs.
compliqué, par contre, connectez-vous sur github et ajoutez les images en drag and drop, plutot que par email
from jeedom_docs.
from jeedom_docs.
je voulais juste savoir ceci :
Installation dépendances sur Jeedom 3.3.39 sur Raspbian GNU/Linux 9.4
(stretch)/armhf/armv7l/32bits aka 'RPI 3 B' avec nodeJS et
jsonrpc:enable et homebridge 2020-01-28 13:32:29
pouvez vous poster les images ici en drag and drop :
#6
from jeedom_docs.
voici le message initial avec les captures 👍
Bonjour,
Je vous remercie pour votre réponse.
1- A priori Jsonrpc est activé
2- J'avais déjà pensé à désactiver tous mes équipements un par un (ca m'a
pris un temps fou), mais l'erreur persiste.
puis j'ai désactivé tous les équipements depuis le plugin Homebridge
et de n'en laisser qu'un seul :
et pourtant l'erreur persiste :
Je coince sur ce problème. Je vous remercie par avance pour votre aide.
from jeedom_docs.
pouvez-vous fournir le log homebridge, le log http.error
from jeedom_docs.
et le DebugInfo
from jeedom_docs.
après avoir réparer et réinstaller homebridge:
-
Le log homebridge est vide
-
le log homebridge deamon affiche :
[2/5/2020, 8:56:47 PM] Got SIGTERM, shutting down Homebridge...
[2020-2-5 21:00:11] Loaded config.json with 0 accessories and 1 platforms.
[2020-2-5 21:00:11] ---
[2020-2-5 21:00:14] Loaded plugin: homebridge-alexa
[2020-2-5 21:00:14] Registering platform 'homebridge-alexa.Alexa'
[2020-2-5 21:00:14] ---
[2020-2-5 21:00:16] Loaded plugin: homebridge-camera-ffmpeg
[2020-2-5 21:00:16] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg'
[2020-2-5 21:00:16] ---
[2020-2-5 21:00:16] Loaded plugin: homebridge-jeedom
[2020-2-5 21:00:16] Registering platform 'homebridge-jeedom.Jeedom'
[2020-2-5 21:00:16] ---
[2020-2-5 21:00:16] Loading 1 platforms...
[2020-2-5 21:00:16] [_Repaired_21] Initializing Jeedom platform...
[2020-2-5 21:00:16] [_Repaired_21] debugLevel:400
Load homebridge-camera-ffmpeg.Camera-ffmpeg
Setup Payload:
X-HM://0023ISYWY74AE
Enter this code with your HomeKit app on your iOS device to pair with Homebridge:
┌────────────┐
│ 031-45-154 │
└────────────┘
[2020-2-5 21:00:17] [_Repaired_21] Synchronisation Jeedom <> Homebridge...
[2020-2-5 21:00:17] Homebridge is running on port 51826.
[2020-2-5 21:00:17] [_Repaired_21] [ERROR] #2 Erreur de récupération des données Jeedom: null
- et le log homebridge-dep affiche :
Installation dépendances sur Jeedom 3.3.39 sur Raspbian GNU/Linux 9.4 (stretch)/armhf/armv7l/32bits aka 'RPI 3 B' avec nodeJS et jsonrpc:enable et homebridge 2020-01-28 13:32:29
--0%
--10%
Lancement de l'installation/mise à jour des dépendances homebridge
--20%
Get:1 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Get:2 http://raspbian.raspberrypi.org/raspbian stretch InRelease [15.0 kB]
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Fetched 40.3 kB in 1s (24.8 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
apt-utils is already the newest version (1.4.9).
avahi-daemon is already the newest version (0.6.32-2).
avahi-discover is already the newest version (0.6.32-2).
avahi-utils is already the newest version (0.6.32-2).
build-essential is already the newest version (12.3).
dialog is already the newest version (1.3-20160828-2).
libavahi-compat-libdnssd-dev is already the newest version (0.6.32-2).
libnss-mdns is already the newest version (0.10-8).
lsb-release is already the newest version (9.20161125+rpi1).
0 upgraded, 0 newly installed, 0 to remove and 185 not upgraded.
--30%
Version actuelle :
--40%
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
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 185 not upgraded.
--45%
Utilisation du dépot officielInstalling the NodeSource Node.js 12.x repo...
Populating apt-get cache...
- apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Fetched 25.4 kB in 1s (15.5 kB/s)
Reading package lists...Confirming "stretch" is supported...
- curl -sLf -o /dev/null 'https://deb.nodesource.com/node_12.x/dists/stretch/Release'
Adding the NodeSource signing key to your keyring...
- curl -s https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
Warning: apt-key output should not be parsed (stdout is not a terminal)
OKCreating apt sources list file for the NodeSource Node.js 12.x repo...
- echo 'deb https://deb.nodesource.com/node_12.x stretch main' > /etc/apt/sources.list.d/nodesource.list
- echo 'deb-src https://deb.nodesource.com/node_12.x stretch main' >> /etc/apt/sources.list.d/nodesource.list
Running
apt-get update
for you...
- apt-get update
Hit:1 http://raspbian.raspberrypi.org/raspbian stretch InRelease
Get:2 http://archive.raspberrypi.org/debian stretch InRelease [25.4 kB]
Hit:3 https://deb.nodesource.com/node_12.x stretch InRelease
Fetched 25.4 kB in 1s (16.3 kB/s)
Reading package lists...Run
sudo apt-get install -y nodejs
to install Node.js 12.x and npmYou 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 | sudo apt-key add -
echo "deb 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 185 not upgraded.
Need to get 0 B/15.5 MB of archives.
After this operation, 82.0 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 ... 63722 files and directories currently installed.)
Preparing to unpack .../nodejs_12.14.1-1nodesource1_armhf.deb ...
Unpacking nodejs (12.14.1-1nodesource1) ...
Setting up nodejs (12.14.1-1nodesource1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Version actuelle : v12.14.1
--50%
--60%
Installation de Homebridge...
npm notice created a lockfile as package-lock.json. You should commit this file.
added 235 packages from 182 contributors and audited 1484 packages in 57.189s
15 packages are looking for funding
runnpm fund
for details
found 0 vulnerabilities
--70%
--80%
--90%
--95%
--100%
Installation des dépendances Homebridge terminée, vérifiez qu'il n'y a pas d'erreur
ou puis je trouver le log
from jeedom_docs.
Qui a dit de "réparer" ?
Dans jeedom
from jeedom_docs.
je n'ai pas bien compris, pardon.
Dans homebridge, dans le panneau log et surveille, je clique sur niveau de log : Debug et ensuite ?
from jeedom_docs.
non, c'est un log qui est dans jeedom, tu vas dans Analyse > Logs > http.error
from jeedom_docs.
merci beaucoup pour votre réactivité.
et voici le log de http.error :
kill: (14450): No suc
h process
kill: (14452): No such process
kill: (14548): No such process
kill: (14550): No such process
kill: (14584): No such process
kill: (14586): No such process
kill: (18268): No such process
kill: (18271): No such process
kill: (18267): No such process
kill: (18278): No such process
kill: (18281): No such process
kill: (18323): No such process
kill: (18325): No such process
kill: (18322): No such process
kill: (18329): No such process
kill: (18331): No such process
kill: (26410): No such process
kill: (26412): No such process
kill: (26425): No such process
kill: (26427): No such process
kill: (26464): No such process
kill: (26466): No such process
kill: (26463): No such process
kill: (26470): No such process
kill: (26477): No such process
kill: (26482): No such process
kill: (26484): No such process
kill: (28609): No such process
kill: (28611): No such process
kill: (28619): No such process
kill: (28621): No such process
kill: (28663): No such process
kill: (28665): No such process
kill: (28662): No such process
kill: (28669): No such process
kill: (28671): No such process
kill: (12279): No such process
kill: (12281): No such process
kill: (12333): No such process
kill: (12335): No such process
kill: (12354): No such process
kill: (12356): No such process
kill: (12382): No such process
kill: (12384): No such process
kill: (12469): No such process
kill: (12471): No such process
kill: (12507): No such process
kill: (12509): No such process
kill: (3244): No such process
kill: (3247): No such process
kill: (3294): No such process
kill: (3296): No such process
kill: (3318): No such process
kill: (3320): No such process
kill: (3345): No such process
kill: (3347): No such process
kill: (3433): No such process
kill: (3435): No such process
kill: (3471): No such process
kill: (3473): No such process
kill: (4574): No such process
kill: (4576): No such process
kill: (4634): No such process
kill: (4636): No such process
kill: (4655): No such process
kill: (4657): No such process
kill: (4685): No such process
kill: (4688): No such process
kill: (6173): No such process
kill: (6175): No such process
kill: (6218): No such process
kill: (6220): No such process
kill: (6242): No such process
kill: (6244): No such process
kill: (6269): No such process
kill: (6272): No such process
kill: (6436): No such process
kill: (6438): No such process
kill: (6476): No such process
kill: (6478): No such process
kill: (6592): No such process
kill: (6594): No such process
kill: (10289): No such process
kill: (10291): No such process
kill: (10338): No such process
kill: (10340): No such process
kill: (10360): No such process
kill: (10362): No such process
kill: (10394): No such process
kill: (10396): No such process
kill: (10481): No such process
kill: (10483): No such process
kill: (10518): No such process
kill: (10520): No such process
cat: '/sys/class/input/event?/device/name': No such file or directory
kill: (23338): No such process
kill: (23340): No such process
kill: (23387): No such process
kill: (23389): No such process
kill: (23409): No such process
kill: (23411): No such process
kill: (23438): No such process
kill: (23440): No such process
kill: (23525): No such process
kill: (23527): No such process
kill: (23567): No such process
kill: (23569): No such process
kill: (25635): No such process
kill: (25638): No such process
kill: (25634): No such process
kill: (25648): No such process
kill: (25651): No such process
kill: (25730): No such process
kill: (25732): No such process
kill: (25737): No such process
kill: (25739): No such process
kill: (29504): No such process
kill: (29506): No such process
kill: (29549): No such process
kill: (29551): No such process
kill: (29573): No such process
kill: (29575): No such process
kill: (29606): No such process
kill: (29608): No such process
kill: (30203): No such process
kill: (30205): No such process
kill: (30254): No such process
kill: (30256): No such process
kill: (30282): No such process
kill: (30284): No such process
kill: (30309): No such process
kill: (30311): No such process
kill: (30845): No such process
kill: (30847): No such process
kill: (30898): No such process
kill: (30901): No such process
kill: (30921): No such process
kill: (30923): No such process
kill: (30959): No such process
kill: (30961): No such process
kill: (31048): No such process
kill: (31050): No such process
kill: (31086): No such process
kill: (31088): No such process
kill: (722): No such process
kill: (726): No such process
kill: (743): No such process
kill: (745): No such process
kill: (802): No such process
kill: (804): No such process
kill: (801): No such process
kill: (808): No such process
kill: (810): No such process
kill: (3859): No such process
kill: (3861): No such process
kill: (3875): No such process
kill: (3877): No such process
kill: (3917): No such process
kill: (3919): No such process
kill: (3916): No such process
kill: (3923): No such process
kill: (3925): No such process
kill: (6795): No such process
kill: (6797): No such process
kill: (4169): No such process
kill: (4171): No such process
kill: (6794): No such process
kill: (6804): No such process
kill: (6806): No such process
kill: (6849): No such process
kill: (6852): No such process
kill: (6855): No such process
kill: (6857): No such process
kill: (10608): No such process
kill: (10610): No such process
kill: (10620): No such process
kill: (10622): No such process
kill: (10662): No such process
kill: (10664): No such process
kill: (10661): No such process
kill: (10668): No such process
kill: (10670): No such process
kill: (7950): No such process
kill: (7953): No such process
kill: (8023): No such process
kill: (8025): No such process
kill: (8039): No such process
kill: (8041): No such process
kill: (8081): No such process
kill: (8083): No such process
kill: (8165): No such process
kill: (8167): No such process
kill: (8215): No such process
kill: (8217): No such process
kill: (15745): No such process
kill: (15747): No such process
kill: (15752): No such process
kill: (15754): No such process
kill: (15803): No such process
kill: (15805): No such process
kill: (15802): No such process
kill: (15812): No such process
kill: (15814): No such process
kill: (15880): No such process
kill: (15882): No such process
kill: (15926): No such process
kill: (15928): No such process
kill: (16733): No such process
kill: (16735): No such process
kill: (16053): No such process
kill: (16732): No such process
kill: (16743): No such process
kill: (16745): No such process
kill: (16797): No such process
kill: (16799): No such process
kill: (16796): No such process
kill: (16804): No such process
kill: (16806): No such process
kill: (27576): No such process
kill: (27578): No such process
kill: (27640): No such process
kill: (27642): No such process
kill: (27663): No such process
kill: (27665): No such process
kill: (27698): No such process
kill: (27700): No such process
kill: (27793): No such process
kill: (27795): No such process
kill: (27837): No such process
kill: (27839): No such process
kill: (1487): No such process
kill: (1489): No such process
kill: (1545): No such process
kill: (1547): No such process
kill: (1567): No such process
kill: (1569): No such process
kill: (1605): No such process
kill: (1607): No such process
kill: (1719): No such process
kill: (1721): No such process
kill: (1764): No such process
kill: (1766): No such process
kill: (1886): No such process
kill: (1888): No such process
kill: (8689): No such process
kill: (8691): No such process
kill: (8747): No such process
kill: (8749): No such process
kill: (8769): No such process
kill: (8771): No such process
kill: (8805): No such process
kill: (8807): No such process
kill: (8903): No such process
kill: (8905): No such process
kill: (8949): No such process
kill: (8951): No such process
kill: (23317): No such process
kill: (23319): No such process
kill: (23373): No such process
kill: (23375): No such process
kill: (23395): No such process
kill: (23397): No such process
kill: (23431): No such process
kill: (23433): No such process
kill: (23524): No such process
kill: (23526): No such process
kill: (23579): No such process
kill: (23581): No such process
kill: (24103): No such process
kill: (24105): No such process
kill: (24159): No such process
kill: (24161): No such process
kill: (24182): No such process
kill: (24184): No such process
kill: (24222): No such process
kill: (24224): No such process
kill: (24626): No such process
kill: (24628): No such process
kill: (24738): No such process
kill: (24740): No such process
kill: (24764): No such process
kill: (24768): No such process
kill: (24826): No such process
kill: (24828): No such process
[Sun Oct 06 23:26:00.107387 2019] [:error] [pid 23856] [client 192.168.1.1:65425] PHP Fatal error: Uncaught Error: Class 'connection' not found in /var/www/html/plugins/blink1/core/php/watch.php:17
Stack trace:
#0 {main}
thrown in /var/www/html/plugins/blink1/core/php/watch.php on line 17
[Sun Oct 06 23:26:04.774938 2019] [:error] [pid 6342] [client 192.168.1.1:65438] PHP Fatal error: Uncaught Error: Class 'connection' not found in /var/www/html/plugins/blink1/core/php/watch.php:17
Stack trace:
#0 {main}
thrown in /var/www/html/plugins/blink1/core/php/watch.php on line 17
[Sun Oct 06 23:27:46.350536 2019] [:error] [pid 22209] [client 192.168.1.1:49175] PHP Fatal error: Uncaught Error: Class 'connection' not found in /var/www/html/plugins/blink1/core/php/watch.php:17
Stack trace:
#0 {main}
thrown in /var/www/html/plugins/blink1/core/php/watch.php on line 17
[Sun Oct 06 23:27:49.150598 2019] [:error] [pid 23856] [client 192.168.1.1:49176] PHP Fatal error: Uncaught Error: Class 'connection' not found in /var/www/html/plugins/blink1/core/php/watch.php:17
Stack trace:
#0 {main}
thrown in /var/www/html/plugins/blink1/core/php/watch.php on line 17
kill: (17059): No such process
kill: (17061): No such process
kill: (17119): No such process
kill: (17121): No such process
kill: (17137): No such process
kill: (17139): No such process
kill: (17178): No such process
kill: (17180): No such process
kill: (17262): No such process
kill: (17264): No such process
kill: (17266): No such process
kill: (17318): No such process
kill: (17320): No such process
warning: commands will be executed using /bin/sh
job 26 at Sat Nov 2 20:07:00 2019
warning: commands will be executed using /bin/sh
job 27 at Sat Nov 2 20:29:00 2019
warning: commands will be executed using /bin/sh
job 28 at Sat Nov 2 20:55:00 2019
warning: commands will be executed using /bin/sh
job 29 at Sat Nov 2 21:01:00 2019
warning: commands will be executed using /bin/sh
job 30 at Sat Nov 2 21:16:00 2019
ls: cannot access '/var/www/html/plugins/homebridge/desktop/modal/../../resources/homebridge/persist/': No such file or directory
warning: commands will be executed using /bin/sh
job 31 at Mon Nov 4 22:38:00 2019
[Sat Dec 21 13:17:13.233520 2019] [mpm_prefork:notice] [pid 579] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Sat Dec 21 13:17:13.234923 2019] [core:notice] [pid 579] AH00094: Command line: '/usr/sbin/apache2'
[Mon Dec 23 16:03:35.350214 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagecreatefrompng(http://chart.apis.google.com/chart?cht=qr&chld=H|0&chs=100x100&chl=X-HM%3A%2F%2F0023ISYWY9EFE): failed to open stream: HTTP request failed! HTTP/1.0 502 Bad Gateway
in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 17, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357224 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagesx() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 20, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357332 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagesy() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 21, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357374 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: Division by zero in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 27, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357416 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagecopyresampled() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 30, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357455 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagepng() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 32, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Mon Dec 23 16:03:35.357491 2019] [:error] [pid 1947] [client 37.71.75.151:32193] PHP Warning: imagedestroy() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 33, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
warning: commands will be executed using /bin/sh
job 32 at Mon Dec 23 16:06:00 2019
warning: commands will be executed using /bin/sh
job 33 at Mon Dec 23 16:09:00 2019
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
[Mon Dec 23 17:16:08.674018 2019] [mpm_prefork:notice] [pid 579] AH00169: caught SIGTERM, shutting down
[Mon Dec 23 17:16:13.768624 2019] [mpm_prefork:notice] [pid 23694] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Dec 23 17:16:13.768923 2019] [core:notice] [pid 23694] AH00094: Command line: '/usr/sbin/apache2'
[Mon Dec 23 17:17:33.522485 2019] [mpm_prefork:notice] [pid 23694] AH00169: caught SIGTERM, shutting down
[Mon Dec 23 17:17:49.768828 2019] [mpm_prefork:notice] [pid 574] AH00163: Apache/2.4.25 (Raspbian) configured -- resuming normal operations
[Mon Dec 23 17:17:49.778673 2019] [core:notice] [pid 574] AH00094: Command line: '/usr/sbin/apache2'
[Tue Feb 04 22:14:45.161244 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagecreatefrompng(http://chart.apis.google.com/chart?cht=qr&chld=H|0&chs=100x100&chl=X-HM%3A%2F%2F0023ISYWYA312): failed to open stream: HTTP request failed! HTTP/1.0 502 Bad Gateway
in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 17, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170656 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagesx() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 20, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170777 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagesy() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 21, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170818 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: Division by zero in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 27, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170861 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagecopyresampled() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 30, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170947 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagepng() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 32, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
[Tue Feb 04 22:14:45.170983 2020] [:error] [pid 28617] [client 192.168.1.1:53151] PHP Warning: imagedestroy() expects parameter 1 to be resource, boolean given in /var/www/html/plugins/homebridge/3rdparty/genQR.php on line 33, referer: http://86.73.45.21:8585/index.php?v=d&m=homebridge&p=homebridge
sh: 1: nodejs: not found
warning: commands will be executed using /bin/sh
job 36 at Tue Feb 4 22:58:00 2020
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
libpng warning: Interlace handling should be turned on when using png_read_image
sh: 1: nodejs: not found
warning: commands will be executed using /bin/sh
job 37 at Wed Feb 5 09:48:00 2020
sh: 1: nodejs: not found
warning: commands will be executed using /bin/sh
job 38 at Wed Feb 5 12:20:00 2020
sh: 1: nodejs: not found
warning: commands will be executed using /bin/sh
job 39 at Wed Feb 5 20:57:00 2020
from jeedom_docs.
aucune information intéressante non plus...
bon, désactivez toutes les pieces sauf une avec un seul équipement (simple type prise) dedans.
from jeedom_docs.
mais envoyez moi aussi le DebugInfo (voir doc), il me semble que vous ne me l'avez pas envoyé
from jeedom_docs.
Bonjour,
C'est déjà le cas. Cf les captues suivantes :
from jeedom_docs.
non, relisez-moi, déplacez les autres équipements.
créez Salon2 et déplacez temporairement les autres équipements dedans
from jeedom_docs.
J'ai créé une pièce Salon2, dans laquelle j'ai mis 1 seul équipement (micromodule fibaro pour volet roulant)
j'ai désactivé toutes les autres pièces et composants des autres pièces:
tout l'erreur
Pour avoir les logs en debug, j'ai modifier le niveau de log dans la page de configuration.
j'ai vidé les logs, pour dans homebridge réparé et réinstallé pour reinitialiser le plugin:
voici les logs :
sh: 1: nodejs: not found
warning: commands will be executed using /bin/sh
job 40 at Thu Feb 6 18:09:00 2020
from jeedom_docs.
Mais enfin pourquoi avez vous à nouveau "réparer et réinstallé" ???
Que voulez vous dire par "tout l'erreur" ?
Avez vous testé avec justement un autre équipement dans la pièce activée ? D'activer une autre pièce et de désactiver celle là ?
from jeedom_docs.
Pardon, il fallait lire à la place de de "tout l'erreur", "tous les autres composants".
j'avais la tête dans un autre message à ce moment.
pourquoi cliquer sur "réparer et réinstaller", justement pour réparer et réinstaller après avoir fait des modifications. Vu que je n'arrive pas à faire fonctionner le plugin, je tente cela.
Je n'arrive pas à trouver la source du pb
from jeedom_docs.
justement ... c'est pour ca qu'il faut m'écouter ;) avez vous fait ce que j'ai proposé dans ma dernière phrase ?
from jeedom_docs.
Oui j'ai essayé .
Faut il redémarrer le daemon à chaque essai ?
from jeedom_docs.
Oui pour identifier à partir de quel périphérique ça fonctionne... et donc le fautif
from jeedom_docs.
lorsque j'avais installé homebridge, j'avais plusieurs micromodule fibaro (pour controler volets roulants et portail).
Homebridge fonctionnait correctement et je pouvais controler les composants depuis siri.
Brusquement ca s'est arreté de fonctionner.
Depuis, j'ai réorganiser mes composants en pièces, installé de nouveaux plugins, etc.
lors du lancement du daemon, l'erreur dans homebridge-dep est la suivante :
[2/6/2020, 11:56:04 PM] [_Repaired_2] [ERROR] #2 Erreur de récupération des données Jeedom: null
Comme vous me l'avez conseillé au départ, j'ai désactiver un à un tous les composants, puis redémarrer le daemon de homebridge, mais rien à faire, l'erreur est toujours présente.
j'ai suivi vos autres recommandations, d'isoler le composant dans une seule pièce et de désactiver les autres, etc.
toujours meme problème.
souhaitez vous vous connecter en teamviewer sur mon poste pour regarder directement ?
from jeedom_docs.
from jeedom_docs.
Resolu : équipement virtuel buggé
from jeedom_docs.
from jeedom_docs.
Bonjour,
resauvegarder le virtuel, c'est ce que j'avais fait la dernière fois.
et identifier lequel
from jeedom_docs.
Bonjour,
Allez, en pleine période de confinement pendant l'épidémie, je me replonge dans la domotique.
Le problème est surement différent de celui de la dernière fois.
Voici l'erreur qui s'écrit dans homebridge_deamon :
[3/15/2020, 11:23:08 AM] Loaded config.json with 0 accessories and 1 platforms. [3/15/2020, 11:23:08 AM] --- [3/15/2020, 11:23:11 AM] Loaded plugin: homebridge-alexa [3/15/2020, 11:23:11 AM] Registering platform 'homebridge-alexa.Alexa' [3/15/2020, 11:23:11 AM] --- [3/15/2020, 11:23:13 AM] Loaded plugin: homebridge-camera-ffmpeg [3/15/2020, 11:23:13 AM] Registering platform 'homebridge-camera-ffmpeg.Camera-ffmpeg' [3/15/2020, 11:23:13 AM] --- [3/15/2020, 11:23:13 AM] Loaded plugin: homebridge-jeedom [3/15/2020, 11:23:13 AM] Registering platform 'homebridge-jeedom.Jeedom' [3/15/2020, 11:23:13 AM] --- [3/15/2020, 11:23:13 AM] Loading 1 platforms... [3/15/2020, 11:23:13 AM] [jeedom_Repaired_26] Initializing Jeedom platform... [3/15/2020, 11:23:13 AM] [jeedom_Repaired_26] debugLevel:400 Load homebridge-camera-ffmpeg.Camera-ffmpeg Setup Payload: X-HM://0023ISYWY740F Enter this code with your HomeKit app on your iOS device to pair with Homebridge: ┌────────────┐ │ 031-45-154 │ └────────────┘ [3/15/2020, 11:23:13 AM] [jeedom_Repaired_26] Synchronisation Jeedom <> Homebridge... [3/15/2020, 11:23:13 AM] Homebridge is running on port 51826. [3/15/2020, 11:25:26 AM] [jeedom_Repaired_26] [ERROR] #2 Erreur de récupération des données Jeedom: Error: connect ETIMEDOUT 192.168.0.126:80 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16) { errno: 'ETIMEDOUT', code: 'ETIMEDOUT', syscall: 'connect', address: '192.168.0.126', port: 80 } Error: connect ETIMEDOUT 192.168.0.126:80 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1137:16)
Souhaitez-vous que je créé une autre issue pour ce sujet ?
from jeedom_docs.
from jeedom_docs.
Génial, vous avez trouvé la solution. En effet, cette ip ne correspondait à rien, et suite à un reboot tout est rentré dans l'ordre.
from jeedom_docs.
from jeedom_docs.
Related Issues (20)
- accesoires ne repondent pas HOT 1
- Démon Homebridge ne démarre pas HOT 7
- Homebridge dependencies NOK HOT 11
- Impossible de faire parler l'enceinte HOT 1
- Plugin incompatible HOT 2
- Pb avec le plugin Homebridge HOT 6
- Synchroniser les modules déjà présent dans homebridge HOT 1
- plugins/homebridge/resources/node_modules est inclus dans tous les backups jeedom HOT 2
- Impossible d'installer les dépendances dans homebridge
- Impossible de fonctionner Xiaomi talk si Jeedom full HTTPS HOT 1
- Event ALARM INACTIVE are never received from NVR on each event HOT 1
- Dependance installation issuer HOT 1
- Disparition du plugin hkControl HOT 11
- Volet sous hkControl HOT 8
- Erreur homebridge HOT 4
- Erreur NodJS XiaomiTalk HOT 8
- Impossible d'integrer homebridge dans maison HOT 15
- GMP n'est pas bien installé, relancez vos dépendances HOT 1
- Impossible d'appairer une connectivity kit box somfy HOT 1
- Attention : Vous êtes en Debian 10 Buster, ce système est déprecié ! Merci de mettre à jour votre distribution !!! HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from jeedom_docs.