Wrong Logos are shown about core HOT 10 CLOSED

Hey there @Kane610, mind taking a look at this issue as it has been labeled with an integration (unifi) you are listed as a code owner for? Thanks!

_{^{(message by CodeOwnersMention)}}

unifi documentation
unifi source
_{^{(message by IssueLinks)}}

from core.

Devices can be covered by multiple integrations like for instance Nmap Tracker and ESPHome:

In those cases it's just random whichever logo is shown for the device.

In your case the device is covered by both the Shelly and Unify integration.

from core.

Hello, this is how the implementation is today. There are discussions about identifying primary and secondary providers of entities to improve this but that is out of scope for a bug report.

from core.

Hello, this is how the implementation is today. There are discussions about identifying primary and secondary providers of entities to improve this but that is out of scope for a bug report.

this is already implemented since 2023.8 (with #95641)

from core.

Hello, this is how the implementation is today. There are discussions about identifying primary and secondary providers of entities to improve this but that is out of scope for a bug report.

this is already implemented since 2023.8 (with #95641)

Sure, I formulated myself poorly. But AFAIK it's just a step towards identifying which source is primary so it's not solved all the way yet. The integration does provide the default_* attributes for clients

from core.

Hi @rrooggiieerr ,

Devices can be covered by multiple integrations like for instance Nmap Tracker and ESPHome: <img alt="Screenshot 2024-05-24 at 16 09 42" width="342" src="https://private-user-images.githubusercontent.com/18603534/333619406-cde5675e-9004-4acc-848f-

In your case the device is covered by both the Shelly and Unify integration.

I now what happens, and it is for sure true, that the device is covered by multiple integration, and in the device overview it is a nice feature to see all the logos.
But refer to the overview in my screenshot. There the logos are shown from the WLAN connection provider, which is imho useless, as for sure all WLAN devives are connected and detected by this integration. So it does not give any more information there, so better leave it out to save space.
Plus the fact, that one device shows the other logo (but has wlan logo in the device overview), makes me „wonder“ to say the least.
Plus the fact that it worked before the update to 2024.5.3 makes it a bug in my opinion.
Anyway. I will avoid updates in the future. Let others walk thru the update problem. I like a reliable system better than a fast, random system.

thanks
Juergen

from core.

Hi @rrooggiieerr ,

Devices can be covered by multiple integrations like for instance Nmap Tracker and ESPHome: <img alt="Screenshot 2024-05-24 at 16 09 42" width="342" src="https://private-user-images.githubusercontent.com/18603534/333619406-cde5675e-9004-4acc-848f-
In your case the device is covered by both the Shelly and Unify integration.

I now what happens, and it is for sure true, that the device is covered by multiple integration, and in the device overview it is a nice feature to see all the logos. But refer to the overview in my screenshot. There the logos are shown from the WLAN connection provider, which is imho useless, as for sure all WLAN devives are connected and detected by this integration. So it does not give any more information there, so better leave it out to save space. Plus the fact, that one device shows the other logo (but has wlan logo in the device overview), makes me „wonder“ to say the least. Plus the fact that it worked before the update to 2024.5.3 makes it a bug in my opinion. Anyway. I will avoid updates in the future. Let others walk thru the update problem. I like a reliable system better than a fast, random system.

thanks Juergen

AFAIK there has been no recent changes to this area but can differ between every restart of hass. Your statement about your upgrade strategy is irrelevant to this issue stay on topic.

from core.

I startet the HA quite often in 2024.4.4 and before, and it neveer was an issue. The randomness of the logos than came in in 2024.5.3.
And „fastness“ seemed to be a major feature. I only vote for reliability.
But you are right. Case closed.

from core.

This is also a purely aesthetic problem, I am happy its not a functional issue :)

from core.

If not handled, it might be sooner or later a functional problem as well, as there seem to be informations not used at least at this point, that might/should/could be handled. I would bet anything that this will be a functional problem.
Anyway… let‘s keep out fingers crossed, that asthetical and functional do not split too much.

form follows function :-)

So if I see „bad form“,…

from core.