# Home Assistant 2026.8.1 reduces duplicate Matter blind triggers

Home Assistant Core 2026.8.1 coalesces rapid position and status updates from Matter covers, reducing duplicate state-change triggers seen with Eve MotionBlinds.

Canonical page: https://matterhome.io/news/home-assistant-2026-8-1-matter-cover-fix
Markdown page: https://matterhome.io/news/home-assistant-2026-8-1-matter-cover-fix.md
Author: Matterhome Editorial Team
Author profile: https://matterhome.io/authors/matterhome-editorial-team
Editorial lead: JC Martinez
Editor profile: https://matterhome.io/authors/jc-martinez
Published: 2026-08-12T02:06:57.000Z
Category: Compatibility update
Tags: Home Assistant, Matter, Automations

## Feature Image

- Origin: sourced
- Image: https://assets.matterhome.io/content/news/2026-08-12-home-assistant-2026-8-1-matter-covers/feature.808e46af2f9cf32db74b/source.webp
- Alt text: Eve MotionBlinds motor, mounting hardware, charging cable, and remote control
- Caption: Official Eve MotionBlinds product image. Home Assistant used an Eve MotionBlinds motor on firmware 3.5.1 to document the update problem; Matterhome has not tested the fix.
- Source: https://www.evehome.com/sites/default/files/social_media/sm-eve-motionblinds-upgrade-kit-roller-blinds.jpg

## Sources

- https://github.com/home-assistant/core/releases/tag/2026.8.1
- https://github.com/home-assistant/core/pull/177540
- https://www.home-assistant.io/integrations/matter/

[Home Assistant Core 2026.8.1](https://github.com/home-assistant/core/releases/tag/2026.8.1), released on August 7, 2026, changes how Matter window coverings publish their state inside Home Assistant. The patch coalesces rapid status and position updates before writing the cover state, reducing a failure mode that could make a state-change automation run twice when a blind stopped moving.

Home Assistant documented the problem with an [Eve MotionBlinds Upgrade Kit](/devices/eve-motionblinds-upgrade-kit) running firmware 3.5.1. Its Matter report said that the motor had stopped, then supplied the final position about six milliseconds later. The Matter Server passed those attributes to Home Assistant as separate events, so the entity briefly appeared stopped at 1% open before changing to closed. An automation watching that state could react to both updates even though the blind made only one movement.

The [merged fix](https://github.com/home-assistant/core/pull/177540) gives Matter cover entities a 100 millisecond state-write window. Incoming attributes are still processed immediately, but Home Assistant can publish the resulting state once after closely spaced updates have arrived. The change applies to Matter cover entities generally; Eve MotionBlinds is the verified example in the code review, not a complete compatibility list.

## Check blind automations after updating

If a Home Assistant automation triggers when a Matter blind opens, closes, or stops, update Core to 2026.8.1 or later before rebuilding the automation. Then run the blind through a full open and close cycle and check the automation trace for duplicate runs. This is a Home Assistant Core fix. It does not require recommissioning the accessory, changing its Matter fabric, or installing new blind firmware.

The coalescing is a practical safeguard rather than proof that every cover will now report one perfect state transition. Home Assistant's review notes that unusual timing can still expose an intermediate state. If duplicate triggers remain after the update, keep the automation guard that prevents repeated actions and report the exact cover model, firmware, and trace to Home Assistant. The useful change in 2026.8.1 is narrower: common split updates should no longer turn one physical stop into two automation events.