If the file is already in the Spook folder do you have any idea why that link exists?
No idea myself, but it seems everyone has it.
2 Likes
I added the SpotifyPlus integration and now Spook gives me a warning :
The script, which is correct :
alias: Spotify playlist 1
sequence:
- data:
entity_id: media_player.spotifyplus_xxx
context_uri: spotify:playlist:6LOkzwqmF7HMwgnMgVq3Qe
device_id: ChromecastAudioLiving
action: spotifyplus.player_media_play_context
mode: single
Can I do something about that ?
don’t think that’s not a device_id you have in the script…more likely an entity_id
AFAIK a device_id is something like this 5447649936cb1b93398c28ca8aa928d7 that is system generated by HA
If you go to /config/devices/dashboard in your HA and click a device in there you’ll see the corresponding device_id in the URL for the page you go to.
@Tsar
I’m not familiar with Spook, so can’t say for sure. My guess is that Spook thinks the device_id argument value is some sort of HA device / entity id that should correspond to some sort of registered device maybe? Best guess.
Either way, you can ignore the Spook warning / error message, though not sure if you can configure Spook to ignore / disregard the cause or not.
The device_id in question is actually a device name ChromecastAudioLiving. Note that the device_id argument of the spotifyplus.player_media_play_context service can accept either a Spotify Connect device name (e.g. ChromecastAudioLiving) or a device identifier (e.g. abcdef12345678901234567890).
UPDATE:
Per the Spook Documentation, there does not seem to be a way to ignore this message. Maybe an opportunity for the Spook developers to add some functionality to whitelist / ignore specified scripts maybe?
UPDATE:
Just noticed the obvious Ignore button at the bottom of the Spook warning dialog. Did you click that to ignore the message? If so, does it keep reappearing whenever you reboot / restart Home Assistant?
AFAIK Spook is creating a standard HA Repair notification so if you click Ignore it does just that until you un-ignore it (via overflow menu in /config/repairs)
1 Like
@Tsar @Gav_in
Kind of curious myself how this works.
I opened Spook Discussion #933 to see if the Spook devs can provide some guidance / insight.
1 Like
And until you restart HA 
Thank you for that.
In the same context I have an error on my “Android TV Remote” integration :
The problem there is that the integration can not load until I switch on my TV. So when I restart HA while my TV is off, I get that error. The moment I switch on my TV, the integration loads and the error disappears.
A white-list like the Watchman integration has would be nice.
yeah, that’s a HA thing…it’s how repairs work
not ideal (and not recommending) but Spook has a service to ignore all Repairs that you could call in an automation to clear this out (obviously it’d clear “real” repairs too)…a better solution for you would be selective ignoring of repairs but that may or may not come in the future who knows
@Tsar @Gav_in
The author of Spook refuses to add a whitelist feature for these types of notifications / repairs (see Spook issue 933 for details). He states that it is an issue with the SpotifyPlus integration, because it uses a device_id argument name. I do not agree with his explanation; the device_id value is not an HA device; it’s a vendor specific (e.g. Spotify Connect) device, of which HA knows nothing about. Spook is assuming that anything named device_id is a device, and performing a lookup in the HA device registry, not finding it, and creating a repair issue. To me, that is Spook’s fault for assuming it’s an HA device identifier. Again, the whitelist processing would account for that.
Anyway, I won’t pursue the whitelist feature any longer as the Spook author has made his position clear.
Just wanted to let you know.
1 Like
Strange, cause I did not get this error anymore the last couple of weeks… 
Thank you for your effort !
1 Like
Just wanted to say that I really like 
Spook! I always found it very annoying that Home Assistant would not warn me when an entity was referenced somewhere in an automation that did no longer exist. Although I still think this is very basic functionality that should be part of Home Assistant, I think it’s brilliant that we have Spook to help us out! It works like a charm: I found a lot of automations and dashboards that had references to non-existent entities. Thanks @frenck!
2 Likes
Hi all, I was pretty happy with Spook so far but - no clue exactly when - something broke.
2 Issues:
-
Spook is not working anymore. I installed it via HACS. Now, when I search for it in HACS I get the option to install it. So it seems that HACS is not aware that I already installed it and I don’t find any option to uninstall it… I saw spook “sensors” and I saw the integration + its devices. Now i uninstalled the Integration and when I click on “add integration” I am able to add it again. So there are some remainings in my system. I already did a full system reboot which had no effect.
=> I am now afraid, that - when I just re-install it via HACS, that I have some remaings in my system which could cause issues. How can I remove Spook to re-install it again? -
The version I see in HACS has a different state than in github
=> Both have the same version number, but a different maintained state… So what is going on here? 