0.110 Lovelace Cannot read property 'states' of undefined

Configuration
21

Thanks for this, very helpful in hunting down these issues

BTW, I have text-element working fine. However, you can add big-number to the not working list.

22

Takk Ole :slight_smile:

23

@pergola.fabio Can you please post your not working code, the one that was visible in the picture? Maybe Petro can take a look? 10x
Mine’s is quite big to post it here.

Did anyone managed to solved this? I have upgraded some of the cards but the issue is still there.

24

The issue was solved by updating the custom:circle-sensor-card according to him.

25

Well, the issue is not solved, he just replaced with something else.
But in my case I do not have alternatives.

@olealm add this to the list: simple-weather-card

26

For example, I have this(see bellow), if I use it stand alone this is working fine, but as soon as I add it to a picture element card with several elements, will ruin my entire card.

type: 'custom:simple-weather-card'
backdrop: false
entity: weather.dark_sky
name: ' '
style: |
  :host {
    left: 25%;
    top:  80%;
  }
  ha-card {
    background: none  !important;
    box-shadow: none !important;
    flex-flow: row-reverse !important;
    padding: 0 !important;
  }
  .weather__info--add{
    display : none !important;
  }
  .weather__info{
    flex-grow: 1;
    min-height: 0 !important;
    height: 2.4vw;
    margin-left: 0.6vw;
  }
  .weather__icon{
    margin-right:0.5% !important;
    margin-top: -1%;
    width: 2vw !important;
    height: 2vw !important;
    flex: 0 0 2vw !important;
  }
**strong text**
27

You can’t style elements inside picture elements with card mod. You have to put the style for elements on the picture element card and use a selector to get to the object element you want to style. This has always been the case.

28

OK, thank you for the hint. I will try that as well.

29

OK, I did what you suggested and it does not work. :frowning_face:
I tend to believe that is not the issue because it applies only to some of them. If it would be like you said than it would be the case for all of them, no?
And then I raise the question, why now? What changed in picture element card?

(Sorry if I insist on this but, I have worked on it 3 weeks before the update. I enjoy it for two days and now it’s gone.)

30

It’s always been the case.

picture elements card has a built in style field that is required. Card mod overrides it. The style field is required for positioning. Unless I’m mistaken, the only option is place the card-mod modifications on the elements card.

something like this

type: picture-elements
style: 
  card-mod-styles using selectors
elements:
- type: custom:simple-weather-card
  etc...
  style:
    left: 25%
    top: 80%

The problem is, you’ll have to use the correct selector(s) and bypass the shadow root elements using $:

EDIT: There’s an advanced usage section now that helps you through this process

using

debug_cardmod: true

will help.

31

Ok, I think I am lost. I don’t think it is related to styles.
I have this, can you explain on this?
This is the most basic configuration I can think off. It reproduces the error. There is no styling on it.
I still believe there is an error with the picture-elements card.

type: picture-elements
elements:
  - type: state-badge
    entity: sensor.washing_machine_status
  - entity: weather.dark_sky
    name: test weather
    type: 'custom:simple-weather-card'
image: 'https://demo.home-assistant.io/stub_config/floorplan.png'

image

32

And if you remove ‘custom:simple-weather-card’?

33

If I remove the weather card it works. But in my case I need the weather card. It is part of what I want in Lovelace. If I add the weather card by it self it works as well.
Only when I combine the weather card and picture-element I have the mentioned issue.

34

Update the card. If the update doesn’t work (or you are up to date), write up an issue against the card.

Unfortunately, this is part of the drawback with custom cards. If something changes in lovelace and the custom card doesn’t adapt, you get errors.

35

I was having the same problem, version 0.110.2 fixed it. Now all the custom components are shown properly.
This error still happens quite often on cast devices, when triggered in Hass using the service, but this is another issue.

36

I had open a bug on mini-graph and the developer said that this will be fixed in the core in the next release. I just started the upgrade, let’s see. :smile:

37

Yes, they are all back. So, yes I confirm 110.2 fixed. 10x @all

38

Yupp, all my ‘customs’ works in 110.2 too.