frontend
frontend copied to clipboard
Remove activate scene in automation editor
trafficstars
Proposed change
Some services have "overrides" in the frontend presenting a different layout. Activate scene is one of them. I'm removing this so the service definition provided by the backend is used, as it provides more options. Options that do already appear if you transition from visual to yaml to visual.
There's also a legacy scene action, I don't know what it is and how long it is legacy.
Type of change
- [ ] Dependency upgrade
- [x] Bugfix (non-breaking change which fixes an issue)
- [ ] New feature (thank you!)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
Example configuration
Additional information
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
Checklist
- [x] The code change is tested and works locally.
- [x] There is no commented out code in this PR.
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for www.home-assistant.io