Boolean selector in blueprint cannot be updated after creating automation

[gregrob]

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.

The problem

• Create an automation based on a blueprint with a boolean selector and select save.
• Go back into the automation and change the state of the boolean selector. No option for save appears.
• Change an additional selector so an option for save appears. The old value of the boolean selector is preserved.

I have simplified my blueprint yaml to the minimum and attached below. This minimised yaml also causes the behaviour that I am observing.

What version of Home Assistant Core has the issue?

2022.4.1 (first observed the problem), still exists with 2022.7.6

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Blueprint, Automation

Link to integration documentation on our website

https://www.home-assistant.io/docs/blueprint/selectors/

Diagnostics information

No response

Example YAML snippet

blueprint:
  name: Boolean Selector Test
  description: Boolean Selector Test
  domain: automation

  input:
    active_only_at_night:
      name: Active at night
      description: The automation only works at night.
      default: false
      selector:
        boolean:

mode: single
max_exceeded: silent

trigger: []
condition: []
action: []

Anything in the logs that might be useful for us?

No response

Additional information

No response

[erkr]

I ran into the same issue. But it's even worse:

• It already fails during the creation of an automation!

My example is:

    my_boolean:
      name: my example boolean
      description: my example boolean 
      default: true
      selector:
        boolean: {}

When I create a new automation, and change this boolean to false, the safe button pops up (so far so good).
Then I press the safe button and look in the yaml. It is saved as true (the default), not false !!!

[github-actions[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[erkr]

Still an issue in latest core-2022.7

[gregrob]

Still the same for me with 2022.7.6.

@erkr I've been manually editing the automation yaml files to true/false ever since April to work around this :laughing:

[erkr]

Yes, that's what I do as well

[smartqasa]

Still present...

Home Assistant 2022.9.6 Supervisor 2022.09.1 Operating System 9.0 Frontend 20220907.2 - latest

[smartqasa]

Issue is still present

Home Assistant 2022.10.3 Supervisor 2022.10.0 Operating System 9.2 Frontend 20221010.0 - latest

[smartqasa]

Issue is no longer present

Home Assistant 2022.11.3 Supervisor 2022.10.2 Operating System 9.3 Frontend 20221108.0 - latest

It appears to have been corrected.

[gregrob]

Checked with Chrome (Version 107.0.5304.107 (Official Build) (64-bit)) and Firefox (107.0 (64-bit)) - the issue appears to be resolved. Will close the issue.

Home Assistant 2022.11.4 Supervisor 2022.10.2 Operating System 9.3 Frontend 20221108.0 - latest