Home Assistant beta unlocks fan speed control and new media triggers

A beta update unlocks native fan speed control and new media triggers. Home Assistant core release 2026.5.0b3 details several enhancements that aim to tighten automation reliability and expand device compatibility.

One of the headline features is exposing SET_SPEED for all fans via PercentSetting in Matter, giving users a more granular knob for controlling connected fans without clunky workarounds. That means automations can set precise speeds rather than cycling between preset levels, a welcome shift for users juggling multiple Matter devices.

The update also broadens automation triggers with timer.time_remaining and expands media control hooks, including a new media_player.unmuted trigger and added media_player volume triggers plus muted conditions. In practice, that combination helps keep audio scenes and dashboards in sync with real time states, so you can react the moment someone un-mutes a stream or adjusts volume.

On the developer and testing front, the notes emphasize tighter YAML validation against implementation in automation options_supported tests, plus improved test helpers and internal methods to guide inclusion logic for triggers and conditions. In short, the beta aims to catch misconfigurations earlier and make writing robust automations less painful for power users.

There are also quality of life tweaks for mobile users: the system now records notifications from legacy notify actions in the Mobile App and improves mobile_app device tracker tests. That combination should translate to more reliable notification pipelines and fewer flaky location updates on mobile devices.

Beyond that, the beta touches the frontend and a handful of integrations by updating the frontend to version 20260429.3 and adding volume-related triggers for media players, as well as excluding incompatible entities from humidity and temperature automations. The goal is fewer surprises when users push new automations and a bit more guardrails for device compatibility.

Practitioner notes and what to watch next: first, beta releases like this are powerful for getting ahead of feature gaps, but they can introduce breaking changes to existing automations. Test changes in a staging setup before rolling to production, and keep a close eye on YAML validation messages as configurations migrate. Second, the Matter SET_SPEED integration is promising for households with mixed fan models, but it may require updating automations to use PercentSetting semantics rather than fixed speed labels. Finally, the focus on compatibility filtering for humidity and temperature automations reduces false triggers, but users should audit existing automations that reference those entities to ensure they remain aligned with the new constraints.