Frigate Card Not Found error on some devices

Checklist:

• I updated to the latest version available
• I cleared the cache of my browser Yes Release with the issue:

Last working release (if known): I believe it still worked with V3.0 RC1 Browser and Operating System: Chrome on WIndows 11

Description of problem: When frigate detects an object, I display the camera feed on a Google Nest Home device. The following is my lovelace card config:

  - type: "custom:frigate-card"
    cameras:
     - camera_name: sideyard
        title: Front Yard
        live_provider: frigate-jsmpeg

I would like to use webrtc, but this has not worked for awhile. Since then I switched to frigate-jsmpeg which only lagged webrtc by a couple seconds and has been working for a couple months now. Since I updated to the latest release, however, I now get an error on the Google Display saying “Custom Element doesn’t exist: frigate-card”. The files exist in the correct directories, so not sure what is going on. The view displays correctly in a browser.

Javascript errors shown in the web inspector (if applicable):

Additional information:

[iMarvinS]

I have encountered the same problem on a iPad Mini 2 running iOS 12.5.
Version 4.0.0 of the card doesn’t seem to be loaded properly. On the device it says “Custom Element doesn’t exist: frigate-card”.

The following output can be seen in the Web Inspector:

[dermotduffy]

Assuming you are not using a version of the card you built yourself, just wait for v4 (very soon I hope!) and try then. I consider this issue resolved in the code (so no extra debug info is necessary), just not yet released in a public build.