Problème avec plugin Meros IOT

[gmb85100]

Bonjour,

J’ai deux prises Meross MSS310 parfaitement installées sur l’application Meross de mon téléphone.
J’ai Jeedom 4.1.28 sur un RPI 3 b avec Raspbian GNU/Linux 9 (stretch).

Le plugin est bien installé :

quand je lance la synchronisation cela mouline pendant quelque seconde puis rien !
Aucun équipent n’est remonté.
J’ai régulièrement une notification comme quoi « de nouveau équipements Meross ont été détectés et qu’il faut faire une synchronisation ».
Je relance la synchronisation mais rien !

Avez vous une idée ?
D’avance merci

[anon53349806]

Sur ta capture en haut a droite on voit une rubrique Logs et dépendances.

Donner le log serait peut être un bon début

[gmb85100]

Ok merci
J’ai pb le site me dit
« Désolé, les nouveaux utilisateurs ne peuvent pas envoyer de fichiers »
Donc je ne peux pas envoyer les logs !

[anon53349806]

Les logs se copient collent entre balises…

[gmb85100]

Quand je fait copier et coller j’ai
Désolé, les nouveaux utilisateurs ne peuvent insérer que 2 liens par message.

[gmb85100]

He oui je suis débutant !!!

[Salvialf]

Salut,

En l’occurrence les logs ne sont pas des images ni des liens mais du texte donc ça ne devrait pas poser de problème. Un sujet rempli de bonnes informations à connaitre dont la manière de formater correctement des logs afin qu’ils soient lisibles :

Comment nous aider à vous aider - ou Comment poser une bonne question?

Avant de commencer… Ce forum n’est pas un Helpdesk La plupart des gens ici ne travaillent pas pour Jeedom SAS, à moins que cela soit spécifiquement indiqué dans leurs profils. Et même s’ils peuvent passer parfois sur le forum, ce n’est pas le moyen officiel d’obtenir du support. Les autres, nous offrons volontairement de notre temps libre pour vous aider. Certaines demandes peuvent ne pas recevoir de réponses et peut-être justement celle qui correspond à votre problème. [image] Il ne s’agi…

[gmb85100]

Restons courtois !
1- J’ai lut la doc et donc ce n’est pas d’une helpdesk que j’ai besoin !
2- Copier coller du texte je sais faire, mais quand je reçoit un incohérent je demande de l’aide.

3- Voici un extrait des log ci cela passe ce coup ci :

2022-02-07 17:31:08,819 - meross.connection - DEBUG - Executing message-id 939f1ac3e00e1e38d8764560a6425fab, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
Traceback (most recent call last):
File "/usr/lib/python3.5/socketserver.py", line 313, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 341, in process_request
self.finish_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 354, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.5/socketserver.py", line 681, in __init__
self.handle()
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 123, in handle
response['result'] = response['result'](*args)
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 341, in syncMerossConso
if device.online and device.supports_consumption_reading():
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 152, in supports_consumption_reading
return CONSUMPTIONX in self.get_abilities()
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 124, in get_abilities
self._abilities = self.execute_command("GET", ABILITY, {})['ability']
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 116, in execute_command
return self.__cloud_client.execute_cmd(self.uuid, command, namespace, payload, callback=callback, timeout=timeout)
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/client.py", line 301, in execute_cmd
raise CommandTimeoutException("A timeout occurred while waiting for the ACK: %d" % timeout)
meross_iot.cloud.exceptions.CommandTimeoutException.CommandTimeoutException: A timeout occurred while waiting for the ACK: 10
[2022-02-07 17:31:08][DEBUG][meross.connection](Thread-5) : Executing message-id 939f1ac3e00e1e38d8764560a6425fab, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:31:08,821 - meross.connection - DEBUG - Waiting for response to message-id 939f1ac3e00e1e38d8764560a6425fab
[2022-02-07 17:31:08][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 939f1ac3e00e1e38d8764560a6425fab
2022-02-07 17:32:18,825 - meross.connection - DEBUG - Executing message-id 8bc9c34e7688856033c5f47ec4c4f168, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:32:18][DEBUG][meross.connection](Thread-5) : Executing message-id 8bc9c34e7688856033c5f47ec4c4f168, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:32:18,828 - meross.connection - DEBUG - Waiting for response to message-id 8bc9c34e7688856033c5f47ec4c4f168
[2022-02-07 17:32:18][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 8bc9c34e7688856033c5f47ec4c4f168
2022-02-07 17:33:28,832 - meross.connection - DEBUG - Executing message-id f622e3020b91a40f4f07c626d5b14e5e, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:33:28][DEBUG][meross.connection](Thread-5) : Executing message-id f622e3020b91a40f4f07c626d5b14e5e, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:33:28,833 - meross.connection - DEBUG - Waiting for response to message-id f622e3020b91a40f4f07c626d5b14e5e
[2022-02-07 17:33:28][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id f622e3020b91a40f4f07c626d5b14e5e
2022-02-07 17:34:38,838 - meross.connection - DEBUG - Executing message-id 796cf9cf6e7b4384ca680109a41607eb, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:34:38][DEBUG][meross.connection](Thread-5) : Executing message-id 796cf9cf6e7b4384ca680109a41607eb, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:34:38,839 - meross.connection - DEBUG - Waiting for response to message-id 796cf9cf6e7b4384ca680109a41607eb
[2022-02-07 17:34:38][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 796cf9cf6e7b4384ca680109a41607eb
2022-02-07 17:35:48,843 - meross.connection - DEBUG - Executing message-id 00ac3425b3a2533ed3a2b69e5e823124, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:35:48][DEBUG][meross.connection](Thread-5) : Executing message-id 00ac3425b3a2533ed3a2b69e5e823124, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:35:48,846 - meross.connection - DEBUG - Waiting for response to message-id 00ac3425b3a2533ed3a2b69e5e823124
[2022-02-07 17:35:48][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 00ac3425b3a2533ed3a2b69e5e823124
2022-02-07 17:36:58,850 - meross.connection - DEBUG - Executing message-id 7d8ff3122aa424dcc2b8ac48fdd87b8f, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:36:58][DEBUG][meross.connection](Thread-5) : Executing message-id 7d8ff3122aa424dcc2b8ac48fdd87b8f, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:36:58,852 - meross.connection - DEBUG - Waiting for response to message-id 7d8ff3122aa424dcc2b8ac48fdd87b8f
[2022-02-07 17:36:58][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 7d8ff3122aa424dcc2b8ac48fdd87b8f
2022-02-07 17:38:08,856 - meross.connection - DEBUG - Executing message-id 7277c340cc4226a5062b83a71dcc0a6c, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:38:08][DEBUG][meross.connection](Thread-5) : Executing message-id 7277c340cc4226a5062b83a71dcc0a6c, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:38:08,858 - meross.connection - DEBUG - Waiting for response to message-id 7277c340cc4226a5062b83a71dcc0a6c
[2022-02-07 17:38:08][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 7277c340cc4226a5062b83a71dcc0a6c
2022-02-07 17:39:18,862 - meross.connection - DEBUG - Executing message-id edd1e694c2dac35e0eba99bbcea2a46f, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:39:18][DEBUG][meross.connection](Thread-5) : Executing message-id edd1e694c2dac35e0eba99bbcea2a46f, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:39:18,865 - meross.connection - DEBUG - Waiting for response to message-id edd1e694c2dac35e0eba99bbcea2a46f
[2022-02-07 17:39:18][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id edd1e694c2dac35e0eba99bbcea2a46f
[2022-02-07 18:40:03][DEBUG] : Mise à jour des consommations des équipements depuis le Cloud Meross
[2022-02-07 18:40:03][DEBUG] : callMeross syncMerossConso
[2022-02-07 17:40:03][DEBUG][root](Thread-4) : Message received in socket
[2022-02-07 17:40:03][DEBUG][root](Thread-4) : {'args': '', 'action': 'syncMerossConso'}
2022-02-07 17:40:03,685 - meross.connection - DEBUG - Executing message-id 2061d1357c3b3c6179a9d901724c7a80, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:40:03][DEBUG][meross.connection](Thread-4) : Executing message-id 2061d1357c3b3c6179a9d901724c7a80, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:40:03,687 - meross.connection - DEBUG - Waiting for response to message-id 2061d1357c3b3c6179a9d901724c7a80
[2022-02-07 17:40:03][DEBUG][meross.connection](Thread-4) : Waiting for response to message-id 2061d1357c3b3c6179a9d901724c7a80
[2022-02-07 18:40:13][DEBUG] : result callMeross
[2022-02-07 18:40:13][DEBUG] : Mise à jour des consommations terminées.
----------------------------------------
Exception happened during processing of request from b''
----------------------------------------
2022-02-07 17:40:28,869 - meross.connection - DEBUG - Executing message-id 520100e06f2c94cbb2c8e4bb5c1b11d4, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
Traceback (most recent call last):
File "/usr/lib/python3.5/socketserver.py", line 313, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 341, in process_request
self.finish_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 354, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.5/socketserver.py", line 681, in __init__
self.handle()
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 123, in handle
response['result'] = response['result'](*args)
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 341, in syncMerossConso
if device.online and device.supports_consumption_reading():
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 152, in supports_consumption_reading
return CONSUMPTIONX in self.get_abilities()
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 124, in get_abilities
self._abilities = self.execute_command("GET", ABILITY, {})['ability']
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 116, in execute_command
return self.__cloud_client.execute_cmd(self.uuid, command, namespace, payload, callback=callback, timeout=timeout)
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/client.py", line 301, in execute_cmd
raise CommandTimeoutException("A timeout occurred while waiting for the ACK: %d" % timeout)
meross_iot.cloud.exceptions.CommandTimeoutException.CommandTimeoutException: A timeout occurred while waiting for the ACK: 10
[2022-02-07 17:40:28][DEBUG][meross.connection](Thread-5) : Executing message-id 520100e06f2c94cbb2c8e4bb5c1b11d4, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:40:28,871 - meross.connection - DEBUG - Waiting for response to message-id 520100e06f2c94cbb2c8e4bb5c1b11d4
[2022-02-07 17:40:28][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 520100e06f2c94cbb2c8e4bb5c1b11d4
2022-02-07 17:41:38,874 - meross.connection - DEBUG - Executing message-id 3afff7b41b6bbebb19477d6cae48dab4, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:41:38][DEBUG][meross.connection](Thread-5) : Executing message-id 3afff7b41b6bbebb19477d6cae48dab4, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:41:38,875 - meross.connection - DEBUG - Waiting for response to message-id 3afff7b41b6bbebb19477d6cae48dab4
[2022-02-07 17:41:38][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 3afff7b41b6bbebb19477d6cae48dab4
2022-02-07 17:42:48,877 - meross.connection - DEBUG - Executing message-id 21ba2ef1244dd4e1dcd76f8a8c87ea57, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-07 17:42:48][DEBUG][meross.connection](Thread-5) : Executing message-id 21ba2ef1244dd4e1dcd76f8a8c87ea57, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-07 17:42:48,878 - meross.connection - DEBUG - Waiting for response to message-id 21ba2ef1244dd4e1dcd76f8a8c87ea57
[2022-02-07 17:42:48][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 21ba2ef1244dd4e1dcd76f8a8c87ea57

[Salvialf]

J’ai formaté les logs (toujours avec cette même balise dont on parle depuis ce matin) c’est beaucoup plus lisible non ?

Donc quand tu écris un message tu as une série d’icônes en haut, dont une qui permet de partager des logs lisibles :

[gmb85100]

Bonjour et merci pour tes explications.
Comme je l’ai dit je suis nouveau et peut habitué aux forums.

J’ai constaté dans mes logs une séquence qui revient régulièrement.
Dedans on peut voir une exception et un timeout !
Je ne voie pas quoi faire.

[2022-02-08 13:40:03][DEBUG] : Mise à jour des consommations des équipements depuis le Cloud Meross
[2022-02-08 13:40:03][DEBUG] : callMeross syncMerossConso
[2022-02-08 12:40:03][DEBUG][root](Thread-4) : Message received in socket
[2022-02-08 12:40:03][DEBUG][root](Thread-4) : {'args': '', 'action': 'syncMerossConso'}
2022-02-08 12:40:03,100 - meross.connection - DEBUG - Executing message-id 9b91488bc9a93c1f85ff606e17871082, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:40:03][DEBUG][meross.connection](Thread-4) : Executing message-id 9b91488bc9a93c1f85ff606e17871082, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:40:03,102 - meross.connection - DEBUG - Waiting for response to message-id 9b91488bc9a93c1f85ff606e17871082
[2022-02-08 12:40:03][DEBUG][meross.connection](Thread-4) : Waiting for response to message-id 9b91488bc9a93c1f85ff606e17871082
[2022-02-08 13:40:13][DEBUG] : result callMeross
[2022-02-08 13:40:13][DEBUG] : Mise à jour des consommations terminées.
----------------------------------------
Exception happened during processing of request from b''
----------------------------------------
2022-02-08 12:40:24,915 - meross.connection - DEBUG - Executing message-id 86c1bf7e73b9f2df0e559cc5a10f7820, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
Traceback (most recent call last):
File "/usr/lib/python3.5/socketserver.py", line 313, in _handle_request_noblock
self.process_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 341, in process_request
self.finish_request(request, client_address)
File "/usr/lib/python3.5/socketserver.py", line 354, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.5/socketserver.py", line 681, in __init__
self.handle()
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 123, in handle
response['result'] = response['result'](*args)
File "/var/www/html/plugins/MerossIOT/resources/MerossIOTd/MerossIOTd.py", line 341, in syncMerossConso
if device.online and device.supports_consumption_reading():
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 152, in supports_consumption_reading
return CONSUMPTIONX in self.get_abilities()
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 124, in get_abilities
self._abilities = self.execute_command("GET", ABILITY, {})['ability']
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/device.py", line 116, in execute_command
return self.__cloud_client.execute_cmd(self.uuid, command, namespace, payload, callback=callback, timeout=timeout)
File "/usr/local/lib/python3.5/dist-packages/meross_iot/cloud/client.py", line 301, in execute_cmd
raise CommandTimeoutException("A timeout occurred while waiting for the ACK: %d" % timeout)
meross_iot.cloud.exceptions.CommandTimeoutException.CommandTimeoutException: A timeout occurred while waiting for the ACK: 10
[2022-02-08 12:40:24][DEBUG][meross.connection](Thread-5) : Executing message-id 86c1bf7e73b9f2df0e559cc5a10f7820, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:40:24,918 - meross.connection - DEBUG - Waiting for response to message-id 86c1bf7e73b9f2df0e559cc5a10f7820
[2022-02-08 12:40:24][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 86c1bf7e73b9f2df0e559cc5a10f7820
2022-02-08 12:41:34,922 - meross.connection - DEBUG - Executing message-id 1fd1c5c17f21c15b5eb1cb5a62a4c744, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:41:34][DEBUG][meross.connection](Thread-5) : Executing message-id 1fd1c5c17f21c15b5eb1cb5a62a4c744, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:41:34,924 - meross.connection - DEBUG - Waiting for response to message-id 1fd1c5c17f21c15b5eb1cb5a62a4c744
[2022-02-08 12:41:34][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 1fd1c5c17f21c15b5eb1cb5a62a4c744
2022-02-08 12:42:44,928 - meross.connection - DEBUG - Executing message-id b88c7c52d5463676bd5bbc680360dca5, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:42:44][DEBUG][meross.connection](Thread-5) : Executing message-id b88c7c52d5463676bd5bbc680360dca5, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:42:44,930 - meross.connection - DEBUG - Waiting for response to message-id b88c7c52d5463676bd5bbc680360dca5
[2022-02-08 12:42:44][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id b88c7c52d5463676bd5bbc680360dca5
2022-02-08 12:43:54,934 - meross.connection - DEBUG - Executing message-id 12b4b3085c957459b2b87ad0e5a4ddbf, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:43:54][DEBUG][meross.connection](Thread-5) : Executing message-id 12b4b3085c957459b2b87ad0e5a4ddbf, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:43:54,937 - meross.connection - DEBUG - Waiting for response to message-id 12b4b3085c957459b2b87ad0e5a4ddbf
[2022-02-08 12:43:54][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 12b4b3085c957459b2b87ad0e5a4ddbf
2022-02-08 12:45:04,939 - meross.connection - DEBUG - Executing message-id 6f6a230d5048162fb2495bebed2f7668, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:45:04][DEBUG][meross.connection](Thread-5) : Executing message-id 6f6a230d5048162fb2495bebed2f7668, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:45:04,941 - meross.connection - DEBUG - Waiting for response to message-id 6f6a230d5048162fb2495bebed2f7668
[2022-02-08 12:45:04][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 6f6a230d5048162fb2495bebed2f7668
2022-02-08 12:46:14,944 - meross.connection - DEBUG - Executing message-id 33b6d7ea7b3f9733a5ab8a4455229d45, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:46:14][DEBUG][meross.connection](Thread-5) : Executing message-id 33b6d7ea7b3f9733a5ab8a4455229d45, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:46:14,946 - meross.connection - DEBUG - Waiting for response to message-id 33b6d7ea7b3f9733a5ab8a4455229d45
[2022-02-08 12:46:14][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 33b6d7ea7b3f9733a5ab8a4455229d45
2022-02-08 12:47:24,950 - meross.connection - DEBUG - Executing message-id 16e68b14c074ddee657b2c2955dd94ae, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:47:24][DEBUG][meross.connection](Thread-5) : Executing message-id 16e68b14c074ddee657b2c2955dd94ae, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:47:24,953 - meross.connection - DEBUG - Waiting for response to message-id 16e68b14c074ddee657b2c2955dd94ae
[2022-02-08 12:47:24][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 16e68b14c074ddee657b2c2955dd94ae
2022-02-08 12:48:34,957 - meross.connection - DEBUG - Executing message-id 5d8e6fc347b773ba767feb3318bfe569, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:48:34][DEBUG][meross.connection](Thread-5) : Executing message-id 5d8e6fc347b773ba767feb3318bfe569, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:48:34,959 - meross.connection - DEBUG - Waiting for response to message-id 5d8e6fc347b773ba767feb3318bfe569
[2022-02-08 12:48:34][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 5d8e6fc347b773ba767feb3318bfe569
2022-02-08 12:49:44,963 - meross.connection - DEBUG - Executing message-id 7503f1d25b9e60324280a10e201d0da5, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
[2022-02-08 12:49:44][DEBUG][meross.connection](Thread-5) : Executing message-id 7503f1d25b9e60324280a10e201d0da5, GET on Appliance.System.Ability command for device 2003319234684525189448e1e919374a
2022-02-08 12:49:44,965 - meross.connection - DEBUG - Waiting for response to message-id 7503f1d25b9e60324280a10e201d0da5
[2022-02-08 12:49:44][DEBUG][meross.connection](Thread-5) : Waiting for response to message-id 7503f1d25b9e60324280a10e201d0da5

Merci

[jercle]

Bonjour,

J’ai développé un nouveau plugin pour Meross pour l’instant en version beta (il faut autoriser les plugin beta dans votre profil market) et en cours d’acceptation par Jeedom.

Le voici disponible en version bêta : Jeedom Market

C’est très stable et sans risques à installer.

La documentation est disponible ici : MerosSync | Jérôme ROUSSEAU

N’hésitez pas si vous avez des questions