'Custom element doesn't exist' error only when casting view. Who do I file a bug report with?

So I have an issue when casting to my Google hub that custom components (button-card in my case) comes up with an error that the ‘custom element doesn’t exist’. I found this old thread on the issue:

One of the suggestions was removing the HACS entry from Resources and creating a new one pointing to /local/. That seemed to work most of the time, but has completely stopped working now.

This lovelace view works fine on everything but casting. I’m not sure who to file a bug report with though. I don’t think its related to the component itself, as it apparently happens with a lot. It seems HACS can screw it up by gzipping, so maybe there? My real guess is core, but what do you guys think?

If anyone else sees this issue, I’ve created a Github issue for it.

1 Like