I’ve recently noticed that I can no longer save changes to boolean selectors in Home Assistant. I have 3 different Home Assistant installations running, all at 2022.7.something, and I see the behavior on all 3 installs. I’m not certain when this started, or if others are experiencing the same thing.
I’ve submitted a bug report here but am interested if anyone else is experiencing this problem as I don’t see any mention of it elsewhere.
Here’s what I’m experiencing:
-
If you edit a blueprint with one or more booleans, toggling the state of the boolean does not bring up the “save” button. You have to edit some other selector in order for the “save” button to be presented.
-
If you save a blueprint after toggling the state of a boolean selector, the updated selector state is not changed.
Here is an example, dummy blueprint that offers a text selector and two booleans: test_blueprint_toggle.yaml · GitHub
Process to replicate
- Import and deploy blueprint:
- Create automation from blueprint
- Toggle one of the booleans, observe that the “save” button appears.
- Press “save” and exit out of automation editor
- Go back to the new automation in the automation editor
- Toggle one of the booleans, observe that the “save” button does not appear.
- Change the text field
- Observe that the “save” button now appears
- Press save and exit out of automation editor.
- Go back to the automation in the automation editor and observe that the new value for the boolean you changed has not been saved, while the value for the text selector has been saved.
- Open
automations.yaml
and observe that the updated boolean has not been saved, while the value for the text selector has been saved.
Is anyone else seeing this same behavior? If you get a minute, can you try the process above and see what happens for you?