Thanks @deus
To gather the messageid for my mss310, there is a interesting way to do it here : https://github.com/albertogeniola/MerossIot/wiki/Device-pairing
I’ll test it
Glad to help @bonilla
I found some time to cludge together a rough script.
Use this to retrieve your messageid, sign and timestamp to be used for the REST request.
It worked , thanks @deus
Do you have found a way to have a tile with consumption and status on lovelace?
I have actually taken apart a Meros MSS410F Power Strip (4 AC Outlet) thinking it would use a ESP8266 like everything else…
But this particular one actually uses a MediaTek chipset called the MT7682S.
Specs:
192MHz ARM® Cortex®-M4 with FPU
RAM
Up to 384KB SRAM, with zero-wait state and 96MHz maximum frequency
Up to 32KB L1 cache, with high hit rate, zero- wait state and 192MHz maximum frequency
Embedded 8Mbits flash, with less than 0.1μA (typical) and 80MHz maximum frequency deep power-down current
I/O
1 SDIO 2.0 master and 1 SDIO 2.0 slave
1 I2C (3.4Mbps) interface
3 UARTs (3Mbps and with hardware flow control)
1 SPI master and 1 SPI slave (both SCKs are up to 48MHz, quad mode)
2 I2S interfaces
5 PWM channels
14 GPIOs (fast IOs, 5V-tolerant)
1 channel 12-bit AUXADC
If anyone is interested, I used https://github.com/albertogeniola/MerossIot to make a custom component: https://github.com/soberstadt/homeassistant-config/blob/master/custom_components/meross.py & https://github.com/soberstadt/homeassistant-config/blob/master/custom_components/switch/meross.py
I have been running this stably for two weeks now with my 110 models, so I can vouch for it.
https://github.com/ping-localhost/meross-custom-component is also out there that was based off my work, but I have not used it, so have fun
Can you share how I can use this and the rest api to setup this switch in HA?
I was able to login.py to get my details and I think I’ve added it correctly in HA config but any help you could give would be awesome?
Hey Craig,
The login.py is a POC script to retrieve your credentials etc.
I’ll spend a little bit of time over the next few days to integrate it into HA properly. Watch this thread for updates over the next week or two
I have create an addons for hassio to manage meross devices. It’s work connecting to meross api system and not directly to the devices.
For now is not documentated and it’ s a little bit more of proof of concept, but seems to work.
I hope this can help you guys.
Ciao Carlo
Can you explain some information needed in the addon config?
I see mqtt server info, but no username/password field.
The discovery prefix is fixed or can be changed?
Thanks
Hi,
the mqtt credential are not implemente or, more correctly, are inplemented in the code, but not in the configuratin part.
I try to implement it ASAP.
The prefix is configurable, but the default works well with the mqtt autodiscovery functionality of HomeAssistant. https://www.home-assistant.io/docs/mqtt/discovery/
Hello,
thank you for your help.
I have installed your addons and this is the log:
[email protected] start /usr/src/hassio_meross
node app.js
Connected to the device 1811061601760125181734298f17adad.
This means that the device was recognized? If yes how to add the relative card?
It is necessary install MQTT Server & Web client?
thank you
Hello,
I’m interested in this add on too. My devices are recognized, and I get the consumptions (MSS310) in the log but cannot find a way to get them in the UI.
Thanks
Hi,
I’ve update the code. Now you can use mqtt credential and certificate. Also I’ve add some documentation about configuration.
let me know.
Hi @ryolaxe,
the module shout work out of the box with hassio mqtt discovery functionality:
https://github.com/carlosatta/hassio-addons/tree/master/hassio_meross
If you want map the device manualy, you have to create some templates.
For the debug, I usualy use MQTTFX or HIVEMQT (http://www.hivemq.com/demos/websocket-client/)
let me know
Hi @matrixfede,
yes, you have to install a mqtt server and have a HA valid configuration.
https://github.com/carlosatta/hassio-addons/tree/master/hassio_meross
Ciao Carlo.
just updated and filled in all the field and it’s working fine.
Leaving “homeassistant” as mqtt prefix is the easy way to configure it, since you’ll find the switch name as you have defined in the Meross app.
Thanks!!!
Is there an easy way to get this to work in an Non HASSIO environment?
Like just a normal docker container?
Yes.
In the hassio-addons directory there is a Docker files and I think this can work in non-hassio env, but first you have to create a file options.json with all the configurations inside the module dir.
let me know if you succeed
Or, If you want, you can run it as a normal node script, maybe with pm2 or forever.