Custom element doesn't exist: webrtc-camera

[Dim3333]

Hello,

Home Assistant 2022.2.6
Same issue that anothers posts : Custom element doesn't exist: webrtc-camera but I don't find the solution.

The integration seems to be well installed.

Could you help me ?

Thanks

[Botond24]

You need to also add the WebRTC integration to home-assistant via the Integrations page.

[Dim3333]

I'm stupid, ..... I forgot to do that ... now the card appears but connection refused

Same issue with VLC, snapshot is OK but rtsp is down. I use this link :
rtsp://username:password@myip/av_stream/ch0

[Dim3333]

I changed the rtsp port to 254 and it's works.

[alexvenom]

I'm running into this same problem: "Custom element doesn't exist: webrtc-camera".

• WebRTC installed correctly via HACS
• WebRTC Camera installed via Configuration -> Integrations

Any thoughts?

[slash133]

I have the same problem since my update on homeassistant, my integration is not loaded and i don t understand for why

if you have ideas ?
thks

[fedemartino]

same problem on version: 2022.3.0

any ideas?

[BabaBoch1]

I am having the same issue when trying to setup a lovelace tile for eufy camera.

[lolfonfire]

I've been using this integration for some weeks now.
Setup was easy but it's not stable. I'm not sure if this is due to Home Assistant updates or the integration itself.
Yesterday I've updated Home Assistant to core-2022.3.3. After the Home Assistant update none of my cameras were visible in Lovelace. Error: Custom element doesn't exist: webrtc-camera

As shown in the following screenshot the integration is added/loaded. Sometimes when I press F5 the error is gone and cameras are visible.
Last week I had a similar issue in the HA Companion app on Android. I needed to sign-out the HA app and sign-in again. Then the "Custom element doesn't exist: webrtc-camera" error was gone. This was before the update to core-2022.3.3.

After pressing F5 a few more times it sometimes shows this:

[BabaBoch1]

I've been using this integration for some weeks now. Setup was easy but it's not stable. I'm not sure if this is due to Home Assistant updates or the integration itself. Yesterday I've updated Home Assistant to core-2022.3.3. After the Home Assistant update none of my cameras were visible in Lovelace. Error: Custom element doesn't exist: webrtc-camera

As shown in the following screenshot the integration is added/loaded. Sometimes when I press F5 the error is gone and cameras are visible. Last week I had a similar issue in the HA Companion app on Android. I needed to sign-out the HA app and sign-in again. Then the "Custom element doesn't exist: webrtc-camera" error was gone. This was before the update to core-2022.3.3.

After pressing F5 a few more times it sometimes shows this:

Same problem here. I gave up on this and deleted it all today.

[Dim3333]

Hi,

None issues from my side with the last version of HA.

[wowgamr]

Same error for me after update to 2022.3.3.

[MagellanOo]

Same issue for me after performing the update to 2022.3.4.

[wowgamr]

In my case the problem resolved itself. Camera is working again. Didn't update or reboot anything. Magic!

[jaegerschnitzel]

I ca

I've been using this integration for some weeks now. Setup was easy but it's not stable. I'm not sure if this is due to Home Assistant updates or the integration itself. Yesterday I've updated Home Assistant to core-2022.3.3. After the Home Assistant update none of my cameras were visible in Lovelace. Error: Custom element doesn't exist: webrtc-camera

As shown in the following screenshot the integration is added/loaded. Sometimes when I press F5 the error is gone and cameras are visible. Last week I had a similar issue in the HA Companion app on Android. I needed to sign-out the HA app and sign-in again. Then the "Custom element doesn't exist: webrtc-camera" error was gone. This was before the update to core-2022.3.3.

After pressing F5 a few more times it sometimes shows this:

Same for me.

[Mark612]

Using 'master', with the latest home assistant, sometimes it works. Sometimes it does not. Refresh and restarting sometimes helps.