Update release notes for externally activated scenes #40653
Conversation
|
It seems that this PR is targeted against an incorrect branch since it has a parent PR on one of our codebases. Documentation that needs to be updated for an upcoming release should target the |
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull Request Overview
This PR updates the release notes for Home Assistant 2025.9 to document a new feature that allows integrations to update scene entities when scenes are activated externally. The change adds information about external scene activation support, which keeps scene states synchronized and enables their use as automation triggers.
Key changes:
- Added documentation for external scene activation feature in release notes
- Credited the feature contributor and mentioned supporting integrations
| @@ -297,11 +297,13 @@ There are many more improvements in this release; here are some of the other not | |||
| - The intent handling for the default agent (non-LLM) now supports fuzzy matching. The technique ensures voice pipelines recognize many more sentences. This improvement is available for English only, while we are looking for ways to extend this to other languages. | |||
| - We now have built-in intents to control the volume of (active) media players! Like the song? Just ask Home Assistant to turn it up a notch! | |||
| - After all that dancing, you might have gotten a little warm. Hence in this release, we now also have intents to control fan speeds. Nice! | |||
| - Integrations can now update scene entities when a scene is activated externally — for example via physical controls or other external events. This keeps scene states in sync, makes activations visible, and lets you use external scene activations as triggers in automations. Thanks to [@thomasddn]! [Qbus](/integrations/qbus/) and [KNX](/integrations/knx#scene) already support this feature. | |||
There was a problem hiding this comment.
The sentence structure could be improved for better readability. Consider breaking this into shorter sentences and using 'for example' instead of the em dash construction. Also, 'lets you' should be 'let you' for consistency with the direct address style guide.
Copilot generated this review using guidance from repository custom instructions.
| @@ -297,11 +297,13 @@ There are many more improvements in this release; here are some of the other not | |||
| - The intent handling for the default agent (non-LLM) now supports fuzzy matching. The technique ensures voice pipelines recognize many more sentences. This improvement is available for English only, while we are looking for ways to extend this to other languages. | |||
| - We now have built-in intents to control the volume of (active) media players! Like the song? Just ask Home Assistant to turn it up a notch! | |||
| - After all that dancing, you might have gotten a little warm. Hence in this release, we now also have intents to control fan speeds. Nice! | |||
| - Integrations can now update scene entities when a scene is activated externally — for example via physical controls or other external events. This keeps scene states in sync, makes activations visible, and lets you use external scene activations as triggers in automations. Thanks to [@thomasddn]! [Qbus](/integrations/qbus/) and [KNX](/integrations/knx#scene) already support this feature. | |||
There was a problem hiding this comment.
I'm not sure if this is noteworthy from an end user perspective. This should be a developer blog.
../Frenck
|
Please take a look at the requested changes, and use the Ready for review button when you are done, thanks 👍 |
Co-authored-by: Simon Lamon <32477463+silamon@users.noreply.github.com>
Proposed change
See
home-assistant/architecture#1236
home-assistant/core#146884
and the two already merged implementations of this feature
home-assistant/core#151232 this one was labeled
noteworthybut wasn't added to release notes yet.home-assistant/core#151218 this one was labeled
breaking-changebut wasn't added to release notes yet.cc @thomasddn
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.