Config error on Camera card

For some reason I am getting this:

Configuration Error on my HA page… I’ve changed nothing and after looking at it I cannot figure out why it’s not working… any suggestions or ideas?

Thank you!

- type: custom:advanced-camera-card
  cameras:
      - camera_entity: camera.backdoor
      - camera_entity: camera.livingroom_camera
      - camera_entity: camera.deck_road
      - camera_entity: camera.porch_backyard
      - camera_entity: camera.backdoor_yard
      - camera_entity: camera.front_upper
      - camera_entity: camera.shed_camera
      - camera_entity: camera.livingroom
  live:
    display:
       mode: grid
  display:
     mode: single
     grid_selected_position: default
     grid_selected_width_factor: 2
     grid_max_columns: 4

I guess you see only a very helpful “configuration error” message instead of the error itself since recent changes.
Suggest to reduce the card to the minimum to get a working result, then increase a complexity step by step.

Note that this is a custom card which may be used by many people. Means - you may not get a quick answer.

Btw, are you using a yaml or a storage mode of a dashboard?
If a storage (with UI editor) - then did you take this code from the UI editor? Asking because your code starts with “-“.

2 Likes

Looks like lots of indentation issues to me.

try something like this

type: custom:advanced-camera-card
cameras:
  - camera_entity: camera.backdoor
  - camera_entity: camera.livingroom_camera
  - camera_entity: camera.deck_road
  - camera_entity: camera.porch_backyard
  - camera_entity: camera.backdoor_yard
  - camera_entity: camera.front_upper
  - camera_entity: camera.shed_camera
  - camera_entity: camera.livingroom
live:
  display:
    mode: grid
display:
  mode: single
  grid_selected_position: default
  grid_selected_width_factor: 2
  grid_max_columns: 4

It does not matter here. You may put as many indents to a block as you like.

Thank you for your idea but it was working and I’ve made no changes to any of this… so a bit confused.

I am using yaml mode. Just so strange that it was working and now suddenly without changing anything it just throws that error…

Can you say “Curve ball” LOL

No idea) note that this community is international so idioms may be at least not clear for many people.

Then try pasting the code into UI editor and play…. May be you will even see an error itself there.

I’ve taken it down to just the basics and still getting error…

- type: custom:advanced-camera-card
        cameras:
          - camera_entity: camera.backdoor
          - camera_entity: camera.livingroom_camera
          - camera_entity: camera.deck_road
          - camera_entity: camera.porch_backyard
          - camera_entity: camera.backdoor_yard
          - camera_entity: camera.front_upper
          - camera_entity: camera.shed_camera
          - camera_entity: camera.livingroom

Possibly the error says “card not found”

Hi,

I tested your code on my dashboard. It works, no errors. Maybe check more upstream?

Used:

type: custom:advanced-camera-card
cameras:
  - camera_entity: camera.camera_front
  - camera_entity: camera.camera_car
  - camera_entity: camera.camera_baby
live:
  display:
    mode: grid
display:
  mode: single
  grid_selected_position: default
  grid_selected_width_factor: 2
  grid_max_columns: 4

1 Like

Found this in the error logs…

Logger: frontend.js.modern.202507021
Source: components/system_log/init.py:331
First occurred: July 4, 2025 at 6:33:32 PM (98 occurrences)
Last logged: 9:07:42 AM

  • Uncaught error from Chrome WebView 137.0.7151.116 on Android 15 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109) /hacsfiles/frigate-hass-card/card-f2dccb12.js:75:3686
  • Uncaught error from Chrome WebView 137.0.7151.116 on Android 15 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109) /hacsfiles/advanced-camera-card/card-855fd26e.js:75:3686
  • Uncaught error from Chrome 138.0.0.0 on Windows 10 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109) /hacsfiles/frigate-hass-card/card-f2dccb12.js:75:3686
  • Uncaught error from Chrome 138.0.0.0 on Windows 10 TypeError: Cannot set properties of undefined (setting ‘moment’) /local/moment.js:10:19 /local/moment.js:11:2
  • Uncaught error from Chrome 138.0.0.0 on Windows 10 Error: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “focus-trap” has already been used with this registry A.define (src/scoped-custom-element-registry.ts:180:12) a.define (/hacsfiles/tabbed-card/tabbed-card.js:63:109) /hacsfiles/advanced-camera-card/card-855fd26e.js:75:3686

Delete browser cache en history?

I’m going to give that a try!! Because for one brief second it started working again… then stopped again.

1 Like

Well I’ve cleared my browser and used a different browser and took the config to the very basic… I’m at a loss…

So strange it just stops working without making any changes to it…

Try a complete new Dashboard and add a manual card

1 Like

Thank you, I’ll give that a try!

Well that’s too bad it works like that… so apparently I need to figure out the config because well it’s not correct for some reason. Thank you for the tip!

1 Like

So here’s the stranger thing… it works on the mobile HA app no problem…
Just can’t see on HA Dashboard no matter what browser I use…

So I’m truly at a loss.

Having the same issue. First it was only happening on my desktop after a core update. iOS mobile app was fine. So I restored a backup. everything is ok now on the desktop but not my iOS mobile app. Same issue if I try to access it on a mobile browser.

It doesnt seem to be connected to the update either because I tried updating to fix the mobile issue and nothing changed.

Did they break some cards?

Hi,

I think the problem is more upstream in your dashboard configuration.

As far as I understand is the below working

Rebuild your dashboard and test