-
After having issues with MyQ and them restricting the API further (using it with HomeBridge) I got a Meross unit last week and it’s working great. I’d love to see how I can help get this project to support Meross GDO’s. I have the MSG100 currently. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 22 replies
-
Hey, thanks for the interest. If you have any coding experience and want to contribute, I accept PR's. Otherwise I need to look around and see if there are any reliable go packages for Meross devices and see if I can incorporate that, or possibly port one from another language (I know there are Meross packages for python), but since I don't have a Meross, testing would be difficult. If you can control your Meross device through Homebridge, it's possible you could control it through one of those services using the HTTP GDO integration. You'd essentially set up the HTTP settings to send the command to your Homebridge server, which would then use its existing integration with Meross to execute the command. Unfortunately I don't use Homebridge so I can't provide detailed instructions on getting that piece working, but I assume Homebridge has an exposed API endpoint that would let you do this. Finally, according to this repo, it is possible to control your Meross device over a local http connection, which this app is already equipped to do for generic http endpoints, so it may already support Meross if you can determine what those http endpoints are. Though if it requires post requests with an API token as a bearer token, I would need to tweak the code slightly to support that, as currently you'd have to either supply the api token in the url or the post body, which may not be supported by Meross. |
Beta Was this translation helpful? Give feedback.
Awesome, thanks for testing! I'll do some code cleanup and release a proper version soon.