We can customize entities in core Home Assistant. This is however rather limited. Two of the most important features Custom-ui offers on top of the core customization are Templates and support for the icon_color attribute. We can use these features globally in our Home Assistant configuration and thus create extremely powerful yet very compact customizations. Added to that, custom-ui allows one to hide attributes from the more-info pane. Check the examples how.
GPT has arrived As an experiment several iterations of optimizations by https://chat.openai.com/chat have been made available as pre-releases. Please have a look, and test if you can.
Recently discovered....: custom-ui facilitates setting a Jinja template on custom attributes in core integrations that allow setting a custom attribute.
-
Download the custom-ui
-
Place the file in your
config/www
folder or any subfolders. -
Include the card code in your
ui-lovelace-card.yaml
title: Home resources: - url: /local/custom-ui.js type: module
or when using the UI, click
-
Make sure the HACS component is installed and working.
-
Search for
custom-ui
and add it through HACS -
Add the configuration to your
ui-lovelace.yaml
resources: - url: /hacsfiles/custom-ui/custom-ui.js type: module
-
Refresh home-assistant.
See INSTALLING
See EXAMPLES.
It goes without saying that custom-ui is an extension of core Home Assistant functionality. As such, you should understand what is documented on Homeassisant.io about the subject.
Important to note, is that Home Assistant core Jinja templating is calculated in the back-end, server side, (the device Home Assistant is running on). Custom-ui Javascript templating is calculated in the front-end, browser side, (the device Home Assistant is displayed on).
Heavy templating might impact the performance of the system and will depend on processor power and memory available on either side of your devices.
Custom-ui can't customize everything. Entities created in python scripts (you need to set the customization in the script itself) and entities created by several add-ons can't be touched by custom-ui. E.g. Home Assistant Google Drive Backup, and Argon One active cooling. You can work around that by creating template sensors for those entities, which you can again customize in HA.
Not all core HA cards use the same icon handling. Because of that custom-ui doesn't work with
Thomas Loven's Card-mod, which is an amazing plugin for Lovelace with many features, to the rescue.
Be aware that custom-ui is very impactful. As a matter of fact, it is 'stronger' than card-mod.
Meaning if you have e.g. a customize_glob
on icon_color
set using custom-ui, any card-mod
config won't work.
I've been a longtime and heavy user of custom-ui, and this is the place to applaud Andrey for his amazing plugin. Home Assistant wouldn't be the same without the global customizing it enables us to do. Couldn't live without it! All credits go to @andrey-git. You can read up on a bit if history how it came to this adapted version.