Device is associated with several integrations

I believed that a device may only be associated with ONE integration:

integration XYZ
  |_ device_1
       |_ entity_11
       |_ entity_12
  |_ device_2
       |_ entity_21
       |_ entity_22

But I see now - a device is associated with several integrations:

изображение

What I see in “core.device_registry”:

      {
        "area_id": null,
        "config_entries": [
          "f202e796036908ce77bd4462ce6eb5da",  # iPhoneDetect entry
          "de12bdbe3bfa9520ef4ccc558dca9e1a"   # ASUSWRT entry
        ],
        "configuration_url": null,
        "connections": [
          [
            "mac",
            "f0:f6:1c:5d:6e:4a"
          ]
        ],
        "disabled_by": null,
        "entry_type": null,
        "hw_version": null,
        "id": "6f1bef960bd1ec9c8962220f850b2f55",
        "identifiers": [
          [
            "iphonedetect",
            "f202e796036908ce77bd4462ce6eb5da"
          ]
        ],
        "labels": [],
        "manufacturer": null,
        "model": null,
        "name_by_user": null,
        "name": "iphone_5s_32_iphonedetect",
        "serial_number": null,
        "sw_version": null,
        "via_device_id": null
      },

Somehow this device is associated with 2 integrations.
Is it by a design?

1 Like

Yeah, it’s by design. For instance I have a Shelly that has 3 integrations associated with it. Shelly, my router’s integration giving home/away status and PowerCalc for calculating power/energy.

I think this might have been a new feature a few months back? Regardless, it’s normal.

1 Like

A device can be associated with several integration (seems to be strange for me).
An entity can be associated with ONE device.
An entity is still associated with ONE integration (as expected) - not with several.
Isn’t it inconsistent?

At least in my cases it all makes a lot of sense and is WAY easier to find stuff in one place rather than having to remember which integrations possibly apply to a given device.

I would agree if a “device” stands for some physical object - which can be analysed/measured/polled by several integrations.
For me, a “device” term in HA is a bit “blurry” since there are “devices” for many not-actual-devices…

Yeah, I noticed this recently myself and find it more confusing to try to keep all my “devices” organized.

for example, I have some Sonos speakers. I installed the Sonos integration, the Sonos Cloud integration and the Powercalc integration. The speakers get associated with all three integrations.

now when I go to the Sonos integration page and open a device the device page shows all the entities associated with all three integrations instead of just the entity associated with the Sonos integration:

So now I have to try to figure out which entities are provided by which integration.

And if you click on the integration list on the left you would think it would drill down and then only show the entities from that particular integration. But it doesn’t. It takes you right back to the exact same device page as before. Totally unhelpful.

To keep things straight I needed to figure out by trial and error and educated guessing which entities were provided by which integration and then name them all accordingly. And that’s the only reason the entities above are named correctly is because I did it myself. The default names gave no indication which was which.

And you can’t just rename a device associated with each integration differently either. So all the integrations end up having the same device name but different entity names depending on the integration.

If I click on the Sonos Cloud integration I don’t want or need to see all the entities from the Sonos or Powercalc integrations. If I wanted to see those I would have clicked on those integrations instead.

Definitely not very user friendly.

2 Likes

iPhoneDetect - in 2.2.1 devices are no longer associated with ASUSWRT.
It was rather confusing to see unrelated devices on ASUSWRT page.

I guess I would add that if someone wants to see all integrations that a device is associated with then there is a tab specifically for devices. And that would make sense under that context to show them all there.

But each integration page should only show the entities of the device that are associated to that integration.

IOW, there should be two device pages and they should each be context sensitive from where you navigated to them from.

Hmmm…

issue

Created a FR. Please vote here.

I think this might be related to this issue. If not, feel free to say so and point me elsewhere.

I have 5 TP-Link devices. For some reason, HA combines clearly separate devices.

Expanding Smart Bulb 1, you can see it contains the bulb and a smart plug (hallway is a light and Tivoli is a plug):

Similarly for bulb 4, it is the foyer and music room lights, and again the plug: