Anyone NOT using HACS - "breaks the template engine and was blocked from loading"

[TheQue42]

Hi,

I've been using Spook manually installed, since I don't have hacs, and I prefer not to. (Spare me the discussions on why, and "you really should")

What I am wondering is, if I am the only one, or if someone else has got current Spook working by manual install, in 2025.11.1, since right now it fails with custom integration 'spook' breaks the template engine and was blocked from loading during start.

Not exactly sure when it stopped working, since I temporarily disabled it when it was complaining about something I didnt have time to fix just then...and now when I tried re-enabling, I cant.

[teskanoo]

That issue came up in the beta testing for 2025.11.b0
Frenk issued an immediate fix - have you updated spook?

[agoose77]

I also have this problem on 2025.11.1, and with spook v4.0.1

[agoose77]

@TheQue42 I've found the fix.

https://github.com/home-assistant/core/blob/7fe0d96c887709156556a6e8e4c5f022962a77df/homeassistant/loader.py#L126

introduces a version test that ensures spook needs to be >= 4.0.0. However, when you manually install the component from the source tree, it doesn't have a useful version:

spook/custom_components/spook/manifest.json

Line 24 in dd6468d

"version": "0.0.0"

That's because the version is set by the release machinery:

spook/.github/workflows/release.yaml

Lines 23 to 31 in dd6468d

	version="${{ github.event.release.tag_name }}"
	version="${version,,}"
	version="${version#v}"
	yq e -P -o=json \
	-i ".version = \"${version}\"" \
	"${{ github.workspace }}/custom_components/spook/manifest.json"
	yq e -P -o=json \
	-i ".version = \"${version}\"" \
	"${{ github.workspace }}/custom_components/spook/integrations/spook_inverse/manifest.json"

So, you just need to consume the files from the release, or patch them yourself.

[TheQue42]

Superb! Thanks for figuring this out!