Thermostat Card and History History Graph Card

I am setting up a new Hass.io on my raspberry pi, and after adding the Thermostat Card, I wanted also to add a History Graph Card. But can’t get it to work. Just get a red square beginning with ’ Entities need to be an array’
Any idea how to get a history graph on lovelace of my room temperatur?

type: history-graph
title: 'My Graph'
entities:
  - entity: climate.tstat_38730f
    name: Main player

Thank you, this worked great! :wink:

Hi,
I am probably doing a silly mistake, but I can’t figure out what it is.
I want to setup a simple history card for my temperature sensors with this code im my configuration.yaml:

type: history-graph
title: 'temperatures'
entities:
  - sensor.temperature_158d0002329070
  - sensor.temperature_158d0002391abc
  - sensor.temperature_158d00053efe36
  - sensor.temperature_158d0005426ba0
  - sensor.temperature_158d0005426bd3

After reboot I get this error message:

Invalid config
The following integrations and platforms could not be set up:

  • entities
  • title
  • type
    Please check your config.

What am I doing wrong? I took the example from the “hass.io manual” History graph card - Home Assistant

Thanks for your help!

edit: atm my hass.io dashboard is fully automatic and created per default from hass.io… is that the problem? Is there a way to just add cards to the automatically created dashboard?

You missed the “entity:” part:

type: history-graph
title: 'temperatures'
entities:
  - entity: sensor.temperature_158d0002329070
1 Like

Thanks for the help. I changed it to his:

type: history-graph
title: 'temperatures'
entities:
  - entity: sensor.temperature_158d0002329070
  - entity: sensor.temperature_158d0002391abc
  - entity: sensor.temperature_158d00053efe36
  - entity: sensor.temperature_158d0005426ba0
  - entity: sensor.temperature_158d0005426bd3

Unfortunately it did not change anything and the error remains the same and no card is showing up.

I noticed you mentioned you put it in configuration.yaml, I was assuming this was wrong and you put it in ui-lovelace.yaml if you’re using lovelace in yaml mode. You can’t paste that code into configuration.yaml as its not for the backend, its for the lovelace frontend or GUI if you wish.

To change things on the frontend like adding cards etc you need to either do it with lovelace yaml mode or edit the card in lovelace by clicking the 3 dots in the top right hand corner of the GUI and then edit a card or add a card. Once you have the card view up then you need to click edit and show code view. If you paste that code in above it should work.

1 Like

Thank you very much for the quick response and the info! I saw that option but until now I am using the automated lovelace interface. If click the three dots and click on edit the notification says that the automated interface will then be switched of. Are all the cards I see no are then gone?

Is this avoided if I put the code in the ui-lovelace.yaml?

Sorry I can’t help with that, I’ve always used it without automated. If you switch to manual you can still see all the unused entities then click to add them. Depending on how many you have it could take a while though.

If you want to customise stuff on Lovelace then you have no choice but to turn off automated interface afaik.

Have a look at the Lovelace info on the wiki and it might give you a better idea.

1 Like

Thank you very much again for your answer.
I went ahead switched on the “manual” mode. All cards stayed where they are and I can edit them as I please. The code shown above worked directly after I added it in the interface with the raw-editor.

image

Just as I wanted. so thank you very much!

1 Like

Excellent, I’ve learnt something new too then!

You don’t have to use raw editor to add a card manually. If you press the + icon when editing the page you can scroll to the bottom and add manual card.

1 Like