what dashboard do u use? something like dwan’s dashboard? or HKI?
I made a script wich is called when clikcing on the camera image on my dasboard (hki and dwain’s) you can also make a glance picture thing and call a script. mine looks like:
I have 2 way audio working using sip between the doorbell and a softphone installed on the receiving tablet so far and I currently have 1 way audio and video using Alexxit’s component in WebRTC. I am using freepbx (asterisk) that is running as a virtual machine on my network the only thing currently blocking 2 way audio is I can’t work out how to create a CA authority certificate that has a hostname that resolves to the virtual machine on my local network, but I think that once that’s working the 2 way audio will work and the Alexxit’s component proves that it’s worth doing using webrtc!
The latest version has changed the default setting of the UDP port range. If you have changed it before - set two zeros in the integration settings and disable UDP port forwarding on the router.
This should work fine for most users.
Use port forwarding only if you’re having trouble connecting.
A small number of ports with a large number of cameras on a page works very badly. There should be many more ports than cameras.
HassOS is running in a VM. Tried to add a Sonoff Camera but while it sometimes seems to work it stays forever on ‘init connection’, then ‘trying to start stream’. Sometimes it shows the stream, sometimes it don’t. When showing the stream you can the stream hanging (seconds don’t update) and eventually stops and tries to reconnect.
VM is running on a new i3 NUC and MotionEye run2 three rtsp stream easily (in a different VM). Also tried to stop the MotionEye container, but that doesn’t help.
And the rtsp streams work perfectly in MotionEye as well. Tried both accessing the HA instance through local IP (no SSL) and external domain through NGINX + SSL.
habe the same issue since today Opera not supported. i use chrome not opera and i have all cams running well . i ununstalled and added the component again but no success … any solutions here? logs:
Is there any way to hardcode that it opens in fullscreen was watchng the code but didn’t find the right part of the code i fear Maybe it’s possible to have a config opetion to start stream in fullscreen?
Thank you @AlexxIT. I have had a Grandstream GDS3710 door station and the lag on video made it very unfriendly. With you project it is working well. Thank you so much.
I am finding since the last update that the card seems to be takign a long time to start.
The card is saying Init connection and if I hit f12. I see the following. The logs seem normal.
‘Uncaught DOMException: Failed to execute ‘define’ on ‘CustomElementRegistry’: the name “webrtc-camera” has already been used with this registry’
Do you have any suggestions.
Thank you again for this amazing project.
I’m getting the same issue with 1.3: Chrome reports same DOME exception.
Strangely it works for me on android (either in HomeAssistant app or in Chrome for android)
The debug log reports:
2021-04-23 13:46:30 DEBUG (webrtc) [custom_components.webrtc.utils] [GIN]
2021/04/23 - 13:46:30 | 200 | 63.28649ms | 127.0.0.1 | POST "/stream"
2021-04-23 13:46:30 DEBUG (MainThread) [custom_components.webrtc] New stream to url: rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov
2021-04-23 13:46:34 DEBUG (webrtc) [custom_components.webrtc.utils]
2021/04/23 13:46:34 Client Not Send ACK (probably the browser is minimized) or tab not active Close client
2021-04-23 13:46:34 DEBUG (webrtc) [custom_components.webrtc.utils]
2021/04/23 13:46:34 Stream Not Send Video Close
2021-04-23 13:46:34 DEBUG (webrtc) [custom_components.webrtc.utils]
2021/04/23 13:46:34 WritePacket WebRTC Client Offline
I haven’t tried rolling back to different versions, but I just tired Edge and the card loads in a few seconds, yet with Chrome it takes around 40 seconds and shows init connection during that time. I would prefer chrome. Any suggestions why Edge works so much faster than Chrome?