Unexpected device attributes

[erkr]

Unexpected device attributes

[teskanoo]

Power calc entities are added to existing devices
integration_entities('powercalc') will return all entities set up by powercalc
device_attr(entity, 'identifiers') will return a list of all identifiers related to the entity (this would be the identifier linked to the entity's original device)
to skip the identidiers belonging to the entities in the groups, you may have to try...

{% set pwr_entities=integration_entities('powercalc') %}
{%- for entity in pwr_entities %}
{%- set ids = device_attr(entity, 'identifiers') %}
{%- if ids is not none %}
    {{ entity }}
    {{ device_attr(entity, 'identifiers')  }}
{%- endif %}
{% endfor %}

You may also be able to expand the groups and iterate over the entities in that group
{%- set group_entities = entity |expand|map(attribute='entity_id') %}

[erkr]

Hi @teskanoo
I really appreciate your quick reply 😊
I realize some extra background should have been helpfully.

I wrote a template to list unavailable devices. That became more complicated than I originally anticipated, two challenges, the first one I tackled, the second I'm looking into 😅

Basically a device is defined unavailable when all device related entities are unavailable, with some exceptions.

1: some devices have a status entity of device_class connectivity. That entity will remain available (in problem state).

2: Sorry for the long intro, but here I found out that some devices were extended with Powercalc entities. Those can remain available as well, depending the configuration for unavailable.

But I now understand you extent them on purpose. So maybe I have to rethink my approach.

Update: the real issue is that I don't now a decent way to list all integrations. So the approach starts with looking up the integrations for all entities (via the device attribute identifiers).

[erkr]

As this seems a deliberate choice, with well thought reasons, you are free to close the issue 🤓

[bramstroker]

Yes, Powercalc entities are connected to same device as the source entitity, and this is one of the key features of Powercalc.

You might want to retrieve all powercalc entities first in your template and assign those to a variable.
As @teskanoo mentioned: {% set pwr_entities=integration_entities('powercalc') %}
And then exclude these when determining availability for a device.

[erkr]

As @teskanoo mentioned: {% set pwr_entities=integration_entities('powercalc') %}

And then exclude these when determining availability for a device.

Yes I have done that, my issue is solved😊 I close this issue now.
I just published the macro to share: https://community.home-assistant.io/t/a-sensor-to-list-unavailable-devices/684896/36