Home Assistant 2026.11 lets blueprints and integration forms hide settings until another choice makes them relevant

Many Home Assistant blueprints ask for settings that only matter in one mode. Four pull requests by Paul Bottein, merged on 21 and 22 October 2026, add a visible condition that shows an input, or a whole section of inputs, only when another field has a given value. It works in blueprints and in the setup and options forms of integrations. The changes are in the development branch and should arrive with Home Assistant 2026.11.

In blueprints

Blueprint inputs and input sections get a visible key next to default and collapsed. In the example from the pull request, a brightness field only appears once the dimming mode is set to fixed:

input:
  dim_mode:
    default: none
    selector:
      select:
        options: [none, fixed]
  brightness:
    default: 50
    visible:
      field: dim_mode
      value: fixed
    selector:
      number:
        min: 1
        max: 100

A hidden section hides all of its inputs, and an input inside a section shows only when both the section's condition and its own match. Conditions can point at any input in the blueprint, because input names are shared across sections. The automation editor hides the fields as you change the other choices.

Blueprint authors need to keep one rule in mind. A hidden input does not need a value, but every !input in the automation must still resolve to something. A hidden input therefore takes its default, or None if it has no default, and the automation logic has to cope with that.

In integration forms

The same mechanism reaches config and options flows, the forms you fill in when adding or reconfiguring an integration. Until now, an integration that wanted to show or hide a few fields had to add an extra step or show the form again after submitting it. A hidden field is not required and its value, default included, is not saved.

The conditions use the format the frontend already used for card editors: eq, not_eq, in, not_in, exists and not_exists, or a list of conditions that must all match. Home Assistant checks them on the server as well, so a field hidden in the interface is also skipped during validation.

OpenAI Conversation is the first integration to use it. Its advanced options (chat model, maximum tokens, temperature, top P and storing responses) now sit in the same step as the "Recommended model settings" switch and stay hidden while that switch is on, instead of waiting in a separate step.