KLF200 has been restarted after found not responding

lunarok · Mars 6, 2022, 8:16

Oui passer en stable, sur un autre post il y a des confirmations que ça fonctionne chez ceux qui avaient le soucis.
La on est sur un habituel sans logs rien donc je laisse les modérateurs ‹ communautaire › aider avec leur impartialité …

Salvialf · Mars 6, 2022, 8:18

Faut pas être chonchon comme ça encore. La vie est belle mon ami nul besoin de se vexer de la sorte et de m’attaquer à demi mots.

micke74 · Mars 6, 2022, 8:19

Salut,
Merci pour l’info, il est effectivement en Beta ainsi que MQTT Manager.
N’ayant rien en Beta je vais attendre un peu.
Un peu du même avis que @jpty un peu dommage de passer par du MQTT.

Salvialf · Mars 6, 2022, 8:20

Ah bon pourquoi cela ?

micke74 · Mars 6, 2022, 8:33

En imaginant comment cela peut fonctionner (je me trompe peut être), cela fait transiter toutes les informations du KLF via docker à MQTT puis de MQTT au plugin.
MQTT n’étant pas forcément sur le même serveur que jeedom les requêtes sont faites de docker vers le KLF reviennent vers docker pour envoyer les valeurs à MQTT que jeedom va ensuite recevoir via le plugin MQTT Manager.
Ca me semble être beaucoup d’échanges réseau.
Avantage effectivement cela permet de centraliser les données dans MQTT et d’utiliser d’autre plugins.
@lunarok je crée un sujet pour mon problème pour ne pas plus polluer celui là.
Bonne soirée

lunarok · Mars 7, 2022, 7:24

Oui merci de créer un sujet avec le max d’info.
Pour info le plugin mqtt klf, il fait pas les BSO, pas les lumières etc. Et aujourd’hui il n’a pas été testé sur autant d’install, donc l’aspect non expliqué sur le nombre, c’est du mensonge que s’avancer aujourd’hui en disant qu’il est parfait (j’ai testé le docker klf200 et il correspond pas à un usage complet de la gateway)

Salvialf · Mars 7, 2022, 7:51

Comme expliqué dans la documentation et dans mon message…

Merci pour les tests en tout cas

micke74 · Mars 28, 2022, 9:06

Salut, @jpty Merci pour l’indice sur la version, après un downgrade de aiohttp dans la bonne version, je n’ai pas eu de problème depuis 3 semaines .
@lunarok merci pour ce plugin, peut être ajouter dans la doc cette astuce sur les versions

berni · Avril 13, 2022, 7:28

Bonjour, j’ai aussi installé un klf200 / raspi+ busty+jeedom 4.2.x+ plugin. j’essaye comme vous de trouver une solution stable sans le plugin pour redémarrer le klf200.
je retrouve les mêmes messages, mais j’ai aussi regardé côté réseau :
au démarrage de l’ensemble tout ce passe bien; une session tcp s’établi (au dessus c’est du tls donc je ne vois rien de plus). cette même session semble « permanente » puisque elle est reste environ 4heures (lors de ce test)
j’ai remarqué une nouvelle session dans l’après midi et ce matin, plus de session. je vois les tentatives qui sont refusées par le klf via un reset.
pour aller plus loin je compte redémarrer le plugin, puis le klf200 pour voir comment ça va se débloquer.
Travaillant sur les infras réseau, ma première remarque serait qu’il faut éviter les sessions tcp permanentes qui font l’objet de pas mal de paramètres perturbateur( timers, dépendances, …) Normalement, un appel API = une nouvelle session TCP .
A suivre…
voici déjà mes premiers logs et trace tcpdump:

`0467|[2022-04-13 09:23:44]ERROR : KLF200 has been restarted after found not responding
0468|Traceback (most recent call last):
0469|File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in 
0470|LOOP.run_until_complete(init_pyvlx_connection(LOOP))
0471|File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
0472|return future.result()
0473|File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
0474|await pyvlx.load_nodes()
0475|File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
0476|await self.nodes.load(node_id)
0477|File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
0478|await self._load_all_nodes()
0479|File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
0480|await get_all_nodes_information.do_api_call()
0481|File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
0482|await self.send_frame()
0483|File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
0484|await self.pyvlx.send_frame(self.request_frame())
0485|File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
0486|await self.connect()
0487|File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
0488|await self.connection.connect()
0489|File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
0490|ssl=self.create_ssl_context(),
0491|File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
0492|raise exceptions[0]
0493|File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
0494|await self.sock_connect(sock, address)
0495|File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
0496|return await fut
0497|File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
0498|raise OSError(err, f'Connect call failed {address}')
0499|ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.100.200', 51200)`

