Mark more trigger fields as optional

[spacegaier]

Breaking change

Proposed change

Marked some more fields as optional.

There are a few others such as numeric_state where at least one of "Above" or Below" is required. Perhaps we should add a hint for those as well)?

Something like: Above (this or "Below" is required)

@matthiasdebaat Do you think that makes sense or is just cluttering the UI? If the user does not provide either of them, we show an (slightly hard to read) error toast.

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 Optional Fields in State Trigger Not Marked #10742
• 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

[matthiasdebaat]

@matthiasdebaat Do you think ...

Hmm, didn't get notifications from PR's. Just changed the settings for this.

Marked some more fields as optional.

I like these text changes! Good to show what is optional, it's positive instead of showing things that are required.

There are a few others such as numeric_state where at least one of "Above" or Below" is required. Perhaps we should add a hint for those as well)?

Something like: Above (this or "Below" is required)

As this PR is now merged leaves it for now as is. I need to check the UI how it is right now.