Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024.02.01 - Custom element doesn't exist: grid-layout #273

Open
4 tasks done
rloo1 opened this issue Feb 12, 2024 · 1 comment
Open
4 tasks done

2024.02.01 - Custom element doesn't exist: grid-layout #273

rloo1 opened this issue Feb 12, 2024 · 1 comment

Comments

@rloo1
Copy link

rloo1 commented Feb 12, 2024

My Home Assistant version: 2024.02.1

Layout-card version (FROM BROWSER CONSOLE):

What I am doing: Fresh install of Home Assistant, tried to install layout-card

What I expected to happen: Dashboard functionality

What happened instead: Error message "Custom element doesn't exist: grid-layout" and nothing works. Seems similar to issue #258

Minimal steps to reproduce:

# The least ammount of code possible to reproduce my error

# End of code

Error messages from the browser console: "Custom element doesn't exist: grid-layout"


By putting an X in the boxes ([X]) below, I indicate that I:

  • Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
  • Have made sure I am using the latest version of the plugin.
  • Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
  • Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
@pascal-mignot-urca
Copy link

Same problem here: new install in docker, new version of everything.

The layout card is completely broken due to a resource path problem:
Configuration in resources.yaml:

  • url: /community_plugin/lovelace-layout-card/layout-card.js
    type: module
    When consulting the Settings/Dashboards/Resources, this path is automagically changed to:
    /community_plugin/lovelace-layout-card/layout-card.js
    Result (chrome trace):
    load_resource.ts:13 Uncaught (in promise) http://192.168.1.3:8123/community_plugin/lovelace-layout-card/layout-card.js
    r.onerror @ load_resource.ts:13

Adding /community_plugin to the docker volumes and copying lovelace_layout inside changes nothing.
Cleaning cache/restarting HA, restarting the docker container changes nothing.

The problem appears when switching from storage mode to yaml mode.
hacs added: button-card, decluttering-card, kiosk-mode, swiss-army-knife-card

configuration.yaml (extract):
lovelace:
mode: yaml
resources: !include lovelace/resources/resources.yaml

resources.yaml (extract):

  • url: /hacsfiles/button-card/button-card.js
    type: module
  • url: /hacsfiles/decluttering-card/decluttering-card.js
    type: module
  • url: /hacsfiles/kiosk-mode/kiosk-mode.js
    type: module
  • url: /community_plugin/lovelace-layout-card/layout-card.js
    type: module
  • url: /hacsfiles/swiss-army-knife-card/swiss-army-knife-card.js
    type: module

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants