Repository navigation
Disable specific Spook features (toggle on/off) #1603
Replies: 9 comments
|
There are two separate controls here:
I do not see a general per-repair feature switch in the current Spook configuration. Thus, for unused-blueprint findings the intended persistent control is Ignore (fixed in v5.4.0), while individual blueprint-update notifications can be suppressed by disabling their update entities. A global “disable this entire repair class” option would still be a feature request. |
|
+1 for disabling certain checks. Where spook is shining is for me things that are not easily obvious. And the feature "ignore" is not really good in this regard, because its quite tedious to ignore every single blueprint. |
|
To add some weight behind the request for a disable option: the recent update notifications from Spook were actually what pushed me to disable Spook entirely. That's not something I wanted to do, because I genuinely like and value what Spook provides for identifying configuration issues that are otherwise hard to spot. The problem is that the growing number of warnings about things like unused blueprints adds a lot of noise for users who don't consider those checks valuable. When the signal-to-noise ratio gets too low, the easiest solution becomes disabling Spook altogether. A simple way to disable specific categories of checks would allow users to keep benefiting from Spook's strongest features without being overwhelmed by warnings they intentionally don't care about. I think that would lead to more people keeping Spook enabled, rather than turning it off completely. |
|
I think something needs to be done with the blueprint notifications - having an unused blueprint is surely not much of an issue and constantly showing false blueprint updates is tedious, especially as they come back after a restart. Disabling certain features would certainly be a step in the right direction. |
|
Agreed with others. I am not sure what value notifications of unused BP brings. If there can be a feature to turn off these information type notifications. |
|
Couldn't agree more, the blueprint update notifications are extremely annoying. They pop up again after every Home Assistant restart. This feature is well-intentioned, but in its current implementation, it just doesn't make sense. |
|
I don't think ignoring a number of repairs is a good solution for several reasons:
Disabling groups of repairs would solve all of these issues. |
|
I'm currently having issues with the template issues. Mine is Admittedly due to the sheer number of templates in a Zenos install. When Spook 11+ runs on one of these installs I get a hard hang. I recognize some might want these tests. Personally they're useless to me and hang the box. I'd prefer to just turn off the entire class. |
|
The unused blueprint notifications are annoying and theyre popping up every few days. |
Uh oh!
There was an error while loading. Please reload this page.
With latest Spook installed, the number of unnecessary warnings/problems found are excessive. How about a feature to turn off certain features such as blueprints unused. I tell Spook to ignore them and they come right back after a day or two. Same for blueprint updates -- they keep coming back after telling them to update (probably because the update for some of the blueprints never completed) but would be nice to turn this off.
All reactions