Ensure explicit false values from customize form get stored

[spacegaier]

Breaking change

Proposed change

false values for explicitly added customize attributes should be stored, but currently the !value checks filters them out. Now we only rule them out if they are null or undefined.

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 Cannot customize programmatically set attribute to false #10377
• 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

[bramkragten]

I don't see logic for undefined like in your description?

[spacegaier]

I don't see logic for undefined like in your description?

To my understanding x == null (note the only two not three =) is equal to x === null || x === undefined.

[bramkragten]

That's why we only use === ;-) Could you please adjust :-)