👻👻👻👻👻👻👻👻👻👻

Two fixes.

If you have no groups, Spook logged a KeyError: 'group' traceback at every start and asked you to report a bug. It had decided not to register its three group actions, correctly, since the group integration was not there, and then went on to describe them anyway. Home Assistant looks an action up while storing a description, did not find one, and said so loudly. The same went for any Spook action aimed at an integration you do not have set up.

And a blueprint update could outlive its blueprint. Nothing in Home Assistant announces a blueprint being deleted, so Spook only noticed on its daily round, and until then the update sat there. Pressing install to clear it fetched the blueprint and wrote it back, which is Spook restoring a file somebody deleted on purpose. Install now looks for the file first and drops the entity when it is gone, and the folder is checked every five minutes instead of once a day: it is a directory listing, it never needed to keep to the cadence the fetching does.

Thanks to @Anto79-ops, @EckiIQ, @PVSonnenfreund, @misa1515 and @JesperHomeAssistant for the group reports, @Merangle for putting it in one sentence, and @gcoan for the blueprint one, found by deleting two blueprints and watching what happened next. 🫶

../Frenck

Blogging my personal ramblings at frenck.dev

🐛 Bug fixes

• Don't describe a service that was never registered @frenck (#1650)
• Don't write back a blueprint that was deleted @frenck (#1666)

🧰 Maintenance

• Translations update from Hosted Weblate @weblate (#1649)

⬆️ Dependency updates

👻👻👻👻👻👻👻👻👻👻