JSMPEG Not working for cameras or birdseye

Checklist:

• I updated to the latest version available
• I cleared the cache of my browser

Release with the issue:

• Card: 1.2
• Integration: 2.1
• Frigate: 0.9.1

Browser and Operating System:

• HA OS
• Windows 10 / Edge 94
• Same issue on Windows 10 / Firefox
• Same issue on HA Android

Description of problem: I want to use the JSMPEG view for birdseye but it does not work with birdseye or any other camera. As soon as I use live_provider: frigate-jsmpeg I get errors:

WebSocket connection to 'ws://homeassistant.local:8123/api/frigate/frigate/jsmpeg/birdseye?authSig=XXXXXXXXXXXXXXXXXXXXXXXXXXX' failed: 
e.start @ frigate-hass-card.js?hacstag=394082552120:430
(anonymous) @ frigate-hass-card.js?hacstag=394082552120:430

In Firefox, it says 404 Not Found.

Similar to this comment but since I don’t have the authentication error and it’s not working at all, I am not sure this is related.

Both following WS URLs are working when I use frigate from Lovelace or using direct URL: ws://homeassistant.local:8123/api/hassio_ingress/TGDdpxY_QFN2xTs_EJoGujLeQzU3QLOV1E_MfCYCa6E/live/birdseye ws://10.0.0.9:5000/live/birdseye

Birdseye is working great from Frigate.

I also tried with a camera which work great with the default live_provider but same issue with jpmpeg. I tried with and without the frigate_camera_name, and with and without spaces, in lower or came case… I don’t think it could be related to the name anyway since it should work with birdseye.

The most basic configuration is the following:

type: custom:frigate-card
frigate_camera_name: birdseye
live_provider: frigate-jsmpeg

[dermotduffy]

Oh no! Happens to everyone @Mincka , very glad you figured it out. Thank you so much for the coffee!

[Mincka]

client_id and topic_prefix are not configured.