I would do it differently

[moskovskiy82]

We all have lovelace. With so many options around (custom buttom cards etc) sometimes we need to have a fresh view on how it can be done differently. So if anyone has an example of a temp control card - would love to see how it’s being done.

For example working on the following.
Room temp card done just with entities (Bedroom). Taking tooo much space and looking ugly

It shows the temperature in the room 1.
Setpoint for the day temperature 2
Setpoint for night temperature 3
Valve position on the radiator 4
Hostory graph for valve position 5.

[tom_l]

Here are some options:

Mini Thermostat

Another take on the thermostat card. I wanted to have a small card which could control my Nest, without pushing other cards all the way down. [image] See https://github.com/Devqon/lovelace-mini-thermostat It can be installed through HACS by adding the above github link. This is my first Lovelace custom card without pre-knowledge, so there probably are a lot of things that can be done better/different. Let me know what you think!

Lovelace: Simple thermostat card

Driven by a want for a simpler thermostat card in terms of interactions and usability, that would also be more flexible and make information clearer I’ve built this card for Lovelace, simple-thermostat. I need to give a lot of credit to @magnus.overli as a faithful tester and having at least 50% of the needs that we’ve tried to cover with this card [59] As you can see the main difference is that it replaces the round dial with simple buttons and it presents relevant entity a…

Lovelace: Multiple entity row

Multiple Entity Row Show multiple entity states or attributes on entity rows in Home Assistant’s Lovelace UI. See the Github page for installation and configuration. Features Show multiple additional entity states on a standard entity row Show attribute value instead of state (from any entity) Any entity or attribute value as secondary_info Show toggle (for switch, light, etc) Hide default entity state to only show additional entities Customize name and unit on additional entity object Custom…

[moskovskiy82]

Thanks. Not exactly what i meant. Maybe HA commuity would share their screenshots on how they have done it. This would also provide inspiration on the logic they have used for such a task

[tom_l]

Oh right. Sorry for the misunderstanding.

Here’s mine:

The reason for the bar graph temperature is that the temperature reported on the thermostat is the system temperature, not the room temperature. They just happen to be the same at the moment. Usually they’re not, like this (you can also see how the bottom section expands to reveal the settings. It uses fold entity row):

I also have this graph:

Where space is a little cramped I use this:

[moskovskiy82]

Exactly what i wanted. Idea with the collapsible automations i what i was looking for! Thanks!
Really neat styling of the dashboard. Do you have a descriton of it somewhere?

[tom_l]

https://community.home-assistant.io/t/day-and-night/116232/31?u=tom_l

It has one minor issue at the moment, that only occurs if the window is open as sunset occurs and the theme is switched.

Card-mod card backgrounds do not update

[moskovskiy82]

@tom_l

For this one. Is it a vertical stack? Thermostat + two bar cards and then a foldable one?

[sparkydave (🇦🇺 Dave)]

I’m guessing stack-in-card

[tom_l]

It’s actually an entities card. Using this:

hui-element - Use built-in elements in the wrong place

Funny thing about lovelace - cards, rows in the entities card, badges and elements in the picture-elements card work exactly the same behind the scenes. That means that you can use them interchangeably if you know how, and e.g. put a button right in an entities card, a badge somewhere in the middle of your view or a markdown card (with background and border removed) right in your carefully crafted picture-elements card. Pretty neat stuff that allows for some fantastic creations. However. Becau…

