wow, migrated to this now, removed alex
nice to see now finally LIVE view without a delay on the camera entities!!! much appreciated! much better now then the custom card before
thnx again!!
3 Likes
Crap, seems if i use mobile connection on my android, the feed is gone
when i turn on wifi again, (local network) feed is back…
Does the camera only works locally??? is this a limitation?
with Alex custom card it worked on wifi and mobile
thnx
EDIT: ok, i think why, we also need 8083 to be open in firewall?
ok, then i can see the dasbboard now, externally, what is the default username/password anyway?
But it still doesnt work, i use nabucasa url, so my guesst it doesnt find the camera on my nabucasaurl on port 8083 ? can this be configured somewhere so it uses my public ip/dns instead?
1 Like
I also removed alex custom integration but still get these error 8083 in use 
can’t figure out what application / addon uses this port.Netstat gave me same result
LOL i still had alex addon running… stupid me … back in my hole …
3 Likes
How will i get the sound running?
And it is not clear for the moment how to add this cameras to ha. have frigate also setup but only cameras from frigate are there?..a bit confusing 
1 Like
See RTSPtoWebRTC - Home Assistant (home-assistant.io), you should be using the RTSPtoWebRTC-addon (for the sake of clarity: not the RTSPtoWeb-addon) and keep this in mind: “Audio Codecs Supported: pcm alaw and pcm mulaw”.
- Add your camera to the configuration.yaml
Generic Camera - Home Assistant (home-assistant.io) - Add the picture entity card to your dashboard
Picture Entity Card - Home Assistant (home-assistant.io) - The stream is automatically using WebRTC instead of HLS. (see “Technical Details” in the first post)
I am experiencing the same issue. The custom webrtc component had some instructions on how to setup external access, so maybe that’s something that isn’t yet implemented in the add-ons of @allenporter ?
I didn’t have todo anything , remote access was just working with the Lovelace card before… I think it’s b cause of the frontend card itself that makes connection…
I hope it’s possible, and also without port forwarding…
already tried to add this cam in frigate card? does not work for me for live provider
No MSE. The port thing could work? It’s using default config.json, but maybe would be cool to expose the port list in the add on. I haven’t tried it.
No MSE , so remote connect not yet available? Is it on todo list?
Does the RTSPtoWeb - WebRTC add-on support the extra Video Endpoints? I’m trying to view the http feed but I can’t get it working (following the example
http://{my_ip}:8083/stream/{entity_id}/channel/0/webrtc ). I’m just getting a ‘404 page not found’ error.
However I can view the feeds from Home Assistant within the webgui
I am facing the same issue
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[14:10:34] INFO: Starting discovery service
[14:10:34] INFO: Starting RSTPtoWebRTC
2022/02/03 14:10:34 Server Start Awaiting Signal
2022/02/03 14:10:34 Start HTTP Server error listen tcp :8083: bind: address already in use
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
Did you stop/uninstall Alex’s WebRTC addon? You must do that or you won’t be able to start this new one.
But, i managed to add camera only to figured it out same thing as others: camera is not available from outside. Since in Alex’s addon camera IS available from outside i guess that i’ll stick with Alex addon for now.
1 Like
Alex addon? You mean his custom component, right?
I’m not getting this… WebRTC streams should be visible on the lovelace cards without having to open external ports right? It’s not working for me… I can view all streams internally using either camera entity or RTSPtoWeb GUI, but externally they all fail. The log says:
2022/02/03 21:30:51 http: panic serving 172.30.32.2:44344: write tcp 172.30.32.1:8083->172.30.32.2:44344: write: broken pipe
goroutine 4104 [running]:
net/http.(*conn).serve.func1(0xc0003b21e0)
/usr/lib/go/src/net/http/server.go:1804 +0x153
panic(0xc86e40, 0xc00035b130)
/usr/lib/go/src/runtime/panic.go:971 +0x499
github.com/gin-gonic/gin.(*Context).Render(0xc003004200, 0xc8, 0xe618e8, 0xc001986030)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:928 +0x17c
github.com/gin-gonic/gin.(*Context).HTML(0xc003004200, 0xc8, 0xd56920, 0xa, 0xc72b40, 0xc000b110b0)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:937 +0x99
main.HTTPAPIServerIndex(0xc003004200)
/build/github.com/deepch/RTSPtoWeb/apiHTTPRouter.go:164 +0x237
github.com/gin-gonic/gin.(*Context).Next(...)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:168
main.CrossOrigin.func1(0xc003004200)
/build/github.com/deepch/RTSPtoWeb/apiHTTPRouter.go:313 +0x3c3
github.com/gin-gonic/gin.(*Context).Next(...)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/context.go:168
github.com/gin-gonic/gin.(*Engine).handleHTTPRequest(0xc0003664e0, 0xc003004200)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:555 +0x2b0
github.com/gin-gonic/gin.(*Engine).ServeHTTP(0xc0003664e0, 0xe66630, 0xc0004b20e0, 0xc003004100)
/root/go/pkg/mod/github.com/gin-gonic/[email protected]/gin.go:511 +0x16b
net/http.serverHandler.ServeHTTP(0xc0004b22a0, 0xe66630, 0xc0004b20e0, 0xc003004100)
/usr/lib/go/src/net/http/server.go:2867 +0xa3
net/http.(*conn).serve(0xc0003b21e0, 0xe687e0, 0xc000ee0dc0)
/usr/lib/go/src/net/http/server.go:1932 +0x8cd
created by net/http.(*Server).Serve
/usr/lib/go/src/net/http/server.go:2993 +0x39b
Yeah I reverted back too, too bad tough, really liked it…
But I need external access
1 Like
Hi Allen,
Thanks so much for your hard work with the add-on and integration. I have gotten it working.
I do find there is about 5-6 second delay for the feed to start. Sometimes the card is black and doesn’t load, the webpage needs to be refreshed to display the video.
Regards,
Sam
Why should we be using an add-on for this when the integration from Alex worked?
I too was confused when I went to integrations and it wanted a url. Text on the integration setup screen to say install the add-on first would help.
1 Like