Enabling any "Advanced Options" in light.turn_on kills the visual editor

[karwosts]

Checklist

• [X] I have updated to the latest available Home Assistant version.
• [X] I have cleared the cache of my browser.
• [X] 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

• In developer-tools/action, select light.turn_on (or maybe any service with "Advanced options").
• Expand advanced options.
• Enable and set a value for an advanced option.
• Visual editor will disappear and only a yaml editor will remain.

Describe the behavior you expected

as above

Steps to reproduce the issue

1. as above

3. ...

What version of Home Assistant Core has the issue?

2024.7 & 2024.8

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

No response

Which operating system are you using to run this browser?

No response

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

none

Additional information

No response

[silamon]

The advanced_fields doesn't specify a selector in the service config. It's a core issue for the light integration.

[karwosts]

advanced_fields isn't supposed to have a selector, it's supposed to be a collapsable section. This was a newly implented thing a month or two ago, but seems it may not have been done correctly.

I'm not sure if this is core or frontend issue, or a mixup between the two.

[silamon]

The logic is here: https://github.com/home-assistant/frontend/blob/dev/src/components/ha-service-control.ts#L374 Every field that has a visual ui should be listed in the service data information we retrieve from backend. Currently, the advanced_fields is not listed as field, and their children not either. From as soon as you use one, it will revert to yaml.