X (6.0.0-alpha.4)

Component development is still undergoing and the release cycle is not ready yet for a stable, definitive version.

In this release, the ability to upgrade devices firmware has been disabled since I've found some possible issues due to the different hardware platforms available for the same device (which of course need different fw releases). A patch has been submitted by @cbusillo and already merged in this codebase but the issue left me with the idea I need to get a better picture of the whole process.

features

• added configuration option to fine tune the rate limiter behavior in Meross cloud profile. The rate limiter has an hardcoded overall rate of 200 messages/hour. The configurable parameter allows to increase/decrease the 'window size' for the algorithm implementation allowing to better tune the allowed 'burst'. Increasing the window size the algorithm would allow bigger bursts (i.e. more messages in a short time frame) but this will of course increase 'latency' in case the time window gets filled by messages (say you send 100 msgs in a short frame, then you must consider you have used half of the hour budget).
• added support for PID parameters in mts150 valves
• improved the 'bind' configuration option (added consistency checks and improved overall resiliency)
• improved detection/discovery of devices after they've been binded to a Meross cloud server

fixes

• minor fixes