Lovelace and hiding entities

Configuration Frontend
22

Thanks @petro

It only includes changes made to .yaml configurations.

Maybe you’ll not run into problems where reverting the config doesn’t need you to revert the UI steps at the same time. I’ve been coding 38 years; it’s happened more frequently recently.

FWIW, the automatic recording of config from switches was a more common thing before. “rancid” (“Really Awesome New Cisco confIg Differ”) was this cruft of “don’t read it but it works” scripts to collect changes in config and commit them to a repo. You might find it useful for that workflow if it’s still out there.

Thanks for the help. You’re generous to give your time for others.

1 Like
23

That’s what the snapshots are for. They backup everything.

24

While I appreciate that I can “take control”, I kinda like that the system automatically adds things. Initial integrations are easy and nothing ever gets lost.

It’s unfortunate that there is no longer the ability to remove from the UI those things that were automatically added. (The UI quickly gets cluttered without it.) That’s the best of both worlds.

– Brian

1 Like
25

I too want to stay with the auto generated Dashboard but need to be able to hide duplicate entities. I don’t understand why they took the capability away to delete them from thenUI!

2 Likes
26

Likewise. Being unable to hide redundant or superfluous entities, without forever preventing new devices being added automatically to the UI in the future, is a harsh penalty.

I have a set of z-wave wall switches that control the lights in my home.
For better integration, I’m using the light platform to announce to Home Assistant that they are lights.
Because of this, there are now two entries for each device in my Lovelace UI. That really clutters things up…

27

Old thread, but this might be useful. I want to hide the HVAC temperature control for the living room if that room has the HVAC is switched off. I use the condition card, with a sensor defined to make it work. This is for the Airtouch4, and I’m using entity slider row as the control.

sensors.yaml
This make the preset mode property of climate.itc_living available as an entity state, so the Conditional card can use it.

      - name: Living Preset Mode
        state: "{{ state_attr('climate.itc_living', 'preset_mode') }}"

This defines a card type on my Lovelace dashboard with two conditions

  • The room damper is turned on
  • The Preset Mode is ITC (which standards for Individual Temperature Control or something like that)
      - type: conditional
        conditions:
          - entity: fan.damper_living
            state: 'on'
          - entity: sensor.preset_mode_living
            state: ITC
        card:
          type: custom:slider-entity-row
          name: Living Temp
          entity: climate.itc_living
          attribute: temperature
          min: 19
          max: 26
          step: 1
          grow: true
          toggle: false
28

I am wondering if it’s possible to use OR in this conditional type like in automations:

- condition: or
        conditions:
        - condition: state
          entity_id: person.jimmy
          state: home
       - condition: state
          entity_id: person.joey
          state: home
29

I’m not really sure I understand your question. You can use OR logic in conditions fine.

30

What I mean is, that your config for the conditional behaviour means that both must be true to show the card (AND condition).
But how to use this with OR?
I have these two entries I would like to simplify to one. I would like to show the ring doorbell camera picture if someone rang the door OR if there is motion (occupancy) in the front yard.

cards:
  - type: conditional
    conditions:
      - entity: input_boolean.ring_active
        state: 'on'
    card:
      type: picture-entity
      entity: camera.kamera_haustur_mqtt_snapshot
      camera_image: camera.haustur
      camera_view: live
      show_state: false
      show_name: false
    view_layout:
      grid-area: header1
  - type: conditional
    conditions:
      - entity: input_boolean.garten_vorne_occupancy
        state: 'on'
    card:
      type: picture-entity
      entity: camera.kamera_haustur_mqtt_snapshot
      camera_image: camera.haustur
      camera_view: live
      show_state: false
      show_name: false
    view_layout:
      grid-area: header1

But the structure is different and there is no “option” to conditional (OR) like in my example above (taken from automation yaml syntax)

I tried:

  - type: conditional
    conditions: or
      - entity: input_boolean.ring_active
        state: 'on'
      - entity: input_boolean.garten_vorne_occupancy
        state: 'on'

and

  - type: conditional
    conditions:
      condition: or
        - entity: input_boolean.ring_active
          state: 'on'
        - entity: input_boolean.garten_vorne_occupancy
          state: 'on'

and

  - type: conditional
    condition: or
    conditions:
      - entity: input_boolean.ring_active
        state: 'on'
      - entity: input_boolean.garten_vorne_occupancy
        state: 'on'

the last syntax one though is accepted by the UI, but acts still as AND

31

That won’t work, all conditions must be met.

IMG_0280
IMG_02801198×920 107 KB

Use an Entity Filter Card instead.

32

You could also try creating another calculated sensor and using that. I think it’s possible, but I haven’t done it. I just do simple things like aliasing sensors, I have this in my sensors.yaml

  - sensor:
      - name: Temperature Forecast Minimum
        unique_id: temperature_forecast_min
        state: "{{ states('sensor.openweathermap_forecast_temperature_low') }}"
        unit_of_measurement: "°C"
33

@pedolsky
Thanks - I will give the Entity Filter Card a shot.
Wouldn’t this entity filter card be shown, but just empty?

@tomwaldnz:
That’s a good suggestion as well to create a combined entity.

34

The card provides show_empty: (true/false).

35

You are right - thanks for pointing out! Never used that before :slight_smile:
Thank you!