No. The Homey app hasn’t been updated yet. Still waiting.
Thanks mate - will wait then.
The fix for the MS605 won’t come through an app update but rather through a Homey firmware update 
“The issue was caused by a problem in Meross’ Matter implementation”
Why would we need a Homey firmware update if the issue is on the Meross side?
1 Like
This seems like a stupid question, but if the fix comes in the form of firmware to the sensor, but we can’t connect the sensor to Homey. How do we get the update?
Because we build a workaround that allows the device to be added even though the fault is in their implementation
To give a more technical insight into the issue; Homey detects a Basic Information Cluster on both endpoint 0 and endpoint 1 of the device. However, Homey expects this cluster to be present only on endpoint 0, as described in the Matter specification.
Because the cluster is also exposed on endpoint 1, this results in a validation error on our side. When this error occurs, Homey treats the device as non-compliant and consequently removes it from the fabric.
With the workaround we are implementing, Homey doesn’t remove the device anymore.
1 Like
And as far as I know, Homey doesn’t support updating firmware of devices (at least for ZigBee it doesn’t, I only have a Pro2019 so I don’t know if it does for Matter)
The update will be a Homey firmware update, not a device update
When will the update finally arrive? They usually release updates even for minor things.
Why don’t just use Siri on your watch to open the garage door then? I mean, since its already in HomeKit
Its already supported in another homey meross app 
Hello, just in the beginning stages of using the Homey self hosted server. So far, just really impressed by the options. Trying to move away from my SmartThings hub, as it is almost 10 years old now and need to plan for transition when/if it dies.
Thanks for all the Meross work so far. My request is support for the Meross Dimming Switches - MSS570x. I am not sure which Homey App has imported them, I installed both. They are available in Homey to control, but ONLY as an On/Off switch, but not exposing their dimming capabilities.
Any knowledge imparted is appreciated,
Richard
Same issue here with the MS605. Works in Meros App, works in Homekit. But not in Homey. Hopefully this will be resolved soon.
Hi,
I just want to confirm that i have the same issue even with the official Meross Homey App.
I reached out to the Homey support and already received a reply:
Both we and Meross are aware of the issue and a fix is being worked on and will be released soon.
So lets hope that they will update this topic soon because those sensors are quite nice if they work
Interestingly vendors are blaming each other for the incompatibility. Mail from Meross:
“*Regarding the compatibility with Homey, our MS605 supports a higher version of the MATTER protocol, while third-party hubs like the one from Homey currently support a lower version. As a result, it is temporarily incompatible.
Our R&D team has been actively communicating and collaborating with Homey in hopes of achieving full compatibility between the MS605 and the Homey ecosystem. We are currently still awaiting their further adjustments for better compatibility.”*
If this response is accurate: so much for backwards compatibility… But given that the Meross works fine with Homekit and the other related issues issues I have seen with Homey, a think the standards are implemented somewhat liberally.
But still eager to see a solution soon.
So, in short, the issue is exactly as described earlier;
Meross has since confirmed that the Matter specification indeed states that this cluster should only be present on the first endpoint. To achieve their original goal, they plan to switch to using the TagList attribute, as defined in Matter version 1.5. This allows them to provide user-friendly names for each sub-device (endpoint).
To clarify: once Meross adopts the TagList attribute, the device will still function correctly on Homey even if we are running a lower Matter version. The only limitation is that, instead of showing the custom user-friendly names, Homey will display generic names for the sub-devices.
The workaround we’ve implemented prevents Homey from force-removing the device from the fabric when it doesn’t fully comply with the Matter specification in this specific case. We’re currently seeing the same behavior with other devices as well, such as the ThirdReality Matter keyboard.
So overall, I don’t think there’s a single party to blame here. Our implementation is somewhat defensive by design, and Meross appears to have misinterpreted this part of the Matter specification
1 Like
Makes sense.
However, it does make me second guess Homeys Best Buy guide. They are recommending a presence sensor that doesn’t even work yet. Are these products actually tested or is this just an affiliate business to generate some extra money?
Our Best Buy Guides aren’t based on affiliate business, we don’t get a single dime. The guides are our personal opinions.
The update to the guide was based on the initial sample we got which did actually not have this bug. And as mentioned, with the upcoming workaround the device will work as expected.
2 Likes
Ok. Then I stand corrected. Apologies!
1 Like
HELP: I am having a tough time this week with trying to reconnect and fix items since migrating from 2023 to 2026.
I have brought brand new Meross MSS315 plugs because my previous ones that worked well with my HP2023, would t reconnect to HP2026 but I just cat get the new ones to connect either.
my home has a UNIFI Network with a 1gig speed so don’t believe it’s the WiFi network.
when pairing I get to the choosing network, enter the password and comes back with can’t connect again and again…../ help as it’s driving me nuts and this is only item 1 to fix about 50 more to go 
so should have kept my HP2023. Had no issues with it.
Any help welcome 