POur le tcpdump, jeedom est en 192.168.100.106 et le klf : 192.168.100.200
notez les flags [S] puis [R] du klf200 :

09:25:46.679642 IP (tos 0x0, ttl 64, id 4965, offset 0, flags [DF], proto TCP (6), length 60)
    192.168.100.106.46820 > 192.168.100.200.51200: Flags [S], cksum 0x4ab2 (incorrect -> 0x1673), seq 1561319422, win 64240, options [mss 1460,sackOK,TS val 1701368508 ecr 0,nop,wscale 7], length 0
09:25:46.679979 IP (tos 0x0, ttl 128, id 56306, offset 0, flags [DF], proto TCP (6), length 40)
    192.168.100.200.51200 > 192.168.100.106.46820: Flags [R.], cksum 0xb158 (correct), seq 0, ack 1561319423, win 0, length 0
09:25:51.754516 ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.100.200 tell 192.168.100.106, length 28
09:25:51.754893 ARP, Ethernet (len 6), IPv4 (len 4), Reply 192.168.100.200 is-at 64:61:84:00:73:85, length 46

berni · Avril 13, 2022, 8:13

…la suite: le demon était NOK bien sûr comme il n’arrive plus a joindre le klf. j’ai éteind et rallumé le klf et le demon est passé OK tout seul et j’ai naturellement une session tcp:

root@jeedom:~# netstat -tunalp | grep 192.168.100.200 tcp 0 0 192.168.100.106:47012 192.168.100.200:51200 ESTABLISHED 12089/python3

berni · Avril 25, 2022, 8:01

Bonsoir,
Je vous fais un retour sur le test que j’ai mis en place avec mon klf200.
Comme précisé juste au dessus je trouvais les sessions TCP trop longue, alors j’ai fait un petit scénario pour forcer une nouvelle session toutes les heures : (192.168.100.200 → klf200)

/* Lancement du kill de la session tcp klf200 */
$cmd = "sudo kill $(netstat -anlp | grep 192.168.100.200 | awk -F \" \" '{print $7}' | cut -d/ -f1)";
$scenario->setLog('DEBUG REQUETTE : '.$cmd);
$result = shell_exec($cmd);
$scenario->setLog('RETOUR REQUETTE : '.$result);

le process python tombe « proprement » et le plugin rétabli la liaison avec le klf200 avec succès.
seul bémol; juste avant de rétablir la liaison le plugin envoie logiquement le message « … restarted after found not responding ».
aucun dysfonctionnement observé depuis 2 semaines.
@lunarok qu’en penses tu ? serait il possible d’établir la session tcp au besoin ?

philou15 · Mai 8, 2022, 1:40

Bonjour
@lunarok

Pense tu pouvoir fiabiliser cela ?

Je suis en version beta et la derniere version de jeedom,

c’est vraiment la cata l’erreur,

Je ne comprend pas ce qu’il faut faire pour reboot suivant le script juste avant la session python, mais la franchement c’est dommage qu’on ai autant d’erreurs

Car j’ai mes volets qui ne marchent plus et plus d’explications, pourtant j’ai remis la sauvegarde avant la mise a jour, idem, donc il doit y avoir un pb entre le KLF et le pluging ?
Merci
Merci

lunarok · Mai 8, 2022, 2:13

Tu parles de quoi là ? Parceque rebondir sur un fil « poubelle » où tout le monde y jette un « moi ca va pas » sans rien de plus, je peux rien faire.
Je rappelle que le seul soucis il y a quelques mois a été corrigé grace à un retour user, la version de librairie est bien bloquée.

