You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Model Name: iPhone 15 Pro Max
macOS Version: 15.3
App Version: 2025.1
Safari Version: 18.3 (20620.2.4.11.5)
Home Assistant Core Version
2025.2.1 Describe the bug
I create an automation using a blueprint. This involves me filling in a view input fields - including for example entities that might be selected.
After creating, I later go back and open the blueprint - i.e. to either inspect its settings or perhaps to edit the automation. When I open the automation, I see the top field is filled in ("Blueprint to use") with the name of the blueprint.
However, the other fields on the page (i.e. the names of entities that I had previously populated when I first created the automation) appear empty.
If i click and put the cursor into one of the apparently empty fields, then I get a hint that there is actually a value contained in the field (because for example the cursor jumps ahead and places itself at the end of the field), however the value of the field (e.g. the name of the entity that I entered previously as one of the inputs for the blueprint) remains invisible.
I can occasionally force the value to appear - for example, if i use my cursor to drag across the (invisible) contents of the field to select the entire value, then it sometimes flashes into visibility as a side effect of being selected.
So in some ways it seems like the values are there but mostly invisible. This makes it feel awkward and risky to edit an automation based on a blueprint.
To Reproduce
Open a pre-existing automation that was created from a blueprint that has one or more input values (such as entities).
Expected behavior
I would expect that when opening a pre-existing automation that is a populated "instance" of a blueprint, that the values (inputs) were entered for the blueprint would show up.
This is what I see when doing the exact same action in the safari browser instead of the companion app.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered:
Device model, version and app version
Model Name: iPhone 15 Pro Max
macOS Version: 15.3
App Version: 2025.1
Safari Version: 18.3 (20620.2.4.11.5)
Home Assistant Core Version
2025.2.1
Describe the bug
I create an automation using a blueprint. This involves me filling in a view input fields - including for example entities that might be selected.
After creating, I later go back and open the blueprint - i.e. to either inspect its settings or perhaps to edit the automation. When I open the automation, I see the top field is filled in ("Blueprint to use") with the name of the blueprint.
However, the other fields on the page (i.e. the names of entities that I had previously populated when I first created the automation) appear empty.
If i click and put the cursor into one of the apparently empty fields, then I get a hint that there is actually a value contained in the field (because for example the cursor jumps ahead and places itself at the end of the field), however the value of the field (e.g. the name of the entity that I entered previously as one of the inputs for the blueprint) remains invisible.
I can occasionally force the value to appear - for example, if i use my cursor to drag across the (invisible) contents of the field to select the entire value, then it sometimes flashes into visibility as a side effect of being selected.
So in some ways it seems like the values are there but mostly invisible. This makes it feel awkward and risky to edit an automation based on a blueprint.
To Reproduce
Open a pre-existing automation that was created from a blueprint that has one or more input values (such as entities).
Expected behavior
I would expect that when opening a pre-existing automation that is a populated "instance" of a blueprint, that the values (inputs) were entered for the blueprint would show up.
This is what I see when doing the exact same action in the safari browser instead of the companion app.
Screenshots
Additional context
The text was updated successfully, but these errors were encountered: