New Custom UI features: Context-aware names, Context-aware hiding, Badges!

It may not be the source of your issue(s) but have a look at the Custom UI activation docs here.

Once you have, you should notice that you are combining 2 ways of activating Custom UI: by specifying extra_html_url under the frontend component AND by adding the customizer component. You only have to use one or the other.
Not only that, you used those 2 ways to specify 2 different sources for Custom UI: in the frontend component you link to the Custom UI files locally, while you set up the customizer component to use hosted files.

And finally, shouldnā€™t ā€œ.ā€: be "*.*" ? (also notice how your quotes are different, I copied/pasted them from your post above)

Hi
Thank you for posting, actually when reading the docs again I can see that there is a change for 0.59
extra_html_url_es5:

  • /local/custom_ui/state-card-custom-ui-es5.html

Now it is wokring!

Would it be possible to enhance the use of sliders for temperature control? They would have a similar function to covers I would think?

Climate can have two temperatures. Also the status takes more space, leaving less space for a slider.

Still you could make it that the sliders were only valid if under the text, one for each of the set temperatures?

Seems nontrivial to make a consistent UI for this case.

That said if someone implements this - you can use it together with my customUI using state_card_custom_ui_secondary

Capture8

trying to figure it out without success.
i did use the update.sh file script
did i miss something ?

configuration.yaml

homeassistant:
  customize: !include customize.yaml
  customize_glob: !include custom_ui.yaml
customizer:
  custom_ui: local
frontend:
  extra_html_url:
    - /local/custom_ui/state-card-custom-ui.html
  extra_html_url_es5:
    - /local/custom_ui/state-card-custom-ui-es5.html

groups.yaml

asaf_devices:
    name: Asaf
    entities:
      - group.asafdevicesbadges
      - sensor.asaf_le_battery
asafdevicesbadges:
    entities:
     - device_tracker.liron_mi
     - device_tracker.asaf_le
     - sensor.asaf_le_state

custom_ui.yaml

    "*.*":
      custom_ui_state_card: state-card-custom-ui  
    group.asafdevicesbadges:
      state_card_mode: badges
      badges_list:
        - device_tracker.liron_mi
        - device_tracker.asaf_le
        - sensor.asaf_le_state

Not sure if related, but you are loading customui twice: once via customizer and once directly via frontend

Is this what it should look like?

This is how the custom-ui config panel looks. It is used to set device name for device-aware attributes.

1 Like

Hi!
Do you guys understand how to configure the distance between badges?

The broken distance between badges should have been fixed.

Hi,

Is it true that this will not work:

customize:
  group.group1:
    hidden: true

custom_ui:
  group.group1:
    custom_ui_state_card: state-card-custom-ui
    device:
      device_name:
        hidden: false

I can get it to work the other way around, using custom UI to hide it on a device but not to show something thatā€™s hidden by default. Would be nice if this was possible.

Correct.

If an entity is hidden it wonā€™t get a state-card, so there will be nothing to customize.

Is it possible to use Custom UI to change the HTML tag of the page so that instead of ā€˜Home Assistantā€™ in the tab on the browser you could change this ?

No, currently it is not possible.

@andrey Anyway to get custom_ui working with Lovelace?

It is still very experimental. Iā€™ll wait before releasing a version.

1 Like

Iā€™m trying to hide some things with customizer and hide_attributes but they are still displayed on the cards.

Any idea what Iā€™m doing wrong? The cards still have ā€œgroupā€, and ā€œslider themeā€ and ā€œstate card modeā€ displayed.

Loaded CustomUI 20180716

customizer:
  custom_ui: local
  hide_attributes:
    - group
    - state_card_mode
    - source_type
    - slider_theme
    - confirm_controls_show_lock

Can you add a screenshot to f the issue?