Pb dépendance

Mick33 · Juin 3, 2024, 6:42

Bonjour,
Je suis sur Atlas version 4.4.6 et je suis interfacé à un ESP-Home piscine via MQTT. Mon système marchait parfaitement, j’ai modifié seulement une table dans mon ESP Home qui transmet les informations piscine: température , pH et ORP et maintenant je n’ai plus de rafraichissement de la température, alors que le Ph et ORP sont bien rafraichis, voir log:

2024-06-03 20:35:38] DEBUG  : Aucune commande n'a été créée pour le topic esp-piscine/sensor/temp__rature_piscine/state dans l'équipement #[Piscine][esp-piscine]# (création automatique de commande)
[2024-06-03 20:35:39] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:39] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:39] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:40] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:40] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:41] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:41] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:42] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:42] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:42] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:43] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:43] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:43] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:sensor:orp_volt:state]# <- 1.913
[2024-06-03 20:35:45] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:45] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:46] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:46] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:46] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:sensor:phvolt_piscine:state]# <- 2.711
[2024-06-03 20:35:47] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:47] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:47] INFO  : Cmd #[Piscine][esp-piscine][pH]# <- 7.5
[2024-06-03 20:35:47] INFO  : Cmd #[Piscine][esp-piscine][ORP]# <- 623
[2024-06-03 20:35:47] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:48] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:35:48] DEBUG  : Aucune commande n'a été créée pour le topic esp-piscine/sensor/temp__rature_piscine/state dans l'équipement #[Piscine][esp-piscine]# (création automatique de commande)
[2024-06-03 20:35:48] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:35:48] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m

J’ai relancé les dépendances JMQTT et Daemon, sans effets et je me suis aperçu qu’il y avait des erreurs dans le log JMQTT_dep:

================================================================================
== Jeedom 4.4.6 Atlas in Debian GNU/Linux 10 (buster) on aarch64/arm64/64bits
== Python 3.7.3 (default, Oct 31 2022, 14:04:00) [GCC 8.3.0]
== jMQTT v23.11.7 (2024-05-17 13:03:17) branch:stable previously:v23.11.6
======================================================================
== 03/06/2024 20:22:00 == Dependencies installation for jMQTT
======================================================================
[  0% ] : Synchronize the package index...
[  9% ] : Synchronize the package index :  ERROR 
[ 10% ] : Purge dynamic contents...
[ 19% ] : Purge dynamic contents : [  OK  ]
[ 20% ] : Install Composer...
[ 29% ] : Install Composer : [  OK  ]
[ 30% ] : Install JsonPath-PHP library...
[ 39% ] : Install JsonPath-PHP library : [  OK  ]
[ 40% ] : Remove Composer...
[ 49% ] : Remove Composer : [  OK  ]
[ 50% ] : Install python3 venv and pip debian packages...
[ 59% ] : Install python3 venv and pip debian packages : [  OK  ]
[ 60% ] : Create a python3 Virtual Environment...
[ 69% ] : Create a python3 Virtual Environment : [  OK  ]
[ 70% ] : Install required python3 libraries in venv...
[ 99% ] : Install required python3 libraries in venv : [  OK  ]
[100% ] : Finished !
======================================================================
==KO== Installation Error
======================================================================
== ANALYSING ERRORS...
== NO KNOWN ERROR DETECTED
== Error in step : Synchronize the package index
== Line 13
== Command `sudo apt-get update' have an issue
== Return code is 100
== Error message :
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://deb.debian.org/debian buster InRelease
Hit:3 http://deb.debian.org/debian buster-updates InRelease
Ign:4 http://deb.debian.org/debian buster-backports InRelease
Err:5 http://deb.debian.org/debian buster-backports Release
404  Not Found [IP: 2a04:4e42:6a::644 80]
Hit:6 http://mirrors.xtom.de/armbian buster InRelease
Hit:7 https://deb.nodesource.com/node_18.x buster InRelease
Reading package lists...
E: The repository 'http://deb.debian.org/debian buster-backports Release' no longer has a Release file.
======================================================================

log esp_broker:

2024-06-03 20:38:27] INFO  : Cmd #[Piscine][esp-piscine][ORP]# <- 623
[2024-06-03 20:38:28] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:28] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:28] DEBUG  : Aucune commande n'a été créée pour le topic esp-piscine/sensor/temp__rature_piscine/state dans l'équipement #[Piscine][esp-piscine]# (création automatique de commande)
[2024-06-03 20:38:28] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:28] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:30] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:30] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:30] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:31] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:31] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:31] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:32] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:33] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:33] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:34] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:34] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:sensor:orp_volt:state]# <- 1.912
[2024-06-03 20:38:35] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:35] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:sensor:phvolt_piscine:state]# <- 2.712
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:36] INFO  : Cmd #[Piscine][esp-piscine][pH]# <- 7.5
[2024-06-03 20:38:37] INFO  : Cmd #[Piscine][esp-piscine][ORP]# <- 624
[2024-06-03 20:38:37] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m
[2024-06-03 20:38:38] INFO  : Cmd #[Piscine][esp-piscine][esp-piscine:debug]# <- e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m
[2024-06-03 20:38:38] DEBUG  : Aucune commande n'a été créée pour le topic esp-piscine/sensor/temp__rature_piscine/state dans l'équipement #[Piscine][esp-piscine]# (création automatique de commande)

log jmqttd:

[2024-06-03 20:22:44,331] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR

et rappel de ma configuration JMQTT:

Je reconnais que je suis sec, si quelqu’un pouvait me débloquer, merci d’avance

Bad · Juin 4, 2024, 8:24

Hello,

Si le changement à eu lieu côté ESP, je pense qu’il faut chercher dessus et pas jMQTT.

Mais je vois que le topic de température est étrange, probablement des accents :

Il serait intéressant de passer aussi le démon en débug, pour avoir plus de logs et de les poster ici.

Bad

akenad · Juin 4, 2024, 12:12

Bonjour,

pour cette erreur,

/plugins/jMQTT/resources/dependance.lib est différent de /plugins/homebridge/resources/dependance.lib
(et donc de dependance.lib/dependance.lib at master · NebzHB/dependance.lib · GitHub)

et voir :

Impossible de relancer les dependances
recovery Atlas (aka réinit conf usine) : Zwave JS DEMON NOK suite MàJ - #19 par akenad

akenad

Mick33 · Juin 4, 2024, 5:37

Merci pour votre retour, la modif de table de valeur dans le programme n’a certainemment pas d’impact sur jmqtt, je précise que mon ESP est connecté à un display qui affiche les bonnes valeurs de température; donc le problème vient dans la communication entre l’esp et jmqtt. Et je ne comprends pas les erreurs qu’il y a sur l’installation et les dépendances.

[  9% ] : Synchronize the package index :  ERROR

N’est ce plutôt là le problème?

esp-piscine/sensor/temp__rature_piscine/state

dans la commande il y avait avant déjà une erreur de script (et ça fonctionnait?):

esp-piscine/sensor/temprature_piscine/state

J’ai essayé de corriger l’erreur de la commande en mettant « température », sans succès?
Je rappelle que dans le programme yaml de l’ESP le nom est bien: « température piscine »
Par contre comment met on le demon en debug, car je n’ai jamais pratiqué.

Mick33 · Juin 4, 2024, 5:44

Merci @akenad pour votre retour, mais malheureusement je n’ai pas un niveau suffisant pour comprendre ton post.
Comme je disais précédemment à @Bad , il faudrait d’abord trouver la cause de l’erreur de synchronisation:

[  9% ] : Synchronize the package index :  ERROR

Je ne sais pas si cela vous donne une piste?

Bad · Juin 4, 2024, 6:18

Hello,

Si le démon se lance, je ne pense pas que ce soit le sujet prioritaire.

Bad

Mick33 · Juin 4, 2024, 6:40

D’accord
le log jmqttd c’est bien le démon?

[2024-06-03 20:22:44,331] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 07:26:37,322] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 07:31:24,942] ERROR  Client141       Brk141Th     on_disconnect() : Unexpected disconnection from broker!
[2024-06-04 20:37:48,749] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 20:38:44,502] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR

Bad · Juin 4, 2024, 6:52

Oui, mais il est actuellement en « error », pas en débug.

Mick33 · Juin 4, 2024, 7:01

[2024-06-03 20:22:44,331] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 07:26:37,322] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 07:31:24,942] ERROR  Client141       Brk141Th     on_disconnect() : Unexpected disconnection from broker!
[2024-06-04 20:37:48,749] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 20:38:44,502] INFO  Main            MainThread   set_log_level() : New log level set to: ERROR
[2024-06-04 20:59:01,148] INFO  Main            MainThread   set_log_level() : New log level set to: DEBUG
[2024-06-04 20:59:01,176] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 3 messages handled in 127.691507ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temp__rature_piscine/state', 'payload': '25.25', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/phvolt_piscine/state', 'payload': '2.710', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_piscine/state', 'payload': '624', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:02,969] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:02,969] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.013113ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:02,971] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:02,972] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.010014ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:02,973] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:02,973] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.008106ms (qToJ size 3): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:02,974] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:02,974] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.005960ms (qToJ size 4): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:02,991] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 4 messages (0 left in queue)
[2024-06-04 20:59:03,126] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 4 messages handled in 134.473801ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:03,962] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:03,963] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.008345ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:04,029] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 1 messages (0 left in queue)
[2024-06-04 20:59:04,109] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 1 messages handled in 79.009295ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:04,360] DEBUG  root            MainThread  signal_handler() : Signal 15 caught, exiting...
[2024-06-04 20:59:04,457] INFO  Main            MainThread        shutdown() : Stop jMQTT python daemon
[2024-06-04 20:59:04,457] DEBUG  JMsg.Rcv        MainThread   receiver_stop() : Stop requested
[2024-06-04 20:59:04,564] INFO  JMsg.Rcv        SockIn            _loopRcv() : Stopped
[2024-06-04 20:59:04,565] DEBUG  JMsg.Rcv        MainThread   receiver_stop() : Stopped
[2024-06-04 20:59:04,566] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004768ms (qToJ size 1): {'cmd': 'brokerDown', 'id': '141'}
[2024-06-04 20:59:04,566] INFO  Client141       Brk141Th     on_disconnect() : Disconnected from broker.
[2024-06-04 20:59:04,567] DEBUG  Client141       MainThread            stop() : jMqttClient ended
[2024-06-04 20:59:04,567] DEBUG  Main            MainThread        shutdown() : Sent Daemon Down signal to Jeedom
[2024-06-04 20:59:04,568] DEBUG  JMsg.Snd        MainThread     sender_stop() : Stop requested
[2024-06-04 20:59:04,611] INFO  JMsg.Snd        SockOut           _loopSnd() : Stopped
[2024-06-04 20:59:04,611] DEBUG  JMsg.Snd        MainThread     sender_stop() : Stopped
[2024-06-04 20:59:04,761] DEBUG  JMsg.Snd        MainThread            send() : Sent TO Jeedom 1 messages handled in 148.794174ms (qToJ size 0): [{'cmd': 'daemonDown'}]
[2024-06-04 20:59:04,762] DEBUG  root            MainThread        <module>() : Exit 0
[2024-06-04 20:59:08,794] INFO  Main            MainThread   set_log_level() : New log level set to: DEBUG
[2024-06-04 20:59:08,795] DEBUG  Main            MainThread         prepare() : Writing PID 328 to /tmp/jeedom/jMQTT/jmqttd.py.pid
[2024-06-04 20:59:08,795] INFO  Main            MainThread         prepare() : Log level   : debug
[2024-06-04 20:59:08,795] INFO  Main            MainThread         prepare() : Socket port : 0
[2024-06-04 20:59:08,795] INFO  Main            MainThread         prepare() : Callback url: http://127.0.0.1:80/plugins/jMQTT/core/php/callback.php
[2024-06-04 20:59:08,795] INFO  Main            MainThread         prepare() : PID file    : /tmp/jeedom/jMQTT/jmqttd.py.pid
[2024-06-04 20:59:08,796] DEBUG  Main            MainThread         prepare() : Apikey      : WHaN4NYLuLqLFnuuVraSM0RRbjc0NNfYV9sUe5C9GQBYmLKyK1Tg6Wunx92pQkNr
[2024-06-04 20:59:08,796] DEBUG  JMsg.Rcv        MainThread  receiver_start() : Start requested
[2024-06-04 20:59:08,797] DEBUG  JMsg.Rcv        SockIn            _loopRcv() : Start
[2024-06-04 20:59:08,797] INFO  JMsg.Rcv        MainThread  receiver_start() : Started, listening on [127.0.0.1:41717]
[2024-06-04 20:59:08,816] DEBUG  JMsg.Snd        MainThread       send_test() : Test successful
[2024-06-04 20:59:08,816] DEBUG  JMsg.Snd        MainThread    sender_start() : Start requested
[2024-06-04 20:59:08,817] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Start
[2024-06-04 20:59:08,817] INFO  JMsg.Snd        MainThread    sender_start() : Started
[2024-06-04 20:59:08,910] DEBUG  JMsg.Snd        MainThread            send() : Sent TO Jeedom 1 messages handled in 92.363119ms (qToJ size 0): [{'cmd': 'daemonUp'}]
[2024-06-04 20:59:08,911] DEBUG  Main            MainThread       open_comm() : Open Comm   : Sent Daemon Up signal to Jeedom, got data: ""
[2024-06-04 20:59:08,911] INFO  Main            MainThread     h_newClient() : Creating Client for Broker 141.
[2024-06-04 20:59:08,914] INFO  Client141       Brk141Th        on_connect() : Connected to broker 192.168.1.71:1883
[2024-06-04 20:59:08,915] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.008583ms (qToJ size 1): {'cmd': 'brokerUp', 'id': '141'}
[2024-06-04 20:59:08,918] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 1 messages (0 left in queue)
[2024-06-04 20:59:09,057] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 1 messages handled in 138.693571ms (qToJ size 0): [{'cmd': 'brokerUp', 'id': '141'}]
[2024-06-04 20:59:09,114] INFO  Client141       MainThread subscribe_topic() : Topic subscribed "esp-piscine/#"
[2024-06-04 20:59:09,115] INFO  Client141       MainThread subscribe_topic() : Topic subscribed "jeedom/interact"
[2024-06-04 20:59:09,115] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=True)
[2024-06-04 20:59:09,116] INFO  Client141       MainThread subscribe_topic() : Topic subscribed "jeedom/interact/advanced"
[2024-06-04 20:59:09,116] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004053ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,116] INFO  Client141       MainThread subscribe_topic() : Topic subscribed "jeedom/api"
[2024-06-04 20:59:09,117] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/ph_piscine/state", payload="7.507", QoS=0, retain=True)
[2024-06-04 20:59:09,117] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.003338ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/ph_piscine/state', 'payload': '7.507', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,117] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/tension_batterie_piscine/state", payload="0.26", QoS=0, retain=True)
[2024-06-04 20:59:09,117] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002146ms (qToJ size 3): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/tension_batterie_piscine/state', 'payload': '0.26', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,118] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/temprature_piscine/state", payload="20.75", QoS=0, retain=True)
[2024-06-04 20:59:09,118] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002623ms (qToJ size 4): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temprature_piscine/state', 'payload': '20.75', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,118] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/phvolt_piscine/state", payload="2.710", QoS=0, retain=True)
[2024-06-04 20:59:09,118] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002146ms (qToJ size 5): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/phvolt_piscine/state', 'payload': '2.710', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,119] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/orp_volt/state", payload="1.913", QoS=0, retain=True)
[2024-06-04 20:59:09,119] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002861ms (qToJ size 6): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_volt/state', 'payload': '1.913', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,119] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/orp_piscine/state", payload="624", QoS=0, retain=True)
[2024-06-04 20:59:09,119] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002861ms (qToJ size 7): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_piscine/state', 'payload': '624', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,120] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/temp__rature_piscine/state", payload="25.25", QoS=0, retain=True)
[2024-06-04 20:59:09,120] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002384ms (qToJ size 8): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temp__rature_piscine/state', 'payload': '25.25', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,120] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/status", payload="online", QoS=0, retain=True)
[2024-06-04 20:59:09,120] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002146ms (qToJ size 9): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/status', 'payload': 'online', 'qos': 0, 'retain': True}
[2024-06-04 20:59:09,158] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 9 messages (0 left in queue)
[2024-06-04 20:59:09,258] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 9 messages handled in 100.199938ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/ph_piscine/state', 'payload': '7.507', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/tension_batterie_piscine/state', 'payload': '0.26', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temprature_piscine/state', 'payload': '20.75', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/phvolt_piscine/state', 'payload': '2.710', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_volt/state', 'payload': '1.913', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_piscine/state', 'payload': '624', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temp__rature_piscine/state', 'payload': '25.25', 'qos': 0, 'retain': True}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/status', 'payload': 'online', 'qos': 0, 'retain': True}]
[2024-06-04 20:59:09,963] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:09,964] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.005245ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:09,970] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:09,970] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.003338ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:09,990] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/ph_piscine/state", payload="7.510", QoS=0, retain=False)
[2024-06-04 20:59:09,990] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.003099ms (qToJ size 3): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/ph_piscine/state', 'payload': '7.510', 'qos': 0, 'retain': False}
[2024-06-04 20:59:10,061] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 3 messages (0 left in queue)
[2024-06-04 20:59:10,143] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 3 messages handled in 81.417084ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/ph_piscine/state', 'payload': '7.510', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:10,559] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/orp_volt/state", payload="1.913", QoS=0, retain=False)
[2024-06-04 20:59:10,560] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004768ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_volt/state', 'payload': '1.913', 'qos': 0, 'retain': False}
[2024-06-04 20:59:10,645] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 1 messages (0 left in queue)
[2024-06-04 20:59:10,724] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 1 messages handled in 78.635216ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_volt/state', 'payload': '1.913', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:10,955] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:10,956] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.005007ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:10,961] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:10,961] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.002623ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:10,981] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/temp__rature_piscine/state", payload="25.25", QoS=0, retain=False)
[2024-06-04 20:59:10,981] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004053ms (qToJ size 3): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temp__rature_piscine/state', 'payload': '25.25', 'qos': 0, 'retain': False}
[2024-06-04 20:59:10,994] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/phvolt_piscine/state", payload="2.711", QoS=0, retain=False)
[2024-06-04 20:59:10,994] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.003815ms (qToJ size 4): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/phvolt_piscine/state', 'payload': '2.711', 'qos': 0, 'retain': False}
[2024-06-04 20:59:11,006] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/sensor/orp_piscine/state", payload="624", QoS=0, retain=False)
[2024-06-04 20:59:11,006] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004053ms (qToJ size 5): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_piscine/state', 'payload': '624', 'qos': 0, 'retain': False}
[2024-06-04 20:59:11,028] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 5 messages (0 left in queue)
[2024-06-04 20:59:11,128] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 5 messages handled in 100.536585ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/temp__rature_piscine/state', 'payload': '25.25', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/phvolt_piscine/state', 'payload': '2.711', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/sensor/orp_piscine/state', 'payload': '624', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:11,961] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:11,961] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.010014ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:11,972] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:11,973] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.008106ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:12,031] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 2 messages (0 left in queue)
[2024-06-04 20:59:12,119] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 2 messages handled in 87.970018ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:12,958] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:12,959] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.011444ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:12,967] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:12,968] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.010014ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:13,023] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 2 messages (0 left in queue)
[2024-06-04 20:59:13,122] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 2 messages handled in 97.781897ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:13,964] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:13,964] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.005007ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:13,971] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:13,971] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.004292ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:14,025] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 2 messages (0 left in queue)
[2024-06-04 20:59:14,099] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 2 messages handled in 73.504686ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:14,956] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:14,956] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.005722ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:14,962] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:14,963] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.006199ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:15,002] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 2 messages (0 left in queue)
[2024-06-04 20:59:15,093] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 2 messages handled in 91.334581ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]
[2024-06-04 20:59:15,964] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).e[0m", QoS=0, retain=False)
[2024-06-04 20:59:15,965] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.009060ms (qToJ size 1): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:15,971] INFO  Client141       Brk141Th        on_message() : Message received (topic="esp-piscine/debug", payload="e[0;33m[W][component:215]: Components should block for at most 20-30ms.e[0m", QoS=0, retain=False)
[2024-06-04 20:59:15,972] DEBUG  JMsg.Snd        Brk141Th        send_async() : Enqued the message in 0.007868ms (qToJ size 2): {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}
[2024-06-04 20:59:15,997] DEBUG  JMsg.Snd        SockOut           _loopSnd() : Sending 2 messages (0 left in queue)
[2024-06-04 20:59:16,083] DEBUG  JMsg.Snd        SockOut               send() : Sent TO Jeedom 2 messages handled in 85.793972ms (qToJ size 0): [{'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:214]: Component display took a long time for an operation (0.29 s).\x1b[0m', 'qos': 0, 'retain': False}, {'cmd': 'messageIn', 'id': '141', 'topic': 'esp-piscine/debug', 'payload': '\x1b[0;33m[W][component:215]: Components should block for at most 20-30ms.\x1b[0m', 'qos': 0, 'retain': False}]

Mick33 · Juin 4, 2024, 7:15

Je crois avoir trouvé: car dans le log jmqttd la température remontée est bonne par contre avec un nom erroné:
« esp-piscine/sensor/temp__rature_piscine/state »
Dans la commande j’ai corrigé est mis le même nom : "esp-piscine/sensor/temp__rature_piscine/state"et ca marche?
Par contre pourquoi le nom a été corrigé suite à la nouvelle version du programme ESP, sachant que le nom de la donnée n’a pas bougé dans le programme?
Mystère de l’informatique?

D’autre part j’utilise jmqtt pour Jeezigbee, les erreurs d’installation des dépendances n’auront elles pas d’effet sur le fonctionnement? Il serait préférable de ne pas avoir d’erreur ue puis je faire pour les supprimer?

akenad · Juin 4, 2024, 7:23

Mick33:

Merci @akenad pour votre retour, mais malheureusement je n’ai pas un niveau suffisant pour comprendre ton post.
Comme je disais précédemment à @Bad , il faudrait d’abord trouver la cause de l’erreur de synchronisation:
[  9% ] : Synchronize the package index :  ERROR 

Cette erreur est la même et précisée par l’erreur que j’indique plus haut et dont je fournie des liens pour l’expliquer et la résoudre.

En résumé:
-soit il faut remplacer manuellement une ligne dans un fichier
-soit le dev utilise la dernière version de dependance.lib
-soit remplacer debian 10 par debian 11

akenad

Mick33 · Juin 4, 2024, 7:52

J’interprète ton post comme des bugs dans la dernière version de jmqtt, et s’il faut modifier des fichiers; je ne veux pas me lancer là dedans, car pas compétent et j’aime comprendre ce que je fais. De plus, j’ai résolu mon problème sur une erreur de libellé entre le nom de l’info transmise et la commande, qui est apparue on ne sait comment? ( voir mon précédent post)
Merci quand même

akenad · Juin 4, 2024, 8:09

Il ne s’agit pas d’un bug dans jMQTT mais d’un dépôt debian 10 qui à été deplacé en archive.

akenad

Mick33 · Juin 4, 2024, 8:20

Tu parles hebreu pour moi? precises un peu mieux pour un non informaticien

akenad · Juin 4, 2024, 8:26

Pour essayer de simplifier et d’être clair, debian 10 n’est plus supporté d’ici la fin du mois et il est conseillé de faire un recovery sur l’Atlas pour passer de debian 10 à debian 11, au risque d’avoir des problèmes lors de l’installation des dépendances de certains plugins.

akenad

Mick33 · Juin 4, 2024, 8:30

J’espère que cela se fera automatiquement dans une prochaine version du core Jeedom, sans avoir à faire de recovery et éviter d’avoir des pb de dépendances avec d’autres plugins? C’est pourquoi je préfére ne pas prendre de risques inutiles.

Mips · Juin 5, 2024, 4:49

Ca n’arrivera pas.
Vous devez suivre la procédure pour migrer la box atlas vers debian11 (reset usine) sans cela plus aucun plugin ne fonctionnera à terme, vous êtes sur un système qui sera obsolète dans moins d’un mois.

En tant que dev on ne peut rien y faire, c’est à vous d’agir.

Mick33 · Juin 5, 2024, 7:12

C’est dommage pour les utilisateurs, d’apprendre par hasard ce problème au travers d’un problème rencontré, que je n’aurais pu voir forcément. Aussi, j’aimerais avoir une procédure précise pour ne pas avoir un système hors d’état.
Il aurait été plus simple que le service commercial Jeedom communique officiellement à tous les utilisateurs, une explication plus précise de ce problème, car tout le monde n’est pas expert et de transmettre une procédure claire aux clients de manière à pas mettre leur système hors d’état.

Mick33 · Juin 5, 2024, 7:20

Ceci n’est pas trés parlant pour moi, simple utilisateur sans être expert

akenad · Juin 5, 2024, 7:26

pour plus de détails, cliquer sur le 3ième lien que j’ai indiqué plus haut.

akenad