i’m configuring automations that use blueprints. i’m using Home Assistant Companion Mac UI 2025.3, Home Assistant Core 2025.4.3.
although i mention these specific versions, i should note that the problem i’m reporting below has been present across multiple versions - i think i’ve been seeing this for perhaps six months or so.
like most HA users, i have lots of automations in my configuration. many of them are based on blueprints. when i go to settings>automations and click to open an existing automation to view or edit it, i am presented with the blueprint “form” interface where you can (or at least should be able to) see the values for various blueprint inputs.
what i see is a form where the values appear to be blank. if i click the mouse into one of the fields on the form, i can see by the behavior of the cursor that the field actually contains a value, despite there being nothing visible. for example, if i click the mouse on the right side of the field, the cursor moves to a specific location corresponding to the right extent of the (invisible) value. i can then move the arrow keys to cause the cursor to move around within the (invisible) text of the field.
another oddity is that just by moving the cursor around within the invisible text within a field, i can sometimes make the text suddenly appear. so this is a kind of fix or work-around for the problem, but on the other hand it is also definitive confirmation that most certainly some kind of UI glitch (since the data on the screen obviously changes).
sometimes, i find that after i’ve “fixed” the bug once, it stays fixed and i can then go on an view/edit other automations within the client and their contents show up normally. but then sometime later (perhaps after the next HA restart? or after quitting and restarting Companion app?), i’ll find that the problem returns again.
i see this over at least most if not all of my blueprint-based automations. i’ve seen this over multiple releases of Home Assistant and the HA-companion app. though i described a work-around above, i still consider this to be a pretty significant bug.