La demande à couper le démon toutes les heures, pour me faire insulter par les users je trouverais pas mieux. Tous ceux qui vont mettre des commandes en scénario à heure fixe pourront commander des poupées vaudous à mon nom pour améliorer les résultats que jeedom se reconnecte avant leurs commandes.

Là mon démon a été lancé le 4 mai pour la dernière fois, donc 4 jours sans aucun soucis, ca ne bloque rien, mes stores et fenetres s’activent par scénario plusieurs fois par jour. Et je suis seulement à 4 jours car j’ai fait la mise à jour des dépendances en version 4.2, avant le démon datait de plusieurs semaines.

Merci de fournir des détails et des logs.

philou15 · Mai 8, 2022, 2:40

@lunarok
Je parle du message qui dit : KLF200 has been restarted after found not responding

J’avais du mettre la beta qui fonctionnais pas trop mal tous les jours.
Ce matin j’ai fait la mise a jour jeedom 4.2.15 et ton plug en 2022-05-05 01:01:17 et depuis je galere,

Plus rien ne fontionne, j’ai voulu remettre ma sauvegarde avant la mise a jour, idem.

du coup j’ai refait les derniers version mais la je galere depuis 4 heures sans trouver de solution
ci joint mon log

Merci pour ton aide

[2022-05-08 16:06:26][ERROR] : Erreur sur la fonction cron du plugin : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:07:15][ERROR] : Erreur sur la fonction cron du plugin : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
Traceback (most recent call last):
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in <module>
LOOP.run_until_complete(init_pyvlx_connection(LOOP))
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
await pyvlx.load_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
await self.nodes.load(node_id)
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
await self._load_all_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
await get_all_nodes_information.do_api_call()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
await self.send_frame()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
await self.pyvlx.send_frame(self.request_frame())
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
await self.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
await self.connection.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
ssl=self.create_ssl_context(),
File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
raise exceptions[0]
File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
await self.sock_connect(sock, address)
File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
return await fut
File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.0.150', 51200)
[2022-05-08 16:08:25][ERROR] : Erreur sur la fonction cron du plugin : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:09:25][ERROR] : Erreur sur la fonction cron du plugin : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:10:27][ERROR] : Erreur sur la fonction cron du plugin : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:10:58][ERROR] : Erreur exécution de la commande [Volets][BUREAU][Arrêter] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:15][ERROR] : Erreur exécution de la commande [Volets][BUREAU][Fermer] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:24][ERROR] : Erreur exécution de la commande [Volets][VELUX][Arrêter] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:32][ERROR] : Erreur exécution de la commande [Volets][VELUX][Fermer] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:45][ERROR] : Erreur exécution de la commande [Volets][VELUX][Arrêter] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:51][ERROR] : Erreur exécution de la commande [Volets][BUREAU][Ouvrir] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
[2022-05-08 16:11:53][ERROR] : Erreur exécution de la commande [Volets][VELUX][Arrêter] : Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT), data : {"ieee":"2c:11:65:ff:fe:22:1a:a2","cmd":[{"endpoint":2,"cluster":"on_off","command":"off","await":1}],"allowQueue":false} erreur : {"state":"error","result":"[0xc571:2:0x0006]: Message send failure","code":0}
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x758e8b30>()]>>
[2022-05-08 16:26:25][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75b4dad0>()]>>
[2022-05-08 16:27:07][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:27:07][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75b58b30>()]>>
[2022-05-08 16:27:49][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75ae9b30>()]>>
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75ac6b10>()]>>
[2022-05-08 16:28:31][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:29:13][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:29:14][ERROR] : KLF200 has been restarted after found not responding
Traceback (most recent call last):
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in <module>
LOOP.run_until_complete(init_pyvlx_connection(LOOP))
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
await pyvlx.load_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
await self.nodes.load(node_id)
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
await self._load_all_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
await get_all_nodes_information.do_api_call()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
await self.send_frame()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
await self.pyvlx.send_frame(self.request_frame())
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
await self.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
await self.connection.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
ssl=self.create_ssl_context(),
File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
raise exceptions[0]
File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
await self.sock_connect(sock, address)
File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
return await fut
File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.0.150', 51200)
[2022-05-08 16:29:44][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75920b10>()]>>
[2022-05-08 16:29:55][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75b11b10>()]>>
[2022-05-08 16:30:38][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75b5bad0>()]>>
[2022-05-08 16:31:20][ERROR] : KLF200 has been restarted after found not responding
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75a95b50>()]>>
[2022-05-08 16:32:03][ERROR] : KLF200 has been restarted after found not responding
Traceback (most recent call last):
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in <module>
LOOP.run_until_complete(init_pyvlx_connection(LOOP))
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
await pyvlx.load_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
await self.nodes.load(node_id)
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
await self._load_all_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
await get_all_nodes_information.do_api_call()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
await self.send_frame()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
await self.pyvlx.send_frame(self.request_frame())
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
await self.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
await self.connection.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
ssl=self.create_ssl_context(),
File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
raise exceptions[0]
File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
await self.sock_connect(sock, address)
File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
return await fut
File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.0.150', 51200)
[2022-05-08 16:32:44][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:32:44][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:32:45][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:35:02][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:35:06][ERROR] : KLF200 has been restarted after found not responding
Traceback (most recent call last):
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in <module>
LOOP.run_until_complete(init_pyvlx_connection(LOOP))
File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
return future.result()
File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
await pyvlx.load_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
await self.nodes.load(node_id)
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
await self._load_all_nodes()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
await get_all_nodes_information.do_api_call()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
await self.send_frame()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
await self.pyvlx.send_frame(self.request_frame())
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
await self.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
await self.connection.connect()
File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
ssl=self.create_ssl_context(),
File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
raise exceptions[0]
File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
await self.sock_connect(sock, address)
File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
return await fut
File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
raise OSError(err, f'Connect call failed {address}')
OSError: [Errno 113] Connect call failed ('192.168.0.150', 51200)
[2022-05-08 16:35:41][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:35:42][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:35:46][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:35:48][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 16:36:44][ERROR] : KLF200 has been restarted after found not responding

