Showing wrong integration when adding them

[thibaultmol]

I'm noticing that for some devices it's showing the wrong integration. Like for this wifi shelly flood sensor, it's showing Unifi instead of Shelly (that devices has both integrations in HA but obv the Shelly one is the main one)... I assume there's a problem where you can't tell which is the 'original' integration from HA? if not.. maybe going off of which integrations provides the most entities for a given device could be a thing? Or maybe you could look at the device manufacturer and see if there's a match with one of the integrations

Same thing is happening for the Roborock custom map hacs integration (which just adds a couple image sensors to existing roborock devices.

[andrew-codechimp]

Hi, those integrations are using the deprecated method of adding themselves to devices (the two integration icons/names showing on the device page). This is due to be removed from HA in August and the majority have been done (Templates as an example).

As it's a fairly time limited issue I don't want to cater explicitly for this now as it will go away, but thanks for pointing it out.

Tech article for reference
https://developers.home-assistant.io/blog/2025/07/18/updated-pattern-for-helpers-linking-to-devices/

[thibaultmol]

OOOH ok interesting. The Unifi network one might have been remnants of a unifi integration I seem to no longer have installed. so i've deleted those entries.
For the "Roborock custom map" (I don't know enough about how it works internally) but I think this one specifically replaces existing entities and thus maybe can't use that method? cc @Lash-L

[andrew-codechimp]

I use UniFi myself and it still does it, just looked at the code and it's doing a little extra than inserting entities, it's adding the MAC address to device info which is probably why it's taking time to fix.

It seems Roborock custom map is doing something similar with device_info.host = network.get("ip")

I don't think the core architecture change has catered for that, which will probably mean they'll have to add those extra values as diagnostic sensors in the new way of doing things.

I've fixed a few of these on my own integrations so I've been watching this subject closely.