Repair: false positive Unknown services used in: ......

[andyblac]

What version of Spook are you using?

2.2.2

What version of Home Assistant are you using?

Core: 2024.2.2

The problem

getting this in system repairs for this Blue Print Low Battery Notification, I have contacted the author and he says the blue print is correct, and using documented code.

Anything in the logs? Paste it here!

No response

[frenck]

Do you use the todo integration?

[andyblac]

no, I do need need it

[frenck]

Well the blueprint uses it, so, as a result, your automation does. Spook checks if all possible called services in an automation exists. If it doesn't, it will raise a repair.

I can see how, this is less helpful in case of a blueprint. I will check if I can learn Spook about it.

[NodeJSmith]

After updating spook yesterday I'm getting a false positive regarding androidtv.adb_command. Happy to open a separate issue but I'm wondering if it's related to this one, based on the timing and similarity.

[frenck]

I think it is related to the issue reported that errors aren't cleaned up. Even if it was a timing issue, it should resolve normally.

[HaraldGithub]

I think it is related to the issue reported that errors aren't cleaned up. Even if it was a timing issue, it should resolve normally.

Hi @frenck Since the last Update of spook I've a similar issue: I got this repair announcement about an unknown entity:

but in developper tools this entity is known:

and in "Overview" it is also available:

I've received this message after restart from update from 2024.2.1 to 2024.2.2.

In former times, and also before last spook-update, I've received this message, too, but it was gone some seconds after restart of HA. On restart of HA, an automation will also restart the samba-addon, so for few seconds it might be possible, that spook recognize this entity as unavailable. But after the restart of the add-on it's available (as you can see in screen shots above). I think it's a bug in the last spook-update.

[frenck]

@HaraldGithub Please don't stack different/unrelated issues. Your message is not about services...

[HaraldGithub]

@frenck I know, that my problem is not related to services, but I quoted you statement, because it might be also a "a timing issue, it should resolve normally". But okay, I've opened an new issue: #627

[dafunkydan]

Well the blueprint uses it, so, as a result, your automation does. Spook checks if all possible called services in an automation exists. If it doesn't, it will raise a repair.

I can see how, this is less helpful in case of a blueprint. I will check if I can learn Spook about it.

I had/have the (i guess) same Problem, where the https://github.com/lsismeiro/awesome-ha-blueprints, which i use for my Remotes, reports an empty and unknown Device

I guess this is, because the Blueprint offers either a Field for a Controller Device (deCONZ, ZHA), or for a Controller Entity (Zigbee2MQTT), where there is always one Field empty..