Is it possible to trigger on target position for Matter Covers

[jvmahon]

The problem

Is it possible to trigger on or read the target position (i.e.,, TargetPositionLiftPercent100ths) attribute for Matter Covers from within an automation? I think the answer is "No" - in which case, can target position be added as an attribute for window shades and other covers?

Use case:
I have a mix of Eve Motion Blinds Matter shade covers as well as some cheap Zigbee shade motors. The Eve Motionblinds have a nice feature in that they can be activated by a local pull-chain to go up or down. What I'd like is if I activate one Eve Motionblind in a group by the pull chain, I can then use an automation to set other shades in a group to the same position as the one I manually adjusted by using the target position:

"{{ state_attr(trigger.entity_id, 'target_position') }}"

At present, I could use current_position, but then the automation has to continually fire as the first device changes with updated current_position values. It also doesn't work well if you want to be able to control the group from any device within the group.

What version of Home Assistant Core has the issue?

2024.12.4

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

Link to integration documentation on our website

https://www.home-assistant.io/integrations/matter/

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)}}

[mib1185]

Hi @jvmahon

We use GitHub for tracking issues with Home Assistant Core itself, not for providing support or handle feature request.
Please use the feature request section of our forum to contribute on existing or create new feature requests or try out the Community Forum or join the Discord chat server to get support.

Thanks! 👍