Mariusthvdb Custom Ui Save

Add templates and icon_color to Home Assistant UI

Project README

What is Custom-ui

hacs_badge GH-release GH-downloads GH-last-commit GH-code-size

We can customize entities in core Home Assistant. However, this is rather limited. Two of the most important features Custom-ui offers on top of the core customization are support for:

  • Templates
  • 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.

icon-color

Development of this plugin, strategy forward

Please see the pinned discussion on development of this plugin.

In short:

  • If you want a tool to customize icon_color: Use either custom-ui-only (with template support) or custom-icon-color.
  • If you want a tool to customize more-info dialogs: Use custom-more-info

Current custom-ui (with legacy more-info manipulation) will be archived, and renamed, so we can keep the custom-ui name for the current custom-ui-only.

NEWS

New Custom More-info

Custom More-info is a new custom Plugin for Home Assistant and superseeds the plugin custom-attributes announced below.

Next to the functionality of custom-attributes, with custom-more-info users can customize when and when not to display the History and Logbook sections in the More-info card. Even hide the History icon in the Header completely. Automatically, or based on manual settings.

From now on you are in control of the More-info attributes and all other sections. Filter all, unfilter all, or select which to see/hide by glob, domain, device_class, or entity_id. Any combination is possible!

Custom More-info gives the user ultimate control over the More-info panel.


New Custom Attributes

Custom attributes is a new resource for Home Assistant to customize which entity attributes are displayed in the Dashboard on more-info cards. Moreover, if configured so that no more attributes are left to display (all attributes are filtered), the attributes dropdown box is not rendered at all. This is replacing that specific functionality from Custom-ui.

DON'T INSTALL BOTH CUSTOM-ATTRIBUTES AND CUSTOM-MORE-INFO SIMULTANEOUSLY. USE ONLY 1 OF THESE 2 NEW PLUGINS


New Custom icon_color

A new custom-ui sibling was released, custom-icon-color, which can be used only for adding an attribute in customize: and the attributes configuration options of template: entities.

No more templates possible with this version, which minimizes impact on the HA system and Frontend if you wish to do so. There was never a huge impact, but this brings it down even further, if you don't need the template options and still want the icon_color attribute in your options. Configuration is identical to what is already explained in the example section


Did you know....: custom-ui facilitates setting a Jinja template on custom attributes in core integrations that allow setting a custom attribute.


Installation

Manual Installation

  1. Download the custom-ui

  2. Place the file in your config/www folder or any subfolders.

  3. 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

Open your Home Assistant instance and show your Lovelace resources.

Installation and tracking with hacs

  1. Make sure the HACS component is installed and working.

  2. Search for custom-ui and add it through HACS

  3. Add the configuration to your ui-lovelace.yaml

    resources:
      - url: /hacsfiles/custom-ui/custom-ui.js
        type: module
    
  4. Refresh home-assistant.

Other installation methods

See INSTALLING

Examples

See EXAMPLES.

For card-mod replacement mods, see CARD-MOD-EXAMPLES


Learn core Home Assistant customization

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.

Caveats

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. You can work around that by creating template sensors for those entities, which you can again customize in HA.

Not all Lovelace cards are equal

Not all core HA cards use the same icon handling. Because of that, cards like

are not customized by custom-ui.

Thomas Loven's Card-mod, which is an amazing plugin for Lovelace with many features, to the rescue.

Interaction with Card-mod

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.

Credits

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.

Open Source Agenda is not affiliated with "Mariusthvdb Custom Ui" Project. README Source: Mariusthvdb/custom-ui
Stars
150
Open Issues
0
Last Commit
3 months ago

Open Source Agenda Badge

Open Source Agenda Rating