Open RASBR opened 1 year ago
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment π This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
This is still relevant
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment π This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still relevant IMO
Yes, still relevant. There is an arch discussion that will potentially enhance the backend so we can reliably get the information from there. That would then help the frontend to show the correct info: https://github.com/home-assistant/architecture/discussions/936
@spacegaier I do believe that proposal would help the situation, but would not completely solve the icon issue. I'll comment more there.
Experiencing the same problem for Shelly devices with a combination of the Shelly integration and a "AVM FRITZ!Box Tools" integration. Expecting to see Shelly icons for the Shelly devices, but some (not all) are represented by FRITZ icons.
There seems to be an architectural discussion on auto determining primairy or secondary integration of a device. Hope that can be addressed soon as the different brand icons are at least confusing. But is there a workaround known for (manual) correction? Should I remove the second integration, so all double registrations fall back to its remaining integration as primary, after which I can reinstall the second integration? My concerned integrations on this topic are primary Shelly devices and secondary Ubiquity network.
+1
All of these should indicate ESPHome as the primary integration. I've even disabled the UniFi device tracker on each of them.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment π This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
+1 I have the same issue. The icon in the device list should be configurable (set to the "main" integration). E.g. Sonos/Ubiquiti:
Same with ESPHome/Ubiquiti:
It seems that the icon in the device list is taken from the first integration that is listed in the device info.
It would be nice to make this configurable (set "main" integration for device).
Thank you
This makes it clear:
The icon is not taken from the "Manufacturer" but from the first entry in the "Integration" column of the device list. I would expect the icon is defined by manufacturer.
(Screenshot was taken from Frontend 20240306.0, Core/Supervisor 2024.3.0)
I encounter the same with Asusrouter integration, Sonos, Samsung and Homewizard devices
Can confirm this happens to me as well, e.g. the TP-Link plugs sometimes having Nmap icons instead of TP-Link based on which integration is listed first
Still relevant. Battery notes and Unifi are destroying any sort by integration I attempt....
Same issue, it's confusing, did not find a workaround to swap the integrations. Would like to see Shelly icon for all Shellies.
+1
Same here with Shelly, Devolo and ESPHome
Same for me, makes it hard to quickly identify devices when everything has a Unifi icon against it :)
I'd also like to see this resolved.
If you wanted a nice, UX friendly solution, you could make the device info panel a list where you can drag the order of the integration around, top one being the primary.
E.g.
Same... this really sucks when trying to organize.
I would like to see this resolved too, current implementation makes organization difficult and confusing. I propose an option that allows for setting a main vendor for each device.
so I think I have similar wher e a device shows multiple installations....and Im also seeing when some devices are resatrt/changed, they then affect those other integrations
In the below example, the integration is Solarman...but its also showing as UNifi and Utility meter. There is an option to Remove device from Unifi (in red text) but it doesn seem to do anything
Strange behaviour is that if I ever change one of the link integrations, it then advsersely effects the others as well which I am sure shouldnt happen
I noticed this on a device page with the wrong icon, this is really sloppy and should be fixed:
Similat problem here, I got a Shelly device and it is primarly assognes to the FRITZ!Box Integration instead to the Shelly integration. It's mainly about the wrong icon.
Checklist
Describe the issue you are experiencing
I have some Shelly 1PM (and other models) devices I setup with the same exact steps. Those devices are provided to HA from two integrations Shelly and Unifi Network. The thing is that they are not represented the same in HA especially in regards to Brand Logo!
Attached some screenshots.
Describe the behavior you expected
Device brand icons to be represented according to their manufacturer.
Steps to reproduce the issue
What version of Home Assistant Core has the issue?
Home Assistant 2022.11.0
What was the last working version of Home Assistant Core?
No response
In which browser are you experiencing the issue with?
Version 108.0.5359.95 (Official Build) (64-bit)
Which operating system are you using to run this browser?
HA is installed on Intel NUC
State of relevant entities
No response
Problem-relevant frontend configuration
No response
Javascript errors shown in your browser console/inspector
No response
Additional information
No response