👻👻👻👻👻👻👻👻👻👻

The blueprint update entities arrived last release. This release is about getting them to tell the truth. 😁 They were reporting updates that were not updates, which is fixed now.

The dialog barely said anything. It offered you a version number and a button. It now tells you what actually changed: which inputs are new, which are gone, which changed their type or their default, in words instead of in key names. It shows the diff. It lists the automations built on that blueprint, each one a link straight to it. And when the new version wants a newer Home Assistant than the one you are running, that is a red banner at the top, because installing it would stop those automations loading. It does not stop you. It is your blueprint, and re-importing by hand from the Blueprints page is always there. It just says what it will cost first.

Before it writes, it keeps a copy. motion_light.yaml.2026-09-01_143000.bak, next to the original, last three kept. There is a checkbox if you would rather it did not.

Elsewhere, statistics imported into the recorder have no entity behind them by design, and Spook was reading that absence as a missing entity. 🙈 Every repair you had ignored came back on the next reload, because unloading deleted the issue and took the ignore with it. And the seventeen triggers and conditions added in v5.1.0 had no icons at all, which nothing logs and nothing fails on.

Thanks to @cnotin 🫶, who spotted that the documentation was generating its sitemap with localhost:3000 in it, which is why pages like the conditions one were nowhere to be found in Google.

../Frenck