The supervisor integration creates services and entities. Why aren’t these entities (specific to addons) grouped as a device?
Secondly, why isn’t the container slug available as a sensor? If it was, you’d be able to template automatic backups using slugs that can be easily gathered by looking at existing entities. Or the slug could be attached to the device like nodes are in zwave.
It does… I have a device per addon, don’t you?
As for the slug, that’s fair. You can get to the slug but it’s not common knowledge and could definitely be easier. I do it in this blueprint. Assuming you have a variable called entity that contains the id of an entity made by the supervisor integration for an addon you can get to the slug with this template:
{{ (device_attr(entity, 'identifiers') | first)[1] }}
Well well well, this WTH should be changed to: WTH are devices hidden behind the services link on the integrations page.
Maybe it’s poor wording, I assumed it was service calls and never clicked on it…
Zwave’s node is located in identifiers too, so that’s not a problem.