philou15 · Mai 8, 2022, 3:39

Pour info, j’ai aussi ce comportement:
Je ferme un volet, je lui dit stop, il arrete celui ci, il repart, il stop il repart comme si il envoyait encore la commande.
Puis ensuite ça plante completement;
Idem pour plusieurs volets, impossible de faire ouvrir ou fermer plusieurs voletS.

Ci joint un log en mode DEBUG

Merci

[2022-05-08 17:35:00][DEBUG] : Send http://localhost:9123/devices
[2022-05-08 17:35:00][DEBUG] : Result {"result": "ok", "devices": [{"id": 0, "name": "VELUX", "type": "RollerShutter", "position": 24}, {"id": 1, "name": "BUREAU", "type": "RollerShutter", "position": 0}, {"id": 2, "name": "SDB", "type": "RollerShutter", "position": 0}, {"id": 3, "name": "SALON", "type": "RollerShutter", "position": 0}, {"id": 4, "name": "SAM-OUEST", "type": "RollerShutter", "position": 0}, {"id": 5, "name": "SAM", "type": "RollerShutter", "position": 0}, {"id": 6, "name": "PORTE-ENTREE", "type": "RollerShutter", "position": 0}, {"id": 7, "name": "CUISINE", "type": "RollerShutter", "position": 0}, {"id": 8, "name": "CHAMBRE-PARENT", "type": "RollerShutter", "position": 0}, {"id": 9, "name": "CHAMBRE-AMIS", "type": "RollerShutter", "position": 1}]}
[2022-05-08 17:35:05][DEBUG] : Send http://localhost:9123/devices
[2022-05-08 17:35:05][DEBUG] : Result {"result": "ok", "devices": [{"id": 0, "name": "VELUX", "type": "RollerShutter", "position": 24}, {"id": 1, "name": "BUREAU", "type": "RollerShutter", "position": 0}, {"id": 2, "name": "SDB", "type": "RollerShutter", "position": 0}, {"id": 3, "name": "SALON", "type": "RollerShutter", "position": 0}, {"id": 4, "name": "SAM-OUEST", "type": "RollerShutter", "position": 0}, {"id": 5, "name": "SAM", "type": "RollerShutter", "position": 0}, {"id": 6, "name": "PORTE-ENTREE", "type": "RollerShutter", "position": 0}, {"id": 7, "name": "CUISINE", "type": "RollerShutter", "position": 0}, {"id": 8, "name": "CHAMBRE-PARENT", "type": "RollerShutter", "position": 0}, {"id": 9, "name": "CHAMBRE-AMIS", "type": "RollerShutter", "position": 1}]}
[2022-05-08 17:35:05][DEBUG] : Update VELUX at 24%
[2022-05-08 17:35:05][DEBUG] : Update BUREAU at 0%
[2022-05-08 17:35:05][DEBUG] : Update SDB at 0%
[2022-05-08 17:35:05][DEBUG] : Update SALON at 0%
[2022-05-08 17:35:05][DEBUG] : Update SAM-OUEST at 0%
[2022-05-08 17:35:05][DEBUG] : Update SAM at 0%
[2022-05-08 17:35:05][DEBUG] : Update PORTE-ENTREE at 0%
[2022-05-08 17:35:05][DEBUG] : Update CUISINE at 0%
[2022-05-08 17:35:05][DEBUG] : Update CHAMBRE-PARENT at 0%
[2022-05-08 17:35:05][DEBUG] : Update CHAMBRE-AMIS at 1%
[2022-05-08 17:35:07][DEBUG] : Action /set/1/100
[2022-05-08 17:35:07][DEBUG] : Send http://localhost:9123/set/1/100
[2022-05-08 17:35:14][DEBUG] : Action /stop/1
[2022-05-08 17:35:14][DEBUG] : Send http://localhost:9123/stop/1
[2022-05-08 17:35:22][DEBUG] : Action /stop/1
[2022-05-08 17:35:22][DEBUG] : Send http://localhost:9123/stop/1
[2022-05-08 17:35:24][DEBUG] : Action /stop/1
[2022-05-08 17:35:24][DEBUG] : Send http://localhost:9123/stop/1
[2022-05-08 17:35:27][DEBUG] : Action /stop/1
[2022-05-08 17:35:28][DEBUG] : Send http://localhost:9123/stop/1
[2022-05-08 17:35:29][DEBUG] : Action /stop/1
[2022-05-08 17:35:29][DEBUG] : Send http://localhost:9123/stop/1
[2022-05-08 17:35:32][DEBUG] : Result 
[2022-05-08 17:35:39][DEBUG] : Result 
[2022-05-08 17:35:47][DEBUG] : Result 
[2022-05-08 17:35:49][DEBUG] : Result 
[2022-05-08 17:35:53][DEBUG] : Result 
[2022-05-08 17:35:54][DEBUG] : Action /set/1/0
[2022-05-08 17:35:54][DEBUG] : Send http://localhost:9123/set/1/0
[2022-05-08 17:35:54][DEBUG] : Result 
[2022-05-08 17:36:03][DEBUG] : Send http://localhost:9123/devices
[2022-05-08 17:36:03][DEBUG] : Result {"result": "ok", "devices": [{"id": 0, "name": "VELUX", "type": "RollerShutter", "position": 24}, {"id": 1, "name": "BUREAU", "type": "RollerShutter", "position": 0}, {"id": 2, "name": "SDB", "type": "RollerShutter", "position": 0}, {"id": 3, "name": "SALON", "type": "RollerShutter", "position": 0}, {"id": 4, "name": "SAM-OUEST", "type": "RollerShutter", "position": 0}, {"id": 5, "name": "SAM", "type": "RollerShutter", "position": 0}, {"id": 6, "name": "PORTE-ENTREE", "type": "RollerShutter", "position": 0}, {"id": 7, "name": "CUISINE", "type": "RollerShutter", "position": 0}, {"id": 8, "name": "CHAMBRE-PARENT", "type": "RollerShutter", "position": 0}, {"id": 9, "name": "CHAMBRE-AMIS", "type": "RollerShutter", "position": 1}]}
[2022-05-08 17:36:03][DEBUG] : Update VELUX at 24%
[2022-05-08 17:36:03][DEBUG] : Update BUREAU at 0%
[2022-05-08 17:36:03][DEBUG] : Update SDB at 0%
[2022-05-08 17:36:03][DEBUG] : Update SALON at 0%
[2022-05-08 17:36:03][DEBUG] : Update SAM-OUEST at 0%
[2022-05-08 17:36:03][DEBUG] : Update SAM at 0%
[2022-05-08 17:36:03][DEBUG] : Update PORTE-ENTREE at 0%
[2022-05-08 17:36:03][DEBUG] : Update CUISINE at 0%
[2022-05-08 17:36:03][DEBUG] : Update CHAMBRE-PARENT at 0%
[2022-05-08 17:36:03][DEBUG] : Update CHAMBRE-AMIS at 1%
[2022-05-08 17:36:13][INFO] : Arrêt du service klf200
[2022-05-08 17:36:14][DEBUG] : Result 
[2022-05-08 17:36:14][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:14][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:19][INFO] : Arrêt du service klf200
[2022-05-08 17:36:19][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:19][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:19][DEBUG] : Send http://localhost:9123/position/1
[2022-05-08 17:36:20][DEBUG] : Result 
[2022-05-08 17:36:27][INFO] : Arrêt du service klf200
[2022-05-08 17:36:28][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:28][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:28][DEBUG] : Send http://localhost:9123/position/1
[2022-05-08 17:36:29][DEBUG] : Result 
[2022-05-08 17:36:29][INFO] : Arrêt du service klf200
[2022-05-08 17:36:30][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:30][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:30][DEBUG] : Send http://localhost:9123/position/1
[2022-05-08 17:36:31][DEBUG] : Result 
[2022-05-08 17:36:33][INFO] : Arrêt du service klf200
[2022-05-08 17:36:33][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:33][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:33][DEBUG] : Send http://localhost:9123/position/1
[2022-05-08 17:36:34][DEBUG] : Result 
[2022-05-08 17:36:34][INFO] : Arrêt du service klf200
[2022-05-08 17:36:34][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:34][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:36:34][DEBUG] : Send http://localhost:9123/position/1
[2022-05-08 17:36:35][DEBUG] : Result 
[2022-05-08 17:36:54][INFO] : Arrêt du service klf200
[2022-05-08 17:36:54][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:36:54][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:00][INFO] : Arrêt du service klf200
[2022-05-08 17:37:01][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:01][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:01][DEBUG] : Update BUREAU at %
Traceback (most recent call last):
  File "/var/www/html/plugins/klf200/resources/klf200d.py", line 269, in <module>
    LOOP.run_until_complete(init_pyvlx_connection(LOOP))
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete
    return future.result()
  File "/var/www/html/plugins/klf200/resources/klf200d.py", line 22, in init_pyvlx_connection
    await pyvlx.load_nodes()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 78, in load_nodes
    await self.nodes.load(node_id)
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 69, in load
    await self._load_all_nodes()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/nodes.py", line 85, in _load_all_nodes
    await get_all_nodes_information.do_api_call()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 21, in do_api_call
    await self.send_frame()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/api/api_event.py", line 33, in send_frame
    await self.pyvlx.send_frame(self.request_frame())
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 66, in send_frame
    await self.connect()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/pyvlx.py", line 43, in connect
    await self.connection.connect()
  File "/usr/local/lib/python3.7/dist-packages/pyvlx/connection.py", line 90, in connect
    ssl=self.create_ssl_context(),
  File "/usr/lib/python3.7/asyncio/base_events.py", line 959, in create_connection
    raise exceptions[0]
  File "/usr/lib/python3.7/asyncio/base_events.py", line 946, in create_connection
    await self.sock_connect(sock, address)
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 464, in sock_connect
    return await fut
  File "/usr/lib/python3.7/asyncio/selector_events.py", line 494, in _sock_connect_cb
    raise OSError(err, f'Connect call failed {address}')
