OK, maybe a NooB thing. Followed destructions. was able to discover the MSG100, added it to HE. used httpcatcher, caught Message ID, Timestamp, and Sign. Key and UUID were prepopulated. port 1 was set by default in the device.
When I trigger an open/close event via HE, I get "the target server failed to respond"
What am I doing wrong. I know the device is at the right IP address, and is online. Actuates fine in the Meross app.
Help! 
I had the same problem, It added the door ok, but the status was always "door: unknown" with the same warning about missing setting configuration.
It seems that the device state isn't captured correctly at installation, so it thinks currentVersion is 0, which is one of the reasons it's log that warning on line 103 of the driver code. I just temporarily changed the code to default to version 428 (mine is 4.2.8) at the end of line 98.
Then I clicked the refresh button and it grabbed the status correctly.
1 Like
Is your Meross MSG200 on version 4.2.8?
(asking as mine shows version 2.1.3)
Yes, my MSG200 has Firmware version 4.2.8. In checking, the iOS app showed me that there is a new firmware version available, 4.2.11:
- Fixed a critical time synchronization issue
- Added support for changing Wi-Fi functionality.
- Improved the device's network stability during online operation
- Addressed other known issues.
I have not installed the update yet.
Thank you,
Alright, for anyone else who is troubleshooting.
My Meross msg200 garage door opener was purchase in Aug 2021 and is a pre/non-homekit version. I can see firmware version 2.1.3 in Hubitat (and I also see hardware version 2.0.0 when I look in HA). I do not have any available updates when I look in the app, so it appears 2.1.3 is the current version for my 2.0.0 for my hardware.
What I just tried based on pjam73's earlier comment was to change all references of the version in the drivers code to 213 (the 0s at the end of line 67, 98; and anywhere there was a value of 323, I changed it to 213.) That solved my issues, and my opener is now working as expected.
1 Like
Thank you for your revised app. It got me to the point that I can now see the meross 100 garage door opener and have set it up as a device and enabled HomeKit. HomeKit shows it as âObstructedâ and does not accept commands to open or close. Same is true in Hubitat as far as issuing commands, they have no affect. Tried refresh on the device in Hubitat with no luck either. Log shows a warning of missing device setting. Thatâs about as much info as I can share without further guidance but are you able to share any pointers to help resove?
Testing with Alexa app also not working to issue open/close commands. Alexa does see the device and I can setup an 4 digit open code for it.
I know nothing about this device, but I think you're going to need to figure out why the device is showing as "obstructed" before doing anything else... And I'd bet that has nothing to do with Hubitat, Alexa ,or HomeKit -- it's likely a wiring or configuration issue with the device itself.
Is there a Meross app or support tool that can help ensure the device is properly set up and configured (i.e. help get it out of its "obstructed" status)?
Meross app functions perfectly and the door opens and closes thru that app. As far as any debug from meross the app is very limited as am I 
Using the Alexa meross skill allows me to close the garage door as well using Alexa. The open function in Alexa is not asking me for the 4 digit code to perform the open which is another issue but not a major concern. Close is most important. May have something to do with new Alexa plus update.
Thank you for the suggestion but I think this is a driver or app concern in Hubitat right now. Does anyone have this working with a Meross MSG100 using HomeKit, Alexa, or hubitat to control the garage door? I got thru all of the device setup fine with the revised app
1 Like
This note from Brian W above was the trick.
Thank you all for your cool work on this device!
Does this method work with the MSG200HK? Does any of this work currently?
Iâm using an old SmartThings hub mainly as an integration broker. It exposes Meross, Tuya and a few other awkward ecosystems into Hubitat via virtual switches, using SmartThings Mira / CStup Edge Drivers with Hubitatâs Maker API.
SmartThings has a much broader consumer integration ecosystem than Hubitat, while Hubitat is architecturally leaner and more functional for local automation.
This effectively stitches the two ecosystems together: SmartThings handles the messy cloud/vendor integrations, while Hubitat remains the local automation engine. For my use case, that is far easier and more reliable than mucking around with a collection of relatively unstable community drivers, at least as an interim step until the equivalent integrations become available in Habitat.
it does for anyone curious
Hi,
The code posted here took me really far. I was noticing the garage door state wasnât refreshing properly. I took the latest code from this discussion and ran it through Claude. You can find the result here: hubitat-meross/README.md at main ¡ jlong4096/hubitat-meross ¡ GitHub
I am having a much better experience now. I have the MSG200, but Claude identified and fixed bugs for MSG100 as well. Iâm unable to test the MSG100, but I would expect it to work now as well.