What version of Spook are you using?
5.4.0
What version of Home Assistant are you using?
Core 2026.9.1, OS 18.2
The problem
Title: Blueprint update falsely reappears after every restart – fingerprint still order-sensitive on nested mapping keys
What version of Spook are you using?
5.4.0
What version of Home Assistant are you using?
Core 2026.9.1, OS 18.2
The problem
After installing a blueprint update via Spook's "Update available" repair, the blueprint update entity disappears as expected right after the update. However, a few minutes after the next Home Assistant restart, the same blueprint is flagged as "Update available" again — even though nothing changed upstream and the installed hash was identical to the latest hash right before restart.
Looking at the "Line by line" diff Spook shows for this repeat notification, the only reported change is a reordering of two sibling keys with unchanged values:
diff
--- the copy you have
+++ what is there now
@@ -138,8 +138,8 @@
default: "-07:00:00"
selector:
text:
-
multiple: false
multiline: false
@@ -202,8 +202,8 @@
default: "Yes, trash can is outside!"
selector:
text:
-
multiple: false
multiline: false
No values changed, only the order of multiple and multiline under selector.text. This looks like the blueprint file gets rewritten with a different key order for a nested mapping at some point (possibly during automation/blueprint reload on restart), and Spook's fingerprinting from #1556 still treats this reordering as a semantic change, re-triggering the update repair.
Blueprint involved
https://github.com/Gifford47/hass_blueprints/blob/main/waste_collection_notifier.yaml
Steps to reproduce
Install/update the blueprint above via Spook's update repair.
Confirm the update entity clears (installed hash == latest hash).
Restart Home Assistant.
Wait a few minutes — the same blueprint is reported as "Update available" again, with a diff that only reorders multiple/multiline keys.
Expected behavior
Once a blueprint is updated to match upstream, it should not be flagged as outdated again purely due to key-order differences with identical values — this should be exactly what #1556 ("Fingerprint what a blueprint says, not how it is written") was meant to fix.
Additional context
This has now happened repeatedly across restarts for several blueprints, not just this one, always with the update dialog showing an identical "install vs. now" diff limited to key reordering.
Anything in the logs? Paste it here!
What version of Spook are you using?
5.4.0
What version of Home Assistant are you using?
Core 2026.9.1, OS 18.2
The problem
Title: Blueprint update falsely reappears after every restart – fingerprint still order-sensitive on nested mapping keys
What version of Spook are you using?
5.4.0
What version of Home Assistant are you using?
Core 2026.9.1, OS 18.2
The problem
After installing a blueprint update via Spook's "Update available" repair, the blueprint update entity disappears as expected right after the update. However, a few minutes after the next Home Assistant restart, the same blueprint is flagged as "Update available" again — even though nothing changed upstream and the installed hash was identical to the latest hash right before restart.
Looking at the "Line by line" diff Spook shows for this repeat notification, the only reported change is a reordering of two sibling keys with unchanged values:
diff
--- the copy you have
+++ what is there now
@@ -138,8 +138,8 @@
default: "-07:00:00"
selector:
text:
@@ -202,8 +202,8 @@
default: "Yes, trash can is outside!"
selector:
text:
No values changed, only the order of multiple and multiline under selector.text. This looks like the blueprint file gets rewritten with a different key order for a nested mapping at some point (possibly during automation/blueprint reload on restart), and Spook's fingerprinting from #1556 still treats this reordering as a semantic change, re-triggering the update repair.
Blueprint involved
https://github.com/Gifford47/hass_blueprints/blob/main/waste_collection_notifier.yaml
Steps to reproduce
Install/update the blueprint above via Spook's update repair.
Confirm the update entity clears (installed hash == latest hash).
Restart Home Assistant.
Wait a few minutes — the same blueprint is reported as "Update available" again, with a diff that only reorders multiple/multiline keys.
Expected behavior
Once a blueprint is updated to match upstream, it should not be flagged as outdated again purely due to key-order differences with identical values — this should be exactly what #1556 ("Fingerprint what a blueprint says, not how it is written") was meant to fix.
Additional context
This has now happened repeatedly across restarts for several blueprints, not just this one, always with the update dialog showing an identical "install vs. now" diff limited to key reordering.
Anything in the logs? Paste it here!