You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have updated to the latest available Home Assistant version.
I have cleared the cache of my browser.
I have tried a different browser to see if it is related to my browser.
I have tried reproducing the issue in safe mode to rule out problems with unsupported custom resources.
Describe the issue you are experiencing
Context
The "Scenes" screen includes scenes created by Zigbee2MQTT, which is awesome. Although the scenes don't come from the YAML configuration and cannot be edited, they are at least visible, and can even be activated, named, iconed etc. from the frontend, which is awesome too.
Also, discovered scenes, just like native scenes, are associated to an Area, either explicitly or implicitly through their corresponding device. In the case of Z2M scenes, the latter case would be through the device (either physical or device group) holding the scene in Z2M. That implicit or explicit Area is shown properly in the scene's Settings, and can also be edited, which continues to be awesome.
Problem
The only issue is for grouping, and only in the case of implicit Areas. When a scene inherit's the Device's Area, grouping doesn't use it, i.e. it shows the scenes in an "Ungrouped" fold. When the Area is set explicitly though, grouping behaves as expected.
Describe the behavior you expected
Scenes discovered from Z2M and inheriting their Area from the corresponding device should be grouped by Area like any other scene.
Steps to reproduce the issue
In Z2M:
Create a scene for an existing device
In HA:
Make sure the device from Z2M is associated to an Area
Navigate to Settings, Automations & Scenes, Scenes.
Locate your created scene. From its settings, make sure "Use device area" is enabled.
Back to the main Scenes screen: Group by Area.
The scene from Z2M is under "Ungrouped" instead of its implicit Area.
What version of Home Assistant Core has the issue?
2025.5.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue?
Microsoft Edge 135.0.3179.98
Which operating system are you using to run this browser?
MacOS Sequoia 15.4.1 (24E263)
State of relevant entities
Problem-relevant frontend configuration
Javascript errors shown in your browser console/inspector
Additional information
No response
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Checklist
Describe the issue you are experiencing
Context
The "Scenes" screen includes scenes created by Zigbee2MQTT, which is awesome. Although the scenes don't come from the YAML configuration and cannot be edited, they are at least visible, and can even be activated, named, iconed etc. from the frontend, which is awesome too.
Also, discovered scenes, just like native scenes, are associated to an Area, either explicitly or implicitly through their corresponding device. In the case of Z2M scenes, the latter case would be through the device (either physical or device group) holding the scene in Z2M. That implicit or explicit Area is shown properly in the scene's Settings, and can also be edited, which continues to be awesome.
Problem
The only issue is for grouping, and only in the case of implicit Areas. When a scene inherit's the Device's Area, grouping doesn't use it, i.e. it shows the scenes in an "Ungrouped" fold. When the Area is set explicitly though, grouping behaves as expected.
Describe the behavior you expected
Scenes discovered from Z2M and inheriting their Area from the corresponding device should be grouped by Area like any other scene.
Steps to reproduce the issue
In Z2M:
In HA:
What version of Home Assistant Core has the issue?
2025.5.2
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue?
Microsoft Edge 135.0.3179.98
Which operating system are you using to run this browser?
MacOS Sequoia 15.4.1 (24E263)
State of relevant entities
Problem-relevant frontend configuration
Javascript errors shown in your browser console/inspector
Additional information
No response
The text was updated successfully, but these errors were encountered: