Icon Color >:(

tescophil · May 17, 2020, 10:44am

So, the latest beta version of HA (0.110.0b3) breaks the icon_color customisation provided in the widely used custom-ui modification https://github.com/andrey-git/home-assistant-custom-ui This repo is no longer maintained, so these issues will only get worse over time.

Is it just me that thinks very basic customisation options like this should be provided in the HA core functionality ?

I have a very basic UI for my HA install, but the one thing I do everywhere is change the icon color/type for a device based on state. This might be something simple like changing the icon color of a group of lights from blue to yellow when the group is turned on to mimic the functionality provided in the HA core (i.e. Turn a light entity on and the icon color changes from blue to yellow), or changing the icon for a person entity based on their location.

It’s even more frustrating that this cannot be done because its done automatically from some entity types like lights.

Isn’t it time this basic customisation was added to the HA core…?

VDRainer · May 17, 2020, 10:47am

No.

github.com/home-assistant/frontend

replace custom-ui, allow for customizing entities globally

opened 09:59AM - 15 May 20 UTC

closed 03:50PM - 19 May 20 UTC

Mariusthvdb

Feature Request

## The request  Since from ha0.110 on custom-ui is no longer able to customize <strike>icon and</strike> icon_color (maybe more, but I haven't tested that yet), and core Lovelace up to now offers no way of customizing entities icons and icon_colors, other than per theme or using eg state_color, the request is to offer some way for replacing custom-ui in core HA ## The alternatives  we can use custom cards, but they too only offer customizations per card ## Additional information using things like: ``` homeassistant: customize_domain: automation: templates: &state_color icon_color: > if (state == 'on') return 'gold'; return 'steelblue'; switch: templates: icon: > if (state == 'on') return 'mdi:toggle-switch'; return 'mdi:toggle-switch-off'; <<: *state_color customize_glob: light.hue_ambiance_spot_*: icon: mdi:spotlight-beam switch.*motion_sensor: assumed_state: false device_tracker.*_bt: templates: icon: > if (state == 'home') return 'mdi:bluetooth'; return 'mdi:bluetooth-off'; icon_color: > if (state == 'home') return 'blue'; return 'grey'; sensor.*_temperature: templates: icon_color: > if (state < -20) return 'black'; if (state < -15) return 'navy'; if (state < -10) return 'darkblue'; if (state < -5) return 'mediumblue'; if (state < 0) return 'blue'; if (state < 5) return 'dodgerblue'; if (state < 10) return 'lightblue'; if (state < 15) return 'turquoise'; if (state < 20) return 'green'; if (state < 25) return 'darkgreen'; if (state < 30) return 'orange'; if (state < 35) return 'crimson'; return 'firebrick'; #icon example sensor.owm_wind_bearing: friendly_name: Wind bearing templates: &direction_icon icon: > var icons = ['mdi:arrow-down','mdi:arrow-bottom-left','mdi:arrow-left', 'mdi:arrow-top-left','mdi:arrow-up','mdi:arrow-top-right', 'mdi:arrow-right','mdi:arrow-bottom-right']; var quadrant = Math.round(Number(state)/45); if (quadrant < icons.length) return icons[quadrant]; return 'mdi:arrow-down'; #used for all other wind-direction/bearing sensors, only define once using an anchor... #untested yet, but hope this will still be possible setting custom images: sensor.dark_sky*icon*: templates: entity_picture: > return '/local/weather/icons/' + state + '.png'; ``` makes it dead easy to have these entities show with a meaningful icon and icon_color in the frontend, and doesn't enforce styling these entities individually in the Lovelace card configs. Be it core or custom. example of an issue the now defunct custom-ui throws at the user: a mere custom:auto-entities card with all temp sensors in the system will become a flat and meaningless card, since without a lot of trouble, and yet again another custom card, like card-mod, we can't style these. Even if we could, these stylings are only refreshed upon reload of the page, and not of the state of the entity. As they are now, using custom-ui. examples: ``` - type: custom:auto-entities card: type: entities style: | ha-card { box-shadow: none; margin: 0px 0px 0px -36px; } filter: include: - group: group.github_repos_in_use options: tap_action: action: more-info hold_action: action: navigate #url navigation_path: weblinks # # url_path: > # # {{ state_attr(config.entity,'latest_release_url') }} type: custom:template-entity-row style: | :host { --paper-item-icon-color: {% set id = config.entity.split('.')[1] %} {% set repo = 'input_boolean.' + id %} {{'gold' if is_state(repo,'on') else 'green'}} ; ``` forgive me the complexity of this, but that is really the purpose of the post: Without functional Custom-ui and no core Lovelace alternative for customizing these entities and properties users are forced to create terribly complex configs. Or be satisfied with/ use a rather pale Homeassistant Lovelace interface... color is a most striking aspect of system feedback. Using custom icons too. Please don't do away with that option. <img width="360" alt="Schermafbeelding 2020-05-15 om 00 32 01" src="https://user-images.githubusercontent.com/33354141/82037250-29e58f00-96a2-11ea-884e-89eb4202dbcf.png"> Of course, if at all possible, and a change/edit of the current custom-ui files would be possible, I'd be glad to try and help realizing that. It's only about changing 1 file, so must be doable...? thanks for considering. some [discussion in the community](https://community.home-assistant.io/t/ha-110-no-longer-supports-custom-ui/195820/18)

tescophil · May 17, 2020, 11:04am

Cool…

On a related note I attempted to downgrade to a non beta version using the command line

ha core update --version 0.109.6

However after the process had finished I was still on 0.110.0b3. Tried this twice on the command line and once via the UI, same result…

VDRainer · May 17, 2020, 11:15am

Have you tried

ha core update --version=0.109.6

If this works, there will be probably an issue on HA start with the external_url key which is added in 0.110 beta.
I had to remove the key from .storage/core.config, HA didn’t start with it.

Mutt · May 17, 2020, 11:45am

Me thinks they are prepared to break that because they are streamlining the frontend and will be providing ‘that sort’ of functionality in the frontend (as they are moving to in other areas).

It’s just my guess though.

And if so, Marius’s PR will get rejected (but perhaps with an explanation this time)

tescophil · May 17, 2020, 11:59am

Still no joy, removed the key, tried the update command with no version specified, then with the = (instead of the space specified in the command line help file), then with the space again…, still on 0.110.0b3.

Another BUG, state dependant glance cards no longer work in this version, OpenHAB is looking better every day…