Desactivation des services cloud par MEROSS :(

Bonjour les gens :slight_smile:
j’utilise ce plug in depuis quelques semaines seulement avec une multiprise et ma foi ça marchait pas mal jusqu’à aujourd’hui :frowning: j’ai reçu un petit mail de MEROSS :

Citation
Dear Customer,
This is meross cloud security team contacting you.
First of all, thanks for purchasing meross and we hope that you enjoy life with our smart products.
Recently our cloud security system has noticed that your devices are communicating with the could server at an extremely high frequency. We consider these behaviors abnormal and are concerned about the security of your devices.
Due to the security concerns and the intent to avoid any further potential damage, we will terminate the cloud services of these devices for now.
If you are sure that your devices are safe, NOT hacked, and are performing as expected. Please first lower your periodic request rate to no more than one message every ten seconds and then send an email to < cloudservice@meross.com >. We will resume cloud service for you within 24 hours. Please note that any abnormal high cloud request frequency will cause cloud service termination again.
Should you have any information you would like to provide us with or would like to offer us any clarification, please contact us within 24 hours.
Thanks!
meross Cloud Security Team

c’est embêtant :slight_smile: je les ai contacté, je leur ai expliqué mon intégration à jeedom et j’ai eu comme réponse ceci :

Citation
Hi Pierrick,
Thank you for the message.
After you have changed the related settings as required, the connection will be resumed automatically within 24 hours. If you are not sure about that, please factory reset the smart devices and configure them from scratch.
Please know that only meross app, eHomelife app, Google Home, Amazon Alexa, IFTTT are officially supported by us, any other customized IoT solutions or API may have get such problem
Thanks for your understandings.
Best regards,
Meross Cloud Team

Donc logiquement je vais retrouver les services demain.

J’ai relu la doc du plug in et je ne me rappelais plus qu’au départ on mettait un temps d’interrogation du cloud, je suppose que j’ai dpu mettre un temps trop faible qui fait que je « sature » meross avec les demandes émanant de jeedom.

Avez vous eu ce genre d’expérience avec ce plugin ?

Merci

Pierrick

C’est bon à savoir. Moi de mon côté, j’avais allongé le temps car j’avais des soucis passé les 6 prises Meross, c’est vrai qu’avec le recul, ça marche plutôt bien mais le Cloud, c’est risqué.