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.

[lolfonfire]

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

[fgonza2]

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

[mortenmoulder]

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

[mishoboss]

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.

[fedemartino]

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

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

[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

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

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!

[Mark612]

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.

[homeoneautomacao]

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

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

[maximatchev]

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

[AlexxIT]

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

[TomKranenburg]

Just an update, I solved this issue by going to edit mode in the dashboard at the top right:

The the top right again select "Manage Resources":

You should see the WebRTC script being loaded here:

Just add a "=" symbol between the v and the version number like so:

Then restart. This fixed it for me. Somewhere there will be a component throwing a fit over the URL parameter not being perfect probably. It might even be browser dependant.

[kvikindi]

You lovely human bean! This absolutely fixed it for me! Cheers.

[AlexxIT]

Once again. Check if link works for you http://hassip:8123/webrtc/webrtc-camera.js

The component automatically configures resources when setting up the integration. If you don't use "lovelace mode yaml" and older browsers - you shouldn't have problems.

Possible problems:

• you haven't setup integration
• you using "lovelace mode yaml" and haven't setup resources (do not use this mode if you do not know how to use it)
• you copy webrtc-camera.js to www/hacsfiles/community and broke something (this was a bad idea)
• you using mobile app and have problems with cache
• you using an old browser, which is causing JavaScript errors for this component

[bigsem89]

Non of this related to me.

[fgonza2]

this should be your #1 issue. I updated to 3.2.1 still custom element doesn't exist. Nto sure what else to do, even manually installing 3.2.1 doesn't work anymore

[bigsem89]

I've realized that it works for direct link. but my HA is behind nginx.
what do i need to make it work?

[fikander]

Perhaps this should be obvious, but after couple hours of debugging I realised, that integrations don't get set up unless there's configuration entry using them.
For me, webrtc wasn't setup up (no services, no custom card), until I added artificial entry using platform: webrtc in configuration.yaml and restarted HA:

media_player:
  - platform: webrtc
    name: Dummy camera
    stream: some_stream
    audio: pcmu/48000

What helped with debugging was turning logging on to observe what integrations are being set up with

logger:
  default: info
  logs:
    custom_components: debug

After restart there should be Setting up webrtc entry if webrtc is being set up when you load all the logs in http://{HOMEASSISTANT}/config/logs

Hope that helps!

[AlexxIT]

Integration don't get setup if you not setup it...

https://github.com/AlexxIT/WebRTC#configuration

[fikander]

Lol. Thanks @AlexxIT. I missed that step indeed!
Just starting with the system and tried to find out in the HA core how integrations get set up. They need some configuration, and I missed the fact, that installing it via HACS doesn't actually create one.

[AlexxIT]

Yes. HACS just download integration source code. Hass won't use this new code if you not ask it.

[AlexxIT]

You're wrong on both "should be"

[AdrianGarside]

For those confused why adding it by HACS, restarting HA, then adding it as an integration still gave this error. Ctrl-Shift-F5 to force a refresh of the browser was necessary for me to fix it. I'd added a card manually and pasted the content in because it wasn't showing as an available custom card. At which point I got the error. And after fixing the error then ctrl-shift-F5 it also then showed as an available custom card.

[tclemos]

• you haven't setup integration

that's it! 🎉

[jturn08]

I'm missing the webrtc camera lovelace card in the default dashboard (I'm not using a custom dashboard). Any tips on how to troubleshoot?

In Home Assistant logs, I see error message "Setup failed for 'type': Integration not found." after updating HomeAssistant configuration.yaml to add type: 'custom:webrtc-camera'.

• WebRTC installed correctly via HACS
• WebRTC Camera installed via Configuration -> Integrations
• Cleared browser cookies, tried different web browser.
• Successfully configured go2rtc.yaml and go2rtc web page and cameras are viewable at http://homeassistant.local:1984/
• Verified http://homeassistant.local:8123/webrtc/webrtc-camera.js is working

[AlexxIT]

If /webrtc/webrtc-camera.js working for you - you probably using lovelace mode yaml without manual including this link to resources.

[jturn08]

If /webrtc/webrtc-camera.js working for you - you probably using lovelace mode yaml without manual including this link to resources.

Thanks for trying to help, but it doesn't seem like I am not using lovelace mode yaml (my configuration.yaml doesn't have lovelace: mode: yaml).

Under Settings -> Dashboards, I see "Overview" dashboard. If I select Overview dashboard, I see "The default dashboard, Overview, cannot be edited from the UI. You can hide it by setting another dashboard as default."

Under Settings -> Dashboards, after I click the three dots menu (top-right) and select Resources, I see an entry for a JavaScript modeul with URL = "/webrtc/webrtc-camera.js?v=v3.5.1"

On the Overview dashboard, after I click the three dots menu (top-right) and select "Edit dashboard", and then after I click the three dots menu (top-right) and select "Raw configuration editor", I see the following

strategy:
  type: original-states
  areas:
    hidden:
      - bedroom_2
    order:
      - bedroom
      - bedroom_3

If WebRTC isn't displayed on the default "Overview" dashboard by default without editing dashboard configuration, that's fine. I can create a custom dashboard. But I was expecting WebRTC cameras to be automatically displayed on the default "Overview" dashboard.

[zeddski]

Just an update, I solved this issue by going to edit mode in the dashboard at the top right:

The the top right again select "Manage Resources":

You should see the WebRTC script being loaded here:

Just add a "=" symbol between the v and the version number like so:

Then restart. This fixed it for me. Somewhere there will be a component throwing a fit over the URL parameter not being perfect probably. It might even be browser dependant.

Mine was slightly different, but your answer did give me a clue:

This was my URL. Removed the second "v", with this result:

And now I have a working card. Now, to configure the camera's....

[Jurrjuna]

Just an update, I solved this issue by going to edit mode in the dashboard at the top right:

The the top right again select "Manage Resources":

You should see the WebRTC script being loaded here:

Just add a "=" symbol between the v and the version number like so:

Then restart. This fixed it for me. Somewhere there will be a component throwing a fit over the URL parameter not being perfect probably. It might even be browser dependant.

Mine was slightly different, but your answer did give me a clue: This was my URL. Removed the second "v", with this result: And now I have a working card. Now, to configure the camera's....

It didn't solve my issue when casting to chromecast. I noticed /webrtc/webrtc-camera.js?v=3.5.1 changed back to /webrtc/webrtc-camera.js?v=v3.5.1 after restart HA. Am I doing something wrong or is it stored somewhere else?
And can this be related to issue #678?