Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom element doesn't exist: webrtc-camera #260

Open
Dim3333 opened this issue Feb 14, 2022 · 85 comments · Fixed by #497
Open

Custom element doesn't exist: webrtc-camera #260

Dim3333 opened this issue Feb 14, 2022 · 85 comments · Fixed by #497
Labels
question Further information is requested

Comments

@Dim3333
Copy link

Dim3333 commented Feb 14, 2022

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
Copy link

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

@Dim3333
Copy link
Author

Dim3333 commented Feb 14, 2022

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
Copy link
Author

Dim3333 commented Feb 15, 2022

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

@alexvenom
Copy link

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
Copy link

slash133 commented Feb 20, 2022

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

@fedemartino
Copy link

same problem on version: 2022.3.0
image

any ideas?

@BabaBoch1
Copy link

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

@lolfonfire
Copy link

lolfonfire commented Mar 11, 2022

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

@BabaBoch1
Copy link

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.

@Dim3333
Copy link
Author

Dim3333 commented Mar 12, 2022

Hi,

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

@wowgamr
Copy link

wowgamr commented Mar 13, 2022

Same error for me after update to 2022.3.3.

@MagellanOo
Copy link

MagellanOo commented Mar 13, 2022

Same issue for me after performing the update to 2022.3.4.

@wowgamr
Copy link

wowgamr commented Mar 14, 2022

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

@jaegerschnitzel
Copy link

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.

@Mark612
Copy link

Mark612 commented Mar 17, 2022

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

@lolfonfire
Copy link

lolfonfire commented Mar 18, 2022

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
Copy link

fgonza2 commented Mar 18, 2022

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
Copy link

mortenmoulder commented Mar 21, 2022

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

@mishoboss
Copy link

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
Copy link

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

@MercerK
Copy link

MercerK commented Mar 25, 2022

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
Copy link

fgonza2 commented Mar 25, 2022

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
Copy link

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
Copy link

Mark612 commented Mar 27, 2022

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
Copy link

homeoneautomacao commented Mar 28, 2022

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
Copy link

georaspi commented Apr 3, 2022

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
Copy link

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 AlexxIT added the invalid This doesn't seem right label Apr 10, 2022
@AlexxIT
Copy link
Owner

AlexxIT commented Apr 10, 2022

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 AlexxIT closed this as completed Apr 10, 2022
@AlexxIT AlexxIT added the question Further information is requested label Jul 20, 2023
@AlexxIT AlexxIT reopened this Jul 20, 2023
@AlexxIT
Copy link
Owner

AlexxIT commented Jul 20, 2023

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
Copy link

Non of this related to me.

@fgonza2
Copy link

fgonza2 commented Jul 23, 2023

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
Copy link

bigsem89 commented Jul 23, 2023

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

@fikander
Copy link

fikander commented Aug 5, 2023

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
Copy link
Owner

AlexxIT commented Aug 5, 2023

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

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

@fikander
Copy link

fikander commented Aug 5, 2023

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
Copy link
Owner

AlexxIT commented Aug 23, 2023

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

@AlexxIT
Copy link
Owner

AlexxIT commented Sep 20, 2023

You're wrong on both "should be"

@AdrianGarside
Copy link

AdrianGarside commented Nov 15, 2023

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
Copy link

tclemos commented Dec 3, 2023

  • you haven't setup integration

that's it! 🎉

@jturn08
Copy link

jturn08 commented Feb 5, 2024

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

@AlexxIT
Copy link
Owner

AlexxIT commented Feb 5, 2024

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

@jturn08
Copy link

jturn08 commented Feb 6, 2024

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
Copy link

zeddski commented Apr 5, 2024

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

Mc2vOshJqN

The the top right again select "Manage Resources":

icWp0rbpkg

You should see the WebRTC script being loaded here:

iGKD4c1g3w

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

Z8tO91EGh0

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:
image
This was my URL. Removed the second "v", with this result:
image
And now I have a working card. Now, to configure the camera's....

@Jurrjuna
Copy link

Jurrjuna commented Apr 6, 2024

Just an update, I solved this issue by going to edit mode in the dashboard at the top right:
Mc2vOshJqN
The the top right again select "Manage Resources":
icWp0rbpkg
You should see the WebRTC script being loaded here:
iGKD4c1g3w
Just add a "=" symbol between the v and the version number like so:
Z8tO91EGh0
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: image This was my URL. Removed the second "v", with this result: image 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?

@mrreview
Copy link

Just an update, I solved this issue by going to edit mode in the dashboard at the top right:
Mc2vOshJqN
The the top right again select "Manage Resources":
icWp0rbpkg
You should see the WebRTC script being loaded here:
iGKD4c1g3w
Just add a "=" symbol between the v and the version number like so:
Z8tO91EGh0
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: image This was my URL. Removed the second "v", with this result: image And now I have a working card. Now, to configure the camera's....

That did the trick. Thank you.

@ENWOD
Copy link

ENWOD commented Oct 25, 2024

I am experiencing this same issue with a Home Assistant Container, Go2RTC running in a docker and Web2RTC installed.

I can view a video stream using a customer Web2RTC card but when I try to cast a dashboard with a panel layout. I get this error on my Google Nest display.

Any ideas - I've tried the "v=" removal of the resource mentioned above but no luck and nothing showing in the logs.

@ChayoteJarocho
Copy link

The /webrtc/webrtc-camera.js method worked for me. I was seeing this problem in my laptop's web browser.

But before removing/adding the js resource, I first made sure that I could access that javascript file directly by going to http://homeassistant.local:8123/webrtc/webrtc-camera.js (or whatever your url is). If the file loads, then the next step is to add the version to see if it loads. I appended ?v=3.6.0 (that's the version of the integration that's installed in my HA at the moment) and I could confirm it loaded correctly.

Lastly, I added the resource to the dashboard per the instructions above. But the important part here is to REFRESH the webpage after doing that, because the javascript file does not get loaded automatically after you add the resouce, meaning that if you go back to the dashboard to try to add a custom:webrtc-camera card again, you will keep seeing the same failure!

I'm surprised Home Assistant does not reload the page automatically for me after adding the javascript resource. Considering HA suggested me to refresh the page after I deleted a resource, I don't see why not suggest the same when adding it. Oh well.

I think I saw some comments above suggesting to reload/restart HA after updating the javascript resource, but that won't work if you keep the browser page open without refreshing it: the js resource won't get loaded!

Anyway, after refreshing, you can add the custom:webrtc-camera card to your dashboard. The error should go away, and you'll be able to see the camera preview.

@AlexxIT
Copy link
Owner

AlexxIT commented Nov 26, 2024

webrtc-camera.js is a static file. Any query parameters (e.g. ?v=3.6.0) have no effect on static files at all.
The only thing they affect is requesting the file bypassing the cache. The value of this parameter is completely unimportant.
It could be anything. For example /webrtc/webrtc-camera.js?i_hate_element_not_exist_error=1.

@kanagawawave
Copy link

If you have trouble finding the "Manage resources" button, enable the Advanced Mode:
https://developers.home-assistant.io/docs/frontend/custom-ui/registering-resources/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.