Ops, if internet is down I can’t turn off/on the power strip? And I don’t see physical buttons either…
That’s a huge limitation…
Hi all,
I need your help guys!
Can you all go to https://github.com/carlosatta/hassio-addons/issues and create an issue for bug and new request?
I’m working on this project right now, and have some problem to track (remember) all the request.
THANKS! 
Hi all,
I have rewrite the addons completely and I think a lot of bugs an little problems are fixed now.
To update I think is necessary to rebuild the addons after the upgrade prcedue.
Probably, this version have some bugs, so if you guys want to help me go to https://github.com/carlosatta/hassio-addons/issues and write down every problems you found, and suggestions too
Thanks!
4 Likes
Hi,
Thanks @carlosatta for this addon, it works really well, search for weeks how to integrate those meross power strip.
As I’m not for now a hassio user, I’ve work on a separate docker integration, only docker and script plumbing 
I’ve push it on my github if this can help https://github.com/rimram31/ha-meross-carlosatta
Not fully satisfied as I’ve copied all of carlosatta code as an idiot but may be a material for those who want to use it.
1 Like
thanks a lot @carlosatta for this addon.
if i understand correctly , we need to first set up a mqtt broker .
i’m running Hass.io only , so i tried to activate mosquito broker , then your addon.
i can see in the mosquito addon log and in your addon log that everything seems to works fine, but my mqtt integration tab is empty.
can you tell me what are the prerequiste ?
what i have done :
- install and start mosquito broker addon : no changes on defaut config
- install and start your meross addon : i changed only the host and the meross cloud credit
- add
mqtt:
discovery: true
discovery_prefix: homeassistant
in configuration.yaml
- restart HA
- add mqtt integration
did i missed something ?
First install Mosquitto MQTT, then this is the addon config:
{
“logins”: [
{
“username”: “MY_USERNAME”, #your MQTT username, between "#
“password”: “MY_PASSWORD” #your MQTT password, between "#
}
],
“anonymous”: true,
“customize”: {
“active”: false,
“folder”: “mosquitto”
},
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
}
Then this is my configuration.yaml file section for MQTT (with Mosquitto):
mqtt: discovery: true discovery_prefix: homeassistant broker: core-mosquitto keepalive: 60 username: MY_USERNAME password: !secret password_mqtt #aka MY_PASSWORD#
and this is my Meross addon configuration (inside addon window):
{
“mqtt”: {
“host”: “192.168.1.110”, #(this is my HA IP where Mosquitto is installed)#
“port”: 1883,
“protocol”: “mqtt”,
“username”: MY_USERNAME", #(same as Mosquitto one)#
“password”: “MY_PASSWORD”, #(same as Mosquitto one)#
“rejectUnauthorized”: false
},
“topic”: {
“discovery_prefix”: “homeassistant”
},
“meross”: {
“email”: “MEROSS_USER_EMAIL”, #my Meross email as used in App#
“password”: “MEROSS_USER_PASSWORD” #my Meross password as used in App#
},
“devices”: {
“refresh”: 10000
}
}
“#” means my comments. Nothing more, nothing less.
I hope it’ll help you!
1 Like
Hey guys,
I got my Meross mss110 switches working with version 0.88.1 using custom_components (thanks to soberstadt’s repo)
3 Likes
@hurstc:
As I wrote in your github repo issue page, I cannot use your method because it makes hanging my HA 0.88.2 (Hass.io). Seems some error in python because looking at hdmi video output, it seems hanging on 3.7.1 (setup?)… All I can do is access via ftp and delete the custom_components
Hi, i tried the component and working fine!
is it possible to read the power consumption from the switches?
i’d like to use it to notify when the whasing machine has done.
Thx
Does anyone know if this works with the Garage Door Opener (MSG100)? I set it up, and it appears in my MQTT broker, but nothing happens when I try to use it.
Same thing for me, shows up as a MQTT switch but doesn’t open/close the door.
Hi Just got from Amazon a Meross MSS310HIT
Do you know if it is possible to get energy consumption in HASS?
Hi tried to install it in HASSIo but failed, opened an issue in github
Hi, any update on this?
Hi,
this is just to add my two cents to the discussion.
I created a Home Assistant custom-component for Meross devices, based
on the work done by Alberto Geniola and Chris Hurst.
You can find it here: https://github.com/vincenzosuraci/hassio_meross_sensor_switch
This custom-component has both sensor and switch capabilities. It means that you can control the switch (on/off) but also monitor its sensors, if it equipped with sensors. For example, mss210 can only switch, while mss310 can switch on and off, but also provides current, voltage and power measurements. With this component you can handle both.
I tested it only with my Meross mss310 and mss210 v2.0.0, but any help to extend it to other Meross devices is more than welcome.
Have fun with it.
Regards,
Vincenzo
1 Like
Hi, just installed your component, seems to work fine. I have one meross plug with energy monitor MSS310HIT.
But which are the mqtt commands for switch on/off and energy monitor? Below I see in log the topic created
homeassistant/switch/18112xxx_0/state.
homeassistant/switch/18112xxx_0/config.
homeassistant/switch/18112xxx_0/.
homeassistant/sensor/18112xxx_0_current/config.
homeassistant/sensor/18112xxx_0_voltage/config.
homeassistant/sensor/18112xxx_0_power/config.
Hi, I tried your component, installed it, put the correct credentials, but no switch is created, and nothing in log!
Hi Klagio,
take into account that the hass component relies on the python meross iot library created by albertogeniola, so if you have a Meross device that is not supported by that library, also the hass component will not work. First of all, I suggest to you to check the compatibility list (link).
I tested the home assistant component on with my Meross devices (mss310 and mss210 version 2.0.0). When I started developing the hass component, my Meross devices were not working with the meross iot library created by Alberto Geniola. I get in contact with him and we discovered that I had a new version of the Meross devices (version 2.0.0 instead of 1.0.0) so, studying the python code of the meross iot library, I found that my Meross devices had a different get_status() function output. So, I provided this output to Alberto Geniola, and he developed a new version of the meross iot library.
So, in case your device is not supported and if you are familiar with python, I still suggest you to try to use the meross iot library, collect the get_status() function output and open a new issue here.
Regards,
Vincenzo
How can I configure your addon with auto discovery in configuration/integration
To change manually the state of a switch, you have to publish on topic homeassistant/switch/18112xxx_0/command the message 1 to turn on, or 0 to turn off.
1 Like