search

Apollon77 / ioBroker.meross

ioBroker Adapter to integrate Meross Cloud based devices
MIT License
23 stars 7 forks source link

Meross Service Termination, Polling Intervall not working? #370

Open AdiosOnline opened 2 months ago

AdiosOnline commented 2 months ago

I get blocked from meross cloud due to their cloud security system has noticed that your devices are communicating with the could server at an extremely high frequency.

In polling intervall i configured 180 sec and 30 min.

Meross says ist polls every 10 seconds. I assume some parameters dont work on my iobroker?

(warn: meross.1 (14560) Can not get DNDMode data for Device 2308042096157362080248e1e9d4c09c: Error: Timeout / undefined)`

I am using following Versions: meross.1v1.17.0 js-controller 6.0.9 Node.js: v20.16.0

Apollon77 commented 2 months ago

Pleas eenable dbug log then you should see in which interval it polls really ... there are no other reports of issues known. Soi please share a log

AdiosOnline commented 2 months ago

Hi, I changed to debug and let some minutes pass.. Log attached. I apprecciate your help.

meross.log

Apollon77 commented 2 months ago

Hm ... ok this DNDMOdde which returns nothing seems to really be a problem ... I will adjust something

AdiosOnline commented 1 month ago

Hi, any updates here? Meross is still dropping Mails out to me. I paste them below: `Dear Customer, We hope this message finds you well. This is the meross Cloud Security Team reaching out to you. Recently, our security system detected that your device/app is communicating with the could server at an extremely high frequency. We consider these behaviours abnormal and are concerned about the security of your device. Important Requirement: To ensure optimal performance and security, please limit your device's communication to no more than 200 messages every one hour. Potential Causes and Recommended Actions:

  1. Unofficial Platforms: If you are using unofficial third-party platforms or scripts (e.g., Home Assistant, ioBroker, other plugins on Github), please ensure they are updated or discontinue the use.
  2. Frequent Human Errors: We suggest that you avoid unnecessary or excessive erroneous operations with your device.
  3. Device Malfunction: If your device is malfunctioning, please try restarting it. If the problem persists, consider resetting and reconfiguring it. Please take the necessary actions within 72 hours of receiving this email. Failure to do so may result in the termination of cloud services for your devices to prevent further potential damage. We appreciate your prompt attention to this matter and your cooperation. If you have any questions, feel free to reach out to us at support@meross.com Best regards, Meross Cloud Security Team`