Bonjour,
Pouvez-vous beta tester le plugin wifilightV2 sur la partie TP-link (Tapo et Kasa)
Si vous avez des périphériques Kasa ou Tapo :
Merci!
Oui moi kasa prise tplink h110.
Je vais tester ce soir
Bonjour,
La méthode d’inclusion ne fonctionne pas :
Aucun log n’est écrit.
HS : le <head> de votre documentation est passé en portugais brésilien :
Cordialement.
wifilightV2 : 2022-02-26 20:47:20
Jeedom : 4.2.13
Debian : 10.11
Nouvelle beta
ça devrait être OK, en tous cas pour cette erreur.
Merci!
et pour la doc, aucne idée du souci, j’utilise la procédure Jeedom.
Nouvelle beta chargée.
Test effectué avec deux TP-Link HS110 Ver : 1.0
Mes deux prises sont bien découvertes mais pas leurs IP (log en MP), il y a un souci avec arp-scan, il n’est pas installé :
Log dépendances :
0000|********************************************************
0001|* Installation des dépendances *
0002|********************************************************
0003|Hit:1 http://security.debian.org/debian-security buster/updates InRelease
0004|Hit:2 http://deb.debian.org/debian buster InRelease
0005|Hit:3 http://deb.debian.org/debian buster-updates InRelease
0006|Reading package lists...
0007|Reading package lists...
0008|Building dependency tree...
0009|Reading state information...
0010|The following additional packages will be installed:
0011|ieee-data
0012|The following NEW packages will be installed:
0013|arp-scan ieee-data
0014|0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
0015|Need to get 0 B/1899 kB of archives.
0016|After this operation, 11.3 MB of additional disk space will be used.
0017|Do you want to continue? [Y/n] Abort.
0018|********************************************************
0019|* Installation terminée *
0020|********************************************************
Ne manque t-il pas une confirmation ?
Je l’installe manuellement…
Après avoir installé arp-scan manuellement il trouve bien les bonnes IP (log en MP), par contre la config. n’est pas bonne :
Pour les périphériques de la liste ci-dessous, le sous-type est trouvé, dans les autres cas le Tapo P100 est choisi par le plugin, vous pouvez changer le sous-type sans perdre le deviceId.
Je ne vois pas la liste ci-dessous.
pour debian je suis en 10.6 et j’ai :
********************************************************
* Installation des dépendances *
********************************************************
Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 https://deb.nodesource.com/node_12.x buster InRelease
Get:4 http://security.debian.org/debian-security buster/updates/main Sources [223 kB]
Get:5 http://security.debian.org/debian-security buster/updates/main amd64 Packages [317 kB]
Get:6 http://security.debian.org/debian-security buster/updates/main Translation-en [171 kB]
Fetched 776 kB in 4s (173 kB/s)
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
arp-scan
debconf: unable to initialize frontend: Dialog
debconf: (TERM is not set, so the dialog frontend is not usable.)
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 229 not upgraded.
Need to get 0 B/310 kB of archives.
After this operation, 937 kB of additional disk space will be used.
Selecting previously unselected package arp-scan.
(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 ... 97753 files and directories currently installed.)
Preparing to unpack .../arp-scan_1.9.5-1_amd64.deb ...
Unpacking arp-scan (1.9.5-1) ...
Setting up arp-scan (1.9.5-1) ...
Processing triggers for man-db (2.8.5-2) ...
********************************************************
* Installation terminée *
********************************************************
Bizarre je reproduis aussi sur mon RPI4 de prod., en rajoutant -y ça passe :
0000|********************************************************
0001|* Installation des dépendances *
0002|********************************************************
0003|Hit:1 http://security.debian.org/debian-security buster/updates InRelease
0004|Hit:2 http://deb.debian.org/debian buster InRelease
0005|Hit:3 http://deb.debian.org/debian buster-updates InRelease
0006|Reading package lists...
0007|Reading package lists...
0008|Building dependency tree...
0009|Reading state information...
0010|The following additional packages will be installed:
0011|ieee-data
0012|The following NEW packages will be installed:
0013|arp-scan ieee-data
0014|debconf: unable to initialize frontend: Dialog
0015|debconf: (TERM is not set, so the dialog frontend is not usable.)
0016|debconf: falling back to frontend: Readline
0017|debconf: unable to initialize frontend: Readline
0018|debconf: (This frontend requires a controlling tty.)
0019|debconf: falling back to frontend: Teletype
0020|dpkg-preconfigure: unable to re-open stdin:
0021|0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
0022|Need to get 0 B/1899 kB of archives.
0023|After this operation, 11.3 MB of additional disk space will be used.
0024|Selecting previously unselected package ieee-data.
0025|(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 ... 60215 files and directories currently installed.)
0026|Preparing to unpack .../ieee-data_20180805.1_all.deb ...
0027|Unpacking ieee-data (20180805.1) ...
0028|Selecting previously unselected package arp-scan.
0029|Preparing to unpack .../arp-scan_1.9.5-1_amd64.deb ...
0030|Unpacking arp-scan (1.9.5-1) ...
0031|Setting up ieee-data (20180805.1) ...
0032|Setting up arp-scan (1.9.5-1) ...
0033|Processing triggers for man-db (2.8.5-2) ...
0034|********************************************************
0035|* Installation terminée *
0036|********************************************************
nouvelle beta :correctif pour les soucis avec le -y
en ssh, supprimer arp-scan :
sudo apt-get remove arp-scan
et relancer les dépendances
et la récup du modèle doit fonctionner :
supprime celui créé et relance la procédure
C’est OK pour les dépendances en ayant supprimé arp-scan avant :
0000|********************************************************
0001|* Installation des dépendances *
0002|********************************************************
0003|Hit:1 http://security.debian.org/debian-security buster/updates InRelease
0004|Hit:2 http://deb.debian.org/debian buster InRelease
0005|Hit:3 http://deb.debian.org/debian buster-updates InRelease
0006|Reading package lists...
0007|Reading package lists...
0008|Building dependency tree...
0009|Reading state information...
0010|The following additional packages will be installed:
0011|ieee-data
0012|The following NEW packages will be installed:
0013|arp-scan ieee-data
0014|debconf: unable to initialize frontend: Dialog
0015|debconf: (TERM is not set, so the dialog frontend is not usable.)
0016|debconf: falling back to frontend: Readline
0017|debconf: unable to initialize frontend: Readline
0018|debconf: (This frontend requires a controlling tty.)
0019|debconf: falling back to frontend: Teletype
0020|dpkg-preconfigure: unable to re-open stdin:
0021|0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
0022|Need to get 0 B/1899 kB of archives.
0023|After this operation, 11.3 MB of additional disk space will be used.
0024|Selecting previously unselected package ieee-data.
0025|(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 ... 60215 files and directories currently installed.)
0026|Preparing to unpack .../ieee-data_20180805.1_all.deb ...
0027|Unpacking ieee-data (20180805.1) ...
0028|Selecting previously unselected package arp-scan.
0029|Preparing to unpack .../arp-scan_1.9.5-1_amd64.deb ...
0030|Unpacking arp-scan (1.9.5-1) ...
0031|Setting up ieee-data (20180805.1) ...
0032|Setting up arp-scan (1.9.5-1) ...
0033|Processing triggers for man-db (2.8.5-2) ...
0034|********************************************************
0035|* Installation terminée *
0036|********************************************************
Pas pour la récup. du modèle, même résultat qu’avant : modèle par défaut, log en MP.
corrigé en beta
Ça fonctionne parfaitement :
Note : Les prises HS100 HS110 KP105 KP110 peuvent nécessiter d’utilier le protocole V2, faire la modification manuellement.
Dans mon cas V1 et V2 fonctionnent aussi bien, je ne trouve pas la différence dans la doc.?
RAS pour les TP-Link HS110.
Je pense que V2 ne sert à rien. Il y a eu un firmware qui posait souci et ça semble ne plus être le cas.
En tous cas merci.
merci pour le débogage
Ce sujet a été automatiquement fermé après 24 heures suivant le dernier commentaire. Aucune réponse n’est permise dorénavant.
