I have just developed a Java library to control Meross IoT devices with the aim to base a binding on it. Could anyone help me testing and give me some feedbacks? Here is the repository:
https://github.com/fabgio/meross4j
Thanks in advance
Giovanni
Hi @fabgio. I am interested in your work on this. I have a Meross Wifo Garage Door opener (MSG100) and want to integrate it in my OH system. For me, a key requirement is to have this unconnected to the Meross cloud. So I definitely need to connect to a local MQTT broker (or have one built into the binding). I have been considering creating a binding, but I notice you are already working on it.
How is the progress? Is the binding code already somewhere on GitHub? Can I help?
By the way, are you aware there was previous work to create a Meross IOT Java library: GitHub - atzbert/meross-java? Maybe there is still something there to learn from. My slight worry with that one is that it pulls in a lot dependencies beyond the typical OH dependencies.
I have developed the nikohomecontrol binding, that also relies on MQTT internally. In contrast to Meross, the MQTT broker is built into the Niko Home Control Controller, so I don’t need a separate one. For Meross, my view would be to rely an a separately installed MQTT broker that needs to have TLS enabled (so needs to be documented) and give the parameters for that as input parameters to the binding. Ideally, the binding should then have an HTTP endpoint for the initial device configuration, where the relevant parameters can be retrieved. The Meross Custom Pairer app (https://github.com/albertogeniola/Custom-Meross-Pairer) could then be used for the initial setup. When a device configuration is started, it should also be listening to and acknowledging the initial MQTT message coming from the device.