WebRTC icon indicating copy to clipboard operation
WebRTC copied to clipboard

Custom element doesn't exist: webrtc-camera

Open Dim3333 opened this issue 4 years ago • 89 comments

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

Dim3333 avatar Feb 14 '22 18:02 Dim3333

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

Botond24 avatar Feb 14 '22 20:02 Botond24

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

image

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

Dim3333 avatar Feb 14 '22 22:02 Dim3333

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

Dim3333 avatar Feb 15 '22 09:02 Dim3333

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?

alexvenom avatar Feb 18 '22 17:02 alexvenom

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

if you have ideas ? thks

slash133 avatar Feb 20 '22 08:02 slash133

same problem on version: 2022.3.0 image

any ideas?

fedemartino avatar Mar 08 '22 02:03 fedemartino

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

BabaBoch1 avatar Mar 08 '22 22:03 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. image

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

lolfonfire avatar Mar 11 '22 17:03 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. image

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

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

BabaBoch1 avatar Mar 11 '22 17:03 BabaBoch1

Hi,

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

Dim3333 avatar Mar 12 '22 09:03 Dim3333

Same error for me after update to 2022.3.3.

wowgamr avatar Mar 13 '22 07:03 wowgamr

Same issue for me after performing the update to 2022.3.4.

MagellanOo avatar Mar 13 '22 20:03 MagellanOo

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

wowgamr avatar Mar 14 '22 11:03 wowgamr

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. image

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

Same for me.

jaegerschnitzel avatar Mar 15 '22 23:03 jaegerschnitzel

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

Mark612 avatar Mar 17 '22 20:03 Mark612

Yeah if i hit F5 like 5-6 times then suddenly it works. Then I close the webinterface/app when I open it again it's broken. Again hitting F5 and it works ...

lolfonfire avatar Mar 18 '22 08:03 lolfonfire

same issue here. In my Raspi based HA container doesnt work, on my NUC based HA container it works. 2022.3.4 version on both

WebRTC Camera "Not Loaded" on the integrations page

fgonza2 avatar Mar 18 '22 19:03 fgonza2

Chipping in to say I've got the same issue. "Not Loaded"

mortenmoulder avatar Mar 21 '22 09:03 mortenmoulder

Same issue here. It's a strange one, because it seems to be random - sometimes it loads the card, sometimes it can't. More often it can't.

mishoboss avatar Mar 22 '22 07:03 mishoboss

Anything we can do to help diagnose this? maybe there is a way to debug the error and help find the cause?

fedemartino avatar Mar 22 '22 13:03 fedemartino

Hi folks.

It looks like Home Assistant and GitHub are pointing to 2.1.0, instead of the latest version 2.2.0. This could be due to the way the author managed the release for the very last one (as it doesn't even show up in the releases list). If you have 2.1.0, you may be encountering this issue. I would recommend uninstalling that version and manually installing version 2.2.0 available here (https://github.com/AlexxIT/WebRTC/releases/tag/v2.2.0).

Once I did this, it started to work.

MercerK avatar Mar 25 '22 01:03 MercerK

Hi folks.

It looks like Home Assistant and GitHub are pointing to 2.1.0, instead of the latest version 2.2.0. This could be due to the way the author managed the release for the very last one (as it doesn't even show up in the releases list). If you have 2.1.0, you may be encountering this issue. I would recommend uninstalling that version and manually installing version 2.2.0 available here (https://github.com/AlexxIT/WebRTC/releases/tag/v2.2.0).

Once I did this, it started to work.

I can confirm that this FIXES the issue. Had to do manual install to 2.20 and it works! so the bug is on HACS installation

fgonza2 avatar Mar 25 '22 07:03 fgonza2

Hi folks. It looks like Home Assistant and GitHub are pointing to 2.1.0, instead of the latest version 2.2.0. This could be due to the way the author managed the release for the very last one (as it doesn't even show up in the releases list). If you have 2.1.0, you may be encountering this issue. I would recommend uninstalling that version and manually installing version 2.2.0 available here (https://github.com/AlexxIT/WebRTC/releases/tag/v2.2.0). Once I did this, it started to work.

I can confirm that this FIXES the issue. Had to do manual install to 2.20 and it works! so the bug is on HACS installation

This solved it! thanks!

fedemartino avatar Mar 25 '22 23:03 fedemartino

Once I did this, it started to work.

Yes, this helps for web browsers. However, is it working for your mobile companion application? It is still problematic for me.

Mark612 avatar Mar 27 '22 02:03 Mark612

here the problem is only on android app.... webrtc doesn´t exist...... on my PC with chrome is ok !! "Solution": remove de WiFi SSDI and Internal URL on android app.... using only external URL is fine now !!

I´m using 2.2.0 webrtc without hacs

homeoneautomacao avatar Mar 28 '22 16:03 homeoneautomacao

Once I did this, it started to work.

Yes, this helps for web browsers. However, is it working for your mobile companion application? It is still problematic for me.

Same issue here. Browser working ok, not on Android up though... A bit disappointed.

georaspi avatar Apr 03 '22 10:04 georaspi

Once I did this, it started to work.

Yes, this helps for web browsers. However, is it working for your mobile companion application? It is still problematic for me.

Same issue here. Browser working ok, not on Android up though... A bit disappointed.

Same for me

maximatchev avatar Apr 03 '22 19:04 maximatchev

GitHub recently had a bug. That's where the latest release got lost (2.2.0).

You need:

  • install it manually or
  • install latest master version via HACS or
  • wait next release

AlexxIT avatar Apr 10 '22 13:04 AlexxIT

Lovelace card still broken on v2.3.0 (in mobile app)

wowgamr avatar Apr 11 '22 12:04 wowgamr

@wowgamr what mobile OS do you use? What lovelace mode do you use?

AlexxIT avatar Apr 11 '22 16:04 AlexxIT