frenck
Unsure of the logic
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
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, maybe something went wrong with the renaming, because I was left with the new entity and the renamed one. The renamed one was undeletable, until I stopped HA completely and did a restart. The "old" entities where gone and SPOOK was "happy". I still have a repair for "LXC 102 does not exist, please remove from it from the integrations options" for PROXMOX. I did remove it, but SPOOK has not deleted the message. Thank you for all your work.