Spook is great. Most people don’t know it exists. It should be standard functionality of home assistant
This, from their website may help explain it.
So, there are a lot of things/features that will never end up in Home Assistant itself.
This can have various reasons. For example, it is just too random, out of scope, not matching the Home Assistant philosophy, violates architectural design, is still in early development, experimental, explorative, or just freaking useless.
What elements from Spook would you like to see in Home Assistant itself?
the config checker would be super useful
my other favorite would be the cooldown Other features - Spook 👻 a scary powerful toolbox for Home Assistant., with a second position for the nagging condition
Other features - Spook 👻 a scary powerful toolbox for Home Assistant.
Im always tempted to integrate this into my system, were it not I fear Spook might at some point be taken down, and my scripts would need a rewrite…
in core this would be awesome
so a +1, but not for the whole thing, just a few cherries
I worry about this too. But actually, I think the bigger risk is that the functionality is reimplemented “better” in core and you don’t realise.
Everything that allows me to access any functionality from script. There his entire added actions list.
There should be Zero things I cannot do from script that I can do from ux. There’s no excuse for not having functions like edit labels edit script exposure. Is user (property)
Without Spook. Zenos doesn’t exist because the parity in functions does not exist.
I cannot count the amount of times spooks has helped me cleanup things of find broken things. Its also the best alert if you change items, automations, remove something and still have artifacts. Having a lot of automations and massive dashboard its a life and time saver. I actually trust spooks to know for sure if was I changed did not break stuff. Because else it will be in my face about it. Indeed WTH, why is spooks not part of HA? 
I think this is a duplicate of my WTH.
Can it be merged?
ask @petro and give the link so he doesnt need to look for it
All I really use it for after discovering it in a WTH thread from last week is the warnings about orphaned devices and scripts/automations that are pointing to entities that have changed names or been removed.
This kind of keeping things tidy should really be core functionality.
Almost everything in spook is an answer to the recurring questions and problems in this forum, on FriendFace (aka Facebook) and Reddit.
The remainder is actions (one of the most useful yet most undiscoverable aspects of HA IMO)
I think that the question is
What elements from Spook would you NOT like to see in Home Assistant ?
It’ll reduce the discussion time
It’s Frenck’s personal project so really it’s up to him. But I agree that perhaps some features in there would make sense for the core install at least. I just don’t know enough to categorically claim they should, and he has to have his reasons for not pushing for it.
I think (at least from reading Frenk’s own narrative) that one of the key reasons it is not in core and he’s not pushing is because of the non architecturally compliant ways the code achieves our goals 
These two, among others, are ones I’d really like.
I agree on this, it’s better to " feel free ", than " obligated to "
That’s in fact what’s driving most DIY’s, we do it our ways, and find ways around the beaten path, and strict “protocols” ( some times affected by a lazy nature ) 
Spook is a very useful piece of software but it increased my cpu usage and drove me crazy 
It doesn’t play well with HALP and other issue scanners, there are lots of them out there and this makes decision ‘what to keep’ a lil hard.
If only I could set it to scan once a week or better yet manual mode only!
Edit: sorry (bad RAM), not HALP, I meant: HACA and HAGS
Spooke has a couple of service, and a bunch of entities, among Events
You can basically disable everything(Most)
Yes He likes to “poke around”, and also “Present” what’s specified
Have you tried to Disable every entities, event’s etc ? , to i.e “locate” what causes the increased CPU ? , PS: No i don’t know anything about HALP, thou i do have a Few “scanners” type specific basic Templates
Repairs:
i.e if you disable this, spook wont listen to the repair events HA creates, and thus don’t “post” it’s findings in the Repair-Page or /Settings
Disable All
Then You have the Actions, And Entities in Spook, in particular Disable/Enable entities.
Maybe you find other “template-entities” in HA, you find irrelevant
Look at the “Diagnostics” i assume it’s similar as “simple” template.entities( for , in , x . count )
Any, Entities/integrations you can start with an automation/script, by using Disable/Enable entity/Int
Maybe you eventually find that it’s actually HALP you don’t need 
The way I understand it, besides being Frenck’s personal playground, Spook is also a way of adding stuff which isn’t allowed in core.
One of them is editing entities using automations/scripts.
That’s why the following things are only allowed in custom integrations, like Spook:
- actions to change labels
- actions to change areas
- actions to disable/enable entities
- actions to change groups
So, based on what I’ve been told (which was a while ago) I don’t expect these actions to ever be standard in HA core.
There is are actions to create/change the old style groups (under the group domain) but these were added before these rules prohibiting such actions were set.
I agree he’s a bit heavy some of the template scans are bad on a large system (ask me how I know) but there’s some PR’s pending (post 5.11.1) to help speed of scanning.
Which I think is the ABSOLUTE dumbest thing Fes - We as end users should be allowed to do this.
Labels, exposure, aliases, user admin state… I can go on.
Thre should not be a SINGLE feature in the UI we CANNOT get to through script / action.