Boolean inputs in blueprint with default `true` don't toggle correctly

[mdegat01]

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.

Describe the issue you are experiencing

I have a blueprint with the following input:

blueprint:
  input:
    take_backup:
      name: Take backup
      description: Do a partial backup before updating if able
      default: true
      selector:
        boolean:

It is presented in the UI like this (which is correct):

The problem is that toggling it to off doesn't seem to do anything. When I toggle it to off I still see this in the yaml:

Note that the boolean inputs in the first screenshot which have default: false don't seem to have this issue. Toggling them to true sets the yaml correctly, they work fine. It's only an issue with ones that default to false.

I will also note that I am displaying the yaml as I found its the easiest way to convey the issue. I can also assure you that if I click "save" on this screen when the toggle is off the automation is still behaving as if "Take backup" is set to true.

Describe the behavior you expected

Toggling this input to false should set the value of that input to false.

Steps to reproduce the issue

1. Make a blueprint with a boolean input
2. Add default: true to that input
3. Make an automation from that blueprint
4. Toggle that input to false
5. Switch to YAML mode and notice that it is still true. Or save your automation and run it and notice the automation still acts as if the value was true. ...

What version of Home Assistant Core has the issue?

core-2022.4.1

What was the last working version of Home Assistant Core?

No response

In which browser are you experiencing the issue with?

Firefox 98.02

Which operating system are you using to run this browser?

macOS Monterey (12.2)

State of relevant entities

No response

Problem-relevant frontend configuration

No response

Javascript errors shown in your browser console/inspector

No response

Additional information

No response

[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.

[crkochan]

This bug is still present on the latest stable Home Assistant as of this date.

Home Assistant 2022.7.3
Supervisor 2022.07.0
Operating System 8.2
Frontend 20220707.0 - latest

[schiz0phr3ne]

Still present here too.

Home Assistant 2022.7.5
Supervisor 2022.07.0
Operating System 8.2
Interface utilisateur : 20220707.1 - latest 

[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

[karwosts]

Duplicate of #13206 ?

[crkochan]

Other way around, actually.

[karwosts]

I believe this is fixed. If you still see an issue, please leave a comment.