Casting to Nest Hub: Custom element doesn't exist: floorplan-card

[Puddingpanzer]

Hi, I set up my first floorplan and it works just fine in Browser and App. But when I try to cast the view via script on my Nest Hub it displays "Custom element doesn't exist: floorplan-card". How is this possible? Restarting HA and Nest Hub no difference. See the screenshot of my configuration. ha-floorplan installed via HACS. Other custom cards are working (i.e. webrtc camera)

Browser View:

Resource:

File path:

Cast Script:

Nest Hub error:

[OzGav]

Yes I see some threads about a bunch of cards with the same problem. We will take a look at it.

[OzGav]

Looks like there are a bunch of potential issues. One might be the floorplan code but you can try this first:

According to here: https://community.home-assistant.io/t/custom-components-and-home-assistant-cast-solved/216762 the issue might be that the resource URL is using /hacsfiles instead of /local/community I saw some talk that if you just add another entry that causes the resource to be loaded twice which slows things down. Up to you whether you want to do that or just change your existing entry.

According to here https://community.home-assistant.io/t/home-assistant-cast-with-custom-cards/137457/14 you might need to add an entry to the http: section of your configuration.yaml For example:

http:
  cors_allowed_origins:
    - https://cast.home-assistant.io/

Try those two things and see if you can get it to work or at least improve and if not then it might be a coding issue in ha-floorplan

[Puddingpanzer]

Thank you, changing the resource URL brings me one step further. But now i got a black screen and error regarding the .css. The error doesn't occur in Browser View. Adding entries to cors_allowed_origins doenst affect anything.

[OzGav]

Ok glad we have some progress. For any code changes hopefully @exetico will be able to have a look at the LitElement comments from here https://community.home-assistant.io/t/home-assistant-cast-with-custom-cards/137457/14

[OzGav]

Yes OK your first example is the normal way of doing things. Will wait and see what @exetico has to say about whether this is something we can fix or whether we will just add to the docs that if you want to use the cast functionality then you will need to add the full path as you have.

[Puddingpanzer]

Okay, if it helps: i'm using Home Assistant Core installed on a Synology NAS.

[exetico]

Are you able to open your HA instance on your external domain? 🤔 And are every floorplan related thing, working as expected?

[Puddingpanzer]

Yes i'm only working via my external URL on HA. The floorplan is working very well in Browser and App View.

[exetico]

Have you tried with both hacsfiles, local/community and local from the Nest Hub? Also, tried the same paths outside your own network, and validated that it's working as expected?

The screen is clearly stating that it's related to the fetch, so I can't really see why this should be a problem with Home Assistant.

If you're proxying anything; Try and see if you're able to see what kind of resources your Nest Hub are fetching for... And if the requests looks as expected.

Without the Next Hub, I can't really do anything else - I'm sorry.... I've also tried to see if it's possible to emulate the Nest Hub, but there sadly nothing like a 1:1 version of it...

[DominicWindisch]

Did you ever solve this? Facing the same problem at the moment