Apply initial values to forms of device trigger extra fields

[farmio]

Proposed change

This applies a schemas initial values for device trigger extra fields.

This can be tested with a core-branch adding a new device trigger for "Sun" with some dummy extra_fields
home-assistant/core#115846

Here the "bool" switch is "off", even though the default value is True.

---

Here are some more selectors without default values with following configuration:

"extra_fields": vol.Schema(
    {
        vol.Required("bool", default=True): selector.BooleanSelector(),
        vol.Required("const", default=True): selector.ConstantSelector(
            selector.ConstantSelectorConfig(label="Constant", value=True)
        ),
        vol.Required("time"): selector.TimeSelector(
            selector.TimeSelectorConfig()
        ),
        vol.Required("datetime"): selector.DateTimeSelector(
            selector.DateTimeSelectorConfig()
        ),
        vol.Required("duration"): selector.DurationSelector(
            selector.DurationSelectorConfig(enable_day=False)
        ),
        vol.Required("number"): selector.NumberSelector(
            selector.NumberSelectorConfig(min=10, max=100)
        ),
        vol.Required("entity"): selector.EntitySelector(
            selector.EntitySelectorConfig(
                filter=selector.EntityFilterSelectorConfig(integration="sun")
            )
        ),
    }
)

previous	with initial ha-form data

---

I'm not very familiar with ha-form so I'm not sure why it does ignore a default value of a schema item that looks like

{"selector": {"boolean": {}}, "name": "test", "required": true, "default": true}

when the key is not included in the data in

frontend/src/panels/config/automation/trigger/types/ha-automation-trigger-device.ts

Lines 82 to 85 in 319a2d8

	<ha-form
	.hass=${this.hass}
	.data=${this._extraFieldsData(this.trigger, this._capabilities)}
	.schema=${this._capabilities.extra_fields}

Type of change

• 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

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue or discussion:
• Link to documentation pull request:

Checklist

• 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

[karwosts]

I'm not very familiar with ha-form so I'm not sure why it does ignore a default value of a schema item that looks like

I think I may have ran into this once before, I believe the ha-selector-boolean is missing placeholder support for rendering default: true. I did add this in another PR I was working on but it hasn't been merged yet.

This fix should cause the switch to appear as visually on when the key is missing from the data, but the field has a default of true.

https://github.com/home-assistant/frontend/pull/19718/files#diff-2991ed11d1b6a96a4567607ab82cc480b314844d8280150dac03480293c84229

Actually it looks like defaults are only used in forms when required: false, so maybe that is a different issue:

  .placeholder=${item.required ? "" : item.default}

[farmio]

Ah, placeholder could make sense here - so show this state but don't add it to data.
I don't think it should behave differently on required or optional in the Boolean case.

[bramkragten]

I think this is correct, adding placeholders can potentially be done in a different PR.