Matter over thread Zemismart MT25B percentage open adjust not waking

[Avatar1976]

The problem

Hi I have three Zemismart MT25B blinds, they work very well however a relatively consistent issue is if the blinds are unused for a long time (no movement adjustments made), they will randomly not wake / respond when adjusting the open percentage.
They are connected via a Skyconnect running thread firmware and literally the other side of the room.
Interesting also generally the blinds respond fine to the open close commands (even when waking from sleeping).

What version of Home Assistant Core has the issue?

core-2023.10.3

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Matter (Beta)

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @home-assistant/matter, mind taking a look at this issue as it has been labeled with an integration (matter) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of matter can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign matter Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

matter documentation
matter source
_{^{(message by IssueLinks)}}

[marcelveldt]

That sounds like a device issue. Did you contact the manufacturer about it ?