entities:
  - type: custom:hui-element
    card_type: thermostat
    entity: climate.downstairs
    card_mod:
      class: inline-card-no-border
  - animation:
      state: 'off'
    columns: '1'
    direction: right
    entities:
      - entity: sensor.rumpus_room_temperature
        icon: mdi:thermometer
        max: '40'
        min: '-10'
        name: Temperature
        severity:
          - color: '#039BE5'
            from: '-10'
            to: '17.9'
          - color: '#0da035'
            from: '18'
            to: '22.9'
          - color: '#e0b400'
            from: '23'
            to: '24.9'
          - color: '#e45e65'
            from: '25'
            to: '40'
        target: '18'
      - entity: sensor.downstairs_heat_pump_power
        max: '4000'
        min: '0'
        name: Power
        severity:
          - color: '#039BE5'
            from: '0'
            to: '299.9'
          - color: '#0da035'
            from: '300'
            to: '899.9'
          - color: '#e0b400'
            from: '900'
            to: '1799.9'
          - color: '#e45e65'
            from: '1800'
            to: '4000'
    entity_row: true
    height: 28px
    positions:
      icon: inside
      indicator: inside
      minmax: 'off'
      name: inside
      title: 'off'
      value: inside
    type: custom:bar-card
    value_style:
      color: var(--primary-text-color)
      text-shadow: none
  - card_type: custom:fold-entity-row
    entities:
      - entity: automation.downstairs_aircon_am_schedule
        name: Enable AM Schedule
        type: custom:multiple-entity-row
        toggle: true
        state_color: true
        entities:
          - entity: input_datetime.downstairs_ac_am_on_time
            name: AM On
          - entity: input_datetime.downstairs_ac_am_off_time
            name: AM Off
      - entity: automation.downstairs_aircon_pm_schedule
        name: Enable PM Schedule
        type: custom:multiple-entity-row
        toggle: true
        state_color: true
        entities:
          - entity: input_datetime.downstairs_ac_pm_on_time
            name: PM On
          - entity: input_datetime.downstairs_ac_pm_off_time
            name: PM Off
      - entity: automation.downstairs_boost_on
        name: Boost
      - entity: input_boolean.downstairs_ac_workday
        state_color: true
      - entity: input_number.downstairs_ac_heat_temp_set
      - entity: input_number.downstairs_ac_cool_temp_set
      - entity: input_number.downstairs_ac_temp_set_heat
        name: AC Heat Set Temp
      - entity: input_number.downstairs_ac_temp_set_cool
        name: AC Cool Set Temp
      - entity: binary_sensor.downstairs_ac_am_automation_time_active
        state_color: true
      - entity: binary_sensor.downstairs_ac_pm_automation_time_active
        state_color: true
      - entity: binary_sensor.downstairs_ac_heat_required
        state_color: true
      - entity: binary_sensor.downstairs_ac_cool_required
        state_color: true
      - entity: sensor.downstairs_preset_mode
    head:
      label: Automation
      type: section
    padding: 0
    type: custom:hui-element
show_header_toggle: false
title: Downstairs
type: entities
card_mod:
  class: top-level-card

[moskovskiy82]

Thanks once again.
Using your ideas i came to a dream solution

Vertical stack per floor. Then use the entity:row plus folding
Only thing i am missing is how to remove that trv_bedroom_position line

This is the code i use

type: vertical-stack

cards:
  - type: entities
    title: 2ой Этаж
    icon: mdi:bed
    entities:
      - type: custom:fold-entity-row
        head:
          entity: climate.trv_bedroom
          type: custom:multiple-entity-row
          name: Спальня
          attribute: current_heating_setpoint
          unit: C
          secondary_info:
            name: В комнате
            entity: sensor.temp_kids_temperature
            unit: C
          entities:
            - sensor.trv_bedroom_position
              name: THIS BREAKS CONFIG


        entities:
          - input_number.temp_day_bed
          - input_number.temp_night_bed
          - sensor.trv_bedroom_position
          - climate.trv_bedroom

As soon as i insert the name: THIS BREAKS CONFIG

I get

bad indentation of a sequence entry (21:19)

18 | unit: C
19 | entities:
20 | - sensor.trv_bedroom_position
21 | name: THIS BREAKS CONFIG
------------------------^
22 |
23 |

[tom_l]

label: not name:

https://github.com/thomasloven/lovelace-fold-entity-row#usage

[moskovskiy82]

@moskovskiy82

custom:multiple-entity-row

Changed the one below for label. But actually name also works. The config in question which breaks is for custom:multiple-entity-row and not for the fold one

[tom_l]

Oh right. If you want to supply a name you have to declare the entity like this:

          entities:
            - entity: sensor.trv_bedroom_position
              name: THIS WONT BREAK THE CONFIG

This pretty much goes for all loveloace cards.

you can supply a simple list of entities:

entities:
  - sensor.something
  - switch.something
  - cover.something

But if you want to change the appearance of an entity you must do this:

entities:
  - sensor.something
  - entity: switch.something
    name: new name
    icon: mdi:whatever
  - cover.something