0.110 Lovelace Cannot read property 'states' of undefined

I did an upgrade to 110 and now my lovelace it is a great red page with this message: Cannot read property ‘states’ of undefined.
image

Any idea where can I start to troubleshoot this?
Log is full of this:
[homeassistant.components.camera] The websocket command 'camera_thumbnail' has been deprecated.
Nothing else peculiar.

i have the same error with my picture elements cards
was working perfectly on older releases

Yes, in my case my entire lovelace it is a big picture-element. OK, so the problem is there.
I added a new lovelace and then I added a picture element from the UI. All went fine. So there is something with the ones customized. I will test more and return.

Cannot read property 'states' of undefined
    at Array.forEach (<anonymous>)
    at ha-state-label-badge.ts:24
    at Array.map (<anonymous>)
    at HTMLElement.value (ha-state-label-badge.ts:24)

I have the same problem. My lovelace-ui.yaml has quite a big configuration (18k6 lines…) consisting of 3 views. The big red “card” lists up the configuration for the complete first card.

Are you use: now-playing-poster? I disable it and now its ok

Can you post the entire card please instead of screenshots?

its fixed, seems related to this custom :

- type: custom:circle-sensor-card

1 Like

I think several card’s are affected. I am using a lot in my configuration.
How did you fixed? I am not using Circle-sensor-card but maybe I can take the same approach.

well, i removed the circle-sensor-card from the picture elemens, replaced by a supported one
now using state-label

you need to figure out what custom element isnt supported yet

Reported as not working (removing them fixed it):

- custom:now-playing-poster
- custom:custom-attribute-card
- custom:circle-sensor-card
- custom:mini-graph
- custom:battery-entity
- custom:big-number
- custom:simple-weather-card

Unsure (suspects):

- custom:gauge-card
- custom:thermostat-card
- custom:mini-media-player
- custom:state-attribute-element

Confirmed working in 0.110:

- custom:button-card
- custom:text-element
- custom-header (fixed)
1 Like

Yes, I am using also some of the ones you mentioned. I would add also mini-graph to your list.
But the question is, how do we still use them? Where is the problem? Should we contact the developer of each card or is there something wrong in this release and wait for 110.x?
I notice that some of them were already updated. e.g Custom Header. This was also bugging my configuration.

same problem around here, back to version 109.6

@pergola.fabio Which one did you then use ?

I replaced by a state-label card

I used the circle card to indicate fuel amount and fuel range, would like to find something similar, any suggestions to what to use rather than the circle-card ?

yeah, use state-label card …

i also used circle-card for my fuel and range, replaced with state-label
do you use the audi mmi integration by any chance? there is an example in the thread there

No, I use the BMW Connected… But for now I’ll adapt to the example you provided :slight_smile: Nice example, thx bud!

Tap action of ‘Service’:

2 Likes

Fin bil :slight_smile:
I have a 530d, unfortunately too old to be ‘connected’.

Anyway, think I’ll wait for the custom cards to be updated before trying to upgrade again. Too much work have gone into the yaml.