This is a big update since 5.8.0 including fixes for almost all of the current standing issues and improvement requests. This code release has been already published in preview at different stages of development so that many of the features in the following list are not very new if you installed any of the pre-release versions. This official new release is not any different from latest beta.
This release should be 'ready for 2026.11' since it already includes some new incoming compatibility issues. It has been tested against HA core 2026.11.0b2

features

• Multi-channel devices (like em06 or msg200) now expose one HA device registration per channel so that this makes it easier to group entities related to the same channel. This also allows leveraging the HA naming conventions where entity names can 'inherit' device name (see #580). Entity naming itself is still to be 'modernized' so I didn't care too much fixing or changing how entity names are generated (they should mostly be the same as before) so you can expect maybe some funny naming here and there depending on the device type and/or channels layout. Of course, this only applies to component generated names so that any customization you made to either entity name or entity Id are preserved being stored in the HA entity registry.
• Hub devices now expose a 'Pair subdevice' button (where supported by the hub) to start the pairing procedure without having to press the physical button on the hub device. (This feature is optimistic i.e. I didn't test it works in real)
• Some 'beep' entities were added for some subdevices (those who expose them - like mts150). I don't know what the feature is about but I suspect it controls a sort of alarm enable/disable for the device when it enters a critical/warning state.
• mts200 (and the likes) supporting summer mode now have a dedicated toggle (see #558) to control the feature and you cannot use the HVAC mode property to switch mode (like in previous versions)
• improved support for mst100/mst200
• added support for (some) devices configuration like ms130-mst100-mst200
• 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).
• improved detection/discovery of devices after they've been binded to a Meross cloud server
• added Slovak translation (thanks to @OskarSidor with #677)
• added support for PID parameters in mts150 valves
• added dedicated sensor entities reporting the motor state of mts150 valves in more detail (i.e. reporting actual valve 'aperture' so to have an indication of 'heating demand' as determined by the valve - see #688/#690)
• added support for 'LedMode' (kind of DND light) handling on supported devices (#683)
• improved/restructured communication errors reporting (handling and logging)
• added an extra attribute to 'Protocol' (diagnostic) sensor reporting the full namespaces states (i.e. the received raw payloads from the device)
• implemented the 'water flow' reporting binary sensor for mstXXX sprinkler devices (according to #671)
• improved 'Overtemp' alarm configuration (#347)

fixes

Almost all of the pending issues should be fully covered here. Check the status (fixed) in the related page to see if and when. In order to tidy up the repository state, all of those are going to be marked closed in the next hours/days as soon as I consider them closed. Please re-open or follow up if any needs further investigation or problem-solving.