Plugin for Meross Devices

---

Hi pimatic community,

I was wondering if anyone is playing with Meross devices?
Recently stumbled across their garage door opener, bought it, installed it and noticed they got a lot of very cheap home automation hardware.
=> https://meross.com/
One drawback is, that they only work over their cloud service and have no local API (and won’t do that - I already asked the support).

Anyway, I was wondering, if anyone with more programming skills could make a pimatic-plugin?

Part of the work (how to connect to the cloud service) should already been done in https://github.com/Apollon77/ioBroker.meross

Thanks for your feedback!

Anyone who is interested to look into this may also want to have a look https://github.com/Apollon77/meross-cloud
As far as I can see this project represent the ground work done as part of the development of the iobroker adapter. The library allows to login into the Meross cloud server, read the registered devices and implement the basic message processing via MQTTS including signing POST message data.

Another source to look at is https://github.com/albertogeniola/MerossIot which provide a library for python which include a simple sniffer for meross protocol messages.

If anyone has information on how to enroll a developer account or has other useful information to share for meross please post it here

It should not be complex to make a plugin for this. So i’m a willing to give it a try.
I don’t own a Meross device and that could be a problem for testing.
@Wolfpack: which devices would you like to be supported?
@mwittig: why would you need a developer account?

@bertreb said in Plugin for Meross Devices:

@mwittig: why would you need a developer account?

@bertreb As @Wolfpack stated it is apparently not possible to control the devices directly via local network access, but you have to use the cloud services provided by meross. Thus, you’ll need a cloud account to test with. Ideally this account should contain some simulated devices similar to what home connect developer provides.

When I glanced over the meross site I could not find any information for developers or a possibility to enroll a regular account. Presumably enrollment is done exclusively via the smartphone app. Regarding developer resources you may want to contact the meross support. For testing maybe @Wolfpack is willing to share his account with you (if the door opener is not yet installed in the garage). If meross does not provide test ressource and @Wolfpack is not able to share his account for some, I am happy to donate a smart bulb or smart socket. Just let me know in case

@bertreb Thank you for your commitment to this subject!
I would need the Meross MSG100 garage opener (https://meross.com/product/29/article/)
Depending on the possibilities, the following features would be nice:

• Control open/shut action
• Read current garage sensor state (opened/closed)

The device consists of two components:

• a trigger that closes the contact for a set time, simulating a manual hand button for garage opening
• a magnetic sensor pair, which you fix one to the garage door and one to the garage wall. If the two magnets meet, it’s “closed”, if the two magnets are on different locations, it’s “open”.

It’s a pretty funny device, of which the seperated functions can also be abused for other purposes. You could build a “remote hard reset device” by connecting the open/close-contact to the reset port of your computer/server. You could use the open/close-sensor as “WiFi door/window contact sensor”.

@bertreb, if you need a device, I would also chip in a device (a garage sensor, smart bulb, smart socket or something like that). Do you live in Germany? If yes, you can send me your postal details by PN and I can order a device on Amazon and let it send directly to you.

@mwittig and @Wolfpack both thanks for your offer, but i hope i can progress without it.

I ordered a smart socket, so testing the interfacing is ok. You create an account via the app and i assume devices are added via the app to the Meross cloud.
After that the plugin should be able to discovery added devices and use them.

I’ll start with the smart socket and when the basics are working i will add the MSG100.

@Wolfpack I received meross smartplugs (type 230) and i’ve got them working in the plugin.
The garagedoor is also more or less ready, but i can’t test it.
Is it possible for you to test ?

@bertreb Nice! Of course I would test it - what a question.
I guess it won’t be available as installer, but I hope I can figure it out with your sources…

You can install the first version (0.0.1) of pimatic-meross via the pimatic plugin manager.
You need to have node 8 or higher because of the used meross library.
When the install/restart is successful, i would like to get the following complete log data
The first one starting with "AllData: " and the second one with "Garagaedoor State: "

@bertreb Perfect you made it into an installer! Unluckily, I’m still on Node 4.9.1 and get the warnings. When I was searching for an upgrade path, all recommodations were “stay at 4.9.1 for stable operation”. Do you have a quick upgrade path from 4.9.1 to last known working stable? Otherwise, it would take me some time to search for myself, backup and upgrade it.

Anyway the installation went through, the node warnings came up, but the plugin was able to activate and I was able to enter my cloud account in the configuration. Is this state maybe already sufficient for sending the log to you (if you give me a short hint, which log and where to find it).

Thank you!

Ok, you can find the log in the home directory of pimatic (/home/pi) its called deamon.log
Or under Info in the message tab in the Gui.
But because of the errors i wonder if the plugin will start.
Do you have any plugins that keeps you on node 4?

Thank you - unluckily the plugin seems to not start up with pimatic under node 4.9.1.
I don’t know if any plugin depends on 4.9.1. I will have to make a backup and try to upgrade it. I will do it as soon as I can, but I fear I won’t make it until next weekend… Sorry!

Going to node 10 is not complex. It’s not an upgrade but a new install with your current config.
If you got an empty sd-card or usb drive, you can install eg the stretch lite image and then follow the instructions.
The ‘old’ sd-card is your back-up

After putting your current config.json in the new pimatic-app home directory, you start pimatic and the system will install itself.

As if I expected it. Went though a lot of errors and have to wait for feedback from another developer. I had a branch of pimatic-fritz which supports multiple AVM Fritz-Boxes which now causes installation problems. But I hope to sort it out over the week.

Ok, good luck with the upgrade.
You could also leave the branch of pimatic-fritz on the current pi and create a new pi for node10 capable plugins.
I created the pimatic-mesh plugin to support these situations by connecting the old to the new pi.

@bertreb I finally did it! According to the logs, it manages to connect and read the GarageOpener from the Meross-Cloud. I send you the relevant data by chat. If something is missing, please tell me!

Thats good news! I will pick it up again.

In a coproduction with @Wolfpack, the Meross plugin is developed, tested and ready for usage. It supports the SmartPlug (mss210) and the Garagedoor Opener (msg100). If there’s interest more devices can be added. Version 0.1.0 is available via the plugin page in Pimatic. The minimum node requirement is v8.

More info

Thank you very much @bertreb for your work! I also got a SmartPlug next to my Garagedoor-Opener and both devices work flawless. I can recommend to everyone to taka a look at the garage opener, as it can be used for widely more as only opening garage doors.

Does anyone use the Meross Smartplugs MSS310?
Is it possible to control them with pimatic?