ConnectionRefusedError: [Errno 111] Connect call failed ('192.168.0.150', 51200)
[2022-05-08 17:37:03][DEBUG] : Send http://localhost:9123/devices
[2022-05-08 17:37:04][DEBUG] : Result 
[2022-05-08 17:37:09][INFO] : Arrêt du service klf200
[2022-05-08 17:37:09][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:09][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:09][DEBUG] : Update BUREAU at %
[2022-05-08 17:37:11][INFO] : Arrêt du service klf200
[2022-05-08 17:37:11][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:11][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:11][DEBUG] : Update BUREAU at %
[2022-05-08 17:37:14][INFO] : Arrêt du service klf200
[2022-05-08 17:37:14][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:14][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:14][DEBUG] : Update BUREAU at %
[2022-05-08 17:37:16][INFO] : Arrêt du service klf200
[2022-05-08 17:37:16][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:16][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:16][DEBUG] : Update BUREAU at %
[2022-05-08 17:37:44][INFO] : Arrêt du service klf200
======== Running on http://0.0.0.0:9123 ========
(Press CTRL+C to quit)
Task was destroyed but it is pending!
task: <Task pending coro=<Heartbeat.loop() running at /usr/local/lib/python3.7/dist-packages/pyvlx/heartbeat.py:46> wait_for=<Future pending cb=[<TaskWakeupMethWrapper object at 0x75ac5ad0>()]>>
[2022-05-08 17:37:44][DEBUG] : Action /set/1/0
[2022-05-08 17:37:44][DEBUG] : Send http://localhost:9123/set/1/0
[2022-05-08 17:37:45][INFO] : Lancement démon klf200 : /usr/bin/python3 /var/www/html/plugins/klf200/resources/klf200d.py 192.168.0.150 9LfUAnBbEC
[2022-05-08 17:37:45][ERROR] : KLF200 has been restarted after found not responding
[2022-05-08 17:37:45][DEBUG] : Result

