This release adds better cloud MQTT traffic management in order to reduce the risk of Meross cloud account 'ban'

It does so by 'absolutely' limiting the rate of outgoing MQTT messages to a maximum of no more than 1 every 12 seconds per MQTT broker.
This means that if your devices are all (or a group of) binded to the same public broker, they'll share the bandwidth together.
When a mesage is about to be sent, the timeout will be checked and if not expired, the message will be queued. Maximum number of messages in queue will be 6 currently, meaning the queue could grow to more than 1 minute in duration before being fully flushed.
If the HA/meross_lan environment keeps trying to push messages (like toggling or setting entities), those will be discarded (a warning will be logged if this happens).
The overall rate of outgoing messages has also been reduced when devices are only communicating over MQTT (that is when the device is not reachable via HTTP)

Here a full explanation on the Cloudy release

fixes

• Meross account ban #285