-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unsure of the logic #585
Comments
I think you need to provide me with more details. I cannot do anything with this description. Please provide me with a reproduction scenario. The intended behavior for it is of course to clean up the repair once it is fixed. Note: Spook and Watchman operate on completely different levels and logic. Watchman inspects YAML by trying to match from it, while Spook inspects runtime configuration inside the memory of Home Assistant relying on information from Home Assistant itself. |
Hi Frenck, |
What version of Spook are you using?
2.1.2
What version of Home Assistant are you using?
2024.1.6
The problem
SPOOK correctly shows errors after I renamed a few entities. WATCHMAN does to, by the way.
Cool, so I go to fix the issues in my template and config and restart. WATCHMAN is happy, SPOOK is not. I still have the two issues, even though they are repaired. Should they not be deleted automatically upon fixing? Under "Repairs" I can ignore them, but can not delete them. So they never go away in my system!! That can not be the intended behavior, or am I misunderstanding something?
Regards from Germany,
Robert
Anything in the logs? Paste it here!
No response
The text was updated successfully, but these errors were encountered: