Forum Communauté Jeedom

bonjour à tous,

je viens de tester le shelly 1 pour une porte de garage, sans soucis avec l'application ios mais j'ai un soucis sous jeedom.

Après intégration( sans soucis), erreur:
"Echec de la requête HTTP : http://192.168.86.35/relay/0?turn=off cURL error : Failed to connect to 192.168.86.35 port 80: No route to host"

est -ce que qq'un a ce problème ?

Qu'ai je raté ?

merci

Hello

Tout est OK dans la page santé de Jeedom ?

Pourquoi une telle IP ? Ton jeedom a quoi comme IP ?

Comme dit @lunarok, c'est sûrement un problème de routage. IP, réseau et gw de jeedom ainsi que du Shelly aideront à comprendre ton problème

merci à tous.

je problème venait d'un conflit entre mes 2 réseaux (box et google). J'ai réinstallé shelly et c'est maintenant ok.

Par contre,
je l'ai installé sur un moteur came (porte de garage) en contact sec (I/O en mode momentary et timer auto off après 1s). Pas de soucis.
Mais est il possible d'utiliser le SW ? venant de la carte mère du moteur afin de bénéficier des commandes on et off et status ?

merci

Sur le fil principal Shelly on en a parlé et c'est indiqué dans la doc comment récupérer l'input SW du Shelly 1

oui d'accord, mais pour recevoir l'input de CAME ??

bonjour,

je viens de recevoir mes modules shelly 2.5, et tout fonctionne avec leur app. J'ai acheté le plugin shelly pour ma jeedom SMART sous stretch, mais l'installation des dépendances ne se passe pas bien; quelqu'un peut il m'aider svp.

voila le compte rendu de l'install:

