A full-featured Homeassistant component to drive Meross devices. This component is based on the underlying MerossIot library available here.
You can install this component in two ways: via HACS or manually. HACS is a nice community-maintained components manager, which allows you to install git-hub hosted components in a few clicks. If you have already HACS installed on your HomeAssistant, it's better to go with that. On the other hand, if you don't have HACS installed or if you don't plan to install it, then you can use manual installation.
If you have HACS, well, it's piece of cake! Just search for "Meross" (Full name is Meross Integration) in the default repository of HACS and it'll show up. Click on Install. When the installation completes, you must restart homeassistant in order to make it work. As soon as HomeAssistant is restarted, you can proceed with component setup.
-
Download the latest zip release archive from here
-
Unzip/copy the meross_cloud directory within the
custom_componentsdirectory of your homeassistant installation. Thecustom_componentsdirectory resides within your homeassistant configuration directory. Usually, the configuration directory is within your home (~/.homeassistant/). In other words, the configuration directory of homeassistant is where the config.yaml file is located. After a correct installation, your configuration directory should look like the following.└── ... └── configuration.yaml └── secrects.yaml └── custom_components └── meross_cloud └── __init__.py └── common.py └── cover.py └── ...Note: if the custom_components directory does not exist, you need to create it.
After copy-pasting the meross_cloud directory into the custom_components folder, you need to restart HomeAssistant. As soon as HomeAssistant is restarted, you can proceed with component setup.
Once the component has been installed, you need to configure it in order to make it work. To do so, navigate to "Configuration -> Integrations -> Add Integration" and look for "Meross Cloud IoT". As soon as you add it, you'll be asked to configure it. The following table summarizes the fields that the wizard will require you to fill in:
| Field Name | Example Value | Description |
|---|---|---|
| HTTP Api Endpoint | One of the following: - https://iotx-ap.meross.com (for Asia/Pacific regions) - https://iotx-eu.meross.com (for Europe) - https://iotx-us.meross.com (for United States) |
Is the HTTP(s) API endpoint used by the Meross Manager. This might vary in accordance with your country |
| Email Address | [email protected] | Your Meross account username/email. If connecting to the official Meross cloud, use the same from the Meross App |
| Password | R4nd0mS3cret | Your Meross account password. If connecting to the official Meross cloud, use the same from the Meross App |
| Skip MQTT certificate validation | True (Checked) | Configures MQTT certificate validation. When unchecked it requires a valid certificate to be exposed from the Meross Server. If checked, it skips the MQTT certificate validation. If connecting to the official Meross cloud, you can uncheck this. When connecting to local-lan or custom MQTT brokers, you might want to check this. |
The following animation shows an example of component configuration
This library supports all the Meross devices currently exposed by the Meross IoT library. In particular Bulbs, Switches, Garage Door Openers and Smart Valves/Thermostat are fully supported and perfectly integrated with HomeAssistant.
Have a look a the screenshots below...
It took a bit, but eventually it's here. A very first unstable version of the Local Meross Addon has been developed. The latest version of this component, v1.2.5rc1, does support it and has been tested successfully with both a MSS210 and a MSS310 devices. Please note that the usage of the Local Addon is only advised for all the advanced users who are experiencing problems with Meross security team, complaining about high rate API calls to their systems. If you plan to use such devices off-grid, the Local Addon is what you are looking for. Again, be avised: it's still a work in progress and your devices might not work as expected (for now).
You can find installation instructions for the Local Addon directly here.
Meross Plugin has gained great success and popularity among the HomeAssistant users. However, the Meross engineers are imposing new limits on their MQTT broker system, which cause problems to the HA users who want to implement aggressive polling or have more than 10 devices connected to HA. For this reason, I am working on a new HomeAssistant addon, namely "Meross Local Addon", which aims at re-implementing the Meross MQTT Broker and HTTP API layer locally to the addon. This would basically allow users to rely only on LAN-local connection, using HomeAssistant as command center.
In order to take advantage of the Local Meross Addon, you need to follow the instructions below:
-
Install or update the version of the Meross Custom Component via HACS (or manually, if you prefer) at least to version 1.2.5rc1, which is the first one supporting the Meross Local Addon.
-
Add the Meross Local Addon repository to your HomeAssistant installation. You can do that following the instructions here or simply press the following button
-
Make sure the "Meross Local Addon for Homeassistant" appears in the section of "community addons" and, if so, install it. At the time of writing the latest available version is 0.0.1-alpha42. Depending on the HA hosting system and on the internect connection speed, it can take up to 20 minutes for the installation to complete.
-
Navigate to the configuration section of the "Meross Local Addon" and make sure the option reinit_db is OFF, while the option "advertise" is ON. Leave debug_mode OFF, unless you need to provide supplementary logging information to debug issues. Make sure you don't have any firewall blocking the network traffic to the ports indicated on this section, as the addon will receive traffic from both meross devices and pairer app on such ports.
-
Navigate to the "info" panel of the addon and make sure the "Start at boot" option is ON. Also, make sure the "Show in menu" option is set to ON. Then, start the ADDON and wait at least 5 minutes. Depending on the device you are running on, the first boot may take up to 10 minutes to complete.
-
Open "Meross Local Addon" web-interface (you can either click on "Open Web UI" or click on the left menu icon
. Then, from the web-ui, click on "Wizard Setup" or on "Setup" and follow the instructions to configure your addon. For now, it's advised not to use the "Official Meross Link", as it is still under development.
-
The wizard will guide you through the Account Setup, Meross App installation and pairing process. Make sure you are able to pair at least one device. Note about Step 1, credentials setup: choose the username/password you will be using locally to pair your devices. If you don't plan to "link" the local addon to the official meross broker, you can choose whatever credentials you like. For instance, you can set: username:
meross@localpassword:changeme -
When you have paired all the devices you want to manage locally, you can proceed with the setup of the Meross Component. Navigate to the HA integration list, and proceed with the installation of the Meross Addon. During the setup phase, make sure to select local addon setup option, not the one relying on the official Meross Broker.
NOTE: sometimes, for yet-unknown reasons, MSS310 fails to pair with the local addon broker. However, resetting and retrying the pairing procedure a second time usually works. More recent devices, as the mss210, seem not to suffer of the same problem.
Credits to @olivermaor
When switching from a cloud based to a local integration, it is important that the correct sequence of steps is followed:
- Install the "Meross Local Addon", as described above, but do not start it yet.
- In the Settings - Integration panel, open the existing Meross IoT integration and copy or print the friendly names of the devices used.
- Go back to the Settings - Integration panel and delete the Meross IoT integration.
- Reboot Home Assistant.
- After the reboot has finished, access the file /config/.storage/core.entity_registry, and copy that file into the same directory as a backup (use a name like core.entity_registry_backup)
- After having backed up that file, open it (not the backup) with an editor, and find obsolete entries of entities which derive from the Meross IoT integration. Each entity is enclosed in a set of brackets ({ }). Delete these entries, and only these entries, this including the respective brackets. Be careful: The entities are separated by commas, but after the last entry in the entire list, a comma may not be set.
- Save the amended file, and reboot Home Assistant. If you made mistakes editing the core.entity_registry file, you can still revert to the backup.
- Now start the "Meross Local Addon" and pair the Meross devices one by one, using the pairing app. After each device had been successsfully paired, rename it in the addon, using exactly the friendly name which the device had before, when you used the cloud integration. Wait until it shows "online", eventually refreshing the browser page. Only after having done that, pair the next device.
- Be sure you have paired all devices, and changed their "friendly names". Only then add the Meross IoT integration, and select the local broker, as described above. Your devices will be re-discovered with the correct friendly names, and can be integrated into HA.
- If you have followed these steps, all devices should again work with all scenes and automations as before.
As you can imagine, there is a huge work behind this repo: first I need to reverse-engineer the Meross protocols, then I need to implement any "logic-layer" implemented on Meross Systems on the new addon I am developing and, eventually, I have to make sure that everything works together. That means that I am not able to spend much time in solving issues that may arise in the meantime, and for that I apologize. If you like this project and you want to support me, please consider donating: that motivates me and helps me buy more ram which is absolutely necessary when developing on a virtualized environment.
By buying me a coffee, not only you make my development more efficient, but also motivate me to further improve my work. On the other hand, buying me a beer will certainly make me happier: a toast to you, supporter! In case you are a pro and a strong opensource supporter, you might also consider sponsoring my GitHub work.
