After some time (and a lot of coding) here the very early preview of the new release for meross_lan.
Beside the major update and consequent name change I'd want to share what are the main drivers for this release and the plans about this repository.
First things first:
This is very experimental and, from now on, the labeling of releases will follow a more conforming convention where:

• *.alpha releases are those under heavy development where things might not really be as reliable as they should be.
• *.beta are, of course, better refined and the development of new features is usually limited to minor patches so that, overall, except maybe specific parts of the code where those new features are being added, the software behaves consistently and should not pose much issues as per reliability.

As usual, this kind of preview releases will be marked in the repository as pre-releases so that, usually, HA/HACS should not 'invite/force' you to install these.

This development cycle which will mark the forthcoming release as 'X' (meaning something like a 'crossing point') is aiming at better modularization so that this integration component could be, later than sooner, integrated in the HA core repository in order to make it available without the need of HACS or any manual installation. In order to do so, I'm isolating all the communication details into a separate package which will became an independent library/repo over the time. The way towards this goal is still long enough that I cannot estimate when this will happen.
As it is now, the big part of code redesign has been done so that, if everything performs as reliably as it should be I guess I can say I'm past half the path.

Now to the interesting part:

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.
• Added an improvement on mst100/200 devices implementation. mst200 should now be correctly detected and the 2 sprinkler toggles installed. Again, not sure it actually works but this should be an improvement for #641 #644. The implementation should be more stable now so that 'hub disruptions' experienced when installing the mst200 should not happen anymore.
• 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)

fixes

• no particular fixes are released with this version

final notes

The deep component re-design is urging me to change the convention used to internally register entities in the HA database so that, sooner or later, a migration will be needed. After that, it will not be possible to re-install a previous version without risking loosing entity history (in some way: it is not effectively loosed, it would just sit 'somewhere' in the HA database). My commitment, right now is to postpone this as much as possible so that, especially in this phase of early alpha's, it would be easier to switch between installation releases (just re-install the desired version) without worrying about a full HA db backup.
This is to say this version should be relatively easy to roll-back (should of course ;)