pepe59
(Pepe59)
August 25, 2022, 9:53pm
21
The problem still exists. Even after today’s update 2022.8.7, the problem is not fixed. Do you have the same?
home-assistant:dev
← home-assistant:fix-target-selector
opened 08:53PM - 13 Aug 22 UTC
<!--
You are amazing! Thanks for contributing to our project!
Please, DO N… OT DELETE ANY TEXT from this template! (unless instructed).
-->
## Breaking change
<!--
If your PR contains a breaking change for existing users, it is important
to tell them what breaks, how to make it work again and why we did this.
This piece of text is published with the release notes, so it helps if you
write it towards our users, not us.
Note: Remove this section if this PR is NOT a breaking change.
-->
## Proposed change
<!--
Describe the big picture of your changes here to communicate to the
maintainers why we should accept this pull request. If it fixes a bug
or resolves a feature request, be sure to link to that issue or discussion
in the additional information section.
-->
## Type of change
<!--
What type of change does your PR introduce to the Home Assistant frontend?
NOTE: Please, check only 1! box!
If your PR requires multiple boxes to be checked, you'll most likely need to
split it into multiple PRs. This makes things easier and faster to code review.
-->
- [ ] Dependency upgrade
- [ ] 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
<!--
Supplying a configuration snippet, makes it easier for a maintainer to test
your PR.
-->
```yaml
```
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #
- This PR is related to issue or discussion:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [ ] The code change is tested and works locally.
- [ ] 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][docs-repository]
<!--
Thank you for contributing <3
-->
[docs-repository]: https://github.com/home-assistant/home-assistant.io
nickrout
(Nick Rout)
August 25, 2022, 9:58pm
22
It’s not a core fix, its a frontend fix. Frontend release schedules are a mystery to me.
glad to see i’m not the only one with this problem… i hadn’t noticed it until i went in today to adjust something and found it missing
I am having the same problem but I’m not sure when this started. I last used Hue scenes in automation probably a couple months ago. Today I updated to whatever the latest version of home assistant is and when I edit any of my scenes, the target field is completely blank just like everyone else is experiencing here. This is concerning that this has been posted since August 6th but still no fix? This makes using Hue scenes in automation unusable. I use Control4 for my home automation, but the one and only thing I use HA for is to trigger Hue DYNAMICS scenes as it seems to be the only platform that supports this. I hope it gets fixed soon as I finally just sat down to fix a bunch of things and it’s not possible.
Edit: In case it helps anyone, the automations still work, so here’s how it looks in the YAML as a workaround.:
- id: '1652643673632'
alias: '[Z-Wave] [Cabana] Keypad Button 1 Pressed - Tokyo'
description: ''
trigger:
- platform: event
event_type: zwave_js_value_notification
event_data:
node_id: 30
label: Scene 001
value: KeyPressed
condition: []
action:
- service: hue.activate_scene
data:
dynamic: true
target:
entity_id: scene.cabana_tokyo
mode: single