gamel53 · Mai 10, 2022, 5:37

Bonjour à tous et merci pour tous ces échanges.
J’ai moi-même eu un problème similaire avec une erreur Python et le redémarrage du KLF, avec aussi des comportements erratiques des commandes (malheureusement je n’ai plus les logs).
Après avoir cherché un moment, j’ai finalement simplement relancé les dépendances, et cela fonctionne à nouveau. Il y a, semble-t-il une incompatibilité majeure avec des librairies Python plus récente comme mentionné par @jpty. En effet, j’ai retrouvé un comportement normal après avoir relancé les dépendances. Ci-dessous les logs correspondants :

********************************************************
*             Installation des dépendances             *
********************************************************
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_12.x buster InRelease
Get:4 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages [13.0 MB]
Fetched 13.0 MB in 20s (665 kB/s)
Reading package lists...
Installation des dépendances apt
Reading package lists...
Building dependency tree...
Reading state information...
python3-dev is already the newest version (3.7.3-1).
python3-setuptools is already the newest version (40.8.0-1).
python3-pip is already the newest version (18.1-5+rpt1).
0 upgraded, 0 newly installed, 0 to remove and 123 not upgraded.
Installation du module pyvlx pour python
Collecting pyvlx
Using cached pyvlx-0.2.20-py3-none-any.whl
Collecting PyYAML
Using cached PyYAML-6.0-cp37-cp37m-linux_armv7l.whl
Installing collected packages: PyYAML, pyvlx
Successfully installed PyYAML-6.0 pyvlx-0.2.20
WARNING: You are using pip version 21.0.1; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
Installation du module aiohttp pour python
Collecting aiohttp==3.7.4.post0
Using cached aiohttp-3.7.4.post0-cp37-cp37m-linux_armv7l.whl
Collecting attrs>=17.3.0
Using cached attrs-21.4.0-py2.py3-none-any.whl (60 kB)
Collecting chardet<5.0,>=2.0
Using cached chardet-4.0.0-py2.py3-none-any.whl (178 kB)
Collecting multidict<7.0,>=4.5
Using cached multidict-6.0.2-cp37-cp37m-linux_armv7l.whl
Collecting async-timeout<4.0,>=3.0
Using cached async_timeout-3.0.1-py3-none-any.whl (8.2 kB)
Collecting yarl<2.0,>=1.0
Using cached yarl-1.7.2-cp37-cp37m-linux_armv7l.whl
Collecting typing-extensions>=3.6.5
Using cached typing_extensions-4.2.0-py3-none-any.whl (24 kB)
Collecting idna>=2.0
Using cached idna-3.3-py3-none-any.whl (61 kB)
Installing collected packages: typing-extensions, multidict, idna, yarl, chardet, attrs, async-timeout, aiohttp
Attempting uninstall: typing-extensions
Found existing installation: typing-extensions 4.1.1
Uninstalling typing-extensions-4.1.1:
Successfully uninstalled typing-extensions-4.1.1
Attempting uninstall: multidict
Found existing installation: multidict 6.0.2
Uninstalling multidict-6.0.2:
Successfully uninstalled multidict-6.0.2
Attempting uninstall: idna
Found existing installation: idna 3.3
Uninstalling idna-3.3:
Successfully uninstalled idna-3.3
Attempting uninstall: yarl
Found existing installation: yarl 1.7.2
Uninstalling yarl-1.7.2:
Successfully uninstalled yarl-1.7.2
Attempting uninstall: chardet
Found existing installation: chardet 4.0.0
Uninstalling chardet-4.0.0:
Successfully uninstalled chardet-4.0.0
Attempting uninstall: attrs
Found existing installation: attrs 21.4.0
Uninstalling attrs-21.4.0:
Successfully uninstalled attrs-21.4.0
Attempting uninstall: async-timeout
Found existing installation: async-timeout 4.0.2
Uninstalling async-timeout-4.0.2:
Successfully uninstalled async-timeout-4.0.2
Attempting uninstall: aiohttp
Found existing installation: aiohttp 3.8.1
Uninstalling aiohttp-3.8.1:
Successfully uninstalled aiohttp-3.8.1
Successfully installed aiohttp-3.7.4.post0 async-timeout-3.0.1 attrs-21.4.0 chardet-4.0.0 idna-3.3 multidict-6.0.2 typing-extensions-4.2.0 yarl-1.7.2
WARNING: You are using pip version 21.0.1; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
Installation du module bottle pour python
Collecting bottle
Using cached bottle-0.12.19-py3-none-any.whl (89 kB)
Installing collected packages: bottle
Successfully installed bottle-0.12.19
WARNING: You are using pip version 21.0.1; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
Installation du module YAML pour python
Collecting PyYAML==5.4.1
Using cached PyYAML-5.4.1-cp37-cp37m-linux_armv7l.whl
Installing collected packages: PyYAML
Attempting uninstall: PyYAML
Found existing installation: PyYAML 6.0
Uninstalling PyYAML-6.0:
Successfully uninstalled PyYAML-6.0
Successfully installed PyYAML-5.4.1
WARNING: You are using pip version 21.0.1; however, version 22.0.4 is available.
You should consider upgrading via the '/usr/bin/python3 -m pip install --upgrade pip' command.
********************************************************
*             Installation terminée                    *
********************************************************

Ce problème sur le KLF 200 est probablement apparu lors de la mise à jour d’un autre plugin, qui lui, ne doit du plus fonctionner avec la version de librairie qu’il attend.
Savez-vous s’il est prévu une mise à jour du plugin pour se resynchroniser avec les dernières librairies?
Merci à vous.

philou15 · Mai 10, 2022, 12:26

@lunarok

Bonjour,
As tu pris en compte ma demande d’aide pour le plug ?
C’est juste pour savoir si j’attend pour avoir la solution.

lunarok · Mai 10, 2022, 1:28

ca, ca veut dire que ton KLF ne répond pas, qu’il faut le redémarrer

ca je sais pas d’ou ca vient et encore moins ce que ca vient faire dans les logs du plugin (comme on le voit sur d’autres lignes, le service du plugin est sur 9123, le klf sur 51200 … 8089 c’est un autre plugin

Là le basique à faire : redémarrer la gateway + relancer es dépendances

philou15 · Mai 10, 2022, 1:32

Oui j’ai fait une reinstal des dépendances, un reboot de jeedom, de la gateway aussi.
Elle fonctionne par moment, tu va pourvoir envoyer un ordre, puis apres fini en carafe.

J’ai beau relancer les dépendances, plus rien ne marche maintenant.

on a pas un probleme avec python ?

merci pour ton aide

arnog23 · Mai 10, 2022, 1:51

Bonjour,

Aurais-tu le #plugin-zigbee qui tourne ?

En cherchant Erreur lors de la requete : http://127.0.0.1:8089/device/command(PUT) sur le forum, on arrive sur des posts relatifs a ce plugin.

C’est peut être une piste.