-
Notifications
You must be signed in to change notification settings - Fork 9
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
Custom element doesn't exist: check-button-card. #18
Comments
I am also getting this message, but with 0.114.4 and CBC card version 1.2.0 but I am using YAML mode and I'm not using layout card on this particular page. Typically, when adding any custom card I have added the resource for it in YAML, then run a reload resource and double checked if it was in the UI resources panel. Not finding any references to resources in any of the instructions, forum threads or issues, I have tried adding it as:
and
neither of which seems to work. Could this be related? I'm not seeing anything that appears to be related in the logs. I checked the Chrome console log and found this, if it helps: I've only added this card today, so for me it has never run correctly yet. Also, I have a working MQTT setup with discovery enabled and I'm using the proper discovery_prefix for my setup. |
And just like that... it's working. I changed from back from type: js to type: module but that's the only change I made. I'd tried module first and it didn't work so I'm not sure what happened. |
It's still not working for me. |
seems like same issue like #17 - maybe same solution applies? |
HASS Version: 0.114.4
Check Button Card Version: 1.2.0
I've been using check button card for a long time now but in the last couple of days it stopped working and now I just get red boxes with "Custom element doesn't exist: check-button-card." wherever the checkboxes should be displayed.
I'm using layout-card for my ui-lovelace cards and recall another HACS addon having similar issues in the past. I can't remember which one it was or what the fix was but do remember it was related to the addon entity needing a slight code change.
The text was updated successfully, but these errors were encountered: