Skip to content

Custom element doesn't exist: hui-conditional-card. #78

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

Closed
veloc1ty opened this issue Mar 19, 2020 · 14 comments
Closed

Custom element doesn't exist: hui-conditional-card. #78

veloc1ty opened this issue Mar 19, 2020 · 14 comments
Labels
duplicate This issue or pull request already exists

Comments

@veloc1ty
Copy link

Hi,

there seems to be a small problem with the vertical-stack-in-card after upgrading to 107. The frontend throws an error "Custom element doesn't exist: hui-conditional-card. when using a "type: conditional" inside the custom:vertical-stack-in-card.

This does not happen when using the "normal" vertical-stack. The YAML for the section is fine, there is no hui-conditional-* referenced anywhere.

@Ernst79
Copy link

Ernst79 commented Mar 19, 2020

Had the same, but after a few refreshes and reloading the front panel it started to work again.

@realk1ko
Copy link

I've noticed the same behaviour with map cards.

Taking a wild guess, this might be the same issue as seen here: thomasloven/lovelace-fold-entity-row#91

@wbilger
Copy link

wbilger commented Mar 20, 2020

I am experiencing the same problem, but I have noticed that the page will load correctly if I start at another page first, and then navigate to the problem page. But if I reload the problem page, then you see the issue.
For me it seems to be when there is multiple picture-elements card inside a vertical-stack-in-card as I have 2 pages that act like that. I have one that does not, and it only has one picture-element card inside the vertical stack, this page works fine. Not sure if that is the issue or not, but seems to be for me. For now I will go back to 106.6 and keep an eye on this and test again later.

@SeLLeRoNe
Copy link

Same as this: #75

Please also note, using the card-preloader (https://community.home-assistant.io/t/lovelace-card-preloader/176655) help you with the issue, of course it is not a fix but it's better than nothing for now :)

@RomRider
Copy link
Contributor

@ofekashery, I can PR something to fix this issue but I had a more broad question: Are you still maintaining this card? Else I'd be happy to take over if we move it back to the custom-cards organisation.
Let me know what you think :)

@Poeschl
Copy link

Poeschl commented Mar 20, 2020

More information about this bug from the HA repository: home-assistant/frontend#4984

@aheath70
Copy link

aheath70 commented Mar 20, 2020

I have the same issue here. I use the vertical stack in card quite a lot, and it throws various errors for various cards nested within it.
Custom element doesn't exist: hui-conditional-card.
Custom element doesn't exist: hui-pciture-entity-card.

etc.

@RomRider
Copy link
Contributor

I've created a new card which is almost a drop-in replacement for vertical-stack-in-card and a bunch of other features:
https://community.home-assistant.io/t/stack-in-card-drop-in-replacement-for-vertical-stack-in-card/180072

@ofekashery
Copy link
Owner

@RomRider, I'm trying to still maintain it, mainly with PRs from the community, because I no longer use Home Assistant 😔.
The stack-in-card looks awesome, and I'd like to merge this card with your card.

@SeLLeRoNe
Copy link

Out of curiosity, what did you switch to? :)

@RomRider
Copy link
Contributor

@ofekashery, stack-in-card is a complete rewrite in typescript. How do you see a merge?

@ofekashery
Copy link
Owner

@RomRider I mean, to release it as a new version of the card, and not as a separate card.

@SeLLeRoNe I built a whole system myself.

@RomRider
Copy link
Contributor

In this case, you should move the repository to the custom-cards org, and give me rights on the repository. I'll rename it to stack in card and replace the code with the new one (and delete my repo)

@ofekashery
Copy link
Owner

Fixed in version 0.3.0, thanks!

@ofekashery ofekashery added the duplicate This issue or pull request already exists label Mar 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

9 participants