======================================================================
Début de l'installation
--2019-12-08 11:15:03-- https://raw.githubusercontent.com/lunar ... /nodejs.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.120.133
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.120.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1491 (1.5K) [text/plain]
Saving to: ‘dependencies.sh’
0K . 100% 5.45M=0s
2019-12-08 11:15:03 (5.45 MB/s) - ‘dependencies.sh’ saved [1491/1491]
dependencies.sh: 3: [: shelly: unexpected operator
Version actuelle : 4
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://repo.jeedom.com/odroid stable InRelease
Ign:3 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ InRelease
Ign:4 http://ftp.debian.org/debian stretch InRelease
Hit:5 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release
Hit:6 http://ftp.debian.org/debian stretch-updates InRelease
Ign:7 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release.gpg
Ign:8 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Hit:9 http://ftp.debian.org/debian stretch-backports InRelease
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Hit:12 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Ign:8 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Hit:13 http://ftp.debian.org/debian stretch Release
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:8 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Get:8 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages [545 B]
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:10 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Get:14 http://repo.jeedom.com/odroid stable/main arm64 Packages [545 B]
Hit:15 http://www.deb-multimedia.org stretch InRelease
Err:17 https://oph.mdrjr.net/meveric all InRelease
Connection timed out after 120000 milliseconds
Err:18 https://oph.mdrjr.net/meveric stretch InRelease
Connection timed out after 120001 milliseconds
Fetched 545 B in 4min 0s (2 B/s)
Reading package lists...
W: The repository 'http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release' is not signed.
W: No Hash entry in Release file /var/lib/apt/lists/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Release
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Release
W: Conflicting distribution: http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release (expected dists/stable/main/binary-arm64/ but got )
E: Failed to stat /var/lib/apt/lists/partial/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Packages - pkgAcqTransactionItem::TransactionState-stat (2: No such file or directory)
Reading package lists...
Building dependency tree...
Reading state information...
lsb-release is already the newest version (9.20161125).
0 upgraded, 0 newly installed, 0 to remove and 189 not upgraded.
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:
libuv1* nodejs*
0 upgraded, 0 newly installed, 2 to remove and 189 not upgraded.
After this operation, 13.5 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 ... 50756 files and directories currently installed.)
Removing nodejs (4.8.2~dfsg-1) ...
Removing libuv1:arm64 (1.9.1-3) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
dependencies.sh: 37: [: aarch64: unexpected operator
Utilisation du dépot officiel
## Installing the NodeSource Node.js 12.x repo...
## Populating apt-get cache...
+ apt-get update
Hit:1 http://security.debian.org stretch/updates InRelease
Hit:2 http://www.deb-multimedia.org stretch InRelease
Hit:3 http://repo.jeedom.com/odroid stable InRelease
Ign:4 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ InRelease
Ign:5 http://ftp.debian.org/debian stretch InRelease
Hit:6 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release
Hit:7 http://ftp.debian.org/debian stretch-updates InRelease
Ign:8 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release.gpg
Ign:9 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Hit:10 http://ftp.debian.org/debian stretch-backports InRelease
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Hit:13 http://ftp.debian.org/debian stretch-proposed-updates InRelease
Ign:9 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Hit:14 http://ftp.debian.org/debian stretch Release
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:9 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Get:9 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Packages [545 B]
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Ign:11 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en
Ign:12 http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Translation-en_US
Get:15 http://repo.jeedom.com/odroid stable/main arm64 Packages [545 B]
Err:17 https://oph.mdrjr.net/meveric all InRelease
Connection timed out after 120000 milliseconds
Err:18 https://oph.mdrjr.net/meveric stretch InRelease
Connection timed out after 120000 milliseconds
Fetched 545 B in 4min 0s (2 B/s)
Reading package lists...
W: The repository 'http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release' is not signed.
W: No Hash entry in Release file /var/lib/apt/lists/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Release
W: Invalid 'Date' entry in Release file /var/lib/apt/lists/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Release
W: Conflicting distribution: http://repo.jeedom.com/odroid dists/stable/main/binary-arm64/ Release (expected dists/stable/main/binary-arm64/ but got )
E: Failed to stat /var/lib/apt/lists/partial/repo.jeedom.com_odroid_dists_stable_main_binary-arm64_Packages - pkgAcqTransactionItem::TransactionState-stat (2: No such file or directory)
Error executing command, exiting
Reading package lists...
Building dependency tree...
Reading state information...
The following additional packages will be installed:
libuv1
The following NEW packages will be installed:
libuv1 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, 2 newly installed, 0 to remove and 189 not upgraded.
Need to get 0 B/3,248 kB of archives.
After this operation, 13.5 MB of additional disk space will be used.
Selecting previously unselected package libuv1:arm64.
(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 ... 50689 files and directories currently installed.)
Preparing to unpack .../libuv1_1.9.1-3_arm64.deb ...
Unpacking libuv1:arm64 (1.9.1-3) ...
Selecting previously unselected package nodejs.
Preparing to unpack .../nodejs_4.8.2~dfsg-1_arm64.deb ...
Unpacking nodejs (4.8.2~dfsg-1) ...
Setting up libuv1:arm64 (1.9.1-3) ...
Processing triggers for libc-bin (2.24-11+deb9u3) ...
Processing triggers for man-db (2.7.6.1-2) ...
Setting up nodejs (4.8.2~dfsg-1) ...
update-alternatives: using /usr/bin/nodejs to provide /usr/bin/js (js) in auto mode
Version actuelle : v4.8.2
dependencies.sh: 59: dependencies.sh: npm: not found
chown: cannot access 'node_modules': No such file or directory
rm: cannot remove '/tmp/shelly_dep': No such file or directory
Fin de l'installation

Bonjour, ton problème vient du repo jeedom qui a mal été migré, je te conseille de prendre contact avec le support jeedom core afin qu'ils résolvent cela.

Bien à toi

ok merci mais ils risquent de m'envoyer bouler car c'est suite a l'install de shelly plugin, non

Cordialement

CG

Non car c'est du a leur dépôt on te dit.
Si je resume, tu rouvres un fil sans rapport avec ton problème
On te dit quoi faire, mais tu préfères douter et me pourrir d'un mp comme si j'allais y répondre et faire mieux
Merci de respecter les personnes, que ce soit les devs ou les intervenants qui vous repondent

Désolé, j'avais pas vu la 1ere réponse, et comme je n'ai jamais appelé le support jeedom, je m'interrogeais sur la marche a suivre,


Donc ce n'est pas un manque de respect, juste mon incompétence et mon manque d'expérience. encore désolé.

encore merci pour l'aide.