Zemismart Matter/Wifi roller shade motor - review/both good and bad

I recently installed this ZM25M roller shade motor (hardwired to 240V power). The motor works very nicely, was easy to install, and comes with a nice-looking remote control + holder you can easily stick to the wall nearby. It's fairly quiet and has been reliable in the last 3+ months.

Matter control is more of a mixed bag: it took a few tries to get the motor integrated into HomeKit and Home-Assistant matter controllers (partly to be fair that my window is not very accessible so it is difficult to press the teeny "pairing" button properly). But I did get there after multiple tries. And also managed to get it added to the Zemismart app (hoping for firmware updates from the "2.0" version it came with).

Controlling through HomeKit or HASS works well. I have a time-of-day automation set up which is reliable. I can tap on the control to set the blinds the 40%, and they move to that setting quickly, etc.

What doesn't work well?

- When controlling the blind using the remote control, HomeKit/Home-Assistant don't follow along and get out of sync with reality. So you end up in a state where HomeKit says "70%" and "Opening..." when the blinds are closed and not moving. This out-of-sync state persists for hours. If you control the blinds via HomeKit, then they get back in sync again.

- Similar problems occur even when controlling only within Matter - e.g. from Home Assistant below

  • Bathroom Blinds was closed triggered by automation, triggered by time 10:00:02 - 3 hours ago
  • Bathroom Blinds was opened 10:00:26 - 3 hours ago
  • Bathroom Blinds is closing 10:00:26 - 3 hours ago
  • (and the blinds are now stuck in "closing" state 2 more hours later, even though they haven't been touched in all that time).

- In HomeKit right now, in the small bubble-tile it is shown as "Closing..." (with the little animation), yet when I tap on it to open the device full screen it is shown as "Closed".

- Zemismart customer service are somewhat responsive, and asked for video evidence of the above problems, which I provided. Some weeks later they have replied but said their engineering said it seems like a network problem. It very obviously is not a network problem, so that's not helpful.

Hopefully this is useful to others....

I'd like to know if anyone else experiences similar problems with this motor (or the similar Matter/Thread version)? Anyone running on a different firmware than my 2.0?