warning
Due to a user signaling 'ban' from Meross cloud I've actually reverted back this as a pre-release while further investigating the issue
This release, as the name implies, brings in Meross cloud connection for your devices paired with the factory app.
This will give you:
- automatic discovery of devices binded to your Meross account wherever they are (if you have devices here and there around the world binded to the same cloud account)
- communication (via official Meross cloud mqtt brokers) to any device (not only local LAN then..despite the
meross_lanname, that is..) - instant updates of device state since this will come through MQTT (no more waiting polling cycles to see your toggle state updates)
- synchronization of the device name from the cloud (what you configure in Meross app will be 'copied' over to HA)
- ability to add more than 1 Meross cloud profile (so if it happens you want to connect and control devices binded to different Meross accounts you can do so from the same HA instance)
These new features will work in addition to the existing ones, so your devices will still be able to communicate over HTTP in LAN (this is actually enforced even for devices which are reachable over Meross cloud MQTT in order to reduce the need for outbound traffic)
Ideally, installing the update, your installation should work as usual with no differences until you complete the configuration of a 'cloud profile'. meross_lan could automatically guess your devices are Meross binded and suggest you to configure a cloud profile for these but that's only an helper and, even if it doesn't show up, you can manually add the configuration the usual way from the 'Integrations' page. Here, when you manually enter a new integration for meross_lan, a new menu will ask you if you want to manually add a device or a (cloud) profile.
Enter your account name (email) and password and save the configuration: this will be enough to activate all of the features.
Depending on many factors you could see no apparent change in your installation i.e. no discovery if all of your meross account devices are already setup in HA and no other UI changes (you could see the names of your devices being updated but if you've already customized the device name in HA this will 'win' over the 'native' device name. If you want to have HA show the cloud configured names you'll have to cancel the device name customization in HA UI)
Also, the cloud list of devices (to retrieve the names and to discover newly added devices) is polled once a day to reduce risk of cloud account banning due to high 'rate of requests'
You should see instead the devices state is now updated instantly in HA UI if you toggle them from the Meross app or on the physical appliance
This release, of course, is so new, many things could go wrong, even if deeply tested. Nevertheless, it is possible to revert back to the old stable Lazy at any time though. Just delete any 'profile configuration' from your integrations page if you plan to do so before downgrading since the old ones could mess a bit their configuration if they load a cloud profile.
Any comments or discussion is really welcome here!
warning
- A lot of backward compatibility code for HA cores back to 2022.1.0 (and earlier) has been removed: I didn't actually tested it but this version should be reasonably compatible with cores from 2022.5.0
features
- Meross cloud profile integration. Info here
- new Protocol sensor which reports the current state of connection i.e. it tells you if the device is 'actively' communicating over HTTP or MQTT.
- diagnostics were updated to support the cloud profile. Also the obfuscation logic was remanaged a bit (This would need a specific post to be explained)
- enriched support for smokealarm sensors (GS559) (#282 #183)
- basic support for doorwindow (MS200) (#281)
- added translation support for thermostat presets